Event History Function - Mitsubishi Electric MELSEC iQ-R Series User Manual

Event history function

• This function is used to save the data such as the error detected by the motion system, the operation executed to the
module, the event related to the motion control of start and stop as event history.
• The occurrence history of the information such as the saved operation and error can be checked in chronological order.
• The data is saved as event history, so that the history can be checked even if the module turns OFF or resets.
• Using this function enables exploration of failure cause occurred in equipment and device, check of the control data update
status of CPU module, and detection of illegal access.
• The event history is always collected regardless of the operation status of Motion module. However, it may not be collected
in the cases such as major error of the module, base module error, or cable error.
• The event which occurred in the Motion module and is not set to be filtered is registered in the event history of the control
CPU module. For event history of a CPU module, refer to the following.
MELSEC iQ-R CPU Module User's Manual (Application)
Event occurred in the motion system
The items saved in the event history are shown below.
For details of the event, refer to the following.
Page 565 List of Event Codes
Event type Category
System Error
Warning
Information
Security Error
Warning
Information
Operation Error
Warning
Information
■MCFB execution and stop event
• The MCFB execution event can be monitored.
• Restart and multiple start by buffer mode also can be monitored as an event.
• Monitoring the execution event enables check such as whether each operation has started in intended order at the system
startup, etc.
• The stop event when the axis stops caused by stop factor input can be monitored.
• Monitoring the stop event enables check of the stop factor caused when the unintended stop has been executed, etc.
Event history file
• Event history data is saved to a file.
• Event history is saved to EVENT.LOG in the storage destination specified by System.PrConst.EventHistoryMotion_Path.
The file capacity is specified in System.PrConst.EventHistoryMotion_Capacity in a unit of kB.
When System.PrConst.EventHistoryMotion_Path is blank, the event history is saved to root path directly.
• When events frequently occur in the intervals shorter than the event history collection intervals of the motion system, the
event history storage area in the motion system might be full of event information which has not been collected. If a new
event occurs in this state, the motion system discards the event information and outputs the message "*HST.LOSS*" (The
event information has been erased.) which indicates the event information has been erased.
• Update of the event history is performed every three seconds after file update completion.
File update is not performed when an event is undetected.
When over 512 events occur during collection interval, the events are erased.
16 RAS FUNCTIONS
486
16.2 History Data
Details
Not applicable
Not applicable
An event on the right is detected in the Motion
module.
Not applicable
Not applicable
An event on the right related to the security is
detected in the Motion module.
Not applicable
Not applicable
Operation by the user on the right is detected in the
motion system.
Event item Event code
Not applicable 

Not applicable
Page 565 System 00000H to 007FFH

Not applicable

Not applicable
Page 565 Security
10000H to 17FFFH

Not applicable

Not applicable
Page 566 Operation
20000H to 27FFFH