Got2000 o Mes e

GRAPHIC OPERATION TERMINAL
GOT2000 Series
MES Interface Function Manual
For GT Works3 Version1
INTRODUCTION
Thank you for purchasing the Mitsubishi Graphic Operation Terminal (GOT).
Before using the GOT, please read this manual carefully to understand the features and performance for
correct handling.
CONTENTS
INTRODUCTION
Safety Precautions.......................................................................................................................................A - 6
Cautions for Using .......................................................................................................................................A - 7
List of Manuals for GT Works3 ....................................................................................................................A - 8
Abbreviations, Generic Terms, the meaning of the icon ..............................................................................A - 9
1. OVERVIEW
1.1 Features........................................................................................................................................... 1 - 3
1.2 What is the MES Interface Function? .............................................................................................. 1 - 7
2. SYSTEM CONFIGURATION
2.1 System Configuration ...................................................................................................................... 2 - 2
2.1.1 Overall system configuration.................................................................................................... 2 - 2
2.1.2 System configuration when installing software used for the MES Interface Function.............. 2 - 3
2.2 Connection between GOT and Controllers...................................................................................... 2 - 4
2.2.1 Connection type used for the MES Interface Function............................................................. 2 - 4
2.2.2 Precautions for inverter or servo amplifier connection ............................................................. 2 - 5
2.3 Required Equipment, Software, and System Application (Extended Function)............................... 2 - 6
2.4 Operating Environment.................................................................................................................... 2 - 7
2.4.1 Configuration computer............................................................................................................ 2 - 7
2.4.2 Server computer (SNTP server computer)............................................................................... 2 - 7
2.5 Cautions on System Configuration .................................................................................................. 2 - 9
3. SPECIFICATIONS
3.1 Performance Specifications ............................................................................................................. 3 - 2
3.2 GOT Devices Available for the MES Interface Function.................................................................. 3 - 4
3.3 Function List and Setting Item List................................................................................................... 3 - 5
3.4 GOT Internal Device (GS) ............................................................................................................... 3 - 7
3.4.1 GOT internal device list............................................................................................................ 3 - 7
3.4.2 MES Interface Function area ................................................................................................... 3 - 7
4. SETTINGS AND PROCEDURES BEFORE USE OF THE MES INTERFACE

FUNCTION
4.1 Settings and Procedures before Use of the MES Interface Function .............................................. 4 - 2
4.2 Installation and Uninstallation .......................................................................................................... 4 - 4
A-1
5. MES INTERFACE FUNCTION
5.1 DB Interface Function ...................................................................................................................... 5 - 2
5.1.1 DB interface function operation................................................................................................ 5 - 2
5.1.2 Job execution procedure.......................................................................................................... 5 - 3
5.1.3 Tag function ............................................................................................................................. 5 - 4
5.1.4 Trigger monitoring function ...................................................................................................... 5 - 5
5.1.5 Trigger buffering function ......................................................................................................... 5 - 7
5.1.6 SQL text transmission (Communication action) ....................................................................... 5 - 9
5.1.7 Arithmetic processing function (Operation action) ................................................................... 5 - 9
5.1.8 Resource data send function (Resource data send action) ................................................... 5 - 10
5.1.9 Program execution function ................................................................................................... 5 - 12
5.1.10 DB buffering function.............................................................................................................. 5 - 13
5.2 Precautions .................................................................................................................................... 5 - 20
6. MES INTERFACE FUNCTION SETTING

6.1 MES Interface Function Setting Screen........................................................................................... 6 - 2
6.2 Displaying the MES Interface Function Setting Screen ................................................................... 6 - 2
6.3 Screen Structure .............................................................................................................................. 6 - 3
6.3.1 Screen structure....................................................................................................................... 6 - 3
6.3.2 Operations using the Edit items tree ........................................................................................ 6 - 4
6.4 Setting.............................................................................................................................................. 6 - 5
6.5 Device Tag Settings......................................................................................................................... 6 - 6
6.5.1 Setting items in Device tag settings ......................................................................................... 6 - 7
6.5.2 Setting items in Array setting ................................................................................................... 6 - 8
6.5.3 Setting items in Component setting ....................................................................................... 6 - 10
6.6 Server Service Settings ................................................................................................................. 6 - 16
6.6.1 Setting items in Server service settings ................................................................................. 6 - 17
6.7 Job Settings ................................................................................................................................... 6 - 20
6.7.1 Setting items in Job settings .................................................................................................. 6 - 21
6.7.2 Setting items in Trigger conditions ......................................................................................... 6 - 23
6.7.3 Setting items in Program execution ....................................................................................... 6 - 30
6.7.4 Setting items in DB Buffering ................................................................................................. 6 - 32
6.7.5 Notify errors (job cancellation) that occur during job execution ............................................. 6 - 33
6.7.6 One-shot execution ................................................................................................................ 6 - 33
6.8 Job Settings - Actions .................................................................................................................... 6 - 35
6.8.1 Setting items in Communication action .................................................................................. 6 - 39
6.8.2 Setting items in Operation action ........................................................................................... 6 - 58
6.8.3 Setting items in Transmit resource action .............................................................................. 6 - 61
6.9 Option Setting ................................................................................................................................ 6 - 72
6.9.1 Setting items in DB buffering settings .................................................................................... 6 - 72
6.10 Diagnosis ....................................................................................................................................... 6 - 76
6.10.1 Checking the MES Interface Function status (Status) ........................................................... 6 - 76
6.10.2 Manipulating the MES Interface Function status (Operation) ................................................ 6 - 77
6.10.3 Changing the job status (Change job status) ......................................................................... 6 - 77
6.10.4 Checking the connection of the previous job execution (Connection result of previous job
execution)............................................................................................................................... 6 - 78
6.10.5 Manipulating DB buffering (DB buffering operation) .............................................................. 6 - 79
6.10.6 Checking the trigger buffering (Trigger buffering status)........................................................ 6 - 80
A-2
6.11 Working Log................................................................................................................................... 6 - 81
6.11.1 MES Interface Execute Log ................................................................................................... 6 - 81
6.11.2 Job Execute Log .................................................................................................................... 6 - 82
6.12 Precautions.................................................................................................................................... 6 - 86
7. DB CONNECTION SERVICE AND SETTING TOOL

7.1 DB Connection Service Functions ................................................................................................... 7 - 2
7.2 Setting ODBC of Database.............................................................................................................. 7 - 4
7.3 Starting DB Connection Service Setting Tool ................................................................................ 7 - 10
7.4 Screen Structure of DB Connection Service Setting Tool ............................................................. 7 - 11
7.4.1 Screen structure..................................................................................................................... 7 - 11
7.4.2 Menu configuration................................................................................................................. 7 - 11
7.5 Setting Items of DB Connection Service Setting Tool ................................................................... 7 - 12
7.5.1 Service port (required) (Range: 1024 to 65535, Default: 5112) ............................................. 7 - 13
7.5.2 DB access timeout (required) (Range: 1 to 3600; Default: 30) .............................................. 7 - 13
7.5.3 Limit IP addresses which permit to connect........................................................................... 7 - 13
7.5.4 Output access log .................................................................................................................. 7 - 14
7.5.5 Output SQL failed log............................................................................................................. 7 - 15
7.6 Importing/Exporting Files ............................................................................................................... 7 - 16
7.7 Help ............................................................................................................................................... 7 - 17
7.8 Output Log Specifications.............................................................................................................. 7 - 18
7.8.1 Access log.............................................................................................................................. 7 - 19
7.8.2 SQL failure log ..................................................................................................................... 7 - 20
8. TROUBLESHOOTING
8.1 Error Handling and Recovery Method ............................................................................................. 8 - 2
8.1.1 MES Interface Function setting ................................................................................................ 8 - 4
8.1.2 When using DB Connection Service Setting Tool.................................................................... 8 - 5
8.2 Error Code List................................................................................................................................. 8 - 6
8.2.1 Error log in the Working log...................................................................................................... 8 - 6
8.2.2 DB Connection Service .......................................................................................................... 8 - 10
9. APPENDICES
9.1 Usable Characters and ASCII Code Tables by Setting Items ......................................................... 9 - 2
9.1.1 ASCII code table ...................................................................................................................... 9 - 2
9.1.2 Characters applicable to item names, component names, variable names, etc. ..................... 9 - 2
9.1.3 Characters applicable to character string constants, etc. ........................................................ 9 - 4
9.1.4 Characters applicable to field names, table names, etc........................................................... 9 - 4
9.2 About Monitoring Interval Timeout................................................................................................... 9 - 5
9.3 Warning Messages in Windows Vista(R)......................................................................................... 9 - 7
9.3.1 Overview of warning messages ............................................................................................... 9 - 7
9.3.2 Methods for disabling warning messages ................................................................................ 9 - 7
9.4 Tables for Used Terms .................................................................................................................. 9 - 11
9.5 Application Example of MES Interface Function............................................................................ 9 - 12
REVISIONS
A-3
A-4
INTRODUCTION
Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A - 6
Cautions for Using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A - 7
List of Manuals for GT Works3 . . . . . . . . . . . . . . . . . . . . . . . . . .A - 8
Abbreviations, Generic Terms, the meaning of the icon . . . . .A - 9
A-5
Safety Precautions
Be sure to read these instructions before using this product.
Before using the product, read this manual and the relevant manuals introduced in this manual carefully and handle the
product properly with full attention to safety.
Note that these precautions apply only to this product.
In this manual, the safety instructions are ranked as "WARNING" and "CAUTION".
Indicates that incorrect handling may cause hazardous conditions,

WARNING resulting in death or severe injury.
Indicates that incorrect handling may cause hazardous conditions,

CAUTION resulting in minor or moderate injury or property damage.
Note that failure to observe the CAUTION level instructions may also lead to serious results depending on the
circumstances.
Be sure to observe the instructions of both levels to ensure personal safety.
Please keep this manual in accessible place and be sure to forward it to the end user.
Design precautions
● Before performing the test operation, read this manual carefully to understand
WARNING the operation procedure.
● When the security of the GOT and relevant information need to be protected against
illegal access from an external device via the Internet, take measures at the user's
discretion.
Failure to do so may cause the configured information to be read out illegally.
A-6
Cautions for Using
■1. GOTs that support the MES interface function
The MES interface function is available on GT27 and GT25.
To use the MES interface function, install the required system application (extended function) on the GOT.
For applicable models, refer to the following:
➠ 2.2 Connection between GOT and Controllers
■2. Option function board that supports the MES interface function
For the option function board that supports the MES interface function, refer to the following:
➠ 2.3 Required Equipment, Software, and System Application (Extended Function)
■3. Relational databases that support the MES interface function

For the option function board that supports the MES interface function, refer to the following:
➠ 2.4.2 Server computer (SNTP server computer)
■4. Connection type used for the MES interface function

To utilize the MES interface function, the Ethernet connection is used.
Install an Ethernet communication unit, and configure the Ethernet setting in Communication Settings of GT Designer3.
For applicable Ethernet communication units, refer to the following:
For the Ethernet connection, refer to the following.
➠ GOT2000 Series Connection Manual (Mitsubishi Products) for GT Works3 Version1
A-7
List of Manuals for GT Works3
For the manuals related to this product, install the manuals with the drawing software.
If you need a printed manual, consult your local Mitsubishi representative or branch office.
■1. List of Manuals for GT Designer3(GOT2000)

(1) Screen drawing software manuals
Manual number
Manual name Format
(Model code)
GT Works3 Version1 Installation Procedure Manual - PDF
SH-081220ENG
GT Designer3 (GOT2000) Screen Design Manual PDF, e-Manual
(1D7ML9)
SH-080862ENG
GT Converter2 Version3 Operating Manual for GT Works3 PDF
(1D7MB2)
GOT2000 Series MES Interface Function Manual for GT Works3 Version1 SH-081228ENG PDF
(2) Connection manuals
Manual number
Manual name Format
(Model code)
SH-081197ENG
GOT2000 Series Connection Manual (Mitsubishi Products) For GT Works3 Version1 PDF
(1D7MJ8)
GOT2000 Series Connection Manual (Non-Mitsubishi Products 1) For GT Works3

SH-081198ENG PDF
Version1
GOT2000 Series Connection Manual (Non-Mitsubishi Products 2) For GT Works3

SH-081199ENG PDF
Version1
GOT2000 Series Connection Manual (Microcomputers, MODBUS/Fieldbus Products,

SH-081200ENG PDF
Peripherals) For GT Works3 Version1
(3) GT SoftGOT2000 manuals
Manual number
Manual name Format
(Model code)
GT SoftGOT2000 Version1 Operating Manual SH-081201ENG PDF
(4) GOT2000 manuals
Manual number
Manual name Format
(Model code)
SH-081194ENG
GOT2000 Series User's Manual (Hardware) PDF, e-Manual
(1D7MJ5)
SH-081195ENG
GOT2000 Series User's Manual (Utility) PDF, e-Manual
(1D7MJ6)
SH-081196ENG
GOT2000 Series User's Manual (Monitor) PDF, e-Manual
(1D7MJ7)
POINT
e-Manual
e-Manual refers to the Mitsubishi FA electronic book manuals that can be browsed using a
dedicated tool.
e-Manual has the following features:
• Required information can be cross-searched in multiple manuals.
• Other manuals can be accessed from the links in the manual.
• Hardware specifications of each part can be found from the product figures.
• Pages that users often browse can be bookmarked.
■2. List of Manuals for GT Designer3(GOT1000)

Refer to the Help and manuals for GT Designer3(GOT1000)
A-8
Abbreviations, Generic Terms, the meaning of the icon
The following shows the abbreviations and generic terms used in Help.
■1. GOT
Meaning of icon
Abbreviations and generic terms Description Not
Support
support
GT27-X GT2715-X GT2715-XTBA, GT2715-XTBD
GT2712-S GT2712-STBA, GT2712-STWA, GT2712-STBD, GT2712-STWD

GT27-S
GT2710-S GT2710-STBA, GT2710-STBD
GT27 GT27-V GT2710-V GT2710-VTBA, GT2710-VTWA, GT2710-VTBD, GT2710-VTWD
GT27-S GT2708-S GT2708-STBA, GT2708-STBD
GT2708-V GT2708-VTBA, GT2708-VTBD

GT27-V
GT2705-V GT2705-VTBD
GT2512-S GT2512-STBA, GT2512-STBD

GT25-S
GT2512F-S GT2512F-STNA, GT2512F-STND
GT2510-V GT2510-VTBA, GT2510-VTWA, GT2510-VTBD, GT2510-VTWD

GT25
GT2510F-V GT2510F-VTNA, GT2510F-VTND
GT25-V
GT2508-V GT2508-VTBA, GT2508-VTWA, GT2508-VTBD, GT2508-VTWD
GT2508F-V GT2508F-VTNA, GT2508F-VTND

GT23 GT23-V
All GT21 models
GT2105-QTBDS
GT21-Q GT2105-Q
GT2105-QMBDS
GOT2000
Series GT21-R GT2104-R GT2104-RTBD
GT2104-PMBD
GT2104-PMBDS
GT2104-P
GT21 GT2104-PMBDS2
GT2104-PMBLS
GT21-P
GT2103-PMBD
GT2103-PMBDS
GT2103-P
GT2103-PMBDS2
GT2103-PMBLS
GT SoftGOT2000 GT SoftGOT2000 Version1
GOT1000 Series GOT1000 Series -
GOT900 Series GOT-A900 Series, GOT-F900 Series -
GOT800 Series GOT-800 Series -
A-9
■2. Communication unit
Abbreviations and generic terms Description
GT15-QBUS, GT15-QBUS2, GT15-ABUS, GT15-ABUS2, GT15-75QBUSL,

Bus connection unit
GT15-75QBUS2L, GT15-75ABUSL, GT15-75ABUS2L
Serial communication unit GT15-RS2-9P, GT15-RS4-9S, GT15-RS4-TE
MELSECNET/H communication unit GT15-J71LP23-25, GT15-J71BR13
CC-Link IE Controller Network communication unit GT15-J71GP23-SX
CC-Link IE Field Network communication unit GT15-J71GF13-T2
CC-Link communication unit GT15-J61BT13
Wireless LAN communication unit GT25-WLAN
Serial multi-drop connection unit GT01-RS4-M
Connection conversion adapter GT10-9PT5S
Field network adapter unit GT25-FNADP
Ethernet communication unit GT25-J71E71-100
■3. Option unit
Printer unit GT15-PRN
Video input unit GT27-V4-Z (A set of GT16M-V4-Z and GT27-IF1000)
RGB input unit GT27-R2, GT27-R2-Z (A set of GT16M-R2-Z and GT27-IF1000)

Video/RGB unit
Video/RGB input unit GT27-V4R1-Z (A set of GT16M-V4R1-Z and GT27-IF1000)
RGB output unit GT27-ROUT, GT27-ROUT-Z (A set of GT16M-ROUT-Z and GT27-IF1000)
Multimedia unit GT27-MMR-Z (A set of GT16M-MMR-Z and GT27-IF1000)
Video signal conversion unit GT27-IF1000
External I/O unit GT15-DIO, GT15-DIOR
Sound output unit GT15-SOUT
SD card unit GT21-03SDCD
■4. Option
NZ1MEM-2GBSD, NZ1MEM-4GBSD, NZ1MEM-8GBSD, NZ1MEM-16GBSD,

SD card
L1MEM-2GBSD, L1MEM-4GBSD
Battery GT11-50BAT
GT27-15PSGC, GT25-12PSGC, GT25-10PSGC, GT25-08PSGC, GT25-

05PSGC, GT21-05PSGC, GT21-04RPSGC-UC, GT21-03PSGC-UC, GT21-
04PSGC-UC, GT27-15PSCC, GT25-12PSCC, GT25-10PSCC, GT25-
Protective sheet
08PSCC, GT25-12PSCC-UC, GT25-10PSCC-UC, GT25-08PSCC-UC, GT25-
05PSCC, GT21-05PSCC, GT21-04RPSCC-UC, GT21-04PSCC-UC, GT21-
03PSCC-UC
Environmental protection sheet GT25F-12ESGS, GT25F-10ESGS, GT25F-08ESGS
GT20-15PCO, GT20-12PCO, GT20-10PCO, GT20-08PCO, GT25-05PCO,

Protective cover for oil
GT21-04RPCO, GT10-30PCO, GT10-20PCO, GT05-50PCO
USB environmental protection cover GT25-UCOV, GT25-05UCOV
GT15-90STAND, GT15-80STAND, GT15-70STAND, GT15-60STAND, GT05-

Stand
50STAND
GT15-70ATT-98, GT15-70ATT-87, GT15-60ATT-97, GT15-60ATT-96, GT15-

Attachment
60ATT-87, GT15-60ATT-77
A - 10
■5. Software
(1) Software related to GOT
GT Works3 SW1DND-GTWK3-J, SW1DND-GTWK3-E, SW1DND-GTWK3-C
GT Designer3 Version1 Screen drawing software GT Designer3 for GOT2000/GOT1000 series
GT Designer3
Screen drawing software for GOT2000 series included in GT Works3
GT Designer3 (GOT2000)
GT Designer3 (GOT1000) Screen drawing software for GOT1000 series included in GT Works3
GT Simulator3 Screen simulator GT Simulator3 for GOT2000/GOT1000/GOT900 series
GT SoftGOT2000 Monitoring software GT SoftGOT2000 series
GT Converter2 Data conversion software GT Converter2 for GOT1000/GOT900 series
GT Designer2 Classic Screen drawing software GT Designer2 Classic for GOT900 series
GT Designer2 Screen drawing software GT Designer2 for GOT1000/GOT900 series
DU/WIN Screen drawing software FX-PCS-DU/WIN for GOT-F900 series
(2) Software related to iQ Works
Abbreviation of iQ Platform compatible engineering environment MELSOFT

iQ Works
iQ Works
Generic term for integrated development environment software included in the

SW DNC-IQWK (iQ Platform compatible engineering environment MELSOFT
MELSOFT Navigator
iQ Works)
(□ indicates a version.)
SW□DND-IQAPL-M type integrated application management software

MELSOFT iQ AppPortal
(3) Other software
SW□DND-GXW3-E (-EA) type programmable controller engineering software

GX Works3
SW□DNC-GXW2-□ type programmable controller engineering software

GX Works2
GX Simulator3 Simulation function of GX Works3
GX Simulator2 Simulation function of GX Works2

Controller simulator
SW□D5C-LLT-E (-EV) type ladder logic test tool function software package
GX Simulator (SW5D5C-LLT (-V) or later versions)
SW□D5C-GPPW-E (-EV)/SW□D5F-GPPW (-V) type software package

GX Developer
SW□DNN-VIEWER-E type software package

GX LogViewer
SW□D5C-FBDQ-E type FBD software package for process control

PX Developer
Motion controller engineering environment MELSOFT MT Works2(SW□DND-

MT Works2 MTW2-E)
SW□RNC-GSV type integrated start-up support software for motion controller

MT Developer Q series
C Controller module configuration and monitor tool (SW1DND-RCCPU-E)

CW Configurator
SW□DNC-MRC2-E type servo configuration software

MR Configurator2
A - 11
MRZJW□-SETUP type servo configuration software

MR Configurator
Inverter setup software (FR-SW□-SETUP-WE)

FR Configurator
NC Configurator2 CNC parameter setting support tool (FCSB1221)
NC Configurator CNC parameter setting support tool
Parameter setting, monitoring, and testing software packages for FX3U-

FX Configurator-FP 20SSC-H (SW□D5CFXSSCE)
FX3U-ENET-L Configuration tool FX3U-ENET-L type Ethernet module setting software (SW1D5-FXENETL-E)
RT ToolBox2 Robot program creation software (3D-11C-WINE)
MX Component Version□(SW□D5C-ACT-E, SW□D5C-ACT-EA)

MX Component
MX Sheet Version□(SW□D5C-SHEET-E, SW□D5C-SHEET-EA)

MX Sheet
CPU Module Logging Configuration Tool CPU module logging configuration tool (SW1DNN-LLUTL-E)
■6. License key (for GT SoftGOT2000)
License key GT27-SGTKEY-U
A - 12
■7. Others
IAI IAI Corporation
AZBIL Azbil Corporation
OMRON OMRON Corporation
KEYENCE KEYENCE CORPORATION
KOYO EI KOYO ELECTRONICS INDUSTRIES CO., LTD.
JTEKT JTEKT Corporation
SHARP Sharp Manufacturing Systems Corporation
SHINKO Shinko Technos Co., Ltd.
CHINO CHINO CORPORATION
TOSHIBA TOSHIBA CORPORATION
TOSHIBA MACHINE TOSHIBA MACHINE CO., LTD.
PANASONIC Panasonic Corporation
PANASONIC IDS Panasonic Industrial Devices SUNX Co., Ltd.
HITACHI IES Hitachi Industrial Equipment Systems Co., Ltd.
HITACHI Hitachi, Ltd.
FUJI FUJI ELECTRIC CO., LTD.
YASKAWA YASKAWA Electric Corporation
YOKOGAWA Yokogawa Electric Corporation
RKC RKC INSTRUMENT INC.
ALLEN-BRADLEY Allen-Bradley products manufactured by Rockwell Automation, Inc.
CLPA CC-Link Partner Association
GE GE Intelligent Platforms, Inc.
HMS HMS Industrial Networks
LS IS LS Industrial Systems Co., Ltd.
MITSUBISHI INDIA Mitsubishi Electric India Pvt. Ltd.
ODVA Open DeviceNet Vendor Association, Inc.
SCHNEIDER Schneider Electric SA
SICK SICK AG
SIEMENS Siemens AG
PLC Programmable controller manufactured by each corporation
Control equipment Control equipment manufactured by each corporation
Temperature controller Temperature controller manufactured by each corporation
Indicating controller Indicating controller manufactured by each corporation
Controller Controller manufactured by each corporation
A - 13
A - 14
1
OVERVIEW
1. OVERVIEW
1.1 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 - 3
1.2 What is the MES Interface Function? . . . . . . . . . . . . . . . . . . . . . 1 - 7
1-1
The MES interface function allows SQL text transmission from a GOT to a database in the server computer connected via
the Ethernet, enabling writing GOT's device values to the database and reading database values to set them to GOT's
devices.
This direct communication with the server computer eliminates the need for gateway equipment, realizing reduction in the
maintenance cost and improvement in reliability.
POINT
The MES interface function is available only for GT27 and GT25.
When not using MES interface function When using MES interface function
Server (Database) Server (Database)
Communication gateway SQL No gateway required
GOT GOT
Controller Controller
1-2
1.1 Features 1
This section explains the features of the MES interface function.
■1. Simple setting enables connection to the information system without programming.
OVERVIEW
Access to information system databases can be realized simply by making the necessary settings with the setting tool.
Since there is no need to create programs for generating SQL texts, the engineering costs for system construction and
the work period can be reduced.
1.1 Features 1-3

■2. Important data can be protected.
(1) Buffering of send data (SQL text) during a communication error
When an error occurs during communications with a database, the SQL texts failed to be sent can be buffered in the
GOT.
After recovery, the buffered SQL texts are automatically sent to the database. (Manual operation is also possible.)
Disconnected
Database
INSERT
INSERT
INSERT
UPDATE
SD card
Recovered
Resend
Database
INSERT
INSERT
INSERT
UPDATE
SD card
(2) Obtaining logs in the event of access errors

After connection to a database, if a communication error occurs, the error details can be recorded as a log on the
database side.
Analyzing the log is useful for data protection and error analysis.
Database
DB connection service
Access
log
SQL failure
log
1-4 1.1 Features

■3. The information system load can be reduced.
1
Data can be monitored on the GOT and when the conditions are met, the data can be sent to the information system.
This can reduce the information system load, compared to the case of the conventional system that constantly samples
and monitors data.
OVERVIEW
[With the MES interface function]
<Information system>
Data transmission only when needed

Conditions met Database
[Conventional system]
<Information system>
Database
Constant sampling/monitoring from

information system is required.
■4. Access independent of the database table configuration is possible.

Freely designed database tables can be used for access to databases.
The MES interface function offers not only the high flexibility in designing a new system but also the capability of
reconstructing the existing system without changing the database tables.
1.1 Features 1-5

■5. Various controller information can be stored and changed in the database.
Controllers can be connected in a variety of topologies and their information can be stored into a database via GOT
devices.
Also, data read out from the database can be set to controllers as parameters via GOT devices.
PLC
Inverter
<MES interface function>

Data transmission
Status monitoring function
Script function Database
Gateway function
Servo
Data query
Microcomputer
Barcode reader
■6. Other features

(1) Reducing setting mistakes by use of tag names
Tag names can be assigned to devices.
Assigning recognizable tag names can reduce setting mistakes.
(2) Supporting system construction
The diagnostic function allows checking the operating status of the MES interface function (in real time, log).
Modification of the job status and test operation of a project under design is also possible.
1-6 1.1 Features

1.2 What is the MES Interface Function? 1
The items listed below are used with the MES interface function.
For equipment required for the MES interface function, refer to the following:
OVERVIEW
Reference
Item Description
section
System application (extended

System application (extended function) running on the GOT to implement the MES interface function 5.
function) [MES Interface]
MES interface function setting This function allows the MES interface function setting in GT Designer3. 6.
Software that runs on the server computer and links databases with the GOT.
DB Connection Service Install the software from either of the following. 7.
• CD-ROM or DVD-ROM of GT Works3
DB Connection Service Setting Software that runs on the server computer and changes the settings of the DB Connection Service.
7.
Tool Install the software from the CD-ROM or DVD-ROM of GT Works3.
1.2 What is the MES Interface Function? 1-7

1-8 1.2 What is the MES Interface Function?
2
SYSTEM CONFIGURATION
2. SYSTEM CONFIGURATION
2.1 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 2
2.2 Connection between GOT and Controllers . . . . . . . . . . . . . . . . 2 - 4
2.3 Required Equipment, Software, and System Application
(Extended Function) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 6
2.4 Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 7
2.5 Cautions on System Configuration. . . . . . . . . . . . . . . . . . . . . . . 2 - 9
2-1
This chapter explains the system configuration available for the MES interface function.
2.1 System Configuration

2.1.1 Overall system configuration
This section shows the overall system configuration when using the MES interface function.
Oracle, SQL Server

Database (Third party product)
SNTP server computer*1 Server computer
DB Connection Service
DB Connection Service Setting Tool
Ethernet
Configuration computer*1
Write
GT Designer3
· MES interface function
· System application (extended function)
GOT
MELSECNET/H, etc.*2
*1 The SNTP server computer and configuration computer can be shared as the server computer.
*2 For controllers available for the MES interface function, refer to the following.
➠ 2.2 Connection between GOT and Controllers
2-2 2.1 System Configuration

2.1.2 System configuration when installing software used for the MES
Interface Function
The following shows system configuration when installing software used for the MES interface function.
2
■1. When installing the DB Connection Service and DB Connection Service Setting Tool on a
server computer
Sever computer
GT Works3
Install
DB Connection Service
DB Connection Service Setting Tool Commercial product
POINT
(1) When installing DB Connection Service on a database server computer, the ODBC setting
for the database used must be made beforehand.
➠ 7.2 Setting ODBC of Database
(2) When installing DB Connection Service on an application server computer, an account for
user program execution must be created beforehand.
■2. When installing GT Designer3 on a configuration computer
GT Works3 Configuration computer
Install
GT Designer3(GOT2000)
Commercial product
■3. When installing a system application (extended function) of [MES Interface] on the GOT
Computer Installing a
system application
(extended function) GOT
of [MES Interface]
on the GOT*1
GT Designer3
(GOT2000)
+
MES interface function
Commercial product
*1 For equipment used for installation, refer to the following manual:
➠ GT Works3 Version1 Installation Procedure Manual
2.1 System Configuration 2-3

2.2 Connection between GOT and Controllers
2.2.1 Connection type used for the MES Interface Function
The following table shows the GOT supporting the MES interface function and availability in each connection type.
For system configuration when using the MES interface function, refer to the following manual:
➠ GOT2000 Series Connection Manual for GT Works3 and a controller used
: Applicable : Partly restricted : Not applicable
Connection type GT27, GT25
Bus connection
Direct CPU connection
Computer link connection
Ethernet connection*7
MELSECNET/H connection (PLC to PLC network)

Mitsubishi PLC connection*4
MELSECNET/10 connection (PLC to PLC network) *1
CC-Link IE controller network connection
CC-Link IE field network connection
CC-Link connection (Intelligent device station) *2
CC-Link connection (via G4)
Inverter connection *3
Servo amplifier connection *3
Robot controller connection*5
Serial connection
CNC connection*6
MELSECNET/10 connection (PLC to PLC network) *1
CC-Link connection (Intelligent device station) *2
Serial connection
Third party PLC connection
Third party safety controller connection
Third party servo amplifier connection
Third party robot controller connection
Third party temperature controller connection
Serial connection
Microcomputer connection
MODBUS/RTU connection
MODBUS/TCP connection
*1 For the MELSECNET/10 connection, use the MELSECNET/H communication unit.

The MELSECNET/10 communication unit cannot be used.
*2 For the CC-Link connection, use the CC-Link communication unit (GT15-J61BT13).
The CC-Link communication unit (GT15-75J61BR13-Z) cannot be used.
*3 For the inverter or servo amplifier connection, use the status observation function or the script function to assign devices.
For how to assign devices, refer to the following:
➠ 2.2.2 Precautions for inverter or servo amplifier connection
*4 Including connection to the motion controller CPU (Q series and A series), CNC C70, and CRnQ-700
*5 Applicable to the CRnD-700 only. For the CRnQ-700, refer to the above Mitsubishi PLC connection.
*6 Applicable to the MELDAS C6/C64 only. For the CNC C70, refer to the above Mitsubishi PLC connection.
2-4 2.2 Connection between GOT and Controllers

2.2.2 Precautions for inverter or servo amplifier connection
In the inverter or servo amplifier connection, the trigger action or the script function must be used for device assignment.
For the trigger action and the script function, refer to the following manual.
➠ GT Designer3 (GOT2000) Screen Design Manual 2
The following are device assignment examples.
Example 1) Setting for assigning devices of the inverter [FREQROL 500/700/800, SENSORLESS SERVO] to the GOT's
internal devices using the trigger action
Example 2) Setting for assigning devices of the inverter [FREQROL 500/700/800, SENSORLESS SERVO] to the GOT's
internal devices using the trigger action
Setting item Setting content Remarks
Trigger ON Device GB40 Ordinary (GB40 is always ON.)
Assigns devices A0 to A15 of the inverter that

