Manual Modbus ME3011b - E - r02 PDF

Alarm Systems
SERIAL PRODUCTS
Alarm Annunciator
Modbus Protocol Configuration

ME 3011b
1 General information
Revision Control 4
Introduction 5
2 Modbus RTU Protocol Properties

Message exchanging 5
Transmission Modes 5
Telegram format - RTU mode 6
ME3011b - Modbus Function Codes 6
Physical interfaces
RS-232 and RS-485 physical interfaces 7
RS-485 line balancing 8
4 - Modbus Network Architecture

Connection example between a Modbus master and a ME3011b 9
Connection example between a Modbus master and various
9
ME3011b
5 - Modbus Slave Configuration

Enabling Modbus protocol 10
Modbus Address 10
Baud rate 10
Parity 11
Data Bits 11
Stop Bit 11
Saving Modbus configuration in device 11
6 Physical Inputs Reading

Request format 12
Answer format 12
Address mapping for reading - formation 2h (0.5 column) 13
Address mapping for reading - formation 6h (1.5 columns) 15
7 Alarm points signaling reading

Request format 21
Answer format 22
8 Registered Events Reading
Last Registered Event reading (LRE) 31
Any registered event reading 33
9 Logical alarms writing

Writing format 35
Answer format 35
Address mapping for writing - formation 2h (0.5 column) 36
Address mapping for writing - formation 4h (1.0 column) 37
Address mapping for writing - formation 6h (1.5 columns) 38
10 Keyboard Remote Commands

Address mapping for writing keyboard commands 44
Command format 44
Answer format 45
11 Special Registers Reading

Request format 46
Answer format 46
Table 1 - Special Info Registers 47
Table 2 - Configuration Registers 48
12 Real Time Clock Sync (RTC)

Writing format 50
Answer format 50
13 - Quick Reference Modbus Mapping

Reading Functions 51
Writing Functions 52
*This document can be changed without previous advice.

REVISION CONTROL
Revision Control
Revision Author Date
00 - Initial mol 30/05/2007
01 ama 18/10/2007
02 raf 30/11/2007
Manual Modbus ME3011b_E r02.doc 4/52

INTRODUCTION
Dear Customer,
Mauell thanks you for trusting us on choosing our products. It is a pleasure to provide you all
necessary information on the newest member of its Mauell annunciator family.
This manual presents all information needed to configure the Modbus RTU Protocol in order to
establish a serial communication on a network. For advanced users in Modbus parameterization, we
recommend the reading start on page 51 of this manual.
Mauell hopes that this manual helps you explore totally the potential of the new ME 3011
annunciator.
Please contact us, if any doubt persists about the equipment operation, after reading it. Our technical
team is always available to clear any doubt you may deem necessary.
Contact the nearest Mauell unit (please refer to the appendix) or send an email to
mauell@mauell.com.br; visit the website www.mauell.com.br; send a fax to +55 11 2117 5354 or
call +55 11 2117 5353.
Important:
In order to help us on our support service have the series number and the firmware version with
you, as these data are essential for clearing the doubts and for technical assistance.
Sincerely,
Helmut Mauell do Brasil

MODBUS RTU PROTOCOL PROPERTIES
The Modbus protocol is based on a Master-Slave model, where only one device, the Master, can start a transmission,
known as queries. The other networks devices, known as Slaves, just answers to the Master requests, performing the
actions demanded and waiting for a new order. The roles of master and slaves are fixed.
2.1 Message exchanging
On the request telegram, the function code informs to the addressed slave device which action must be performed.
The data bytes contains the detailed information required to the function execution, for example, which register
address it must access and the quantity of bytes that must be returned. At the end of the telegram a cyclic redundancy
check guarantee the quality of the data transmission.
The answer telegram carries the result of the search or action performed by the slave. The telegram header is the
same of the request telegram, carrying the address of the slave and the function code requested. If the slave
encounters any problems when performing the action required, special answers for many types of errors will be sent.
2.2 Transmission modes
The Modbus standard allows two different transmission modes: ASCII (American Code for Information Interchange)
and RTU (Remote Terminal Unit). The ME3011b alarm annunciators family just works with the RTU mode. All detailed
information about the protocol contained in this document refers to this mode.
Through the ME3011b is possible acquire time-stamp information from the annunciators, even the Modbus standard
not having this special function. The procedure used doesnt collide with any protocol statement, and can be used with
any master Modbus device. To more detailed explanation about time-stamp acquiring, refer to page 32 of this manual.

