scilab

[Alan at BAE]

I am running SP3 with no problems now.

[GrantM]

Hello,

The Scilab developer I spoke with noted it was a problem on their end.  A workaround is to not install Atlas during Scilab installation or to install MKL for Scilab immediately after installation.  He noted that it is fixed in the latest daily build of the master branch (not the 5.0 branch).  If you wish, install the latest version from http://www.scilab.org/download/index_download.php?page=nightly_builds. 

Grant M.
Staff Software Engineer | LabVIEW Math & Signal Processing | National Instruments

[chaosguy]

Looks like using the latest build does the trick.  If you have any clout with the Scilab folks, I'd be grateful if you could encourage them to make an official release that clears up this kind of issue.  I'm actually teaching a course on control theory (for science students, not engineers).  We use LabVIEW primarily (so that we can interact easily with DAQs, etc.), but I would like to be able to occasionally include some Scilab scripts.  I'd be more comfortable asking students to download a proper Scilab version......

Many thanks! 

[chaosguy]

Further to this issue, I tried the new Scilab 5.1.  As long as you don't install fftw (the default), the gateway interface seems to work fine.

[mtang]

Hi Grant, I am a fresher of LV and have used Scilab before. I have LV8.6 installed and want to use the labview_scilab_script_node for my application. I have unzip the labview_scilab_script_node files based on the readme file, now I have the following problems:

1. At first, I installed the latest stable version of Scilab, version 5.1.1. But when I open the example vi in C:/Program Files/National Instruments/LabVIEW 8.6/examples/Scilab , it return a error of R6034:  An application has made an attempt to load the C runtime library incorrectly, then followed by a Labview error (1046) that it cannot initiate the script server.

2. As your mentioned, I uninstall Scilab5.1.1 and install the latest Nightly builds: scilab-master-1244748622. This time, when I open the example vi from LabVIEW 8.6/examples/Scilab no such error appears but the labview software stops to response and what I can do is to close the non-responding labview process. 

I am really confused about the problem, need help and solutions from community, thanks!

[GrantM]

Hello,

I have asked the developer of Scilab which stable version will have the fix.  I will update you when I hear back.  The latest nightly build is probably not stable enough to use for regular development.  It is mainly to use to verify a bug has been fixed.

Using the 5.1.1 stable release, have you tried the workaround of not installing Atlas during Scilab installation or instead installing MKL for Scilab after installation?

Grant M.
Staff Software Engineer | LabVIEW Math & Signal Processing | National Instruments

[GrantM]

Hello,

The Scilab developer believes the original problem is fixed and would like to have some additional information from your system.  Can you type the following command in the Scilab software and post the output:

[a,b] = getdebuginfo()

Also, can you post your "C:\Program Files\<scilab>\bin\SetupAtlas.log" file, if it exists?  Did the workaround of not installing Atlas fix the problem for you?

Grant M.
Staff Software Engineer | LabVIEW Math & Signal Processing | National Instruments

[mtang]

Hello, Grant,

I did not install the Atlas in Scilab5.1 or latest nightly build master edition, but problem was still there.

Then I tried to install the Scilab branches-5.1-1244653915, with FFTW, without MKL and Atlas, then everything runs smoothly. But if I install MKL, error message will be shown. Hope this information will be helpful for other users.

As you request, I post the output of getdebuginfo here, in attachment

[GrantM]

Hello,

Okay, it looks like we have a slight misunderstanding here.  You have said that the latest nightly build does not exhibit the problem, but that it seems to hang.  This is likely a result of an unstable release.  Since this build does not exhibit the problem, the debug information is not as useful.  Try the following:

• Remove all Scilab installations from your system
• Install Scilab 5.1.1 without Atlas

Do you still have the problem?  If so, can you get the debug information and post it again?

Grant M.
Staff Software Engineer | LabVIEW Math & Signal Processing | National Instruments

[candidus]

Hello there,

I stumbled upon the same problem using LabVIEW 8.0 and SciLab 5.1.1 with FFTW and MKL.

It seems that the problem has something to do with MKL, not FFTW:

SciLab scripting works properly since I deinstalled MKL.