ATI Technologies Metrinet User manual

O & M Manual
Metrinet
Ethernet-IP Communication Manual
Home Office European Office
Analytical Technology, Inc. ATI (UK) Limited
6 Iron Bridge Drive Unit 1 & 2 Gatehead Business Park
Collegeville, PA 19426 Delph New Road, Delph
Phone: [phone] Saddleworth OL3 5DE
610-917-0991 Phone: [phone]
Fax: [phone] Fax: + 44 (0)1457-874-468
Email: [e-mail] Email: [e-mail]

Table of Contents
Ethernet/IP Option ........................................................................................................... 3
1.1 General ............................................................................................................. 3
1.2 Ethernet/IP Communication .............................................................................. 3
1.3 Ethernet/IP Transmission Details ...................................................................... 4
1.4 Cable Connection ............................................................................................. 4
1.5 Configuring MetriNet for Ethernet Option .......................................................... 6
1.6 Configuring fixed IP with BOOTP ...................................................................... 6
1.7 Loading EDS File ............................................................................................ 11
1.8 PLC Object Generic Settings .......................................................................... 11
1.9 PLC Object Settings Parameter Detail, and EDS Files ................................... 13
1.10 Optional Tool Examples: RSLinx Classic ........................................................ 27
Table of Figures
Figure 1 – Ethernet Cable Routing on MetriNet .............................................................. 5
Figure 2 - RJ45 Crimp Tool ............................................................................................. 5
Figure 3 – Force PC to Specific Network Subnet Prior to Running BOOTP .................... 7
Figure 4 – Launching BOOTP server .............................................................................. 7
Figure 5 – Setting IP/mask Assignment in BOOTP Server .............................................. 8
Figure 6 – Successful Detection of MAC ID and IP Address ........................................... 9
Figure 7 – PING and ARP Command Tests for IP Address Setting. ............................. 10
Figure 8 – Generic Module Input/Output Settings ......................................................... 12
Figure 9 – Connection/RPI Settings .............................................................................. 12
Figure 10 –Output Assembly Object Command Example with EIP_Tool ...................... 23
Figure 11 –Special Write-Codes for MetriNet Variable Changes .................................. 24
Figure 12 – TCP Object Query Example with EIP_Tool ................................................ 25
Figure 13 – Ethernet Link Object Query Example with EIP_Tool .................................. 26
Figure 14 – RSLinx Classic ........................................................................................... 28
Figure 15 – Adding Ethernet/IP Driver........................................................................... 28
Figure 16 – New Node Added Successfully to Driver Application. ................................ 29
Figure 17 – Creating DDE/OPC Topic ........................................................................... 29
Figure 18 – Processor Selection for PC-based OPC Topic ........................................... 30
Figure 19 – RSLinx OPC Test Client ............................................................................. 30
Figure 20 – OPC Running On Active Node Data .......................................................... 31

ATI MetriNet Ethernet/IP Communications Manual
3
O&M Manual
Rev-A (6/19)
Ethernet/IP Option
1.1 General
MetriNet Monitors are available with three digital communication options: Cellular,
Modbus-RTU, Modbus-TCP/IP, and Ethernet/IP. This manual applies only to
instruments supplied with the Ethernet/IP communication option. It is critical to
note that Ethernet/IP devices only communicate with other systems running the
“Industrial Protocol” of Ethernet. You cannot plug a MetriNet into your office
Ethernet and expect to have the instrument talk to your desktop computer.
The discussion of standard Ethernet and Ethernet/IP is vast, and well beyond the
ability to discuss here in great detail. The documentation for this option assumes
working network knowledge by the user.
1.2 Ethernet/IP Communication
Ethernet/IP was first introduced in 2001, and is a highly developed and complete
protocol for an industrial Ethernet network solution. Intended for automation
applications, EtherNet/IP is a member of a family of networks that implement the
Common Industrial Protocol (CIP) at its upper layers of the standard ISO/OSI 7-
layer model. CIP defines the object structure, specifies the message transfer,
provides users with a unified communication architecture, and encompasses a
comprehensive suite of services for a variety of manufacturing automation
applications which include data, control, safety, and configuration.
In the CIP Protocol, every network device represents itself as a series of objects.
Each object is simply a grouping of the related data values in a device. The identity
object contains related identity data values called attributes. Attributes for the
identity object include the vendor ID, date of manufacture, device serial number
and other identity data.

ATI MetriNet Ethernet/IP Communications Manual
4
O&M Manual
Rev-A (6/19)
1.3 Ethernet/IP Transmission Details
It should be understood that Ethernet/IP is simply an application layer protocol that
is transferred over an Ethernet hardware link. The word "Ethernet" simply refers
to the common physical cable, perhaps running to an office PC.
In the OSI model, “Ethernet” is the lower part of the model, the physical transfer
method or the hardware. It says nothing about the way information is transferred,
which is specified near the top of the OSI model. In the common office network,
many different standard communication protocols are operating during normal
office use, like IP, TCP, etc. None of these are designed to handle the CIP
industrial format, so that interface must be handled by a specific program that
recognizes the format. Because of this, an Ethernet/IP device cannot be directly
connected to your office network for transferring information.
The data for the protocol is constructed into a specific structure inside a standard
TCP/IP Packet. A user application program simply decodes the structure inside
the received TCP or UDP packet. The data structure consists of a grouping of
data values called Attributes inside other sets of containment data called Objects.
There are Ethernet/IP required Objects and application Objects. Required objects
are typically - Identity, TCP, and Router. Application objects consist of some
defined data types, like a Motor Object, and some user specific data types.
1.4 Cable Connection
The cable used for Ethernet/IP communication should meet the CAT5 standard
defined by the Electronic Industries Association and Telecommunications Industry
Association. It is readily available in lengths up to 100 ft. (30 m) with plugs on each
end.
To install an Ethernet cable in the MetriNet, pass the unterminated cable through
the cable gland nearest the location of the RJ45 connector on the Ethernet/IP
option board. Provide a slight service loop amount of slack so that the terminated
cable will not be pulling directly on the RJ45 connector once installed. Termination
of Cat5/5e/6 cables is very easy and can be completed quickly with the commonly
available RJ45 crimp tool.
Note that there a reconnection LEDs present on the face of the RJ45 connector,
which can be used to verify activity on the interface. Rather than detail their
specific use, it is sufficient to just very flashing on these LEDS when the unit is
powered up or actively communicating with the network client.

ATI MetriNet Ethernet/IP Communications Manual
5
O&M Manual
Rev-A (6/19)
Figure 1 – Ethernet Cable Routing on MetriNet
Figure 2 - RJ45 Crimp Tool
While professional results are optimized with the use of the termination tool and
custom cable lengths, patch cord style connection can be completed in some
cases by passing the finished RJ45 connectors through the enclosure cable gland.
The connector will fit through the plastic part of the cable gland, and the rubber
grommet can be slit (some RJ45s may be too big for this.) Once the connector is
inside the enclosure, simply plug it into the jack provided on the Ethernet/IP
communication board. Be sure to adjust the rubber insert in the cable gland so
that the slit is on the bottom and then tighten the gland to seal around the wire.

