9 RAS FUNCTIONS
9.3 Event History Function
373
9
9.3 Event History Function
The Motion CPU stores errors detected by the module, operations done for the module as "event history" in the standard
ROM of the Motion CPU, or the SD memory card. Once errors and operations are stored, their occurrence history and other
information can be checked chronologically. This function helps to determine the causes of problems that have occurred in the
equipment/devices, check the update status of the Motion CPU control data, and detect unauthorized access.
The event history information is constantly collected regardless of the operating state of the Motion CPU.
There are occasions, however, when the event history information cannot be collected due to a major error in
a module, a base unit error, a cable failure, or some other cause.
Event history settings
Under normal circumstances, the event history function can be used with its default settings and need not be manually
configured. The storage memory and size settings for event history files can be changed as needed.(Page 55 CPU
parameter)
Saving event history
This section describes events saving for the event history.
Modules from which event history information is collected
For the Motion CPU, only events that occur on the self CPU are saved.
Events on the modules managed by the self CPU are not saved.
Events saved by the CPU module
Information saved in the event history includes operation initiator and other detailed information for troubleshooting purposes.
For events that are saved in the event history on the Motion CPU, refer to event list. (Page 422 Event List)
Collects the information of events that occurred
in the Motion CPU in a batch and saves it.
MT Developer2
Displays the event information
retained by the Motion CPU with
MT Developer2.
To Next Page
Loading...
