January 2008
The LabVIEW Statechart Module 1.0.1 updates the Statechart Module 1.0 with several bug fixes. The following items are the IDs and titles of a subset of issues fixed between versions 1.0 and 1.0.1. If you have a Bug ID, you can search this list to validate that the issue has been fixed.
| ID | Fixed Issue |
|---|---|
| 4BIH39HA | Semantic checker does not enforce transition rules for segments that leave a Junction connector. |
| 4BOE27HA | The initial condition should never terminate in a Junction connector regardless of how many layers there are. |
| 4CDH3IHA | The property page for Single Cycle Loop did not allow selection of buffered and non-buffered output. |
| 4CNFL800 | Generating code for large statecharts can take a long time. |
| 4BQBR49A | Errors may occur trying to download a statechart to an RT target after making changes to the statechart. |
| 4C0H8D9A | Alert dialogs and internal errors may occur when generating code for some statecharts. |
| 4C0GS09A | Building an application that calls a statechart with a guard or action VI containing a Call Library Function Node returns an error. |
August 2007
This file contains the following information about the LabVIEW Statechart Module 1.0.
Accessing the Help and Examples
Complete the following steps to install the LabVIEW Statechart Module 1.0.
The LabVIEW Statechart Module Help contains conceptual, how-to, and reference information about the Statechart Module. Complete the following steps to access this help file.
The following items are known issues in the LabVIEW Statechart Module 1.0.
| ID | Known Issue |
|---|---|
| 45TC7THA |
Statecharts with unsaved library items fail cross-context sync If you are working with a statechart that is located in certain symbolic paths, such as <vilib> or <userlib>, in multiple contexts at the same time, and you view a state as a subdiagram, LabVIEW might not find the subdiagram in some contexts. In this situation, LabVIEW might show search dialogs. Additionally, saving a statechart when the statechart cannot find a subdiagram might corrupt the statechart file on disk. Workaround—Either save the statechart in a non-symbolic directory, or save the statechart immediately after you view a state as a subdiagram. |
| 44EFQS9A |
Using LabVIEW Statecharts without the LabVIEW Statechart Module Installed The creation and usage of LabVIEW statecharts and VIs that call them requires the installation of the LabVIEW Statechart Module. If you create such statecharts and calling VIs and then try to open them in a LabVIEW installation without the Statechart Module present, you will encounter search dialogs and broken calling VIs. Workaround—Create and build a Source Distribution from a LabVIEW installation with the Statechart Module present. You can then use the output of this Source Distribution, instead of the original Statecharts and calling VIs, in a LabVIEW installation without the Statechart Module present. |
| 48TGOE00 |
Rename of .lvsc file on disk does not work Renaming a .lvsc file directly on disk breaks the link between the file and its dependencies. Workaround—Display the Project Explorer window for that .lvsc file. Right-click the .lvsc project item and select Rename. |
| 4689Q9HA |
Statechart library file cannot do auto save LabVIEW does not save statechart .lvsc files automatically for recovery. Workaround—National Instruments recommends saving .lvsc files frequently as you work on them. |
| 4B8GO89A |
Data display has stale data for internal trigger queue The statechart data display and custom data display update only after the statechart executes a transition action. Therefore, these tools might show the internal trigger queue as having a trigger that has been removed from the queue already. |
| 4BCE3T9A |
Generating code for a statechart not opened in a project can be slow If you open a statechart .lvsc file in the main application instance or in any context that is not part of a LabVIEW project, generating code for that statechart can be slow. Workaround—Open the statechart .lvsc file in a LabVIEW project before generating code for that statechart. |
| 4AJE6300 |
Trigger names must contain only single-byte characters If you enter a multi-byte character in the name of a trigger, the code generation fails. Workaround—Use only English characters in trigger names. |
| 4ALB3MUG |
External trigger queue is created only after the statechart runs once For asynchronous statecharts, the Statechart Module creates the external trigger queue only after you run the Run Statechart function once. Ensure this function completes at least one iteration before attempting to send triggers to the external trigger queue. |
To view the label of a transition node, right-click that transition node and select View»Label. You can change this label by double-clicking the label and entering text.
© 2007–2008 National Instruments Corporation. All rights reserved.
Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National Instruments Corporation.
National Instruments, NI, ni.com, and LabVIEW are trademarks of National Instruments Corporation. Refer to the Terms of Use section on ni.com/legal for more information about National Instruments trademarks.
For patents covering the National Instruments products, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your CD, or ni.com/patents.