2.3 Telegram format RTU Mode
START ADDRESS FUNCTION DATA CRC STOP
Silence Silence
8 bits 8 bits N x 8 bits 16 bits
3.5 chars 3.5 chars
Address (ID): The Modbus protocol allows slaves with addresses between 1 and 247. The address 0 is reserved
and used by the master for broadcast telegrams, messages sent to the network carrying actions that must be
performed by all connected devices.
Function Code (FC): The identification of the function that must be performed by the slave after a master request.
There are different types of functions, for example, to write and read values or send commands. The next session
shows the function codes implemented in the ME3011b alarm annunciator.
Data: This field is size variable and is determined by the selected function code. It can contain parameters for a
certain function on master request or the data gathered in the slave as the result of a master request.
Cyclic Redundancy Check (CRC): The CRC field checks the telegrams bit sequence in order to guarantee its
consistency. This value is a 16-bit long data calculated by the telegram sender and checked by the receiver, who will
reject the received data if the CRC calculated doesnt match the expected value.
2.4 ME3011b - Modbus Function Codes
The data acquisition and command assignments on ME3011b are performed by the following function codes:
Code 03 (03h) - Read Holding Registers for reading the output states (visualization of the LEDs states) and
for the annunciators parameterization
Code 04 (04h) - Read Input Registers for physical inputs reading and for registered events reading
Code 05 (05h) - Write Single Coil for logical alarms writing and remote commands assignment
Code 16 (10h) Write Multiple Registers for the RTC (real time clock) setting.

PHYSICAL INTERFACES
3.1 RS-232 and RS-485 physical interfaces
The ME3011b alarm annunciator has two physical interfaces for serial communication, as below described:
CM-03:
1 TXDT 1 Data +
CX8
CX7 2 GND 2 Data -
(RJ11) 3 RXDT
4 +5 Vcc
CM-04:
1 TXDT 1 Data +
CX8
CX7 2 GND 2 Data -
(RJ11) 3 RXDT
4 +5 Vcc
CX7 RS-232 with a proprietary protocol, used for communication with configuration software e.Tool ME3011 config
or with the supervision software e.Tool ME3011 view.
CX8 RS-485, used for communication on a MODBUS RTU network.

3.2 RS-485 line balancing
In order to avoid communication disturbances on RS-485 Modbus, the line balancing must be done. For this, remove
the frontal cover from alarm point 4 (to ME3011b rectangular formation) or from alarm point 3 (to ME3011b square
formation) and configure the jumper as following described:
CM-03 (rectangular formation):
JP1 and JP2 closed on the last annunciator connected to the RS-485 bus
JP1 and JP2 open for all intermediary annunciators (or 3rd part devices) connected to the RS-485.
CM04 (square formation):
JP1 and JP2 closed on the last annunciator connected to the RS-485 bus
JP1 and JP2 open for all intermediary annunciators (or 3rd part devices) connected to the RS-485.

MODBUS NETWORK ARCHITECTURE
The assembling of a ME3011b alarm annunciators network is simple but demands some attention on the following
aspects:
- Is recommended the use of twisted pair shielded cables, 24 AWG, on the entire RS-485 bus
- One of the shields extreme must be connected to ground
- Is recommended a maximum of 32 devices on a RS-485 network
- If the Modbus Master (a computer, for example) has a RS-232 interface, a RS-232/RS-485 converter must be used;
- The maximum cable length for the RS-485 network is 1000 meters
- A parallel 130 termination resistor must be connected on the beginning of RS-485 bus (i.e. in the converter) and on
the end of the line (if the last device is a ME3011b the use of the resistor is not necessary, the use of the jumpers
explained on the previous session will perform this action).
4.1 Connection example between a SCADA Modbus Master and one ME3011b alarm annunciator
2 x AWG24 cable
RS-232
RS-485
Data +
Data - Serial cable
RS232/RS485
Converter
4.2 - Connection example between a SCADA Modbus Master and various ME3011b alarm annunciators
RS-485
RS-232
Data +
Data -
2 x 24AWG cable 130

RS232/ RS485
Converter
Serial cable
JP1 and JP2 ON

On the last device

MODBUS SLAVE CONFIGURATION
The Modbus parameterization on ME3011b is performed through the software e.Tool ME3011 config. This operation
requires the connection of the computer where the software is running with the annunciator through the CS-02 cable.
The following procedures must be followed:
5.1 Enabling Modbus protocol
To enable the protocol communication on the ME3011b, call the Communication tab and select the Modbus option
in the checkbox:
Then the protocol parameters will be available for parameterization.
5.2 Modbus address
To address the annunciator, increase or decrease the value on the arrows or type the value (between 1 and 247) in
the box directly:
Remember that the address 0 (zero) is reserved and cannot be used for this purpose.
5.3 - Baud rate
The baud rate must be selected on the list box detailed below:
All devices on the network must be configured with the same baud rate, otherwise failures on communication will
occur.

