石鑫华视觉
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 8.6.1F1 Update Win32Eng LV8.6.1状态图模块升级包SC861f1
SC861f1必须要先安装SC861，未找到SC861的升级包，可以先安装SC860的安装包。
LabVIEW Statechart Module 8.6 Win32Eng LV状态图模块SC860
http://pcmv.cn/thread-24890-1-1.html
LabVIEW状态图模块提供了高级抽象来帮助用户设计基于状态、转换和事件的应用程序。
LabVIEW状态图模块是LabVIEW编程环境的一个附加软件。该模块可以在所有NI硬件终端上运行，包括台式PC、实时系统、FPGA和ARM微控制器，而且还可帮助您在架构之间轻松移植代码。
百度网盘下载（限速，请开会员或使用工具下载）:
请注册视觉论坛会员，登陆购买附件查看，充值请联系在线客服
NI官方下载地址（可能无法下载完成或地址无效）：
请注册视觉论坛会员，登陆购买附件查看，充值请联系在线客服
LabVIEW Statechart Module 8.6.1F1 Update Win32Eng LV8.6.1状态图模块升级包SC861f1
http://pcmv.cn/thread-24891-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
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
Bug Fixes
| Bug ID | Fixed Issue |
| 133221 | Statechart Module Generates Broken Code |
LabVIEW 8.6.1 Statechart Module Readme
Known Issues with Version 8.6.1
| 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:
Workaround—Apply the following workarounds for the corresponding issues above:
|
Bug Fixes
| 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
New Features
Changing Function Icon Styles
Displaying the Name of the Current Active State
Displaying Current Active States for Diagrams
Debugging Statecharts on Real-Time Targets
Viewing State Configuration in the Context Help Window
Saving Statecharts for a Previous Version of LabVIEW
Generating Statechart Code from the Project Explorer Window
Using the View Option of the Statechart Communication Functions
Deselecting All Triggers
Using New Statechart Module Examples
System Requirements
LabVIEW 8.6 Base, Full, or Professional Development System for Windows
250 MB additional available disk space
Installation Instructions
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
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
| 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 <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. |
| 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
| 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