Detailed Description
2.4 Starting up the PLC program
PLC Basic Program Solution Line (P3 sl)
2-18 Function Manual, 08/2005 Edition, 6FC5397-0BP10-0BA0
2.4.9 Troubleshooting
This Section describes problems which may occur, their causes and remedies and should be
read carefully before hardware is replaced.
Errors, cause/description and remedy
Serial
no.
error
infor-
mation
Error Cause/description Remedy
1 No
connection
via MPI to
PLC.
The MPI cable is not
connected or is defective.
The STEP 7 software for
the MPI card may not be
configured correctly.
Test: Create a link with the programmer in the
STEP7 editor by means of connection
"Direct_PLC". A number of node addresses
must be displayed here. If they do not appear,
the MPI cable is faulty/has not been
connected.
2 PLC cannot
be accessed
in spite of
PLC general
reset.
A system data block SDB 0
has been loaded with a
modified MPI address. This
has caused an MPI bus
conflict due to dual
assignment of addresses.
Disconnect all MPI cables to other
components. Create the link "Direct_PLC" with
the programmer. Correct the MPI address.
3 All four LEDs
on the PLC
flash (DI
disaster)
A system error has
occurred in the PLC.
Actions: The diagnostic
buffer on the PLC must be
read to analyze the system
error in detail. To access
the buffer, the PLC must
be stopped (e.g., set "PLC"
switch to position 2). A
hardware reset must then
be performed. The
diagnostic buffer can then
be read out with STEP7.
Relay the information from
the diagnostic buffer to the
Hotline / Development
Service. A general reset
must be carried out if
requested after the
hardware reset. The
diagnostic buffer can then
be read with the PLC in the
Stop state.
Once the PLC program has been reset or
reloaded, the system may return to normal
operation. Even in this case, the content of the
diagnostic buffer should be sent to the
Development Office.
To Next Page
Loading...
Need help?
General
