Windows系统下（Linux和MAC系统下请自行了解清楚）NI的各种软件、模块、工具包、驱动程序，使用NI许可证管理器来激活的，绝大部分的都可以使用NI Lincense Activator来激活，以下链接可下载：
NI序列号Serial Number生成激活工具NI License Activator，LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本
http://pcmv.cn/thread-490-1-1.html
视觉论坛的各种资源，除了视觉相关的模块有使用外，大部分的都不会使用，所以仅提供资源不能提供技术支持。资源的下载地址一般会同时提供NI官方地址和百度网盘的下载地址。某些工具包NI的地址失效或没有NI的下载地址，那视觉论坛也没有办法，只能尝试使用百度网盘地址下载；如果百度网盘的下载地址失效过期，可联系论坛客服更新。现在NI的下载服务器对我国IP地址不是很友好，有些时候速度很慢或大的资源下载很容易出错，这样会造成安装过程各种类型报错而无法安装。建议在下载完成后，对下载资源做校验和验证（NI一般会提供MD5或SHA256等），与官方或视觉论坛提供的校验和对比，一致就可以安装，如果不一致，则需要重新下载。视觉论坛早期下载的资源，那时候NI没有这么多限制，基本上都是正常下载的资源；后期下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘，所以百度网盘的资源基本上是正确的。校验和工具下载地址：
文件Hash计算器FHash,文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算
http://pcmv.cn/thread-26524-1-1.html
LabVIEW Statechart Module 2009 Win32Eng LV状态图模块SC2009
LabVIEW状态图模块提供了高级抽象来帮助用户设计基于状态、转换和事件的应用程序。
LabVIEW状态图模块是LabVIEW编程环境的一个附加软件。该模块可以在所有NI硬件终端上运行，包括台式PC、实时系统、FPGA和ARM微控制器，而且还可帮助您在架构之间轻松移植代码。
百度网盘下载（限速，请开会员或使用工具下载）:
请注册视觉论坛会员，登陆购买附件查看，充值请联系在线客服
NI官方下载地址（可能无法下载完成或地址无效）：
请注册视觉论坛会员，登陆购买附件查看，充值请联系在线客服
LabVIEW Statechart Module 2009 Win32Eng LV状态图模块SC2009
http://pcmv.cn/thread-24892-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
文件大小: 52206112 字节 (49.79 MB)
修改日期: 2010-01-07 00:30
MD5: 9e6bcefb0e6aa912b31e5fc232971a54
SHA1: b47150bf2771af93e4b136d64a706f80024626d9
SHA256: dcde3efaa14465aee288d2c8bd142f2d6d5e99b833170c3286c1bae2112987e0
CRC32: 8af39bc8
LabVIEW 2009 Statechart Module Readme
June 2009
This file contains information to introduce you to the LabVIEW 2009 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.
New Features
System Requirements
Installation Instructions
Accessing the Help
Finding Examples
Known Issues
Bug Fixes
New Features
The LabVIEW 2009 Statechart Module includes the following new features.
Generating Documentation for Statecharts
You now can generate documentation that describes all components of a completed statechart. Print or save statechart documentation to keep a record you can refer to later.
You can generate statechart documentation from either the Project Explorer window or the Statechart Editor window. In the Project Explorer window, right-click the .lvsc item, or statechart library, for a statechart and select Generate Documentation from the shortcut menu. In the Statechart Editor window, select File»Generate Documentation. The LabVIEW Statechart Module generates an XML file that contains information about all components, including states, pseudostates, connectors, regions, and transitions, of the statechart. You can view the XML file in a Web browser.
You also can use the Generate Documentation method to generate statechart documentation programmatically.
No Code Generation Required for Guard or Action Changes
In earlier versions of the LabVIEW Statechart Module, when you modify a guard or action in a transition or static reaction, you must re-generate code for the statechart. Code generation can be time-consuming for large statecharts. In the LabVIEW 2009 Statechart Module, you no longer must re-generate code for a statechart when you make modifications to a non-empty guard or action. However, you still must re-generate code if you add code to a previously empty guard or action or if you delete all code from a guard or action.
Debugging Statecharts for FPGA Targets
You now can debug statecharts for field-programmable gate array (FPGA) targets executing on the host computer. LabVIEW can run the statechart on the host computer to allow you to debug the statechart before you deploy the statechart to the FPGA target. You cannot debug a statechart that runs on an actual FPGA. Select LabVIEW FPGA Target from the Execution Target pull-down menu on the Statechart Code Generation page of the Project Library Properties dialog box to specify that the statechart executes on an FPGA target.
Right-click a Run Statechart function and select Debug Statechart from the shortcut menu to debug a statechart for an FPGA target. This action is valid only when you have linked the Run Statechart function to a statechart that runs on the host computer. By default, statechart debugging for FPGA targets is disabled. You can enable statechart debugging for FPGA targets by selecting Enabled from the Debugging pull-down menu on the Statechart Code Generation page of the Project Library Properties dialog box. Enabling statechart debugging for FPGA targets increases the code size of the statechart.
Configuring Multiple States or Transitions Simultaneously
You now can configure multiple states and transitions simultaneously. Open multiple Configure State or Configure Transition dialog boxes from the Statechart Editor window. You may not edit the statechart diagram when you open a Configure State or Configure Transition dialog box. The states or transitions you configure display a wrench icon in the Statechart Editor window and change color on the statechart diagram when a Configure State or Configure Transition dialog box is open. The default configuration color is yellow. You can customize the color that the states and transitions you configure turn.
You also can switch from the open Configure State or Configure Transition dialog boxes to the state or transition you are configuring in the Statechart Editor window. The Configure State dialog box contains a new Jump to State button and the Configure Transition dialog box contains a Jump to Transition button to the left of the Code Status button. The Jump to State and Jump to Transition buttons highlight the state or transition to which the Configure State and Configure Transition dialog boxes correspond. If you attempt to configure a state or transition you are already configuring, the currently open configuration dialog box for the state or transition appears.
Finding Objects and Text in Statecharts
You now can search statecharts for a particular object or string of text. Use the Find dialog box to find VIs, Express VIs, objects, or text in the guard and action code of a statechart or to find Statechart Development objects or text in the Statechart Editor window. Select Edit»Find and Replace in the Statechart Editor window to display the Find dialog box.
You also now can find all instances of triggers and groups in a statechart. Right-click a trigger or group on the Triggers/Groups page of the Configure State or Configure Transition dialog box and select Find Trigger/Group from the shortcut menu to find all static reactions and transitions that react to the trigger or group.
Browsing a Statechart Hierarchy
You now can browse the hierarchy of a statechart to identify the relationship of the statechart to other VIs. You can browse the statechart hierarchy from either the Statechart Editor window or the Project Explorer window.
You can browse the following elements of a statechart hierarchy:
.lvsc file—From the Statechart Editor window, select View»Browse Relationships»This VI's Statechart to find the corresponding .lvsc file, or statechart library, for the statechart. From the Project Explorer window, right-click a caller VI or subVI of the statechart and select Find»SubVIs or Find»Callers, respectively, from the shortcut menu to find the corresponding .lvsc file for the statechart.
Caller VIs—From the Statechart Editor window, select View»Browse Relationships»This VI's Callers to find the caller VIs of the statechart. You also can right-click the icon in the upper right corner of the Statechart Editor window and select Find All Instances from the shortcut menu to find all caller VIs of the statechart. From the Project Explorer window, right-click the .lvsc file for a statechart and select Find»Callers from the shortcut menu to find the caller VIs of the statechart.
SubVIs—From the Statechart Editor window, select View»Browse Relationships»This VI's SubVIs to find the subVIs of the statechart. From the Project Explorer window, right-click the .lvsc file for a statechart and select Find»SubVIs from the shortcut menu to find the subVIs of the statechart.
Statechart Editor window—From a caller VI or subVI of the statechart, select View»Browse Relationships»This VI's SubVIs or View»Browse Relationships»This VI's Callers, respectively, to find the corresponding Statechart Editor window for the statechart.
System Requirements
LabVIEW 2009 Base, Full, or Professional Development System for Windows
250 MB additional available disk space
Installation Instructions
You can install all of your LabVIEW products—including the LabVIEW Statechart Module—using the LabVIEW 2009 Platform DVDs. You can find installation instructions for the LabVIEW Statechart Module along with activation instructions in the following locations:
LabVIEW Release Notes, which are available in your LabVIEW software kit.
LabVIEW 2009 Platform DVDs Readme, which is available on the top-level of LabVIEW Platform DVD 1.
To request additional LabVIEW 2009 Platform DVDs, refer to the National Instruments Web site.
Accessing the Help
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.
Finding Examples
LabVIEW examples for the Statechart Module are located in the labviewexamplesStatechart 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.
Known Issues
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 2009 Statechart Module.
Bug Fixes
The following items are the IDs and titles of a subset of issues fixed in the LabVIEW 2009 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 | Legacy ID | Fixed Issue |
| 41330 | 4D6G4PI8 | Unable to Show/Hide Paths in Library-only Project Window |
| 44517 | 4HFEEM9A | The icon for the statechart .lvsc file is confusing and not presented well |
| 44933 | 4HTEFNWS | Internal errors when closing project while statechart configuration dialog is open |
| 52739 | 4BOA749A | Certain items from the palette drop at incorrect positions in the statechart configuration dialog |
| 91641 | 46JGUIUG | Cannot drag items out of guard or action VIs in the State/Transition configuration dialog |
| 92523 | 4BTF3H9A | The "Replace With" menu option can be used in the statechart diagram to connect statechart objects in non-allowed ways |
| 92893 | 4DKCLN9A | Statecharts should not require code generation when only a guard or action has been modified |
| 93007 | 4EB9AAHA | No easy way to find out which transitions or Static reactions respond to a particular trigger. |
| 93008 | 4EB9BNHA | There is no way to do find objects in the guard and action code of states/transitions in a Statechart. |
| 93090 | 4EPD3Q9A | Finding callers and callees of statecharts on Project window does not working properly. |
| 93495 | 4HKAHJUG | Applying changes to statechart type definitions can result in very long delays |
| 95703 | — | Easy to move objects outside of the visible region in the guard and action windows of the statechart configuration dialog |
| 104376 | — | Quick Drop does not work when configuring a Statechart state node or transition node |
| 106768 | — | Compound arithmetic VI appears in incorrect position when dropped in statechart configuration dialog. |
| 110377 | — | Double clicking a state or transition twice in quick succession gives a configuration error |
| 110716 | — | Drawing or moving objects offscreen in a statechart diagram does not scroll the viewing area. |
| 112854 | — | Statecharts from previous LabVIEW versions may miss out on some non-essential mutation when loaded in current LabVIEW |
| 126845 | — | Should not be able to edit statechart type definitions in one context while configuring statechart states/transitions in other context |
| 131651 | — | Renaming a state's static reaction can delete the reaction's guard/action code |
| 133221 | — | Certain statecharts always generate broken code and cannot be run |
| 134252 | — | Changing a static reaction's name to that of one that existed when you began your state configuration can cause incorrect reaction ordering and/or guard/action code |
| 136900 | — | Edits to one statechart static reaction can be incorrectly applied to another static reaction |
| 147850 | — | Breakpoints added on Statechart debug window do not get updated in Breakpoint Manager when it is opened for the first time. |
| 147853 | — | Breakpoint added in subdiagram gets hit while debugging but the subdiagram window does not open if it was closed when the breakpoint was hit. |
| 155447 | — | Better feedback needed when dropping an unsupported function block node in a statechart guard or action VI |
| 162458 | — | Saving a statechart that uses subdiagrams from LabVIEW 8.6 to LabVIEW 8.5 results in problems in LabVIEW 8.5 |
Important Information
Copyright
© 2009 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
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.
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.
