Badger Basket ModMag M2000 User manual

®Badger Meter Europa GmbH
ModMAG®M2000
Profibus®DP
INSTALLATION AND
OPERATION MANUAL
December 2016
MID_M2000_BA_02_PB_1612

Contents Page
MID_M2000_BA_02_PB_1612
1.Basic safety recommendations........................................................................................1
2.About this manual .............................................................................................................1 
2.1Definitions ..................................................................................................................1
2.2Scope.........................................................................................................................1 
3.Introduction........................................................................................................................2
4.Installation..........................................................................................................................3
4.1Prerequisites ..............................................................................................................3
4.2Installing the daughterboard ......................................................................................3
5.System configuration........................................................................................................6
5.1Master class 1............................................................................................................7
5.2Master class 2............................................................................................................7
5.3General station data (GSD) files for master class 1 devices .....................................7
5.4Cyclic data exchange.................................................................................................7
5.5Identity numbers ........................................................................................................9
5.6Network baud rate......................................................................................................9
5.7Dependent device network address...........................................................................9
6.Data management............................................................................................................10
6.1Physical block ..........................................................................................................10
6.2Transducer block .....................................................................................................12
6.3Profibus®transducer block indexes (SLOT 1) by category ......................................12
6.4Analog input functional block ...................................................................................20
7. Compliance.......................................................................................................................22
8. History...............................................................................................................................23
9. Return of goods for repair / Harmlessness declaration ...............................................23

Basic safety recommendations / About this manual Page 1/23
MID_M2000_BA_02_PB_1612
1. Basic safety recommendations
Please see “Basic safety recommendations” in installation and operation manual
ModMAG® M2000.
2. About this manual
2.1 Definitions
2.2 Scope
This document shall discuss the supported features of Profibus®DP, how these features
are related to the ModMAG®M2000, and the special considerations and type of data that
is accessible over Profibus®DP.This document assumes general understanding of the
Profibus®DP protocol by the reader. For further information regarding the Profibus®DP
protocol, refer to www.PROFIBUS.com.
The ModMAG®M2000 Profibus®DP daughterboard supports Profibus®DPV1 protocol.
This is an extended protocol that allows for acyclic communication for parameter
configuration.
In addition, the ModMAG®M2000 Profibus®DP daughterboard supports PA profile
version 3.0.
DD Device description
DP Profibus®protocol for (D)ecentralized or distributed (P)eripherals.
Defines the basic function related to cyclic data exchange.
DPV1 Extended function of Profibus®DP that allows acylic communication
for parameter configuration. DP is traditionally ony suited for transfer
of measured variables.
DTM Device type manager
GSD General station data file. Driver file that defines the behavior of the
Profibus® DP device over Profibus®. The driver file describes
capabilities like data-rates, dynamic variables, etc. A Profibus®DP
master uses the GSD file to start cyclic communication with the
device.
PA profile The PA profile standardizes the basic functions for all the different
Profibus®devices.
SPS Alternate abbreviation for PLC (Programmable Logic Controller)
User units Defined by configuration of the meter’s volume unit or flow unit

Introduction Page 2/23
MID_M2000_BA_02_PB_1612
3. Introduction
Profibus®is an international, vendor-independent bus standard for a wide range of
applications in manufacturing, production, process and building automation, and other
automation control industries.
The Profibus®family comprises three types of protocol, Profibus®DP, Profibus®PA and
Profibus® S-FMS and each is used for different tasks. Only Profibus® DP is considered in
this document.
Profibus®DP (Decentralized Periphery) is a rapid and low cost communication connection
designed for high speed data transmission. Profibus®DP is accomplished with a
ModMAG®M2000 through a Profibus®DP to ModBus®RTU signal conversion board,
referred to as the Profibus®DP daughterboard throughout the remainder of this document.
Figure 1: Profibus® DP to ModBus®RTU commands
ModMAG®
M2000 DSP
Profibus®
daughter
board
Intelligent
host
Profibus
®
DPModBus
®
RTU

