MODBUS Protocol

User Manual

For use with ProComm Converter

30124-76 Rev. 1.1

December 2, 2020
Table of Contents
SAFETY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Safety Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Safety Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 Protocol Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.1 A Modbus Query as Part of the Application Data Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2.2 Error Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.0 Connecting the RS485 Cable to the Converter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.0 Establishing Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1 Data Word Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2 Converter Parameter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.0 Transmitting / Receiving Commands & Data via MODBUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.0 Converter Data Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.1 RS485 Hardware Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.2 Data Word Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.3 Communication Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.4 Serial Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.5 Data Register Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Page ii 30124-76 Rev. 1.1 | 02DEC2020

 SAFETY

SAFETY
Safety Symbols
Throughout this manual are safety warning and caution information boxes. Each warning and caution box will be identified
by a large symbol indicating the type of information contained in the box. The symbols are explained below:

Safety Warnings

!
WARNING
This symbol indicates important safety information. Failure to follow the instructions can
result in serious injury or death.

i
IMPORTANT
This symbol indicates important information. Failure to follow the instructions can result in
permanent damage to the meter or installation site.

When installing, operating, and maintaining McCrometer equipment where hazards may be present, you must protect
yourself by wearing Personal Protective Equipment (PPE) and be trained to enter confined spaces. Examples of confined
spaces are manholes, pumping stations, pipelines, pits, septic tanks, sewage digesters, vaults, degreasers, storage tanks,
boilers, and furnaces.

!
WARNING!
Incorrect installation or removal of FPI Mag meters can result in serious injury or death. Read the
instructions in this manual on the proper procedures carefully.
WARNING

WARNING!

! Never enter a confined space without testing the air at the top, middle, and bottom of the space. The
air may be toxic, oxygen deficient, or explosive. Do not trust your senses to determine if the air is safe. You
WARNING cannot see or smell many toxic gases.

WARNING!

! Never enter a confined space without the proper safety equipment. You may need a respirator, gas de-
tector, tripod, lifeline, and other safety equipment.
WARNING WARNING!

Never enter a confined space without standby/rescue personnel within earshot. Standby/rescue
! personnel must know what action to take in case of an emergency.
WARNING WARNING!

Pressurized pipes should only be hot tapped, cut, or drilled by qualified personnel. If possible,

! depressurize and drain the pipe before attempting any installation.

WARNING!
WARNING Carefully read all safety warning tags attached to the meter.

At the end of its lifetime, this product shall be disposed of in full compliance with the
environmental regulations of the state in which it is located.

Page 1 30124-76 Rev. 1.1 | 02DEC2020

 Introduction

1.0 Introduction
MODBUS is an application layer communication protocol for client/server communications between devices connected on
different types of buses or networks.
A typical MODBUS network consists of one MASTER and up to 247 SLAVES, each with a unique SLAVE Address from 1 to 247.
The Modbus protocol establishes the format of the manner in which the MASTER communicates with the SLAVE, referred to
as the MASTER query. The SLAVE responds using the Modbus protocol. For the MODBUS protocol, the converter attached
to the McCrometer flow meter has the function of the SLAVE device, and communicates with the MASTER via its RS485
serial port.

IMPORTANT
i Important Note 1: MODBUS communication is only possible on converters factory configured with MODBUS,
unless the converter was ordered with MODBUS installed the converter cannot communicate to the MODBUS
network.
Important Note 2: McCrometer provides technical support for its MODBUS converter wired directly to the MODBUS
network via an RS485 serial port. For any technical assistance for your MODBUS beyond the McCrometer MODBUS
converter or for alternative connection methods such as USD or wireless consult the supplier of that equipment or these
additional resources.
• Modbus.org
• Simplymodbus.ca
• Modbustools.com
• Wikipedia/modbus

2.0 Protocol Conventions

The MODBUS protocol defines a simple Protocol Data Unit (PDU), which is independent of the underlying communication
layers.
The mapping of a MODBUS protocol on specific buses or networks introduces some additional fields in the Application
Data Unit (ADU). (See Figure 1 below.)

ADU

1 byte 1 byte n byte 2 byte

Additional Address Function Code Data Error Check

