Table of Contents
Advertisement
Saving event history
■Modules from which event history information is collected
Event history information is collected from the C Controller module and other modules mounted on the same base unit (such
as the main base unit and any additional extension base units). Event history information may or may not be collected from
devices on the network depending on the specifications of the network modules used to connect to them. For more
information including the coverage of event history collection regarding devices on the network, refer to the manual of each
module. For a multiple CPU system, each CPU logs only events detected on the modules under its control.
■Events to be saved
The detailed information such as the operation initiator information are saved for troubleshooting purpose when the event
history is saved. For the event to be saved as the event history by C Controller module, refer to the event list. (Page 68
Event history function)
Event history file
The storage destination memory and file size for event history files can be changed in the event history setting. (Page 68
Event history settings)
■Storage destination memory
The storage destination memory is set to either the data memory or SD memory card.
When an SD memory card is selected, disable the write protect switch of the SD memory card. If it is enabled, an event
history will not be stored. (Reading the event history file in the SD memory card using CW Configurator is possible.)
If the write protect switch of an SD memory card is enabled, the write error will occur, because, during system operation, an
attempt to write an event occurred will failed as the write protect switch is enabled. An error can be checked with the Module
Diagnostic function immediately after the error occurred, but the same information cannot be checked after turning the power
OFF and ON, or resetting the module since errors are not saved.
For a system for which file write occurs frequently or the system of which state frequently changes because of
the unstable communication, the file size of the event history must be larger enough to store a greater number
of events. In this case, using an SD memory card is recommended as the storage memory.
■File size
If the specified size is exceeded, the records are deleted from the oldest one and the latest one is stored.
A file size of the event history can be obtained by the following formula.
• File size = File header size + Event history management information size + Number of records × Size per event history
record
The sizes of each element are as follows:
Element name
File header size
Event history management information size
*1
Size per event history record
*1 Since the events which overlaps multiple records exist depending on the event to be saved, a file size per one record will be changed.
■Conditions for collecting events
A C Controller module collects event history regardless of the operating status (RUN/STOP/PAUSE/STOP error); however,
the event history may not be collected under the following conditions.
• Major error
• Base unit error
• Cable failure
Size
20 bytes
12 bytes
40 to 1112 bytes
4 BASIC FUNCTIONS
69
4.12 RAS Function
4
Advertisement
Table of Contents
