ProSoft Technology ILX69-PBS - Manual (Page 87)

ILX69-PBS ♦ CompactLogix or MicroLogix Platform Contents
PROFIBUS Slave Communication Module User Manual
ProSoft Technology, Inc. Page 87 of 102
March 20, 2015
Error Sources and Reasons
This section describes the typical problems and sources of error that come up while
commissioning the ILX69-PBS.
Behavior Significance Typical Reason Help
CompactLogix™ I/O LED is
flashing green No communication
with the ILX69-PBS (or
other modules) - Modules slot number in
Studio 5000 program does
not match with the
physical slot of the module
- Configured Input / Output
/ Configuration array size
is wrong - Check modules slot number in
Studio 5000 project
- Compare configured Input /
Output size with required values
ILX69-PBS
COM LED is off SYS LED
flashing irregular green Configuration missing
or faulty No configuration or faulty
stored - Check initialization values of the
configuration array
- Check the value "LastError" in
SlaveStatusField to determine the
error reason
Watchdog expired Watchdog value in
configuration is smaller
then RPI (Requested
Packet Intervall) - Increase Watchdog value in
configuration array
- Module has to be reset
ILX69-PBS
COM LED is off and SYS LED
flashing cyclic fast green Application
is not ready - PLC is not in RUN mode
- PLC application has set
the NRDY bit
- PLC has no I/O
communication with the
module - Bring PLC into RUN Mode.
- Check that the PLC application
has deleted the NRDY bit.
-
Check PLC’s I/O LED
Master and slave
Configuration
mismatch The configuration of the
master which wants to
communicate with the
module don’t match to the
configuration of the slave
module - Use the ExtStaInfo in
SlaveStatusField to compare
what the expected configuration
is from the master and the
modules configuration
Network problem No physical network
connection
No master present who
wants to communicate - Check if the slave module is
properly connected to the
PROFIBUS Network
- Check if bus activity can be
detected in "IrqCounter" in
SlaveStatusField
- Check if a master is present
who wants to communicate to the
module and check if the slave
address is correct
Master output data can not be
found in Studio 5000 program Input array mismatch Configured input size in
Studio 5000 to small Check if the configured input size
in Studio 5000 covers the
mandatory size of 136 byte status
data plus the size of the outputs
configured.
Inputs are not transferred to
master although PROFIBUS
is running Output array mismatch Configured output size in
Studio 5000 to small
Check if the configured output
size in Studio 5000 covers the
mandatory size of 4 byte status
data plus the configured
PROFIBUS input data