Viewing The Event History; Clearing The Event History - Mitsubishi Electric MELSEC iQ-R16MTCPU Programming Manual

■Timing of file creation
Event history files are created at the following times.
• The Multiple CPU system power supply is turned OFF and ON (if there is no event history file or after the event history
settings are changed).
• The Multiple CPU system is reset (if there is no event history file or after the event history settings are changed).
• Initialization of the SD memory card (when no event history file exists)
• Write of parameters (when no event history file exists, or after an event history setting is changed).
*1 When a parameter is stored in the standard ROM, the event history file is created on the SD memory card, according to the event history
setting.
When a new event history file is created, that operation is logged into the event file as an event.
The following table shows how the event history is treated depending on operation.
Operation
Memory initialization
Event history creation
Indicates the operation of the event history for the SD memory which was removed and mounted in case that the save
destination memory is the SD memory.
Operation
Removal of the SD memory card
Installation of the SD memory card
■Timing of parameters taking effect
Any changed parameters take effect at the following times.
• The Multiple CPU system power supply is turned ON.
• The Multiple CPU system is reset
Any changed parameters written in the storage memory with the Motion CPU in the STOP state does not take
effect when the Motion CPU operating state is changed from STOP to RUN. In this case, the changed
parameters will take effect the next time when the Motion CPU is turned OFF and ON or reset.
Loss of event history information
If many events are detected frequently, some events may be lost without being collected. When event loss occurs, "*HST
LOSS*" appears in the "Event Code" field of MT Developer2.

Viewing the event history

The Motion CPU event history can be viewed using MT Developer2. For operating procedures and how to interpret the
displayed information, refer to the following.
Help of MT Developer2

Clearing the event history

The event history can be cleared using the event history window in MT Developer2. Once the event history is cleared, all the
event history information stored in the specified storage memory is deleted. For operating procedures and other details, refer
to the following.
Help of MT Developer2
Operation for the event history
When this event occurs, the event history is stored into the internal memory. If the internal memory reaches the
maximum number of event history records it can store, all subsequent events are lost.
The event history, which has been stored in the internal memory during absence of the event history file, is stored
into the standard ROM or the SD memory card. (If any event was lost, it is logged as "*HST LOSS*".)
Operation for the event history
When this event occurs, the event history is stored into the internal memory. If the internal memory reaches the
maximum number of event history records it can store, all subsequent events are lost.
The event history that has been stored in the internal memory during absence of the SD memory card, is stored
to the SD memory card. If the re-inserted SD memory card contains an event history file of the same file size, the
CPU module continues to store the event history information. If the file size is different, the CPU module removes
the existing event history file and creates a new event history file.
*1
9 RAS FUNCTIONS
9.3 Event History Function
9
375