From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
04-21-2008 08:20 AM
04-21-2008 11:00 AM
Hi DK_bp
The OS on the 9014 and 9012 cRIO controllers is VxWorks. This means that you cannot run a DLL in these controllers. That is why when you run the sinewave example nothing works. For these VxWorks controllers you need to convert your model into an .OUT file instead of a .DLL file.
If you want to run SIT in a 9014 controller you will need the following things:
1.- A VxWorks compiler - Developing Shared Libraries for the cRIO-901x and Other VxWorks Targets
2.- LabVIEW SIT 4.0
3.- Some extra files to enable support for VxWorks. SIT 4.0 as shipped doesn't have full support for VxWorks. You will need some files that we (NI) can give you.
Do you have a Service Request number or an e-mail address I can use to contact you directly?
Thanks
Ricardo Santa Olalla
Systems Engineering
National Instruments
04-21-2008 12:49 PM - last edited on 04-21-2008 04:19 PM by Support
07-03-2008 09:46 AM
Hi Ricardo,
We have just had one of your field engineers come in today and show us the cRIO. We are interested in the 9014, hence the VxWorks Platform. We asked him about the compatibility of Simulink, SIT and VxWorks and he didn't know of any problems. From reading this post it does not seem very straight forward compared to using the ETS platform.
He did mention that around August there may be a new version of LabView on the way out. Would you know if in this new version if the integration between Simulink, SIT and VxWorks is any smoother.
Many Thanks
Alex
07-07-2008 09:57 AM
Hi Alex,
The only reason why support for VxWorks is not as straightforward as ETS is because you would need to install a patch. Installing this patch only requires to copy some files into three different folders.
This patch will be included in the next release of SIT so the only other thing you will still need will be the compiler for VxWorks, which you can download for free from our web in case you don't have already one.
Once you have the patch installed, compiling the model into an .OUT file (shared library for VxWorks, instead of DLL) is the same process as compiling the model into a DLL.
The only difference between using SIT for ETS and SIT for VxWorks is if you want to use the SIT Connection Manager (a wizard that generates LabVIEW code for you). SIT Connection Manager reads a list of parameters and signals from the model DLL. Since an OUT file cannot be read in a Windows computer, the SIT Connection Manager cannot get this list from an OUT file. To solve this problem, we just give a model DLL to SIT Connection Manager so that it can get this list and do its magic. Keep in mind that the OUT file is still what gets deployed and used by the VxWorks target and not the DLL.
Having to provide a DLL to the SIT Connection manager is the only hurdle you will have if you want to use SIT in a VxWorks target and only if you want to use the SIT Connection Manager. If you want to discuss this a bit more, please let me know if it is OK for me to access your e-mail address from your Discussion Forum account and I'll contact you directly to discuss further this or any other question you might have.
Ricardo
04-23-2009 07:42 AM
Hi Ricardo SR,
I have the same case as DK_bp.
How kann I get the extra files to enable support for VxWorks ?
My email adress is : mehdi.meddeb@mytum.de
And is there any easy solution to convert the mdl file into an .OUT file ?
Thank you very much !!!
04-23-2009 03:07 PM
07-09-2009 09:34 AM
Hello Ricardo,
I know it's toooooo late, but I want say thank you very much !!!!!!!!!!!!!!!!!!!!!!!!!
Mehdi.
07-09-2009 09:37 AM
Hello Mehdi,
You are welcome. Did you get it working?
Ricardo
07-09-2009 10:07 AM
Hallo Ricardo,
yes ! Thank you again 🙂
now I have other Problems concerning Simulation Interface Toolkit mappings.
When I try to map large arrays (<10001x2 double>,...) to Simulink constants, I get an overflow Failure 62. (see attachment, sorry it's in German).
Now I have following questions:
- How can I avoid this overflow Failure 62 !
- Can you explain me what is the difference between SIT In/Outs and normal Simulink In/Outs ?
- How can I prepare CAN Data (Variables) in the Simulink Model (.out File) ; what kind of Output Variables I must have, to do CAN Mappings. (I have the CAN Module NI 9853 with cRIO 9014).
Thank you again !
Mehdi.