Archived: LabVIEW 2011 Statechart 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 2011 Statechart 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)

LabVIEW 2011 Known Issues List

The LabVIEW 2011 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 LabVIEW 2011 Statechart Module sorted by Date.

100185 4BTB979AReplacing a block diagram constant when configuring a statechart state node or transition node may not delete the original block diagram constant
110487Deleting cluster constant in statechart configuration guard/action diagram can crash LabVIEW
118558Issue with copying/pasting states/transitions between different statecharts of the same name in different application instances
159675Cannot rename statechart groups
197572The 12th element in the Inputs.ctl Cluster of a Statechart is always disabled
210687If an object in a search result is deleted, all the search results get grayed out
222978Clean up diagram creates loose wires



IDKnown Issue
100185
4BTB979A


Return
Replacing a block diagram constant when configuring a statechart state node or transition node may not delete the original block diagram constant
Replacing a block diagram constant with the "Select a VI..." option in the statechart state node or transition node configuration dialog may not delete original block diagram constant

Workaround: Delete the original block diagram constant manually.

Reported Version: 1.0  Resolved Version: N/A  Added: 08/01/2009
110487

Return
Deleting cluster constant in statechart configuration guard/action diagram can crash LabVIEW
In the Guard or Action diagram of the Configure State dialog box, if you try to delete the contents of a block diagram cluster that is typedef'ed, and then delete the cluster constant itself, LabVIEW might crash.

Workaround: When deleting a cluster constant in the Configure State dialog box, delete the entire constant at once instead of deleting the contents first.

Reported Version: 8.5.1  Resolved Version: N/A  Added: 08/01/2009
118558

Return
Issue with copying/pasting states/transitions between different statecharts of the same name in different application instances
Copying and pasting a statechart diagram from a statechart state or transition in one application instance to a different statechart of the same name in another application instance generates an error.

Workaround: Ensure the statecharts between which you want to copy and paste states/transitions have different names.

Reported Version: 8.6  Resolved Version: N/A  Added: 08/01/2009
159675

Return
Cannot rename statechart groups
If you try to change the name of a statechart group of triggers, you will not be able to. Similarly, if you create a new group of triggers, you will be unable to change the name from the default name initially assigned.

Workaround: N/A

Reported Version: 2009  Resolved Version: N/A  Added: 08/01/2009
197572

Return
The 12th element in the Inputs.ctl Cluster of a Statechart is always disabled
When creating an Inputs.ctl for a statechart, the 12th element cannot be selected when configuring the transition from the Diagram.vi.

Workaround: N/A

Reported Version: 2009  Resolved Version: N/A  Added: 07/25/2011
210687

Return
If an object in a search result is deleted, all the search results get grayed out
If an object in a search result is deleted from a State or Transition, all other search results corresponding to a State or Transition get grayed out

Workaround: N/A

Reported Version: 2010  Resolved Version: N/A  Added: 07/25/2011
222978

Return
Clean up diagram creates loose wires
In some cases, clean up diagram can create loose wires which causes the VI to become broken.

Workaround: N/A

Reported Version: 2010  Resolved Version: N/A  Added: 07/25/2011

Document last updated on 7/25/2011

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