LabWindows/CVI 2020 f3 and Drivers Win32Eng LabWindows/CVI2020f3和驱动下载

石鑫华视觉

LabWindows/CVI 2020 f3 and Drivers Win32Eng LabWindows/CVI2020f3和驱动下载

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

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

Windows系统下（Linux和MAC系统下请自行了解清楚）NI的各种软件、模块、工具包、驱动程序，使用NI许可证管理器来激活的，绝大部分的都可以使用NI Lincense Activator来激活：NI序列号Serial Number生成激活工具NI License Activator，LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本http://visionbbs.com/thread-490-1-1.html

视觉论坛的各种NI资源，除了视觉相关的模块有使用外，大部分的都不会使用，仅提供资源不提供技术支持。资源的下载地址一般会同时提供NI官方和百度网盘的地址。某些工具包NI地址失效或没有NI地址，只能使用百度网盘地址；如果百度网盘地址失效过期，可联系论坛客服更新。NI的服务器在美国，有时候速度很慢或下载容易出错，这样会造成安装时各种错误而无法安装。建议在下载完成后，对下载资源做校验和(NI一般会提供MD5或SHA256等)验证，与官方或视觉论坛提供的校验和对比，一致就可以安装；如不一致，则需要重新下载。视觉论坛早期下载上传的资源，基本上都是正常下载的资源；2019后下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘。校验和工具下载地址：文件Hash计算器FHash，文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算http://visionbbs.com/thread-26524-1-1.html

LabWindows/CVI 2020f3 and Drivers
发布日期：2023/4/18
包含的版本：2020F3和驱动，版本号20.0.3
受支持的操作系统:
Windows 7 (SP1) 32-bit
Windows 7 (SP1) 64-bit
Windows 8.1 32-bit
Windows 8.1 64-bit
Windows 10 32-bit
Windows 10 64-bit
Windows Embedded Standard 7 (SP1)
Windows Server 2008 R2 (SP1) 64-bit
Windows Server 2012 R2 64-bit
Windows 11
语言：英文
程序位数：32位
校验和：
文件大小: 20625688576 字节 (19.21 GB)
修改日期: 2023-04-12 21:50
MD5: 9b1f6c5425d4f0001c12119fadb2c246
SHA1: 3a88b7a7393e3bb2889bb10227e9512510255b3a
SHA256: 0938f358c078fe8c58dca7e654a76fd0c03fcf14f623dcc29f54f90ede9d1da0
CRC32: f7ba61d1

百度和NI官方下载地址：
请注册登陆机器视觉论坛，购买附件查看下载地址
LWCVI2020F3Full and Drivers.txt (612 Bytes, 下载次数: 0, 售价: 40 元)

2023-9-20 08:49 上传

点击文件名下载附件

LabWindows/CVI for Windows 2020 f3 Readme

This file contains important information about LabWindows™/CVI™, including installation instructions, programming considerations, new features, a partial list of bugs fixed for LabWindows/CVI 2020, and known issues.

System Requirements

Installation Instructions

After Installation

Behavior Changes in LabWindows/CVI

    Behavior Changes Introduced in LabWindows/CVI 2019

    Behavior Changes Introduced in LabWindows/CVI 2015 SP1

    Behavior Changes Introduced in LabWindows/CVI 2013 SP2

    Behavior Changes Introduced in LabWindows/CVI 2013

    Behavior Changes Introduced in LabWindows/CVI 2010

    Behavior Changes Introduced in LabWindows/CVI 9.0 and Earlier

Bug Fixes

Finding Examples

Using NI Software with Microsoft Windows 11

Using NI Software with Microsoft Windows 8.1

Legal Information

System Requirements

LabWindows/CVI 2020 supports the following operating systems:

• Windows 11/10/8.11/7 SP12
• Windows Embedded Standard 7 SP12
• Windows Server 2016
• Windows Server 2012 R21
• Windows Server 2008 R2 SP12
  

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 and KB3125574 for more information about how to install these updates.

Note  Refer to LabWindows/CVI Drops Support for Windows 7 (32- and 64-Bit), Windows Server 2008 R2, and All 32-Bit Windows Operating Systems in 2021 for information about future OS support.

For more information about the changes to our OS support for 2016, visit ni.com/r/OSSupport2016.

NI installs LabWindows/CVI using NI Package Manager. If you do not already have NI software installed, LabWindows/CVI installs NI Package Manager to handle the installation of your NI software. Visit ni.com/r/NIPMDownload to download NI Package Manager. Refer to the NI Package Manager Manual for more information about installing, removing, and upgrading NI software using NI Package Manager.

LabWindows/CVI and Drivers includes LabWindows/CVI and the following modules and toolkits, in addition to driver support for LabWindows/CVI.

Toolkits

• LabWindows/CVI Database Connectivity (SQL) Toolkit
• LabWindows/CVI PID Control Toolkit
• LabWindows/CVI Execution Profiler Toolkit
• NI ECU Measurement and Calibration Toolkit
• NI Automotive Diagnostic Command Set
  

If you want to evaluate other modules or toolkits before purchasing them, you can install these add-ons and try them for 45 days. After an initial 7 day period, you can register on ni.com for access to the remainder of the evaluation period.

Installation Considerations

• The LabWindows/CVI installation includes the LabWindows/CVI 2020 Shared Runtime. This version replaces any previous version of the LabWindows/CVI Shared Runtime. After you install LabWindows/CVI 2020, executables and DLLs created with previous versions of LabWindows/CVI automatically use the new LabWindows/CVI 2020 Shared Runtime.
  To restore the previous shared runtime, uninstall LabWindows/CVI 2020 and any previous versions of LabWindows/CVI on the computer. Then reinstall the LabWindows/CVI version you want to use.
• 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.
• IVI Tools for LabWindows/CVI can be installed only if the IVI Compliance Package product is selected or if the IVI Compliance Package is already installed.
• If your software is part of a Volume License Agreement (VLA), contact your VLA administrator for installation instructions.
  

Running the Installation

Note  You must install Windows SDK 8.1 components, available with the LabWindows/CVI installer. If you do not install these components, LabWindows/CVI will not function properly.

If you install software using LabWindows/CVI media, insert the media and follow the on-screen instructions to install LabWindows/CVI, modules, toolkits, and drivers. When prompted, log in to your NI User Account to activate your NI products. If you are managing your license with a volume license server, you should receive your volume license file by email.

Product Security and Critical Updates

LabWindows/CVI no longer installs IVI Compliance Package (ICP). LabWindows/CVI supports IVI configuration and runtime, but no longer installs the following IVI components:

• LabVIEW and CVI IVI class drivers for developing IVI interchangeable applications
• IVI Class Simulation drivers
• IVI-COM Adapters
  

Support for UTF-8 Encoding

• UI Library and UI Editor – Develop user interfaces to display UTF-8 strings with the new encoding attribute for panels and menus.
• Other CVI libraries – Expand the functionality of your application with added UTF-8 support to the following libraries:
  
  • TDM Streaming Library
  • Formatting Library
  • Utility Library
  • DDE Library
  • RS-232 Library
  • ANSI-C Library
  • ActiveX Library
  • Internet Library
  • Toolslib Library
  • XML Library
  • INI Library
  • Menu Utility Library
  • A subset of custom controls
    
• Debugging Tools – Debug applications containing UTF-8 characters using the environment debugger integration tools such as the Array Display, Watch Window, and Variables Window.
• Source Code Editor – Write source code containing UTF-8 strings or change the encoding of the current source file using the Edit menu utilities.
  

Project Encoding Conversion

• Convert the encoding of existing ANSI projects to UTF-8 or vice-versa. Change the project encoding from the Edit Project dialog box, Edit»Project, the Build Options dialog box, Options»Build Options, or enable the Convert projects to UTF-8 on load in the Environment dialog box, Options»Environment.
  

Live Error Indicator

• View errors and diagnostics in the source editor before compiling a project.
  

New Utility Library Functions

• GetKeyUnicode
• IsUTF8PathLengthValid
• MBStrToUTF8Str
• MBStrToUTF8StrBuf
• UTF8StrToMBStr
• UTF8StrToMBStrBuf
• PackKeyCodeUnicode
• UnpackKeyCodeUnicode
  

New User Interface Library Functions

• FakeKeystrokeUnicode
  

After Installation

• Using Example Programs—Find example programs in the following location: Users\Public\Public Documents\National Instruments\CVI2020\samples.
• Working with Project and File Templates—Save user-defined project and file templates in the LabWindows/CVI public documents directory (Users\Public\Public Documents\National Instruments\CVI). LabWindows/CVI 8.5 and later does not search previous locations, Documents and Settings\All Users\Application Data\CVI and Documents and Settings\\Application Data\CVI, for project and file templates.
• 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 2020, 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 2020 in LabWindows/CVI 8.1.1 or earlier.
  You can save .uir files you create or load in LabWindows/CVI 2020 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.
  

Product Security and Critical Updates

Refer to the following sections for behavior changes specific to different versions of LabWindows/CVI. Refer to the LabWindows/CVI Release Information web page on ni.com for an up-to-date list of behavior changes in LabWindows/CVI.

Behavior Changes Introduced in LabWindows/CVI 2020

• Encoding:
  
  • Functions with string parameters have both an ANSI and UTF-8 version. LabWindows/CVI indicates the version of the function with a suffix, such as SetCtrlAttributeAnsi or SetCtrlAttributeUtf8. LabWindows/CVI automatically maps functions in ANSI projects and applications to the ANSI-suffixed version. Internally, LabWindows/CVI 2020 works with UTF-8 strings. When you use the ANSI version of a function, the conversion between encoding types can result in errors:
    
    • Converting from UTF-8 to ANSI can result in loss of data, manifesting as missing characters replaced by question marks.
    • Converting from ANSI to UTF-8 can result in incorrect characters if the character set used for creating the ANSI string is different from the System code page. For example, when you call SetCtrlVal for an ANSI encoded string, the string returned by GetCtrlVal may not be identical to the input string. In general, you must change the character set of the control before calling a getter/setter function if the character set is different from the System code page to avoid these conversion errors.
      
  • User Interface Library:
    
    • When you call the ANSI version of InsertAxisItem and ReplaceAxisItem, only the first 31 bytes of the string are shown in the axis label. When you call the UTF-8 version of InsertAxisItem and ReplaceAxisItem, the byte limit of the axis label is 255.
    • The string size limit is removed for setting the axes names of graph, strip chart, and digital graph controls. To determine the size of the buffer to pass when you are obtaining the name, call GetCtrlAttribute and specify the ATTR_XNAME_LENGTH or ATTR_YNAME_LENGTH attribute. For backwards compatibility, setting the axes names using SetCtrlAttributeAnsi is limited to 30 bytes.
      Note:  In ANSI projects the function SetCtrlAttribute is mapped automatically to SetCtrlAttributeAnsi.
      
  • The dictionary (.lwd) files you create in using Tools»User Interface Localizer are not backwards compatible with previous versions of LabWindows/CVI if one or more of your panels has UTF-8 encoding.
  • The LabWindows/CVI enviroment only supports file paths that are compatible with the System Codepage.
  • Function panels support UTF-8 characters only in operate mode.
  • The character set for interpreting ANSI strings in LabWindows/CVI environment windows is specified globally as an environment option using Options»Environment rather than individually for each window using Options»Font.
    
• For panels where Drag-And-Drop support is enabled, the eventData1 callback parameter for EVENT_FILESDROPPED is no longer backwards compatible for 32-bit programs.
• LabWindows/CVI 2020 does not include the LabWindows/CVI Real-Time Module and does not support real-time applications. Install LabWindows/CVI 2019 to use LabWindows/CVI Real-Time Module or if you need support for real-time applications.
  

Behavior Changes Introduced in LabWindows/CVI 2019

• When you build a Windows installer in LabWindows/CVI, the default name of the executable is changed from setup.exe to install.exe. This behavior change may have potential impact to post-build processes that rely on the setup.exe name. To specify a different name for the executable, use the Installer Executable Name option on the Advanced tab of the Edit Installer dialog box.
• LabWindows/CVI no longer ships executables with sample projects. You must build the project to create an executable.
  
  • iconedit.exe - Icon Editor - Previous LabWindows/CVI releases included it in two locations: LabWindows/CVI Samples and LabWindows/CVI installation folder. Now it will be found only in LabWindows/CVI installation folder: \National Instruments\CVI2019\bin\iconedit.exe
  • build.exe - Command line build tool - You will need to build it before using it.
  • SelectColor.dll
  • cviLibCust.dll
    
• The following files are removed:
  
  • NIReports
  • Merge modules installed in the system merge module directory C:\Program Files\Common Files\Merge Modules
  • 8.1 Network Variable library support from the system Global Assembly Cache (GAC)
  • LabWindows/CVI sample application GetInfoByZip
    

Behavior Changes Introduced in LabWindows/CVI 2017

• The following components and features were deprecated in LabWindows/CVI 2017:
  
  • NIReports
  • Merge Modules installed by LabWindows/CVI in system's merge module directory (C:\Program Files\Common Files\Merge Modules).
  • Support for LabWindows/CVI Library with .NET 1.1 and 2.0
  • LabWindows/CVI versions of the Clang 2.6 and 2.9 compilers shipped with LabWindows/CVI
    Note  Deprecated components can still be used, but they are less visible than fully supported components and are likely to be removed in a future version of LabWindows/CVI. NI recommends that you do not use deprecated components in new applications and that you update existing applications to remove dependencies on deprecated components.
    
• The following components were removed in LabWindows/CVI 2017:
  
  • cvirt.dll
  • LabWindows/CVI Project Wizards for Visual Studio
  • LabWindows/CVI support for DIAdem Connectivity Library (NI-USI)Note  NI recommends that you use the TDM Streaming Library for existing projects and the TDM C DLL for new projects. Refer to ni.com/white-paper/3727/ to download the TDM C DLL.
    
• LabWindows/CVI 2017 removes the Make .obj build option compatible with LabWindows/CVI 5.0.1.
• LabWindows/CVI 2017 deprecates the ni7seg.ttf and nisystem.ttf fonts. These fonts will be removed in the next release.
• After installing an NI product that upgrades the LabWindows/CVI Runtime Engine to 2017, distributions created in LabWindows/CVI 2015 or earlier can no longer target Windows XP.
• After installing an NI product that upgrades the LabWindows/CVI Runtime Engine to 2017, distributions created in LabWindows/CVI 2012 that do not have all components of the LabWindows/CVI Shared Runtime Engine selected in the Drivers and Components tab page will require users to manually install Microsoft Visual C++ 2015 Runtime on the target computer.
  

Behavior Changes Introduced in LabWindows/CVI 2015 SP1

• LabWindows/CVI 2015 and later displays warnings that are part of the Compiler Warnings dialog box. Pragma messages are displayed as notes.
• Minimum and maximum OS value ranges can overlap in the Edit Installer»Advanced range selections.
• The WINVER Windows SDK macro is defined to the value corresponding to Windows 7.
  

Behavior Changes Introduced in LabWindows/CVI 2015

• The LabWindows/CVI installation includes the complete Windows 8.1 SDK.
• The Instrument I/O Assistant is no longer accessible by default through the LabWindows/CVI environment. The Tools»Create Instrument I/O Task is no longer available.
• The DIAdem Connectivity Library is no longer available by default. To use this library, select Library»Customize and enable the DIAdem Connectivity option. NI recommends that you use the TDM Streaming Library for new projects.
• The NI-USI component, which is necessary for applications that use the DIAdem Connectivity Library, is no longer included in the LabWindows/CVI Runtime. To deploy applications that use DIAdem Connectivity Library functions, create an installer and select the NI USI item in the Drivers & Components tab of the Edit Installer dialog box.
• The Variables and Call Stack window lists static local variables before local variables. In previous versions of LabWindows/CVI, local variables appeared before static local variables.
• You cannot use LabWindows/CVI 2013 to debug DLLs you create with LabWindows/CVI 2015.
• Files installed with the Windows SDK are in different locations than in previous versions of LabWindows/CVI:

  Files	Previous Location	Current Location
  Import libraries	\sdk\lib	\Windows Kits\8.1\Lib\winv6.3\um\x86 (or \x64)
  Include files	\sdk\include	National Instruments\Shared\MSDTRedistributables\SDKHeaderFiles\8.1

  
  

Behavior Changes Introduced in LabWindows/CVI 2013 SP2

• Activating the LabWindows/CVI Base Package also activates the LabWindows/CVI PID Control Toolkit.
• Activating the LabWindows/CVI Full Development System also activates the LabWindows/CVI PID Control Toolkit, LabWindows/CVI Database Connectivity (SQL) Toolkit, and LabWindows/CVI Execution Profiler Toolkit.
  

