石鑫华视觉
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地址，只能使用百度网盘地址；如果百度网盘地址失效过期，可联系论坛客服更新。NI的服务器在美国，有时候速度很慢或下载容易出错，这样会造成安装时各种错误而无法安装。建议在下载完成后，对下载资源做校验和(NI一般会提供MD5或SHA256等)验证，与官方或视觉论坛提供的校验和对比，一致就可以安装；如不一致，则需要重新下载。视觉论坛早期下载上传的资源，基本上都是正常下载的资源；2019后下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘。校验和工具下载地址：文件Hash计算器FHash，文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算http://pcmv.cn/thread-26524-1-1.html
NI LabVIEW 2016 Win32ENG/FRE/GER/JPN/KOR 32位LV2016英语/法语/德语/日语/韩语版多国语言下载
什么是LabVIEW 2016？
LabVIEW 2016是目前可靠性最高的版本，可以帮助您大胆地创新，高效地开发工程应用。 这些新的功能可以抽象底层细节，简化开发，助您专注于要解决的问题，而不是编程语法。 利用LabVIEW的开放性，您可集成任何硬件终端或编程语言。 LabVIEW 2016提供了对第三方设备的更多支持，并提高了与开源软件工具的集成度，使您可以针对应用需求使用正确的工具组合来构建最佳解决方案。
该版本包含LabVIEW的新特性、各类LabVIEW模块，以及针对其余LabVIEW平台的更新和缺陷修复。本版本对核图标风格进行了间距扩大处理，以显示更多的字符信息
LabVIEW2016 32位英语版
百度网盘和NI官方下载地址：
请注册视觉论坛会员登录后购买附件下载查看
NI LabVIEW 2016 Win32ENG/FRE/GER/JPN/KOR 32位LV2016英语/法语/德语/日语/韩语版多国语言下载
http://pcmv.cn/thread-14097-1-1.html?fromuid=9
(出处: 机器视觉论坛)
LabVIEW2016 32位法语版
百度网盘和NI官方下载地址：
NI LabVIEW 2016 Win32ENG/FRE/GER/JPN/KOR 32位LV2016英语/法语/德语/日语/韩语版多国语言下载
http://pcmv.cn/thread-14097-1-1.html?fromuid=9
(出处: 机器视觉论坛)
LabVIEW2016 32位德语版
百度网盘和NI官方下载地址：
NI LabVIEW 2016 Win32ENG/FRE/GER/JPN/KOR 32位LV2016英语/法语/德语/日语/韩语版多国语言下载
http://pcmv.cn/thread-14097-1-1.html?fromuid=9
(出处: 机器视觉论坛)
LabVIEW2016 32位日语版
百度网盘和NI官方下载地址：
NI LabVIEW 2016 Win32ENG/FRE/GER/JPN/KOR 32位LV2016英语/法语/德语/日语/韩语版多国语言下载
http://pcmv.cn/thread-14097-1-1.html?fromuid=9
(出处: 机器视觉论坛)
LabVIEW2016 32位韩语版
百度网盘和NI官方下载地址：
NI LabVIEW 2016 Win32ENG/FRE/GER/JPN/KOR 32位LV2016英语/法语/德语/日语/韩语版多国语言下载
http://pcmv.cn/thread-14097-1-1.html?fromuid=9
(出处: 机器视觉论坛)
LabVIEW 2016 Readme for Windows
System Requirements
| Windows | Run-Time Engine | Development Environment |
| Processor | Pentium III/Celeron 866 MHz (or equivalent) or later (32-bit) Pentium 4 G1 (or equivalent) or later (64-bit) | Pentium 4M (or equivalent) or later (32-bit) Pentium 4 G1 (or equivalent) or later (64-bit) |
| RAM | 256 MB | 1 GB |
| Screen Resolution | 1024 x 768 pixels | 1024 x 768 pixels |
| Operating System | Windows 10/8.11/7 SP12 Windows Server 2012 R21 Windows Server 2008 R2 SP12 | Windows 10/8.11/7 SP12 Windows Server 2012 R21 Windows Server 2008 R2 SP12 |
| Disk Space | 620 MB | 5 GB (includes default drivers from the NI Device Drivers media) |
| Color Palette | N/A | LabVIEW and the LabVIEW Help contain 16-bit color graphics. LabVIEW requires a minimum color palette setting of 16-bit color. |
| Temporary Files Directory | N/A | LabVIEW uses a directory for storing temporary files. NI recommends that you have several megabytes of disk space available for this temporary directory. |
| Adobe Reader | N/A | You must have Adobe Reader installed to search PDF versions of all LabVIEW manuals. |
| 1 NI software installs VC2015 Runtime and .NET 4.6.1. Windows 8.1 and Windows Server 2012 R2 require Microsoft updates to support these items. Refer to Microsoft KB2919442 and KB2919355 for more information about how to install these updates. 2 NI software is signed with a SHA-256 certificate. Windows 7 SP1, Windows Embedded Standard 7 SP1, and Windows Server 2008 R2 SP1 require Microsoft updates to support SHA-256. Refer to Microsoft KB3033929 for more information about how to install this security update. Note You cannot access LabVIEW using a Guest account on Windows. | ||
Installation Instructions
LabVIEW Installation Guide—Includes information about installing LabVIEW, modules and toolkits, drivers, and hardware.
LabVIEW Upgrade Notes—Includes information about protecting existing VIs and projects before you install a new version of LabVIEW, as well as upgrade and compatibility issues and a complete list of new features in LabVIEW 2016.
If Windows Update is enabled, the installation process might hang if Windows Update interferes with the installation of Microsoft Visual C++ 2015 Run-Time. Visit ni.com/info and enter the Info Code exjq43 for more information and steps to resolve this issue.
If you purchased this product with an NI Software Suite or NI Product Bundle, use the installation media that shipped with your purchase to install this product.
LabVIEW 2016 Drops Support for Microsoft Windows 7 RTM, Windows Vista, Windows XP, and Windows Server 2003
Product Security and Critical Updates
LabVIEW 2016 (64-bit)
Supported Hardware
Supported Modules and Toolkits
| Product | LabVIEW 2016 (32-bit) | LabVIEW 2016 (64-bit) |
| Advanced Signal Processing Toolkit | ✓ | — |
| Control Design and Simulation Module | ✓ | ✓1 |
| Database Connectivity Toolkit | ✓ | — |
| DataFinder Toolkit | ✓ | — |
| Datalogging and Supervisory Control Module | ✓ | — |
| Desktop Execution Trace Toolkit for Windows | ✓ | ✓ |
| Digital Filter Design Toolkit | ✓ | — |
| FPGA Module | ✓ | — |
| MathScript RT Module | ✓ | ✓2 |
| Report Generation Toolkit for Microsoft Office | ✓ | ✓ |
| Real-Time Module | ✓ | — |
| Robotics Module | ✓ | — |
| SoftMotion Module | ✓ | — |
| Statechart Module | ✓ | — |
| Sound and Vibration Measurement Suite | ✓ | ✓ |
| Unit Test Framework Toolkit | ✓ | ✓ |
| VI Analyzer Toolkit | ✓ | ✓ |
| Vision Development Module | ✓ | ✓ |
| 1 The Control Design and Simulation Module (64-bit) does not support the System Identification VIs, System Identification Assistant, and Control Design Assistant. 2 The MathScript RT Module (64-bit) does not support the libraries class of MathScript RT Module functions. | ||
Known Issues
Bug Fixes
| ID | Fixed Issue |
| 333388 | Incorrect highlight execution order with LVOOP property node |
| 405304 | Menu Item VIs can cause LabVIEW to crash |
| 425622 | Edit Events menu for Event Structures can delete the new event you are trying to create |
| 434420 | Leading zeros are not allowed in Numeric Case Selector values |
| 463239 | Resizing the front panel in an EXE and running Quit LabVIEW.vi causes an access violation |
| 468139 | .NET Callback Event VI keeps the Callback VI reserved even after calling a Close Reference VI is called |
| 518954 | Unconstrained Downhill Simplex ignores some stopping conditions |
| 519216 | LabVIEW crash when closing subVI Icon Editor that was opened from VI Hierarchy |
| 526175 | Spreadsheet String to Array VI crashes when an empty string is wired to delimeter input |
| 530595 | Not a Refnum Primitive returns incorrect value when evaluating a specific type of "Invalid Refnum" |
| 533890 | lvinput.dll crashes on Surface Pro 3 |
| 534553 | Quit LabVIEW function closes VI if you choose cancel |
| 539895 | File Dialog Express VI alters error chain |
| 544435 | 1-D Array Probe Display Window has issues with high resolutions |
| 544526 | Fatal Internal Error 0x89B93EF0: "drawmgr2.cpp" when running Mac application for extended time |
| 544533 | Scripting dynamic events on an event structure returns Error 1 |
| 544907 | Delaunay Triangulation hangs on certain input data |
| 546555 | Error 1025 when creating Override VI for an already open parent class |
| 547120 | Incorrect VI dataflow when using an Error Wire with a parallelized For Loop |
| 548355 | Running a VI using the 'DataSocket Select URL.VI', navigating to a remote machine on the network, and browsing to the DataSocket Server Item can cause LabVIEW to crash |
| 549429 | DAbort 0x34E86741 ConvertNum called with non-numeric |
| 554381 | Sort items in the Choose Implementation class dialog alphabetically |
| 555317 | In rare cases Waveform Charts can show different sets of data when pulling from the same source |
| 555758 | Using the 'Unflatten From String Function' to unflatten an "invalid" string within LabVIEW x64 can cause the computer to become unresponsive |
| 555788 | Using "Fast File Format" to build an executable could result in error 2208 in some cases |
| 555868 | Using the Tree Control 'Drag Starting? Event' allows you to Delete the reference to the item you are dragging and can result in a LabVIEW crash |
| 561615 | In specific cases, building a LabVIEW executable with shared variables causes Error 1003 during the build |
| 564219 | Sometimes if RFmx continuously modifies the loading state of the UI thread, a race condition can occur and potentially cause a crash |
| 564417 | Special characters in Control names can cause Unit Tests to not recognize cluster elements in some cases |
| 567369 | LabVIEW crashes when getting the properties of a class containing a member VI with certain connector pane configurations. |
| 569362 | In cases of extreme load on a TCP server, LabVIEW can miss new connection notifications, causing a timeout |
| 569793 | Rare persistent Error 56 at TCP Read |
| 570547 | Bluetooth Read, Write, and Close primitives have TCP icon |
| 571421 | In certain cases, dynamically calling a VI containing a SubVI can cause a memory leak. The size of the memory leak scales with the size of the SubVI and its dependencies |
| 571556 | Showing Visible Items on Waveform Chart probe does not resize chart in the probe window |
| 571713 | Scripting a Value Change event for an IVI Logical Name control crashes LabVIEW |
| 571935 | Closing a project library containing a class with unsaved changes does not prompt for save |
| 573160 | The German, Chinese, and Japanese LabVIEW registry files have the incorrect LabVIEW version |
| 573195 | If applications called from SystemExec.vi crash, it can affect LabVIEW TCP communication |
| 573539 | In some cases, DNS name resolution in LabVIEW can block other TCP calls |
| 574048 | Error 8 when trying to create an actor under an unsaved library |
| 575278 | Error 1019 when creating a message, if the actor contains a never-before-saved method |
| 578899 | LabVIEW 64-bit Development Environment has the potential to crash while running certain RFmx examples |
| 580210 | Remote debugging sessions that involve packed project libraries can stop unexpectedly |
| 580212 | Remote debugging VIs that were built without front panels can close the session unexpectedly |
| 581199 | Unflatten From String throws error 74, does not update indicators |
| 585229 | LabVIEW packed project library can cause calling executable to break when rebuilt |
Additions to the LabVIEW Help
Installers built on a computer that has LabVIEW 2016 installed can only run on the operating systems that LabVIEW 2016 supports, even if you used an earlier version of LabVIEW to build those installers. To build an installer that can run on an operating system supported by an earlier version of LabVIEW but not by LabVIEW 2016, you must first uninstall LabVIEW 2016 and reinstall the earlier version of LabVIEW.
Finding Examples
Automating the Installation of NI Products
For more information about silent installations of individual NI products, refer to KB 4CJDP38M, Automating the Installation of a Single Installer.
For more information about silent installations of NI products in a suite, such as NI Developer Suite, refer to KB 4GGGDQH0, How Do I Automate the Installation of a Suited Installer?.
To determine what version of NI Installers your product contains, refer to KB 4CJDR18M, How Can I Determine the Type and Version of My NI Installer?.
Using NI Software with Microsoft Windows 10
Using NI Software with Microsoft Windows 8.1
Legal Information
Notices are located in the <National Instruments> directories.
EULAs are located in the <National Instruments>SharedMDFLegallicense directory.
Review <National Instruments>_Legal Information.txt for information on including legal information in installers built with NI products.