Archived: LabVIEW 2012 and 2012 SP1 Real-Time Module Known Issues
Updated Mar 17, 2020
NI does not actively maintain this document.
This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
This document contains the LabVIEW 2012 and 2012 SP1 Real-Time Module known issues that were discovered before and since the release of the LabVIEW 2012 and 2012 SP1 Real-Time Module. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.
Time Triggered Variables do not work on NI Real-Time Hypervisor Systems
Workaround: If you need deterministic Ethernet in an NI Real-Time Hypervisor system, you can use the virtual Ethernet device to communicate between Windows and the RT target or you can use NI EtherCAT to communicate with add-on I/O.
FieldPoint Data Channels Swapped when Reading Data using Datasockets in a For Loop
Workaround: 1. Use a sequential read with multiple Datasocket functions. 2. Explicitly open the Datasocket connections and then use a Datasocket Read in the for loop. 3. Use a different API to access the IO point (SV, FieldPoint, etc)
VIs or controls that use library items in community scope fail to download on VxWorks targets
Workaround: Change "community scope" vis in lvlibs and lvclasses to "public scope". Consider renaming these vis in a way that indicates they should not be used by external clients (i.e., rename "method.vi" to "__method.vi"). You might also restructure your class relationships to use a different access restriction policy.