Archived: LabVIEW 8.6.1 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.

Overview



The following items are the IDs and titles of a subset of issues fixed between the LabVIEW 8.6 Control Design and Simulation Module and the LabVIEW 8.6.1 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 8.6 Control Design and Simulation Module.

Bug IDFixed Issue
36749Add array elements in case of single array input when converting to Summation block
117820Discrete Models should be loadable in Discrete TF Configuration Dialog
124353LUT2D behaves incorrectly
125485Rlocus, Margin and any other path files are not working on Mac
126195Query Subsystem.vi is not runnable in RT VxWorks
127230Lookup Table 2D in LabVIEW 8.6 - Reversed X and Y axis
127433Various "config window" issues in the ZPK block
127536Seed in the Signal Generator in Random Mode Only Changes Every Second
128265Broken Run Arrow with no Errors in Error List
131345"Set Parameter Value" Vector does not work

 

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).