PDU
Figure 1. Data unit layers

2.1 A Modbus Query as Part of the Application Data Unit

• SLAVE ID
The address of the SLAVE device to communicate with (0 broadcasts to all devices, 1-247 for individual devices). When
the MASTER requests data, the first byte it sends is the SLAVE address. Each SLAVE in a network is assigned a unique unit
address from 1 to 247 (excluding 232, which is reserved). This way each SLAVE knows after the first byte whether or not to
ignore the message. In the graphic above the SLAVE ID is contained in the additional address.
NOTE: the converter cannot have the SLAVE ID of 0.

Page 2 30124-76 Rev. 1.1 | 02DEC2020

 Protocol Conventions
• FUNCTION CODE
The instruction to the SLAVE for the type of action to perform, e.g., write coils, read states, read registers, etc. The second
byte sent by the MASTER is the Function code. It tells the SLAVE which table to access and whether to read from or write to
it. The following table lists the function codes available in McCrometer MODBUS converters.

Function Code Action

04 (04 hex) Read the Converter’s Process Data, Data Log, or Events Log
05 (05 hex) Reset the Converter’s Totalizer, Data Log, or Events Log
08 (08 hex) MODBUS Diagnostics (refer to the MODBUS organization for how to use these)
110 (6E hex) Read/Write ETP Commands
• DATA
The additional information relative to the function code, e.g., discrete
register addresses, quantity of items handled, etc.
MODBUS uses a ‘big-Endian’ representation for addresses and data
items. This means that when a numerical quantity larger than a
single byte is transmitted, the most significant byte is sent first. For
example, if a 16-bit Register (2 bytes) has the value 1234 (hexadecimal)
the first byte sent is 12 (hexadecimal) and the second byte sent is 34
(hexadecimal).
The MASTER of the MODBUS network sees the Converter as a set of
registers of 1 bit or 16 bit. Information is stored in the SLAVE device
in four different tables. Two tables store on/off discrete values (coils)
and two store numerical values (registers). The coils and registers
each have a read-only table and read-write table. Each table has 9999
values.
Single precision floating point data is stored and communicated
following the IEEE-754 standard format.

2.2 Error Check

An error-check value calculated by the sending and the receiving
devices from all the bits in the query.
The MASTER builds the message to send to the serial port and then
adds two bytes (the Cyclic Redundancy Check, or CRC) to the end of
every Modbus message for error detection. Every byte in the message
is used to calculate the CRC using the standard CRC16 algorithm. (See
Figure 2.)

Figure 2. CRC process

Page 3 30124-76 Rev. 1.1 | 02DEC2020

 Protocol Conventions
In normal operation the MASTER makes a request or sends a command to the SLAVE. The SLAVE then responds so that the
response function code equals the request function code, e.g., address, function code, data, CRC, etc. (See Figure 3.)

MASTER SLAVE

Initiate Request
Perform The Action,
Function Code Data Request
Initiate The Response

Function Code Data Response

Receive The Response

Figure 3. Example Of An Error Free MODBUS Transaction

If an error is detected in the transmission an exception code is created to indicate the reason of the error. The exception
function code is the sum of the request function code added to 80 (hexadecimal). In other words, the server returns a code
equivalent to the original function code from the request PDU with its most significant bit set to logic 1. (See Figure 4.)

MASTER SLAVE

Initiate Request

Function Code Data Request Error Detected In The

Action, Initiate An Error

Exception Function Code Exception Code

Receive The Response
Figure 4. Example Of A MODBUS Transaction With An Error

2.2.1 Example of a Master Query Containing an Error

If the MASTER sends a request in the following form: “buff tx: [01][03][AB][CD][00][02][75][D0]”
MASTER query elements:
SlaveID = [01]
Function = [04]
Start addr = [AB][CD]
Num. reg. = [00][02]
Crc 16 = [75][D0]
Assuming there is an error in the MASTER Query, the SLAVE will return the following response containing the modified
function code with the appropriate error code (refer to the attached table for an explanation of error codes).

buff rx:[01][83][02][C0][F1] MODBUS Exception Codes

Code Name
SLAVE response elements:
1 Illegal Function
SlaveID =[01] 2 Illegal Address
Function =[83]
3 Illegal Data Value
Err. code =[02] --------> Exception Code : Illegal Address
Crc 16 =[C0][F1] 4 Server Device Failure
5 Acknowledge Error
6 Server Device Busy
7 Memory parity Error

Page 4 30124-76 Rev. 1.1 | 02DEC2020

 Connecting the RS485 Cable to the Converter

3.0 Connecting the RS485 Cable to the Converter

The RS485 serial interface is used to connect the converter to a network of several instruments. The converter adopts the
MASTER-SLAVE type format for communication. Up to 32 devices can be connected with this interface in a single network
covering a length of up to 4000 feet with only two wires. It has excellent immunity to electrical disturbance. The RS485
port is suitable for even long distance and network connections because it is galvanically insulated from all other circuits.
Connect the RS485 cable to the terminal block in the converter as shown in Figure 5. Pin 29 is B, pin 28 is A, and pin 26 is
common.
The RS485 network must be terminated by the last device on the network. If the ProComm converter is the last device, set
the termination switch to the ON position.

VC +24V
ELECTRODES RS485 4-20 OUTPUTS

E1 E2 C B A VC AO2 AO1 AOC

Slide DIP

1 2
ON
switches to
ON position
RS485
Termination
Switch

Figure 5. RS485 Data Cable Wiring Diagram For The Flow Meter Converter

Page 5 30124-76 Rev. 1.1 | 02DEC2020

 Establishing Communication

4.0 Establishing Communication

4.1 Data Word Format
The data bytes travelling in serial form on the communication line are enclosed in words which have a fixed length of 10
bits: 1 START BIT, 8 DATA BITS (1 BYTE), and 1 STOP BIT. NOTE: a byte commonly consists of 8 bits.
Each word contains one byte of data plus additional bits which serve to synchronize communication and make it safer.
These extra bits are added automatically in the transmission phase by the transmitter integrated circuit. In the reception
phase, the reverse operation is executed by the receiver integrated circuit: the eight data bits are extracted and the others
are eliminated. These operations are executed entirely on a hardware level. Note that the 8 data bits must be serialized,
starting from bit 0 (the least significant bit). NOTE: communication Flow Control is set to none; no control lines or XON/
XOFF characters are used.

4.2 Converter Parameter Settings

The settings indicated below must be entered in the Communications menu of the converter to establish serial
communication after the serial port is wired. Refer to the ProComm Electromagnetic Flow Meter Installation, Operation
and Maintenance manual for complete instructions (literature number 30124-62). (See Figure 6 below.)
• Device Address [Dev.Addr=]: establishes the address of the converter in the MODBUS network. Options are 1 through
247 (excluding 232, which is reserved).
• Speed [Speed=bps]: establishes serial line communication speed. Options are 1200, 2400, 4800, 9600, 19200, 22800,
38400, 57600, 76800 and 115200
• Parity [Parity=]: establishes parity for the byte frame in MODBUS communication. Options are EVEN (0), NONE (1),
and ODD (2). Set to match the parity of the MODBUS network’s MASTER device.
• Delay [Delay=ms]: establishes converter delay (how long it will wait to answer the MODBUS network’s MASTER).
Options, in milliseconds, are 0 (0), 20 (1), 4 (2), 60 (3), 80 (4), 100 (5), 120 (6) and 140 (7). Typically, set to 0.
• Timeout [C.timeout=]: Maximum delay between chars (frames) MODBUS
•
8-COMMUNICATION
Dev.Addr= 001
Speed=bps 9600
Parity= NO
Delay=ms 00
C.timeout= 2

Figure 6. ProComm Series Converter

Communications Screen

