Diagnostics with the CP 341
8.1 Diagnostics Functions of the CP 341
CP 341 Point-to-Point Communication, Installation and Parameter Assignment
188
Manual, 09/2008, A5E02191071-01
Event classes
The table below describes the various event classes and numbers.
Table 8- 1
Event classes and event numbers
Event class 0 (00H):
"CP start-up"
Event no.
Event text
Remedy
(00)03H
PtP parameters received
-
(00)04H
Parameters already on CP (time versions match)
-
(00)07H
Status transition CPU to STOP
-
(00)08H
Status transition CPU to RUN/STARTUP
-
Event Class 1 (01H):
"Hardware fault on CP"
Event no.
Event text
Remedy
(01)01H
Fault while testing operating system EPROM of CP
(01)02H
RAM test of CP errored
(01)03H
Request interface of CP defective
CP defective; replace CP.
(01)10H
Fault in CP firmware
Switch module off and on again. If necessary,
replace module.
Event Class 2 (02H):
"Initialization error"
Event no.
Event text
Remedy
(02)0FH
Invalid parameter assignment detected at start of
assigned communication. Interface parameters
could not be assigned.
Correct invalid parameters and restart.
Event class 3(03H):
"Error during parameter assignment of FBs" (not displayed in the diagnostic buffer)
Event no.
Event text
Remedy
(03)01H
Illegal or missing source/destination data type Area
(start address, length) not permitted
The DB is not permitted or does not exist (e.g.,
DB 0) or
Other data type invalid or missing
Interprocessor communication byte number invalid
or
Interprocessor communication bit number invalid or
neither 'S' nor 'F' selected (for FB P_SND_RK)
Check parameter assignment on CPU and CP, and
correct if necessary.
RK 512 only: Partner returns invalid parameters in
message frame header.
Check parameter assignment on CPU and CP;
create block, if necessary.
See request tables for valid data types.
RK 512 only: Partner returns incorrect parameters in
message frame header.
长沙工控帮教育科技有限公司
www.gkbpx.com