ATI MetriNet Ethernet/IP Communications Manual
6
O&M Manual
Rev-A (6/19)
1.5 Configuring MetriNet for Ethernet Option
Once the proper power is applied to the MetriNet monitor, select “Ethr” in the
^Host Comms listing of the OPTIONS menu to enable Ethernet/IP functionality.
1.6 Configuring fixed IP with BOOTP
The next step in the use of the MetriNet is to sort out how an IP network address
will be assigned to the instrument. The MetriNet acquires a dynamic network IP
address from the network client/master through the BOOTP service, which is
enabled by default for ODVA EIP-CIP conformance.
BOOTP is a very simple software server application that waits for a specific MAC
address to appear on the network, and then assigns it a pre-determined IP address
that has been set-up by the user. In the most actual applications, BOOTP runs
right on the PLC alongside tools like Rockwell’s Logix/Studio 5000. For manual
fixed settings, this same BOOTP server tool can be easily run on a PC. The current
Rockwell version of this tool (recommended) is –
“BootP-DHCP Ethernet/IP Commissioning Tool Version 3.02.00”
This tool is available from the Rockwell Automation website for free. For optimum
security, only download this tool directly from Rockwell Automation.
While this tool is normally used for dynamic assignment, the MetriNet will
remember the last successful assignment made by BOOTP, and it will retain that
assignment after cycling instrument power. Therefore, the tool can be used to lock
in a fixed IP address assignment, and then the BOOTP service will not actually be
required after that first assignment.
In order to use BOOTP properly on a PC, some careful NIC adjustment settings
must be made to the PC Ethernet port prior to running the BOOTP service. The
PC can only reach IP addresses at the predetermined IP/subnet level, so we must
force the PC to a subnet that can reach the existing MetriNet.
1) Turn off MetriNet. Connect MetriNet to laptop with direct cable. Set laptop
NIC port on a locked IP and subnet to stop DHCP service. In IPV4
properties on your PC’s Ethernet connection port, select "Use the following
IP Address" and set the PC to fixed IP of -
IP Address = 192.168.0.10
Subnet Mask = 255.255.255.0

ATI MetriNet Ethernet/IP Communications Manual
7
O&M Manual
Rev-A (6/19)
Figure 3 – Force PC to Specific Network Subnet Prior to Running BOOTP
2) Once this IP/subnet is set, click OK to save and then close it all out. Turn
PC off then back on to place it on the new IP address set in step 1. The PC
will now be able to access any network device on 192.168.0.X, as the
subnet mask 255.255.255 locks in the first three variables. The default
value for the MetriNet is 192.168.0.254, so it can now be reached by the
PC.
3) Find the Rockwell BOOTP PC application and launch it. Select your
Ethernet Adapter as the network interface.
Figure 4 – Launching BOOTP server

ATI MetriNet Ethernet/IP Communications Manual
8
O&M Manual
Rev-A (6/19)
4) On next screen, you must create an assignment relationship to match a
known MAC ID with a desired IP address. The MAC ID for your MetriNet is
written on a label inside the enclosure. For this example, we will use the
MAC ID - 00:80:A3:9B:BE:B6 and assign it an IP of 192.168.0.30. Hit OK
after this information is filled in, and you will see this entry appear in the
bottom half of the window under “Entered Relations.”
Once the MAC assignment has been entered, it is ready for a BOOTP IP
request to come in for assignment. Requests for assignment will appear in
the upper window as they come in.
Figure 5 – Setting IP/mask Assignment in BOOTP Server
5) Now, plug the cable from MetriNet into the PC Ethernet port, turn on power
to the MetriNet, and wait for BOOTP to detect the request from the MetriNet
for an IP address.
The upper “Discovery History Window” will show new IP requests coming
in on the Ethernet port, and when the specific MAC ID in our relation shows
up, the IP will be automatically assigned per our relation entry and sent to
the MetriNet. Note that you may see requests from other devices as they
come in, but only the specific MAC ID from the assignment will be
acknowledged.

ATI MetriNet Ethernet/IP Communications Manual
9
O&M Manual
Rev-A (6/19)
Figure 6 – Successful Detection of MAC ID and IP Address
Assignment in BOOTP Server
Once the assignment has been made and the IP has been sent to the
MetriNet, disconnect power to the MetriNet and that IP will be stored in the
instrument. The MetriNet stores the very last successful IP address
assignment. Then close out all BOOTP server windows.
6) Now, to check that the IP address has been properly saved, apply power to
MetriNet again and wait one 1 minute before connecting it to the PC port.
Do not launch BOOTP server this time, as you don’t need it. During the 1
minute wait, MetriNet will search for a BOOTP server on power up and won’t
find the service because it is not used here now, and the MetriNet is also
not connected to the PC. It will then revert to the stored default – the last
successful BOOTP assignment. Connect cable from MetriNet to the PC
after that one minute. You can now check the IP connection to the MetriNet
at that address by entering a ping command at the Windows OS command
prompt, for example “>ping 192.168.0.30.” You should see a response as
shown below. In addition, you can try an “>arp -a” command to show all
current connections and associated MAC addresses. You should see the
new IP address of 192.168.0.30 showing up.