i
IMPORTANT
Important Notes Regarding RS485 Networks:
An RS485 network is comprised of a certain number of devices, each one identified by a unique address number.
Each of these devices is designated a SLAVE with one device in the network, the network “referee”, designated
the MASTER. The MASTER interrogates all of the other instruments connected to the network (the SLAVES) in turn. The
maximum number of devices that can be connected to the network is 32. Information requests sent from the MASTER
are received simultaneously by all the SLAVES, but only the one addressed in the communication replies.
For this reason, it is absolutely necessary that each SLAVE has a different address. As the MASTER establishes the time
scheduling by which the information must transit the network, there must be only one MASTER in the network; two
MASTERs would create conflicts in the communication, making the entire system unusable. MASTER devices can be PCs,
PLCs, or other terminals that collect measurement data from the instruments. The converter is always a SLAVE.
When more than 32 instruments must be networked, the network must be divided into separate groups of a maximum
of 32 devices. Each group connects to the next through a repeater which has the task of regenerating the necessary
electric signals. In any case, given that the converter sets a maximum number of addresses that can be assigned to 247,
networks with more than 246 elements cannot be created (note that address 232 is reserved).

Page 6 30124-76 Rev. 1.1 | 02DEC2020

 Transmitting / Receiving Commands & Data via MODBUS

5.0 Transmitting / Receiving Commands & Data via MODBUS

As described earlier, in the MODBUS protocol the converter functions as a SLAVE device. The MASTER of the network sees
the converter as a set of registers of 1 bit or 16 bit. These registers are addressed and grouped in tables with different
length. The data in these registers are accessed specific function calls.

A transmission from the MASTER to a SLAVE on the MODBUS network has the form as shown in the table below.

CRC16 Error Check

SLAVE ID

Function
Address from which Number of Registers Number
to Start Reading to Read
(see above)

Byte: 1 2 3 4 5 6 7 8
[01] [04] [00] [04] [00] [02] [30] [0A]
Function 4
Device 1

Start at
CRC16: 300A
address 0004 Read 2 Registers
(hexadecimal)
Transmission example, buff tx: (hexadecimal)

A transmission from the SLAVE to a MASTER on the MODBUS network has the form as shown in the table below.
Number of

CRC16 Error Check

SLAVE ID

Function

Bytes (n)

Data from the first Data from the Last Number

Register Queried (1) Register Queried (1)
(see above)

Byte: 1 2 3 4 5 n+4 n+5 n+6 n+7

...
[01] [04] [04] [42] [47] [FF] [CF] [5F] [FA]
Function 4

Data in first register: Data in Last Register:

Device 1

4 Bytes

CRC16: 5FFA
4247 FFCF
(hexadecimal)
(hexadecimal) Hexadecimal
Reply example, buff tx:

Page 7 30124-76 Rev. 1.1 | 02DEC2020

 Converter Data Map

6.0 Converter Data Map

Process data, data logger data, and data logger events are contained in the converter’s memory at specific addresses or
registers and can be accessed by the MODBUS function codes. Following are the maps for process data.

6.1 RS485 Hardware Connection

For the hardware connection see the relative section in this manual and MODBUS manual.

6.2 Data Word Format

The data bytes travelling in serial form on the communication line are enclosed in words which have a fixed length of 10
bits:
1 START BIT
8 DATA BITS = 1 DATA BYTE
1 STOP BIT
Each word contains one byte of data plus additional bits which serve to synchronies and make the communication safer.
These extra bits added automatically in the transmission phase by the transmitter integrated circuit. In the reception
phase, the reverse operation is executed by the receiver integrated circuit: the eight data bits are extracted and the others
eliminated. These operation are executed entirely on a hardware level. The 8 data bits must be serialised staring from bit 0
(the least significant one).

6.3 Communication Speed

The millennium series instruments have 4 communication speeds: 4800 bps
9600 bps
19200 bps
38400 bps

6.4 Serial Port Settings

Serial port setting:
Data bits: 8
Parity: Manu < 7-Comunication >, function - < Parity > Stop bits: 1
Flow control: none (no control lines no xon/xoff characters used)

6.5 Data Register Format

All data are sent in group of 16 bits registers. The format used is BIG ENDIAN, MSB byte is sent first, LSB is sent last. When a
variable is more than 16 bits in size, it uses two adjacent registers. The totalizer values are expressed as integer numbers.
For the correct representation of the value in case there is a fractional part, the decimal dot must be placed in the position
specified by the next variable register following the totalized value. All values relative to the flow rate are averaged. The
number of samples that compose the average value varies depending on the measure sample rate and the MODBUS
reading requests. Example: measure sample rate = 50 Hz, MODBUS reading frequency = 10 Hz, Number of samples used
for average calculation = 50/10 = 5.

