Archived: LabVIEW 8.6 Control Design and Simulation Module Bug Fixes

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 following items are the IDs and titles of a subset of issues fixed between the 8.5.1 and 8.6 versions of the LabVIEW Control Design and Simulation Module. If you have a CAR ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of the LabVIEW Control Design and Simulation Module.

Bug Fixes

The following items are the IDs and titles of fixed issues from the LabVIEW Control Design and Simulation Module 8.5.1.

Bug IDFixed Issue
112234Updating a global variable through the node will not update its view from the window
101393Should have warning or error when subsystem parameters have an invalid format
70185Two bugs in Indexer function
66302Zero crossings in Quantizer function are incorrect
59740VI broken in Simulation when using Case structure
58785Control Design and Simulation error text files installed to the wrong directory
58435[MathScript] bodemag - wout vector is filled with phase values instead of frequencies
58006[MathScript] default step plot for discrete system should have constant value between samples
57884[MathScript] leadlag, ltimodels, and plot functions removed
57860Connector pane icons of instances of CD Parallel VI do not match the icon of the polymorphic VI
57732[MathScript] c2d function does not perform trapezoid method
56887[MathScript] rlocus function plot displays poor representation of double pole
56452CD Root Locus VI does not return the correct graph
54657LabVIEW Control Design shows up in MAX when you have the Control Design and Simulation Module installed
54557Shipping examples do not work as expected when changing sampling rate parameter
54470Several front panel indicators and palettes have confusing names
54467Grid lines on root locus graph are transparent when turned on
54465[Assistant] Loading projects with polymorphic steps from Control Design does not generate output
54304Right-click»Configure opens a different dialog box than double-clicking for the Multiplication function.
53703LabVIEW hangs when loading simulation on RT target
53433Diagram versions of Discrete Transfer Function and Discrete Zero-Pole-Gain functions have states and derivatives switched in implementation
53011CDEx Kalman Filter and Controller Implementation with example has incorrect wiring
52373[MathScript] tf function does not accept an unspecified sampling time in the format of [ ]
46354Simulation Loop does not compile and returns no error
45883time report from "simulation time" and "simulation info" is different
42912Simulation Model Converter should handle 1-based indexes in Formula Node
41961Simulation Model Converter indexes incorrectly
40534Parameter names inconsistent between CD Feedback VI and CD Unit Feedback VI
39333Simulation Model Converter does not convert exponential character
38478Simulation Model Converter incorrectly converts Formula Node formulas when array indexing is involved
37775Simulation Model Converter reverses terms on real-imag to complex
37719Simulation Model Converter converts subsystems with same name to single VI
37706[Simulation Model Converter] The widths function behaves differently in LabVIEW for 2D arrays
37488Simulation Model Converter generates data type mismatch
37487Simulation Model Converter does not convert array index
35734Simulation Model Converter does not work with fractions


Glossary of Terms


  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on  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).