Installation Page 3/23
MID_M2000_BA_02_PB_1612
4. Installation
4.1 Prerequisites
Installing a Profibus®DP daughterboard into a ModMAG®M2000 requires firmware
revision v1.10 or later.
4.2 Installing the daughterboard
The Profibus®DP daughterboard connects to the 11-pin connector labeled COMMUNI-
CATION on the main amplifier.
Figure 2: Daughterboard connection
Follow these steps to install the daughterboard:
1. Prior to installing the daughterboard, verify or configure the ModMAG®M2000
communication port B. Access the port settings at main menu > communications > port
B settings.
Parameter Value Comments
Port address 001 Mandatory value of 001
Extended port address — Application specific. Sets Profibus®DP
address of module
Baud rate 38400 Profibus®DP daughterboard auto-bauds
Data bits 8 Mandatory value of 8
Parity EVEN Mandatory value of EVEN
Stop bits 1 Mandatory value of 1

Installation Page 4/23
MID_M2000_BA_02_PB_1612
2. Power off the ModMAG®M2000.
DISCONNECT THE INPUT POWER BEFORE ACCESSING THE EQUIPMENT.
This step is important for the ModMAG®M2000 to properly recognize the Profibus®DP
daughterboard.
3. Prior to inserting the daughterboard, install the foam insulation pad as shown in figure
3. Be sure to align the groove with the two screws attaching the detector or wall mount
bracket to the enclosure. The primary purpose of this pad is to ensure the daughter-
board is insulated from the enclosure wall. It is important to install this pad flush with
the top of the enclosure wall.
Figure 3: Installing foam insulation pad
4. Insert the 8-pin daughterboard into the 11-pin connector.
5. Use the following information to make appropriate wiring of analog wires for signals to
the 7-pin customer connector.
Pin number Pin description Comments
51 RXD/TXD-P Receive data / transmission
data – plus
52 RXD/TXD-N Receive data / transmission
data – negative
53 Shield —
54 RXD/TXD-P Receive data / transmission
data – plus
55 RXD/TXD-N Receive data / transmission
data – negative
56 Shield —
57 Chassi —
Apply insulation pad
flush with the top of the
housing.

Installation Page 5/23
MID_M2000_BA_02_PB_1612
Figure 4: Signal wiring diagram
If several devices need to be connected, please loop them all through input terminal
51/52/53 and output terminal 54/55/56. The integrated bus termination must be activated
on the last device (DIP switch 1 to 4 on “Close”).
6. Power on the ModMAG®M2000.
7. Allow time for the daughterboard to properly power up and be recognized by the
ModMAG® M2000 before navigating the menus. This time is typically 5 seconds. If the
Profibus®DP daughterboard is not recognized, then the ModMAG® M2000 should be
power cycled.
8. Verify recognition of the Profibus®DP daughterboard. Navigate to main menu > info >
help. The daughterboard Info field indicates the daughterboard type is Profibus®DP.
390Ω220Ω390Ω
5V
RXD/TXD-P
RXD/TXD-N
„Close“
„Open“
Switch S1
PCB
Fastening screw
Chassi
Shield
51 52 53 54 55 56 57
FB
FB
FB FB
GND
Shield
PROFIBUS cable Green – A-scale
Red – B-scale

System configuration Page 6/23
MID_M2000_BA_02_PB_1612
5. System configuration
The network diagram below illustrates a typical network configuration of Profibus®devices
with an RS485 interface. The Profibus®devices with an RS485 interface do not need any
segment coupler. These devices can connect directly to the Profibus®DP network.
The maximum cable length in a segment depends on the transmission speed. The
Profibus®DP daughterboard communicates at speeds from 9.6 kBps to 6 Mbps over
distances from 100 to 1200 meters.
Baud Rate (pbs) 9.6
K
19.2
K
93.75
K
187.5
K
500
K
1.5 M 6M
Length (m) 1200 1200 1200 1000 400 200 100
The Profibus®DP protocol has two distinct modes of operation - cyclic data-exchange
mode and acyclic configuration mode. Two types of master devices are defined in a DPV1
network.
Figure 5: Typical network configuration
SPS or PLC
(master class 1)
PC with Siemens
PDM (master class 2)
Profibus
®
DP with max. 6 Mbits/s
ModBus
®
RTU
IMPORTANT: Only two master connections are supported ModMAG®
M2000
Profibus®DP
daughter-
board
Other Profibus
®
DP
(RS485 devices)
Profibus USB
Interface