Behavior Changes Introduced in LabWindows/CVI 2013 SP1

• You can specify a .c file as the module to load to the LoadExternalModule and LoadExternalModuleEx functions.
  

Behavior Changes Introduced in LabWindows/CVI 2013

• The following product components no longer appear in the tree on the Driver and Components tab of the Edit Installer dialog box:
  
  • Standard Runtime
  • Instrument Driver Runtime
  • Real-Time Runtime
    
  
  If you select NI LabWindows/CVI Shared Runtime Engine from the tree, LabWindows/CVI includes these components automatically.
• The minimum installer size when including the runtime engine increased by approximately 41MB compared to previous versions of LabWindows/CVI. To decrease the size of your distribution, you can include LabWindows/CVI merge modules. For more information, refer to KB 6AHC1EQW.
• The Install LabWindows/CVI Shared Runtime Engine in the application directory option on the Advanced tab of the Edit Installer dialog box is deprecated. If you need to install and preserve a specific version of the LabWindows/CVI Runtime Engine, consider installing the LabWindows/CVI Side-by-Side Runtime Engine. Refer to the Binding Executables and DLLs to Side-by-Side Runtime Engines topic in the LabWindows/CVI Help for more information about the Side-by-Side Runtime Engine.
• The Project Tree no longer displays the Status column.
• If you enable the Build with C99 extensions option, the Require function prototypes option is always implicitly enabled.
• The results of several mathematical operations performed using floating-point numbers might differ from results returned in previous versions of LabWindows/CVI. The differences are small and within acceptable error ranges for the data types.
• Function calls are no longer allowed in watch expressions or in the condition of a breakpoint.
• You must rebuild any EXEs and DLLs built in LabWindows/CVI 2012 or earlier in LabWindows/CVI 2013 before you can debug them.
• You cannot debug EXEs and DLLs built in LabWindows/CVI 2013 in LabWindows/CVI 2012 or earlier.
• Displaying extended data in the Variables and Call Stack window is available only when a program stops gracefully, for example, as a result of a breakpoint or when stepping through code. Extended data is unavailable in the following instances:
  
  • If the program breaks as a result of an exception
  • If you manually break execution, for example, by pressing the Stop button
    
• Expressions in the Watch window do not update continuously while a program is running.
• You can no longer choose scope in the Watch window. All variables and expressions in the Watch window are evaluated in the current context.
• Watch expressions that you save in LabWindows/CVI 2013 cannot be loaded by LabWindows/CVI 2012 or earlier.
• Some C99 features are available in C89.
• When debugging a real-time application via LabVIEW, LabWindows/CVI does not stop listening when the VI is unloaded. You must either Disconnect or Abort and reboot.
• When graphs scale, they will always scale to the thickness of their line plots. In previous versions of LabWindows/CVI, only plots whose thickness was greater than 1 scaled up or down.
• LabWindows/CVI no longer links to gpibstub.obj or vxistub.obj.
• To use the ExportStyle method in 3DGraphCtrl.fp, you must specify the directories to which you want to export files. Refer to KB 67L8L0QW for more information about using the ExportStyle method.
• LabWindows/CVI 2013 includes updated bracket and indentation styles. You can continue using bracket and indent styles available in previous versions of LabWindows/CVI by selecting the Use CVI legacy formatting option in the Editor Preferences dialog box. Some of the legacy formatting options map to the updated styles except for the following combinations:
  
  • Function brackets set to uneven, left; statement brackets set to uneven, right
  • Function brackets set to uneven, left; statement brackets set to flush, left
  • Function brackets set to uneven, left; statement brackets set to flush, right
  • Function brackets set to uneven, right; statement brackets set to uneven, left
  • Function brackets set to uneven, right; statement brackets set to flush, left
  • Function brackets set to uneven, right; statement brackets set to flush, right
  • Function brackets set to flush, left; statement brackets set to uneven right
  • Function brackets set to flush, left; statement brackets set to flush right
  • Function brackets set to flush, right; statement brackets set to uneven, left
  • Function brackets set to flush, right; statement brackets set to uneven, right
  • Function brackets set to flush, right; statement brackets set to flush, left
    
  
  
  Note that if you select a legacy formatting option, batch auto indent support (selecting Edit»Format File and Edit»Format Selection), is unavailable.