5.4 - Parity
The parity must be the same for all devices on the network, and is configured on the following list box:
5.5 - Data Bits
The ME3011b alarm annunciator works only with 8 bits of data length, this value cannot be changed.
5.6 - Stop Bit
One or two bits can be selected for the Stop bit function, as described below:
5.7 Saving the Modbus configuration in the device
To write the protocol parameterization on the annunciator the button Send data to annunciator must be pressed, as
described on the following picture:

PHYSICAL INPUTS READING
The physical inputs are the fields signals value and represent the real state of the alarm point. Each bit is an image of
one annunciators alarm point. If the bit has the value 0 (zero) the alarm is not present (off state), while the value
1 (one) represents that the alarm is present (on state).
For input state reading without timestamp information, the Modbus master must request data through Function Code
04 (04h) Read Input Register.
6.1 Request format
The masters request must have the following syntax:
ADDHL ADDLO QHI QLO

ADD FC CRC CRC
REGISTERS
INITIAL ADD.
QTY.
Where:
ADD Devices Modbus address

FC Function Code 04h Read Input Register
INITIAL ADD. Initial register address (2 Bytes), as follows:
- 8000h for first modules physical inputs reading (alarm point 1 to 60)
- 8001h for second modules physical inputs reading (alarm point 61 to 124)
- 8002h for third modules physical inputs reading (alarm point 125 to 188)
- 8003h for fourth modules physical inputs reading (alarm point 189 to 252)
REGISTERS QTY. Quantity of registers (16-bits) requested (always 0004h in this case)
CRC Frame sequence check (CRC16)
6.2 Answer format
The right answer from annunciator must be:
BYTE 8 BYTE 7 BYTE 6 BYTE 5 BYTE 4 BYTE 3 BYTE 2 BYTE 1

BYTES REGISTER 4 REGISTER 3 REGISTER 2 REGISTER 1
ADD FC CRC CRC
QTY.
DATA
Where:

BYTES QTY. Quantity of transmitted bytes (always 08h for this function, representing four 16-bits registers)
DATA State of the alarm points, arranged as follows:
- BYTE 1 = Register 1 least significant byte (LsB)
- BYTE 2 = Register 1 most significant byte (MsB)
For reach the annunciators alarm points the following mapping tables must be used, varying according to its physical
formation.

6.3 Address mapping for FC-04 (04h) - formation 2h (0.5 column) 44 maximum alarm points
All points corresponds to the main module (CM-04), thus should be requested using the address 8000h on the
INITIAL ADD field of FC-04 (page 12).

6.4 - Address mapping for FC-04 (04h) - formation 4h (1 column) 92 maximum alarm points
The green points correspond to the 2nd module, thus should be requested using the address 8001h on the INITIAL
ADD field of FC-04 (page 12).
The yellow points corresponds to the main module (CM-04), thus should be requested using the address 8000h on the

6.5 - Address mapping for FC-04 (04h) - formation 6h (1.5 columns) 44 maximum alarm points

6.6 - Address mapping for FC-04 (04h) - formation 8h (2 columns) 188 maximum alarm points
The blue points correspond to the 3rd module, thus should be requested using the address 8002h on the INITIAL
The yellow points correspond to the main module (CM-04), thus should be requested using the address 8000h on the


The blue points correspond to the 4th module, thus should be requested using the address 8003h on the INITIAL
The blue points correspond to the 3rd module, thus should be requested using the address 8002h on the INITIAL
The yellow points correspond to the main module (CM-04), thus should be requested using the address 8000h on the


The blue points corresponds to the 4th module, thus should be requested using the address 8003h on the INITIAL
The blue points corresponds to the 3rd module, thus should be requested using the address 8002h on the INITIAL
The green points corresponds to the 2nd module, thus should be requested using the address 8001h on the INITIAL
The yellow points corresponds to the main module (CM-04), thus should be requested using the address 8000h on the

ALARM POINTS SIGNALING READING
For alarm points signaling reading the Modbus master must request the information through Function Code 03
(03h) Read Holding Registers.
This function returns the alarm point state as it is currently displayed on the annunciator front. The byte is divided in
two distinct nibbles (4 bits) and its value represents the following states:
BIT 03 BIT 02 BIT 01 BIT 00 REPRESENTATION

0 0 0 0 W/o alarm, LED off
0 0 0 1 W/o alarm, LED blinking fast
0 0 1 0 W/o alarm, LED blinking slow
0 0 1 1 W/o alarm, LED on (steady state)
1 0 0 0 With alarm, LED off
1 0 0 1 With alarm, LED blinking fast
1 0 1 0 With alarm, LED blinking slow
1 0 1 1 With alarm, LED on (steady state)
The alarm points acquisition is performed through a data block reading function, having each block 8 data bytes that
returns the state of 16 alarm points per request.
These blocks addresses increases from 0000h to 000Fh and its quantity is directly proportional to the annunciator size.
7.1 Request format
The masters request must have the following syntax:
ADDHL ADDLO QHI QLO

