Re : Re: scilab

[AJ.Geissler]

Dear Community,

after installing the upgrade to Labview 8.5.1, Labview crashes

• when i try to open a vi, which contains Scilab Script Nodes or
• if i try to create a new Scilab Script node in an empty VI.

I've even installed the SciLab Gateway again and i've restarted my PC: The behaviour is still the same !

Does Labview 8.5.1 not support the SciLab Gateway ?

Thanks for your reply

Andreas

[GrantM]

Hello Andreas,

The Scilab script node behaves correctly here on a test machine with LabVIEW 8.5.1.  Did the Scilab script node work before you upgraded LabVIEW?  Are you using Scilab version 4.1.1 or later?

Can you try creating the Scilab script node another way?  Drop an Xmath script node or a MATLAB script node.  Right-click the node and select "Choose Script Server."  Then choose "Scilab script."  Does this work?

MATLAB® is a registered trademark of The MathWorks, Inc.

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

[AJ.Geissler]

Hello,

i've done some further investigations. Everythings works well, but i've done a thing, which should be mentioned.

On Friday afternoon, i've installed the alpha-Release of SciLab 5.1

Then after that, i've played with my new installation of Labview 8.5.1 and my SciLab-Files. Everything worked well !

On Monday (PC was rebooted during weekend ) i've detected the problem as described.

Now i've uninstalled SciLab 5-alpha and after that, i've even uninstalled and installed the SciLab-Gateway-Files. It seems to work again, with one negative effect.

The SciLab-Mathscript parts do not deliver results. I really have to create new SciLab-Script Nodes in my Labview VI's (content is the same).

Has anyone experiences with the SciLab Gateway and installing new versions of SciLab ?

Best Regards
Andreas

[GrantM]

Hello Andreas,

I was not able to get the alpha release of Scilab 5, but I found the beta-1 release.  I installed Scilab 4.1.1 and then Scilab 5 beta-1.  There is a small issue with registry settings.  Since you were able to make the Gateway work, perhaps this is an issue unique to the beta.  If you are comfortable editing your registry, navigate to HKLM\SOFTWARE\Scilab\scilab-5.0-beta-1.  Locate the SCIPATH value and change it to remove the double quotes around the path.  I have worked with the Scilab developers and this seems to be fixed in the latest daily build of Scilab.

If you uninstalled the alpha version, it is odd that you saw the behavior you did with old nodes failing but new nodes working.  Try editing your registry again.  Navigate to HKLM\SOFTWARE\Scilab and look at the LASTINSTALL value.  The contents of this will be the registry key used by the Gateway to read the SCIPATH value.  Make sure it is set to be the version of Scilab you wish to use.  If you are not comfortable editing the registry, reinstalling the previous version of Scilab will restore this value.

If you wish to use Scilab 5, try installing the latest daily build.  If you continue to see problems, indicate which daily build you are using and post the values of the following registry settings:
LASTINSTALL from HKLM\SOFTWARE\Scilab
SCIPATH from HKLM\SOFTWARE\Scilab\$(LASTINSTALL)

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

[chaosguy]

Hi, I may be having a related problem.  I am running Labview 8.5 and have installed Scilab 5.0.3 and the Labview-Scilab gateway software.  When I place a Scilab scriptnode and try to run it (or any of the pre-packaged examples), I always get the following error message:

Error 1046 occurred at LabVIEW:  LabVIEW cannot initialize the script server.  Ensure the server software is installed. in Untitled 1

If anyone has ideas on what has gone wrong, that would be great!  (I do start up Scilab before running Labview.)

[BachFugue]

Hi,

Trying to install the scilab-labview gateway, here's a result of my experimentations: OS: Vista x64 Business, Labview 8.2.1

1. I tried: Scilab-5.0.3 (x64) => no success (error 1046)
2. I tried: Scilab-5.0.3 (x86) => no success (error 1046). I edited the registry because the keys for Scilab are then in HKLM/Software/Wow6432/Scilab.
   So I supposed the gateway could not find the keys. I duplicated these two keys in  HKLM/Software/Scilab.I still had the same error.
3. I installed Scilab 4.1.2 and added the 2 keys. It seems to work fine.

There's no need to start Scilab before Labview.

My conclusion: scilab 5.0.3 is not supported (at least not on 64 bits platforms).

My suggestion: it would be convenient if the gateway looked also at the Wow6432 branch.

[GrantM]

Hello,

I have looked into this issue.  The LabVIEW to Scilab Gateway software will not work with the 64-bit version of Scilab or the 64-bit version of LabVIEW.  You need to have both the 32-bit version of Scilab and LabVIEW installed.

It is odd that your case 2 didn't work.  I installed Scilab 5.0.3 (x86) and was successfully able to run it from LabVIEW 8.6.  You are correct in that the registry keys in this instance are in HKLM\Software\Wow6432Node\Scilab, but the LabVIEW to Scilab Gateway software knows to look in this place for WoW applications.

Try removing all versions of Scilab and ensuring your registry settings are removed.  Then reinstall the 32-bit version of Scilab.

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

[Alan at BAE]

Hello:

I am having a somewhat different problem.  I am using LabVIEW 8.6 and just installed Scilab 5.0.3 (first time for any version of Scilab).  When I try to create a Scilab script node, I get an error from  "Microsoft Visual C++ Runtime Library" - An application has made an attempt to load the C runtime library incorrectly, followed later by the 1046 error if I try to run a VI with a Scilab script node.  I am using Windows XP, SP3 and 32 bit versions of all software, and Microsoft Visual C++ 2005 and 2008 Redistributable are installed.

This is the first time I have tried to use a Scilab script node so I have no prior success with prior versions of the software.  

Registry keys for Scilab were in HKLM\Software\Scilab\Scilab-5.0.3, and also an entry in HKCU\Software\Scilab\Scilab-5.0.3. 

Any thoughts? 

Alan 

[GrantM]

Hello Alan,

That is very weird behavior.  I also have those two redistributables installed on my system and that combination works without any problems.  Are you able to launch Scilab by itself?

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

[Alan at BAE]

Yes, Scilab seems to work normally.