LabVIEW 2009 Statechart Module Known Issues

Publish Date: Nov 23, 2009 | 0 Ratings | 0.00 out of 5 |  PDF

Overview

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

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

100185 4BTB979A Replacing a block diagram constant when configuring a statechart state node or transition node may not delete the original block diagram constant
100729 Unexpected searching may occur when saving Statechart Communication nodes to a previous LabVIEW version
101248 Building a build specification may fail if it uses statecharts or their callers last saved in LabVIEW 8.5
110487 Deleting cluster constant in statechart configuration guard/action diagram can crash LabVIEW
118558 Issue with copying/pasting states/transitions between different statecharts of the same name in different application instances
159675 Cannot rename statechart groups
184024 Existing guard/action VIs may be locked in config dialog when debugging is off



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.

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

Return
Unexpected searching may occur when saving Statechart Communication nodes to a previous LabVIEW version
Unexpected searching may occur when saving Statechart Communication nodes to a previous LabVIEW version

Workaround: N/A

Reported Version: Saturn    Resolved Version: N/A    Added: 08/01/2009
101248

Return
Building a build specification may fail if it uses statecharts or their callers last saved in LabVIEW 8.5
Building a build specification may fail if it uses statecharts or their callers last saved in LabVIEW 8.5

Workaround: Save your statecharts and their callers in the current version of LabVIEW before attempting to build.

Reported Version: Saturn    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
184024

Return
Existing guard/action VIs may be locked in config dialog when debugging is off
You may be unable to edit Guard or Action code in your statechart if you generated code with debugging turned off.

Workaround: Enable Debugging and regenerate code for your statechart.

Reported Version: 2009    Resolved Version: N/A    Added: 10/30/2009

Document last updated on 11/5/2009

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit