Precautions - Mitsubishi Electric MELSEC iQ-R Series User Manual

Precautions

Clearing the event history during execution of another function
No event history can be cleared during execution of the following functions. Check that the following functions are not being
executed and then clear the event history.
• CPU module data backup/restoration function
• iQ Sensor Solution data backup/restoration function
Reading the event history during execution of another function
No event history can be read during execution of the following function. Check that the following function is not being
executed and then read the event history.
• CPU module data restoration function
Logging of event history
When event history logging is restricted, the relevant special relay ( Page 215 How to check whether event history
logging is restricted) turns on. Eliminate the event causes from the target module. The target module can be identified in
SD1464 to SD1467 (Module information on event history logging restriction).
Whether event history logging is restricted or not can also be checked in "Event history logging restricted" (00421) in "Event
History" window of the engineering tool.
Execution of other functions while event history logging is restricted
When the CPU module is restored by turning on SM1354 while event history logging is restricted, event history logging is
restarted after the completion of the restoration.
When event history logging is restarted and event history from a module is frequently logged again, logging the history of
events occurring on the target module is stopped (restricted).
Change of the event history setting
The following table shows the operation when the event history setting is changed after the CPU module starts, and written to
the CPU module.
Changed item
Save Destination
Set Save Volume of Per File
Save Device/Label Operations
Therefore, to save a past event history, before changing the event history setting, save data by using the [Create File] button
in the event history window of the engineering tool.
[Diagnostics]  [System Monitor]  [Event History] button  [Create File] button
Checking the event history of both systems chronologically
The engineering tool displays the event history saved in the CPU module of the connected system. Therefore, when checking
the event history of both systems chronologically, output the event history of each system from the Event History window of
the engineering tool to a CSV file and check the event history on the CSV file.
Operation
With the original file left as is, an event history file is generated in the enabled save destination (drive).
The event history file is discarded and regenerated.
With the original file left as is, EVENT.LOG is generated when the file is not saved, and EVEN2.LOG is generated
when the file is saved.
15 RAS FUNCTIONS
15.4 Event History Function
15
217