• The LabWindows/CVI Help no longer includes a Font button for increasing or decreasing the font size in the help file. Refer to KB 696A8AOA for more information.
• The Options»Generate Visual Basic Include menu item is no longer available.
• LabWindows/CVI 2013 now returns 2 as the size of variables of type wchar_t, which is consistent with the ANSI C specification. You must recompile existing code in LabWindows/CVI 2013 to see the change in behavior.
• LabWindows/CVI 2012 returned certain compiler errors that are now returned as warnings. Refer to KB 6A9GOOQW for more information.
• LabWindows/CVI 2012 returned certain compiler errors that are no longer errors. Refer to KB 6A9GO5QW for more information.
• Using the token-pasting operator (##) might return compiler errors that were not returned in LabWindows/CVI 2012.
• The Conservative and Aggressive levels of unitialized local variables detection are now combined into one compiler warning. You might notice more unitialized local variables warnings because LabWindows/CVI now flags all variables that may or may not have values assigned to them. This behavior more closely matches the Aggressive level for the Uninitialized local variables detection option in previous versions of LabWindows/CVI.
• You must enable the Include project files in Interactive window or Include loaded instrument drivers in Interactive window options if you run code in a function panel or in the Interactive Execution window that has dependencies on other files in the project or on a loaded instrument driver.
• You cannot view the values of #define macros when you are debugging.
• You cannot specify a .c file as the module to load to the LoadExternalModule and LoadExternalModuleEx functions.
• The Up Call Stack menu item moves toward the callee. The Down Call Stack menu item moves toward the caller. In previous versions of LabWindows/CVI, the Up Call Stack menu item moved toward the caller, while the Down Call Stack menu moved toward the callee.
• You can separate multiple compiler defines using a comma and a space.
• The keyword __FUNCTION__ behaves as a compiler intrinsic variable. LabWindows/CVI does not convert __FUNCTION__ during preprocessing.
• LabWindows/CVI displays rounded values instead of actual values for floating point numbers in data tooltips and Watch, Variables and Call Stack, Graphical Array View, and Array Display windows.
  

Behavior Changes Introduced in LabWindows/CVI 2012

• The Physical Memory Access functions, located in the Utility Library, are deprecated. Refer to KB 5QCCQSQW for more information.
• If your program includes any Port IO functions, located in the Utility Library, the program will require administrator privileges to run. Refer to KB 5Q5FO1QW for more information.
• The LabWindows/CVI low-level support driver can be loaded only by applications running with administrator privileges on 32-bit systems. Refer to KB 5Q5FJ4QW for more information.
• You can no longer create a reduced-size distribution that includes the low-level support driver. If your application uses the low-level support driver, you must include the full LabWindows/CVI Runtime Engine in your installer. To include the full runtime engine in your installer, complete the following:
  
  • Select the NI LabWindows/CVI Shared Runtime Engine item in the Drivers & Components tab of the Edit Installer dialog box.
  • Ensure that you deselect the Install the LabWindows/CVI Shared Runtime Engine in the application directory option in the Advanced tab of the Edit Installer dialog box.
    
  Refer to KB 5R6A4SQW for more information.
• The GetFontTypefaceName function, when used on VAL_DIALOG_FONT or VAL_DIALOG_META_FONT, now returns the actual typeface of the dialog font on your system, rather than the substitute for that font that Windows uses.
• LabWindows/CVI 2013 supports the Perforce SCC Plug-in (P4SCC) 2006.1 and later.
• For projects you save in LabWindows/CVI 2013, LabWindows/CVI attempts to resolve paths that were previously saved as absolute paths to be relative to the project. You can override this behavior by specifying the following options in the .prj file:
  
  For a target file, specify the following in the [Create Executable] section of the .prj file:
  Executable File_Configuration Force Path Absolute = True
  
  where _Configuration is the configuration of your target, such as Debug, Release, or Debug64.
  
  For a file in the project list, specify the following in the [File nnnn] section of the .prj file, where nnnn is the index of the file in the project list:
  Path Force Path Absolute = True
• You can call .NET Library functions from multiple threads simultaneously without getting blocked.
• 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 2010 SP1, 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 2010 SP1 includes the GaussHypergeometric function, which you should use instead of the GaussHG function.
  

Behavior Changes Introduced in LabWindows/CVI 2010

• To specify multiple compiler defines, separate each compiler define using only a space. If you separate each one with a comma and a space, LabWindows/CVI displays an error.
• 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.
• NI 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. NI recommends that you view the latest version of this documentation at www.msdn.com. For more information, visit ni.com.
  

Behavior Changes Introduced in LabWindows/CVI 2009

• 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 2015. You can find installed files in the CVI2015 folder in the various locations where LabWindows/CVI installs files. The registry keys corresponding to this version of LabWindows/CVI are located in CVI\15.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.
  

Behavior Changes Introduced in LabWindows/CVI 9.0 and 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

• 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.
• 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.
• 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, NI recommends using the CNVBufferedWriter connection.
• During a read operation, the Network Variable Library flushes all network variable connections in your program, including data in writer connections, for better performance.
• Registering ActiveX Servers—When you build ActiveX servers in LabWindows/CVI 8.1.1 and later on Windows XP and later, the ActiveX servers are registered in your user profile. This registration is not visible to other users on your system. On versions of Windows prior to Windows XP, 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 and later.
• 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.
    

Known Issues

You can access the issues fixed online. Visit LabWindows/CVI 2020 Bug Fixes for an up-to-date list of issues fixed.

Accessing the Help

Select Help»Find Examples from LabWindows/CVI to launch the NI Example Finder. LabWindows/CVI examples are located in the Users\Public\Public Documents\National Instruments\CVI2020\samples directory. You can modify an example program to fit an application, or you can copy and paste from one or more examples into a program that you create.

Automating the Installation of NI Products

If the NI product you are installing uses Microsoft .NET 4.6.2, the .NET installer may run before any NI software installs and may require a reboot before the installation of NI software begins. To avoid a .NET reboot, install .NET 4.6.2 separately before you install NI software.

Microsoft Windows 11 is the latest version of the Windows operating system and features significant changes compared to previous versions. For more information about NI support for Windows 11, visit ni.com/windows11.

Using NI Software with Microsoft Windows 10

When you install NI software on Microsoft Windows 8.1, you will notice a few additional tiles in the Apps view, including shortcuts to NI application software products such as NI LabVIEW, Measurement & Automation Explorer (NI MAX), and NI Launcher. For more information about NI support for Windows 8.1, visit ni.com/windows8.

LabWindows/CVI Drops Support for Windows 7 (32- and 64-Bit), Windows Server 2008 R2, and All 32-Bit Windows Operating Systems in 2021

NI Software will drop support for Phar Lap ETS Real-Time Operating System starting in 2022. Versions of this product that ship after May 1, 2022, may not install or execute correctly on this operating system. For high-level information on the support roadmap for Phar Lap and its replacement, NI Linux Real-Time, visit ni.com/r/xf35k1. To find out what hardware is supported on PXI controllers running NI Linux Real-Time, visit ni.com/r/b7g5wi.

---

Legal Information

© 1993–2020 National Instruments Corporation. All rights reserved.

NI respects the intellectual property of others, and we ask our users to do the same. NI software is protected by copyright and other intellectual property laws. Where NI software may be used to reproduce software or other materials belonging to others, you may use NI software only to reproduce materials that you may reproduce in accordance with the terms of any applicable license or other legal restriction.

You can find end-user license agreements (EULAs) and third-party legal notices in the following locations after installation:

• Notices are located in the \_Legal Information and directories.
• EULAs are located in the \Shared\MDF\Legal\license directory.
• Review \_Legal Information.txt for information on including legal information in installers built with NI products.
  

If you are an agency, department, or other entity of the United States Government ("Government"), the use, duplication, reproduction, release, modification, disclosure or transfer of the technical data included in this manual is governed by the Restricted Rights provisions under Federal Acquisition Regulation 52.227-14 for civilian agencies and Defense Federal Acquisition Regulation Supplement Section 252.227-7014 and 252.227-7015 for military agencies.

Content from the IVI specifications reproduced with permission from the IVI Foundation.

Trademarks

Patents

374674F-01