Mitsubishi Electric MELSEC iQ-R Series User Manual page 216

Element
Event to be saved
Total
*1 The size will be 56 bytes for a CPU module with firmware version "06" or later.
■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 generated, the "Event history file generation" (00420) is logged. When a new
event history file is generated during the logging restriction of the event history, the "Event history logging
restriction" (00421) is also logged.
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 an 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.
15 RAS FUNCTIONS
214
15.4 Event History Function
Power-on and reset
Operating status change (STOP)
Writing files/folders (SYSTEM.PRM)
Writing files/folders (CPU.PRM)
Writing files/folders (UNIT.PRM)
Writing files/folders (MAIN_001.PRG to MAIN_100.PRG)
Operating status change (RUN)
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 215 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 215 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.
Size (byte)
40
40
96
88
88
9600
40
10024
*1
*1