石鑫华视觉
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 Simnuation Moudule 1.0 Win32Eng LabVIEW7.1仿真模块SM1.0下载
1.0时叫LabVIEW Simnuation Moudule，后面的版本应该是改名为LabVIEW Simulation Interface Toolkit。大概是同一个模块，具体是不是相同工具包，请查看自述文件自行确认。
LabVIEW Simnuation Moudule 1.0 Win32Eng LabVIEW7.1仿真模块SM1.0下载
http://pcmv.cn/thread-28714-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
LabVIEW Simulation Module Readme
National Instruments LabVIEW 7.1 for Windows, Full or Professional Development Systems
Insert the LabVIEW Simulation Module CD.
Run the setup.exe program.
Follow the instructions that appear on the screen.
The Compare VIs dialog box might not work properly with Simulation functions. The Compare VIs dialog box might not detect changes to the simulation parameters during the comparison.
Large simulation diagrams might take a long time to compile.
Probes will not work correctly on a particular signal if the signal wire data type does not match the indicator or subsystem terminal data type. Use a VI on the Conversion palette to correct this problem.
After adapting to a different polymorphic type, the SimTime Waveform chart reverts to its default formatting. In this case, the SimTime Waveform chart displays the x-axis units using a month/year format rather than seconds. Right-click the waveform chart and select Properties from the shortcut menu to open the Chart Properties: Waveform Chart dialog box. In the Format and Precision tab, change the x-axis format from Absolute time to Relative time or Floating point.
The LabVIEW RT Communication Wizard does not find a Simulation Loop in a stand-alone subsystem. Copy the contents of the subsystem into a Simulation Loop before using the RT Communication Wizard.
Automatic error handling does not work with the Simulation Loop error out terminal. You must explicitly wire a Simple Error Handler VI or a General Error Handler VI to the terminal to make LabVIEW display a dialog box when an error occurs.
If you right-click a continuous mode subVI in the Simulation Loop and select Relink to SubVI from the shortcut menu, the subVI changes to a discrete mode subVI. You can correct this problem by specifying the subVI as continuous. Right-click the subVI icon and select SubVI Node Setup. In the SubVI Node Setup dialog box, remove the checkmark from the Run as Discrete Node checkbox.
The Edit»Undo SubVI Setup and Edit»Redo SubVI Setup options do not affect the Run as Discrete Node option you set in the SubVI Node Setup dialog box for subVIs you place in the Simulation Loop.
If you wire the Simulation Loop parameters terminal, error in terminal, or error out terminal from inside the Simulation Loop, you might receive errors or indeterminate results.
The Run toolbar button might appear broken after you use the Loop Configuration dialog box. This broken Run button occurs only when the Loop Configuration dialog box originally contains a checkmark in the Use terminal checkbox for the Timing Source control. To correct the problem, either 1) click the broken Run button, 2) edit the contents of the Simulation Loop, which tells LabVIEW that the VI needs to be recompiled, or 3) open the Loop Configuration dialog box and click the OK button.
If you set the Integrator function limit type parameter to upper, lower, or both, a variable step-size solver might not evaluate the model and update the model output exactly when the output starts to be limited.
For the Discrete Filter function, the Numerator and Denominator coefficients, which are subparameters of the Filter input, are represented in ascending powers of z^-1.
Performing a mass compile on a VI that contains a missing linked sub-VI inside a Simulation Loop results in the parent VI losing its control and indicator default values.
Performing a Create Sub-VI from the Edit menu on nodes within a Simulation Loop or Subsystem that contains a feedback cycle may cause LabVIEW to crash or report an inaccurate warning. Manually creating a sub-VI from a new VI and subsequently adding it to the Simulation Loop and/or Subsystem avoids this problem.
Do not use a Simulation Module Collector function with the LabVIEW Real-Time Module.
The Simulation Loop depends on many VIs, so the Simulation Loop may take a long time to load on an RT target because LabVIEW must download all the VIs to the RT target.
Refer to the LabVIEW Simulation User Manual for information about running simulation diagrams with LabVIEW Real-Time Module for RTX.
Breakpoints are not supported for standalone subsystem debugging under LabVIEW Real-time. There are two workarounds for this problem. 1) you can use a conditional probe as a breakpoint in the standalone subsystem. 2) You can copy all the code from the subsystem's diagram to a simulation loop, then debug the VI containing the simulation loop. Breakpoints on nodes or wires inside a simulation loop are supported under LabVIEW Real-time.
All controls are placed as one dimensional arrays (or vectors) of double-precision real numbers by default. After all blocks and lines have been placed, the Simulink Translator attempts to correct all mismatched types on the diagram but does not always successfully correct mismatched types. Therefore, in some cases you must set data sources to produce a vector output after the conversion is complete.
Boolean constants might be placed as double-precision real numbers, but the Simulink Translator converts these numbers to Boolean signals before feeding them into terminals requiring Boolean inputs.
The Simulink Translator might convert sample rate divisors on discrete blocks incorrectly. If it does, you must set the sample rate divisors manually after the conversion is complete.
The Simulink Translator does not correctly convert a Bus Selector block with the Muxed Output checked.
All Multiport switches use zero-based indexing.
The Simulink Translator converts the Mux and Demux blocks to Bundle and Unbundle nodes, respectively. Because you can use the Mux and Demux blocks for different purposes within Simulink®, you might want to replace the Bundle and Unbundle functions with Build Array and Index Array functions after the conversion is complete.
The Manual Switch and Initial Condition nodes do not always automatically adapt to the proper scalar or vector type. You might have to correct these nodes manually after the conversion is complete.
If any fields within the Simulink model, such as the Tag field in the Block properties dialog box, contain curly braces, the Simulink Translator might fail or hang.