System configuration Page 7/23
MID_M2000_BA_02_PB_1612
5.1 Master class 1
Master class 1 devices can read and write to variables within the dependent device
cyclically. The master class 1 device will also support acyclic read and write services to
application parameters in the dependent device. The dependent device offers such
services only to the master device that has set the device into cyclic data exchange and
only when it is in cyclic data exchange.
A master class 1 device is typically a process controller (PLC or SPS) that is performing
control functions based on continuously updated measurement variables.
5.2 Master class 2
Master class 2 devices typically establish connections to the dependent device. Through
this connection the master device will be able to manipulate application parameters of the
dependent device.
A master class 2 device is typically a configuration station (laptop/PC with configuration
management software). Master class 2 devices are capable of configuring the device and
may operate on all network accessible parameters within the PA profile.
5.3 General station data (GSD) files for master class 1 devices
The GSD files contain information that will be needed for project planning of the Profibus®
communication network and are downloadable via the internet.
GSD files describe the capabilities of the Profibus®DP device. For example, the baud
rates supported by the slave device are listed in the GSD file.
Configuration type Identity number GSD file name
Profibus®3.0 PA profile
configuration
0x9700 PA139700.GSD
Manufacture specific
configuration
0x0D01 BD020D01.GSD
5.4 Cyclic data exchange
During network configuration the user defines which data should be transferred cyclically
to the master from the dependent device. This is performed through the bus configuration
tool for the PLC or SPS. Network configuration will be done using one of the supported
GSD files (PA139700.GSD or BD020D01.GSD).
The PA profile configuration cyclically transfers the analog input function block as defined
by the GSD file, PA139700.GSD. The Profibus®DP daughterboard associates the
meter’s flow rate [User Units] with the analog input function block. This is the only dynamic
variable that can be cyclically exchanged using the PA profile configuration.
The manufacture specific configuration allows for selection of up to 12 dynamic variables
to be transmitted cyclically. The table below defines configurable data that can be
exchanged cyclically.

System configuration Page 8/23
MID_M2000_BA_02_PB_1612
Slot
assignment
(see GSD)
Dynamic
variable Units Number of bytes
Supported
configurations
1 Flow rate User Units 5 0x94 or 0x42 84 08 05
2 Flow velocity m/s 4 0x93
3 T1/T+ User Units 4 0x93
4 T2/T– User Units 4 0x93
5 T3/TN User Units 4 0x93
6 Digital input
status — 2 0x91
7 Flow direction — 2 0x91
8 Relative flow
rate % 4 0x93
9 Preset batch
totalizer m3 4 0x93
10 Preset batch
totalizer User Units 4 0x93
11 Power loss
totalizer seconds 4 0x93
12 Meter Error — 4 0x93
Total: 45 bytes (maximum)
Below the definition of the dynamic variable no. 12. “Meter Error”:
Byte Bit Supported Bit description
0
0
Yes
Detector error
1 Empty pipe error
2 Full scale flow error
3 Totalizer rollover error
4 Totalizer rollover status
5 Flow simulation status
6 Pulse synchronization warning
7 ADC interrupt error
1 0 Yes ADC range error
1-7 ——
2 0-7 ——
3 0-7 ——
4
0 Yes Internal communication failure – sensor electronics
have not responded to ModBus requests.
1 Yes Configuration error
2-7 ——

System configuration Page 9/23
MID_M2000_BA_02_PB_1612
The Profibus®DP daughterboard supports zero module configuration (0x00) to allow the
possibility of leaving a dynamic variable out of cyclic data exchange when using
manufacture-specific configurations.
IMPORTANT
For both types of supported network configurations, modification of the display units [User
Units] will have an immediate effect on the data transferred over Profibus®.
IMPORTANT
For best performance of the Profibus®DP daughterboard, please ensure the ModBus®
RTU baud rate for Port B is set to 38400.
5.5 Identity numbers
The Profibus®DP daughterboard is based on the Profibus®PA orofile v3.0. The device
supports two identity numbers.
0x0D01 belongs to GSD file BD020D01.GSD and includes the complete functionality of
the ModMAG® M2000.
0x9700 is a manufacturer independent identity number and belongs to the GSD file
PA139700.GSD. This provides interchangeability of devices (that is, an exchange of
electromagnetic flow meters of different vendors).
5.6 Network baud rate
After power on, a baud rate search is started to detect the current bus speed. It is not
necessary to set the baud rate manually.
If the baud rate is changed during operation, a power cycle of the dependent device is
required to re-establish communication with the master.
IMPORTANT
The Profibus®DP daughterboard only supports baud rates up to 6 Mbs. A baud rate of 12
Mbs is not supported.
5.7 Dependent device network address
A new device will have the address of 126. In order to operate on the network it must be
assigned a bus address in the range of 0 to 125. Normally, the lower addresses will be
assigned for master devices. The address may be changed only when the device is not in
cyclic data exchange mode.
There are two ways to commission the network address of the dependent device:
Using Profibus®DP
Using ModMAG® M2000 menu (port B external node address)

Data management Page 10/23
MID_M2000_BA_02_PB_1612
6. Data management
The Profibus®DP interface is based on the Profibus®PA profile v3.0 and supports the
following blocks:
One physical block – contains parameters defined in PA profile v3.0
One transducer block – contains parameters defined in PA profile v3.0 in addition to
meter specific parameters.
One analog input function block – contains one fixed channel, flow rate [User Units]
6.1 Physical block
The physical block contains general device setup parameters.It is important to describe
the details of the DIAGNOSIS and DIAGNOSIS_EXT parameters of the physical block.
Below is the definition of the supported bits of the DIAGNOSIS parameter.
Bit Bit mnemonic Supported Bit description
0 DIA_HW_ELECTR Yes Hardware failure of electronics
1 DIA_HW_MECH — —
2 DIA_TEMP_MOTOR — —
3 DIA_TEMP_ELECTR — —
4 DIA_MEM_CHKSUM — —
5 DIA_MEASUREMENT Yes Failure in measurement – sensor
failure, set if there is a failure over
ModBus®.
6 DIA_NOT_INIT — —
7 DIA_INIT_ERR — —
8 DIA_ZERO_ERR — —
9 DIA_SUPPLY — —
10 DIA_CONF_INVAL Yes Configuration invalid –
Configuration mismatch between
the Profibus®DP daughterboard
and the sensor electronics
11 DIA_WARMSTART Yes Reset occurred within last 10
seconds
12 DIA_COLDSTART Yes Power cycle occurred within last 10
seconds
13 DIA_MAINTENANCE — —
14 DIA_CHARACT — —
15 IDENT_NUMBER_VIOLA
TION
Yes Wrong identity number
16-30 — — —
31 EXTENSION_AVAILABLE Yes Extension status is available

Data management Page 11/23
MID_M2000_BA_02_PB_1612
Below is the definition of the DIAGNOSIS_EXTENSION parameter.
Byte Bit Supported Bit description
0
0
Yes
Detector error
1 Empty pipe error
2 Full scale flow error
3 Totalizer rollover error
4 Totalizer rollover status
5 Flow simulation status
6 Pulse synchronization warning
7 ADC interrupt error
1
0 Yes ADC range error
1-7 — —
2 0-7 — —
3 0-7 — —
4
0 Yes
Internal communication failure – sensor
electronics have not responded to ModBus®
requests.
1 Yes Configuration error
2-7 — —
5 0-7 — —
The FACTORY_RESET parameter of the physical block is supported. This parameter
index is used to reset the device. Three levels exist based on the value written to this
index.
1 – Factory reset
2506 – Warm start
2712 – Set bus address to 126
Remaining parameter indices of the physical block are out of the scope of this document.
Please refer to Profibus®standards for additional information.

Data management Page 12/23
MID_M2000_BA_02_PB_1612
6.2 Transducer block
Typically, the device description file is used to understand the organization of the meter
specific parameters within the transducer block.
6.3 Profibus®transducer block indexes (SLOT 1) by category
Measurements category
Absolute
index
Relative
index
Write
access level
Index name ModBus
®
register
address
Data type Static
revision
120 10 READ-ONLY T1 / T+ [m3] 0x00CF FLOAT32 —
121 11 READ-ONLY T1 / T+ [User Units] 0x00D3 FLOAT32 —
122 12 READ-ONLY T2 / T- [m3] 0x00D7 FLOAT32 —
123 13 READ-ONLY T2 / T– [User Units] 0x00DB FLOAT32 —
124 14 READ-ONLY T3 / TN [m3] 0x00DF FLOAT32 —
125 15 READ-ONLY T3 / TN [User Units] 0x00E3 FLOAT32 —
126 16 READ-ONLY T1 / T+ Rollver
Counter
0x00E7 UINT16 —
127 17 READ-ONLY T2 / T– Rollover
Counter
0x00E8 UINT16 —
128 18 READ-ONLY Flow Velocity [m/s] 0x00E9 FLOAT32 —
129 19 READ-ONLY Flow Rate [m3/s] 0x00ED FLOAT32 —
130 20 READ-ONLY Flow Rate [User
Units]
0x00F1 DS-33 —
131 21 READ-ONLY Relative Flow Rate [
% ]
0x00F3 FLOAT32 —
132 22 READ-ONLY Preset Batch
Totalizer [m3]
0x00EB FLOAT32 —
133 23 READ-ONLY Preset Batch
Totalizer [User Units]
0x00EF FLOAT32 —
134 24 READ-ONLY Power Loss Totalizer
[ seconds ]
0x0107 UINT32 —
135 25 READ-ONLY Flow Direction 0x012D UINT16 —

Data management Page 13/23
MID_M2000_BA_02_PB_1612
Product identification category
Absolute
index
Relative
index
Write
access level
Index name ModBus
®
register
address
Data type Static
revision
136 26 READ-ONLY Product code 0x0000 UINT16 —
137 27 READ-ONLY Firmware name 0x0009 UCHAR16[16] —
138 28 READ-ONLY Application bersion 0x0019 UCHAR16[10] —
139 29 READ-ONLY Compile date
[MMM:DD:YYYY]
0x0023 UCHAR16[16] —
140 30 READ-ONLY Compile time
[HH:MM:SS]
0x0033 UCHAR16[16] —
141 31 READ-ONLY OTP boot checksum 0x0048 UCHAR16[3] —
142 32 READ-ONLY Flash OS checksum 0x004B UCHAR16[3] —
143 33 READ-ONLY Boot version 0x004E UCHAR16[5] —
144 34 READ-ONLY OS version 0x0053 UCHAR16[4] —
145 35 READ-ONLY Daughterboard major
version
0x0058 UINT16 —
146 36 READ-ONLY Daughterboard minor
version
0x0059 UINT16 —
147 37 READ-ONLY Power on splash line
1
0x005A UCHAR16[11] —
148 38 READ-ONLY Power on splash line
2
0x0156 UCHAR16[11] —

Data management Page 14/23
MID_M2000_BA_02_PB_1612
Meter calibration category
Absolute
index
Relative
index
Write
access level
Index name ModBus
®
register
address
Data type Static
revision
149 39 READ-ONLY Detector diameter 0x006F UINT16 —
150 40 READ-ONLY Detector diameter
other [mm]
0x0070 UINT16 —
151 41 READ-ONLY Detector factor 0x0071 FLOAT32 —
152 42 READ-ONLY Detector offset [m/s] 0x0075 FLOAT32 —
153 43 READ-ONLY Amplifier factor 0x0079 FLOAT32 —
154 44 READ-ONLY Detector current [A] 0x007D FLOAT32 —
155 45 SERVICE Power line
Frequency [Hz]
0x0081 UINT16 YES
156 46 ADMIN Excitation frequency
[Hz]
0x0082 UINT16 YES
157 47 SERVICE Scale factor [%] 0x010B FLOAT32 YES
Meter measurement settings category
Digital input category
Absolute
index
Relative
index
Write
access level
Index name ModBus
®
register
address
Data type Static
revision
158 48 USER Flow unit 0x0083 UINT16 YES
159 49 USER Volume unit 0x0084 UINT16 YES
160 50 USER Unit multiplier 0x0085 UINT16 YES
161 51 USER Full scale velocity
[m/s]
0x0086 FLOAT32 YES
240 130 USER Full scale
f
low [User
Units]
0x0090 FLOAT32 YES
162 52 USER Low flow cutoff [%] 0x008E FLOAT32 YES
163 53 USER Flow direction 0x0092 UINT16 YES
164 54 USER Damping
f
actor [s] 0x0093 UINT16 YES
Absolute
index
Relative
index
Write
access level
Index name ModBus
®
register
address
Data type Static
revision
165 55 SERVICE Digital input: nput
operation
0x0094 UINT16 YES
166 56 READ-ONLY Digital input: status 0x0155 UINT16 —

Data management Page 15/23
MID_M2000_BA_02_PB_1612
Output 1 category
Output 2 category
Absolute
index
Relative
index
Write
access level
Index name ModBus
®
register
address
Data type Static
revision
173 63 SERVICE Output #2: Pulses per
unit [User Units]
0x00A9 FLOAT32 YES
174 64 SERVICE Output #2: Pulse width
[ms]
0x00AD UINT16 YES
175 65 SERVICE Output #2: Flow alarm
minimum [%]
0x00AE UINT16 YES
176 66 SERVICE Output #2: Flow alarm
maximum [%]
0x00AF UINT16 YES
177 67 SERVICE Output #2: Output
mode
0x00B0 UINT16 YES
178 68 SERVICE Output #2: Output
operation
0x00B1 UINT16 YES
Absolute
index
Relative
index
Write
access level
Index name ModBus
®
register
address
Data type Static
revision
167 57 SERVICE Output #1: Pulses per
unit [User Units]
0x009C FLOAT32 YES
168 58 SERVICE Output #1: Pulse width
[ms]
0x00A0 UINT16 YES
169 59 SERVICE Output #1: Flow alarm
minimum [%]
0x00A1 UINT16 YES
170 60 SERVICE Output #1: Flow alarm
maximum [%]
0x00A2 UINT16 YES
171 61 SERVICE Output #1: Output
mode
0x00A3 UINT16 YES
172 62 SERVICE Output #1: Output
operation
0x00A4 UINT16 YES

Data management Page 16/23
MID_M2000_BA_02_PB_1612
Output 3 category
Absolute
index
Relative
index
Write
access level
Index name ModBus
®
register
address
Data type Static
revision
179 69 SERVICE Output #3: Full scale
frequency [Hz]
0x00B2 UINT16 YES
180 70 SERVICE Output #3: Flow
alarm minimum [%]
0x00B3 UINT16 YES
181 71 SERVICE Output #3: Flow
alarm maximum [%]
0x00B4 UINT16 YES
182 72 SERVICE Output #3: Output
mode
0x00B5 UINT16 YES
183 73 SERVICE Output #3: Hardware
select
0x00B6 UINT16 YES
184 74 SERVICE Output #3: Output
operation
0x00B7 UINT16 YES
Output 4 category
Absolute
index Relative index Write access level Index name ModBus
®
register
address
Data type Static
revision
185 75 SERVICE Output #4: Flow alarm
minimum [%]
0x00B8 UINT16 YES
186 76 SERVICE Output #4: Flow alarm
maximum [%]
0x00B9 UINT16 YES
187 77 SERVICE Output #4: Output
mode
0x00BA UINT16 YES
188 78 SERVICE Output #4: Hardware
select
0x00BB UINT16 YES
189 79 SERVICE Output #4: Output
operation
0x00BC UINT16 YES

Data management Page 17/23
MID_M2000_BA_02_PB_1612
Port A diagnostic counters category
Absolute
index
Relative
index
Write
access level
Index name ModBus
®
register
address
Data type Static
revision
190 80 READ-ONLY Port A: Packets
processed
0x00BD UINT16 —
191 81 READ-ONLY Port A: Broadcast
packets
0x00BE UINT16 —
192 82 READ-ONLY Port A: CRC errors 0x00BF UINT16 —
193 83 READ-ONLY Port A: Packets
received
0x00C0 UINT16 —
194 84 READ-ONLY Port A: Packets sent 0x00C1 UINT16 —
195 85 READ-ONLY Port A: Parity errors 0x00C2 UINT16 —
196 86 READ-ONLY Port A: Framing
errors
0x00C3 UINT16 —
197 87 READ-ONLY Port A: Overrun
errors
0x00C4 UINT16 —
198 88 READ-ONLY Port A: Break detects 0x00C5 UINT16 —
Port B diagnostic counters category
Absolute
index
Relative
index
Write
access level
Index name ModBus
®
register
address
Data type Static
revision
199 89 READ-ONLY Port B: Packets
processed
0x00C6 UINT16 —
200 90 READ-ONLY Port B: Broadcast
packets
0x00C7 UINT16 —
201 91 READ-ONLY Port B: CRC errors 0x00C8 UINT16 —
202 92 READ-ONLY Port B: Packets
received
0x00C9 UINT16 —
203 93 READ-ONLY Port B: Packets sent 0x00CA UINT16 —
204 94 READ-ONLY Port B: Parity errors 0x00CB UINT16 —
205 95 READ-ONLY Port B: Framing errors 0x00CC UINT16 —
206 96 READ-ONLY Port B: Overrun errors 0x00CD UINT16 —
207 97 READ-ONLY Port B: Break detects 0x00CE UINT16 —

Data management Page 18/23
MID_M2000_BA_02_PB_1612
Meter diagnostic counters category
Absolute
index
Relative
index
Write
access level
Index name ModBus
®
register
address
Data type Static
revision
208 98 READ-ONLY Power up counter 0x00F5 UINT16 —
209 99 READ-ONLY Detector error
counter
0x00F6 UINT16 —
210 100 READ-ONLY Empty pipe counter 0x00F7 UINT16 —
211 101 READ-ONLY Full scale counter 0x00F8 UINT16 —
212 102 READ-ONLY Totalizer overflow
counter
0x00F9 UINT16 —
213 103 READ-ONLY Pulse sync counter 0x00FC UINT16 —
214 104 READ-ONLY ADC interrupt
counter
0x00FD UINT16 —
215 105 READ-ONLY ADC range counter 0x00FE UINT16 —
216 106 READ-ONLY WDT resets counter 0x00FF UINT16 —
217 107 READ-ONLY WDT location 0x0100 UINT16 —
218 108 READ-ONLY System error # 0x0101 UINT16 —
219 109 READ-ONLY Meter status 0x0106 UINT16 —
220 110 READ-ONLY Action request
overflows
0x0109 UINT16 —
221 111 READ-ONLY Measurement
overflows
0x010A UINT16 —
222 112 READ-ONLY Remote resets 0x0154 UINT16 —
Miscellaneous category
Absolute
index
Relative
index
Write
access level
Index name ModBus
®
register
address
Data type Static
revision
223 113 USER Display backlight
mode
0x010F UINT16 YES
224 114 SERVICE Preset batch amount
[m3]
0x0110 FLOAT32 YES
225 115 USER Menu language
setting
0x0114 UINT16 YES