Academic Company Events Community Support Solutions Products & Services Contact NI MyNI
This Document is not yet Rated  Rate this Document

Frequently Asked Questions (FAQ) for NI cRIO-901x and cRIO-907x Targets



Hardware: CompactRIO>>Controllers>>cRIO-9012

Problem:
What are some of the frequently asked questions regarding the NI cRIO-901x and cRIO-907x targets?

Solution:
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.
Q.  Will path controls automatically switch file paths from / to \ (that is, Linux style to Windows style)?
A.  Yes, path controls will automatically handle the switch, but a string-to-path function will not fix any unchanged path slash.
Q.  Can I read from or write to TDM files?
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.
Q. Which LabVIEW functions are not available for use with the cRIO-901x?
A.  Unsupported LabVIEW Real-Time features can be found under Related Links: LabVIEW 2010 Real-Time Module Help: Unsupported LabVIEW Features (RT Module on VxWorks Targets).
Q.  Is there an alternative to DLLs which can be used with the cRIO-901x?
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 under Related Links: KnowledgeBase 43QD6TS9: Calling External Code on VxWorks Target and Developer Zone Tutorial: Developing Shared Libraries for the cRIO-901x and Other VxWorks Targets
Q.  Does the cRIO-901x allow parallelism?
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.
Q. Should I use the console when creating an application?
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.
Q. Can I use UDP multicast?
A.  Yes, LabVIEW 2009 Real-Time Module introduced support for UDP multicast. Use the UDP Multicast Open VI to initiate a UDP multicast session.
Q.  Is it possible to copy Real-Time Executables from a cRIO-900x to a cRIO-901x?
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.
Q.  Where can I find the minimum requirements for the version of NI-RIO and LabVIEW necessary to use the cRIO-901x?
A.  The Developer Zone Tutorial: Software Support for CompactRIO, CompactDAQ, Single-Board RIO, R Series, FlexRIO, and EtherCAT page lists the minimum version requirementes f cRIO and R series devices.



Related Links:
KnowledgeBase 43QD6TS9: Calling External Code on VxWorks Targets
KnowledgeBase 4O08M6Z6: Why do I get Error 1430 when using string-to-path on my VxWorks controller?
Developer Zone Tutorial: Developing Shared Libraries for the cRIO-901x and Other VxWorks Targets
Products and Services: NI cRIO-9012
Products and Services: NI cRIO-9014
Developer Zone Tutorial: 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)

Attachments:







Report Date: 12/18/2006
Last Updated: 01/19/2014
Document ID: 44HDTKQ0

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
  1 2 3 4 5
Please Contact NI for all product and support inquiries.submit