ET24XX Instrument Driver Readme

To rate this driver, go to the ET24XX driver download page on the Instrument Driver Network.

1. Overview

Instrument Driver Technology:  Plug and Play
Supported Language(s):  LabVIEW

Supported Model(s): 2416, 2408, 2404
Model(s) Tested:  2408, 2404
Interface:  Serial
Supported Bus Communication Types: MODBUS
Firmware Revision(s) Tested:  V3.06, V4.11


Certified:  No
NI Supported:  No
Source Code Available:  Yes

Driver Revision:  1.2
Original Release Date:  12/2004
Current Revision Date:  2/2009



2. Required Software

Some software components need to be installed before using this instrument driver. The minimum versions of 
these components are listed below, and can be downloaded from the Download Site.

VISA 3.0

Note: VISA has additional software requirements. For example, unless you are using a serial interface, 
NI-VISA requires that NI-488.2 and/or NI-VXI be installed on your system. Check with VISA help for additional 
support software and hardware requirements.


3. Installation Instructions

LabVIEW:
Instrument drivers should be installed as a subdirectory of the labview\instr.lib. For example, the HP34401A 
instrument driver, which is included with LabVIEW, is installed in the following directory: 

labview\instr.lib\hp34401a

Within this directory you can find the menu files and VI libraries that make up an instrument driver. The 
menu files allow you to view the instrument driver VIs from the Functions palette. The VI libraries contain 
the instrument driver VIs.


4. Using the Instrument Driver

LabVIEW:
To verify communication with your instrument and test a typical programmatic instrument operation, you should 
first open the Getting Started or Example VIs the instrument driver. Look over each of the controls and set 
them appropriately. Generally, with the exception of the address field, the defaults for most controls will 
be sufficient for your first run. You will need to set the instrument resource name appropriately. After 
running the VI, check to see that reasonable data was returned and an error was not reported in the error 
cluster.

After you have verified basic communication with your instrument, you might want to customize instrument 
control for your needs. If your application needs are similar to the Getting Started or Example VI, the 
simplest means of creating a customized VI is to save a copy of the Getting Started or Example VI by 
selecting Save As from the File menu. You can then modify this example to meet your specific needs.

For more details, reference the LabVIEW Help under Help » VI, Function, & How-To Help.


5. Known Issues
1. The "ET24XX Read Processor Utilisation Factor.vi" will not return a valid result for firmware V4.00 and above.

To report issues or provide feedback about this instrument driver, please send an email to instrument.drivers@ni.com.

Using the driver with the 22xx models: 
Although this driver is intended for use only with the 24xx models, a number of VIs are supported or partially supported with the 2204, 2208, and 2216 models.

List of VIs not supported by the ET22XX models:
-ET24XX Configure OP Main Parameters 1
-ET24XX Configure OP Main Parameters 2
-ET24XX Configure OP Running Program Parameters
-ET24XX Configure OP Logic Output Status
-ET24XX Configure OP Basic Alarm Options
-ET24XX Configure OP Autotune Options
-ET24XX Configure OP Active PID
-ET24XX Configure OP Cool Bands
-ET24XX Configure OP Gain Scheduler Setpoint
-ET24XX Configure OP PID Feedforward Parameters
-ET24XX Configure OP Setpoint Parameters
-ET24XX Configure OP Remote Setpoints Parameters
-ET24XX Configure OP Basic Input Parameters
-ET24XX Configure OP Pyrometer Emisivity
-ET24XX Configure OP Switchover Transition Region Limits
-ET24XX Configure OP On Off Control Parameters 1
-ET24XX Configure OP On Off Control Parameters 2
-ET24XX Configure OP Output PID Control Parameters 1
-ET24XX Configure OP Output PID Control Parameters 2
-ET24XX Configure OP Motor Parameters
-ET24XX Configure OP Motor Parameters (old)
-ET24XX Configure OP Program Parameters
-ET24XX Configure OP Working Program Parameters
-ET24XX Configure OP Program Segment Type
-ET24XX Configure OP Program Segment Parameters
-ET24XX Configure OP DC Output Telemetry
-ET24XX Logging Operations
-ET24XX Additional Operator Parameters for 2408 Indicator
-ET24XX Instrument Configuration
-ET24XX Instrument Configuration - Extended Parameters
-ET24XX Configure BCD Input Function
-ET24XX Input Configuration
-ET24XX Configure 8-point Custom Linearisation
-ET24XX Configure Setpoints
-ET24XX Programmer Configuration
-ET24XX Programmer Configuration - Extended Parameters
-ET24XX Extended Configuration Digital Input2
-ET24XX Configure JA Comm Module
-ET24XX Configure Output Modules - Percent of PID or Retran Values Giving Limits Output
-ET24XX Configure Output Modules - Selecting Units
-ET24XX Configure Output Modules - Input Module Value Limit
-ET24XX Configure Output Modules - Potentiometer Input Scalar Limits
-ET24XX Configure Output Module 1C - Values Giving Output Limits¨
-ET24XX Configure Output Module 3A - Value Limits
-ET24XX Configure Output Module 3A - Input Value Limits
-ET24XX Configure Calibration
-ET24XX Configure Calibration Output Modules
-ET24XX Configure - Additional Configuration Parameters for 2408 Indicator
-ET24XX Set Control Output mode
-ET24XX Set Program Status
-ET24XX Read Program Status
-ET24XX Read Output Components
-ET24XX Read Currently Selected PV Input
-ET24XX Read Rate Limit Status
-ET24XX Read Program Segment Type
-ET24XX Read Processor Utilisation Factor
-ET24XX Prosess Value Monitoring Example
-ET24XX Temperatur Control and Monitoring Example