[w:GD0]=[0-0:w:A0]; has channel No. 1 and station No. 0 to device
GD0.
Assigns devices Pr 0 to Pr 15 of the inverter that

[w:GD10]=[0-0:w:Pr0]; has channel No. 1 and station No. 0 to device GD
10.
Operation device
Assigns devices PG0 to PG15 of the inverter that
[w:GD20]=[0-0:w:PG0]; has channel No.1 and station No.0 to device
GD20.
Assigns devices A0 to A15 of the inverter that has

[w:GD31600]=[@3:0-16:w:A0]; channel No.3 and station No.16 to device
GD31600.
2.2 Connection between GOT and Controllers 2-5

2.3 Required Equipment, Software, and System Application (Extended
Function)
■1. Required equipment and software
The following table lists the equipment and software required for use of the MES interface function.
Application Required equipment/software Module name
Licence Key for MES Interface

Executing the MES interface function on the GOT GT25-MESIFKEY
function
Built-in Ethernet interface -

Connecting the GOT to Ethernet
Ethernet communication unit GT25-J71E71-100
For connection to a controller, refer to the following.

Connecting the GOT to controllers ➠ GOT2000 Series Connection Manual For GT Works3 Version1 compatible for a
controller used
GT Designer3 Version1.108N or
Setting the MES
later -
interface function
(MES interface function)
Setting the MES
interface function NZ1MEM-2GBSD, NZ1MEM-4GBSD,
DB buffering function,
NZ1MEM-8GBSD, NZ1MEM-16GBSD,
log output function, SD card
L1MEM-2GBSD, L1MEM-4GBSD,
diagnostics function
Commercially available CF card (128MB or more)*1
*1 Some models with the operations checked by our company are usable.
For applicable SD cards, refer to the following Technical News.
➠ Operation Check Results of Non-Mitsubishi SD Cards on GOT2000 Series Units (GOT-A-0065)
For installation of the required equipment, refer to the following manual.

➠ GOT2000 Series User's Manual (Hardware)
For connection of the required equipment, refer to the following manual.
➠ GOT2000 Series Connection Manual for GT Works3
■2. Required system application (extended function)

To use the MES interface function, a system application (extended function) of [MES Interface] is required.
Setting [MES Interface] installs the advanced system application (MES Interface) automatically into
the package data.
POINT
(1) To use the MES Interface function, the BootOS Version of GOT D or later is required.
When the old version, license registration to use the MES interface function can not be.
(2) How to set the SNTP server, refer to the following.
➠ GT Designer3 (GOT2000) Screen Design Manual
2-6 2.3 Required Equipment, Software, and System Application (Extended Function)
2.4 Operating Environment
2.4.1 Configuration computer
The operating environment for the configuration computer is identical to those for GT Designer3.
For the operating environment for GT Designer3, refer to the following manual.
2
2.4.2 Server computer (SNTP server computer)
This section explains the operating environment for the server computer.
Item Description
Personal computer Personal computer or Server on which the following operating systems and relational database can run
Microsoft Windows Server 2012 R2 *10*11*15*16*17*18*19

Microsoft Windows Server 2012 *10*11*15*16*17*18*19
Microsoft Windows Server 2008 R2 *10*11*15
Microsoft Windows Server 2008 *10*11*15
Microsoft Windows Server 2003 x64 Editon *4*5
Microsoft Windows Server 2003 *4*5
Microsoft Windows 2000 Server Service Pack2 or later *4
Microsoft Windows 8 Enterprise (32 bit, 64bit)*5*10*11*14*16*17*18*19
OS(English Version) Microsoft Windows 8 pro (32bit, 64bit) *5*10*11*14*16*17*18*19
Microsoft Windows 7 Ultimate (32bit, 64bit) *5*10*11*14
Microsoft Windows 7 Enterprise (32bit, 64bit) *5*10*11*14
Microsoft Windows 7 Professional (32bit, 64bit) *5*10*11*14
Microsoft Windows Vista Ultimate (32bit) *5*10*11
Microsoft Windows Vista Enterprise (32bit) *5*10*11
Microsoft Windows Vista Business (32bit) *5*10*11
Microsoft Windows XP Professional (32bit) *4*5
Microsoft Windows 2000 Professional Service Pack2 *4
CPU 1GBHz or more
• When using the Windows Server 2012 R2, Windows Server 2012, Windows Server 2008, Windows Server 2003 x64
Edition, Windows 8.1 (64bit), Windows 8 (64bit) and Windows7 (64bit):2GB or more
Memory • When using the Windows Server 2003, Windows Server 2000, Windows 8.1 (32bit), Windows 8 (32bit), Windows7
(32bit) and Windows Vista (32bit):1GB or more
• When using the Windows XP and Windows 2000:512MB or more
Display A display where the above OS and after-mentioned databases can run
Free hard disk space 64MB or more (After database installation)
Interface Ethernet
When using the DB interface function: Relational database (any of the following)
Oracle 12c*3
Oracle 11g*2
Oracle 10g*1
Oracle 9i*1
Oracle 8i*1
Microsoft SQL Server 2014*2*6*7
Microsoft SQL Server 2008 R2*2*6*7
Other software
Microsoft SQL Server 2005*1*6
Microsoft SQL Server 2000*1*6
Microsoft SQL Server 2000 Desktop Engine(MSDE 2000)*6
Microsoft Access 2013*1*7*12*13
Microsoft Access 2010*2*7*12*13
Microsoft Access 2007*7*12*13
Microsoft Access 2003*7*8
Microsoft Access 2000*7*8
When using the SNTP server: SNTP server

(Equipped as a standard to Windows 2000 Server, Windows Server 2003)
2.4 Operating Environment 2-7

Item Description
Instration: Mouse, Keyboard, and DVD-ROM drive or CD-ROM drive

Other hardware
Running: Mause and Keyboard
*1 Only 32-bit is available.

*2 32-bit and 64-bit are available.
*4 To install or operate DB Connection Service or DB Connection Service Setting Tool, the administrator authority is required.
*5 The following functions are not available.
If any of the following functions is used, this product many not operate normally.
• Activating the application with Windows compatibility mode
• Fast user switching
• Change your desktop themes (fonts)
• Remote desktop
• DPI setting other than the normal size (For Windows XP, Windows Vista, Windows Server 2003)
• Setting the size other than [Smaller - 100%] for the characters and images on the screen (For Windows 7, Windows 8)
• Standby and hibernation of Windows
*6 Set [SQL Server and Windows] for the security authentication mode.
*7 Up to 127 fields can be updated for a communication action.
*8 Do not access the same file with multiple GOTs and MES interface modules simultaneously.
*9 Only [Insert] can be used for the communication action.
*10 15GB or more of free space is required.
*11 A standard user account or above is required.
*12 Memo-type fields in Rich Text Format cannot be used.
*13 A field having multiple values cannot be used.
*14 Windows XP Mode is not supported.
*15 Server Core installation is not supported. Be sure to perform a full installation.
*16 Windows Touch and Touch are not supported.
*17 Modern UI style is not supported.
*18 Hyper-V is not supported.
*19 It is necessary to install .NET FrameWorks3.5.
When the Windows8 or Windows Server 2012 is used, it is necessary to activation [.NET FrameWorks3.5(including .NET2.0 and
.NET3.0)] in the control panel at [Disable or Enable the Windows function]
2-8 2.4 Operating Environment

POINT
How to set security authentication mode (SQL Server and Windows)
(1) For Microsoft SQL Server 2014, Microsoft SQL Server 2012, Microsoft SQL Server 2008
R2, Microsoft SQL Server 2008, Microsoft SQL Server 2005, and Microsoft SQL Server
2
2000
Set the security authentication mode in the SQL Server Properties (Configure) screen.
(2) For Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
When installing MSDE2000, specify a command parameter.
setup sapwd = "sa" SECURITYMODE=SQL
(sa: Specify an arbitrary password.)
2.5 Cautions on System Configuration

■1. Relational databases that support the MES interface function
For the relational databases that support the MES interface function, refer to the following:
➠ 2.4.2 Server computer (SNTP server computer)
2.5 Cautions on System Configuration 2-9

2 - 10 2.5 Cautions on System Configuration
3
SPECIFICATIONS
3. SPECIFICATIONS
3.1 Performance Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 2
3.2 GOT Devices Available for the MES Interface Function . . . . . . 3 - 4
3.3 Function List and Setting Item List. . . . . . . . . . . . . . . . . . . . . . . 3 - 5
3.4 GOT Internal Device (GS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 7
3-1
This chapter explains the performance specifications, functions and devices of the MES interface function.
3.1 Performance Specifications

The following are the performance specifications of the MES interface function.
Reference
Item Specifications
section
No. of connected databases Up to 8 databases/project
• Oracle 12c*5
• Oracle 11g*4
• Oracle 10g*3
• Oracle 9i*3
• Oracle 8i*3
• Microsoft SQL Server 2014*4
• Microsoft SQL Server 2008 R2*4 6.6.1
No. of connectable databases
• Microsoft SQL Server 2000 Desktop Engine(MSDE 2000)
• Microsoft Access 2013*3
• Microsoft Access 2010*4
• Microsoft Access 2007
Allowable number of
Up to 64 jobs/project
Job settings 6.7.1
Trigger buffering Up to 128 tag components/tag
No. of conditions can be Up to 2 conditions

DB
combined • (Combination can be selected either AND or OR)/job
interfa
ce 20 types (Time specification (6 types), Specified time period, comparison
trigger conditions between tag component values (6 types), comparison between tag 6.7.2
Condition type
component value and constant value (6 types), At module startup) and
Handshake operation
Validation interval One second at the minimum
Allowable number of
Up to 10 actions/job
settings
6.8
Communication action
4 types (Select, Update, Insert, MultiSelect)
type
Up to 8192 fields/project
No. of communication • [DB-Tag link setting]: Up to 256 rows/communication action
action fields • [Select/Update conditions]: Up to 8 rows/communication action
• [Select sort settings]: Maximum 8 rows/communication action 6.8.1
No. of records/data
Action Up to 40000 records/MultiSelect communication action
selectable for
Up to 45000 words/job
communication action
No. of operations
possible for operation (Up to 20 dyadic operations)/operation action
action 6.8.3
Operators for operation 6 types (Addition, subtraction, multiplication, division, remainder, character
action string combination)
No. of resource data

Maximum 8192 fields/project 6.8.3
send action fields
3-2 3.1 Performance Specifications

Reference
Item Specifications
section
No. of tags Up to 64 tags/project
Up to 256 tag components/tag

No. of tag components
Up to 4096 tag components/project
5 types (Signed single-precision integer type (16 bits), signed double-

Data type precision integer type (32 bits), single-precision floating point type (32 bits),
bit type, character string type)
Device tag
Character string length Up to 32 characters
6.5.3 3
DB
No. of statistical
interfa Up to 64 tag components
processings
ce
6 types
SPECIFICATIONS
Statistical processing (Average, maximum, minimum, moving average*1, moving maximum*1,
moving minimum*1)
Allowable number of (Once before execution of the initial action + once after execution of the
Program execution 6.7.3
settings final action)/job*2
DB Buffering capacity for Maximum capacity: SD card capacity -32M bytes

6.9.1
buffering communication errors*2 (16 Mbytes to 512 Mbytes)
Worki Log capacity for MES interface function execution Maximum capacity: 1 Mbyte (SD card)
ng 6.11
log Log capacity for job execution events Maximum capacity: 2 Mbytes (SD card)
*1 [No. of samples] can be set up to 20.

*2 How to estimate the buffering time from the buffering capacity is shown below.
Buffering time = (Allowable No. of bufferings) (Frequency [times/hour]) [h]
Allowable No. of bufferings = (Capacity to be used) (SQL text length + Overhead (4 bytes)
SQL text length = Total field character length + 6 No. of fields + Total data length + 20 [bytes]
[Calculation Example]
In the case of the capacity of 64 Mbytes, the field name of 16 characters, the data length of 32 characters, access to 256 fields by
one action per job, and executing once per 30 seconds
SQL text length = (16 256) + 6 256 + (32 256) = 13844 [bytes]
Allowable No. of bufferings = (64 1024 1024) (13844 + 4) 4846
Buffering time = 4846 (60 30 60) 40 [h]
*4 32-bit and 64-bit are available.
3.1 Performance Specifications 3-3

3.2 GOT Devices Available for the MES Interface Function
The following are GOT devices that can be set in the Device tag settings of the MES interface function.
Type Description Available setting range
Bit register inside the GOT

GOT bit register GB64 to GB65535*1
Can be used as a bit device.
Data register inside the GOT

GOT data register GD0 to GD65535
Can be used as a word device.
Special register inside the GOT

GOT special register Stores GOT's internal information, communication status, error information, etc. GS0 to GS1023*2
Used when making interaction between the MES interface function and the gateway function.
Virtual device for indirectly reading or writing the controller devices that are monitored by 1-1: EG0 to 239-64:
Gateway device
another GOT. EG32767*3
*1 For GB0 to GB63, refer to the following manual.

*2 Do not write any value to a write-prohibited GOT special register.
Setting a value to the GOT special register may affect the GOT operation.
For the GOT special register, refer to the following manual.
➠ GT Designer3 Version1 Screen Design Manual (Fundamentals)
*3 Specify the gateway device in the following format.
(Network No.) - (Station No.) : EG (Device No.)
Network No. : 1 to 239
Station No. : 1 to 64
Device No. : 0 to 32767
POINT
The gateway function setting is required for use of the gateway devices.
For the gateway setting, refer to the following manual.
3-4 3.2 GOT Devices Available for the MES Interface Function
3.3 Function List and Setting Item List
This section provides the lists of the functions and setting items that can be set for the MES interface function.
■1. MES interface function list

Reference
Function Description
section
Executes communication with the database in units of jobs.

5.1
6.8 3
Collects data in the internal devices or gateway devices of the GOT on the
network in units of tags. 5.1.3
Tag function
Assigning a database field to a tag component allows reading or writing of a 6.5
database value or device data that is specified by the tag component.
SPECIFICATIONS
Monitors values such as the time and tag values and, when the trigger
Trigger monitoring 5.1.4
condition changes from false to true (when the conditions are met), starts a
function 6.7.2
job.
Allows the system to buffer the data and the time that trigger conditions are
met to the user area of the GOT when too many trigger conditions (data
transmission conditions) are met simultaneously. The action (operation and 5.1.5
Trigger buffering function
transmission of the data) for the buffered data is executed later. 6.7.1
Even when the data transmission triggers are activated frequently, no
triggers are missed so that all the jobs are executed.
Automatically creates an SQL text and communicates with the database.

DB interface function
The following three types of commands can be selected for the SQL text.
SQL text transmission 5.1.6
• Select/MultiSelect
(Communication action) 6.8.1
• Update
• Insert
Arithmetic processing
5.1.7
function Allows operations of tag component values.
6.8.2
(Operation action)
Resource data send 5.1.6

Sends the resource data collected in the GOT to the database.
function (Resource data 5.1.8
A SQL text (INSERT) is used for sending the resource data to the database.
send action) 6.8.3
Program execution Executes programs in the application server computer before execution of 5.1.9
function the first action and after execution of the last one in a job. 6.7.3
Temporarily stores SQL texts into a CF card when they cannot be sent due to 5.1.10
network disconnection or failure of the database server computer. 6.9.1
DB buffering function
After recovery, the buffered SQL texts are automatically sent to the 6.10.4
database. (Manual operation is also possible.) 6.10.5
Diagnostics function Used to stop/restart the MES interface function, check job operations and configure the settings. 6.10
Allows direct access to a database upon request of the DB interface function. 7.1
ODBC connection Executes the operation requested by the DB interface function or returns a
7.2
function response.
DB server function
Connection setting
Restricts IP addresses of GOTs that can be connected to the database. 7.5
function
Log output function Outputs the execution status of DB Connection Service to the log. 7.8
3.3 Function List and Setting Item List 3-5

■2. List of the MES interface setting items
Reference
section
Configure the settings for the tag function. 6.5
Configure this setting when writing multiple records extracted from a

Device tag settings Array setting 6.5.2
database to the same tag component.
Component setting Configure the settings for assigning GOT devices to tags. 6.5.3
Server service settings Configure the settings for access to a server computer. 6.6
Configure the settings for the DB interface function. 6.7
trigger conditions Configure the settings for startup conditions of the job. 6.7.2
Trigger buffering Set whether to utilize the trigger buffering function or not. 6.7.1
Communication action Configure the settings for communications with a database. 6.8.1
Operation action Configure the settings for operation of tag component values. 6.8.2
Job settings
Resource data send
Configure the settings for sending the resource data to the database. 6.8.3
action
program execution Configure the settings for the program execution function. 6.7.3
DB buffering Set whether to utilize the DB buffering function or not. 6.7.4
One-shot execution Execute a job as a one-shot task. 6.7.6
Configure the DB buffering function setting. 6.9

Option setting
DB buffering setting Configure the settings for the DB buffering function. 6.9.1
Perform the remote diagnosis for the MES Interface function. 6.10
Status The operation status of the MES Interface function can be checked. 6.10.1
Operation The operation of the MES interface function can be controlled. 6.10.2
diagnosis Change Job Status The job status can be changed. 6.10.3
Connection result of Connection with the server computer set in [Server Service setting], which is
6.10.4
previous job execution made at the time of the previous job execution, can be displayed.
DB buffering operation The DB buffering can be operated. 6.10.5
Displays the working log of the MES Interface function. 6.11
MES Interface Execute

MESI/F Log Displays the MES Interface function execution log. 6.11.1
Log
Job Execute Log Displays the job execution event log. 6.11.2
■3. List of setting items of DB Connection Service Setting Tool

Reference
section
Service port Specify the number of the port where the DB Connection Service operates.
Set a timeout time (unit: seconds) used when no response may be returned after requesting program
DB access timeout
execution or value writing/reading from the GOT to a database.
Determine whether or not to restrict IP addresses of GOTs whose connection to DB Connection Service 7.5
IP address setting
is permitted.
Output access log Set whether or not to output the access log.
Output SQL failed log Set whether or not to output the SQL failure log.
3-6 3.3 Function List and Setting Item List

3.4 GOT Internal Device (GS)
3.4.1 GOT internal device list
The list of the GOT internal devices (GS) used for the MES interface module is shown below.
POINT
(1) For details of any other GOT internal devices (GS) than the shown areas used for the MES
interface function, refer to the following manual. 3
(2) Values stored in the GOT internal devices (GS) are cleared to 0 when the GOT is powered
OFF and then ON or is reset.
SPECIFICATIONS
Reference
GS Application Name Initial value
section
275 Monitoring interval timeout count 0
670 MES interface No. of trigger buffer data 0

3.4.2
671 function area Trigger buffer overflow count 0
672 to 675 Trigger buffer overflow flag for a job 0
3.4.2 MES Interface Function area

This section explains the details of the special registers used for the MES interface function.
■1. Monitoring interval timeout count (GS275)

The cumulative number of times that a monitoring interval timeout has occurred is stored.
If monitoring interval timeout occurs frequently, check the number of job settings and the trigger condition setting.
For the monitoring interval timeout, refer to the following:
➠ 9.2 About Monitoring Interval Timeout
■2. No. of trigger buffer data (GS670)

The number of trigger buffer data is stored.
When many trigger buffer data is stored for a long time, the GOT becomes busy. As a result, some data may not be
collected.
Check the number of job settings for which [Trigger buffering] is enabled and the trigger condition setting.
■3. Trigger buffer overflow count (GS671)

The cumulative number of times that a trigger buffer overflow has occurred is stored.
The trigger buffer overflow means that 129th trigger data is discarded without being buffered when 128 trigger data is
already buffered.
If trigger buffer overflow occurs frequently, check the number of job settings for which [Trigger buffering] is enabled and
the trigger condition setting.
■4. Trigger buffer overflow flag for a job (GS672 to GS675)

The flag indicates the status of trigger buffer overflow for each job.
When a trigger buffer overflow occurs for a job, the internal device corresponding to the job turns ON.
The following table shows the internal devices that are corresponding to jobs 1 to 64.
Name Job and internal device
GS672 b0 b1 b2 b3 b4 b5 b6 b7 b8 b9 b10 b11 b12 b13 b14 b15
Jobs 1 to 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Jobs 17 to 32 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
Jobs 33 to 48 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
Jobs 49 to 64 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64
3.4 GOT Internal Device (GS) 3-7

3-8 3.4 GOT Internal Device (GS)
4
SETTINGS AND PROCEDURES BEFORE USE OF THE MES INTERFACE FUNCTION

4. SETTINGS AND
PROCEDURES BEFORE USE
OF THE MES INTERFACE
FUNCTION
4.1 Settings and Procedures before Use of the MES Interface
Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 2
4.2 Installation and Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 4
4-1
4.1 Settings and Procedures before Use of the MES Interface Function
This chapter explains the procedures and settings to be done before use of the MES interface function.
The flowcharts for use of the MES interface function are shown here.
POINT
Start the server computer, and then the GOT.
■1. Starting the server computer
Procedure before operation
Server computer/SNTP server computer
Database server computer *1 Application server computer *2 SNTP server computer *3
Start up the SNTP server.
Install a relational database and design Create a user program. *5

a table. *4
Set the ODBC of the database. Create an account for user program
execution. *6
7.2 Setting ODBC of Database
Perform login check with the account

for user program execution. *7
Install DB Connection Service and Install DB Connection Service and

DB Connection Service Setting Tool. DB Connection Service Setting Tool.
4.2 Installation and Uninstallation 4.2 Installation and Uninstallation
Change the settings of DB Connection Change the settings of DB Connection

Service. Service.
7.5 Setting Items of DB Connection 7.5 Setting Items of DB Connection
Service Setting Tool Service Setting Tool
Operation *8
*1 Be sure to make the settings to use the DB interface function.
➠ 5.1 DB Interface Function

*2 Make the settings when using the program execution function.
➠ 5.1.9 Program execution function

*3 Make the settings when using the time on the SNTP server computer.
*4 Restart the personal computer after installing the relational database.
Communication with GOT may fail if not restarted.
*5 Create it only when necessary.
An existing program, a program included in OS, or a commercially available program can also be used.
*6 Always set a password for the account for user program execution.
Use of an account without password will result in execution failure by OS.
*7 If the login is not confirmed, the program execution function may not operate properly.
When installing DB Connection Service and DB Connection Service Setting Tool, log in using a user name with administrative
right.
*8 Do not log in the server computer using an account for user program execution during user program execution.
Doing so may cause incorrect operation of the program execution function.
4-2 4.1 Settings and Procedures before Use of the MES Interface Function
■2. Starting the GOT
Procedure for starting GOT
Preparation of the GOT On the configuration computer
Regist the license of MES Inteface to Install GT Designer3.

*1
GOT.
Connect to Ethernet. *2 Create project data.

4
Install a SD card. Configure MES interface settings.
(Only when needed)
SETTINGS AND PROCEDURES BEFORE USE OF THE MES INTERFACE FUNCTION

Connect the GOT to the configuration computer.
(USB, RS-232, Ethernet *3*4)
Writting the package data on the GOT.

(Including MES interface)
Operation start
*1 Register the license of MES functionality in utility.

*2 For connecting GOT to a device supporting 10BASE(-T/2/5), configure the network that supports both 10Mbps and 100Mbps
communication speeds by using a switching hub.
*3 When using the MES interface function only on the Ethernet, the GOT port No. setting in Communication Detail Settings is
ignored.
*4 Use the Ethernet interface built in the GOT.
4.1 Settings and Procedures before Use of the MES Interface Function 4-3
4.2 Installation and Uninstallation
For how to install and uninstall each execution software for the MES interface function on the operating environment, refer to
the following manual.
➠ GT Works3 Version1 Installation Procedure Manual
4-4 4.2 Installation and Uninstallation

5
5. MES INTERFACE FUNCTION
MES INTERFACE FUNCTION

5.1 DB Interface Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 2
5.2 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 20
5-1
You can use the MES interface function by installing a system application (extended function) of [MES Interface] on the
GOT.
This chapter describes the MES interface function.
POINT
The MES interface function settings are configured on the MES interface function setting screen
of GT Designer3.
5.1 DB Interface Function
The DB interface function executes access to the database in units of jobs.
5.1.1 DB interface function operation

The operation of the DB interface function is shown below.
GOT
Device *6 Tag 1 Job 1
Trigger monitoring *2 Database server computer
Action *3
GD1000 Component Communication action 1 (Update)
Operation action 2
Communication action 3 (Insert)
Resource data send action 4
Database
Executed in
order
Communication action 10 (Select)
Program execution *4
*1 DB buffering *5 Execute
file
Application server computer
*1 Collects tag data.
➠ 5.1.3 Tag function

*2 Activates a job.
➠ 5.1.4 Trigger monitoring function

*3 Accesses the database and performs arithmetic processing.
➠ 5.1.6 SQL text transmission (Communication action)

5.1.7 Arithmetic processing function (Operation action)
5.1.8 Resource data send function (Resource data send action)
*4 Executes programs.

*5 Temporarily stores SQL texts that cannot be sent due to a communication error.
➠ 5.1.10 DB buffering function

*6 For devices usable for the MES interface function, refer to the following.
➠ 3.2 GOT Devices Available for the MES Interface Function
5-2 5.1 DB Interface Function

5.1.2 Job execution procedure
The following is the job execution procedure.
Start
Stopped
Is the GOT working?
No job is executed during the stop.

Working Activate the GOT.
?6.10.1 Checking the MES Interface Function status
(Status)
?6.10.2 Manipulating the MES Interface Function status
(Operation)
5
Disabled
Is the job enabled?

The job is not executed when it is disabled.
Enabled Enable the job.
?6.10.3 Changing the job status (Change job status)
Job execution starts when trigger conditions are met.

?5.1.4 Trigger monitoring function
?6.7.2 Setting items in Trigger conditions
When [Handshake operation] is selected for Trigger conditions,

tag component values are obtained again.
Is the [Execute Not checked

program before action.] box
checked?
Checked
The program in the application server computer is
executed before execution of the first action.
?5.1.9 Program execution function
?6.7.3 Setting items in Program execution
(To the next page)
5.1 DB Interface Function 5-3

(From the previous page) Executed in order
Actions are executed.

Up to 10 actions can set for a job, and they are
executed in order.
?5.1.6 SQL text transmission (Communication action)
?5.1.7 Arithmetic processing function (Operation action)
?5.1.8 Resource data send function (Resource data send
action)
?6.8 Job Settings - Actions
In Update/Insert actions, substitute or insert values are

committed to database.
Is the [Execute
Not checked
program after action.]
box checked?
Checked
The program in the application server computer is
executed after execution of the last action.
?5.1.9 Program execution function
?6.7.3 Setting items in Program execution
If a value was written to a tag component, it is written

to the device data of the PLC CPU.
Job execution is completed.
End
POINT
For the case where an error occurs during job execution, refer to the following:
➠ 5.1.10 ■2. When an error occurs in job execution
5.1.3 Tag function

The tag function collects device data of the GOTs on the network in units of tags.
Assigning a database field to a tag component allows reading or writing of a database value or device data that is specified
by the tag component.
For the tag function setting, refer to the following:
➠ 6.5 Device Tag Settings
GOT
Device tag name: Process1

Device Component name Device Data type
Read
GD1000 Work_No. GD1000 Single
GD2000 Parameter GD2000 Double
GD2001 Write

5.1.4 Trigger monitoring function
The trigger monitoring function monitors values such as the time and tag values and, when the trigger condition changes
from false to true (when the condition is met), starts a job.
The following setting options are available as conditions for start.
• [Time specification startup]: Starts the job at the specified time.
• [Specified time period startup]: Starts the job at the specified intervals (Unit: Seconds).
• [Value monitoring startup]:
Compares the actual tag component value with the condition value (tag component value or constant value) at every
sampling times, and starts the job when the condition is met.
• [Handshake operation]:
Starts the job on request from the GOT.
Completion of job execution can be reported to the GOT.
• [At GOT startup]:
Starts the job only once when the GOT starts up.
Two kinds of conditions can be used in combination for starting a job.
For the trigger monitoring function setting, refer to the following:
5
➠ 6.7.2 Setting items in Trigger conditions
Tag

Component
Value monitoring
startup Job
Time specification
1st of every month, 9:00:00 startup Trigger
Specified time Conditions met Job startup
3600 seconds monitoring
period startup
Handshake
operation
ON
OFF

POINT
In [Value monitoring startup], tag component values used for triggering monitoring and those
used in the activated job are collected at different timings without synchronization.
Tag 1 Sampling cycle: 1s

Job Component name Value
Component A 10 Sampling time 10:08:30
Component B 20

Trigger When Tag 1Component A is 10 Component name Value Sampling time 10:08:00
Component B 5
Action 1) Add Tag 2 Component B to Tag 1 Component B.
Action 2) Send Tag 3 Component C to database Component name Value
Component C 12
Sampling time 10:08:21
Component D 3
Component E 4 (Too many components,
Component F 8 sampling delayed)
: :
To synchronize collection of the above tag component values, perform either of the following
(Plan 1) or (Plan 2).
(Plan 1)
Use [Handshake operation].
➠ 6.7.2 ■8. Handshake operation
Job Component name Value
Component A 10 GOT device
Component B 20
Trigger When startup tag component turns ON Tag 2 Sampling cycle: 60s
(Handshake Component name Value GOT device
operation setting) Component B 5
Action 1) Add Tag 2 Component B to Tag 1 Component B. Tag 3 Sampling cycle: 1s

Component name Value
Action 2) Send Tag 3 Component C to database Component C 12
Component D 3 GOT device
Component E 4
Component F 8
: :
(Plan 2)
Put the tag components used in a job into one tag.
Since the tag components collect the specified GOT device values during job execution, the
execution time of the job is increased.
Job

Component name Value
Component A 10
Trigger When Tag 1Component A is 10 Component B 20
Component B' 5
Component C 12 Sampling time 10:08:21
Action 1) Add Tag 1 Component B' to Tag 1 Component B.
Component D 3
Action 2) Send Tag 1 Component C to database Component E 4
Component F 8
: :

5.1.5 Trigger buffering function
When too many trigger conditions (data transmission conditions) are met simultaneously, the trigger buffering function
allows the system to buffer the data and time trigger conditions are met to the user area of the GOT. The action (operation
and transmission of the data) for the buffered data is executed later.
Even when the data transmission triggers are activated frequently, no triggers are missed so that all the jobs are executed.
Enable [Trigger buffering] in each job setting to utilize the trigger buffering function.
■1. Trigger buffering function

The following describes the behavior of a job for which [Trigger buffering] is enabled.
(1) When normal (Interval that trigger conditions are met is longer than processing time of action)
• When trigger conditions are met, the tag data and the time are stored in the trigger buffer.
• The action, which is specified by the data stored in the trigger buffer, is executed immediately.
[GOT]
[When normal] Data
Job 1
Trigger buffer Job 1
trans- 5
mission
Trigger Action is
conditions executed Database
are met

Time Time
(2) When busy (Interval that trigger conditions are met is shorter than processing time of action)
• Tag data and time that conditions are met are stored to the trigger buffer every time the conditions are met.
• If an action cannot complete before another condition is met, up to 128 trigger data can be stored.
[GOT]
[When busy] Data
Trigger buffer trans-
Job 1 ... 1)
Trigger conditions Job 1 ... 2) Trigger data (Tag data and time)
mission
are met
Job 3 ... 3) Trigger data (Tag data and time) Database
Job 1 ... 2) Job 1 ... 1)
Trigger conditions
are met Action is
executed The action for "Job 1 ... 1)" is executed.
Job 3 ... 3) The trigger data of "Job 1 ... 2)" and
Trigger conditions
are met "Job 3 ... 3)" is stored to the trigger buffer.
Time Time
The numbers 1) to 3) correspond to the order of that trigger conditions are met.
In this example, the jobs 1 and 3 access the same database.