ADD FC CRC CRC
INITIAL ADD. REGISTER QTY.
Where:
FC Function Code 03h Read Holding Register
INITIAL ADD. Initial Memory Address (2 Bytes), as follows:

- 0000h for alarm points signaling reading of the 1st block (16 points) of the main module
- 0001h for alarm points signaling reading of the 2nd block (16 points) of the main module
- 0002h for alarm points signaling reading of the 3rd block (16 points) of the main module
- 0003h for alarm points signaling reading of the 4th block (16 points) of the main module
- 0004h for alarm points signaling reading of the 1st block (16 points) of the 2nd module
- 0005h for alarm points signaling reading of the 2nd block (16 points) of the 2nd module
- 0006h for alarm points signaling reading of the 3rd block (16 points) of the 2nd module
- 0007h for alarm points signaling reading of the 4th block (16 points) of the 2nd module
- 0008h for alarm points signaling reading of the 1st block (16 points) of the 3rd module
- 0009h for alarm points signaling reading of the 2nd block (16 points) of the 3rd module
- 000Ah for alarm points signaling reading of the 3rd block (16 points) of the 3rd module
- 000Bh for alarm points signaling reading of the 4th block (16 points) of the 3rd module
- 000Ch for alarm points signaling reading of the 1st block (16 points) of the 4th module
- 000D9h for alarm points signaling reading of the 2nd block (16 points) of the 4th module
- 000Eh for alarm points signaling reading of the 3rd block (16 points) of the 4th module
- 000Fh for alarm points signaling reading of the 4th block (16 points) of the 4th module
REGISTERS QTY. Quantity of registers (16-bits) requested (always 0004h in this case);

7.2 Answer format
The right answer from the annunciator must be:

BYTES
ADD FC CRC CRC
QTY.
DATA
Where:
FC Function Code 03h Read Holding Register
BYTES QTY. Quantity of transmitted bytes (always 08h for this function, representing four 16-bits registers);
DATA State of the requested alarm points, where:

- BYTE 8 = MsB Nibble + Lsb Nibble of the 8th requested blocks byte
- BYTE 3 = MsB Nibble + Lsb Nibble of the 3rd requested blocks byte
- BYTE 2 = MsB Nibble + Lsb Nibble of the 2nd requested blocks byte
- BYTE 1 = MsB Nibble + Lsb Nibble of the 1st requested blocks byte

7.3 - Address mapping for FC-03 (03h) - formation 2h (0.5 column) 44 maximum alarm points
The yellow points refer to the 2nd, 3rd and 4th blocks of the main module.

The yellow points refer to the 1st, 2nd, 3rd and 4th blocks of the main module.
The green points refer to the 3rd and 4th blocks of the 2nd module.

The yellow points refer to the 2nd, 3rd and 4th blocks of the main module.

The green points refer to the 1st, 2nd, 3rd and 4th blocks of the 2nd module.
The blue points refer to the 1st, 2nd, 3rd and 4th blocks of the 3rd module.


The orange points refer to the 2nd, 3rd and 4th blocks of the 4th module.


The orange points refer to the 1st, 2nd, 3rd and 4th blocks of the 4th module.

REGISTERED EVENTS READING
The ME3011b alarm annunciator can acquire and register until 1024 events internally. This is an optional item and
must be requested in the order.
There are two ways of retrieve the registered events from the devices memory: the first one is reading the last
registered event in order to know the time of last occurrence and the current memorys pointer status; the other one is
using a command to read the information of a specific memory pointer, allowing the retrieving of all events registered
in the device. With the help of these two functions is possible gathering the registered events of all ME3011b devices,
with high-resolution (1ms) timestamp information.
Each ME 3011 alarm annunciator can handle up to 252 alarm inputs. But these alarms cannot be reached directly
because every unit can be divided in up to four sub-modules, as described in the picture below:
4th Module 3rd Module

64 alarm inputs max. 64 alarm inputs max.
2nd Module Main Module

64 alarm inputs max. 60 alarm inputs max.
All those modules are enclosured in the same case and form only one physical unit; the division is purely logical.
The number of slaves is based on the total number of alarm points of the unit. For example, one 132-alarm point
annunciator is formed by one complete Master module plus one complete Slave 1 module plus one non-complete Slave
2 module. (60+64+8).
Each module (master and slaves) is equipped with an EEPROM memory, responsible for registering alarm changes with
milliseconds precision. All changes of any alarm input are registered in this buffer. Each module can register up to
1000 events in the following format:
8 bytes 5 bytes 1 byte 2 bytes

