224
12 DEBUG FUNCTION
12.1 Memory Dump Function
Combining trigger conditions
A trigger can be generated with trigger conditions combined. This combination is based on an OR condition. The
establishment of a condition, either device specification or error code specification, results in data collection.
Procedure for memory dump
This section describes the procedure for memory dump. Note that each operation of the memory dump function is performed
with the engineering tool.
[Debug] [Memory Dump]
For how to view and operate the window, refer to the following.
GX Works3 Operating Manual
1. Configure the memory dump settings by the menu operation in the engineering tool.
2. Writing the memory dump setting file results in a wait state for the trigger. Whether the CPU module is in a RUN state,
STOP state (a stop error also included
*1
), or PAUSE state, a wait state for the trigger results.
*1 Limited to where the trigger condition is device specification.
• If the memory dump setting file is stored, putting the CPU module back into operation (powering off and on,
or resetting) results in a wait state for the trigger.
• The engineering tool allows the memory dump status to be checked. The event history also allows checking
whether or not in a wait state for the trigger.
3. Establishment of the trigger condition initiates data collection, saving the memory dump file to the SD memory card.
4. The contents of the memory dump file (collected device data) can be checked with the engineering tool.
END END END END END END
On error
Data condition
Collecting after trigger
(collecting/saving)
Program
Condition
established
Trigger
generated
Condition
established
Condition
established
Trigger
generated
The established condition is
not recognized as a trigger
because collecting after trigger
(collecting/saving) is in progress.
To Next Page
Loading...
