Sei sulla pagina 1di 11

Modbus Protocol Reference Guide

1 Introduction .....................................................................……….................... 2
2 Modbus Protocol ..........................................................………....................... 2
2.1 General Description .................................…………………………………………………................ 2

2.2 Modbus Message Framing ..................................……………………………………………………... 3


ASCII Framing ..............................……………………………………………...………................ 3
RTU Framing ........……………………………………….............................................………..... 3

Address Field ........................……….............................………………………………………..... 3

Function Field ..................................……….....................................………………………….... 4

Data Field .............................…..................………..................………………………………….. 4

Error Checking Field ............................……………………………………………....................... 4

LRC Checking ..............................................…………………………………………………....... 4

CRC Checking .........................................………………………………………………............... 4

2.3 Modbus Function Formats …...........…........………………………………………………….............. 5


Data Address ...............................…......................…………………………………………......... 5

Coil ................................................….......……………………………………………………........ 5

Input Status ....................................…............…………………………………………………...... 5

Input Register ..................................….............………………………………………………….... 5

Holding Register ..........………………….………………………………....................................... 5

2.4 Field Contents in Modbus Messages .................................................……………......................... 6

3 Modbus Function Codes ...................................................…..................... 7


3.1 Read Holding Register (03) .................................................................……………………….... 7

3.2 Preset Multiple Registers (16, 0X10) …................................................………………………... 7

4 S-CON 800SM Modbus Communications ....………….....................……... 10


4.1 Function Codes ..........................................................................................……………….….... 10

4.2 Register Map …........................................................................................……………..………... 10

4.3 Display Value Description (40001) ……........................................................……….………….... 10

4.4 Display Command & Decimal Point (40009) ……………………………………………………… 11

S-CON 800 SM Modbus Protocol Reference Guide 1


1. Introduction

The Modbus protocol is provided by Modicon Inc. (AEG Schneider Automation International S.A.S.), originally developed for Modicon

programmable controllers. Detailed information is described in Modicon Modbus Protocol Reference Guide

This protocol defines a message structure, regardless of the physical layer such like the type of networks over which they

communicate. The table below shows examples of M-System products which support Modbus and their supported parameters.

Parameters S-CON800SM

Transmission Mode RTU

Transmission Speed 4800 / 9600 / 19200/ 38400 bps

Parity None / Odd / Even

Bit Length 7 or 8

Stop Bit 1 or 2

Node Addresses 1 to 31

Floating Point Data —

Physical Layer RS-485/422

2. Modbus Protocol
2.1 General Description
The Modbus devices communicate using a master-slave technique, in which only one device (the master) can initiate trans-actions

(called ‘queries’). The other devices (the slaves) respond by supplying the requested data to the master, or by taking the action

requested in the query.

The master can address individual slaves, or can initiate a broadcast messages to all slaves. Slaves return a message (called a

‘response’) to queries that are addressed to them individually. Responses are not returned to broadcast queries from the master.

The Modbus protocol establishes the format for the master’s query by placing into it the device (or broadcast) address, a function

code defining the requested action, any data to be sent, and an error-checking field. The slave’s response message is also

constructed using Modbus protocol. It contains fields confirming the action taken, any data to be returned, and an error-checking field.

The figure below illustrates a query-response cycle.

S-CON 800 SM Modbus Protocol Reference Guide 2


Devices can be setup to communicate on standard Modbus networks either of two transmission modes: ASCII (American Standard

Code for Information Interchange) or RTU (Remote Terminal Unit). The mode must be the same for all devices on a Modbus network.

In ASCII mode, each 8-bit byte in a message is sent as two ASCII characters. In RTU mode, each 8-bit byte in a message contains

two 4-bit hexadecimal characters. The RTU mode, with its greater character density, allows better data throughput than ASCII for the

same baud rate.

