Home Support Documentation Bugs

LabVIEW 2015 Statechart Module Known Issues

Updated Mar 10, 2020

Overview

This document contains known issues for the LabVIEW 2015 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. The LabVIEW 2015 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.

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)

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.

Known Issues by Date

The following items are known issues in LabVIEW 2015 Statechart Module sorted by Date.

110487—Deleting cluster constant in statechart configuration guard/action diagram can crash LabVIEW
222978—Clean up diagram creates loose wires
421985—In certain cases, using the replace VI within the Guard tab in a transition can crash LabVIEW
530616—Real Time executables that contain Statechart code can load broken on Linux RT x64 targets.



IDKnown Issue
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: 2011  Resolved Version: N/A  Added: 08/01/2009
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: 2011  Resolved Version: N/A  Added: 07/25/2011
421985

Return		In certain cases, using the replace VI within the Guard tab in a transition can crash LabVIEW

Workaround: Do not use the replace option. Add the new VI and delete the original.

Reported Version: 2013  Resolved Version: N/A  Added: 06/24/2014
530616

Return		Real Time executables that contain Statechart code can potentially load broken on Linux RT x64 targets.
Real Time Executables will build and deploy properly but can load with a broken run arrow on Linux RT x64 targets.

Workaround: Run the VI interactively or use a non-x64 Linux target when using Statechart code on a real time target.

Reported Version: 2014  Resolved Version: N/A  Added: 06/03/2015

Document last updated on 7/30/2015

Back to top

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