scilab

[chaosguy]

I'm having what may be a variant of this problem.  The first time I use a vi with a scilab node, everything is ok.  But when I try to load a second vi or add a scilab node in a new vi, LabVIEW hangs and stops responding.

I've tried removing and reinstalling all of my NI applications and reinstalling Scilab and the Scilab-LabVIEW gateway, to no avail.  (It seems, however, that uninstalling LabVIEW is not working perfectly, as when I reinstall it, it still has retained some user information, such as "favorite" LabVIEW nodes). 

LabVIEW 2009 (and also 8.6 with same result), Scilab 5.2.2 (but I've tried 5.2.1 and 5.1.1, with same results). Gateway = 1.1 (Dec. 2008 version).

Since LabVIEW may still retain some files after uninstalling, maybe one of those got corrupted?  If so, what to do?

Thanks for any suggestions.

John 

[chaosguy]

Further to this issue, an applications engineer at NI confirmed the bug and is looking into it.  The workaround is to open a new vi and put a scilab node in it.  As long as this "dummy vi" is not closed, one can open and close vi's with scilab nodes in them without crashing (or problems running the vi's).

[Gordal]

Any news yet about a bug fix?

[chaosguy]

Some more details:  While this is a verified problem with Scilab 5.2.2, Scilab 5.1.1 is ok (not sure about 5.2.0 and 5.2.1).  Apparently, there is an issue in the communication between LabVIEW and Scilab DLLs.  The issue has been flagged within NI.  Since the Gateway does not ship with LabVIEW, fixing it is not at the top of NI's priority list.  On the other hand, some encouragement from other users might help to move it up.....

[Gordal]

Is the code for the DLL available to the public?

[chaosguy]

Not as far as I know....  (I'm just a user -- no special connection to either the LabVIEW or Scilab side.)

[Gordal]

I have a feature request: can labview report the actual error issued by scilab instead of saying 'Labview: Error occured while executing script.'??

[chaosguy]

In the latest beta of Scilab 5.3 (5.3.0.beta3), the issues in the dll described above seem to have been resolved. I can now get LabVIEW 2009 SP1 to run with this Scilab version (using Gateway 1.1).

As before, when installing Scilab, one should NOT install the fftw package.  (Since that package is installed by default, this means that one needs to do a custom install.  Failure to do this results in LabVIEW's not finding Scilab and a "1046" error.)

[OttoBerge]

I am experience a very strange problem.

I can only open SciLab scripts in vis with Scilab 5.3.0_64bit and Labview 8.5 32 bit, however when I run them I receive Error 1046. If I uninstall SciLab 5.3.0_64bit and install SciLab 5.3.0_32bit as suggested. Labview crashes before it completely load the vis with SciLab. It also crashes is I insert a Scilab script into a blank vi.

Any help would be great.

[GrantM]

Hello,

The Scilab API changed in version 5.2.  The LabVIEW to Scilab Gateway relied on this API for proper communication.  This is why version 1.1 of the LabVIEW to Scilab Gateway did not function properly with Scilab version 5.2 and later.  In order to update the LabVIEW to Scilab Gateway, some changes were necessary to the Scilab software as well.  We now have a new version of the LabVIEW to Scilab Gateway available.  Download it from http://bit.ly/ScilabLabVIEW.  You will also need to use Scilab 5.3, available from http://www.scilab.org.  The new version also adds support for 64-bit LabVIEW and Scilab as well as a few new data types.

As for the problem you mention, OttoBerge, you will need to have 32-bit or 64-bit versions of both software installed.  The LabVIEW to Scilab Gateway will not work with a 32-bit version of one and a 64-bit version of the other.  The previous LabVIEW to Scilab Gateway version did not support 64-bit, but the latest release does.

Grant M.
Senior Software Engineer | National Instruments