The checking algorithm used in the Error Check Field depends upon which transmission method is employed; LRC (Longitudinal

Redundancy Check) in ASCII mode; CRC (Cyclical Redundancy Check) in RTU mode.

2.2 Modbus Message Framing

ASCII Framing
In ASCII mode, messages start with a ‘colon’ ( : ) character (ASCII 0X3A), and end with a ‘carriage return – line feed’ (CRLF) pair

(ASCII 0X0D and 0X0A). The allowable characters transmitted for all other fields are hexadecimal 0 – 9, A – F.

When the messages are to be sent over Ethernet, this message frame is handled as a data frame in TCP/IP protocol. Dividing a

message frame is not allowed.

START ADDRESS FUNCTION DATA LRC CHECK END

2 CHARS
1 CHAR : 2 CHARS 2 CHARS nCHARS 2 CHARS
CRLF

Figure 1. ASCII Message Frame

RTU Framing
In RTU mode, messages start with a silent interval of at least 3.5 character times, and end with a similar interval of at least 3.5

character times. This is most easily implemented as a multiple of character times at the baud rate that is being used on the network

(shown as T1 – T2 – T3 – T4 in the figure below).

All other fields are composed of 8-bit data.

START ADDRESS FUNCTION DATA CRC CHECK END

T1–T2–T3–T4 8 BITS 8 BITS nx 8 BITS 16 BITS T1–T2–T3–T4

Figure 2. RTU Message Frame

Address Field
Valid slave device addresses are in the range of 0 – 247 decimal. The individual slave devices are assigned addresses in the range

of 1 – 247. A master addresses a slave by placing the slave address in the address field of the message. When the slave sends its

response, it places its own address in this address field of the response to let the master know which slave is responding. Address 0

is used for the broadcast query.

S-CON 800 SM Modbus Protocol Reference Guide 3


Function Field
Valid function field codes are in the range of 1 – 255 decimal.

When a message is sent from a master to a slave device the function code field tells the slave what kind of action to perform. When

the slave responds to the master, it uses the function code field to indicate either a normal (error-free) response or that some kind of

error occurred (called an exception response). For a normal response, the slave simply echoes the original function code. For an

exception response, the slave returns a code that is equivalent to the original function code with its most-significant bit set to a logic 1.

This tells the master what kind of error occurred, or the reason for the exception.

Whether a particular function code is applicable or not depends upon the slave device. Check specifications for each slave device.

Data Field
The data field of messages sent from a master to slave devices contains information which the slave must use to take the action

defined by the function code. The data field may be of various length, or can be nonexistent (of zero length). Refer to specifications

for each slave device for the constructions and meaning of the data field.

Error Checking Field

ASCII

When ASCII mode is used for character framing the error checking field contains two ASCII characters. The error check characters

are the result of a Longitudinal Redundancy Check (LRC) calculation that is performed on the message content, exclusive of the

beginning ‘colon’ and terminating CRLF characters.

RTU

When RTU mode is used for character framing, the error checking field contains a 16-bit value implemented as two 8-bit bytes. The

error check value is the result of a Cyclical Redundancy Check calculation performed on the message contents.

LRC Checking
In ASCII mode, messages include an error-checking field that is based on a Longitudinal Redundancy Check (LRC) method. The

LRC field checks the contents of the message, exclusive of the beginning ‘colon’ and ending CRLF pair. It is applied regardless of

any parity check method used for the individual characters of the message.

The LRC field is one byte, containing an 8-bit binary value. The LRC value is calculated by the transmitting device, which appends

the LRC to the message. The receiving device calculates an LRC during receipt of the message, and compares the calculated value

to the actual value it received in the LRC field. If the two values are not equal, an error results.

The LRC is calculated by adding together successive 8-bit bytes of the message, discarding any carries, and then two’s

complementing the result. It is performed on the ASCII message field contents excluding the ‘colon’ character that begins the

message, and excluding the CRLF pair at the end of the message.

CRC Checking
In RTU mode, messages include an error-checking field that is based on a Cyclical Redundancy Check (CRC) method. The CRC

field checks the contents of the entire message. It is applied regardless of any parity check method used for the individual characters

S-CON 800 SM Modbus Protocol Reference Guide 4


of the message.

The CRC field is two bytes, containing a 16-bit binary value. The CRC value is calculated by the transmitting device, which appends

the CRC to the message. The receiving device recalculates a CRC during receipt of the message, and compares the calculated value

to the actual value it received in the CRC field. If the two values are not equal, an error results.

The CRC is started by first preloading a 16-bit register to all 1’s. Then a process begins of applying successive 8-bit bytes of the

message to the current contents of the register. Only the eight bits of data in each character are used to generating the CRC. Start

and stop bits, and the parity bit if one is used, do not apply to the CRC.

During generation of the CRC, each 8-bit character is exclusive ORed with the register contents. Then the result is shifted in the

direction of the least significant bit (LSB), with a zero filled into the most significant bit (MSB) position. The LSB is extracted and

examined. If the LSB was a 1, the register is then exclusive ORed with a preset, fixed value. If the LSB was a 0, no exclusive OR

takes place.

This process is repeated until eight shifts have been performed. After the last (eighth) shift, the next 8-bit byte is exclusive ORed

with the register’s current value, and the process repeats for eight more shifts as described above. The final contents of the register,

after all the bytes of the message have been applied, is the CRC value.

When the CRC is appended to the message, the low-order byte of the field is appended first, followed by the high-order byte.

2.3 Modbus Function Formats

Data Address
Data addresses are used in Modbus query messages when reading or modifying data. Four types of data are used: Coil, Input Status,

Input Register and Holding Register.

Coil
Coils are used to force the ON/OFF state of discrete outputs (DO) to the field, or to modify the mode or status of slave devices. Coil

data is either ON or OFF, which can be both read and modified. Valid addresses are in the range of 1 – 9999.

Input Status
Input Status is used for the ON/OFF state of discrete inputs (DI) from the field, or the status of slave devices. The input status is

either ON or OFF, which can be read only. Valid addresses are in the range of 10001 – 19999.

Input Register
Input registers are used for the value of analog inputs (AI) from the field, or the information of slave devices. The input register is of

16-bit long, which can be read only. Valid addresses are in the range of 30001 – 39999. Floating or double-floating data can be

handled when consecutive addresses are assigned.

Holding Register
Holding registers are used for the value of analog outputs (AO) to the field, or to set information of slave devices. The holding register

is of 16-bit long, which can be both read and modified. Valid addresses are in the range of 40001 – 49999. Floating or double-floating

data can be handled when consecutive addresses are assigned.

S-CON 800 SM Modbus Protocol Reference Guide 5


2.4 Field Contents in Modbus Messages
All data addresses in Modbus messages are referenced to 0. The first occurrence of a data item is addressed as item number zero.

For example, the input register 30156 decimal is addressed as register 155 decimal in the message field. The function code field

specifies data type.

Figure 3 shows an example of a Modbus query message. The master query is a Read Holding Registers request (function code 03)

to slave device address 06. The message requests data from three holding registers, 40108 through 40110. Note that the messages

specifies the starting register address as 107 (0X6B hex).

Field Name Example ASCII RTU

(Hex) Characters 8-Bit Field (Hex)

Header : (colon) None

Slave Address 0X06 06 0X06

Function 0X03 03 0X03

Starting Address Hi 0X00 00 0X00

Starting Address Lo 0X6B 6B 0X6B

No. of Registers Hi 0X00 00 0X00

No. of Registers Lo 0X03 03 0X03

Error Check LRC (2 chars.) CRC (16 bits)

Trailer CR LF None

Total Bytes: 17 8

Figure 3. Example of Master Query

Figure 4 is an example of a normal response from the slave to the master query shown in Figure 3. The slave response echoes the

slave address and function code. The ‘Byte Count’ field specifies how many 8-bit data items are being returned. Note that the value

does not represent the actual character count transmitted in either ASCII or RTU mode. In this example, the message contains

three sets of 16-bit data, therefore the ‘Byte Count’ is ‘6’ regardless of the character framing method.

Field Name Example ASCII RTU

(Hex) Characters 8-Bit Field (Hex)

Header : (colon) None

Slave Address 0X06 06 0X06

Function 0X03 03 0X03

Byte Count 0X06 06 0X06

Data 1 Hi 0X03 03 0X03

Data 1 Lo 0XE8 E8 0XE8

Data 2 Hi 0X01 01 0X01

S-CON 800 SM Modbus Protocol Reference Guide 6


Data 2 Lo 0XF4 F4 0XF4

Data 3 Hi 0X00 00 0X00

Data 3 Lo 0X0A 0A 0X0A

Error Check LRC (2 chars.) CRC (16 bits)

Trailer CR LF None

Total Bytes: 23 11

Figure 4. Example of Slave Response

3. Modbus Function Codes

3.1 Read Holding Register (03)

Description

Read the binary contents of holding registers in the slave. Broadcast is not supported. Refer to specifications of the slave device for

data addresses and their contents.

Query

The query message specifies the starting register and quantity of registers to be read. Here is an example of a request to read

registers 40201 – 40203, 3 registers in total, from slave device 7:

Field Name Example ASCII RTU

(Hex) Characters 8-Bit Field (Hex)

Header : (colon) None

Slave Address 0X07 07 0X07

Function 0X03 03 0X03

Starting Address Hi 0X00 00 0X00

Starting Address Lo 0XC8 C8 0XC8

No. of Registers Hi 0X00 00 0X00

No. of Registers Lo 0X03 03 0X03

Error Check LRC (2 chars.) CRC (16 bits)

Trailer CR LF None

Total Bytes: 17 8

Figure 9. Read Holding Register–Query

Response

The register data in the response message are packed as 16 bits per register. Figure 10 shows an example of a response to the

query shown in Figure 9.

S-CON 800 SM Modbus Protocol Reference Guide 7


Field Name Example ASCII RTU

(Hex) Characters 8-Bit Field (Hex)

Header : (colon) None

Slave Address 0X07 07 0X07

Function 0X03 03 0X03

Byte Count 0X06 06 0X06

Data 1 Hi 0X03 03 0X03

Data 1 Lo 0XE8 E8 0XE8

Data 2 Hi 0X01 01 0X01

Data 2 Lo 0XF4 F4 0XF4

Data 3 Hi 0X00 00 0X00

Data 3 Lo 0X0A 0A 0X0A

Error Check LRC (2 chars.) CRC (16 bits)

Trailer CR LF None

Total Bytes: 23 11

Figure 10. Read HoldingRegister-Response

3.2 Preset Multiple Registers (16, 0X10)

Description

Presets values into a sequence of holding registers. When broadcast, the function presets the same register reference in all attached

slaves. Refer to specifications of the slave device for data addresses and their contents.

Query

The query message specifies the register references (the starting register and the data) to be preset. The requested preset values

are specified in the query data field.

Here is an example of a request to preset registers 40020 – 40022 in slave device 5 to the following data:

40020 data 0X0164

40021 data 0X0165

40022 data 0X0166

Field Name Example ASCII RTU

(Hex) Characters 8-Bit Field (Hex)

Header : (colon) None

Slave Address 0X05 05 0X05

Function 0X10 10 0X10

S-CON 800 SM Modbus Protocol Reference Guide 8


Starting Address Hi 0X00 00 0X00

Starting Address Lo 0X13 13 0X13

No. of Registers Hi 0X00 00 0X00

No. of Registers Lo 0X03 03 0X03

Byte Count 0X06 06 0X06

Data 1 Hi 0X01 01 0X01

Data 1 Lo 0X64 64 0X64

Data 2 Hi 0X01 01 0X01

Data 2 Lo 0X65 65 0X65

Data 3 Hi 0X01 01 0X01

Data 3 Lo 0X66 66 0X66

Error Check LRC (2 chars.) CRC (16 bits)

Trailer CR LF None

Total Bytes: 31 15

Figure 25. Preset Multiple Registers – Query

Response
The normal response returns the slave address, function code, starting address, and quantity of registers preset, excluding byte count

and preset data in the query. Figure 26 shows an example of a response to the query shown in Figure 25.

Field Name Example ASCII RTU

(Hex) Characters 8-Bit Field (Hex)

Header : (colon) None

Slave Address 0X05 05 0X05

Function 0X10 10 0X10

Starting Address Hi 0X00 00 0X00

Starting Address Lo 0X13 13 0X13

No. of Registers Hi 0X00 00 0X00

No. of Registers Lo 0X03 03 0X03

Error Check LRC (2 chars.) CRC (16 bits)

Trailer CR LF None

Total Bytes: 17 8

Figure 26. Preset Multiple Registers – Response

S-CON 800 SM Modbus Protocol Reference Guide 9


4. S-CON 800SM Modbus Communications
The model S-CON800S supports only the RTU framing. ASCII mode is not available.

4.1 Function Codes


The following list shows the function codes supported by the R1M.

Code Name* Notes

03 (0X03) Read Holding Register

16 (0X10) Force Multiple Registers

4.2 Register Map

Address Register
Parameter Name Access Notes
(hex) (decimal)

0000 40001 Display Value R/W Long(32bit) –199999 ~ +999999

0002 40003 Display Digit 6 R/W Integer(16bit)-Digit 6(10⁵) 20h~5fH

0003 40004 Display Digit 5 R/W Integer(16bit)-Digit 5(10⁴) 20h~5fH

0004 40005 Display Digit 4 R/W Integer(16bit)-Digit 4(10³) 20h~5fH

0005 40006 Display Digit 3 R/W Integer(16bit)-Digit 3(10²) 20h~5fH

0006 40007 Display Digit 2 R/W Integer(16bit)-Digit 2(10¹) 20h~5fH

0007 40008 Display Digit 1 R/W Integer(16bit)-Digit 1(10⁰) 20h~5fH

Display Command Integer(16bit)-High byte

02 : “-“ / Normal Display

03 : “+”/ Normal Display


0008 40009 R/W 06 : “-“ / Flicker Display

07 : “+” / Flicker Display

Didplay Decimal Point Low byte

0~5 : Decimal Point

4.3 Display Value Description

Display value (40001 – 40002)


- -199999 ~ +999999

-Display 32bit Value(signed long) to ASCII display

Display each one of Digits (40003 - 40007)


- 0x0020 ~ 0x005f

-Each Display Integer 16 bit to Character display

-Numeric display value is 0x0030 ~ 0x0039 ( 0 ~ 9 decimals)

S-CON 800 SM Modbus Protocol Reference Guide 10


4.4 Display Command & Decimal Point (40009)

Command Description (40009 High byte)


Integer(16bit) High byte value

00xxH : Polarity is “+” display of value

02xxH : Polarity is “-” display of value

03xxH : Polarity is “+” display of value

06xxH : Polarity is “+” and Flicker display

07xxH : Polarity is “-” and Flicker display

Decimal Point Description (40009 Low byte)


Integer(16bit) Low byte value

- xx00H ~ xx05H (10⁰,10¹,10²,10³,10⁴,10⁵)

- xx00H -> 999999.

- xx01H -> 99999.9

- xx02H -> 9999.99

- xx03H -> 999.999

- xx04H -> 99.9999

- xx05H -> 9.99999

S-CON 800 SM Modbus Protocol Reference Guide 11

Potrebbero piacerti anche