NI Vision Acquisition Software 7.1.1 for LabVIEW7.1.1 Win32Eng LV7.1.1视觉采集软件VAS7.1.1版 IMAQ for IEEE 1394 V2.0.1
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
NI Vision Acquisition Software 7.1.1 for LabVIEW7.1.1 Win32Eng LV7.1.1视觉采集软件VAS7.1.1版 IMAQ for IEEE 1394 V2.0.1
美国国家仪器视觉采集软件NI Vision Acquisition Software 7.1.1版本，视觉论坛visionbbs.com珍藏版。在8.0版以前，VAS不是叫VAS，而是叫IMAQ1394，即以前版本，是只对1394等老旧协议有效的。不支持最新的Gige Vision/USB3 VISION/等协议，所以请考虑使用1394相机。NI不再提供老旧版本的下载服务或是SSP服务才可以下载，本论坛会收取一定的费用用于论坛日常维护。
VAS是工业相机专用驱动程序，VAS7.1.1版本针对LabVIEW7.1.1版本(LV7.1版可支持）。本论坛提供LabVIEW7.1.1的下载。另外如需要VDM7.1.1视觉开发包的，可在本论坛搜索下载。
RAR
文件大小: 177918866 字节 (169.68 MB)
修改日期: 2016-05-06 17:36
MD5: 11404a6b46956d1783151577d7c3c6ef
SHA1: 769d481be43a89c8b2c56d493c7587841cec36d5
SHA256: 136e3c142032f133dcb29e64b9f14442ac08a68ff494287afb68e18c19bb0a16
CRC32: 21ce516e
ZIP
文件大小: 189698904 字节 (180.91 MB)
修改日期: 2022-06-24 10:49
MD5: f0b5bd0eb8d8046f7988a879c9686321
SHA1: b451d205b33570488eb8fe1efaceff8cc98e3188
SHA256: e885e626d5352275871c3554747fd0a7617f3aa2424201cc895bcf63ea2dbba1
CRC32: b99757bb
百度网盘下载：
链接: 请购买主题附件下载查看
提取码: 请购买主题附件下载查看
压缩包需要解压密码，请关注论坛顶上微信公众号，回复“密码”获取
All rights reserved.
GENERALINFORMATION
1) Always install your NI-IMAQ for IEEE 1394 Cameras software beforeconnecting your camera to the IEEE 1394 adapter.
2) This version of the driver supports LabVIEW 7.0 and higher,Windows 2000/XP.
3) NI-IMAQ for 1394 Directory Structure
The directory structure under the NI-IMAQ installationdirectory is the following:
DATANI-IMAQ for IEEE 1394 camera files
DOCSNI-IMAQ for IEEE 1394 Cameras online reference manuals
EXAMPLESC examples for Microsoft Visual C++VB examples for Microsoft Visual BasicdotNET examples for Microsoft Visual Basic .NET
INCLUDEHeader files for compiling Cprograms that control your IEEE 1394 camera
LIB Import libraries for Microsoft Visual C++
DOTNET.NET assemblies for MicrosoftVisual Studio .NET 2003
4) This distribution includes a new component, NI-IMAQ I/O, which hasreplaced the former NI-1450 Series Support component.NI-IMAQ I/O is compatible with the NI-1450Series compact vision system.
5) NI-IMAQ I/O adds support for the NI 8254R.
6) The LabVIEW examples are located in the standard EXAMPLES directory of LabVIEW.
7) The Measurement Studio and LabWindows/CVI examples are located inthe standard SAMPLES directory of LabWindows/CVI.
SWITCHING DRIVERS
Measurement &Automation Explorer (MAX) enumerates other IEEE 1394 camera drivers forWindows. All IEEE 1394 digital cameras show up under the NI-IMAQ IEEE 1394Devices tree. Cameras using the NI-IMAQ for IEEE 1394 Cameras driver havefull configuration and acquisition functionality. Cameras not using the NI-IMAQfor IEEE 1394 Cameras driver do not work with National Instruments software.Inactive cameras have a camera icon with a red cross. Perform the followingsteps to select a different IEEE 1394 driver:
1) Right-click on the desired camera in MAX and select Driverfrom the pop-up menu.
2) Select a driver from the list of available compatible drivers.
3) A warning dialog message appears. Read the message and click Yesto proceed.
4) The camera driver is updated. MAX also updates to reflect thechanges.
UPGRADE CONSIDERATIONS
Wherever possible,NI-IMAQ for IEEE 1394 Cameras 2.0 is designed to provide the same functionalityas NI-IMAQ for IEEE 1394 Cameras 1.x. In some cases, NI knowinglychanged functionality to improve overall performance, stability, and userexperience. These changes are explained below.
Driver:1. In previous version of the driver, attributes were verified duringthe Set Attribute function. Setting an invalid value resulted in an immediateerror from the set function. With NI-IMAQ for IEEE 1394 Cameras 2.0, allattributes are verified and set during configuration. Setting camera attributesduring an active acquisition validates the attribute and sets the cameraregister, as required. Setting acquisition parameters during an activeacquisition returns the following error: “Non-writable attribute.”
2. In the documentation for previous versions of the driver, NIrecommended that you configure one buffer for continuous acquisitions. Althoughthis works in many cases, some frames may be lost during heavy CPU usage. WithNI-IMAQ for IEEE 1394 Cameras 2.0, NI recommends that you configure N + 2buffers for continuous acquisitions, where N is the number ofsimultaneously acquiring cameras.
LabVIEW Specific:1. The sessionwire changed to an IMAQ1394 generic refnum. Most applications are not affectedby this change. However, applications using the not a refnum constant maybe affected. With NI-IMAQ for IEEE 1394 Cameras 1.x, you could use the nota refnum constant to initialize a shift register, or you could test whetherthe session is valid with a Boolean operator. Any existing code loaded withNI-IMAQ for IEEE 1394 Cameras 2.0 results in error messages and broken wires.The typical error message reads: “Insane TypeID ‘20’ at DTHP+1034.”
NI recommends thatyou replace the not a refnum constant with an IMAQ1394 constant. To verify that thesession is valid, use the not a refnum comparison primitive.
Using VIs (left) and property nodes (right) to setcamera attributes
KNOWN ISSUES
Driver:1. Consult your IEEE 1394 adapter documentation for instructions onhow to correctly install and power on your adapter.
2. When doing a snap or a sequence acquisition, some cameras producea poorly exposed frame as the first image. To correct this issue, enable the IgnoreFirst Frame checkbox in MAX.
3. Plugging a device into an IEEE 1394 bus causes a bus reset. Ifthere are any ongoing acquisitions, the acquisition continues, but it ispossible that a frame could be dropped. If you have an application in which itis important to get every frame, you should protect against devices beingplugged into the bus.
Windows OSSpecific issues:1. When switching drivers, you may find that the camera does notalways appear in the MAX configuration or in your Device Manager. To correctthis, disconnect the IEEE 1394 camera from your IEEE 1394 adapter and reconnectit. You can also press the F5 button to refresh.
LabVIEW RTSpecific Issues:1. MAX does not support automatic refresh for remote systems whencameras are added and removed from the remote device. Press F5 to refresh MAXto get the current configuration.
NI-IMAQ I/OSpecific Issues:1. When you use LabVIEW RT Application Builder to create anexecutable on an NI CVS-1450 Series device, create the executable in thedefault directory for LabVIEW RT startup applications (c:\ni-rt\startup). Ifyou do not create the executable in the default directory, the applicationcannot connect to the FPGA code.
2. If you need to call multiple instances of “Open FPGA VIReference”, National Instruments recommends running them sequentially and notsimultaneously.
3. When creating LabVIEW FPGA applications for IMAQ I/O Devices, thedigital inputs ISO_POWER_PRESENT and USER_DIP are low true signals.Also, digital outputs should be treated asoutputs only.Trying to use an output onyour device as a digital output and a digital input in your LabVIEW FPGAdiagram will result in a compilation error.
4. Configuring the shutdown states on an IMAQ I/O device while thedefault personality is running on the FPGA can affect the value of the isolatedoutput lines.Drive the isolated outputswith the value you expect after configuring shutdown states.
5. The LabVIEW invoke node--which is used in many of the IMAQ Vision7.0 examples--may not work and can cause a crash in the host LabVIEW. If youwould like to run IMAQ Vision 7.0 examples on your NI CVS-1450 Series device,modify the code so that it does not use the invoke node.
USINGMULTIPLE CAMERAS
The IIDC1394-based Digital Camera Specification version 1.30 allows up to 16cameras and one controller to exist on an IEEE 1394 bus at one time. Multiplecameras connected to a single adapter share the same IEEE 1394 bus and theavailable bandwidth for that bus. To simultaneously acquire images frommultiple cameras, select a video mode for each camera so that the totalbandwidth does not exceed the bandwidth capability of the bus.
NOTE: NI-IMAQ for IEEE 1394 Cameras returns an InsufficientResources error if you perform an acquisition that requires more bandwidththan is available on the bus.
To use multiplecameras simultaneously at full speed, connect each camera to a separate IEEE1394 adapter. You cannot simultaneously acquire images at maximum bandwidthfrom multiple cameras when all cameras are connected to the same bus.
页:
[1]