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.
The LabVIEW 2012 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
You can contact us by phone, email, or the discussion forums. Visit the NI Website to contact us. If you are contacting NI in regards to a specific issue, be sure to reference the ID. If you have feedback on this document, please contact NI on this NI Developer Zone post.
National Instruments is committed to maintaining compatibility with Microsoft Windows technology changes. However, NI has become aware of a number of issues of potential significance regarding Microsoft Windows 7. To learn how Windows 7 affects your use of NI products, visit ni.com/info and enter the Info Code windows7.
The following items are known issues in LabVIEW 2012 and 2012 SP1 Control Design and Simulation Module sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 118492 Return | Cannot generate C code with Optimize SubVI calls and Serial Only both on Workaround: Either deselect Optimize SubVI Calls or select parallel code generation in your Build Specification options.
| |||||
| 145976 Return | Editing a Subsystem VI may not add asterisk (*) to title bar of caller VIs Workaround: N/A
| |||||
| 156847 Return | Show Buffer Allocations does not work on simulation diagrams Workaround: N/A
| |||||
| 167071 Return | Simulation Trim and Linearize will not work on VxWorks targets Workaround: Use another target such as PXI or Desktop.
| |||||
| 172558 Return | External model library interface does not automatically download to target. Workaround: Place a Call Library Function node that points to the library and hide it behind a case structure that always executes the empty case. This causes RT to download the shared library to the target and load it when the VI runs, or ftp the file to the target.
| |||||
| 174841 Return | Dependency conflicts for internal VIs in stored in vi.lib may appear when upgrading projects Workaround: Mass compile the project's VIs before opening the project.
| |||||
| 174968 Return | Some Control Design Assistant Examples have trouble with localized OS Workaround: Change the separator to a decimal in the localization settings.
| |||||
| 175714 Return | Collector causes crash in executable built for ARM Workaround: Pass an array of data (doubles or clusters) into a Memory block that feedsback to itself and use Replace Array Subset (or Build Array for an arbitrary length) on each step of the Sim Loop. If using anything other than Euler or Discrete Only solvers, put the Replace Array Subset function inside a subVI and mark the subvi for execution on Major Steps only.
| |||||
| 49285 Return | Compiling subsystem erases clipboard Workaround: N/A
| |||||
| 89687 Return | Cannot make root locus plots part of subplots Workaround: N/A
| |||||
| 155420 Return | A Function Block Appears Twice in a Project When Dropped Inside Simulation Node Workaround: Place the Function block inside a subVI. This will prevent the second instance of the function block inside the project.
| |||||
| 224620 Return | Triggered Subsystems may not perform as expected in certain situations Workaround: N/A
| |||||
| 229977 Return | VI with Simulation opens with broken run arrow but no errors Workaround: Select any single node on the Simulation Diagram and choose Edit->Clean Up Diagram (Ctrl-U) Having selected a single node will mean that nothing gets moved by the Clean Up Diagram command, but the VI will become runnable.
| |||||
| 172863 Return | Simulation Parameters of a subsystem do not update in the parameter tree Workaround: N/A
| |||||
| 192062 Return | Cannot change dll that External Model function points to Workaround: N/A
| |||||
| 289835 Return | MPC Controller constraints are not hard constraints. Workaround: Add a saturation VI to the output of the MPC function and feed this vector back to u(k-1).
| |||||
| 314976 Return | LabVIEW crashes when inserting a VI Snippet into a Simulation Diagram Workaround: Snippets containing Simulation Nodes or Timed Loops cannot be inserted into a Simulation Diagram.
| |||||
| 352317 Return | Accessors do not read data correctly for 2D Signals Workaround: N/A
| |||||
| 353239 Return | Subsystem with multiple inputs connected directly to outputs fails to compile Workaround: Remove all but a single input that is directly connected to outputs.
| |||||
| 357963 Return | Incorrect instance VI's shown for polymorphic instances of simulation subsystems. Workaround: N/A
| |||||
| 357971 Return | Dropping a merge VI containing a polymorphic simulation subsystem can crash LabVIEW. Workaround: Mass Compile Merge VI's before using
| |||||
| 358232 Return | Simulation subsystem VIs marked as friends of classes report a compile error. Workaround: N/A
| |||||
| 358339 Return | External Model DLL Dependency is not recognized Workaround: Add a Call Library Function Node to the diagram which calls into the same DLL as the external model.
| |||||
| 358695 Return | Using an XControl with a Simulation Subsystem can cause LabVIEW to hang Workaround: XControls are not supported on Simulation Subsystems at this time.
| |||||
| 360066 Return | Access Model Hierarchy Block does not work with unsaved VI's on Mac OS Workaround: Save the VI before using the Access Model Hierarchy block
| |||||
| 361324 Return | Continuous Kalman Filter outside Control Design & Simulation Loop gives incorrect results Workaround: N/A
| |||||
| 355886 Return | Subsystem VI with Time-Critical execution priority fails to compile. Workaround: Time-critical execution priority and synchronization to a hardware timing source are mutually exclusive options. Either lower the VI execution priority or use software timing for the Simulation Subsystem.
| |||||
| 368583 Return | Editing a password protected simulation subsystem can cause subsystem to fail to compile Workaround: To work around this behavior remove the password protection and force the VI to recompile. If necessary password protect the VI again.
|
Document last updated on 2/4/2013