Table of Contents
Advertisement
VIPA System 300S
Event class 05h "error while processing CPU request"
Event class / number Description
05 01h
05 02h
05 14h
05 17h
05 18h
Event class 07h "Send error"
Event class / number Description
07 01h
07 02h
07 03h
07 04h
HB130 | CP | 341-1CH01 | en | 18-40
Current request aborted as a result of CP restart.
Remedy: No remedy is possible at PowerON. When re-parameterization of the CP from the
programming device, before writing an interface you should ensure there are no more request
running from the CPU.
Request not permitted in this operating mode of CP (e.g. device interface not parameterized).
Remedy: Parameterize the device interface.
Specified start addresses too high for desired data type, or start address or DB/DX number too
low.
Remedy: Obtain from the request tables the permissible start addresses and DB/DX numbers
that can be specified in the program.
Transmission length > 1kbyte too great for CP or too short for interface parameter.
Remedy: Split the request up into several shorter requests.
With Modbus Master only
Transmission length during transmission is too large (> 4kbytes) or transmission length for
Send is too small.
Remedy: Check the parameter LEN for SEND.
Transmission of the first repetition:
n
An error was detected during transmission of the message frame.
n
The partner requested a repetition by means of a negative acknowledgment code (NAK).
Remedy: A repetition is not an error, but it can be an indication that there are disturbances on
the transmission line or that the partner device is behaving incorrectly. If the message frame still
has not been transmitted after the maximum number of repetitions, an error number describing
the first error that occurred is output.
With 3964(R) only
Error during connection setup: after STX was send, NAK or any other code (except for DLE or
STX) was received.
Remedy: Check for malfunction at partner device, possible by using interface test device
switched into the transmission line.
With 3964(R) only
Acknowledgment delay time (ADT) exceeded: after STX was sent, no response came from
partner within acknowledgement delay time.
Remedy: Partner device is too slow or not ready to receive, or there is a break on the send line,
for example. Check for malfunction at partner device, possible by using interface test device
switched into the transmission line.
With 3964(R) only
Termination by partner: during current send operation, one or more characters were received by
partner.
Remedy: Check whether the partner is also showing an error, possible because not all trans-
mission data has arrived (e.g. due to break on line) or due to serious fault or because the
partner device has malfunctioned. If necessary, use an interface test device switched into the
transmission line for this purpose.
Diagnostics and error behavior
Diagnostics via FB STATUS
95
Advertisement
Table of Contents
