Technical data

Program test You can call the "program test" function to test individual program
steps anywhere in your user program. When you do this, you stop
program processing and allow the CPU to process one operation after
the other. The PG outputs the current signal status of operands, the
accumulator contents, and the RLO for each operation executed.
Calling the function and
specifying the first
breakpoint
To call the "program test" function, specify the type and number of
the block (if necessary with nesting sequence) you want to test. At the
PG, mark the first operation, whose data are to be output. This is how
you specify the first breakpoint.
BARB is marked in the control bits. Command output is disabled
(BASP LED = on).
Caution
If you set Test mode on the coordinator, enter the block type and
block number (if necessary, with nesting sequence) of the block
to be tested. At the PG, mark the first operation whose data are to
be output.
This is how you specify the first breakpoint.
BARB is marked in the control bits. Command output is disabled
(BASP LED = on).
Calling in RESTART and in
RUN
When you specify the first breakpoint during program processing,
the CPU continues processing the program until it reaches the
operation marked by the specified breakpoint. The operation is
executed up to the operation boundary. (The DO FW and DO DW
operations are processed
including the substituted operation.)
The CPU then goes to the WAIT STATE. The data of the marked and
last executed operation are output there.
Calling test functions in SOFT
STOP
You can also call the "program test" function and specify an initial
breakpoint when the CPU is in the soft STOP mode. The CPU
remains in the soft STOP mode, and you can execute either a COLD
RESTART or a MANUAL WARM RESTART. The CPU processes
the program up to the marked operation and it proceeds as outlined
above.
11
PG Functions
CPU 928B Programming Guide
C79000-B8576-C898-01
11 - 11