下载中心

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

LabWindows/CVI 2010 SP1 Full Win32Eng LabWindows/CVI2010SP1完整版下载

LabWindows/CVI是一个ANSI C软件开发环境，提供一套用于开发测试和测量应用程序的完整编程工具。
LabWindows/CVI ANSI C集成编程环境可帮助您创建自定义工程应用程序。该环境可用于管理项目、编辑和调试源代码和构建用户界面，并提供一个简化的选项卡式工作区来测试代码输出和性能。LabWindow/CVI提供了高级调试、代码文档描述和系统部署所需的工具，可帮助您集成源代码控制、需求和数据管理系统。该软件还可具有内置仪器I/O库、内置仪器驱动程序或两个交互式测量辅助工具，帮助您更轻松、快速地采集GPIB、USB、串行、以太网、PXI、VXI和FPGA仪器的数据。LabWindows标志经Microsoft公司授权使用。Windows是Microsoft公司在美国和其他国家的注册商标。

自2009版LabWindows开始，NI仅提供完整版和运行版，不再提供基本版。

2010SP1
文件大小: 449059424 字节 (428.26 MB)
修改日期: 2011-06-23 11:48
MD5: 39a367b3fb1e75b4d07c12bbbf2003b5
SHA1: 7e56e9e1b6ab2b6975b8076d0175016f90ef539d
SHA256: cfe6d9195bc1baf498faa25f67a73dac83c50d6d6ca518963db187e6714ea510
CRC32: 340fb7d9

百度和NI官方下载地址：

LabWindows/CVI 2010 SP1 Full Win32Eng LabWindows/CVI2010SP1完整版下载

http://pcmv.cn/thread-25916-1-1.html?fromuid=9

(出处: 视觉论坛VISIONBBS|视觉之家VISIONHOME)

LabWindows/CVI for Windows, Version 2010 Service Pack 1Readme File

Contents

Minimum System Requirements

• Personal computer using a Pentium 1 GHz or higher microprocessor

• Microsoft operating systems:
  

• Windows 7, including Starter Edition (32-bit and 64-bit)

• Windows Vista (32-bit and 64-bit)

• Windows XP Service Pack 2 (32-bit)

• Windows Server 2008 R2 (64-bit)

• Windows Server 2003 R2 (32-bit)
  

• 1024 × 768 resolution (or higher) video adapter

• Minimum of 128 MB of RAM, 512 MB recommended

• 1.1 GB free hard disk space for full installation, which includes the Interface to Win32 Application Programmatic Interface (API)

• Microsoft-compatible mouse
  

Installing LabWindows/CVI

Before Installation

• When installing LabWindows/CVI, the LabWindows/CVI Real-Time Module, and NI Device Drivers, install device drivers after the LabWindows/CVI Real-Time Module. If you install all of these products at the same time using the LabWindows/CVI Platform DVD, the products are installed in the correct order. If you install the LabWindows/CVI Real-Time Module on a computer that already has device drivers installed, reinstall the device driver software to ensure that real-time support is installed for the device drivers you selected.

• When you install LabWindows/CVI, your user account must have administrator privileges.

• The complete Interface to Win32 API is available with the LabWindows/CVI Full Development System. Some Win32 API header and import library files are included when you install the LabWindows/CVI Base Package.

• The LabWindows/CVI installation includes the LabWindows/CVI 2010 SP1 Run-Time Engine. This version replaces any previous version of the LabWindows/CVI Run-Time Engine. After you install LabWindows/CVI 2010 SP1, executables and DLLs created with previous versions of LabWindows/CVI automatically use the new LabWindows/CVI 2010 SP1 Run-Time Engine.
  
  To restore the previous Run-Time Engine, uninstall LabWindows/CVI 2010 SP1 and any previous versions of LabWindows/CVI on the computer. Then reinstall the LabWindows/CVI version you want to use, along with any additional National Instruments software you might have installed.

• If you install LabWindows/CVI onto a network drive, you might encounter an error during installation that prevents files that the IVI Instrument Driver Wizard requires from being installed. This issue does not affect other functionality in LabWindows/CVI.

• If you have installed Microsoft Security Update 896358, you might not be able to view topics within the LabWindows/CVI Help if the file is on a network drive. To solve this issue, copy the .chm files that LabWindows/CVI installs to your local hard drive and launch them as normal.

• The IVI Installer Creator and IVI Specific Driver Test Suite items are selected by default in the installer feature tree only if the IVI Compliance Package is installed. You can select these items if the IVI Compliance Package is not installed, but you must then install the IVI Compliance Package, which you can download from ni.com.

• You can install the Visual Studio 2005 Wizards and Visual Studio 2008 Wizards features only if you have installed Visual Studio 2005 and Visual Studio 2008, respectively.
  

Running the Installation

• Real-Time Module

• Vision Development Module
  

• Execution Profiler Toolkit

• PID Toolkit

• Real-Time Execution Trace Toolkit

• Signal Processing Toolkit

• SQL Toolkit
  

• Insert the LabWindows/CVI media into the disk drive. If the media does not run automatically, open Windows Explorer, right-click the disk drive icon, and select AutoPlay.

• On installation startup, the National Instruments LabWindows/CVI 2010 screen appears. Click Install LabWindows/CVI, Modules, and Toolkits.

• Continue to follow the instructions on the screen.

• If you selected Device Drivers in the Product List, the LabWindows/CVI installer prompts you to insert the National Instruments Device Drivers DVD after you install LabWindows/CVI and any selected modules and toolkits. Follow the instructions on the screen to install the device drivers.

• To activate a National Instruments product, refer to the Activating LabWindows/CVI section.
  

Activating LabWindows/CVI

After Installation

• Installing LabWindows/CVI in a New Directory—If you installed driver or toolkit software for LabWindows/CVI 8.1.1 or earlier and you install LabWindows/CVI 2010 SP1 in a new directory, you must uninstall and reinstall the LabWindows/CVI portion of the driver or toolkit software.

• Using Example Programs—You can find example programs in the following location on Windows 7/Vista/Server 2008: UsersPublicDocumentsNational InstrumentsCVI2010samples. On Windows XP/Server 2003, example programs are located in the following location: Documents and SettingsAll UsersDocumentsNational InstrumentsCVI2010samples.

• Working with Project and File Templates—Save user-defined project and file templates in the LabWindows/CVI public documents directory (Documents and SettingsAll UsersDocumentsNational InstrumentsCVI on Windows XP/Server 2003 and UsersPublicDocumentsNational InstrumentsCVI on Windows 7/Vista/Server 2008). LabWindows/CVI 8.5 and later does not search previous locations, Documents and SettingsAll UsersApplication DataCVI and Documents and Settings<User ID>Application DataCVI, for project and file templates.
  

Upgrading from LabWindows/CVI 2010 or Earlier

• Previous versions of LabWindows/CVI did not recognize numbers entered in scientific notation for numeric controls of type int64 or unsigned int64. Starting with LabWindows/CVI 2010SP1, you can enter numbers in scientific notation. When you enter a number in scientific notation into numeric controls of type int64 or unsigned int64, LabWindows/CVI converts the number to a double and then to a 64-bit integer. This conversion may cause a loss of precision after 15 decimal digits.

• LabWindows/CVI 2010SP1 includes the GaussHypergeometric function, which you should use instead of the GaussHG function.
  

Upgrading from LabWindows/CVI 2009 or Earlier

• Build Options and Target Settings dialog box options apply per configuration. The options on these dialog boxes are no longer global as in previous releases.

• National Instruments no longer supports Windows 2000.

• The minimum operating system version for distributions is Windows XP. If you open an existing distribution that specifies Windows 2000 as the minimum operating system, LabWindows/CVI updates the minimum operating system to Windows XP.

• If you install the Full Development System, the Interface to Win32 Application Programmatic Interface (API) is installed by default.

• The glaux.lib import library is deprecated and is no longer included with LabWindows/CVI. The glaux.prj sample program is no longer installed.

• The Save changes before debugging option in the Environment dialog box is now a global option. In previous releases, this option was workspace-specific.

• The Save changes before compiling option in the Environment dialog box is enabled by default. This global option allows LabWindows/CVI to save all modified files before compiling and debugging.

• LabWindows/CVI no longer installs the Documentation from MSDN Library. National Instruments recommends that you view the latest version of this documentation at www.msdn.com. For more information, visit ni.com.
  

Upgrading from LabWindows/CVI 9.0 or Earlier

• Borland is no longer supported as a compatible compiler or as a third-party compiler in LabWindows/CVI.

• Starting with the 2009 version of LabWindows/CVI, major versions align with the year in which they release. For example, this version of LabWindows/CVI is called LabWindows/CVI 2010. You can find installed files in the CVI2010 folder in the various locations where LabWindows/CVI installs files. The registry keys corresponding to this version of LabWindows/CVI are located in CVI.0 in the registry.

