LabVIEW Statechart Module 8.6.1F1 Update Win32Eng LV8.6.1状态图模块升级包SC861f1

石鑫华视觉

Windows系统下（Linux和MAC系统下请自行了解清楚）NI的各种软件、模块、工具包、驱动程序，使用NI许可证管理器来激活的，绝大部分的都可以使用NI Lincense Activator来激活：NI序列号Serial Number生成激活工具NI License Activator，LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本http://visionbbs.com/thread-490-1-1.html

视觉论坛的各种NI资源，除了视觉相关的模块有使用外，大部分的都不会使用，仅提供资源不提供技术支持。资源的下载地址一般会同时提供NI官方和百度网盘的地址。某些工具包NI地址失效或没有NI地址，只能使用百度网盘地址；如果百度网盘地址失效过期，可联系论坛客服更新。NI的服务器在美国，有时候速度很慢或下载容易出错，这样会造成安装时各种错误而无法安装。建议在下载完成后，对下载资源做校验和(NI一般会提供MD5或SHA256等)验证，与官方或视觉论坛提供的校验和对比，一致就可以安装；如不一致，则需要重新下载。视觉论坛早期下载上传的资源，基本上都是正常下载的资源；2019后下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘。校验和工具下载地址：文件Hash计算器FHash，文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算http://visionbbs.com/thread-26524-1-1.html

LabVIEW Statechart Module 8.6.1F1 Update Win32Eng LV8.6.1状态图模块升级包SC861f1

SC861f1必须要先安装SC861，未找到SC861的升级包，可以先安装SC860的安装包。
LabVIEW Statechart Module 8.6 Win32Eng LV状态图模块SC860
http://visionbbs.com/thread-24890-1-1.html

LabVIEW状态图模块提供了高级抽象来帮助用户设计基于状态、转换和事件的应用程序。
LabVIEW状态图模块是LabVIEW编程环境的一个附加软件。该模块可以在所有NI硬件终端上运行，包括台式PC、实时系统、FPGA和ARM微控制器，而且还可帮助您在架构之间轻松移植代码。

百度网盘下载（限速，请开会员或使用工具下载）:
请注册视觉论坛会员，登录购买附件查看，充值请联系在线客服

NI官方下载地址（可能无法下载完成或地址无效）：
请注册视觉论坛会员，登录购买附件查看，充值请联系在线客服
SC861.txt (277 Bytes, 下载次数: 1, 售价: 2 元)

2020-8-31 23:44 上传

点击文件名下载附件

lvsc861f1
文件大小: 43538976 字节 (41.52 MB)
修改日期: 2010-04-25 06:14
MD5: 7fa215adc7b5c2ff77adbc9ea4947c04
SHA1: 2260c908e8b2a074105a1f0fe2aecde25482297d
SHA256: 200ece7472f55f310746dd095139b47489d8dccf4bb45acf8255e7f5ca808a41
CRC32: bdf96429

LabVIEW 8.6.1f1 Statechart Module Readme

March 2009

The LabVIEW 8.6.1f1 Statechart Module updates the Statechart Module 8.6.1 to address known issues from the previous release.

Bug Fixes

The following items are the IDs and titles of fixed issues from the LabVIEW Statechart Module 8.6.1.

Bug ID	Fixed Issue
133221	Statechart Module Generates Broken Code

---

LabVIEW 8.6.1 Statechart Module Readme

November 2008

The LabVIEW 8.6.1 Statechart Module updates the Statechart Module 8.6 to address known issues from the previous release.

Known Issues with Version 8.6.1

The following sections describe known issues at the time of the LabVIEW 8.6.1 Statechart Module release.

ID	Known Issue
110487	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 delete the contents of a block diagram cluster type definition 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.
118558	Error when copying and pasting states or transitions between identically named statecharts in different application instances Copying and pasting states or transitions from a statechart in one application instance to an identically named statechart in another application instance generates an error. Workaround—Ensure the statecharts between which you want to copy and paste states or transitions have unique names.
131651	Renaming static reaction might delete corresponding guard or action code If you rename the static reaction of a state in the Configure State dialog box without modifying the corresponding guard or action code, LabVIEW might delete the guard or action code when you close the dialog box. Workaround—When renaming a static reaction in the Configure State dialog box, be sure to modify any corresponding guard or action code before closing the dialog box.
134252	Problems when renaming or deleting static reactions in single configuration sessions If you rename or delete static reactions without closing the Configure State dialog box between each modification, you might encounter the following issues: If you delete a static reaction and create a new static reaction with the same name, LabVIEW might assign the execution position of the original static reaction to the new static reaction. Therefore, the new static reaction might not execute last. However, the expected behavior is that static reactions execute in the order they are created. If you rename a static reaction to the name of a static reaction that previously existed in the same configuration session, guards or actions corresponding to the previously existing static reaction might apply to the new static reaction of the same name. For example, suppose you have two static reactions, A and B. You rename static reaction B to C and rename static reaction A to B. The new static reaction B might have the guards and actions of the old static reaction B rather than the guards and actions of the old static reaction A. Workaround—Apply the following workarounds for the corresponding issues above: After deleting a static reaction, click the OK button in the Configure State dialog box to apply changes and close the dialog box. Then reopen the Configure State dialog box and create a new static reaction with the name of the static reaction you deleted. Click the OK button in the Configure State dialog box to apply changes and close the dialog box after you rename each static reaction.

