Manual Protocolo Modbus ME3011b E_r02

8/12/2019 Manual Protocolo Modbus ME3011b E_r02

http://slidepdf.com/reader/full/manual-protocolo-modbus-me3011b-er02 1/52

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 variousME3011b

9

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





Address mapping for reading - formation 10h (2.5 columns) 27 Address mapping for reading - formation 12h (3.0 columns) 28





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.



Manual Modbus ME3011b_E r02.doc 4/5

REVISION CONTROL

Revision Control

Revision Author Date

00 - Initial mol 30/05/2007

01 ama 18/10/2007

02 raf 30/11/2007

2




INTRODUCTION

Dear Customer,

Mauell thanks you for trusting us on choosing our products. It is a pleasure to provide you allnecessary information on the newest member of its Mauell annunciator family.

This manual presents all information needed to configure the Modbus RTU Protocol in order toestablish a serial communication on a network. For advanced users in Modbus parameterization, werecommend the reading start on page 51 of this manual.

Mauell hopes that this manual helps you explore totally the potential of the new ME 3011annunciator.

Please contact us, if any doubt persists about the equipment operation, after reading it. Our technicalteam 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 [email protected]; visit the website www.mauell.com.br; send a fax to +55 11 2117 5354 orcall +55 11 2117 5353.

Important:

In order to help us on our support service have the series number and the firmware version withyou, as these data are essential for clearing the doubts and for technical assistance.

Sincerely,

Helmut Mauell do Brasil

2




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 network’s devices, known as Slaves , just answers to the Master requests, performing theactions 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 registeraddress it must access and the quantity of bytes that must be returned. At the end of the telegram a cyclic redundancycheck 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 thesame of the request telegram, carrying the address of the slave and the function code requested. If the slaveencounters 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 detailedinformation 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 standardnot having this special function. The procedure used doesn’t collide with any protocol statement, and can be used withany master Modbus device. To more detailed explanation about time-stamp acquiring, refer to page 32 of this manual.

2






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:

CM-04:

CX7 – RS-232 with a proprietary protocol, used for communication with configuration software e.Tool ME3011 configor with the supervision software e.Tool ME3011 view.

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

1 Data +

2 Data -CX8

1 TXDT

2 GND

3 RXDT

4 +5 Vcc

CX7

(RJ11)

1 Data +

2 Data -CX8

1 TXDT

2 GND

3 RXDT

4 +5 Vcc

CX7

(RJ11)

2




3.2 – RS-485 line balancing

In order to avoid communication disturbances on RS-485 Modbus, the line balancing must be done. For this, removethe frontal cover from alarm point 4 (to ME3011b rectangular formation) or from alarm point 3 (to ME3011b squareformation) and configure the jumper as following described:

CM-03 (rectangular formation):

JP1 and JP2 closed on the last annunciator connected to the RS-485 busJP1 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 busJP1 and JP2 open for all intermediary annunciators (or 3rd –part devices) connected to the RS-485.

2






MODBUS SLAVE CONFIGURATION

The Modbus parameterization on ME3011b is performed through the software e.Tool ME3011 config. This operationrequires 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” optionin 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) inthe 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 willoccur.

2




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, asdescribed on the following picture:

2




PHYSICAL INPUTS READING

The physical inputs are the field’s signals value and represent the real state of the alarm point. Each bit is an image ofone annunciator’s 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 Code04 (04h) – Read Input Register.

6.1 – Request format

The master’s request must have the following syntax:

ADDHL ADDLO QHI QLO ADD FC

INITIAL ADD.CRC CRC

REGISTERSQTY.

Where:

ADD – Device’s Modbus addressFC – Function Code 04h – Read Input RegisterINITIAL ADD. – Initial register address (2 Bytes), as follows:

- 8000h for first module’s physical inputs reading (alarm point 1 to 60)- 8001h for second module’s physical inputs reading (alarm point 61 to 124)- 8002h for third module’s physical inputs reading (alarm point 125 to 188)- 8003h for fourth module’s 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

