Kernel of the LabVIEW RTOS

[dof]

In the training course of the LabVIEW Real Time Application Development,
It mentioned that the RTOS of the LabVIEw is based on the Venturcom's RTX or ETS.
However, in the latest new from NI, it annoced that the VxWorks' RTOS will be adopted in the CompactRIO.

Does this mean the Venturcom's RTOS no longer exist in the later version of the LabVIEW RTOS?

BTW, does this change induced any problem to the exiting VIs developed by the old RTOS?

Thanks.

[Christian_L]

Hello,

You are correct. VxWorks is used as the RTOS on the new 9012 and 9014 High-Performance CompactRIO controllers. All existing CompactRIO controllers (9002 and 9004) as well as other LabVIEW Real-Time platforms (PXI, FieldPoint, desktops) will continue to run using the ETS RTOS.

Most current VIs developed for LabVIEW Real-Time will port to the new controllers without any changes. Any code that is written purely in LabVIEW code will work on the new controllers. Code that uses DLLs in the background will need to be updated as DLLs are not supported in VxWorks. The original DLL source code will need to be recompiled into a VxWorks shared library. More information on these compatibility issues can be found in the following document.

http://zone.ni.com/reference/en-XX/help/370622D-01/lvrtconcepts/rt_unsupportedvxworks/

[dof]

Thank you, Christian.

Your information is very useful to me.

Some more questions.

Do you know why VxWorks is chosen and why only new cRIO is replaced to this new RTOS platform? (or just because they are new annoced HWs)

Is it the plan that all later version of RT controllers will adopt VxWorks as the RTOS in the near future?

How do I check the RTOS version and provider from my present cRIO-9012? From the directories of the "c/:"?

Dof.

[RVallieu]

Would it be possible to install VxWorks on a PXI controller and use LabVIEW RT to target that system?

[Jimmie_A.]

Hello,

Both ETS and VxWorks have their benefits and if we look at ETS for an example some of them include:

Small footprint, works with standard PC HW, support for a subset of the Win32 API which is helpful when migrating Windows based code and runs on all 32-bit x86 architectures.

However ETS doesn't support PowerPC which is the processor family we use in cRIO 901x series. So for cRIO 901x we use VxWorks which has been around for many years and are proven to work well.

Finally we don't offer any support for VxWorks on the PXI platform as of today i.e. ETS is the real-time operative system to use.