English (GB)
52
14.1.2 CIM/CIU 200 Modbus communication faults
5. Modbus LED1 is flashing red. a) Fault in the Modbus communication
(fault in parity or cyclic redundancy
check).
• Check the transmission speed, switches
SW4 and SW5.
See section 5.1 Setting the Modbus
transmission speed.
• Check the parity setting, switch SW3.
See section 5.2 Setting the stop bits and
the parity bit.
• Check the cable connection between CIM
200 and the Modbus network.
• Check the termination resistor settings,
switches SW1 and SW2.
See section 5.4 Termination resistor.
Fault Possible cause Remedy
1. The slave does not respond
to telegrams.
a) Configuration or wiring error. • Check the visual diagnostics on the Modbus
slave. Is the Grundfos GENIbus LED flashing
green and the Modbus LED off or flashing
green?
• Ensure that the cable between the Modbus
master and the Modbus slave is connected
correctly. See section 5. CIM 200 Modbus RTU
setup for wiring recommendations.
• Ensure that the slave address is configured
correctly, and that the correct slave address is
used in the Modbus master poll. See section
5.3 Modbus address selection for slave address
selection.
• Ensure that the transmission speed and stop
bit/parity settings are configured correctly in
both master and slave.
• Ensure that each end of the Modbus trunk cable
is terminated, if necessary. See section
5.4 Termination resistor for line termination of
the Grundfos slave.
• Ensure that the bus topology for a Modbus
network is correct.
b) The slave may be in listen-only mode. Either send a restart communications diagnostics
command, or restart the booster system manually.
c) If the holding register of address 00001
"SlaveMinimumReplyDelay" is set too high,
the master may time out before receiving the
response from the slave.
Increase the time-out span in the master in order
to communicate.
2. The slave responds with
exception response 0x01:
"Invalid function".
a) The master is trying to use an unsupported
function in the module or unit.
See section 8. Modbus function code overview for
supported function codes. Note that reading and
writing coils are not supported, so only register
functions and diagnostics will be valid.
3. The slave responds with
exception response 0x02:
"Invalid data address".
a) The master is trying to read or write an invalid
data address. If a master tries to read register
addresses that are not listed in the tables, the
slave responds with this exception response.
Some masters may automatically try to read
large blocks in one telegram, which will cause
problems if some of the registers in the block
are not supported. An example would be
reading the CIM configuration and CIM status
blocks in one telegram. This is not possible
since there are unused addresses between
the blocks.
• Avoid reading or writing invalid data addresses.
• Ensure that register X is addressed as X-1 in
Modbus telegrams, according to the Modbus
standard.
b) The register address offset may have been
changed from default.
Read the holding register at address 00002
"Register Offset" to see if this value is different
from 0. If so, write the value 0 to this address to
make the slave return to the default used in this
functional profile.
4. The slave returns data
value 0xFFFF (65535).
a) The value is unavailable. A data value of
0xFFFF does not necessarily indicate an error
condition. It means that the value is
unavailable from the booster system.
See section 9. Modbus register addresses for
available data.
b) The booster system is not configured to show
the value or lacks a sensor to read the value.
See section 9.7 System data register block for
data values that require a sensor.
Fault (LED status) Possible cause Remedy
To Next Page
Loading...
