Event History Function
Information including errors detected in the CPU module, expansion board and expansion adapter, and errors that occur in
the network is collected and saved by the CPU module. Once errors are stored, they can be checked chronologically. This
function can be used to pinpoint the cause of faults that occur in the system or device.
For supported version of event history function, refer to Page 478 Added and Enhanced Functions.
The event information held by the CPU
module is displayed by the engineering
The event history information is constantly collected regardless of the operating state of the CPU module.
There are occasions, however, when the event history information cannot be collected due to a major error in
a module, 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 161 Event
Navigation window [Parameter] [FX5UCPU] [CPU Parameter] "RAS Setting" "Event History Setting"
Specify the storage location of event history files.
Specify the storage capacity per event history file.
Setting per File
21 RAS FUNCTIONS
21.2 Event History Function
The event information that occurred in the CPU
module, expansion board and expansion adapter is
collected in batch and saved by the CPU module.
• Memory Card
• Data Memory
• Built-in RAM Battery Keeping
• 1 to 2048K bytes (Save Destination: Memory Card)
• 1.5K bytes (fixed) (Save Destination: Data Memory)
• 1 to 64K bytes (Save Destination: Built-in RAM
Unit: 1K bytes
1.5 K Byte