REGISTER 4 REGISTER 3 REGISTER 2 REGISTER 1 ADD FCBYTESQTY.

CRC CRC

DATA

Where:

ADD – Device’s Modbus addressFC – Function Code 04h – Read Input RegisterBYTES 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)- BYTE 3 = Register 2 least significant byte (LsB)- BYTE 4 = Register 2 most significant byte (MsB)- BYTE 5 = Register 3 least significant byte (LsB)- BYTE 6 = Register 3 most significant byte (MsB)- BYTE 7 = Register 4 least significant byte (LsB)- BYTE 8 = Register 4 most significant byte (MsB)

CRC – Frame sequence check (CRC16)

For reach the annunciator’s alarm points the following mapping tables must be used, varying according to its physicalformation.

2




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).

2




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

“INITIAL ADD” field of FC-04 (page 12).

2




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

2




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 ADD” field of FC-04 (page 12).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 correspond to the main module (CM-04), thus should be requested using the address 8000h on the

“INITIAL ADD” field of FC-04 (page 12).

2





2





The blue points correspond to the 4th module, thus should be requested using the address 8003h on the “INITIAL ADD” field of FC-04 (page 12).The blue points correspond to the 3rd module, thus should be requested using the address 8002h on the “INITIAL

ADD” field of FC-04 (page 12).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 correspond to the main module (CM-04), thus should be requested using the address 8000h on the “INITIAL ADD” field of FC-04 (page 12).

2





2





The blue points corresponds to the 4th module, thus should be requested using the address 8003h on the “INITIAL ADD” field of FC-04 (page 12).The blue points corresponds to the 3rd module, thus should be requested using the address 8002h on the “INITIAL

ADD” field of FC-04 (page 12).The green points corresponds 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 “INITIAL ADD” field of FC-04 (page 12).

2




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 intwo 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 thatreturns 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.


The master’s request must have the following syntax:


INITIAL ADD.CRC CRC

REGISTER QTY.

Where:

ADD – Device’s Modbus address

FC – Function Code 03h – Read Holding Register

INITIAL ADD. – Initial Memory Address (2 Bytes), as follows:- 0000h for alarm point’s signaling reading of the 1st block (16 points) of the main module- 0001h for alarm point’s signaling reading of the 2nd block (16 points) of the main module- 0002h for alarm point’s signaling reading of the 3rd block (16 points) of the main module- 0003h for alarm point’s signaling reading of the 4th block (16 points) of the main module- 0004h for alarm point’s signaling reading of the 1st block (16 points) of the 2nd module- 0005h for alarm point’s signaling reading of the 2nd block (16 points) of the 2nd module- 0006h for alarm point’s signaling reading of the 3rd block (16 points) of the 2nd module- 0007h for alarm point’s signaling reading of the 4th block (16 points) of the 2nd module- 0008h for alarm point’s signaling reading of the 1st block (16 points) of the 3rd module- 0009h for alarm point’s signaling reading of the 2nd block (16 points) of the 3rd module- 000Ah for alarm point’s signaling reading of the 3rd block (16 points) of the 3rd module- 000Bh for alarm point’s signaling reading of the 4th block (16 points) of the 3rd module- 000Ch for alarm point’s signaling reading of the 1st block (16 points) of the 4th module- 000D9h for alarm point’s signaling reading of the 2nd block (16 points) of the 4th module- 000Eh for alarm point’s signaling reading of the 3rd block (16 points) of the 4th module- 000Fh for alarm point’s 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);


2





The right answer from the annunciator must be:


ADD FCBYTESQTY.

CRC CRCDATA

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 block’s byte- BYTE 7 = MsB Nibble + Lsb Nibble of the 7th requested block’s byte- BYTE 6 = MsB Nibble + Lsb Nibble of the 6th requested block’s byte

- BYTE 5 = MsB Nibble + Lsb Nibble of the 5th

requested block’s byte- BYTE 4 = MsB Nibble + Lsb Nibble of the 4th requested block’s byte- BYTE 3 = MsB Nibble + Lsb Nibble of the 3rd requested block’s byte- BYTE 2 = MsB Nibble + Lsb Nibble of the 2nd requested block’s byte- BYTE 1 = MsB Nibble + Lsb Nibble of the 1st requested block’s byte


2




7.3 - Address mapping for “FC-03 (03h)” - formation 2h (0.5 column) – 44 maximum alarm points

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

2





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

2





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

2





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

2





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

2





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

2





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

2





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

2






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 calculation’s 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 annunciator’s 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.

2




8.1 – Last Registered Event function (LRE)

The function LRE seek in the device’s 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 master’s request must be as follows:


INITIAL ADD.CRC CRC

REGISTERSQTY.

Where:


FC – Function Code 04h – Read Input Register

INITIAL ADD. – Initial register address (2 Bytes), as follows:- 8010h for main module’s last registered event reading- 8011h for 2nd module’s last registered event reading

- 8012h for 3

rd

module’s last registered event reading- 8013h for 4th module’s last registered event reading

REGISTERS QTY. – Quantity of registers (16-bits) requested (always 0004h in this case)


The annunciator’s answer must be:

BYTE16 BYTE15 BYTE14 BYTE13 BYTE12 BYTE11 BYTE10 BYTE9 BYTE8 BYTE7 BYTE6 BYTE5 BYTE4 BYTE3 BYTE2 BYTE 1

T1 T2 T3 T4 T5 - MSB LSB

N/A

CRC ADD FC QBYTES CRC

MEMORY

POSITIONTIMESTAMPDATA

REGISTER 4 REGISTER 3 REGISTER 2 REGISTER 1

Where:


FC – Function Code 04h – Read Input Register

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)- BYTE 14 = Register 3 Most Significant Byte (MsB)- BYTE 13 = Register 3 Least Significant Byte (LsB)- BYTE 12 = Register 2 Most Significant Byte (MsB)

- BYTE 11 = Register 2 Least Significant Byte (LsB)- BYTE 10 = Register 1 Most Significant Byte (MsB)- BYTE 09 = Register 1 Least Significant Byte (LsB)

TIMESTAMP – Clock-data for the last registered event:- BYTE 8 = “T1” – Clock’s Most significant Byte (MsB)- BYTE 7 = “T2”- BYTE 6 = “T3”- BYTE 5 = “T4”- BYTE 4 = “T5” – Clock’s Least significant Byte (LsB)

NA – Reserved Byte;

POINTER – Position of the event in the table:- BYTE 2 = Memory’s pointer Most Significant Byte (MsB)- BYTE 1 = Memory’s pointer Least Significant Byte – (LsB)


2






LOGICAL ALARMS WRITING

The ME3011b alarm annunciator allows the writing of logical alarms through the Modbus protocol. This feature makespossible any master device on a Modbus network (a PLC, for example) sending an alarm indication when an abnormalcondition 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 fordisabling “00h 00h”.

9.1 – Writing format

The writing syntax must have the following format:

ADDHL ADDLO BYTE2 BYTE1 ADD FC

REGISTER ADD.CRC CRC

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



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 logicalcommand (00h00h = OFF).

2





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

2




9.4 – Address mapping for “FC-05 (05h)” - formation 4h (1 column) – 92 maximum alarm points

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 0060h to 007Fh.

2





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

2





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

2





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

2





The yellow points refer to the logical alarms of the main module and represents addresses 0000h to 003BhThe green points refer to the logical alarms of the 2nd module and represents addresses 0040h to 007FhThe blue points refer to the logical alarms of the 3rd module and represents addresses 0080h to 00BFhThe orange points refer to the logical alarms of the 4th module and represents addresses 00D0h to 00FFh

2





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

2





The yellow points refer to the logical alarms of the main module and represents addresses 0000h to 003BhThe green points refer to the logical alarms of the 2nd module and represents addresses 0040h to 007FhThe blue points refer to the logical alarms of the 3rd module and represents addresses 0080h to 00BFhThe orange points refer to the logical alarms of the 4th module and represents addresses 00C0h to 00FFh

2




KEYBOARD REMOTE COMMANDS

The buttons on annunciator’s front - QS, QL, RE, LT - can also be controlled through Modbus protocol. Thesecommands are sent through the Function Code 05 (05h) – Write Single Coil, in the same way done with thelogical alarms described on the previous session. This chapter describes the correct addresses to be used in Modbusconfiguration.

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 fordisabling “00h 00h”.

10.2 – Command Format

The writing syntax must have the following format:

ADDHL ADDLO BYTE2 BYTE1 ADD FC


REGISTERSQTY.

Where:

ADD – Device’s Modbus addressFC – Function Code 05h – Write single coilREGISTER ADD. – Writing address, as follows

- 003Ch to QS button- 003Dh to QL button- 003Eh to RE button

- 003Fh to LT buttonDATA – ON/OFF Command, as follows:

- FF00h to force ON state- 0000h to force OFF state



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 anOFF 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 withoutthe local visualization.

2




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 accessspecial 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 moredetailed 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 HoldingRegisters.


The master’s request must have the following format:



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)



The correct answer must be:


ADD FCBYTESQTY.

CRC CRCDATA

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.


2




11.3 – TABLE 1 – Special Info Registers

2




11.4 – TABLE 2 – Configuration Registers

2




REAL TIME CLOCK SYNC

The RTC (Real Time Clock) of the ME3011 device can be set through a Modbus command. This function must be usedto 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 significantones 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 proceduredescribed 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

T1 T2 T3 T4 T5 - - -REGISTERS Nº

BYTESQTY.

CRC CRCINITIAL ADD.

DATA

ADD FC

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;



The answer must be exactly the same as the Master’s request.

2




QUICK REFERENCE MODBUS MAPPING

13.1 – Reading Functions

Function Code Address16-bits registers

quantityContent

0000h

:

0003h

4 registers Main module's alarm signaling reading

0004h

:

0007h

4 registers Second module's alarm signaling reading

0008h

:

000Bh

4 registers Third module's alarm signaling reading

000Ch

:

000Fh

4 registers Fourth module's alarm signaling reading

0040h 4 registers Special Info Registers (check Table 1)

0050h 4 registers Configuration Registers (check Table 2)

03h


quantityContent

0000h

:0FFFh

8 registers Main module’s registered events reading (1024 events)

1000h

:

1FFFh

8 registers Second module’s registered events reading (1024 events)

2000h

:

2FFFh

8 registers Third module’s registered events reading (1024 events)

3000h

:

3FFFh

8 registers Fourth module’s registered events reading (1024 events)

8000h 4 registers Main module's physical input reading

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 module’s last registered event reading (LRE)

8011h 8 registers Second module’s last registered event reading (LRE)

8012h 8 registers Third module’s last registered event reading (LRE)

8013h 8 registers Fourth module’s last registered event reading (LRE)

04h

2




CONDENSED MODBUS MAPPING

13.2 – Writing functions


quantityContent

0000h

:

003Bh

1 register Main module's logical alarm writing (alarms 1 to 60)

0040h

:

007Fh

1 register Second module's logical alarm writing (alarms 61 to 124)

0080h

:

00BFh

1 register Third module's logical alarm writing (alarms 125 to 188)

00C0h

:00FFh 1 register Fourth module's logical alarm writing (alarms 189 to 252)

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)

05h

Function Code Address 16-bits registers

quantity Content

16h 0000h 4 registers Real Time Clock (RTC) Sync

2



Date post:	03-Jun-2018
Category:	Documents
Upload:	maxdcruz
View:	244 times
Download:	1 times

Manual Protocolo Modbus ME3011b E_r02

Documents