• The NI Distributed System Manager replaces the NI Variable Manager. Use the System Manager to create and monitor network variables, processes, and I/O servers. For more information about the System Manager, refer to the NI Distributed System Manager Help, which you can access from the System Manager.

• The Translate LW DOS Program option is no longer available.

• The LabWindows/CVI compiler now defines the NDEBUG macro for release configuration builds.

• LabWindows/CVI no longer adds _dbg suffix to the base name of the debug target of a project.

• The data type of the targetThreadId parameter of the PostDeferredCallToThread and PostDeferredCallToThreadAndWait functions has been changed from unsigned long to unsigned int.
  

Upgrading from LabWindows/CVI 8.5 or Earlier

• toolbox.h now includes some LabWindows/CVI headers that must be included after including windows.h. Therefore, if your code includes toolbox.h before including windows.h, reverse the order of these includes.

• Network variable processes that begin with NI_ are disallowed. The CNVNewProcess function returns an error if the process name you specify begins with NI_.

• The following macros have been renamed:
  
  

  Library	Previous Macro Name	New Macro Name
  WordReport.fp Instrument Driver	NONE	WR_NONE
  Analysis Library	SORT_ASCENDING	ANALYSIS_SORT_ASCENDING
  Analysis Library	SORT_DESCENDING	ANALYSIS_SORT_DESCENDING

• The enum value CVIConst_CVI_FPVERSION_90 has been changed to CVIConst_CVI_FPVERSION_85 for the fpVersion parameter of the FPGenCreateFunctionTree function of the LabWindows/CVI ActiveX Server Interface Library.

• The modini utility and related source code as well as the modreg source code are deprecated and no longer installed with LabWindows/CVI.

• The LabWindows/CVI Quick Reference card is no longer published and is not installed with LabWindows/CVI.

• The option to create Microsoft Windows WinHelp files (.hlp) from LabWindows/CVI, Generate»Documentation»Windows Help, is no longer available.
  

Known Issues

• Using EVENT_INTERACTIVE_LEGEND for Strip Chart Controls—Although trace indices for strip charts are 1-based, the values for trace indices returned by eventData1 are 0-based. For example, for an event that refers to trace 3, the value returned by eventData1 is 2.
  
  For backwards-compatibility purposes, National Instruments is not correcting this behavior.

• Using the IVI Specific Driver Test Suite—To use the IVI Specific Driver Test Suite in LabWindows/CVI 2010 SP1 or later, you must have ICP 4.4 installed on your computer.

• Incorrect Reference in LabWindows/CVI Release Notes—The LabWindows/CVI Release Notes references the DetachDebugger ActiveX Server Interface function. However, this function is not included in LabWindows/CVI 2010.

• Selecting Files Using Libraries Shortcut—In Windows 7, the Libraries shortcut item in file dialog boxes does not work correctly.

• Zooming Graph Axis—Zooming a graph axis can skew a plot when the magnification becomes too large.

• Using Perforce with LabWindows/CVI—LabWindows/CVI crashes when using the Perforce 2009.1 source code control plug-in.

• Displaying Popups—Second popup can appear behind another popup if the application is not in the foreground when the second popup is displayed.

• Displaying Panels and Windows in Windows 7—LabWindows/CVI panels and windows do not support Aero Shake.

• Availability of Example Programs for Base Package—Examples that only work in FDS are listed in Example Finder when Base version is activated.

• Displaying PNG Images—PNG images with alpha-channel transparency lose their transparency when displayed on transparent classic-style picture controls.

• Numerical Differences in Analysis Function Results—LabWindows/CVI 2010 uses the latest version of the Intel® Math Kernel Library (MKL). Some of the functions in the Intel MKL return different results compared to previous versions of MKL due to optimization, causing slight numerical differences between results from Vector and Matrix Algebra, Statistics, and Curve Fitting functions in LabWindows/CVI 2010 and previous versions of LabWindows/CVI.

• Error When Building a LabWindows/CVI Project in Visual Studio 2005—If you create a project in Visual Studio 2005 that uses LabWindows/CVI libraries, you will see the following error: fatal error LNK1103: debugging information corrupt; recompile module. To address this issue, install the hotfix available from Microsoft.

• Flushing Internal Buffers in a Network Variable Write Operation—Starting with LabWindows/CVI 8.5.1, the Network Variable Library flushes all internal buffers in a write operation, which improves network variable performance.
  
  Flushing on write may cause lower throughput in some high bandwidth conditions, in which case you can set CNVFlushOnWriteAttribute to 0 (FALSE). In high bandwidth conditions, National Instruments recommends using the CNVBufferedWriter connection.

