Combining Trigger Conditions; Procedure For Memory Dump - Mitsubishi Electric FX5 User Manual

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.
On error
Condition
established
Data condition
Collecting after trigger
(collecting/saving)
Program
Precautions
If the trigger conditions are established again during data collection, the state will not be recognized as a trigger so data will
not be collected.
If the trigger conditions for both device specification and error occurrence are established within the same
scan, the trigger conditions for error occurrence will have priority.
20.3

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 (including stop error
*1 Limited to where the trigger condition is device specification.
• If the memory dump setting file is stored, the memory dump will be executed when the CPU module power
is turned OFF→ON or reset.
• The engineering tool allows the memory dump status to be checked.
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.
Trigger
generated
END END
*1
), or PAUSE state, a wait state for the trigger results.
Condition Trigger
established generated
Condition
established
END END
20 MEMORY DUMP FUNCTION
20.3 Procedure for Memory Dump
The established condition is not
recognized as a trigger because
collecting after trigger
(collecting/saving) is in progress.
END END
20
151