Detailed description
2.5 Linking PLC CPUs to 810D, 840D
Power Line Basic PLC Program (P3)
Function Manual, 08/2005 Edition, 6FC5397-0BP10-0BA0
2-23
Errors, cause/description and remedy
Serial
no.
error
inform
ation
Error Cause/description Remedy
2 PLC
cannot
be
accesse
d 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
switch S4 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.
2.5 2.5 Linking PLC CPUs to 810D, 840D
General
The AS 300 family is used as the PLC for all systems. The essential difference between the
NCU variants lies in the method by which they are linked. On the 840D and 810D, the
PLC 314 CPU (user memory capacity up to 128 KB) or PLC 315-2 DP (user memory
capacity up to 288 KB) is integrated as a submodule into the NC unit.
The PLC/CPU 315-2 DP also supports distributed I/Os on the PROFIBUS (L2DP). The
relevant performance data for individual PLC CPUs can be found in the above table or in
Catalog FT70.
To Next Page
Loading...
Need help?
General
