Viewing The Event History; Clearing The Event History - Mitsubishi Electric MELSEC iQ-R-R00CPU User Manual

■When files are created
An event history file is created when:
• The CPU module is turned off and on (if there is no event history file or after the event history settings are changed).
• The CPU module 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 data memory, 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
The following table shows how the event history is treated at removal and installation of a SD memory card when the SD
memory card is specified as the storage memory.
Operation
Removal of the SD memory card
Installation of the SD memory
card
■When parameters take effect
Any changed parameters take effect when:
• The CPU module is powered on
• The CPU module is reset
Any changed parameters written in the storage memory with the CPU module in the STOP state does not take
effect when the CPU module operating state is changed from STOP to RUN. In this case, the changed
parameters will take effect the next time the CPU module is powered off and on or is reset.
Loss of event history information
If events are detected frequently, or the CPU module is powered off or reset immediately after the detection of events, some
events may not be collected and lost. When event loss occurs, "*HST LOSS*" appears in the "Event Code" field of the
engineering tool.

Viewing the event history

The event history can be viewed using the menus of the engineering tool. For operating procedures and how to interpret the
displayed information, refer to the following:
 GX Works3 Operating Manual

Clearing the event history

The event history can be cleared from the event history window. Once the event history is cleared, the CPU module deletes all
the event history information stored in the specified storage memory. For operating procedures and other details, refer to the
following:
 GX Works3 Operating Manual
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 ( Page 139 Loss of event history
information)
The event history, which has been stored in the internal memory during absence of the event history file, is stored into the
data memory 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 ( Page 139 Loss of event history
information)
The event history, which have 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
6 RAS FUNCTIONS
6.4 Event History Function
6
139