石鑫华视觉
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 8.2.1 Win32Eng LabVIEW8.2.1英文专业版下载
美国国家仪器LabVIEW 8.2.1版，英文，Windows系统32位版。石鑫华视觉珍藏。
链接: 请购买附件下载查看
提取码:请购买主题查看
NI LabVIEW 8.2.1 Win32Eng LabVIEW8.2.1英文专业版下载
http://pcmv.cn/thread-484-1-1.html?fromuid=9
(出处: 机器视觉论坛)
LabVIEW 8.2.1 Readme for Windows
Supported Platforms
Installing LabVIEW 8.2.1
Installing Another Language Version
Installing LabVIEW Silently
Licensing
Known IssuesInstallation
If you uninstall LabVIEW 8.2.1 and a previous version of LabVIEW remains on the system, the previous version of LabVIEW might try to repair itself the next time you open it. The repair process might remove any patches you installed for that version of LabVIEW. Make sure to reinstall any patches you have on the system after the repair finishes. Refer to the KnowledgeBase at ni.com for more information about this issue.
If you have Windows XP Service Pack 2 or Windows Vista installed, a Security Alert dialog box appears when you launch LabVIEW or the NI Example Finder for the first time. If you select the Keep blocking this program option, the LabVIEW VI Server, LabVIEW Web Server, and any server written in LabVIEW cannot accept incoming connections from a remote computer. Select the Unblock this program, despite the security risk option to configure your computer to launch LabVIEW without any changes in functionality. Refer to the KnowledgeBase at ni.com for more information about correcting this problem.
VIs, Express VIs, and Functions
The links to subVIs from the ni.com for more information about correcting this problem.
If you create a new, untitled VI while using the Storage VIs, the numbering of the untitled VI might be inconsistent.
The Storage VIs do not support the extended-precision, floating-point data type. If you wire this data type to a Storage VI, LabVIEW returns a compiler error when you run the VI.
The Delete Data VI does not work with .tdm file, the size of the file does not change, but you cannot access the data you try to delete.
The Sound File Read VI uses large amounts of memory to read an entire .wav file piece by piece rather than in one large file.
The Array instance of the Sound Output Set Volume VI does not use the volume input to set the volume on a per-channel basis. Instead, this VI uses the first element of the volume input as the sound level for all channels.
The Read From Measurement File Express VI returns an error if you call it on the same file multiple times, which makes using this Express VI in a subVI problematic.
If the Database Connectivity Toolkit is installed, you cannot place the Database Variant To Data function on the block diagram. Refer to the KnowledgeBase at x7FFFFFFF as an unsigned, 32-bit integer to a Formula Node, LabVIEW coerces the value to 0.
If you register an ActiveX event, you must unregister the event explicitly. Otherwise, memory leaks might occur because the ActiveX control does not know that the client has disconnected.
When you select Tools»Compare»Compare VIs and use the Compare VIs dialog box, LabVIEW does not display differences between values of cluster constants.
Environment
A blue field does not surround the palette icons for Express VIs from LabVIEW 7.x and earlier that you open in LabVIEW 8.2.1. For example, if you use a LabVIEW 7.1 toolkit in LabVIEW 8.2.1, a blue field does not surround the icons for Express VIs on the toolkit palette. You must mass compile the Express VIs to display the blue field around the icons.
If you define a custom run-time menu for a control and you save that run-time menu with the control, you cannot localize the run-time menu. As a workaround, you can save the custom run-time menu to an external file and point the control to that file, or you can build the run-time menu dynamically with localized strings.
LabVIEW does not correctly hide subpalette menus that belong to locked project libraries.
When you print the VI Hierarchy window, LabVIEW does not print the VI labels.
LabVIEW MathScript
If you select File»Save for Previous Version and save a VI that contains a MathScript Node for LabVIEW 8.0, the VI is broken when you load it in LabVIEW 8.0. To correct this problem, load the VI in LabVIEW 8.0 and then modify the script in the MathScript Node. For example, add and remove a space. Then click the block diagram outside of the MathScript Node. When you click the Run button, the VI runs correctly.
MathScript does not support string inputs that use LaTeX syntax.
If you mass compile VIs last saved in a previous version of LabVIEW and the VIs contain MathScript Nodes, LabVIEW might return error messages, but LabVIEW compiles and saves the VIs correctly.
If a LabVIEW MathScript contains a gca, get, or ni.com for more information about correcting this problem.
If you rename a parent class while any child classes are in memory, LabVIEW does not record the mutation history of the class correctly. LabVIEW resets any flattened data or non-default data in memory to the default value. To avoid losing data, rename a class only when it is not in memory. Refer to the KnowledgeBase at http protocol with the DataSocket VI and functions in LabVIEW-built shared libraries.
You cannot use front panel DataSocket data binding with fixed-sized arrays.
If you use the DataSocket Server Manager to create a Boolean object, the DataSocket Server Manager converts the Boolean object to numeric data in the configuration file.
Shared Variables
You can read from and write to private single-process shared variables.
If you open a VI that contains a shared variable from a zip file, LabVIEW displays a file dialog box indicating that it cannot find the file for the global VI associated with the shared variable. Click the Cancel button to recreate the global VI.
LabVIEW fails to deploy all shared variables in a library if one shared variable has an invalid binding. To correct this problem, either delete the shared variable that has an invalid binding or unbind the shared variable.
If you select File»Save for Previous Version and save a VI that contains a Shared Variable node for LabVIEW 8.0, the VI might not return correct results. If you save the VI for LabVIEW 8.0.1, the VI returns correct results. Refer to the KnowledgeBase at ni.com for more information about using remote panel servers with built applications.
If you have more than one Ethernet card, Logos is automatically assigned to the primary Ethernet card. To assign Logos to a different Ethernet card, switch the Ethernet cards.
The maximum size of datalog files is 2 GB.
.NET type definitions do not correctly update when you change the related assembly.
If you use the Edit Items page of the Enum Properties dialog box to edit an enumerated type control that contains a large amount of items, LabVIEW 8.2.1 might perform slower than LabVIEW 8.0. To avoid this problem, use the Labeling tool to add or edit items directly from the front panel. Refer to the Adding Items to Enumerated Type Controls topic in the LabVIEW Help for more information about adding items to enumerated type controls.
Windows Vista
For compatibility reasons, the LabVIEW installation process enables write permissions for the -start and net start and .tdm and .tdms file into the new .tdm file format.
| Functions | |
| 423GHDQ4 | Fixed an issue where LabVIEW crashes when compiling a VI that uses a Bundle function to bundle a cluster and an element of the same cluster. |
| 41SEH2R0 | Fixed an issue with the Unbundle By Name function where the outputs shift and return the wrong elements if you expand the input cluster and add an element to the beginning of the cluster. |
| 40LD2E1W | Fixed an issue where a broken wire incorrectly becomes unbroken when you wire an array with an incorrect number of dimensions to the Replace Array Subset function and then perform an undo operation. |
| 41HDO7D5 | Fixed an issue with the Delete function where LabVIEW does not display a dialog box that asks you to confirm the delete operation when the confirm input is TRUE. |
| 406GLS7U | Fixed an issue where the File/Directory Info function returns an incorrect size for files larger than 4 GB. |
| 400J6DAB | Fixed an issue where the TDM Streaming functions leak small amounts of memory when you use the functions to read from and write to a file simultaneously. |
| 40LAG76O | Fixed an issue where the TDMS Set Properties function does not accept the subarray data type. |
| 4498F7I8 | Fixed an issue with the TDMS Get Properties function where the NI_ChannelLength property returns an incorrect result for channels with more than eight billion values. |
| 3ZRAECAF | Fixed an issue where LabVIEW might crash when you wire array data to the channel name(s) in input of the TDMS Write function or the TDMS Read function. |
| 44A82UN3 | Fixed an issue where the TDMS Write function incorrectly handles values in subarrays. |
| 44E2K100 | Fixed an issue where LabVIEW might crash when you wire cluster data from the error out output of any VI or function to the quit? input of the Quit LabVIEW function, delete the error cluster wire, right-click the quit? input, and then select Create»Constant from the shortcut menu. |
| 42934191 | Fixed an issue with the Database Connectivity Toolkit in localized versions of LabVIEW where you cannot place the Database Variant To Data function on the block diagram. |
| Front Panel Objects | |
| 40A8TF70 | Fixed an issue where LabVIEW crashes when you click a front panel table control or indicator when the VI is running. |
| 3YT8QDTC | Fixed an issue where LabVIEW hangs or crashes when you open a VI that contains a graph with thousands of cursors. |
| 41PGKSK | Fixed an issue where LabVIEW crashes when you open a reentrant VI that contains a graph with cursors. |
| 4298GDCY | Fixed an issue where LabVIEW crashes when you rename a plot on a waveform graph if dynamic data is wired to the graph, the graph contains no data, and the graph is configured to not ignore attributes. |
| 43SAIR2A | Fixed an issue where LabVIEW crashes when you run a VI that contains a mixed signal graph with a multi-plot cursor. |
| 43SAIR2A | Fixed an issue where LabVIEW crashes when you select File»Save for Previous Version to save a VI that contains a graph with a cursor for a previous version of LabVIEW and then you open the VI in the previous version of LabVIEW. |
| 40FC9LTX | Fixed an issue where a floating-point numeric control cannot show zero digits of precision. |
| 41ICLC00 | Fixed an issue where the File»Apply Changes menu item in the Control Editor window might fail for nested type definitions. |
| 40AD38YR | Fixed an issue where a shortcut menu item on a subcomponent of a type definition operates on the subcomponent instead of the top-level type definition. |
| 431GRU7J | Fixed an issue with tree controls where when you press the <Ctrl> key to copy an item while you click and drag the item within the tree control, the data value returned by the tree control output differs from the data value returned by the Value property. |
| 40E8RFI8 | Fixed an issue where LabVIEW does not draw the plot correctly when you graph a set of data that includes values of not a number (NaN) instead of a complex result when you use the ^) to raise a negative number to a power. |
| 45T9T528 | Fixed an issue with localized versions of LabVIEW where LabVIEW crashes when reading matrix data from the MathScript Node. |
| LabVIEW Object-Oriented Programming | |
| 4101CU8P | Fixed an issue where LabVIEW crashes when you right-click a folder that contains a LabVIEW class and select Convert to Library from the shortcut menu. |
| 40AA12CS | Fixed an issue where LabVIEW crashes when you rename a dynamic dispatch member VI of a LabVIEW class located in the middle of an inheritance hierarchy. |
| 43JCLR2K | Fixed an issue where LabVIEW crashes when you display the Context Help window and then move the cursor over the wire of a LabVIEW class whose private data contains a VI reference that refers to a VI with a terminal of the same class type. |
| 40O8NJMX | Fixed an issue where a memory leak occurs and LabVIEW might crash when you use the Build Array function to prepend a LabVIEW class object to an array. |
| 3ZP99HN8 | Fixed an issue where LabVIEW hangs when you add a LabVIEW class to a library while the library is open in both the Project Explorer window and the project library window. |
| 40667H1W | Fixed an issue where if you edit the cluster elements in the private data control of a LabVIEW class and you save the class but not all its member VIs, the Bundle and Unbundle functions no longer map to the correct elements of the cluster, and LabVIEW might crash. |
| 3ZAFD6J1 | Fixed an issue where a LabVIEW class that is broken because of a missing VI is not fixed when you remove the missing VI from the LabVIEW class. |
| 42B8NUJ1 | Fixed an issue where the LabVIEW class example .tdms file created by writing a large number of small data segments to the file. |
| 41AGS3AB | Fixed an issue where you cannot append data to a channel in a .llb file extension. You also cannot access a VI in a stand-alone application or shared library by specifying the path to the VI from outside of the application or shared library. |
The System Requirements section on the Advanced page of the Installer Properties dialog box includes the option Windows Vista and later. Use this option if you want to specify that users have Microsoft Windows Vista or a later version to run the installer.
The Create Instrument Driver Project wizard includes a progress bar so you can view the status of the instrument driver project as LabVIEW builds it. You can cancel the operation by clicking the Cancel button.
The default value for the Cache VIs component of the Mass Compile dialog box changed from 5 to 10. Also, caching VIs is enabled by default.
In LabVIEW 8.0 or earlier, the value for the Priority input of a Timed Loop must be a positive integer between 1 and 2,147,480,000. In LabVIEW 8.2.x, the value for the Priority input must be a positive integer between 1 and 65,535.
To create a new VI or project from the LabVIEW MathScript Window, you first must return to the Getting Started window by selecting View»Getting Started Window.
You must use NI Spy 2.3 or later in LabVIEW 8.x. NI Spy 2.4 is available on the National Instruments Device Drivers CD.
You must use the LabVIEW Report Generation Toolkit 1.1.1 or later in LabVIEW 8.2.1. Refer to the National Instruments Web site to access the Upgrade Advisor and order the Report Generation Toolkit 1.1.1 or later.
You must use Measurement Studio 8.0 or later with LabVIEW 8.2.x. Refer to the National Instruments Web site to access the Upgrade Advisor and order Measurement Studio 8.0.
LabVIEW initializes a Shared Variable node the first time you run a VI that contains that node.
In LabVIEW 7.x and earlier, LabVIEW enables debugging automatically for new VIs. If you then make a VI reentrant by selecting File»VI Properties, selecting Execution from the pull-down menu, and placing a checkmark in the Reentrant execution checkbox, LabVIEW automatically removes the checkmark from the Allow debugging checkbox. In LabVIEW 8.x, LabVIEW does not automatically remove the checkmark from the Allow debugging checkbox.
A .NET or ActiveX property that returns a reference to a class outside the current type library cannot be made into a dotted property. When you view the property in the Class Browser window, a blue glyph does not appear next to the property name in the Properties and Methods list.
LabVIEW supports smooth scrolling, or scrolling by pixels, on the front panel and block diagram of a VI.
Select File»Close in a file with unsaved changes to display the Save changes before closing? dialog box. Select File»Close All to display the Save changes and Close All? dialog box.
You can access LabVIEW data files from DIAdem regardless of the format in which you stored those data files.
If you configure source control in LabVIEW, LabVIEW does not report an error when you save a VI to a directory outside the SCC specification.
In LabVIEW 7.x and earlier, if you wire dynamic data to a waveform-based polymorphic VI that has Automatic selected in the polymorphic VI selector, LabVIEW selects the 1-channel instance. In LabVIEW 8.x, LabVIEW selects the N-channel instance. The N-channel instance returns arrays of measurement data instead of a single measurement, so VIs that use a waveform-based polymorphic VI might be broken in LabVIEW 8.x. If you want to process only the first signal in the dynamic data, you must manually select the 1-channel instance in the polymorphic VI selector.
You must use an application reference when you use VI server properties and methods in one application instance, and you want to interact with a different application instance. It is not always obvious that VIs are running in different application instances. For example, each LabVIEW project has its own application instance, and each target within a project has its own application instance. LabVIEW also creates a main application instance, which contains open VIs that are not part of a project and VIs that you did not open from a project. In addition, LabVIEW opens user VIs you place in the labviewproject, and <font face="" "="" style="margin: 0px; padding: 0px; overflow-wrap: break-word;">labviewwizard directories in a private application instance. If you are unsure whether you are interacting with a different application instance, use an application reference.
Documentation Corrections
The LabVIEW Help incorrectly states that you can use the DataSocket VIs and functions to read or write shared variables from Mac and Linux.
The LabVIEW Upgrade Notes refers you to the Fundamentals»Calling Code Written in Text-Based Programming Languages»Concepts»Importing Functions from Shared Library Files topic on the Contents tab of the LabVIEW Help for more information about creating wrappers for shared library files. The path to this topic should be Fundamentals»Calling Code Written in Text-Based Programming Languages»How-To»Importing Functions from a Shared Library File.
The LabVIEW Upgrade Notes refers you to the Fundamentals»Windows Connectivity»Concepts»Web Services book on the Contents tab of the LabVIEW Help for more information about importing Web services. The path to this topic should be Fundamentals»Windows Connectivity»Concepts»Importing Web Services.
In the LabVIEW Upgrade Notes, the TDM Streaming File Viewer VI should be the TDMS File Viewer VI.
The LabVIEW Fundamentals manual and the LabVIEW Quick Reference Card did not change for LabVIEW 8.2.x. Therefore, the content might not reflect changes made in LabVIEW 8.2.x. Refer to the LabVIEW Help for the most updated information.
The LabVIEW Upgrade Notes, the LabVIEW Release Notes, and the Getting Started with LabVIEW manual did not change for LabVIEW 8.2.1. Therefore, the content might not reflect changes made in LabVIEW 8.2.1.
Copyright
Trademarks
Patents