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 • 36 Fault tracing
Figure 10. Fault tracing diagram for Modbus TCP
Drive does not
start from the bus
Check communi-
cation status (par.
5.7.3.2.1/5.8.3.2.2)
Counter does not
run
Counter for bad
frames (see Table
3) increases
Counter OK.
No communication
Poor
communication
Is the device in
READY state?
Check the led on
keypad
Check external
interlockings (I/O)
Is fieldbus selected
as control place?
Check parameter
M1.15 or P3.2.1
Does Master give
RUN command?
Use keypad to
monitor variable
M5.7.3.2.5
Set variable AV36
to ‘1’
Check fieldbus
parameters
Check other field-
bus parameters in
menu M5.8
Check selected
protocol (M5.7.1.1)
Check Master’s
parameters
Check IP address,
gateway etc.
Check cabling
Check cable for
cuts
Check correct place-
ment of conductors
in terminals
Other bus devices
Check other
necessary devices
(e.g. switches)
Check cabling
Check distances
between cables,
see chapter 4.2.
Check cable types
and lengths, see
chapter 3.
Check connections
Check stripping of
cables and
conductors, see
chapter 4.
Check e.g WLAN or
other routers