• Flushing Internal Buffers in a Network Variable Read Operation—During a read operation, the Network Variable Library flushes all network variable connections in your program, including data in writer connections, for better performance.

• Debugging Executables on Windows Vista—On Windows Vista, executables that contain setup, install, or update as part of their name automatically require administrator privileges. If you run these executables as stand-alone from a user-level account, Windows will prompt you for an administrator password. However, LabWindows/CVI cannot debug these applications from a user-level account. When you try to run them, LabWindows/CVI displays a Could not run executable notification. NI recommends that you rename your executable so that it does not contain those words in its name, or that you embed a manifest into the application that marks the application as being Vista-aware. You can embed a manifest using the Target Settings dialog box.

• Performing DAQmx USB Buffered Operations on Windows Vista—On Windows Vista x64 Edition, running a program that uses NI-DAQmx 8.5 and terminating the program while it is performing DAQmx USB buffered operations can cause the machine to reboot or to display a Windows kernel bugcheck.
  
  The following may cause a process to terminate unexpectedly:
  

• Selecting the End Process option in the Task Manager to kill the process.

• Using a utility such as pskill to request process termination.

• Shutting down the computer from the command line using shutdown -r -t 0 while the task is still running.

• The process encountering an access violation, breakpoint, or other unhandled exception.

• Attempting to log off, restart, or shutdown and clicking Cancel when the process prompts you to quit or cancel.

• Choosing to stop the process from the LabWindows/CVI debugger while it is running or suspended.
  

• Using Functions Requiring the Low-Level Driver—The LabWindows/CVI low-level driver is not supported on Windows Vista x64 Edition. The following functions are affected: inp, inpd, inpw, MapPhysicalMemory, outp, outpd, outpw, ReadFromPhysicalMemory, ReadFromPhysicalMemoryEx, StartPCSound, StopPCSound, UnMapPhysicalMemory, WriteToPhysicalMemory, WriteToPhysicalMemoryEx.

• Registering ActiveX Servers—When you build ActiveX servers in LabWindows/CVI 8.1.1 and later on Windows Vista and XP, the ActiveX servers are registered in your user profile. This registration is not visible to other users on your system. On previous versions of Windows, ActiveX servers are registered for all users. When you register these servers outside the LabWindows/CVI environment, they are always registered for all users; this option requires administrator privileges on Windows Vista.

• Registering LabWindows/CVI as an ActiveX Server—Installing LabWindows/CVI registers it for all users. Launching LabWindows/CVI registers LabWindows/CVI as an ActiveX server. LabWindows/CVI is registered in your user profile on all versions of Windows.

• Viewing Help—If you open the LabWindows/CVI Help outside of LabWindows/CVI, such as launching it through the Start menu, you might not see all driver or toolkit content. Select Help»Contents to open the LabWindows/CVI Help from within LabWindows/CVI to ensure that all driver and toolkit content is available.

• Creating and Deleting Network Variables and Processes—You may notice that about 50 bytes of memory are lost when you create and delete a network variable or process.

• Using the LabWindows/CVI Conversion Wizard in Microsoft Visual Studio 2005 or Microsoft Visual Studio 2008—Microsoft Visual Studio 2005 and later do not support the single-threaded version of the Visual Studio C library. Therefore, you must configure your project's linker settings to ignore directives to use the single-threaded C library. In Visual Studio, select Project»Properties and expand the properties tree to the Configuration Properties»Linker»Input item. Add libc to the Ignore Specific Library option. Refer to the I Receive Linker Errors When Using LabWindows/CVI-Generated Static Libraries and Object Files in Microsoft Visual Studio 2005 KnowledgeBase article for more information.

• Using the NI Instrument I/O Assistant—The Instrument I/O Assistant 2.0 generates LabWindows/CVI code that is not backward compatible with code that previous versions of the Instrument I/O Assistant generated. If you run code generated with the Instrument I/O Assistant 2.0 with an existing application, the code in that application might not compile.

• Uninstalling LabWindows/CVI—If you have multiple versions of LabWindows/CVI installed and you uninstall one of the versions, the remaining installation will be missing its file associations, and its automation capabilities will not function properly. To fix this problem, perform a repair installation of the remaining LabWindows/CVI version.