ATI MetriNet Ethernet/IP Communications Manual
10
O&M Manual
Rev-A (6/19)
Figure 7 – PING and ARP Command Tests for IP Address Setting.
Note that the “arp -a” listing still shows this IP as a “dynamic” assignment,
as this is the fall-back IP that has been stored in the MetriNet. On power
up, the MetriNet will still try and find a BOOTP server for 30 seconds, and
then default to this stored value as the fallback. If you do not see your new
connection, two troubleshooting notes –
1-You must always be careful to place the new IP address on the proper
subnet level so the PC can still reach it with the settings made in step 1. If
the PC is on 192.168.0.X, then any assigned IP must be on the X level –
and don’t place the MetriNet on the same IP as the PC. During BOOTP
server assignment, if you place the MetriNet on a vastly different IP like
10.20.120.100, you must repeat step 1 before step 6 above to place the PC
at something like 10.20.120.10. This can get tricky, as you can make
assignments anywhere, but then the PC must be re-established on that new
net to find the new assignment.
2-Remember to wait a minute before the ping test if you verify a connection.
The MetriNet runs BOOTP by default, so it will be searching for that server
for about 30 seconds on power up, and then will default to the stored IP.

ATI MetriNet Ethernet/IP Communications Manual
11
O&M Manual
Rev-A (6/19)
1.7 Loading EDS File
The EDS file will specify many of the parameters for reading and writing the proper
registers in the MetriNet. It must first be loaded into server in control of the
network. This can vary widely depending on the tools, but here is an example
using Rockwell’s library “EDS Hardware Installation Tool.”
1-Launch the EDS tool and select “Add” to start the EDS Wizard for file
addition.
2-Select button for “Register a single file,” and browse to the file location for
the EDS file “ATI Q52x Transmitter EDS File.eds”
3-Follow though the screens to complete the addition, then exit the tool.
Now, the EDS file that is specific to the MetriNet is part of the Rockwell EDS
RSLinx library, and devices can be recognized when connected to the network.
1.8 PLC Object Generic Settings
PLCs handle this Ethernet/IP exchange in a wide variety of configurations, and the
basic configuration of a class 1 connection in every PLCs software is different, but
there should be a place to enter the following basic information.
Data Type: "INT" or "16-Bit"
Input T->O Assembly Instance: 0x65 or 101 decimal
Input T->O Size: 250 words (16-bit) or 500 bytes (8-bit)
Output O->T Assembly Instance: 0x66 or 102 decimal
Output O->T Size: 5 word (16-bit) or 10 bytes (8-bit)
Configuration Assembly Instance: 0x80 or 128 decimal
Configuration Size: 0
RPI Setting = 1000 mS or higher
This description represents the raw block of data in and out of the MetriNet, and
will take everything in 16-bit words (so you must parse out the 32-bit values shown
earlier.) The data typing and setting up of variables must all be done manually,
based on the values shown below in section 1.9. For more basic tools, like Molex-
EIP, that there may be an endian byte-swap occurring on each set of registers, so
you may have to byte swap each 16-bit register to recombine the data.

ATI MetriNet Ethernet/IP Communications Manual
12
O&M Manual
Rev-A (6/19)
Figure 8 – Generic Module Input/Output Settings
Figure 9 – Connection/RPI Settings