Page 8 30124-76 Rev. 1.1 | 02DEC2020

 Converter Data Map
Read process variable : COMMAND 04.

Address Size Type of Data Meaning

0000-0001 2 REGISTERS 32 BITS FLOAT full scale flow rate in the unit of measure chosen (as can
be seen in the display of the instrument)
0002-0003 2 REGISTERS 32 BIT FLOAT flow rate value in percentage
0004-0005 2 REGISTERS 32 BITS FLOAT flow rate value in the unit of measure chosen
0006-0007 2 REGISTERS 32 BITS FLOAT Flow speed in the unit of measure chosen (m/s or ft/s)
0008-0009 2 REGISTERS 32 BITS UNSIGNED LONG Totalizer T+ value
0010 1 REGISTER 8+8 BITS TWO BYTES First byte (MSB): number of overflows recorded, second
byte (LSB): number of decimal places
0011-0012 2 REGISTERS 32 BITS UNSIGNED LONG Totalizer P+ value
0013 1 REGISTER 8+8 BITS TWO BYTES First byte (MSB): number of overflows recorded, second
byte (LSB): number of decimal places
0014-0015 2 REGISTERS 32 BITS UNSIGNED LONG totalizer T- value
0016 1 REGISTER 8+8 BITS TWO BYTES First byte (MSB): number of overflows recorded, second
byte (LSB): number of decimal places
0017-0018 2 REGISTERS 32 BITS UNSIGNED LONG Totalizer P- value
0019 1 REGISTER 8+8 BITS TWO BYTES First byte (MSB): number of overflows recorded, second
byte (LSB): number of decimal places
0020 1 REGISTER 8+8 BITS TWO BYTES first byte (MSB): process flags 1, (LSB): process flags 2
0021 1 REGISTER 16 BITS UNSIGNED SHORT Number of measure samples used for to calculate the
latest read average value of flow rate
0022 1 REGISTER 16 BITS UNSIGNED SHORT Equivalent resistance measured between electrode E1
and the common point, in kilo ohm
0023 1 REGISTER, 16 BITS UNSIGNED SHORT equivalent resistance measured between electrode E2
and the common point, in kilo ohm
0024 1 REGISTER, 16 BITS SIGNED SHORT voltage measured between electrode E1 and the
common point, in millVolts
0025 1 REGISTER, 16 BITS SIGNED SHORT voltage measured between electrode E2 and the
common point, in millVolts
0026 1 REGISTER, 16 BITS UNSIGNED SHORT voltage measured at rechargeable terminals, in milliVolts
0027 1 REGISTER, 16 BITS UNSIGNED SHORT residual battery capacity in percentage
0028 1 REGISTER, 16 BITS SIGNED SHORT CPU temperature in the unit of measure chosen
0029 1 REGISTER, 16 BITS SIGNED SHORT Board temperature T1 the unit of measure chosen
0030 1 REGISTER, 16 BITS SIGNED SHORT Board temperature T2 the unit of measure chosen
0031 1 REGISTER, 16 BITS SIGNED SHORT Flow sensor coil’s temperature the unit of measure
chosen
0032 1 REGISTER, 16 BITS UNSIGNED SHORT latest sensor test result code
0033 1 REGISTER, 16 BITS UNSIGNED SHORT number of alarms currently active

Page 9 30124-76 Rev. 1.1 | 02DEC2020

 Converter Data Map
Meaning and value of the process flags 1 returned with the register 0020 (MSB):
• bit 7 (MSB): flow rate alarm MIN (flow rate below the minimum threshold set)
• bit 6: flow rate alarm MAX (flow rate over the maximum threshold set)
• bit 5: flow rate sign (1 = negative)
• bit 4: flow rate below the cut-off value
• bit 3: measure range active (0= range 1, 1= range 2)
• bit 2: flow rate measure reset value status (1= measure is forcibly reset to zero)
• bit 1: volume counters lock status (1= counters are locked)
• bit 0 (LSB) : internal use, no meaning

