Print
PDFOverview
This document contains known issues for the LabVIEW 2012 Control Design and Simulation 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.
Each Issue appears as a row in the table and
includes these fields:
- Issue ID
- Legacy ID - The issue's legacy ID from NI's deprecated bug reporting database (if applicable)
- Issue Title
- Problem Description
- Workaround
- Reported Version - the earliest version of LabVIEW the issue was reported in
- Resolved Version - version the issue was resolved or was no longer applicable
- Date Added - the date the issue was added to the document
(not reported date)
The LabVIEW 2012 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
Contacting NI
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.
Windows 7
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.
Known Issues by Date
The following items are known issues in the LabVIEW 2012 Control Design and Simulation Module sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 145976 Return |
Editing a Subsystem VI may not add asterisk (*) to title bar of caller VIs When making edits to a Subsystem VI, which will require recompiling the Subsystem's caller, an asterisk may not appear on the caller VI, indicating that it has changed. However, before closing the caller VI, LabVIEW will still prompt you to save the modified VI and there is no danger of unintentionally losing changes. Workaround: N/A
|
|||||
| 156847 Return |
Show Buffer Allocations does not work on simulation diagrams Buffer allocation for arrays and clusters do not show up on a simulation loop or subsystem when using the show buffer allocations tool. Workaround: N/A
|
|||||
| 172558 Return |
External model library interface does not automatically download to target. 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.
|
|||||
| 89687 3SBBPSE9 Return |
Cannot make root locus plots part of subplots You 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 When you drop a Function Block inside a Simulation Loop, the block and its parameters will be populated in the project twice. 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 There are two situations where a triggered subsystem may not perform as expected. First, if a node that uses the discrete step size as part of its calculations (such as the discrete integrator) is inside a triggered subsystem, the node will use the global discrete step size rather than the interval between triggers as the discrete step size for its calculations. For example, consider a discrete integrator in a simulation with a discrete step size of .1 inside a triggered subsystem. If the integrator has a constant value of 1 as its input, and it is triggered at t=2 and t=5, its output value after t=5 would be .1, not 2. Second, if a trigger occurs on a time step that is not also a discrete time step (i.e., the trigger occurs at t=1.5, and the discrete step size is set to 1), the triggered subsystem will execute, but none of the discrete nodes inside it will execute. Workaround: N/A
|
|||||
| 172863 Return |
Simulation Parameters of a subsystem do not update in the parameter tree In the configuration dialog of a Subsystem placed outside of a simulation loop, Simulation Parameters do not update their values as you edit them. However they will be updated the next time the dialog is opened. Workaround: N/A
|
|||||
| 192062 Return |
Cannot change dll that External Model function points to After an iniital dll has been selected for an External Model function, it cannot be changed. A user can select a different dll in the dialog but the change does not get saved. Workaround: N/A
|
|||||
| 194660 Return |
Cannot set up a Single-Input Multiple-Ouputt system When trying to setup a Single-Input Multiple-Output system transfer function, the output reverts to a scalar (single output) when it should be an array (multiple output) Workaround: N/A
|
|||||
| 289835 Return |
MPC Controller constraints are not hard constraints. Constraints set by the user for the MPC controller are treated as soft constraints and can be violated in certain control situations. 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 When attempting to insert a VI Snipped that contains a Simulation Node or Timed Loop onto a Simulation Diagram LabVIEW crashes. Workaround: Snippets containing Simulation Nodes or Timed Loops cannot be inserted into a Simulation Diagram.
|
|||||
| 334069 Return |
Adjust Delay Setting of Unit Delay function does not work with PID When set to true the adjust delay setting should remove the delay and replace with its pade approximation. This does not happen with the CD Unit Feedback VI. Workaround: N/A
|
|||||
| 352317 Return |
Accessors do not read data correctly for 2D Signals If you create an accessor for a 2D signal in the Access Model Hierarchy Configuration of the Control and Simulation Loop the data is not collected correctly. The array of signal data will be empty. Workaround: N/A
|
|||||
| 353239 Return |
Subsystem with multiple inputs connected directly to outputs fails to compile Simulation Subsystems that have more than one input connected directly to an output without any other blocks on the wire may fail 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. When opening a VI containing a simulation loop and polymorphic simulation subsystems the incorrect instance VIs are shown for the polymorphic instances. Workaround: N/A
|
|||||
| 357971 Return |
Dropping a merge VI containing a polymorphic simulation subsystem can crash LabVIEW. Dropping a merge VI containing a polymorphic simulation subsystem can crash LabVIEW when the merge VIs are saved in a previous LabVIEW version. Workaround: Mass Compile Merge VI's before using
|
|||||
| 358232 Return |
Simulation subsystem VIs marked as friends of classes report a compile error. Simulation subsystem VIs marked as friends of classes report a compile error when calling a static accessor VI with Community scope. Workaround: N/A
|
|||||
| 358339 Return |
External Model DLL Dependency is not recognized When deploying a VI containing an external model to a VxWorks target the 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 Adding an XControl to a simulation subsystem and saving the VI 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 If you try to use the Access Model Hierarchy block on a Mac OS before the VI is saved the VI will have a broken run arrow and state that it is not executable. Workaround: Save the VI before using the Access Model Hierarchy block
|
|||||
| 361324 Return |
Continuous Kalman Filter outside Control Design & Simulation Loop gives incorrect results Continuous Kalman Filter outside Control Design & Simulation Loop gives incorrect results. Using the filter inside a Control Design and Simulation Loop works as expected. Workaround: N/A
|
Document last updated on 7/13/2012
Reader Comments | Submit a comment »
Legal
This tutorial (this "tutorial") was developed by National Instruments ("NI"). Although technical support of this tutorial may be made available by National Instruments, the content in this tutorial may not be completely tested and verified, and NI does not guarantee its quality in any way or that NI will continue to support this content with each new revision of related products and drivers. THIS TUTORIAL IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND SUBJECT TO CERTAIN RESTRICTIONS AS MORE SPECIFICALLY SET FORTH IN NI.COM'S TERMS OF USE (http://ni.com/legal/termsofuse/unitedstates/us/).