User Guide
Table Of Contents
- 1. Safety
- 2. Modbus - general info
- 3. Modbus technical data
- 4. Modbus installation
- 5. Programming
- 5.2.1 Ethernet common settings (M5.8.1)
- 5.2.2 Modbus TCP settings (M5.8.2)
- 5.3.1 Modbus RTU Parameters
- 5.3.2 Modbus RTU monitoring values
- 5.4.1 Ethernet common settings
- 5.4.2 Modbus TCP settings
- 5.4.2.1 Common settings
- 5.4.3 Modbus TCP monitoring values
- 5.4.3.1 Connection 1
- 5.4.3.2 Connection 2
- 6.3.1 Coil registers
- 6.3.2 Input discrete registers
- 6.3.3 Holding and input registers
- 6.3.3.1 Drive Application ID’s
- 6.3.3.2 FB Process data IN
- 6.3.3.3 FB Process data OUT
- 6.3.3.4 ID map
- 6.3.3.5 Operation day counter
- 6.3.3.6 Resettable operation day counter
- 6.3.3.7 Energy counter
- 6.3.3.8 Resettable energy counter
- 6.3.3.9 Fault history
Honeywell • 22 Communications
6. Communications
Features of the Modbus-drive interface:
• Direct control of drive (e.g. Run, Stop, Direction, Speed reference, Fault reset)
• Full access to all drive parameters
• Monitor drive status (e.g. Output frequency, Output current, Fault code)
6.1 Data addresses in Modbus messages
All data addresses in Modbus messages are referenced to zero. The first occurrence of a data
item is addressed as item number zero. For example:
• The coil known as ‘Coil 1’ in a programmable controller is addressed as ‘Coil 0000’ in
the data address field of a Modbus message.
• Coil 127 decimal is addressed as ‘Coil 007E hex’ (126 decimal).
• Holding register 40001 is addressed as register 0000 in the data address field of the
message. The function code field already specifies a ‘holding register’operation. There-
fore the ‘4XXXX’ reference is implicit.
• Holding register 40108 is addressed as register 006B hex (107 decimal).
6.2 Modbus memory map
The Honeywell variables and fault codes as well as the parameters can be read and written
from Modbus. The parameter addresses are determined in the application. Every parameter
and actual value have been given an ID number in the application. The ID numbering of the
parameter as well as the parameter ranges and steps can be found in the application manual
in question. The parameter value shall be given without decimals. If several parameters/actual
values are read with one message, the addresses of the parameters/actual values must be
consecutive.
Function
code
Current terminology Access type
Address range
(hex)
TCP/RTU
1 (0x01) Read coils Discrete 00000-0FFFF TCP
2 (0x02) Read Input Discrete Discrete 10000-1FFFF TCP
3 (0x03) Read holding registers 16bit 40000-4FFFF TCP&RTU
4 (0x04) Read input registers 16bit 30000-3FFFF TCP&RTU
5 (0x05) Force single coils Discrete 00000-0FFFF TCP
6 (0x06) Write single register 16bit 40000-4FFFF TCP&RTU
15 (0x0F) Force multiple coils Discrete 00001-0FFFF TCP
16 (0x10) Write multiple registers 16bit 40000-4FFFF TCP&RTU
23 (0x17)
Read/Write multiple
registers
16bit 40000-4FFFF TCP&RTU
NOTE: Broadcasting not supported in TCP.
Broadcast supported with function code 06 and 16 in RTU
Table 12. Supported functions