I/O Diagnostics Interface; Diagnostics Via Ethernet/Ip; Overview Of Diagnostic Data With Explicit Messaging; Diagnostic Steps - Festo CPX-E-EP Translation Of The Original Instructions

Function
If different errors occur simultaneously on different module types, errors cannot be assigned. To
clearly determine errors, the I/O diagnostic interface can be used è 2.4.2 I/O Diagnostics Interface.
You can find detailed information about status bits in the "Description of system CPX-E"
è 1.1 Applicable Documents.
2.4.2

I/O Diagnostics Interface

The system CPX-E provides an I/O diagnostic interface in the form of 16 input bits and 16 output bits
for reading detailed diagnostic information. The I/O diagnostic interface can be used, for example, to
precisely determine the module and channel on which an error has occurred. In order to make use of
the I/O diagnostic interface, the bus module of the system CPX-E must be configured accordingly.
You can find detailed information about the I/O diagnostic interface in the "Description of system CPX-
E" è 1.1 Applicable Documents.
2.5

Diagnostics via EtherNet/IP

The system CPX-E supports the following diagnostic options via the EtherNet/IP protocol.
The following diagnostics options are supported here:
– Explicit messaging via EtherNet/IP Master
– Diagnostics via PLC user program. The I/O diagnostic interface can also be read out here.
2.5.1

Overview of Diagnostic Data with Explicit Messaging

Object Name
class
101 Generic module parameter
d
object
133 Status and diagnostics object
d
134 Diagnostics trace object
d
135 Diagnostics trace status object
d
1) specifies whether diagnostic data are present
Tab. 11
2.5.2

Diagnostic Steps

The necessary steps for performing diagnostics on the system CPX-E are explained below.
Festo — CPX-E-EP — 2020-01a
– Error number of module
– Faulty channel type
– Number of the faulty channel
– Diagnostic status
1)
– Number of the module in which an error has
occurred
– System error number
– Long-term memory (maximum of 40 entries)
– Detailed diagnostics + relative time stamp per
error event
– Number of entries in the diagnostic memory
– Trace status
15