Archived: LabVIEW 2013 Control Design and Simulation Module Known Issues

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.

Overview



This document contains known issues for the LabVIEW 2013 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.

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.

Known Issues by Date

The following items are known issues in LabVIEW 2013 Control Design and Simulation Module sorted by Date.

145976 Editing a Subsystem VI may not add asterisk (*) to title bar of caller VIs
156847 Show Buffer Allocations does not work on simulation diagrams
89687 3SBBPSE9 Cannot make root locus plots part of subplots
155420 A Function Block Appears Twice in a Project When Dropped Inside Simulation Node
224620 Triggered Subsystems may not perform as expected in certain situations
172863 Simulation Parameters of a subsystem do not update in the parameter tree
192062 Cannot change dll that External Model function points to
289835 MPC Controller constraints are not hard constraints.
314976 LabVIEW crashes when inserting a VI Snippet into a Simulation Diagram
352317 Accessors do not read data correctly for 2D Signals
353239 Subsystem with multiple inputs connected directly to outputs fails to compile
357963 Incorrect instance VI's shown for polymorphic instances of simulation subsystems.
357971 Dropping a merge VI containing a polymorphic simulation subsystem can crash LabVIEW.
358232 Simulation subsystem VIs marked as friends of classes report a compile error.
358339 External Model DLL Dependency is not recognized
358695 Using an XControl with a Simulation Subsystem can cause LabVIEW to hang
360066 Access Model Hierarchy Block does not work with unsaved VI's on Mac OS
410913 Simulation VI takes a long time to run or save after an edit



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

Reported Version: 2009    Resolved Version: N/A    Added: 08/01/2009
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

Reported Version: Orion    Resolved Version: N/A    Added: 08/01/2009
89687
3SBBPSE9


Return
Cannot make root locus plots part of subplots
You cannot make root locus plots part of subplots.

Workaround: N/A

Reported Version: 2.1    Resolved Version: N/A    Added: 08/01/2009
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.

Reported Version: Saturn    Resolved Version: N/A    Added: 06/25/2010
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

Reported Version: 2010    Resolved Version: N/A    Added: 07/31/2010
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

Reported Version: 2009    Resolved Version: N/A    Added: 07/24/2011
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

Reported Version: 2009    Resolved Version: N/A    Added: 07/24/2011
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).

Reported Version: 2011    Resolved Version: N/A    Added: 07/12/2012
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.

Reported Version: 2010    Resolved Version: N/A    Added: 07/12/2012
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

Reported Version: 2012    Resolved Version: N/A    Added: 07/12/2012
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.

Reported Version: 2012    Resolved Version: N/A    Added: 07/12/2012
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

Reported Version: 2012    Resolved Version: N/A    Added: 07/12/2012
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

Reported Version: 2012    Resolved Version: N/A    Added: 07/12/2012
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

Reported Version: 2012    Resolved Version: N/A    Added: 07/12/2012
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.

Reported Version: 2012    Resolved Version: N/A    Added: 07/12/2012
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.

Reported Version: 2012    Resolved Version: N/A    Added: 07/12/2012
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

Reported Version: 2012    Resolved Version: N/A    Added: 07/12/2012
410913

Return
Simulation VI takes a long time to run or save after an edit
A VI with a large number of wires can cause this. This includes all wires on the simulation diagram and within any subsystems.

Workaround: Try to reduce the number of wires by using subVIs where a large number of non-simulation nodes are used.

Reported Version: 2012    Resolved Version: N/A    Added: 07/19/2013

Document last updated on 7/19/2013

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).