Table of Contents
Advertisement
Diagnostics and error behavior
Diagnostics via FB STATUS
Event class 03h "Error parameterization of FBs" (not displayed in diagnostic buffer)
Event class / number Description
03 01h
Event class 04h "CP detected error in data traffic CP - CPU"
Event class / number Description
04 03h
04 07h
04 08h
04 09h
04 0Ah
94
Invalid or no source/destination data type Invalid area (start address, length) DB invalid or no
DB (e.g. DB 0) or other data type invalid or missing.
Remedy: Check parameterization on CPU and CP and correct if necessary.
Incorrect, unknown or illegal data type (e.g. wrong parameterization of FB)
Remedy: Check program for incorrect parameterization of the FB.
Error during data transmission between CPU and CP.
Remedy: If fault indication persists, check whether function blocks you have called in user pro-
gram are parameterized correctly.
If error is indicated immediately after PowerON, no connection has yet been set up to the CPU.
In the case of ASCII driver and 3964(R), the receiving CP re-attempts data transfer until the
data is transmitted to the CPU.
If fault indication is sporadic in the course of data transfer, the CPU is temporarily unable to
accept data. In the case of the ASCII driver and 3964(R) the receiving CP re-attempts data
transfer until the data is transmitted to the CPU.
Error during data transmission between CPU and CP (reception).
n
CPU is temporarily overloaded, request queued for repetition.
Remedy: Reduce number of communication calls.
n
CPU data area temporarily unavailable for access, for example because receive block is
called too infrequently.
Remedy: Call the receive block more frequently.
n
CPU data area temporarily unavailable for access, for example because receive block is
temporarily locked (EN = false).
Remedy: Check whether the receive block is disabled for too long.
Data cannot be received. Error during data transmission between CPU and CP (reception).
Request is canceled in 10s following multiple attempts, because:
n
Receive block is not called.
Remedy: Check whether your user program runs the receive block.
n
Receive block is disabled.
Remedy: Check whether the receive block is disabled.
n
Access to CPU data area denied.
Remedy: check that the data area to which the data is to be transferred is available.
n
CPU data area too short.
Remedy: Check the length of the data area.
Error during data transmission between CPU and CP.
Data transfer canceled by RESET because:
n
Destination DB is not available
n
Destination DB is too short
n
RESET bit set at FB.
Remedy: Create destination DB in the user program or increase the length of the existing desti-
nation DB, as applicable.
VIPA System 300S
HB130 | CP | 341-1CH01 | en | 18-40
Advertisement
Table of Contents