(3) When becoming less busy (Interval that trigger conditions are met is longer than processing time
of action)
• The action, which is specified by the data stored in the trigger buffer, is read and executed sequentially.
• When the action for the trigger data in the trigger buffer completes, the trigger data is cleared, and another trigger
data can be stored.
[GOT]
[When becoming less busy] Data
Trigger buffer trans-
Job 1 ... 2)
mission
Action is
executed Database
Job 3 ... 3)
Action is
executed The action for "Job 1 ... 1)" is executed.
The action for "Job 1 ... 2)" and "Job 3 ... 3)",
which is specified by the data in the trigger
buffer, is executed sequentially.
Time Time
The numbers 1) to 3) correspond to the order of that trigger conditions are met.
In this example, the jobs 1 and 3 access the same database.
POINT
(1) For job operation for which [Trigger buffering] is disabled, refer to the following:
➠ 5.1.10 ■1. Operation behavior of jobs
(2) Whether the condition is changed from false to true is judged at collection of the tag.
■2. Maximum times of trigger buffering

(1) The trigger buffering function allows up to 128 trigger data (tag data and time) to be stored
simultaneously.
A job can be stored for unlimited number of times.
(2) Check status of the trigger buffering in the following.
• Number of jobs in the trigger buffer (GS670)
• [MES Interface] - [Diagnostics] tab
➠ 6.10.6 Checking the trigger buffering (Trigger buffering status)
(3) If 128 conditions are already met and another condition is met, the trigger of the new condition is
discarded.
Check the number of discards in the trigger buffer overflow (GS671).
■3. Clearing trigger buffer

Any of the following operation clears the trigger buffer.
• Power off the GOT.
• Reset the GOT (when changing the communication settings, etc.)
• Install the OS from GT Designer3
• Download project data, etc.
• Stop the MES interface function operation by [MES Interface] - [Diagnostics]
➠ 6.10.2 Manipulating the MES Interface Function status (Operation)

5.1.6 SQL text transmission (Communication action)
The SQL text transmission function allows automatic creation of SQL texts, enabling communications with the database.
The following three types of commands can be selected for the SQL text.
• Select/MultiSelect
• Update
• Insert
For the SQL text transmission setting, refer to the following:
➠ 6.8.1 Setting items in Communication action
■1. Select/MultiSelect
Select/MultiSelect is used to write a database value to a tag component value area or to store it in the temporary
variable area by sending a SQL text to the database.
When a value is stored in the temporary variable area, it can be used as a variable for other actions.
■2. Update and Insert

Update and Insert are used to add a tag component value or a temporary variable to an SQL text and write the value to 5
the database.
Database server computer

Select/MultiSelect
Select...
Tag Component
Temporary variable Data
Update
Tag Component Update...
Temporary variable Data Database
Constant
Insert
Tag Component Insert...
Temporary variable Data
Constant
5.1.7 Arithmetic processing function (Operation action)

The arithmetic processing function performs operations for tag component values.
In this function, up to 20 dyadic operations can be processed per operation action.
By storing an operation result in the temporary variable area, complicated operations are also executable.
For the arithmetic processing function setting, refer to the following:
➠ 6.8.2 Setting items in Operation action
An operand is selectable from

tag component, constant and
temporary variable.
Temporary Tag component Tag component

variable Constant Constant
Temporary Tag component Up to 20 dyadic operations

Tag component Constant
variable can be performed for one
operation action.
The result can be Four operations and

assigned to a tag remainder can be specified
component or by corresponding operators.
temporary variable.
Executed in order

5.1.8 Resource data send function (Resource data send action)
The resource data send function allows the GOT to send resource data collected in a GOT buffering area and a CF card to
a database.
Device values for controllers, alarm data for the GOT, and others can be stored to the database without any communication
programs.
For the resource data send function settings, refer to the following.
➠ 6.8.3 Setting items in Transmit resource action
Data transmission
Database
Time No Count
08:20:10 101 10
08:30:20 102 11
08:30:30 105 12
Logging data, alarm data and others
■1. Resource data send function

(1) Available data to be sent
For using the resource data send function, set [Transmit resource action] in the action for [Job settings].
The following resource data can be sent to a database.
Resource data Description
Logging data Logging data collected by the logging function
Advanced user alarm Alarm data collected by the advanced user alarm observation setting
Alarm data
Advanced system alarm Alarm data collected by the advanced system alarm observation setting
Operation log data GOT operation history data collected by the operation log function
(2) Resource data to be sent

(a) Settings on the resource data send action for the collected resource data
The GOT sends the resource data before and after turning on the GOT.
Specifying the number of resource data and the time of collecting the data or others are available.
This setting allows the GOT to send resource data when the loads on the GOT and controllers are lower.
[Resource data]
Data collected before Sending data at

turning on GOT* the first action
Turning on GOT
Data collected after
turning on GOT
First action
Sending data at
Database
the second action
Data collected after the
first action
Sending data at
Second action the third action
Data collected after the
second action
Third action
*Excluding logging data at the first action
5 - 10 5.1 DB Interface Function

POINT
The GOT sends the resource data to the database only one time. The GOT does not send the
sent data to the database on the subsequent actions. Unnecessary data is not stored to the
database.
The GOT may send the sent data to the database in the following cases.
• When turning on the GOT
• When restarting the GOT (Downloading a project data or others)
➠ 6.12 Precautions
(b) Sending one resource data at the multiple resource data send actions
When one resource data is sent at the multiple resource data send actions, the resource data is sent and stored
to the database for each action.
[Resource data]
Data collected before

turning on GOT
5
Turning on GOT
Resource data for the first action A
Resource data for the first action B

First action A
First action B
Collected data
Resource data for the second action A
after turning on
Resource data for the second action B
GOT
Second action A
Second action B
Resource data for the third action A
Third action A
Resource data for the action A is sent again when the action B is executed.
5.1 DB Interface Function 5 - 11

5.1.9 Program execution function
The program execution function is used for executing programs in the application server computer before execution of the
first action and after execution of the last one in a job.
For the program execution function setting, refer to the following:
➠ 6.7.3 Setting items in Program execution
Programs that can be executed from [Command line] are applicable.
Since program execution is set on the application server computer as described below, more sophisticated data linkage can
be realized.
■1. Before executing the first action of the job

By executing programs before the first action of the job, data required for the job can be produced on the database in
advance.
■2. After executing the last action of the job

By executing programs after the last action of the job, data written to the database by the job can be utilized for
programs on the application server computer.

5.1.10 DB buffering function
■1. DB buffering function
The DB buffering function temporarily stores SQL texts into a CF card when they cannot be sent due to network
disconnection or failure of the database server computer.
After recovery, the buffered SQL texts are automatically sent to the database. (Manual operation is also possible.)
Disconnected
Database
INSERT
INSERT
INSERT
UPDATE
5

SD card
Recovered
Resend
Database
INSERT
INSERT
INSERT
UPDATE
SD card
POINT
(1) To automatically send SQL texts after recovery, irrespective of transmission
sequence, select the auto-resend processing.
➠ 5.1.10 ■5. (3) Automatically resending data after recovery
(2) To send SQL texts after recovery, without changing the transmission sequence, select
the manual resend processing.
➠ 5.1.10 ■5. (4) Manually resending data

■2. Factors for starting DB buffering
The DB buffering is conducted when SQL texts cannot be sent to the database by the following factors:
• Network disconnection
• Failure of the database server computer
• Failure of the database software
POINT
(1) If an error occurs when the sent SQL text is executed on the database, by some
reason such as its incorrectness or inconsistency with the database, buffering is not
performed and an SQL failure log is output on the database server computer.
➠ 7.1 DB Connection Service Functions
(2) When SQL texts cannot be sent to the database due to network disconnection or
failure of the database server computer, DB buffering is not performed until the
connection timeout is detected (approx. 10 seconds).
➠ 5.1.10 ■7. When SQL texts cannot be sent to the database
Even if a trigger condition is met again during connection timeout detection, the
corresponding job is not executed.
(3) If SQL texts cannot be sent to the database due to failure of database software, DB
buffering is not performed until detection of DB access timeout.
➠ 5.1.10 ■7. When SQL texts cannot be sent to the database
Time for detecting DB access timeout is set to 30 seconds by default.
➠ 7.5.2 DB access timeout (required) (Range: 1 to 3600; Default: 30)
Even if a trigger condition is met again during detection of DB access timeout, the
corresponding job is not executed.
■3. Jobs applicable to DB buffering

Jobs performing Update or Insert actions can be stored in the DB buffer.
The DB buffering is not available for jobs performing Select/MultiSelect action.
■4. Setting the DB buffering
Start
Configure the settings for the DB buffering function.

6.9.1 Setting items in DB buffering settings
Set whether to enable or disable the DB buffering for

each job.
6.7.4 Setting items in DB Buffering
End

■5. DB buffering operation
(1) When no data are currently stored in the DB buffer
Start

Were the SQL texts sent Sent

to the database?
Sent to the database without being stored in the DB
■2. Factors for starting DB buffering buffer.
Not sent
5
Is the [Enable DB buffering] Not checked
box checked?

When disabled, the job execution is canceled without
6.7.4 Setting items in DB Buffering DB buffering.
5.2 Precautions
Checked
DB buffering is started.
End
POINT
Check the DB buffer status (No. of bufferings, utilization) and prevent the full status of the DB
buffer.
➠ 6.7.4 Setting items in DB Buffering
6.10.5 Manipulating DB buffering (DB buffering operation)

(2) When some data are currently stored in the DB buffer
Start
Yes Is "Manual resend" selected

for the job?

No
Were the SQL texts sent Sent

to the database?
(3) Automatically resending data after recovery
Not sent
Is the [Enable DB buffering] Not checked

box checked?
When disabled, the job execution is canceled without
DB buffering.
Checked 5.2 Precautions
DB buffering is started. *1
End
*1 When accumulated job data currently exist in the DB buffer.

Job settings DB buffer
Job 1 (Auto) Job 3_SQL TEXT (Auto)

Job 2 (Auto) Job 6_SQL TEXT (Manual)
Stored in the order
Job 3 (Auto) that trigger conditions Job 4_SQL TEXT (Manual)
Job 4 (Manual) are met. Job 1_SQL TEXT (Auto)
Job 5 (Manual) Job 2_SQL TEXT (Auto)
Job 6 (Manual) Job 5_SQL TEXT (Manual)
POINT
Check the DB buffer status (No. of bufferings, utilization) and prevent the full status of the DB
buffer.

Start
Execution of the job with Auto resend setting is started.

1) The job with Auto resend setting is sent to the database
without being buffered. *1
In the order of storing the jobs data in the DB buffer,

2) the accumulated data of the jobs with Auto resend
setting are sent again. *1
Is there any job for which Yes

Manual resend is selected?
No
3)
Job with Manual resend setting will not be sent even
after recovery. 5
(4) Manually resending data
End

*1 Automatically resends job data after recovery.
The numbers 1) to 3) correspond to those shown in the above.
Job settings DB buffer Database
Job 1 (Auto) Job 3_SQL TEXT (Auto) Job 10_SQL TEXT (Auto)
Job 2 (Auto) Job 6_SQL TEXT (Manual) Job 3_SQL TEXT (Auto)
Job 3 (Auto) Job 4_SQL TEXT (Manual) Job 1_SQL TEXT (Auto)
Job 4 (Manual) Job 1_SQL TEXT (Auto) 2) Job 2_SQL TEXT (Auto)
Job 5 (Manual) Job 2_SQL TEXT (Auto)
3)
Job 10 (Auto)
1)

(4) Manually resending data
Start
Execute manual resend of the DB buffer data. After line recovery, retry the manual resend of DB buffer
Request for resend on [MES interface setting] - [Diagnosis] data.
tab
Request for resend on [Resend DB buffer request] of the
specified tag component
?6.9.1 Setting items in DB buffering settings
?6.10.5 Manipulating DB buffering (DB buffering operation)
Were the SQL texts sent Not sent

to the database?
Sent
In the order of storage in the DB buffer, the accumulated data
1)
of the jobs with Manual resend setting are sent again. *1
If a job with manual resend setting is started during manual

2)
resending, its SQL texts are stored in the DB buffer and then
sent to the database. *1
Not completed Has all the manual resend

processing been completed?
Completed
If a job with manual resend setting is started after completion
3) of manual resending, its SQL texts are sent to the database
if it is accessible, without being buffered. *1
Is there any job for which Yes

Auto resend is selected?
Data of the job with Auto Resend setting are sent again
No after recovery.
End
*1 Manually resending data

The numbers 1) to 3) correspond to those shown in the above.
Job setting DB buffer Database
Job 1 (Auto) Job 3_SQL TEXT (Auto) 1) Job 6_SQL TEXT (Manual)
Job 2 (Auto) Job 6_SQL TEXT (Manual) Job 4_SQL TEXT (Manual)
Job 3 (Auto) Job 4_SQL TEXT (Manual) Job 5_SQL TEXT (Manual)
Job 4 (Manual) Job 1_SQL TEXT (Auto) Job 10_SQL TEXT (Manual)
Job 5 (Manual) Job 2_SQL TEXT (Auto) Job 11_SQL TEXT (Manual)
Job 10 (Manual) 2)
Job 11 (Manual)
3)
POINT
If any of the jobs for which manual resend is selected exists in the DB buffer, it remains there
after recovery until manual resend is executed.

■6. Clearing the DB buffer
The DB buffer is cleared by the following:
• After downloading the project data, for which the MES interface function is set, to the GOT, powering OFF and ON or
restarting the GOT
• Clear request from [MES interface setting screen] - [Diagnosis tab].
➠ 6.10.6 Checking the trigger buffering (Trigger buffering status)
• Clear request from [Clear DB buffer request] of the specified tag component
➠ 6.9.1 Setting items in DB buffering settings
■7. When SQL texts cannot be sent to the database

(1) When auto-send is selected for the job
Step 1. If SQL texts cannot be sent to the database due to network disconnection or failure of the database server
computer or database software, the system starts DB buffering after detection of a timeout.
5
Step 2. After DB buffering is started, whether SQL texts can be sent to the database or not is checked every time
each job is activated.
Step 3. When the system has not been recovered from network disconnection or failure of the database server

computer or database software, DB buffering is executed after detection of the timeout.
Recovery from network

disconnection
Job startup Job startup Job startup
After sending Sending SQL

SQL texts, texts
timeout detected
DB buffering executed DB buffering execution Auto-resending
after checking if SQL DB buffer data
texts can be sent
(2) When manual resend is selected for the job
Step 1. If SQL texts cannot be sent to the database due to network disconnection or failure of the database server
computer or database software, the system starts DB buffering after detection of a timeout.
Step 2. After started, DB buffering is performed without checking whether SQL texts can be sent to the database
or not for each job activation.
Step 3. The data stored in the DB buffer are resend when manual resend is executed.
Recovery from network

disconnection
Job startup Job startup Manual resend operation
After sending
SQL texts,
timeout detected
DB buffering executed DB buffering executed Resending DB buffer data
■8. Precaution on the DB buffering

Do not remove the CF card from the GOT during DB buffering.

5.2 Precautions
■1. Operation behavior of jobs
(1) When a trigger condition for a job is met again during execution of the job
(a) Jobs for which [Trigger buffering] is disabled
A new job is not executed during execution of the previous job.
(Example)
When a trigger condition for a job is met again during execution of the job set to [Value monitoring startup]
Condition value
Interval
of tag Tag component value
sampling
:Trigger conditions are met

Job Job Job :Job is not started after trigger
startup startup startup conditions are met
Job execution 1) 2) 3)
A new job is not executed during execution of the previous job.
(b) Jobs for which [Trigger buffering] is enabled

Trigger data is stored to the trigger buffer, and the job for the stored trigger data is executed after completion of
the previous job.
(Example)
When a trigger condition for a job is met again during execution of the job set to [Value monitoring startup]
Condition value
Interval
of tag Tag component value
sampling
:Trigger conditions
are met
Trigger data 2)
3) Trigger buffer
4)
Job Job Job Job Job
startup startup startup startup startup
Job execution 1) 2) 3) 4) 5)
(2) When trigger conditions for multiple jobs are met concurrently
• Up to three jobs can start their executions concurrently in the order in [Job settings].
• After completion of these jobs, executions of the other jobs are started sequentially.
Note that, if a job uses the same item in [Server service settings] that is currently used for another job, the job is not
executed until another job execution is completed.
5 - 20 5.2 Precautions
(3) When actions are set for a job
When actions are set for a job, if a communication error occurs, a timeout time will be generated.
In the case of multiple action settings, timeout time is generated for each action.
For the timeout time, refer to the following.
➠ 7.5 Setting Items of DB Connection Service Setting Tool
Job execution
Program execution (before actions)

Action 1
Action 2
Action 10
Program execution (after actions)
5
Timeout time occurs for each.
The time taken until completion of the job is obtained from the formula shown below.

No. of communications Timeout time
No. of communications: Total number of set communication actions and program executions
Example) Time taken until completion of a job in the event of a communication error
No. of communications: 10 + 1 + 1 = 12
Time taken until job completion: 12 30s = 360s
Item Setting
Communication action 12
Program execution (before action) 1
Program execution (after action) 1
Timeout 30 seconds
(4) Monitoring interval timeout

Depending on the number of set jobs or the trigger condition setting, the monitoring interval timeout may be
generated.
➠ 9.2 About Monitoring Interval Timeout
5.2 Precautions 5 - 21
■2. When an error occurs in job execution
(1) The job execution is canceled when the error cause is the following:
• Failure in device data writing due to network disconnection within the PLC system
• Failure in device data writing, or operation error
• Failure in access to the database (Except jobs for which [Enable DB buffering] is selected)
(2) If a job execution is canceled, the operation processed before the error occurrence returns to the
status before the job execution.
POINT
The following explains access to GOT device data and the database.
(1) GOT device data
Since all of data are written to the device data area in the GOT at a time upon completion of
job execution, any change due to the error is not reflected in the device data of the GOT.
(2) Database
Rollback is executed assuming the time immediately before job activation as a commit point.
When an error occurs during inserting data into a database, the data inserted into the
database before occurring the error are reflected.
(3) When [Notify errors (job cancellation) that occur during job execution] has been selected, a value
is assigned to the specified tag component.
➠ 6.7.5 Notify errors (job cancellation) that occur during job execution
6. MES INTERFACE FUNCTION 6
SETTING
MES INTERFACE FUNCTION SETTING

6.1 MES Interface Function Setting Screen . . . . . . . . . . . . . . . . . . . 6 - 2
6.2 Displaying the MES Interface Function Setting Screen . . . . . . 6 - 2
6.3 Screen Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 3
6.4 Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 5
6.5 Device Tag Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 6
6.6 Server Service Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 16
6.7 Job Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 20
6.8 Job Settings - Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 35
6.9 Option Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 72
6.10 Diagnosis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 76
6.11 Working Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 81
6.12 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 86
6-1
6.1 MES Interface Function Setting Screen
The MES interface function setting screen is a screen for configuring various settings required for the MES interface
function.
In addition, the operation status of the MES interface function and the working log can be checked, and other operations
such as stop/restart of the MES interface function can be also performed.
6.2 Displaying the MES Interface Function Setting Screen

Step 1. Start GT Designer3.
For how to start GT Designer3, refer to the following manual.
Step 2. Perform the following:

• Select [Common] [MES Interface] from the menu.
Step 3. The MES interface screen is displayed. Configure the settings referring to the following descriptions.
6-2 6.1 MES Interface Function Setting Screen

6.3 Screen Structure
This section explains the structure of the MES interface function setting screen.
6.3.1 Screen structure

Title bar
Tab
Edit items tree

6.3.2 Operations
using the Edit items
Detailed setting
edit screen

POINT
(1) Display on the title bar
On the title bar, the status of connection to the GOT is displayed.
The connection status displays are shown below.
Connection type Display Remarks
RS232 (Connect Type RS232 COM1) Displays the communication port.
USB (Connect Type USB) ?
(Connect Type Ethernet

Ethernet Displays the IP address.
192.168.3.10)
(2) Column width adjustment

The column width of the tables can be adjusted on the MES interface function setting
screen.To adjust the width, drag the right boundary line of the column.When only a part of a
long item name is displayed, this adjustment is useful.
6.3 Screen Structure 6-3

6.3.2 Operations using the Edit items tree
The Edit items tree shows overall MES interface function settings in a tree.
This section explains the operations using the Edit items tree.
Project root
Item
Setting type
■1. Selecting an item

Step 1. When double-clicking the project root or each setting type, some items are displayed.
Step 2. Selecting one of the items displays the corresponding edit screen on the detailed setting edit screen area.
■2. Adding an item

Step 1. Selecting an item or a setting type to be added and performing either of the following will add the item.
• Select an item of the same type or a setting type, right-click the mouse, and choose [Add].
• Double-click a setting type that contains no item.
Step 2. When the item is added properly, it is automatically selected and the edit screen is switched to the one for
the added item.
POINT
Since the number of items that can be added is limited depending on the setting type, refer to the
relevant section of each item.
■3. Deleting an item

Step 1. Select an item to be deleted and right-click the mouse. Selecting [Delete] deletes the item.
POINT
For precautions on the item deletion, refer to the following.
➠ 6.12 ■2. When deleting an item
■4. Replicating an item

Step 1. Select an item to be copied, right-click it to display the menu. Selecting [Copy & Paste] replicates the item.
Step 2. When the item is added properly, it is automatically selected and the edit screen is switched to the one for
the added item.
POINT
Since the number of items that can be added is limited depending on the setting type, refer to the
relevant section of each item.
6-4 6.3 Screen Structure

6.4 Setting
Configure the settings for the MES interface function.
Step 1. Click the "Setting" tab.
Step 2. The "Setting" sheet is displayed on the detailed setting edit screen.
For each of the setting items, refer to the section shown below.

Item Description Reference section
Device tag settings Configure the settings for the tag function. 6.6
Server service settings Configure the settings for access to a server computer. 6.7
Job settings Configure the settings for the DB interface function. 6.8
Option Setting Configure the DB buffering function setting. 6.9
6.4 Setting 6-5

6.5 Device Tag Settings
Configure the settings for the tag function.
For the tag function, refer to the following:
➠ 5.1.3 Tag function
Configured tags are used in [Job settings], etc.
Step 1. Double-clicking [Device tag settings] in the Edit items tree displays relevant items.
Make the setting referring to the following descriptions.
POINT
(1) How to add, delete, or copy an item
For addition, deletion or copying of items, refer to the following:
➠ 6.3.2 Operations using the Edit items tree
(2) When an item is added or copied, a "New Tag" item is added.
6-6 6.5 Device Tag Settings

6.5.1 Setting items in Device tag settings
Up to 64 items can be set in [Device tag settings] within one project.
?? ??
Device tag name Enter a device tag name. (Up to 16 characters)

6
Set whether to periodically sample the tag or not.
Sampling setting
Set a sampling interval to sample the tag.
Set whether to use arrays for the tag or not.

Array setting
➠ 6.5.2 Setting items in Array setting
Configure the tag component settings.

Component setting input
➠ 6.5.3 Setting items in Component setting
Displays a list of the components that have been already set.

Component list
Array block size Make setting when changing the block size manually.
No. of tag components in project Displays the number of all the tag components in the project.
Displays the number of the components in the project, for which [Perform statisticcal processing] is
No. of statistical processings in project
selected.
No. of device points in tag Displays the number of total device points used in [Device Tag setting].
■1. Device tag name (Up to 16 characters)

Enter a device tag name.
Configured tags are used in [Job settings], etc.
For characters that can be used for device tag names, refer to the following:
➠ 9.1.2 Characters applicable to item names, component names, variable names, etc.
Note that using the name same as the one set in [Server service settings] is not allowed.
■2. Sampling setting

(1) When sampling is enabled
The tag is sampled in the specified interval.
When selecting [Sampling], also set a sampling interval in units of seconds. The setting range for the interval is 1 to
32767 seconds.
(2) When sampling is disabled
The tag is not sampled. When [Do not sample] is selected, statistical processing cannot be performed for tag
component values.
6.5 Device Tag Settings 6-7

POINT
(1) The GOT becomes less busy if [Do not sample] is selected for the following tags.
• Tags only for writing
• Tags for sampling device values with the handshake operation.
For the handshake operation, refer to the following:
➠ 6.7.2 ■8. Handshake operation
(2) When [Do not sample] is selected, the setting items for reading tags cannot be selected for
the tag. (Except cases that [Handshake operation] is set for the trigger conditions.)
• Tag component values that are set in [Select/Update conditions] in [Select] of
[Communication action]
(3) When [Array setting] is set for the tag, [Do not sample] is fixed for the sampling setting.
6.5.2 Setting items in Array setting

An array is a data format, in which the specified number of data of the same data type are arranged sequentially. The Array
setting is set when writing multiple records extracted from a database to the same tag component.
Either of the following can be selected for device assignment to each tag component.
• Assigning consecutive devices to each tag component (series)
• Handling all tag components as a block and assigning the same kind of devices in a series of blocks (block)
Tags with array settings are used for [MultiSelect].
■1. Use array

When the [Use array] checkbox is checked, the tag is arranged as arrays.
POINT
(1) When the array setting is set, device data are not collected.
(2) The array setting is unavailable for the tags set for the actions in [Job settings].
■2. Length of array (Range: 2 to 40000, Default: 2)

Set the number of arrays for the tag.
6-8 6.5 Device Tag Settings

■3. Series/Block (Default: Series)
Select a method for the array setting.
(1) Series
Devices of respective tag components are arranged consecutively.
(Example) When [Length of array] is set to 4 with [series] setting
Only the start device (device in n=1) need be set.
Devices in and after n=2 are configured automatically.
n=1 n=2 n=3 n=4
Component A GB0 GB1 GB2 GB3

GD100 GD102 GD104 GD106
Component B to GD101 to GD105 to GD107
to GD103
GD1000 GD1004 GD1008 GD1012
Component C to GD1003 to GD1007 to GD1011 to GD1015
(2) Block
Devices of all tag components are arranged as a block.
The size of the block can be changed in [array block size].
For [array block size], refer to the following.
6
Usually, the block size need not be changed because it is automatically adjusted to avoid device duplication.
(Example) When [Length of array] is set to 4 with [block] setting
Only the start device (device in n=1) need be set.

Devices in and after n=2 are configured automatically
n=1 n=2 n=3 n=4
Component A GD0 GD7 GD14 GD21

Component B GD1 to GD2 GD8 to GD9 GD15 to GD16 GD22 to GD23
Component C GD3 to GD6 GD10 to GD13 GD17 to GD20 GD24 to GD27
Block
POINT
When device types are different, [block] cannot be selected.
For the device types, refer to the following.
6.5 Device Tag Settings 6-9

6.5.3 Setting items in Component setting
Configure the settings for assigning GOT devices to tags.
Up to 256 components can be set for one tag.
Up to 4096 components can be set for one project.
(Adding a component)
• Set required items in [Component setting input], and click the Add button.
• The component is added in [Component list].
(Modifying a component)
• When a component to be modified is selected in [Component list], its settings are displayed in [Component setting input].
• Modify the item settings in [Component setting input], and click the Replace button.
(Deleting a component)
• Select a component to be deleted in [Component list], and click the Delete button.
(Deleting the settings in [Component setting input])

• Clicking the Clear button deletes the settings in [Component setting input].
Item Description
Component name Enter a component name. (Up to 16 characters)
Head device Set device name.
Component Data type Select the data type of the sampling data.
setting input
Set a character string length when [String] is selected for [Data type].
Character string length
(1 to 32 characters)
Perform statistical processing Set whether to perform statistical processing or not.
Component name Displays a component name.
Device Displays a device range used.
Data type Displays a data type.
Component List When [Perform statistical processing] is set, displays the type of
Statistical type
statistical processing.
When [Array setting] is set, displays the device range of array No.n.
Device [n] For a display example, refer to the following.
➠ 6.5.2 Setting items in Array setting
6 - 10 6.5 Device Tag Settings

Item Description
Displays the array No. that is currently displayed in [Device [n]] of [Component
n (Arrray No.)
List].
If this is clicked, the device range of the first array is displayed in [Device [n]] of
[Component List].
< button When the device range of the first array is already displayed, this button cannot be
clicked.
If this is clicked, the device range of the previous array is displayed in [Device [n]]
of [Component List].
< button When the device range of the first array is already displayed, this button cannot be
clicked.
If this is clicked, the device range of the next array is displayed in [Device [n]] of
[Component List].
> button When the device range of the last array is already displayed, this button cannot be
Component List clicked.
If this is clicked, the device range of the last array is displayed in [Device [n]] of
< [Component List].
button When the device range of the last array is already displayed, this button cannot be
clicked.
button
Selecting a component in [Component List] and clicking the button reverses
the order between the selected component and the one immediately above it.
6
The button cannot be clicked on the first component.
Selecting a component in [Component List] and clicking the button reverses

button the order between the selected component and the one immediately below it.
The button cannot be clicked on the last component.
Array block size Make setting when changing the block size manually.
POINT
The following are displayed on the status bar of [Device Tag setting].
• [No. of tag components in project]
The total number of tag components in the project is displayed.
• [No. of statistical processings in project]
The number of component settings in the project, for which [Perform statistical processing] is
checked, is displayed.
• [No. of device points in tag]
The total number of device points used in [Device tag settings] is displayed.
Up to 40000 device points can be set for a tag with [Array setting].
■1. Component name (Up to 16 characters)

Enter a component name.
For characters that can be used for component names, refer to the following:
■2. Device
• Set a device type and an actual device number.
• Bit specification is not allowed for word devices.
• For accessible devices, refer to the following:
6.5 Device Tag Settings 6 - 11

■3. Data type
Select the data type of the sampling data (device data).
Item Description Selectable Device
Single word Handles data as single word data (16-bit Integer type). Word
Double word Handles data as double word data (32-bit Integer type). Word
Real number Handles data as floating point data. Word
Bit Handles data as bit data (in units of bits (0/1)). Bit
String*1 Handles data as character strings. Word
*1 When [Data type] is [String], device values are processed as follows:

• When the device value is not an ASCII code or JIS code
It is replaced with "." (period: 2EH).
• When the device value is a model-dependent character
The character code may be converted when an action is executed.
• When the device value is a termination character (NULL code: 00H)
The character data following it are ignored. (The character string is regarded as terminated.)
■4. Character string length (2 to 32 characters)

(1) Set a character string length when [String] is selected for [Data type].
(2) When [String] is selected, data are stored as follows:
(a) When the value length is shorter than the character string length
NULL codes (00H) are stored after the stored values.
Example: "ABCD" is stored in the device of the tag component, whose character length is 8.
A B C D
41h 42h 43h 44h 00h 00h 00h 00h
(b) When the value length is longer than the character string length
The values whose quantity is equal to the character string length are stored.
Example: "ABCD" is attempted to be stored in the device of the tag component, whose character length is 2.
"AB"
(3) Odd numbers are not allowed for the character string length setting.
Set an even number for the character string length.

■5. Perform statistical processing
(1) Set whether to perform statistical processing or not.
Up to 64 components that have [Perform statistical processing] setting can be set in all projects. (Check [No. of
statistical processings in project] on the status bar.)
When the [Perform statistical processing] box is checked, statistical processing is performed for tag component
values.
Statistically processed values can be used by specifying the tag component values, for which [Perform statistical
processing] is selected, in [Job setting].
Note that this setting is not available when:
• [Do not sample] is selected in [Sampling setting].
• The data type of the tag component is [String].
• [Array setting] is set.
(2) When [Perform statistical processing] is selected, set the following items.
Item Description
Statistical type Select a type of the statistical processing.
Specify the number of samples when [Moving average], [Moving maximum], or [Moving
No. of samples
minimum] is selected.
(a) Statistical type 6

Select a type of the statistical processing.
Item Description
Average*1 An average value after starting sampling

Maximum*1 The maximum value after starting sampling
Minimum*1 The minimum value after starting sampling
An average of the tag component values that are collected at sampling intervals for the
Moving average*2 *3 number of times specified by [No. of samples]
Since the processing range moves at each sampling, the latest value can be obtained.
The maximum value in the tag component values that are collected at sampling intervals
Moving maximum*2 *3 for the number of times specified by [No. of samples]
The minimum value in the tag component values that are collected at sampling intervals
Moving minimum*2 *3 for the number of times specified by [No. of samples]
*1 If a statistical value of [Average], [Maximum], or [Minimum] is reset, a value obtained after resetting will be stored.
• How to reset a statistical value of [Average], [Maximum], or [Minimum]
Perform substitution of some value for the relevant tag component using [Operation action] of a job.
For operation actions, refer to the following:
➠ 6.8.2 Setting items in Operation action
The statistical processing is reset and a value processed after the substitution is stored.
*2 Statistical values of [Moving average], [Moving maximum], and [Moving minimum] cannot be reset.
*3 When a tag component having [Moving average], [Moving maximum], or [Moving minimum] setting is specified in a job, the job is
not activated until data are collected for the specified number of times after start of sampling.

