Frequently Asked Questions (FAQ) for NI cRIO-901x and cRIO-907x Targets
What are some of the frequently asked questions regarding the NI cRIO-901x and cRIO-907x targets?
Q. Will floating point results appear different when passed to a cRIO-901x with a Motorola PowerPC as opposed to a cRIO-9004 with an Intel x86?
A. Yes, but the difference will be apparent for high-precision operations only.
A. Yes, path controls will automatically handle the switch, but a string-to-path function will not fix any unchanged path slash.
A. Yes, however only on LabVIEW Real-Time 8.6 and higher. Previous versions of LabVIEW Real-Time do not support TDM files for the cRIO-901x.
A. Unsupported LabVIEW Real-Time features can be found in LabVIEW Help: Unsupported LabVIEW Features (RT Module on VxWorks Targets).
A. Code can be compiled to a *.out file which can be used exclusively on VxWorks. More information about compiling *.out files can be found in KnowledgeBase 43QD6TS9 and this tutorial.
A. The cRIO-901x has 4 threads per execution system while the cRIO-900x series has only one. Therefore, parallelism is possible and timing and synchronization is different on a cRIO-901x target. It may be necessary to benchmark your application again and run the trace tool to make sure it still works as expected.
A. The console is the highest-priority process and will add jitter to time-critical priority loops and all lower-priority loops. When an application is deployed, it is not recommended to use the console out unless field debugging is required.
A. Yes, LabVIEW 2009 Real-Time Module introduced support for UDP multicast. Use the UDP Multicast Open VI to initiate a UDP multicast session.
A. The cRIO-901x operated on a different OS and a different processor, so everything must be recompiled (VIs, RTEXEs). It is recommended you add a cRIO-901x to your project and drag everything from the cRIO-900x onto the cRIO-901x. Then you can make a new build specification, such as a Real-Time Executable, and rebuild your executable.
A. This product documentation lists the minimum version requirements of cRIO and R series devices.
KnowledgeBase 43QD6TS9: Calling External Code on VxWorks Targets
KnowledgeBase 4O08M6Z6: Why do I get Error 1430 or Error 6 when using string-to-path on my VxWorks controller?
Tutorial: Developing Shared Libraries for the cRIO-901x and Other VxWorks Targets
Products and Services: NI cRIO-9012
Products and Services: NI cRIO-9014
Product Documentation: Software Support for CompactRIO, CompactDAQ, Single-Board RIO, R Series, FlexRIO, and EtherCAT
LabVIEW 2010 Real-Time Module Help: Unsupported LabVIEW Features (RT Module on VxWorks Targets)
Report Date: 12/18/2006
Last Updated: 04/05/2017
Document ID: 44HDTKQ0