B-9
Equipment
Manual OP7, OP17
Release 04/99
Remedy:CauseMes-
sage
507 Transfer
of the data record was not acknowledged
by the PLC within a certain period.
Checking of data records by the user
at the PLC end must be carried out
more quickly (< 10 s).
509
Firmware version is dif
ferent from standard FB
version.
Please contact the SIMA
TIC Hotline.
510
Data record not present.
A process link with a non-existent
data block has been configured in a
recipe or the recipe data contains er
-
rors.
511 Y
ou have used a PLC job to select a recipe or a
request data record that does not exist.
512
Configured data block length is too short.
The variable transferred with the message
identifies the number of the data block.
Change configuration and retransfer
.
516
SINEC L2 protocol configured but no interface
module inserted.
Change configuration and retransfer
.
518
Interface module inserted and protocol configured
do not match.
Change configuration and retransfer
.
520
Excessive number of saved returns has meant that
maximum nesting level has been exceeded.
Go to Message Level (by pressing
ESC key if necessary).
521,
522
Screen can not be constructed or selected because
there is not enough memory available.
Message 522 triggers a restart with memory opti
-
mization.
Y
ou can optimize memory availabi
-
lity by
1.
Removing unused fields from the
configuration
2.
Configuring the screen with fewer
fields, or splitting it into more than
one screen
3.
Creating fewer recipe data re
-
cords
523
No text found.
524
Object class does not exist.
525
Illegal operand.
526
Loop-through operation is set on the OP
.
Change mode from “Loop-through
operation” to ”Normal operation”.
527
Access to recipe data is not possible at present.
528
Recipe does not exist.
529
File does not exist.
530
Data record not present.
531
Data record can not be loaded.
532
Information message: data record memory is full.
533
Floppy connection unclear
.
To Next Page
Loading...
Need help?
General