ATI MetriNet Ethernet/IP Communications Manual
13
O&M Manual
Rev-A (6/19)
1.9 PLC Object Settings Parameter Detail, and EDS Files
The following table describes all of the data types used
UINT Unsi
g
ned Inte
g
er
(
16-bit
)
UDINT Unsi
g
ned Double Inte
g
er
(
32-bit
)
INT Si
g
ned Inte
g
er
(
16-bit
)
DINT Si
g
ned Inte
g
er
(
32-bit
)
BYTE Bit Strin
g
(
8-bits
)
WORD Bit Strin
g
(
16-bits
)
DWORD Bit Strin
g
(
32-bits
)
LWORD Bit Strin
g
(
64-bits
)
ODVA CIP conforming objects implemented include –
0x01 Identity Object
0x04 Assembly Object, Input
0x04 Assembly Object, Output
0xF5 TCP Object
0xF6 Ethernet Link Object
*These are all broken down below in sections below.
Identity Object (01HEX – 1 Instance)
The following tables contain the attribute, status, and common services
information for the Identity Object. The Identity Object lists specific information
on the actual product and the vendor.
Class Attributes (Instance 0)
Attribute ID Name Data Type Data Value Access Rule
1 Revision UINT 1 Get
Identity Instance Attributes (Instance 1)
Attribute ID Name Data Type Data Value Access Rule
1 Vendor Number UINT 1530 Get
2 Device Type UINT
2B
HEX Get
3 Product Code
Number
UINT 101 Get
4 Major Revision
Minor Revision
USINT
USINT
01
01 Get
5 Status WORD See Below Get
6 Serial Number UDINT NU Get
7 Product Name SHORT STRING32 ATI Q52x Get

ATI MetriNet Ethernet/IP Communications Manual
14
O&M Manual
Rev-A (6/19)
Identity Instance Common Services
Service Code Implemented for Service Name
Class Level Instance Level
05HEX No Yes Reset
0EHEX Yes Yes Get_Attribute_Single
Input Assembly Object (04HEX – 1 Instance)
The Input Assembly Object is a collection of all the measurement information that
can be read from the MetriNet. This includes all data from any attached sensor(s.)
This is “read only” data that the MetriNet can send out. The data arrangement is
detailed below, including the byte size of various data fields.
Class Attributes (Instance 0)
Attribute ID Name Data Type Data Value Access Rule
1 Revision UINT 2 Get
2 Max Instance UINT 0x66 (102 decimal) Get
Input Instance Attributes (Instance 101)
Attribute ID Name Data Type Default Data Value Access Rule
3 Input Data VARIES 0 Get
Input Instance Common Services
Service Code Implemented for Service Name
Class Level Instance
Level
0E
HEX Yes Yes Get_Attribute_Single
Input Instance 101 – 500 Bytes
System IINFO
Bytes Data Type Description
0–1 WORD Interface Status Flags1
2–3 WORD System Status 1 Flags2
4–5 WORD System Status 2 Flags2
6–7 UINT Number of Sensors
8–9 UINT IP Address High
10–11 UINT IP Address Low
12–13 UINT Subnet Mask High
14–15 UINT Subnet Mask Low
16–17 UINT Gateway High
18–19 UINT Gateway Low

ATI MetriNet Ethernet/IP Communications Manual
15
O&M Manual
Rev-A (6/19)
Notes on System INFO flag data –
1Flags are as follows. Status flags2 is currently NU –
Bit Interface Status S
y
stem Status 1
0
(
LSB
)
MB Brid
g
e Status Sensor 1 Comm Err
1 MB Brid
g
e Timeou
t
Sensor 2 Comm Err
2 MB Brid
g
e Fail Sensor 3 Comm Err
3 NU Sensor 4 Comm Err
4 NU Sensor 5 Comm Err
5 NU Sensor 6 Comm Err
6 NU Sensor 7 Comm Err
7 NU Sensor 8 Comm Err
8
A
ctive NU
9 New Confi
g
NU
10 NU NU
11 NU NU
12 NU NU
13 NU NU
14 NU NU
15 NU NU
Sensor 1 MEASURE
Bytes Data Type Description
20-23 DINT S1 Main Value
24-27 DINT S1 Units
28-31 DINT S1 Raw Value
32-35 DINT S1 Temperature
36-37 INT S1 Output Value
38-39 WORD S1 Status 1
40-41 WORD S1 Status 2
42-43 INT S2 ID
Sensor 2 MEASURE
Bytes Data Type Description
44-47 DINT S2 Main Value
48-51 DINT S2 Units
52–55 DINT S2 Raw Value
56–59 DINT S2 Temperature
60-61 INT S2 Output Value
62-63 WORD S2 Status 1
64-65 WORD S2 Status 2
66-67 INT S2 ID

