OWMT-SOFT-OPC Version 2.2 Copyright ©2004, Omega Engineering, Inc.
OMEGAnet® Online Service www.omega.com USA: ISO 9001 Certified Canada: USA and Canada: Mexico: Benelux: Czech Republic: France: Germany/Austria: United Kingdom: ISO 9002 Certified Internet e-mail info@omega.com Servicing North America: One Omega Drive, Box 4047 Stamford CT 06907-0047 Tel: (203) 359-1660 e-mail: info@omega.com FAX: (203) 359-7700 976 Bergar Laval (Quebec) H7L 5A1, Canada Tel: (514) 856-6928 e-mail: info@omega.
Contents Overview 1 OMWT-SOFT-OPC Main Window 8 Quick Start................................................................................................................................. 1 Description ................................................................................................................................ 3 OMWT-SOFT-OPC Server and Wireless ................................................................................. 3 Receivers ..............................................
OMWT-SOFT-OPC Server Tags 29 OMWT-SOFT-OPC Server Data Logging 47 OMWT-RECIP Receivers 51 Error Messages 53 Corrections 55 Using OPC Tags.......................................................................................................................29 Device Names ..........................................................................................................................29 Device Tag Names ........................................................................................
Overview Quick Start When OMWT-SOFT-OPC is run for the first time it displays this help screen. You may view this help screen again by selecting "Help" from OMWT-SOFT-OPC's main window. OMWT-SOFT-OPC is designed to gather data from sensors. OMWT-SOFT-OPC makes available the data it receives from each sensor through OPC tags. The main OMWT-SOFT-OPC Server window will show the total number of devices in the startup list and how many of those that are online.
If there is not an OMWT-SOFT-OPC.ini file or if [Server]NumberDevices=0 and when OMWT-SOFT-OPC starts, it will automatically search for all devices on the network and add them to its list of devices to process.
Description OMWT-SOFT-OPC is a data acquisition OLE for Process Control (OPC) server that acquires data from devices and passes this data using OPC to a client application. OMWT-SOFT-OPC waits for the device to transmit and then processes the transmission. Any Windows® application that can use OPC can obtain this data from the OMWTSOFT-OPCServer. Examples of such applications include Wonderware® Intouch, National Instruments® LookOut, Capital Equipment Corp.
delete it. To edit a device click on the device to select it and click on "Edit" to edit the device. There is also a "Stop" button. If you click that button, OMWT-SOFTOPC will stop listing devices in the window. When you click on the "Stop" button it becomes a "Receive" button. If you click on that, OMWT-SOFT-OPC will start receiving packets and listing devices again. When you are ready, hit "OK", or "Cancel" to exit.
Receivers The following is a list of supported receivers: x OMWT-REC232-600 x OMWT-RECIP x x Device List OMWT-XREC-SER (at 19200 baud) OMWT-REPEAT OWMT-SOFT-OPC Server interfaces to a large number of devices. New devices are continually being created for wireless network. Check with your distributor for the latest.
Polling For a wireless device the polltime has a slightly different meaning. OWMT-SOFTOPC does not actively poll wireless devices. Rather, it waits to receive a packet from the devices. Therefore, the polltime is how often OWMT-SOFT-OPC expects to receive a packet from the wireless devices. The polltime for a wireless device is configurable during device setup. OWMTSOFT-OPC will use this time to determine when to mark a device offline.
What is OPC? Data Logging OLE for Process Control (OPC) is a specific specification of Microsoft’s Object Linking and EmbeOPCding (OLE) and Component Object Model (COM) that is administered by the OPC Foundation (150 member companies including Microsoft Corporation). OPC provides a common interface for devices and applications to communicate. Devices that gather or originate data become OPC servers, providing data to OPC client applications in a consistent fashion.
OMWT-SOFT-OPC Main Window Main Window Setup OMWT-SOFT-OPC displays the number of devices online and offline. It also lists the devices that are currently offline displaying the name and serial number of the device. If OMWT-SOFT-OPC is running with TCP/IP receivers, then for each offline device it will display the node address, name and serial number of the device. OWMT-SOFT-OPC simplifies setup by automatically finding, identifying and beginning to poll devices in a network.
Add/Delete IP Connection (OMWT-RECIP Receiver only) OWMT-SOFT-OPC will display the “Add/Delete IP Connection” screen. IP addresses already setup will be displayed. The following is a list of the columns: Node – Node number for the IP address. OWMT-SOFT-OPC uses this number to identify this IP connection. OWMT-SOFT-OPC uses this number to update the OPC item “nodaladdress”. IP Address – the IP address that is used to address the receiver.
View IP Connection Status (OMWT-RECIP Receiver only) OWMT-SOFT-OPC will display the “IP Status” screen. OWMT-SOFT-OPC shows the current state of the all the connections. The following describes the columns: Node – Node number for the IP address. OWMT-SOFT-OPC uses this number to identify this IP connection. OWMT-SOFT-OPC uses this number to update the OPC item “nodaladdress”. IP Address – the IP address that is used to address the receiver.
Outputs Outputs are only send packets. The Output devices do not send packets. Therefore the setup for an Output sensor must be done manually. Some Outputs need to be “trained” to the packets that it will receive for from the Server. New and Edit Create or edit an Output object to manage an Output sensor. The following describe the parameters necessary to set up an Output sensor. Type – “Dual Discrete Outputs” or “12 bit Analog Output”. Select the type of Output sensor.
Train The Train dialog is used in the processing of training the Output device to output packets (as produced by OWMT-SOFT-OPC). Follow these steps to train an Output device: 1. Select the desired Output from the list of Outputs. 2. Press and hold the button on the Output device (label as “train”). 3. Click the button on the Train window. Repeat until the LED on the Output device is on. The Output device is now ready to receive Output packets from OWMT-SOFT-OPC.
Search and Add Devices OWMT-SOFT-OPC will display the "Add Wireless Device" screen. Devices already in the OWMT-SOFT-OPC.ini file are displayed in the top portion of the screen. Follow the setup procedure to add more devices. The setup screen is the method by which OWMT-SOFT-OPC acquires wireless devices. The default on the setup screen is to accept only packets that are sent in service mode from the device (the packet is sent by pressing the service button on the device.
Devices Errors Clicking this menu option shows the View Device List window. OMWT-SOFT-OPC shows a list of devices and their serial numbers. To see the help for a device, click on the device and then click the help button. OMWT-SOFT-OPC will display the help for the selected device. OMWT-SOFT-OPC displays the Communication Errors window. This window shows the last error that occurred. Tries Count: Number of tries that have occurred before a device is considered offline.
OMWT-SOFT-OPC Server .INI File Format OMWT-SOFT-OPC.ini The OMWT-SOFT-OPC.INI file contains the configuration parameters for the server and the devices being polled. When OMWT-SOFT-OPC searches and finds a new device it adds the device to the INI file and assigns default initial parameters. These parameters can be changed by using a text editor and editing the INI file, or by using the included OMWT-SOFT-OPC.ini Editing Utility, which will be discussed later in this Help.
SERVER [Server] - Section name. PortType - Communication medium (AUTO, OMWT-232-600, etc.). PortNo - Port number. NumberDevices - Number of devices to be polled by the server. OfflinePollTime - How often to poll for offline devices. Milliseconds Tries - No. of tries during polling before a device is marked offline. HostAdapterCheck - Enables/disables the detection of receiver. (0 or 1) BaudRate –options are: 115,200; 38,400; 19,200; or 1200. The default is 19200.
Logging [Logging] - section name LogRate - 0: no logging; 1-100000 logging interval in seconds. 5 sec or greater OMWT-SOFT-OPC opens and closes the log file at every logging interval. Less than 5 OMWT-SOFT-OPC leaves the file open until OMWT-SOFT-OPC is terminated or “Server.Logging.LogRate” is set to 0 or 5 and greater. LogFile - full pathname for the log file - default "OMWT-SOFTOPC.
TEMPERATURE Setup (OMWT-TEMP15 and OMWT-THERM) [Devicen] - Section name. Address - – serial number of the sensor. DeviceType - Device type. (DeviceType=TEMP) PollTime - How often to poll the device. (ms) Label - Name used for the device (and Topic). Log - Enable/disable logging of device. LogDecimalPlaces - Number of decimals to create when logging. Units - See OPC tags list under input.units for description. Cal1Raw - Two point calibration point 1. Cal2Raw - Two point calibration point 2.
HUMIDITY (OMWT-TEMPRH) [Devicen] - Section name. Address - – serial number of the sensor. DeviceType - Device type. (DeviceType=HUMIDITY) PollTime - How often to poll the device. (ms) Label - Name used for the device (and Topic). Log - Enable/disable logging of device. LogDecimalPlaces - Number of decimals to create when logging. PollSamples - No. of samples per poll (must be odd no.) If >0 Median Filter if <0 then Average Filter is used.
DIGCOUNTER and Directional Counter (OMWT-IRCNT, OMWT-DIRCNT) [Devicen] - Section name. Address - – serial number of the sensor. DeviceType - Device type. (DeviceType=DIGCOUNTER or DIRECTCNT) PollTime - How often to poll the device. (ms) Label - Name used for the device (and Topic) (typically DIGCOUNTER1 or DIRECTCNT1). Log - Enable/disable logging of device. LogDecimalPlaces - Number of decimals to create when logging.
CNTTEMP (OMWT-DOORCNT) [Devicen] - Section name. Address – serial number of the sensor. DeviceType - Device type. (DeviceType=CNTTEMP) PollTime - How often to poll the device. (ms) Label - Name used for the device (and Topic) (typically CNTTEMP1). Log - Enable/disable logging of device. LogDecimalPlaces - Number of decimals to create when logging. Scale - Multiplier for Counter A Units - Generic label for units - no function Description - Generic description field temp.Units - See OPC tag item temp.
FASTCNTTEMP (OMWT-PULSECNT) [Devicen] - Section name. Address – serial number of the sensor. DeviceType - Device type. (DeviceType=FASTCNTTEMP) PollTime - How often to poll the device. (ms) Label - Name used for the device (and Topic) (typically FASTCNTTEMP1). Log - Enable/disable logging of device. LogDecimalPlaces - Number of decimals to create when logging. Scale - Multiplier for Counter A Units - Generic label for units - no function Description - Generic description field temp.
ALARMTEMP (OMWT-TEMPALRM) [Devicen] - Section name. Address - serial number of the sensor. DeviceType - Device type. (DeviceType=TEMP) PollTime - How often to poll the device. (ms) Label - Name used for the device (and Topic). Log - Enable/disable logging of device. LogDecimalPlaces - Number of decimals to create when logging. Units - See OPC item temp.input.units for description. Cal1Raw - Two point calibration point 1. Cal2Raw - Two point calibration point 2.
Analog Input (OMWT-AIN5V, OMWT-AIN10V, OMWT-AIN20MA, OMWT-VIB, OMWTMOT) [Devicen] - Section name Address – serial number of the sensor. DeviceType - DeviceType=AI PollTime - How often to poll the device (ms). Label - Name used for the device (and Topic) (typically AI1) Log - Enable/disable logging of device. LogDecimalPlaces - Number of decimals to create when logging. Cal1Raw - Two point calibration point 1 (default 0). Cal2Raw - Two point calibration point 2 (default 4095).
Access/Control Reader (OMWT-ACCESSREADER) [Devicen] - Section name. Address - serial number of the sensor. DeviceType - Device type. (DeviceType=IDR) PollTime - How often to poll the device or wait for packet. (ms) Label - Name used for the device (and Topic). Log - Enable/disable logging of device. LogDecimalPlaces - Number of decimals to create when logging. Description - General purpose description. OMWT-SOFT-OPC Server OMWT-SOFT-OPC Server .
Repeater (OMWT-REPEAT) [Devicen] - Section name. Address - serial number of the sensor. DeviceType - Device type. (DeviceType=REPEATER) PollTime - How often to poll the device or wait for packet. (ms) Label - Name used for the device (and Topic) (typically REPEATER1). Log - Enable/disable logging of device. LogDecimalPlaces - Number of decimals to create when logging. Description - General purpose description. Dual Discrete Output (OMWT-DUALOUT) [Devicen] - Section name.
Wireless Analog Output (OMWT-ANGOUT) [Devicen] - Section name. Address - serial number of the sensor. NodalAddress – node where the output will be sent. Defaults to 0 for the OMWT-REC323-600 Receiver. For OMWT-RECIP, the node number represents each receiver starting at 1. If set to 0, OMWT-SOFT-OPC will send the output packet to all nodes. DeviceType - Device type. (DeviceType= OUTPUTANALOG) PollTime - How often to poll the device or wait for packet. (ms) Defaults to 0 for outputs.
OMWT-SOFT-OPC INI Backup Any time OMWT-SOFT-OPC Server modifies the INI file, OMWT-SOFT-OPC will create a copy of the previous INI file. OMWT-SOFT-OPC Server names this backup file the same file name as the INI file but names the file extension as “.Bnn” where n is from 01 to 20. OMWT-SOFT-OPC will create up to 20 backups. If OMWTSOFT-OPC needs to create more, it will overwrite the oldest backup which will be typically starting at “.B01”.
OMWT-SOFT-OPC Server Tags Using OPC Tags OMWT-SOFT-OPC uses the Device Name for the first part of the OPC tag name. The individual tag names from Device follow. OMWT-SOFT-OPC uses a hieratchial tree from name with various degrees of levels. The following is two examples of access two tags from a temperature device: TEMP1.input.value Device Names TEMP2.input.units OMWT-SOFT-OPC uses the device name as the first part of the OPC tag name. A device contains a nodal address.
Where n is a number starting at 1. OMWT-SOFT-OPC Server guarantees that each label assigned will be unique (No Duplicates Allowed).
Device Tag Names The Server uses device tag names to allow access to the I/O data and specific operational information. Tag names are dependent on the type of devices used. Temperature (OMWT-TEMP15, OMWT-THERM): TEMPn or 'T' Prefixed Topic Names online (R) - indicates if the device is communicating (0 or 1) nodaladdress (R) – (TCP/IP Receiver). The node address starts at 1. For TCP/IP Receivers, the node address corresponds to the node number for the TCP/IP connection.
Digital I/O: DIGITALn online (R) - indicates if the device is communicating (0 or 1) nodaladdress (R) – (TCP/IP Receiver). The node address starts at 1. For TCP/IP Receivers, the node address corresponds to the node number for the TCP/IP connection. repeateraddress (R) – (Wireless mode) contains the location identifier of the OMWT-REPEAT repeater. If the sensor did not pass through a repeater then the value is 0.
Temperature/Humidity: HUMIDITYn (OMWT-TEMPRH) online (R) - indicates if the device is communicating (0 or 1) polltime (R/W) - how often to poll the device (in milliseconds) nodaladdress (R) – (TCP/IP Receiver). The node address starts at 1. For TCP/IP Receivers, the node address corresponds to the node number for the TCP/IP connection. repeateraddress (R) – (Wireless mode) contains the location identifier of the OMWT-REPEAT repeater. If the sensor did not pass through a repeater then the value is 0.
DIGCOUNTER and Directional Counter: DIGCOUNTERn and DIRECTCNTn (OMWT-IRCNT, OWT-DIRCNT) online(R) - indicates if the device is communicating (0 or 1) polltime(R/W) - how often to poll the device (in milliseconds) nodaladdress (R) – (TCP/IP Receiver). The node address starts at 1. For TCP/IP Receivers, the node address corresponds to the node number for the TCP/IP connection. repeateraddress (R) – (Wireless mode) contains the location identifier of the OMWT-REPEAT repeater.
CNTTEMP: CNTTEMPn (OMWT-DOORCNT) online(R) - indicates if the device is communicating (0 or 1) polltime(R/W) - how often to poll the device (in milliseconds) nodaladdress (R) – (TCP/IP Receiver). The node address starts at 1. For TCP/IP Receivers, the node address corresponds to the node number for the TCP/IP connection. repeateraddress (R) – (Wireless mode) contains the location identifier of the OMWT-REPEAT repeater. If the sensor did not pass through a repeater then the value is 0.
FASTCNTTEMP: FASTCNTTEMPn (OMWT-PULSECNT) online(R) - indicates if the device is communicating (0 or 1) polltime(R/W) - how often to poll the device (in milliseconds) nodaladdress (R) – (TCP/IP Receiver). The node address starts at 1. For TCP/IP Receivers, the node address corresponds to the node number for the TCP/IP connection. repeateraddress (R) – (Wireless mode) contains the location identifier of the OMWT-REPEAT repeater. If the sensor did not pass through a repeater then the value is 0.
ALARMTEMP: ALARMTEMPn (OMWT-TEMPALRM) online (R) - indicates if the device is communicating (0 or 1) nodaladdress (R) – (TCP/IP Receiver). The node address starts at 1. For TCP/IP Receivers, the node address corresponds to the node number for the TCP/IP connection. repeateraddress (R) – (Wireless mode) contains the location identifier of the OMWT-REPEAT repeater. If the sensor did not pass through a repeater then the value is 0.
AnalogInput: AIn (OMWT-AIN5V, OMWT-AIN10V, OMWT-AIN20MA, OMWT-VIB, OMWTMOT) online(R) - indicates if the device is communicating (0 or 1) polltime(R/W) - how often to poll the device (in milliseconds) nodaladdress (R) – (TCP/IP Receiver). The node address starts at 1. For TCP/IP Receivers, the node address corresponds to the node number for the TCP/IP connection. repeateraddress (R) – (Wireless mode) contains the location identifier of the OMWT-REPEAT repeater.
Access/Control Reader: IDRn (OMWT-ACCESSREADER) online (R) - indicates if the device is communicating (0 or 1) polltime (R/W) - how often to poll the device (in milliseconds) nodaladdress (R) – (TCP/IP Receiver). The node address starts at 1. For TCP/IP Receivers, the node address corresponds to the node number for the TCP/IP connection. repeateraddress (R) – (Wireless mode) contains the location identifier of the OMWT-REPEAT repeater. If the sensor did not pass through a repeater then the value is 0.
(W) – indicates that the tag is writeable only. (R/W) – indicates that the tag is both readable and writeable. OPC Write operations will either change an I/O point at the device, or an operation will be performed.
Repeater: REPEATERn (OMWT-REPEAT) online (R) - indicates if the device is communicating (0 or 1) polltime (R/W) - how often to poll the device (in milliseconds) nodaladdress (R) – (TCP/IP Receiver). The node address starts at 1. For TCP/IP Receivers, the node address corresponds to the node number for the TCP/IP connection. repeateraddress (R) – (Wireless mode) contains the location identifier of the OMWT-REPEAT Repeater. If the sensor did not pass through a repeater then the value is 0.
Dual Discrete Output: OUTPUTDISCn (OMWT-DUALOUT) online (R) - indicates if the device is communicating (0 or 1) polltime (R/W) - how often to poll the device (in milliseconds) nodaladdress (R/W) – (TCP/IP Receiver). The node address starts at 1. For TCP/IP Receivers, the node address corresponds to the node number for the TCP/IP connection. You can write to this parameter to determine which node to send the output packet.
Wireless Analog Output: OutputAnalogn (OMWT-ANGOUT) online (R) - indicates if the device is communicating (0 or 1) polltime (R/W) - how often to poll the device (in milliseconds) nodaladdress (R/W) – (TCP/IP Receiver). The node address starts at 1. For TCP/IP Receivers, the node address corresponds to the node number for the TCP/IP connection. You can write to this parameter to determine which node to send the output packet.
Server Item Names Server Items are made available when the "Server" Topic is defined. These items give information about the Server and the current operational status of the Server. PortType (R) - communication medium: "COM", "LPT", etc. PortNo (R) - port number. PollTries (R) - No. of missed polls before a device is considered offline.
DeviceCount.REPEATER – number of Repeaters DeviceCount.OUTPUTDESC – number of Dual Discrete Outputs DeviceCount.OUTPUTANALOG – number of Wireless Analog Outputs Logging.Rate (R/W) - indicates the rate of logging in seconds. 0 - no logging. Less than 1 is accepted. Less than 5, OMWT-SOFT-OPC leaves the file open until terminated or set to 0. When 5 or greater, OMWT-SOFT-OPC opens, then logs, and then closes the file at every logging interval.
Description of NetErrors.LastNo and NetErrors.Last -44 Communication Error: CRC16 or Time Out -39 OMWT-SOFT-OPC Server Internal Error. -46 -33 -25 46 x OMWT-SOFT-OPC Server Tags Cannot Find Receiver. Invalid calibration entered. Communication error with Receiver.
OMWT-SOFT-OPC Server Data Logging Features OMWT-SOFT-OPC Server can log data to an ASCII file at a programmable interval. The default name of the file is OMWT-SOFT-OPC.LOG. The name can be changed by changing the INI file. The log rate (programmable interval) can be changed in the INI file ([Logging] LogRate=) or by a client application through OPC (SERVER!LogRate). By default, all devices listed in the INI file are logged. You can disable logging for each device ([Devicen] Log=).
File Management If the log rate is greater than or equal to 5 seconds, OMWT-SOFT-OPC opens and then closes the log file each time data is logged. If the log rate is less than 5 seconds, OMWT-SOFT-OPC leaves the file open and closes the file when OMWT-SOFTOPC is terminated, the log rate is set to zero, or the log rate is set to 5 or greater. The log file can be viewed while OMWT-SOFT-OPC is logging.
File Format - Data Log The log record format is as follows: Where: hh:mm:ss,mm/dd/yyyy,data1,data2,data3, ... , datan hh:mm:ss is the time (ex. 23:40:50) mm/dd/yyyy is the date (ex. 02/03/99) datan - is the data for each device that has logging enabled. Most devices have one value for the data. However 4 devices have different formats. MANALOG: channels enabled. DIGITAL: COUNTER: value1,value2,...
File Format - Error Log The log record format is as follows: Where: hh:mm:ss,mm/dd/yyyy,Error number,Error Msg,Online Flag,DeviceLabel hh:mm:ss is the time (ex. 23:40:50) mm/dd/yyyy is the date (ex.
OMWT-RECIP Receivers Overview of OMWT-RECIP Receivers OWMT-SOFT-OPC can connect to OMWT-RECIP receivers and receive and process sensors packets. As of this writing, the OWMT-RECIP (operating in “PassThru” mode) is the only supported TCP/IP receiver. OWMT-SOFT-OPC makes a TCP/IP connection to a receive and then waits for sensor packets. OWMT-SOFTOPC then processes the sensor packet as if it came from a receiver (like OWMTREC232).
OMWT-RECIP Receiver Notes If OWMT-SOFT-OPC initiates the connection then OWMT-SOFT-OPC will continually try to establish the connection when the connection is disrupted or never accepted. If the receiver initiates the connection, OWMT-SOFT-OPC relies on the receiver to re-establish the connection if the connection is disrupted. Each TCP/IP connection is assigned a “node number”. This “node number” gets associated with a sensor’s data. The “nodaladdress” OPC item is updated with the “node number”.
Error Messages Communication Errors OMWT-SOFT-OPC Server communication initialization errors will cause the 'OMWT-SOFT-OPC Initializing Error!" window to be displayed to help you determine what the cause of failure may be and to allow you to retry or abort the program. Error In Finding/Initializing Port. You have specified a port that does not exist on your computer. Use Setup to change to a port you have, or select Auto and let OMWT-SOFT-OPC Server search for you.
Runtime Errors Communication Error: CRC16 or Time Out Sensor transmission was not received within the polltime or the transmission got corrupted. Cannot Find Receiver. Receiver has become disconnected from the computer. OMWT-SOFT-OPC Server Internal Error. Contact your dealer.
Corrections Why Use Corrections Some devices, like a thermistor, need their data corrected in order to be meaningful. A thermistor uses resistance to measure temperature. The relation between the resistance and the temperature is non linear. A thermistor uses a set of correction parameters to convert resistance to temperature. Other devices may need to correct data values in a non linear way.
How to use Corrections Correction.INI file After adding the Correction ID to the device section of the OMWT-SOFT-OPC.INI file, you must set up the Correction used by that Correction ID. If you're using a correction that is not predefined, you must write a Correction.INI file. This file should be stored in the same directory as the OMWT-SOFT-OPC.INI file. Name your file "Correction.INI" and include all the correction sections you like, from 1 to 127.
Predefined Corrections The device type "Thermistor" will default to a correction ID of 128. To override this default you can add a CorrID parameter to the device section of the OMWT-SOFTOPC.INI file, or you can set a new default for all thermistors in the Server section of the OMWT-SOFT-OPC.INI file. To change the default CorrectionID for all thermistors add the parameter "DefaultThermistorCorrID=" to the Server section, and set it to whatever CorrectionID you wish.
WARRANTY/DISCLAIMER OMEGA ENGINEERING, INC. warrants this unit to be free of defects in materials and workmanship for a period of 13 months from date of purchase. OMEGA’s Warranty adds an additional one (1) month grace period to the normal one (1) year product warranty to cover handling and shipping time. This ensures that OMEGA’s customers receive maximum coverage on each product. If the unit malfunctions, it must be returned to the factory for evaluation.
Where Do I Find Everything I Need for Process Measurement and Control? OMEGA…Of Course! Shop online at www.omega.