Meaning and value of the process flags 2 returned with the register 0020 (LSB):
• bit 7 (MSB): flow rate overflow (value greater than full scale)
• bit 6: pulse channel #2 overflow (frequency greater than maximum possible for the given parameters)
• bit 5: pulse channel #1 overflow (frequency greater than maximum possible for the given parameters)
• bit 4: measure signal amplitude out of A/D converter range
• bit 3: measure signal amplitude out of amplifier capability
• bit 2: input signal error (out of input chain capability)
• bit 1: coils excitation error
• bit 0 (LSB) : pipe empty

Meaning and value of the sensor test flags returned with the register 0021:
• bit 15 (MSB): resistance at electrode E2 is outside the limits respect to the reference value
• bit 14 : resistance at electrode E1 is outside the limits respect to the reference value
• bit 13: coil time B is outside the limits respect to the reference value
• bit 12: coil time A is outside the limits respect to the reference value
• bit 11: coil temperature is outside the limits respect to the reference value
• bit 10: coil leakage current is outside the limit
• bit 09: coil driver output 2 voltage is out of tolerance during test phase 3
• bit 08: coil driver output 1 voltage is out of tolerance during test phase 3
• bit 07: coil driver output 2 voltage is out of tolerance during test phase 2
• bit 06: coil driver output 1 voltage is out of tolerance during test phase 2
• bit 05: coil driver output 2 voltage is out of tolerance during test phase 1
• bit 04: coil driver output 1 voltage is out of tolerance during test phase 1
• bit 03: coil driver power generator voltage is out of tolerance during test phase 2
• bit 02: coil driver power generator voltage is out of tolerance during test phase 1
• bit 01: coil driver power generator value is out of tolerance during test phase 2
• bit 00 (LSB): coil driver power generator value is out of tolerance during test phase 1

Page 10 30124-76 Rev. 1.1 | 02DEC2020

 Converter Data Map
Reset totalizers: COMMAND 05.

Address Size Type of Data Command Value Meaning

0000 1 REGISTER, 16 BITS UNSIGNED SHORT 0XFF00 (HEX) Reset the enabled totalizers
(same totalizer enabled for reset
from digital input).

Diagnostics: COMMAND 08.

Address Size Type of Data Function / Value

0001 1 REGISTER, 16 BITS UNSIGNED SHORT Return query data
0004 1 REGISTER, 16 BITS SIGNED SHORT Restart communication from listen mode
0010 1 REGISTER, 16 BITS SIGNED SHORT Activate listen mode
0011 1 REGISTER, 16 BITS UNSIGNED SHORT Clear diagnostic counters
0012 1 REGISTER, 16 BITS UNSIGNED SHORT Number of total received packets
0013 1 REGISTER, 16 BITS UNSIGNED SHORT Number of received packets with CRC error
0014 1 REGISTER, 16 BITS UNSIGNED SHORT Number of addressed or broadcast received packets
0015 1 REGISTER, 16 BITS UNSIGNED SHORT Number of broadcast received packets
0016 1 REGISTER, 16 BITS UNSIGNED SHORT Number of received packets with NAK flag
0017 1 REGISTER, 16 BITS UNSIGNED SHORT Number of received packets with BUSY flag
0018 1 REGISTER, 16 BITS UNSIGNED SHORT Number of received packets with OVERRUN flag

Page 11 30124-76 Rev. 1.1 | 02DEC2020

 OTHER McCROMETER PRODUCTS INCLUDE:

Propeller Flowmeters

Differential Pressure Flowmeters

Magnetic Flowmeters

DURA MAG ™

Wireless Monitoring System

FlowConnect ™

Copyright © 2001-2019 McCrometer, Inc. All printed material should not be changed or altered without permission of McCrometer. Any published pricing,
technical data, and instructions are subject to change without notice. Contact your McCrometer representative for current pricing, technical data, and instructions.

3255 WEST STETSON AVENUE • HEMET, CALIFORNIA 92545 USA

TEL: 951-652-6811 • 800-220-2279 • FAX: 951-652-3078
www.mccrometer.com
Page 12 30124-76 Rev. 1.1 | 02DEC2020