Bug Fixes

The following items are the IDs and titles of fixed issues from the LabVIEW Statechart Module 8.6.

Bug ID	Fixed Issue
110820	Right-click copy from tab in configuration dialog box crashes LabVIEW
117715	Removing or adding trigger to transition node causes internal error
117814	Statechart files renamed on disk have stale name library data items, can cause copying to another statechart to fail
117889	Prompting to save changes for libraries/statecharts does not work with library-only projects
118583	Various scenarios where unsaved changes can be lost when configuring statechart transitions
120028	Deleting wire between transition node and state crashes LabVIEW
120339	Highlighted states in Diagram Picture output are not being drawn properly
122811	AbstractXNodeInterface.cpp error during code generation
123014	LabVIEW crashes due to data manager leak
123232	File»New... overwrites statecharts without warning
126856	Run statechart nodes using classes are broken with code generation error due to LV class code

---

LabVIEW 8.6 Statechart Module Readme

June 2008

This file contains the following information about the LabVIEW 8.6 Statechart Module.

New Features

System Requirements

Installation Instructions

Accessing the Help

Known Issues

Bug Fixes

New Features

The LabVIEW 8.6 Statechart Module includes the following new features.

Changing Function Icon Styles

You can change the icon style of a Statechart Communication function on the block diagram. You can right-click a Statechart Communication function and select Icon Style»Custom Icon to display the function with the custom icon of the statechart diagram. You also can right-click a Statechart Communication function and select Icon Style»Configuration to display the function with a list of configuration information.

Displaying the Name of the Current Active State

You can configure the Run Statechart function to display the name of the current active state. Right-click the Run Statechart function and select Configure from the shortcut menu to display the Configure dialog box. The Statechart Active States option specifies to display the name of the current active state.

Displaying Current Active States for Diagrams

You can configure the Run Statechart function to display current active states for diagrams. Right-click the Run Statechart function and select Configure from the shortcut menu to display the Configure dialog box. The Statechart Diagram Display option specifies to display current active states for diagrams. You can choose to display current active states for one diagram, N diagrams, or all diagrams.

Debugging Statecharts on Real-Time Targets

You now can debug statecharts on real-time (RT) targets. Right-click a Run Statechart function and select Debug Statechart to debug a statechart on an RT target. This action is valid only when you have linked the Run Statechart function to a statechart. By default, statechart debugging on RT targets is disabled. You can enable statechart debugging on RT targets by using the Statechart Code Generation page. Enabling statechart debugging on RT targets might increase the code size of the statechart.

Viewing State Configuration in the Context Help Window

You can move the cursor over a state to view the state configuration in the Context Help window. The Context Help window displays the entry action, exit action, and static reactions of the state.

Saving Statecharts for a Previous Version of LabVIEW

You can save a statechart for a previous version of LabVIEW. Select File»Save for Previous Version in the Project Explorer window to display the Save for Previous Version dialog box. Select the version of LabVIEW and save the statechart.

Generating Statechart Code from the Project Explorer Window

You can generate LabVIEW code for a statechart from the Project Explorer window. After you create or update a statechart, right-click the .lvsc file in the Project Explorer window and select Generate LabVIEW Code from the shortcut menu to generate LabVIEW code that corresponds to the statechart.

Using the View Option of the Statechart Communication Functions

In the caller VI, right-click a Statechart Communication function and select View»Statechart to display the Project Explorer window that contains the .lvsc file. Right-click the Statechart Communication function and select View»Statechart Diagram to display the Statechart Editor window.

Deselecting All Triggers

Deselecting all triggers enables a transition or static reaction to react to any triggers in the Triggers list and to any new triggers that you create. You can deselect all triggers by clicking the Deselect All Triggers button in the Triggers/Groups page of the Configure Transition dialog box or Configure State dialog box.

