11-05-2014 08:17 AM
I had test the (.so) file that use MIT example ( MIT Get Model Information.vi ),it can respond the shared library informations,I think it's ok!!
After I back office ,I will test function using MIT & deployed it to 9068...
I must offer my heartfelt thanks to you!!!
11-05-2014 08:17 AM
I would suggest using the MIT Inport and Outport example found in the example finder under Toolkits and Modules » Model Interface » MIT Inport and Outport.
The initialization section of the VI can be seen below. You should be able to execute this VI on the target and point it to the .so model in the filesystem, Then depending on what inports and outports you want to use you can modify the example to find the offsets of them in your model:
The loop part of the example looks like this:
You can see how the model gets executed every iteration and can be tied to other inputs and outputs.
11-05-2014 08:19 AM
We posted back at the same time
I'm glad that everything is working!
11-05-2014 08:26 AM
Ha..
you reply so soon!!
I already test it use MIT Tool!!
But when I add Take Model Time Step.vi ..LabVIEW always crash!!
I think maybe it need work in Linux platform...
11-05-2014 08:30 AM
11-05-2014 08:41 AM
Hm...I had compiler this .mdl with Pharlap two years ago,and deployed in PXI successfully!
Thanks!!!
11-06-2014 09:08 PM
hi...I want to talk you...I deployed .so to 9068 using MIT function that all goes well!!
Thank you again!!!!
I develop HIL system application..
But 9068 calculate too slow,I need more fast CPU...Maybe the only way is deploy on PXI system.
11-09-2014 03:51 AM
Hi...Sir!!
I have a question ...when I installer the 2014 eclipse package...
I can't find the path" <National Instruments>\Eclipse\toolchain\gcc-4.4-arm\i386\bin\" .....
But the 2013 eclipse package version had the folder!
Could you tell how resolved ..
thanks!!!
11-10-2014 12:06 PM
Well, for one the 2014 Tools updated the GCC version to 4.7.2.
This setup document does indicate the paths you're supposed to set within eclipse for the different targets:
http://www.ni.com/tutorial/14625/en/
Specifically section 4 item 14 notes:
In the Cross compiler path text box, browse to the location of the correct compiler for your target as specified in the following list:
(ARM-based targets, 2013 software stack) \<National Instruments>\Eclipse\toolchain\gcc-4.4-arm\i386\bin
(ARM-based targets, 2014 software stack) \<National Instruments>\Eclipse\14.0\arm\sysroots\i686-nilrtsdk-mingw32\usr\bin\armv7a-vfp-neon-nilrt-linux-gnueabi
(Intel x64-based targets, 2014 software stack) \<National Instruments>\Eclipse\14.0\x64\sysroots\i686-nilrtsdk-mingw32\usr\bin\x86_64-nilrt-linux
So, if you're compiling with the 2014 stack on a 9068 (ARM based) you'll choose the <National Instruments>\Eclipse\14.0\arm\sysroots\i686-nilrtsdk-mingw32\usr\bin\armv7a-vfp-neon-nilrt-linux-gnueabi path.
11-10-2014 08:00 PM
OK~~
I also need fix the Prefix path:"arm-nilrt-linux-gnueabi-"
It would be OK!!
Thanks a lot!