• Making Backup .uir Files—Make backup copies of your .uir files if you have been using previous versions of LabWindows/CVI. Once you save .uir files in LabWindows/CVI 2010, the .uir files are no longer compatible with versions 8.1.1 or earlier. You cannot load .uir files that you have saved in LabWindows/CVI 2010 in LabWindows/CVI 8.1.1 or earlier.
  
  You can save .uir files you create or load in LabWindows/CVI 2010 in earlier formats. Select File»Save .uir As and specify the format in the Save as type option. If you save a user interface with features that were added in later versions of LabWindows/CVI, those features are removed when you save the file in earlier formats.

• Using Microsoft Excel as an ActiveX Control—If you develop an application that uses Excel as an ActiveX control on a LabWindows/CVI user interface panel, make sure that a separate instance of Excel is not running simultaneously. Otherwise, programmatic calls to the Excel control might not work as expected after the separate Excel application terminates.

• Navigating Toolkit Topics in the LabWindows/CVI Help—If you click a link from a topic in a toolkit section of the LabWindows/CVI Help or from the toolslib function panel help, you cannot use the Back button in the help viewer toolbar to return to the original topic.

• Using the Advanced Analysis Library—Upgrading to LabWindows/CVI 8.5 and later may cause the Advanced Analysis or Analysis Library to produce numerical differences in floating point results and different results for exceptional inputs, such as positive or negative infinity and NaN. These differences may occur because the underlying C Analysis library has been recompiled in LabWindows/CVI 8.5 to take advantage of new processors and operating systems.

• Analysis Function Behavior Changes—The following function behavior has changed from LabWindows/CVI 7.1 to LabWindows/CVI 8.x:
  

• SVD and CxSVD—The following formula defines the SVD factorization of an n-by-m matrix A: A = USVT.
  
  In LabWindows/CVI 7.1 and earlier, U is an orthogonal matrix of dimensions n-by-m. In LabWindows/CVI 8.x and later, U is an orthogonal matrix of dimensions n-by-min(n, m).
  
  In LabWindows/CVI 7.1 and earlier, V is an orthogonal matrix of dimensions m-by-m. In LabWindows/CVI 8.x and later, V is an orthogonal matrix of dimensions m-by-min(n, m).
  
  In LabWindows/CVI 7.1 and earlier, S is a diagonal matrix of dimensions m-by-m. In LabWindows/CVI 8.x and later, S is a diagonal matrix of dimensions min(n, m)-by-min(n, m).
  
  In LabWindows/CVI 7.1 and earlier, CxSVD has the following requirement: If numberOfRows (n) < numberOfColumns (m), you must allocate m*m*sizeof(ComplexNum) bytes of memory to the input matrix and the U orthogonal matrix. LabWindows/CVI 8.x and later no longer has this requirement.

• Lu and CxLU—In LabWindows/CVI 7.1 and earlier, if the input matrix is singular, the functions stop the decomposition and return SingularMatrixErr. In LabWindows/CVI 8.x and later, if the input matrix is singular, the functions complete the decomposition and return SingularMatrixWarn. In this case, there are one or more zero elements along the diagonal of U.

• CxTrace—CxTrace accepts only a square matrix. In LabWindows/CVI 7.1 and earlier, the function requires both the number of rows and the number of columns as input parameters. In LabWindows/CVI 8.x and later, matrixSize specifies both the number of rows and the number of columns. The numberOfColumns parameter in LabWindows/CVI 7.1 and earlier is a reserved parameter in LabWindows/CVI 8.x and later. This parameter is not referenced in the function.

• ConditionNumber and CxConditionNumber—In LabWindows/CVI 7.1 and earlier, these functions return NaN for singular input matrices. In LabWindows/CVI 8.x and later, these functions return Inf for singular input matrices.

• GenLSFit—In LabWindows/CVI 8.x and later, GenLSFit calculates the mean squared error as the weighted mean square error, which differs from the prior implementation of the function.
  

• Help File Font Size—Starting with LabWindows/CVI 2009, the LabWindows/CVI Help includes a Font button that you can use to increase or decrease the font size in the help file. The Font button might not update the font size in help files that merge into the LabWindows/CVI Help.
  
  In addition, the smallest font size setting of the Font button is the standard font size for National Instruments help files. The text size settings in Internet Explorer might cause the font to appear larger than typical National Instruments help files. If you resize the font, the help file retains the font size the next time you open the product help.
  

Bug Fixes

Development Environment

Performance

User Interface

Compiler

Stand-Alone Applications and Distributions

.NET and ActiveX

Analysis

Miscellaneous

Notice Regarding Microsoft Silverlight Installation and RedistributionInstalling Microsoft Silverlight

Using Microsoft Silverlight

Redistribution of Microsoft Silverlight