Operating Event History Screen - Mitsubishi MELSEC-Q Series User Manual

9
UTILITY OPERATION

9.2.3 Operating Event history screen

(1) Precautions for Event history screen
(a) Event history update timing
(b) Event history also displays the data registered by QBF_RegistEventLog
(c) When communication error has occurred during connection
(d) Communication during reset
(e) Precautions for using QBF_RegistEventLog function
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.
Update
function
The event history also displays the data registered by the QBF_RegistEvent Log
function.
( Section 10.2.1)
If a communication error has occurred during connection, make the connection
target setting again.
Communication are not available during reset of the C Controller module.
Start communication after terminating the reset process.
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" (
flag" of the file saved in CSV format by clicking the
This section (5)).
This section (3)) or "Source
Save event history
9.2 C Controller Setting Utility
9.2.3 Operating Event history screen
9
10
11
12
13
button (
14
15
16
9
- 15