Filter
Top Products
10
- 52
10.3 Troubleshooting by symptom
10.3.3 When operating the MES interface module
10
TROUBLESHOOTING
(From the previous page)
(To the next page)
Table 10.21 Troubleshooting about the DB interface function
Symptom Checked item Corrective action
Job startup is delayed.
Were the trigger conditions for multiple
jobs met concurrently?
• If the trigger conditions for multiple jobs are
met concurrently, startup of some job may be
delayed.
Section 6.1.11 (1) Operation behavior
of jobs
Has an error occurred in [Error log] of
[Working log]?
Section 7.12.5 Checking the
working log of the MES interface
module
• If an error has occurred, identify the error
cause and take corrective actions.
Section 10.2 Error Code List
Was the job execution time prolonged?
• If the job execution time is prolonged, startup
of the next job may be delayed.
Section 6.1.11 (1) Operation behavior
of jobs
Was the value in the Monitoring interval
timeout count area (buffer memory
address: 11510) increased?
• Check and correct the number of job settings
or trigger condition settings.
Job execution is slow.
Is the processing load of the server
computer is appropriate?
• Check if the processing load of a personal
computer for server is excessively high.
Is data volume in the data base within the
specified capacity of the personal
computer?
• Review data volume in the data base.
Check if the number of selected/updated
records are extreme when selecting or
updating.
• Set the Select/Update/Delete conditions that
apply appropriate records only.
Selecting [Resend] from [DB buffering
operation] of [Remote operation] will not
resend buffered SQL texts of the job for
which manual resend is selected.
Section 7.13.6 Operating the DB
buffering
Is there any problem on the connection
routes to all of the database server
computers?
• Check the connections with all of the
database server computers.
• When buffered SQL texts are to be sent to
more than one destination, unless the
communication with all the database server
computers is recovered, resending is not
started.
Are the DB Connection Services in all the
database server computers operating
normally?
• Check each of the DB Connection Services
in all the database server computers.
• When buffered SQL texts are to be sent to
more than one destination, unless DB
Connection Services in all the database
server computers are operating, resending is
not started.
Data such as DB buffering status, No. of
DB bufferings, DB buffer full, or DB buffer
utilization will not be stored in the tag
component which is selected in [DB
buffering settings] of [System setting].
Section 7.6.4 Setting items in DB
buffering setting
Was the setting that enables data writing
to the tag component made in [Job
settings]?
• Select another tag component, or check the
[Job settings] and disable data writing to the
relevant tag component.
Was the device value of the relevant tag
component manipulated in the
programmable controller CPU?
• Specify another device. Or do not manipulate
the relevant device value in the
programmable controller CPU.
Failed to communicate with the server
computer several times after module
startup.
Was the programmable controller
powered ON immediately after OFF?
• Turn OFF the programmable controller, and
after several minutes, turn it ON.
Is there any problem on the server
computer?
• Restart the server computer.