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.
The LabVIEW 2012 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
The following items are known issues in LabVIEW 2012 and 2012 SP1 Real-Time Module sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 176762 Return | 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.
| |||||
| 115784 Return | Timed-Structure CPU Usage not Reported as Time-Critical Priority by RTSM and CPU Measurement VIs on VxWorks Workaround: Use the NI Real-Time Execution Trace Toolkit to monitor thread priorities.
| |||||
| 275880 Return | UDP Broadcast behaves differently on Phar Lap and VxWorks Real-Time Targets Workaround: N/A
| |||||
| 298990 Return | Clear Errors VI is Not Reentrant Workaround: Create custom "Clear Error" VI.
| |||||
| 305567 Return | File/Directory Info function reports two extra files when called on for an external hard drive Workaround: Subtract 2 from the file count returned from the File/Directory Info function when reporting on a folder on an external hard drive.
| |||||
| 196504 Return | 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)
| |||||
| 323607 Return | On an RT OS, Numeric Control With "Visible" Property Node Stops Updating Workaround: Put the numeric indicator on a Tab Control, then make the property of the tab control invisible/visible rather than the numeric indicator itself.
| |||||
| 345803 Return | 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.
| |||||
| 346430 Return | High CPU usage when setting date and time on certain CompactRIO controllers Workaround: Set the date and time at the beginning of the Real-Time application and wait for the CPU to return to normal levels before executing the rest of the application.
| |||||
| 358016 Return | Cannot connect to debuggable executable when Wait on IRQ Timed Out is wired to case structure selector Workaround: Put an "Or" or other boolean logic in between the "Timed Out" terminal and the case structure.
| |||||
| 340541 Return | End of line constant behaves differently in interactive mode than as a built executable Workaround: Add a carriage return constant to the new line for use in a RT Executable
| |||||
| 366257 Return | Waveform chart doesn't update when running on first run after clearing chart in interactive mode on RT target Workaround: Run the VI twice
| |||||
| 371282 Return | A Real Time Executable with a Packed Project Library set to Always Included Cannot be remotely debugged Workaround: N/A
| |||||
| 376910 Return | Using Match Regular Expression Function can cause crash on VxWorks Target Workaround: Use Match Pattern Function instead
| |||||
| 387418 Return | Set Number of Records function erases all datalog contents on VxWorks targets Workaround: Use binary file or another file format to store cluster data.
|
Document last updated on 2/4/2013