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 LabVIEW 2010 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
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.
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.
The following items are known issues in LabVIEW 2010 Statechart Module sorted by Date.
| ID | Known 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 228612 Return | Making a State (containing a IsIn Node) as a sub-diagram results in a broken statechart under certain conditions. Sometimes, making a State (containing a IsIn Node) as a sub-diagram results in a broken statechart. Workaround: Delete all IsIn Nodes in the opaqued state and add them again and relink them appropriately.
| |||||
| 276756 Return | Code in Statechart 2010 Transition Node Causes Error 1502 During VxWorks RT exe Build Building an RT exe for VxWorks that contains LabVIEW code in a Statechart transition node causes error 1502. Workaround: N/A
| |||||
| 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
| |||||
| 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
| |||||
| 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
|
Document last updated on 7/25/2011