9
UTILITY OPERATION
9.2 C Controller Setting Utility
9.2.3 Operating Event history screen
9 - 15
9
UTILITY OPERATION
10
FUNCTIONS AND
PROGRAMMING
11
OVERVIEW OF
MULTIPLE CPU
SYSTEM
12
MULTIPLE CPU
SYSTEM
CONFIGURATION
13
MULTIPLE CPU
SYSTEM
CONCEPT
14
COMMUNICATIONS
BETWEEN CPU
MODULES
15
PARAMETERS
ADDED FOR
MULTIPLE CPU
16
PRECAUTIONS FOR
USE OF AnS SERIES
MODULE
9.2.3 Operating Event history screen
(1) Precautions for Event history screen
(a) Event history update timing
Event history data are acquired from the C Controller module and updated when
connection is made to the C Controller module by the connection target setting or
when the button is clicked.
(b) Event history also displays the data registered by QBF_RegistEventLog
function
The event history also displays the data registered by the QBF_RegistEvent Log
function.
( Section 10.2.1)
(c) When communication error has occurred during connection
If a communication error has occurred during connection, make the connection
target setting again.
(d) Communication during reset
Communication are not available during reset of the C Controller module.
Start communication after terminating the reset process.
(e) Precautions for using QBF_RegistEventLog function
If the same data as in a character string in the table of Section 18.4.2 is specified
in the argument SrcStr[ ] of the QBF_RegistEventLog function, it will be difficult to
differentiate the data on the <<Event history>> tab screen.
Do not specify the same character string as in the table of Section 18.4.2.
Whether the event occurred in the system or application can be differentiated by "
Event type" of the "Event detail information" ( This section (3)) or "Source
flag" of the file saved in CSV format by clicking the button (
This section (5)).
Update
Save event history
To Next Page
Loading...
Need help?
General
