Hello,
I see some problems when running the script as well. It seems there are some slight problems communicating with the Scilab software.
First, when looking at the text in the Scilab script node, I see an extra character before the new line. Upon closer investigation, the script contains both a carriage return and a line feed at the end of every line. This currently causes a problem with the Scilab software. I was able to eliminate the extra character (the CR) by loading the script from disk in a text editor and copying and pasting it into the script node.
Second,
getcwd may not return what you expect. It is not the directory in which the VI resides (unless you happened to put the VI in Scilab's default working directory). You can find out what it returns by simply calling that function and then creating a string output variable on the script node. Another method to specify the location of your data file is to pass in a string that is the current VI's location on disk. You can find this using the Programming >> File I/O >> File Constants >> Current VI's Path primitive. Simply use the Strip Path primitive to get the directory name. Wire that into the script node as a string input and then append the filename like you currently do.
Third, comments in the script seem to cause some problems. The script node doesn't actually return an error, but most of the script simply doesn't execute. Try removing all your comments from the script.
Last, the Scilab-LabVIEW Gateway currently does not support plotting from the Scilab software, so your plot commands will not work.
Grant M.
Staff Software Engineer | LabVIEW Math & Signal Processing | National Instruments