List of VIs partially supported by the ET22XX models:
-ET24XX Configure OP Advanced Parameters : works only for parameter "Targret Setpoint" (and only in manual mode)
-ET24XX Configure OP PID Parameters : will work only if "PID number" will be set to 1
-ET24XX Configure OP Relative Cool Gain : will work only if "PID number" will be set to 1
-ET24XX Select Setpoint : V "Setpoint Number" only 0 or 1 can be set
-ET24XX Configure OP Setpoint Value : Limited to "Setpoint Number" 0 or 1
-ET24XX Configure OP Advanced Input Parameters : works only with setting "User calibration enable"
-ET24XX Display Configuration : can only set values: 0,1,2,3,5,6
-ET24XX Alarm Configuration : for "Alarm Type" last 6 values are not valid and for "Latching" last 2 values are not valid
-ET24XX Configure Digital Inputs : most of the values for parameter "Input Functions" is not valid, see Instrument Handbook
-ET24XX Configure HA Comm Module : "Delay" setting is not supported
-ET24XX Configure Retransmitted Values for Comms Modules : Only for "HA" module
-ET24XX Configure Output 1A : Enumerated params and "Digital function mask" have different values/ranges see. Instrument Handbook
-ET24XX Configure Output 2A : Enumerated params and "Digital function mask" have different values/ranges see. Instrument Handbook
-ET24XX Configure Output 3A : Enumerated params and "Digital function mask" have different values/ranges see. Instrument Handbook
-ET24XX Configure Output 4A : from series 22XX supports only 2204
-ET24XX Configure Output Modules : Electrical Output Limits : only for module "1A"
-ET24XX Configure Calibration Input Modules : only for "Selected Input" = "Input 1"
-ET24XX Read Status Words : Some status words are not supported or have other meaning
-ET24XX Read Input Values : For "Selected Input"=1 does not read parameter "Input Linearised Value", "Selected Input"=2 does not read anything
-ET24XX Read Statuses Flags : reads only "Sensor Break Status Flag"
-ET24XX Read Advanced Parameter value : reads only parameters: "Target setpoint", "Heater current", "Working setpoint", "Valve Posn"
-ET24XX Read Miscellaneous Status and Comms-only Parameters 1 : Reads only parameters: "Instrument mode",
"Acknowledge all alarms", "Disable keys"
-ET24XX Read Miscellaneous Status and Comms-only Parameters 1 : Reads only parameters: "Process error", "PV millivolts from comms", 
"Input test point enable", "Sensor break sourced from Test", "Filter initialisation flag"
-ET24XX Read Process Variables: reads only "Process Value"

Other ET24XX VIs should work with the ET22XX models, although they have not been tested.


6. Revision History

The latest version of this and other LabVIEW and LabWindows/CVI instrument drivers can be downloaded at the 
Instrument Driver Network.

REV 1.0.0, 12/2004, Ondrej Krahulec
Original Release

REV 1.0.1, 01/2005, Ondrej Krahulec
Changes : Corrected register number in VI: "ET24XX Set Controller Mode"

REV 1.0.2, 04/2005, Ondrej Krahulec
Changes : 1. Optimized functions of modbus communication (utility)
        2. Repaired ID Query in "ET24XX Initialize.vi"
        3. Repaired bug in "ET24XX Set Instrument Mode.vi"
        4. Improvement example "ET24XX Temperature Control and Monitoring Example.vi"
        
REV 1.1, 09/2006, Russell Read
Changes : 1. Added modbus VIs for reading/writing U32 values (for use with millisecond time-types)
	  New VIs in _et24xx.llb
		Utility Multiple Write To Registers - Milliseconds.vi
		Utility Write To Register - Milliseconds.vi
		Utility Read From Register - Milliseconds.vi
	2. Corrected calculation of program parameter addresses.
        3. Corrected programmer durations from being sent as IEEE-754 floating-point. All programmer durations should now be sent in ms (U32)
        4. Repaired several bugs in "ET24XX Configure OP Program Segment Parameters.vi" 
        
REV 1.11, 12/2006, Russell Read
Changes : 1. Modified "ET24XX Instrument Configuration.vi" to remove the write to PD track parameter. Required to correctly support V4.00 and above.
	2. Also modified "ET24XX Instrument Configuration.vi" to default the control action as reverse (which is probably more usual)
	3. Corrected "ET24XX Operations with Alarms.vi" to use correct write VI
        4. Modified "ET24XX Configure OP PID Parameters.vi" to write to integral and derivative times in milliseconds (U32) not as floats

REV 1.2, 2/2009, Nathan T.
Changes : 1. Modified "ET24XX Instrument Configuration.vi" to remove the write to the Manual/Auto Transfer PD Control register to conform with firmware changes.