The driver supports devices manufactured by DataTranslation, which are Ethernet (LXI) versions.
At the time of writing the available versions are:
Please configure the devices with the relevant tools, before connecting this driver.
Typically you can use the Eureka LXI Instrument Discovery tool from DataTranslation to locate the IP address of the device, and then login to the devices web page at that address to set its configuration.
This will allow you to assign the input types to the relevant channels. Please note if you enable a scan to check the values being read, please remember to stop it before setting up this driver.
Important constraints:
After the device(s) have been calibrated and setup as necessary, Niagara can be setup to poll for values from the device(s).
As with other Niagara drivers the devices driver has an associated .jar file named dataTranslation.jar. Identical to other drivers this module needs to be installed in the installation workbench used to manipulate the driver, and the station that is to run the driver.
When the module is opened in the palette, you will see a DataTranslationNetwork item. This should be added under the drivers section of the station that it is to run on.
If you get an error when attempting to do this, check that both the station and workbench have been restarted since installing the module.
To add a device to the network, click on the DataTranslationNetwork that has been added under the drivers section of the station, and use the new button.
During the inclusion of a new device, to the network you need to know its IP Address and if you have modified it then the port number. The port number is usually the one that can be connected to via telnet.
Firmware V2.2.3.1 and later has a new password function. The password entry can be found under the devices communicator, if the password field is saved as empty the default password will be applied.
After the device has been added you will see it has these 4 fields under it:
Once successful communications have been established to the device, these 4 slots will become populated with the relevant information from the device and if necessary the device status will be set to Ok.
Once the Model and Serial information have been received they will be kept between reboots, so that if the communications cannot be restored these fields may help to identify the device that is not responding.
After the device communications have started and the 4 fields populated, you can discover the points as would be done in other Niagara drivers.
If you wish to force the driver to check before the next ping interval you can use the Action named Ping, on the device and it will then re-attempt to check communications with the device.
It is recommended to always use discovery to bring in the points from the device
Helpful hint: To bring in several points from a device, select the top one and then while holding shift click down to the last one to select multiple entries, before dragging them into the database.
If they are non-sequential you could hold down Ctrl while selecting the different points before dragging them into the database.
It is not expected that in normal use the points should need to be edited, however this may be helpful should it be deemed necessary.
Each point has the 4 additional settings that can be set:
This defines the input type of the channel:
Depending on the device, and the boards added to the unit will determine which input types are supported by the relevant channel.
If the point type T Couple has been selected, this option is used to set the Thermo Couple Type in relation to this input type. Please see dataTranslations documentation for further information.
If your point type is not a T Couple type, please ensure that this is set to "Def"
Just like the thermo couple type, if you have a Rtd input type this should be set appropriately to the relevant sensor type that has been connected.
If Rtd type is not relevant please ensure that this is set to "Def"
Simply specifies the channel number that the data is to come from.
Discovery is recommended as the preferred option to bring in points, this is because when the driver requests information it will configure the channels as setup based on the fields above.
If you modify the above settings against a point, this will reconfigure that channel in the device to the settings given.