⮫ “DIAG - reading out diagnosis messages”.
|
Entry |
Length [byte] |
Values |
Description |
Display |
|---|---|---|---|---|
|
Error severity |
1 |
0 .. 255 |
Used values: 1, 2, 3, 4, 11⮫ “Error severity” |
Ex abc |
|
Hardware ID (HwId) |
1 |
0 .. 255 |
Location of diagnosis, e.g., subdevice, as three-letter word⮫ Further information |
Ex abc |
|
Error code |
2 |
1 .. 65535 |
Error number (low word) |
12345 |
|
SubSysteminfo byte 1 |
1 |
0 .. 255 |
Depends on hardware ID |
d1 123 |
|
SubSysteminfo byte 2 |
1 |
0 .. 255 |
Depends on hardware ID |
d2 123 |
|
SubSysteminfo byte 3 |
1 |
0 .. 255 |
Depends on hardware ID |
d3 123 |
|
SubSysteminfo byte 4 |
1 |
0 .. 255 |
Depends on hardware ID |
d4 123 |
The display of the processor module does not show any communication modules or fieldbus diagnosis. To view these diagnosis messages use Automation Builder or IEC application.
⮫ “Diagnosis in Automation Builder”
⮫ “Diagnosis in IEC application”
This is valid for the following:
-
all external communication modules including safety processor module
-
CANopen on onboard CAN interface
-
fieldbuses on Ethernet interfaces ETH1/ETH2 like PROFINET IO controller, EtherCAT master, etc.
The location of a diagnosis is shown in the CPU display with 3 characters.
|
Display |
Location of diagnosis |
|---|---|
 |
CPU |
 |
CPU RAM |
 |
CPU flash |
 |
CPU flash disk |
 |
CPU memory card |
 |
CPU display |
 |
CPU battery |
 |
Real-time clock (RTC) |
 |
Floating point unit (FPU) |
 |
Power supply |
 |
Communication module 1 |
 |
Communication module 2 |
 |
Communication module 3 |
 |
Communication module 4 |
 |
Communication module 5 |
 |
Communication module 6 |
 |
COM1 serial interface 1 |
 |
COM2 reserved for serial interface 2 |
 |
CAN interface |
 |
I/O bus |
 |
Ethernet ETH1 |
 |
Ethernet ETH2 |