石鑫华视觉
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 Interface Toolkit 5.0 Win32Eng LabVIEW8.6仿真接口工具包SIT5.0下载
1.0时叫LabVIEW Simnuation Moudule，后面的版本应该是改名为LabVIEW Simulation Interface Toolkit。大概是同一个模块，具体是不是相同工具包，请查看自述文件自行确认。
5.0~LV8.6
文件大小: 96505321 字节 (92.03 MB)
修改日期: 2019-12-17 12:20
MD5: 45aeb3448d7ca804b9d14974cd257357
SHA1: adcfb53b5e488163ff9198c72b850405b577e9ec
SHA256: d7badf48ddfbd3dc1232ecab2faa421a06741ee37acfdc4594ad9f934c1f320e
CRC32: 6b3faeba
百度网盘和NI官方下载地址：
注册登陆视觉论坛用户，购买附件查看下载地址
LabVIEW Simnuation Interface Toolkit 5.0 Win32Eng LabVIEW8.6仿真接口工具包SIT5.0下载
http://pcmv.cn/thread-28715-1-1.html?fromuid=9
(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)
LabVIEW Simulation Interface Toolkit 5.0 Readme
System Requirements
The MathWorks, Inc. MATLAB® software and The MathWorks, Inc Simulink® software application software release 13.x, 14.x, 2006a, 2006b, 2007a, 2007b, or 2008a
The MathWorks, Inc. Real-Time Workshop® software Release 13.x, 14.x, 2006a, 2006b, 2007a, 2007b, or 2008a
Microsoft Visual C++ 6.0 or .NET 2003 or 2005
National Instruments LabVIEW 8.6 Real-Time Module for ETS Targets.
(Optional) National Instruments LabVIEW 8.6 FPGA Module, to create customized FPGA bitfiles used in real-time simulations involving NI FPGA devices.
You also must install the following driver software versions, depending on the type of hardware you want to use.
| National Instruments Hardware | Driver Software Version Required |
| National Instruments FPGA Devices | NI-RIO™ 3.0 or later |
| National Instruments CAN Interfaces | NI-CAN™ 2.6 or later |
| National Instruments DAQ Devices | NI-DAQmx™ 8.7.2 or later |
Installation/Upgrading Instructions
Install and activate the necessary software as described in the System Requirements section of this document.
Uninstall any existing installations of the LabVIEW Simulation Interface Toolkit. If you do not perform this step, the installer automatically uninstalls any existing installations.
Insert the LabVIEW Simulation Interface Toolkit 5.0 installation CD.
Run the setup.exe program.
Follow the instructions that appear on the screen.
| Tip For information about activating the LabVIEW Simulation Interface Toolkit, refer to the Activation Instructions for National Instruments Software document that ships with the LabVIEW Simulation Interface Toolkit 5.0. |
Upgrading from SIT 2.0.x/3.0.x/4.0
Load a host VI saved in SIT 3.0.x/4.0 and launch the SIT Connection Manager dialog box. Click the OK button to apply new settings. The conversion process preserves control/indicator mappings and all block diagram code. You will lose changes to SIT 3.0.x driver VI, but SIT 5.0 maintains hardware mappings. If the path to the model is invalid, SIT 5.0 prompts you to specify a valid path.
SIT 3.0.x driver VIs are not supported in SIT 5.0. If you are not using the SIT Connection Manager you will need to manually upgrade the driver VI. Refer to one of the examples for the correct driver VI structure.
SIT 5.0 does not convert driver VIs that SIT 2.0.x generated. Use the SIT Connection Manager dialog box to build a new driver VI for use in real-time simulations.
SIT 5.0 does not convert host VIs that SIT 2.0 generated.
The Simulation Interface Toolkit 4.0 deprecated the following VIs: SIT Execute Task and SIT Synchronize Base Rate.
The Simulation Interface Toolkit 5.0 relies heavily upon the SIT Connection Manager dialog box. National Instruments recommends you use this dialog box to create host VIs and driver VIs.
When running simulation in Simulation Environment, the SignalProbe blocks from SIT 3.0.x/4.0 do not recognize tuneable variables specified through Data Objects. To be able to tune variables specified as tuneable through Data Objects, you must delete and re-add the SignalProbe block.
Update any custom FPGA bitfiles and VIs you developed in SIT 3.0.x/4.0 to the new FPGA VI template and recompile them.
SIT Write Log Settings to Configuration File.vi and SIT Write Playback Settings to Configuration File.vi in the User API have a new required input for Model Path.
What's New in 5.0
Reconfigurable TDMS Data Logging—Create several logging configurations in the SIT Connection Manager and then switch between them and control them at run time.
Reconfigurable Data Log File Playback—Create several playback configurations in the SIT Connection Manager and then switch between them and control them at run time.
Support for Workspace Variables—You now can map a control to a workspace variable. Updating the workspace variable updates all parameters that are dependent on it.
Tuning Parameters in a StateFlow Chart—You can tune parameters in StateFlow charts using workspace variables.
SIT I/O Blocks—Allow hardware connections to any level of model.
Updated dialog for doing hardware I/O mappings—All hardware types configured and mapped in a single dialog.
Increased I/O in default FPGA Bitfiles—The default FPGA bitfiles now have 8 analog in, 8 analog out, 40 digital in, 40 digital out, 8 PWM in, and 8 PWM out channels.
Improved Probing of Virtual Signals—You now can probe virtual signals in more cases.
Specifying a MDL File—It is no longer necessary to specify a MDL model file when the execution host is Real-Time Target or Driver VI on Localhost.
Project Directory—You can specify a project directory that is different from the MDL or DLL model file directory.
Import of Data Files for Replay—Replay supports importing data from MAT, MDF, TDM, LVM, CSV and TXT files. You may need to get a plugin from http://ni.com/dataplugins to support the data file type.
VxWorks Support Files—Refer to the X:SimulationInterfaceToolkit.0VxWorks
eadme_sit_vxworks.txt for information about enabling VxWorks support where X is the drive letter where you installed the Simulation Interface Toolkit.
Support for Real-Time Targets
PXI
Any PXI-RT controller
FieldPoint
Any Compact FieldPoint controller
CompactRIO
Any CompactRIO controller is supported. A default bitfile is provided for the cRIO-9103 with NI-9215, NI-9263, NI-9411 and NI-9474 I/O modules. If you are using a different controller or a different set of I/O modules you can use LabVIEW FPGA module to compile a custom bitfile.
You can use the Single Point Timed I/O Timing Engine in the FPGA Wizard to help create the FPGA VI for use with SIT. FPGA VIs created by the FPGA Wizard can only be used when there is only one HW timed device in the system. If you are using more than one HW timed device (e.g. two R-series boards in a PXI chassi) you need to use the template provide with SIT.
If you are using a VxWorks-based controller refer to the X:SimulationInterfaceToolkit.0VxWorks eadme_sit_vxworks.txt for information about enabling VxWorks support where X is the drive letter where you installed the Simulation Interface Toolkit.
National Instruments recommends that you do not install the Scan Engine if you are using the CompactRIO controller with Simulation Interface Toolkit.
NI PCI-7811R
NI PXI-7811R
NI PCI-7813R
NI PXI-7813R
NI PCI-7831R
NI PXI-7831R
NI PCI-7833R
NI PXI-7833R
NI cRIO-9103
Accessing the Help and Examples
Launch LabVIEW.
Select Help»Search the LabVIEW Help to launch the LabVIEW Help.
Click the Contents tab.
Navigate to the Toolkits»Simulation Interface top-level topic.
Development Tips
Driver VIs running on NI FPGA devices use the hardware settings for channel measurements.
Known Issues
If you installed the MATLAB application software files as read-only, the SIT Server does not start automatically and you cannot place a SignalProbe block in the Simulink window. You must modify the matlabrc.m file in order to make these changes. Refer to the Communicating with the SIT Server topic in the LabVIEW Help for information about making these changes.
SIT 4.0 driver VIs do not support controlling replay and datalogging configurations until the simulation is running.
You can use only one instance of a typedefed cluster in a SIT host VI.
Importing mappings exported in SIT 3.0.x/4.0 may fail to import some signals if the block name has a linefeed in the name.
You cannot import hardware mappings exported in SIT 3.0.x/4.0 in SIT 5.0.
When converting a model to a model DLL, you can improve conversion time by excluding signals from virtual blocks. However, if you exclude these signals, you cannot probe these signals unless you add a non-virtual block to the signal. Complete the following steps to exclude signals from virtual blocks.
Launch the Simulink application software and load the model you want to convert.
For the MATLAB application software release 13, select Simulation»Simulation parameters to launch the Simulation Parameters dialog box.
For the MATLAB application software release 14, select Simulation»Configuration Parameters to launch the Configuration Parameters dialog box.
Click the Real-Time Workshop tab.
Click the Browse button to launch the System Target File Browser dialog box.
Select nidll.tlc—NI Real-Time Target from the list.
Click the OK button.
For the MATLAB application software release 13, enter nidll.tlc -aNiDisableVirtualBlockMap=1 in the System target file text box.
For the MATLAB application software release 14, enter -aNiDisableVirtualBlockMap=1 in the TLC options text box.
If you do not map file playback channels before you attempt to play back a TDMS file, the driver VI does not execute correctly. Workaround: If you enable file playback, use the Edit Mappings dialog box to map file playback channels before you play back a TDMS file. You also can remove the checkmark from the Enable File Playback option in File Playback page of the SIT Connection Manager dialog box.
When you map a fixed-point control or indicator to a model parameter, LabVIEW returns an error when you run the simulation. Workaround: Do not map fixed-point controls or indicators to a model parameter. Instead, map double-precision controls or indicators to model parameters.
If you run a driver VI on a non-RT target and want to connect to the driver VI by using a networked PC, you must run the driver VI before attempting to connect to it from the networked PC. You also must complete the following steps on the PC running the driver VI.
Launch LabVIEW and open the driver VI.
Select Tools»Options from the pull-down menu.
Select VI Server: Configuration in the Category list.
Place a checkmark in the TCP/IP checkbox.
Select VI Server: Machine Access in the Category list.
Click the Add button, and enter the IP address of the networked PC in the Machine name/address text box.
Select VI Server: Exported VIs in the Category list.
Click the Add button, and enter the path and name of the driver VI in the Exported VI text box.
Click the OK button.
If you are running a multirate simulation and a lower-priority task finishes late, this late finish forces the driver VI to report an overrun, which halts the simulation.
If you map more than one model signal to a host VI indicator, the signals tree does not automatically highlight the signals you selected.
The target model of a model reference block cannot contain a SignalProbe block. Placing a SignalProbe block in a target model prevents the simulation from running.
If you do not specify any signals to probe, SIT 5.0 does not return the current simulation time in the Simulation Details dialog box.
Waveform charts might scroll incorrectly to a slightly different time than the end time of the simulation. For example, the chart might display 299.90 instead of 300.00. This is an issue with the LabVIEW chart. Workaround: Enter the correct end time into the scale of the chart to show the appropriate data.
If you run a simulation more than once, an XY graph does not clear between runs.
SIT is listed under LabVIEW 5.0 in NI License Manager if SIT is installed but LabVIEW 8.6 is not installed.
The LabVIEW Help does not include topics for the following VIs:
SIT Probe Data Log Signals
SIT Read Replay FIFO
The LabVIEW Help does not include topics for the following palettes:The LabVIEW Help incorrectly states that VIs on these palettes are owned by the higher-level Model Interface and User Interface palettes. However, the VI documentation is otherwise accurate.
Data Logging (subpalette of Model Interface)
File Playback (subpalette of Model Interface)
Data Logging (subpalette of User Interface)
File Playback (subpalette of User Interface)
Bug Fixes
| 97408 | There are incorrect values for some multi-rate models. |
| 69875 | The SIT Connection Manager hangs if you try to map a control or indicator with a model that has no parameters or signals. |
| 60086 | Using SIT in Simulation Environment Mode crashes the Simulink software when probing signals. |
| 59224 | sit Get Current Data.vi needs to be re-entrant. |
| 58830 | Multiple SIT DLLs do not work on a single RT target. |
| 58826 | When you are using multiple DLLs with SIT 4.0, you cannot run models. |
| 35937 | Remove cRIO Calibration VIs from SIT personality. |
| 104172 | Error 2206 in driver VI when you stop a simulation programmatically. |
| 95267 | Making a mapping and then deleting control ConnMngr results in error 1055 on close. |
| 61309 | If you cancel the SIT Connection Manager after adding a new mapping, the mapping is retained. |
| 59012 | Not able to probe fixed-point values. |
| 58993 | Multi-rate model with no inports hangs. |
| 58830 | Multiple SIT DLLs do not work on a single RT target. |
| 58550 | _FTPToTarget.llb contains duplicate VIs of other places in VI.lib. |
| 58441 | Virtual signal from inport does not become available for probing in DLL. |
| 58438 | Virtual signal from Demux does not probe correct part of original signal. |
| 57944 | Exiting Data Log Dialog in maximized state makes it appear behind the ConnMngr the next time it's launched. |
| 57845 | Opening SIT example models in R13 (Simulink 5.0) produces a warning. |
| 57842 | Block with more than one output port does not work correctly in SIT DLL for R14.2 and later. |
| 57831 | Logging more than 63 signals in TDMS in SimEnv shifts logged data up one channel. |
| 57477 | Probing 2D signals in DLL returns 1D array in client VI. |
| 57468 | Getting Error 42 when running a client VI with TDMS logging disabled. |
| 57369 | Compile error with models with long file names. |
| 57293 | Allow users to configure time stamp format for data log files. |
| 57228 | Allow mapping to masked S-Function parameters. |
| 57156 | Start driver VI immediately without waiting for client. |
| 56852 | There are problems parsing models saved on another platform. |
| 56829 | SIT needs better error reporting for ftp of DLL. |
| 56806 | List of FPGA targets does not update if they have changed after first search. |
| 56731 | TLC build error in R2006a with a model that has Inline Parameters off and contains a Model Reference block. |
| 56223 | Allow setting of decimation and halt on data loss options in the SIT Connection Manager instead of only in the Simulation Details dialog box. |
| 56122 | Handle complex parameters and signals in the Simulink environment. (complex vector inports) |
| 54354 | In the SIT Connection Manager, add an option for scaling or not scaling controls to parameter size. |
| 42732 | Model parameters show up twice. |
| 40538 | Remap dialog doesn't refresh Model Signals or Parameters tree when rearranging Current Mappings. |
| 40525 | Remap Dialog can be shut down with error 1055 (invalid object reference). |
| 40190 | Clean up host VI running as a executable. |
| 40165 | SIT mappings scroll bar does not update position. |
| 39101 | Error 1077 when setting Knob max scale to infinity. |
| 38552 | Simulation Interface Toolkit shows error when using international regional settings. |