Checking Data Logging Process Time; Checking Event Logging Process Time; Checking Report Process Time - Mitsubishi Electric MELSEC iQ-R Series User Manual

Checking data logging process time

Check if data, sampled with the data logging (continuous logging, trigger logging), can all be processed.
Checking the I/O signals, and the processing method when a problem occurs are as follows:
I/O signal
'Processing overload occurrence' (X1B)
if ON
Check the processing overload count of 'data
logging information 1 to 64' (Un\G2030 to
2989)
if not 0
The data logging processing (trigger
judgment and file saving) cannot catch up
with the sampling speed of the target data.
'Trigger reoccurrence' (X1C)
if ON
Check the trigger reoccurrence count of 'data
logging information 1 to 64' (Un\G2030 to
2989)
if not 0
Not processed because the next trigger
occurred immediately after a trigger.

Checking event logging process time

Check if the data, sampled with the event logging, can all be processed.
Checking the I/O signals, and the processing method when a problem occurs are as follows:
I/O signal
'Processing overload occurrence' (X1B)
if ON
Check the processing overload count of
'event logging information 1 to 64' (Un\G3030
to 3989)
if not 0
The event logging processing (event
judgment and file saving cannot catch up
with the sampling speed of the target data.

Checking report process time

Check if the data, sampled with the report, can all be processed.
Checking the I/O signals, and the processing method when a problem occurs are as follows:
I/O signal
'Processing overload occurrence' (X1B)
if ON
Check the processing overload count of
'report creation information 1 to 64'
(Un\G4030 to 4989)
if not 0
The report processing (creation trigger
judgment) cannot catch up with the sampling
speed of the target data.
'Creation trigger reoccurrence' (X1D)
if ON
Check the trigger reoccurrence count of
'report creation information 1 to 64'
(Un\G4030 to 4989)
if not 0
Not processed because the next creation
trigger occurred immediately after a trigger.
Processing method when a problem occurs
Take any of the following actions.
• Decrease the amount of target data.
• Lengthen the data sampling interval.
• Save only the necessary data to the file. (Use the trigger logging function).
• Stop access from GX LogViewer.
• Adjust the system so that the next trigger does not immediately occur after a trigger.
After taking the action, check that the processing overload count is 0 and the number of unprocessed data
(current) does not increase with time.
Adjust the system so that the next trigger does not immediately occur after a trigger.
For operation when triggers continuously occur, refer to the following:
Page 29 Trigger logging function
The period that the data is being saved in a file can be checked as per the 'Data logging execution information
(Un\G2008 to 2011).
For the time from when a trigger occurs up to when saving to the file is completed, refer to the following:
Page 345 High speed sampling
Processing method when a problem occurs
Take any of the following actions.
• Decrease the number of events.
• Lengthen the data sampling interval.
• Lower the frequency of event occurrence.
• Stop access from GX LogViewer.
After taking the action, check that the processing overload count is 0 and the number of unprocessed data
(current) does not increase with time.
Processing method when a problem occurs
Take any of the following actions.
• Decrease the number of reports.
• Lengthen the data sampling interval.
After taking the action, check that the processing overload count is 0 and the number of unprocessed data
(current) does not increase with time.
Take any of the following actions.
• Decrease the number of reports.
• Lengthen the data sampling interval.
• Adjust the system so that the next creation trigger does not immediately occur after a creation trigger.
For operation when triggers continuously occur, refer to the following:
Page 29 Trigger logging function
APPX
Appendix 7 Processing Time
A
351