Using New Statechart Module Examples

Refer to the labview\examples\Statechart\ directory for example VIs that demonstrate common tasks and concepts using the LabVIEW Statechart Module. You also can access these VIs by selecting Help»Find Examples and selecting Toolkits and Modules»Statechart in the NI Example Finder window.

System Requirements

• LabVIEW 8.6 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 LabVIEW and the Statechart Module—using the LabVIEW 8.6 Platform DVDs. Refer to the LabVIEW DVD Installation Instructions or the LabVIEW Release Notes, which are available in your LabVIEW box, for information about the LabVIEW Platform DVDs.

Complete the following steps to install the Statechart Module from the LabVIEW 8.6 Statechart Module installation CD.

Note  Some virus detection programs interfere with the installer. Disable any automatic virus detection programs before you install. After installation, check your computer for viruses and enable any virus detection programs you disabled.

• Log on as an administrator or as a user with administrator privileges.
• Insert the LabVIEW 8.6 Statechart Module installation CD and follow the instructions that appear on the screen.
• Activate your LabVIEW products using the NI License Manager.
  

Accessing the Help

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.

• Launch LabVIEW.
• Select Help»Search the LabVIEW Help to launch the LabVIEW Help.
• Click the Contents tab.
• Navigate to the Statechart Module top-level topic.
  

Known Issues

The following items are known issues in the LabVIEW 8.6 Statechart Module.

ID	Known Issue
91194	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.
91443	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 or , 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.
91500	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.
91918	Revert is not available on statecharts Workaround—If you want to discard changes you have made to a statechart, close the statechart and all callers and do not save the changes, then reopen the statechart.
92421	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.
100185	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 Configure State or Configure Transition dialog box may not delete original block diagram constant. Workaround—You can delete original block diagram constants manually.
100729	Unexpected searching may occur when saving Statechart Communication functions to a previous LabVIEW version You may see unexpected search dialogs when saving VIs with Statechart Communication functions to a previous LabVIEW version, but the operation will still complete successfully.
101248	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.
104376	Quick Drop does not work when configuring a Statechart state node or transition node The Quick Drop feature does not work in the Configure Transition and Configure State dialog boxes.

Bug Fixes

The following items are the IDs and titles of a subset of issues fixed in the LabVIEW 8.6 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.

Bug ID	Fixed Issue
52190	The edit triggers dialog should give feedback about non-valid groups so the user knows why the OK button is disabled.
57043	When a statechart pauses because of a breakpoint or custom data display, it should flash its debugging window like we do when we hit a traditional VI breakpoint.
57207	Wiring from the tip of a transition node is difficult.
57685	Statechart does not generate code correctly if Trigger name has dual byte characters.
57692	Save changes dialog for .lvsc file should show changes for all pieces of the statechart.
57807	State nodes sometimes cannot be resized to be as small as desired.
57874	Cannot correctly debug a statechart when its calling VI is running in two different application instances at the same time.
57916	Subdiagram still shows up in error list window even after deleting its state node.
58375	Statechart typedefs should not throw save changes dialog when closed unless statechart is leaving memory as a result of the operation.
58379	Cannot edit statechart typedefs while configuring a state or transition node.
58426	A new statechart on a non-desktop target should automatically have code generation settings appropriate for that target.
58480	Need to show pictorially the current active state of the Statechart.
58664	Context help for a statechart state node should show more information about the actions a state contains.
63095	Renaming a .lvsc file on disk does not work.
63208	Creating a constant from an input to a statechart guard or action VI places the constant off screen.
63425	Easy to confuse statechart editing and debugging windows.
64013	VI properties on statechart diagram should show .lvsc file properties.
64382	Slowness when generating code for a statechart with many guard and action VIs.
65597	Should be able to drop a statechart on a block diagram in all the ways you can drop a subVI on a block diagram.
72668	Execution highlighting in statechart debugging window could be clearer.
94777	After stepping out of subdiagram during statechart debugging, pause button on subdiagram does not stop execution.
94781	Can press execution step buttons while debugging statechart but not paused.
94985	Hang when replacing a string constant with an empty string in statechart state or transition configuration dialog.
97915	Send External Trigger node slowly leaks memory.
103001	Pause button highlighted on statechart debugging window does not always cause execution to be paused.
103002	Statechart debugging window should come to front and flash when statechart next runs if debugging window has pause button enabled.

---

Copyright

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

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.

Other product and company names mentioned herein are trademarks or trade names of their respective companies.

Patents

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.