06-06-2019 02:01 AM
What's the compatible version of simulink and software in crio 9063? Should Simulink be transferred into so. or dll. ? And how to deploy the transferred file in labview in crio 9063?
06-06-2019 05:28 PM
Jeannie Falcon at NI has done some talks about the options - so look for those first.
Have you looked into NI's Veristand for this? You would also need a the Simulink Coder to generate a real-time executable.
You should also consider any features of your Simulink model that might need changed to make compatible with the route you take - for example if you are using any toolboxes, variable time step solvers, etc
There is also something called LHP Pantera which targets certain cRIO models directly from Simulink - again some limitations on what it can handle.
If your Simulink model is simple enough a manual conversion may be the quickest rather than trying to get the various tools to connect. If your Simulink model is in the form of a scriptted s-function, it is fairly easily to map the different parts of the s-function into an equivalent structure in LV Real-time and Mathscript nodes.
06-07-2019 10:09 PM
Actually, I tried to use 2017 eclipse and 2017 ni veristand to transfer simulink into .so file. Error code shows error locating the NI linux real-time 2014 toolchain as shown in the figure. When I applied 2014 eclipse and 2017 ni veristand, the compiling process could be done without any error code. But the result in labview turned out to be wrong and constant when deploying the transferred .so file.
06-08-2019 03:25 PM
There's a link about compatibility checks in this notes:
https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P7qZSAS&l=en-GB
But, I guess you know all this and probably need more specialist support from one of the NI Technical team.