(b) No. of samples (2 to 20)
Specify the number of samples when [Moving average], [Moving maximum], or [Moving minimum] is selected.
(Moving average when [No. of samples] is 4)

Device value 4) Sampling interval
3)
2) 5)
1) 6) 8) 9)
7) 12)
10) 11)
1st Tag component value

2nd Moving average
3rd
0 Time (seconds)
<Change in tag component values>

1st 2nd 3rd
1)+2)+3)+4) 2)+3)+4)+5) 3)+4)+5)+6)
4 4 4

■6. n (Array No.)
When [Array setting] is set, the device range of array No.n, is displayed in [Device [n]] of [Component List].
To change the [Device [n]] display, use the following methods.

• Enter a value in the box.
• Change the value with the , , , or button.
■7. Array block size

When [block] is selected in [Array setting], [array block size] setting is available.
Usually, the block size need not be changed because the it is automatically adjusted to avoid duplication of
components.
Change [array block size] when:
• Setting a desired number for the start device No. of each block.
• Adding any component in the future.
6
The following example explains the cases where [array block size] is manually set and is not set.
(Example) When [Component D] is to be added in the future
• When 10 is set for [array block size], device numbers are not changed.
• When nothing is set for [array block size], device numbers in and after array No.2 are changed.

[When the size is set]
(Array block size = 10)
n=1 n=2 n=3

Component A GD0 GD10 GD20
Component B GD1 to GD2 GD11 to GD12 GD21 to GD22
Component C GD3 to GD8 GD13 to GD18 GD23 to GD28
Component D GD9 GD19 GD29
Component name Device Data type
Component A GD0 Single word
Component B GD1 Double word
[When the size is not set]
Component C GD3 String (12 characters)
Planned to Component D GD9 Single word n=1 n=2 n=3
be added
GD9 GD18
Component A GD0 GD10 GD20
GD10 to GD11 GD19 to GD20
Component B GD1 to GD2 GD11 to GD12 GD21 to GD22
Component C GD3 to GD8
Component D GD9 GD19 GD29
■8. Precautions on [Component setting]

If a wrong device number is set for a component in [Component setting], an error will occur on another component that
has the same access target CPU setting.
Correct the device number in [Component setting].

6.6 Server Service Settings
Configure the settings for the access to a server computer.
The set server service name is used in [Job setting].
Step 1. Double-clicking [Server Service setting] in the Edit items tree displays relevant items.
POINT
(2) When an item is added or copied, a "NewServer" item is added.
6 - 16 6.6 Server Service Settings

6.6.1 Setting items in Server service settings
Up to 8 items can be set in [Server service settings] within one project.

Item Description
Sever service name Enter a server service name. (Up to 16 characters)
Server type Select the server type of the server computer to be accessed.
IP address Enter a decimal IP address of the server computer where DB Connection Service is installed.
Set a port number of the server computer.

Port No.
(Range: 1024 to 65535, Default: 5112)
Set a user name used to access the server computer.

User name
(Up to 30 characters)
Set a password used to access the server computer.

Password/Confirm password
(Up to 30 characters)
Data source name Set the name of the ODBC data source to be accessed.
Database type Select the type of the database server.
Access error notification setting Set whether to enable or disable notification of the access error status.
In case a connection error occurs on the network between the GOT and the server computer, set a
Connection timeout timeout time during which the GOT will detect the error.
(Range: 1 to 180 seconds, Default: 10 seconds)
6.6 Server Service Settings 6 - 17

■1. Server service name (Up to 16 characters)
Enter a server service name.
The set server service name is used in [Job setting].
For characters that can be used for server service names, refer to the following:
Note that using the name same as the one of the device tags set in [Device tag settings] is not allowed.
■2. Server type

(1) Select the server type of the server computer to be accessed.
Item Description
Database server Used in [Communication action] of [Job setting].
Application server Used in [Program execution] of [Job setting].
(2) When [Database server] is selected, set the following items.

Item Description
Set the name of the ODBC data source to be accessed.

Data source name For characters that can be used for data source names, refer to the following:
➠ 9.1.4 Characters applicable to field names, table names, etc.
Select the type of the database server.

• Oracle 8i
• Oracle 9i
• Oracle 10g/11g/12c*1
Database type
• SQL Server 2000/2005/2008/2008 R2/2012/2014
• MSDE200
• Access2000
• Access2003/2007/2010/2013
■3. IP address
Enter a decimal IP address of the server computer where DB Connection Service is installed.
■4. Port No. (Range: 1024 to 65535, Default: 5112)

Set a port number of the server computer.
Set the same value in [Port No.] as the one set in [Service port] of DB Connection Service.
■5. User name (Up to 30 characters)

Set a user name used to access the server computer.
For characters that can be used for user names, refer to the following:
➠ 9.1.3 Characters applicable to character string constants, etc.
(1) When [Database server] is selected for [Server type]
Set a user name that is required for ODBC access.
(2) When [Application server] is selected for [Server type]
Set the account user name used for the operating system (OS) of the application server computer.
■6. Password/Confirm password (Up to 30 characters)

Set a password used to access the server computer.
For characters that can be used for passwords, refer to the following:
6 - 18 6.6 Server Service Settings

■7. Access error notification setting
(1) [Notify the access error status.]
Set whether to enable or disable notification of the access error status.
If the [Notify the access error status.] box is checked, an error occurred in access to the server computer is reported
to a tag component.
(2) When [Notify the access error status.] is selected, choose a tag component into whose device the access error status
data is stored.
Tags that have a tag component with [Array setting] cannot be selected.
Data are stored as follows depending on the data type.
Data type of tag component Description
OFF: Normal/Not accessed/Network line disconnected

Bit
ON: Access error status
"0": Normal/Not accessed/Network line disconnected

String
"1": Access error status
0: Normal/Not accessed/Network line disconnected

Other than the above
1: Access error status
■8. Connection timeout (Range: 1 to 180 seconds, Default: 10 seconds) 6

In case a connection error occurs on the network between the GOT and the server computer, set a timeout time during
which the GOT will detect the error.
Usually, this setting is not needed.
In any of the following cases, adjust the connection timeout time if necessary.

(1) Reduce the connection timeout time to:
• Make the time elapsed from occurrence of a connection error to the start of DB buffering shorter.
• Make the time elapsed from occurrence of a connection error to notification of an access error and job cancellation
shorter.
(2) Increase the connection timeout time when:
• A connection timeout occurs in spite of normal network condition.
POINT
The relation of the values set for [Connection timeout] and [DB access timeout time] in [DB
Connection Service Setting Tool] must be as follows:
• Connection timeout value DB access timeout value
6.6 Server Service Settings 6 - 19

6.7 Job Settings
Configure the settings for the DB interface function.
For the DB interface function, refer to the following:
➠ 5.1 DB Interface Function
Step 1. Double-clicking [Job settings] in the Edit items tree displays relevant items.
POINT
(2) When an item is added or copied, a "New Job" item is added.
6 - 20 6.7 Job Settings

6.7.1 Setting items in Job settings
Up to 64 items can be set in [Job settings] within one project.
For job operations, refer to the following:
➠ 5.2 Precautions

Item Description
Job name Enter a job name. (Up to 16 characters)
GOT Initializing Set whether to enable the job at startup of the GOT or not.
Trigger buffering Set whether to enable the trigger buffering or not.
Startup logging Set whether to output the startup history of the job to the log or not.
Test mode Set whether to operate the job in test mode or not.
Configure the settings for startup conditions of the job.

Trigger conditions
Configure the action settings.

Action
➠ 6.8 Job Settings - Actions
Configure the settings for the program execution function.

Program execution
➠ 6.7.3 Setting items in Program execution

DB buffering
Set whether to enable or disable notification of errors (job cancellation) that occur during
Notify errors (job cancellation) that occur during job job execution.
execution
No. of fields in project Displays the total number of fields in the project.
Tag component data length in job Displays the total data length of the tag components in the job.
6.7 Job Settings 6 - 21

■1. Job name (Up to 16 characters)
Enter a job name.
For characters that can be used for job names, refer to the following:
■2. GOT Initializing

(1) Set whether to enable the job at startup of the GOT or not.
If the [GOT Initializing] box is not checked, the job is disabled at startup of the GOT. (Even if trigger conditions are
met, the job is not executed.)
(2) When the GOT is ON, the enable/disable setting of the job can be changed in [Change Job Status] on the
[Diagnosis] tab.
➠ 6.10.3 Changing the job status (Change job status)
■3. Trigger buffering

(1) Set whether to enable the trigger buffering function or not.
For the trigger buffering function, refer to the following:
➠ 5.1.5 Trigger buffering function
(2) Precautions for enabling [Trigger buffering]
• [Handshake operation] cannot be selected for the trigger conditions.
• A tag component cannot be selected for the substitution tag in [Operation action].
• Tag component values cannot be set for [DB-tag link setting] in [Select] of [Communication action].
• [Communication action] - [MultiSelect] cannot be selected.
• Up to 4096 words can be used for the total data length of tag components in one job. (The current data length is
displayed on the status bar of [Job setting].)
POINT
The total data length of tag components in one job is the total data length of tag components set
in [Communication action] and [Operation action]. In [Communication action], tag components
are set in [Select/Update conditions] and [DB-tag link setting].
All tags in one job are treated as different tags even if there are the same tags.
■4. Startup logging

(1) Set whether to output the startup history of the job to the log or not.
If this function is enabled, the job startup timing can be checked during system start-up or tune-up.
When the [Startup logging] box is checked, the startup history of the job (date and time, job name, trigger conditions)
is saved on a CF card.
The startup log can be confirmed in [Job Execute Log] on the [Working log] tab.
➠ 6.11.2 Job Execute Log
(2) When the log capacity becomes full (Log capacity: 1MB 2)
The first half of the data are deleted.
The latest log is stored after the remaining data.
(3) When this function is enabled, a processing time is required for saving or deleting the startup history of the job.
It is recommended to disable this function during system operation.
■5. Test mode

(1) Set whether to operate the job in test mode or not.
Up to 4 jobs can be set to [Test mode].
When the [Test mode] box is checked, the test mode is activated, and execution details of the job can be confirmed
before operation.
Job execution can be confirmed in [Job Execute Log] on the [Working log] tab.
(2) When [Test mode] is selected
The following are performed in the test mode.
Operations other than the following are identical to the actual operations.
• Startup data are logged.
• Detailed data are logged.
• Data are not written to GOT devices.
• No data are written to the database.

6.7.2 Setting items in Trigger conditions
Configure the settings for startup conditions of the job.
The job is activated when the trigger condition value is changed from false to true.
At the time of power-up, at restart of the MES interface function, or at the end of one-shot execution, all the conditions are
initialized to false, and the job is started up when the initial condition is true.
Item Description
6
Combination Selects conjunction of Trigger 1 and 2.
Trigger 1 Selects Trigger 1.
Trigger 2 Selects Trigger 2.

■1. Combination
(1) Selects a combination of [Trigger 1] and [Trigger 2].
• OR (When either of them is true, the result is true.)
• AND (When both of them are true, the result is true.)
When the combination result of [Trigger 1] and [Trigger 2] is changed from false to true, the job is activated.
(2) The following shows the timings at which the combination result of [Trigger 1] and [Trigger 2] is changed from false to
true.

(In any other cases, because the combination result is not changed from false to true, the job is not activated.)
Combination Trigger 1 Trigger 2 Combination result
(Changed from false to (Remained

true) false)
True True
False False
(Changed from false to (Changed from false to

true) true)
OR (When either of them is true, the result is true.)
True True
False False
(Remained (Changed from false to

false) true)
True True (Changed from false to

False False true)
(Changed from false to (Remained True

true) true) False
True True
False False
(Changed from false to (Changed from false to

true) true)
AND (When both of them are true, the result is true.)
True True
False False
(Remained (Changed from false to

true) true)
True True
False False

■2. Trigger 1, Trigger 2
Select items for [Trigger 1] and [Trigger 2], referring to this ■3. and subsequent descriptions.
○: Selectable, ×: Not selectable
Item Description Trigger 1 Trigger 2
No trigger conditions
Disable ○ ○
➠ ■3. Disable
When the specified date, time and day of the week match the
actual date, time and day of the week, the condition changes
Time specification startup from false to true, resulting in job startup. ○ ○
➠ ■4. Time specification startup
The condition is alternated between true and false in the

specified cycles (unit: seconds), and when it changes from false
Specified time period startup to true, the job is activated. ○ ○
➠ ■5. Specified time period startup
The actual tag component value is compared with the condition

value (tag component value or constant value) at every sampling
Value monitoring startup times, and the job is activated when the condition changes from ○ ○
false to true.
➠ ■6. Value monitoring startup
6
The job is activated only once when the GOT is started up.
GOT Initializing ○ ○
➠ ■7. GOT Initializing

The job is activated when [Handshake startup] of the GOT turns
ON.
Handshake operation Upon completion of the job execution, [Completion notification] ○ ×
of the GOT turns ON.
➠ ■8. Handshake operation
■3. Disable
(1) When [Disable] is selected for [Trigger 1] or [Trigger 2]
Another trigger is regarded as a trigger condition.
(2) When [Disable] is selected for both [Trigger 1] and [Trigger 2]
The job is not activated by trigger conditions.
The job can be executed only by one-shot execution.
■4. Time specification startup

(1) When the specified date, time and day of the week match the actual date, time and day of the week, the condition
changes from false to true, resulting in job startup.
(2) When [Time specification startup] is selected, the date, time, and day of the week must be set.
(a) Year, Month, Day, Hour, and Minute

Directly enter the date and time.
Matching with the actual date and time is not checked for any field that remains blank.
Item Description
Year (4 digits) 0000 to 9999
Month 1 to 12
Day 1 to 31
Hour 0 to 23
Minute 0 to 59

(b) Day
Specify a day of the week.
Check the checkbox of the day to be specified.
If no box is checked, it means "every day".
(Example) The following shows that the job is to be activated at 17:30 on Monday through Friday.
(Example) The following shows that the job is to be activated at 9:00 on the 1st day of every month.
POINT
If [Startup logging] is selected, each job startup can be confirmed with the time to the second in
the startup log.
The startup log can be checked on the [Working log] tab.
➠ 6.11 Working Log
■5. Specified time period startup

(1) The condition is alternated between true and false in the specified cycles (unit: seconds), and when it changes from
false to true, the job is activated.
(2) When [Specified time period startup] is selected, set the cycle.
(Range: 1 to 32767 seconds)
(Example)
The following shows that the job is activated at 60-second intervals for an hour from 12:00 to 13:00 every day.

■6. Value monitoring startup
(1) The actual tag component value is compared with the condition value (tag component value or constant value) at
every sampling times, and the job is activated when the condition changes from false to true.
Even if the trigger condition becomes true temporarily between samplings, the job is not activated unless it is true at
time of sampling.
Startup point
Startup point
Condition value
Not activated here.
Tag component value
Sampling interval

(2) When [Value monitoring startup] is selected, specify conditions for comparison.
(a) Tag, Component

Select a tag component to be compared with.
(b) Condition
Select a condition for comparison.
Item Description
= The tag component value is equal to the condition value.
The tag component value is not equal to the condition value.
The tag component value is equal to or greater than the condition value.
(Not selectable when [Data type] of the tag component is [bit] or [String])
The tag component value is greater than the condition value.

The tag component value is smaller than the condition value.

The tag component value is equal to or smaller than the condition value.
(c) Tag/Type
Select a tag or constant that is used as a condition for comparison.

(d) Component
Select or enter a component/constant value that is used as a condition for comparison.
(Example)
The following shows that the job is activated when the value of the tag component (Process 1, Temperature)
reaches 45 or higher.
(Example)
To activate the job repeatedly while the condition of [Value monitoring startup] is met,
Make settings as follows:
Item Description
Combination AND (When both of them are true, the result is true.)
Trigger 1, Trigger 2 [Value monitoring startup], [Specified time period startup]
As the condition alternates between true and false as shown below, job startup can be repeated while the [Value
monitoring startup] condition is met.
Tag component value

[Trigger 1] Timing of [Value monitoring startup]
Condition value
True
Sampling interval
False
[Trigger 2] Timing of [Specified time period startup]
True
False
Fixed cycle
Combined by AND
Timing when AND is used

Startup point
True
False
■7. GOT Initializing

The job is activated only once when the GOT is started up.

■8. Handshake operation
(1) The job is activated when [Handshake startup] of the GOT turns ON.
Upon completion of the job execution, [Completion notification] of the GOT turns ON.
[Handshake operation] is a startup method by which completion of job execution can be notified to a GOT.
Sampling interval
GOT
Handshake operation started
ON
[Handshake startup]
OFF
ON
[Completion notification]
OFF
Handshake operation completed
Device data
6
Job operation

Data
Step 1. When [Handshake startup] turns ON in the sequence program, the GOT collects tag component values
used for the job and executes the job.
Step 2. Upon completion of the job execution, [Completion notification] of the GOT is turned ON.*1
Step 3. After confirming that [Completion notification] is ON, turn OFF [Handshake startup] of the GOT.
Step 4. When [Handshake startup] turns OFF, the GOT turns OFF [Completion notification], causing the
handshake operation to be completed.
Step 5. After confirming the completion of the handshake operation, the next job is executed.
*1 If an error occurs during job execution, [Completion notification] does not turn ON.
To detect such an error, enable [Notify errors (job cancellation) that occur during job execution].
(2) [Handshake operation] is selectable only in [Trigger 1].

When [Handshake operation] is selected, selection is not allowed for [Trigger 2].
For selection of [Handshake operation], set the following items.
Item Description
Select a tag component used to request for job startup.

Handshake startup (Selectable only when [Data type] of the tag component is [bit])
Select a tag component that allows notification of execution completion of the job.
Completion notification (Selectable only when [Data type] of the tag component is [bit])
*1 Do not specify the same [Completion notification] to multiple jobs.

6.7.3 Setting items in Program execution
Configure the settings for the program execution function.
For the program execution function, refer to the following:
Step 1. Click the Setting button of [Before actions] or [After actions].

• Before actions:
Set a program to be performed before execution of the first action of the job.
• After actions:
Set a program to be performed after execution of the last action of the job.
Step 2. [Program execution setting (before action)] or [Program execution setting (after action)] is displayed.
After completing the setting, click the OK button.

6
Item Description
Execute program before (after) action Set whether or not to enable program execution before or after execution of actions.
Program execution destination Select an application server to be accessed.

Enter a command line for the program that is executed on the application server computer. (Up to
Command line
127 characters)
Check return value Set whether to check the return value or not.
Set whether or not to wait for execution completion of the program before executing the next
Wait for execution completion
processing.
■1. Execute program before action, or Execute program after action

(1) Set whether or not to enable program execution before or after execution of actions.
(2) When [Execute program before action] or [Execute program after action] is enabled, make the setting described in
this section (2) and subsequent sections.
■2. Program execution destination

Select an application server to be accessed.
■3. Command line (Up to 127 characters)

Enter a command line for the program that is executed on the application server computer.*1*2
For characters that can be used for command lines, refer to the following:
➠ 9.1.1 ASCII code table
*1 Programs that need to be run with administrator privileges (by a user in Administrators group) are not executable.
*2 To execute a program including any displays, place the application server computer into the logon status.

■4. Check return value
(1) Set whether to check the return value or not.
When the [Check return value] box is checked, the return value (End code) of the executed program is checked.
If no return value is returned within the [DB access timeout] time set in DB Connection Service Setting Tool, a timeout
error is detected and the job execution is canceled.
For [DB access timeout], refer to the following:
(2) When [Check return value] is selected, set the following items.
(a) Normal return value (Default: 0)
Set a normal return value.
(b) Write the value into the tag when the value is faulty.
When the [Write the value into the tag when the value is faulty] box is checked, if the return value is not normal,
a value is assigned to the specified tag component.
Set a tag component to which a value is assigned when this is selected.
• Tag, Component
Select a tag component to which a value is assigned.
• Substitute value
Directly enter a substitute value.
(c) Do not execute job when the value is faulty. ([Program execution setting (before action)] only)
When the [Do not execute job when the value is faulty] box is checked, if the return value is faulty, the job
execution is canceled.
■5. Wait for execution completion

If the [Wait for execution completion] box is checked, the next processing is executed after completion of the program
execution.
When [Check return value] is selected, [Wait for execution completion] is always selected.

Set whether to utilize the DB buffering function or not.
For the DB buffering function, refer to the following:
Item Description
Enable DB buffering Set whether to enable the DB buffering or not.
Set whether or not to automatically resend data after recovery.

When the [Automatically resend at time of restoration] box is checked, resend processing is
Automatically resend at time of restoration automatically performed after recovery.
When the [Automatically resend at time of restoration] box is not checked, resend processing is
manually performed after recovery.
POINT
Before resending data, the GOT communicates with the database.
At this time, if an action for communicating with the same database is set for a job, a long time is
required for execution of the job.
In the case of a large buffering size, it is advisable to resend the data manually while any job that
is set to communicate with the database is not in execution, so that no problem will arise even if
the MES interface function processing is affected.

6.7.5 Notify errors (job cancellation) that occur during job execution
Set whether to enable or disable notification of errors (job cancellation) that occur during job execution.
Job execution is canceled when access to the database fails or when type mismatch is found.
➠ 5.2 Precautions
6.11.2 ■3. (2) Operation of numerical values
■1. Notify errors (job cancellation) that occur during job execution
(1) Set whether to enable or disable notification of errors (job cancellation) that occur during job execution.
When [Notify errors (job cancellation) that occur during job execution] box is checked, if job execution is canceled, a
value is assigned to the specified tag component.
(2) When [Notify errors (job cancellation) that occur during job execution] has been selected, set a tag component to
which a value is assigned.
(a) Tag, Component
6
(b) Substitute value

6.7.6 One-shot execution
Execute a job as a one-shot task.
Doing so allows the user to check the execution result of the currently editing [Job setting].
■1. Procedure for one-shot execution
POINT
• In [One-shot execution], settings of [Startup logging] and [DB Buffering] are not executed.
• All of job operations running with the MES interface function are temporarily disabled during
one-shot execution.
Step 1. Click the One-shot execution button with the [Job settings] edit screen displayed.
Step 2. Clicking the One-shot execution button performs one-shot job execution ignoring the trigger conditions.
Step 3. the execution result shown in the [View details] dialog box, which is displayed after the execution.
For the display of the [View details] dialog box, refer to the following:
➠ 6.11.2 ■3. Updating the Job Execute Log
POINT
A dialog box indicating the current processing status is displayed until completion of one-shot
execution.

■2. Precautions for one-shot execution
(1) Precautions before one-shot execution
One-shot execution can be performed only when the MES interface function is active.
When the MES interface function is not active, check the status and restart the operation before starting one-shot
execution.
For restart of the MES interface function, refer to the following:
(2) Precautions during one-shot execution
Do not perform the following during one-shot execution.
• Do not disconnect the cable that is connected to the GOT during one-shot execution.
Doing so will cause the MES interface function to be inoperative.
• Do not remove the CF card from the GOT during one-shot execution.
Doing so will cause the MES interface function to be inoperative.
If the MES interface function becomes inoperative, check the status and restart the operation on the Diagnosis tab.
For restart of the MES interface function, refer to the following:
(3) Precautions after one-shot execution
One-shot execution results are not reflected in [Connection result of previous job execution].

6.8 Job Settings - Actions
The following shows types of actions.
Up to 10 actions can be set for one job.
• [Communication action]
For communicating the GOT with a database
• [Operation action]
For operating tag component values
• [Transmit resource action]
For sending the resource data to the database
(Adding an action)
• Select [Communication action], [Operation action], or [Transmit resource action] from the list box next to the Add button,
and click the Add button.
• The Communication action dialog box, the Operation action dialog box, or the Transmit resource action dialog box is
displayed.
6.8.2 Setting items in Operation action
6.8.3 Setting items in Transmit resource action 6
(Modifying an action)
• Select an action to be modified in [Action list], and click the Edit button.

• The Communication action dialog box, the Operation action dialog box, or the Transmit resource action dialog box is
displayed.
6.8.3 Setting items in Transmit resource action
(Deleting an action)
• Select an action to be deleted in [Action list], and click the Delete button.
(Copying an action)
• Select an action to be copied in [Action list], choose [Replicate the selected action] from the list box next to the Add
button, and click the Add button.
6.8 Job Settings - Actions 6 - 35

(Copying an action of another job within the project)
Step 1. Select [Replicate actions of other jobs] in the list box next to the Add button, and click the Add button.
Step 2. The [Replicate actions] dialog box is displayed.
Step 3. By repeating the following steps 4 to 6 , set copy targets in [Selected Actions to replicate].
Step 4. From [Source Jobs], select a job that includes a desired action.
Step 5. Actions of the job selected in 4 are listed in [Source Actions]. Select an action to be copied. (Multiple
selection is available.)
Step 6. Clicking the > button displays the action(s) selected in 5 in [Selected Actions to replicate].
Item Description
> button Puts the action(s) selected in [Source Actions] into [Selected Actions to replicate].
>> button Puts all of the actions in [Source Actions] into [Selected Actions to replicate].
< button Deletes the action(s) selected in [Selected Actions to replicate] from the box.
<< button Deletes all of the actions in [Selected Actions to replicate] from the box.
6 - 36 6.8 Job Settings - Actions

Step 7. Clicking the Run button executes copying.
Copied actions are located after existing actions.
Item Description
Type The types of the existing actions are displayed.
Summary Details of the existing actions are displayed.
button
Selecting an action in [Action list] and clicking the
the selected one and the one immediately above it.
button reverses the order between
6
The button cannot be clicked on the first action.
Selecting an action in [Action list] and clicking the button reverses the order between

button the selected one and the one immediately below it.
The button cannot be clicked on the last action.
POINT
When more than one action are set, they are executed in order, starting from the top.
■1. Type
The types of the existing actions are displayed.
Item Description
Select [Select] of [Communication action]
Update [Update] of [Communication action]
Insert [Insert] of [Communication action]
MultiSelect [MultiSelect] of [Communication action]
Operation [Operation action]
Resource [Transmit resource action]
■2. Summary
(1) Details of the existing actions are displayed.
(a) In the case of [Communication action]
Item Description
[Database: Table name]{DB-tag link setting No.1}...{DB-tag link setting No.n}

*1
Display format
Select: {DB-tag link setting} = {Field name -> Tag component/Constant value}
Update/Insert: {DB-tag link setting} = {Field name <- Tag component/Constant value}

(b) In the case of [Operation action]
Item Description
{Operation action No.1}...{Operation action No.n}
With substitution setting:

{Operation action} =
Display format*1 *2 {Substitution tag component/Constant value <- Operation tag component/Constant value
Operator Operation tag component/Constant value}
Without substitution setting:
{Operation action} =
{Substitution tag component/Constant value <- Operation tag component/Constant value}
(c) In the case of [Transmit resource action]

Item Description
[Database: Table name]{Comment storing field name, Time storing field name, Field name No.1,
Display format
..., Field name No.n}
*1 Display format of the tag component/constant value
Item Description
Tag component Device tag name, component name
Numerical value Numerical value
String "Character string"
GOT time: Date [GOT time]

Date
Server time: Date [Server time]
Date String "Date [Date String]"
Variable (Variable name)
*2 Display format of the operator
Item Description
+ (Addition) +
- (Subtraction) -
(Multiplication)
(Division)
% (Remainder) %

6.8.1 Setting items in Communication action
Configure the settings for communications with a database.
Step 1. Performing the operation for adding or modifying an action displays the [Communication action] dialog box.
Step 2. Make the setting referring to the following descriptions.
Step 3. Clicking the OK button after setting adds or modifies the action.
Step 4. For the operation for adding or modifying an action, refer to the following:

Item Description
Action type Select an action type.
Database Set a table name of the database to be accessed.
Table name Set a table name of the database to be accessed.
DB-tag link settings*1 Set assignments between field values and tag component values (or constant values)
When [Select], [Update] or [MultiSelect] is selected for [Action type], set conditions for the
Select/Update conditions*1
records to be selected or updated.
When [Select] or [MultiSelect] is selected for [Action type], set a condition for sorting
Select sort settings*1
selected records.
Set the processing to be performed in the following cases:

• No corresponding record exists when [Select], [Update], or [MultiSelect] is selected for
[Action type].
Exception process setting button • Multiple corresponding records exist when [Select] or [Update] is selected for [Action
type].
• The number of records to be multi-selected is greater than the number of arrays set in
[Array setting] of the tag when [MultiSelect] is selected for [Action type].
Multi select setting button When [MultiSelect] is selected, detailed settings can be configured by clicking this.
Generated SQL text Displays SQL text that is generated in the currently editing [Communication action].
No. of fields in project Displays the total number of fields in the project.
Selecting a row and clicking the button reverses the order between the selected row
button and the one immediately above it.
The button cannot be clicked on the first row.
Selecting a row and clicking the

button button reverses the order between the selected row and the one immediately below it.
The button cannot be clicked on the last row.

Item Description
Delete row button Selecting a row and clicking the Delete row button deletes the row.
• All of the tags set in [Device tag settings] are inserted into [Tag] and [Component].
• Select a row into which data are inserted and choose a tag in a list box next to the
Insert a whole tag button Insert a whole tag button. Clicking the Insert a whole tag button inserts
all of the tag components into contiguous rows starting from the selected one.
• The existing data set in the rows starting from the selected one are moved down.
*1 Up to 8192 fields can be set in [DB-tag link settings], [Select/Update conditions] and [Select sort settings] for each project.
(Check [No. of fields in project] in the lower left of the Communication action dialog box.)
POINT
(1) Entry of [Component]
When data are entered in [Component] by [Insert a whole tag] or with the [Field name] space
blank, the data are copied to the [Field name] space.
(Characters not allowed for [Field name] are not entered.)
Because of this, setting the same name to each of the field name and tag component name
is useful.
■1. Action type

Select an action type.
Item Description
[Select] substitutes a field value of the record, whose conditions are met, for a substitute value (tag
Select
component value/variable).
[Update] substitutes a substitute value (tag component value/variable) for a field value of the record
Update *1
whose conditions are met.
Generates a new value, and inserts an insert value (tag component value/constant value/variable) into a
Insert
field of the generated record.
Substitutes field values of the records, whose conditions are met, for substitute values (tag component
MultiSelect
values).
*1 With Microsoft Access 2000/2003/2007/2010/2013, the following restrictions exist.

• Up to 127 fields can be updated for a communication action.
• Do not access the same file with multiple GOTs and MES interface modules simultaneously.
■2. Database
Select a database to be accessed.
■3. Table name (1 to 32 characters)

Set a table name of the database to be accessed.
For characters that can be used for table names, refer to the following:

■4. DB-tag link settings
Set assignments between field values and tag component values (or constant values).
Up to 256 rows can be set in [DB-tag link settings] for each communication action.
(1) When [Select] is selected for [Action type]
[Select] substitutes a field value of the record, whose conditions are met, for a substitute value (tag component value/
variable).
Set conditions of the record to be selected in [Select/Update conditions].
➠ 6.8.1 ■5. Select/Update conditions
Conditions for sorting the selected records are set in [Select sort settings].
➠ 6.8.1 ■6. Select sort settings
(a) Field name (1 to 32 characters)
Set a field name for the field value to be selected.
For characters that can be used for field names, refer to the following:
(b) Tag
Select a tag or variable for which a value is substituted.
(c) Component
6
Select or directly enter a component value or a variable of the substitution target.

Database: DB1, Table name: RecipeData
Work_No RECIPE1 RECIPE2 RECIPE3
536 5 32 1
Matched Selected Selected Selected
Tag component
Process1.Work_No Process1.RECIPE1 Process1.RECIPE2 Process1.RECIPE3
536 5 32 1

(2) When [Update] is selected for [Action type]
[Update] substitutes a substitute value (tag component value/variable) for a field value of the record whose
conditions are met.
Set conditions of the record to be updated in [Select/Update conditions].
Set a field name for the field value to be updated.
(b) Tag
Select a tag, constant, or variable which is substituted.
(c) Component
Select or directly enter a Component value or a variable that is to be substituted.
Database: DB1, Table name: CompletionReport

