![]() ![]() Last, the Scilab-LabVIEW Gateway currently does not support plotting from the Scilab software, so your plot commands will not work. Inside a function, the first comment lines, up to the first instruction or an empty line may be used to provide the default. The slashes as well as all the following characters up to the end of the lines are not interpreted. Try removing all your comments from the script. A sequence of two consecutive slashes // out of a string definition marks the beginning of a comment. The script node doesn't actually return an error, but most of the script simply doesn't execute. Third, comments in the script seem to cause some problems. Recommandation: You should create a text file named for instance. user spends most of his time going back and forth between Scilab and a text editor. ![]() Wire that into the script node as a string input and then append the filename like you currently do. For Scilab user: you must replace the Matlab comment by its Scilab counterpart //. Scicos provides a block-diagram editor for constructing models. Simply use the Strip Path primitive to get the directory name. You can find this using the Programming > File I/O > File Constants > Current VI's Path primitive. 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 out what it returns by simply calling that function and then creating a string output variable on the script node. Right-click the action, select Add Keyboard Shortcut, and press the necessary key combination. In the search field, type Comment with block comment or Comment with line comment to locate the required action on the list. It is not the directory in which the VI resides (unless you happened to put the VI in Scilab's default working directory). Press Ctrl+Alt+S to open the IDE settings and select Keymap. Second, getcwd may not return what you expect. 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. This currently causes a problem with the Scilab software. Upon closer investigation, the script contains both a carriage return and a line feed at the end of every line. It seems there are some slight problems communicating with the Scilab software.įirst, when looking at the text in the Scilab script node, I see an extra character before the new line. I see some problems when running the script as well. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |