315-4PN33

8.13.4 Diagnostics via OB start information
n On an error the faulty system generates a diagnostics message
for the CPU. Then the CPU calls the according diagnostics OB.
Here the CPU operating system transfers start information to the
local data of the OB.
n By evaluating the start information of the according OB you can
get information about cause and location of the error.
n During runtime you can access the start information with the
system function SFC 6 RD_SINFO.
n Please consider that you can even read the start information in
the OB himself, because the data are temporary data.
n Depending on the type of error, the following OBs are called in a
diagnostics event:
–
OB 82 on an error of an module at the IO device (Diagnostics
interrupt)
– OB 83 on inserting respectively removing a module on a IO
device
– OB 86 on failure respectively return of a IO device
More information about the OBs and their start information
may be found in the online help of your programming tool
and in the manual "SPEED7 operation list" from VIPA.
8.13.5 Diagnostics via status LEDs
MT
(Mainte-
nance)
BF
(Bus error)
Meaning
yellow red
X ●
n Bus error, no connection to sub net/switch
n wrong transfer rate
n Full-duplex-transmission is not activated
X BB
n Failure of a connected IO device
n At least one IO device is not access-able
n Faulty configuration
● X Maintenance event is pending.
BB * BB * * The alternate blinking with 4Hz indicates that a firmware update of
the PROFINET IO controller is executed.
● ● Firmware update of the PROFINET IO controller is finished without
error.
LEDs PROFINET IO
controller X8
VIPA System 300S Deployment Ethernet communication - PROFINET
PROFINET diagnostics > Diagnostics via status LEDs
HB140 | CPU | 315-4PN33 | GB | 14-43 145