64 alarm input state Timestamp data Reserved Pointer
Note that a status change in a single alarm input will register the actual status of the entire module (up to 64 points).
The timestamp information is generated by a 5-byte counter, that increments in 1ms steps, starting from 01/01/2000
00:00:00,000.
All live and stored data can be obtained through a communication port with Modbus protocol. There are no live data
for timestamp events. They have to be read from the events register buffer.
Description of event analysis in ME 3011
For a brief description, let us take as an example a 4-alarm annunciator. The last event stored has the following
register:
0000 28/07/2006 14:55:25,000 Reserved 10
The first column refers to the state of the four alarm inputs in the order A4-A3-A2-A1. In this case, all alarms are idle.
After a while, a new event on A2 occurs. The latest register will be as described below:
0010 28/07/2006 15:11:05,346 Reserved 11
Comparing the last two registers the analysis will return:
Event: A2 (rising edge)

Timestamp: 28/07/2006 15:11:05,34

Another example:
0000 28/07/2006 11:15:05,310 Reserved 100

1001 28/07/2006 11:15:25,030 Reserved 101
1000 28/07/2006 11:25:13,101 Reserved 102
0110 28/07/2006 11:25:35,251 Reserved 103
These entries on the events register will result the following list (indexed by the timestamp):
Alarm input Value Timestamp

A1 (rising edge) 1 28/07/2006 11:15:25,030
A4 (rising edge) 1 28/07/2006 11:15:25,030
A1 (falling edge) 0 28/07/2006 11:25:13,101
A2 (rising edge) 1 28/07/2006 11:25:35,251
A3 (falling edge) 1 28/07/2006 11:25:35,251
A4 (falling edge) 0 28/07/2006 11:25:35,251
Formula for timestamp calculation:
T-stamp = T1 x (256)4 + T2 x (256)3 + T3 x (256)2 + T4 x 256 + T5 [seconds]

1024
To make the calculations understand easier, the example below is presented, assuming the hypothetical values T1 =
16, T2 = 135, T3 = 202, T4 = 180 and T5 = 129.
Applying these values on the formula above, it will return: T-stamp = 69333677,13 [seconds]
To extract the year value we make T-stamp = 69333677,13 = 2,198556479 [years]

31536000
Truncating the integer value returns 2 years.
In order to return the number of days, the remainder (0,198556479) must be multiplied for 365:
DAYS = 0,198556479 x 365 = 72,473114884 days. Truncating it again will return 72 days.
The same must be done to find the hour information:
HOURS = 0,473114884 x 24h = 11,354757216 = 11 hours
MINUTES = 0,354757216 x 60m = 21,285432943 = 21 minutes
SECONDS = 0,285432943 x 60s = 17,125976560 = 17 seconds
The fraction that remains on second calculation is the milliseconds information, which must be rounded:
MILISECOND = ROUND (0,125976560) = 126 ms
All those values summed to the annunciators clock initial time (01/01/2005 00:00:00.000) will return the event data:
For this case, the timestamp is 14/03/2007 11:21:17,126.

8.1 Last Registered Event function (LRE)
The function LRE seek in the devices memory of the selected module the last event that was registered.
For the LRE function the Function Code 04 (04h) Read Input Register, must be used.
The Modbus masters request must be as follows:
ADDHL ADDLO QHI QLO

ADD FC CRC CRC
REGISTERS
INITIAL ADD.
QTY.
Where:

- 8010h for main modules last registered event reading
- 8011h for 2nd modules last registered event reading
- 8012h for 3rd modules last registered event reading
- 8013h for 4th modules last registered event reading
REGISTERS QTY. Quantity of registers (16-bits) requested (always 0004h in this case)
The annunciators answer must be:
BYTE16 BYTE15 BYTE14 BYTE13 BYTE12 BYTE11 BYTE10 BYTE9 BYTE8 BYTE7 BYTE6 BYTE5 BYTE4 BYTE3 BYTE2 BYTE 1
REGISTER 4 REGISTER 3 REGISTER 2 REGISTER 1 T1 T2 T3 T4 T5 - MSB LSB

ADD FC QBYTES CRC CRC
MEMORY
DATA TIMESTAMP N/A
POSITION
Where:
BYTES QTY. Quantity of transmitted bytes (always 10h for this function, representing eight 16-bits registers)
DADOS Status of the physical inputs at the moment of the occurrence:

- BYTE 16 = Register 4 Most Significant Byte (MsB)
- BYTE 15 = Register 4 Least Significant Byte (LsB)
TIMESTAMP Clock-data for the last registered event:

- BYTE 8 = T1 Clocks Most significant Byte (MsB)
- BYTE 7 = T2
- BYTE 6 = T3
- BYTE 5 = T4
- BYTE 4 = T5 Clocks Least significant Byte (LsB)
NA Reserved Byte;
POINTER Position of the event in the table:

- BYTE 2 = Memorys pointer Most Significant Byte (MsB)
- BYTE 1 = Memorys pointer Least Significant Byte (LsB)

