Error identifiers
If it was not possible to execute a job, the failure is indicated by "logic 1" on status parameter
error. The error cause is coded at the block output State:
State
WORD H
0
0
0
0
0
0
0
0
0
0
1 ... 8
0
Configuration steps
To be able to read a GUD variable, its name must be stored in a string variable. The data
block with this string variable must be defined in the symbol table so that the "Addr"
parameter can be assigned symbolically for FB GETGUD. A structure variable can be
defined optionally in any data area of the PLC to receive the variable pointer (see
specification in following example).
Basic logic functions: PLC basic program solution line (P3 sl)
Function Manual, 11/2006, 6FC5397-0BP10-2BA0
Significance
WORD L
1
Access error
2
Error in job
3
Negative
acknowledgment, job not
executable
4
Data areas or data
types do not tally
6
FIFO full
7
Option not set
8
Incorrect target area (SD) RD may not be local data
9
Transmission occupied
10
Error in addressing
11
Address of variable
invalid
13 (0x0d)
ANY data reference
incorrect
15 (0x0f)
String more than 32
characters
Detailed description
2.12 Block descriptions
Note
Incorrect compilation of Var. in a job
Internal error, try:
NC RESET
Check data to be
read in RD
Job must be repeated,
since queue is full
BP parameter "NCKomm" is not set
Job must be repeated
Unit contains value 0
Check Addr (or variable name), area,
unit
String/NcVar data required has not
been parameterized
GUD variable name too long
151