10-24-2008 01:48 PM
I have in the past created VxWorks shared libraries for use with the LabVIEW 8.2 and 8.5 Realtime Module and there were different toolchains required because of the change of VxWorks versions by these two LabVIEW Versions.
For informative purposes I would be interested to know if changing to LabVIEw 8.6 Realtime Module will require again a new compilation, or if this version still is based on the same VxWorks 6.3 kernel and my shared lib therefore would simply continue to work?
Rolf Kalbermatter
Solved! Go to Solution.
10-27-2008 07:24 AM
Dear Rolf,
Thank you for your post on our webforum. What type of hardware is involved in your configuration. I see different installers for the different hardware targets (under C:\Program Files\National Instruments\RT Images\Base\5.0 ) It isn't clear wich installer is for which target.
Is your target a cRIO 901x controller?
Best regards,
10-27-2008 07:29 AM - edited 10-27-2008 07:30 AM
ninlmartijn wrote:Dear Rolf,
Thank you for your post on our webforum. What type of hardware is involved in your configuration. I see different installers for the different hardware targets (under C:\Program Files\National Instruments\RT Images\Base\5.0 ) It isn't clear wich installer is for which target.
Is your target a cRIO 901x controller?
Best regards,
The one in question is a cRIO system but I was under the impression that the used vxWorks OS was more dependant on the used LabVIEW version with LabVIEW RT 8.2 using VxWorks 6.1 and LabVIEW RT 8.5 using VxWorks 6.3. But if you say that (just as an example) LabVIEW RT 8.5 for a VXI PC using VxWorks does use a different VxWorks version than 6.3 I guess I would also have to reconsider the installation procedure for my shared library to make sure that it would still get installed correctly in a LabVIEW development system when other VxWorks targets than cRIO or concerned.
Rolf Kalbermatter
10-27-2008 08:18 AM
Dear Rolf,
thank you for your reply. At this moment I can't say if the VXwork version is different for the targets. I only noticed different installers for different controller targets. With these installers it isn't clear which VXworks version is involved. I forwarded your question, and I will get back to you as soon as possible.
I also asked if there are known issues with shared library's when migrating from VXworks 6.3 to 6.6 (if 6.6 is involved).
I will keep you posted!
Best regards,
10-27-2008 09:49 AM
ninlmartijn wrote:Dear Rolf,
thank you for your reply. At this moment I can't say if the VXwork version is different for the targets. I only noticed different installers for different controller targets. With these installers it isn't clear which VXworks version is involved. I forwarded your question, and I will get back to you as soon as possible.
I also asked if there are known issues with shared library's when migrating from VXworks 6.3 to 6.6 (if 6.6 is involved).
I will keep you posted!
Best regards,
Thanks a lot! And if there is indeed a new version involved it would be great to update this Knowledge Base article.
10-27-2008 10:13 AM
Hello Rolf,
Great news; the VXwork version is still 6.3, so we don't see any problems with migrating to this version. Please let me know if there are.
Best regards,
10-27-2008 02:08 PM
Thanks very much!
I will test this as soon as I get access to a compatible cRIO system!
Rolf Kalbermatter