8.2 Any registered event reading
This function allows the reading of any event registered in the devices internal memory. It works like the LRE function,
but requires an additional parameter: the pointer of the desired event in the memory (ADDHL, ADDLO).
The masters request must be:
ADDHL ADDLO QHI QLO

ADD FC CRC CRC
REGISTERS
INITIAL ADD.
QTY.
Where:
- Main module: from 0000h to 03FFh (event 1 to event 1024)

- 2nd module: from 1000h to 13FFh (event 1 to event 1024)
- 3rd module: from 2000h to 23FFh (event 1 to event 1024)
- 4th module: from 3000h to 33FFh (event 1 to event 1024)
REGISTERS QTY. Quantity of registers (16-bits) requested (0008h in this case)
The annunciators answer must be:
BYTE16 BYTE15 BYTE14 BYTE13 BYTE12 BYTE11 BYTE10 BYTE9 BYTE8 BYTE7 BYTE6 BYTE5 BYTE4 BYTE3 BYTE2 BYTE 1
REGISTER 4 REGISTER 3 REGISTER 2 REGISTER 1 T1 T2 T3 T4 T5 - MSB LSB

ADD FC QBYTES CRC CRC
MEMORY
DATA TIMESTAMP N/A
POSITION
Where:
BYTES QTY. Quantity of transmitted bytes (always 10h for this function, representing eight 16-bits registers);
DADOS Status of the physical inputs at the moment of the occurrence:

TIMESTAMP Clock-data for the last registered event:

- BYTE 8 = T1 Clocks Most significant Byte (MsB)
- BYTE 7 = T2
- BYTE 6 = T3
- BYTE 5 = T4
- BYTE 4 = T5 Clocks Least significant Byte (LsB)
NA Reserved Byte;
POINTER Position of the event in the table:
- BYTE 2 = Memorys pointer Most Significant Byte (MsB)
- BYTE 1 = Memorys pointer Least Significant Byte (LsB)

LOGICAL ALARMS WRITING
The ME3011b alarm annunciator allows the writing of logical alarms through the Modbus protocol. This feature makes
possible any master device on a Modbus network (a PLC, for example) sending an alarm indication when an abnormal
condition is detected. This function forces the state of one single alarm point.
The logical alarm writing is performed by the Function Code 05 (05h) Write Single Coil.
Two data bytes must be sent to the annunciator. To enable the point the value FFh 00h should be written, and for
disabling 00h 00h.
9.1 Writing format
The writing syntax must have the following format:
ADDHL ADDLO BYTE2 BYTE1

ADD FC CRC CRC
REGISTER ADD. DATA
Where:
FC Function Code 05h Write single coil
REGISTER ADD. Writing address (check the tables for proper addressing):
- From 0000h to 003Bh for writing the main module alarm points
- From 0040h to 007Fh for writing the 2nd module alarm points
- From 0080h to 00BFh for writing the 3rd module alarm points
- From 00C0h to 00FFh for writing the 4th module alarm points
DATA ON/OFF Command, as follows:

- FF00h to force ON state
- 0000h to force OFF state
9.2 Answer format
The answer from the annunciator must be identical to the request telegram sent by the master.
ATTENTION: When a logical alarm is set (FFh00h = ON) it can just be unasserted with another logical
command (00h00h = OFF).

The yellow points refer to the logical alarms of the main module and represents addresses 0010h to 003Bh.

9.4 Address mapping for FC-05 (05h) - formation 4h (1 column) 92 maximum alarm points
The green points refer to the logical alarms of the 2nd module and represents addresses 0060h to 007Fh.


The yellow points refer to the logical alarms of the main module and represents addresses 0000h to 003Bh
The green points refer to the logical alarms of the 2nd module and represents addresses 0040h to 007Fh
The blue points refer to the logical alarms of the 3rd module and represents addresses 0080h to 00BFh


The orange points refer to the logical alarms of the 4th module and represents addresses 00D0h to 00FFh


The orange points refer to the logical alarms of the 4th module and represents addresses 00C0h to 00FFh

KEYBOARD REMOTE COMMANDS
The buttons on annunciators front - QS, QL, RE, LT - can also be controlled through Modbus protocol. These
commands are sent through the Function Code 05 (05h) Write Single Coil, in the same way done with the
logical alarms described on the previous session. This chapter describes the correct addresses to be used in Modbus
configuration.
10.1 Address mapping for writing keyboard commands
LT = address 3Fh Lamp test
RE = address 3Eh Reset
QL = address 3Dh Light Quitting
QS = address 3Ch Sound Quitting
Two data bytes must be sent to the annunciator. To enable the button the value FFh 00h should be written, and for
disabling 00h 00h.
10.2 Command Format
The writing syntax must have the following format:
ADDHL ADDLO BYTE2 BYTE1