Work_No Completed Rejected Date
: : : :
536 496 32 2005.07.01 15:12:00
Matched Updated Updated Updated
Tag component
Process1.Work_No Process1.Complete Process1.Rejected Constant: Server time
536 496 32 2005.07.01 15:12:00

(3) When [Insert] is selected for [Action type]
[Insert] generates a new record, and inserts an insert value (tag component value/constant value/variable) into a field
of the generated record.
Set a field name for the field value to be inserted.
(b) Tag
Select a tag, constant, or variable which is substituted.
(c) Component
Select or directly enter a Component value or a variable that is to be substituted.

Database: DB1, Table name: ERRORLOG
Date Process No Work_No Parameter
2005.07.01 15:12:00 1 536 8
Inserted Inserted Inserted Inserted
Tag component
Constant: GOT time Constant: 1 Process1.Work_No. Process1.Parameter
2005.07.01 15:12:00 1 536 8

(4) When [MultiSelect] is selected for [Action type]
[MultiSelect] substitutes field values of the records, whose conditions are met, for substitute values (tag component
values).
Conditions for the redords to be selected are set in [Select/Update conditions].
Conditions for sorting the selected records are set in [Select sort settings].
➠ 6.8.1 ■6. Select sort settings
(a) Field name (Up to 32 characters)
Set a field name for the field values to be multi-selected.
For characters that can be used for field names, refer to the following.
(b) Tag
Only the tags with [Array setting] can be selected.
(c) Component
Select a target component.

POINT
(1) When [MultiSelect] is used in a job, the total of [Tag component data length in job] must be
45000 words or less.
[Tag component data length in job] represents a total length of the tag component data set for
the following:
• [DB-tag link settings] in [Communication action]
• [Select/Update conditions] in [Communication action]
• [Operation action]
Even if the same tag component is set more than once in the same job, each setting is
handled separately.
(The number of settings can be confirmed on the status bar of [Job setting], or in the
[Communication action] or [Operation action] dialog box.)

Database: DB1, Table name: RECIPEDATA
Work_No RECIPE_A RECIPE_B RECIPE_C
: : : :
536 5 32 1
537 6 33 0
538 7 34 1
539 8 35 0
540 9 36 1
Select-sorted Matched
Selected Selected
(Ascending) (RECIPE_C=1)
Tag component
Process1.Work_No[1] Process1.RECIPE_A[1] Process1.RECIPE_B[1] Process1.RECIPE_C[1]
536 5 32 1
538 7 34 1
540 9 36 1

(5) About tag components
Tag component values can be used as substitute/insert values for [Select], [Update], [Insert] or [MultiSelect], or as
condition values of [Select/Update conditions].
The following table lists data types of tag components and those of assignable fields.
If the data type of a tag component does not match the one of its substitution target field, an error occurs, resulting in
cancellation of job execution.
POINT
The data type of a tag component will change through operation processing of a job.
➠ 6.11.2 ■3. (2) Operation of numerical values
Data type of assignable field
SQL Server 2014

SQL Server 2012 Access 2013
Data type of tag Oracle 11g
SQL Server2008 R2 Access 2010
component Oracle 10g
Oracle 9i
SQL Server 2005 Access 2003
Oracle 8i
MSDE 2000
Bit type Yes/No type

bit
Byte type
int
Integer type
smallint
Long integer type
NUMBER tinyint
Single type
(Numeric type: Integer) CHAR float
Double type
Single-precision type VARCHAR real
AutoNumber type
Double-precision type char
Currency type
varchar
Text type*1 *2
text*1
Memo type*1 *2
float
Single type
(Numeric type: Floating NUMBER real
Double type
point) CHAR char
Text type*1 *2
Floating-point type *3 VARCHAR varchar
Memo type*1 *2
text*1
char
CHAR Text type *2
Character string varchar
VARCHAR Memo type *2
text*1
*1 Not available for [Select/Update conditions]

*2 Memo-type fields in Rich Text Format cannot be used with Microsoft Access 2013/2010/2007.
*3 Values are assigned with precision of six decimal digits.

(6) About constants
Constants can be used as substitute/insert values for [Update] or [Insert], or as condition values of [Select/Update
conditions].
The following table lists constant types and the data types of assignable fields.
If the type of a constant does not match the data type of its substitution target field, an error occurs, resulting in
SQL Server 2014

Oracle 12c SQL Server 2012 Access 2013
Constant type Values that can be entered in [Component] Oracle 11g SQL Server2008 R2 Access 2010
Oracle 10g SQL Server2008 Access 2007
Oracle 9i SQL Server2005 Access 2003
Oracle 8i SQL Server 2000 Access 2000
MSDE 2000
Yes/No type
bit *1 Byte type
Up to 16 characters
int *1 Integer type
• Signed decimal notation
smallint *1 Long integer type
[Number] (Example: -521.98) NUMBER
Single type
• Signed exponential notation tinyint *1
(Example: -5.2198E03) float
Double type
AutoNumber type
6
real
Currency type
Up to 32 characters
For characters that can be used for character char
CHAR Text type *4

[String] strings, refer to the following: varchar
VARCHAR Memo type *4
➠ 9.1.3 Characters applicable to character text *3
string constants, etc.
When using the date and time of the database

server:
datetime
[Date] *2 Select [Server time]. DATE Date/Time type
smalldatetime
When using the date and time of the GOT:
Select [GOT time].
Up to 32 characters
For characters that can be used for character
strings, refer to the following:
➠ 9.1.3 Characters applicable to character
string constants, etc.
Specify the date and time of the GOT in the
following format.
char
Year (4 digits): YYYY CHAR Text type *4
[Date String] varchar
Year (2 digits): YY VARCHAR Memo type *4
Month (2 digits): MM text*3
Day (2 digits): DD
Hour (2 digits): hh
Minute (2 digits): mm
Second (2 digits): ss
Example: "YYYY-MM-DD hh:mm:ss"
"2005-07-01 15:12:00"
*1 Signed integer notation only

*2 Clock precision:
When [GOT time] is selected: In units of seconds
When [Server time] is selected: Depends on the database server.

(7) About variables
Variables can be used as substitute/insert values for [Select], [Update] or [Insert], or as condition values of [Select/
Update conditions].
The following table lists data types of variables and those of assignable fields.
If the type of a variable does not match the data type of its substitution target field, an error occurs, resulting in
Up to 64 variables can be set for one job.
POINT
(1) A variable is valid only in a single job execution and is not held.
(2) The initial variable value before substitution processing is the numerical value of zero.
(3) The data type of a variable will change through operation processing of a job
➠ 6.12 (2) Operation of numerical values
SQL Server2014
Oracle 12c SQL Server2012 Access 2013
Data type of Values (variable names) that can be entered in Oracle 11g SQL Server2008 R2 Access 2010
variable [Component] Oracle 10g Access 2007
SQL Server2008
Oracle 9i SQL Server 2005 Access 2003
Oracle 8i Access 2000
SQL Server2000
MSDE 2000
Bit type Yes/No type

bit
Byte type
int
Integer type
(Numeric type: smallint
Long integer type
Integer) NUMBER tinyint
Single type
Single- CHAR float
Double type
precision type VARCHAR real
AutoNumber type
Double- char
Up to 16 characters. Currency type
precision type vachar
For characters that can be used for variables, Text type *1*2
text *1
refer to the following: Memo type *1*2
➠ 9.1.2 Characters applicable to item names, float
(Numeric type: component names, variable names, etc. Single type
NUMBER real
Floating point) Double type
CHAR char
Floating-point Text type *1*2
VARCHAR vachar
type *3 Memo type *1*2
text *1
char
Character CHAR Text type*2
vachar
string VARCHAR Memo type*2
text *1

*3 Values are assigned with precision of six decimal digits.

■5. Select/Update conditions
When [Select], [Update] or [MultiSelect] is selected for [Action type], set conditions for the records to be selected,
updated or multi-selected.
When a field value of a record matches a condition value, the record is selected or updated.
Up to 8 rows can be set for one communication action in [Select/Update conditions].
POINT
Exception processing is executed when records that meet [Select/Update conditions] are in the
following cases.
6
• Records to be selected/updated/multi-selected do not exist.
• Multiple records exist for select/update.
• The number of records to be multi-selected is greater than the number of arrays set in [Array

setting] of the tag.
For details of the exception processing, refer to the following.
➠ 6.8.1 ■7. Exception processing setting
(1) Combine
Select a method by which conditions set in respective lines are combined.
Select "AND" or "OR".
If "AND" and "OR" are combined, the database will process "AND" first and then "OR".
Item Description
AND The condition of the line just above the corresponding line and the condition of the corresponding line
OR The condition of the line just above the corresponding line or the condition of the corresponding line
(2) Field name (1 to 32 characters)

Set a field name that is used for comparison.
For characters that can be used for field and table names, refer to the following:
(3) Condition
Select a condition for comparison.
Item Description
The field value is equal to the condition value.
The field value is not equal to the condition value.
The field value is equal to or greater than the condition value.
The field value is greater than the condition value.
The field value is smaller than the condition value.
The field value is equal to or smaller than the condition value.
(4) Tag
Select a tag or constant that is used as a condition for comparison.
(5) Component
Select or directly enter a component/constant value that is used as a condition for comparison.
If [Variable] is selected for [Tag], select or directly enter a variable.
POINT

For tag components, constants or variables, refer to the following:
➠ 6.8.1 ■4. (5) About tag components
6.8.1 ■4. (6) About constants
6.8.1 ■4. (7) About variables

■6. Select sort settings
When [Select] or [MultiSelect] is selected in [Action type], set conditions for sorting the records to be selected/multi-
selected.
If multiple sort conditions are set, the database will process the conditions in order, starting from the top.
In [Select sort settings], settings of up to eight lines are allowed for each communication action.
(1) Field name (Up to 32 characters)

Set a field name for records to be selected.
For characters that can be used for field names and table names, refer to the following.
6

(2) Order
Set the order of sorting the selected records.
Item Description
Ascending order Sorts the records so that the specified fields are arranged in ascending order.
Descending order Sorts the records so that the specified fields are arranged in descending order.
Database (before sorting)

ORDER_NO PRODUCT_CODE DELIVERY_DATE
200 707 2007-01-31
201 662 2007-01-10
202 666 2007-01-29
203 662 2007-01-31
204 707 2007-01-10
205 666 2007-01-29
206 707 2007-01-10
207 662 2007-01-29
208 662 2007-01-31
Sorting conditions in [Select sort settings]
1)
2)
Selected records [sorting results]

ORDER_NO PRODUCT_CODE DELIVERY_DATE
206 707 2007-01-10
2) 204 707 2007-01-10

201 662 2007-01-10
207 662 2007-01-29
2) 205 666 2007-01-29

202 666 2007-01-29
208 662 1) 2007-01-31
2) 203 662 2007-01-31

200 707 2007-01-31
1) First, selected records are sorted in ascending order of DELIVERY_DATE.

2) Then, records of the same DELIVERY_DATE are sorted in descending order of ORDER_NO.

■7. Exception processing setting
A click on the Exception process setting button displays the [Exception process setting] dialog box.
(Example) When [Select] is selected for [Action type]
(1) Exception processing: No applicable record 6

When [Select], [Update] or [MultiSelect] is selected for [Action type], set processing for the case where there is no
record to be selected, updated or multi-selected.

(a) Send notification of this exception
When the [Send notification of this exception] box is checked, if there is no record to be selected, updated or
multi-selected, assign a value to the specified tag component.
When [Send notification of this exception] is selected, set a tag component to which the value is assigned.
• Tag, Component
(b) Continue this job
After execution of exception processing described in the above 1), the system continues executions of other
actions.
(c) Finish this job (Default: Finish this job)
After execution of exception processing described in the above 1), the job is forcibly terminated without
executing remaining actions.
At this time, substitute/insert values before exception processing execution are committed, and they are written
to relevant tag components.
POINT
(1) When a job is forcibly terminated, an error occurred during job execution (job cancellation) is
not notified.
(2) If [Enable DB buffering] is selected for a job, its exception processing setting is disabled.

(2) Exception processing: Multiple applicable records
When [Select] or [Update] is selected for [Action type], set processing for the case where there are multiple records
to be selected or updated.
(a) Select firster find records (Default: Checked)

When [Select] is selected for [Action type], checking the [Select firster find records] box allows extraction of the
head record from multiple applicable records.
When this checkbox is not checked, the select/update processing is not performed.
POINT
When [Update] is selected for [Action type], if multiple records to be updated exist, all of them are
updated.
(b) Send notification of this exception
When the [Send notification of this exception] box is checked, if multiple records to be selected or updated exist,
assign a value to the specified tag component.
When [Send notification of this exception] is selected, set a tag component to which the value is assigned.
• Tag, Componen
(c) Continue this job
After executions of exception processing described in the above 1) and 2), the system continues executions of
other actions.
(d) Finish this job (Default: Finish this job)
After execution of exception processing described in 1) and 2), the job is forcibly terminated without executing
remaining actions.
At this time, substitute/insert values before exception processing execution are committed, and they are written
to relevant tag components.
POINT
not notified.

(3) Exception processing: Applicable records overflow
When [MultiSelect] is selected for [Action type], set processing for the case where the number of records to be
selected is greater than the number of arrays set in [Array setting].
(a) Select firster find records (Default: Checked)

When the [Select firster find records] checkbox is checked, if the number of records selected by [Select/Update
conditions] is greater than the number of arrays set in [Array setting], records equivalent to the number of arrays
are actually selected.
When this checkbox is not checked, the select processing is not performed.
POINT
If the [Select firster find records] checkbox is not checked, the following is performed.
• When [Notify the number of acquired records] is set in [Multi select setting], 0 is notified.
• When [Clear the unused tag components by zero] is set in [Multi select setting], 0 is assigned.
6
➠ 6.8.1 ■8. Multi select setting
(b) Send notification of this exception
If the [Send notification of this exception] checkbox is checked, a value is assigned to the specified tag
component when the number of records selected by [Select/Update conditions] is greater than the number of

arrays set in [Array setting].
[Array setting] is less than the number of records selected by [Select/Update conditions].
When selecting this, set a tag component to which a value is assigned.
• Tag, Component
(c) Continue this job
After executions of exception processing described in the above 1) and 2), the system continues executions of
other actions.
(d) Finish this job (Default: Finish this job)
After executions of exception processing described in the above 1) and 2), the system forcibly terminates the job
without executing other actions.
At this time, substitute/insert values before execution of the exception processing are committed to the
database, and data written to tag component are updated.
POINT
not notified.

■8. Multi select setting
A click on the Multi select setting button displays the [Multi select setting] dialog box.
Complete the setting, referring to the following explanation.
(1) Specify the maximum number of acquiring records

If the [Specify the maximum number of acquiring records] checkbox is checked, records of up to the specified
number are acquired.
The GOT acquires the records in the order that the records are extracted from the database.
When selecting this, set a tag for which a value is specified.
(a) Tab/Type
Select a tag for which a value is specified.
(b) Component
Select or directly enter a component or a constant value to be specified.
Item Values available for Component
[Number] Within the range of 1 to 40000
Device tag Single- or double-precision type tag component
POINT
(1) When the select sort settings are set, the GOT acquires the records in the set sorting orders.
(2) An error occurs if the specified tag component value is 0 or less.
➠ 5.1.10 ■2. When an error occurs in job execution
(2) Send notificcation of selected record number
When the [Notify the number of acquired records] checkbox is checked, the number of actually acquired records is
notified to the specified tag component.
When selecting this, set a tag component to which a value is notified.
• Tag
Select a tag component to which a value is notified.
(3) Clear the unused tag components by zero
When the [Clear the unused tag components by zero] checkbox is checked, if the specified number of arrays of the
tag component is less than the number of actually acquired records, zeros are assigned to other array areas.
(Example) When the specified number of arrays of the tag component is "6" and the number of actually acquired
records is "4":
ent name Device Data type n=1 n=2 n=3 n=4 n=5
ent A GB0 Bit Component A GB0 9 GB1 4 GB2 7 GB3 1 GB4 0 GB
ent B GD10 Double word Component B GD10 482 GD12 623 GD14 769 GD16 154 GD18 0 GD
ent C GD100 String (10 characters) Component C GD100 Table GD105 Data1 GD110 Data2 GD115 Data3 GD120 "" GD
Acquired records "0" is assigned

unassigned tag
components. ("
the character st
type)

■9. Generated SQL text
The SQL text generated by the currently editing [Communication action] is displayed.
It indicates the display format of the tag component/constant value.
Note that data of Tag component, Date, Date String, and Variable are generated at job execution, and displayed in the
format shown below. (It is different from the actual SQL text.)
Actions of [Select] and [MultiSelect] generate SQL texts with SELECT. With the SQL text, the user cannot identify
which action is executed.
Item Description
Tag component '(Device tag name, component name)'
Numerical value 'Number'
String 'String'
GOT time:
?TO_DATE('( Date and time [YYYYMMDDhhmmss])',
Oracle 8i
?'YYYYMMDDHH24MISS')
Server time: sysdate
Oracle 12c GOT time:

Oracle 11g ?TO_DATE('( Date and time [YYYYMMDDhhmmss])',
Oracle 10g
Oracle 9i
?'YYYYMMDDHH24MISS')
Server time: CURRENT_TIMESTAMP 6
SQL Server 2014
Date SQL Server 2012
SQL Server 2008 R2
GOT time: '( Date and time [YYYY-MM-DD hh:mm:ss])'
SQL Server 2008

Server time: CURRENT_TIMESTAMP
SQL Server 2005
SQL Server 2000
MSDE2000
Access 2013
Access 2010
GOT time: '( Date and time [YYYY-MM-DD hh:mm:ss])'
Access 2007
Server time: NOW()
Access 2003
Access 2000
Date String '(Date[String])'
Variable '(Variable name)'

Configure the settings for operation of tag component values.
Up to 20 dyadic operations can be set for one operation action.
Step 1. Performing the operation for adding or modifying an action displays the [Operation action] dialog box.
Clicking the OK button after setting adds or modifies the action.
For the operation for adding or modifying an action, refer to the following:
Item Description
Select a tag or variable to which a value is assigned.

Substitution tag
Component Select or directly enter a component value or a variable of the substitution target.
Select a tag, constant, or variable which is computed.

Operation tag
Component Select or directly enter a component/constant value or a variable that is to be computed.
Select an operator.
Operator [ ] (None), [+] (Addition), [-] (Subtraction), [ ] (Multiplication), [ ] (Division), [%]
(Remainder)
button and the one immediately above it.
The button cannot be clicked on the first row.
button and the one immediately below it.
The button cannot be clicked on the last row.
Delete row button Selecting a row and clicking the Delete row button deletes the row.
POINT
Operation actions are executed in order, from the top to the bottom.

■1. About constants
Constants can be used for [Operation tag] - [Component] and not for [Operator].
The following shows the constant types and values that can be entered in the [Component] column.
Constant type Values that can be entered in [Component]
Up to 16 characters
[Number] • Signed decimal notation (Example: -521.98)
• Signed exponential notation (Example: -5.2198E03)
Up to 32 characters
[String] For characters that can be used for character strings, refer to the following:
Up to 32 characters
For characters that can be used for character strings, refer to the following:
Specify the date and time of the GOT in the following format.
Year (4 digits): YYYY
Year (2 digits): YY
[Date String]
Month (2 digits): MM
Day (2 digits): DD
Hour (2 digits): hh
Minute (2 digits): mm
6
Second (2 digits): ss
Example: "YYYY-MM-DD hh:mm:ss" "2005-07-01 15:12:00"
■2. About variables

Variables can be used for [Component] of [Substitution tag] or [Component] of [Operation tag].
By using a variable, a value computed in [Operation action] can be assigned to a database, or to a tag component (In
the latter case, operation is performed based on a value extracted from the database).
The following table shows the variable types and values that can be entered in the [Component] column.
Up to 64 variables can be set for one job.
POINT
(1) A variable is valid only in a single job execution and is not held.
(2) The initial variable value before substitution processing is the numerical value of zero.
(3) The data type of a variable will change through operation processing of a job.
➠ 6.11.2 ■3. (2) Operation of numerical values
Variable type Values (variable names) that can be entered in [Component]
Up to 16 characters
[Variable] For characters that can be used for variables, refer to the following:

■3. Setting example of [Operation action]
The following is a case in which correction power is calculated using a correction voltage and it is assigned to a tag
component (Process 1.Correction power).
The tag component value (Process 1.Correction power) obtained from the following [Operation action] is:
(Process 1.Voltage 100 + 50) Currrent

6.8.3 Setting items in Transmit resource action
Configure the settings for sending the resource data collected in a GOT to a database.
POINT
Before setting [Transmit resource action], configure the settings to collect the resource data (the
logging setting, the advanced user alarm observation, the advanced system alarm observation,
and the operation log setting).
For details, refer to the following manual.
The settings for collecting the resource data must be matched to the settings for the resource
data send action. When the settings are not matched, an error may occur at the job execution.

Item Description
Action type Select an action type.
Database Select a database to be accessed.
Table name Select a table name of the database to be accessed.
Resource type Select a resource data type.
Field name setting*1 Set the assignments between the resource data to be sent and the field value for the database.
Clicking this button checks that the settings for collecting the resource data are matched to the
settings for the resource data send action.
Confirm setting button An error message is displayed when the settings are not matched.
For the displayed error message, refer to the following.
Set the logging ID for the logging setting or the alarm ID that is set on the advanced alarm
Logging ID/Alarm ID
observation.
Clicking the Set operation log file name button displays the stored location for the operation log data
Operation log file
to be sent.
Range of data Specify the number of resource data to be sent for each action.
Generated SQL text Displays the SQL text that is generated during editing the data for [Transmit resource action].
*1 Up to 8192 fields can be set in [Field name setting] for each project.
(Check [No. of fields in project] in the lower left of the Transmit resource action dialog box.)

■1. Action type
Select an action type.
The selectable action type is the insert only.
Item Description
Insert Generates a new record, and assigns a value (resource data) into a field.
■2. Database
Select a database to be accessed.
■3. Table name (1 to 32 characters)

Set a table name of the database to be accessed.
For characters that can be used for table names, refer to the following:
■4. Resource type

(Default: Logging)
Select a resource data type.
Item Description
Logging Device values of a controller that are collected at any timing or in specified intervals.
Advanced user alarm Alarm data that are collected in specified intervals for the advanced user alarm observation setting
Alarm data for controllers and a network that are collected by the advanced system alarm observation
Advanced system alarm
setting
Operation log GOT operation history data collected by the operation log function

■5. Field name setting
Set the assignments between the resource data to be sent and the field values for the database.
The resource data types vary according to [Resource type].
(Example) Screen for settings of sending logging data
1)
4)
2) 5)
3) 6)
Item Description
*1
1) First row (comment)
?A field name for sending a comment to the database can be set.
2) Second row (time)*1
Field name*3*5
A field name that specifies a date and time for a resource data send action can be set.
(0 to 32 characters)
3) Third row or later (resource data)
?A field name for sending the resource data to the database can be set.
?Input the field name for [Insert data] to be sent.
6
4) First row (0 to 32 characters, Default: Comment)*1*4
?The comment to be inserted into the database can be set.
5) Second row (Default: GOT time)

?The date and time for inserting the data to the database can be selected from [GOT time] or [Server
time].
6) Third row or later (resource data)
Insert data*2
?The list of resource data to be inserted to the database is displayed.
➠ (1) When selecting [Logging] for [Resource type]
(2) When selecting [Advanced user alarm] for [Resource type]
(3) When selecting [Advanced system alarm] for [Resource type]
(4) When selecting [Operation Log] for [Resource type]
*1 When setting [Field name], fields for the stroring comment and the time data are created in the database. (The setting for the field
name is not necessarily required.)
*2 When [Field name] is not inputted, no resource data is sent.
*3 For the types of data to be sent in the fields, refer to the following.
➠ 6.8.1 ■4. (5) About tag components

*4 For characters that can be used for character strings, refer to the following:

*5 For characters that can be used for field and table names, refer to the following:

The following shows the resource data to be sent and the types of the data.
(1) When selecting [Logging] for [Resource type]
Insert data Data type
Logging time Date
*1 Numeric type (Integer, floating point)

LoggingDevice (1 to 250)
*1 The numbers of 1 to 250 correspond to the rows set for the number of the block number in the logging setting.
(2) When selecting [Advanced user alarm] for [Resource type]
Alarm time Date
Alarm status Character string
General comment*1 Character string
Middle comment*1 Character string
*1 Character string
Higher comment
Detail comment*1 Character string
*1 The first column data of the column number set in the comment group is sent.
POINT
Up to 512 of one-byte and two-byte characters can be set in a comment for the advanced user
alarm.
Set the length of character string on the database more than that for the comment.

(3) When selecting [Advanced system alarm] for [Resource type]
6
Alarm time Date
Alarm status Character string
Comment Character string

POINT
Up to 512 of one-byte and two-byte characters can be set in a comment for the advanced system
alarm.
Set the length of character string on the database more than that for the comment.
(4) When selecting [Operation Log] for [Resource type]
Insert data*1 Data type
Logging time(DATE) Date
Log No.(NO) Numeric type (Integer)
Screen No.(SCRN_NO) Character string
Action type(ACT_ABBR) Character string
Action type(ACTION) Character string
Object name(OPNAME) Character string
Operation level(OPERATOR) Character string
Operation level(OPE_ID) Numeric type (Integer)
User ID(USER_ID) Numeric type (Integer)
Action No.(ACT_NO) Numeric type (Integer)
Data type(DATA_TYPE) Character string
Device name(DEV_NAME) Character string

Insert data*1 Data type
Change value(CHG_VALUE) Character string
Previous value(PREV_VALUE) Character string
*1 The data to be sent vary according to the operation log target.

For details of the collected data in the operation log, refer to the following manual.
(5) Data types

The following table shows the data types of resource data and the data types of data to be sent in the field.
When the data type of the resource data does not match that of data to be sent in the field, an error occurs, resulting
in the cancellation of the job execution.
Data type of data to be sent in field
SQL Server2014
Oracle 12c SQL Server2012 Access 2013
Data type of resource data Oracle 11g SQL Server2008 R2 Access 2010
Oracle 10g SQL Server2008 Access 2007
SQL Server2005
SQL Server 2000
MSDE 2000
datetime
Date DATE Date/Time type
smalldatetime
char
CHAR Text type*1
Character string varchar
VARCHAR Memo type*1
text
Yes/No type
bit Byte type
int Integer type
smallint Long integer type
NUMBER tinyint Single type
Numeric type CHAR float Double type
VARCHAR real AutoNumber type
char Currency type
varchar
Text type*1
text
Memo type*1
*1 Memo-type fields in Rich Text Format cannot be used with Microsoft Access 2013/2010/2007
■6. Logging ID/Alarm ID

When selecting [Logging] or [Advanced user alarm] for [Resource type], set the logging ID of logging data or the alarm
ID for advanced user alarm data.
■7. Operation log file

The GOT displays the operation log file when [Operation log] is selected for [Resource type] only.
Clicking the Set operation log file name button displays the stored location for the operation log file.
The GOT can send the displayed operation log file to the database.
Inputting the data directly to [Drive Name], [Folder Name], and [File Name] are not available.

POINT
When the operation log settings are changed after setting [Transmit resource action], click the
Set operation log file name button to set the operation log file again.
The settings for [Operation log file] are not automatically changed.
When the displayed data on [Operation log file] does not exist, an error occurs at the job
execution.
■8. Range of data

Specify the maximum number of resource data to be sent for one resource data send action.
When [Operation Log] is selected for [Resource type], [Range of data] is fixed to [Latest data (days specified)].
6
Item Description
Specify the maximum number of resource data collected in the GOT after the last action.
Latest data (No. specified)
(Range:1 to 99999, Default:1)

Specify the time period from the job execution time to the specified time for sending the collected
Latest data (time specified)*1 resource data.
(Range:1 to 99999, Default:1 (seconds))
Specify the number of days including in the date at the job execution for sending the resource data.
(This item cannot be specified for sending the logging data, the advanced user alarm data, and the
Latest data (days specified)*1
advanced system alarm data.)
(Range:1 to 400, Default:1 (days))
All data All the resource data collected in the GOT after the last action.
For details of *1, refer to the following.
*1 Resource data to be sent after changing the GOT time and date
When changing the GOT time, the resource data to be sent may differ from the resource data to be
sent without changing the GOT time.
The following shows the resource data to be sent after changing the GOT time and date.
?Logging data?
• Executing the next action before the time of the last action
Example 1) Changing the time from 11:40 to 11:10, and executing the next action at 11:20
: Time specified (300 seconds)
GOT time
Sending resource data <Resource data to be sent for the last action>
(last action) A:Data collected for the specified time (300 seconds)
A B
(11:25) 11:30 11:40
Sending resource data <Resource data to be sent for the next action>
C
(next action) B:Data collected after the last action until changing
11:10 11:20 the GOT time
C:Data collected for the specified time (300 seconds)
Changing GOT time

• Executing the next action after the time of the last action
GOT time
(last action) A:Data collected for the specified time (300 seconds)
A B D
(11:25) 11:30 (11:35) 11:40
C
(next action) B,C:Data collected for the specified time (300
Changing GOT time 11:20 11:35 seconds)
D:Data collected after the time of the next action (in
the previous GOT time setting)
GOT time
A (last action) A:Data collected for the specified time (300 seconds)
(11:25) 11:30 11:58
B
(next action) B:Data collected for the specified time (300 seconds)
Changing GOT time 12:58 13:00
?Advanced user alarm data/advanced system alarm data?

(The GOT does not send all the data collected after the last acton.)
GOT time
A (last action) A:Data collected for the specified time (300 second
(11:25) 11:30 11:40
(next action) No data
11:00 11:20
Changing GOT time

GOT time
(last action) A:Data collected for the specified time (300 second
A B
(11:25) 11:30 (11:35) 11:40
Sending resource data

C* <Resource data to be sent for the next action>
(next action) Data collected for the specified time (300 seconds)
Changing GOT time 11:20 11:35 B:Data collected before changing the GOT time
C:Data collected after changing the GOT time
* The data collected before the last action are not sent by the next action even though the data is collected within the specified
time.
?Operation log data?
(The GOT does not send all the data collected after the last acton.) 6
Example 1) Changing the time from 0:40 to 23:40 on the previous day, and executing the next
action at 23:50
: Days specified (1 day)

GOT time
Changing date Sending resource data <Resource data to be sent for the last action>
A (last action) A:Data collected for the specified day (1 day)
0:30 0:40

<Resource data to be sent for the next action>
(next action)
No data
23:40 23:50
Changing GOT time
Example 2) Changing the time from 0:40 to 0:10 on the same day, and executing the next action at
0:20
GOT time
Changing date Sending resource data <Resource data to be sent for the last action>
0:30 0:40

<Resource data to be sent for the next action>
(next action)
No data
0:10 0:20
Changing GOT time
Example 1) Changing the time from 23:40 to 0:10 on the next day, and executing the next action at
0:20

GOT time
Changing date
23:30 23:40
B
(next action) B:Data collected for the specified day (1 day) after
Changing GOT time 0:10 0:20 the last action
Example 2) Changing the time from 0:40 to 0:50 on the same day, and executing the next action at
1:00
GOT time
nging date Sending resource data <Resource data to be sent for the last action>
(last action) A:Data collected for the specified day (1 day)
A B
0:30 0:40
C
(next action) B, C:Data collected for the specified day (1 day)
Changing GOT time 0:50 1:00 after the last action
POINT
(1) The GOT sends the resource data only one time, regardless of the settings for [Range of
data]. The GOT does not send the sent data to the database.
The GOT may send the sent data when restarting the GOT for downloading the project data
and others.
(2) When an action fails due to the communication error between the GOT and the server
computer or others, the GOT sends the failed action data at the next action.
(3) The time to complete the resource data send action (Reference value (seconds))
The following shows the resource data send time for the resource type, and the number of
resource data (100, 500, 1000, 10000).
Under the following conditions, the values for sending data differ from the reference values in
the following table.
• Loads on the GOT or loads on between the GOT and the server computer or others
• MES interface function setting
Number of resource data
Resource type
100 500 1000 10000
7 31 59 582
Logging*1*2
(5) (23) (42) (410)
Advanced user alarm*3 2 5 8 88
Advanced system alarm*3 2 5 8 -
Operation log*4 1 5 9 82
*1 The logging is collected by the buffer historical and the device points set to 250 points and a 100ms cycle
for the logging setting.
*2 When collecting data every 100ms cycle is canceled, the value is shown in the parentheses.
*3 When sending the alarm comment with 512 one-byte characters.
*4 When the numbers of insert fields are 7 to 13 by one action.