ATI MetriNet Ethernet/IP Communications Manual
16
O&M Manual
Rev-A (6/19)
Sensor 3 MEASURE
Bytes Data Type Description
68-71 DINT S3 Main Value
72-75 DINT S3 Units
76–79 DINT S3 Raw Value
80–83 DINT S3 Temperature
84-85 INT S3 Output Value
86-87 WORD S3 Status 1
88-89 WORD S3 Status 2
90-91 INT S3 ID
Sensor 4 MEASURE
Bytes Data Type Description
92-95 DINT S4 Main Value
96-99 DINT S4 Units
100–103 DINT S4 Raw Value
104–107 DINT S4 Temperature
108-109 INT S4 Output Value
110-111 WORD S4 Status 1
112-113 WORD S4 Status 2
114-115 INT S4 ID
Sensor 5 MEASURE
Bytes Data Type Description
116-119 DINT S5 Main Value
120-123 DINT S5 Units
124–127 DINT S5 Raw Value
128–131 DINT S5 Temperature
132-133 INT S5 Output Value
134-135 WORD S5 Status 1
136-137 WORD S5 Status 2
138-139 INT S5 ID
Sensor 6 MEASURE
Bytes Data Type Description
140-143 DINT S6 Main Value
144-147 DINT S6 Units
148–151 DINT S6 Raw Value
152–155 DINT S6 Temperature
156-157 INT S6 Output Value
158-159 WORD S6 Status 1
160-161 WORD S6 Status 2
162-163 INT S6 ID

ATI MetriNet Ethernet/IP Communications Manual
17
O&M Manual
Rev-A (6/19)
Sensor 7 MEASURE
Bytes Data Type Description
164-167 DINT S7 Main Value
168-171 DINT S7 Units
172–175 DINT S7 Raw Value
176–179 DINT S7 Temperature
180-181 INT S7 Output Value
182-183 WORD S7 Status 1
184-185 WORD S7 Status 2
186-187 INT S7 ID
Sensor 8 MEASURE
Bytes Data Type Description
188-191 DINT S8 Main Value1
192-195 DINT S8 Units2
196–199 DINT S8 Raw Value1
200–203 DINT S8 Temperature1
204-205 INT S8 Output Value3
206-207 WORD S8 Status 15
208-209 WORD S8 Status 25
210-211 INT S8 ID4
Notes on MEASURE data –
1Main Value, Raw Value, are Temperature are all 32 bit integers, displayed with an implied
fixed-decimal point 0.000 resolution.
So, 14.00 pH will show as 14000, which means 14.000 pH. 2000 uS conductivity will show as
2000000, meaning 2000.000 uS. 25C will show as 25000 meaning 25.000.
2Units are stored as packed ASCII hi/lo bytes.
3 Output Value is also displayed with implied 0.000 resolution. The MetriNet has no actual
hardware level output for these voltages. So, these are virtual values, like the alarm setpoints,
that could be used to feed some other process digitally.
4 ID not implemented at this time.

ATI MetriNet Ethernet/IP Communications Manual
18
O&M Manual
Rev-A (6/19)
5 Status Flags are as follows -
Bit Status 1 Status 2
0
(
LSB
)
A
LARM_
A
EE_INIT_FAIL
1
A
LARM_B MAIN_UNITS_HI
2
A
LARM_C MAIN_UNITS_LO
3
A
LARM_D MAIN_INPUT_ERR
4
A
LARM_E TC_UNITS_HI
5 ENTRY_OUT_OF_R
A
NGE
TC_UNITS_LO
6 ENTRY_ACCEPTED TC_INPUT_ERR
7 ENTRY_FAIL CAL_MAIN_SLOPE_HI
8 MAIN_CAL_PASS CAL_MAIN_SLOPE_LO
9 MAIN_CAL_FAIL CAL_MAIN_ZERO_HI
10 TC_CAL_PASS CAL_MAIN_OFFSET_H
I
11 TC_CAL_FAIL MAIN_UNSTABLE
12 TC_F CAL_TC_OFFSET_HI
13 SENSOR_LOCK TC_UNSTABLE
14 NU NU
15 NU NU
Sensor 1 INFO
Bytes Data Type Description
212-213 INT S1 Slope
214-215 INT S1 Offset
216–217 INT S1 Delay
218–219 INT S1 Alarm A
220-221 INT S1 Alarm B
222-223 INT S1 Slope Alarm
224-225 INT S1 Timer Limit
226-227 INT S1 Vout HI
228-229 INT S1 Vout LO
230-231 INT S1 TC Mode
232-239 LWORD S1 Tag1
240-247 LWORD S1 Tag2
Sensor 2 INFO
Bytes Data Type Description
248-249 INT S2 Slope
250-251 INT S2 Offset
252–253 INT S2 Delay
254–255 INT S2 Alarm A
256-257 INT S2 Alarm B
258-259 INT S2 Slope Alarm
260-261 INT S2 Timer Limit
262-263 INT S2 Vout HI
264-265 INT S2 Vout LO
266-267 INT S2 TC Mode
268-275 LWORD S2 Tag1
276-283 LWORD S2 Tag2

