PROFIBUS Power Hub Segment Coupler 3 (SK3)
Troubleshooting
Symptom
LED "Seg 1" ... "SEG 4" are
flashing red
LED "Seg 1" ... "SEG 4" lights
up constantly red and
LED "DP/ERR" lights up
constantly red
Redundancy switchover
occurs for no apparent reason
No redundancy even though
2 gateway modules are used
11.2
Fault Indicated via DTM
Symptom
Redundancy switchover
occurs for no apparent
reason.
"Redundancy partner
missing"
No redundancy even though
2 gateway modules are used
"Firmware version mismatch" Devices use different firmware
"Firmware updated"
"Hardware error"
60
Possible cause
Address collision: The
■
same address is assigned
to field devices on
2 segments.
BIS address collision: The
■
same address is assigned
to a field device and1 of
the built-in slaves (in case
of redundant board:
address or address + 64).
Hardware error.
Built-in slave has left data
■
exchange.
Inactivity/startup toggle.
■
Gateway module is defective.
Possible cause
Built-in slave has left data
■
exchange
Inactivity/startup toggle
■
No second gateway
■
module plugged into
motherboard
Secondary gateway
■
module has failed
Gateway module is defective.
versions.
Device has not been
rebooted.
Poor signal quality
■
Hardware error
■
Remedy
Change address of
■
PA slave.
Change address of
■
PA slave.
Send gateway to Pepperl+
Fuchs.
Not a fault. See
■
PROFIBUS specification .
Not a fault. While not used,
■
redundant slaves
constantly change their
roles (see PROFIBUS
specification).
Send gateway to Pepperl+
Fuchs.
Remedy
Not a fault. See
■
PROFIBUS specification
Not a fault. While not used,
■
redundant slaves
constantly change their
roles (see PROFIBUS
specification)
Plug second gateway
■
module into motherboard
Replace second gateway
■
module
Send gateway to Pepperl+
Fuchs.
Harmonize firmware versions.
Reboot device. Firmware is
not active until device has
been rebooted.
Perform physical layer
■
diagnostics.
Send gateway to Pepperl+
■
Fuchs.