■9. Generated SQL text
The SQL (INSERT) text generated by the currently editing data for [Transmit resource action] is displayed.
The SQL text shows the display type for the resource data, the character string, and the date.
The GOT does not send the resource data without setting the field name for [Field name setting]. The data with no field
name are not included in the SQL text.
The following table shows the display type for the generated resource data and the date at the job execution. (The
display type differs from the actual data at the job execution.)
Item Description
Resource data*1 'Data name'
String 'String'
GOT time:
TO_DATE('(Date and time[YYYYMMDDhhmmss])',
Oracle 8i
'YYYYMMDDHH24MISS')
Server time: sysdate
Oracle 12c GOT time:

Oracle 11g TO_DATE('(Date and time[YYYYMMDDhhmmss])',
Oracle 10g 'YYYYMMDDHH24MISS')
Oracle 9i
SQL Server 2014

6
Date SQL Server 2012
SQL Server 2008 R2
GOT time: '(Date and time[YYYY-MM-DD hh:mm:ss])'
SQL Server 2008
SQL Server 2005

SQL Server 2000
MSDE2000
Access 2013
Access2010
GOT time: '(Date and time[YYYY-MM-DD hh:mm:ss])'
Access 2007
Server time: NOW()
Access 2003
Access 2000
*1 For the data name, refer to the following.
➠ ■5. Field name setting

6.9 Option Setting
Configure the DB buffering function setting.
Step 1. Click [Option setting] in the Edit items tree.
Step 2. The "option setting" area is displayed on the detailed setting edit screen.
6.9.1 Setting items in DB buffering settings

■1. DB buffering capacity (Range: 16MB to 512MB, Default: 64MB)

Set the capacity used for DB buffering out of the entire CF card capacity within the following range.
Maximum capacity = CF card capacity - 32M bytes
6 - 72 6.9 Option Setting

■2. DB buffering status
(1) Select a tag component into whose device whether data are currently accumulated in the DB buffer or not is stored.
(2) Data are stored as follows depending on the data type.
OFF : Not accumulated

Bit
ON : One or more data accumulated
“0” : Not accumulated

String
“1” : One or more data accumulated
0 : Not accumulated
1 : One or more data accumulated
■3. No. of DB bufferings

(1) Select a tag component into whose device whether data are currently accumulated in the DB buffer or not is stored.
6

Bit

String
1 or greater : Number of buffering data that are accumulated
0 : Not accumulated
1 or greater : Number of buffering data that are accumulated
6.9 Option Setting 6 - 73

■4. Resend DB buffer request
(1) Select a tag component used to request for resend processing of the DB buffer.
(2) The following explains the operation of the resend processing using [Resend DB buffer request].
The resend processing of the DB buffer is performed when the specified tag component is ON.
Normal: Turns OFF after completion of the resend processing.*1*2
Error:
Outputs an error code to MES interface Execute Log, and turns OFF.
Bit
Resend DB buffer request
Tag component value
DB buffer resend processing Execute resend
The resend processing of the DB buffer is performed when "1" is written to the specified tag
component.
String Normal: "0" is written after completion of the resend processing.*1*2
Error:
Outputs an error to the MES interface Execute Log, and "0" is written.
The resend processing of the DB buffer is performed when "1" is written to the specified tag
component.
Other than the above Normal: "0" is written after completion of the resend processing.*1*2
Error:
Outputs an error to the MES interface Execute Log, and "0" is written.
*1 Do not change the value of the specified tag component until the resend processing is completed.
Even if the value changes, the resend processing is not interrupted.
*2 To make another DB buffer resend request after completion of resend processing, wait for a sampling interval of the specified tag
component or more, and then set the device as follows:
• Bit type: ON
• Character string type: "1"
• Other than the above: 1
■5. Clear DB buffer request

(1) Select a tag component used to request for clear processing of the DB buffer.
(2) The following explains the operation of the clear processing using [Clear DB buffer request].
The clear processing of the DB buffer is performed when the specified tag component is ON.
Turns OFF after completion of the clear processing.*3*4
Clear DB buffer request

Bit Tag component value
DB buffer clear
processing Execute clear
The DB buffer is cleared when "1" is written to the specified tag component.
String
"0" is written after completion of the clear processing.*3*4
The DB buffer is cleared when "1" is written to the specified tag component.
Other than the above (Including string)
"0" is written after completion of the clear processing.*3*4
*1 Do not change the value of the specified tag component until the clear processing is completed.
Even if the value changes, the clear processing is not interrupted.
*2 To make another DB buffer clear request after completion of clear processing, wait for a sampling interval of the specified tag
component or more, and then set the device as follows:
• Bit type: ON
• Character string type: "1"
• Other than the above: 1
6 - 74 6.9 Option Setting

■6. DB buffering full
(1) Select a tag component into whose device the status of whether the DB buffer is full or not is stored.

OFF : DB buffer is not full.

Bit
ON : DB buffer is full.
“0” : DB buffer is not full.

String
“1” : DB buffer is full.
0 : DB buffer is not full.

1 : DB buffer is full.
(3) When the DB buffer becomes full, buffering operation will be stopped.
After buffering operation is stopped, even if a job for which DB buffering is enabled is activated, its SQL texts are
discarded without being buffered.
Execution of a job for which DB buffering is enabled is not canceled.
POINT
Check [DB buffer utilization] shown in this 6.9.1 ■7. DB buffer utilization to prevent the "DB buffer 6
full" status.
■7. DB buffer utilization

(1) Select a tag component into whose device the utilization of the DB buffer area (unit: %) is stored.
Tags that have a tag component with [Array setting] cannot be selected
(2) Data are stored as follows depending on the data type


Bit

String
Other than "0" : Utilization of DB buffer area (Unit: %)
0 : Not accumulated
Other than 0 : Utilization of DB buffer area (Unit: %)
6.9 Option Setting 6 - 75

6.10 Diagnosis
Perform the remote diagnosis for the MES interface function.
Step 1. Click the [Diagnosis] tab.
Step 2. The [Diagnosis] sheet is displayed.

Operate it referring to the following descriptions.
6.10.1 Checking the MES Interface Function status (Status)

The operation status of the MES interface function can be checked.
The following explains the display of [Status].
The display of [Status] is updated every 3 seconds.
Display Description
Running The MES interface function is working normally.
The MES interface function is stopped.

Stopped
Even if trigger conditions are met, no job will be executed during stop of the function.
The GOT is in process of powering from OFF to ON, or resetting.

Initializing
Even if trigger conditions are met, no job will be executed during initialization.
The MES interface function is starting up after processing of the above Initializing status.
Starting
Even if trigger conditions are met, no job will be executed during startup.
Stopping The MES interface function is being stopped.
The MES interface function setting screen is attempting to acquire the status from the MES interface
Getting status
function.
The MES interface function setting screen failed to connect to the MES interface function and could
Connection failed
not acquire the status.
The MES interface setting has not been done, or the MES interface function is stopped due to an
Error
error.
6 - 76 6.10 Diagnosis
6.10.2 Manipulating the MES Interface Function status (Operation)
The operation of the MES interface function can be controlled.
■1. Stop
Selecting the [Stop] radio button and clicking the Execute button stops the operation of the MES interface function.
POINT
If a job is in execution, the MES interface function will stop upon completion of the job.
For completion of a job in which a communication error has occurred, refer to the following:
➠ 5.2 (3) When actions are set for a job
■2. Restart
Selecting the [Restart] radio button and clicking the Execute button restarts the operation of the stopped MES
interface function. 6
6.10.3 Changing the job status (Change job status)
The job status can be changed.

POINT
The job status changed by this operation returns to the status set in [Job settings] by powering
OFF and ON or resetting the GOT.
Step 1. From [Job list], select the job whose status is to be changed.
Step 2. Select a checkbox of the status to be changed.

Item Description
• Checked
The job is enabled and thereby it is executed when the trigger conditions are met.
Enable job
• Not checked
The job is disabled, and thereby it is not executed even if the trigger conditions are met.
• Checked
The startup logging is enabled, and thereby startup records are logged.
Enable startup logging *1
• Not checked
The startup logging is disabled, and thereby startup records are not logged.
• Checked
*2
The detailed logging is enabled, and thereby detailed records are logged.
Enable detailed logging
• Not checked
The detailed logging is disabled, and thereby detailed records are not logged.
6.10 Diagnosis 6 - 77
Item Description
• Checked
Writing to PLC devices is disabled.
Disable writing to GOT device
• Not checked
Writing to PLC devices is enabled.
• Checked *3
Writing to the database is disabled.
Disable writing to database
• Not checked
Writing to the database is enabled.
*1 The startup log can be confirmed in [Job Execute Log] on the [Working log] tab.

*2 [Enable detailed logging] is selectable only when [Test mode] is selected in [Job settings].
➠ 6.7.1 ■5. Test mode

When [Enable detailed logging] is checked, [Enable startup logging] is also selected.
The detailed log can be confirmed in [Job Execute Log] on the [Working log] tab.
*3 When [Disable writing to database] is checked, the following processing are executed.
• The SQL text is sent to a database, and then the rollback is executed at the last.
Errors occur when the server service settings and the settings for the actions in [Job settings], including table names and field
names, are incorrect. When an error occurs, check the settings.
Step 3. Clicking the Execute button changes the job status.
6.10.4 Checking the connection of the previous job execution (Connection result of
previous job execution)
Connection with the server computer set in [Server service settings], which is made at the time of the previous job
execution, can be checked.
The following explains the display of [Connection result of previous job execution].
Displayed result Description
Connected Normally connected to the server computer at the time of the previous job execution.
Initial status (Not connected to the database server computer), or normal connection could not be
Disconnected
established at the previous job execution and thereby the line was disconnected.
POINT
• The display of the connection result is not changed until the next job is executed to
communicate the database server computer.
• The result of the one-shot communication with the database server computer is not reflected.
Operate the DB buffering.
■1. Number of bufferings and Buffer utilization

This section explains checking the number of data buffered, the current buffer utilizations, and the highest buffer
utilizations of the DB buffering function.
Description
Display
Current value Highest value*2
No. of bufferings *1
Shows the current number of bufferings (number
of buffered jobs).
Shows the number of bufferings (number of
buffered jobs) in the past.
6
Buffer utilization*1 Shows the current buffer utilization. Shows the highest buffer utilization in the past.
*1 A value is not displayed when the value is being obtained or could not be obtained.

*2 Any of the following operation clears the highest value.
• Restart the MES interface function
• One-shot execution
Note that the highest value is not cleared if the MES interface function was stopped by the diagnostics function.
■2. Resending data stored in the DB buffer

Clicking the Resend button executes the resend processing of the SQL texts stored in the DB buffer, when manual
resend is selected for the jobs of the SQL texts.
If resend processing fails, an error will be output to the MES interface Execute Log.
■3. Clearing the DB buffer

Clicking the Clear button clears all of the SQL texts that are stored in the DB buffer.
6.10 Diagnosis 6 - 79
6.10.6 Checking the trigger buffering (Trigger buffering status)
This section explains checking the number of data buffered, the current buffer utilizations, and the highest buffer utilizations
of the trigger buffering function.
For the trigger buffering function, refer to the following:
➠ 5.1.5 Trigger buffering function
Description
Display
Current value Highest value*2
Shows the current number of bufferings (number Shows the number of bufferings (number of
No. of bufferings*1
of buffered jobs). buffered jobs) in the past.
*1 A value is not displayed when the value is being obtained or could not be obtained.
*2 Any of the following operation clears the highest value.
• Restart the MES interface function
• One-shot execution
POINT
When a large number of data is buffered, check the number of job settings and the trigger
condition setting.
6.11 Working Log
The operation log of the MES interface function can be checked.
In [Working log], the MES interface Execute Log and the Job Execute Log of the GOT can be checked.
Step 1. Click the [Working log] tab.
Step 2. The [Working log] sheet is displayed.
Step 3. Click the Acquire button.
Step 4. Log data are displayed.

Operate this screen referring to the following descriptions.

6.11.1 MES Interface Execute Log
■1. The MES interface function execution log is displayed.
Data displayed in the MES Interface Execute Log are shown below.
Item Description
Date Displays the date and time on which an error occurred.
Displays an error code of the error occurred.

Error code For error codes, refer to the following:
➠ 8.2 Error Code List
Summary Displays an error message.
■2. Updating the MES interface Execute Log

Clicking the Acquire button updates the MES interface Execute Log.
■3. Clearing the MES interface Execute Log

Clicking the Clear button clears the historical data in the MES interface Execute Log.
6.11 Working Log 6 - 81

6.11.2 Job Execute Log
This area displays event log data of the jobs whose executions have been completed.
There are two kinds of Job Execute Log data: [Startup log] and [Detailed log], by which the job startup history and job
execution details can be checked respectively.
■1. Startup log

Startup log data of the jobs, each of which has [Startup logging] setting in [Job settings], are displayed.
➠ 6.7.1 ■4. Startup logging
The following explains the display of the Startup log.
(1) Icon
The completion status of the job is displayed as an icon in the Job Execute Log area.
The following explains the status of each icon.
Icon Description
The job was completed normally. (No detailed log)
The job was completed normally. (With detailed log)
Selecting the job and clicking the View details button displays the [View details] dialog box.
The job was canceled. (No detailed log)
The job was canceled. (With detailed log)
Selecting the job and clicking the View details button displays the [View details] dialog box.
(2) Date
The date and time of job startup is displayed.
(3) Job name
Started jobs are displayed.
(4) Summary
Trigger instructions are displayed.
Display Description
Start Shows that any job other than handshake operation was activated.
Handshake start Shows that job execution of handshake operation was activated.
Handshake end Shows that job execution of handshake operation was completed.
6 - 82 6.11 Working Log

■2. Detailed log
Detailed log data of the jobs, each of which has [Test mode] setting in [Job settings], are displayed.
➠ 6.7.1 ■5. Test mode
POINT
Do not remove the CF card from the GOT during detailed log output.
Step 1. Selecting a job of or icon and clicking the View details button displays the [View details] dialog
box.
The following explains the display of the [View details] dialog box.

Item Description
Displays a list of executed job actions.

Action list
Selecting an action displays its action details.
Program execution result

Displays a program execution result before execution of the first action.
(before action)
Program execution result

Displays a program execution result after execution of the last action.
(after action)
Action details*1*2 *3 Displays the action details.

*1 In the case of Communication action
1)
2)
6)
3)
4)
5)
7)
Display Description
Displays data of [Action type], [Database], and [Table name],

1) Type, Database, Table name
which were set in [Communication action].
Displays the number of records specified for [Specify the

maximum number of acquiring records] in the Multi select setting
2) Request record No. screen for the communication action.
When the number of records is not specified, [No specification] is
displayed.
Displays the execution result of the SQL text.

• When succeeded
3) Execution result [Success] is displayed.
• When failed
[Failed] is displayed.
• When [Select] or [MultiSelect] is selected for [Action type]

The number of records that meet the Select/Update conditions
is displayed.
Applicable record No. • When [Update] is selected for [Action type]
4)
(Insert records No.) The number of updated records is displayed.
• When [Insert] is selected for [Action type] ([Insert records No.] is
displayed.)
The number of inserted records is displayed.
Displays the number of acquired records when [Select] or

5) Acquired record No.
[MultiSelect] is selected for [Action type].
Displays data of [DB-tag link settings], which were set in

6) DB-tag link settings
[Communication action].
7) SQL text The SQL text executed in [Communication action] is displayed.
*2 In the case of Operation action
1)
2)
Display Description
1) Upper row Displays the settings of [Operation action].
2) Lower row Displays values calculated in [Operation action].
6 - 84 6.11 Working Log

*3 In the case of Transmit resource action
1)
3)
4)
2)
5)
6)
Display Description
Displays data of [Action type], [Database], and [Table name],

1) Type, Database, Table name
which were set in [Communication action].
Displays the execution result of the SQL text.

• When succeeded
6
2) Execution result [Success] is displayed.
• When failed
[Failed] is displayed.

Displays the data of [Resource type], [Logging ID/Alarm ID], and
Resource type, Logging ID/Alarm ID,
3) [Operation log file] (the stored location for the operation log file) set
Operation log file
for [Transmit resource action].
Displays the field name set on [Field name setting] in [Transmit

resource action] and the substitute value.
• When the resource data to be sent exists
4) Field name setting Displays the substitute value sent the first.
• When the resource data to be sent does not exist. (all or part of
the substitute value for the field)
No data is inserted to [Value(1st rec.)].
Displays the number of the SQL texts sent for [Transmit resource
action].
Displays 0 in the following cases.
• When sending no resource data (substitute values for all the
5) No. of execute SQL
fields)
• When a communication error occurs between the GOT and the
database
• When the SQL text cannot be sent to the database.
Displays the SQL text executed for [Transmit resource action].

6) SQL text Displays no data when sending no resource data (all or part of
substitute values for the field)
■3. Updating the Job Execute Log

Clicking the Update
Acquire button updates the Job Execute Log.
■4. Clearing the Job Execute Log

Clicking the Clear button clears the Job Execute Log.

6.12 Precautions
Precautions for the MES interface function setting are described below.
■1. When adding, editing or deleting a MES interface setting

Adding a new MES interface setting, or editing or deleting an existing one is performed on the MES interface function
setting screen.
To newly add, edit or delete a MES interface setting, have the MES interface function setting screen displayed on GT
Designer3.
■2. When deleting an item

Deleting an item such as [Device tag settings] is not allowed when the selected item is used for another item such as
[Job settings].
As the error dialog box appears, identify the location, stop using it for another item, and then delete the item.
Up to ten locations of usage are displayed in the error dialog box.

If the item is used in 11 other items or more, the dialog box is displayed as shown below.
■3. Type mismatch

(1) Value substitution
A value is assigned to a tag component after the type of the source is converted into the type of the tag component.
A value is assigned to a variable after the type of the variable is converted into the type of the substitution source.
(Example) Type conversion of tag components and variables
the variable Temp1 is the floating-point type.
A value is assigned after being converted to the type for the tag com
For example, when the tag component, Data1, is double-precision ty
the type of the variable, Temp1, is converted from floating-point to
double-precision first, and then the converted value is assigned.
If a type that cannot be converted is assigned to a tag component, the job execution is canceled.
At this time, "Type conversion to tag component error" is displayed in the MES interface Execute Log.
(2) Operation of numerical values
There are two kinds of numerical values: Integer type and Floating-point type.
• Integer type : Represents the bit type, single-precision type, and double-precision type of tag components.
• Floating-point type : Represents the floating-point type of tag components.
The following table lists operation items and types of the results.
Item Operation result
Operation of floating-point type Floating-point type in all cases
Addition, subtraction, multiplication of In the range from -2147483648 to 2147483647 : Integer type
Integer type Exceeding the above range : Floating-point type
Divisible : Integer type

Not divisible : Floating-point type
Division of Integer type
When zero divide is executed, the job execution is canceled.
At this time, "Zero divide error" is displayed in the MES interface Execute Log.
(3) Operation between character string type values

(a) + operator
Combines character strings.
Example: "ABCDEFG" + "HIJ" "ABCDEFGHIJ"
(b) Other operators
6
When both of the operands can be converted to numerical values, the operation is performed using the
numerical values.
Both or either of them cannot be converted to numerical values, the job execution is canceled.
At this time, "Operation error" is displayed in the MES interface Execute Log.

Example:"312" "4" "1248"
??"31AH" "4" Cancellation of job execution
(c) Operation between a character string type value and a numerical type value
Same as the case of the operation between character string type values
■4. Precautions resource data send action

(1) Checking resource data
The settings for collecting the resource data must be matched to the settings for the resource data send action.
When the settings are not matched, an error may occur at the job execution.
When setting for the resource data send action, click the Confirm setting button, and then check that [No problem in
the resource setting.] is displayed.
When the resource data send action setting differs from the setting for collecting the resource data, the following
error message are displayed.
Resource type Error message Corrective action
Logging function setting does not exist. Set [Logging Setting].

Logging Set the logging ID in [Logging ID/Alarm ID] that is set
The logging ID is not available.
for [Logging Setting].
User alarm function setting does not exist. Set [Advanced User Alarm Observation].
User alarm Set the alarm ID in [Logging ID/Alarm ID] that is set for
The alarm ID is not available.
[User Alarm].
System alarm System alarm function is not available. Check [Use System Alarm] for [System Alarm].
Check [Use Operation Log Settings] for [Operation Log

Operation log function is not available.
Setting].
Operation log
Click the Set operation log file name button to obtain
The operation log file name is mismatch.
the stored file for the operation log setting.
(2) Conditions for sending the sent resource data

When restarting the GOT, the GOT may send the sent data.
Multiple records are created in the database when the GOT sends the sent data.
The following shows conditions for sending the sent resource data
Resource type Condition
Logging No sent resource data is sent.
User alarm When restarting the GOT, the sent resource data is stored in the alarm log file.
System alarm When restarting the GOT, the sent resource data is stored in the alarm log file.
6.12 Precautions 6 - 87
Resource type Condition
Operation log When restarting the GOT, the sent resource data is stored in the operation log file.
(3) Collecting no resource data when executing an action

(a) When the data in the field set for [Field name setting] does not exist.
The GOT sends the data of "" (Null) to the field.
The following resource data shows the resource data types with no data depending on conditions.
Resource type Insert data Action execution
Logging LoggingDevice Sending no data
User alarm Comments Sending ""(Null) data
System alarm None -
Object name(OPNAME), Operation level(OPERATOR),

Operation level(OPE_ID), User ID(USER_ID), Action
Operation log No.(ACT_NO), Data type(DATA_TYPE), Device Sending no data
name(DEV_NAME), Change value(CHG_VALUE),
Previous value(PREV_VALUE)
POINT
Set "null-capable" in the fields for the database.
Without setting "null-capable", an error occurs at the job execution.
For the database setting, refer to the manual for the database to be used.
(b) Collecting no resource data after the last action
The action is succeeded without communicating the GOT with the database. (The MESInterface Execute Log is
output.)
The access log is not output to the server computer.
7. DB CONNECTION SERVICE
AND SETTING TOOL
7
7.1 DB Connection Service Functions . . . . . . . . . . . . . . . . . . . . . . . 7 - 2
7.2 Setting ODBC of Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 4
DB CONNECTION SERVICE AND SETTING TOOL

7.3 Starting DB Connection Service Setting Tool . . . . . . . . . . . . . 7 - 10
7.4 Screen Structure of DB Connection Service Setting Tool . . . 7 - 11
7.5 Setting Items of DB Connection Service Setting Tool . . . . . . 7 - 12
7.6 Importing/Exporting Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 16
7.7 Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 17
7.8 Output Log Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 18
7-1
This chapter explains DB Connection Service and DB Connection Service Setting Tool.
7.1 DB Connection Service Functions

Installing DB Connection Service on the server computer allows to use the MES interface function of the GOT.
The following shows the functions of the DB Connection Service.
POINT
(1) It is necessary to install DB Connection Service on all the database server computers and
application server computers to be accessed from the GOT.
(2) When using DB Connection Service on a database server computer, the ODBC setting for
the database used must be made beforehand.
(3) When using DB Connection Service on an application server computer, an account for user
program execution must be created beforehand.
(4) Changes to the DB Connection Service settings are made with DB Connection Service
Setting Tool.
■1. ODBC connection function

The OBDC connection function connects the GOT and the ODBC interface for database.
The following shows operation on the database server computer.
Database server
Database computer
ODBC
MES interface DB Connection

function Service
When When SQL

accessed execution failed
Access
log SQL
failure log
Step 1. Receives SQL texts from the GOT.
Step 2. Accesses the database via ODBC interface and executes the SQL text.
Step 3. Sends the SQL text execution results to the GOT.
7-2 7.1 DB Connection Service Functions

■2. Program execution function
The program execution function executes a program on an application server computer upon request from the GOT.
The following shows operation on the application server computer.
Application server
Program computer
MES interface DB Connection

function Service
When
accessed
Access
log
7
Step 1. Receives a program execution request from the GOT.
Step 2.

Executes programs on the application server computer.
Step 3. Sends the program execution results to the GOT.
■3. IP filter function

➠ 7.5.3 Limit IP addresses which permit to connect
The IP filter function allows specification of the IP address of the GOT that can connect to the DB Connection Service,
ensuring the security of the server computer.
Batch specification using the mask bit length specification is possible.
If the IP filter function is not used, any GOT can connect to DB Connection Service.
■4. Log output function

DB Connection Service outputs an access log and an SQL failure log.
(1) Access log
➠ 7.5.4 Output access log
The communication contents between the GOT and DB Connection Service are output to the access log.
For access log specifications, refer to the following.
➠ 7.8.1 Access log
(2) SQL failure log
➠ 7.5.5 Output SQL failed log
If data cannot be updated/inserted normally due to an error such as no table at SQL text execution, the error
information is output to the SQL failure log.
For SQL failure log specifications, refer to the following.
➠ 7.8.2 SQL failure log
7.1 DB Connection Service Functions 7-3

7.2 Setting ODBC of Database
When using DB Connection Service on a database server computer, the ODBC setting for the database used must be done
beforehand.
For the ODBC setting, refer to the following.
➠ Manuals and online help for the database software and operating system (OS) used
■1. When Oracle 12c, 11g, 10g, 9i, or 8i is used

(The following shows a setting example when Oracle 11g runs on Microsoft Windows 7 Professional Operating
System.)
Set the following conditions.
• Data source name *1 : SAMPLEDS
• TNS Service Name *2 : SAMPLETNS
• OracleHome: OraDb11g_home1
*1 Data source name can be set as desired.
For [Data source name] in [Server service settings], use the name set with this setting.
*2 The TNS service name is the name for accessing an Oracle database.
The name is entered when installing Oracle and creating a database instance.
This can be checked with [Configuration and Migration Tools] - [Net Manager] - [Service naming] of Oracle. .
(Start)
Step 1. Select [System and Security] in the Control

Panel.
To display Control Panel, select [Start]
[Control Panel].
Step 2. Select [Administrative Tools].
(To the next page)
7-4 7.2 Setting ODBC of Database

(From the previous page)
Step 3. Double-clicking [Data Sources (ODBC)]

displays the [ODBC Data Source
Administrator] dialog box.
Select the [System DSN] tab, and click the
Add button.
Step 4. In the [Create New Data Source] dialog

box, select [Oracle in OraDb11g_home1].

Step 5. In the displayed [Oracle ODBC Driver
Configuration] dialog box, set the
following.
• [Data Source Name]: SAMPLEDS
• [TNS Service Name]: SAMPLETNS
Step 6. Clicking the Connection test button

displays the [Oracle ODBC Driver
Connect] dialog box.
Enter the user name and password, then
click the OK button.
If the connection is normal, the
confirmation dialog box appears.
Step 7. Click the OK button to close the
confirmation dialog box.
(Completed)
7.2 Setting ODBC of Database 7-5

■2. For Microsoft SQL Server 2014, Microsoft SQL Server 2012, Microsoft SQL Server 2008 R2,
Microsoft SQL Server 2008, Microsoft SQL Server 2005, Microsoft SQL Server 2000, and
MSDE 2000
(The following shows a setting example when Microsoft SQL Server 2000 runs on Microsoft Windows 7 Professional
Operating System.)
• Data source name*1: SAMPLEDS
• Server name*2: SAMPLESRV
*2 The server name is the name for accessing a Microsoft SQL Server 2000 database. This name is entered when installing
Microsoft SQL Server 2000.
This can be checked with the SQL Server service manager server.
(Start)

Panel.
[Control Panel].
(To the next page)

Step 3. Double clicking [Data Sources (ODBC)]

