C H A P T E R 6 : M O D B U S T C P P R O T O C O L

CHAPTER 6:

MODBUS TCP PROTOCOL

One of the most popular and well-proven industrial automation protocols in use today is Modbus. Modbus TCP allows the Modbus protocol to be carried over standard Ethernet networks.

6.1MODBUS TCP OVERVIEW

Under the Modbus TCP protocol, the HS500E acts as a Modbus Server and the Host or PLC is the Modbus Client. By utilizing Produce and Consume registers for mapping commands and responses, data produced by the HS500E is consumed by the Modbus Client and data produced by the Modbus Client is consumed by the HS500E.

NOTE:

The Modbus Client (Host or PLC) must connect to the Modbus Server (HS500E) on port 502.

Maximum number of words transferred to/from an RFID tag per read/write cycle:

100 Words / 200 Bytes

6 . 1 . 1 M o d b u s T C P C o m m a n d S t r u c t u r e

M A P P I N G N O D E 0 1 ( C O N S U M E R E G I S T E R S )

Consume Registers hold data destined for the HS500E. Modbus TCP commands must be placed in the holding registers of Device ID 1 (i.e. Node 01), starting at address 40001. Commands utilize at least six registers (double-byte values or words).

 

Modbus

Read / Write

 

Register Description

 

 

Address

Privilege

 

 

 

 

(4xxxx /

 

 

 

 

 

3xxxx)

 

 

 

 

 

 

 

 

 

 

 

(4000) 1

R/W

 

2-byte HS500E Consume Data Overall Length

 

 

 

 

 

(> 0 indicates that data is available; HS500E clears to

 

 

 

 

 

0 after data is processed)

 

 

 

 

 

 

 

 

2

R/W

 

MSB = Reader Type

 

 

 

 

 

LSB = Command ID

 

 

 

 

 

 

 

 

3

R/W

 

MSB = 0x00

 

 

 

 

 

LSB = Node ID (0x01)

 

 

 

 

 

 

 

 

 

H S 5 0 0 E – O P E R A T O R ’ S M A N U A L

P / N : 1 7 - 1 3 0 5 R E V 0 2 ( 1 2 - 0 5 )

 

 

 

 

P A G E 5 2 O F 8 2

Page 52
Image 52
Emsa HS500E manual Modbus TCP Overview, O d b u s T C P C o m m a n d S t r u c t u r e, Words / 200 Bytes, 4000