Checking Fatal Errors - Omron SYSMAC CS Series Programming Manual

Checking Programs
2-3-4

Checking Fatal Errors

Address
A294 The type of task and the task number at the
point where operation stopped will be stored
here if operation stops due to a program error.
FFFF Hex will be stored if there are no active
cyclic tasks in a cycle, i.e., if there are no cyclic
tasks to be executed.
A298/A299 The program address at the point where opera-
tion stopped will be stored here in binary if
operation stops due to a program error.
If the END(001) instruction is missing (A29511
will be ON), the address where END(001) was
expected will be stored.
If there is a task execution error (A29512 will be
ON), FFFFFFFF Hex will be stored in A298/
A299.
UM (User Memory) Overflow Errors
UM overflow errors indicate that an attempt was made to execute instruction
data stored beyond the last address in the user memory (UM) defined as pro-
gram storage area. This error will normally not occur as long as the program
is created on a CS/CJ-series Programming Device (including Programming
Consoles).
In the rare even that this error does occur, it will be treated as a program
error, operation will stop (fatal error), and the UM Overflow Flag (A29515) will
turn ON.
The following errors are fatal program errors and the CPU Unit will stop run-
ning if one of these occurs. When operation is stopped by a program error,
the task number where operation stopped will be stored in A294 and the pro-
gram address will be stored in A298/A299. The cause of the program error
can be determined from this information.
Description Stored Data
Cyclic task: 0000 to 001F Hex (cyclic tasks 0 to 31)
Interrupt task: 8000 to 80FF Hex (interrupt tasks 0 to 255)
A298: Rightmost portion of program address
A299: Leftmost portion of program address
Section 2-3
65