Table of Contents
Advertisement
Causes of Error and Reactions of the CPU
5.6.10
OB 34: Error with
G DB/GX DX
(FEDBX)
5.6.11
OB 35: Communication
Errors
Reaction if OB 35 is not loaded If you have not programmed OB 35, the system program does not
Error information in ACCU 1
5 - 32
Causes:
• • with the operation G DB/GX DX, an illegal block number was
specified (number of a reserved block, number > 255),
• • with the operation G DB/GX DX, an illegal block length was
specified (> 4091),
• • there is no longer enough space in the user memory for the
operation GDB/GXDX.
Reaction:
The system program calls OB 34 is this is loaded. If OB 34 is not
loaded, the CPU changes to the stop mode.
If problems occur on the second serial interface with an RK 512
computer link, data transfer with procedure 3964/3964R, data transfer
with an open driver or data transfer with SINEC L1, the system
program calls organization block OB 35 and enters additional
information about the error in ACCU 1.
react and the CPU does not change to the STOP mode.
The system program checks whether errors have occurred on the serial
interface every 100 ms. If an error has occurred, the system program
enters error information in ACCU 1.
Error numbers for up to a maximum of three errors can be transferred
when OB 35 is called. If there are more than three errors, this is indicated
by an overflow identifier.
CPU 948 Programming Guide
C79000-G8576-C848-04
Advertisement
Table of Contents