ATI MetriNet Ethernet/IP Communications Manual
19
O&M Manual
Rev-A (6/19)
Sensor 3 INFO
Bytes Data Type Description
284-285 INT S3 Slope
286-287 INT S3 Offset
288-289 INT S3 Delay
290-291 INT S3 Alarm A
292-293 INT S3 Alarm B
294-295 INT S3 Slope Alarm
296-297 INT S3 Timer Limit
298-299 INT S3 Vout HI
300-301 INT S3 Vout LO
302-303 INT S3 TC Mode
304-311 LWORD S3 Tag1
312-319 LWORD S3 Tag2
Sensor 4 INFO
Bytes Data Type Description
320-321 INT S4 Slope
322-323 INT S4 Offset
324-325 INT S4 Delay
326-327 INT S4 Alarm A
328-329 INT S4 Alarm B
330-331 INT S4 Slope Alarm
332-333 INT S4 Timer Limit
334-335 INT S4 Vout HI
336-337 INT S4 Vout LO
338-339 INT S4 TC Mode
340-347 LWORD S4 Tag1
348-355 LWORD S4 Tag2
Sensor 5 INFO
Bytes Data Type Description
356-357 INT S5 Slope
358-359 INT S5 Offset
360-361 INT S5 Delay
362-363 INT S5 Alarm A
364-365 INT S5 Alarm B
366-367 INT S5 Slope Alarm
368-369 INT S5 Timer Limit
370-371 INT S5 Vout HI
372-373 INT S5 Vout LO
374-375 INT S5 TC Mode
376-383 LWORD S5 Tag1
384-391 LWORD S5 Tag2

ATI MetriNet Ethernet/IP Communications Manual
20
O&M Manual
Rev-A (6/19)
Sensor 6 INFO
Bytes Data Type Description
392-393 INT S6 Slope
394-395 INT S6 Offset
396-397 INT S6 Delay
398-399 INT S6 Alarm A
400-401 INT S6 Alarm B
402-403 INT S6 Slope Alarm
404-405 INT S6 Timer Limit
406-407 INT S6 Vout HI
408-409 INT S6 Vout LO
410-411 INT S6 TC Mode
412-419 LWORD S6 Tag1
420-427 LWORD S6 Tag2
Sensor 7 INFO
Bytes Data Type Description
428-429 INT S7 Slope
430-431 INT S7 Offset
432-433 INT S7 Delay
434-435 INT S7 Alarm A
436-437 INT S7Alarm B
438-439 INT S7 Slope Alarm
440-441 INT S7 Timer Limit
442-443 INT S7 Vout HI
444-445 INT S7 Vout LO
446-447 INT S7 TC Mode
448-455 LWORD S7 Tag1
456-463 LWORD S7 Tag2
Sensor 8 INFO
Bytes Data Type Description
464-465 INT S8 Slope
466-467 INT S8 Offset
468-469 INT S8 Delay
470-471 INT S8 Alarm A
472-473 INT S8Alarm B
474-475 INT S8 Slope Alarm
476-477 INT S8 Timer Limit
478-479 INT S8 Vout HI
480-481 INT S8 Vout LO
482-483 INT S8 TC Mode
484-491 LWORD S8 Tag1
492-499 LWORD S8 Tag2