displays [ODBC Data Source
Select the [System DSN] tab, then click the
Add button.
Step 4. The [Create New Data Source] dialog box

is displayed, then select [SQL Server].

Step 5. The [Create a New Data Source to SQL
Server] dialog box is displayed, then set
the following.
• [Name]: SAMPLEDS
• [Server]: SAMPLESRV
Step 6. Select the [With SQL Server authentication

using a login ID and password entered by
the user.] radio button, then enter [Login
ID] and [Password].
Step 7. In the [ODBC Microsoft SQL Server

Setup] dialog box, click the [Test Data
Source] button to check that the
connection is normal.

(End)

■3. For Microsoft Access 2013/2010/2007/2003/2000
(The following shows a setting example when Microsoft Access 2003 runs on Microsoft Windows 7 Professional
Operating System.)
• Data source name*1: SAMPLEDS
• Database name*2: C \ mes \ sampledb.mdb
*2 The database name is the name for accessing a Microsoft Access 2003 database. Specify a database file path created with
Microsoft Access 2003.
(Start)

Panel.
[Control Panel].
Step 3. Double clicking [Data Sources (ODBC)]

displays [ODBC Data Source
Select the [System DSN] tab, then click the
Add button.
(To the next page)

Step 4. The [Create New Data Source] dialog box

is displayed, then select [Microsoft Access
Driver(*.mdb)].
For Microsoft Access 2007/2010/2013
Select [Microsoft Access Driver(*.mdb.
*accdb)].
Step 5. The [ODBC Microsoft Access Setup]

dialog box is displayed. Set the following
and click the [Database] [Select] button.
• [Data Source Name]: SAMPLEDS
Step 6. The [Select Database] dialog box is

displayed. Select the following and click

the OK button.
• [Database Name]: sampledb.mdb
• [Directories]: C:\mes

(End)
POINT
Precautions for using Access 2007, Access 2010 and Access 2013
When using SELECT or MultiSelect for a field whose data type is the single type or the double
type, set the following.
• Select [Microsoft Access Driver (*.mdb)] for the ODBC setting for the database.
• When the data base source file is *.accdb, convert it into *.mdb before using it.

7.3 Starting DB Connection Service Setting Tool
POINT
Only one DB Connection Service Setting Tool can be activated.
■1. When Windows 8.1, Windows 8, Windows 7, or Windows Vista is used

Step 1. Select [Start] → [All Programs] → [MELSOFT Application] → [MES Interface] → [DB connection service
setting tool].
Step 2. The following dialog box appears.

Click [Allow].
Step 3. DB Connection Service Setting Tool is started.
■2. When Windows XP is used

Select [Start] → [All Programs] → [MELSOFT Application] → [MES Interface] → [DB connection service setting tool].
After selecting it, DB Connection Service Setting Tool is started.
7 - 10 7.3 Starting DB Connection Service Setting Tool

7.4 Screen Structure of DB Connection Service Setting Tool
This section explains the screen structure of DB Connection Service Setting Tool.
7.4.1 Screen structure
Menu
7.4.2 Menu configuration
7
7.4.2 Menu configuration
This section shows each command provided on the menu bar.

■1. File
Import Imports an existing file.

7.6
Export Exports the DB Connection Service Setting Tool to a file.
Exit Exits the DB Connection Service Setting Tool. ―
■2. Help
Product information Displays product information of the DB Connection Service Setting Tool.
7.7
Connect to MELFANSweb Connects to the Mitsubishi Electric Factory Automation Global Website.
7.4 Screen Structure of DB Connection Service Setting Tool 7 - 11

7.5 Setting Items of DB Connection Service Setting Tool
The following shows how to change the DB Connection Service settings.
Step 1. Set the following items and click the Reflect settings button.
Step 2. After updating the settings, check for an error by selecting [Administrative Tools] - [Event Viewer] in
Windows.
➠ ■2. Error checking procedure
POINT
(1) Change the DB Connection Service settings while a job using the DB Connection Service is
not operating.
The status is as follows:
• The GOT is powered OFF.
• The MES interface function operation is stopped by [MES interface setting] - [Diagnosis]
tab.
(2) If any changed settings are entered with a job using DB Connection Service being operating,
the execution of the connected job is canceled and a communication error occurs.
Also, for a job to which [Enable DB buffering] is selected, SQLtexts are buffered in the DB
buffer.
Item Description
Service port (required) Set the number of a port through which the DB Connection Service operates.
Set a DB access timeout time (Unit: seconds) for writing/reading a database value from the GOT to the server computer, or for the
DB access timeout
case where no response is returned after request for program execution.
Limit IP addresses which permit to connect Specify whether or not to set IP addresses to which connection is to be permitted.
Output access log Set whether or not to output the access log.
Output SQL failed log Set whether or not to output the SQL failure log.
7 - 12 7.5 Setting Items of DB Connection Service Setting Tool

7.5.1 Service port (required) (Range: 1024 to 65535, Default: 5112)
The specified port number is used for communications with the GOT.
Set the number of a port through which the DB Connection Service operates.
Set the same value in [Service port] as the one set in [Port No.] in [Server service settings] under [MES interface setting].
➠ 6.6.1 Setting items in Server service settings
7.5.2 DB access timeout (required) (Range: 1 to 3600; Default: 30)

Set a DB access timeout time (Unit: seconds) for writing/reading a database value from the GOT to the server computer, or
for the case where no response is returned after request for program execution.
When a timeout occurs, the connection with the GOT is disconnected and job execution is canceled.
POINT
Set a value to [DB access timeout] so that the relation with a value set in [Connection timeout] in
[MES Interface Configuration Tool] is as follows:
• Connection timeout value DB access timeout value
7.5.3 Limit IP addresses which permit to connect

■1. Specify whether or not to set IP addresses to which connection is to be permitted.
If the [limit IP addresses which permit to connect] box is checked, connection is permitted from only the GOT with the
specified IP address.
For IP addresses that are permitted to connect to DB Connection Service, at least one IP address setting is required
7
and up to 64 addresses can be set.
If the box is not checked, connection from any GOT will be permitted.
■2. When [limit IP addresses which permit to connect] is selected, set IP address(es).

(1) Adding an IP address to permit its connection
(a) <Specifying individual IP addresses>
Step 1. Set the following items and click the Add button.
Item Description
Set an IP address in decimal notation so that its connection will be

IP address
permitted.
Mask bit length (Blank)
Step 2. The IP address is added to the [Permitted IP addresses list].

(Example) 192.168.0.64
(b) <Specifying IP addresses in a batch>
Step 1. Set the following items and click the Add button
Item Description
Set an IP address in decimal notation so that its connection will be

IP address
permitted.
Set the effective bit length of the set IP address.

Mask bit length
(Range: 1 to 32)
Step 2. The IP address/mask bit length is added to the [Permitted IP addresses list].
(Example) 192.168.0.64/26
7.5 Setting Items of DB Connection Service Setting Tool 7 - 13

(Example) Specifying IP addresses in a batch
If [192.168.0.64] is set for [IP address] and [26] for [Mask bit length], the IP addresses set for connection
permission are [192.168.0.64] to [192.168.0.127], as the logical product is [192.168.0.64].
IP address permitted 192 168 0 ?

to connect 1 1 0 0 0 0 0 0 1 0 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 ? ? ? ? ? ?
255 255 255 192

Mask bit length (26) 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0
Logical product
192 168 0 64
IP address 1 1 0 0 0 0 0 0 1 0 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0
The range in which the logical product above is met is between 192.168.0.64 to 127.
192 168 0 64
1 1 0 0 0 0 0 0 1 0 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0
192 168 0 127

1 1 0 0 0 0 0 0 1 0 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1
(2) Deleting an IP address with connection permission

Select the IP address to be deleted from [Permitted IP addresses list], then click the Delete button.
7.5.4 Output access log

(Default: Output)
■1. Set whether or not to output the access log.

■2. When [Output access log] is selected, set the following items.
Item Description
Output destination Set the output destination of the log file.
Access log capacity Set the capacity for one access log file and the number of files.
(1) Output destination (Default: "dbConnector.log")

Set the output destination of the log file.
If no output destination is set, the log is output to the install folder.
If a read-only file is specified, the log is not output and an [Access log output error] is output to [Event Viewer] of
[Administrative Tools] in Windows.
(2) Access log capacity (Range: 1 to 10MB 2 to 100 files, Default: 1MB 10 files)
Set the capacity for one access log file and number of files.
If the log exceeds the capacity for one file, the data are copied to a file of the original name with a number attached
and a new log file is created.
If the total number of files exceeds the set number of files, files are deleted in order from the oldest one.
7 - 14 7.5 Setting Items of DB Connection Service Setting Tool

(Example) When [Output destination] is set as [dbConnector.log] and [Access capacity] as [1MB 3 files]
Capacity over
Ne
w
dbConnector.log dbConnector.log
Re
na
me
Files
within the
dbConnector.log.001 dbConnector.log.001 specified
Re number of
na
me files
dbConnector.log.002 dbConnector.log.002
De
let
e
Step 1. When [dbConnector.log] exceeds 1M byte, it is renamed as [dbConnector.log.001].

A new [dbConnector.log] is created and logging resumes.
Step 2. [dbConnector.log.001] is renamed as [dbConnector.log.002].
Step 3. The total number of files exceeds 3 if [dbConnector.log.002] is renamed, therefore [dbConnector.log.002]
7
is deleted.
7.5.5 Output SQL failed log

(Default: Output)
■1. Set whether or not to output the SQL failure log.
■2. When [Output SQL failed log] is selected, set the following items.
Item Description
Output destination Set the output destination of the log file.
SQL failure log capacity Set the capacity for one SQL failure log file and the number of files.
(1) Output destination (Default: "SQLFailed.log")

Set the output destination of the log file.
If no output destination is set, the log is output to the install folder.
If a read-only file is specified, the log is not output and an [SQL failure log output error] is output to [Event Viewer] of
[Administrative Tools] in Windows.
(2) SQL failure log capacity (Range: 1 to 10MB 2 to 100 files, Default: 1MB 10 files)
Set the capacity for one SQL failure log file and the number of files.
If the log exceeds the capacity for one file, the data are copied to a file of the original name with a number attached
and a new log file is created.
If the total number of files exceeds the set number of files, files are deleted in order from the oldest one.
7.5 Setting Items of DB Connection Service Setting Tool 7 - 15

7.6 Importing/Exporting Files
Import/export files.
■1. Import
An existing file can be imported.
Step 1. Select [File] [Import] from the menu.
Step 2. The [Open] dialog box is displayed.

Set the following items, then click the Open button.
Item Description
Look in Select the location where the file is stored.
File name Specify the name of the file to be imported.
Select a type of the file to be imported.

Files of type
• DB connection service setting files
■2. Export
DB Connection Service Setting Tool can be exported to a file.
Step 1. Select [File] [Export] from the menu.
Step 2. The [Save As] dialog box is displayed.

Set the following items, then click the button.
Item Description
Save in Select the location where the file is to be saved.
File name Specify the name of the file to be saved.
Select a type of the file to be saved.

Files of type
• DB connection service setting files
7 - 16 7.6 Importing/Exporting Files

7.7 Help
The product information of the DB Connection Service Setting Tool and the Connect to Mitsubishi Electric Factory
Automation Global Website screen can be displayed.
■1. Product information

Step 1. Select [Help] [Product information] from the menu.
Step 2. The [Product information] dialog box of the DB Connection Service Setting Tool is displayed.

■2. Connect to Mitsubishi Electric Factory Automation Global Website
Step 1. Select [Help] [Connect to MELFANSweb] from the menu.
Step 2. The [Connect to MELFANSweb] dialog box is displayed.
Step 3. Click the OK to display the Mitsubishi Electric Factory Automation Global Website.
Online manuals and other information can be viewed on the website.
7.7 Help 7 - 17
7.8 Output Log Specifications
The following shows the output log format for the access log and SQL failure log given in Section 7.8.1 and later.
[Date] [Error code] message Line feed

Item Description
First line
1st to 4th bytes from the

Year Four-digit integer for year (Numbers)
line head
5th byte from the line

Year - Month delimiter "/" (Slash: 2FH)
head
6th and 7th bytes from

Month 2-digit integer (01 to 12) (Numbers)
the line head

Month - Day delimiter "/" (Slash: 2FH)
head

Day 2-digit integer (01 to 31) (Numbers)
the line head

Day - Hour delimiter " " (Space: 20H)
head
[Date] 12th and 13th bytes from

Hour 2-digit integer (00 to 23) (Numbers)
the line head

Hour - Minute delimiter ":" (Colon: 3AH)
head

Minute 2-digit integer (00 to 59) (Numbers)
the line head

Minute - Second delimiter ":" (Colon: 3AH)
head

Output Second 2-digit integer (00 to 59) (Numbers)
the line head
character
Second - Millisecond delimiter 20th byte from the line head "." (Period: 2EH)
21st to 23rd bytes from

Millisecon 3-digit integer (000 to 999) (Numbers)
the line head

Millisecond - Error code delimiter " " (Space: 20H)
head
25th to 34th bytes from

[Error code]*1 Alphanumeric character of "0x"+8-digithexadecimal
the line head

Error code - Message delimiter " " (Space: 20H)
head
36th and later bytes from

Message Compliant with the specifications of each log
the line head
Line feed End of line CR + LF (0DH, 0AH)
Second line (For database errors only)
Tab Line head TAB (09H)
2nd to 17th bytes from

Database message header "Database Message "
the line head
Database message header - Database message 18th byte from the line
" " (Space: 20H)
delimiter head
19th and later bytes from

Database message Error messages that the database outputs
the line head
Line feed End of line CR + LF (0DH, 0AH)
*1 For error codes, refer to the following:
7 - 18 7.8 Output Log Specifications

7.8.1 Access log
The following explains the access log contents.
■1. Service start/end

(1) Start
Item Description
Output log format [Date] [Error code] Service Start
Example 2005/07/01 12:00:00.000 0x00000000 Service Start
(2) End
Item Description
Output log format [Date] [Error code] Service Stop
Example 2005/07/01 12:00:00.000 0x00000000 Service Stop
■2. Connection/disconnection from the GOT

(1) Connection
Item Description
Output log format [Date] [Error code] SID [Session ID]:MIFWS Connected:[Source IP]:[Target data source]:[Connection ID]
Example 2005/07/01 12:00:00.000 0x00000000 SID 0:MIFWS Connected:192.168.3.3:DataSource:ID

7
(2) Disconnection
Item Description
Output log format [Date] [Error code] SID [Session ID]:MIFWS Disconnected:[Source IP]:[Target data source]:[Connection ID]

Example 2005/07/01 12:00:00.000 0x00000000 SID 0:MIFWS Disconnected:192.168.3.3:DataSource:ID
■3. Connection/disconnection to a database

(1) Connection
Item Description
Output log format [Date] [Error code] SID [Session ID]:DB Connect:[Target data source]: [Connection ID]:[Connection result*1]
Example 2005/07/01 12:00:00.000 0x00000000 SID 0:DB Connect:DataSource:ID:Success
*1 When succeeded: Success, when failed: Failed
(2) Disconnection
Item Description
Output log format [Date] [Error code] SID [Session ID]:DB Disconnect:[Target data source]: [Connection ID]:[Disconnection result*1]
Example 2005/07/01 12:00:00.000 0x00000000 SID 0:DB Disconnect:DataSource:ID:Success
*1 When succeeded: Success, when failed: Failed
7.8 Output Log Specifications 7 - 19

■4. SQL text reception/processing results
(1) SELECT
Item Description
Output log format [Date] [Error code] SID [Session ID]:SQL<[SQL text]>:[Processing result*2]([No. of selected records])
Example 2005/07/01 12:00:00.000 0x00000000 SID 0:SQL<SELECT COL from TABLE;>:Success(1)
*1 When succeeded: Success ([No. of selected records]), when failed: Failed (Line feed) Database message
(2) UPDATE
Item Description
Output log format [Date] [Error code] SID [Session ID]:SQL<[SQL text]>:[Processing result*3]([No. of updated records])
Example 2005/07/01 12:00:00.000 0x00000000 SID 0:SQL<UPDATE TABLE SET COL = '';>:Success(1)
*1 When succeeded: Success ([No. of updated records]), when failed: Failed (Line feed) Database message
(3) INSERT
Item Description
Output log format [Date] [Error code] SID [Session ID]:SQL<[SQL text]>:[Processing result*4]([No. of inserted records])
Example 2005/07/01 12:00:00.000 0x00000000 SID 0:SQL<INSERT INTO TABLE ( COL ) VALUES ('') ;>:Success(1)
*1 When succeeded: Success ([No. of inserted records]), when failed: Failed (Line feed) Database message
(4) COMMIT
Item Description
Output log format [Date] [Error code] SID [Session ID]:COMMIT:[Processing result*5]
Example 2005/07/01 12:00:00.000 0x00000000 SID 0:COMMIT:Success
*1 When succeeded: Success, when failed: Failed (Line feed) Database message
(5) ROLLBACK
Item Description
Output log format [Date] [Error code] SID [Session ID]:ROLLBACK:[Processing result*6]
Example 2005/07/01 12:00:00.000 0x00000000 SID 0:ROLLBACK:Success
(6) GetNext (Request for next record)

Item Description
Output log format [Date] [Error code] SID [Session ID]:GetNext:[Processing result*7]
Example 2005/07/01 12:00:00.000 0x00000000 SID 0:GetNext:Success
■5. Program execution reception/processing results

Item Description
Output log format [Date] [Error code] SID ProgramExec:[Source IP]:<[Command line]>[Processing result*8]([Return value])
Example 2005/07/01 12:00:00.000 0x00000000 ProgramExec:192.168.3.3:<hoge.exe>:Success(0)
*1 When succeeded: Success ([Return value]), when failed: Failed only
7.8.2 SQL failure log

The following shows the SQL failure log contents.
Item Description
Output log format [Date] [Error code] [Target data source]:[SQL text]
2005/07/01 12:00:00.000 0x00000000 DataSource:INSERT INTO TABLE ( COL ) VALUES ('') ;

Example
Database Message 0x00000388 [Oracle][ODBC][Ora]ORA-00904: "NUM" :invalid identifier
7 - 20 7.8 Output Log Specifications

8. TROUBLESHOOTING
8.1 Error Handling and Recovery Method . . . . . . . . . . . . . . . . . . . . 8 - 2
8.2 Error Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 6
TROUBLESHOOTING
8-1
8.1 Error Handling and Recovery Method
This section describes how to check an error output when using the MES interface function.
■1. Error checking and restoration

The following lists the points to be checked when an error occurred, and corresponding recovery methods.
Error type Check point Recovery method
• Check a warning dialog displayed when a setting out • When a value out of the permitted range has been
MES interface setting error of the permitted range was made in the MES entered in the MES interface function setting, disable
interface function setting. the entry and return to the previous status.
• Check the GOT for a system alarm.

• If any problem is found in the setting, reconfigure the
• Check the MES interface Execute Log.
MES interface function execution MES interface setting and restart the GOT.
• Check the status information.
error • For an error of the GOT or a controller, restore it to
• Check the value of the tag component used for
normal condition according to its specifications.
notification.
• Check a warning dialog displayed when a setting out • When a value out of the permitted range has been
DB Connection Service setting
of the permitted range was made in DB Connection entered in DB Connection Service Setting Tool,
error
Service Setting Tool. disable the entry and return to the previous status.
• If any problem is found in the setting, reconfigure the

• Check Event Viewer of Windows. settings in DB Connection Service Setting Tool and
DB Connection Service execution
• Check the access log file. restart DB Connection Service.
error
• Check the SQL log file. • If the server computer has a problem, resolve it and
restart DB Connection Service.
POINT
If more than one error are displayed in the error log of [MESI/F Log] or by error dialog boxes, take
corrective actions in chronological order.
8-2 8.1 Error Handling and Recovery Method

■2. Error checking procedure
For error codes, refer to the following:
Item Checking procedure
MES interface function execution

Shows how to check an error occurred in execution of the MES interface function.
error
System alarm checking • For the system alarm checking procedure, refer to the following manual.
procedure ➠ GT Designer3 (GOT2000) Screen Design Manual
• Connect the operating GOT to a configuration computer.

Working log checking
*1
• Display the Working log sheet in the MES interface setting.
procedure
• Display the detailed log from the Working log sheet and check the data.
• Connect the operating GOT to a configuration computer.

Status checking procedure
• Display the Diagnosis sheet in the MES interface setting and check the data.
• Set a notification tag in the MES interface setting.

• Add a setting for monitoring the tag value on the GOT screen.
• On the GOT screen, check if an error or exception has occurred in the tag or not.
• Notification tags can be set for the following four items:
[Job settings] - [Communication action] - [Exception process setting] - [Exception processing: No applicable
Notification tag component record]
value checking procedure [Job settings] - [Communication action] - [Exception process setting] - [Exception processing: Multiple
applicable records]
[Job settings] - [Communication action] - [Exception process setting] - [Exception processing: Applicable
records overflow]
[Job settings] - [Notify errors (job cancellation) that occur during job execution]
[Server service settings] - [Access error notification setting]
DB Connection Service execution

error
Shows how to check an error occurred in execution of DB Connection Service. 8
• From the Windows start menu, select [Control Panel] - [Performance and Maintenance] - [Administrative
Windows Event Viewer Tools] - [Event Viewer]. (Windows XP)
checking procedure • Select the Application log to display the list.
TROUBLESHOOTING
• Click on [Source] (sorting the list by the source name), and check for "DB Connector."
Access log checking • In DB Connection Service Setting Tool, select [Output access log].
procedure • Display the output file with Windows Notepad.
• In DB Connection Service Setting Tool, select [[Output SQL failed log].

SQL log checking procedure
• Display the output file with Windows Notepad.
*1 A CF card is required.
8.1 Error Handling and Recovery Method 8-3

8.1.1 MES Interface Function setting
This section explains troubleshooting information on the setting of the MES interface function.
■1. Common to all settings

Symptom Checked item Corrective action
• Check that no other GT Designer3 is running

and communicating on the same personal
Is the GOT communicating with another GT
computer.
Designer3?
• Check that GT Designer3 is not running and
communicating on other personal computers.
Is there any disconnection in the connection

• Connect the cables properly.
route?
Is there any problem on the personal computer? • Replace it with another computer.
Is the port number correct?

GT Designer3 cannot communicate with GOT. • Check the port number setting.
(In RS-232 or Ethernet connection)
• Issue the ping command from the personal

Is the GOT connected to the network?
computer to the GOT to confirm the network
(When using Ethernet connection)
connection.
Is the IP address setting correct?

• Correct the IP address setting.
(When using Ethernet connection)
Is there a firewall and/or a proxy server in the

• Ask your network administrator about the
connection route?
firewall and proxy server settings.
(In Ethernet connection)
All the text is not displayed in a table. • Adjust the column width of the table.
Isn't the column width narrow?
(The text display is truncated.) 6.3.1 Screen structure
■2. [Device tag settings]

Is the selected item used in [Job settings]?

• As the error dialog box appears, identify the
Is the selected item used in [DB buffering location, stop using it for another item, and
Unable to change or delete an item in [Device
setting] of [Option setting]? then delete the item.
tag settings].
• An item used for another item is unable to be
Is the selected item used in [Access error
deleted.
notification setting] of [Server service settings]?
• Because a unique name must be used for

Is the same name used for [Server service
Unable to set or change [Device tag name]. [Server service name] and [Device tag
name] or another [Device tag name]?
name], use a different name.
■3. [Job settings]

➠ 6.7 Job Settings
• Do not use Select actions in the job where DB

buffering is enabled.
Unable to set [DB buffering setting]. Is there any Select action set for the job?
• The DB buffering is not available for jobs
performing Select actions.
• Delete any unnecessary variable settings of

Are there 64 variables that were already defined
Unable to set a new variable. the job.
in the job?
• Up to 64 variables can be set for one job.
• Select any other than [Handshake operation]

Unable to select [Trigger 2] in [Trigger Is [Handshake operation] selected for [Trigger for [Trigger 1].
conditions]. 1]? • When [Handshake operation] is selected,
selection is not allowed for [Trigger 2].
Unable to set [Exception processing setting] in Is the DB buffering enabled? • Disable the DB buffering.
[Communication action]. Is [Insert] set for [Action type]? • Set any other than [Insert] for [Action type].
8-4 8.1 Error Handling and Recovery Method

■4. [Diagnosis] tab
➠ 6.10 Diagnosis
Has a system application (extended function) of

GT Designer3 cannot communicate with GOT. • Install the package data on the GOT.
[MES Interface] been installed?
■5. [Working log] tab

➠ 6.11 Working Log
Has a system application (extended function) of

GT Designer3 cannot communicate with GOT. • Install the package data on the GOT.
[MES Interface] been installed?
• Install a CF card.
Is there a CF card inserted?
• Turn ON the CF card access switch.
No log is displayed.
• On the Diagnosis tab, check the MES
Is the MES interface function operating?
interface function status.
• Check if Adjust is enabled with the Utility

No execution result is displayed in spite of
Is the time adjust function of the GOT disabled? function of the GOT.
SNTP server setting.
• Check if Adjust is enabled in GT Designer3.
8.1.2 When using DB Connection Service Setting Tool

This section explains troubleshooting information on the setting of DB Connection Service Setting Tool.
➠ 7. DB CONNECTION SERVICE AND SETTING TOOL
Symptom Checked item Corrective action 8
• Terminate the already started DB Connection
Unable to start DB Connection Service Setting Has DB Connection Service Setting Tool been Service Setting Tool.
Tool. already started? • Only one DB Connection Service Setting Tool
can be activated.
TROUBLESHOOTING
Was a user ID having the administrator authority • Log in again with a user ID having the
Unable to reflect the setting.
used for the login? administrator authority.
• Uncheck the [limit IP addresses which permit to

Unable to save the setting. Is there no permitted IP address? connect] checkbox, or add an IP address for
which connection is permitted.
Is the file set in [Output destination] read-only? • Correct the file specification.
[Access log output error] is recorded in [Event Is the access to the folder containing the file set in
• Check the right of access to the folder.
Viewer] of [Administrative Tools] in Windows. [Output destination] authorized?
Is the drive space of the server computer full? • Check the free space on the drive.
Is the file set in [Output destination] read-only? • Correct the file specification.
[SQL failure log output error] is recorded in [Event Is the access to the folder containing the file set in
• Check the right of access to the folder.
Viewer] of [Administrative Tools] in Windows. [Output destination] authorized?
Is the drive space of the server computer full? • Check the free space on the drive.
8.1 Error Handling and Recovery Method 8-5

8.2 Error Code List
The error code list is shown below.
For the error output checking method, refer to the following.
➠ 8.1 Error Handling and Recovery Method
8.2.1 Error log in the Working log

Error code Error description and cause Corrective action
• The device value cannot be collected. Check the device

0x41130001 Tag value collecting error
settings and the network configuration.
0x41140029 • The set data are erroneous.

Download them again.
Setting read error
0x4114002A • In the case of one-shot job execution, the CF card may
corrupted. Replace the CF card.
• Check the Ethernet connection.

• An Ethernet communication error has occurred.
• Check if [Server service settings] are correct.
0x4114002B DB connection service communication error
➠ 6.6 Server Service Settings
• Check if the ODBC setting is correct.
• The data cannot be converted to the specified type.

0x4114005F Type conversion error • Change the setting so that type conversion will be
available in any case.
• Failed to write data to the tag.

0x41140061 Tag write error • Check if data can written to the device specified for the
tag component.
• Check if [Device tag settings] are correct.

0x41140065 Failed to perform the tag access.
• Failed to read data from the tag.

0x41140069 Tag value read error • Check if [Device tag settings] are correct.
• The data could not be converted to the type specified for

the tag component.
0x41140077 Type conversion to tag component error
• Change the setting so that type conversion will be
0x41140081 • Data stored in the DB buffer are invalid.

DB buffer content error • The CF card may be corrupted.
0x41140083 • Replace the CF card.
• A part of invalid data in the DB buffer has been

corrected.
0x41140084 Partial correction of DB buffer content
• A part of the DB buffered data in the CF card may have
been corrupted.
• Failed to clear the DB buffer.

0x41140086 DB buffer clear error • The CF card may be corrupted.
• Replace the CF card.
• The DB buffer file is invalid.

0x41140087 DB buffer file error • The CF card may be corrupted.
• Data stored in the DB buffer are invalid.

0x41140089 DB buffer content error • The CF card may be corrupted.
• Because the DB buffer became full, the data could not

0x41140093 DB buffer full error be stored in the DB buffer.
• Ensure the CF card capacity.
• Failed in file operation during DB buffering operation.

0x41140099 DB buffering error
• Check the CF card, and if corrupted, replace it.
• Data in the DB buffer could not be read normally.

0x4114009F DB buffer read error
• Failed to clear the DB buffer.

0x411400A1 DB buffer clear error
8-6 8.2 Error Code List

• Data in the DB buffer could not be read normally.

0x411400A3 DB buffer read error
• The DB buffer is empty.

0x411400A5 DB buffer empty error
• Data stored in the DB buffer are invalid.

0x411400A6 DB buffer content error
0x411400B2
• Character strings could not be converted to numerical
0x411400B6 values.
Character string number conversion error
0x411400BA • Change the setting so that type conversion will be
0x411400C0
• Division by zero was attempted.

0x411400D0 Overflow or zero divide error
• Change the setting to avoid division by zero.
• Invalid operation was performed.

0x411400D2 Operation error • Change the setting so that any invalid operation will not
performed.
• Check that the option OS for the logging function for

0x411400D4 Logging function is not running. installed on the GOT.
• Check that the logging setting is configured.
• The logging ID is invalid.

0x411400D6 Invalid logging ID.
• Set the logging ID for the logging setting.
• The advanced system alarm setting is invalid.

0x411400DC Advanced system alarm function is not available.
• Set the advanced system alarm observation setting.
• The alarm ID is invalid.

0x411400E2 Invalid alarm ID. • Set the alarm ID for the advanced user alarm
observation setting.
8
• The maximum number of obtained records is invalid.
0x411400E8 Invalid max number of select record. • Set the tag component value specified as the maximum
number of records 1 or more.
• Check that the required system application (extended
TROUBLESHOOTING
0x411400EA Operation log function is not running function) is installed on the GOT.
• Check that the operation log setting is configured.
0x411400EE Unable to find the operation log file. • The MES interface function in the GOT cannot access
the operation log file.
0x411400F0 Unable to open the operation log file.
• Check that the CF card including the operation log file is
0x411400F2 Unable to acquire the operation log file. installed in the GOT.
• An error occurred in the Ethernet communication, and

the communication failed to start.
0x41150110 Communication start error • Check if [Server service settings] are correct.
0x41150120 Communication connection error

0x41150121 Communication connection timeout • Check if [Server service settings] are correct.
0x41150130 Message transmission error
0x41150131 Message transmission timeout
8.2 Error Code List 8-7


0x41150140 Message reception error
• Check if [Server Service setting] are correct.
• Check the error information of DB Connection Service
0x41150141 Message reception timeout (access log file).
0x41150160 DB transaction status error
0x41150161 DB transaction start status error • Check the transaction status of the database.
0x41150162 DB transaction end status error
• The connection to unsupported DB Connection Service

0x41150300 Unsupported DB Connection Service error is failed.
• Check the version of DB Connection Service.
• The connection to DB Connection Service with

0x41150301 Unsupported communication timeout setting unsupported communication timeout is failed.
• Check the version of DB Connection Service.

• Check if [Server service settings] are correct.
0x41151010 Database connection error
0x41151110 Message reception error • An Ethernet communication error has occurred.

• Check if [Server Service setting] are correct.
0x41151120 Received message data error
• Check the error information of DB Connection Service
(access log file).
Waiting for DB access (program execution) completion • No response is received from DB Connection Service.
0x41151180
timeout Check the server and the network.
0x41151320 SELECT execution error
0x41151330 COMMIT execution error

• Check the sent SQL text and database contents.
0x41151340 ROLLBACK execution error
• Check if the table and field settings are correct.
0x41151350 DB update error
0x41151410 SQL execution error
0x41151420 ODBC connection error during SQL execution
0x41152005 • Check if the program specified with the program

Execution error (Program execution function) execution function is executable with the specified
0x41152006 account.
• There is no execution file of the program that is specified

for the program execution function.
Specified program file not exist (Program execution
function)
execution function is executable with the specified
account.
• There are more than one execution file of the program

that is specified for the program execution function.
Specified program file duplicated (Program execution
function)
execution function is executable with the specified
account.
8-8 8.2 Error Code List


to Execution error (Program execution function) execution function is executable with the specified
0x41152014 account.
TROUBLESHOOTING
8.2 Error Code List 8-9

8.2.2 DB Connection Service
The DB Connection Service outputs errors to the Windows Event Log, access log, and SQL failure log.
For Windows Vista, DB Connection Service Client also outputs errors to Windows Event Log.
■1. Event log of Windows

(1) Event log output warning list of DB Connection Service (Source name: DBConnector)
Warning event ID Error description and cause Corrective action
• Configure the settings again with DB Connection

There is no setting file. Service Setting Tool.
1
Start the service using the default setting. ➠ 7.5 Setting Items of DB Connection Service Setting
Tool
(2) Event log output warning list of DB Connection Service (Source name: DBConnector)
Error event ID Error description and cause Corrective action
1 Unable to start the service due to insufficient memory.

• Add more memory to the personal computer.
2 Unable to start the service due to insufficient resources.
Failed to read the setting file. • Refer to the actions of error codes 101 to 129.
5
The service is stopped. • Actions are displayed with error codes 101 to 129.
• Refer to the actions of error codes 401 to 403, and 501

Failed to initialize the log file. to 503.
6
The service is stopped. • Actions are displayed with error codes 401 to 403, and
501 to 503.
• Change the server port No. with DB Connection

The server port has already been opened. Service Setting Tool.
9
The service is stopped. ➠ 7.5 Setting Items of DB Connection Service Setting
Tool
The computer ran out of memory while reading the setting • Terminate any unnecessary applications.
101
file. • Add more memory to the personal computer.
• Reinstall the DB Connection Service to the directory

102 The setting file path is too long.
whose path name is shorter.
103 The setting file name indicates the directory.

• Reinstall the DB Connection Service.
104 The setting file could not be opened.
• Terminate other applications, and make the setting

again with DB Connection Service Setting Tool.
105 Description of the setting file is not correct.
➠ 7.5 Setting Items of DB Connection Service Setting
Tool
108 The server port No. setting is not correct.
109 The server port No. setting is out of range.
110 The timeout time setting is not correct.
111 The timeout time setting is out of range.
There are too many connection-permitted IP address

112
settings.
• Configure the settings again with DB Connection
Description of the connection-permitted IP address setting Service Setting Tool.
113
is not correct.
The mask bit length setting of the connection-permitted IP Tool
114
address is not correct.
The mask bit length setting of the connection-permitted IP

115
address is out of range.
116 The access log setting is not correct.
117 The setting of the access log file name is not correct.
118 The access log file name is too long.
8 - 10 8.2 Error Code List

The maximum file size setting for the access log is not
119
correct.
The maximum file size setting for the access log is out of
120
range.
The maximum number of access log files is not set

121
correctly.
122 The maximum number of access log files is out of range.
123 The SQL failure log setting is not correct. • Configure the settings again with DB Connection
124 The setting of the SQL failure log file name is not correct. Service Setting Tool.
125 The SQL failure log file name is too long. ➠ 7.5 Setting Items of DB Connection Service Setting
Tool
The maximum file size setting for the SQL failure log is not
126
correct.
The maximum file size setting for the SQL failure log is out
127
of range.
The maximum number of SQL failure log files is not set

128
correctly.
The maximum number of SQL failure log files is out of

129
range.
The computer ran out of memory when initializing the

401
access log file. • Terminate any unnecessary applications.
The computer ran out of resources when initializing the • Add more memory to the personal computer.
402
access log file.
• Shorten the path to the access log file with DB

Connection Service Setting Tool.
403 The full path name of the access log file is too long.
8
Tool
• If no directory exists for storing the access log file,

create it.
• When the attribute of the access log file is set to read-
TROUBLESHOOTING
only, cancel the setting.
• If read/write is disabled for the access log file, enable it
404 The access log file could not be opened. in the security setting.
• When the access log file name represents a directory,
rename or delete the directory.
• When the access log file has been open in another
application, terminate the application.
• Check the disk device for any fault.
• When the disk space is full, ensure a free disk space.

• When the access log file has been open in another
405 The log could not be written to the access log file.
• When the attribute of the oldest access log file is set to

read-only, cancel the setting.
• If read/write is disabled for the oldest access log file,
406 Failed to delete an old access log file. enable it in the security setting.
• When the oldest access log file has been open in
another application, terminate the application.
• When the attributes of the new and old access log files
are set to read-only, cancel the setting.
• If read/write is disabled for the new and old access log
407 Failed to rename the access log file. files, enable it in the security setting.
• When the new and old access log files have been open
in another application, terminate the application.
The computer ran out of memory when initializing the SQL

501
failure log file. • Terminate any unnecessary applications.
The computer ran out of resources when initializing the • Add more memory to the personal computer.
502
SQL failure log file.
8.2 Error Code List 8 - 11

• Shorten the path to the SQL failure log file with DB

503 The full path name of the SQL failure log file is too long.
Tool
• If no directory exists for storing the SQL failure log file,

create it.
• When the attribute of the SQL failure log file is set to
read-only, cancel the setting.
• If read/write is disabled for the SQL failure log file,
504 The SQL failure log file could not be opened. enable it in the security setting.
• When the SQL failure log file name represents a
directory, rename or delete the directory.
• When the SQL failure log file has been open in another
• When the disk space is full, ensure a free disk space.

• When the SQL failure log file has been open in another
505 The log could not be written to the SQL failure log file.
• When the attribute of the oldest SQL failure log file is

set to read-only, cancel the setting.
• If read/write is disabled for the oldest SQL failure log
506 Failed to delete an old SQL failure log file. file, enable it in the security setting.
• When the oldest SQL failure log file has been open in
another application, terminate the application.
• When the attributes of the new and old SQL failure log
files are set to read-only, cancel the setting.
• If read/write is disabled for the new and old SQL failure
507 Failed to rename the SQL failure log file. log files, enable it in the security setting.
• When the new and old SQL failure log files have been
open in another application, terminate the application.
(3) Event log output error list of DB Connection Service Client (source name: DBCnctClient)
50
51 • Terminate unnecessary applications.

Unable to start DB Connection Service Client.
52 • Add more memory to the computer.
53

■2. Access log of DB Connection Service
(Service Not Start.)

0x20100001
Failed to start the service due to insufficient memory. • Terminate any unnecessary applications.
(Service Not Start.) • Add more memory to the personal computer.
0x20100002
Failed to start the service due to insufficient resources.
(Service Not Start.)

• If a firewall software has been installed, make the
0x20100011 Failed to start the service due to failure of the server port
specified server port operational.
initialization.
• Terminate the application that has opened the server

port.
(Service Not Start.) • Set another server port No. with DB Connection
0x20100012
Another application has opened the server port. Service Setting Tool.

Tool
(Not Initialize a service for each client: [IP address])

• Terminate any unnecessary applications.
0x20200001 Failed to initialize a service for each client due to
insufficient memory.
• Using DB Connection Service Setting Tool, add the IP

(Deny network connection request from [IP address]) address to those with connection permission.
0x20200002 Rejected the connection request from the non-permitted
IP address. ➠ 7.5 Setting Items of DB Connection Service Setting
Tool
(SID [Session ID]: Request Receive Error: [IP address]) • Terminate any unnecessary applications.
0x20300001
Failed to receive data due to insufficient memory. • Add more memory to the personal computer.
(SID [Session ID]: Request Receive Error: [IP address])

0x20300010
Connection disconnected during request reception. 8
0x20300011
Timed out during request reception. • Check if it is connected to the network.
(SID [Session ID]: Request Receive Error: [IP address]) • Check if the gateway and/or hub is operating.
• Check if the power of the GOT has not been turned off.
TROUBLESHOOTING
0x20300012 Detected failure of the MES interface module while waiting
for or receiving a request.

0x20300013
Receive I/O error

0x20300014 • Check the source IP address setting.
Buffer overrun (Request length exceeded)
• Check the version of a system application (extended
(SID [Session ID]: Request Receive Error: [IP address]) function) of [MES Interface].
0x20300015
Received an invalid request.
(SID [Session ID]: Response Transmit Error: [IP address])

0x20310010
Failed to transmit a response due to disconnection.

0x20310011
Timed out during response transmission.
• Check if it is connected to the network.
(SID [Session ID]: Response Transmit Error: [IP address]) • Check if the power of the GOT has not been turned off.
0x20310012 Detected failure of the MES interface module during
response transmission.

0x20310013
Send I/O error
(SID [Session ID]: DB Connect: [Data source]: [User]:

0x20400001 Failed)
Failed in DB connection due to insufficient memory. • Terminate any unnecessary applications.
(SID [Session ID]: DB Connect: [Data source]: [User]: • Add more memory to the personal computer.
0x20400002 Failed)
Failed in DB connection due to insufficient resources.
(SID [Session ID]: DB Connect: [Data source]: [User]: • Check the source IP address setting.
0x20400010 Failed) • Check the version of a system application (extended
Invalid DB connection request function) of [MES Interface].
(SID [Session ID]: DB Connect: [Data source]: [User]:

• Terminate any unnecessary applications.
0x20400020 Failed)
Failed to create a DB handle.

• Set correct data source name, user name, and

password in [Server service settings] of [MES interface
setting].
(SID [Session ID]: DB Connect: [Data source]: [User]: • Check if the personal computer is restarted after the
0x20400022 Failed) database is installed. Restart the personal computer if
Failed in DB connection. not restarted.
• When the server computer is running a 64 bit OS, call
the [ODBC Data Source Administrator] dialog box.
To call this dialog box, enter the following command line
in the Command Prompt.
%SystemRoot%\SysWOW64\odbcad32.exe
(SID [Session ID]: SQL<...>: Failed)

(SID [Session ID]: COMMIT: Failed)
(SID [Session ID]: ROLLBACK: Failed)
0x20600001
(SID [Session ID]: GetNext: Failed)
(SID [Session ID]: Reset: Failed)
Failed in SQL execution due to insufficient memory. • Terminate any unnecessary applications.
(SID [Session ID]: SQL<...>: Failed) • Add more memory to the personal computer.
0x20600002
Failed in SQL execution due to insufficient resources.

0x20600010
Invalid SQL execution request • Check the source IP address setting.
(SID [Session ID]: SQL<...>: Failed) • Check the version of a system application (extended
(SID [Session ID]: COMMIT: Failed) function) of [MES Interface].
0x20600020 (SID [Session ID]: GetNext: Failed)
DB Connection Service does not support the SQL
instruction to be executed.

0x20600021
(SID [Session ID]: Reset: Failed) • Correctly set a database type for [DB server setting], a
Failed in preparation before SQL execution. table name in the job for the communication action
setting, or the resource data send action setting in
[MES Interface].
(SID [Session ID]: ROLLBACK: Failed) ➠ 6.6 Server Service Settings
0x20600022 (SID [Session ID]: GetNext: Failed)
Failed to obtain the number of fields in the record that is to
be obtained by the SQL execution.
(SID [Session ID]: SQL<...>: Failed) • Correctly set a database type for [DB server setting], a
(SID [Session ID]: COMMIT: Failed) table name, field names, Select/Update conditions, and
(SID [Session ID]: ROLLBACK: Failed) types of the data to be stored in the fields in the job for
0x20600023 the communication action setting or the resource data
(SID [Session ID]: Reset: Failed) send action setting in [MES Interface].
Failed in SQL execution. ➠ 6.6 Server Service Settings
(SID [Session ID]: SQL<...>: Failed) • In [MES interface setting], set update conditions
(SID [Session ID]: COMMIT: Failed) correctly for the Communication action setting of the
(SID [Session ID]: ROLLBACK: Failed) Job settings.
0x20600025
(SID [Session ID]: GetNext: Failed) ➠ 6.8.1 Setting items in Communication action
(SID [Session ID]: Reset: Failed) • Check if the database has been filled with registered
No record was updated or inserted by the SQL execution. data.
(SID [Session ID]: *** Transmitting Commit Success • Check if it is connected to the network.
0x2060002B Response Failed. ***) • Check if the gateway and/or hub is operating.
Failed to transmit the COMMIT success response. • Check if the power of the GOT has not been turned off.

(ProgramExec: [IP address]: <...>: Failed)

0x20700001
Failed in remote execution due to insufficient memory. • Terminate any unnecessary applications.
(ProgramExec: [IP address]: <...>: Failed) • Add more memory to the personal computer.
0x20700002
Failed in remote execution due to insufficient resources.
• Check the source IP address setting.

0x20700010 • Check the version of a system application (extended
Invalid remote execution request
function) of [MES Interface].
• In [MES interface setting], set correct user name and

password for the application server setting.
• Check if the user account is invalid or not by
(ProgramExec: [IP address]: <...>: Failed) Administrative Tools of Windows.
0x20700020
Failed to log on in remote execution. • Check if the setting is forcing the user to enter
password at next logon by Administrative Tools of
Windows.
• Check if the user password is expired or not by
Administrative Tools of Windows.
No user profile for Windows has been created.

(ProgramExec: [IP address]: <...>: Failed) Confirm that the user ID set for the application server
0x20700021
Failed to load user profile during remote execution. setting of the MES interface setting can be used to log on
Windows, and reexecute.
• Check if the application to be executed in remote

execution exists or not.
(ProgramExec: [IP address]: <...>: Failed) • Check if the name of the application to be executed in
0x20700023
Failed to generate process during remote execution. remote execution is a directory.
• Make a proper security setting for the application to be
executed in remote execution.
• Set the longer time to the DB access timeout for DB

8
0x20700024 Timeout or aborted of waiting to complete remote
• Exit the application for the remote execution before
execution.
logging off.
TROUBLESHOOTING
(SID [Session ID]: TCPOpen Request Error: [IP address])
Invalid TCPOpen request

■3. SQL failure log of DB Connection Service
0x20600001 Failed in SQL execution due to insufficient memory. • Terminate any unnecessary applications.
0x20600002 Failed in SQL execution due to insufficient resources. • Add more memory to the personal computer.

DB Connection Service does not support the SQL
instruction to be executed.
0x20600021 Failed in preparation before SQL execution. • Correctly set a database type for [DB server setting], a
table name in the job for the communication action
setting, or the resource data send action setting in
Failed to obtain the number of fields in the record that is to
0x20600022 [MES Interface].
be obtained by the SQL execution.
• Correctly set a database type for [DB server setting], a

table name, field names, Select/Update conditions, and
types of the data to be stored in the fields in the job for
0x20600023 Failed in SQL execution. the communication action setting or the resource data
send action setting in [MES Interface].
• In [MES interface setting], set update conditions

correctly for the Communication action setting of the
Job settings.
0x20600025 No record was updated or inserted by the SQL execution.
• Check if the database has been filled with registered
data.
(Data source name: *** Transmitting Commit Success • Check if it is connected to the network.
0x2060002B Response Failed. ***) • Check if the gateway and/or hub is operating.
Failed to transmit the COMMIT success response. • Check if the power of the GOT has not been turned off.

9. APPENDICES
9.1 Usable Characters and ASCII Code Tables by Setting Items . . 9 - 2
APPENDICES
9.2 About Monitoring Interval Timeout . . . . . . . . . . . . . . . . . . . . . . . 9 - 5
9.3 Warning Messages in Windows Vista(R) . . . . . . . . . . . . . . . . . . 9 - 7
9.4 Tables for Used Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 - 11
9.5 Application Example of MES Interface Function . . . . . . . . . . . 9 - 12
9
9-1
9.1 Usable Characters and ASCII Code Tables by Setting
Items
9.1.1 ASCII code table
2 3 4 5 6 7
0 (SP) 0 @ P ` p
1 ! 1 A Q a q
2 [ 2 B R b r
3 # 3 C S c s
4 $ 4 D T d t
5 % 5 E U e u
6 & 6 F V f v
7 ‘ 7 G W g w
8 ( 8 H X h x
9 ) 9 I Y i y
A * : J Z j z
B + ; K [ k {
C , < L \ l |
D - = M ] m }
E . > N ^ n ~
F / ? O _ o
9.1.2 Characters applicable to item names, component names, variable names,

etc.
■1. ASCII characters
The shaded characters can be used.
(However, neither a number nor an underscore ( _ ) can be used as the first character.)
2 3 4 5 6 7
0 (SP) 0 @ P ` p
1 ! 1 A Q a q
2 [ 2 B R b r
3 # 3 C S c s
4 $ 4 D T d t
5 % 5 E U e u
6 & 6 F V f v
7 ‘ 7 G W g w
8 ( 8 H X h x
9 ) 9 I Y i y
A * : J Z j z
B + ; K [ k {
C , < L \ l |
D - = M ] m }
E . > N ^ n ~
F / ? O _ o
9-2 9.1 Usable Characters and ASCII Code Tables by Setting Items
■2. Reserved terms
The following words are reserved terms and therefore cannot be used.
Reserved terms
A abstract
B boolean, break, byte
C case, catch, char, class, cons, continue
D DATETIME, debugger, default, delete, do, double
E else, enum, event, exit, export, extends
F false, final, finally, float, for, function
G goto
I if, implements, import, in, include, Infinity, instanceof, int, interface, invoke
L long
N NaN, native, new, null
O oneshot
P package, private, protected, public
R return
S short, static, super, switch, synchronized, SYSTEM
T this, throw, throws, trace, transient, true, try, typeof
APPENDICES
U undefined
V var, void, volatile
W while, with
9.1 Usable Characters and ASCII Code Tables by Setting Items 9-3
9.1.3 Characters applicable to character string constants, etc.
2 3 4 5 6 7
0 (SP) 0 @ P ` p
1 ! 1 A Q a q
2 [ 2 B R b r
3 # 3 C S c s
4 $ 4 D T d t
5 % 5 E U e u
6 & 6 F V f v
7 ‘ 7 G W g w
8 ( 8 H X h x
9 ) 9 I Y i y
A * : J Z j z
B + ; K [ k {
C , < L \ l |
D - = M ] m }
E . > N ^ n ~
F / ? O _ o
9.1.4 Characters applicable to field names, table names, etc.

(However, a number cannot be used as the first character.)
2 3 4 5 6 7
0 (SP) 0 @ P ` p
1 ! 1 A Q a q
2 [ 2 B R b r
3 # 3 C S c s
4 $ 4 D T d t
5 % 5 E U e u
6 & 6 F V f v
7 ‘ 7 G W g w
8 ( 8 H X h x
9 ) 9 I Y i y
A * : J Z j z
B + ; K [ k {
C , < L \ l |
D - = M ] m }
E . > N ^ n ~
F / ? O _ o
9-4 9.1 Usable Characters and ASCII Code Tables by Setting Items
9.2 About Monitoring Interval Timeout
Depending on the number of set jobs or the trigger condition setting, the monitoring interval timeout may be generated in the
MES interface function.
This section explains monitoring interval timeout.
POINT
Although up to 64 jobs can be registered and trigger conditions can be set to each of them, some
adjustment in trigger condition settings is required depending on the number of the jobs.
■1. Monitoring interval timeout

The monitoring interval timeout means that the trigger detection time (the time provided for the trigger monitoring
function to determine if the trigger conditions are met) becomes longer than the time limit of trigger occurrence
(monitoring interval).
When a monitoring interval timeout occurs, the job may not be executed even though set trigger conditions are met.
Monitoring interval: 1s 10:08:30 10:08:31 10:08:32 10:08:33 10:08:34 10:08:35
Monitoring timeout
occurred
Detecting Detecting Detecting Detecting Detecting

trigger trigger trigger trigger trigger
Job Job Job Job

execution execution execution execution
■2. Causes of monitoring interval timeout
APPENDICES
A monitoring interval timeout occurs when the total jobs cannot be processed in a monitoring interval.
The monitoring interval includes the following sampling intervals.
• Sampling interval set for [Sampling setting] in [Device tag settings] when selecting [Value monitoring startup] or
[Handshake operation] for [Trigger conditions] in [Job settings]
• Sampling interval set for [Trigger conditions] when selecting [Specified time period startup] for [Trigger conditions] in
[Job settings]
9
POINT
In the following cases, monitoring interval timeouts do not occur.
• When selecting [Time specification startup] or [GOT Initializing] for [Trigger conditions] in [Job
settings]
• When the total jobs are processed in a monitoring interval
(Example 1)
When the time for trigger detection is shorter than the monitoring interval
Since processing for trigger detection is performed within each monitoring interval, no monitoring interval timeout
occurs.
Monitoring
interval
Detecting trigger
(Example 2)
When the time for trigger detection is longer than the monitoring interval
Since processing for trigger detection cannot be completed within each monitoring interval, monitoring interval timeout
occurs.
The processing for trigger detection is performed at the next timing after the monitoring interval.
Monitoring
interval
Detecting trigger
Monitoring interval
timeout occurred.
9.2 About Monitoring Interval Timeout 9-5

POINT
If the monitoring interval timeout has occurred, set a monitoring interval longer than the
processing time described in This section (4) in each of all jobs.
■3. How to check the monitoring interval timeout

The monitoring interval timeout can be checked in the Monitoring interval timeout count area (GS275).
For the Monitoring interval timeout count area, refer to the following.
➠ 3.4.2 ■1. Monitoring interval timeout count (GS275)
■4. Processing time for trigger detection

Total number of trigger conditions 100 (ms) can be assumed as a processing time for trigger detection.
Total number of trigger conditions is the total of those set for individual jobs.
Note that [Trigger 1] and [Trigger 2] are counted separately.
Also, [Handshake operation] must be counted as "2" for each.
(Example 3)
Processing time for trigger detection, which is required for [Job settings] shown below
Since the number of trigger conditions is 12, the assumed processing time for trigger detection is: 12 100 = 1200
(ms)
Setting a value of 1200ms or longer to the monitoring interval in all jobs can prevent occurrence of the monitoring
interval timeout.
Job name Trigger conditions [Trigger 1] Trigger conditions [Trigger 2]
Job 1 [Value monitoring startup] [Value monitoring startup]
Job 3 [Handshake operation] -
Job 4 [Specified time period startup] -
Job 5 [Time specification startup] -
Job 7 [Handshake operation] -
9-6 9.2 About Monitoring Interval Timeout

9.3 Warning Messages in Windows Vista(R)
9.3.1 Overview of warning messages
In Windows Vista, a User Account Control feature has been added.
When installing/uninstalling GT Works3, or starting [DB Connection Service Setting Tool], a warning message is displayed.
9.3.2 Methods for disabling warning messages
POINT
The User Account Control (UAC) is provided to protect the system from being destroyed (e.g.
prevention of start-up of a program which will execute an unintended operation).
Before taking either of the methods described below, understand that the security function
offered by UAC will be disabled and consider the risk.
The following two methods are available for preventing warning messages.
■1. Disabling the User Account Control function

The following shows a procedure for disabling the User Account Control function.
Step 1. Select [Start] - [Control Panel].
APPENDICES
9
Step 2. Select [User Accounts].
(To the next page)
9.3 Warning Messages in Windows Vista(R) 9-7

Step 3. Select [User Accounts].
Step 4. Select [Turn User Account Control on or off].

When User Account Control is enabled in
Windows Vista, the following screen
appears.Click the Continue button.
Step 5. Deselect [Turn on User Account Control

(UAC) to make your computer more secure].
(End)
9-8 9.3 Warning Messages in Windows Vista(R)

■2. Method for permitting programs without any warning message
The following shows a procedure for permitting programs without any warning message.
Step 1. Select [Start] - [Control Panel].
Step 2. Select [Classic View].
APPENDICES
9
(To the next page)
9.3 Warning Messages in Windows Vista(R) 9-9

Step 4. Select [Local Security Policy].

When User Account Control is enabled in
Windows Vista, the following screen
appears.Click the Continue button.
Step 5. Select [Local Policies].
Step 6. Select [Security Options].
(To the next page)
9 - 10 9.3 Warning Messages in Windows Vista(R)

Step 7. Select [User Account Control: Behavior of

the elevation prompt for administrators in
Admin Approval Mode, Prompt for consent].
Step 8. Select [Elevate without prompting] on the

[Local Security Setting] tab, and click the
OK button.
APPENDICES
(End)
9.4 Tables for Used Terms 9

In GT Designer3, some different terms are used for the same meaning on the MES interface function setting screen and
other setting screens.
They are listed in the tables shown below.
■1. In the case of Device tag settings

MES interface function setting Others
Signed Decimal (Data length: 16 bits)

Single word Signed BIN
Signed BIN16
Signed Decimal (Data length: 32 bits)

Double word
Signed BIN32
Real number Real
String ASCII Display
bytes Digits
■2. In the case of Job settings

MES interface function setting Others
Specified time period startup Sampling
Rise
Value monitoring startup
Fall
= ==
!=
<- =
Variable temporary works
9.4 Tables for Used Terms 9 - 11

9.5 Application Example of MES Interface Function
The following is an example of the system where the MES interface function is used.
Example) A system where manufacturing information is collected in a GOT and managed in a database
In the company-wide integrated system in which parts acceptance, manufacturing processing, assembly, shipment, and
inventory control are managed, information of the actual performance is managed in a database using the MES interface
function.
A process line control PLC handles information on process line (equipment) stop, running time, down time, quantity of
production, and the number of rejected products.
On the GOT, the status of each process line is displayed, allowing control by operators.
By the MES interface function, the termination time of the process line, regularly-checked operation rate, and fraction
defective information are managed.
The system configuration is illustrated below.
Database
<Server computer>
IP address: 192.168.11.1
Ethernet
<GOT>
IP address: 192.168.11.101
Engineering process
Process line
■1. Setup on the server computer (database)

The actual performance for every 5 seconds, and fraction defective and operation rate for every hour are managed
using the database.
(1) Table setting
• Table name: PROCESS
• Field:
Name Data type Size Scale NULL Default
DATETIME CHAR 32 Possible
PERFORMANCE NUMBER 10 0 Possible
REJECT NUMBER 10 1 Possible
WORKINGRATE NUMBER 10 1 Possible
• ODBC setting
ODBC data source name: PROCESS
Driver: OracleHome2
TNS service name: PROCESS
• DB Connection Service setting
Service port No.: 5112
Timeout: 10 seconds
9 - 12 9.5 Application Example of MES Interface Function

■2. Setup on the configuration computer (GT Designer3)
(1) IP address setting
• Communication Settings
Extend I/F-1: 1
CH No.: *
Driver: Ethernet Download
• Detailed setting
IP address: 192.168.11.101
Ethernet Download: 5014
Default Gateway: 0.0.0.0
Subnet mask: 255.255.255.0
(2) Script
No. Trigger Operation Remarks
[w:GD540]=[w:D540]; M101: Operation stop flag

1 During M101=ON [w:GD542]=[w:D542]; D540: Operation time
[b:M101]=0; D542: Accumulated down time
[w:GD544]=[w:D544];
M102: Completion notification
[w:GD546]=[w:D546];
2 When M102 rises (The GOT collects PLC information upon
[b:GB102]=[b:M102];
completion of the processing.)
[b:M102]=0;
(3) Screen design

For how to create the screens, refer to the following manual.
APPENDICES
(4) MES interface setting
• Device tag settings
Device tag name Sampling cycle Component name Data type Device
Operation time Single word GD540
Accumulated down time Single word GD542

9
Performance Single word GD544
Normal sampling 5 seconds
Rejected Single word GD546
Fraction defective Real number GD548
WorkingRate Real number GD550
Sync. trigger 5 seconds Stop flag Bit GB101
• Server service settings

Service name Type IP address/Port No.
DBServer Database server 192.168.11.1
• Job settings
Job name Trigger Processing Remarks
Startup Startup • Initializing tags
Value monitoring • Inserting the time and performance data into the Calculation of the
Status report
GB102=ON database (DBServer) operation rate
• Calculating fraction defective from the actual

• Temporary variables
performance and the number of rejected products
F_DEFECT: Fraction
Specified time period • Calculating the operation rate from the operation time
Regular report defective
1 hour and the accumulated down time
OPERAT_R: Operation
• Inserting the time, operation rate and fraction
rate
defective into the database (DBServer)
9.5 Application Example of MES Interface Function 9 - 13

■3. Operation results
The operation results (database data) of the above system are as follows:
DATETIME PERFORMANCE REJECT WORKINGRATE
2006/3/2 10:12:01 1
2006/3/2 10:24:32 2
2006/3/2 10:53:17 3
2006/3/2 11:00:00 0 87.35
2006/3/2 11:05:42 4
2006/3/2 11:17:31 5
: : : :
9 - 14 9.5 Application Example of MES Interface Function

REVISIONS
* The manual number is given on the bottom left of the back cover.
Print Date * Manual Number Revision
Jan., 2014 SH(NA)-081228ENG-A GT Works3 Version 1.108N
Apr., 2014 SH(NA)-081228ENG-B GT Works3 Version 1.111R

• GT25 is supported.
• Writing errors have been corrected.
Oct., 2014 SH(NA)-081228ENG-C GT Works3 Version 1.122C

• Compatible with Windows 8.1 and Windows Server 2012 R2
• Compatible with Oracle 12c and Access2013
Apr., 2015 SH(NA)-081228ENG-D • The following SD cards are supported.

NZ1MEM-2GBSD, NZ1MEM-4GBSD, NZ1MEM-8GBSD, NZ1MEM-16GBSD
May, 2016 SH(NA)-081228ENG-E GT Works3 Version 1.155M

• Compatible with Microsoft SQL Server 2014
Aug., 2016 SH(NA)-081228ENG-F GT Works3 Version 1.160S

• The GOT2000 series Ethernet communication unit (GT25-J71E71-100) is supported.
This manual confers no industrial property rights or any rights of any other kind, nor does it confer any patent licenses. Mitsubishi Electric
Corporation cannot be held responsible for any problems involving industrial property rights which may occur as a result of using the
contents noted in this manual.
© 2014 MITSUBISHI ELECTRIC CORPORATION
REVISIONS - 1
GOT is a registered trademark of Mitsubishi Electric Corporation.
Microsoft, Windows, Windows NT, Windows Server, Windows Vista, and Windows 7 are registered trademarks or trademarks
of Microsoft Corporation in the United States and other countries.
Adobe and Adobe Reader are registered trademarks of Adobe Systems Incorporated.
Intel, Intel Core, Pentium, and Celeron are trademarks or registered trademarks of Intel Corporation in the United States and
other countries.
Ethernet is a registered trademark of Xerox Corporation in the United States.
MODBUS is a trademark of Schneider Electric SA.
VNC is a registered trademark of RealVNC Ltd. in the United States and other countries.
Other company and product names herein are either trademarks or registered trademarks of their respective owners.
SH(NA)-081228ENG-F
GOT2000 Series MES Interface Function Manual
For GT Works3 Version1
MODEL GOT2000-O-MES-E
MODEL
CODE
When exported from Japan, this manual does not require application to the Ministry of Economy,
SH(NA)-081228ENG-F(1608)MEE Trade and Industry for service transaction permission.
HEAD OFFICE : TOKYO BUILDING, 2-7-3 MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN
NAGOYA WORKS : 1-14 , YADA-MINAMI 5-CHOME , HIGASHI-KU, NAGOYA , JAPAN
Specifications subject to change without notice. Printed in Japan, August 2016.

Got2000 o Mes e

Uploaded by

Got2000 o Mes e

Uploaded by

GRAPHIC OPERATION TERMINAL

4. SETTINGS AND PROCEDURES BEFORE USE OF THE MES INTERFACE

6. MES INTERFACE FUNCTION SETTING

7. DB CONNECTION SERVICE AND SETTING TOOL

Indicates that incorrect handling may cause hazardous conditions,

Indicates that incorrect handling may cause hazardous conditions,

■3. Relational databases that support the MES interface function

■4. Connection type used for the MES interface function

■1. List of Manuals for GT Designer3(GOT2000)

GT Works3 Version1 Installation Procedure Manual - PDF

(2) Connection manuals

GOT2000 Series Connection Manual (Non-Mitsubishi Products 1) For GT Works3

GOT2000 Series Connection Manual (Non-Mitsubishi Products 2) For GT Works3

GOT2000 Series Connection Manual (Microcomputers, MODBUS/Fieldbus Products,

(3) GT SoftGOT2000 manuals

GT SoftGOT2000 Version1 Operating Manual SH-081201ENG PDF

(4) GOT2000 manuals

■2. List of Manuals for GT Designer3(GOT1000)

GT27-X GT2715-X GT2715-XTBA, GT2715-XTBD

GT2712-S GT2712-STBA, GT2712-STWA, GT2712-STBD, GT2712-STWD

GT27 GT27-V GT2710-V GT2710-VTBA, GT2710-VTWA, GT2710-VTBD, GT2710-VTWD

GT27-S GT2708-S GT2708-STBA, GT2708-STBD

GT2708-V GT2708-VTBA, GT2708-VTBD

GT2512-S GT2512-STBA, GT2512-STBD

GT2510-V GT2510-VTBA, GT2510-VTWA, GT2510-VTBD, GT2510-VTWD

GT2508F-V GT2508F-VTNA, GT2508F-VTND

GT2310-V GT2310-VTBA, GT2310-VTBD

All GT21 models

GT SoftGOT2000 GT SoftGOT2000 Version1

GOT1000 Series GOT1000 Series -

GOT900 Series GOT-A900 Series, GOT-F900 Series -

GOT800 Series GOT-800 Series -

Abbreviations and generic terms Description

GT15-QBUS, GT15-QBUS2, GT15-ABUS, GT15-ABUS2, GT15-75QBUSL,

Serial communication unit GT15-RS2-9P, GT15-RS4-9S, GT15-RS4-TE

MELSECNET/H communication unit GT15-J71LP23-25, GT15-J71BR13

CC-Link IE Controller Network communication unit GT15-J71GP23-SX

CC-Link IE Field Network communication unit GT15-J71GF13-T2

CC-Link communication unit GT15-J61BT13

Wireless LAN communication unit GT25-WLAN

Serial multi-drop connection unit GT01-RS4-M

Connection conversion adapter GT10-9PT5S

Field network adapter unit GT25-FNADP

Ethernet communication unit GT25-J71E71-100

■3. Option unit

Abbreviations and generic terms Description

Printer unit GT15-PRN

Video input unit GT27-V4-Z (A set of GT16M-V4-Z and GT27-IF1000)

RGB input unit GT27-R2, GT27-R2-Z (A set of GT16M-R2-Z and GT27-IF1000)

RGB output unit GT27-ROUT, GT27-ROUT-Z (A set of GT16M-ROUT-Z and GT27-IF1000)

Multimedia unit GT27-MMR-Z (A set of GT16M-MMR-Z and GT27-IF1000)

Video signal conversion unit GT27-IF1000

External I/O unit GT15-DIO, GT15-DIOR

Sound output unit GT15-SOUT

SD card unit GT21-03SDCD

Abbreviations and generic terms Description

NZ1MEM-2GBSD, NZ1MEM-4GBSD, NZ1MEM-8GBSD, NZ1MEM-16GBSD,

GT27-15PSGC, GT25-12PSGC, GT25-10PSGC, GT25-08PSGC, GT25-

Environmental protection sheet GT25F-12ESGS, GT25F-10ESGS, GT25F-08ESGS

GT20-15PCO, GT20-12PCO, GT20-10PCO, GT20-08PCO, GT25-05PCO,

USB environmental protection cover GT25-UCOV, GT25-05UCOV

GT15-90STAND, GT15-80STAND, GT15-70STAND, GT15-60STAND, GT05-

GT15-70ATT-98, GT15-70ATT-87, GT15-60ATT-97, GT15-60ATT-96, GT15-

Abbreviations and generic terms Description

GT Works3 SW1DND-GTWK3-J, SW1DND-GTWK3-E, SW1DND-GTWK3-C

GT Designer3 Version1 Screen drawing software GT Designer3 for GOT2000/GOT1000 series

GT Simulator3 Screen simulator GT Simulator3 for GOT2000/GOT1000/GOT900 series

GT SoftGOT2000 Monitoring software GT SoftGOT2000 series

GT Converter2 Data conversion software GT Converter2 for GOT1000/GOT900 series

GT Designer2 Screen drawing software GT Designer2 for GOT1000/GOT900 series

DU/WIN Screen drawing software FX-PCS-DU/WIN for GOT-F900 series

(2) Software related to iQ Works

Abbreviations and generic terms Description

Abbreviation of iQ Platform compatible engineering environment MELSOFT

Generic term for integrated development environment software included in the

SW□DND-IQAPL-M type integrated application management software