4.2
Program
test
Faults causing the PC to enter the The following debugging functions are
"STOP" status can be identified with
available for tracing logic errors in
the aid of the interrupt stack (see
program scanning.
Instructions, Section
4.2)
4.2.1 Search function
The programmer "Search" function is Search runs are important in conjunction
available for locating points in the with the following functions:
user program.
-
Input/correction
In the test phase, for instance, all
-
Display
points in a program containing a
de-
-
Program-dependent signal status display
finite operand can be displayed, e.g.
an output not acting as expected.
For more details, please refer to the
The following search keys can be used: Operating Instructions of the programmers.
-
Statements, e.g.
AI
1.0
-
merands, e.g.
I
1.0
-
Labels (FB
1
only)
-
Addresses
4.2.2 Signal status display
The following programmer functions are
available for displaying the signal
statuses of binary and digital operands:
Direct signal status display
Program-dependent signal status display
The status of any operands can be
ob-
This test function enables the signal
served at the cycle checkpoint
(Sec-
status of an operand and the result
tion
2.1)
with the aid of this function.
of the logic operation to be observed
when the selected statement is processed.
4.2.3
Forcing of outputs and flags
The "FORCE" function enables definite
binary and digital operands to be
in-
f
luenced with the PC in the
"RUN"
mode.
The desired statuses of the operands
are entered from the
programmer byte
by byte and transferred to the PC.
The following can be forced:
-
QB
0..
.
QB
3
-
FB O...FB
63
In this way,
it
is possible to force
definite outputs on system
startup without
the user program and check the correct
wiring of actuators and indicators etc.
When forcing while a user program is
executing, the operand statuses entered
are transferred once to the PC and program
scanning resumed with these statuses
entered may be modified by the current
program.
To Next Page
Loading...
