Ver 3.4.7.3 - 04/03/2013 - LV-Link3 Readme File PREREQUISITE -----------The 32 bit release of LV-Link3 is built on LabVIEW 8.5.1.

The supplied VIs will also run on later versions of LabVIEW but not earlier ones. The 64 bit release of LV-Link3 is built on LabVIEW 2009. This is the first versi on of LabVIEW with 64 bit support. The supplied VIs will also run on later 64 bi t versions of LabVIEW. If you get warning messages with the supplied VIs because you are running a late r version of LabVIEW, you can perform a Mass Compile. To do this, select Tools > Advanced -> Mass Compile, go to the user.lib\LV-Link3 folder and click the "Cu rrent Folder" button. This will compile all of the LV-Link VI's and convert the m to the later version of LabVIEW. Once updated to a later LabVIEW version, thes e VIs will no longer be compatible with older version of LabVIEW. INSTALLATION -----------Before installing LV-Link3, do the following: o Ensure that you have installed the latest software for your device from the latest Data Acquisition OMNI CD. o Ensure that you have installed LabVIEW 8.5.1 or greater for 32 bits Windows or LabVIEW 2009 for 64 bit Windows. o. e may vious imply While most changes are backwards compatible (unless otherwise noted), ther be incompatibilities we did not anticipate. If you are updating from a pre version of LV-Link3 and you wish to keep a copy of the previous content, s copy the entire LV-Link3 directory to another location.

This version of LV-Link installs in the directory "LabVIEW ## \ user.lib \ LV-Li nk3" where "##" is the version of LabVIEW you have (such as 8.5, 2010, etc). The installation directory name "LV-Link3" differentiates it from previous versions of LV-Link and thus allows it to coexist with those previous version (if they e xist). Examples and VIs are likewise named with the "Dt" prefix to avoid name co llisions with previous versions of LV-Link. TECHNICAL SUPPORT ----------------If you have difficulty using LV-Link, Data Translation s Technical Support Departm ent is available to provide technical assistance. To request technical support, go to our web site at http://www.datatranslation.c om and click on the Support link. When requesting technical support, be prepared to provide the foll owing information: Your product serial number The hardware/software product you need help on The version of the OMNI CD you are using

Your contract number, if applicable If you are located outside the USA, contact your local distributor; see our web site (www.datatranslation.com) for the name and telephone number of your nearest distributor. VERSION INFORMATION ------------------3.4.7.3 * Corrected a bug in the help documentation regarding the sample rate setting. T he sample rate is a per-subsystem value, not a per-channel value. * Packaged with OpenLayers 7.3 installer. 3.3.7.2 * LvLink 3.3.0.0 packaged with OpenLayers 7.2 installer. New Feature * Data filtering selection has been added to thermocouple related VIs. 3.2.7.1 * LvLink version 3.2.0.0 packaged with OpenLayers 7.1 installer. 3.2.0.0 New feature * Thermocouple support has been added. Use "DtOLSetChanTermocoupleOptions.vi" to set the type of thermocouple used on a per-channel basis. See "DtAinThermocoupl eContinuous.vi" for a sample program that continuously reads a thermocouple from a DT9828. 3.1.0.1 Bug fixed * Aborting an acquisition using DtOLStop.vi with parameter "Finish Buffer" = "Fa lse" did not always work correctly. A new error (LveAborted, error code 1080) ha s been added and is returned by an aborted read operation. It is recommended tha t you programmatically check for this source string/error code and handle it app ropriately to ensure that your application behaves as expected when an operation is aborted. New feature * True 32 bit DAC support added. 3.1.0.0 Bug fixed * Allow VIs to easily restart acquisition within a VI after they have been progr ammatically stopped. New feature * Triggered Scan support has been added. See "DtOLTrigger.vi". This new VI lets you set specify the Triggered Scan mode parameters. Example program "DtAinTrigge redScan.vi" shows a simple use of this feature. * Reference trigger support has been added. See "DtOLTrigger.vi". This new VI le ts you set the reference trigger parameters. Example program "DtAinReferenceTrig .vi" shows a simple use of this feature. * Strain support has been added. See "DtOLGetTEDS.vi" and "DtOLSetChanSensor.vi" . These VIs let you retrieve TEDS information from strain related hardware and s et strain data acquisition parameters on boards that support strain measurement.

Example programs "DtAinBridgeSensorContinuousTEDS.vi" and "DtAinStrainContinuou s.vi" show simple examples of strain measurement. * 16 and 32 bit unsigned integer raw data read interface has been added. This in terface is identical to the existing 64 bit "double" interface but uses less mem ory when raw data is desired. See "DtOLRead.vi". * Multi-channel / Single=Sample read is now directly supported in "DtOLRead.vi". This is just a variant of Multi-Channel / Multi-sample read. * Update "DtOLGetBoard.vi" to also return the serial number of a given board. * Added offset and shunt calibration VIs for strain gages and full-bridge based sensors. These are implemented as a user interface and a worker VI pair; the lat ter of which may easily be copied and modified by the user and used in an end us er application. No longer supported Interface functions "Lvi Read I32Data1D.vi", "Lvi Read I32Data2D.vi", "Lvi Read I32Data Pt.vi", "Lvi Write I32Data1D.vi" and "Lvi Write I32DataPt.vi" are no lon ger supported. These have been replaced by "U32" versions. Raw data is now alway s returned as unsigned integers. 3.0.0.2 Bug fixed - When streaming reads in finite mode, the incoming buffers were not f reed correctly leading to a memory leak. 3.0.0.1 Bug fixed - When using an OpenLayers compliant acquisition boards that does not support streaming (Single Value only), a "Not Supporeted" error was erroneously generated. Bug fixed - Counters and digital I/O subsystems did not properly process the ele ment / port number. This caused a failure to handle more than one element / port at a time. 3.0.0.0 First release of LV-Link3 KNOWN ISSUES ------------1- If a given Task consisting of a device and subsystem combination is opened m ore than once at the same time, LvLink will fail to detect this conflict. The la st such Task created will be the legitimate Task; any preceeding Tasks with the device and subsystem combination will be invalidated. Invalidated Tasks may yiel d runtime errors or cause invalid results depending on its actions at the time o f the conflict.