Version 10.0.0
June 2010
This file contains information to introduce you to the LabVIEW 2010 Statechart Module. This file also provides you with help resources you can use while working with the Statechart Module. The file contains the following information that you need to understand.
In LabVIEW 2010, you can minimize subVI overhead by inlining subVIs into their calling VIs. In the LabVIEW 2010 Statechart Module, the default is to inline all internal VIs and VIs for guard and action code. While subVI inlining improves performance, it also can increase the memory footprint of a statechart. To disable subVI inlining, place a checkmark in the Disable Inline Settings? checkbox on the Statechart Code Generation page of the Project Library Properties dialog box. You can access the Project Library Properties dialog box by right-clicking a .lvsc file in the Project Explorer window and selecting Properties from the shortcut menu.
For more information about subVI inlining, refer to the SubVI Overhead section of the VI Execution Speed topic in the LabVIEW Help.
The LabVIEW 2010 Statechart Module supports the Windows Server 2003 R2 (32-bit) and Windows Server 2008 R2 (64-bit) editions. The LabVIEW 2010 Statechart Module does not support the Windows Server non-R2 editions.
You can install all of your LabVIEW products—including the LabVIEW Statechart Module—using the LabVIEW 2010 Platform DVDs. You can find installation instructions for the LabVIEW Statechart Module along with activation instructions in the following locations:
To request additional LabVIEW 2010 Platform DVDs, refer to the National Instruments Web site.
Note: If you purchased this product with an NI Software Suite or NI Product Bundle, use the installation media that shipped with your purchase to install this product.
Refer to the LabVIEW Help, accessible by selecting Help»Search the LabVIEW Help from the pull-down menu in LabVIEW, for information about the Statechart Module.
LabVIEW examples for the Statechart Module are located in the labview\examples\Statechart folder. You can modify an example VI to fit an application, or you can copy and paste from one or more examples into a VI that you create.
You can access the software and documentation known issues list online. Refer to the National Instruments Web site for an up-to-date list of known issues in the LabVIEW 2010 Statechart Module.
The following items are the IDs and titles of a subset of issues fixed in the LabVIEW 2010 Statechart Module. If you have a CAR ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of the Statechart Module.
| ID | Fixed Issue |
|---|---|
| 143338 | Adding a VI with a large VI hierarchy to a guard or action is slow. |
| 162906 | LabVIEW hangs when editing values in the Edit Triggers and Groups dialog box. |
| 167089 | Statecharts saved in LabVIEW 8.5.x containing states you view as a subdiagram do not load correctly in LabVIEW 8.6 or later. |
| 172955 | Software labels for some controls in the Edit Trigger and Groups dialog box do not match the text in the Context Help window. |
| 177155 | Inserting items into signals using the Configure State and Configure Transition dialog boxes may not appear in the correct position. |
| 180266 | Statechart communication VI icons do not update correctly when you change the system font. |
| 183441 | You cannot enable the Disconnect Type Definitions option when building a statechart application using the Application Builder. |
| 184208 | States and regions with the same ID can be overwritten when you generate documentation for a statechart. |
| 198045 | You cannot change the headings of Triggers and Groups using the Edit Triggers and Groups dialog box. |
| 198618 | Stand-alone applications that contain statecharts do not run. |
| 202636 | You cannot maintain hierarchy within a statechart when you build a Real-Time application. |
Copyright
© 2010 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 respects the intellectual property of others, and we ask our users to do the same. NI software is protected by copyright and other intellectual property laws. Where NI software may be used to reproduce software or other materials belonging to others, you may use NI software only to reproduce materials that you may reproduce in accordance with the terms of any applicable license or other legal restriction.
Trademarks
LabVIEW, National Instruments, NI, ni.com, the National Instruments corporate logo, and the Eagle logo are trademarks of National Instruments Corporation. Refer to the Trademark Information at ni.com/trademarks for other National Instruments trademarks.
Other product and company names mentioned herein are trademarks or trade names of their respective companies.
Patents
For patents covering the National Instruments products/technology, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your media, or the National Instruments Patent Notice at ni.com/patents.