ADD FC CRC CRC
REGISTERS
REGISTER ADD.
QTY.
Where:

FC Function Code 05h Write single coil
REGISTER ADD. Writing address, as follows
- 003Ch to QS button
- 003Dh to QL button
- 003Eh to RE button
- 003Fh to LT button
DATA ON/OFF Command, as follows:
- FF00h to force ON state
- 0000h to force OFF state
10.3 Answer format
The answer from the annunciator must be identical to the request telegram sent by the master.
ATTENTION: When a button command is set (FFh00h = ON) it will remain in this state until receive an
OFF command (00h00h = OFF). Thus the correct procedure is generating a seconds-long pulse by
software to avoid a continuous button assertion.
The remote quitting function demands a special care because the local alarms will be quitted without
the local visualization.

SPECIAL REGISTERS READING
The ME3011b alarm annunciator is provided with the following special registers:
Address 0040h - Special Info Registers: Inform the status of several internal routines and can be used to access
special flags or internal fault alarms. For a more detailed description about this register take a look on Table 1 (page
46).
Address 0050h Configuration Registers: Return all details of the device configuration parameters. For a more
detailed description about this register take a look on Table 2 (page 47).
To access these special registers the Modbus master must use Function Code 03 (03h) Read Holding
Registers.
11.1 Request format
The masters request must have the following format:
ADDHL ADDLO QHI QLO

ADD FC CRC CRC
REGISTER ADD. REGISTER QTY.
Where:
FC Function Code 03h Read Holding Registers
REGISTER ADD:
Special Info Register Address = 0040h (look Table 1 for more details)
Configuration Registers Address = 0050h (look Table 2 for more details)
REGISTER QTY. Number of requested 16-bits registers = 0004h (8 bytes)
11.2 Answer format
The correct answer must be:

BYTES
ADD FC CRC CRC
QTY.
DATA
Where:
FC Function Code 03h Read Holding Registers
BYTES QTY. Quantity of transmitted bytes (always 08h for this function, representing four 16-bits registers);
DATA Special registers contents, as described on Table 1 on the next page.

11.3 TABLE 1 Special Info Registers

11.4 TABLE 2 Configuration Registers

REAL TIME CLOCK SYNC
The RTC (Real Time Clock) of the ME3011 device can be set through a Modbus command. This function must be used
to synchronize a Modbus network.
The RTC Sync Command is performed with Function Code 16 (10h) Write Multiple Registers.
The telegram must send 8 data bytes. The 5 most significant ones are the clock information, and the 3 least significant
ones are not used. Please, check the syntax description below for correct time synchronization.
To perform the clock calculation and obtain the values for T1, T2, T3, T4 and T5, use inversely the procedure
described on page 32.
12.1 Writing format
The syntax for writing the RTC must be:
ADDHL ADDLO QHI QLO BYTE8 BYTE7 BYTE6 BYTE5 BYTE4 BYTE3 BYTE2 BYTE 1
BYTES T1 T2 T3 T4 T5 - - -
ADD FC CRC CRC
QTY.
INITIAL ADD. REGISTERS N
DATA
Where:
FC Function Code 10h Write Multiple Registers
REGISTER ADD: 0000h
REGISTER QTY. Number of requested 16-bits registers = 0004h (8 bytes)
DATA The clock information, as following described:

- BYTE 1 = Reserved
- BYTE 2 = Reserved
- BYTE 3 = Reserved
- BYTE 4 = T5;
- BYTE 5 = T4;
- BYTE 6 = T3;
- BYTE 7 = T2;
- BYTE 8 = T1;
12.2 Answer format
The answer must be exactly the same as the Masters request.

QUICK REFERENCE MODBUS MAPPING
13.1 Reading Functions
16-bits registers
Function Code Address Content
quantity
0000h
: 4 registers Main module's alarm signaling reading
0003h
0004h
: 4 registers Second module's alarm signaling reading
0007h
0008h
03h :
000Bh
4 registers Third module's alarm signaling reading
000Ch
: 4 registers Fourth module's alarm signaling reading
000Fh
0040h 4 registers Special Info Registers (check Table 1)
0050h 4 registers Configuration Registers (check Table 2)
16-bits registers
quantity
0000h
: 8 registers Main modules registered events reading (1024 events)
0FFFh
1000h
: 8 registers Second modules registered events reading (1024 events)
1FFFh
2000h
: 8 registers Third modules registered events reading (1024 events)
2FFFh
3000h
: 8 registers Fourth modules registered events reading (1024 events)
3FFFh
8000h 4 registers Main module's physical input reading
04h
8001h 4 registers Second module's physical input reading
8002h 4 registers Third module's physical input reading
8003h 4 registers Fourth module's physical input reading
8010h 8 registers Main modules last registered event reading (LRE)
8011h 8 registers Second modules last registered event reading (LRE)
8012h 8 registers Third modules last registered event reading (LRE)
8013h 8 registers Fourth modules last registered event reading (LRE)

CONDENSED MODBUS MAPPING
13.2 Writing functions
16-bits registers
quantity
0000h
: 1 register Main module's logical alarm writing (alarms 1 to 60)
003Bh
0040h
: 1 register Second module's logical alarm writing (alarms 61 to 124)
007Fh
0080h
: 1 register Third module's logical alarm writing (alarms 125 to 188)
00BFh
05h 00C0h
: 1 register Fourth module's logical alarm writing (alarms 189 to 252)
00FFh
003Ch 1 register QS Buttom remote command (Sound Quitting)
003Dh 1 register QL Button remote command (Light Quitting)
003Eh 1 register RE Button remote command (Reset)
003Fh 1 register TL Button remote command (Lamp test)
16-bits registers
quantity
16h 0000h 4 registers Real Time Clock (RTC) Sync

Brazil Representatives and
branches Worldwide
Helmut Mauell do Brasil
Est. Estadual Salvador de Leone, 2998 Abu Dhabi E.A.U. Kuwait
06850-000 Itapecerica da Serra - SP Argentina Malaysia
Tel.: +55 (0) 11 2117 5353 Austria Netherlands
Fax.: +55 (0) 11 2117 5354 Belgium Norway
www.mauell.com.br Czech Republic Poland
mauell@mauell.com.br Denmark Singapore
Finland Spain
France Sweden
Germany Great Britain Switzerland
Hungary Turkey
Helmut Mauell GmbH Iran USA
Am Rosenhgel 17
D-42553 Velbert
Tel.:+49 (0)20 53/1 30
Fax.:+49 (0)20 53/1 36 53
www.mauell.com
info@mauell.com

Manual Modbus ME3011b - E - r02 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual Modbus ME3011b - E - r02 PDF

Uploaded by

Copyright:

Available Formats

Alarm Systems

Modbus Protocol Configuration

2 Modbus RTU Protocol Properties

4 - Modbus Network Architecture

5 - Modbus Slave Configuration

6 Physical Inputs Reading

7 Alarm points signaling reading

9 Logical alarms writing

10 Keyboard Remote Commands

11 Special Registers Reading

12 Real Time Clock Sync (RTC)

13 - Quick Reference Modbus Mapping

*This document can be changed without previous advice.

Manual Modbus ME3011b_E r02.doc 4/52

Helmut Mauell do Brasil

Manual Modbus ME3011b_E r02.doc 5/52

2.1 Message exchanging

2.2 Transmission modes

Manual Modbus ME3011b_E r02.doc 6/52

START ADDRESS FUNCTION DATA CRC STOP

2.4 ME3011b - Modbus Function Codes

Manual Modbus ME3011b_E r02.doc 7/52

CX8 RS-485, used for communication on a MODBUS RTU network.

Manual Modbus ME3011b_E r02.doc 8/52

CM-03 (rectangular formation):

CM04 (square formation):

Manual Modbus ME3011b_E r02.doc 9/52

2 x 24AWG cable 130

JP1 and JP2 ON

Manual Modbus ME3011b_E r02.doc 10/52

5.1 Enabling Modbus protocol

Then the protocol parameters will be available for parameterization.

5.2 Modbus address

5.3 - Baud rate

Manual Modbus ME3011b_E r02.doc 11/52

5.5 - Data Bits

5.6 - Stop Bit

5.7 Saving the Modbus configuration in the device

Manual Modbus ME3011b_E r02.doc 12/52

6.1 Request format

The masters request must have the following syntax:

ADDHL ADDLO QHI QLO

ADD Devices Modbus address

6.2 Answer format

The right answer from annunciator must be:

BYTE 8 BYTE 7 BYTE 6 BYTE 5 BYTE 4 BYTE 3 BYTE 2 BYTE 1

ADD Devices Modbus address

Manual Modbus ME3011b_E r02.doc 13/52

Manual Modbus ME3011b_E r02.doc 14/52

Manual Modbus ME3011b_E r02.doc 15/52

Manual Modbus ME3011b_E r02.doc 16/52

Manual Modbus ME3011b_E r02.doc 17/52

Manual Modbus ME3011b_E r02.doc 18/52

Manual Modbus ME3011b_E r02.doc 19/52

Manual Modbus ME3011b_E r02.doc 20/52

Manual Modbus ME3011b_E r02.doc 21/52

BIT 03 BIT 02 BIT 01 BIT 00 REPRESENTATION

7.1 Request format

The masters request must have the following syntax:

ADDHL ADDLO QHI QLO

ADD Devices Modbus address

FC Function Code 03h Read Holding Register

INITIAL ADD. Initial Memory Address (2 Bytes), as follows: