caution
Series
Connection Manual
(Microcomputer, MODBUS Products, Peripherals) for GT Works3
MICROCOMPUTER CONNECTION
MODBUS/RTU CONNECTION
MODBUS/TCP CONNECTION
CONNECTION TO SOUND OUTPUT UNIT
CONNECTION TO EXTERNAL I/O DEVICE
FINGERPRINT AUTHENTICATION DEVICE CONNECTION
BAR CODE READER CONNECTION
REMOTE PERSONAL COMPUTER OPERATION CONNECTION
VNC(R) SERVER CONNECTION
VIDEO/RGB CONNECTION
PRINTER CONNECTION
MULTIMEDIA CONNECTION
RFID CONNECTION
SAFETY PRECAUTIONS
(Always read these precautions before using this equipment.)
Before using this product, please read this manual and the relevant manuals introduced in this manual
carefully and pay full attention to safety to handle the product correctly.
The precautions given in this manual are concerned with this product.
In this manual, the safety precautions are ranked as "DANGER" and "CAUTION".
DANGER
Indicates that incorrect handling may cause hazardous conditions,
resulting in death or severe injury.
CAUTION
Indicates that incorrect handling may cause hazardous conditions,
resulting in medium or slight personal injury or physical damage.
Note that the
caution level may lead to a serious accident according to the circumstances.
Always follow the instructions of both levels because they are important to personal safety.
Please save this manual to make it accessible when required and always forward it to the end user.
[DESIGN PRECAUTIONS]
DANGER
● Some failures of the GOT, communication unit or cable may keep the outputs on or off.
An external monitoring circuit should be provided to check for output signals which may lead to a
serious accident.
Not doing so can cause an accident due to false output or malfunction.
● If a communication fault (including cable disconnection) occurs during monitoring on the GOT,
communication between the GOT and PLC CPU is suspended and the GOT becomes inoperative.
For bus connection
: The CPU becomes faulty and the GOT becomes inoperative.
For other than bus connection : The GOT becomes inoperative.
A system where the GOT is used should be configured to perform any significant operation to the
system by using the switches of a device other than the GOT on the assumption that a GOT
communication fault will occur.
Not doing so can cause an accident due to false output or malfunction.
● Do not use the GOT as the warning device that may cause a serious accident.
An independent and redundant hardware or mechanical interlock is required to configure the device
that displays and outputs serious warning.
Failure to observe this instruction may result in an accident due to incorrect output or malfunction.
A-1
[DESIGN PRECAUTIONS]
DANGER
● Incorrect operation of the touch switch(s) may lead to a serious accident if the GOT backlight is gone
out.
When the GOT backlight goes out, although the POWER LED blinks (green/orange) and the display
section dims, the input of the touch switch(s) remains active.
This may confuse an operator in thinking that the GOT is in "screensaver" mode, who then tries to
release the GOT from this mode by touching the display section, which may cause a touch switch to
operate.
Note that the following occurs on the GOT when the backlight goes out.
• GT1655-V: The POWER LED blinks (green/orange) and the monitor screen appears blank.
• Models other than GT1655-V: The POWER LED blinks (green/orange) and the monitor screen
appears dimmed.
● The display section of the GT16, GT1595-X, GT14, GT12 or GT1020 are an analog-resistive type
touch panel.
If you touch the display section simultaneously in 2 points or more, the switch that is located around
the center of the touched point, if any, may operate.
Do not touch the display section in 2 points or more simultaneously.
Doing so may cause an accident due to incorrect output or malfunction.
● When programs or parameters of the controller (such as a PLC) that is monitored by the GOT are
changed, be sure to reset the GOT or shut off the power of the GOT at the same time.
Not doing so can cause an accident due to false output or malfunction.
CAUTION
● Do not bundle the control and communication cables with main-circuit, power or other wiring.
Run the above cables separately from such wiring and keep them a minimum of 100mm apart.
Not doing so noise can cause a malfunction.
● Do not press the GOT display section with a pointed material as a pen or driver.
Doing so can result in a damage or failure of the display section.
● When the GOT is connected to the Ethernet network, the available IP address is restricted according
to the system configuration.
• When multiple GOTs are connected to the Ethernet network:
Do not set the IP address (192.168.0.18) for the GOTs and the controllers in the network.
• When a single GOT is connected to the Ethernet network:
Do not set the IP address (192.168.0.18) for the controllers except the GOT in the network.
Doing so can cause the IP address duplication. The duplication can negatively affect the
communication of the device with the IP address (192.168.0.18).
The operation at the IP address duplication depends on the devices and the system.
● Turn on the controllers and the network devices to be ready for communication before they
communicate with the GOT.
Failure to do so can cause a communication error on the GOT.
A-2
[MOUNTING PRECAUTIONS]
DANGER
● Be sure to shut off all phases of the external power supply used by the system before mounting or
removing the GOT to/from the panel.
Not switching the power off in all phases can cause a unit failure or malfunction.
● Be sure to shut off all phases of the external power supply used by the system before mounting or
removing the communication unit, option function board or multi-color display board onto/from the
GOT.
Not doing so can cause the unit to fail or malfunction.
● Before mounting an optional function board or Multi-color display board, wear a static discharge wrist
strap to prevent the board from being damaged by static electricity.
CAUTION
● Use the GOT in the environment that satisfies the general specifications described in the User's
Manual.
Not doing so can cause an electric shock, fire, malfunction or product damage or deterioration.
● When mounting the GOT to the control panel, tighten the mounting screws in the specified torque
range.
Undertightening can cause the GOT to drop, short circuit or malfunction.
Overtightening can cause a drop, short circuit or malfunction due to the damage of the screws or the
GOT.
● When loading the communication unit or option unit to the GOT (GT16, GT15), fit it to the extension
interface of the GOT and tighten the mounting screws in the specified torque range.
Undertightening can cause the GOT to drop, short circuit or malfunction.
Overtightening can cause a drop, failure or malfunction due to the damage of the screws or unit.
● When mounting the multi-color display board onto the GOT (GT15), connect it to the corresponding
connector securely and tighten the mounting screws within the specified torque range.
Loose tightening may cause the unit and/or GOT to malfunction due to poor contact.
Overtightening may damage the screws, unit and/or GOT; they might malfunction.
● When mounting the option function board onto the GOT (GT16), connect it to the corresponding
connector securely and tighten the mounting screws within the specified torque range.
● When mounting an optional function board onto the GOT(GT15), fully connect it to the connector
until you hear a click.
● When mounting an optional function board onto the GOT(GT11), fully connect it to the connector.
● When inserting a CF card into the GOT(GT16, GT15, GT11), push it into the CF card interface of
GOT until the CF card eject button will pop out.
Failure to do so may cause a malfunction due to poor contact.
● When inserting/removing a SD card into/from the GOT(GT14), turn the SD card access switch off in
advance.
Failure to do so may corrupt data within the SD card.
A-3
[MOUNTING PRECAUTIONS]
CAUTION
● When inserting/removing a CF card into/from the GOT(GT16, GT15, GT11), turn the CF card access
switch off in advance.
Failure to do so may corrupt data within the CF card.
● When removing a SD card from the GOT(GT14), make sure to support the SD card by hand, as it may
pop out.
Failure to do so may cause the SD card to drop from the GOT and break.
● When removing a CF card from the GOT, make sure to support the CF card by hand, as it may pop out.
Failure to do so may cause the CF card to drop from the GOT and break.
● When installing a USB memory to the GOT(GT16, GT14), make sure to install the USB memory to
the USB interface firmly.
Failure to do so may cause a malfunction due to poor contact.
● Before removing the USB memory from the GOT(GT16, GT14), operate the utility screen for removal.
After the successful completion dialog box is displayed, remove the memory by hand carefully.
Failure to do so may cause the USB memory to drop, resulting in a damage or failure of the memory.
● For closing the USB environmental protection cover, fix the cover by pushing the
firmly to comply with the protective structure.
mark on the latch
● Remove the protective film of the GOT.
When the user continues using the GOT with the protective film, the film may not be removed.
● Operate and store the GOT in environments without direct sunlight, high temperature, dust, humidity,
and vibrations.
● When using the GOT in the environment of oil or chemicals, use the protective cover for oil.
Failure to do so may cause failure or malfunction due to the oil or chemical entering into the GOT.
[WIRING PRECAUTIONS]
DANGER
● Be sure to shut off all phases of the external power supply used by the system before wiring.
Failure to do so may result in an electric shock, product damage or malfunctions.
CAUTION
● Please make sure to ground FG terminal and LG terminal and protective ground terminal of the GOT
power supply section by applying Class D Grounding (Class 3 Grounding Method) or higher which is
used exclusively for the GOT.
Not doing so may cause an electric shock or malfunction.
● Be sure to tighten any unused terminal screws with a torque of 0.5 to 0.8N•m.
Failure to do so may cause a short circuit due to contact with a solderless terminal.
● Use applicable solderless terminals and tighten them with the specified torque.
If any solderless spade terminal is used, it may be disconnected when the terminal screw comes
loose, resulting in failure.
A-4
[WIRING PRECAUTIONS]
CAUTION
● Correctly wire the GOT power supply section after confirming the rated voltage and terminal
arrangement of the product.
Not doing so can cause a fire or failure.
● Tighten the terminal screws of the GOT power supply section in the specified torque range.
Undertightening can cause a short circuit or malfunction.
Overtightening can cause a short circuit or malfunction due to the damage of the screws or the GOT.
● Exercise care to avoid foreign matter such as chips and wire offcuts entering the GOT.
Not doing so can cause a fire, failure or malfunction.
● The module has an ingress prevention label on its top to prevent foreign matter, such as wire offcuts,
from entering the module during wiring.
Do not peel this label during wiring.
Before starting system operation, be sure to peel this label because of heat dissipation.
● Plug the bus connection cable by inserting it into the connector of the connected unit until it "clicks".
After plugging, check that it has been inserted snugly.
Not doing so can cause a malfunction due to a contact fault.
● Plug the communication cable into the connector of the connected unit and tighten the mounting and
terminal screws in the specified torque range.
Undertightening can cause a short circuit or malfunction.
Overtightening can cause a short circuit or malfunction due to the damage of the screws or unit.
● Plug the QnA/ACPU/Motion controller (A series) bus connection cable by inserting it into the
connector of the connected unit until it "clicks".
After plugging, check that it has been inserted snugly.
Not doing so can cause a malfunction due to a contact fault.
[TEST OPERATION PRECAUTIONS]
DANGER
● Before performing the test operations of the user creation monitor screen (such as turning ON or
OFF bit device, changing the word device current value, changing the settings or current values of
the timer or counter, and changing the buffer memory current value), read through the manual
carefully and make yourself familiar with the operation method.
During test operation, never change the data of the devices which are used to perform significant
operation for the system.
False output or malfunction can cause an accident.
A-5
[STARTUP/MAINTENANCE PRECAUTIONS]
DANGER
● When power is on, do not touch the terminals.
Doing so can cause an electric shock or malfunction.
● Correctly connect the battery connector.
Do not charge, disassemble, heat, short-circuit, solder, or throw the battery into the fire.
Doing so will cause the battery to produce heat, explode, or ignite, resulting in injury and fire.
● Before starting cleaning or terminal screw retightening, always switch off the power externally in all
phases.
Not switching the power off in all phases can cause a unit failure or malfunction.
Undertightening can cause a short circuit or malfunction.
Overtightening can cause a short circuit or malfunction due to the damage of the screws or unit.
CAUTION
● Do not disassemble or modify the unit.
Doing so can cause a failure, malfunction, injury or fire.
● Do not touch the conductive and electronic parts of the unit directly.
Doing so can cause a unit malfunction or failure.
● The cables connected to the unit must be run in ducts or clamped.
Not doing so can cause the unit or cable to be damaged due to the dangling, motion or accidental
pulling of the cables or can cause a malfunction due to a cable connection fault.
● When unplugging the cable connected to the unit, do not hold and pull the cable portion.
Doing so can cause the unit or cable to be damaged or can cause a malfunction due to a cable
connection fault.
● Do not drop or apply strong impact to the unit.
Doing so may damage the unit.
● Do not drop or give an impact to the battery mounted to the unit.
Doing so may damage the battery, causing the battery fluid to leak inside the battery.
If the battery is dropped or given an impact, dispose of it without using.
● Before touching the unit, always touch grounded metal, etc. to discharge static electricity from
human body, etc.
Not doing so can cause the unit to fail or malfunction.
● Replace battery with GT15-BAT(GT16, GT15) or GT11-50BAT(GT14, GT12, GT11, GT10) by
Mitsubishi electric Co. only.
Use of another battery may present a risk of fire or explosion.
● Dispose of used battery promptly.
Keep away from children. Do not disassemble and do not dispose of in fire.
A-6
[TOUCH PANEL PRECAUTIONS]
CAUTION
● For the analog-resistive film type touch panels, normally the adjustment is not required. However,
the difference between a touched position and the object position may occur as the period of use
elapses. When any difference between a touched position and the object position occurs, execute
the touch panel calibration.
● When any difference between a touched position and the object position occurs, other object may be
activated. This may cause an unexpected operation due to incorrect output or malfunction.
[BACKLIGHT REPLACEMENT PRECAUTIONS]
DANGER
● Be sure to shut off all phases of the external power supply of the GOT (and the PLC CPU in the case
of a bus topology) and remove the GOT from the control panel before replacing the backlight (when
using the GOT with the backlight replaceable by the user).
Not doing so can cause an electric shock.
Replacing a backlight without removing the GOT from the control panel can cause the backlight or
control panel to drop, resulting in an injury.
CAUTION
● Wear gloves for the backlight replacement when using the GOT with the backlight replaceable by the
user.
Not doing so can cause an injury.
● Before replacing a backlight, allow 5 minutes or more after turning off the GOT when using the GOT
with the backlight replaceable by the user.
Not doing so can cause a burn from heat of the backlight.
[DISPOSAL PRECAUTIONS]
CAUTION
● When disposing of the product, handle it as industrial waste.
● When disposing of this product, treat it as industrial waste. When disposing of batteries, separate
them from other wastes according to the local regulations.
(For details of the battery directive in EU member states, refer to the User's Manual of the GOT to be
used.)
A-7
[TRANSPORTATION PRECAUTIONS]
CAUTION
● When transporting lithium batteries, make sure to treat them based on the transport regulations.
(For details on models subject to restrictions, refer to the User's Manual for the GOT you are using.)
● Make sure to transport the GOT main unit and/or relevant unit(s) in the manner they will not be
exposed to the impact exceeding the impact resistance described in the general specifications of the
User's Manual, as they are precision devices.
Failure to do so may cause the unit to fail.
Check if the unit operates correctly after transportation.
A-8
INTRODUCTION
Thank you for choosing Mitsubishi Graphic Operation Terminal (Mitsubishi GOT).
Read this manual and make sure you understand the functions and performance of the GOT thoroughly
in advance to ensure correct use.
CONTENTS
SAFETY PRECAUTIONS .........................................................................................................................A - 1
INTRODUCTION ......................................................................................................................................A - 9
CONTENTS ..............................................................................................................................................A - 9
MANUALS............................................................................................................................................... A - 15
QUICK REFERENCE ............................................................................................................................. A - 16
ABBREVIATIONS AND GENERIC TERMS ...........................................................................................A - 18
HOW TO READ THIS MANUAL ............................................................................................................. A - 23
1.PREPARATORY PROCEDURES FOR MONITORING
1.1
Setting the Communication Interface............................................................................................... 1 - 3
1.1.1 Setting connected equipment (Channel setting)................................................................... 1 - 3
1.1.2 I/F communication setting................................................................................................... 1 - 10
1.1.3 Precautions......................................................................................................................... 1 - 12
1.2
Writing the Project Data and OS onto the GOT............................................................................. 1 - 13
1.2.1 Writing the project data and OS onto the GOT................................................................... 1 - 13
1.2.2 Checking the project data and OS writing on GOT ............................................................ 1 - 14
1.3
Option Devices for the Respective Connection ............................................................................. 1 - 15
1.3.1 Communication module ...................................................................................................... 1 - 15
1.3.2 Option unit .......................................................................................................................... 1 - 16
1.3.3 Conversion cable ................................................................................................................ 1 - 16
1.3.4 Connector conversion adapter ........................................................................................... 1 - 16
1.3.5 Serial Multi-Drop Connection Unit ...................................................................................... 1 - 16
1.3.6 RS-232/485 signal conversion adapter .............................................................................. 1 - 16
1.3.7 Installing a unit on another unit (Checking the unit installation position) ............................ 1 - 17
1.4
Connection Cables for the Respective Connection ....................................................................... 1 - 24
1.4.1 GOT connector specifications ............................................................................................ 1 - 24
1.4.2 Coaxial cable connector connection method ...................................................................... 1 - 27
1.4.3 Terminating resistors of GOT ............................................................................................. 1 - 28
1.4.4 Setting the RS-232/485 signal conversion adaptor ............................................................ 1 - 31
1.5
Verifying GOT Recognizes Connected Equipment........................................................................ 1 - 32
1.6
Checking for Normal Monitoring .................................................................................................... 1 - 36
1.6.1 Check on the GOT.............................................................................................................. 1 - 36
1.6.2 Confirming the communication state on the GOT side (For Ethernet connection) ............. 1 - 38
1.6.3 Confirming the communication state with each station (station monitoring function) ......... 1 - 40
1.6.4
Check on the PLC ............................................................................................................. 1 - 43
A-9
MICROCOMPUTER CONNECTION
2.MICROCOMPUTER CONNECTION (SERIAL)
2.1
Microcomputer Connection (Serial) ................................................................................................. 2 - 2
2.2
System Configuration ...................................................................................................................... 2 - 4
2.2.1 For the microcomputer connection (serial) ........................................................................... 2 - 4
2.3
Connection Diagram ........................................................................................................................ 2 - 6
2.3.1 RS-232 cable ........................................................................................................................ 2 - 6
2.3.2 RS-422 cable ........................................................................................................................ 2 - 8
2.4
Device Data Area........................................................................................................................... 2 - 10
2.4.1 D devices ............................................................................................................................ 2 - 11
2.4.2 R devices ............................................................................................................................ 2 - 15
2.4.3 L devices............................................................................................................................. 2 - 16
2.4.4 M devices............................................................................................................................ 2 - 17
2.4.5 SD devices.......................................................................................................................... 2 - 18
2.4.6 SM devices ......................................................................................................................... 2 - 21
2.5
Message Formats .......................................................................................................................... 2 - 23
2.5.1 Data format type and application ........................................................................................ 2 - 23
2.5.2 List of commands................................................................................................................ 2 - 25
2.5.3 Formats 1, 2 (GOT-A900 Series microcomputer connection) ............................................ 2 - 28
2.5.4 Formats 3 to 6 (A compatible 1C frame)............................................................................. 2 - 41
2.5.5 Formats 7 to 10 (QnA compatible 3C/4C frame) ................................................................ 2 - 46
2.5.6 Formats 11 to 13 (Digital Electronics Corporation's memory link method) ......................... 2 - 54
2.5.7 Formats 14, 15 (GOT-F900 Series microcomputer connection)......................................... 2 - 63
2.6
GOT Side Settings ......................................................................................................................... 2 - 77
2.6.1 Setting communication interface (Communication settings)............................................... 2 - 77
2.6.2 Communication detail settings............................................................................................ 2 - 78
2.7
System Configuration Examples.................................................................................................... 2 - 79
2.8
Device Range that Can Be Set ...................................................................................................... 2 - 82
2.9
Precautions .................................................................................................................................... 2 - 83
3.MICROCOMPUTER CONNECTION (ETHERNET)
3.1
Microcomputer connection (Ethernet).............................................................................................. 3 - 2
3.2
System Configuration ...................................................................................................................... 3 - 2
3.2.1 For the microcomputer connection (Ethernet) ...................................................................... 3 - 2
3.3
Device Data Area............................................................................................................................. 3 - 3
3.3.1 D devices .............................................................................................................................. 3 - 4
3.3.2 R devices .............................................................................................................................. 3 - 8
3.3.3 L devices............................................................................................................................... 3 - 9
3.3.4 M devices............................................................................................................................ 3 - 10
3.3.5 SD devices.......................................................................................................................... 3 - 11
3.3.6 SM devices ......................................................................................................................... 3 - 14
3.4
Message Formats .......................................................................................................................... 3 - 16
3.4.1 Data format type and application ........................................................................................ 3 - 16
3.4.2 List of commands................................................................................................................ 3 - 17
3.4.3 Formats 1, 2 (GOT-A900 Series microcomputer connection) ............................................ 3 - 19
3.4.4 Formats 3, 4 (GOT-F900 series microcomputer connection) ............................................. 3 - 31
3.4.5 Formats 5(Digital Electronics Corporation's memory link method) ..................................... 3 - 45
A - 10
3.4.6
3.4.7
Formats 6, 7 (4E frame) ..................................................................................................... 3 - 50
Formats 8, 9 (QnA compatible 3E frame) ........................................................................... 3 - 60
3.5
GOT Side Settings......................................................................................................................... 3 - 69
3.5.1 Setting communication interface (Communication settings)............................................... 3 - 69
3.5.2 Communication detail settings............................................................................................ 3 - 69
3.6
System Configuration Examples.................................................................................................... 3 - 72
3.7
Device Range that Can Be Set...................................................................................................... 3 - 73
3.8
Precautions.................................................................................................................................... 3 - 74
MODBUS CONNECTIONS
4.MODBUS(R)/RTU CONNECTION
4.1
Connectable Model List ................................................................................................................... 4 - 2
4.2
System Configuration ...................................................................................................................... 4 - 3
4.2.1 Connecting to MODBUS(R)/RTU equipment ....................................................................... 4 - 3
4.3
Connection Diagram ........................................................................................................................ 4 - 4
4.3.1 RS-232 cable ........................................................................................................................ 4 - 4
4.3.2 RS-422/485 cable ................................................................................................................. 4 - 5
4.4
GOT Side Settings......................................................................................................................... 4 - 12
4.4.1 Setting communication interface (Communication settings)............................................... 4 - 12
4.4.2 Communication detail settings............................................................................................ 4 - 12
4.5
MODBUS(R)/RTU Equipment Side Setting ................................................................................... 4 - 14
4.5.1 Communication settings ..................................................................................................... 4 - 14
4.5.2 Station number setting........................................................................................................ 4 - 17
4.6
Precautions.................................................................................................................................... 4 - 17
5.MODBUS(R)/TCP CONNECTION
5.1
Connectable Model List ................................................................................................................... 5 - 2
5.2
System Configuration ...................................................................................................................... 5 - 2
5.2.1 Connecting to MODBUS(R)/TCP equipment........................................................................ 5 - 2
5.3
GOT Side Settings........................................................................................................................... 5 - 3
5.3.1 Setting communication interface (Communication settings)................................................. 5 - 3
5.3.2 Communication detail settings.............................................................................................. 5 - 3
5.3.3 Ethernet setting .................................................................................................................... 5 - 5
5.4
MODBUS(R)/TCP Equipment Setting ............................................................................................. 5 - 6
5.5
Device Range that Can Be Set........................................................................................................ 5 - 6
5.6
Example of Connection.................................................................................................................. 5 - 10
5.6.1 Connecting to SCHNEIDER PLC
(Modicon Premium series and Modicon Quantum series).................................................. 5 - 10
5.6.2 Connecting to YOKOGAWA PLC (STARDOM).................................................................. 5 - 12
5.7
Precautions.................................................................................................................................... 5 - 15
CONNECTIONS TO PERIPHERAL EQUIPMENT
6.CONNECTION TO SOUND OUTPUT UNIT
6.1
Connectable Model List ................................................................................................................... 6 - 2
6.2
System Configuration ...................................................................................................................... 6 - 2
A - 11
6.2.1
Connecting to sound output unit ........................................................................................... 6 - 2
6.3
GOT Side Settings ........................................................................................................................... 6 - 3
6.3.1 Setting communication interface........................................................................................... 6 - 3
6.4
Precautions ...................................................................................................................................... 6 - 4
7.CONNECTION TO EXTERNAL I/O DEVICE
7.1
Connectable Model List ................................................................................................................... 7 - 2
7.2
System Configuration ...................................................................................................................... 7 - 2
7.2.1 Connecting to the external I/O device................................................................................... 7 - 2
7.3
Connection Diagram ........................................................................................................................ 7 - 4
7.3.1 Connection cable between external I/O unit and operation panel ........................................ 7 - 4
7.3.2 Connection cable between external I/O unit and connector/terminal block converter
module .................................................................................................................................. 7 - 6
7.3.3 Connection diagram between connector/terminal block converter module and user-created
original operation panel ........................................................................................................ 7 - 8
7.4
GOT Side Settings ......................................................................................................................... 7 - 12
7.4.1 Setting communication interface......................................................................................... 7 - 12
7.5
Precautions .................................................................................................................................... 7 - 13
8.FINGERPRINT AUTHENTICATION DEVICE CONNECTION
8.1
Connectable Model List ................................................................................................................... 8 - 2
8.2
System Configuration ...................................................................................................................... 8 - 2
8.2.1 Connecting to fingerprint authentication device.................................................................... 8 - 2
8.3
GOT Side Settings ........................................................................................................................... 8 - 3
8.3.1 Setting communication interface........................................................................................... 8 - 3
8.4
Precautions ...................................................................................................................................... 8 - 4
9.BAR CODE READER CONNECTION
9.1
Connectable Model List ................................................................................................................... 9 - 2
9.2
System Configuration ...................................................................................................................... 9 - 2
9.2.1 Connecting to bar code reader ............................................................................................. 9 - 2
9.3
GOT Side Settings ........................................................................................................................... 9 - 3
9.3.1 Setting communication interface........................................................................................... 9 - 3
9.3.2 Communication detail settings.............................................................................................. 9 - 4
9.4
System Configuration Examples...................................................................................................... 9 - 5
9.5
Precautions ...................................................................................................................................... 9 - 7
10.PC REMOTE CONNECTION
10.1
Connectable Model List ................................................................................................................. 10 - 2
10.2
Serial Connection .......................................................................................................................... 10 - 2
10.2.1 System Configuration ......................................................................................................... 10 - 2
10.2.2 Connection Diagram ........................................................................................................... 10 - 3
10.2.3 GOT Side Settings.............................................................................................................. 10 - 4
10.2.4 Communication detail settings............................................................................................ 10 - 5
10.2.5 Installing and setting up computer remote operation driver................................................ 10 - 6
10.2.6 Precautions......................................................................................................................... 10 - 6
A - 12
10.3
Ethernet Connection ...................................................................................................................... 10 - 7
10.3.1 System Configuration ......................................................................................................... 10 - 7
10.3.2 GOT Side Settings.............................................................................................................. 10 - 8
10.3.3 Install and setting the required software ............................................................................. 10 - 8
10.3.4 Precautions......................................................................................................................... 10 - 8
11.VNC(R) SERVER CONNECTION
11.1
Connectable Model List ................................................................................................................. 11 - 2
11.2
System Configuration .................................................................................................................... 11 - 2
11.3
GOT Side Settings......................................................................................................................... 11 - 3
11.3.1 VNC(R) server function setting ........................................................................................... 11 - 3
11.3.2 Setting communication interface (Communication settings)............................................... 11 - 3
11.4
Setting in Personal Computer........................................................................................................ 11 - 4
12.VIDEO/RGB CONNECTION
12.1
Connectable Model List ................................................................................................................. 12 - 2
12.2
System Configuration .................................................................................................................... 12 - 3
12.2.1 Displaying video image on GOT ......................................................................................... 12 - 3
12.2.2 Displaying GOT screen on external monitor....................................................................... 12 - 4
12.3
Connection Diagram ...................................................................................................................... 12 - 5
12.3.1 Coaxial cable ...................................................................................................................... 12 - 5
12.3.2 Analog RGB cable .............................................................................................................. 12 - 5
12.4
GOT Side Settings......................................................................................................................... 12 - 7
12.4.1 Setting communication interface ........................................................................................ 12 - 7
12.4.2 Communication detail settings............................................................................................ 12 - 8
12.4.3 Setting the video/RGB function .......................................................................................... 12 - 8
12.5
Precautions.................................................................................................................................... 12 - 8
13.PRINTER CONNECTION
13.1
Connectable Model List ................................................................................................................. 13 - 2
13.2
System Configuration .................................................................................................................... 13 - 2
13.2.1 Connecting to PictBridge compatible printer ...................................................................... 13 - 2
13.2.2 Connecting to serial printer................................................................................................. 13 - 3
13.3
GOT Side Settings......................................................................................................................... 13 - 4
13.3.1 Setting communication interface ........................................................................................ 13 - 4
13.3.2 Communication detail settings............................................................................................ 13 - 5
13.4
Precautions.................................................................................................................................... 13 - 6
14.MULTIMEDIA CONNECTION
14.1
Connectable Model List ................................................................................................................. 14 - 2
14.2
System Configuration .................................................................................................................... 14 - 2
14.2.1 Saving video image and displaying it on GOT.................................................................... 14 - 2
14.2.2 Sending video image to personal computer ....................................................................... 14 - 3
14.3
Connection Diagram ...................................................................................................................... 14 - 4
14.3.1 Coaxial cable ...................................................................................................................... 14 - 4
14.4
GOT Side Settings......................................................................................................................... 14 - 5
14.4.1 Setting communication interface ........................................................................................ 14 - 5
14.4.2 Communication detail settings............................................................................................ 14 - 6
A - 13
14.4.3
14.4.4
14.4.5
14.5
Installing and setting multimedia interaction tool onto personal computer ......................... 14 - 6
Setting the multimedia function........................................................................................... 14 - 6
Set the gateway function .................................................................................................... 14 - 6
Precautions .................................................................................................................................... 14 - 7
15.RFID CONNECTION
15.1
Connectable Model List ................................................................................................................. 15 - 2
15.2
System Configuration .................................................................................................................... 15 - 2
15.2.1 Connecting to RFID ............................................................................................................ 15 - 2
15.3
GOT Side Settings ......................................................................................................................... 15 - 3
15.3.1 Setting communication interface......................................................................................... 15 - 3
15.3.2 Communication detail settings............................................................................................ 15 - 4
15.4
Precautions .................................................................................................................................... 15 - 5
INDEX
REVISIONS
A - 14
MANUALS
The following table lists the manual relevant to this product.
Refer to each manual for any purpose.
Packaging
Manual Number
(Model code)
GT Works3 Version1 Installation Procedure Manual
Enclosed in product
-
GT Designer3 Version1 Screen Design Manual (Fundamentals)1/2, 2/2
Stored in CD-ROM
SH-080866ENG
(1D7MB9)
GT Designer3 Version1 Screen Design Manual (Functions) 1/2, 2/2
Stored in CD-ROM
SH-080867ENG
(1D7MC1)
GOT1000 Series Connection Manual (Mitsubishi Products) for GT Works3
Stored in CD-ROM
SH-080868ENG
(1D7MC2)
GOT1000 Series Connection Manual (Non-Mitsubishi Products 1) for GT Works3
Stored in CD-ROM
SH-080869ENG
(1D7MC3)
GOT1000 Series Connection Manual (Non-Mitsubishi Products 2) for GT Works3
Stored in CD-ROM
SH-080870ENG
(1D7MC4)
GOT1000 Series Connection Manual (Microcomputer, MODBUS Products, Peripherals) for GT
Works3
Stored in CD-ROM
SH-080871ENG
(1D7MC5)
GOT1000 Series Gateway Functions Manual for GT Works3
Stored in CD-ROM
SH-080858ENG
(1D7MA7)
GOT1000 Series MES Interface Function Manual for GT Works3
Stored in CD-ROM
SH-080859ENG
(1D7MA8)
GT SoftGOT1000 Version3 Operating Manual for GT Works3
Stored in CD-ROM
SH-080860ENG
(1D7MA9)
GT Simulator3 Version1 Operating Manual for GT Works3
Stored in CD-ROM
SH-080861ENG
(1D7MB1)
GT Converter2 Version3 Operating Manual for GT Works3
Stored in CD-ROM
SH-080862ENG
(1D7MB2)
GOT1000 Series User's Manual (Extended Functions, Option Functions) for GT Works3
Stored in CD-ROM
SH-080863ENG
(1D7MB3)
GT16 User's Manual (Hardware)
Stored in CD-ROM
SH-080928ENG
(1D7MD3)
GT16 User's Manual (Basic Utility)
Stored in CD-ROM
SH-080929ENG
(1D7MD4)
GT16 Handy GOT User's Manual
Stored in CD-ROM
JY997D41201
JY997D41202
(09R821)
GT15 User's Manual
Stored in CD-ROM
SH-080528ENG
(1D7M23)
GT14 User's Manual
Stored in CD-ROM
JY997D44801
(09R823)
GT12 User’s Manual
Stored in CD-ROM
SH-080977ENG
(1D7ME1)
GT11 User's Manual
Stored in CD-ROM
JY997D17501
(09R815)
GT11 Handy GOT User's Manual
Stored in CD-ROM
JY997D20101
JY997D20102
(09R817)
GT10 User's Manual
Stored in CD-ROM
JY997D24701
(09R819)
Manual Name
A - 15
QUICK REFERENCE
 Creating a project
Obtaining the specifications and operation methods of GT Designer3
Setting available functions on GT Designer3
Creating a screen displayed on the GOT
GT Designer3 Version1 Screen Design Manual
(Fundamentals)1/2, 2/2
Obtaining useful functions to increase efficiency of drawing
Setting details for figures and objects
Setting functions for the data collection or trigger action
GT Designer3 Version1 Screen Design Manual (Functions)
1/2, 2/2
Setting functions to use peripheral devices
Simulating a created project on a personal computer
GT Simulator3 Version1 Operating Manual for GT Works3
 Connecting a controller to the GOT
Obtaining information of Mitsubishi products applicable to the GOT
Connecting Mitsubishi products to the GOT
GOT1000 Series Connection Manual (Mitsubishi Products) for
Connecting multiple controllersto one GOT (Multi-channel function)
GT Works3
Establishing communication between a personal computer and a
controller via the GOT (FA transparent function)
Obtaining information of Non-Mitsubishi products applicable to the GOT
• GOT1000 Series Connection Manual (Non-Mitsubishi
Products 1) for GT Works3
Connecting Non-Mitsubishi products to the GOT
Obtaining information of peripheral devices applicable to the GOT
Connecting peripheral devices including a barcode reader to the GOT
• GOT1000 Series Connection Manual (Non-Mitsubishi
Products 2) for GT Works3
GOT1000 Series Connection Manual (Microcomputer,
MODBUS Products, Peripherals) for GT Works3
 Transferring data to the GOT
Writing data to the GOT
Reading data from the GOT
Verifying a editing project to a GOT project
A - 16
GT Designer3 Version1 Screen Design Manual
(Fundamentals)1/2, 2/2
 Others
Obtaining specifications (including part names, external dimensions, and
• GT16 User's Manual (Hardware)
options) of each GOT
• GT16 User's Manual (Basic Utility)
• GT16 Handy GOT User's Manual
Installing the GOT
• GT15 User’s Manual
• GT14 User's Manual
• GT12 User’s Manual
Operating the utility
• GT11 User's Manual
• GT11 Handy GOT User's Manual
• GT10 User's Manual
Configuring the gateway function
Configuring the MES interface function
Configuring the extended function and option function
Using a personal computer as the GOT
GOT1000 Series Gateway Functions Manual for GT Works3
GOT1000 Series MES Interface Function Manual for GT
Works3
GOT1000 Series User's Manual (Extended Functions, Option
Functions) for GT Works3
GT SoftGOT1000 Version3 Operating Manual for GT Works3
A - 17
ABBREVIATIONS AND GENERIC TERMS
 GOT
Abbreviations and generic terms
GT1695M-X
Abbreviation of GT1695M-XTBA, GT1695M-XTBD
GT1685
GT1685M-S
Abbreviation of GT1685M-STBA, GT1685M-STBD
GT1675M-S
Abbreviation of GT1675M-STBA, GT1675M-STBD
GT1675
GT1675M-V
Abbreviation of GT1675M-VTBA, GT1675M-VTBD
GT1675-VN
Abbreviation of GT1675-VNBA, GT1675-VNBD
GT1672-VN
Abbreviation of GT1672-VNBA, GT1672-VNBD
GT1665M-S
Abbreviation of GT1665M-STBA, GT1665M-STBD
GT1665M-V
Abbreviation of GT1665M-VTBA, GT1665M-VTBD
GT1662
GT1662-VN
Abbreviation of GT1662-VNBA, GT1662-VNBD
GT1655
GT1655-V
Abbreviation of GT1655-VTBD
GT1595-X
Abbreviation of GT1595-XTBA, GT1595-XTBD
GT1585V-S
Abbreviation of GT1585V-STBA, GT1585V-STBD
GT1672
GT1665
Abbreviation of GT1695, GT1685, GT1675, GT1672, GT1665, GT1662, GT1655, GT16 Handy GOT
GT16
GT1595
GT1585
GT157
GT156
GOT1000
Series
GT155
GT1585-S
Abbreviation of GT1585-STBA, GT1585-STBD
GT1575V-S
Abbreviation of GT1575V-STBA, GT1575V-STBD
GT1575-S
Abbreviation of GT1575-STBA, GT1575-STBD
GT1575-V
Abbreviation of GT1575-VTBA, GT1575-VTBD
GT1575-VN
Abbreviation of GT1575-VNBA, GT1575-VNBD
GT1572-VN
Abbreviation of GT1572-VNBA, GT1572-VNBD
GT1565-V
Abbreviation of GT1565-VTBA, GT1565-VTBD
GT1562-VN
Abbreviation of GT1562-VNBA, GT1562-VNBD
GT1555-V
Abbreviation of GT1555-VTBD
GT1555-Q
Abbreviation of GT1555-QTBD, GT1555-QSBD
GT1550-Q
GT15
GT145
Abbreviation of GT1550-QLBD
Abbreviation of GT1595, GT1585, GT157 , GT156 , GT155
GT1455-Q
Abbreviation of GT1455-QTBDE, GT1455-QTBD
GT1450-Q
Abbreviation of GT1450-QLBDE, GT1450-QLBD
GT14
Abbreviation of GT1455-Q, GT1450-Q
GT1275
GT1275-V
Abbreviation of GT1275-VNBA, GT1275-VNBD
GT1265
GT1265-V
Abbreviation of GT1265-VNBA, GT1265-VNBD
GT12
GT115
Abbreviation of GT1275, GT1265
GT1155-Q
GT1150-Q
GT11
GT105
GT104
A - 18
Description
GT1695
Abbreviation of GT1155-QTBDQ, GT1155-QSBDQ, GT1155-QTBDA, GT1155-QSBDA,
GT1155-QTBD, GT1155-QSBD
Abbreviation of GT1150-QLBDQ, GT1150-QLBDA, GT1150-QLBD
Abbreviation of GT115 , GT11 Handy GOT,
GT1055-Q
Abbreviation of GT1055-QSBD
GT1050-Q
Abbreviation of GT1050-QBBD
GT1045-Q
Abbreviation of GT1045-QSBD
GT1040-Q
Abbreviation of GT1040-QBBD
GT1030
Abbreviation of GT1030-LBD, GT1030-LBD2, GT1030-LBL, GT1030-LBDW, GT1030-LBDW2,
GT1030-LBLW, GT1030-LWD, GT1030-LWD2, GT1030-LWL, GT1030-LWDW, GT1030-LWDW2,
GT1030-LWLW, GT1030-HBD, GT1030-HBD2, GT1030-HBL, GT1030-HBDW, GT1030-HBDW2,
GT1030-HBLW, GT1030-HWD, GT1030-HWD2, GT1030-HWL, GT1030-HWDW, GT1030-HWDW2,
GT1030-HWLW
GT1020
Abbreviation of GT1020-LBD, GT1020-LBD2, GT1020-LBL, GT1020-LBDW, GT1020-LBDW2,
GT1020-LBLW, GT1020-LWD, GT1020LWD2, GT1020-LWL, GT1020-LWDW, GT1020-LWDW2,
GT1020-LWLW
GT10
Abbreviation of GT105 , GT104 , GT1030, GT1020
Abbreviations and generic terms
GOT1000
Series
GT16
Handy
GOT
Handy
GOT
GT11
Handy
GOT
Description
GT1665HS-V
Abbreviation of GT1665HS-VTBD
GT1155HS-Q
Abbreviation of GT1155HS-QSBD
GT1150HS-Q
Abbreviation of GT1150HS-QLBD
GT SoftGOT1000
Abbreviation of GT SoftGOT1000
GOT900 Series
Abbreviation of GOT-A900 series, GOT-F900 series
GOT800 Series
Abbreviation of GOT-800 series
 Communication unit
Abbreviations and generic terms
Description
GT15-QBUS, GT15-QBUS2, GT15-ABUS, GT15-ABUS2, GT15-75QBUSL, GT15-75QBUS2L,
GT15-75ABUSL, GT15-75ABUS2L
Bus connection unit
Serial communication unit
GT15-RS2-9P, GT15-RS4-9S, GT15-RS4-TE
RS-422 conversion unit
GT15-RS2T4-9P, GT15-RS2T4-25P
Ethernet communication unit
GT15-J71E71-100
MELSECNET/H communication unit
GT15-J71LP23-25, GT15-J71BR13
MELSECNET/10 communication unit
GT15-75J71LP23-Z*1, GT15-75J71BR13-Z*2
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, GT15-75J61BT13-Z*3
Interface converter unit
GT15-75IF900
Serial multi-drop connection unit
GT01-RS4-M
Connection Conversion Adapter
GT10-9PT5S
RS-232/485 signal conversion adapter
GT14-RS2T4-9P
*1
*2
*3
A9GT-QJ71LP23 + GT15-75IF900 set
A9GT-QJ71BR13 + GT15-75IF900 set
A8GT-J61BT13 + GT15-75IF900 set
 Option unit
Abbreviations and generic terms
Printer unit
Video input unit
Video/RGB unit
Description
GT15-PRN
GT16M-V4, GT15V-75V4
RGB input unit
GT16M-R2, GT15V-75R1
Video/RGB input unit
GT16M-V4R1, GT15V-75V4R1
RGB output unit
GT16M-ROUT, GT15V-75ROUT
Multimedia unit
GT16M-MMR
CF card unit
GT15-CFCD
CF card extension unit
*1
GT15-CFEX-C08SET
External I/O unit
GT15-DIO, GT15-DIOR
Sound output unit
GT15-SOUT
*1
GT15-CFEX + GT15-CFEXIF + GT15-C08CF set.
A - 19
 Option
Abbreviations and generic terms
Memory card
CF card
SD card
Description
GT05-MEM-16MC, GT05-MEM-32MC, GT05-MEM-64MC, GT05-MEM-128MC,
GT05-MEM-256MC, GT05-MEM-512MC, GT05-MEM-1GC, GT05-MEM-2GC,
GT05-MEM-4GC, GT05-MEM-8GC, GT05-MEM-16GC
L1MEM-2GBSD, L1MEM-4GBSD
Memory card adaptor
GT05-MEM-ADPC
Option function board
GT16-MESB, GT15-FNB, GT15-QFNB, GT15-QFNB16M,
GT15-QFNB32M, GT15-QFNB48M, GT11-50FNB, GT15-MESB48M
Battery
GT15-BAT, GT11-50BAT
For GT16
GT16-90PSCB, GT16-90PSGB, GT16-90PSCW, GT16-90PSGW,
GT16-80PSCB, GT16-80PSGB, GT16-80PSCW, GT16-80PSGW,
GT16-70PSCB, GT16-70PSGB, GT16-70PSCW, GT16-70PSGW,
GT16-60PSCB, GT16-60PSGB, GT16-60PSCW, GT16-60PSGW,
GT16-50PSCB, GT16-50PSGB, GT16-50PSCW, GT16-50PSGW,
GT16-90PSCB-012, GT16-80PSCB-012, GT16-70PSCB-012,
GT16-60PSCB-012, GT16-50PSCB-012, GT16H-60PSC
For GT15
GT15-90PSCB, GT15-90PSGB, GT15-90PSCW, GT15-90PSGW,
GT15-80PSCB, GT15-80PSGB, GT15-80PSCW, GT15-80PSGW,
GT15-70PSCB, GT15-70PSGB, GT15-70PSCW, GT15-70PSGW,
GT15-60PSCB, GT15-60PSGB, GT15-60PSCW, GT15-60PSGW,
GT15-50PSCB, GT15-50PSGB, GT15-50PSCW, GT15-50PSGW
Protective Sheet
For GT14
GT14-50PSCB, GT14-50PSGB, GT14-50PSCW, GT14-50PSGW
For GT12
GT11-70PSCB, GT11-65PSCB
For GT11
GT11-50PSCB, GT11-50PSGB, GT11-50PSCW, GT11-50PSGW,
GT11H-50PSC
For GT10
GT10-50PSCB, GT10-50PSGB, GT10-50PSCW, GT10-50PSGW,
GT10-40PSCB, GT10-40PSGB, GT10-40PSCW, GT10-40PSGW,
GT10-30PSCB, GT10-30PSGB, GT10-30PSCW, GT10-30PSGW,
GT10-20PSCB, GT10-20PSGB, GT10-20PSCW, GT10-20PSGW
Protective cover for oil
GT05-90PCO, GT05-80PCO, GT05-70PCO, GT05-60PCO, GT05-50PCO,
GT16-50PCO, GT10-40PCO, GT10-30PCO, GT10-20PCO
USB environmental protection cover
GT16-UCOV, GT16-50UCOV, GT15-UCOV, GT14-50UCOV, GT11-50UCOV
Stand
GT15-90STAND, GT15-80STAND, GT15-70STAND, A9GT-50STAND, GT05-50STAND
Attachment
GT15-70ATT-98, GT15-70ATT-87, GT15-60ATT-97, GT15-60ATT-96,
GT15-60ATT-87, GT15-60ATT-77, GT15-50ATT-95W, GT15-50ATT-85
Backlight
GT16-90XLTT, GT16-80SLTT, GT16-70SLTT, GT16-70VLTT, GT16-70VLTTA, GT16-70VLTN,
GT16-60SLTT, GT16-60VLTT, GT16-60VLTN, GT15-90XLTT, GT15-80SLTT, GT15-70SLTT,
GT15-70VLTT, GT15-70VLTN, GT15-60VLTT, GT15-60VLTN
Multi-color display board
GT15-XHNB, GT15-VHNB
Connector conversion box
GT11H-CNB-37S, GT16H-CNB-42S
Emergency stop sw guard cover
GT11H-50ESCOV, GT16H-60ESCOV
Memory loader
GT10-LDR
Memory board
GT10-50FMB
Panel-mounted USB port extension
GT14-C10EXUSB-4S, GT10-C10EXUSB-5S
A - 20
 Software
Abbreviations and generic terms
GT Works3
Description
Abbreviation of the SW DNC-GTWK3-E and SW DNC-GTWK3-EA
GT Designer3
Abbreviation of screen drawing software GT Designer3 for GOT1000 series
GT Simulator3
Abbreviation of screen simulator GT Simulator3 for GOT1000/GOT900 series
GT SoftGOT1000
Abbreviation of monitoring software GT SoftGOT1000
GT Converter2
Abbreviation of data conversion software GT Converter2 for GOT1000/GOT900 series
GT Designer2 Classic
Abbreviation of screen drawing software GT Designer2 Classic for GOT900 series
GT Designer2
Abbreviation of screen drawing software GT Designer2 for GOT1000/GOT900 series
iQ Works
Abbreviation of iQ Platform compatible engineering environment MELSOFT iQ Works
MELSOFT Navigator
Generic term for integrated development environment software included in the SW DNC-IQWK (iQ
Platform compatible engineering environment MELSOFT iQ Works)
GX Works2
Abbreviation of SW DNC-GXW2-E and SW DNC-GXW2-EA type programmable controller
engineering software
GX Simulator2
Abbreviation of GX Works2 with the simulation function
GX Simulator
Abbreviation of SW D5C-LLT-E(-EV) type ladder logic test tool function software packages
(SW5D5C-LLT (-EV) or later versions)
GX Developer
Abbreviation of SW D5C-GPPW-E(-EV)/SW D5F-GPPW-E type software package
GX LogViewer
Abbreviation of SW DNN-VIEWER-E type software package
PX Developer
Abbreviation of SW D5C-FBDQ-E type FBD software package for process control
MT Works2
Abbreviation of motion controller engineering environment MELSOFT MT Works2
(SW DNC-MTW2-E)
MT Developer
Abbreviation of SW RNC-GSV type integrated start-up support software for motion controller Q series
MR Configurator2
Abbreviation of SW DNC-MRC2-E type Servo Configuration Software
MR Configurator
Abbreviation of MRZJW -SETUP E type Servo Configuration Software
FR Configurator
Abbreviation of Inverter Setup Software (FR-SW -SETUP-WE)
NC Configurator
Abbreviation of CNC parameter setting support tool NC Configurator
FX Configurator-FP
Abbreviation of parameter setting, monitoring, and testing software packages for FX3U-20SSC-H
(SW D5C-FXSSC-E)
FX3U-ENET-L Configuration tool
Abbreviation of FX3U-ENET-L type Ethernet module setting software (SW1D5-FXENETL-E)
RT ToolBox2
Abbreviation of robot program creation software (3D-11C-WINE)
MX Component
Abbreviation of MX Component Version
MX Sheet
Abbreviation of MX Sheet Version
LCPU Logging Configuration Tool
Abbreviation of LCPU Logging Configuration Tool (SW1DNN-LLUTL-E)
(SW D5C-ACT-E, SW D5C-ACT-EA)
(SW D5C-SHEET-E, SW D5C-SHEET-EA)
 License key (for GT SoftGOT1000)
Abbreviations and generic terms
License
Description
GT15-SGTKEY-U, GT15-SGTKEY-P
A - 21
 Others
Abbreviations and generic terms
IAI
Description
Abbreviation of IAI Corporation
AZBIL
Abbreviation of Azbil Corporation (former Yamatake Corporation)
OMRON
Abbreviation of OMRON Corporation
KEYENCE
Abbreviation of KEYENCE CORPORATION
KOYO EI
Abbreviation of KOYO ELECTRONICS INDUSTRIES CO., LTD.
SHARP
Abbreviation of Sharp Manufacturing Systems Corporation
JTEKT
Abbreviation of JTEKT Corporation
SHINKO
Abbreviation of Shinko Technos Co., Ltd.
CHINO
Abbreviation of CHINO CORPORATION
TOSHIBA
Abbreviation of TOSHIBA CORPORATION
TOSHIBA MACHINE
Abbreviation of TOSHIBA MACHINE CO., LTD.
HITACHI IES
Abbreviation of Hitachi Industrial Equipment Systems Co., Ltd.
HITACHI
Abbreviation of Hitachi, Ltd.
FUJI FA
Abbreviation of Fuji Electric FA Components & Systems Co., Ltd.
PANASONIC
Abbreviation of Panasonic Corporation
FUJI SYS
Abbreviation of Fuji Electric Systems Co., Ltd.
YASKAWA
Abbreviation of YASKAWA Electric Corporation
YOKOGAWA
Abbreviation of Yokogawa Electric Corporation
ALLEN-BRADLEY
Abbreviation of Allen-Bradley products manufactured by Rockwell Automation, Inc.
GE FANUC
Abbreviation of GE Fanuc Automation Corporation GE Fanuc Automation Corporation
LS IS
Abbreviation of LS Industrial Systems Co., Ltd.
SCHNEIDER
Abbreviation of Schneider Electric SA
SICK
Abbreviation of SICK AG
SIEMENS
Abbreviation of Siemens AG
RKC
Abbreviation of RKC INSTRUMENT INC.
HIRATA
Abbreviation of Hirata Corporation
MURATEC
Abbreviation of Muratec products manufactured by Muratec Automation Co., Ltd.
PLC
Abbreviation of programmable controller
Temperature controller
Generic term for temperature controller manufactured by each corporation
Indicating controller
Generic term for indicating controller manufactured by each corporation
Control equipment
Generic term for control equipment manufactured by each corporation
CHINO controller
Abbreviation of indicating controller manufactured by CHINO CORPORATION
PC CPU module
Abbreviation of PC CPU Unit manufactured by CONTEC CO., LTD
GOT (server)
Abbreviation of GOTs that use the server function
GOT (client)
Abbreviation of GOTs that use the client function
Windows font
Abbreviation of TrueType font and OpenType font available for Windows
(Differs from the True Type fonts settable with GT Designer3)
Intelligent function module
Indicates the modules other than the PLC CPU, power supply module and I/O module that are mounted
to the base unit
MODBUS/RTU
Generic term for the protocol designed to use MODBUS protocol messages on a serial
communication
MODBUS/TCP
Generic term for the protocol designed to use MODBUS protocol messages on a TCP/IP network
A - 22
HOW TO READ THIS MANUAL
 Symbols
Following symbols are used in this manual.
BUS CONNECTION
Connectable model name
Not connectable model name
5.1 Connectable Model List
5-2
Applicable model name
Shows GT16.
Shows GT15.
Shows GT14.
Shows GT12.
Shows GT11.
Shows GT11 (BUS).
Shows GT11 (SERIAL).
Shows GT10.
Shows GT105 ,GT104 .
Shows GT1020,GT1030 (input power supply : 24V).
Shows GT1020,GT1030 (input power supply : 5V).
1.
2.
3. …
Indicates the operation steps.
2.
[ ]: Indicates the setting items displayed on
the software and GOT screen.
3.
4.
Click!
Refers to the information required.
Refers to information useful
for operation.
Indicates the location of related content.
Since the above page was created for explanation purpose, it differs from the actual page.
A - 23
 About system configuration
The following describes the system configuration of each connection included in this manual.
The configuration of
equipment connected
to GOT is shown.
The cable connecting
the GOT to the
equipment is shown.
The configuration of
the GOT connected to
equipment is shown.
For the option devices,
refer to the following.
1.3 Option Devices
for the Respective
Connection
QCPU
RS-422 connector
conversion Cable
GOT
Connection cable
Indicates the connection diagram
number of cables to be prepared by
the user.
Refer to the connection diagram
section in each chapter.
A representative example
of the system configuration
is described with an
illustration.
Indicates the maximum distance between
the PLC and GOT.
System Configuration Examples
(When connecting the PLC [MELSEC-Q] and GT16, with RS-422 cable)
Indicates the commercially available
cable models that can be used.
1) Connect the RS-422 conversion cable [FA-CNV2402CBL] to the [MELSEC-Q].
2) Connect the option [GT16-C02R4-9S] to [GT16].
3) Connect [MELSEQ-Q] and [GT16] with the connection cable [GT01-C30R4-25P].
Since the above page was created for explanation purpose, it differs from the actual page.
A - 24
1
PREPARATORY
PROCEDURES FOR
MONITORING
MICROCOMPUTER
CONNECTION
(SERIAL)
2
PREPARATORY PROCEDURES
FOR MONITORING
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
1.1 Setting the Communication Interface . . . . . . . . . . . . . . . . . . 1 - 3
1.2 Writing the Project Data and OS onto the GOT . . . . . . . . . 1 - 13
4
1.3 Option Devices for the Respective Connection . . . . . . . . . 1 - 15
MODBUS(R)/RTU
CONNECTION
1.4 Connection Cables for the Respective Connection . . . . . . 1 - 24
1.5 Verifying GOT Recognizes Connected Equipment . . . . . . 1 - 32
1.6 Checking for Normal Monitoring. . . . . . . . . . . . . . . . . . . . . 1 - 36
MODBUS(R)/TCP
CONNECTION
5
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
1.
1
1-1
1.
PREPARATORY PROCEDURES FOR
MONITORING
The following shows the procedures to be taken before monitoring and corresponding reference sections.
Setting the communication interface
Determine the connection type and channel No. to be used, and
perform the communication setting.
1.1
Setting the Communication Interface
Each chapter GOT Side Settings
Writing the project data and OS
Write the standard monitor OS, communication driver, option
1.2.1
Writing the project data and OS onto the GOT
1.2.2
Checking the project data and OS writing on GOT
OS, project data and communication settings onto the GOT.
Verifying the project data and OS
Verify the standard monitor OS, communication driver, option
OS, project data and communication settings are properly
written onto the GOT.
Attaching the communication unit and
connecting the cable
Mount the optional equipment and prepare/connect the
connection cable according to the connection type.
Verifying GOT recognizes connected
equipment
1.3
Option Devices for the Respective Connection
1.4
Connection Cables for the Respective Connection
Each chapter System Configuration
Each chapter Connection Diagram
1.5
Verifying GOT Recognizes Connected Equipment
1.6
Checking for Normal Monitoring
Verify the GOT recognizes controllers on [Communication
Settings] of the Utility.
Verifying the GOT is monitoring normally
Verify the GOT is monitoring normally using Utility, Developer,
etc.
1-2
1. PREPARATORY PROCEDURES FOR MONITORING
Set the communication interface of GOT and the connected equipment.
When using the GOT at the first time, make sure to set the channel of communication interface and the communication
driver before writing to GOT.
Set the communication interface of the GOT at [Controller Setting] and [I/F Communication Setting] in GT Designer3.
2
Setting connected equipment (Channel setting)
MICROCOMPUTER
CONNECTION
(SERIAL)
1.1.1
PREPARATORY
PROCEDURES FOR
MONITORING
1
1.1 Setting the Communication Interface
Set the channel of the equipment connected to the GOT.
 Setting
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
MODBUS(R)/RTU
CONNECTION
4
1.
Select [Common]
2.
The Controller Setting dialog box appears. Select the channel No. to be used from the list menu.
3.
Refer to the following explanations for the setting.
MODBUS(R)/TCP
CONNECTION
5
[Controller Setting] from the menu.
CONNECTION TO
SOUND OUTPUT
UNIT
6
POINT
Channel No.2 to No.4
Use the channel No.2 to No.4 when using the Multi-channel function.
For details of the Multi-channel function, refer to the following.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Mitsubishi Products 20. MULTI-CHANNEL FUNCTION
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
1. PREPARATORY PROCEDURES FOR MONITORING
1.1 Setting the Communication Interface
1-3
 Setting item
This section describes the setting items of the Manufacturer, Controller Type, Driver and I/F.
When using the channel No.2 to No.4, put a check mark at [Use CH*].
Item
Description
Use CH*
Select this item when setting the channel No.2 to No.4.
Manufacturer
Select the manufacturer of the equipment to be connected to the GOT.
Select the type of the equipment to be connected to the GOT. For the settings, refer to the following.
Type
(2)Setting [Controller Type]
Select the interface of the GOT to which the equipment is connected.For the settings, refer to the following.
I/F
(3)Setting [I/F]
Select the communication driver to be written to the GOT.For the settings, refer to the following.
Driver
(1)Setting [Driver]
Make settings for the transmission speed and data length of the communication driver.
Detail Setting
Refer to each chapter of the equipment to be connected to the GOT.
(1) Setting [Driver]
The displayed items for a driver differ according to the settings [Manufacturer], [Controller Type] and [I/F].
When the driver to be set is not displayed, confirm if [Manufacturer], [Controller Type] and [I/F] are correct.
For the settings, refer to the following.
[Setting the communication interface] section in each chapter
1-4
1. PREPARATORY PROCEDURES FOR MONITORING
1.1 Setting the Communication Interface
1
PREPARATORY
PROCEDURES FOR
MONITORING
(2) Setting [Controller Type]
The types for the selection differs depending on the PLC to be used.
For the settings, refer to the following.
Type
Model name
NFCP100
NFJT100
Manufacturer
YOKOGAWA
2
MICROCOMPUTER
CONNECTION
(SERIAL)
TSX P57 203M
TSX P57 253M
TSX P57 303M
TSX P57 353M
TSX P57 453M
140 CPU 311 10
3
140 CPU 434 12U
140 CPU 534 14U
Schneider Electric
MICROCOMPUTER
CONNECTION
(ETHERNET)
MODBUS
140 CPU 651 50
140 CPU 651 60
140 CPU 671 60
140 CPU 113 02
140 CPU 113 03
4
140 CPU 434 12A
Microcomputer
-
MODBUS(R)/TCP
CONNECTION
5
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Microcomputer connection
MODBUS(R)/RTU
CONNECTION
140 CPU 534 14A
1. PREPARATORY PROCEDURES FOR MONITORING
1.1 Setting the Communication Interface
1-5
(3) Setting [I/F]
The interface differs depending on the GOT to be used.
Set the I/F according to the connection and the position of communication unit to be mounted onto the GOT.
(a) GT16
Extension interface 1
3rd stage
Extension interface 2
2nd stage
Standard interface 3
(RS-422/485 interface built in the GOT)
Standard interface 4
(Ethernet interface built in the GOT)
1st stage
Standard interface 1
(RS-232 interface built in the GOT)
(Example: In the case of the GT1685)
Standard interface 2
(USB interface built in the GOT)
(b) GT15
Extension interface 1
Extension interface 2
3rd stage
2nd stage
1st stage
Standard interface 1
(RS-232 interface built in the GOT)
(Example: In the case of the GT1575)
1-6
Standard interface 2
(USB interface built in the GOT)
1. PREPARATORY PROCEDURES FOR MONITORING
1.1 Setting the Communication Interface
1
GT14
PREPARATORY
PROCEDURES FOR
MONITORING
(c)
[Front view]]
MICROCOMPUTER
CONNECTION
(SERIAL)
2
[Rear view]
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
Standard interface 3
(GOT built-in USB interface)
Standard interface 1
(GOT built-in RS-422 interface)
Standard interface 2
(GOT built-in RS-232 interface)
MODBUS(R)/RTU
CONNECTION
4
Standard interface 4
(GOT built-in Ethernet interface)
[Under view]
5
MODBUS(R)/TCP
CONNECTION
(d) GT12
[Rear view]
Standard interface 4
(GOT built-in Ethernet interface)
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Standard interface 1
(GOT built-in RS-422 interface)
Standard interface 2
(GOT built-in RS-232 interface)
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
[Front view]
CONNECTION TO
SOUND OUTPUT
UNIT
6
1. PREPARATORY PROCEDURES FOR MONITORING
1.1 Setting the Communication Interface
1-7
(e) GT11
• GT11 Serial
[Front view]
Standard interface 3
(GOT built-in USB interface)
[Rear view]
Standard interface 1
(GOT built-in RS-422 interface)
Standard interface 2
(GOT built-in RS-232 interface)
• GT11 Bus
[Front view]
Standard interface 3
(GOT built-in USB interface)
[Rear view]
Standard interface 2
(GOT built-in RS-232 interface)
Standard interface 1
(GOT built-in Bus interface)
1-8
1. PREPARATORY PROCEDURES FOR MONITORING
1.1 Setting the Communication Interface
1
GT105
PREPARATORY
PROCEDURES FOR
MONITORING
(f)
MICROCOMPUTER
CONNECTION
(SERIAL)
2
[Rear view]
3
Standard interface 3
(GOT built-in USB interface)
MICROCOMPUTER
CONNECTION
(ETHERNET)
Standard interface 1
(GOT built-in RS-422 interface)
Standard interface 2
(GOT built-in RS-232 interface)
(g) GT104
MODBUS(R)/RTU
CONNECTION
4
Standard interface 1
(GOT built-in RS-422 interface)
MODBUS(R)/TCP
CONNECTION
5
Standard interface 3
(GOT built-in USB interface)
6
CONNECTION TO
SOUND OUTPUT
UNIT
Standard interface 2
(GOT built-in RS-232 interface)
(h) GT1020, GT1030
7
Standard interface 2
(GOT built-in RS-232 interface)
CONNECTION TO
EXTERNAL I/O
DEVICE
Standard interface 1
(GOT built-in RS-422 interface)
or (GOT built-in RS-232 interface)
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
1. PREPARATORY PROCEDURES FOR MONITORING
1.1 Setting the Communication Interface
1-9
1.1.2
I/F communication setting
This function displays the list of the GOT communication interfaces.
Set the channel and the communication driver to the interface to be used.
 Setting
1.
Select [Common]
2.
The I/F Communication Setting dialog box appears. Make the settings with reference to the following explanation.
1 - 10
[I/F Communication Setting] from the menu.
1. PREPARATORY PROCEDURES FOR MONITORING
1.1 Setting the Communication Interface
1
PREPARATORY
PROCEDURES FOR
MONITORING
 Setting item
The following describes the setting items for the standard I/F setting and extension I/F setting.
MICROCOMPUTER
CONNECTION
(SERIAL)
2
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
5
GT11, GT105
, GT104
: Standard I/F-1, Standard I/F-2, Standard I/F-3
CH No.
Set the CH No. according to the intended purpose.
The number of channels differs depending on the GOT to be used.
0: Not used
1 to 4: Used for connecting a controller of channel No. 1 to 4 set in Setting connected equipment (Channel
setting)
8: Used for barcode reader connection, RFID connection, PC remote operation connection (serial) fingerprint
authentication device connection, or printer (serial) GOT (extended computer)
9: Used for connecting Host (PC) or Host (modem)
*: Used for gateway function, MES interface function, and Ethernet download
Multi: Used for Ethernet multiple connection
I/F
The communication type of the GOT standard interface is displayed.
RS232 Setting
None
Host (PC)
Each communication driver for connected devices
7
Make settings for the transmission speed and data length of the communication driver.
Refer to each chapter of the equipment to be connected to the GOT.
To validate the 5V power supply function in RS232, mark the [Enable the 5V power supply] checkbox.
The RS232 setting is invalid in the following cases.
• CH No. of [I/F-1: RS232] is [9] in GT15 and 16.
• CH No. of [I/F-1: RS232] is [9] or [8] in GT14.
• For GT12, GT11 and GT10
CONNECTION TO
EXTERNAL I/O
DEVICE
Detail Setting
Set the driver for the device to be connected.
6
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Driver
MODBUS(R)/TCP
CONNECTION
Standard I/F Setting
Description
Set channel No. and drivers to the GOT standard interfaces.
GT16, GT14, GT12: Standard I/F-1, Standard I/F-2, Standard I/F-3, Standard I/F-4
GT15, GT1030, GT1020: Standard I/F-1, Standard I/F-2
CONNECTION TO
SOUND OUTPUT
UNIT
Item
MODBUS(R)/RTU
CONNECTION
4
1. PREPARATORY PROCEDURES FOR MONITORING
1.1 Setting the Communication Interface
1 - 11
Item
Description
Extend I/F Setting
Set the communication unit attached to the extension interface of the GOT.
CH No.
Set the CH No. according to the intended purpose.
The number of channels differs depending on the GOT to be used.
0: Not used
1 to 4: Used for connecting a controller of channel No. 1 to 4 set in Setting connected equipment (Channel
setting)
5 to 7: Used for barcode reader connection, RFID connection, and PC remote operation connection
* : For the gateway function, MES interface function, Ethernet download, report function,
hard copy (For printer output), video/RGB input, RGB output, multimedia function,
CF card unit, CF card extension unit, sound output, and external I/O or operation panel
Set the driver for the device to be connected.
Driver
None
Detail Setting
Each driver for connected devices
Make settings for the transmission speed and data length of the communication driver.
Refer to each chapter of the equipment to be connected to the GOT.
POINT
Channel No., drivers, [RS232 Setting]
(1) Channel No.2 to No.4
Use the channel No.2 to No.4 when using the Multi-channel function.
For details of the Multi-channel function, refer to the following.
Mitsubishi Products 20. MULTI-CHANNEL FUNCTION
(2) Drivers
The displayed items for a driver differ according to the settings [Manufacturer], [Controller Type] and [I/F].
When the driver to be set is not displayed, confirm if [Manufacturer], [Controller Type] and [I/F] are correct.
[Setting the communication] section in each chapter
(3) [RS232 Setting] of GT14
Do not use [RS232 Setting] of GT14 for other than the 5V power feeding to the RS-232/485 signal conversion
adaptor.
For details, refer to the following manual.
GT14 User's Manual 7.11 RS-232/485 Signal Conversion Adaptor
1.1.3
Precautions
(1) Precautions for changing model
(a) When devices that cannot be converted are included.
When setting of [Manufacturer] or [Controller Type] is changed, GT Designer3 displays the device that
cannot be converted (no corresponding device type, or excessive setting ranges) as [??]. In this case, set
the device again.
(b) When the changed Manufacturer or Controller Type does not correspond to the network.
The network will be set to the host station.
(c)
1 - 12
When the Manufacturer or Controller Type is changed to [None]
The GT Designer3 displays the device of the changed channel No. as [??]. In this case, set the device
again.
Since the channel No. is retained, the objects can be reused in other channel No. in a batch by using the
[Device Bach Edit], [CH No. Batch Edit] or [Device List].
1. PREPARATORY PROCEDURES FOR MONITORING
1.1 Setting the Communication Interface
Write the standard monitor OS, communication driver, option OS, project data and communication settings onto the GOT.
For details on writing to GOT, refer to the following manual.
GT Designer3 Version1 Screen Design Manual
2
Writing the project data and OS onto the GOT
MICROCOMPUTER
CONNECTION
(SERIAL)
1.2.1
PREPARATORY
PROCEDURES FOR
MONITORING
1
1.2 Writing the Project Data and OS onto the GOT
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
MODBUS(R)/RTU
CONNECTION
4
MODBUS(R)/TCP
CONNECTION
The [Communication configuration] dialog box appears.
Set the communication setting between the GOT and the personal computer.
Click the [OK] button when settings are completed.
The [GOT Write] tab appears on the [Communicate with GOT] dialog box.
Select the [Project data, OS] radio button of the Write Data.
6
Check-mark a desired standard monitor OS, communication driver, option OS, extended function OS, and
Communication Settings and click the [GOT Write] button.
CONNECTION TO
SOUND OUTPUT
UNIT
4.
[Write to GOT…] from the menu.
POINT
Writing communication driver onto GT10
When writing a communication driver onto the GT10 in which a Boot OS Ver. under F or a standard monitor OS
Ver. under 01.08.00 is written, turn on the GOT in the OS transfer mode.
Also, even when the communication port to be used for transferring is assigned to Ch9, turn on the GOT in the OS
transfer mode.
For details, refer to the following manual.
GT10 User's Manual
(Operating of transmission mode)
7
CONNECTION TO
EXTERNAL I/O
DEVICE
3.
5
Select [Communication]
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
1.
2.
Turn on the GOT while the bottom right corner is touched.
1. PREPARATORY PROCEDURES FOR MONITORING
1.2 Writing the Project Data and OS onto the GOT
1 - 13
1.2.2
Checking the project data and OS writing on GOT
Confirm if the standard monitor OS, communication driver, option OS, project data and communication settings are
properly written onto the GOT by reading from GOT using GT Designer3.
For reading from the GOT, refer to the following manual.
GT Designer3 Version1 Screen Design Manual
1.
2.
3.
Select [Communication]
[Read from GOT…] from the menu.
The [Communication configuration] dialog box appears.
Set the communication setting between the GOT and the personal computer.
Click the [OK] button when settings are completed.
The [GOT Read] tab appears on the [Communicate with GOT] dialog box.
Select the [Drive information] radio button of the Read Data.
4.
Click the [Info Reception] button.
5.
Confirm that the project data and OS are written correctly onto the GOT.
1 - 14
1. PREPARATORY PROCEDURES FOR MONITORING
1.2 Writing the Project Data and OS onto the GOT
1
PREPARATORY
PROCEDURES FOR
MONITORING
1.3 Option Devices for the Respective Connection
The following shows the option devices to connect in the respective connection type.
For the specifications, usage and connecting procedure on option devices, refer to the respective device manual.
Communication module
2
GT15-QBUS2
For QCPU (Q mode), motion controller CPU (Q series)
Bus connection (2ch) unit standard model
GT15-ABUS
For A/QnACPU, motion controller CPU (A series)
Bus connection (1ch) unit standard model
GT15-ABUS2
For A/QnACPU, motion controller CPU (A series)
Bus connection (2ch) unit standard model
For QCPU (Q mode), motion controller CPU (Q series)
Bus connection (1ch) unit slim model
GT15-75QBUS2L
For QCPU (Q mode), motion controller CPU (Q series)
Bus connection (2ch) unit slim model
GT15-75ABUSL
For A/QnACPU, motion controller CPU (A series)
Bus connection (1ch) unit slim model
GT15-75ABUS2L
For A/QnACPU, motion controller CPU (A series)
Bus connection (1ch) unit slim model
GT15-RS2-9P
RS-232 serial communication unit (D-sub 9-pin (male))
GT15-RS4-9S
RS-422/485 serial communication unit (D-sub 9-pin (female))
GT15-RS4-TE
RS-422/485 serial communication unit (terminal block)
GT15-RS2T4-9P
GT15-RS2T4-25P
RS-422 conversion unit
Optical loop unit
GT15-J71BR13
Coaxial bus unit
MELSECNET/10
Model
GT15-75J71LP23-Z
Optical loop unit (A9GT-QJ71LP23 + GT15-75IF900 set)
GT15-75J71BR13-Z
Coaxial bus unit (A9GT-QJ71BR13 + GT15-75IF900 set)
GT15-J71GP23-SX
Optical loop unit
GT15-J61BT13
GT15-J71E71-100
6
Intelligent device station unit CC-LINK Ver. 2 compatible
Intelligent device station unit
(A8GT-61BT13 + GT15-75IF900 set)
Ethernet (100Base-TX) unit
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Ethernet communication unit
GT15-75J61BT13-Z
5
RS-422 side connector 25-pin
GT15-J71LP23-25
CC-Link communication unit
4
RS-422 side connector 9-pin
RS-232
MELSECNET/H
Communication module
CC-Link IE controller
network communication unit
3
MODBUS(R)/TCP
CONNECTION
RS-422 conversion unit
GT15-75QBUSL
MICROCOMPUTER
CONNECTION
(SERIAL)
For QCPU (Q mode), motion controller CPU (Q series)
Bus connection (1ch) unit standard model
MICROCOMPUTER
CONNECTION
(ETHERNET)
GT15-QBUS
Bus connection unit
Serial communication unit
Specifications
MODBUS(R)/RTU
CONNECTION
Model
CONNECTION TO
SOUND OUTPUT
UNIT
Product name
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
1.3.1
1. PREPARATORY PROCEDURES FOR MONITORING
1.3 Option Devices for the Respective Connection
1 - 15
1.3.2
Option unit
Product name
Model
Printer unit
GT15-PRN
Multimedia unit
GT16M-MMR
Video input unit
RGB input unit
Video/RGB input unit
RGB output unit
GT16M-V4
GT15V-75V4
GT16M-R2
GT15V-75R1
GT16M-V4R1
GT15V-75V4R1
GT16M-ROUT
GT15V-75ROUT
USB slave (PictBridge) for connecting printer 1 ch
For video input signal (NTSC/PAL) 1 ch, playing movie
For video input signal (NTSC/PAL) 4 ch
For analog RGB input signal 2 ch
For video input signal (NTSC/PAL) 4 ch, for analog RGB mixed input signal 1 ch
For analog RGB output signal 1 ch
CF card unit
GT15-CFCD
CF card extension unit
GT15-CFEX-C08SET
Sound output unit
GT15-SOUT
For sound output
GT15-DIOR
For the connection to external I/O device or operation panel (Negative Common
Input/Source Type Output)
GT15-DIO
For the connection to external I/O device or operation panel (Positive Common
Input/Sink Type Output)
Product name
Model
Specifications
RS-422 connector conversion
cable
GT16-C02R4-9S
External I/O unit
1.3.3
Specifications
For CF card installation (B drive) For GOT back face CF card eject
For CF card installation (B drive) For control panel front face CF card eject
Conversion cable
RS-422/485 (Connector)
RS-422 conversion cable (D-sub 9-pin)
FA-LTBGTR4CBL05
RS-485 terminal block
conversion modules
FA-LTBGTR4CBL10
RS-422/485 (Connector)
RS-485 (Terminal block)
Supplied connection cable dedicated for the conversion unit
FA-LTBGTR4CBL20
1.3.4
Product name
Model
Connector conversion adapter
GT10-9PT5S
1.3.5
1.3.6
1 - 16
Connector conversion adapter
Specifications
RS-422/485 (D-Sub 9-pin connector)
RS-422/485 (Terminal block)
Serial Multi-Drop Connection Unit
Product name
Model
Serial multi-drop
connection unit
GT01-RS4-M
Specifications
GOT multi-drop connection module
Mitsubishi Products 18. GOT MULTI-DROP CONNECTION
RS-232/485 signal conversion adapter
Product name
Model
RS-232/485 signal
conversion adapter
GT14-RS2 4-9P
Specifications
RS-232 signal (D-Sub 9-pin connector)
1. PREPARATORY PROCEDURES FOR MONITORING
1.3 Option Devices for the Respective Connection
RS-485 signal (Terminal block)
1
PREPARATORY
PROCEDURES FOR
MONITORING
Installing a unit on another unit (Checking the unit installation position)
This section describes the precautions for installing units on another unit.
For the installation method of each unit, refer to the following manual.
GT16 User’s Manual (Hardware)
GT15 User's Manual
For using multiple extension units, a bar code reader, or a RFID controller, the total current for the extension units,
bar code reader, or RFID controller must be within the current that the GOT can supply.
For the current that the GOT can supply and the current for the extension units, bar code reader, or RFID controller,
refer to the following tables. Make sure that the total of consumed current is within the capacity of the GOT.
(1) Current supply capacity of the GOT
GT1595-X
2.13
GT1685M-S
2.4
GT1585V-S
1.74
GT1675M-S
2.4
GT1585-S
1.74
2.4
GT1575V-S
2.2
2.4
GT1575-S
2.2
GT1665M-S
2.4
GT1575-V,
GT1572-VN
2.2
GT1665M-V
2.4
GT1565-V,
GT1562-VN
2.2
GT1662-VN
2.4
GT1555-V
GT1655-V
1.3
GT1555-Q,
GT1675-VN,
GT1672-VN
MICROCOMPUTER
CONNECTION
(ETHERNET)
2.4
4
MODBUS(R)/RTU
CONNECTION
GT1695M-X
GT1675M-V
3
Current supply
capacity
(A)
GOT type
1.3
GT1550-Q
1.3
5
(2) Current consumed by an extension unit/barcode reader/RFID controller
GT15-QBUS,
GT15-75QBUSL,
GT15-QBUS2,
GT15-75QBUS2L
0.275*1
GT15-ABUS,
GT15-75ABUSL,
GT15-ABUS2,
GT15-75ABUS2L
0.12
Module type
GT16M-R2
GT15V-75R1
Consumed
current
(A)
0*1
*1
GT15-RS2-9P
0.29
GT16M-V4R1
0.12
GT15-RS4-9S
0.33
GT15V-75V4R1
0.2*1
GT15-RS4-TE
0.3
GT16M-ROUT
0.11*1
GT15-RS2T4-9P
0.098
GT15V-75ROUT
GT15-J71E71-100
0.224
GT16M-MMR
0.27*1
GT15-J71GP23-SX
1.07
GT15-CFCD
0.07
GT15-J71LP23-25
0.56
GT15-CFEX-C08SET
0.15
GT15-J71BR13
0.77
GT15-SOUT
0.08
GT15-J61BT13
0.56
GT15-DIO
0.1
Bar code reader
*2
GT15-DIOR
0.1
RFID controller
*2
GT15-PRN
0.09
GT16M-V4
0.12*1
GT15V-75V4
0.2*1
*1
*2
GT15-80FPA
6
0.2*1
CONNECTION TO
SOUND OUTPUT
UNIT
Consumed
current
(A)
0.11
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Module type
8
0.22
Value used for calculating the current consumption of the multi-channel function.
For the specifications of the unit, refer to the manual included with the unit.
When the GOT supplies power to a barcode reader or a RFID controller from the standard interface, add their consumed
current.(Maximum value is less than 0.3 A.)
1. PREPARATORY PROCEDURES FOR MONITORING
1.3 Option Devices for the Respective Connection
MODBUS(R)/TCP
CONNECTION
Current supply
capacity
(A)
GOT type
MICROCOMPUTER
CONNECTION
(SERIAL)
2
 Calculating consumed current
1 - 17
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
1.3.7
(3) Calculation example
(a) When connecting the GT15-J71BR13, GT15-RS4-9S (3 units), GT15-J71E71-100 (for the gateway
function) and a bar code reader (0.12 A) to the GT1575-V
Current supply capacity of GOT (A)
Total consumed current (A)
2.2
0.77+0.33+0.33+0.33+0.224+0.12=2.104
Since the calculated value is within the capacity of the GOT, they can be connected to the GOT.
(b) When connecting the GT15-J71BR13, GT15-RS4-9S (2 units), GT15-J71E71-100 (for the gateway
function) and a bar code reader (0.12 A) to the GT1585-S
Current supply capacity of GOT (A)
Total consumed current (A)
1.74
0.77+0.33+0.33+0.224+0.12=1.774
Since the calculated value exceeds the capacity of the GOT, such configuration is not allowed.
 When using a bus connection unit
The installation position varies depending on the bus connection unit to be used.
(1) Wide bus units (GT15-75QBUS(2)L, GT15-75ABUS(2)L, GT15-QBUS2,
GT15-ABUS2)
Install a bus connection unit in the 1st stage of the extension interface.
If a bus connection unit is installed in the 2nd stage or above, the unit cannot be used.
Example: Installing a bus connection unit and serial communication units
1 - 18
Serial communication unit
Bus connection unit
Bus connection unit
Serial communication unit
1. PREPARATORY PROCEDURES FOR MONITORING
1.3 Option Devices for the Respective Connection
POINT
Cautions for using GT15-QBUS2 and GT15-ABUS2
Recognized as the
3rd stage of extend
interface 1
Recognized as the 2nd stage
of extend interface 2
Recognized as the
2nd stage of extend
interface 1
Recognized as the 1st stage
of extend interface 2
2
MICROCOMPUTER
CONNECTION
(SERIAL)
The stage number of communication units installed on the next stage of GT15-QBUS2 or GT15-ABUS2 are
recognized by the GOT differently depending on the extension interface position.
For communication units installed in the extension interface 2 side, even if the communication unit is physically
installed in the 2nd stage position, the GOT recognizes the position as the 1st stage.
PREPARATORY
PROCEDURES FOR
MONITORING
1
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
Recognized as the 1st stage
of extend interface 1
GT15-QBUS2, GT15-ABUS2
Relay connector
MODBUS(R)/RTU
CONNECTION
4
(2) Standard size bus connection unit (GT15-QBUS and GT15-ABUS)
5
A bus connection unit can be installed in any position (1st to 3rd stage) of the extension interface.
Serial communication unit
Bus connection unit
Bus connection unit
Serial communication unit
MODBUS(R)/TCP
CONNECTION
Example: Installing a bus connection unit and serial communication units
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
1. PREPARATORY PROCEDURES FOR MONITORING
1.3 Option Devices for the Respective Connection
1 - 19
 When using a MELSECNET/H communication unit, CC-Link IE controller network
communication unit, or CC-Link communication unit (GT15-J61BT13)
Install a MELSECNET/H communication unit, CC-Link IE controller network communication unit, or CC-Link
communication unit in the 1st stage of an extension interface.
These communication units cannot be used if installed in the 2nd or higher stage.
Example: When installing a MELSECNET/H communication unit and a serial communication unit
Serial communication unit
MELSECNET/H
communication unit
MELSECNET/H
communication unit
Serial communication unit
POINT
Precautions for using a MELSECNET/H communication unit, CC-Link IE controller network communication unit,
CC-Link communication unit (GT15-J61BT13)
The installed stage number of communication units installed on the next stage of MELSECNET/H communication
unit, CC-Link IE controller network communication unit, or CC-Link communication unit are recognized by the GOT
differently depending on the extension interface position.
For communication units installed in the extension interface 2 side, even if the communication unit is physically
installed in the 2nd stage position, the GOT recognizes the position as the 1st stage.
Recognized as the 3rd stage
of extension interface 1
Recognized as the 2nd stage
of extension interface 1
Recognized as the 2nd stage
of extension interface 2
Recognized as the 1st stage
of extension interface 2
Recognized as the 1st stage
of extension interface 1
MELSECNET/H communication unit
Relay connector
1 - 20
1. PREPARATORY PROCEDURES FOR MONITORING
1.3 Option Devices for the Respective Connection
Z) or CC-Link communication unit (GT15-75J61BT13-Z)
Install a MELSECNET/10 communication unit (GT15-75J71LP23-Z, GT15-75J71BR13-Z) or CC-Link communication
unit (GT15-75J61BT13-Z) at the 1st stage of the extension interface.
These communication units cannot be used if installed in the 2nd or higher stage.
For GT16 and the GT155 , the MELSECNET/10 communication unit (GT15-75J71LP23-Z, GT15- 75J71BR13-Z)
and the CC-Link communication unit (GT15-75J61BT13-Z) are not applicable.
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Example: When installing a MELSECNET/10 communication unit and a serial communication unit
1
PREPARATORY
PROCEDURES FOR
MONITORING
 When using a MELSECNET/10 communication unit (GT15-75J71LP23-Z, GT15- 75J71BR13-
MELSECNET/10
communication unit
Serial communication unit
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
An Ethernet communication unit can be installed in any position (1st to 3rd stage) of the extension interface.
For GT16, the Ethernet communication unit is not applicable.
Use the Ethernet interface built in the GOT.
Example: When installing an Ethernet communication unit and a serial communication unit
Ethernet
communication unit
Ethernet
communication unit
5
Serial communication unit
MODBUS(R)/TCP
CONNECTION
Serial communication unit
MODBUS(R)/RTU
CONNECTION
4
 When using an Ethernet communication unit
CONNECTION TO
SOUND OUTPUT
UNIT
6
 When using a serial communication unit
A serial communication unit can be installed in any position (1st to 3rd stage) of the extension interface.
Serial
communication
unit
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Serial
communication
unit
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
1. PREPARATORY PROCEDURES FOR MONITORING
1.3 Option Devices for the Respective Connection
1 - 21
 When using the printer unit, sound output unit, or external I/O unit
The printer unit, sound output unit, or external I/O unit can be installed in any position (1st to 3rd stage) of the
extension interface.
Example: When installing a printer unit
Communication
unit
Printer unit
Printer unit
Communication
unit
 When using the video input unit, RGB input unit, video/RGB input unit, RGB output unit, or
multimedia unit
Install the video input unit, RGB input unit, video/RGB input unit, RGB output unit, or multimedia unit at the 1st stage
of the extension interface.If any of these units is installed in the 2nd stage or above, the unit cannot be used.
When any of these units is used, the communication units indicated below must be installed in the 2nd stage of the
extension interface.
Communication unit
Model
Bus connection unit
GT15-QBUS2,
GT15-ABUS2
MELSECNET/H communication
unit
GT15-J71LP23-25,
GT15-J71BR13
CC-Link IE controller
network communication unit
GT15-J71GP23-SX
CC-Link communication unit
GT15-J61BT13
Example: When installing a video input unit and a MELSECNET/H communication unit
MELSECNET/H
communication unit
Video/RGB
input unit
1 - 22
1. PREPARATORY PROCEDURES FOR MONITORING
1.3 Option Devices for the Respective Connection
Video/RGB
input unit
MELSECNET/H
communication unit
POINT
Precautions for video input unit, RGB input unit, video/RGB input unit, RGB output unit, and multimedia unit
Recognized as the 2nd stage of
extension interface 1
Recognized as the 2nd stage
of extension interface 2
Recognized as the 1st stage
of extension interface 2
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
Recognized as the 3rd stage of
extension interface 1
2
MICROCOMPUTER
CONNECTION
(SERIAL)
When a communication unit is installed on any of the units above, the stage number of the communication unit
recognized by the GOT varies according to the extension interface.
For communication units installed in the extension interface 2 side, even if the communication unit is physically
installed in the 2nd stage position, the GOT recognizes the position as the 1st stage.
PREPARATORY
PROCEDURES FOR
MONITORING
1
Recognized as the 1st stage of
extension interface 1
Video/RGB input unit
Relay connector
MODBUS(R)/RTU
CONNECTION
4
 When using CF card unit or CF card extension unit
5
CF card unit
MODBUS(R)/TCP
CONNECTION
Install the CF card unit or CF card extension unit on the extension interface at the last.
The following figures show how to install the CF card unit.
Serial communication
unit
Serial communication
unit
6
CONNECTION TO
SOUND OUTPUT
UNIT
CF card unit
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
1. PREPARATORY PROCEDURES FOR MONITORING
1.3 Option Devices for the Respective Connection
1 - 23
1.4 Connection Cables for the Respective Connection
To connect the GOT to a device in the respective connection type, connection cables between the GOT and a device are
necessary.
For cables needed for each connection, refer to each chapter for connection.
1.4.1
GOT connector specifications
The following shows the connector specifications on the GOT side.
Refer to the following table when preparing connection cables by the user.
 RS-232 interface
Use the following as the RS-232 interface and RS-232 communication unit connector on the GOT. For the GOT side
connection cable, use a connector and connector cover applicable to the GOT connector.
(1) Connector specifications
Hardware
GOT
Connector type
version*1
GT16
―
GT1595-X
―
GT1585V-S
17LE-23090-27(D4C
B or later
―
GT1575V-S
―
GT1575-STBD
GT1575-VTBA
)
DDK Ltd.
GM-C9RMDU11
Honda Tsushin Kogyo Co., Ltd.
17LE-23090-27(D4CK)
DDK Ltd.
GM-C9RMDU11
Honda Tsushin Kogyo Co., Ltd.
17LE-23090-27(D4CK)
DDK Ltd.
GM-C9RMDU11
Honda Tsushin Kogyo Co., Ltd.
C
GT1585-STBD
GT1575-STBA
Manufacturer
17LE-23090-27(D4CK)
―
GT1585-STBA
Connector model
B or later
C
―
D or later
9-pin D-sub (male)
inch screw fixed type
E
GT1575-VTBD
―
GT1575-VN
―
GT1572-VN
―
GT1565-V
―
GT1562-VN
―
GT12
―
GT155
―
GT14
―
GT115
-Q
―
GT105
-Q
―
GT104
-Q
―
17LE-23090-27(D4CK)
DDK Ltd.
17LE-23090-27(D3CC)
GT1030, GT1020
―
9-pin terminal block*2
MC1.5/9-G-3.5BK
PHOENIX CONTACT Inc.
GT15-RS2-9P
―
GT01-RS4-M
―
9-pin D-sub (male)
inch screw fixed type
17LE-23090-27(D3CC)
DDK Ltd.
*1
*2
For the procedure to check the GT15 hardware version, refer to the GT15 User's Manual.
The terminal block (MC1.5/9-ST-3.5 or corresponding product) of the cable side is packed together with the GT1030 and
GT1020.
(2) Connector pin arrangement
GT16, GT15, GT14, GT12, GT11, GT105
, GT104
, GT01-RS4-M
GOT main part connector
see from the front
1
5
9
9-pin D-sub (male)
1 - 24
See from the back of a
GOT main part
1. PREPARATORY PROCEDURES FOR MONITORING
1.4 Connection Cables for the Respective Connection
SD
RD
ER
DR
SG
RS
CS
NC
NC
6
GT1030, GT1020
9-pin terminal block
Use the following as the RS-422 interface and RS-422/485 communication unit connector on the GOT.
For the GOT side of the connection cable, use a connector and connector cover applicable to the GOT connector.
(1) Connector model
Connector model
Manufacturer
2
RS-422 conversion unit
9-pin D-sub (female)
M2.6 millimeter screw
fixed type
17LE-13090-27(D2AC)
DDK Ltd.
GT16*1
14-pin (female)
HDR-EC14LFDT1-SLE+
Honda Tsushin Kogyo Co., Ltd.
9-pin D-sub (female)
M2.6 millimeter screw
fixed type
17LE-13090-27(D3AC)
DDK Ltd.
GT1030, GT1020
9-pin terminal block*2
MC1.5/9-G-3.5BK
PHOENIX CONTACT Inc.
GT15-RS4-9S
9-pin D-sub (female)
M2.6 millimeter screw
fixed type
17LE-13090-27(D3AC)
DDK Ltd.
MICROCOMPUTER
CONNECTION
(SERIAL)
Connector type
GT14
GT115
-Q
GT105
-Q
GT104
-Q
GT01-RS4-M
*1
*2
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
GT12
When connecting to the RS-422/485 interface, use HDR-E14MAG1+ as a cable connector.
To use HDR-E14MAG1+, a dedicated pressure welding tool is required.
For details on the connector and pressure welding tool, contact Honda Tsushin Kogyo Co., Ltd.
The terminal block (MC1.5/9-ST-3.5 or corresponding product) of the cable side is packed together with the GT1030, GT1020.
(2) Connector pin arrangement
GT104
GOT main part connector
see from the front
5
14-pin (female)
9
1
6
9-pin D-sub (female)
9-pin terminal block
6
CONNECTION TO
SOUND OUTPUT
UNIT
7
5
See from the back of a
GOT main part
7
CONNECTION TO
EXTERNAL I/O
DEVICE
14
GT1030, GT1020
SDA
SDB
RDA
RDB
SG
RSA
RSB
CSA
CSB
1
GOT main part connector
see from the front
,
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
, GT01-RS4-M
MODBUS(R)/TCP
CONNECTION
GT15, GT14, GT12, GT11, GT105
GT16
4
MODBUS(R)/RTU
CONNECTION
GOT
PREPARATORY
PROCEDURES FOR
MONITORING
1
 RS-422 interface
1. PREPARATORY PROCEDURES FOR MONITORING
1.4 Connection Cables for the Respective Connection
1 - 25
 RS-485 interface
Use the following as the RS-485 interface and RS-422/485 communication unit connector on the GOT.
For the GOT side of the connection cable, use a connector and connector cover applicable to the GOT connector.
(1) Connector model
Hardware version*1
GOT
GT16*2
―
GT14
―
GT12
―
GT1155-QTBD
C or later
GT1155-QSBD
F or later
GT1150-QLBD
GT105
-Q
GT104
-Q
Manufacturer
14-pin (female)
HDR-EC14LFDT1-SLE+
Honda Tsushin Kogyo Co., Ltd.
9-pin D-sub (female)
M2.6 millimeter screw
fixed type
17LE-13090-27(D3AC)
DDK Ltd.
9-pin terminal block*3
MC1.5/9-G-3.5BK
PHOENIX CONTACT Inc
9-pin D-sub (female)
M2.6 millimeter screw
fixed type
17LE-13090-27(D3AC)
DDK Ltd.
SL-SMT3.5/10/90F BOX
Weidmuller interconnections inc
A or later
B or later
GT1020
E or later
GT15-RS4-9S
―
GT15-RS4-TE
―
*3
Connector model
C or later
GT1030
*1
*2
Connector type
―
For the checking procedure of the hardware version, refer to the User's Manual.
When connecting to the RS-422/485 interface, use HDR-E14MAG1+ as a cable connector.
To use HDR-E14MAG1+, a dedicated pressure welding tool is required.
For details on the connector and pressure welding tool, contact Honda Tsushin Kogyo Co., Ltd..
The terminal block (MC1.5/9-ST-3.5 or corresponding product) of the cable side is packed together with the GT1030, GT1020.
(2) Connector pin arrangement
GT15, GT14, GT12, GT11,
GT16
GT105
GOT main part connector
see from the front
8
7
14-pin (female)
1 - 26
9
GT1030, GT1020
See from the back of a
GOT main part
1
6
9-pin D-sub (female)
1. PREPARATORY PROCEDURES FOR MONITORING
1.4 Connection Cables for the Respective Connection
SDA
SDB
RDA
RDB
SG
RSA
RSB
CSA
CSB
1
GOT main part connector
see from the front
5
14
, GT104
9-pin terminal block
The following describes the method for connecting the BNC connector (connector plug for coaxial cable) and the cable.
CAUTION
 Solder the coaxial cable connectors properly.
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Insufficient soldering may result in malfunctions.
Structure of the coaxial cable
Components of the BNC connector
Nut
Washer
PREPARATORY
PROCEDURES FOR
MONITORING
1
Coaxial cable connector connection method
Gasket
External conductor
Outer sheath Insulating material
3
Internal conductor
Contact
1.
Remove the external sheath of the coaxial cable with
dimensions as shown below.
A
2.
Clamp
4
A
Cable in use
Cut this portion of the outer sheath
3C-2V
15mm
5C-2V, 5C-2V-CCY
10mm
Pass the nut, washer, gasket, and clamp through the coaxial
cable as shown on the left and loosen the external conductor.
5
Nut
Washer
Gasket
3.
C
B
Cut the external conductor, insulting material, and internal
conductor with the dimensions as shown below.
Note that the external conductor should be cut to the same
dimension as the tapered section of the clamp and smoothed
down to the clamp.
Clamp and external
conductor
Solder here
Cable in use
4.
B
C
3C-2V
6mm
3mm
5C-2V, 5C-2V-CCY
7mm
5mm
6
CONNECTION TO
SOUND OUTPUT
UNIT
Insulating material
Internal conductor
MODBUS(R)/RTU
CONNECTION
Clamp
MICROCOMPUTER
CONNECTION
(ETHERNET)
Plug shell
MODBUS(R)/TCP
CONNECTION
1.4.2
Solder the contact to the internal conductor.
5.
Insert the connector assembly shown in
shell and screw the nut into the plug shell.
into the plug
CONNECTION TO
EXTERNAL I/O
DEVICE
7
Note the following precautions when soldering the internal conductor and contact.
• Make sure that the solder does not bead up at the soldered section.
• Make sure there are no gaps between the connector and cable insulator or they do not cut into each other.
• Perform soldering quickly so the insulation material does not become deformed.
1. PREPARATORY PROCEDURES FOR MONITORING
1.4 Connection Cables for the Respective Connection
1 - 27
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
Precautions for soldering
1.4.3
Terminating resistors of GOT
The following shows the terminating resistor specifications on the GOT side.
When setting the terminating resistor in each connection type, refer to the following.
 RS-422/485 communication unit
 GT16
Set the terminating resistor using the terminating
resistor setting switch.
Switch No.
Terminating
The default setting is "Disable".
100 OHM
ON
ON
Disable
OFF
OFF
*1
• For RS422/485 communication unit
2
ON
OFF
1
2
ON
OFF
resistor*1
1
ON
Disable
SW1
2
100 OHM
*1
Switch No.
Terminating
2
ON
1
1
resistor*1
Set the terminating resistor using the terminating
resistor setting switch.
SW1
The default setting is "Disable".
• For GT1685M-S
1
ON
SW1
2
ON
Terminating resistor setting switch
Rear view of RS-422/485 communication unit.
 RS-232/485 signal conversion adapter
For details, refer to the following.
Terminating resistor setting switch
(inside the cover)
1.4.4 Setting the RS-232/485 signal
conversion adaptor
 GT14
Set the terminating resistor using the terminating
resistor setting switch.
Terminating resistor selector switch
1 - 28
1. PREPARATORY PROCEDURES FOR MONITORING
1.4 Connection Cables for the Respective Connection
1
 GT105
Set the terminating resistor using the terminating
resistor setting switch.
PREPARATORY
PROCEDURES FOR
MONITORING
 GT12
Set the terminating resistor using the terminating
resistor setting switch.
MICROCOMPUTER
CONNECTION
(SERIAL)
2
Terminating resistor selector switch
 GT11
Terminating resistor selector switch
Set the terminating resistor using the terminating
resistor setting switch.
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
4
 GT104
MODBUS(R)/RTU
CONNECTION
Set the terminating resistor using the terminating
resistor setting switch.
MODBUS(R)/TCP
CONNECTION
5
Terminating resistor selector switch
Terminating resistor selector switch
resistor setting switch.
CONNECTION TO
SOUND OUTPUT
UNIT
6
7
 GT1030
CONNECTION TO
EXTERNAL I/O
DEVICE
Set the terminating resistor using the terminating
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
Terminating resistor selector switch
1. PREPARATORY PROCEDURES FOR MONITORING
1.4 Connection Cables for the Respective Connection
1 - 29
 GT1020
Set the terminating resistor using the terminating
resistor setting switch.
Terminating resistor selector switch
1 - 30
1. PREPARATORY PROCEDURES FOR MONITORING
1.4 Connection Cables for the Respective Connection
Set the 2-wire/4-wire terminating resistor setting switch according to the connection type.
POINT
Enable the 5V power supply
Make sure to validate "Enable the 5V power supply" in the [RS232 Setting] to operate the RS-232/485 signal
conversion adaptor.
1.2.2 Checking the project data and OS writing on GOT
When validating the function using the utility function of the GOT main unit, refer to the following manual.
GT14 User's Manual 8.2 Utility Function List
PREPARATORY
PROCEDURES FOR
MONITORING
1
Setting the RS-232/485 signal conversion adaptor
2
MICROCOMPUTER
CONNECTION
(SERIAL)
1.4.4
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
2-wire/4-wire terminating resistor setting switch
MODBUS(R)/RTU
CONNECTION
4
 Setting the 2-wire/4-wire terminating resistor setting switch
2-wire/4-wire
Terminating resistor
5
6
4
3
MODBUS(R)/TCP
CONNECTION
Set value
Switch No.
1
2
3
4
5
6
2-wire (1Pair)
ON
ON
-
-
-
OFF
4-wire (2Pair)
OFF
OFF
-
-
-
OFF
110
-
-
ON
OFF
OFF
OFF
OPEN
-
-
OFF
OFF
OFF
OFF
330
-
-
OFF
ON
ON
OFF
6
CONNECTION TO
SOUND OUTPUT
UNIT
Setting item
2
1
O
N
5
7
CONNECTION TO
EXTERNAL I/O
DEVICE
POINT
RS-232/485 signal conversion adapter
For details on the RS-232/485 signal conversion adapter, refer to the following manual.
GT14-RS2T4-9P RS-232/485 Signal Conversion Adapter User's Manual
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
1. PREPARATORY PROCEDURES FOR MONITORING
1.4 Connection Cables for the Respective Connection
1 - 31
1.5 Verifying GOT Recognizes Connected Equipment
Verify the GOT recognizes controllers on [Communication Settings] of the Utility.
• Channel number of communication interface, communication drivers allocation status
• Communication unit installation status
For details on the Utility, refer to the following manual.
User's Manual of GOT used.
 When using GT16, GT12
(For GT16)
1.
1.
2.
2.
1 - 32
1. PREPARATORY PROCEDURES FOR MONITORING
1.5 Verifying GOT Recognizes Connected Equipment
After powering up the GOT, touch [Main menu]
[Communication setting] from the Utility.
Touch [Communication setting].
4.
5.
1
The [Communication Settings] appears.
Verify that the communication driver name to
be used is displayed in the communication
interface box to be used.
When the communication driver name is not
displayed normally, carry out the following
procedure again.
1.1Setting the Communication Interface
PREPARATORY
PROCEDURES FOR
MONITORING
3.
4.
2
MICROCOMPUTER
CONNECTION
(SERIAL)
3.
 For GT15, GT14 or GT11
1.
4
MODBUS(R)/RTU
CONNECTION
1.
After powering up the GOT, touch [Main menu]
[Communication setting] from the Utility.
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
Touch [Communication setting].
(The screen on the left is not displayed on
GT11.)
2.
6
CONNECTION TO
SOUND OUTPUT
UNIT
2.
MODBUS(R)/TCP
CONNECTION
5
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
1. PREPARATORY PROCEDURES FOR MONITORING
1.5 Verifying GOT Recognizes Connected Equipment
1 - 33
3.
3.
4.
4.
5.
The [Communication Settings] appears.
Verify that the communication driver name to
be used is displayed in the box for the
communication interface to be used.
When the communication driver name is not
displayed normally, carry out the following
procedure again.
1.1Setting the Communication Interface
 For GT10
1.
1.
2.
3.
4.
2.
Touch [Standard I/F] on [Comm. Setting].
3.
The [Standard I/F] appears.
4.
5.
1 - 34
After powering up the GOT, touch [Main menu]
[Communication setting] from the Utility.
1. PREPARATORY PROCEDURES FOR MONITORING
1.5 Verifying GOT Recognizes Connected Equipment
Verify that the communication driver name to
be used is displayed in the box for the
communication interface to be used.
When the communication driver name is not
displayed normally, carry out the following
procedure again.
1.1Setting the Communication Interface
1
PREPARATORY
PROCEDURES FOR
MONITORING
POINT
Utility
(1) How to display Utility (at default)
When using GT16, GT1595, GT14, GT12 or GT1020
2
Utility display
(When using GT16,GT12) (When using GT15)
MICROCOMPUTER
CONNECTION
(SERIAL)
Utility call key
1-point press on GOT screen upper-left corner
When using GT1585, GT157 ,
GT156 , GT155 , GT11, GT105 ,
GT104 or GT1030
(When using GT105
(When using GT14, GT11) GT104 )
,
Utility call key
Simultaneous 2-point press
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
(2) Utility call
When setting [Pressing time] to other than 0 second on the setting screen of the utility call key, press and hold
the utility call key until the buzzer sounds.For the setting of the utility call key, refer to the following.
User's Manual of GOT used.
(3) Communication interface setting by the Utility
The communication interface setting can be changed on the Utility's [Communication setting] after writing
[Communication Settings] of project data.
For details on the Utility, refer to the following manual.
6
CONNECTION TO
SOUND OUTPUT
UNIT
User's Manual of GOT used.
5
MODBUS(R)/TCP
CONNECTION
(When using GT1030,GT1020)
MODBUS(R)/RTU
CONNECTION
4
(4) Precedence in communication settings
When settings are made by GT Designer3 or the Utility, the latest setting is effective.
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
1. PREPARATORY PROCEDURES FOR MONITORING
1.5 Verifying GOT Recognizes Connected Equipment
1 - 35
1.6 Checking for Normal Monitoring
1.6.1
Check on the GOT
 Check for errors occurring on the GOT
Presetting the system alarm to project data allows you to identify errors occurred on the GOT, PLC CPU, servo
amplifier and communications.
For details on the operation method of the GOT Utility screen, refer to the following manual.
User's Manual of GOT used.
(When using GT15)
Error code
Communication Channel No.
Error message
Time of occurrence
(Displayed only for errors)
HINT
Advanced alarm popup display
With the advanced alarm popup display function, alarms are displayed as a popup display regardless of whether
an alarm display object is placed on the screen or not (regardless of the display screen).
Since comments can be flown from right to left, even a long comment can be displayed all.
For details of the advanced popup display, refer to the following manual.
GT Designer3 Version1 Screen Design Manual
1 - 36
1. PREPARATORY PROCEDURES FOR MONITORING
1.6 Checking for Normal Monitoring
GT10 User's Manual
(Operation of communication monitoring function screen)
Main Menu
2
MICROCOMPUTER
CONNECTION
(SERIAL)
The communication monitoring is a function that checks whether the PLC can communicate with the GOT.
If this check ends successfully, it means correct communication interface settings and proper cable connection.
Display the communication monitoring function screen by [Main Menu]
[Comm. Setting]
[Comm. Monitor].
For details on the communication monitoring function, refer to the following manual:
PREPARATORY
PROCEDURES FOR
MONITORING
1
 Communication monitoring function
Touch [
Touch [Comm. Setting]
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
]
MODBUS(R)/RTU
CONNECTION
4
Communication settings
MODBUS(R)/TCP
CONNECTION
5
Touch [Comm. Monitor]
 Write data to virtual devices inside GOT (For microcomputer connection)
Send a message from the host to the GOT, and confirm that the values are stored in the virtual devices inside the
GOT.
2.7 System Configuration Examples)
CONNECTION TO
EXTERNAL I/O
DEVICE
Write command
S
E
T RW 0100 000A 0163 0362 T
X
X
7
D3
8
Microcomputer board
1. PREPARATORY PROCEDURES FOR MONITORING
1.6 Checking for Normal Monitoring
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(
CONNECTION TO
SOUND OUTPUT
UNIT
6
1 - 37
1.6.2
Confirming the communication state on the GOT side (For Ethernet
connection)
 Confirming the communication state in Windows®, GT Designer3
(1) When using the Command Prompt of Windows®
Execute a Ping command at the Command Prompt of Windows®.
(a) When normal communication
C:\>Ping 192.168.0.18
Reply from 192.168.0.18: bytes=32 time<1ms TTL=64
(b) When abnormal communication
C:\>Ping 192.168.0.18
Request timed out.
(2) When using the [PING Test] of GT Designer3
Select [Communication]
[PING Test].
[Communication configuration]
1.
2.
[Ethernet] and
[Connection Test] to display
Specify the [GOT IP Address] of the [PING
Test] and click the [PING Test] button.
The [Test Result] is displayed after the [PING
Test] is finished.
2.
Click!
1.
(3) When abnormal communication
At abnormal communication, check the followings and execute the Ping command again.
• Mounting condition of Ethernet communication unit
• Cable connecting condition
• Confirmation of [Communication Settings]
• IP address of GOT specified by Ping command
1 - 38
1. PREPARATORY PROCEDURES FOR MONITORING
1.6 Checking for Normal Monitoring
1
PREPARATORY
PROCEDURES FOR
MONITORING
 Confirming the communication state in the GOT module (For GT16, GT14)
The Ping test can be confirmed by the Utility screen of the GOT.
For the operation method of GOT Utility, refer to the following.
GT16 User's Manual (Basic Utility)
GT14 User's Manual
MICROCOMPUTER
CONNECTION
(SERIAL)
2
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
MODBUS(R)/RTU
CONNECTION
4
MODBUS(R)/TCP
CONNECTION
5
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
1. PREPARATORY PROCEDURES FOR MONITORING
1.6 Checking for Normal Monitoring
1 - 39
1.6.3
Confirming the communication state with each station (station monitoring
function)
The station monitoring function detects the faults (communication timeout) of the stations monitored by the GOT.
When detecting the abnormal state, it is assigning the information of the faulty station to the GOT special register
(GS).
(1) No. of faulty stations
(a) For the Ethernet connection (except for the Ethernet multiple connection)
The total No. of the faulty CPUs is stored.
Device
b15 to b8
b7 to b0
GS230
(00Hfixed)
No. of faulty stations
(b) For the Ethernet multiple connection
The total No. of the faulty devices is stored.
Channel
Device
b15 to b8
b7 to b0
Ch1
GS280
(00Hfixed)
No. of faulty stations
Ch2
GS300
(00Hfixed)
No. of faulty stations
Ch3
GS320
(00Hfixed)
No. of faulty stations
Ch4
GS340
(00Hfixed)
No. of faulty stations
POINT
When monitoring GS230 on Numerical Display
When monitoring GS230 on Numerical Display, check [mask processing] with data operation tab as the following.
For the data operation, refer to the following manual.
GT Designer3 Version1 Screen Design Manual
Numerical Display (Data Operation tab)
Set [mask processing] to the upper eight bits (b8
to b15) of GS230 on Numerical Display.
1 - 40
1. PREPARATORY PROCEDURES FOR MONITORING
1.6 Checking for Normal Monitoring
1
PREPARATORY
PROCEDURES FOR
MONITORING
(2) Faulty station information
The bit corresponding to the faulty station is set. (0: Normal 1: Abnormal)The bit is reset after the fault is
recovered.
(a) For the Ethernet connection (except for the Ethernet multiple connection).
2
MICROCOMPUTER
CONNECTION
(SERIAL)
GS231 bit 0
GS231 bit 1
GS231 bit 2
GS231 bit 3
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
b11
b10
b9
b8
b7
b6
b5
b4
b3
b2
b1
b0
13
12
11
10
9
8
7
6
5
4
3
2
1
GS232
32
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
GS233
48
47
46
45
44
43
42
41
40
39
38
37
36
35
34
33
GS234
64
63
62
61
60
59
58
57
56
55
54
53
52
51
50
49
GS235
80
79
78
77
76
75
74
73
72
71
70
69
68
67
66
65
GS236
96
95
94
93
92
91
90
89
88
87
86
85
84
83
82
81
GS237
112
111
110
109
108
107
106
105
104
103
102
101
100
99
98
97
GS238
128
127
126
125
124
123
122
121
120
119
118
117
116
115
114
113
(b) For the Ethernet multiple connection or the temperature controller connection
The station number to which each device corresponds changes according to the connection/non
connection with Ethernet.
With Ethernet connection: 1 to 128
With other than Ethernet connection: 0 to 127
Example) With Ethernet connection, when PC No. 100 CPU connecting to Ch3 is faulty, GS327.b3 is set.
The following table shows the case with Ethernet connection.
Device
Station No.
Ch1
Ch2
Ch3
Ch4
b15
b14
b13
b12
b11
b10
b9
b8
b7
b6
b5
b4
b3
b2
b1
b0
GS281
GS301
GS321
GS341
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
GS282
GS302
GS322
GS342
32
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
GS283
GS303
GS323
GS343
48
47
46
45
44
43
42
41
40
39
38
37
36
35
34
33
GS284
GS304
GS324
GS344
64
63
62
61
60
59
58
57
56
55
54
53
52
51
50
49
GS285
GS305
GS325
GS345
80
79
78
77
76
75
74
73
72
71
70
69
68
67
66
65
GS286
GS306
GS326
GS346
96
95
94
93
92
91
90
89
88
87
86
85
84
83
82
81
GS287
GS307
GS327
GS347
112
111
110
109
108
107
106
105
104
103
102
101
100
99
98
97
GS288
GS308
GS328
GS348
128
127
126
125
124
123
122
121
120
119
118
117
116
115
114
113
For details on the GS Device, refer to the following manual.
GT Designer3 Screen Design Manual (Fundamentals) Appendix.2.3 GOT special register (GS)
1. PREPARATORY PROCEDURES FOR MONITORING
1.6 Checking for Normal Monitoring
1 - 41
4
MODBUS(R)/RTU
CONNECTION
b12
14
5
MODBUS(R)/TCP
CONNECTION
b13
15
6
CONNECTION TO
SOUND OUTPUT
UNIT
b14
16
7
CONNECTION TO
EXTERNAL I/O
DEVICE
b15
GS231
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Ethernet setting No.
Device
(3) Network No., station No. notification
The network No. and station No. of the GOT in Ethernet connection are stored at GOT startup.
If connected by other than Ethernet, 0 is stored.
Device
1 - 42
Description
CH1
CH2
CH3
CH4
GS376
GS378
GS380
GS382
Network No. (1 to 239)
GS377
GS379
GS381
GS383
Station No. (1 to 64)
1. PREPARATORY PROCEDURES FOR MONITORING
1.6 Checking for Normal Monitoring
1
Check on the PLC
PREPARATORY
PROCEDURES FOR
MONITORING
1.6.4
 Read IC tag (For RFID connection)
Read IC tag with a RFID reader/writer and check that the read data are written into the PLC CPU.
Detailed settings including sequence programs, device settings and other settings required for monitoring, refer to
the following manual.
GT Designer3 Version1 Screen Design Manual (Functions)
MICROCOMPUTER
CONNECTION
(SERIAL)
2
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
MODBUS(R)/RTU
CONNECTION
4
MODBUS(R)/TCP
CONNECTION
5
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
1. PREPARATORY PROCEDURES FOR MONITORING
1.6 Checking for Normal Monitoring
1 - 43
1 - 44
1. PREPARATORY PROCEDURES FOR MONITORING
1.6 Checking for Normal Monitoring
MICROCOMPUTER
CONNECTION
2.
MICROCOMPUTER CONNECTION (SERIAL) . . . . . . . . . . 2 - 1
3.
MICROCOMPUTER CONNECTION (ETHERNET). . . . . . . 3 - 1
2
PREPARATORY
PROCEDURES FOR
MONITORING
1
MICROCOMPUTER
CONNECTION
(SERIAL)
2
MICROCOMPUTER
CONNECTION (SERIAL)
2.
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
4
MODBUS(R)/RTU
CONNECTION
2.1 Microcomputer Connection (Serial) . . . . . . . . . . . . . . . . . . . 2 - 2
2.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 4
2.3 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 6
2.4 Device Data Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 10
5
MODBUS(R)/TCP
CONNECTION
2.5 Message Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 23
2.6 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 77
2.7 System Configuration Examples . . . . . . . . . . . . . . . . . . . . 2 - 79
2.8 Device Range that Can Be Set . . . . . . . . . . . . . . . . . . . . . 2 - 82
6
CONNECTION TO
SOUND OUTPUT
UNIT
2.9 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 - 83
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
2-1
2.
MICROCOMPUTER CONNECTION
(SERIAL)
2.1 Microcomputer Connection (Serial)
The "microcomputer connection (Serial)" is a function by
which data can be written or read from a PC,
microcomputer board, PLC, etc. (hereinafter referred to as
"host") to virtual devices of the GOT.
 Flow of data processing
(1) When reading or writing data
Interrupt output is also available from the GOT to the host.
GOT
Virtual devices inside GOT
Screen data
D0
D0 to 4095
Screen display
D100
000A
Device data area
(Virtual devices)*2
Display(D4 to 9)
04/06/01 18:46:49
D163
0362
4.
Input(D20)
D4095
2.
1254
Write,Read Command
Interrupt
output
1. Request
message
3. Response
message
*1
S
E
T RW 0100 000A 0163 0362 T D3
X
X
*1
Host
Microcomputer board
POINT
Virtual devices inside the GOT
The devices inside the GOT are used in the
microcomputer connection.
(PLC devices are not used)
1.
2.
2.4 Device Data Area
3.
4.
2-2
2. MICROCOMPUTER CONNECTION (SERIAL)
2.1 Microcomputer Connection (Serial)
The host sends a request message (the read/write
command) to the GOT.
The GOT performs a read/write processing to its
virtual devices according to the request from the host.
Upon completion of the processing, the GOT sends a
response message (processing result) to the host.
Creating the following objects on the screen allows
you to use the data read/written to the virtual devices:
• Numerical Display that displays data written by the
write command
• Numerical Input that is used to input data to be
upload to the host
1
PREPARATORY
PROCEDURES FOR
MONITORING
(2) When outputting interrupts
GOT
Screen data
1.
Device data area
(virtual devices)*2
Interrupt(D13)
output value1
D13
2
3139H
MICROCOMPUTER
CONNECTION
(SERIAL)
Screen display
output value2
31H
39H
2. Interrupt output
*1
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
(When the number of
interrupt data bytes is 2)
Host
5
2.5 Message Formats
2.4 Device Data Area
6
CONNECTION TO
SOUND OUTPUT
UNIT
*1
*2
MODBUS(R)/TCP
CONNECTION
The GOT sends the written data (interrupt output) to
the host.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
2.
Data are written to the virtual devices for interrupt
output from the touch switches on the GOT.
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
1.
MODBUS(R)/RTU
CONNECTION
4
2. MICROCOMPUTER CONNECTION (SERIAL)
2.1 Microcomputer Connection (Serial)
2-3
2.2 System Configuration
2.2.1
For the microcomputer connection (serial)
 When connecting one GOT
Communication driver
Computer
Host
GOT
Connection cable
Host
Connection cable
Communication
Type
Max.
distance
RS-232
Differs
according to
host side
specifications
GOT
Connection diagram number
Option device
Number of
connectable
equipment
Model
- (Built into GOT)
RS-232 connection diagram 1)
GT15-RS2-9P
RS-232 connection diagram 2)
- (Built into GOT)
RS-422 connection diagram 1)
- (Built into GOT)
1 GOT for 1 host
GT16-C02R4-9S(0.2m)
RS-422
Differs
according to
host side
specifications
GT15-RS2T4-9P*1
RS-422 connection diagram 2)
GT15-RS4-9S
- (Built into GOT)
RS-422 connection diagram 3)
*1
2-4
- (Built into GOT)
Connect it to the RS-232 interface (built into GOT). It cannot be mounted on GT1655 and GT155
2. MICROCOMPUTER CONNECTION (SERIAL)
2.2 System Configuration
.
Communication driver
Computer
2
MICROCOMPUTER
CONNECTION
(SERIAL)
GOT
(n+1th)
GOT
(n-th)
Connection cable
Connection type
Option device
Model
Commun
ication
Type
Cable model
Max.
distance
GT10-C30R2-6P(3m)*2
3m
GT10-C02H-6PT9P(0.2m)
+
RS-232
RS-422
- (Built into
GOT)
RS-232
GT01-C30R2-6P(3m)
GT10-C02H-6PT9P(0.2m)
+
For the system configuration
between the GOT and host,
refer to the following.
RS-232 connection
diagram 7)
When connecting one
GOT
RS-232 connection
diagram 6)
RS-232
RS-422
- (Built into
GOT)
- (Built into
GOT)
RS-422
RS-232
15m
Option
device
- (Built into
GOT)
4
*3
3m
15m
- (Built into
GOT)
4 GOT for 1
host
30m
- (Built into
GOT)
RS-422 connection
diagram 5)
30m
- (Built into
GOT)
RS-232 connection
diagram 4)
15m
- (Built into
GOT)
RS-232 connection
diagram 5)
15m
RS-422 connection
diagram 4)
Model
Number of
connectable
equipment
*4
*3
6
- (Built into
GOT)
*1
This is the connection type (for n-th and n+1th from the host) of GOT, which is connected to the host.
*2
For the connection to GOT, refer to the connection diagram. (
*3
*4
The n+1th GOT must be a RS-232 built-in product.
The n+1th GOT must be a RS-422 built-in product (input power supply: 24V).
5
MODBUS(R)/TCP
CONNECTION
Commun
ication
Type
GOT (n+1th) *1
Connection cable
CONNECTION TO
SOUND OUTPUT
UNIT
GOT (n-th) *1
Host
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
Varies according to
the connection type.
MODBUS(R)/RTU
CONNECTION
Host
PREPARATORY
PROCEDURES FOR
MONITORING
1
 When connecting multiple GOTs
RS-232 connection diagram 3))
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
2. MICROCOMPUTER CONNECTION (SERIAL)
2.2 System Configuration
2-5
2.3 Connection Diagram
The following diagram shows the connection between the
GOT and the microcomputer.
RS-232 connection diagram 2)
(For GT1030, GT1020)
2.3.1
Example of the case where the DTR/DSR signal is not used
RS-232 cable
GOT side
(terminal block)
 Connection diagram
RS-232 connection diagram 1)
(For GT16, GT15, GT14, GT12, GT11, GT105 ,
GT104 )
Example of the case where the DTR/DSR signal is not used
GOT side
Host side
CD/NC*1
1
FG
RD(RXD)
2
SD(TXD)
SD(TXD)
3
RD(RXD)
ER(DTR)
4
RS(RTS)
SG
5
SG
DR(DSR)
6
CS(CTS)
RS(RTS)
7
-
CS(CTS)
8
-
-
9
ER(DTR)
Host side
SD
RD(RXD)
RD
SD(TXD)
ER
RS(RTS)
DR
CS(CTS)
SG
SG
RS
-
CS
-
NC
ER(DTR)
NC
FG
Example of the case where the DTR/DSR signal is used
*1
GOT side
(terminal block)
GT16: CD, GT15: CD, GT14: NC, GT12: NC, GT11: NC,
GT105 : NC, GT104 : NC
Example of the case where the DTR/DSR signal is used
GOT side
Host side
Host side
SD
RD(RXD)
RD
SD(TXD)
ER
DR(DSR)
DR
ER(DTR)
SG
SG
RS
RS(RTS)
*1
CD/NC
1
FG
CS
CS(CTS)
RD(RXD)
2
SD(TXD)
NC
5V
SD(TXD)
3
RD(RXD)
NC
FG
ER(DTR)
4
DR(DSR)
SG
5
SG
DR(DSR)
6
ER(DTR)
RS(RTS)
7
RS(RTS)
CS(CTS)
8
CS(CTS)
-
9
5V
*1
RS-232 connection diagram 3)
(For GT1030, GT1020)
Connection diagram for connecting GT10-C30R2-6P to GT1030 or GT1020
Unfastened cable color of
GT10-C30R2-6P
n+1th GOT side
(terminal block)
Brown
SD
Red
RD
Blue
ER
Yellow
DR
Green
SG
Purple
RS
GT16: CD, GT15: CD, GT14: NC, GT12: NC, GT11: NC,
GT105 : NC, GT104 : NC
CS
NC
NC
2-6
2. MICROCOMPUTER CONNECTION (SERIAL)
2.3 Connection Diagram
,
side
to GT1030 or
GT103
GT102
,
side
N.C.
1
RS(RTS)
RD(RXD)
2
SD(TXD)
SD(TXD)
3
RD(RXD)
ER(DTR)
4
DR(DSR)
SG
5
SG
DR(DSR)
6
ER(DTR)
RS(RTS)
7
CS(CTS)
CS(CTS)
8
N.C.
9
N.C.
Cable (GT10-C02H-6PT9P)
9-pin D-sub side
2nd GOT side
N.C.
1
1
RD(RXD)
2
3
SD(TXD)
SD(TXD)
3
2
RD(RXD)
ER(DTR)
4
6
DR(DSR)
SG
5
5
SG
DR(DSR)
6
4
ER(DTR)
RS(RTS)
7
8
CS(CTS)
CS(CTS)
8
7
RS(RTS)
N.C.
9
 Precautions when preparing a cable
The length of the RS-232 cable must be 15m or less.
(For GT105 , GT104 )
Connection diagram for connecting GT105
or GT104
to GT105
or
GT104
2
3
(1) Cable length
RS-232 connection diagram 5)
PREPARATORY
PROCEDURES FOR
MONITORING
GT105
GT104
or GT104
MICROCOMPUTER
CONNECTION
(SERIAL)
(For GT105 , GT104 , GT1030, GT1020)
Connection diagram for connecting GT105
GT1020
1
RS-232 connection diagram 7)
(2) GOT side connector
MICROCOMPUTER
CONNECTION
(ETHERNET)
RS-232 connection diagram 4)
4
For the GOT side connector, refer to the following.
N.C.
1
1
N.C.
RD(RXD)
2
3
SD(TXD)
SD(TXD)
3
2
RD(RXD)
ER(DTR)
4
6
DR(DSR)
SG
5
5
SG
DR(DSR)
6
4
ER(DTR)
RS(RTS)
7
8
CS(CTS)
CS(CTS)
8
7
RS(RTS)
9
9
5
MODBUS(R)/TCP
CONNECTION
GOT side
MODBUS(R)/RTU
CONNECTION
1.4.1 GOT connector specifications
GOT side
6
2nd GOT side
(terminal block)
1
6
RS
RD(RXD)
2
1
SD(TXD)
SD(TXD)
3
2
RD(RXD)
ER(DTR)
4
4
DR(DSR)
SG
5
5
SG
DR(DSR)
6
3
ER(DTR)
RS(RTS)
7
7
CS(CTS)
CS(CTS)
8
8
N.C.
9
9
N.C.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
N.C.
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Cable (GT10-C02H-6PT9P)
9-pin D-sub side
CONNECTION TO
SOUND OUTPUT
UNIT
RS-232 connection diagram 6)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.3 Connection Diagram
2-7
2.3.2
RS-422 cable
RS-422 connection diagram 3)
(For GT1030, GT1020)
 Connection diagram
GOT side
RS-422 connection diagram 1)
(For GT16)
GOT side
Host side
Host side
RDA
SDA
RDB
SDB
SDA
RDA
SDB
RDB
RSA
-
RSB
-
CSA
-
SDA1(TXD1+)
1
RDA
SDB1(TXD1-)
2
RDB
RDA1(RXD1+)
3
SDA
RDB1(RXD1-)
4
SDB
SDA2(TXD2+)
5
-
SDB2(TXD2-)
6
-
RDA2(RXD2+)
7
-
RDB2(RXD2-)
8
-
RSA(RTS+)
9
-
RS-422 connection diagram 4)
RSB(RTS-)
10
-
(For GT105 , GT104 , GT1030, GT1020)
CSA(CTS+)
11
-
Connection diagram for connecting GT105
GT1020
CSB(CTS-)
12
-
SG
13
SG
NC
14
-
SG
SHELL
GT105 ,
GT104 side
Shell
RS-422 connection diagram 2)
(For GT16, GT15, GT14, GT12, GT11, GT105 ,
GT104 )
GOT side
CSB
Host side
to GT1030 or
GT103 ,
GT102 side
(terminal block)
RXD+(RDA)
2
TXD+(SDA)
RXD-(RDB)
7
TXD-(SDB)
TXD+(SDA)
1
RXD+(RDA)
TXD-(SDB)
6
RXD-(RDB)
SG
5
SG
CTS+(CSA)
4
RTS+(RSA)
CTS-(CSB)
9
RTS-(RSB)
RTS+(RSA)
3
CTS+(CSA)
RTS-(RSB)
8
CTS-(CSB)
RDA
2
SDA
RDB
7
SDB
SDA
1
RDA
SDB
6
RDB
RSA
3
-
RS-422 connection diagram 5)
RSB
8
-
(For GT105 , GT104 )
CSA
4
-
CSB
9
-
SG
5
SHELL
2-8
or GT104
Connection diagram for connecting GT105
or GT104
to GT105
or
GT104
2. MICROCOMPUTER CONNECTION (SERIAL)
2.3 Connection Diagram
GOT side
GOT side
TXD+(SDA)
1
2
RXD+(RDA)
RXD+(RDA)
2
1
TXD+(SDA)
RTS+(RSA)
3
4
CTS+(CSA)
CTS+(CSA)
4
3
RTS+(RSA)
SG
5
5
SG
TXD-(SDB)
6
7
RXD-(RDB)
RXD-(RDB)
7
6
TXD-(SDB)
RTS-(RSB)
8
9
CTS-(CSB)
CTS-(CSB)
9
8
RTS-(RSB)
1
PREPARATORY
PROCEDURES FOR
MONITORING
POINT
The polarity A and B in signal names may be reversed
depending on the microcomputer to be used.
Prepare a cable according to the microcomputer to be
used.
MICROCOMPUTER
CONNECTION
(SERIAL)
2
 Precautions when preparing a cable
(1) Cable length
The distance between the GOT and the PLC of
connection diagram 1), 2) and 3) must be 1200 m or
less.
The length of the RS-422 connection diagram 4) or RS422 connection diagram 5) must be 30m or less.
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
(2) GOT side connector
For the GOT side connector, refer to the following.
1.4.1 GOT connector specifications
 Connecting terminating resistors
4
(1) GOT side
MODBUS(R)/RTU
CONNECTION
When connecting a microcomputer to the GOT, a
terminating resistor must be connected to the GOT.
(a) For GT16, GT15, GT12
Set the terminating resistor setting switch of the
GOT main unit to "Disable".
(b) For GT14, GT11, GT10
Set the terminating resistor selector to "330 ".
For the procedure to set the terminating resistor, refer
to the following.
MODBUS(R)/TCP
CONNECTION
5
1.4.3 Terminating resistors of GOT
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
2. MICROCOMPUTER CONNECTION (SERIAL)
2.3 Connection Diagram
2-9
2.4 Device Data Area
The following shows a list of virtual devices inside the GOT available in the microcomputer connection (serial), and the
address specification values for each data format.
The address specification of the virtual devices differs depending on the data format.*1
Virtual device*2
Model
Address specification value
Name
Device
range
(decimal)
Device
type
Format
1, 2
Format
3 to 6
Format
7 to 10
Format
11 to 13
Format
14, 15
D
0 to 4095
Word
0 to 4095
D0 to 4095
D0 to 4095
0000 to 0FFFH
8000 to 9FFFH
2.4.1
R
0 to 4095
Word
4096 to 8191
R0 to 4095
R0 to 4095
1000 to 1FFFH
0000 to 1FFFH
2.4.2
L
0 to 2047
Bit
8192 to 8319
L0 to 2047
L0 to 2047
2000 to 207FH
A000 to A0FFH
2.4.3
M0 to 2047
20FFH
2000 to 20FFH
2.4.4
M
0 to 2047
Bit
8320 to 8447
M0 to 2047
SD0 to 15
2100 to 210FH
SM0 to 63
2110 to 2113H
SD
0 to 15
Word
8448 to 8463
D9000 to
9015
SM
0 to 63
Bit
8464 to 8467
M9000 to
9063
D
0 to 511
Word
0 to 511
R
0 to 4095
Word
4096 to 8191
2080 to
2100 to 211FH
Refer to
(3000 to 300DH)*3
2.4.5
2200 to 2207H
2.4.6
-
8000 to 83FFH
2.4.1
-
0000 to 1FFFH
2.4.2
L
0 to 2047
Bit
8192 to 8319
-
A000 to A0FFH
2.4.3
M
0 to 2047
Bit
8320 to 8447
-
2000 to 20FFH
2.4.4
SD
0 to 15
Word
8448 to 8463
-
SM
0 to 63
Bit
8464 to 8467
-
*1
2100 to 211FH
(3000 to 300DH)*3
2.4.5
2200 to 2207H
2.4.6
For the address specification method for each data format, refer to the following.
2.5 Message Formats
•
•
•
•
•
*2
Formats 1, 2
Formats 3 to 6
Formats 7 to 10
Formats 11 to 13
Formats 14, 15
:
:
:
:
:
GOT-A900 Series microcomputer connection
A compatible 1C frame
QnA compatible 3C/4C frame
Digital Electronics Corporation's memory link method
GOT-F900 Series microcomputer connection
When reusing GOT900 Series project data
• GOT-A900 Series virtual devices (D0 to 2047)
Can be used as they are without changing the assignments.
• GOT-F900 Series virtual devices
Since some of the assigned virtual device values differ as indicated below, change the assignment using device batch edit of
GT Designer3.
Refer to the following manual for device batch edit of GT Designer3.
GT Designer3 Version1 Screen Design Manual
*3
GOT1000 Series virtual devices
GOT-F900 Series virtual devices
D0 to 2047
―
D2048 to 4095
―
R0 to 4095
D0 to 4095
L0 to 2047
―
M0 to 2047
M0 to 2047
SD0 to 15
D8000 to 8015
GD0 to 6
SM0 to 63
M8000 to 8063
Access to SD3 to 9 can also be made by the specification of the addresses (3000 to 300DH) of GD0 to 6 on the GOT-F900 Series.
POINT
Values of virtual devices inside the GOT
When the GOT is turned OFF or reset, values are cleared to their defaults
(bit devices: OFF, word devices: 0).
Values are held in the memory when project data are written to the GOT.
2 - 10
2. MICROCOMPUTER CONNECTION (SERIAL)
2.4 Device Data Area
 List of D devices
The following lists the D devices (virtual devices inside the GOT).
Address
Description
Set side
D0 to 2
Unused
―
Communication error status
Stores the communication error details of GOT.
0: Normal
1: Error
b8 b7 b6 b5 b4 b3
–
3
b0
MICROCOMPUTER
CONNECTION
(ETHERNET)
–
Unused
D3
SIO framing error
SIO parity error
SIO overrun error
Communication timeout
error
Unused
MODBUS(R)/RTU
CONNECTION
4
• b4 to 6 turn ON when an SIO error occurs, and turn OFF when an request message from the host is received
successfully after the error occurrence.
• b7 turns ON about 3 seconds after the host side DTR becomes OFF, and turns OFF when transmission is
performed successfully to the host after the error occurrence.
Clock data (year)
b15
–
b8 b7
–
5
b0
System
D4
Lower 2 digits of calendar
year stored as 2-digit BCD
Unused
6
Clock data (month)
–
b8 b7
–
b0
CONNECTION TO
SOUND OUTPUT
UNIT
b15
MODBUS(R)/TCP
CONNECTION
b15
2
MICROCOMPUTER
CONNECTION
(SERIAL)
The D devices are word devices into which GOT communication errors, clock data or other information are stored.
The user can also store data using the user area.
PREPARATORY
PROCEDURES FOR
MONITORING
1
D devices
D5
Data of months 01 to
12 stored as 2-digit BCD
Unused
7
b15
–
b8 b7
–
CONNECTION TO
EXTERNAL I/O
DEVICE
Clock data (day)
b0
D6
Data of days 01 to
31 stored as 2-digit BCD
8
Unused
(Continued to next page)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.4 Device Data Area
2 - 11
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
2.4.1
(From previous page)
Address
Description
Set side
Clock data (hour)
b15
–
–
b8 b7
b0
D7
Data of hours 00 to
23 stored as 2-digit BCD
Unused
Clock data (minute)
b15
–
–
b8 b7
b0
D8
Data of minutes 00 to
59 stored as 2-digit BCD
Unused
Clock data (second)
System
b15
–
–
b8 b7
b0
D9
Data of seconds 00 to
59 stored as 2-digit BCD
Unused
Clock data (day of week)*1
b15
–
b8 b7
–
b0
Day-of-week data stored as
2-digit BCD
D10
00: Sunday 01: Monday
02: Tuesday 03: Wednesday
04: Thursday 05: Friday
06: Saturday
Unused
D11, D12
Unused
―
(Continued to next page)
*1
2 - 12
If a wrong day of the week is set by the clock data setting commands, the clock data will differ from the time displayed on the
utility.
Example: When June 1, 2004 (Thursday) is set by the clock data setting command (the actual day of the week is Tuesday),
"04" is stored to D10 although Tuesday (TUE) will be displayed on the utility time display.
2. MICROCOMPUTER CONNECTION (SERIAL)
2.4 Device Data Area
Address
Description
Set side
Interrupt output
When data are written to D13 and D14 from a GOT touch switch, for example, the data of D13
and D14 are transmitted (interrupt output) to the host side.*1*2
The data amount (number of bytes) to be interrupt-output is set at "Interrupt Data Byte" in
"Communication Detail Settings".(
settings))
2
2.6.1 Setting communication interface (Communication
MICROCOMPUTER
CONNECTION
(SERIAL)
D13
• Output value when 1 is set to "Interrupt Data Byte" in "Communication Detail Settings"
D13
Lower 8 bits
• Output value when 2 is set to "Interrupt Data Byte" in "Communication Detail Settings"
D13
User
2 bytes
4
D14
MODBUS(R)/RTU
CONNECTION
• Output value when 4 is set to "Interrupt Data Byte" in "Communication Detail Settings
"(1) When setting the LH order to [32bit Storage] for the communication detail settings
D13
D14
Upper 8 bits
Lower 8 bits
Upper 8 bits
Lower 8 bits
4 bytes
(2) When setting the HL order to [32bit Storage] for the communication detail settings
D13
Upper 8 bits
5
D14
Lower 8 bits
Upper 8 bits
Lower 8 bits
4 bytes
Unused
―
D20 to 2031
User area
User
D2032 to 2034
Unused
―
D2035
1-second binary counter
The counter is incremented at 1-second intervals after the GOT is turned ON.
(The time elapsed after GOT is turned ON is stored in 1-second units.)
Data are stored in binary format.
System
User area
User
D20 to 511
User area
User
7
After writing data, the interrupt data is output within a period of 1 to 10ms.
When data are written to D13 and D14 from the host side, interrupt output is not performed.
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
*1
*2
6
CONNECTION TO
EXTERNAL I/O
DEVICE
D2036 to 4095
MODBUS(R)/TCP
CONNECTION
Lower 8 bits
CONNECTION TO
SOUND OUTPUT
UNIT
Upper 8 bits
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
1 byte
D15 to 19
1
PREPARATORY
PROCEDURES FOR
MONITORING
(From previous page)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.4 Device Data Area
2 - 13
POINT
(1) The side where virtual devices are set
System : Set on the system side.
User
: Set on the user side (by sending request messages from host or using the touch switches, etc.
on the GOT).
(2) Interrupt output (D13, D14)
• To disable the interrupt output, turn ON SM52 (interrupt code output disable flag). (
2.4.6 SM devices)
• To enable the interrupt output, set 8 bits to the data length at "Communication Detail Settings".
(
2.6.1 Setting communication interface (Communication settings))
• When "7 bits" is set, the MSB (8th bit) is ignored. (Example: FFH 7FH)
 Differences in address specifications by data format
The address specification of devices varies depending on the data format.*1
The following shows the address specification values for each data format.
Address specification value
Model
Address
Format
1, 2
Format
3 to 6
Format
7 to 10
Format
11 to 13
D0
0
D0
D0
0000H
Format
14, 15
8000H
8000H
8001H
8001H
Upper 8 bits
Lower 8 bits
8002H
D1
1
D1
D1
8003H
:
:
:
:
:
D4095
4095
D4095
D4095
0FFFH
D0
0
1
9FFEH
9FFFH
9FFFH
Upper 8 bits
Lower 8 bits
8000H
8000H
8001H
8001H
Upper 8 bits
Lower 8 bits
-
8003H
D511
511
-
83FEH
83FFH
83FFH
Upper 8 bits
Lower 8 bits
GOT-A900 Series microcomputer connection
A compatible 1C frame
QnA compatible 3C/4C frame
Digital Electronics Corporation's memory link method
GOT-F900 Series microcomputer connection
2. MICROCOMPUTER CONNECTION (SERIAL)
2.4 Device Data Area
Lower 8 bits
83FEH
For the address specification method for each data format, refer to the following.
:
:
:
:
:
Upper 8 bits
:
2.5 Message Formats
2 - 14
8002H
-
:
Formats 1, 2
Formats 3 to 6
Formats 7 to 10
Formats 11 to 13
Formats 14, 15
Lower 8 bits
-
:
•
•
•
•
•
Upper 8 bits
9FFEH
8003H
*1
8003H
:
8002H
D1
8002H
0001H
1
PREPARATORY
PROCEDURES FOR
MONITORING
R devices
The R devices are word devices into which user data are stored.
All of these devices can be used as a user area.
 List of R devices and differences in address specification by data format
The following shows the R devices (virtual devices inside the GOT).
Format
1, 2
Format
3 to 6
Format
7 to 10
Format
11 to 13
R0
4096
R0
R0
1000H
R1
4097
R1
R1
:
:
:
:
R4095
8191
R4095
R4095
1FFFH
4096
R1
0000H
0001H
0001H
Upper 8 bits
Lower 8 bits
0002H
0002H
0003H
0003H
Upper 8 bits
Lower 8 bits
:
1FFEH
1FFEH
1FFFH
1FFFH
Upper 8 bits
Lower 8 bits
0000H
0000H
0001H
0001H
Upper 8 bits
Lower 8 bits
0002H
0002H
0003H
0003H
Upper 8 bits
Lower 8 bits
-
4097
-
:
:
-
R4095
8191
-
:
1FFEH
1FFEH
1FFFH
1FFFH
Upper 8 bits
Lower 8 bits
For the address specification method for each data format, refer to the following.
5
CONNECTION TO
SOUND OUTPUT
UNIT
GOT-A900 Series microcomputer connection
A compatible 1C frame
QnA compatible 3C/4C frame
Digital Electronics Corporation's memory link method
GOT-F900 Series microcomputer connection
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Formats 1, 2
:
Formats 3 to 6 :
Formats 7 to 10 :
Formats 11 to 13 :
Formats 14, 15 :
4
6
2.5 Message Formats
•
•
•
•
•
3
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
*1
0000H
1001H
:
R0
Format
14, 15
MICROCOMPUTER
CONNECTION
(ETHERNET)
Address
MODBUS(R)/RTU
CONNECTION
Address specification value
Model
MICROCOMPUTER
CONNECTION
(SERIAL)
2
The address specification values different depending on the data format are also given below.*1
MODBUS(R)/TCP
CONNECTION
2.4.2
2. MICROCOMPUTER CONNECTION (SERIAL)
2.4 Device Data Area
2 - 15
2.4.3
L devices
The L devices are bit devices into which user data are stored.
All of these devices can be used as a user area.
 List of L devices and differences in address specification by data format
The following shows the L devices (virtual devices inside the GOT).
The address specification values different depending on the data format are also given below.*1
Address
Model
Address specification value
b7
b6
b5
b4
b3
b2
b1
b0
L7
L6
L5
L4
L3
L2
L1
L0
L15
L14
L13
L12
L11
L10
L9
L8
L23
L22
L21
L20
L19
L18
L17
L16
L31
L30
L29
L28
L27
L26
L25
L24
:
L2039
L2038
L2037
L2036
L2035
L2034
L2033
L2032
L2046
L2045
L2044
L2043
L2042
L2041
L2040
L7
L6
L5
L4
L3
L2
L1
L0
L15
L14
L13
L12
L11
L10
L9
L8
L23
L22
L21
L20
L19
L18
L17
L16
L31
L30
L29
L28
L27
L26
L25
L24
:
8193
L2038
L2037
L2036
L2035
L2034
L2033
L2032
L2047
L2046
L2045
L2044
L2043
L2042
L2041
L2040
Format
7 to 10
8192
8193
8319
Format
11 to 13
2000H
Same as address
column on left
2001H
*2
:
8319
:
L2039
Format
3 to 6
8192
:
L2047
*1
Format
1, 2
207FH
*2
2 - 16
:
:
:
:
:
A002H
A003H
:
A0FEH
A0FFH
-
A001H
-
A002H
-
A003H
-
:
-
A0FEH
-
A0FFH
GOT-A900 Series microcomputer connection
A compatible 1C frame
QnA compatible 3C/4C frame
Digital Electronics Corporation's memory link method
GOT-F900 Series microcomputer connection
For reading or writing data in word units, specify the addresses in 16-point units. (Example: L0, L16, L32, etc.)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.4 Device Data Area
A001H
A000H
2.5 Message Formats
Formats 1, 2
Formats 3 to 6
Formats 7 to 10
Formats 11 to 13
Formats 14, 15
A000H
-
For the address specification method for each data format, refer to the following.
•
•
•
•
•
Format
14, 15
1
PREPARATORY
PROCEDURES FOR
MONITORING
M devices
The M devices are bit devices into which user data are stored.
All of these devices can be used as a user area.
 List of M devices and differences in address specification by data format
The following shows the M devices (virtual devices inside the GOT).
Address specification value
b7
b6
b5
b4
b3
b2
b1
b0
M7
M6
M5
M4
M3
M2
M1
M0
M15
M14
M13
M12
M11
M10
M9
M8
M23
M22
M21
M20
M19
M18
M17
M16
M31
M30
M29
M28
M27
M26
M25
M24
:
M2039
M2038
M2037
M2036
M2035
M2034
M2033
M2032
M2046
M2045
M2044
M2043
M2042
M2041
M2040
M7
M6
M5
M4
M3
M2
M1
M0
M15
M14
M13
M12
M11
M10
M9
M8
M23
M22
M21
M20
M19
M18
M17
M16
M31
M30
M29
M28
M27
M26
M25
M24
:
M2037
M2036
M2035
M2034
M2033
M2032
M2046
M2045
M2044
M2043
M2042
M2041
M2040
*1
Format
7 to 10
2080H
Same as address
column on left
*2
8321
8447
2081H
:
8447
8320
Format
11 to 13
20FFH
Format
14, 15
2000H
2H001H
2002H
2003H
:
20FEH
20FFH
-
2000H
-
2001H
-
2002H
-
2003H
-
:
-
20FEH
-
20FFH
For the address specification method for each data format, refer to the following.
3
4
5
•
•
•
•
•
:
:
:
:
:
GOT-A900 Series microcomputer connection
A compatible 1C frame
QnA compatible 3C/4C frame
Digital Electronics Corporation's memory link method
GOT-F900 Series microcomputer connection
For reading or writing data in word units, specify the addresses in 16-point units.(Example: M0, M16, M32, and others)
CONNECTION TO
SOUND OUTPUT
UNIT
6
7
CONNECTION TO
EXTERNAL I/O
DEVICE
*2
Formats 1, 2
Formats 3 to 6
Formats 7 to 10
Formats 11 to 13
Formats 14, 15
MODBUS(R)/TCP
CONNECTION
2.5 Message Formats
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
M2047
8321
:
M2038
Format
3 to 6
8320
:
M2047
M2039
Format
1, 2
MICROCOMPUTER
CONNECTION
(ETHERNET)
Address
Model
MICROCOMPUTER
CONNECTION
(SERIAL)
2
The address specification values different depending on the data format are also given below.*1
MODBUS(R)/RTU
CONNECTION
2.4.4
2. MICROCOMPUTER CONNECTION (SERIAL)
2.4 Device Data Area
2 - 17
2.4.5
SD devices
The SD devices are word devices into which GOT communication errors (error codes), clock data and other information
are stored.
 List of SD devices
The following lists the SD devices (virtual devices inside the GOT).
Address
Description
Set side
100ms counter (32bits)
The counter is incremented at 100ms intervals after GOT is turned ON.
(The time elapsed after GOT is turned ON is stored in 100ms units.)
(1) When setting the LH order to [32bit Storage] for the communication detail settings
The lower and upper bits are stored in SD0 and SD1 respectively.
SD0
SD1
SD1
SD0
Upper word
Lower word
(2) When setting the HL order to [32bit Storage] for the communication detail settings
The upper and lower bits are stored in SD0 and SD1 respectively.
SD0
SD1
Upper word
Lower word
Communication error status
An error data (error code) occurred during communication is stored.
•Host Address (Communication error that occurred on the request destination GOT)
0: No error
1: Parity error
2: Framing error
3: Overrun error
4: Communication message error
5: Command error
6: Clock data setting error
SD2*1
System
•Other station (Communication error that occurred on another GOT when multiple GOTs are connected)
101: Parity error
102: Framing error
103: Overrun error
104: Communication message error
105: Timeout error (No station of the specified address exists.)
106: Multiple units not connectable
107: Clock data setting error
SD3
Clock data (second)
Second data of 00 to 59 is stored.
SD4
Clock data (minute)
Minute data of 00 to 59 is stored.
SD5
Clock data (hour)
Hour data of 00 to 23 is stored.
SD6
Clock data (day)
Day data of 00 to 31 is stored.
SD7
Clock data (month)
Month data of 01 to 12 is stored.
(Continued to next page)
*1
For details and corrective actions for the errors (error codes) that are stored into SD2, refer to the following:
■ Details and actions for errors (error codes) stored into SD2
2 - 18
2. MICROCOMPUTER CONNECTION (SERIAL)
2.4 Device Data Area
Description
SD8
Clock data (year)
4-digit year data is stored.
SD9
Clock data (day of week)*1
Day-of-the-week data is stored.
0: Sunday
1: Monday
4: Thursday
5: Friday
Set side
System
2: Tuesday
6: Saturday
SD10 to 15
2
3: Wednesday
Unused
―
If a wrong day of the week is set by the clock data setting commands, the clock data will differ from the time displayed on the
utility.
Example: When June 1, 2004 (Thursday) is set by the clock data setting command (the actual day of the week is Tuesday),
"4" is stored to SD9 although Tuesday (TUE) will be displayed on the utility time display.
The side where virtual devices are set
: Set on the system side.
: Set on the user side (by sending request messages from host or using the touch switches, etc.
on the GOT).
0
Description
Action
No error
―
1, 101
Parity error
The parity bit does not match.
2, 102
Framing error
The data bit and/or stop bit are not correct.
3, 103
Overrun error
The next data was transmitted from the host before GOT
completes the processing of the data received.
• Check the settings of "Communication Detail Settings".
• Decrease the transmission speed.
4, 104
Communication message error
EXT/CR could not be found before the upper limit of the
receive buffer was exceeded.
• Check the communication cable and communication module
attachment.
• Check the settings of "Communication Detail Settings".
• Review the contents of the message to transmit.
5
• Check the communication cable and communication module
attachment.
• Check the settings of "Communication Detail Settings".
• Match the GOT and host transmission settings.
• Review the contents of the message to transmit.
• Check the commands in the message.
Command error
An unsupported command was used.
(
2.5.2 List of commands)
105
Timeout error
There is no response from the GOT, or the station of the
specified address does not exist.
• Check the communication cable and communication module
attachment.
• Check the settings of "Communication Detail Settings".
• Review the contents of the message to transmit.
106
Multiple units not connectable
The RS-232 port is occupied.
• Check the communication cable and communication module
attachment.
• Check the settings of "Communication Detail Settings".
• Check to see if the RS-232 port is occupied.
Clock data setting error
The setting value of the clock data has error.
• Review the contents of the message to transmit.
• Check whether the non-existent data is set (e.g. setting "07"
at the day of the week) as clock data.
6
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
6, 107
5
MODBUS(R)/TCP
CONNECTION
Error code
MODBUS(R)/RTU
CONNECTION
4
 Details and actions for errors (error codes) stored into SD2
CONNECTION TO
SOUND OUTPUT
UNIT
System
User
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
POINT
CONNECTION TO
EXTERNAL I/O
DEVICE
*1
MICROCOMPUTER
CONNECTION
(SERIAL)
Address
1
PREPARATORY
PROCEDURES FOR
MONITORING
(From previous page)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.4 Device Data Area
2 - 19
 Differences in address specifications by data format
The address specification of devices varies depending on the data format.*1
The following shows the address specification values for each data format.
Address specification value
Address
Formats 1, 2
Formats 3 to 6
Formats 7 to 10
Formats 11 to 13
8448
D9000
SD0
2100H
SD0
SD1
8449
SD2
D9001
8450
SD3
D9002
8451
SD4
D9003
8452
SD5
D9004
8453
SD6
D9005
8454
SD7
D9006
8455
SD8
D9007
8456
SD9
D9008
8457
*1
D9009
SD1
SD2
SD3
SD4
SD5
SD6
SD7
SD8
SD9
Formats 14, 15*2
2100H
2100H
2101H
2101H
Upper 8 bits
Lower 8 bits
2102H
2102H
2103H
2103H
Upper 8 bits
Lower 8 bits
2104H
2104H
2105H
2105H
Upper 8 bits
Lower 8 bits
2106H
(3000H)
2106H(3000H)
2107H(3001H)
Upper 8 bits
Lower 8 bits
2108H(3002H)
2109H(3003H)
Upper 8 bits
Lower 8 bits
210AH(3004H)
210BH(3005H)
Upper 8 bits
Lower 8 bits
210CH(3006H)
210DH(3007H)
Upper 8 bits
Lower 8 bits
210EH(3008H)
210FH(3009H)
Upper 8 bits
Lower 8 bits
2110H(300AH)
2111H(300BH)
Upper 8 bits
Lower 8 bits
2112H(300CH)
2113H(300DH)
Upper 8 bits
Lower 8 bits
2101H
2102H
2103H
2104H
2105H
2106H
2107H
2108H
2109H
2107H
(3001H)
2108H
(3002H)
2109H
(3003H)
210AH
(3004H)
210BH
(3005H)
210CH
(3006H)
210DH
(3007H)
210EH
(3008H)
210FH
(3009H)
2110H
(300AH)
2111H
(300BH)
2112H
(300CH)
2113H
(300DH)
For the address specification method for each data format, refer to the following.
2.5 Message Formats
•
•
•
•
•
*2
2 - 20
Formats 1, 2
Formats 3 to 6
Formats 7 to 10
Formats 11 to 13
Formats 14, 15
:
:
:
:
:
GOT-A900 Series microcomputer connection
A compatible 1C frame
QnA compatible 3C/4C frame
Digital Electronics Corporation's memory link method
GOT-F900 Series microcomputer connection
SD3 to 9 correspond to GD0 to 6 on the GOT-F900 Series.
Access to SD3 to 9 can be also made by the specification of the addresses (3000 to 300DH) of GD0 to 6 on the GOT-F900
Series.
2. MICROCOMPUTER CONNECTION (SERIAL)
2.4 Device Data Area
The SM devices are bit devices into which interrupt outputs and clock data that turn ON/OFF at 1-second cycles.
 List of SM devices
The following shows the SM devices (virtual devices inside the GOT).
Set side
MICROCOMPUTER
CONNECTION
(SERIAL)
codes shown below are transmitted (interrupt output) to the host side.*1*2
The data amount (number of bytes) to be interrupt-output is set at "Interrupt Data Byte" in "Communication
2.6.1 Setting communication interface (Communication settings))
SM0 to 49
SM1
SM2
SM48
SM49
Interrupt code
Changed from OFF to ON
50H
Changed from ON to OFF
51H
Changed from OFF to ON
52H
Changed from ON to OFF
53H
Changed from OFF to ON
54H
Changed from ON to OFF
55H
Changed from OFF to ON
B0H
Changed from ON to OFF
B1H
Changed from OFF to ON
B2H
Changed from ON to OFF
B3H
3
User
4
MODBUS(R)/RTU
CONNECTION
SM0
Event type
1-second cycle clock
Turns ON/OFF at a 1-second cycle.
5
SM50
0.5
0.5
System
2-second cycle clock
Turns ON/OFF at a 2-second cycle.
SM51
1
1
Interrupt code output disable flag
Enables or disables the output of the interrupt code.
OFF : Interrupt code output enabled ON : Interrupt code output disabled
SM52
6
User
When set to disable the interrupt code output, no interrupt data are output to the host.
(Relevant devices: D13, D14, SM0 to 49)
SM53 to 63
Unused
*1
*2
―
After the ON/OFF state is changed, the interrupt data is output within a period of 1 to 10 ms.
When the ON/OFF state of SM0 to 49 is changed from the host side, interrupt output is not performed.
7
POINT
(1) The side where virtual devices are set
System : Set on the system side.
User
: Set on the user side (by sending request messages from host or using the touch switches, etc.
on the GOT).
(2) Interrupt outputs (SM0 to 49)
• To disable the interrupt output, turn ON SM52 (interrupt code output disable flag).(
2.4.6 SM devices)
• To enable the interrupt output, set 8 bits to the data length at "Communication Detail Settings".
(
2.6.1 Setting communication interface (Communication settings))
• When "7 bits" is set, the MSB (8th bit) is ignored. (Example: FFH 7FH)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.4 Device Data Area
MODBUS(R)/TCP
CONNECTION
Address
CONNECTION TO
SOUND OUTPUT
UNIT
Detail Settings". (
2
MICROCOMPUTER
CONNECTION
(ETHERNET)
Description
Interrupt output
When the ON/OFF state of SM0 to 49 is changed by a touch switch on the GOT, for example, the interrupt
2 - 21
CONNECTION TO
EXTERNAL I/O
DEVICE
Address
PREPARATORY
PROCEDURES FOR
MONITORING
1
SM devices
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
2.4.6
 Differences in address specifications by data format
The address specification of devices varies depending on the data format.*1
The following shows the address specification values for each data format.
Address
Model
Address specification value
b7
b6
b5
b4
b3
b2
b1
b0
SM7
SM6
SM5
SM4
SM3
SM2
SM1
SM0
SM15
SM14
SM13
SM12
SM11
SM10
SM9
SM8
SM23
SM22
SM21
SM20
SM19
SM18
SM17
SM16
SM31
SM30
SM29
SM28
SM27
SM26
SM25
SM24
SM39
SM38
SM37
SM36
SM35
SM34
SM33
SM32
SM46
SM45
SM44
SM43
SM42
SM41
SM40
SM52
SM51
SM50
SM49
SM48
SM47
Unused
Unused
SM7
SM6
SM5
SM15
SM14
SM13
SM23
SM22
SM21
SM31
SM30
SM29
SM39
SM38
SM46
SM47
Unused
*1
SM4
Format
1, 2
Format
3 to 6
Format
7 to 10
8464
2110H
8465
2111H
*2*4
*3*4
8466
2112H
8467
2113H
―
SM3
SM2
SM1
SM0
SM12
SM11
SM10
SM9
SM8
SM20
SM19
SM18
SM17
SM16
SM28
SM27
SM26
SM25
SM24
SM37
SM36
SM35
SM34
SM33
SM32
SM45
SM44
SM43
SM42
SM41
SM40
SM52
SM51
SM50
SM49
SM48
Format
11 to 13
8464
8465
8466
8467
*2
*3
*4
2 - 22
:
:
:
:
:
2202H
2203H
2204H
2205H
2206H
―
―
2201H
―
2202H
―
2203H
―
2204H
―
2205H
―
2206H
GOT-A900 Series microcomputer connection
A compatible 1C frame
QnA compatible 3C/4C frame
Digital Electronics Corporation's memory link method
GOT-F900 Series microcomputer connection
In formats 3 to 6, values are specified within a range of M9000 to 9052.
In formats 7 to 10, values are specified within a range of SM0 to 52.
For reading or writing data in word units, specify the addresses in 16-point units. (Example: SM0, SM16, SM32, etc.)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.4 Device Data Area
2201H
2200H
2.5 Message Formats
Formats 1, 2
Formats 3 to 6
Formats 7 to 10
Formats 11 to 13
Formats 14, 15
2200H
―
For the address specification method for each data format, refer to the following.
•
•
•
•
•
Format
14, 15
1
PREPARATORY
PROCEDURES FOR
MONITORING
2.5 Message Formats
This section describes the format of messages that can be used in the microcomputer connection (serial).
Data format type and application
2
MICROCOMPUTER
CONNECTION
(SERIAL)
 Data format type and application
Type
Name
Description
Format 1
GOT-A900 Series microcomputer connection
(format 1)
This format is used when the GOT is connected to the host in a 1:1
connection.
Format 2
GOT-A900 Series microcomputer connection
(format 2)
This is the appended format with error code at the error response of the
GOT-A900 Series microcomputer connection (format 1).
Refer to
2.5.3
(2) Formats 3 to 6 (A compatible 1C frame)
This is the same message format as when communication is performed using the dedicated protocol of the A
series computer link module.
Type
Name
Description
Format 3
A compatible 1C frame (format 1)
This is the basic format of the dedicated protocols.
Format 4
A compatible 1C frame (format 2)
This is the appended format of the A compatible 1C frame (format 1) with a
block No.
Format 5
A compatible 1C frame (format 3)
This is the enclosed format of the A compatible 1C frame (format 1) with
STX and ETX.
Format 6
A compatible 1C frame (format 4)
This is the appended format of the A compatible 1C frame (format 1) with
CR and LF.
Refer to
2.5.4
(3) Formats 7 to 10 (QnA compatible 3C/4C frame)
This is the same message format as when a communication is performed using the MC protocol of Q/QnA
Series serial communication module.
Name
Description
QnA compatible 3C/4C frame (format 1)
This is the basic format of the MC protocols.
Format 8
QnA compatible 3C/4C frame (format 2)
This is the appended format of the QnA compatible 3C/4C frame (format 1)
with block No.
Format 9
QnA compatible 3C/4C frame (format 3)
This is the enclosed format of the QnA compatible 3C/4C frame (format 1)
with STX and ETX.
Format 10
QnA compatible 3C/4C frame (format 4)
This is the appended format of the QnA compatible 3C/4C frame (format 1)
with CR and LF.
Refer to
2.5.5
4
5
6
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Type
Format 7
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
This is the same message format as when a microcomputer connection is established with the GOT-A900
series.
MODBUS(R)/RTU
CONNECTION
(1) Formats 1, 2 (GOT-A900 Series microcomputer connection)
MODBUS(R)/TCP
CONNECTION
Communication is possible using any of the data formats shown below.
CONNECTION TO
SOUND OUTPUT
UNIT
2.5.1
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 23
(4) Formats 11 to 13 (Digital Electronics Corporation's memory link method)
This is the same format as the protocol of the Digital Electronics Corporation's memory link method.
Type
Name
Description
Format 11
Digital Electronics Corporation's memory link
method
(compatible mode)
This is the basic format of the Digital Electronics Corporation's memory link
method.
Format 12
Digital Electronics Corporation's memory link
method
(extended mode, ASCII code 1:1)
This is the appended format of the Digital Electronics Corporation's memory
link method (compatible mode) with sum check, CR and LF.
Format 13
Digital Electronics Corporation's memory link
method
(extended mode, ASCII code 1:n)
This is the appended format of the Digital Electronics Corporation's memory
link method (extended mode, ASCII code 1:1) with a station No.
Refer to
2.5.6
(5) Formats 14, 15 (GOT-F900 Series microcomputer connection)
This is the same message format as when a microcomputer connection is established with the GOT-F900
Series.
Type
Name
Description
Format 14
GOT-F900 Series microcomputer connection
(format 1)
Use this format when establishing a 1:1 or m:n connection between the
GOT and the host.
The end code is CR.
Format 15
GOT-F900 Series microcomputer connection
(format 2)
Use this format when establishing a 1:1 or m:n connection between the
GOT and the host.
The end code is ETX or sum check.
 How to set data format
Set the data format at [Detail setting] in GT Designer3.
For details of the data format setting method, refer to the following.
2.6.1 Setting communication interface (Communication settings)
2 - 24
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
Refer to
2.5.7
1
PREPARATORY
PROCEDURES FOR
MONITORING
List of commands
Description
Max. number of points
processed
ASCII
code
RD
52H 44H
Batch read
in word units
WD
57H 44H
Batch write
in word units
Writes to word devices in 1-point units.
Random read
Reads multiple different bit devices in 16-point units.
64 words (1024 points)
in word units*1
Reads multiple different word devices in 1-point units.
64 points
Random write
Writes to multiple different word devices in 16-point units.
64 words (1024 points)
in word units*1
Writes to multiple different word devices in 1-point units.
64 points
Reads bit devices in 16-point units.
64 words (1024 points)
Reads word devices in 1-point units.
64 points
Writes to bit devices in 16-point units.
64 words (1024 points)
64 points
RR
52H 52H
RW
52H 57H
TR
54H 52H
Read clock data
Reads the clock data of the GOT.
―
TS
54H 53H
Set clock data
Sets the clock data of the GOT.
―
*1
 List of commands for formats 3 to 6 (A compatible 1C frame)
Command name
Description
Max. number of points
processed
Symbol
ASCII
code
BR
JR
42H 52H
4AH 52H
Batch read
in bit units
WR
QR
57H 52H
51H 52H
Batch read
in word units
BW
JW
42H 57H
4AH 57H
Batch write
in bit units
WW
QW
57H 57H
51H 57H
Batch write
in word units
BT
JT
42H 54H
4AH 54H
Test in bit units
(random write)
WT
QT
57H 54H
51H 54H
Test in word units
(random write)
Writes to multiple different bit devices in 16-point units.*3
64 words (1024 points)
Writes to multiple different word devices in 1-point units.
64 points
TR*2
54H 52H
Read clock data
Reads the clock data of the GOT.
―
TS*2
54H 53H
Set clock data
Sets the clock data of the GOT.
―
Reads bit devices in 1-point units.
5
64 points
Reads bit devices in 16-point units.*3
64 words (1024 points)
Reads word devices in 1-point units.
64 points
Writes to bit devices in 1-point units.
64 points
Writes to bit devices in 16-point units.*3
64 words (1024 points)
Writes to word devices in 1-point units.
64 points
Writes to multiple different bit devices in 1-point units.
64 points
6
7
CONNECTION TO
EXTERNAL I/O
DEVICE
This is a dedicated command of GOT for the microcomputer connection.
Specifies the address of bit devices in 16-point units. (Example: M0, M16, M32, and others)
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
*2
*3
3
4
Mixed specification of bit devices and word devices is also possible.
Command
2
MODBUS(R)/RTU
CONNECTION
Command name
Symbol
MODBUS(R)/TCP
CONNECTION
Command
MICROCOMPUTER
CONNECTION
(SERIAL)
 List of commands for formats 1, 2 (GOT-A900 Series microcomputer connection)
MICROCOMPUTER
CONNECTION
(ETHERNET)
The following shows the list of commands available in each data format.
CONNECTION TO
SOUND OUTPUT
UNIT
2.5.2
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 25
 Command lists for formats 7 to 10 (QnA compatible 3C/4C frame)
Command
Subcommand
0401
0001
Batch read
in bit units
0401
0000
Batch read
in word units
Command name
Description
Reads bit devices in 1-point units.
Max. number of points
processed
64 points
Reads bit devices in 16-point units.*3
64 words (1024 points)
Reads word devices in 1-point units.
64 points
Writes to bit devices in 1-point units.
64 points
1401
0001
Batch write
in bit units
1401
0000
Batch write
in word units
Writes to bit devices in 16-point units.*3
64 words (1024 points)
Writes to word devices in 1-point units.
64 points
Random read
Reads multiple different bit devices in 16-point and 32-point units.*3
in word units*1
Reads multiple different word devices in 1-point and 2-point units.
64 points
Random write
in bit units
Writes to multiple different bit devices in 1-point units.
64 points
Random write
Writes to multiple different bit devices in 16-point and 32-point units.*3
0403
0000
1402
0001
1402
0000
in word units
*1
Writes to multiple different word devices in 1-point and 2-point units.
64 words (1024 points)
64 words (1024 points)
64 points
0406
0000
Multiple block
batch read
Reads multiple blocks. A bit device (16 bits for 1 point) or a word device
1406
0000
Multiple block
batch write
Writes multiple blocks. A bit device (16 bits for 1 point) or a word device
1901*2
0000
Read clock data
Reads the clock data of the GOT.
―
0901*2
0000
Set clock data
Sets the clock data of the GOT.
―
*1
*2
*3
(1 word for 1 point) is regarded as one block.*3
(1 word for 1 point) is regarded as one block.*3
64 points
64 points
Mixed specification of bit devices and word devices is also possible.
This is a dedicated command of GOT for the microcomputer connection.
Specifies the address of bit devices in 16-point units. (Example: M0, M16, M32, and others)
 List of commands for formats 11 to 13 (Digital Electronics Corporation's memory link method)
Command
Command name
Description
Max. number of points
processed
Symbol
ASCII
code
R
52H
Batch read
in word units
Reads bit devices in 16-point units.
64 words (1024 points)
Reads word devices in 1-point units.
64 points
W
57H
Batch write
in word units
Writes to bit devices in 16-point units.
64 words (1024 points)
Writes to word devices in 1-point units.
64 points
I
49H
Interrupt inquiry
Issues an interrupt inquiry.(format 13 only)
―
*4
4DH
Read clock data
Reads the clock data of the GOT.
―
M*4
4EH
Set clock data
Sets the clock data of the GOT.
―
N
*4
2 - 26
This is a dedicated command of GOT for the microcomputer connection.
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
Command name
Description
Max. number of points
processed
Symbol
ASCII
code
0
30H
Batch read
(w/out station No.)
Reads bit devices in byte units.
255bytes (2040 points)
Reads word devices in byte units.
255bytes (127 points)
A
41H
Batch read
(w/ station No.)
Reads bit devices in byte units.
255bytes (2040 points)
Reads word devices in byte units.
255bytes (127 points)
1
31H
Batch write
(w/out station No.)
Writes to bit devices in byte units.
255bytes (2040 points)
Writes to word devices in byte units.
255bytes (127 points)
B
42H
Batch write
(w/ station No.)
Writes to bit devices in byte units.
255bytes (2040 points)
Writes to word devices in byte units.
255bytes (127 points)
33H
Multi-point write in bit
units (w/out station No.)
44H
Writes bit patterns (bit ON/OFF, inversion, direct specification) in
1-point units (8 bits for 1 point) to a specified device.
70bytes (560 points)
D
Multi-point write in bit
units (w/ station No.)
4
34H
Fill command
(w/out station No.)
E
45H
Fill command
(w/ station No.)
5
35H
Set clock data
(w/out station No.)
F
46H
Set clock data
(w/ station No.)
6
36H
Read clock data
(w/out station No.)
G
47H
Read clock data
(w/ station No.)
Sets the clock data of the GOT.
―
Reads the clock data of the GOT.
―
MICROCOMPUTER
CONNECTION
(ETHERNET)
4
MODBUS(R)/RTU
CONNECTION
―
5
MODBUS(R)/TCP
CONNECTION
Writes the same value to a range of specified devices.
3
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
3
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Command
PREPARATORY
PROCEDURES FOR
MONITORING
1
 List of commands for formats 14, 15 (GOT-F900 series microcomputer connection)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 27
2.5.3
Formats 1, 2 (GOT-A900 Series microcomputer connection)
 Basic format of data communication
Item
Message format
STX
Command
ETX
Data
Sum
Check
Request message
(host
03H
02H
GOT)
(H)
(H)
(L)
(L)
Sum check is performed in this range.
(1) During processing of read commands
STX
ETX
Data
Sum
Check
03H
02H
(H)
Response message
during normal
communication
(GOT
host)
(L)
Sum check is performed in this range.
(2) During processing of write commands
ACK
06H
(format 1: GOT-A900 Series microcomputer connection (format 1))
(format 2: GOT-A900 Series microcomputer connection (format 2))
NAK
NAK Code
15H
15H
Response message
during faulty
communication
(GOT
host)
(format 1: GOT-A900 Series microcomputer connection (format 1))
Error
(format 2: GOT-A900 Series microcomputer connection (format 2))
Output value
During interrupt
output
1/2/4
bytes*1
STX Output value ETX Sum check
02H
1/2/4
bytes*1
03H
(H)
(L)
Sum check is performed in this ran
*1
Set the number of interrupt data bytes at [Detail setting] in GT Designer3.
For the setting of the number of interrupt data bytes, refer to the following.
2.6.1 Setting communication interface (Communication settings)
2 - 28
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
1
PREPARATORY
PROCEDURES FOR
MONITORING
 Details of data items in message format
POINT
Data code during communication
Communication is performed in ASCII code. (excluding interrupt output)
MICROCOMPUTER
CONNECTION
(SERIAL)
2
(1) Control codes
ASCII code
STX
02H
Start of Text (start marker of message frame)
Description
ETX
03H
End of Text (end marker of message frame)
EOT
04H
End of Transmission
ENQ
05H
Enquiry (start of enquiry)
NAK
15H
Negative ACK (error response)
ACK
06H
Acknowledge (write completion response)
LF
0AH
Line Feed
CL
0CH
Clear
CR
0DH
Carriage Return
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
Symbol
4
(2) Command
MODBUS(R)/RTU
CONNECTION
Specifies the contents to access from the host to GOT.
The command is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.
For details of the commands that can be used, refer to the following.
Specifies the head No. of the device data to be read/written.
The address notated in decimal is converted to a 4-digit ASCII code (Hex) and transmitted from the upper digit.
For details of the device range that can be accessed, refer to the following.
2.4 Device Data Area
(4) Number of points
Specifies the number of device data to be read/written. (Setting range: 1 to 64)
The address notated in decimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.
(5) Year, month, day, hour, minute, second and day of the week data
Specifies year, month, day, hour, minute, second, and day of the week to be read/set to the GOT clock data.
The address notated in decimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.
■ Message format (5) Read clock data (TR) command
6
Specifies the data to read from/write to the specified device data.(word unit)
The address notated in hexadecimal is converted to a 4-digit ASCII code (Hex) and transmitted from the upper
digit.
(7) Error code
This is the response message at faulty communication appended with error contents.
Error code is transmitted in 1 byte.
For details of the error codes generated in format 2 (GOT-A900 Series microcomputer connection (format 2)),
refer to the following:
■ Error code list
2 - 29
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(6) Data
CONNECTION TO
EXTERNAL I/O
DEVICE
7
■ Message format (6) Set clock data (TS) command
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
5
MODBUS(R)/TCP
CONNECTION
(3) Address
CONNECTION TO
SOUND OUTPUT
UNIT
2.5.2 List of commands
(8) Sum check code
The sum check code is obtained by converting the lower 1 byte (8 bits) of the result (sum), after having added
the sum check target data as binary data, to 2-digit ASCII code (Hex).
Number of
points
STX
Command
R
D
0
1
0
0
0
2
02H
52H
44H
30H
31H
30H
30H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
Address
ETX
03H
Sum check is performed in this range.
52H + 44H + 30H + 31H + 30H + 30H + 30H + 32H + 03H = 1BCH
2 - 30
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
Sum
Check
B
C
42H
43H
(H)
(L)
1
PREPARATORY
PROCEDURES FOR
MONITORING
 Message Formats
(1) Batch read in word units (RD) command
(a) When reading a word device
The following shows an example of reading the two points of the virtual devices D100 and D101.
(Assuming D100=0102H, D101=0304H are stored.)
GOT)
D101
0304H
Message format
3
Number of
points
STX
Command
R
D
0
1
0
0
0
2
02H
52H
44H
30H
31H
30H
30H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
Request message
(host
0102H
Address
ETX
03H
Sum
Check
B
C
42H
43H
(H)
(L)
MICROCOMPUTER
CONNECTION
(ETHERNET)
Item
D100
MICROCOMPUTER
CONNECTION
(SERIAL)
2
Sum check is performed in this range.
Response message
during normal
communication
(GOT
host)
02H
Data 1 (D100)
Data 2 (D101)
ETX
0
1
0
2
0
3
0
4
30H
31H
30H
32H
30H
33H
30H
34H
(L)
(H)
(H)
(L)
03H
4
Sum
Check
8
D
38H
44H
(H)
(L)
MODBUS(R)/RTU
CONNECTION
STX
Sum check is performed in this range.
(format 1: GOT-A900 Series microcomputer connection (format 1))
5
MODBUS(R)/TCP
CONNECTION
NAK
15H
6
Error
NAK code
15H
CONNECTION TO
SOUND OUTPUT
UNIT
host)
06H
The above is a case
where the sum check error
(06H) has occurred.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
(GOT
(format 2: GOT-A900 Series microcomputer connection (format 2))
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Response message
during faulty
communication
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 31
(b) When reading a bit device
The following shows an example of reading the two points of the virtual devices M0 to M31.
(Assuming M0="1" and M31="1" are stored.
Item
Request message
GOT)
0001H
M31 to 6
8000H
Message format
STX
(host
M15 to 0
02H
Number of
points
Address
Command
R
D
8
3
2
0
0
2
52H
44H
38H
33H
32H
30H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
ETX
03H
Sum
Check
C
8
43H
38H
(H)
(L)
Sum check is performed in this range.
Sum check is performed in this range.
STX
Response message
during normal
communication
(GOT
02H
Data 2 (M31 to 16)
Data 1 (M15 to 0)
0
0
0
1
8
0
0
0
30H
30H
30H
31H
38H
30H
30H
30H
(L)
(H)
(H)
ETX
03H
(L)
host)
00000000000000011000000000000000
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
11111198765432103322222222221111
543210
1098765432109876
(format 1: GOT-A900 Series microcomputer connection (format 1))
NAK
15H
Response message
during faulty
communication
(GOT
(format 2: GOT-A900 Series microcomputer connection (format 2))
host)
Error
NAK code
15H
06H
The above is a case where
the sum check error (06H)
has occurred.
2 - 32
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
Sum
Check
8
C
38H
43H
(H)
(L)
1
PREPARATORY
PROCEDURES FOR
MONITORING
(2) Batch write in word units (WD) command
(a) When writing to a word device
The following shows as example of writing "0064H"and "0065H"to virtual devices D100 and D101.
D100
0064H
D101
0000H
D101
0065H
Before execution
After execution
Item
Message format
GOT)
Number of
points
STX
Command
W
D
0
1
0
0
0
2
0
0
6
4
0
0
6
5
02H
57H
44H
30H
31H
30H
30H
30H
32H
30H
30H
36H
34H
30H
30H
36H
35H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
Request message
(host
2
Address
Data 1(D100)
ETX
Data 2 (D101)
(L)
03H
Sum
Check
5
6
35H
36H
(H)
(L)
Sum check is performed in this range.
ACK
(GOT
06H
host)
4
(format 1: GOT-A900 Series microcomputer connection (format 1))
NAK
5
Error
NAK code
15H
06H
6
CONNECTION TO
SOUND OUTPUT
UNIT
The above is a case where
the sum check error (06H)
has occurred.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
host)
(format 2: GOT-A900 Series microcomputer connection (format 2))
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(GOT
MODBUS(R)/TCP
CONNECTION
15H
Response message
during faulty
communication
3
MODBUS(R)/RTU
CONNECTION
Response message
during normal
communication
MICROCOMPUTER
CONNECTION
(SERIAL)
0000H
MICROCOMPUTER
CONNECTION
(ETHERNET)
D100
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 33
(b) When writing to a bit device
The following shows an example of writing "1"s to virtual devices M0 and M31.
M15 to 0
0000H
M15 to 0
0001H
M31 to 16
0000H
M31 to 16
8000H
Before execution
After execution
Item
Message format
Sum check is performed in this range.
Request message
(host
GOT)
Number
of points
STX
Command
W
D
8
3
2
0
0
2
0
0
0
1
8
0
0
0
02H
57H
44H
38H
33H
32H
30H
30H
32H
30H
30H
30H
31H
38H
30H
30H
30H
(H)
(L)
(H)
–
–
(L)
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
Address
Data 1 (M15 to 0)
Data 2 (M31 to 16)
ETX
03H
00000000000000011000000000000000
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
11111198765432103322222222221111
543210
1098765432109876
ACK
Response message
during normal
communication
(GOT
06H
host)
(format 1: GOT-A900 Series microcomputer connection (format 1))
NAK
15H
Response message
during faulty
communication
(GOT
host)
(format 2: GOT-A900 Series microcomputer connection (format 2))
Error
NAK code
15H
06H
The above is a case where
the sum check error (06H)
has occurred.
2 - 34
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
Sum
Check
5
6
35H
36H
(H)
(L)
1
PREPARATORY
PROCEDURES FOR
MONITORING
(3) Random read in word units (RR) command
The following shows an example of reading the two points of the virtual devices D100 and M0 to M15.
(Assuming D100=0064H, M0=1are stored.)
GOT)
0001H
2
MICROCOMPUTER
CONNECTION
(SERIAL)
M15 to 0
Message format
STX
Command
R
R
0
1
0
0
8
3
2
0
02H
52H
52H
30H
31H
30H
30H
38H
33H
32H
30H
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
Request message
(host
0064H
Address 1
Sum
Check
ETX
Address 2
03H
3
5
33H
35H
(H)
(L)
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
Item
D100
Sum check is performed in this range.
Sum check is performed in this range.
Response message
during normal
communication
(GOT
02H
Data 2 (M15 to 0)
Data 1 (D100)
0
0
6
30H
30H
36H
(H)
–
–
0
0
0
34H
30H
30H
30H
31H
(L)
(H)
–
–
(L)
4
ETX
Sum
Check
8
1
03H
4
E
38H
45H
(H)
(L)
MODBUS(R)/RTU
CONNECTION
STX
host)
0000000000000001
MMMMMMMMMMMMMMMM
1111119876543210
543210
5
MODBUS(R)/TCP
CONNECTION
(format 1: GOT-A900 Series microcomputer connection (format 1))
NAK
15H
CONNECTION TO
SOUND OUTPUT
UNIT
host)
Error
NAK code
15H
06H
7
The above is a case where
the sum check error (06H)
has occurred.
CONNECTION TO
EXTERNAL I/O
DEVICE
(GOT
6
(format 2: GOT-A900 Series microcomputer connection (format 2))
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Response message
during faulty
communication
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 35
(4) Random write in word units (RW) command
The following shows an example of writing "0064H" and "1" to virtual devices D100 and M0, respectively.
D100
0000H
D100
0064H
M15 to 0
0000H
M15 to 0
0001H
Before execution
After execution
Item
Message format
STX
Command
R
W
02H
52H
57H
(H)
(L)
ETX
Following*1
03H
Sum
Check
C
5
43H
35H
(H)
(L)
Sum check is performed in this range.
Request message
(host
*1
Address 1
GOT)
Data 1 (D100)
Data 2 (M15 to 0)
Address 2
0
1
0
0
0
0
6
4
8
3
2
0
0
0
0
1
30H
31H
30H
30H
30H
30H
36H
34H
38H
33H
32H
30H
30H
30H
30H
31H
(H)
–
–
(L)
(H)
–
–
(L)
(H)
–
–
(L)
(H)
–
–
(L)
0000000000000001
MMMMMMMMMMMMMMMM
1111119876543210
543210
Response message
during normal
communication
(GOT
ACK
06H
host)
(format 1: GOT-A900 Series microcomputer connection (format 1))
NAK
15H
Response message
during faulty
communication
(GOT
host)
(format 2: GOT-A900 Series microcomputer connection (format 2))
Error
NAK code
15H
06H
The above is a case where
the sum check error (06H)
has occurred.
2 - 36
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
1
PREPARATORY
PROCEDURES FOR
MONITORING
(5) Read clock data (TR) command
The following shows an example of reading the clock data of GOT.
(Assuming that the clock data of GOT has been set to "2004, June 1, 18:46:49, Tuesday".)
Time display
2004/06/01 18:46:49
MICROCOMPUTER
CONNECTION
(SERIAL)
Message format
STX
Command
T
R
02H
54H
52H
(H)
(L)
Request message
(host
2
GOT)
ETX
03H
Sum
Check
A
9
41H
39H
(H)
(L)
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
Item
TUE
Sum check is performed in this range.
Response message
during normal
communication
(GOT
host)
Second
data
Day-ofweek data
STX
Year data Month data
0
4
0
6
0
1
1
8
4
6
4
9
0
2
02H
30H
34H
30H
36H
30H
31H
31H
38H
34H
36H
34H
39H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Day data
Hour data Minute data
ETX
03H
Sum
Check
D
0
44H
30H
(H)
(L)
4
MODBUS(R)/RTU
CONNECTION
Sum check is performed in this range.
(format 1: GOT-A900 Series microcomputer connection (format 1))
NAK
5
host)
Error
NAK code
15H
6
06H
The above is a case where
the sum check error (06H)
has occurred.
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(GOT
(format 2: GOT-A900 Series microcomputer connection (format 2))
CONNECTION TO
SOUND OUTPUT
UNIT
Response message
during faulty
communication
MODBUS(R)/TCP
CONNECTION
15H
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 37
(6) Set clock data (TS) command
The following shows an example of setting the clock data of GOT.
(Assuming the clock data of GOT is to be set to "2004, June 1, 18:46:49 Tuesday".)
Time display
2004/06/01 18:46:49
TUE
After execution
Item
Message format
GOT)
Day-ofweek data ETX
Command
T
S
0
4
0
6
0
1
1
8
4
6
4
9
0
2
02H
54H
53H
30H
34H
30H
36H
30H
31H
31H
38H
34H
36H
34H
39H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Request message
(host
Second
data
STX
Year data
Month data
Day data
Hour data Minute data
03H
Sum
Check
7
7
37H
37H
(H)
(L)
Sum check is performed in this range.
Response message
during normal
communication
(GOT
ACK
06H
host)
(format 1: GOT-A900 Series microcomputer connection (format 1))
NAK
15H
Response message
during faulty
communication
(GOT
(format 2: GOT-A900 Series microcomputer connection (format 2))
host)
Error
NAK code
15H
06H
The above is a case where
the sum check error (06H)
has occurred.
POINT
When a wrong day of the week has been set by the clock data setting command
If a wrong day of the week is set by the clock data setting commands, the clock data will differ from the time
displayed on the utility.
Example: When June 1, 2004 (Thursday) is set by the clock data setting command (the actual day of week is
Tuesday), Tuesday (TUE) will be displayed on the utility time display.
2 - 38
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
The following shows an example of an interrupt output when data are written to the interrupt output devices (D13
and D14).
(Assuming that "3139H" is written to D13 and "AA55H" to D14.)
Example: When the number of interrupt data bytes is 2
2
3139H
MICROCOMPUTER
CONNECTION
(SERIAL)
D13
PREPARATORY
PROCEDURES FOR
MONITORING
1
(7) In the case of interrupt outputs
Interrupt
Interrupt output
Output Output
value 1 value 2
Item
3
39H
MICROCOMPUTER
CONNECTION
(ETHERNET)
31H
Message format
(1) When [Interrupt Data Byte] in "Communication Detail Settings" is set to "1 byte"
(format 1: in the case of GOT-A900 Series
microcomputer connection
(format 1))
Output
value 1
(format 2: in the case of GOT-A900 Series
microcomputer connection
(format 2))
4
02H
39H
39H
03H
3
C
33H
43H
(H)
(L)
MODBUS(R)/RTU
CONNECTION
STX Output
value 1 ETX Sum check
Sum check is performed in this range.
5
(format 1: in the case of GOT-A900 Series
microcomputer connection
(format 1))
Output
STX Output
value 1 value 2 ETX Sum check
31H
39H
02H
31H
39H
03H
6
D
36H
44H
(H)
(L)
6
CONNECTION TO
SOUND OUTPUT
UNIT
host)
Sum check is performed in this range.
(3) When [Interrupt Data Byte] in "Communication Detail Settings" is set to "4 byte"
(format 1: in the case of GOT-A900 Series
microcomputer connection
(format 1))
Output Output Output Output
value1 value2 value3 value4
AAH
55H
31H
39H
(format 2: in the case of GOT-A900 Series
microcomputer connection
(format 2))
Output Output Output Output
STX value1 value2 value3 value4 ETX
02H
AAH
55H
31H
39H
03H
7
Sum
Check
6
C
36H
43H
(H)
(L)
Sum check is performed in this range.
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(GOT
Output Output
value 1 value 2
(format 2: in the case of GOT-A900 Series
microcomputer connection
(format 2))
CONNECTION TO
EXTERNAL I/O
DEVICE
Interrupt output
MODBUS(R)/TCP
CONNECTION
(2) When [Interrupt Data Byte] in "Communication Detail Settings" is set to "2 byte"
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 39
POINT
Interrupt output
• To disable the interrupt output, turn ON SM52 (interrupt code output disable flag). (
2.4.6 SM devices)
• To enable the interrupt output, set 8 bits to the data length at "Communication Detail Settings".
(
2.6.1 Setting communication interface (Communication settings))
• When "7 bits" is set, the MSB (8th bit) is ignored. (Example: FFH 7FH)
 Error code list
In the case of format 2 (GOT-A900 series microcomputer connection (format 2)), the error contents (error code) are
appended to the response message during faulty communication.
The following shows error code, error contents, cause, and measures.
Error code
Description
06H
Sum check error
The sum check code created from received data differs
from the sum check code in the receive data.
10H
Command error
An unsupported command was used.
Action
• Review the contents of the message to transmit.
• Review the contents of the message to transmit.
• Check the commands in the message.
(
2.5.2 List of commands)
11H
Message length error
The upper limit of the data length that can be received by
the GOT has been exceeded.
• Review the contents of the message to transmit.
• Check the data length of the message.(data length of the data section,
etc.)
12H
Communication message error
EXT was not found within the upper limit of the receive
buffer.
• Check the communication cable and communication module attachment.
• Check the settings of "Communication Detail Settings".
• Review the contents of the message to transmit.
15H
Clock data setting error
The setting value of the clock data has error.
• Review the contents of the message to transmit.
• Check whether the non-existent data is set (e.g. setting "07" at the day of
the week) as clock data.
7AH
Address error
The start address of the read/write device is out of range.
7BH
Exceeded number of points error
The read/write range exceeded the device range.
• Review the contents of the message to transmit.
• Check the devices that can be used and the device ranges.
(
2.4 Device Data Area)
 Precautions
(1) Batch reading/writing crossing over different devices
When using the batch read (RD) or batch write (WD) command, do not batch read/write crossing over the
different devices.
This will cause an error response.
(2) Storage order for 32-bit data
To use the program of GOT-A900 series with [32bit Order] setting to GOT1000 series, set [HL Order] to [32bit
Order] for [Communication Detail Settings] when 32-bit data is set for GOT-A900 series.
With setting [LH Order], the order of upper bits and lower bits are reversed when the GOT displays and writes
32-bit data.
2 - 40
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
1
Formats 3 to 6 (A compatible 1C frame)
PREPARATORY
PROCEDURES FOR
MONITORING
2.5.4
MELSEC-Q/L MELSEC Communication Protocol Reference Manual
This section describes items whose settings differ from the dedicated protocol of the A Series computer link modules,
and the dedicated commands for a GOT microcomputer connection.
Example: Request message for the batch read in word units (QR) command in format 4 (A compatible 1C frame
(format 2))
Character A section
05H
0
PLC No.
0
0
0
0
Command Wait
Q
R
0
30H
30H
30H
30H
30H
30H
30H
51H
52H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Address
Number
of points
Sum
Check
0
2
B
D
0
0
0
1
0
44H
30H
30H
30H
31H
30H
30H
30H
32H
42H
41H
(H)
–
–
–
–
–
(L)
(H)
(L)
(H)
(L)
0
4
A
MODBUS(R)/RTU
CONNECTION
0
Station
No.
Sum check is performed in this range.
 Details of data items in message format
5
MODBUS(R)/TCP
CONNECTION
POINT
Data code during communication
Communication is performed in ASCII code.
6
(1) Block No, PLC No.
Ignored in a microcomputer connection of the GOT.
Specify "00".
"00" is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.
(2) Station No.
Station No. is used to identify the GOT with which the host communicates. (Setting range: 0 to 31)
The address notated in decimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.
The GOT processes only commands whose station No. matches the "Host Address (0 to 31)" set at
"Communication Detail Settings". (The message of command whose station No. does not match is ignored.)
For setting method of "Communication Detail Settings", refer to the following.
2.6.1 Setting communication interface (Communication settings)
(3) Command
Specifies the contents to access from the host to GOT.
The command is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.
For details of the commands that can be used, refer to the following.
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
2.5.2 List of commands
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
CONNECTION TO
SOUND OUTPUT
UNIT
Block No.
CONNECTION TO
EXTERNAL I/O
DEVICE
ENQ
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
This is the same message format as when communication is performed using the dedicated protocol (A compatible
1C frame) of the A Series computer link module.
For details of the basic format of data communication, refer to the following manual:
MICROCOMPUTER
CONNECTION
(SERIAL)
2
 Basic format of data communication
2 - 41
(4) Address
Specifies the head No. of the device data to be read/written.
The data annotated in decimal is converted to a 5- or 7-digit ASCII code (Hex) and transmitted from the upper
digit.
For details of the device range that can be accessed, refer to the following.
2.4 Device Data Area
(5) Number of points
Specifies the number of device data to be read/written. (Setting range: 1 to 40H)
The address notated in hexadecimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper
digit.
(6) Year, month, day, hour, minute, second and day of the week data
Specifies year, month, day, hour, minute, second, and day of the week to be read/set to the GOT clock data.
The address notated in decimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.
■ (1) Read clock data (TR) command
■ (2) Set clock data (TS) command
(7) Error code
This is the response message at faulty communication appended with error contents.
The address notated in hexadecimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper
digit.
For details of error codes generated in formats 3 to 6 (A compatible 1C frame), refer to the following:
■ Error code list
POINT
When connecting a microcomputer, etc. that uses the dedicated protocol of the A series computer link module with
the GOT
When connecting a microcomputer, etc. that uses the dedicated protocol of the A series computer link module with
the GOT, correct the commands to use and the device range according to the specifications of GOT.
2 - 42
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
The following shows the message format of the dedicated commands for a microcomputer connection of GOT.
(1) Read clock data (TR) command
The following shows an example of reading the clock data of GOT.
(Assuming that the clock data of GOT has been set to "2004, June 1, 18:46:49, Tuesday".)
PREPARATORY
PROCEDURES FOR
MONITORING
1
 Message format
2
2004/06/01 18:46:49
Item
MICROCOMPUTER
CONNECTION
(SERIAL)
Time display
TUE
Message format
3
Example: Format 3 (A compatible 1C frame (format 1))
(host
GOT)
05H
Command Wait
0
0
0
0
T
R
0
9
6
30H
30H
30H
30H
54H
52H
30H
39H
36H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
MICROCOMPUTER
CONNECTION
(ETHERNET)
PLC No.
ENQ Station No.
Request message
Sum
Check
Sum check is performed in this range.
4
Example: Format 3 (A compatible 1C frame (format 1))
STX Station No.
02H
Response message
during normal
communication
0
0
0
0
30H
30H
30H
30H
(H)
(L)
(H)
(L)
Following*1
03H
Sum
Check
9
0
39H
30H
(H)
(L)
5
Sum check is performed in this range.
host)
MODBUS(R)/TCP
CONNECTION
(GOT
ETX
PLC No.
MODBUS(R)/RTU
CONNECTION
Character B section
*1
Day data
Hour data
Minute
data
Second
data
Day-ofweek data
0
4
0
6
0
1
1
8
4
6
4
9
0
2
30H
34H
30H
36H
30H
31H
31H
38H
34H
36H
34H
39H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
6
CONNECTION TO
SOUND OUTPUT
UNIT
Year data Month data
Example: Format 3 (A compatible 1C frame (format 1))
host)
15H
PLC No.
Error code
0
0
0
0
0
5
30H
30H
30H
30H
30H
35H
(H)
(L)
(H)
(L)
(H)
(L)
7
The above is the case where an
overrun error (05H) has occurred.
CONNECTION TO
EXTERNAL I/O
DEVICE
(GOT
NAK Station No.
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Response message
during faulty
communication
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 43
(2) Set clock data (TS) command
The following shows an example of setting the clock data of GOT.
(Assuming the clock data of GOT is to be set to "2004, June 1, 18:46:49 Tuesday".)
Time display
2004/06/01 18:46:49
TUE
After execution
Item
Message format
Example: Format 3 (A compatible 1C frame (format 1))
Character C section
ENQ Station No.
05H
Request message
(host
Following*1
0
0
0
0
T
S
0
30H
30H
30H
30H
54H
53H
30H
(H)
(L)
(H)
(L)
(H)
(L)
GOT)
Sum
Check
Command Wait
PLC No.
6
4
36H
34H
(H)
(L)
Sum check is performed in this range.
*1
Year data
Month data
Day data
Second
data
Hour data Minute data
Day-ofweek data
0
4
0
6
0
1
1
8
4
6
4
9
0
2
30H
34H
30H
36H
30H
31H
31H
38H
34H
36H
34H
39H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Example: Format 3 (A compatible 1C frame (format 1))
Response message
during normal
communication
(GOT
ACK Station No.
host)
06H
PLC No.
0
0
0
0
30H
30H
30H
30H
(H)
(L)
(H)
(L)
Example: Format 3 (A compatible 1C frame (format 1))
NAK Station No.
Response message
during faulty
communication
(GOT
15H
host)
PLC No.
Error code
0
0
0
0
0
5
30H
30H
30H
30H
30H
35H
(H)
(L)
(H)
(L)
(H)
(L)
The above is the case where an
overrun error (05H) has occurred.
POINT
When a wrong day of the week has been set by the clock data setting command
If a wrong day of the week is set by the clock data setting commands, the clock data will differ from the time
displayed on the utility.
Example: When June 1, 2004 (Thursday) is set by the clock data setting command (the actual day of week is
Tuesday), Tuesday (TUE) will be displayed on the utility time display.
2 - 44
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
The following shows error code, error contents, cause, and measures.
Description
Action
Parity error
The parity bit does not match.
• Check the communication cable and communication module attachment.
• Check the settings of "Communication Detail Settings".
• Match the GOT and host transmission settings.
02H
Sum check error
The sum check code created from received data differs
from the sum check code in the receive data.
• Review the contents of the message to transmit.
03H
Protocol error
Received a message that does not follow the control
procedure of the format set at "Communication Detail
Settings".
• Check the settings of "Communication Detail Settings".
• Review the contents of the message to transmit.
05H
Overrun error
The next data was transmitted from the host before GOT
completes the processing of the data received.
• Check the settings of "Communication Detail Settings".
• Decrease the transmission speed.
06H
Character section error
The character section specification error.
•The method of specifying the character section is wrong.
•The specified command has error.
•The number of points of the processing requests exceeds
the allowable range.
•A non-existent device has been specified.
•The setting value of the clock data has error.
• Review the contents of the message to transmit.
• Check the commands in the message.
(
2.5.2 List of commands)
• Check the devices that can be used and the device ranges.
(
2.4 Device Data Area)
• Check whether the non-existent data is set (e.g. setting "07" at the day of
the week) as clock data.
4
MODBUS(R)/RTU
CONNECTION
Character error
A character other than "A to Z", "0 to 9", space, and control
codes has been received.
3
• Review the contents of the message to transmit.
MODBUS(R)/TCP
CONNECTION
5
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
07H
2
MICROCOMPUTER
CONNECTION
(SERIAL)
01H
MICROCOMPUTER
CONNECTION
(ETHERNET)
Error code
PREPARATORY
PROCEDURES FOR
MONITORING
1
 Error code list
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 45
2.5.5
Formats 7 to 10 (QnA compatible 3C/4C frame)
 Basic format of data communication
This is the same message format as when communication is performed using the MC protocol (QnA compatible 3C/
4C frame) of the Q/QnA Series serial communication module.
For details of the basic format of data communication, refer to the following manual:
MELSEC-Q/L MELSEC Communication Protocol Reference Manual
This section describes items whose settings differ from the MC protocol of the Q/QnA Series serial communication
module, and the dedicated commands for a GOT microcomputer connection.
Example: Request message for the batch read in word units (0401) command in format 8 (QnA compatible 4C frame
(format 2))
Frame ID
No.
ENQ Block No.
05H
Station No.
Network
No.
PLC No.
Request destination
module I/O No.
Request destination Host Address
module station No. No.
Sum check
Following
*1
0
0
F
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
B
A
30H
30H
46H
38H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
42H
41H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Sum check is performed in this range.
Character A section
*1
Command
Device
code
Sub-command
0
4
0
1
0
0
0
0
D
*
0
0
0
1
0
0
0
0
0
2
30H
34H
30H
31H
30H
30H
30H
30H
44H
2AH
30H
30H
30H
31H
30H
30H
30H
30H
30H
32H
(H)
–
–
(L)
(H)
–
–
(L)
(H)
(L)
(H)
–
–
–
–
(L)
(H)
–
–
(L)
POINT
QnA compatible 4C frame (format 5)
GOT cannot use the QnA compatible 4C frame (format 5).
2 - 46
Device points
Head Device
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
1
PREPARATORY
PROCEDURES FOR
MONITORING
 Details of data items in message format
POINT
Data code during communication
Communication is performed in ASCII code.
MICROCOMPUTER
CONNECTION
(SERIAL)
2
(1) Block No., network No., PLC No., request destination module I/O No. and station No.
Ignored in a microcomputer connection of the GOT.
Specify "00". (The request destination module I/O No. is "0000".)
"00" is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.
(The request destination module I/O No. is 4-digit.)
Station No. is used to identify the GOT with which the host communicates.(Setting range: 0 to 1FH)
The address notated in hexadecimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper
digit.
The GOT processes only commands whose station No. matches the "Host Address (0 to 31)" set at
"Communication Detail Settings". (The message of command whose station No. does not match is ignored.)
For setting method of "Communication Detail Settings", refer to the following.
4
MODBUS(R)/RTU
CONNECTION
2.6.1 Setting communication interface (Communication settings)
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
(2) Station No.
(3) Command, sub-command
Specifies the contents to access from the host to GOT.
The command is converted to a 4-digit ASCII code (Hex) and transmitted from the upper digit.
For details of the commands that can be used, refer to the following.
5
2.5.2 List of commands
MODBUS(R)/TCP
CONNECTION
(4) Device code
Specifies the code by which the device data to be read/written is recognized.
The command is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.
For details of the device range that can be accessed, refer to the following.
2.4 Device Data Area
2.4 Device Data Area
(6) Device points
Specifies the number of device data to be read/written. (Setting range: 1 to 40H)
The address notated in hexadecimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper
digit.
When specifying multiple devices as follows, limit the total device points to within 64 points.
(b) When using multiple block batch read/write commands
When setting multiple blocks, limit the total number of points of all blocks to within 64 points.
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(a) When using random read/write command
When setting multiple bit accesses, word accesses or double word accesses, limit the total number of
access points to within 64 points
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Specifies the head No. of the device data to be read/written.
The address notated in decimal is converted to a 6-digit ASCII code (Hex) and transmitted from the upper digit.
For details of the device range that can be accessed, refer to the following.
CONNECTION TO
SOUND OUTPUT
UNIT
6
(5) Head device
2 - 47
(7) Year, month, day, hour, minute, second and day of the week data
Specifies year, month, day, hour, minute, second, and day of the week to be read/set to the GOT clock data.
The address notated in decimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.
■ Message format (1) Read clock data (1901) command
■ Message format (2) Set clock data (0901) command
(8) Error code
This is the response message at faulty communication appended with error contents.
The address notated in hexadecimal is converted to a 4-digit ASCII code (Hex) and transmitted from the upper
digit.
For details of error codes that are generated in formats 7 to 10 (QnA compatible 3C/4C frame), refer to the
following:
■ Error code list
POINT
When connecting a microcomputer, etc. that uses the MC protocol of the Q/QnA series serial communication
module with the GOT
When connecting a microcomputer, etc. that uses the MC protocol of the Q/QnA series serial communication
module with the GOT, correct the commands to be used and the device ranges to match the GOT specifications.
2 - 48
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
The following shows the message format of the dedicated commands for a microcomputer connection of GOT.
(1) Read clock data (1901) command
The following shows an example of reading the clock data of GOT.
(Assuming that the clock data of GOT has been set to "2004, June 1, 18:46:49, Tuesday".)
PREPARATORY
PROCEDURES FOR
MONITORING
1
 Message format
2
2004/06/01 18:46:49
Item
MICROCOMPUTER
CONNECTION
(SERIAL)
Time display
TUE
Message format
3
Example: Format 7 (QnA compatible 4C frame (format 1))
05H
Frame ID
No.
Station No.
Network
No.
Request destination
module station No.
F
8
0
0
0
0
0
0
0
0
0
0
0
0
46H
38H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
Request message
(host
Request destination
module I/O No.
PLC No.
Sum check
Following
*1
A
9
41H
39H
(H)
(L)
MICROCOMPUTER
CONNECTION
(ETHERNET)
ENQ
Sum check is performed in this range.
GOT)
4
Character A section
*1
Command
Sub-command
0
0
1
9
0
1
0
0
0
0
30H
30H
31H
39H
30H
31H
30H
30H
30H
30H
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
MODBUS(R)/RTU
CONNECTION
Host
Address No.
5
Example: Format 7 (QnA compatible 4C frame (format 1))
0
0
0
0
0
0
0
0
0
0
0
0
46H
38H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
Following
*1
03H
E
E
43H
43H
(H)
(L)
MODBUS(R)/TCP
CONNECTION
8
ETX Sum check
Sum check is performed in this range.
6
Character B section
*1
Host
Address No. Year data
Month data
Day data
Hour data Minute data
Second
data
Day-ofweek data
0
0
0
4
0
6
0
1
1
8
4
6
4
9
0
2
30H
30H
30H
34H
30H
36H
30H
31H
31H
38H
34H
36H
34H
39H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
CONNECTION TO
SOUND OUTPUT
UNIT
host)
Request destination
module station No.
F
Response message
during normal
communication
(GOT
PLC No.
Request destination
module I/O No.
(Continued to next page)
7
CONNECTION TO
EXTERNAL I/O
DEVICE
02H
Station No.
Network
No.
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
STX
Frame ID
No.
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 49
(From previous page)
Item
Message format
Example: Format 7 (QnA compatible 4C frame (format 1))
NAK
Frame ID
No.
F
15H
8
Station No.
0
0
Network
No.
PLC No.
Request destination
module I/O No.
0
0
0
0
0
0
0
host)
0
0
0
46H
38H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
(H)
(L)
*1
Error code
7
F
6
9
37H
46H
36H
39H
(H)
–
–
(L)
The above is the case where a parity error
(7F69H) has occurred.
2 - 50
0
Host
Address No.
(H)
Response message
during faulty
communication
(GOT
0
Request destination
module station No.
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
Following
*1
1
PREPARATORY
PROCEDURES FOR
MONITORING
(2) Set clock data (0901) command
The following shows an example of setting the clock data of GOT.
(Assuming the clock data of GOT is to be set to "2004, June 1, 18:46:49 Tuesday".)
Time display
TUE
After execution
Message format
Example: Format 7 (QnA compatible 4C frame (format 1))
ENQ Frame ID
No.
8
F
05H
Network
No.
Station No.
0
0
0
0
0
0
Request
Host
destination
module station No. Address No.
Request destination
module I/O No.
PLC No.
0
0
0
0
0
0
0
0
Sum check
Following
*1
7
5
46H
38H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
37H
35H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Sum check is performed in this range.
Character C section
*1
(host
GOT)
0
9
0
30H
39H
30H
(H)
–
–
4
Sub-command
1)
0
0
0
31H
30H
30H
30H
30H
(L)
(H)
–
–
(L)
1
0
MODBUS(R)/RTU
CONNECTION
Command
Request message
Character C section
1)
Month data
Day data
Second
data
Hour data Minute data
5
Day-ofweek data
0
4
0
6
0
1
1
8
4
6
4
9
0
2
30H
34H
30H
36H
30H
31H
31H
38H
34H
36H
34H
39H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
MODBUS(R)/TCP
CONNECTION
Year data
Example: Format 7 (QnA compatible 4C frame (format 1))
Response message
during normal
communication
Frame ID
ACK No.
(GOT
06H
Network
No.
PLC No.
Request destination
module I/O No.
Request destination
module station No.
6
Host
Address No.
F
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
46H
38H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
(H)
(L)
(Continued to next page)
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
host)
Station No.
3
CONNECTION TO
SOUND OUTPUT
UNIT
Item
MICROCOMPUTER
CONNECTION
(SERIAL)
2
MICROCOMPUTER
CONNECTION
(ETHERNET)
2004/06/01 18:46:49
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 51
(From previous page)
Item
Message format
Example: Format 7 (QnA compatible 4C frame (format 1))
Frame ID
No.
NAK
F
15H
Response message
during faulty
communication
(GOT
8
Station No.
0
0
Network
No.
0
PLC No.
0
0
0
Request destination
module I/O No.
0
0
0
0
Request destination
module station No.
0
0
Host
Address No.
0
0
46H
38H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
(H)
(L)
Following*1
*1
host)
Error code
7
F
6
9
37H
46H
36H
39H
(H)
–
–
(L)
The above is the case where a
parity error (7F69H) has occurred.
POINT
When a wrong day of the week has been set by the clock data setting command
If a wrong day of the week is set by the clock data setting commands, the clock data will differ from the time
displayed on the utility.
Example: When June 1, 2004 (Thursday) is set by the clock data setting command (the actual day of week is
Tuesday), Tuesday (TUE) will be displayed on the utility time display.
2 - 52
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
1
PREPARATORY
PROCEDURES FOR
MONITORING
 Error code list
The following shows error code, error contents, cause, and measures.
Action
7E42H
Number of data error
The number of requests exceeds the command range.
7E43H
Device error
A non-existent device has been specified.
(
2
2.5.2 List of commands)
MICROCOMPUTER
CONNECTION
(SERIAL)
7E41H
Data length error
Specified points exceeding the number of points that can
be communicated during random read/write.
• Review the contents of the message to transmit.
• Check the commands in the message.
• Review the contents of the message to transmit.
• Check the devices that can be used and the device ranges.
(
2.4 Device Data Area)
• Review the contents of the message to transmit.
• Check the devices that can be used and the device ranges.
(
3
2.4 Device Data Area)
• Review the contents of the message to transmit.
• Check whether the non-existent data is set (e.g. setting "07" at the day of
the week) as clock data.
7E46H
Clock data setting error
The setting value of the clock data has error.
7E4FH
Exceeded number of points error
The read/write range exceeded the device range.
7F20H
Character error
A character other than "A to Z", "0 to 9", space, and control
codes has been received.
• Review the contents of the message to transmit.
7F23H
Communication message error
EXT/CR+LF was not found within the upper limit of the
receive buffer.
• Check the communication cable and communication module attachment.
• Check the settings of "Communication Detail Settings".
• Review the contents of the message to transmit.
7F24H
Sum check error
The sum check code created from received data differs
from the sum check code in the receive data.
• Review the contents of the message to transmit.
7F67H
Overrun error
The next data was transmitted from the host before GOT
completes the processing of the data received.
• Check the settings of "Communication Detail Settings".
• Decrease the transmission speed.
7F68H
Framing error
The data bit and/or stop bit are not correct.
7F69H
Parity error
The parity bit does not match.
7F6AH
Buffer full error
The receive buffer overflowed.
• Review the contents of the message to transmit.
• Check the devices that can be used and the device ranges.
(
2.4 Device Data Area)
MICROCOMPUTER
CONNECTION
(ETHERNET)
Command error
An unsupported command or sub-command was used.
4
MODBUS(R)/RTU
CONNECTION
7E40H
5
• Check the communication cable and communication module attachment.
• Check the settings of "Communication Detail Settings".
• Match the GOT and host transmission settings.
• Check the communication cable and communication module attachment.
• Check the settings of "Communication Detail Settings".
• Review the contents of the message to transmit.
MODBUS(R)/TCP
CONNECTION
Description
6
CONNECTION TO
SOUND OUTPUT
UNIT
Error code
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 53
2.5.6
Formats 11 to 13 (Digital Electronics Corporation's memory link method)
 Basic format of data communication
This is the same format as the protocol of the Digital Electronics Corporation's memory link method.
For details of the basic format of data communication, refer to the following manual:
The connection manual of the device manufactured by Digital Electronics Corporation
This section describes items whose settings differ from the protocols of the Digital Electronics Corporation's memory
link method and dedicated commands for a microcomputer connection of GOT.
Example:Request message for the batch read in word units (R) command in format 13 (Digital Electronics
Corporation's memory link method (extended mode, ASCII code 1:n))
ENQ Station No. ESC Command
05H
0
0
30H
30H
(H)
(L)
1BH
Number of points
Address
Sum
Check
R
0
0
6
4
0
0
0
2
5
E
52H
30H
30H
36H
34H
30H
30H
30H
32H
35H
45H
(H)
–
–
(L)
(H)
–
–
(L)
(H)
(L)
CR
LF
0DH
0AH
Sum check is performed in this range.
POINT
Compatibility with the Digital Electronics Corporation's memory link method
In the case of formats 12 and 13 (Digital Electronics Corporation's memory link method (extended mode)), a
communication error may occur since some communication packets are not compatible with the Digital Electronics
Corporation's memory link method in the communication.
To give the compatibility, turn on the digital compatible signals (GS580 to GS583) of the GOT internal device and
communicate in the fully compatible message format.
Device
GS580
GS581
GS582
GS583
Function
Bit
Bit position
Microcomputer connection (serial) extended
setting (CH1)
Digital compatible
signal
b0
0: Partly compatible (Default)
1: Fully compatible
b1 to b15
Unused
Microcomputer connection (serial) extended
setting (CH2)
Digital compatible
signal
b0
0: Partly compatible (Default)
1: Fully compatible
b1 to b15
Unused
Microcomputer connection (serial) extended
setting (CH3)
Digital compatible
signal
b0
0: Partly compatible (Default)
1: Fully compatible
b1 to b15
Unused
Microcomputer connection (serial) extended
setting (CH4)
Digital compatible
signal
b0
0: Partly compatible (Default)
1: Fully compatible
b1 to b15
Unused
For the GOT internal device, refer to the following manual.
GT Designer3 Version1 Screen Design Manual (Fundamentals)
2 - 54
Settings
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
1
PREPARATORY
PROCEDURES FOR
MONITORING
 Details of data items in message format
POINT
Data code during communication
Communication is performed in ASCII code.
MICROCOMPUTER
CONNECTION
(SERIAL)
2
Specifies the contents to access from the host to GOT.
The command is converted to a 1-digit ASCII code (Hex) and transmitted.
For details of the commands that can be used, refer to the following.
2.5.2 List of commands
(2) Station No.
Station No. is used to identify the GOT with which the host communicates. (Setting range: 0 to 1FH)
The address notated in hexadecimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper
digit.
The GOT processes only commands whose station No. matches the "Host Address (0 to 31)" set at
"Communication Detail Settings". (The message of command whose station No. does not match is ignored.)
For setting method of "Communication Detail Settings", refer to the following.
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
(1) Command
4
2.6.2 Communication detail settings
Specifies the head No. of the device data to be read/written.
The address notated in hexadecimal is converted to a 4-digit ASCII code (Hex) and transmitted from the upper
digit.
For details of the device range that can be accessed, refer to the following.
2.4 Device Data Area
MODBUS(R)/RTU
CONNECTION
(3) Address
■ Message format (1) Read clock data (N) command
■ Message format (2) Set clock data (M) command
(6) Error code
This is the response message at faulty communication appended with error contents.
The address notated in hexadecimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper
digit.
For details of error codes generated in formats 12 and 13 (Digital Electronics Corporation's memory link method
(extended mode)), refer to the following:
■ Error code list
POINT
When connecting a microcomputer, etc. that uses the protocol of the Digital Electronics Corporation's memory link
method with the GOT
When connecting a microcomputer, etc. that uses the protocol of the Digital Electronics Corporation's memory link
method with the GOT, correct the commands to be used and the device ranges to match the specifications of the
GOT.
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 55
6
CONNECTION TO
SOUND OUTPUT
UNIT
Specifies year, month, day, hour, minute, second, and day of the week to be read/set to the GOT clock data.
The address notated in decimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
(5) Year, month, day, hour, minute, second and day of the week data
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Specifies the number of device data to be read/written. (Setting range: 1 to 40H)
The address notated in hexadecimal is converted to a 4-digit ASCII code (Hex) and transmitted from the upper
digit.
MODBUS(R)/TCP
CONNECTION
5
(4) Number of points
 Message format
The following shows the message format of the dedicated commands for a microcomputer connection of GOT.
(1) Read clock data (N) command
The following shows an example of reading the clock data of GOT.
(Assuming that the clock data of GOT has been set to "2004, June 1, 18:46:49, Tuesday".)
Time display
2004/06/01 18:46:49
Item
TUE
Message format
Example: Format 13 (Digital Electronics Corporation's memory link method (extended mode, ASCII code 1:n))
• Digital compatible signal (GS580 to GS583): OFF (Partly compatible)
ENQ Station No. ESC Command
05H
Request message
(host
GOT)
0
0
30H
30H
(H)
(L)
1BH
Sum
Check
N
C
E
4EH
43H
45H
(H)
(L)
CR
LF
0DH
0AH
CR
LF
0DH
0AH
This range Sum check
• Digital compatible signal (GS580 to GS583): ON (Fully compatible)
ENQ Station No. ESC Command
05H
0
0
30H
30H
(H)
(L)
1BH
Sum
Check
N
C
9
4EH
43H
39H
(H)
(L)
This range Sum check
(Continued to next page)
2 - 56
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
Item
Message format
Example: Format 13 (Digital Electronics Corporation's memory link method (extended mode, ASCII code 1:n))
• Digital compatible signal (GS580 to GS583): OFF (Partly compatible)
02H
0
0
30H
30H
(H)
(L)
A
1BH
Sum
Check
ETX
*1
Following
03H
41H
8
E
38H
45H
(H)
(L)
CR
LF
0DH
0AH
2
MICROCOMPUTER
CONNECTION
(SERIAL)
STX Station No. ESC Command
This range Sum check
*1
(GOT
host)
Day data
Hour data Minute data
Second
data
Day-ofweek data
0
4
0
6
0
1
1
8
4
6
4
9
0
2
30H
34H
30H
36H
30H
31H
31H
38H
34H
36H
34H
39H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
3
• Digital compatible signal (GS580 to GS583): ON (Fully compatible)
STX Station No. ESC Command
02H
0
0
30H
30H
(H)
(L)
A
1BH
ETX
Following*1
03H
41H
Sum
Check
8
C
38H
43H
(H)
(L)
CR
0DH
LF
4
0AH
MODBUS(R)/RTU
CONNECTION
Response message
during normal
communication
Month data
MICROCOMPUTER
CONNECTION
(ETHERNET)
Year data
This range Sum check
*1
0
4
Month data
0
6
Day data
0
1
Hour data Minute data
1
8
4
6
Second
data
4
9
Day-ofweek data
0
5
2
30H
34H
30H
36H
30H
31H
31H
38H
34H
36H
34H
39H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
MODBUS(R)/TCP
CONNECTION
Year data
Example: Format 13 (Digital Electronics Corporation's memory link method (extended mode, ASCII code 1:n))
0
0
0
6
30H
30H
30H
36H
(H)
(L)
(H)
(L)
LF
0DH
0AH
6
CONNECTION TO
SOUND OUTPUT
UNIT
host)
15H
CR
The above is a case where the sum
check error (06H) has occurred.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
(GOT
NAK Station No. Error code
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Response message
during faulty
communication
1
PREPARATORY
PROCEDURES FOR
MONITORING
(From previous page)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 57
(2) Set clock data (M) command
The following shows an example of setting the clock data of GOT.
(Assuming the clock data of GOT is to be set to "2004, June 1, 18:46:49 Tuesday".)
Time display
2004/06/01 18:46:49
TUE
After execution
Item
Message format
Example: Format 13 (Digital Electronics Corporation's memory link method (extended mode, ASCII code 1:n))
• Digital compatible signal (GS580 to GS583): OFF (Partly compatible)
ENQ Station No.
0
0
30H
30H
(H)
(L)
05H
Sum
Check
ComESC mand
M
1BH
Following*1
4DH
9
CR
LF
A
39H
41H 0DH
(H)
(L)
0AH
Sum check is performed in this range.
*1
Year data Month data
Request message
(host
GOT)
Day data
Hour data
Day-ofMinute data Second data week data
0
4
0
6
0
1
1
8
4
6
4
9
0
2
30H
34H
30H
36H
30H
31H
31H
38H
34H
36H
34H
39H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
CR
LF
• Digital compatible signal (GS580 to GS583): ON (Fully compatible)
Sum
Check
ComENQ Station No. ESC mand
05H
0
0
30H
30H
(H)
(L)
M
1BH
Following
*1
4DH
9
5
39H
35H 0DH
(H)
(L)
0AH
Sum check is performed in this range.
*1
Year data Month data
Day data
Hour data
Day-ofMinute data Second data week data
0
4
0
6
0
1
1
8
4
6
4
9
0
2
30H
34H
30H
36H
30H
31H
31H
38H
34H
36H
34H
39H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Example: Format 13 (Digital Electronics Corporation's memory link method (extended mode, ASCII code 1:n))
Response message
during normal
communication
(GOT
host)
ACK Station No. CR
06H
0
0
30H
30H
(H)
(L)
0DH
LF
0AH
(Continued to next page)
2 - 58
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
Message format
Example: Format 13 (Digital Electronics Corporation's memory link method (extended mode, ASCII code 1:n))
host)
15H
0
0
0
6
30H
30H
30H
36H
(H)
(L)
(H)
(L)
CR
LF
0DH
0AH
2
The above is a case where the sum
check error (06H) has occurred.
POINT
3
When a wrong day of the week has been set by the clock data setting command
If a wrong day of the week is set by the clock data setting commands, the clock data will differ from the time
displayed on the utility.
Example: When June 1, 2004 (Thursday) is set by the clock data setting command (the actual day of week is
Tuesday), Tuesday (TUE) will be displayed on the utility time display.
MODBUS(R)/RTU
CONNECTION
4
MODBUS(R)/TCP
CONNECTION
5
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(GOT
NAK Station No. Error code
MICROCOMPUTER
CONNECTION
(SERIAL)
Response message
during faulty
communication
MICROCOMPUTER
CONNECTION
(ETHERNET)
Item
1
PREPARATORY
PROCEDURES FOR
MONITORING
(From previous page)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 59
(3) In the case of interrupt inquiry
The following shows an example of an interrupt inquiry when data are written to the interrupt output devices
(D13 and D14).
(Assuming that "3139H" is written to D13 and "AA55H" to D14.)
Example: When the number of interrupt data bytes is 2 in format 11
D13
3139H
Interrupt
Interrupt output
Output Output
value 1 value 2
31H
Item
39H
Message format
Example: Format 13 (Digital Electronics Corporation's memory link method (extended mode, ASCII code 1:n))
• Digital compatible signal (GS580 to GS583): OFF (Partly compatible)
ENQ Station No. ESC Command
05H
Request message
(host
GOT)
0
0
30H
30H
(H)
(L)
1BH
Sum
Check
I
C
9
49H
43H
39H
(H)
(L)
CR
LF
0DH
0AH
CR
LF
0DH
0AH
This range Sum check
• Digital compatible signal (GS580 to GS583): ON (Fully compatible)
ENQ Station No. ESC Command
05H
0
0
30H
30H
(H)
(L)
1BH
Sum
Check
I
C
4
49H
43H
34H
(H)
(L)
This range Sum check
(Continued to next page)
2 - 60
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
Item
Message format
Example: Format 13 (Digital Electronics Corporation's memory link method (extended mode, ASCII code 1:n))
(1) When [Interrupt Data Byte] in "Communication Detail Settings" is set to "1 byte"
0
02H
0
30H
30H 1BH
(H)
(L)
Output
value 1
I
3
9
49H
33H
39H
(H)
(L)
Sum
Check
ETX
03H
9
4
39H
44H
(H)
(L)
CR
LF
0DH
0AH
2
MICROCOMPUTER
CONNECTION
(SERIAL)
ComSTX Station No. ESC mand
This range Sum check is performed.
(2) When [Interrupt Data Byte] in "Communication Detail Settings" is set to "2 byte"
Interrupt inquiry
host)
02H
0
30H
30H
(H)
(L)
I
1BH
49H
Output
value 2
3
3
1
ETX
9
33H
31H
33H
39H
(H)
(L)
(H)
(L)
Sum
Check
F
03H
CR
LF
0DH
0A H
3
9
46H
39H
(H)
(L)
Sum check is performed in this range.
(3) When [Interrupt Data Byte] in "Communication Detail Settings" is set to "4 byte"
Station No. ESC Command
0
0
02H
30H
30H
(H)
(L)
1BH
Output
value 1
Output
value 2
Output
value 3
Output
value 4
I
A
A
5
5
3
1
3
9
49H
41H
41H
35H
35H
33H
31H
33H
39H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
ETX
Sum
Check
E
03H
CR
4
LF
MODBUS(R)/RTU
CONNECTION
STX
7
45H
37H 0DH
(H)
(L)
0AH
Sum check is performed in this range.
POINT
Interrupt output
• To disable the interrupt output, turn ON SM52 (interrupt code output disable flag).(
2.4.6 SM devices)
• To issue interrupts in format 11, set the data length to "8 bits" at "Communication Detail Settings".
(
2.6.1 Setting communication interface (Communication settings))
7FH)
• When "7 bits" is set, the MSB (8th bit) is ignored.(Example: FFH
MODBUS(R)/TCP
CONNECTION
5
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(GOT
0
Output
value 1
MICROCOMPUTER
CONNECTION
(ETHERNET)
STX Station No. ESC Command
1
PREPARATORY
PROCEDURES FOR
MONITORING
(From previous page)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 61
 Error code list
In the case of formats 12 and 13 (Digital Electronics Corporation's memory link method (extended mode)), the details
(error code) of the error are appended to the response message during faulty communication.
The following shows error code, error contents, cause, and measures.
Error code
Description
Action
06H
Sum check error
The sum check code created from received data differs
from the sum check code in the receive data.
10H
Command error
An unsupported command was used.
12H
Message length error
The upper limit of the data length that can be received by
the GOT has been exceeded.
16H
Clock data setting error
The setting value of the clock data has error.
• Review the contents of the message to transmit.
• Check the data length of the message.(data length of the data section,
etc.)
FAH
Address error
The start address of the read/write device is out of range.
• Review the contents of the message to transmit.
• Check whether the non-existent data is set (e.g. setting "07" at the day of
the week) as clock data.
FBH
Exceeded number of points error
The read/write range exceeded the device range.
• Review the contents of the message to transmit.
• Review the contents of the message to transmit.
• Check the commands in the message.
(
2.5.2 List of commands)
• Review the contents of the message to transmit.
• Check the devices that can be used and the device ranges.
(
2.4 Device Data Area)
FCH
Message format error
The format of the received message has error.
• Check the settings of "Communication Detail Settings".
• Review the contents of the message to transmit.
FFH
Timeout error
There is no response from the GOT, or the station of the
specified address does not exist.
• Check the communication cable and communication module attachment.
• Check the settings of "Communication Detail Settings".
• Review the contents of the message to transmit.
 Precautions
(1) Batch reading/writing crossing over different devices
When using the batch read (R) or batch write (W) command, do not batch read/write crossing over the different
devices.
This will cause an error response.
(2) Storage order for 32-bit data
To use the program of Digital Electronics Corporation's memory link method with [32bit Order] setting to
GOT1000 series, set [HL Order] to [32bit Order] for [Communication Detail Settings] when 32-bit data is set for
GOT-A900 series.
With setting [LH Order], the order of upper bits and lower bits are reversed when the GOT displays and writes
32-bit data.
2 - 62
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
1
Formats 14, 15 (GOT-F900 Series microcomputer connection)
PREPARATORY
PROCEDURES FOR
MONITORING
2.5.7
 Basic format of data communication
Message format
Data
02H
CR
STX Command
0DH
02H
Data
Sum
Check
ETX
03H
(H)
(L)
Request message
(host
Sum check is performed in this range.
GOT)
(2) w/station No.
(2) w/station No.
STX Com- Station No.
mand
Data
02H
(H)
CR
STX Command Station No.
0DH
02H
(L)
Data
4
Sum
Check
ETX
03H
(H)
(L)
(H)
(L)
Sum check is performed in this range.
(1) During processing of read commands
(format 14: GOT-F900 Series microcomputer connection (format 1))
STX
02H
Response message
during normal
communication
host)
(format 15: GOT-F900 Series microcomputer connection (format 2))
CR
STX
0DH
02H
Data
Sum
Check
ETX
03H
(H)
(L)
6
Sum check is performed in this range.
(2) During processing of write commands
ACK
06H
NAK
(GOT
15H
host)
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Response message
during faulty
communication
Output
value
During interrupt
output
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
1/2/4
bytes*1
*1
Set the number of interrupt data bytes at [Detail setting] in GT Designer3.
For the setting of the number of interrupt data bytes, refer to the following.
2.6.1 Setting communication interface (Communication settings)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
5
CONNECTION TO
SOUND OUTPUT
UNIT
(GOT
Data
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
STX Command
(format 15: GOT-F900 Series microcomputer connection (format
2))
(1) w/out station No.
MODBUS(R)/RTU
CONNECTION
(format 14: GOT-F900 Series microcomputer connection (format
1))
(1) w/out station No.
MODBUS(R)/TCP
CONNECTION
Item
MICROCOMPUTER
CONNECTION
(SERIAL)
2
2 - 63
 Details of data items in message format
POINT
Data code during communication
Communication is performed in ASCII code. (excluding interrupt output)
(1) Control codes
Symbol
ASCII code
STX
02H
Start of Text (start marker of message frame)
Description
ETX
03H
End of Text (end marker of message frame)
EOT
04H
End of Transmission
ENQ
05H
Enquiry (start of enquiry)
NAK
15H
Negative ACK (error response)
ACK
06H
Acknowledge (write completion response)
LF
0AH
Line Feed
CL
0CH
Clear
CR
0DH
Carriage Return
(2) Command
Specifies the contents to access from the host to GOT.
The command is converted to a 1-digit ASCII code (Hex) and transmitted.
For details of the commands that can be used, refer to the following.
2.5.2 List of commands
(3) Station No.
Station No. is used to identify the GOT with which the host communicates. (Setting range: 0 to 31)
The address notated in decimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.
The GOT processes only commands whose station No. matches the "Host Address (0 to 31)" set at
"Communication Detail Settings". (The message of command whose station No. does not match is ignored.)
For setting method of "Communication Detail Settings", refer to the following.
2.6.1 Setting communication interface (Communication settings)
(4) Address
Specifies the head No. of the device data to be read/written.
The address notated in hexadecimal is converted to a 4-digit ASCII code (Hex) and transmitted from the upper
digit.
For details of the device range that can be accessed, refer to the following.
2.4 Device Data Area
(5) Bit pattern
Specifies the pattern of the bits to change.
The address notated in hexadecimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper
digit.
■ Message format (3) Multi-point write in bit units (3) command (w/out station No.), multi-point
write in bit units (D) command (w/ station No.)
(6) Write specification
Specifies how to change the data of the specified address by bit pattern.
(Setting range: 0 to 3)
Data notated in decimal is converted to a 1-digit ASCII code (Hex) and transmitted.
■ Message format (3) Multi-point write in bit units (3) command (w/out station No.), multi-point
write in bit units (D) command (w/ station No.)
2 - 64
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
(9) Year, month, day, hour, minute, second and day of the week data
Specifies year, month, day, hour, minute, second, and day of the week to be read/set to the GOT clock data.
The address notated in decimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.
■ (5) Read clock data (6) command (w/out station No.), read clock data (G) command (w/station
No.)
■ (6) Set clock data (5) command (w/out station No.), set clock data (F) command (w/station No.)
(10) Data
Specifies the data to read from/write to the specified device data.(word unit)
The address notated in hexadecimal is converted to a 4-digit ASCII code (Hex) and transmitted from the upper
digit.
(11) Write data
Specifies the data to write to the specified device data.
The address notated in hexadecimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper
digit.
(12) Sum check code (for format 15: GOT-F900 series microcomputer connection (format 2) only)
The sum check code is obtained by converting the lower 1 byte (8 bits) of the result (sum), after having added
the sum check target data as binary data, to 2-digit ASCII code (Hex).
02H
Number of
points
Address
R
D
0
1
0
0
0
2
52H
44H
30H
31H
30H
30H
30H
32H
(H)
(L)
(H)
–
–
(L)
(H)
(L)
Sum
Check
ETX
B
C
42H
43H
(H)
(L)
03H
3
4
5
MODBUS(R)/TCP
CONNECTION
STX Command
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Specifies the number of device data to be written to multiple points in bit units.(Setting range: 0 to 70)
The address notated in decimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.
MICROCOMPUTER
CONNECTION
(ETHERNET)
(8) Number of points
MODBUS(R)/RTU
CONNECTION
Specifies the number of bytes of the device data to be batch read/written.(Setting range: 0 to FFH)
The address notated in hexadecimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper
digit.
PREPARATORY
PROCEDURES FOR
MONITORING
1
(7) Number of bytes
Sum check is performed in this range.
CONNECTION TO
SOUND OUTPUT
UNIT
6
52H + 44H + 30H + 31H + 30H + 30H + 30H + 32H + 03H = 1BCH
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 65
 Message format
(1) Batch read (0) command (w/out station No.), batch read (A) command (w/station No.)
(a) When reading a word device
The following shows an example of reading four bytes of virtual devices R100 to R101 from the GOT at
station No.15.
(Assuming R100=3D21H, R101=3604H are stored.)
Item
R100
3D21H
R101
3604H
Message format
(format 14: GOT-F900 Series microcomputer connection (format 1))
STX Com- Station No.
mand
02H
Request message
(host
GOT)
Number
of bytes
Address
CR
A
1
5
0
0
C
8
0
4
41H
31H
35H
30H
30H
43H
38H
30H
34H
(H)
(L)
(H)
–
–
(L)
(H)
(L)
0DH
(format 15: GOT-F900 Series microcomputer connection (format 2))
STX Command Station No.
02H
Number of
bytes
Address
Sum
Check
ETX
A
1
5
0
0
C
8
0
4
41H
31H
35H
30H
30H
43H
38H
30H
34H
(H)
(L)
(H)
–
–
(L)
(H)
(L)
03H
E
9
45H
39H
(H)
(L)
Sum check is performed in this range.
(format 14: GOT-F900 Series microcomputer connection (format 1))
Data 1
Data 2
Data 3
Data 4
STX (R100 upper) (R100 lower) (R101 upper) (R101 lower) CR
02H
Response message
during normal
communication
(GOT
host)
3
D
2
1
3
6
0
33H
44H
32H
31H
33H
36H
30H
4
34H 0DH
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(format 15: GOT-F900 Series microcomputer connection (format 2))
Data 4
Data 3
Data 1
Data 2
STX (R100 upper) (R100 lower) (R101 upper) (R101 lower) ETX
02H
3
D
2
1
3
6
0
4
33H
44H
32H
31H
33H
36H
30H
34H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Sum check is performed in this range.
Response message
during faulty
communication
NAK
(GOT
15H
2 - 66
host)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
03H
Sum
Check
A
A
41H
41H
(H)
(L)
1
0001H
M31 to 16
8000H
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Item
M15 to 0
PREPARATORY
PROCEDURES FOR
MONITORING
(b) When reading a bit device
The following shows an example of reading four bytes of the virtual devices M0 to M31.
(Assuming M0="1" and M31="1" are stored.
Message format
(format 14: GOT-F900 Series microcomputer connection (format 1))
1
A
02H
(host
GOT)
5
2
0
0
0
0
CR
3
4
31H
35H
32H
30H
30H
30H
30H
34H
(H)
(L)
(H)
–
–
(L)
(H)
(L)
0DH
(format 15: GOT-F900 Series microcomputer connection (format 2))
Station No.
STX Command
02H
Sum
Check
Number of ETX
bytes
Address
A
1
5
2
0
0
0
0
4
41H
31H
35H
32H
30H
30H
30H
30H
34H
(H)
(L)
(H)
–
–
(L)
(H)
(L)
03H
D
0
44H
30H
(H)
(L)
4
MODBUS(R)/RTU
CONNECTION
Request message
41H
Number of
bytes
Address
MICROCOMPUTER
CONNECTION
(ETHERNET)
ComSTX mand Station No.
Sum check is performed in this range.
STX
Data 1
(M7 to 0)
0
02H
1
Data 2
Data 3
Data 4
(M15 to 8) (M23 to 16) (M31 to 24)
0
0
0
0
8
CR
5
0DH
MODBUS(R)/TCP
CONNECTION
(format 14: GOT-F900 Series microcomputer connection (format 1))
0
30H
31H
30H
30H
30H
30H
38H
30H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
00000001000000000000000010000000
CONNECTION TO
SOUND OUTPUT
UNIT
(GOT
6
(format 15: GOT-F900 Series microcomputer connection (format 2))
host)
Sum check is performed in this range.
Data 2
(M15 to 8)
Data 3
Data 4
(M23 to 16) (M31 to 24) ETX
STX
Data 1
(M7 to 0)
0
1
0
0
0
0
8
0
02H
30H
31H
30H
30H
30H
30H
38H
30H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
03H
Sum
Check
8
C
38H
43H
(H)
(L)
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Response message
during normal
communication
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
76543210111111982222111133222222
543210
3210987610987654
00000001000000000000000010000000
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
76543210111111982222111133222222
543210
3210987610987654
NAK
(GOT
15H
host)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
Response message
during faulty
communication
2 - 67
(2) Batch write (1) command (w/out station No.), batch write (B) command (w/station No.)
(a) When writing to a word device
The following shows an example of writing "0064H" and "0065H" to virtual devices R100 and R101 on the
GOT at station No.15.
R100
0000H
R100
0064H
R101
0000H
R101
0065H
Before execution
After execution
Item
Message format
(format 14: GOT-F900 Series microcomputer connection (format 1))
STX Command Station No.
02H
Number of
bytes
Address
B
1
5
0
0
C
8
0
4
42H
31H
35H
30H
30H
43H
38H
30H
34H
(H)
(L)
(H)
(L)
(H)
(L)
CR
Following
*1
0DH
(format 15: GOT-F900 Series microcomputer connection (format 2))
Request message
(host
STX Com- Station No.
mand
GOT)
02H
Number
of bytes
Address
B
1
5
0
0
C
8
0
4
42H
31H
35H
30H
30H
43H
38H
30H
34H
(H)
(L)
(H)
–
–
(L)
(H)
(L)
ETX
Following*1
Sum check is performed in this range.
*1
Data 1
Data 2
Data 3
Data 4
(R100 upper) (R100 lower) (R101 upper) (R101 lower)
0
0
6
4
0
0
6
5
30H
30H
36H
34H
30H
30H
36H
35H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Response message
during normal
communication
ACK
(GOT
06H
host)
Response message
during faulty
communication
NAK
(GOT
15H
2 - 68
host)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
03H
Sum
Check
9
1
39H
31H
(H)
(L)
M15 to 0
0000H
M15 to 0
0001H
M31 to 16
0000H
M31 to 16
8000H
2
After execution
Item
MICROCOMPUTER
CONNECTION
(SERIAL)
Before execution
Message format
(format 14: GOT-F900 Series microcomputer connection (format 1))
02H
Number of
bytes
Address
B
1
5
2
0
0
0
0
4
42H
31H
35H
32H
30H
30H
30H
30H
34H
(H)
(L)
(H)
–
–
(L)
(H)
(L)
CR
Following
3
*1
0DH
MICROCOMPUTER
CONNECTION
(ETHERNET)
ComSTX mand Station No.
(format 15: GOT-F900 Series microcomputer connection (format 2))
Station No.
STX Command
02H
B
1
5
2
0
0
0
0
4
42H
31H
35H
32H
30H
30H
30H
30H
34H
(H)
(L)
(H)
–
–
(L)
(H)
(L)
Request message
ETX
Following*1
03H
Sum
Check
5
A
35H
41H
(H)
(L)
4
GOT)
MODBUS(R)/RTU
CONNECTION
(host
Byte
Number
Address
Sum check is performed in this range.
*1
Data 2
Data 3
Data 4
(M15 to 8) (M23 to 16) (M31 to 24)
0
1
0
0
0
0
8
0
30H
31H
30H
30H
30H
30H
38H
30H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
5
MODBUS(R)/TCP
CONNECTION
Data 1
(M7 to 0)
00000001000000000000000010000000
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
76543210111111982222111133222222
543210
3210987610987654
(GOT
06H
host)
Response message
during faulty
communication
NAK
(GOT
15H
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
host)
CONNECTION TO
SOUND OUTPUT
UNIT
ACK
6
CONNECTION TO
EXTERNAL I/O
DEVICE
Response message
during normal
communication
1
PREPARATORY
PROCEDURES FOR
MONITORING
(b) When writing to a bit device
The following shows an example of writing "1"s to virtual devices M0 and M31 on the GOT at station No.15.
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 69
(3) Multi-point write in bit units (3) command (w/out station No.), multi-point write in bit units (D) command (w/
station No.)
The following shows an example of turning OFF the virtual device M31 and turning ON the virtual device M2038
on the GOT at station No.31.
Item
Message format
(format 14: GOT-F900 Series microcomputer connection (format 1))
Number of
ComSTX mand Station No.
points
02H
D
3
1
0
2
44H
33H
31H
30H
32H
(H)
(L)
(H)
(L)
CR
Following*1
0DH
(format 15: GOT-F900 Series microcomputer connection (format 2))
STX Com- Station No. Number of
mand
points
02H
D
3
1
0
2
44H
33H
31H
30H
32H
(H)
(L)
(H)
(L)
Following
03H
E
C
45H
43H
(H)
(L)
Sum check is performed in this range.
Request message
(host
ETX Sum check
*1
GOT)
*1
Write
specification
1
Bit pattern1
Address1
Write
specification
2
Bit pattern2
1
2
0
0
3
8
0
0
2
0
F
E
4
0
31H
32H
30H
30H
33H
38H
30H
30H
32H
30H
46
45H
34H
30H
(H)
–
–
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
*2
*2
(write specification1=1)
Source data
bit pattern
Result
(write specification2=0)
10101010
10000000
Source data
bit pattern
00101010
Result
MMMMMMMM
33222222
10987654
Response message
during normal
communication
ACK
(GOT
06H
host)
Response message
during faulty
communication
NAK
(GOT
15H
2 - 70
Address2
host)
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
10101010
01000000
11101010
MMMMMMMM
22222222
00000000
33333333
98765432
0
ON
specification
Description
Action example
Original data
The numerical values to write by the bit pattern are specified
directly.
Original data
1010
Bit pattern
1100
Result
0010
Original data
1010
Bit pattern
1100
Result
0110
Original data
1010
Bit pattern
1100
Result
1100
2
3
4
MODBUS(R)/RTU
CONNECTION
Write
specification
Bits set to "1" by the bit pattern are inverted.
1110
5
MODBUS(R)/TCP
CONNECTION
3
Invert
specification
1100
Result
6
CONNECTION TO
SOUND OUTPUT
UNIT
2
Bits set to "1" by the bit pattern are turned OFF.
Bit pattern
7
CONNECTION TO
EXTERNAL I/O
DEVICE
1
OFF
specification
Bits set to "1" by the bit pattern are turned ON.
1010
MICROCOMPUTER
CONNECTION
(SERIAL)
Function
MICROCOMPUTER
CONNECTION
(ETHERNET)
Write
specification
PREPARATORY
PROCEDURES FOR
MONITORING
1
The write specification specifies how the data of the specified address is changed in the bit pattern.
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
*2
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 71
(4) Fill command (4) (w/out station No.), fill command (E) (w/station No.)
The following shows an example of writing "16"s to virtual devices R50 to R100 on the GOT at station No.27.
R50
0000H
1616H
R50
1616H
0000H
R100
R100
0000H
Before execution
1616H
After execution
Item
Message format
(format 14: GOT-F900 Series microcomputer connection (format 1))
STX Com- Station No.
mand
02H
Request message
(host
GOT)
Start address
Write
Data
End address
CR
E
2
7
0
0
6
4
0
0
C
9
1
45H
32H
37H
30H
30H
36H
34H
30H
30H
43H
39H
31H
36H 0DH
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
(H)
(L)
6
(format 15: GOT-F900 Series microcomputer connection (format 2))
STX Command Station No.
02H
Start address
Write
Data
End address
E
2
7
0
0
6
4
0
0
C
9
1
6
45H
32H
37H
30H
30H
36H
34H
30H
30H
43H
39H
31H
36H
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
(H)
(L)
ETX
03H
Sum
Check
B
E
42H
45H
(H)
(L)
Sum check is performed in this range.
Response message
during normal
communication
ACK
(GOT
06H
host)
Response message
during faulty
communication
NAK
(GOT
15H
host)
POINT
(1) Start address/end address specification conditions
Specify addresses so that the start address is the same or less than the end address.
Error response occurs in the following cases:
• The address to specify has the start address greater than the end address.
• Either of the start address or end address exceeds the device range that can be specified.
(2) Address specifying crossing over different devices
The start address and end address can be specified crossing over different devices.
2 - 72
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
1
PREPARATORY
PROCEDURES FOR
MONITORING
(5) Read clock data (6) command (w/out station No.), read clock data (G) command (w/station No.)
The following shows an example of reading the clock data of GOT at station No.27.
(Assuming that the clock data of GOT has been set to "2004, June 1, 18:46:49, Tuesday".)
Time display
Item
TUE
2
MICROCOMPUTER
CONNECTION
(SERIAL)
2004/06/01 18:46:49
Message format
(format 14: GOT-F900 Series microcomputer connection (format 1))
ComSTX mand Station No. CR
Request message
2
7
32H
37H
(H)
(L)
3
0DH
(format 15: GOT-F900 Series microcomputer connection (format 2))
GOT)
Sum
Check
STX Command Station No. ETX
02H
G
2
7
47H
32H
37H
(H)
(L)
B
3
42H
33H
(H)
(L)
03H
4
MODBUS(R)/RTU
CONNECTION
(host
G
47H
MICROCOMPUTER
CONNECTION
(ETHERNET)
02H
Sum check is performed in this range.
(format 14: GOT-F900 Series microcomputer connection (format 1))
0
4
0
6
0
1
1
8
4
6
4
9
0
2
02H
30H
34H
30H
36H
30H
31H
31H
38H
34H
36H
34H
39H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
CR
5
0DH
MODBUS(R)/TCP
CONNECTION
(GOT
Year data Month data
(format 15: GOT-F900 Series microcomputer connection (format 2))
host)
Day-ofHour data Minute data Second data week data
STX
Year data Month data
0
4
0
6
0
1
1
8
4
6
4
9
0
2
02H
30H
34H
30H
36H
30H
31H
31H
38H
34H
36H
34H
39H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Day data
ETX
03H
Sum
Check
D
0
44H
30H
(H)
(L)
6
CONNECTION TO
SOUND OUTPUT
UNIT
Response message
during normal
communication
Day data
Day-ofHour data Minute data Second data week data
STX
Sum check is performed in this range.
NAK
(GOT
15H
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
host)
CONNECTION TO
EXTERNAL I/O
DEVICE
Response message
during faulty
communication
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 73
(6) Set clock data (5) command (w/out station No.), set clock data (F) command (w/station No.)
The following shows an example of setting clock data of GOT at station No.27.
(Assuming the clock data of GOT is to be set to "2004, June 1, 18:46:49 Tuesday".)
Time display
2004/06/01 18:46:49
TUE
After execution
Item
Message format
(format 14: GOT-F900 Series microcomputer connection (format 1))
STX Com- Station No.
mand
02H
Year data
Month data
Day Data
Hour data Minute data
Second
data
Day-ofweek data
F
2
7
0
4
0
6
0
1
1
8
4
6
4
9
0
2
46H
32H
37H
30H
34H
30H
36H
30H
31H
31H
38H
34H
36H
34H
39H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
CR
0DH
(format 15: GOT-F900 Series microcomputer connection (format 2))
Station No.
STX Command
Request message
(host
GOT)
02H
F
2
7
46H
32H
37H
(H)
(L)
ETX
Following*1
03H
Sum
Check
7
F
37H
46H
(H)
(L)
Sum check is performed in this range.
*1
Year data Month data
Day data
Second
data
Hour data Minute data
Day-ofweek data
0
4
0
6
0
1
1
8
4
6
4
9
0
2
30H
34H
30H
36H
30H
31H
31H
38H
34H
36H
34H
39H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Response message
during normal
communication
ACK
(GOT
06H
host)
Response message
during faulty
communication
NAK
(GOT
15H
host)
POINT
When a wrong day of the week has been set by the clock data setting command
If a wrong day of the week is set by the clock data setting commands, the clock data will differ from the time
displayed on the utility.
Example: When June 1, 2004 (Thursday) is set by the clock data setting command(the actual day of week is
Tuesday),
Tuesday (TUE) will be displayed on the utility time display.
2 - 74
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
The following shows an example of an interrupt output when data are written to the interrupt output devices (D13
and D14).
(Assuming that "3139H" is written to D13 and "AA55H" to D14.)
Example: When the number of interrupt data bytes is 2
2
3139H
MICROCOMPUTER
CONNECTION
(SERIAL)
D13
Interrupt
Interrupt output
Output Output
value 1 value 2
Item
3
39H
MICROCOMPUTER
CONNECTION
(ETHERNET)
31H
Message format
(1) When [Interrupt Data Byte] in "Communication Detail Settings" is set to "1 byte"
4
MODBUS(R)/RTU
CONNECTION
Output
value 1
39H
(2) When [Interrupt Data Byte] in "Communication Detail Settings" is set to "2 byte"
Output Output
value 1 value 2
Interrupt output
5
host)
39H
MODBUS(R)/TCP
CONNECTION
31H
(3) When [Interrupt Data Byte] in "Communication Detail Settings" is set to "4 byte"
Output Output Output Output
value 1 value 2 value 3 value 4
55H
31H
6
39H
CONNECTION TO
SOUND OUTPUT
UNIT
AAH
POINT
Interrupt output
7
CONNECTION TO
EXTERNAL I/O
DEVICE
• To disable the interrupt output, turn ON SM52 (interrupt code output disable flag). (
2.4.6 SM devices)
• To enable the interrupt output, set 8 bits to the data length at "Communication Detail Settings".
(
2.6.1 Setting communication interface (Communication settings))
• When "7 bits" is set, the MSB (8th bit) is ignored.(Example: FFH 7FH)
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(GOT
PREPARATORY
PROCEDURES FOR
MONITORING
1
(7) In the case of interrupt outputs
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
2 - 75
 Error code list
When faulty, the error code is stored in SD2.
For details of error code stored in SD2, the error contents, cause and measures, refer to the following:
2.4.5 ■ Details and actions for errors (error codes) stored into SD2
When an error other than those to be stored in SD2 occurs, at faulty, only the NAK response is executed.
 Precautions
(1) Batch reading/writing crossing over different devices
When using the batch read (0, A) or batch write (1, B) command, do not batch read/write crossing over different
devices.
This will cause an error response.
2 - 76
2. MICROCOMPUTER CONNECTION (SERIAL)
2.5 Message Formats
 Controller setting
POINT
Set the channel of the equipment to be connected to the
GOT.
Microcomputer connection extension
The setting is required when connecting multiple GOTs
for one microcomputer.
2.
2.
3.
3.
4.
1.
2.
3.
4.
3.
Select [Common]
menu.
[Controller Setting] from the
MODBUS(R)/RTU
CONNECTION
2.
Click!
Select [Common]
[Peripheral Setting]
[GOT(Extended Computer)] from the menu.
Set the interface to which the n+1th GOT is
connected.
Clicking the detail setting button displays the
Communication Detail Settings dialog box for the
communication driver.
The Controller Setting window is displayed. Select the
channel to be used from the list menu.
Set the following items.
• Manufacturer: Others
• Controller Type:Computer
• I/F: Interface to be used
• Driver:Computer
5
6
Item
Connection CH No.
The detailed setting is displayed after Manufacturer,
Controller Type, I/F, and Driver are set.
Make the settings according to the usage
environment.
3
4
Click!
1.
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Set the GOT interface connecting to the n+1th GOT.
No setting is required for a terminal GOT.
MICROCOMPUTER
CONNECTION
(ETHERNET)
 Extension setting for microcomputer
MODBUS(R)/TCP
CONNECTION
Setting communication
interface (Communication
settings)
Description
This CH No. is used for the
connection with a
microcomputer or n-1th GOT.
(Default: 1)
Range
1 fixed
Click the [OK] button when settings are completed.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
2.6.2 Communication detail settings
CONNECTION TO
SOUND OUTPUT
UNIT
2.6.1
PREPARATORY
PROCEDURES FOR
MONITORING
1
2.6 GOT Side Settings
Click the [OK] button when settings are completed.
POINT
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
The settings of connecting equipment can be set and
confirmed in [I/F Communication Setting]. For details,
refer to the following.
1.1.2 I/F communication setting
2. MICROCOMPUTER CONNECTION (SERIAL)
2.6 GOT Side Settings
2 - 77
2.6.2
Communication detail settings
Make the settings according to the usage environment.
POINT
(1) Special Interrupt Code
The following shows the compatibility between the
special interrupt codes and the event types.
Item
Transmission Speed
Description
Set this item when change the
transmission speed used for
communication with the
connected equipment.
(Default: 19200bps)
Data Bit
7bits/8bits
Stop Bit
Specify the stop bit length for
communications.
(Default: 1bit)
1bit/2bits
Parity
Specify whether or not to
perform a parity check, and
how it is performed during
communication.
(Default: Even)
None
Even
Odd
Host Address
Specify the host address
(station No. of the PLC to
which the GOT is connected)
in the network of the GOT.
(Default: 0)
0 to 31
Select the communication
format.
(Default: 1)
1 to 15
Select the communication
format.
(Default: 14)
1, 2, 14, 15
Interrupt Data Byte
Specify the number of bytes of
interrupt data.
(Default: 1byte)
1byte, 2byte,
4byte
Special Interrupt
Code
Set whether or not to output
the special interrupt code.
(Default: No)
Yes or No
Control Method
Set this item when selecting
the XON/XOFF control for the
control method.
(Default: No)
XON/XOFF,
No
32bit Storage
Select the steps to store two
words (32-bit data).
(Default: LH Order)
LH Order/
HL Order
2 - 78
Event type
20H
Base Screen*1 and Overlap Window*1
Output when the screens are switched according to the
change in the switching device values assigned to 1/2.
*1: Base Screen or Overlap Window 1/2 switches
independently without being interlocked.
(Example of output)
When all the switching device values assigned to
the Base Screen and Overlap Window1/2 are
changed, 3 special interrupt codes are output.
21H
Output when Numerical/ASCII Input is completed.
22H
Output when Recipe data transfer (read-out, write-in) is
completed.
23H
Output when Bar code, RFID data has been imported
into GOT
Range
4800bps,
9600bps,
19200bps,
38400bps,
57600bps,
115200bps
Set this item when change the
data length used for
communication with the
connected equipment.
(Default: 7bits)
Format
Special
Interrupt Code
(Hex)
(2) Communication detail setting when connecting
multiple GOTs
For the following items, set the same settings to
the n+1th GOT interface as the CH No.1 of n-th
GOT.
• Transmission Speed
• Data Bit
• Stop Bit
• Parity
Set each [Host Address] for the GOT.
(3) Communication interface setting by the Utility
The communication interface setting can be
changed on the Utility's [Communication setting]
after writing [Communication Settings] of project
data.
For details on the Utility, refer to the following
manual.
User's Manual of GOT used.
2. MICROCOMPUTER CONNECTION (SERIAL)
2.6 GOT Side Settings
(4) Precedence in communication settings
When settings are made by GT Designer3 or the
Utility, the latest setting is effective.
The following shows the monitor screen settings in this
system configuration example.
(a) Common settings
Set D20 to the screen switching device (base
screen).
 System configuration
The system configuration example illustrated below is
explained in this section.
1.
IBM-PC/AT-compatible PC
(Microsoft® Visual C++® Ver.6.0)
Select [Common]
[GOT Environmental Setting]
[Screen Switching/Window] to display [Environment
Setup] on GT Designer3.
 Communication settings on GOT side and
monitor screen settings
Set D20 to the screen switching device (base screen).
Even
Interrupt Data Byte
1 byte
Host address (0 to 31)
0
Format
1
Special Interrupt Code
None
Control Method
None
32bit Storage
MODBUS(R)/TCP
CONNECTION
1bit
Parity
6
CONNECTION TO
SOUND OUTPUT
UNIT
Stop bit
8bits
LH Order
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Data bit
5
38400bps
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Baud rate
Setting details
MODBUS(R)/RTU
CONNECTION
2.
2.6.2 Communication detail settings
Setting item
3
4
(1) Transmission settings
Set the transmission settings of the GOT.
The transmission settings in the microcomputer
connection (serial) are made at [Detail Setting] on GT
Designer3.
2
MICROCOMPUTER
CONNECTION
(SERIAL)
(2) Monitor screen settings
MICROCOMPUTER
CONNECTION
(ETHERNET)
The following shows a system configuration example in the
case of the microcomputer connection (serial).
PREPARATORY
PROCEDURES FOR
MONITORING
1
2.7 System Configuration Examples
2. MICROCOMPUTER CONNECTION (SERIAL)
2.7 System Configuration Examples
2 - 79
(b) Monitor screen image
Create the following screens by GT Designer3.
Numerical display
Basic Settings
No.
Base screen 1
Device/Style
Device
D21
Sample Screen 1
Data Type
Format
Number Size
Digits
Arbitrary
4
Unsigned BIN16 Signed Decimal
Touch switch
123
Basic Settings
Action
No.
Screen 2
Action
Next Screen
Screen Switching
Fixed
Base
Screen No.2
1.
2.
Numerical display
By setting this with the numerical display, the device
value of D21 can be monitored.
The device value is incremented only while [Sample
Screen 1] is displayed.
Switch 1
This is the screen switching switch to [Sample
Screen 2].
Touching this changes the base screen to [Sample
Screen 2].
―
―
―
―
Signed Constant
BIN16
1
BIt
―
D22.b0
―
―
Alternate
―
―
―
―
―
Signed Constant
BIN16
255
D13
―
―
Bit lamp
Screen 1
Bit lamp
The device status of D22.b0 is displayed as a lamp.
Switch 2
This is an alternate switch for changing the state of
D22.b0.
Switch 3
This is the screen switching switch to [Sample
Screen 1]. Touching this changes the base screen
to [Sample Screen 1].
2 - 80
Action
Type
D13
Word
Sample Screen 2
5.
Setting
Value
―
Basic Settings
No.
4.
Data
Type
Word
Screen Switching
Fixed
Base
Screen No.1
Base screen 2
3.
Device
2. MICROCOMPUTER CONNECTION (SERIAL)
2.7 System Configuration Examples
Device/Style
Lamp Type
Device
Shape
Shape Attribute
BIt
D22.b0
Arbitrary
Arbitrary
Display/
Processing on
GOT side
――
――
Opens the port.
Writes "1" to the screen
switching device (D20).
Receives a response from
the GOT.
Judges whether or not
there is an error in the
response from the GOT.
Writes an initial value to
device (D21).
End
processing
(only when
receiving an
error
response)
When
receiving a
response to
reading of
device (D21)
from the
GOT
Issues the
current
value
acquisition
request to
device
(D21).
Batch
numerical
value
display write
packet*2
Batch
numerical
value
display read
packet*3
――
Calculates
the sum
check of the
send packet.
0
1
0
0
0
1
30H
30H
31H
30H
30H
30H
31H
(H)
(L)
(H)
–
–
(L)
(H)
(L)
(H)
–
–
(L)
――
Batch
numerical
value
display write
packet*2
03H
8
2
38H
32H
(H)
(L)
Sum check is performed in this range.
*2
2
Displays the send packet structure of the numerical value display
batch write packet.
STX Command
02 H
Displays base
screen 1.
Number of
points
Address
W
D
0
0
2
1
0
1
57H
44H
30H
30H
32H
31H
30H
31H
(H)
(L)
(H)
–
–
(L)
(H)
(L)
ETX Sum check
Data 1 (D21)
(Changes
according to
(any value)
03H data section.)
(H)
–
–
(L)
(H)
(L)
Sum check is performed in this range.
*3
Displays the send packet structure of the numerical value display
batch read packet.
――
Number of
points
Address
Command
――
02H
Displays "0" on
the numerical
value display
on base screen
1.
R
D
0
0
2
1
0
1
52H
44H
30H
30H
32H
31H
30H
31H
(H)
(L)
(H)
–
–
(L)
(H)
(L)
Sum
Check
ETX
B
D
42H
44H
(H)
(L)
03H
Sum check is performed in this range.
*4
Displays the receive packet structure of the batch write response
packet.
When normally operated
Increments the
numerical value
displayed on
base screen 1.
(The host side
repeats the
processing on
the left as long
as base screen
1 is displayed.))
When an error occurred
ACK
NAK
06H
15H
*5
Displays the receive packet structure of the batch read response
packet.
When normally operated
Data
STX
(Changes
according to
(any data)
02H
(H)
–
–
03H data section.)
(L)
(H)
NAK
15H
(L)
Sum check is performed in this range.
*6
Sets the
state of the
base screen
to base
screen 2.
When
receiving an
interrupt
requesting
the base
screen
switching
from 2 to 1
Sets the
state of the
base screen
to base
screen 1.
Interrupt
receive
*6
Interrupt
receive
packet*6
*6
――
Touch touch
switch 1 to
switch to base
screen 2.Notify
the host by an
interrupt.
3
4
5
When an error occurred
ETX Sum check
PREPARATORY
PROCEDURES FOR
MONITORING
0
32H
Displays the receive packet structure of the interrupt receive packet.
Output value
When
receiving an
interrupt
requesting
the base
screen
switching
from 1 to 2
Close the port.
2
30H
STX
――
Creates the
next device
value (D21).
Issues the
update
request of
device
(D21).
0
30H
6
Interrupt data
(value of D13)
CONNECTION TO
SOUND OUTPUT
UNIT
When
receiving a
response to
writing to
device (D21)
from the
GOT
Reception of
response/
interrupt from
GOT
――
0
44H
Sum
Check
Touch touch
switch 3 to
switch to base
screen 1.Notify
the host by an
interrupt.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Initial
processing
Screen 1
batch
switching
Write
packet*1
D
57H
ETX
Data 1 (D20)
MICROCOMPUTER
CONNECTION
(SERIAL)
Packet
used for
data transfer
W
02H
Address
MICROCOMPUTER
CONNECTION
(ETHERNET)
Processing on host side
Command
――
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Processing
Number of
points
STX
MODBUS(R)/RTU
CONNECTION
The following describes the processing on the host
side, display/processing on the GOT side, and data
transfer packets.
(Assuming that host side programs use programs
which perform the processing on host side shown
below.)
1
Displays the send packet structure of the screen 1 batch switching
write packet.
MODBUS(R)/TCP
CONNECTION
*1
 Outline of system operation
2. MICROCOMPUTER CONNECTION (SERIAL)
2.7 System Configuration Examples
2 - 81
2.8 Device Range that Can Be Set
The device ranges of controller that can be used for GOT are as follows.
Note that the device ranges in the following tables are the maximum values that can be set in GT Designer3.
The device specifications of controllers may differ depending on the models, even though belonging to the same series.
Please make the setting according to the specifications of the controller actually used.
When a non-existent device or a device number outside the range is set, other objects with correct device settings may
not be monitored.
 Setting item
Item
Description
Device
Set the device name, device number, and bit number.
The bit number can be set only when specifying the bit of word device.
Information
Displays the device type and setting range which are selected in [Device].
(1) For GT16, GT15, GT14, GT12, GT11
Bit device
Device name
Device No. representation
M0
to
M2047
Special relay (SM)
SM0
to
SM63
Latch relay (L)
L0
to
L2047
Word device bit
Word device
Setting range
Internal relay (M)
Decimal
Specified bit of the following word devices
Data register (D)
D0
to
D4095
Link special register (SD)
SD0
to
SD15
File register (R)
R0
to
R4095
Bit device word
Decimal
Converting bit devices into word
(2) For GT10
Bit device
Device name
Word device
Device No. representation
M0
to
M2047
Special relay (SM)
SM0
to
SM63
Latch relay (L)
L0
to
L2047
Word device bit
2 - 82
Setting range
Internal relay (M)
Decimal
Specified bit of the following word devices
Data register (D)
D0
to
D511
Link special register (SD)
SD0
to
SD15
File register (R)
R0
to
R4095
2. MICROCOMPUTER CONNECTION (SERIAL)
2.8 Device Range that Can Be Set
Decimal
1
PREPARATORY
PROCEDURES FOR
MONITORING
2.9 Precautions
 GOT clock control
The settings of "time adjusting" or "time broadcast"
made on the GOT will be disabled on the PLC. Use the
dedicated commands to set or read out the clock data
of microcomputer.
MICROCOMPUTER
CONNECTION
(SERIAL)
2
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
MODBUS(R)/RTU
CONNECTION
4
MODBUS(R)/TCP
CONNECTION
5
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
2. MICROCOMPUTER CONNECTION (SERIAL)
2.9 Precautions
2 - 83
2 - 84
2. MICROCOMPUTER CONNECTION (SERIAL)
2.9 Precautions
3
PREPARATORY
PROCEDURES FOR
MONITORING
1
MICROCOMPUTER
CONNECTION
(SERIAL)
2
MICROCOMPUTER
CONNECTION (ETHERNET)
3.
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
4
MODBUS(R)/RTU
CONNECTION
3.1 Microcomputer connection (Ethernet) . . . . . . . . . . . . . . . . . 3 - 2
3.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 2
3.3 Device Data Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 3
3.4 Message Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 16
5
MODBUS(R)/TCP
CONNECTION
3.5 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 69
3.6 System Configuration Examples . . . . . . . . . . . . . . . . . . . . 3 - 72
3.7 Device Range that Can Be Set . . . . . . . . . . . . . . . . . . . . . 3 - 73
3.8 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 74
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
3-1
3.
MICROCOMPUTER CONNECTION
(ETHERNET)
3.1 Microcomputer connection (Ethernet)
The "microcomputer connection (Ethernet)" is a function by which data can be written or read from a PC, microcomputer
board, PLC, etc. (hereinafter referred to as "host") to virtual devices of the GOT after connecting the host to the GOT with
the Ethernet.
Interrupt output is also available from the GOT to the host.
For the flow of the data processing, such as reading or writing data and interrupt output, refer to the following.
2.1 Microcomputer Connection (Serial)
3.2 System Configuration
3.2.1
For the microcomputer connection (Ethernet)
Communication driver
Ethernet (microcomputer)
Host
GOT
Connection cable
Host
Connection cable
Communication
Type
Ethernet
Cable model
Option device
Model*3
length*2
Twisted pair cable*1
• 10BASE-T
Shielded twisted pair cable (STP) or
unshielded twisted pair cable (UTP):
Category 3, 4, and 5
• 100BASE-TX
Shielded twisted pair cable (STP):
Category 5 and 5e
*1
*2
*3
*4
3-2
GOT
Maximum
segment
- (Built into GOT)
Number of
connectable
equipment
*4
100m
GT15-J71E71-100
Unlimited number
of GOTs for 1 host
The destination connected with the twisted pair cable varies with the configuration of the applicable Ethernet network system.
Connect to the Ethernet module, hub, transceiver or other system equipment corresponding to the applicable Ethernet network
system.
Use cables, connectors, and hubs that meet the IEEE802.3 10BASE-T/100BASE-TX standard.
A length between a hub and a node.
The maximum distance differs depending on the Ethernet device to be used.
The following shows the number of the connectable nodes when a repeater hub is used.
• 10BASE-T: Max. 4 nodes for a cascade connection (500m)
• 100BASE-TX: Max. 2 nodes for a cascade connection (205m)
When switching hubs are used, the cascade connection between the switching hubs has no logical limit for the number of
cascades.
For the limit, contact the switching hub manufacturer.
When connecting GT16 of the function version A to an equipment that meets the 10BASE (-T/2/5) standard, use the switching
hub and operate in a 10Mbps/100Mbps mixed environment.
For how to check the function version, refer to the following.
GT16 User’s Manual (Hardware)
GT14 models compatible with Ethernet connection are only GT1455-QTBDE and GT1450-QLBDE.
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.1 Microcomputer connection (Ethernet)
D
Address specification value
Refer to
Device type
Format
1, 2
Format
3, 4
Format
5
Format
6 to 9
0 to 4095
Word
0 to 4095
8000 to 9FFFH
0000 to 0FFFH
D0 to 4095
3.3.1
R
0 to 4095
Word
4096 to 8191
0000 to 1FFFH
1000 to 1FFFH
R0 to 4095
3.3.2
L
0 to 2047
Bit
8192 to 8319
A000 to A0FFH
2000 to 207FH
L0 to 2047
3.3.3
8320 to 8447
20FFH
2080 to 20FFH
M0 to 2047
3.3.4
2100 to 210FH
SD0 to 15
3.3.5
2110 to 2113H
SM0 to 63
3.3.6
0 to 2047
Bit
SD
0 to 15
Word
8448 to 8463
SM
0 to 63
Bit
8464 to 8467
*1
2000 to
2100 to 211FH
*3
(3000 to 300DH)
2200 to 2207H
For the address specification method for each data format, refer to the following.
3.4 Message Formats
•
•
•
•
•
*2
Formats 1, 2
Formats 3, 4
Formats 5
Formats 6, 7
Formats 8, 9
:
:
:
:
:
GOT-A900 Series microcomputer connection
GOT-F900 series microcomputer connection
Digital Electronics Corporation's memory link method
4E frame
QnA compatible 3E frame
3
4
When reusing GOT900 Series project data
• GOT-A900 Series virtual devices (D0 to 2047)
Can be used as they are without changing the assignments.
• GOT-F900 Series virtual devices
Since some of the assigned virtual device values differ as indicated below, change the assignment using device batch edit of
GT Designer3.
Refer to the following manual for device batch edit of GT Designer3.
5
GOT-F900 Series virtual devices
D0 to 2047
―
D2048 to 4095
―
R0 to 4095
D0 to 4095
L0 to 2047
―
M0 to 2047
M0 to 2047
SD0 to 15
D8000 to 8015
GD0 to 6
SM0 to 63
M8000 to 8063
6
Access to SD3 to 9 can also be made by the specification of the addresses (3000 to 300DH) of GD0 to 6 on the GOT-F900 Series.
POINT
CONNECTION TO
SOUND OUTPUT
UNIT
*3
GOT1000 Series virtual devices
MODBUS(R)/TCP
CONNECTION
GT Designer3 Version1 Screen Design Manual
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Values of virtual devices inside the GOT
When the GOT is turned OFF or reset, values are cleared to their defaults
(bit devices: OFF, word devices: 0).
Values are held in the memory when project data are written to the GOT.
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
M
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Name
Device
range
(decimal)
MODBUS(R)/RTU
CONNECTION
Virtual device*2
MICROCOMPUTER
CONNECTION
(ETHERNET)
The following shows a list of virtual devices inside the GOT available in the microcomputer connection (Ethernet), and
the address specification values for each data format.
The address specification of the virtual devices differs depending on the data format.*1
PREPARATORY
PROCEDURES FOR
MONITORING
1
3.3 Device Data Area
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.3 Device Data Area
3-3
3.3.1
D devices
The D devices are word devices into which GOT communication errors, clock data or other information are stored.
The user can also store data using the user area.
 List of D devices
The following lists the D devices (virtual devices inside the GOT).
Address
Description
Set side
D0 to 2
Unused
―
Communication error status
Stores the communication error details of GOT.
0: Normal
1: Error
b15
–
b8 b7 b6 b5 b4 b3
–
b0
Unused
D3
SIO framing error
SIO parity error
SIO overrun error
Communication timeout
error
Unused
• b4 to 6 turn ON when an SIO error occurs, and turn OFF when an request message from the host is received
successfully after the error occurrence.
• b7 turns ON about 3 seconds after the host side DTR becomes OFF, and turns OFF when transmission is
performed successfully to the host after the error occurrence.
Clock data (year)
b15
–
b8 b7
–
b0
System
D4
Lower 2 digits of calendar
year stored as 2-digit BCD
Unused
Clock data (month)
b15
–
b8 b7
–
b0
D5
Data of months 01 to
12 stored as 2-digit BCD
Unused
Clock data (day)
b15
–
b8 b7
–
b0
D6
Data of days 01 to
31 stored as 2-digit BCD
Unused
(Continued to next page)
3-4
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.3 Device Data Area
Address
Description
Set side
Clock data (hour)
b15
–
–
b8 b7
b0
D7
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Data of hours 00 to
23 stored as 2-digit BCD
Unused
Clock data (minute)
b15
–
–
b8 b7
1
PREPARATORY
PROCEDURES FOR
MONITORING
(From previous page)
b0
Data of minutes 00 to
59 stored as 2-digit BCD
Unused
Clock data (second)
System
b15
–
–
b8 b7
b0
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
D8
4
MODBUS(R)/RTU
CONNECTION
D9
Data of seconds 00 to
59 stored as 2-digit BCD
Unused
Clock data (day of week)*1
b8 b7
–
5
b0
MODBUS(R)/TCP
CONNECTION
–
Day-of-week data stored as
2-digit BCD
D10
00: Sunday 01: Monday
02: Tuesday 03: Wednesday
04: Thursday 05: Friday
06: Saturday
6
Unused
D11, D12
Unused
―
(Continued to next page)
7
CONNECTION TO
EXTERNAL I/O
DEVICE
If a wrong day of the week is set by the clock data setting commands, the clock data will differ from the time displayed on the
utility.
Example: When October 1, 2009 (Tuesday) is set by the clock data setting command (the actual day of the week is Thursday),
"02" is stored to D10 although Thursday (THU) will be displayed on the utility time display.
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
*1
CONNECTION TO
SOUND OUTPUT
UNIT
b15
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.3 Device Data Area
3-5
(From previous page)
Address
Description
Set side
Interrupt output
When data are written to D13 and D14 from a GOT touch switch, for example, the data of D13 and D14 are
transmitted (interrupt output) to the host side.*1*2
The data amount (number of bytes) to be interrupt-output is set at "Interrupt Data Byte" in "Communication Detail
Settings".
(
3.5.1 Setting communication interface (Communication settings))
D13
• Output value when 1 is set to "Interrupt Data Byte" in "Communication Detail Settings"
D13
Lower 8 bits
1 byte
• Output value when 2 is set to "Interrupt Data Byte" in "Communication Detail Settings"
D13
User
Upper 8 bits
Lower 8 bits
2 bytes
• Output value when 4 is set to "Interrupt Data Byte" in "Communication Detail Settings
(1) When setting the LH order to [32bit Storage] for the communication detail settings
D14
D13
D14
Upper 8 bits
Lower 8 bits
Upper 8 bits
Lower 8 bits
4 bytes
(2) When setting the HL order to [32bit Storage] for the communication detail settings
D13
Upper 8 bits
D14
Lower 8 bits
Upper 8 bits
Lower 8 bits
4 bytes
D15 to 19
Unused
―
D20 to 2031
User area
User
D2032 to 2034
Unused
―
1-second binary counter
The counter is incremented at 1-second intervals after the GOT is turned ON.
(The time elapsed after GOT is turned ON is stored in 1-second units.)
Data are stored in binary format.
D2035
D2036 to 4095
User area
*1
*2
System
User
After writing data, the interrupt data is output within a period of 1 to 10ms.
When data are written to D13 and D14 from the host side, interrupt output is not performed.
POINT
(1) The side where virtual devices are set
System : Set on the system side.
User
: Set on the user side (by sending request messages from host or using the touch switches, etc.
on the GOT).
(2) Interrupt output (D13, D14)
• To disable the interrupt output, turn ON SM52 (interrupt code output disable flag). (
3.3.6 SM devices)
• To enable the interrupt output, set 8 bits to the data length at "Communication Detail Settings".
(
3.5.1 Setting communication interface (Communication settings))
• When "7 bits" is set, the MSB (8th bit) is ignored. (Example: FFH 7FH)
3-6
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.3 Device Data Area
The address specification of devices varies depending on the data format.*1
The following shows the address specification values for each data format.
Address specification value
8000H
8000H
8001H
8001H
Upper 8 bits
Lower 8 bits
0
8002H
8002H
:
:
D4095
4095
Upper 8 bits
9FFEH
9FFFH
Upper 8 bits
0001H
D1
:
:
0FFFH
D4095
3
9FFFH
Lower 8 bits
For the address specification method for each data format, refer to the following.
3.4 Message Formats
:
:
:
:
:
4
GOT-A900 Series microcomputer connection
GOT-F900 series microcomputer connection
Digital Electronics Corporation's memory link method
4E frame
QnA compatible 3E frame
5
MODBUS(R)/TCP
CONNECTION
Formats 1, 2
Formats 3, 4
Formats 5
Formats 6, 7
Formats 8, 9
6
CONNECTION TO
SOUND OUTPUT
UNIT
•
•
•
•
•
2
7
CONNECTION TO
EXTERNAL I/O
DEVICE
*1
D0
Lower 8 bits
:
9FFEH
0000H
8003H
1
8003H
Format
6 to 9
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
D1
Format
5
MICROCOMPUTER
CONNECTION
(SERIAL)
D0
Format
3, 4
MICROCOMPUTER
CONNECTION
(ETHERNET)
Format
1, 2
MODBUS(R)/RTU
CONNECTION
Address
PREPARATORY
PROCEDURES FOR
MONITORING
1
 Differences in address specifications by data format
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.3 Device Data Area
3-7
3.3.2
R devices
The R devices are word devices into which user data are stored.
All of these devices can be used as a user area.
 List of R devices and differences in address specification by data format
The following shows the R devices (virtual devices inside the GOT).
The address specification values different depending on the data format are also given below.*1
Address specification value
Address
Format
1, 2
D0
4096
D1
Format
3, 4
0000H
0000H
0001H
0001H
Upper 8 bits
Lower 8 bits
0002H
0002H
0003H
0003H
Upper 8 bits
Lower 8 bits
4097
:
:
D4095
8191
*1
:
1FFEH
1FFEH
1FFFH
1FFFH
Upper 8 bits
Lower 8 bits
For the address specification method for each data format, refer to the following.
3.4 Message Formats
•
•
•
•
•
3-8
Formats 1, 2
Formats 3, 4
Formats 5
Formats 6, 7
Formats 8, 9
:
:
:
:
:
GOT-A900 Series microcomputer connection
GOT-F900 series microcomputer connection
Digital Electronics Corporation's memory link method
4E frame
QnA compatible 3E frame
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.3 Device Data Area
Format
5
Format
6 to 9
1000H
R0
1001H
R1
:
:
1FFFH
R4095
1
PREPARATORY
PROCEDURES FOR
MONITORING
L devices
The L devices are bit devices into which user data are stored.
All of these devices can be used as a user area.
 List of L devices and differences in address specification by data format
The following shows the L devices (virtual devices inside the GOT).
Address
Address specification value
b7
b6
b5
b4
b3
b2
b1
b0
L7
L6
L5
L4
L3
L2
L1
L0
L15
L14
L13
L12
L11
L10
L9
L8
L23
L22
L21
L20
L19
L18
L17
L16
L31
L30
L29
L28
L27
L26
L25
L24
Format
1, 2
8192
8193
:
:
L2039
L2038
L2037
L2036
L2035
L2034
L2033
L2032
L2047
L2046
L2045
L2044
L2043
L2042
L2041
L2040
*1
8319
Format
3, 4
A000H
A001H
A002H
A003H
Format
5
2000H
2001H
Same as
address
column on
:
left*2
:
A0FEH
A0FFH
Format
6 to 9
207FH
For the address specification method for each data format, refer to the following.
GOT-A900 Series microcomputer connection
GOT-F900 series microcomputer connection
Digital Electronics Corporation's memory link method
4E frame
QnA compatible 3E frame
MODBUS(R)/RTU
CONNECTION
:
:
:
:
:
For reading or writing data in word units, specify the addresses in 16-point units. (Example: L0, L16, L32, etc.)
MODBUS(R)/TCP
CONNECTION
5
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
*2
Formats 1, 2
Formats 3, 4
Formats 5
Formats 6, 7
Formats 8, 9
3
4
3.4 Message Formats
•
•
•
•
•
MICROCOMPUTER
CONNECTION
(SERIAL)
2
The address specification values different depending on the data format are also given below.*1
MICROCOMPUTER
CONNECTION
(ETHERNET)
3.3.3
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.3 Device Data Area
3-9
3.3.4
M devices
The M devices are bit devices into which user data are stored.
All of these devices can be used as a user area.
 List of M devices and differences in address specification by data format
The following shows the M devices (virtual devices inside the GOT).
The address specification values different depending on the data format are also given below.*1
Address
Address specification value
b7
b6
b5
b4
b3
b2
b1
b0
M7
M6
M5
M4
M3
M2
M1
M0
M15
M14
M13
M12
M11
M10
M9
M8
M23
M22
M21
M20
M19
M18
M17
M16
M31
M30
M29
M28
M27
M26
M25
M24
Format
1, 2
8320
8321
:
:
M2039
M2038
M2037
M2036
M2035
M2034
M2033
M2032
M2047
M2046
M2045
M2044
M2043
M2042
M2041
M2040
*1
8447
Format
3, 4
2000H
2001H
2002H
2003H
:
20FEH
20FFH
Format
5
Format
6 to 9
2080H
2081H
Same as
address
column on
:
left*2
20FFH
For the address specification method for each data format, refer to the following.
3.4 Message Formats
•
•
•
•
•
*2
3 - 10
Formats 1, 2
Formats 3, 4
Formats 5
Formats 6, 7
Formats 8, 9
:
:
:
:
:
GOT-A900 Series microcomputer connection
GOT-F900 series microcomputer connection
Digital Electronics Corporation's memory link method
4E frame
QnA compatible 3E frame
For reading or writing data in word units, specify the addresses in 16-point units.(Example: M0, M16, M32, and others)
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.3 Device Data Area
The SD devices are word devices into which GOT communication errors (error codes), clock data and other information
are stored.
 List of SD devices
The following lists the SD devices (virtual devices inside the GOT).
Set side
100ms counter (32bits)
The counter is incremented at 100ms intervals after GOT is turned ON.
(The time elapsed after GOT is turned ON is stored in 100ms units.)
(1) When setting the LH order to [32bit Storage] for the communication detail settings
The lower and upper bits are stored in SD0 and SD1 respectively.
SD1
SD0
Upper word
Lower word
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
SD0
SD1
(2) When setting the HL order to [32bit Storage] for the communication detail settings
The upper and lower bits are stored in SD0 and SD1 respectively.
SD1
Upper word
Lower word
4
Communication error status
An error data (error code) occurred during communication is stored.
•Host Address (Communication error that occurred on the request destination GOT)
0: No error
1: Parity error
2: Framing error
3: Overrun error
4: Communication message error
5: Command error
6: Clock data setting error
SD2*1
System
•Other station (Communication error that occurred on another GOT when multiple GOTs are connected)
101: Parity error
102: Framing error
103: Overrun error
104: Communication message error
105: Timeout error (No station of the specified address exists.)
106: Multiple units not connectable
107: Clock data setting error
Clock data (second)
Second data of 00 to 59 is stored.
SD4
Clock data (minute)
Minute data of 00 to 59 is stored.
SD5
Clock data (hour)
Hour data of 00 to 23 is stored.
SD6
Clock data (day)
Day data of 00 to 31 is stored.
SD7
Clock data (month)
Month data of 01 to 12 is stored.
6
CONNECTION TO
SOUND OUTPUT
UNIT
SD3
7
(Continued to next page)
For details and corrective actions for the errors (error codes) that are stored into SD2, refer to the following:
8
■ Details and actions for errors (error codes) stored into SD2
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
*1
5
MODBUS(R)/TCP
CONNECTION
SD0
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Description
MODBUS(R)/RTU
CONNECTION
Address
PREPARATORY
PROCEDURES FOR
MONITORING
1
SD devices
CONNECTION TO
EXTERNAL I/O
DEVICE
3.3.5
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.3 Device Data Area
3 - 11
(From previous page)
Address
Description
SD8
Clock data (year)
4-digit year data is stored.
SD9
Clock data (day of week)*1
Day-of-the-week data is stored.
0: Sunday
1: Monday
4: Thursday
5: Friday
Set side
System
2: Tuesday
6: Saturday
SD10 to 15
3: Wednesday
Unused
*1
―
If a wrong day of the week is set by the clock data setting commands, the clock data will differ from the time displayed on the
utility.
Example: When October 1, 2009 (Tuesday) is set by the clock data setting command (the actual day of the week is Thursday),
"2" is stored to SD9 although Thursday (THU) will be displayed on the utility time display.
POINT
The side where virtual devices are set
System
User
: Set on the system side.
: Set on the user side (by sending request messages from host or using the touch switches, etc.
on the GOT).
 Details and actions for errors (error codes) stored into SD2
Error code
0
Action
―
1, 101
Parity error
The parity bit does not match.
2, 102
Framing error
The data bit and/or stop bit are not correct.
3, 103
Overrun error
The next data was transmitted from the host before GOT
completes the processing of the data received.
• Check the settings of "Communication Detail Settings".
• Decrease the transmission speed.
4, 104
Communication message error
EXT/CR could not be found before the upper limit of the
receive buffer was exceeded.
• Check the communication cable and communication module
attachment.
• Check the settings of "Communication Detail Settings".
• Review the contents of the message to transmit.
5
Command error
An unsupported command was used.
• Check the communication cable and communication module
attachment.
• Check the settings of "Communication Detail Settings".
• Match the GOT and host transmission settings.
• Review the contents of the message to transmit.
• Check the commands in the message.
(
3.4.2 List of commands)
105
Timeout error
There is no response from the GOT, or the station of the
specified address does not exist.
• Check the communication cable and communication module
attachment.
• Check the settings of "Communication Detail Settings".
• Review the contents of the message to transmit.
106
Multiple units not connectable
The RS-232 port is occupied.
• Check the communication cable and communication module
attachment.
• Check the settings of "Communication Detail Settings".
• Check to see if the RS-232 port is occupied.
Clock data setting error
The setting value of the clock data has error.
• Review the contents of the message to transmit.
• Check whether the non-existent data is set (e.g. setting "07"
at the day of the week) as clock data.
6, 107
3 - 12
Description
No error
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.3 Device Data Area
Address specification value
Upper 8 bits
Lower 8 bits
SD1
2102H
2102H
2103H
2103H
Upper 8 bits
Lower 8 bits
2104H
2104H
2105H
8449
SD2
8450
SD3
8451
SD4
8452
SD5
8453
SD6
8454
SD7
8455
SD8
8456
SD9
8457
*1
2105H
Upper 8 bits
Lower 8 bits
2106H
(3000H)
2106H(3000H)
2107H(3001H)
Upper 8 bits
Lower 8 bits
2108H(3002H)
2109H(3003H)
Upper 8 bits
Lower 8 bits
210AH(3004H)
210BH(3005H)
Upper 8 bits
Lower 8 bits
210CH(3006H)
210DH(3007H)
Upper 8 bits
Lower 8 bits
210EH(3008H)
210FH(3009H)
Upper 8 bits
Lower 8 bits
2110H(300AH)
2111H(300BH)
Upper 8 bits
Lower 8 bits
2112H(300CH)
2113H(300DH)
Upper 8 bits
Lower 8 bits
2107H
(3001H)
2108H
(3002H)
2109H
(3003H)
210AH
(3004H)
210BH
(3005H)
210CH
(3006H)
210DH
(3007H)
210EH
(3008H)
210FH
(3009H)
2110H
(300AH)
2111H
(300BH)
2112H
(300CH)
2113H
(300DH)
2100H
SD0
2101H
SD1
2102H
SD2
2103H
SD3
3
4
2104H
SD4
2105H
SD5
5
2106H
SD6
2107H
SD7
2108H
SD8
2109H
SD9
For the address specification method for each data format, refer to the following.
3.4 Message Formats
•
•
•
•
•
*2
Formats 1, 2
Formats 3, 4
Formats 5
Formats 6, 7
Formats 8, 9
:
:
:
:
:
MICROCOMPUTER
CONNECTION
(ETHERNET)
2101H
8448
2
MODBUS(R)/RTU
CONNECTION
2101H
GOT-A900 Series microcomputer connection
GOT-F900 series microcomputer connection
Digital Electronics Corporation's memory link method
4E frame
QnA compatible 3E frame
6
7
8
SD3 to 9 correspond to GD0 to 6 on the GOT-F900 Series.
Access to SD3 to 9 can be also made by the specification of the addresses (3000 to 300DH) of GD0 to 6 on the GOT-F900
Series.
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.3 Device Data Area
MODBUS(R)/TCP
CONNECTION
2100H
Formats 6 to 9
CONNECTION TO
SOUND OUTPUT
UNIT
SD0
2100H
Formats 5
CONNECTION TO
EXTERNAL I/O
DEVICE
Formats 3, 4*2
Formats 1, 2
3 - 13
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Address
MICROCOMPUTER
CONNECTION
(SERIAL)
The address specification of devices varies depending on the data format.*1
The following shows the address specification values for each data format.
PREPARATORY
PROCEDURES FOR
MONITORING
1
 Differences in address specifications by data format
3.3.6
SM devices
The SM devices are bit devices into which interrupt outputs and clock data that turn ON/OFF at 1-second cycles.
 List of SM devices
The following shows the SM devices (virtual devices inside the GOT).
Address
Description
Set side
Interrupt output
When the ON/OFF state of SM0 to 49 is changed by a touch switch on the GOT, for example, the interrupt
codes shown below are transmitted (interrupt output) to the host side.*1*2
The data amount (number of bytes) to be interrupt-output is set at "Interrupt Data Byte" in "Communication
Detail Settings". (
3.5.1 Setting communication interface (Communication settings))
Address
Event type
SM0
SM0 to 49
SM1
SM2
SM48
SM49
Interrupt code
Changed from OFF to ON
50H
Changed from ON to OFF
51H
Changed from OFF to ON
52H
Changed from ON to OFF
53H
Changed from OFF to ON
54H
Changed from ON to OFF
55H
Changed from OFF to ON
B0H
Changed from ON to OFF
B1H
Changed from OFF to ON
B2H
Changed from ON to OFF
B3H
User
1-second cycle clock
Turns ON/OFF at a 1-second cycle.
SM50
0.5
0.5
System
2-second cycle clock
Turns ON/OFF at a 2-second cycle.
SM51
1
1
Interrupt code output disable flag
Enables or disables the output of the interrupt code.
OFF : Interrupt code output enabled ON : Interrupt code output disabled
SM52
User
When set to disable the interrupt code output, no interrupt data are output to the host.
(Relevant devices: D13, D14, SM0 to 49)
SM53 to 63
Unused
*1
*2
―
After the ON/OFF state is changed, the interrupt data is output within a period of 1 to 10 ms.
When the ON/OFF state of SM0 to 49 is changed from the host side, interrupt output is not performed.
POINT
(1) The side where virtual devices are set
System : Set on the system side.
User
: Set on the user side (by sending request messages from host or using the touch switches, etc.
on the GOT).
(2) Interrupt outputs (SM0 to 49)
• To disable the interrupt output, turn ON SM52 (interrupt code output disable flag). (
3.3.6 SM devices)
• To enable the interrupt output, set 8 bits to the data length at "Communication Detail Settings".
(
3.5.1 Setting communication interface (Communication settings))
• When "7 bits" is set, the MSB (8th bit) is ignored. (Example: FFH 7FH)
3 - 14
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.3 Device Data Area
Address specification value
b7
b6
b5
b4
b3
b2
b1
b0
SM7
SM6
SM5
SM4
SM3
SM2
SM1
SM0
SM15
SM14
SM13
SM12
SM11
SM10
SM9
SM8
SM23
SM22
SM21
SM20
SM19
SM18
SM17
SM16
SM31
SM30
SM29
SM28
SM27
SM26
SM25
SM24
SM39
SM38
SM37
SM36
SM35
SM34
SM33
SM32
SM47
SM46
SM45
SM44
SM43
SM42
SM41
SM40
SM52
SM51
SM50
SM49
SM48
Unused
Format
1, 2
8464
8465
8466
Format
5
2200H
2201H
2202H
2203H
2204H
2205H
8467
2206H
―
―
Unused
*1
Format
3, 4
Format
6 to 9
2110H
2111H
*2*3
2112H
3
2113H
For the address specification method for each data format, refer to the following.
3.4 Message Formats
:
:
:
:
:
GOT-A900 Series microcomputer connection
GOT-F900 series microcomputer connection
Digital Electronics Corporation's memory link method
4E frame
QnA compatible 3E frame
4
In formats 6, 7, values are specified within a range of SM0 to 52.
For reading or writing data in word units, specify the addresses in 16-point units. (Example: SM0, SM16, SM32, etc.)
MODBUS(R)/TCP
CONNECTION
5
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
*2
*3
Formats 1, 2
Formats 3, 4
Formats 5
Formats 6, 7
Formats 8, 9
MODBUS(R)/RTU
CONNECTION
•
•
•
•
•
2
MICROCOMPUTER
CONNECTION
(ETHERNET)
Address
MICROCOMPUTER
CONNECTION
(SERIAL)
The address specification of devices varies depending on the data format.*1
The following shows the address specification values for each data format.
PREPARATORY
PROCEDURES FOR
MONITORING
1
 Differences in address specifications by data format
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.3 Device Data Area
3 - 15
3.4 Message Formats
This section describes the format of messages that can be used in the microcomputer connection (Ethernet).
3.4.1
Data format type and application
 Data format type and application
Communication is possible using any of the data formats shown below.
(1) Formats 1, 2 (GOT-A900 Series microcomputer connection)
This is the same message format as when a microcomputer connection is established with the GOT-A900
series.
Type
Name
Description
Format 1
GOT-A900 series microcomputer connection
(ASCII)
This format is used when the GOT is connected to the host in a 1:1
connection. The data format is ASCII.
Format 2
GOT-A900 series microcomputer connection
(Binary)
This format is used when the GOT is connected to the host in a 1:1
connection. The data format is Binary.
Refer to
3.4.3
(2) Formats 3, 4 (GOT-F900 series microcomputer connection)
This is the compatible message format with when a microcomputer connection is established with the GOTF900 Series.
Type
Name
Description
Format 3
GOT-F900 series microcomputer connection
(ASCII)
This format is used when the GOT is connected to the host in a 1:1
connection. The data format is ASCII.
Format 4
GOT-F900 series microcomputer connection
(Binary)
This format is used when the GOT is connected to the host in a 1:1
connection. The data format is Binary.
Refer to
3.4.4
(3) Format 5 (Digital Electronics Corporation's memory link method)
This is the compatible message format with the protocol of the Digital Electronics Corporation's memory link
method.
Type
Format 5
Name
Digital Electronics Corporation's memory link
method
Description
This is the basic format of the Digital Electronics Corporation's memory link
method.
Refer to
3.4.5
(4) Formats 6, 7 (4E frame)
This is the compatible message format with when a communication is performed using the MC protocol of Q/
QnA Series serial communication module.
Type
Name
Description
Format 6
4E frame (ASCII)
This is the basic format of the MC protocols. The data format is ASCII.
Format 7
4E frame (Binary)
This is the basic format of the MC protocols. The data format is Binary.
Refer to
3.4.6
(5) Formats 8, 9 (QnA compatible 3E frame)
This is the compatible message format with when a communication is performed using the MC protocol of Q/
QnA Series serial communication module.
Type
Name
Description
Format 8
QnA compatible 3E frame (ASCII)
This is the basic format of the MC protocols. The data format is ASCII.
Format 9
QnA compatible 3E frame (Binary)
This is the basic format of the MC protocols. The data format is Binary.
 How to set data format
Set the data format at [Detail setting] in GT Designer3.
For details of the data format setting method, refer to the following.
3.5.1 Setting communication interface (Communication settings)
3 - 16
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
Refer to
3.4.7
1
PREPARATORY
PROCEDURES FOR
MONITORING
List of commands
Command name
Description
Max. number of points
processed
Symbol
ASCII
code
RD
52H 44H
Batch read
in word units
WD
57H 44H
Batch write
in word units
Writes to word devices in 1-point units.
Random read
Reads multiple different bit devices in 16-point units.
64 words (1024 points)
in word units*1
Reads multiple different word devices in 1-point units.
64 points
Random write
Writes to multiple different word devices in 16-point units.
64 words (1024 points)
in word units*1
Writes to multiple different word devices in 1-point units.
64 points
Reads bit devices in 16-point units.
64 words (1024 points)
Reads word devices in 1-point units.
64 points
Writes to bit devices in 16-point units.
64 words (1024 points)
64 points
RR
52H 52H
RW
52H 57H
TR
54H 52H
Read clock data
Reads the clock data of the GOT.
―
TS
54H 53H
Set clock data
Sets the clock data of the GOT.
―
*1
 List of commands for formats 3, 4 (GOT-F900 series microcomputer connection)
Command name
Description
Max. number of points
processed
Symbol
ASCII
code
0
30H
Batch read
(w/out station No.)
Reads bit devices in byte units.
255bytes (2040 points)
Reads word devices in byte units.
255bytes (127 points)
A
41H
Batch read
(w/ station No.)
Reads bit devices in byte units.
255bytes (2040 points)
Reads word devices in byte units.
255bytes (127 points)
1
31H
Batch write
(w/out station No.)
B
42H
Batch write
(w/ station No.)
3
33H
Multi-point write in bit
units (w/out station No.)
D
44H
Multi-point write in bit
units (w/ station No.)
4
34H
Fill command
(w/out station No.)
E
45H
Fill command
(w/ station No.)
5
35H
Set clock data
(w/out station No.)
F
46H
Set clock data
(w/ station No.)
6
36H
Read clock data
(w/out station No.)
47H
Read clock data
(w/ station No.)
255bytes (2040 points)
255bytes (127 points)
Writes to bit devices in byte units.
255bytes (2040 points)
Writes to word devices in byte units.
255bytes (127 points)
Writes bit patterns (bit ON/OFF, inversion, direct specification) in
1-point units (8 bits for 1 point) to a specified device.
70bytes (560 points)
―
Sets the clock data of the GOT.
―
Reads the clock data of the GOT.
―
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Writes the same value to a range of specified devices.
6
CONNECTION TO
SOUND OUTPUT
UNIT
Writes to bit devices in byte units.
Writes to word devices in byte units.
5
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
G
3
4
Mixed specification of bit devices and word devices is also possible.
Command
2
MODBUS(R)/RTU
CONNECTION
Command
MICROCOMPUTER
CONNECTION
(SERIAL)
 List of commands for formats 1, 2 (GOT-A900 Series microcomputer connection)
MICROCOMPUTER
CONNECTION
(ETHERNET)
The following shows the list of commands available in each data format.
MODBUS(R)/TCP
CONNECTION
3.4.2
3 - 17
 List of commands for formats 5 (Digital Electronics Corporation's memory link method)
Command
Command name
Description
Max. number of points
processed
Symbol
ASCII
code
R
52H
Batch read
in word units
Reads bit devices in 16-point units.
64 words (1024 points)
Reads word devices in 1-point units.
64 points
W
57H
Batch write
in word units
Writes to bit devices in 16-point units.
64 words (1024 points)
Writes to word devices in 1-point units.
64 points
I
49H
Interrupt inquiry
Issues an interrupt inquiry.
―
 List of commands for formats 6, 7 (4E frame), formats 8, 9 (QnA compatible 3E frame)
Command
Subcommand
0401
0001
Batch read
in bit units
0401
0000
Batch read
in word units
Command name
Description
Reads bit devices in 1-point units.
Max. number of points
processed
64 points
Reads bit devices in 16-point units.*3
64 words (1024 points)
Reads word devices in 1-point units.
64 points
Writes to bit devices in 1-point units.
64 points
1401
0001
Batch write
in bit units
1401
0000
Batch write
in word units
Writes to bit devices in 16-point units.*3
64 words (1024 points)
Writes to word devices in 1-point units.
64 points
Random read
Reads multiple different bit devices in 16-point and 32-point units.*3
in word units*1
Reads multiple different word devices in 1-point and 2-point units.
64 points
Random write
in bit units
Writes to multiple different bit devices in 1-point units.
64 points
Random write
Writes to multiple different bit devices in 16-point and 32-point units.*3
0403
0000
1402
0001
1402
0000
in word units
*1
Writes to multiple different word devices in 1-point and 2-point units.
64 words (1024 points)
64 words (1024 points)
64 points
0406
0000
Multiple block
batch read
Reads multiple blocks. A bit device (16 bits for 1 point) or a word device
1406
0000
Multiple block
batch write
Writes multiple blocks. A bit device (16 bits for 1 point) or a word device
1901*2
0000
Read clock data
Reads the clock data of the GOT.
―
*2
0000
Set clock data
Sets the clock data of the GOT.
―
0901
*1
*2
*3
3 - 18
(1 word for 1 point) is regarded as one block.*3
(1 word for 1 point) is regarded as one block.*3
Mixed specification of bit devices and word devices is also possible.
This is a dedicated command of GOT for the microcomputer connection.
Specifies the address of bit devices in 16-point units. (Example: M0, M16, M32, and others)
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
64 points
64 points
1
Formats 1, 2 (GOT-A900 Series microcomputer connection)
PREPARATORY
PROCEDURES FOR
MONITORING
3.4.3
2
Item
MICROCOMPUTER
CONNECTION
(SERIAL)
 Basic format of data communication
Message format
Command
Data
Request message
3
GOT)
(H)
(L)
MICROCOMPUTER
CONNECTION
(ETHERNET)
(host
(1) During processing of read commands
Data
(GOT
host)
4
MODBUS(R)/RTU
CONNECTION
Response message
during normal
communication
(2) During processing of write commands
ACK
5
MODBUS(R)/TCP
CONNECTION
06H
Error
Response message
during faulty
communication
NAK Code
(GOT
15H
host)
6
CONNECTION TO
SOUND OUTPUT
UNIT
Output value
During interrupt
output
1/2/4
bytes*1
Set the number of interrupt data bytes at [Detail setting] in GT Designer3.
For the setting of the number of interrupt data bytes, refer to the following.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
3.5.1 Setting communication interface (Communication settings)
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
*1
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 19
 Details of data items in message format
POINT
Data code during communication
Communication of the format 1 is performed in ASCII code. (excluding interrupt output)
Communication of the format 2 is performed in Binary code.
(1) Control codes
Symbol
ASCII code
EOT
04H
End of Transmission
Description
ENQ
05H
Enquiry (start of enquiry)
NAK
15H
Negative ACK (error response)
ACK
06H
Acknowledge (write completion response)
LF
0AH
Line Feed
CL
0CH
Clear
CR
0DH
Carriage Return
(2) Command
Specifies the contents to access from the host to GOT.
The command is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.
For details of the commands that can be used, refer to the following.
3.4.2 List of commands
(3) Address
Specifies the head No. of the device data to be read/written.
In the format 1, the address notated in decimal is converted to a 4-digit ASCII code (Hex) and transmitted from
the upper digit.
In the format 2, the address notated in decimal is converted to a 2-digit Binary code (binary) and transmitted
from the upper digit.
For details of the device range that can be accessed, refer to the following.
3.3 Device Data Area
(4) Number of points
Specifies the number of device data to be read/written. (Setting range: 1 to 64)
In the format 1, the address notated in decimal is converted to a 2-digit ASCII code (Hex) and transmitted from
the upper digit.
In the format 2, the address notated in decimal is converted to a 1-digit Binary code (binary) and transmitted.
(5) Year, month, day, hour, minute, second and day of the week data
Specifies year, month, day, hour, minute, second, and day of the week to be read/set to the GOT clock data.
In the format 1, the address notated in decimal is converted to a 2-digit ASCII code (Hex) and transmitted from
the upper digit.
In the format 2, the address notated in decimal is converted to a 1-digit Binary code (binary) and transmitted.
■ Message format (5) Read clock data (TR) command
■ Message format (6) Set clock data (TS) command
(6) Data
Specifies the data to read from/write to the specified device data.(word unit)
In the format 1, the address notated in hexadecimal is converted to a 4-digit ASCII code (Hex) and transmitted
from the upper digit.
In the format 2, the address notated in hexadecimal is converted to a 2-digit Binary code (binary) and
transmitted from the upper digit.
(7) Error code
This is the response message at faulty communication appended with error contents. Error code is transmitted
in 1 byte.
For the error codes, refer to the following.
■ Error code list
3 - 20
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
1
PREPARATORY
PROCEDURES FOR
MONITORING
 Message Formats
(1) Batch read in word units (RD) command
(a) When reading a word device
The following shows an example of reading the two points of the virtual devices D100 and D101.
(Assuming D100=0102H, D101=0304H are stored.)
Item
D100
0102H
D101
0304H
MICROCOMPUTER
CONNECTION
(SERIAL)
2
Message format
3
Command
(host
GOT)
Number of
points
Address
R
D
0
1
0
0
0
2
52H
44H
30H
31H
30H
30H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
4
(format 2: GOT-A900 Series microcomputer connection (Binary))
Command
R
Number
of points
Address
D
00H
64H
MODBUS(R)/RTU
CONNECTION
Request message
MICROCOMPUTER
CONNECTION
(ETHERNET)
(format 1: GOT-A900 Series microcomputer connection (ASCII))
02H
(format 1: GOT-A900 Series microcomputer connection (ASCII))
5
(GOT
host)
0
1
0
2
0
3
0
4
30H
31H
30H
32H
30H
33H
30H
34H
(L)
(H)
(H)
(L)
(format 2: GOT-A900 Series microcomputer connection (Binary))
Data 1
(D100)
01H
02H
6
Data 2
(D101)
03H
CONNECTION TO
SOUND OUTPUT
UNIT
Response message
during normal
communication
Data 2 (D101)
MODBUS(R)/TCP
CONNECTION
Data 1 (D100)
04H
Error
NAK code
06H
host)
The above is a case
where the sum check error
(06H) has occurred.
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(GOT
15H
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Response message
during faulty
communication
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 21
(b) When reading a bit device
The following shows an example of reading the two points of the virtual devices M0 to M31.
(Assuming M0="1" and M31="1" are stored.)
Item
M15 to 0
0001H
M31 to 6
8000H
Message format
(format 1: GOT-A900 Series microcomputer connection (ASCII))
Command
Request message
(host
GOT)
Number of
points
Address
R
D
8
3
2
0
0
2
52H
44H
38H
33H
32H
30H
30H
32H
(H)
(L)
(H)
(L)
(H)
(L)
(format 2: GOT-A900 Series microcomputer connection (Binary))
Command
R
D
Address
83H
20H
Number
of points
02H
(format 1: GOT-A900 Series microcomputer connection (ASCII))
Data 2 (M31 to 16)
Data 1 (M15 to 0)
0
0
0
1
8
0
0
0
30H
30H
30H
31H
38H
30H
30H
30H
(L)
(H)
(H)
(L)
00000000000000011000000000000000
Response message
during normal
communication
(GOT
host)
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
11111198765432103322222222221111
543210
1098765432109876
(format 2: GOT-A900 Series microcomputer connection (Binary))
Data 1
Data 2
(M15 to 0) (M31 to 16)
00H
01H
80H
00H
00000000000000011000000000000000
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
11111198765432103322222222221111
543210
1098765432109876
Error
NAK code
Response message
during faulty
communication
(GOT
15H
06H
host)
The above is a case where
the sum check error (06H)
has occurred.
3 - 22
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
1
PREPARATORY
PROCEDURES FOR
MONITORING
(2) Batch write in word units (WD) command
(a) When writing to a word device
The following shows as example of writing "0064H"and "0065H"to virtual devices D100 and D101.
0000H
D100
0064H
D101
0000H
D101
0065H
Before execution
2
MICROCOMPUTER
CONNECTION
(SERIAL)
D100
After execution
Item
Message format
(format 1: GOT-A900 Series microcomputer connection (ASCII))
W
GOT)
1
0
31H
30H
57H
44H
30H
(H)
(L)
(H)
0
0
2
0
0
6
30H
36H
30H
30H
32H
30H
(L)
(H)
(L)
(H)
3
Data 2 (D101)
0
0
6
34H
30H
30H
36H
(L)
(H)
4
5
35H
(L)
(format 2: GOT-A900 Series microcomputer connection (Binary))
Command
W
D
Number
of points
Address
00H
64H
02H
Response message
during normal
communication
ACK
(GOT
06H
host)
Data1
(D100)
00H
64H
Data 2
(D101)
00H
4
65H
MODBUS(R)/RTU
CONNECTION
(host
0
Data 1(D100)
5
MODBUS(R)/TCP
CONNECTION
Request message
D
Number of
points
Address
MICROCOMPUTER
CONNECTION
(ETHERNET)
Command
Error
NAK code
Response message
during faulty
communication
06H
host)
6
CONNECTION TO
SOUND OUTPUT
UNIT
The above is a case where
the sum check error (06H)
has occurred.
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(GOT
15H
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 23
(b) When writing to a bit device
The following shows an example of writing "1"s to virtual devices M0 and M31.
M15 to 0
0000H
M15 to 0
0001H
M31 to 16
0000H
M31 to 16
8000H
Before execution
After execution
Item
Message format
(format 1: GOT-A900 Series microcomputer connection (ASCII))
Command
Number
of points
Address
Data 1 (M15 to 0)
Data 2 (M31 to 16)
W
D
8
3
2
0
0
2
0
0
0
1
8
0
0
0
57H
44H
38H
33H
32H
30H
30H
32H
30H
30H
30H
31H
38H
30H
30H
30H
(H)
(L)
(H)
–
–
(L)
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
00000000000000011000000000000000
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
11111198765432103322222222221111
543210
1098765432109876
Request message
(host
GOT)
(format 2: GOT-A900 Series microcomputer connection (Binary))
Command
W
D
Data 1
Data 2
Number
of points (M15 to 0) (M31 to 16)
Address
20H
80H
02H
00H
01H
80H
00H
00000000000000011000000000000000
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
11111198765432103322222222221111
543210
1098765432109876
ACK
Response message
during normal
communication
(GOT
06H
host)
Error
NAK code
Response message
during faulty
communication
(GOT
15H
06H
host)
The above is a case where
the sum check error (06H)
has occurred.
3 - 24
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
1
PREPARATORY
PROCEDURES FOR
MONITORING
(3) Random read in word units (RR) command
The following shows an example of reading the two points of the virtual devices D100 and M0 to M15.
(Assuming D100=0064H, M0=1are stored.)
0064H
M15 to 0
0001H
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Item
D100
Message format
(format 1: GOT-A900 Series microcomputer connection (ASCII))
R
Request message
(host
GOT)
Address 1
R
0
1
0
Address 2
0
8
3
2
3
0
52H
52H
30H
31H
30H
30H
38H
33H
32H
30H
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
MICROCOMPUTER
CONNECTION
(ETHERNET)
Command
(format 2: GOT-A900 Series microcomputer connection (Binary))
Command
Address 1
Address 2
4
R
64H
00H
80H
20H
MODBUS(R)/RTU
CONNECTION
R
(format 1: GOT-A900 Series microcomputer connection (ASCII))
Data 1 (D100)
Data 2 (M15 to 0)
0
6
4
0
0
0
1
30H
36H
34H
30H
30H
30H
31H
(H)
–
–
(L)
(H)
–
–
(L)
5
MODBUS(R)/TCP
CONNECTION
0
30H
0000000000000001
Response message
during normal
communication
6
(format 2: GOT-A900 Series microcomputer connection (Binary))
host)
Data 1
(D100)
00H
64H
CONNECTION TO
SOUND OUTPUT
UNIT
(GOT
MMMMMMMMMMMMMMMM
1111119876543210
543210
Data 2
(M15 to 0)
00H
01H
7
CONNECTION TO
EXTERNAL I/O
DEVICE
0000000000000001
MMMMMMMMMMMMMMMM
1111119876543210
543210
Error
NAK code
(GOT
15H
8
06H
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Response message
during faulty
communication
host)
The above is a case where
the sum check error (06H)
has occurred.
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 25
(4) Random write in word units (RW) command
The following shows an example of writing "0064H" and "1" to virtual devices D100 and M0, respectively.
D100
0000H
D100
0064H
M15 to 0
0000H
M15 to 0
0001H
Before execution
After execution
Item
Message format
(format 1: GOT-A900 Series microcomputer connection (ASCII))
Command
Address 1
Data 1 (D100)
Address 2
Data 2 (M15 to 0)
R
W
0
1
0
0
0
0
6
4
8
3
2
0
0
0
0
1
52H
57H
30H
31H
30H
30H
30H
30H
36H
34H
38H
33H
32H
30H
30H
30H
30H
31H
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
(H)
–
–
(L)
(H)
–
–
(L)
0000000000000001
MMMMMMMMMMMMMMMM
1111119876543210
543210
Request message
(host
GOT)
(format 2: GOT-A900 Series microcomputer connection (Binary))
Command
R
W
Address 1
00H
64H
Data 1
(D100)
00H
00H
Address 2
20H
80H
Data 2
(M15 to 0)
00H
01H
0000000000000001
MMMMMMMMMMMMMMMM
1111119876543210
543210
Response message
during normal
communication
(GOT
ACK
06H
host)
Error
NAK code
Response message
during faulty
communication
(GOT
15H
06H
host)
The above is a case where
the sum check error (06H)
has occurred.
3 - 26
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
1
PREPARATORY
PROCEDURES FOR
MONITORING
(5) Read clock data (TR) command
The following shows an example of reading the clock data of GOT.
(Assuming that the clock data of GOT has been set to "2009, October 1, 18:46:49, Thursday".)
Time display
2009/10/01 18:46:49
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Item
THU
Message format
Command
Request message
T
R
54H
52H
(H)
(L)
GOT)
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
(host
(format 1: GOT-A900 Series microcomputer connection (ASCII))
Year data Month data
(GOT
Second
data
Hour data Minute data
Day-ofweek data
0
9
1
0
0
1
1
8
4
6
4
9
0
4
30H
39H
31H
30H
30H
31H
31H
38H
34H
36H
34H
39H
30H
34H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
4
(format 2: GOT-A900 Series microcomputer connection (Binary))
MODBUS(R)/RTU
CONNECTION
Response message
during normal
communication
Day data
host)
Year Month Day Hour Minute Second Day-ofdata data data data data data week data
09H
0AH
01H
12H
2EH
31H
04H
5
MODBUS(R)/TCP
CONNECTION
Error
NAK code
Response message
during faulty
communication
06H
host)
The above is a case where
the sum check error (06H)
has occurred.
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(GOT
15H
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 27
(6) Set clock data (TS) command
The following shows an example of setting the clock data of GOT.
(Assuming the clock data of GOT is to be set to "2009, October 1, 18:46:49 Thursday".)
Time display
2009/10/01 18:46:49
THU
After execution
Item
Message format
(format 1: GOT-A900 Series microcomputer connection (ASCII))
Command
Request message
(host
GOT)
Year data
Month data
Day data
Second
data
Hour data Minute data
Day-ofweek data
T
S
0
9
1
0
0
1
1
8
4
6
4
9
0
4
54H
53H
30H
39H
31H
30H
30H
31H
31H
38H
34H
36H
34H
39H
30H
34H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(format 2: GOT-A900 Series microcomputer connection (Binary))
Year Month Day Hour Minute Second Day-ofCommand data data data data data data week data
T
S
09H
Response message
during normal
communication
(GOT
01H
0AH
12H
2EH
31H
04H
ACK
06H
host)
Error
NAK code
Response message
during faulty
communication
(GOT
15H
06H
host)
The above is a case where
the sum check error (06H)
has occurred.
POINT
When a wrong day of the week has been set by the clock data setting command
If a wrong day of the week is set by the clock data setting commands, the clock data will differ from the time
displayed on the utility.
Example: When October 1, 2009 (Tuesday) is set by the clock data setting command (the actual day of the week is
Thursday), Thursday (THU) will be displayed on the utility time display.
3 - 28
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
The following shows an example of an interrupt output when data are written to the interrupt output devices (D13
and D14).
(Assuming that "3139H" is written to D13 and "AA55H" to D14.)
Example: When the number of interrupt data bytes is 2
2
3139H
MICROCOMPUTER
CONNECTION
(SERIAL)
D13
Interrupt
Interrupt output
Output Output
value 1 value 2
Item
3
39H
MICROCOMPUTER
CONNECTION
(ETHERNET)
31H
Message format
(1) When [Interrupt Data Byte] in "Communication Detail Settings" is set to "1 byte"
4
MODBUS(R)/RTU
CONNECTION
Output
value 1
39H
(2) When [Interrupt Data Byte] in "Communication Detail Settings" is set to "2 byte"
Output Output
value 1 value 2
Interrupt output
5
host)
39H
MODBUS(R)/TCP
CONNECTION
31H
(3) When [Interrupt Data Byte] in "Communication Detail Settings" is set to "4 byte"
Output Output Output Output
value1 value2 value3 value4
55H
31H
6
39H
CONNECTION TO
SOUND OUTPUT
UNIT
AAH
POINT
Interrupt output
7
To disable the interrupt output, turn ON SM52 (interrupt code output disable flag).
3.3.6 SM devices)
CONNECTION TO
EXTERNAL I/O
DEVICE
(
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(GOT
PREPARATORY
PROCEDURES FOR
MONITORING
1
(7) In the case of interrupt outputs
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 29
 Error code list
The error contents (error code) are appended to the response message during faulty communication.
The following shows error code, error contents, cause, and measures.
Error code
Description
Action
• Review the contents of the message to transmit.
• Check the commands in the message.
10H
Command error
An unsupported command was used.
11H
Message length error
The upper limit of the data length that can be received by
the GOT has been exceeded.
• Review the contents of the message to transmit.
• Check the data length of the message. (data length of the data section,
etc.)
15H
Clock data setting error
The setting value of the clock data has error.
• Review the contents of the message to transmit.
• Check whether the non-existent data is set (e.g. setting "07" at the day of
the week) as clock data.
7AH
Address error
The start address of the read/write device is out of range.
7BH
Exceeded number of points error
The read/write range exceeded the device range.
(
3.4.2 List of commands)
• Review the contents of the message to transmit.
• Check the devices that can be used and the device ranges.
(
3.3 Device Data Area)
 Precautions
(1) Batch reading/writing crossing over different devices
When using the batch read (RD) or batch write (WD) command, do not batch read/write crossing over the
different devices.
This will cause an error response.
(2) Storage order for 32-bit data
To use the program of GOT-A900 series with [32bit Order] setting to GOT1000 series, set [HL Order] to [32bit
Order] for [Communication Detail Settings] when 32-bit data is set for GOT-A900 series.
With setting [LH Order], the order of upper bits and lower bits are reversed when the GOT displays and writes
32-bit data.
3 - 30
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
1
Formats 3, 4 (GOT-F900 series microcomputer connection)
PREPARATORY
PROCEDURES FOR
MONITORING
3.4.4
2
Item
MICROCOMPUTER
CONNECTION
(SERIAL)
 Basic format of data communication
Message format
(1) w/out station No.
Command
Data
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
Request message
(host
GOT)
(2) w/station No.
(H)
Data
4
MODBUS(R)/RTU
CONNECTION
Com- Station No.
mand
(L)
(1) During processing of read commands
5
MODBUS(R)/TCP
CONNECTION
Data
Response message
during normal
communication
(GOT
host)
(2) During processing of write commands
6
CONNECTION TO
SOUND OUTPUT
UNIT
ACK
06H
NAK
(GOT
15H
host)
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Response message
during faulty
communication
Output
value
During interrupt
output
1/2/4
bytes*1
8
Set the number of interrupt data bytes at [Detail setting] in GT Designer3.
For the setting of the number of interrupt data bytes, refer to the following.
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
*1
3.5.1 Setting communication interface (Communication settings)
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 31
 Details of data items in message format
POINT
Data code during communication
Communication of the format 3 is performed in ASCII code. (excluding interrupt output)
Communication of the format 4 is performed in Binary code.
(1) Control codes
Symbol
ASCII code
EOT
04H
End of Transmission
Description
ENQ
05H
Enquiry (start of enquiry)
NAK
15H
Negative ACK (error response)
ACK
06H
Acknowledge (write completion response)
LF
0AH
Line Feed
CL
0CH
Clear
CR
0DH
Carriage Return
(2) Command
Specifies the contents to access from the host to GOT.
The command is converted to a 1-digit ASCII code (Hex) and transmitted.
For details of the commands that can be used, refer to the following.
3.4.2 List of commands
(3) Station No.
Station No. is used to identify the GOT with which the host communicates. (Setting range: 0 to 31)
In the format 3, the address notated in decimal is converted to a 2-digit ASCII code (Hex) and transmitted from
the upper digit.
In the format 4, the address notated in decimal is converted to a 1-digit Binary code (binary) and transmitted.
The GOT processes only commands whose station No. matches the "Host Address (0 to 31)" set at
"Communication Detail Settings". (The message of command whose station No. does not match is ignored.)
For setting method of "Communication Detail Settings", refer to the following.
3.5.1 Setting communication interface (Communication settings)
(4) Address
Specifies the head No. of the device data to be read/written.
In the format 3, the address notated in hexadecimal is converted to a 4-digit ASCII code (Hex) and transmitted
from the upper digit.
In the format 4, the address notated in hexadecimal is converted to a 2-digit Binary code (binary) and
transmitted from the upper digit.
For details of the device range that can be accessed, refer to the following.
3.3 Device Data Area
(5) Bit pattern
Specifies the pattern of the bits to change.
In the format 3, the address notated in hexadecimal is converted to a 2-digit ASCII code (Hex) and transmitted
from the upper digit.
In the format 4, the address notated in hexadecimal is converted to a 1-digit Binary code (binary) and
transmitted.
■ Message format (3) Multi-point write in bit units (3) command (w/out station No.), multi-point
write in bit units (D) command (w/ station No.)
3 - 32
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
Specifies how to change the data of the specified address by bit pattern.
(Setting range: 0 to 3)
Data notated in decimal is converted to a 1-digit ASCII code (Hex) and transmitted.
■ Message format (3) Multi-point write in bit units (3) command (w/out station No.), multi-point
write in bit units (D) command (w/ station No.)
PREPARATORY
PROCEDURES FOR
MONITORING
1
(6) Write specification
Specifies the number of device data to be written to multiple points in bit units. (Setting range: 0 to 70)
In the format 3, the address notated in decimal is converted to a 2-digit ASCII code (Hex) and transmitted from
the upper digit.
In the format 4, the address notated in decimal is converted to a 1-digit Binary code (binary) and transmitted.
(9) Year, month, day, hour, minute, second and day of the week data
Specifies year, month, day, hour, minute, second, and day of the week to be read/set to the GOT clock data.
In the format 3, the address notated in decimal is converted to a 2-digit ASCII code (Hex) and transmitted from
the upper digit.
In the format 4, the address notated in decimal is converted to a 1-digit Binary code (binary) and transmitted.
■ (5) Read clock data (6) command (w/out station No.), read clock data (G) command (w/station
No.)
■ (6) Set clock data (5) command (w/out station No.), set clock data (F) command (w/station No.)
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
(8) Number of points
4
MODBUS(R)/RTU
CONNECTION
Specifies the number of bytes of the device data to be batch read/written. (Setting range: 0 to FFH)
In the format 3, the address notated in hexadecimal is converted to a 2-digit ASCII code (Hex) and transmitted
from the upper digit.
In the format 4, the address notated in hexadecimal is converted to a 1-digit Binary code (binary) and
transmitted.
MICROCOMPUTER
CONNECTION
(SERIAL)
2
(7) Number of bytes
(11) Write data
Specifies the data to write to the specified device data.
The address notated in hexadecimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper
digit.
6
CONNECTION TO
SOUND OUTPUT
UNIT
Specifies the data to read from/write to the specified device data. (word unit)
In the format 3, the address notated in hexadecimal is converted to a 4-digit ASCII code (Hex) and transmitted
from the upper digit.
In the format 4, the address notated in hexadecimal is converted to a 2-digit Binary code (binary) and
transmitted from the upper digit.
MODBUS(R)/TCP
CONNECTION
5
(10) Data
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 33
 Message format
(1) Batch read (0) command (w/out station No.), batch read (A) command (w/station No.)
(a) When reading a word device
The following shows an example of reading four bytes of virtual devices R100 to R101 from the GOT at
station No.15.
(Assuming R100=3D21H, R101=3604H are stored.)
Item
R100
3D21H
R101
3604H
Message format
(format 3: GOT-F900 Series microcomputer connection (ASCII))
Com- Station No.
mand
Request message
(host
GOT)
Number
of bytes
Address
A
1
5
0
0
C
8
0
4
41H
31H
35H
30H
30H
43H
38H
30H
34H
(H)
(L)
(H)
–
–
(L)
(H)
(L)
(format 4: GOT-F900 Series microcomputer connection (Binary))
Com- Station
mand No.
A
Number
of bytes
Address
0FH
C8H
00H
04H
(format 3: GOT-F900 Series microcomputer connection (ASCII))
Data 1
Data 2
Data 3
Data 4
(R100 upper) (R100 lower) (R101 upper) (R101 lower)
Response message
during normal
communication
(GOT
host)
3
D
2
1
3
6
0
4
33H
44H
32H
31H
33H
36H
30H
34H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Data 3
Data 4
(format 4: GOT-F900 Series microcomputer connection (Binary))
Data 1
Data 2
(R100 upper) (R100 lower) (R101 upper) (R101 lower)
3DH
21H
Response message
during faulty
communication
NAK
(GOT
15H
3 - 34
host)
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
36H
04H
1
0001H
M31 to 16
8000H
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Item
M15 to 0
PREPARATORY
PROCEDURES FOR
MONITORING
(b) When reading a bit device
The following shows an example of reading four bytes of the virtual devices M0 to M31.
(Assuming M0="1" and M31="1" are stored.)
Message format
(format 3: GOT-F900 Series microcomputer connection (ASCII))
1
A
41H
Request message
(host
GOT)
Number of
bytes
Address
5
2
0
0
0
0
3
4
31H
35H
32H
30H
30H
30H
30H
34H
(H)
(L)
(H)
–
–
(L)
(H)
(L)
MICROCOMPUTER
CONNECTION
(ETHERNET)
Command Station No.
(format 4: GOT-F900 Series microcomputer connection (Binary))
Com- Station
mand No.
0FH
20H
00H
4
04H
MODBUS(R)/RTU
CONNECTION
A
Number
of bytes
Address
(format 3: GOT-F900 Series microcomputer connection (ASCII))
0
1
Data 2
Data 3
Data 4
(M15 to 8) (M23 to 16) (M31 to 24)
0
0
0
0
8
5
0
30H
31H
30H
30H
30H
30H
38H
30H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
MODBUS(R)/TCP
CONNECTION
Data 1
(M7 to 0)
00000001000000000000000010000000
(GOT
6
CONNECTION TO
SOUND OUTPUT
UNIT
Response message
during normal
communication
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
76543210111111982222111133222222
543210
3210987610987654
(format 4: GOT-F900 Series microcomputer connection (Binary))
host)
Data 1 Data 2 Data 3 Data 4
(M7 to 0) (M15 to 8) (M23 to 16) (M31 to 24)
00H
00H
7
80H
CONNECTION TO
EXTERNAL I/O
DEVICE
01H
00000001000000000000000010000000
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
76543210111111982222111133222222
543210
3210987610987654
NAK
(GOT
15H
host)
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
Response message
during faulty
communication
3 - 35
(2) Batch write (1) command (w/out station No.), batch write (B) command (w/station No.)
(a) When writing to a word device
The following shows an example of writing "3D21H" and "3604H" to virtual devices R100 and R101 on the
GOT at station No.15.
R100
0000H
R100
0064H
R101
0000H
R101
0065H
Before execution
After execution
Item
Message format
(format 3: GOT-F900 Series microcomputer connection (ASCII))
Com- Station No.
mand
B
42H
1
Number
of bytes
Address
5
0
C
43H
38H
30H
34H
–
(L)
(H)
(L)
31H
35H
30H
30H
(H)
(L)
(H)
–
0
Following*1
0
8
4
*1
Data 1
Data 2
Data 3
Data 4
(R100 upper) (R100 lower) (R101 upper) (R101 lower)
Request message
(host
GOT)
3
D
2
1
3
6
0
4
33H
44H
32H
31H
33H
36H
30H
34H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(format 4: GOT-F900 Series microcomputer connection (Binary))
Com- Station
mand No.
Number
of bytes
Address
Following*2
B
0FH
00H
C8H 04H
*2
Data 1
Data 2
Data 3
Data 4
(R100 upper) (R100 lower) (R101 upper) (R101 lower)
3DH
21H
Response message
during normal
communication
ACK
(GOT
06H
host)
Response message
during faulty
communication
NAK
(GOT
15H
3 - 36
host)
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
36H
04H
M15 to 0
0000H
M15 to 0
0001H
M31 to 16
0000H
M31 to 16
8000H
2
After execution
Item
MICROCOMPUTER
CONNECTION
(SERIAL)
Before execution
Message format
(format 3: GOT-F900 Series microcomputer connection (ASCII))
B
42H
1
Number
of bytes
Address
5
0
0
30H
30H
30H
34H
–
(L)
(H)
(L)
31H
35H
32H
30H
(H)
(L)
(H)
–
0
Following*1
2
0
4
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
Com- Station No.
mand
*1
Data 2
Data 3
Data 4
(M15 to 8) (M23 to 16) (M31 to 24)
0
1
0
0
0
0
8
0
30H
31H
30H
30H
30H
30H
38H
30H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
4
MODBUS(R)/RTU
CONNECTION
Data 1
(M7 to 0)
00000001000000000000000010000000
(host
GOT)
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
76543210111111982222111133222222
3210987610987654
543210
(format 4: GOT-F900 Series microcomputer connection (Binary))
Com- Station
mand No.
5
Number
of bytes
Address
MODBUS(R)/TCP
CONNECTION
Request message
Following*2
B
0FH
20H
04H
00H
*2
6
00H
00H
CONNECTION TO
SOUND OUTPUT
UNIT
Data 1 Data 2
Data 3
Data 4
(M7 to 0) (M15 to 8) (M23 to 16) (M31 to 24)
01H
80H
00000001000000000000000010000000
MMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM
76543210111111982222111133222222
543210
3210987610987654
ACK
(GOT
06H
host)
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Response message
during normal
communication
1
PREPARATORY
PROCEDURES FOR
MONITORING
(b) When writing to a bit device
The following shows an example of writing "1"s to virtual devices M0 and M31 on the GOT at station No.15.
NAK
(GOT
15H
host)
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
Response message
during faulty
communication
3 - 37
(3) Multi-point write in bit units (3) command (w/out station No.), multi-point write in bit units (D) command (w/
station No.)
The following shows an example of turning OFF the virtual device M31 and turning ON the virtual device M2038
on the GOT at station No.31.
Item
Message format
(format 3: GOT-F900 Series microcomputer connection (ASCII))
Com- Station No. Number of
mand
points
Following *1
D
3
1
0
2
44H
33H
31H
30H
32H
(H)
(L)
(H)
(L)
*1
Write
specification
1
Write
specification
2
Bit pattern1
Address1
Address2
1
2
0
0
3
8
0
0
2
0
F
E
4
0
31H
32H
30H
30H
33H
38H
30H
30H
32H
30H
46
45H
34H
30H
(H)
–
–
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
*2
*2
(write specification1=1)
(write specification2=0)
10101010
Source data
bit pattern
Result
10000000
Source data
bit pattern
00101010
Result
MMMMMMMM
33222222
10987654
GOT)
10101010
01000000
11101010
MMMMMMMM
22222222
00000000
33333333
98765432
Request message
(host
Bit pattern2
(format 4: GOT-F900 Series microcomputer connection (Binary))
Com- Station Number
mand No.
of points
Following *3
D
1FH
02H
*3
Write
specification
1
1
Address1
20H
03H
Bit
pattern1
Write
specification
2
80H
0
Address2
20H
FEH
Bit
pattern2
40H
*2
*2
(write
(write
specification1=1)
specification2=0)
1 0 1 0 1 0 1 0 Source data
10101010
Source data
bit pattern
1 0 0 0 0 0 0 0 bit pattern
01000000
Result
00101010
Result
MMMMMMMM
33222222
10987654
Response message
during normal
communication
ACK
(GOT
06H
host)
Response message
during faulty
communication
NAK
(GOT
15H
3 - 38
host)
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
11101010
MMMMMMMM
22222222
00000000
33333333
98765432
0
ON
specification
Description
Action example
Original data
The numerical values to write by the bit pattern are specified
directly.
Original data
1010
Bit pattern
1100
Result
0010
Original data
1010
Bit pattern
1100
Result
0110
Original data
1010
Bit pattern
1100
Result
1100
2
3
4
MODBUS(R)/RTU
CONNECTION
Write
specification
Bits set to "1" by the bit pattern are inverted.
1110
5
MODBUS(R)/TCP
CONNECTION
3
Invert
specification
1100
Result
6
CONNECTION TO
SOUND OUTPUT
UNIT
2
Bits set to "1" by the bit pattern are turned OFF.
Bit pattern
7
CONNECTION TO
EXTERNAL I/O
DEVICE
1
OFF
specification
Bits set to "1" by the bit pattern are turned ON.
1010
MICROCOMPUTER
CONNECTION
(SERIAL)
Function
MICROCOMPUTER
CONNECTION
(ETHERNET)
Write
specification
PREPARATORY
PROCEDURES FOR
MONITORING
1
The write specification specifies how the data of the specified address is changed in the bit pattern.
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
*2
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 39
(4) Fill command (4) (w/out station No.), fill command (E) (w/station No.)
The following shows an example of writing "16"s to virtual devices R50 to R100 on the GOT at station No.27.
R50
0000H
1616H
R50
1616H
0000H
R100
R100
0000H
Before execution
1616H
After execution
Item
Message format
(format 3: GOT-F900 Series microcomputer connection (ASCII))
Com- Station No.
mand
Request message
(host
GOT)
Start address
Write
Data
End address
E
2
7
0
0
6
4
0
0
C
9
1
6
45H
32H
37H
30H
30H
36H
34H
30H
30H
43H
39H
31H
36H
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
(H)
(L)
(format 4: GOT-F900 Series microcomputer connection (Binary))
Com- Station
mand No.
E
1BH
Start
address
00H
64H
Response message
during normal
communication
ACK
(GOT
06H
host)
Response message
during faulty
communication
NAK
(GOT
15H
host)
End
address
00H
C9H
Write
Data
16H
POINT
(1) Start address/end address specification conditions
Specify addresses so that the start address is the same or less than the end address.
Error response occurs in the following cases:
• The address to specify has the start address greater than the end address.
• Either of the start address or end address exceeds the device range that can be specified.
(2) Address specifying crossing over different devices
The start address and end address can be specified crossing over different devices.
3 - 40
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
1
PREPARATORY
PROCEDURES FOR
MONITORING
(5) Read clock data (6) command (w/out station No.), read clock data (G) command (w/station No.)
The following shows an example of reading the clock data of GOT at station No.27.
(Assuming that the clock data of GOT has been set to "2009, October 1, 18:46:49, Thursday".)
Time display
Item
THU
2
MICROCOMPUTER
CONNECTION
(SERIAL)
2009/10/01 18:46:49
Message format
(format 3: GOT-F900 Series microcomputer connection (ASCII))
Command Station No.
2
7
32H
37H
(H)
(L)
Request message
(host
GOT)
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
G
47H
(format 4: GOT-F900 Series microcomputer connection (Binary))
Com- Station
mand No.
G
4
1BH
Year data Month data
(GOT
host)
Day-ofHour data Minute data Second data week data
Day data
0
9
1
0
0
1
1
8
4
6
4
9
0
4
30H
39H
31H
30H
30H
31H
31H
38H
34H
36H
34H
39H
30H
34H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
5
(format 4: GOT-F900 Series microcomputer connection (Binary))
MODBUS(R)/TCP
CONNECTION
Response message
during normal
communication
MODBUS(R)/RTU
CONNECTION
(format 3: GOT-F900 Series microcomputer connection (ASCII))
Year Month Day Hour Minute Second Day-ofdata data data data data data week data
09H
0AH
01H
12H
2EH
31H
04H
Response message
during faulty
communication
NAK
(GOT
15H
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
host)
CONNECTION TO
SOUND OUTPUT
UNIT
6
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 41
(6) Set clock data (5) command (w/out station No.), set clock data (F) command (w/station No.)
The following shows an example of setting clock data of GOT at station No.27.
(Assuming the clock data of GOT is to be set to "2009, October 1, 18:46:49 Thursday".)
Time display
2009/10/01 18:46:49
THU
After execution
Item
Message format
(format 3: GOT-F900 Series microcomputer connection (ASCII))
Com- Station No.
mand
Year data
Month data
Day Data
Hour data Minute data
Second
data
Day-ofweek data
F
2
7
0
9
1
0
0
1
1
8
4
6
4
9
0
4
46H
32H
37H
30H
39H
31H
30H
30H
31H
31H
38H
34H
36H
34H
39H
30H
34H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Request message
(host
GOT)
(format 4: GOT-F900 Series microcomputer connection (Binary))
Com- Station Year Month Day Hour Minute Second Day-ofmand No.
data data data data data data week data
F
1BH
09H
0AH
01H
Response message
during normal
communication
ACK
(GOT
06H
host)
Response message
during faulty
communication
NAK
(GOT
15H
host)
12H
2EH
31H
04H
POINT
When a wrong day of the week has been set by the clock data setting command
If a wrong day of the week is set by the clock data setting commands, the clock data will differ from the time
displayed on the utility.
Example: When October 1, 2009 (Tuesday) is set by the clock data setting command (the actual day of the week is
Thursday), Thursday (THU) will be displayed on the utility time display.
3 - 42
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
The following shows an example of an interrupt output when data are written to the interrupt output devices (D13
and D14).
(Assuming that "3139H" is written to D13 and "AA55H" to D14.)
Example: When the number of interrupt data bytes is 2
2
3139H
MICROCOMPUTER
CONNECTION
(SERIAL)
D13
Interrupt
Interrupt output
Output Output
value 1 value 2
Item
3
39H
MICROCOMPUTER
CONNECTION
(ETHERNET)
31H
Message format
(1) When [Interrupt Data Byte] in "Communication Detail Settings" is set to "1 byte"
4
MODBUS(R)/RTU
CONNECTION
Output
value 1
39H
(2) When [Interrupt Data Byte] in "Communication Detail Settings" is set to "2 byte"
Output Output
value 1 value 2
Interrupt output
5
host)
39H
MODBUS(R)/TCP
CONNECTION
31H
(3) When [Interrupt Data Byte] in "Communication Detail Settings" is set to "4 byte"
Output Output Output Output
value 1 value 2 value 3 value 4
55H
31H
6
39H
CONNECTION TO
SOUND OUTPUT
UNIT
AAH
POINT
Interrupt output
7
CONNECTION TO
EXTERNAL I/O
DEVICE
• To disable the interrupt output, turn ON SM52 (interrupt code output disable flag). (
3.3.6 SM devices)
• To enable the interrupt output, set 8 bits to the data length at "Communication Detail Settings".
(
3.5.1 Setting communication interface (Communication settings))
• When "7 bits" is set, the MSB (8th bit) is ignored.(Example: FFH 7FH)
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(GOT
PREPARATORY
PROCEDURES FOR
MONITORING
1
(7) In the case of interrupt outputs
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 43
 Error code list
When faulty, the error code is stored in SD2.
For details of error code stored in SD2, the error contents, cause and measures, refer to the following:
3.3.5 ■ Details and actions for errors (error codes) stored into SD2
When an error other than those to be stored in SD2 occurs, at faulty, only the NAK response is executed.
 Precautions
(1) Batch reading/writing crossing over different devices
When using the batch read (0, A) or batch write (1, B) command, do not batch read/write crossing over different
devices.
This will cause an error response.
3 - 44
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
1
Formats 5(Digital Electronics Corporation's memory link method)
PREPARATORY
PROCEDURES FOR
MONITORING
3.4.5
 Basic format of data communication
This is the same format as the protocol of the Digital Electronics Corporation's memory link method.
For details of the basic format of data communication, refer to the following manual:
The connection manual of the device manufactured by Digital Electronics Corporation
This section describes items whose settings differ from the protocols of the Digital Electronics Corporation's memory
link method and dedicated commands for a microcomputer connection of GOT.
ESC Command
Data length
B
Number
of points
00H
00H
R
00H 00H
00H
00H
00H
00H
06H
1BH
52H
64H
4
02H
MODBUS(R)/RTU
CONNECTION
42H
Address
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
Example:Request message for the batch read in word units (R) command in format 5
(Digital Electronics Corporation's memory link method)
MICROCOMPUTER
CONNECTION
(SERIAL)
2
 Details of data items in message format
POINT
5
Data code during communication
MODBUS(R)/TCP
CONNECTION
Communication is performed in ASCII code.
(1) Command
Specifies the contents to access from the host to GOT.
The command is converted to a 1-digit ASCII code (Hex) and transmitted.
For details of the commands that can be used, refer to the following.
Specifies the head No. of the device data to be read/written.
The address notated in hexadecimal is converted to a 4-digit ASCII code (Hex) and transmitted from the upper
digit.
For details of the device range that can be accessed, refer to the following.
3.3 Device Data Area
(3) Number of points
Specifies the number of device data to be read/written. (Setting range: 1 to 40H)
The address notated in hexadecimal is converted to a 4-digit ASCII code (Hex) and transmitted from the upper
digit.
(4) Error code
This is the response message at faulty communication appended with error contents.
The address notated in hexadecimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper
digit.
For details of error codes generated in format 5 (Digital Electronics Corporation's memory link method), refer to
the following:
■ Error code list
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 45
7
CONNECTION TO
EXTERNAL I/O
DEVICE
(2) Address
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
3.4.2 List of commands
CONNECTION TO
SOUND OUTPUT
UNIT
6
POINT
When connecting a microcomputer, etc. that uses the protocol of the Digital Electronics Corporation's memory link
method with the GOT
When connecting a microcomputer, etc. that uses the protocol of the Digital Electronics Corporation's memory link
method with the GOT, correct the commands to be used and the device ranges to match the specifications of the
GOT.
3 - 46
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
The following shows the message format of the dedicated commands for a microcomputer connection of GOT.
(1) Batch read in word units (R) command
The following shows an example of reading the two points of the virtual devices D100 and D101.
(Assuming D100=0102H, D101=0304H are stored.)
PREPARATORY
PROCEDURES FOR
MONITORING
1
 Message Formats
0102H
D101
0304H
Message format
B
42H
Response message
during normal
communication
(GOT
00H
00H
00H
00H
06H
1BH
52H
b
42H
00H
ESC Command
Data length
host)
00H
R
00H 00H
64H
02H
Address
Number
of points
01H
03H
4
MODBUS(R)/RTU
CONNECTION
GOT)
Address
ESC Command
Data length
Request message
(host
3
Number
of points
MICROCOMPUTER
CONNECTION
(ETHERNET)
Item
D100
MICROCOMPUTER
CONNECTION
(SERIAL)
2
A
00H 00H
00H
00H
00H
06H
00H
1BH
41H
02H
04H
5
(2) Batch write in word units (WD) command
D100
0000H
D100
0064H
D101
0000H
D101
0065H
After execution
Item
Message format
ESC Command
Data length
Request message
B
42H
Response message
during normal
communication
(GOT
host)
Data 1
Data 2
7
W
00H 00H
00H
00H
00H
00H
0AH
1BH
57H
00H
64H
00H
Data length
02H
00H
64H
00H
65H
CONNECTION TO
EXTERNAL I/O
DEVICE
GOT)
Number
of points
Address
ACK
b
42H
00H 00H
00H
00H
00H
00H
06H
8
06H
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(host
6
CONNECTION TO
SOUND OUTPUT
UNIT
Before execution
MODBUS(R)/TCP
CONNECTION
(a) When writing to a word device
The following shows as example of writing "0064H"and "0065H"to virtual devices D100 and D101.
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 47
(3) In the case of interrupt outputs
The following shows an example of an interrupt output when data are written to the interrupt output devices
(D13).
(Assuming that "31H" is written to D13.)
Example: When the number of interrupt data bytes is 1
D13
31H
Interrupt
Interrupt output
Output
value 1
31H
Item
Message format
When [Interrupt Data Byte] in "Communication Detail Settings" is set to "1 byte"
Output
value 1
Interrupt output
(GOT
host)
31H
POINT
Interrupt output
• To disable the interrupt output, turn ON SM52 (interrupt code output disable flag).
(
3.3.6 SM devices)
• To enable the interrupt output, set 8 bits to the data length at "Communication Detail Settings".
(
3.5.1 Setting communication interface (Communication settings))
• When "7 bits" is set, the MSB (8th bit) is ignored. (Example: FFH 7FH)
3 - 48
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
In the case of format 5 (Digital Electronics Corporation's memory link method), the details (error code) of the error are
appended to the response message during faulty communication.
The following shows error code, error contents, cause, and measures.
Action
12H
Message length error
The upper limit of the data length that can be received by
the GOT has been exceeded.
FAH
Address error
The start address of the read/write device is out of range.
FBH
Exceeded number of points error
The read/write range exceeded the device range.
2
• Review the contents of the message to transmit.
• Check the commands in the message.
(
3.4.2 List of commands)
• Review the contents of the message to transmit.
• Check whether the non-existent data is set (e.g. setting "07" at the day of
the week) as clock data.
• Review the contents of the message to transmit.
• Check the devices that can be used and the device ranges.
(
3.3 Device Data Area)
FCH
Message format error
The format of the received message has error.
• Check the settings of "Communication Detail Settings".
• Review the contents of the message to transmit.
FFH
Timeout error
There is no response from the GOT, or the station of the
specified address does not exist.
• Check the communication cable and communication module attachment.
• Check the settings of "Communication Detail Settings".
• Review the contents of the message to transmit.
 Precautions
(1) Batch reading/writing crossing over different devices
When using the batch read (R) or batch write (W) command, do not batch read/write crossing over the different
devices.
This will cause an error response.
(2) Storage order for 32-bit data
To use the program of Digital Electronics Corporation's memory link method with [32bit Order] setting to
GOT1000 series, set [HL Order] to [32bit Order] for [Communication Detail Settings] when 32-bit data is set for
GOT-A900 series.
With setting [LH Order], the order of upper bits and lower bits are reversed when the GOT displays and writes
32-bit data.
MICROCOMPUTER
CONNECTION
(SERIAL)
Command error
An unsupported command was used.
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
10H
4
MODBUS(R)/RTU
CONNECTION
Description
5
MODBUS(R)/TCP
CONNECTION
Error code
PREPARATORY
PROCEDURES FOR
MONITORING
1
 Error code list
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 49
3.4.6
Formats 6, 7 (4E frame)
 Basic format of data communication
This is the same message format as when communication is performed using the MC protocol (4E frame) of the Q/
QnA Series serial communication module.
For details of the basic format of data communication, refer to the following manual:
MELSEC-Q/L MELSEC Communication Protocol Reference Manual
This section describes items whose settings differ from the MC protocol of the Q/QnA Series serial communication
module, and the dedicated commands for a GOT microcomputer connection.
Example: Request message for the batch read (0401) command in word units
Device name : D
Head device : 100
Device points : 2
Communication setting of GOT side : Network No.=1, PLC No.=1
(Format 6 (4E frame (ASCII))
Serial No.
Request type
5
4
35H
34H
(H)
(L)
0
0
0
0
30H
30H
30H
30H
(H)
(L)
(H)
(L)
0
Fixed value
0
0
0
30H
30H
30H
(H)
(L)
(H)
Network
No.
PLC No.
0
0
0
0
30H
30H
30H
30H
31H
30H
(L)
(H)
–
(H)
(L)
(H)
1
Request destination
module I/O No.
Request destination
module station No.
0
0
0
31H
30H
30H
30H
30H
30H
30H
(L)
(H)
–
–
(L)
(H)
(L)
1
0
0
0
Following
*1
*1
Request data length
CPU monitoring timer
Command
1)
0
0
1
8
0
0
0
0
0
4
0
1
30H
30H
31H
38H
30H
30H
30H
30H
30H
34H
30H
31H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
Data length target range
Character A section
Device
code
Sub-command
1)
Device points
Head Device
0
0
0
0
D
*
0
0
0
1
0
0
0
0
0
2
30H
30H
30H
30H
44H
2AH
30H
30H
30H
31H
30H
30H
30H
30H
30H
32H
(H)
–
–
(L)
(H)
(L)
(H)
–
–
–
–
(L)
(H)
–
–
(L)
Data length target range
(format 7:4E frame (Binary))
Request
type
54H
00H
Serial No.
00H 00H
Fixed
value
00H
00H
Network PLC
No.
No.
01H 01H
Request
destination
module I/O No.
00H
00H
Request
destination Request
module data length
station No.
00H 0CH
00H
CPU
monitoring
timer
00H 00H
Command
Subcommand
Head Device
01H
00H 00H
64H 00H 00H
04H
Data length target range
 Details of data items in message format
POINT
Data code during communication
Communication of format 6 is performed in ASCII code.
Communication of the format 7 is performed in Binary code.
3 - 50
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
Device Device points
code
A8H
02H
00H
1
Contents
Fixed value
Response message: ASCII "D400" (Fixed value)
Command message: 54H (Upper digit) (Fixed value)
2
Response message: D4H (Upper digit) (Fixed value)
Arbitrary number for recognition of the message appended at the microcomputer side. GOT sends the response message appending
this Serial No.
Should be ASCII "0000".
Should be "0000H".
Set the same number as the network No. set in the GOT.
For setting method of "Communication Detail Settings", refer to the following.
3
3.5.1 Setting communication interface (Communication settings)
Transmit the data converted to a 2-digit ASCII code from the upper
digit.
Transmit the data converted to a 2-digit binary code.
MICROCOMPUTER
CONNECTION
(ETHERNET)
Network No.
Set the same number as the PLC No. set in the GOT.
For setting method of "Communication Detail Settings", refer to the following.
PLC No.
3.5.1 Setting communication interface (Communication settings)
Transmit the data converted to a 2-digit ASCII code from the upper
digit.
Request destination
module I/O No.
Ignore GOT.
Request destination
module station No.
Ignore GOT.
Transmit the data converted to a 2-digit binary code.
4
Number of bytes from the start of CPU monitoring timer to the last request data.
Request data length
Response data
length
CPU monitoring
timer
Transmit the data converted to a 4-digit ASCII code from the upper
digit.
Transmit the data converted to a 4-digit binary code from the lower
two digits.
Appended to the response message from the microcomputer side.
Number of bytes from the start of end code to the last request data.
Transmit the data converted to a 4-digit ASCII code from the upper
digit.
Transmit the data converted to a 4-digit binary code from the lower
two digits.
Ignore GOT.
Specifies the access contents from the microcomputer side to GOT. For details of the commands that can be used, refer to the following.
Command,
Sub-command
3.4.2 List of commands
Transmit the command and sub-command converted to a 4-digit
ASCII code, from the upper digit.
Transmit the data converted to a 4-digit binary code from the lower
two digits.
Specifies the code by which the device data to be read/written is recognized.
For details of the device range that can be accessed, refer to the following.
3.3 Device Data Area
Device code
Device name
Device code
Transmit the 2-digit binary code corresponding to the following
device codes.
Device name
Device code
90H
M
M*
M
SM
SM
SM
91H
L
L*
L
92H
A8H
D
D*
D
SD
SD
SD
A9H
R
R*
R
AFH
5
6
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Transmit the 2-digit ASCII code corresponding to the following
device codes.
MODBUS(R)/RTU
CONNECTION
Indicates it is a response message.
Command message: ASCII "5400" (Fixed value)
MODBUS(R)/TCP
CONNECTION
Response type
(GOT side)
Format 7
CONNECTION TO
SOUND OUTPUT
UNIT
Indicates it is a command message.
MICROCOMPUTER
CONNECTION
(SERIAL)
Format 6
Request type
(Microcomputer
side)
8
(Continued to next page)
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 51
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Data item name
Serial No.
PREPARATORY
PROCEDURES FOR
MONITORING
The following table shows the contents of the data items.
(From previous page)
Contents
Data item name
Format 6
Format 7
Specifies the head No. of the device data to be read/written.
For details of the device range that can be accessed, refer to the following.
3.3 Device Data Area
Head device
Transmit the data notated in decimal converted to a 6-digit
ASCII code, from the upper digit.
Device points
Transmit the data converted to a 6-digit binary code from the lower
two digits.
Specifies the number of device data to be read/written. (Setting range: 1 to 40H)
<When using random read/write command>
When setting multiple bit accesses, word accesses or double word accesses, limit the total number of access points to within 64 points.
<When using multiple block batch read/write commands>
When setting multiple blocks, limit the total number of points of all blocks to within 64 points.
Transmit the data notated in decimal converted to a 4-digit
ASCII code, from the upper digit.
Transmit the data converted to a 4-digit binary code from the lower
two digits.
Specifies year, month, day, hour, minute, second, and day of the week to be read/set to the GOT clock data.
Year, month, day,
hour,
minute, second and
day
of the week data
End code
(Microcomputer
side)
■ Message format (1) Read clock data (1901) command
■ Message format (2) Set clock data (0901) command
Transmit the data notated in decimal converted to a 2-digit
ASCII code, from the upper digit.
Transmit the data converted to a 2-digit binary code.
Appended to the response message from the microcomputer side. If an error occurs at the microcomputer side, the error code is
displayed.
■ Error code list
Transmit the data notated in hexadecimal converted to a 4-digit
ASCII code, from the upper digit.
Transmit the data converted to a 4-digit binary code from the lower
two digits.
POINT
When connecting a microcomputer, etc. that uses the MC protocol of the Q/QnA series serial communication
module with the GOT
When connecting a microcomputer, etc. that uses the MC protocol of the Q/QnA series serial communication
module with the GOT, correct the commands to be used and the device ranges to match the GOT specifications.
3 - 52
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
The following shows the message format of the dedicated commands for a microcomputer connection of GOT.
(1) Read clock data (1901) command
The following shows an example of reading the clock data of GOT.
(Assuming that the clock data of GOT has been set to "2009, October 1, 18:46:49, Thursday".)
2
THU
Message format
(format 6:4E frame (ASCII))
Serial No.
3
Network
No.
Fixed value
PLC No.
5
4
0
0
0
0
0
0
0
0
0
0
0
1
0
1
35H
34H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
31H
30H
31H
(H)
–
–
(L)
(H)
–
–
(L)
(H)
–
–
(L)
(H)
(L)
(H)
(L)
MICROCOMPUTER
CONNECTION
(ETHERNET)
Request type
Following
*1
*1
Request destination
module station No.
4
CPU monitoring timer
Request data length
0
0
0
0
0
0
0
0
0
C
0
0
0
0
30H
30H
30H
30H
30H
30H
30H
30H
30H
43H
30H
30H
30H
30H
(H)
–
–
(L)
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
1)
MODBUS(R)/RTU
CONNECTION
Request destination
module I/O No.
Character A section
1)
1
9
0
1
0
0
0
0
31H
39H
30H
31H
30H
30H
30H
30H
(H)
–
–
(L)
(H)
–
–
(L)
Network PLC Request destination
No.
module I/O No.
No.
Request
destination
module
station No.
MODBUS(R)/TCP
CONNECTION
GOT)
(format 7:4E frame (Binary))
54H
00H
Serial No. Fixed value
00H
00H
00H
00H
01H
01H
00H
00H
00H
Request
data length
06H
00H
6
Following
*1
CONNECTION TO
SOUND OUTPUT
UNIT
Request
type
Data length target range
*1
CPU monitoring
Command
timer
00H
00H
01H
19H
Subcommand
00H
7
00H
(Continued to next page)
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(host
5
Sub-command
Command
Request message
CONNECTION TO
EXTERNAL I/O
DEVICE
2009/10/01 18:46:49
MICROCOMPUTER
CONNECTION
(SERIAL)
Time display
Item
PREPARATORY
PROCEDURES FOR
MONITORING
1
 Message format
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 53
(From previous page)
Item
Message format
(format 6:4E frame (ASCII))
Response type
D
4
0
44H
34H
30H
(H)
–
–
Serial No.
0
0
0
30H
30H
30H
30H
(L)
(H)
–
–
0
Network
No.
Fixed value
PLC No.
0
0
0
30H
30H
30H
30H
30H
30H
31H
30H
31H
(L)
(H)
–
–
(L)
(H)
(L)
(H)
(L)
0
0
1
0
1
0
Following
*1
*1
Request destination
module I/O No.
Request destination
module station No.
End code
Response data length
0
0
0
0
0
0
0
0
1
2
0
0
0
0
30H
30H
30H
30H
30H
30H
30H
30H
31H
32H
30H
30H
30H
30H
(H)
–
–
(L)
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
1)
Character B section
Response message
during normal
communication
(GOT
host)
Year data Month data
1)
Day data
Second
data
Hour data Minute data
Day-ofweek data
0
9
1
0
0
1
1
8
4
6
4
9
0
4
30H
39H
31H
30H
30H
31H
31H
38H
34H
36H
34H
39H
30H
34H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(format 7:4E frame (Binary))
Request
type
D4H
00H
Serial No. Fixed value
00H
00H
00H
00H
Network PLC Request destination
No.
No.
module I/O No.
01H
01H
00H
00H
Request
destination
module
station No.
00H
Response
data length
09H
00H
Following
*1
Data length target range
*1
End code
00H
00H
Year Month Day Hour Minute Second Day-ofdata data data data data data week data
09H
0AH
01H
12H
2EH
31H
04H
(Continued to next page)
3 - 54
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
Message format
(format 6:4E frame (ASCII))
D
4
0
44H
34H
30H
(H)
–
–
Serial No.
0
0
0
30H
30H
30H
30H
(L)
(H)
–
–
0
Network
No.
Fixed value
PLC No.
0
0
0
30H
30H
30H
30H
30H
30H
31H
30H
31H
(L)
(H)
–
–
(L)
(H)
(L)
(H)
(L)
0
0
0
1
0
1
Following
*1
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Response type
*1
Request destination
module I/O No.
0
0
0
0
0
0
0
0
1
6
0
0
5
6
30H
30H
30H
30H
30H
30H
30H
31H
36H
30H
30H
35H
36H
(L)
(H)
–
–
(L)
Network
No.
(L)
PLC No.
(H)
(L)
(H)
–
Request destination
module I/O No.
–
Request destination
module station No.
Command
Sub-command
0
0
0
0
0
0
0
0
0
0
1
9
0
1
0
0
0
0
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
31H
39H
30H
31H
30H
30H
30H
30H
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
(format 7:4E frame (Binary))
00H
00H
00H
00H
00H
01H
01H
00H
00H
Request
destination
module
station No.
00H
Response
data length
0BH
00H
Following
*1
5
MODBUS(R)/TCP
CONNECTION
D4H
PLC Request destination
Serial No. Fixed value Network
module I/O No.
No.
No.
Data length target range
*1
End code
56H
00H
Network PLC Request destination
module I/O No.
No.
No.
00H
00H
00H
00H
Request
destination
module
station No.
00H
Command
Subcommand
01H
00H
19H
6
00H
CONNECTION TO
SOUND OUTPUT
UNIT
Request
type
4
MODBUS(R)/RTU
CONNECTION
1)
–
7
CONNECTION TO
EXTERNAL I/O
DEVICE
host)
–
3
1)
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(GOT
End code
Response data length
30H
(H)
Response message
during faulty
communication
Request destination
module station No.
MICROCOMPUTER
CONNECTION
(ETHERNET)
Item
1
PREPARATORY
PROCEDURES FOR
MONITORING
(From previous page)
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 55
(2) Set clock data (0901) command
The following shows an example of setting the clock data of GOT.
(Assuming the clock data of GOT is to be set to "2009, October 1, 18:46:49 Thursday".)
Time display
2009/10/01 18:46:49
THU
After execution
Item
Message format
(format 6:4E frame (ASCII))
Response type
Serial No.
Network
No.
Fixed value
PLC No.
5
4
0
0
0
0
0
0
0
0
0
0
0
1
0
1
35H
34H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
31H
30H
31H
(H)
–
–
(L)
(H)
–
–
(L)
(H)
–
–
(L)
(H)
(L)
(H)
(L)
Following
*1
*1
Request destination
module I/O No.
Request destination
module station No.
Command
CPU monitoring timer
Request data length
0
0
0
0
0
0
0
0
1
A
0
0
0
0
0
9
0
1
30H
30H
30H
30H
30H
30H
30H
30H
31H
41H
30H
30H
30H
30H
31H
39H
30H
31H
(H)
–
–
(L)
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
(H)
–
–
(L)
1)
Character C section
Request message
(host
GOT)
Year data Month data
Sub-command
1)
Day data
Hour data Minute data
Second
data
Day-ofweek data
0
0
0
0
0
9
1
0
0
1
1
8
4
6
4
9
0
4
30H
30H
30H
30H
30H
39H
31H
30H
30H
31H
31H
38H
34H
36H
34H
39H
30H
34H
(H)
–
–
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(format 7:4E frame (Binary))
Request
type
Serial No. Fixed value
54H
00H
00H
00H
00H
00H
Network PLC Request destination
No.
module I/O No.
No.
01H
01H
00H
00H
Request
destination
module
station No.
00H
Request
data length
0DH
00H
Following
*1
Data length target range
*1
CPU monitoring
Command
timer
00H
00H
01H
09H
Year Month Day Hour Minute Second Day-ofSubcommand data data data data data data week data
00H
00H
09H
0AH
01H
12H
2EH
31H
04H
(Continued to next page)
3 - 56
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
Message format
(format 6:4E frame (ASCII))
D
4
0
44H
34H
30H
(H)
–
–
Serial No.
0
0
0
30H
30H
30H
30H
(L)
(H)
–
–
0
Network
No.
Fixed value
PLC No.
0
0
0
30H
30H
30H
30H
30H
30H
31H
30H
31H
(L)
(H)
–
–
(L)
(H)
(L)
(H)
(L)
0
0
0
1
1
0
Following
*1
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Response type
*1
End code
0
0
0
0
0
0
0
0
0
4
0
0
0
0
30H
30H
30H
30H
30H
30H
30H
30H
30H
34H
30H
30H
30H
30H
(L)
(H)
–
–
(L)
(H)
–
–
(L)
(H)
(L)
(H)
–
–
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
Response data length
(format 7:4E frame (Binary))
Data length
target range
D4H
00H
Serial No. Fixed value
00H
00H
00H
00H
Network PLC Request destination
No. No.
module I/O No.
01H
01H
00H
00H
Request
destination
module
station No.
00H
Response
data length
02H
00H
End code
00H
4
00H
(Continued to next page)
5
MODBUS(R)/TCP
CONNECTION
Request
type
6
CONNECTION TO
SOUND OUTPUT
UNIT
host)
Request destination
module station No.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
(GOT
Request destination
module I/O No.
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Response message
during normal
communication
MODBUS(R)/RTU
CONNECTION
Item
1
PREPARATORY
PROCEDURES FOR
MONITORING
(From previous page)
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 57
(From previous page)
Item
Message format
(format 6:4E frame (ASCII))
Response type
D
4
0
44H
34H
30H
(H)
–
–
Serial No.
0
0
0
30H
30H
30H
30H
(L)
(H)
–
–
0
Network
No.
Fixed value
PLC No.
0
0
0
30H
30H
30H
30H
30H
30H
31H
30H
31H
(L)
(H)
–
–
(L)
(H)
(L)
(H)
(L)
0
0
1
0
1
0
Following
*1
*1
Request destination
module I/O No.
(GOT
1)
host)
End code
Response data length
0
0
0
0
0
0
0
0
1
6
0
0
5
6
30H
30H
30H
30H
30H
30H
30H
30H
31H
36H
30H
30H
35H
36H
(H)
–
–
(L)
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
Network
No.
Response message
during faulty
communication
Request destination
module station No.
Request destination
module I/O No.
PLC No.
Request destination
module station No.
1)
Command
Sub-command
0
0
0
0
0
0
0
0
0
0
0
9
0
1
0
0
0
0
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
39H
30H
31H
30H
30H
30H
30H
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
(format 7:4E frame (Binary))
Request
type
Serial No. Fixed value Network PLC
No. No.
Request
Request destination destination
module
module I/O No.
station No.
Response
data length
Following*1
D4H
00H
00H
00H
00H
00H
01H
01H
00H
00H
00H
0BH
0H
Data length target range
*1
End code
56H
00H
Network PLC
No. No.
00H
00H
Request
Request destination destination
module
module I/O No.
station No.
00H
00H
00H
Command
Subcommand
01H
00H
09H
00H
POINT
When a wrong day of the week has been set by the clock data setting command
If a wrong day of the week is set by the clock data setting commands, the clock data will differ from the time
displayed on the utility.
Example: When October 1, 2009 (Tuesday) is set by the clock data setting command (the actual day of the week is
Thursday), Thursday (THU) will be displayed on the utility time display.
3 - 58
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
Description
Action
Device point error
The specification of device range to read/write has error.
0050H
Request (command)/Response (response) type code error
Code other than the specified value is set for command/
response type.
0056H
Device error
A non-existent device has been specified.
3.3 Device Data Area)
• Check the command/response type set in the microcomputer and correct
it.
• Check the devices that can be used and the device ranges.
(
Device point error
• The command number of points specification from the
microcomputer exceeds the maximum number of points
processed at each process (number of points processed in
one communication).
• The start address (head device number) to specified
number of points exceeds the maximum address (device
number, step number) for each process.
When reading data which the command bit length is longer
than the specification, the set number of write data points
differs from the specified number of points value.
0058H
(
3.3 Device Data Area)
• Correct the specified number of points, or the start address (device
number).
(
2
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
0057H
• Check the specified head device and number of points, and correct it.
3.3 Device Data Area)
• Check the command data length and set the data again.
4
• The command start address (head device number, start
step number) specification from the microcomputer
exceeds the range that can be specified.
• Value outside the GOT parameter setting range is specified
in the microcomputer program and file register (R) reading/
writing.
• Correct the values to values that can be specified in each process.
• Word device is specified in the command for bit device.
• In the command for word device, a bit device start number
is specified in other than hexadecimal.
• Correct the command or the specified device.
00A1H
Request content cannot be analyzed because the text length
or request data length is too short.
• Review the text length or the head request data length.
00A2H
Request cannot be processed.
• Correct the request content and command.
C0D6H
The specification of network No. and station No. have error.
• Review the network No., station No. specification method.
MODBUS(R)/RTU
CONNECTION
0002H
5
MODBUS(R)/TCP
CONNECTION
Error code
MICROCOMPUTER
CONNECTION
(SERIAL)
The following shows error code, error contents, cause, and measures.
PREPARATORY
PROCEDURES FOR
MONITORING
1
 Error code list
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 59
3.4.7
Formats 8, 9 (QnA compatible 3E frame)
 Basic format of data communication
This is the same message format as when communication is performed using the MC protocol (QnA compatible 3E
frame) of the Q/QnA Series serial communication module.
For details of the basic format of data communication, refer to the following manual:
MELSEC-Q/L MELSEC Communication Protocol Reference Manual
This section describes items whose settings differ from the MC protocol of the Q/QnA Series serial communication
module, and the dedicated commands for a GOT microcomputer connection.
Example: Request message for the batch read (0401) command in word units
Device name : D
Head device : 100
Device points : 2
Communication setting of GOT side : Network No.=1, PLC No.=1
(Format 8: QnA compatible 3E frame (ASCII))
Network
No.
Subheader
0
5
0
0
1
0
1
0
Request
destination
module station No.
Request destination
module I/O No.
PLC No.
0
0
0
0
0
Request data length
0
0
0
Following
*1
8
1
35H
30H
30H
30H
30H
31H
30H
31H
30H
30H
30H
30H
30H
30H
30H
30H
31H
38H
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Character A section
*1
CPU monitoring timer
Device
code
Sub-command
Command
Start Device
Device points
0
0
0
0
0
4
0
1
0
0
0
0
D
*
0
0
0
1
0
0
0
0
0
2
30H
30H
30H
30H
30H
34H
30H
31H
30H
30H
30H
30H
44H
2AH
30H
30H
30H
31H
30H
30H
30H
30H
30H
32H
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
–
–
(L)
(H)
(L)
(H)
–
–
–
–
(L)
(H)
–
–
(L)
Data length target data
(Format 9: QnA compatible 3E frame (Binary))
Subheader
50H
00H
Network
No.
PLC
No.
01H 01H
Request
Request
Request
destination
CPU
destination
module
module I/O No. station No. data length monitoring timer
00H
00H
00H 0CH
00H
00H 00H
Command
Subcommand
Start Device
01H
00H 00H
64H 00H 00H
04H
Data length target data
 Details of data items in message format
POINT
Data code during communication
Communication of format 8 is performed in ASCII code.
Communication of the format 9 is performed in Binary code.
3 - 60
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
Device
Device points
code
A8H
02H
00H
1
PREPARATORY
PROCEDURES FOR
MONITORING
The following table shows the contents of the data items.
Contents
Format 8
Indicates it is a command message.
Subheader
(GOT side)
Indicates it is a response message.
Format 9
Command message: ASCII "5000" (Fixed value)
Response message: ASCII "D000" (Fixed value)
Command message: 50H (Upper digit) (Fixed value)
2
Response message: D0H (Upper digit) (Fixed value)
MICROCOMPUTER
CONNECTION
(SERIAL)
Subheader
(Microcomputer
side)
Set the same number as the network No. set in the GOT.
For setting method of "Communication Detail Settings", refer to the following.
3.5.1 Setting communication interface (Communication settings)
Transmit the data converted to a 2-digit ASCII code from the upper
digit.
Transmit the data converted to a 2-digit binary code.
3
Set the same number as the PLC No. set in the GOT.
For setting method of "Communication Detail Settings", refer to the following.
Transmit the data converted to a 2-digit ASCII code from the upper
digit.
Ignore GOT.
Request destination
module station No.
Ignore GOT.
Transmit the data converted to a 2-digit binary code.
4
Number of bytes from the start of CPU monitoring timer to the last request data.
Request data length
Response data
length
CPU monitoring
timer
Transmit the data converted to a 4-digit ASCII code from the upper
digit.
Transmit the data converted to a 4-digit binary code from the lower
two digits.
Appended to the response message from the microcomputer side.
Number of bytes from the start of end code to the last request data.
Transmit the data converted to a 4-digit ASCII code from the upper
digit.
Transmit the data converted to a 4-digit binary code from the lower
two digits.
Ignore GOT.
Specifies the access contents from the microcomputer side to GOT. For details of the commands that can be used, refer to the following.
Command,
Sub-command
3.4.2 List of commands
Transmit the command and sub-command converted to a 4-digit
ASCII code, from the upper digit.
Transmit the data converted to a 4-digit binary code from the lower
two digits.
Specifies the code by which the device data to be read/written is recognized.
For details of the device range that can be accessed, refer to the following.
3.3 Device Data Area
Transmit the 2-digit ASCII code corresponding to the following
device codes.
Device name
Device code
Device name
Device code
M
M*
M
90H
SM
SM
SM
91H
L
L*
L
92H
A8H
D
D*
D
SD
SD
SD
A9H
R
R*
R
AFH
8
3.3 Device Data Area
Transmit the data notated in decimal converted to a 6-digit
ASCII code, from the upper digit.
6
7
Specifies the head No. of the device data to be read/written.
For details of the device range that can be accessed, refer to the following.
Head device
5
CONNECTION TO
EXTERNAL I/O
DEVICE
Device code
Transmit the 2-digit binary code corresponding to the following
device codes.
MODBUS(R)/RTU
CONNECTION
Request destination
module I/O No.
MICROCOMPUTER
CONNECTION
(ETHERNET)
3.5.1 Setting communication interface (Communication settings)
MODBUS(R)/TCP
CONNECTION
PLC No.
CONNECTION TO
SOUND OUTPUT
UNIT
Network No.
Transmit the data converted to a 6-digit binary code from the lower
two digits.
(Continued to next page)
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 61
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Data item name
(From previous page)
Contents
Data item name
Device points
Format 8
Transmit the data notated in decimal converted to a 4-digit
ASCII code, from the upper digit.
Year, month, day,
hour,
minute, second and
day
of the week data
End code
(Microcomputer
side)
Format 9
Specifies the number of device data to be read/written. (Setting range: 1 to 40H)
<When using random read/write command>
When setting multiple bit accesses, word accesses or double word accesses, limit the total number of access points to within 64 points.
<When using multiple block batch read/write commands>
When setting multiple blocks, limit the total number of points of all blocks to within 64 points.
Transmit the data converted to a 4-digit binary code from the lower
two digits.
Specifies year, month, day, hour, minute, second, and day of the week to be read/set to the GOT clock data.
■ Message format (1) Read clock data (1901) command
■ Message format (2) Set clock data (0901) command
Transmit the data notated in decimal converted to a 2-digit
ASCII code, from the upper digit.
Transmit the data converted to a 2-digit binary code.
Appended to the response message from the microcomputer side. If an error occurs at the microcomputer side, the error code is
displayed.
■ Error code list
Transmit the data notated in hexadecimal converted to a 4-digit
ASCII code, from the upper digit.
Transmit the data converted to a 4-digit binary code from the lower
two digits.
POINT
When connecting a microcomputer, etc. that uses the MC protocol of the Q/QnA series serial communication
module with the GOT
When connecting a microcomputer, etc. that uses the MC protocol of the Q/QnA series serial communication
module with the GOT, correct the commands to be used and the device ranges to match the GOT specifications.
3 - 62
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
The following shows the message format of the dedicated commands for a microcomputer connection of GOT.
(1) Read clock data (1901) command
The following shows an example of reading the clock data of GOT.
(Assuming that the clock data of GOT has been set to "2009, October 1, 18:46:49, Thursday".)
PREPARATORY
PROCEDURES FOR
MONITORING
1
 Message format
2
2009/10/01 18:46:49
Item
MICROCOMPUTER
CONNECTION
(SERIAL)
Time display
THU
Message format
(format 8:QnA compatible 3E frame (ASCII))
0
PLC No.
Request destination
module I/O No.
0
0
0
0
5
0
0
35H
30H
30H
30H
30H
31H
30H
31H
30H
30H
30H
30H
30H
30H
(H)
–
–
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
0
1
1
3
Request
destination module
station No.
0
0
MICROCOMPUTER
CONNECTION
(ETHERNET)
Network
No.
Subheader
Following
*1
0
Character A section
*1
Request message
GOT)
Command
4
Sub-command
0
0
0
C
0
0
0
0
1
9
0
1
0
0
0
0
30H
30H
30H
43H
30H
30H
30H
30H
31H
39H
30H
31H
30H
30H
30H
30H
(H)
–
–
(L)
(H)
–
–
(L)
(H)
–
–
(L)
(H)
–
–
(L)
Data length target data
(format 9:QnA compatible 3E frame (Binary))
01H
01H
Request
destination
module I/O No.
00H
00H
Request
destination
module
station No.
00H
Request
data length
06H
00H
CPU monitoring
timer
00H
00H
Command
Subcommand
01H
00H
19H
5
MODBUS(R)/TCP
CONNECTION
00H
PLC
No.
00H
Data length target data
(Continued to next page)
6
CONNECTION TO
SOUND OUTPUT
UNIT
50H
Network
No.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Subheader
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(host
CPU monitoring timer
MODBUS(R)/RTU
CONNECTION
Request data length
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 63
(From previous page)
Item
Message format
(format 8:QnA compatible 3E frame (ASCII))
Network
No.
Subheader
0
PLC No.
Request destination
module I/O No.
0
0
0
0
Request
destination
module station No.
D
0
0
44H
30H
30H
30H
30H
31H
30H
31H
30H
30H
30H
30H
30H
(H)
–
–
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
0
1
1
0
0
Response data length
0
0
1
30H
30H
30H
31H
32H
(L)
(H)
–
–
(L)
0
2
Following
*1
Character B section
*1
Year data
End code
Month data
Day data
Hour data Minute data
Second
data
Day-ofweek data
Response message
during normal
communication
0
0
0
0
0
9
1
0
0
1
1
8
4
6
4
9
0
4
30H
30H
30H
30H
30H
39H
31H
30H
30H
31H
31H
38H
34H
36H
34H
39H
30H
34H
(GOT
(H)
–
–
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
host)
Data length target data
(format 9:QnA compatible 3E frame (Binary))
PLC
Subheader Network
No.
No.
D0H
00H
01H
01H
Request
Request
destination
destination
module
module I/O No. station No.
00H
00H
00H
Response
data length
End code
Year Month
data data
Day
data
Hour Minute Second Day-ofdata data data week data
09H
00H
09H
01H
12H
00H
00H
0AH
2EH
31H
04H
Data length target data
(Continued to next page)
3 - 64
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
Item
Message format
(format 8:QnA compatible 3E frame (ASCII))
0
PLC No.
Request destination
module I/O No.
0
0
0
0
Request
destination
module station No.
D
0
0
44H
30H
30H
30H
30H
31H
30H
31H
30H
30H
30H
30H
30H
(H)
–
–
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
0
1
1
0
0
Response data length
0
0
1
30H
30H
30H
31H
36H
(L)
(H)
–
–
(L)
0
6
Following
*1
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Network
No.
Subheader
*1
Network
No.
End code
Request destination
module I/O No.
PLC No.
Request
destination
module station No.
0
0
5
6
0
0
0
0
0
0
0
0
0
0
30H
30H
35H
36H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
(H)
–
–
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
1)
3
Command
1
9
0
1
0
0
0
0
31H
39H
30H
31H
30H
30H
30H
30H
(H)
–
–
(L)
(H)
–
–
(L)
4
Data length target data
Subheader
Network
No.
PLC
No.
Request
Request
destination
destination module
module I/O No. station No.
MODBUS(R)/RTU
CONNECTION
(format 9:QnA compatible 3E frame (Binary))
Response
data length
Following
*1
D0H
00H
01H
01H
00H
00H
00H
0BH
00H
5
End code
00H
00H
PLC
No.
00H
00H
00H
00H
Command
Subcommand
01H
00H
19H
00H
Data length target data
6
CONNECTION TO
SOUND OUTPUT
UNIT
56H
Network
No.
Request
Request
destination
destination module
module I/O No. station No.
MODBUS(R)/TCP
CONNECTION
*1
7
CONNECTION TO
EXTERNAL I/O
DEVICE
host)
Sub-command
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(GOT
1)
MICROCOMPUTER
CONNECTION
(ETHERNET)
Data length target data
Response message
during faulty
communication
1
PREPARATORY
PROCEDURES FOR
MONITORING
(From previous page)
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 65
(2) Set clock data (0901) command
The following shows an example of setting the clock data of GOT.
(Assuming the clock data of GOT is to be set to "2009, October 1, 18:46:49 Thursday".)
Time display
2009/10/01 18:46:49
THU
After execution
Item
Message format
(format 8:QnA compatible 3E frame (ASCII))
Network
No.
Subheader
1
5
0
0
35H
30H
30H
30H
30H
31H
30H
(H)
–
–
(L)
(H)
(L)
(H)
0
0
Request
destination
module station No.
Request destination
module I/O No.
PLC No.
1
0
0
0
31H
30H
30H
30H
30H
30H
30H
(L)
(H)
–
–
(L)
(H)
(L)
0
0
0
0
Following
*1
*1
Response data length
CPU monitoring timer
Command
0
0
1
A
0
0
0
0
0
9
0
1
30H
30H
31H
41H
30H
30H
30H
30H
31H
39H
30H
31H
(H)
–
–
(L)
(H)
–
–
(L)
(H)
–
–
(L)
1)
Data length target data
Character C section
Year data Month data
Sub-command
Request message
(host
GOT)
1)
Day data
Hour data Minute data
Second
data
Day-ofweek data
0
0
0
0
0
9
1
0
0
1
1
8
4
6
4
9
0
4
30H
30H
30H
30H
30H
39H
31H
30H
30H
31H
31H
38H
34H
36H
34H
39H
30H
34H
(H)
–
–
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Data length target data
(format 9:QnA compatible 3E frame (Binary))
Network PLC
Subheader No.
No.
50H
01H
00H
01H
Request
Request
destination
destination module
module I/O No. station No.
00H
00H
00H
Request
data length
0DH
00H
Following
*1
*1
CPU
Command
monitoring timer
00H
00H
01H
09H
Subcommand
Year Month Day Hour Minute Second Day-ofdata data data data data data week data
00H
09H
00H
0AH
01H
12H
2EH
31H
04H
Data length target data
(Continued to next page)
3 - 66
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
Message format
(format 8:QnA compatible 3E frame (ASCII))
PLC No.
Request
destination
module station No.
Request destination
module I/O No.
D
0
0
0
0
1
0
1
0
0
0
0
0
0
44H
30H
30H
30H
30H
31H
30H
31H
30H
30H
30H
30H
30H
30H
(H)
–
–
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
Following
*1
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Network
No.
Subheader
*1
Response data length
0
4
0
0
0
0
30H
34H
30H
30H
30H
30H
(H)
–
–
(L)
(H)
–
–
(L)
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
Data length target data
(format 9:QnA compatible 3E frame (Binary))
Request
Request
PLC
destination Response
Subheader Network No.
destination module
No.
module I/O No. station No. data length
End code
D0H
00H
01H
01H
00H
00H
00H
02H
00H
00H
4
Data length
target data
(Continued to next page)
5
MODBUS(R)/TCP
CONNECTION
00H
6
CONNECTION TO
SOUND OUTPUT
UNIT
host)
0
30H
7
CONNECTION TO
EXTERNAL I/O
DEVICE
(GOT
0
30H
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Response message
during normal
communication
End code
MODBUS(R)/RTU
CONNECTION
Item
1
PREPARATORY
PROCEDURES FOR
MONITORING
(From previous page)
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
3 - 67
(From previous page)
Item
Message format
(format 8:QnA compatible 3E frame (ASCII))
Network
No.
Subheader
Request
destination
module station No.
Request destination
module I/O No.
PLC No.
Response data length
D
0
0
0
0
1
0
1
0
0
0
0
0
0
0
0
1
6
44H
30H
30H
30H
30H
31H
30H
31H
30H
30H
30H
30H
30H
30H
30H
30H
31H
36H
(H)
–
–
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
(H)
–
–
(L)
Following
*1
*1
Network
No.
End code
Request destination
module I/O No.
PLC No.
Request
destination
module station No.
0
0
5
6
0
0
0
0
0
0
0
0
0
0
30H
30H
35H
36H
30H
30H
30H
30H
30H
30H
30H
30H
30H
30H
(H)
–
–
(L)
(H)
(L)
(H)
(L)
(H)
–
–
(L)
(H)
(L)
1)
Data length target data
Sub-command
Command
Response message
during faulty
communication
(GOT
1)
host)
0
9
0
1
0
0
0
0
30H
39H
30H
31H
30H
30H
30H
30H
(H)
–
–
(L)
(H)
–
–
(L)
Data length target data
(format 9:QnA compatible 3E frame (Binary))
Network PLC
Subheader No.
No.
Request
destination
module I/O No.
Request
destination
module
station No.
Response
data length
Following
*1
D0H
00H
01H
01H
00H
00H
00H
0BH
00H
*1
PLC
End code Network
No.
No.
56H
00H
00H
00H
Request
Request
destination
destination module
module I/O No. station No.
00H
00H
00H
Command
Subcommand
01H
00H
09H
00H
Data length target data
POINT
When a wrong day of the week has been set by the clock data setting command
If a wrong day of the week is set by the clock data setting commands, the clock data will differ from the time
displayed on the utility.
Example: When October 1, 2009 (Tuesday) is set by the clock data setting command (the actual day of the week is
Thursday), Thursday (THU) will be displayed on the utility time display.
 Error code list
For the error codes, refer to the following.
3.4.6 Formats 6, 7 (4E frame) ■Error code list
3 - 68
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.4 Message Formats
Setting communication
interface (Communication
settings)
3.5.2
Communication detail settings
Make the settings according to the usage environment.
Set the channel of the equipment to be connected to the
GOT.
 GT16, GT14
2
MICROCOMPUTER
CONNECTION
(SERIAL)
3.5.1
PREPARATORY
PROCEDURES FOR
MONITORING
1
3.5 GOT Side Settings
2.
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
3.
4.
Set the IP address of the GOT.
(Default: 192.168.3.18)
Subnet Mask*1
Set the subnet mask for the
sub network. (Only for
connection via router)
If the sub network is not used,
the default value is set.
(Default: 255.255.255.0)
0.0.0.0 to
255.255.255.
255
Default Gateway*1
Set the router address of the
default gateway where the
GOT is connected. (Only for
connection via router)
(Default: 0.0.0.0)
0.0.0.0 to
255.255.255.
255
Set the GOT port No. for
Ethernet download.
(Default: 5014)
1024 to 5010.
5014 to
65534
(Except for
5011, 5012,
5013 and
49153)
GOT Communication
Port No.
Set the GOT port No. for the
connection with the Ethernet
module.
(Default: 5021)
1024 to 5010.
5014 to
65534
(Except for
5011, 5012,
5013 and
49153)
Startup Time
Specify the time period from
the GOT startup until GOT
starts the communication with
the PLC CPU.
(Default: 3sec)
3 to 255sec
Delay Time
Set the delay time for reducing
the load of the network/
destination PLC.
(Default: 0ms)
0 to 10000
( 10ms)
Click!
1.
2.
3.
4.
Select [Common]
menu.
[Controller Setting] from the
The Controller Setting window is displayed. Select the
channel to be used from the list menu.
Set the following items.
• Manufacturer: Others
• Controller Type: Computer
• I/F: Interface to be used
• Driver: Ethernet (MICROCOMPUTER)
Ethernet Download
Port No.
The detailed setting is displayed after Manufacturer,
Controller Type, I/F, and Driver are set.
Make the settings according to the usage
environment.
3.5.2 Communication detail settings
Click the [OK] button when settings are completed.
POINT
The settings of connecting equipment can be set and
confirmed in [I/F Communication Setting]. For details,
refer to the following.
6
7
8
1.1.2 I/F communication setting
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.5 GOT Side Settings
5
MODBUS(R)/TCP
CONNECTION
GOT IP Address*1
CONNECTION TO
SOUND OUTPUT
UNIT
Range
0.0.0.0 to
255.255.255.
255
CONNECTION TO
EXTERNAL I/O
DEVICE
Description
3 - 69
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Item
MODBUS(R)/RTU
CONNECTION
4
Item
Description
Select the steps to store two
words (32-bit data).
(Default: LH Order)
LH Order/
HL Order
Protocol*2
Select the communication
protocol
(Default: UDP/IP)
TCP/IP
UDP/IP
Format
Select the communication
format.
(Default: 1)
1 to 9
Interrupt Data Length
Specify the number of bytes of
interrupt data.
(Default: 1)
1/2/4
Special Interrupt
Output
Set whether or not to output
the special interrupt code.
(Default: none)
Yes or No
Living Confirmation*3
Set whether or not to perform
a living confirmation.
(Default: No)
Yes/No
Set the sampling to perform a
living confirmation.
(Default: 20s)
10 to 100s
32bit Storage
Living Confirmation
*4
Cycle
*1
*2
*3
*4
Item
Description
Range
Subnet Mask
Set the subnet mask for the
sub network. (Only for
connection via router)
If the sub network is not used,
the default value is set.
(Default: 255.255.255.0)
0.0.0.0 to
255.255.255.
255
Default Gateway
Set the router address of the
default gateway where the
GOT is connected. (Only for
connection via router)
(Default: 0.0.0.0)
0.0.0.0 to
255.255.255.
255
Set the GOT port No. for
Ethernet download.
(Default: 5014)
1024 to 5010.
5014 to
65534
(Except for
5011, 5012,
5013 and
49153)
GOT Communication
Port No.
Set the GOT port No. for the
connection with the Ethernet
module.
(Default: 5021)
1024 to 5010.
5014 to
65534
(Except for
5011, 5012,
5013 and
49153)
Startup Time
Specify the time period from
the GOT startup until GOT
starts the communication with
the PLC CPU.
(Default: 3sec)
3 to 255sec
Delay Time
Set the delay time for reducing
the load of the network/
destination PLC.
(Default: 0ms)
0 to 10000
( 10ms)
32bit Storage
Select the steps to store two
words (32-bit data).
(Default: LH Order)
LH Order/
HL Order
Protocol*1
Select the communication
protocol
(Default: UDP/IP)
TCP/IP
UDP/IP
Format
Select the communication
format.
(Default: 1)
1 to 9
Interrupt Data Byte
Specify the number of bytes of
interrupt data.
(Default: 1)
1/2/4
Special Interrupt Code
Set whether or not to output
the special interrupt code.
(Default: none)
Yes or No
Living Confirmation*2
Set whether or not to perform
a living confirmation.
(Default: No)
Yes/No
Set the sampling to perform a
living confirmation.
(Default: 20s)
10 to 100s
Range
Ethernet Download
Port No.
Click the [Setting] button and perform the setting in the [GOT
IP Address Setting] screen.
For the interrupt output, select [TCP/IP].
Select [Yes] only when [Protocol] is [TCP/IP].
The setting value can be changed when the [Living
Confirmation] is [Yes].
 GT15, GT12
Living Confirmation
Cycle*3
*1
*2
*3
Item
GOT IP Address
3 - 70
Description
Range
Set the IP address of the GOT.
(Default: 192.168.0.18)
0.0.0.0 to
255.255.255.
255
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.5 GOT Side Settings
For the interrupt output, select [TCP/IP].
Select [Yes] only when [Protocol] is [TCP/IP].
The setting value can be changed when the [Living
Confirmation] is [Yes].
1
PREPARATORY
PROCEDURES FOR
MONITORING
POINT
(1) Special Interrupt Code
The following shows the compatibility between the
special interrupt codes and the event types.
20H
Base Screen*1 and Overlap Window*1
Output when the screens are switched according to the
change in the switching device values assigned to 1/2.
*1: Base Screen or Overlap Window 1/2 switches
independently without being interlocked.
(Example of output)
When all the switching device values assigned to
the Base Screen and Overlap Window1/2 are
changed, 3 special interrupt codes are output.
21H
Output when Numerical/ASCII Input is completed.
22H
Output when Recipe data transfer (read-out, write-in) is
completed.
23H
Output when Bar code, RFID data has been imported
into GOT
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
Event type
MICROCOMPUTER
CONNECTION
(SERIAL)
2
Special
Interrupt Code
(Hex)
4
MODBUS(R)/RTU
CONNECTION
(1) Communication interface setting by the Utility
The communication interface setting can be
changed on the Utility's [Communication setting]
after writing [Communication Settings] of project
data.
For details on the Utility, refer to the following
manual.
5
User's Manual of GOT used.
MODBUS(R)/TCP
CONNECTION
(2) Precedence in communication settings
When settings are made by GT Designer3 or the
Utility, the latest setting is effective.
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.5 GOT Side Settings
3 - 71
3.6 System Configuration Examples
The following shows a system configuration example in the case of the microcomputer connection (Ethernet).
 System configuration
The system configuration example illustrated below is explained in this section.
IBM-PC/AT-compatible PC
(Microsoft® Visual C++® Ver.6.0)
 Communication settings on GOT side and monitor screen settings
(1) Transmission settings
Set the transmission settings of the GOT.
The transmission settings in the microcomputer connection (Ethernet) are made at [Detail Setting] on GT
Designer3.
3.5.2 Communication detail settings
(2) Monitor screen settings
For the monitor screen settings in this system configuration example, refer to the example of the system
configuration of the microcomputer connection (serial).
2.7 System Configuration Examples
3 - 72
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.6 System Configuration Examples
2
MICROCOMPUTER
CONNECTION
(SERIAL)
The device ranges of controller that can be used for GOT are as follows.
Note that the device ranges in the following tables are the maximum values that can be set in GT Designer3.
The device specifications of controllers may differ depending on the models, even though belonging to the same series.
Please make the setting according to the specifications of the controller actually used.
When a non-existent device or a device number outside the range is set, other objects with correct device settings may
not be monitored.
PREPARATORY
PROCEDURES FOR
MONITORING
1
3.7 Device Range that Can Be Set
 Setting item
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
Device
Set the device name, device number, and bit number.
The bit number can be set only when specifying the bit of word device.
Information
Displays the device type and setting range which are selected in [Device].
Device No. representation
to
M2047
Special relay (SM)
SM0
to
SM63
Latch relay (L)
L0
to
L2047
Word device bit
Specified bit of the following word devices
Data register (D)
D0
to
D4095
Link special register (SD)
SD0
to
SD15
File register (R)
R0
to
R4095
Decimal
6
Converting bit devices into word
CONNECTION TO
SOUND OUTPUT
UNIT
Bit device word
5
Decimal
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Word device
Setting range
M0
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Bit device
Device name
Internal relay (M)
MODBUS(R)/RTU
CONNECTION
4
Description
MODBUS(R)/TCP
CONNECTION
Item
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.7 Device Range that Can Be Set
3 - 73
3.8 Precautions
 GOT clock control
The settings of "time adjusting" or "time broadcast"
made on the GOT will be disabled on the PLC.
Use the dedicated commands to set or read out the
clock data of microcomputer.
 UDP/IP connection
When the commands are sent from multiple controllers
simultaneously, the GOT may not receive all the
commands.
Retry sending the commands on the controller, to
receive them on the GOT again.
 Station monitoring function
The microcomputer connection (Ethernet) does not
support the station monitoring function.
 Interrupt output
The interrupt output is effective only at TCP/IP
connection.
At UDP/IP connection, the interrupt output is not
enabled.
3 - 74
3. MICROCOMPUTER CONNECTION (ETHERNET)
3.8 Precautions
MODBUS CONNECTIONS
4.
MODBUS(R)/RTU CONNECTION . . . . . . . . . . . . . . . . . . . . 4 - 1
5.
MODBUS(R)/TCP CONNECTION . . . . . . . . . . . . . . . . . . . . 5 - 1
4
PREPARATORY
PROCEDURES FOR
MONITORING
MICROCOMPUTER
CONNECTION
(SERIAL)
2
MODBUS(R)/RTU CONNECTION
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
4.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 2
4
MODBUS(R)/RTU
CONNECTION
4.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 3
4.3 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 4
4.4 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 12
4.5 MODBUS(R)/RTU Equipment Side Setting . . . . . . . . . . . . 4 - 14
5
MODBUS(R)/TCP
CONNECTION
4.6 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 17
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
4.
1
4-1
4.
MODBUS(R)/RTU CONNECTION
4.1 Connectable Model List
For applicable MODBUS®/RTU equipment, refer to the following Technical News.
List of Valid Devices Applicable for GOT1000 Series with MODBUS Connection (GOT-A-0037)
Visit the Mitsubishi Electric FA Equipment Information Service website (MELFANSweb) to refer to the Technical News.
http://wwwf2.mitsubishielectric.co.jp/english/index.html
POINT
Compatible hardware version for the RS-422/485 connection
The following GOT models are compatible with the RS-422/485 connection.
For the confirming method of hardware version, refer to the following.
GT16 User’s Manual (Hardware)
GT15 User's Manual
GT14 User's Manual
GT11 User's Manual
GT10 User's Manual
GOT
4-2
Hardware version
GT16, GT15, GT14, GT12
version A or later
GT1155-QTBD
version C or later
GT1155-QSBD
version F or later
GT1150-QLBD
version F or later
GT1055-QSBD, GT1050-QBBD
version C or later
GT1045-QSBD, GT1040-QBBD
version A or later
GT1030-L
D
version B or later
GT1020-L
D
version E or later
4. MODBUS(R)/RTU CONNECTION
4.1 Connectable Model List
Standard monitor OS
-
Standard monitor OS[01.12.**]or later
1
Connecting to MODBUS(R)/RTU equipment
Communication driver
Connection cable
Controller
Communic
ation Type
Connection cable
Cable model
Connection diagram number
RS232 connection diagram
RS-232
1)
GOT
Max.
distance
Option device
Model
- (Built into GOT)
15m*1
1 MODBUS
equipment for 1
GOT
GT15-RS2-9P
2)
RS422/485 connection
diagram 1)
RS422/485 connection
diagram 2)
MODBUS®/RTU
equipment
15m*1
4
- (Built into GOT)
FA-LTBGTR4CBL05(0.5m)*2
1200m*1
FA-LTBGTR4CBL10(1m)*2
FA-LTBGTR4CBL20(2m)*2
1200m*1
- (Built into GOT)
5
GT16-C02R4-9S(0.2m)
RS422/485 connection
diagram 3)
RS-422/
485
RS422/485 connection
diagram 4)
1200m
*1
GT15-RS4-9S
GT15-RS2T4-9P*4
1200m*1
- (Built into GOT)
1200m*1
GT10-9PT5S*5
1200m*1
- (Built into GOT)
1200m*1
GT15-RS4-TE
1200m*1
GT14-RS2T4-9P*6
Up to 31 MODBUS
equipment for 1
GOT
*3
diagram 5)
RS422/485 connection
diagram 6)
RS422/485 connection
diagram 7)
RS422/485 connection
diagram 8)
6
CONNECTION TO
SOUND OUTPUT
UNIT
RS422/485 connection
3
MODBUS(R)/RTU
CONNECTION
RS232 connection diagram
Number of
connectable
equipment
MICROCOMPUTER
CONNECTION
(SERIAL)
2
MODBUS/RTU
MICROCOMPUTER
CONNECTION
(ETHERNET)
GOT
MODBUS(R)/TCP
CONNECTION
MODBUS®/RTU
equipment
7
*1
*2
The shortest specification on the MODBUS®/RTU equipment side is prioritized.
Product manufactured by MITSUBISHI ELECTRIC ENGINEERING COMPANY LIMITED.
For details of the product, contact MITSUBISHI ELECTRIC ENGINEERING COMPANY LIMITED.
*3
When it is less than 31 units, the number of the maximum connectable units on the MODBUS®/RTU equipment side will apply.
*4
*5
*6
Connect it to the RS-232 interface (built into GOT). It cannot be mounted on GT1655, GT155
Connect it to the RS-422 interface (built into GOT).
Connect it to the RS-232 interface (built into GOT).
.
CONNECTION TO
EXTERNAL I/O
DEVICE
4.2.1
PREPARATORY
PROCEDURES FOR
MONITORING
4.2 System Configuration
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
4. MODBUS(R)/RTU CONNECTION
4.2 System Configuration
4-3
4.3 Connection Diagram
The following diagram shows the connection between the
GOT and the PLC.
4.3.1
(1) Cable length
RS-232 cable
The length of the RS-232 cable must be 15m or less.
 Connection diagram
(2) GOT side connector
For the GOT side connector, refer to the following.
RS232 connection diagram 1)
GOT side
*1
1.4.1 GOT connector specifications
MODBUS equipment side
1
-
RD(RXD)
2
TxD
CD/NC
SD(TXD)
3
RxD
ER(DTR)
4
-
SG
5
SG
DR(DSR)
6
-
RS(RTS)
7
-
CS(CTS)
8
-
NC
9
-
*1
*2
*2
GT16: CD, GT15: CD, GT14: NC, GT12: NC,GT11: NC,
GT105 : NC, GT104 : NC
Some MODBUS®/RTU equipment require the control line
(CS, RS, etc.) to be controlled.
Make sure to connect the cables and wires as described in
the MODBUS®/RTU equipment manual.
RS232 connection diagram 2)
GOT side
*1
MODBUS equipment side
SD
RxD
RD
TxD
ER
-
DR
-
SG
SG
RS
-
CS
-
*1
4-4
 Precautions when preparing a cable
Some MODBUS®/RTU equipment require the control line
(CS, RS, etc.) to be controlled.
Make sure to connect the cables and wires as described in
the MODBUS®/RTU equipment manual.
4. MODBUS(R)/RTU CONNECTION
4.3 Connection Diagram
(3) MODBUS equipment side connector
Use the connector compatible with the MODBUS®/RTU
equipment side module.
For details, refer to the MODBUS®/RTU equipment
user's manual.
The following shows the connection diagrams and connector specifications of the RS-422/485 cable used for connecting
the GOT to a PLC.
RS-422/485 cable 1) (2 pair wiring)
SDA1(TXD1+) *5
8
RDA1(RXD1+) *5
RDB1(RXD1-) *5
10
12
*3
SG
NC
NC
NC
SDA2(TXD2+)
SDB2(TXD2-)
RDA2(RXD2+)
RDB2(RXD2-)
NC
RSA(RTS+)
NC
RSB(RTS-)
NC
CSA(CTS+)
NC
CSB(CTS-)
RDA(+)
RDB(-)
RDB(-)
SDA(+)
SDA(+)
SDB(-)
SDB(-)
SG
SG
2
2
1
3
4
5
3
7
9
11
MICROCOMPUTER
CONNECTION
(ETHERNET)
R
6
*5
13
14
15
16
17
18
4
19
20
*3
Some MODBUS®/RTU equipment doesn't have SG.In this case, the wiring between GOT and SG is unnecessary.
Some MODBUS®/RTU equipment require the control line (CS, RS, etc.) to be controlled. Make sure to connect the cables and
wires as described in the MODBUS®/RTU equipment manual.
A terminating resistor is required. Set the terminating resistor selector of the main unit to "Disable" and connect a 110
*4
*5
terminating resistor. (
1.4.3 Terminating resistors of GOT)
For the terminating resistor of MODBUS®/RTU equipment, refer to the manual of MODBUS®/RTU equipment to be used.
Use the twisted pair cable for SDA1/SDB1 and RDA1/RDB1.
*1
*2
5
RS-422/485 cable 1) (1 pair wiring)
CON side(20 pin)*3
SDA1(TXD1+)*5
SDB1(TXD1-)*5
RDA1(RXD1+)
SG
NC
NC
NC
SDA2(TXD2+)
SDB2(TXD2-)
RDA2(RXD2+)
RDB2(RXD2-)
NC
RSA(RTS+)
NC
RSB(RTS-)
NC
CSA(CTS+)
NC
CSB(CTS-)
(+)
(-)
(-)
SG
SG
8
10
12
6
2
1
CONNECTION TO
SOUND OUTPUT
UNIT
*3
RDB1(RXD1-)
MODBUS®/RTU equipment side*1*2*4
(+)
3
4
5
7
9
11
7
13
14
15
CONNECTION TO
EXTERNAL I/O
DEVICE
R
6
MODBUS®/RTU equipment side*1*2*4
MODBUS(R)/RTU
CONNECTION
*3
SDB1(TXD1-)
MODBUS®/RTU equipment side*1*2*4
RDA(+)
MODBUS(R)/TCP
CONNECTION
R
MODBUS®/RTU equipment side*1*2*4
MICROCOMPUTER
CONNECTION
(SERIAL)
CON side(20 pin)*3
PREPARATORY
PROCEDURES FOR
MONITORING
1
RS-422/485 cable
16
17
18
19
20
*2
*3
The actual terminal layout on the MODBUS®/RTU equipment may differ from the example shown above. SDA/B(+/-) and RDA/
B(+/-) terminals can be separated from each other. Make sure to connect the cables and wires as described in the MODBUS®/
RTU equipment manual.
Some MODBUS®/RTU equipment doesn't have SG. In this case, the wiring between GOT and SG is unnecessary.
A terminating resistor is required. Set the terminating resistor selector of the main unit to "Disable" and connect a 110
*4
*5
terminating resistor. (
1.4.3 Terminating resistors of GOT)
For the terminating resistor of MODBUS®/RTU equipment, refer to the manual of MODBUS®/RTU equipment to be used.
Use the twisted pair cable for SDA1/SDB1.
*1
4. MODBUS(R)/RTU CONNECTION
4.3 Connection Diagram
4-5
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
4.3.2
RS422/485 cable 2) (2 pair wiring)
CON side(14 pin)*3
SDA1(TXD1+)*5
R
*3
R
SDB1(TXD1-)*5
RDA1(RXD1+)*5
*5
RDB1(RXD1-)
*3
MODBUS®/RTU equipment side*1*2*4
RDA(+)
RDA(+)
1
RDB(-)
RDB(-)
SDA(+)
SDA(+)
SDB(-)
SDB(-)
SG
SG
2
3
4
SG
13
SDA2(TXD2+)
5
SDB2(TXD2-)
6
RDA2(RXD2+)
7
RDB2(RXD2-)
8
RSA(RTS+)
9
RSB(RTS-)
10
CSA(CTS+)
11
CSB(CTS-)
12
NC
MODBUS®/RTU equipment side*1*2*4
14
Shell
*1
Some MODBUS®/RTU equipment doesn't have SG.In this case, the wiring between GOT and SG is unnecessary.
*2
Some MODBUS®/RTU equipment require the control line (CS, RS, etc.) to be controlled.
*3
Make sure to connect the cables and wires as described in the MODBUS®/RTU equipment manual.
A terminating resistor is required. Set the terminating resistor selector of the main unit to "Disable" and connect a 330
*4
*5
For the terminating resistor of MODBUS®/RTU equipment, refer to the manual of MODBUS®/RTU equipment to be used.
Use the twisted pair cable for SDA1/SDB1 and RDA1/RDB1.
terminating resistor. (
1.4.3 Terminating resistors of GOT)
RS422/485 cable 2) (1 pair wiring)
CON side(14 pin)*3
SDA1(TXD1+)*5
*5
SDB1(TXD1-)
RDA1(RXD1+)
R
RDB1(RXD1-)
*3
MODBUS®/RTU equipment side*1*2*4
(+)
(+)
(-)
(-)
SG
SG
1
2
3
4
SG
13
SDA2(TXD2+)
5
SDB2(TXD2-)
6
RDA2(RXD2+)
7
RDB2(RXD2-)
8
RSA(RTS+)
9
RSB(RTS-)
10
CSA(CTS+)
11
CSB(CTS-)
12
NC
MODBUS®/RTU equipment side*1*2*4
14
Shell
*1
The actual terminal layout on the MODBUS®/RTU equipment may differ from the example shown above. SDA/B(+/-) and RDA/
B(+/-) terminals can be separated from each other. Make sure to connect the cables and wires as described in the MODBUS®/
RTU equipment manual.
*2
Some MODBUS®/RTU equipment doesn't have SG. In this case, the wiring between GOT and SG is unnecessary.
*3
A terminating resistor is required. Set the terminating resistor selector of the main unit to "Disable" and connect a 110
*4
*5
For the terminating resistor of MODBUS®/RTU equipment, refer to the manual of MODBUS®/RTU equipment to be used.
Use the twisted pair cable for SDA1/SDB1.
terminating resistor. (
4-6
1.4.3 Terminating resistors of GOT)
4. MODBUS(R)/RTU CONNECTION
4.3 Connection Diagram
GOT side (D-Sub 9-pin)*3
R
RDB
*3
equipment
(2nd)
RDA(+)
1
RDB(-)
RDB(-)
SDA(+)
SDA(+)
SDB(-)
SDB(-)
SG
SG
6
2
7
SG
5
RSA
3
RSB
8
CSA
4
CSB
9
2
MICROCOMPUTER
CONNECTION
(SERIAL)
RDA
RDA(+)
side*1*2*4
*1
Some MODBUS®/RTU equipment doesn't have SG. In this case, the wiring between GOT and SG is unnecessary.
*2
Some MODBUS®/RTU equipment require the control line (CS, RS, etc.) to be controlled.
*3
Make sure to connect the cables and wires as described in the MODBUS®/RTU equipment manual.
A terminating resistor is required. For GT16, set the terminating resistor selector of the main unit to "Disable" and connect a
*4
For the terminating resistor of MODBUS®/RTU equipment, refer to the manual of MODBUS®/RTU equipment to be used.
330
terminating resistor. For GT15, connect a 330
terminating resistor. (
1.4.3 Terminating resistors of GOT)
RS422/485 cable 4) (2 pair wiring)
MODBUS®/RTU equipment side*1*2*4
(1st)
GOT side (D-Sub 9-pin)*3
SDA
MODBUS®/RTU equipment side*1*2*4
(2nd)
RDA(+)
RDA(+)
RDB(-)
RDB(-)
SDA(+)
SDA(+)
SDB(-)
SDB(-)
SG
SG
4
6
RDA
2
RDB
MODBUS(R)/RTU
CONNECTION
1
SDB
7
5
RSA
3
RSB
8
CSA
4
CSB
9
5
®
*1
Some MODBUS /RTU equipment doesn't have SG. In this case, the wiring between GOT and SG is unnecessary.
*2
Some MODBUS®/RTU equipment require the control line (CS, RS, etc.) to be controlled.
*3
Make sure to connect the cables and wires as described in the MODBUS®/RTU equipment manual.
When placing the GOT to the terminal in the system configuration, set the terminating resistor to "330 ".
When placing the GOT to the position other than the terminal, set the terminating resistor of the GOT to "OPEN".
*4
For the terminating resistor of MODBUS®/RTU equipment, refer to the manual of MODBUS®/RTU equipment to be used.
MODBUS(R)/TCP
CONNECTION
SG
1.4.3 Terminating resistors of GOT
6
RS422/485 cable 4) (1 pair wiring)
GOT side (D-Sub 9-pin)*3
MODBUS®/RTU equipment side*1*2*4
(1st)
MODBUS®/RTU equipment side*1*2*4
(2nd)
(+)
(+)
(-)
(-)
SG
SG
1
SDB
6
RDA
2
RDB
7
SG
5
RSA
3
RSB
8
CSA
4
CSB
9
*1
7
The actual terminal layout on the MODBUS®/RTU equipment may differ from the example shown above. SDA/B(+/-) and RDA/
B(+/-) terminals can be separated from each other. Make sure to connect the cables and wires as described in the MODBUS®/
RTU equipment manual.
*2
Some MODBUS®/RTU equipment doesn't have SG. In this case, the wiring between GOT and SG is unnecessary.
*3
When placing the GOT to the terminal in the system configuration, set the terminating resistor to "110 ".
When placing the GOT to the position other than the terminal, set the terminating resistor of the GOT to "OPEN".
*4
For the terminating resistor of MODBUS®/RTU equipment, refer to the manual of MODBUS®/RTU equipment to be used.
1.4.3 Terminating resistors of GOT
4. MODBUS(R)/RTU CONNECTION
4.3 Connection Diagram
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
SDA
3
CONNECTION TO
SOUND OUTPUT
UNIT
*3
SDB
MODBUS®/RTU
CONNECTION TO
EXTERNAL I/O
DEVICE
SDA
R
equipment
(1st)
side*1*2*4
MICROCOMPUTER
CONNECTION
(ETHERNET)
MODBUS®/RTU
PREPARATORY
PROCEDURES FOR
MONITORING
1
RS422/485 cable 3) (2 pair wiring)
4-7
RS422/485 cable 5) (2 pair wiring)
GOT side (terminal
block)*3
MODBUS®/RTU equipment side*1*2*4
(1st)
MODBUS®/RTU equipment side*1*2*4
(2nd)
RDA(+)
SDA
SDB
RDA
RDB
SG
*1
RDA(+)
RDB(-)
RDB(-)
SDA(+)
SDA(+)
SDB(-)
SDB(-)
SG
SG
Some MODBUS®/RTU equipment doesn't have SG. In this case, the wiring between GOT and SG is unnecessary.
*2
Some MODBUS®/RTU equipment require the control line (CS, RS, etc.) to be controlled.
*3
Make sure to connect the cables and wires as described in the MODBUS®/RTU equipment manual.
When placing the GOT to the terminal in the system configuration, set the terminating resistor to "330 ".
When placing the GOT to the position other than the terminal, set the terminating resistor of the GOT to "OPEN".
1.4.3 Terminating resistors of GOT
Set the 1pair/2pair signal selection switch to "1pair" when using the connection conversion adapter.
Connection Conversion Adapter User’s manual
*4
For the terminating resistor of MODBUS®/RTU equipment, refer to the manual of MODBUS®/RTU equipment.
RS422/485 cable 5) (1 pair wiring)
GOT side (terminal block)*3
MODBUS®/RTU equipment side*1*2*4
(1st)
SDA
SDB
MODBUS®/RTU equipment side*1*2*4
(2nd)
(+)
(+)
(-)
(-)
SG
SG
RDA
RDB
SG
*1
The actual terminal layout on the MODBUS®/RTU equipment may differ from the example shown above. SDA/B(+/-) and RDA/
B(+/-) terminals can be separated from each other. Make sure to connect the cables and wires as described in the MODBUS®/
RTU equipment manual.
*2
*3
Some MODBUS®/RTU equipment doesn't have SG. In this case, the wiring between GOT and SG is unnecessary.
When placing the GOT to the terminal in the system configuration, set the terminating resistor to "110 ".
When placing the GOT to the position other than the terminal, set the terminating resistor of the GOT to "OPEN".
1.4.3 Terminating resistors of GOT
Set the 1pair/2pair signal selection switch to "1pair" when using the connection conversion adapter.
Connection Conversion Adapter User’s manual
*4
For the terminating resistor of MODBUS®/RTU equipment, refer to the manual of MODBUS®/RTU equipment.
RS422/485 cable 6) (2 pair wiring)
GOT side (terminal block)*3
MODBUS®/RTU equipment side*1*2*4
(1st)
SDA
SDB
RDA
RDB
SG
MODBUS®/RTU equipment side*1*2*4
(2nd)
RDA(+)
RDA(+)
RDB(-)
RDB(-)
SDA(+)
SDA(+)
SDB(-)
SDB(-)
SG
SG
RSA
RSB
CSA
CSB
*1
Some MODBUS®/RTU equipment doesn't have SG. In this case, the wiring between GOT and SG is unnecessary.
*2
Some MODBUS®/RTU equipment require the control line (CS, RS, etc.) to be controlled.
*3
Make sure to connect the cables and wires as described in the MODBUS®/RTU equipment manual.
When placing the GOT to the terminal in the system configuration, set the terminating resistor to "330 ".
When placing the GOT to the position other than the terminal, set the terminating resistor of the GOT to "OPEN".
*4
For the terminating resistor of MODBUS®/RTU equipment, refer to the manual of MODBUS®/RTU equipment.
1.4.3 Terminating resistors of GOT
4-8
4. MODBUS(R)/RTU CONNECTION
4.3 Connection Diagram
1
GOT side (D-Sub 9-pin)
6
RDA
2
RDB
7
SG
5
RSA
3
RSB
8
CSA
4
CSB
9
(+)
(-)
(-)
SG
SG
2
*1
MICROCOMPUTER
CONNECTION
(SERIAL)
SDB
(+)
The actual terminal layout on the MODBUS®/RTU equipment may differ from the example shown above. SDA/B(+/-) and RDA/
B(+/-) terminals can be separated from each other. Make sure to connect the cables and wires as described in the MODBUS®/
RTU equipment manual.
*2
*3
Some MODBUS®/RTU equipment doesn't have SG.
In this case, the wiring between GOT and SG is unnecessary.
When placing the GOT to the terminal in the system configuration, set the terminating resistor to "110 ".
When placing the GOT to the position other than the terminal, set the terminating resistor of the GOT to "OPEN".
4
1.4.3 Terminating resistors of GOT
*4
For the terminating resistor of MODBUS®/RTU equipment, refer to the manual of MODBUS®/RTU equipment.
SDB1
2
RDA1
3
RDB1
4
SDA2
5
SDB2
6
RDA2
7
RDB2
8
SG
9
FG
10
(+)
(+)
(-)
(-)
SG
SG
5
6
*1
The actual terminal layout on the MODBUS®/RTU equipment may differ from the example shown above. SDA/B(+/-) and RDA/
B(+/-) terminals can be separated from each other. Make sure to connect the cables and wires as described in the MODBUS®/
RTU equipment manual.
*2
*3
Some MODBUS®/RTU equipment doesn't have SG. In this case, the wiring between GOT and SG is unnecessary.
When placing the GOT to the terminal in the system configuration, set the terminating resistor to "100 OHM".
When placing the GOT to the position other than the terminal, set the terminating resistor of the GOT to "No".
*4
For the terminating resistor of MODBUS®/RTU equipment, refer to the manual of MODBUS®/RTU equipment.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
1
1.4.3 Terminating resistors of GOT
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
SDA1
MODBUS®/RTU equipment side*1*2*4
(2nd)
MODBUS(R)/TCP
CONNECTION
GOT side (terminal
MODBUS®/RTU equipment side*1*2*4
(1st)
MODBUS(R)/RTU
CONNECTION
RS422/485 connection diagram 7)
block)*3
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
1
MODBUS®/RTU equipment side*1*2*4
(2nd)
CONNECTION TO
SOUND OUTPUT
UNIT
SDA
MODBUS®/RTU equipment side*1*2*4
(1st)
*3
PREPARATORY
PROCEDURES FOR
MONITORING
RS422/485 cable 6) (1 pair wiring)
4. MODBUS(R)/RTU CONNECTION
4.3 Connection Diagram
4-9
RS422/485 cable 8) (2 pair wiring)
GOT side (terminal
block)*)*4*5
MODBUS®/RTU equipment side*1*2*3
(1st)
MODBUS®/RTU equipment side*1*2*3
(2nd)
RDA(+)
SDA
SDB
RDA
RDB
SG
*1
RDA(+)
RDB(-)
RDB(-)
SDA(+)
SDA(+)
SDB(-)
SDB(-)
SG
SG
The actual terminal layout on the MODBUS®/RTU equipment may differ from the example shown above. SDA/B(+/-) and RDA/
B(+/-) terminals can be separated from each other. Make sure to connect the cables and wires as described in the MODBUS®/
RTU equipment manual.
*2
Some MODBUS®/RTU equipment doesn't have SG.
In this case, the wiring between GOT and SG is unnecessary.
*3
*4
For the terminating resistor of MODBUS®/RTU equipment, refer to the manual of MODBUS®/RTU equipment to be used.
Set the 2-wire/4-wire terminating resistor setting switch of the RS-232/485 signal conversion adaptor as follows.
2-wire type/4-wire type: 4-wire type (2Pair)
<When placing GOT to the terminal>
Set the same terminating resistor value as that of MODBUS®/RTU equipment. However, only "110
terminating resistor of GOT.
If the terminating resistor value of MODBUS®/RTU equipment is other than "110
"/"330
"/"330
" can be set as the
", set the terminating resistor of GOT
side to "OPEN" and install the terminating resistor set according to the terminating resistor value of MODBUS®/RTU equipment to
the RS-232/485 signal conversion adaptor externally.
<When placing GOT to other than the terminal>
Set the terminating resistor of the GOT to "OPEN".
1.4.4 Setting the RS-232/485 signal conversion adaptor
*5
Some MODBUS®/RTU equipment require the control line (CS, RS) to be controlled. In this case, the connection using the RS232/485 signal conversion adaptor is unavailable.
RS422/485 cable 8) (1 pair wiring)
GOT side(terminal block)*4*5
MODBUS®/RTU equipment side*1*2*3
(1st)
SDA
SDB
MODBUS®/RTU equipment side*1*2*3
(2nd)
(+)
(+)
(-)
(-)
SG
SG
RDA
RDB
SG
*1
The actual terminal layout on the MODBUS®/RTU equipment may differ from the example shown above. SDA/B(+/-) and RDA/
B(+/-) terminals can be separated from each other. Make sure to connect the cables and wires as described in the MODBUS®/
RTU equipment manual.
*2
Some MODBUS®/RTU equipment doesn't have SG.
In this case, the wiring between GOT and SG is unnecessary.
*3
*4
For the terminating resistor of MODBUS®/RTU equipment, refer to the manual of MODBUS®/RTU equipment to be used.
Set the 2-wire/4-wire terminating resistor setting switch of the RS-232/485 signal conversion adaptor as follows.
2-wire type/4-wire type: 2-wire type (1Pair)
<When placing GOT to the terminal>
Set the same terminating resistor value as that of MODBUS®/RTU equipment. However, only "110
terminating resistor of GOT.
If the terminating resistor value of MODBUS®/RTU equipment is other than "110
"/"330
"/"330
" can be set as the
", set the terminating resistor of GOT
side to "OPEN" and install the terminating resistor set according to the terminating resistor value of MODBUS®/RTU equipment to
the RS-232/485 signal conversion adaptor externally.
<When placing GOT to other than the terminal>
Set the terminating resistor of the GOT to "OPEN".
1.4.4 Setting the RS-232/485 signal conversion adaptor
*5
4 - 10
Some MODBUS®/RTU equipment require the control line (CS, RS) to be controlled. In this case, the connection using the RS232/485 signal conversion adaptor is unavailable.
4. MODBUS(R)/RTU CONNECTION
4.3 Connection Diagram
1
PREPARATORY
PROCEDURES FOR
MONITORING
 Precautions when preparing a cable
(1) Cable length
The length of the RS-422/485 cable must be 1200m or
less.
(2) GOT side connector
For the GOT side connector, refer to the following.
2
MICROCOMPUTER
CONNECTION
(SERIAL)
1.4.1 GOT connector specifications
(3) MODBUS®/RTU equipment side connector
Use the connector compatible with the MODBUS®/RTU
equipment side module.
For details, refer to the MODBUS equipment user's
manual.
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
 Connecting terminating resistors
(1) GOT side
When connecting a MODBUS®/RTU equipment to the
GOT, a terminating resistor must be connected to the
GOT.
(a) For GT16 body, GT12, RS-422/485 communication
unit
Set the terminating resistor using the terminating
resistor setting switch.
(b) For GT14, GT11, GT10
Set the terminating resistor using the terminating
resistor selector.
For the procedure to set the terminating resistor, refer
to the following.
MODBUS(R)/RTU
CONNECTION
4
5
1.4.3 Terminating resistors of GOT
equipment side
MODBUS(R)/TCP
CONNECTION
When connecting a MODBUS®/RTU equipment to the
GOT, a terminating resistor must be connected to the
MODBUS®/RTU equipment.
For details, refer to the MODBUS®/RTU equipment
user's manual.
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
(2)
MODBUS®/RTU
4. MODBUS(R)/RTU CONNECTION
4.3 Connection Diagram
4 - 11
4.4 GOT Side Settings
4.4.1
Setting communication
interface (Communication
settings)
4.4.2
Communication detail settings
Make the settings according to the usage environment.
Set the channel of the equipment to be connected to the
GOT.
2.
3.
Item
Description
Transmission
Speed
9600bps,
19200bps,
38400bps,
57600bps,
115200bps
Data Bit
Set this item when change the data
length used for communication with
the connected equipment.
(Default: 8bits)
7bits/8bits
Stop Bit
Specify the stop bit length for
communications.
(Default: 1bit)
1bit/2bits
Parity
Specify whether or not to perform a
parity check, and how it is performed
during communication.
(Default: Even)
None
Even
Odd
The Controller Setting window is displayed. Select the
channel to be used from the list menu.
Retry
Set the number of retries to be
performed when a communication
error occurs.
(Default: 3times)
0 to 5times
Set the following items.
• Manufacturer: MODBUS
• Controller Type: MODBUS
• I/F: Interface to be used
• Driver: MODBUS/RTU
Timeout Time
Set the time period for a
communication to time out.
(Default: 3sec)
3 to 30sec
Host Address
Specify the host address in the
network of the GOT.
(Default: 1)
1 to 247
Delay Time*1
Set this item to adjust the
transmission timing of the
0 to 300ms
communication request from the GOT.
(Default: 0ms)
32bit Storage
Select the steps to store two words
(32-bit data).
(Default: LH Order)
4.
Click!
1.
2.
3.
4.
Range
Set this item when change the
transmission speed used for
communication with the connected
equipment.
(Default: 19200bps)
Select [Common]
menu.
[Controller Setting] from the
The detailed setting is displayed after Manufacturer,
Controller Type, I/F, and Driver are set.
Make the settings according to the usage
environment.
4.4.2 Communication detail settings
*1
The GOT ensures in advance the minimum interval (3.5
characters time) for communication frame defined in the
MODBUS®/RTU.
Therefore, the actual send delay time is as follows.
Click the [OK] button when settings are completed.
Actual send
delay time
POINT
The settings of connecting equipment can be set and
confirmed in [I/F Communication Setting]. For details,
refer to the following.
1.1.2 I/F communication setting
4 - 12
4. MODBUS(R)/RTU CONNECTION
4.4 GOT Side Settings
LH Order/HL
Order
=
Send delay time set in
the communication +
detail setting
3.5 character
time
Minimum interval for
communication frame
defined in MODBUS/RTU
When connecting to MODBUS®/RTU equipment which
requires a delay longer than 3.5 character time, adjust the
send delay time.
PREPARATORY
PROCEDURES FOR
MONITORING
1
HINT
If the communication with MODBUS®/RTU equipment
is not established, some equipment which requires a
delay longer than 3.5 character time may be
connected.
Adjust the send delay time in the communication detail
setting.
MICROCOMPUTER
CONNECTION
(SERIAL)
2
POINT
(1) Communication interface setting by the Utility
The communication interface setting can be
changed on the Utility's [Communication setting]
after writing [Communication Settings] of project
data.
For details on the Utility, refer to the following
manual.
User's Manual of GOT used.
(2) Precedence in communication settings
When settings are made by GT Designer3 or the
Utility, the latest setting is effective.
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
MODBUS(R)/RTU
CONNECTION
4
MODBUS(R)/TCP
CONNECTION
5
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
4. MODBUS(R)/RTU CONNECTION
4.4 GOT Side Settings
4 - 13
4.5 MODBUS(R)/RTU Equipment Side Setting
 Function Code
POINT
MODBUS®/RTU equipment
For details of the MODBUS®/RTU equipment, refer to
the manual of MODBUS®/RTU equipment to be used.
4.5.1
Communication settings
 Device setting items for GT Designer3
Item
Device
Description
Set the device name, device number, and bit number.
The bit number can be set only when specifying the bit of word
device.
File No.
Informati
on
Set the file No.
The file No. can be set only when select 6 at
[Device].
Displays the device type and setting range which are selected
in [Device].
Set the station number of the controller to be monitored.
Host
Select this item for monitoring the host controller.
• For GT16, GT15
Select this for monitoring other controllers.
After selecting the item, set the station number and
network number of the controller to be monitored.
NW No.:
Network
Other
4 - 14
For the MODBUS®/RTU connection,
set "1".
For the MODBUS®/TCP connection,
set the network No.
Station No.: Set the station No.
• For GT11, GT10
Select this for monitoring other controllers.
After selecting, set the station number of the
controller to be monitored.
Station No.: Set the station No.
4. MODBUS(R)/RTU CONNECTION
4.5 MODBUS(R)/RTU Equipment Side Setting
The GOT supports the following function codes.
Function Code
Function
Number of device
that is accessible
with one
message
[Unit: point(s)]
0x01
Read Coils
1 to 2000
0x02
Read Discrete Inputs
1 to 2000
0x03
Read Holding Registers
1 to 125
0x04
Read Input Registers
1 to 125
0x05
Write Single Coil
1
0x06
Write Single Register
1
0x0F
Write Multiple Coils
1 to 1968
0x10
Write Multiple Register
1 to 123
0x14
Read File Record
1 to 124
0x15
Write File Record
1 to 122
Coil
Input relay
Input register
Holding
register
Function code to be
used
Representation on GT
Designer3
0000
0001
to
FFFE
FFFF
000001
000002
to
065535
065536
-
0000
0001
to
FFFE
FFFF
100001
100002
to
165535
165536
-
0000
0001
to
FFFE
FFFF
300001
300002
to
365535
365536
0x06
0x10
0000
0001
to
FFFE
FFFF
400001
400002
to
465535
465536
0x15
0000
0001
to
270E
270F
600000
600001
to
609998
609999
Read
Write
0x01
0x05
0x0F
0x02
0x04
0x03
Extension file
register
Address
0x14
(2) Communication setting
When the MODBUS/RTU communication driver is
assigned to multiple channel numbers using the multichannel function, the following cases are possible. The
communication settings are shared between the
assigned multiple channel numbers, or the individual
communication setting is configured to a specific
channel number.
By setting the device GS579, either the GS device used
for sharing communication settings (GS570 to GS576)
or the GS device used for individual communication
setting (GS590 to GS617) is validated.
GS
device
Description
Set value
Bit0:
0
1
Bit1:
POINT
0
1
Address conversion example
When monitoring the holding register's address
"1234H", GT Designer3 displays "4*****" since GT
Designer3 processes the internal conversion in
decimal format as follows:
GT Designer3 converts the holding register's address
"1234H" to "04660" in decimal format.
Then, "+1" is added to this decimal address since the
holding register's address on GT Designer3 always
starts from "1."
Therefore, the holding register's address "1234H" is
displayed as "404661" on GT Designer3.
Holding register
1234H
GS579
Validity of
setting channel
number
Bit2:
0
1
Bit3:
0
1
Configure the Ch1 communication
settings between GS570 to
GS576.
Configure the Ch1 communication
settings between GS590 to
GS596.
Configure the Ch2 communication
settings between GS570 to
GS576.
Configure the Ch2 communication
settings between GS590 to
GS603.
Configure the Ch3 communication
settings between GS570 to
GS576.
Configure the Ch3 communication
settings between GS604 to
GS610
Configure the Ch4 communication
settings between GS570 to
GS576.
Configure the Ch4 communication
settings between GS611 to
GS617.
For details of GS devices (GS570 to GS576) and GS
devices (GS590 to GS617), refer to the next page.
PREPARATORY
PROCEDURES FOR
MONITORING
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Device name
This function is to prevent the communication response
delay that occurs because the devices on the
MODBUS network differs from each other in network
specification.
This function is effective for the MODBUS network
conditions as described below:
• When only a part of function codes is supported
(Example: "0F" is not supported)
• When the maximum transfer size of function code is
small (Example: The maximum number of coil read
times is 1000)
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
MODBUS/RTU Communication protocol
(1) Function overview
4
MODBUS(R)/RTU
CONNECTION
The table below shows the representations on the
MODBUS®/RTU communication protocol and GT
Designer3.
the GS device
5
MODBUS(R)/TCP
CONNECTION
GT Designer3 converts the device numbers into
decimal format according to the address map of the
MODBUS®/RTU equipment to be used.
1
6
CONNECTION TO
SOUND OUTPUT
UNIT
 MODBUS communication control function on
7
CONNECTION TO
EXTERNAL I/O
DEVICE
 Address
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
"4 04660" +1
"404661"
4. MODBUS(R)/RTU CONNECTION
4.5 MODBUS(R)/RTU Equipment Side Setting
4 - 15
(a) When sharing communication settings between multiple channel numbers
The table below shows the settings for the GS device.
GS device
Description
Set value
Bit0:
0
1
0
1
Using Function Code "0F"
Not using Function Code "0F"
Using Function Code "10"
Not using Function Code "10"
GS570
Command selection
GS571
Function Code "01"
Specification for the max. number of
coil read times
0:2000
1 to 2000: Specify the maximum number.
Other than above: 2000
GS572
Function Code "02"
Specification for the max. number of
input relay read times
0:2000
1 to 2000: Specify the maximum number.
Other than above: 2000
GS573
Function Code "03"
Specification for the max. number of
holding register read times
0:125
1 to 125: Specify the maximum number.
Other than above: 125
GS574
Function Code "04"
Specification for the max. number of
input register read times
0:125
1 to 125: Specify the maximum number.
Other than above: 125
GS575
Function Code "0F"
Specification for the max. number of
multiple-coil write times
0:800
1 to 1968: Specify the maximum number.
Other than above: 1968
When Bit0 of GS570 is "1", the function code "0F" is not
used, and therefore the setting of GS575 will be disabled.
GS576
Function Code "10"
Specification for the max. number of
multiple-holding register write times
0:100
1 to 123: Specify the maximum number.
Other than above: 123
When Bit1 of GS570 is "1", the function code "10F" is not
used, and therefore the setting of GS576 will be disabled.
Bit1:
(b) When configuring individual communication settings for specific channel numbers
The table below shows the settings for the GS device.
GS device
Ch1
Ch2
Ch3
Ch4
Description
Set value
Bit0:
Using Function Code "0F"
Not using Function Code "0F"
Using Function Code "10"
Not using Function Code "10"
GS590
GS597
GS604
GS611 Command selection
GS591
GS598
GS605
Function Code "01"
GS612 Specification for the max. number of
coil read times
0:2000
1 to 2000: Specify the maximum number.
Other than above: 2000
GS592
GS599
GS606
Function Code "02"
GS613 Specification for the max. number of
input relay read times
0:2000
1 to 2000: Specify the maximum number.
Other than above: 2000
GS593
GS600
GS607
Function Code "03"
GS614 Specification for the max. number of
holding register read times
0:125
1 to 125: Specify the maximum number.
Other than above: 125
GS594
GS601
GS608
Function Code "04"
GS615 Specification for the max. number of
input register read times
0:125
1 to 125: Specify the maximum number.
Other than above: 125
GS609
Function Code "0F"
GS616 Specification for the max. number of
multiple-coil write times
0:800
1 to 1968: Specify the maximum number.
Other than above: 1968
When Bit0 of GS570 is "1", the function code "0F" is not
used, and therefore the setting of GS575 will be disabled.
GS610
Function Code "10"
GS617 Specification for the max. number of
multiple-holding register write times
0:100
1 to 123: Specify the maximum number.
Other than above: 123
When Bit1 of GS570 is "1", the function code "10F" is not
used, and therefore the setting of GS576 will be disabled.
GS595
GS596
4 - 16
0
1
0
1
GS602
GS603
4. MODBUS(R)/RTU CONNECTION
4.5 MODBUS(R)/RTU Equipment Side Setting
Bit1:
1
PREPARATORY
PROCEDURES FOR
MONITORING
Station number setting
In the MODBUS network, a maximum of 31 MODBUS®/
RTU equipment can be connected to one GOT.
Assign a non-overlapped station number ranging from 1 to
247 arbitrarily to each MODBUS®/RTU equipment.
2
MICROCOMPUTER
CONNECTION
(SERIAL)
In the system configuration, the MODBUS®/RTU
equipment with the station number set with the host
address must be included.
The station number can be set without regard to the cable
connection order. There is no problem even if station
numbers are not consecutive.
Station
No.3
Station
No.15
Station
No.1
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
GOT
Examples of station number setting
4.6 Precautions
The GOT reads the holding registers (400001) for
checking whether the GOT can communicate with the
controller.
Therefore, if the equipment does not have holding
registers (400001), normal communication may not be
performed.
 MODBUS communication control function on
the GS device
At GOT startup, set MODBUS communication control
function with project scripts, etc.
If settings are changed after communication start, a
communication error may occur.
 Station No. settings of the MODBUS®/RTU
equipment side
In the system configuration, the MODBUS®/RTU
equipment with the station number set with the host
address must be included.For details of host address
setting, refer to the following.
CONNECTION TO
SOUND OUTPUT
UNIT
6
4.4.1 Setting communication interface
(Communication settings)
 GOT clock control
The settings of "time adjusting" or "time broadcast"
made on the GOT will be disabled on the PLC.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
 Disconnecting some of multiple connected
equipment
Setting example for project script
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
The GOT can disconnect some of multiple connected
equipment by setting GOT internal device. For
example, the faulty station where a communication
timeout error occurs can be disconnected from
connected equipment. For details of GOT internal
device setting, refer to the following manual.
5
MODBUS(R)/TCP
CONNECTION
 Reading the holding registers
4
MODBUS(R)/RTU
CONNECTION
4.5.2
GT Designer3 Version1 Screen Design Manual
4. MODBUS(R)/RTU CONNECTION
4.6 Precautions
4 - 17
4 - 18
4. MODBUS(R)/RTU CONNECTION
4.6 Precautions
5
PREPARATORY
PROCEDURES FOR
MONITORING
MICROCOMPUTER
CONNECTION
(SERIAL)
2
MODBUS(R)/TCP CONNECTION
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
5.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 2
4
MODBUS(R)/RTU
CONNECTION
5.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 2
5.3 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 3
5.4 MODBUS(R)/TCP Equipment Setting . . . . . . . . . . . . . . . . . 5 - 6
5.5 Device Range that Can Be Set . . . . . . . . . . . . . . . . . . . . . . 5 - 6
5
5.6 Example of Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 10
MODBUS(R)/TCP
CONNECTION
5.7 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 - 15
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
5.
1
5-1
5.
MODBUS(R)/TCP CONNECTION
5.1 Connectable Model List
For applicable MODBUS®/TCP equipment, refer to the following Technical News.
List of Valid Devices Applicable for GOT1000 Series with MODBUS Connection (GOT-A-0037)
Visit the Mitsubishi Electric FA Equipment Information Service website (MELFANSweb) to refer to the Technical News.
http://wwwf2.mitsubishielectric.co.jp/english/index.html
5.2 System Configuration
5.2.1
Connecting to MODBUS(R)/TCP equipment
MODBUS®/TCP
equipment
Connection cable
Controller
MODBUS
®
/TCP
equipment
Ethernet
Cable model
Twisted pair cable*4
• 10BASE-T
Shielded twisted pair
cable (STP) or
unshielded twisted
pair cable (UTP):
Category 3, 4, and 5
• 100BASE-TX
Shielded twisted pair
cable (STP):
Category 5 and 5e
GOT*2
Connection cable
Maximum
segment
External
device
Cable model
length*3
100m
Maximum
segment
length*3
Hub*1
Twisted pair cable*4
• 10BASE-T
Shielded twisted pair
cable (STP) or
unshielded twisted
pair cable (UTP):
Category 3, 4, and 5
• 100BASE-TX
Shielded twisted pair
cable (STP):
Category 5 and 5e
Option
device
- (Built into
GOT)
GOT
model
Number of
connectable
equipment
*6
Depends on the
MODBUS®/TCP
100m
GT15J71E71-100
equipment used.*5
*4
Connect the GOT to the MODBUS®/TCP equipment via a hub.
Use cables, connectors, and hubs that meet the IEEE802.3 10BASE-T/100BASE-TX standards.
When connecting GT16 to an equipment that meets the 10BASE (-T/2/5) standard, use the switching hub and operate in an
environment where 10Mbps and 100Mbps can be mixed.
A length between a hub and a node.
The maximum distance differs depending on the Ethernet device to be used.
The following shows the number of the connectable nodes when a repeater hub is used.
• 10BASE-T: Max. 4 nodes for a cascade connection (500m)
• 100BASE-TX: Max. 2 nodes for a cascade connection (205m)
When switching hubs are used, the cascade connection between the switching hubs has no logical limit for the number of
cascades.
For the limit, contact the switching hub manufacturer.
Use the straight cable.
*5
*6
For details, refer to the MODBUS®/TCP equipment manual.
GT14 models compatible with Ethernet connection are only GT1455-QTBDE and GT1450-QLBDE.
*1
*2
*3
5-2
Connection cable
Connection cable
Commun
ication
Type
GOT
Hub
5. MODBUS(R)/TCP CONNECTION
5.1 Connectable Model List
5.3.2
Communication detail settings
Make the settings according to the usage environment.
2.
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
3.
4.
Set the station No. of the GOT.
(Default: 1)
1 to 247
Set the IP address of the GOT.
(Default: 192.168.3.18)
0.0.0.0 to
255.255.255.255
Set the subnet mask for the sub
network.(Only for connection via
router)
If the sub network is not used, the
default value is set.
(Default: 255.255.255.0)
0.0.0.0 to
255.255.255.255
Set the router address of the
default gateway where the GOT is
connected.(Only for connection via
router)
(Default: 0.0.0.0)
0.0.0.0 to
255.255.255.255
Set the GOT port No. for Ethernet
download.
(Default: 5014)
1024 to 5010,
5014 to 65534
(Except for 5011,
5012, 5013 and
49153)
GOT
Communication
Port No.
Set the GOT port No. for the
connection with the Ethernet
module.
(Default: 5020)
1024 to 5010,
5014 to 65534
(Except for 5011,
5012, 5013 and
49153)
Startup Time
Specify the time period from the
GOT startup until GOT starts the
communication with the PLC CPU.
(Default: 3sec)
3 to 255sec
Timeout Time
Set the time period for a
communication to time out.
(Default: 3sec)
3 to 90sec
Delay Time
Set the delay time for reducing the
load of the network/destination
PLC.
(Default: 0ms)
32bit Storage
Select the steps to store two words
(32-bit data).
(Default: LH Order)
Subnet Mask*1
[Controller Setting] from the
Default
Gateway
*1
3.
4.
Set the following items.
• Manufacturer: MODBUS
• Controller Type: MODBUS
• I/F: Interface to be used
• Driver: MODBUS/TCP, Gateway
The detailed setting is displayed after Manufacturer,
Controller Type, I/F, and Driver are set.
Make the settings according to the usage
environment.
5.3.2 Communication detail settings
Ethernet
Download Port
No.*1
Click the [OK] button when settings are completed.
POINT
The settings of connecting equipment can be set and
confirmed in [I/F Communication Setting].For details,
refer to the following.
1.1.2 I/F communication setting
5. MODBUS(R)/TCP CONNECTION
5.3 GOT Side Settings
6
7
8
0 to 10000
(
5
CONNECTION TO
EXTERNAL I/O
DEVICE
GOT PLC No.
Click!
The Controller Setting window is displayed. Select the
channel to be used from the list menu.
4
1 to 239
IP Address*1
2.
Range
GOT NET No.
GOT
Select [Common]
menu.
Description
Set the network No. of the GOT.
(Default: 1)
MODBUS(R)/RTU
CONNECTION
Item
1.
2
MICROCOMPUTER
CONNECTION
(SERIAL)
(1) GT16, GT14
MODBUS(R)/TCP
CONNECTION
Set the channel of the equipment to be connected to the
GOT.
CONNECTION TO
SOUND OUTPUT
UNIT
Setting communication
interface (Communication
settings)
10 ms)
LH Order/HL Order
5-3
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
5.3.1
PREPARATORY
PROCEDURES FOR
MONITORING
1
5.3 GOT Side Settings
*1
Click the [Setting] button and perform the setting in the [GOT
IP Address Setting] screen.
Item
Description
Timeout Time
Set the time period for a
communication to time out.
(Default: 3sec)
Delay Time
Set the delay time for reducing the
load of the network/destination
PLC.
(Default: 0ms)
32bit Storage
Select the steps to store two words
(32-bit data).
(Default: LH Order)
Range
3 to 90sec
0 to 10000
(
10 ms)
LH Order/HL Order
POINT
(1) Communication interface setting by the Utility
The communication interface setting can be
changed on the Utility's [Communication setting]
after writing [Communication Settings] of project
data.
For details on the Utility, refer to the following
manual.
(2) GT15, GT12
User's Manual of GOT used.
(2) Precedence in communication settings
When settings are made by GT Designer3 or the
Utility, the latest setting is effective.
Item
Description
Range
GOT NET No.
Set the network No. of the GOT.
(Default: 1)
1 to 239
GOT PLC No.
Set the station No. of the GOT.
(Default: 1)
1 to 247
GOT
IP Address
Set the IP address of the GOT.
(Default: 192.168.0.18)
0.0.0.0 to
255.255.255.255
Subnet Mask
Set the subnet mask for the sub
network.(Only for connection via
router)
If the sub network is not used, the
default value is set.
(Default: 255.255.255.0)
0.0.0.0 to
255.255.255.255
Default
Gateway
Set the router address of the
default gateway where the GOT is
connected.(Only for connection via
router)
(Default: 0.0.0.0)
0.0.0.0 to
255.255.255.255
Ethernet
Download Port
No. *2 *3
Set the GOT port No. for Ethernet
download.
(Default: 5014)
1024 to 5010,
5014 to 65534
(Except for 5011,
5012, 5013 and
49153)
GOT
Communication
Port No.
Set the GOT port No. for the
connection with the Ethernet
module.
(Default: 5020)
1024 to 5010,
5014 to 65534
(Except for 5011,
5012, 5013 and
49153)
Startup Time
Specify the time period from the
GOT startup until GOT starts the
communication with the PLC CPU.
(Default: 3sec)
3 to 255sec
5-4
5. MODBUS(R)/TCP CONNECTION
5.3 GOT Side Settings
1
Ethernet setting
PREPARATORY
PROCEDURES FOR
MONITORING
5.3.3
Description
Range
Host
The host is displayed.(The host is
indicated with an asterisk (*).)
N/W No.
Set the network No. of the
connected Ethernet module.
(Default: blank)
1 to 239
PLC No.
Set the station No. of the
connected Ethernet module.
(Default: blank)
1 to 247
Type*1
MODBUS/TCP (fixed)
MODBUS/TCP
(fixed)
IP Address
Set the IP address of the
connected Ethernet module.
(Default: blank)
PLC side IP
address
Port No.
502 (fixed)
502 (fixed)
Communication
format
TCP (fixed)
TCP (fixed)
*1
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
―
4
MODBUS(R)/RTU
CONNECTION
Item
MICROCOMPUTER
CONNECTION
(SERIAL)
2
Select [MODBUS/TCP] for [Controller Type].
For the applicable Ethernet module, refer to the following.
5
MODBUS(R)/TCP
CONNECTION
5.2 System Configuration
POINT
Changing the host with GOT module (GT16, GT14
only)
The host can be changed by the GOT module Utility.
For details of settings, refer to the following.
6
CONNECTION TO
SOUND OUTPUT
UNIT
GT16 User's Manual (Basic Utility)
GT14 User's Manual
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
5. MODBUS(R)/TCP CONNECTION
5.3 GOT Side Settings
5-5
5.4 MODBUS(R)/TCP Equipment Setting
For details of the MODBUS®/TCP equipment, refer to the manual of MODBUS®/RTU equipment to be used.
5.5 Device Range that Can Be Set
The device ranges of controller that can be used for GOT are as follows.
Note that the device ranges in the following tables are the maximum values that can be set in GT Designer3.
The device specifications of controllers may differ depending on the models, even though belonging to the same series.
Please make the setting according to the specifications of the controller actually used.
When a non-existent device or a device number outside the range is set, other objects with correct device settings may
not be monitored.
 Setting item
Item
Device
Description
Set the device name, device number, and bit number.
The bit number can be set only when specifying the bit of word device.
File No.
Information
Set the file No.
The file No. can be set only when select 6 at [Device].
Displays the device type and setting range which are selected in [Device].
Set the station number of the controller to be monitored.
Host
Select this item for monitoring the host controller.
• For GT16, GT15
Select this for monitoring other controllers.
After selecting the item, set the station number and network number of the controller to be monitored.
Network
NW No.:
Other
5-6
For the MODBUS® /RTU connection, set "1".
For the MODBUS®/TCP connection, set the network No.
Station No.: Set the station No.
• For GT11, GT10
Select this for monitoring other controllers.
After selecting, set the station number of the controller to be monitored.
Station No.: Set the station No.
5. MODBUS(R)/TCP CONNECTION
5.4 MODBUS(R)/TCP Equipment Setting
Coils (0)
000001
to
065536
Discretes input (1)*1
100001
to
165536
Input registers (3)*1
300001
to
365536
400001
to
465536
to
609999
Decimal
Decimal
File No.: 0 to104
Extension file register (6)
600000
Only reading is possible.
POINT
(1) Range of coils and input relays that can be monitored
The device range of MODBUS equipment differs depending on the type.
When using types that the device range for coils and input relays are other than hexadecimal, monitoring to
the device maximum range may not be possible.
In this case, the device range extends to the last number divisible by 16.
Example: For a type whose coil device range is from 0 to 9999.
The range that can be actually monitored is from 0 to 9984.
(2) Address conversion example
When monitoring the holding register's address "1234H", GT Designer3 displays "4*****" since GT Designer3
processes the internal conversion in decimal format as follows:
GT Designer3 converts the holding register's address "1234H" to "04660" in decimal format.
Then, "+1" is added to this decimal address since the holding register's address on GT Designer3 always
starts from "1."
Therefore, the holding register's address "1234H" is displayed as "404661" on GT Designer3.
4
5
1234H
MODBUS(R)/TCP
CONNECTION
Holding register
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
MODBUS(R)/RTU
CONNECTION
*1
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Holding registers (4)
1
PREPARATORY
PROCEDURES FOR
MONITORING
Device No.
representation
Setting range
"4 04660" +1
6
CONNECTION TO
SOUND OUTPUT
UNIT
"404661"
CONNECTION TO
EXTERNAL I/O
DEVICE
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Word device
Bit device
Device name
5. MODBUS(R)/TCP CONNECTION
5.5 Device Range that Can Be Set
5-7
 MODBUS communication control function on the GS device
(1) Function overview
This function is to prevent the communication response delay that occurs because the devices on the MODBUS
network differ from each other in network specification.
This function is effective for the MODBUS network conditions as described below:
When only a part of function codes is supported (Example: "0F" is not supported)
When the maximum transfer size of function code is small (Example: The maximum number of coil read times is
1000)
(2) Communication setting
When the MODBUS®/TCP communication driver is assigned to multiple channel numbers using Ethernet
multiple connection, the following cases are possible. The communication settings are shared between the
assigned multiple channel numbers, or the individual communication setting is configured for a specific channel
number.
By setting the device GS579, either the GS device used for sharing communication settings (GS570 to GS576)
or the GS device used for individual communication setting (GS590 to GS617) is validated.
GS device
Description
Set value
Bit0:
Bit1:
GS579
Validity of setting channel
number
Bit2:
Bit3:
0
Configure the Ch1 communication settings
between GS570 to GS576.
1
Configure the Ch1 communication settings
between GS590 to GS596.
0
Configure the Ch2 communication settings
between GS570 to GS576.
1
Configure the Ch2 communication settings
between GS590 to GS603.
0
Configure the Ch3 communication settings
between GS570 to GS576.
1
Configure the Ch3 communication settings
between GS604 to GS610
0
Configure the Ch4 communication settings
between GS570 to GS576.
1
Configure the Ch3 communication settings
between GS611 to GS617.
For details of GS devices (GS570 to GS576) and GS devices (GS590 to GS617), refer to the next page.
5-8
5. MODBUS(R)/TCP CONNECTION
5.5 Device Range that Can Be Set
1
Set value
Using Function Code "0F"
Not using Function Code "0F"
Using Function Code "10"
Not using Function Code "10"
GS570
Command selection
GS571
Function Code "01"
Specification for the max. number of
coil read times
0:1000
1 to 2000: Specify the maximum number.
Other than above: 2000
GS572
Function Code "02"
Specification for the max. number of
input relay read times
0:1000
1 to 2000: Specify the maximum number.
Other than above: 2000
GS573
Function Code "03"
Specification for the max. number of
holding register read times
0:125
1 to 125: Specify the maximum number.
Other than above: 125
GS574
Function Code "04"
Specification for the max. number of
input register read times
0:125
1 to 125: Specify the maximum number.
Other than above: 125
GS575
Function Code "0F"
Specification for the max. number of
multiple-coil write times
0:800
1 to 800: Specify the maximum number.
Other than above: 800
When Bit0 of GS570 is "1", the function code "0F" is not used,
and therefore the setting of GS575 will be disabled.
GS576
Function Code "10"
Specification for the max. number of
multiple-holding register write times
0:100
1 to 100: Specify the maximum number.
Other than above: 100
When Bit1 of GS570 is "1", the function code "10F" is not
used, and therefore the setting of GS576 will be disabled.
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Bit1:
3
MICROCOMPUTER
CONNECTION
(ETHERNET)
0
1
0
1
4
MODBUS(R)/RTU
CONNECTION
Bit0:
(b) When configuring individual communication settings for specific channel numbers
The table below shows the settings for the GS device.
Ch2
Ch3
Ch4
Description
5
Set value
Bit0:
0
1
0
1
Using Function Code "0F"
Not using Function Code "0F"
Using Function Code "10"
Not using Function Code "10"
MODBUS(R)/TCP
CONNECTION
GS device
Ch1
GS590
GS597
GS604
GS611 Command selection
GS591
GS598
GS605
Function Code "01"
GS612 Specification for the max. number of
coil read times
0:1000
1 to 2000: Specify the maximum number.
Other than above: 2000
GS592
GS599
GS606
Function Code "02"
GS613 Specification for the max. number of
input relay read times
0:1000
1 to 2000: Specify the maximum number.
Other than above: 2000
GS593
GS600
GS607
Function Code "03"
GS614 Specification for the max. number of
holding register read times
0:125
1 to 125: Specify the maximum number.
Other than above: 125
GS594
GS601
GS608
Function Code "04"
GS615 Specification for the max. number of
input register read times
0:125
1 to 125: Specify the maximum number.
Other than above: 125
GS609
Function Code "0F"
GS616 Specification for the max. number of
multiple-coil write times
0:800
1 to 800: Specify the maximum number.
Other than above: 800
When Bit0 of GS570 is "1", the function code "0F" is not
used, and therefore the setting of GS575 will be disabled.
GS610
Function Code "10"
GS617 Specification for the max. number of
multiple-holding register write times
0:100
1 to 100: Specify the maximum number.
Other than above: 100
When Bit1 of GS570 is "1", the function code "10F" is not
used, and therefore the setting of GS576 will be disabled.
GS595
GS596
GS602
GS603
5. MODBUS(R)/TCP CONNECTION
5.5 Device Range that Can Be Set
6
CONNECTION TO
SOUND OUTPUT
UNIT
Bit1:
5-9
7
CONNECTION TO
EXTERNAL I/O
DEVICE
Description
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
GS device
PREPARATORY
PROCEDURES FOR
MONITORING
(a) When sharing communication settings between multiple channel numbers
The table below shows the settings for the GS device.
5.6 Example of Connection
5.6.1
Connecting to SCHNEIDER PLC (Modicon Premium series and Modicon
Quantum series)
 System Configuration
Communication driver
MODBUS/TCP
SCHNEIDER
PLC
Ethernet
module
GOT
Hub
Connection cable
controller
Modicon
Premium
Series
Ethernet
module
*4
Communi
cation
Type
TSX ETY 4102
TSX ETY 5102
Ethernet
Modicon
Quantum
Series
140 NOE 771 00
140 NOE 771 10
140 NWM 100 00
*1
*2
*3
*4
*5
*6
Connection cable
Cable model
*5
Twisted pair cable
• 10BASE-T
Shielded twisted
pair cable (STP)
or unshielded
twisted pair
cable (UTP):
Category 3, 4,
and 5
• 100BASE-TX
Shielded twisted
pair cable (STP):
Category 5 and
5e
Max.
distance
100m*3
Connection cable
External
device
Hub*1
Connection cable
Cable model
Twisted pair cable
• 10BASE-T
Shielded twisted
pair cable (STP)
or unshielded
twisted pair
cable (UTP):
Category 3, 4,
and 5
• 100BASE-TX
Shielded twisted
pair cable (STP):
Category 5 and
5e
Max.
distance
Option device
- (Built into GOT)
GOT
model
Number of
connectable
equipment
*6
64 GOTs
for 1 PLC
100m*3
GT15-J71E71-100
Connect the GOT to the Ethernet module via a hub.
Use cables, connectors, and hubs that meet the IEEE802.3 10BASE-T/100BASE-TX standards.
When connecting GT16 to an equipment that meets the 10BASE (-T/2/5) standard, use the switching hub and operate in an
environment where 10Mbps and 100Mbps can be mixed.
A length between a hub and a node.
The maximum distance differs depending on the Ethernet device to be used.
The following shows the number of the connectable nodes when a repeater hub is used.
• 10BASE-T: Max. 4 nodes for a cascade connection (500m)
• 100BASE-TX: Max. 2 nodes for a cascade connection (205m)
When switching hubs are used, the cascade connection between the switching hubs has no logical limit for the number of
cascades.
For the limit, contact the switching hub manufacturer.
Product manufactured by SCHNEIDER ELECTRIC SA.For details of the product, contact SCHNEIDER ELECTRIC SA.
Use the straight cable.
GT14 models compatible with Ethernet connection are only GT1455-QTBDE and GT1450-QLBDE.
 PLC Side Setting
POINT
SCHNEIDER ELECTRIC PLC
For details of SCHNEIDER PLC, refer to the following manual.
SCHNEIDER PLC user's Manual
5 - 10
*5
GOT*2
5. MODBUS(R)/TCP CONNECTION
5.6 Example of Connection
1
PREPARATORY
PROCEDURES FOR
MONITORING
(1) Parameter settings
Set the parameter settings with programming software for SCHNEIDER PLC.
(a) For Modicon Premium series
Set for PL7 Pro programming software.
Item
Processors
Memory cards
2
Memory card to be used
Connected Ethernet module
IP Address
MICROCOMPUTER
CONNECTION
(SERIAL)
Module
Set value
Connected CPU module
IP address for Ethernet module
Size of global address
fields
Setting for device points
Bits: Coil, Input
Words: Input register, Maintenance register
(b) For Modicon Quantum series
Set for Concept programming software.
MICROCOMPUTER
CONNECTION
(ETHERNET)
IP address for Ethernet module
4
MODBUS(R)/RTU
CONNECTION
Internet Address
Numbers of unit
Connected Ethernet module
5
MODBUS(R)/TCP
CONNECTION
I/O Module Selection
Connected CPU module
6
CONNECTION TO
SOUND OUTPUT
UNIT
TCP/IP Ethernet
7
CONNECTION TO
EXTERNAL I/O
DEVICE
PLC Selection
Set value
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Item
3
5. MODBUS(R)/TCP CONNECTION
5.6 Example of Connection
5 - 11
5.6.2
Connecting to YOKOGAWA PLC (STARDOM)
 System Configuration
Communication driver
MODBUS/TCP
YOKOGAWA
PLC
Connection cable
controller
STARDOM*1
(NFCP100,
NFJT100)
Communic
ation Type
Ethernet
*1
*2
*3
*4
*5
*6
GOT
Hub
Connection cable
Cable model*5
Twisted pair cable
• 10BASE-T
Shielded twisted
pair cable (STP) or
unshielded twisted
pair cable (UTP):
Category 3, 4, and
5
• 100BASE-TX
Shielded twisted
pair cable (STP):
Category 5 and 5e
Max.
distance
Connection cable
External
device
100m*4
Hub*2
Connection cable
Cable model*5
Twisted pair cable
• 10BASE-T
Shielded twisted
pair cable (STP) or
unshielded twisted
pair cable (UTP):
Category 3, 4, and
5
• 100BASE-TX
Shielded twisted
pair cable (STP):
Category 5 and 5e
Max.
distance
GOT*3
Option device
- (Built into GOT)
GOT
Model
Number of
connectable
equipment
*6
126 GOTs
for 1 PLC
100m*4
GT15-J71E71-100
When connecting STARDOM to MODBUS®/TCP, Modbus Communication Portfolio License is required.
For details, refer to the following manual.
YOKOGAWA PLC user's Manual
When connect a GOT to a PLC, connect to the PCL Ethernet port via a hub.
Use cables, connectors, and hubs that meet the IEEE802.3 10BASE-T/100BASE-TX standards.
When connecting GT16 to an equipment that meets the 10BASE (-T/2/5) standard, use the switching hub and operate in an
environment where 10Mbps and 100Mbps can be mixed.
A length between a hub and a node.
The maximum distance differs depending on the Ethernet device to be used.
The following shows the number of the connectable nodes when a repeater hub is used.
• 10BASE-T: Max. 4 nodes for a cascade connection (500m)
• 100BASE-TX: Max. 2 nodes for a cascade connection (205m)
When switching hubs are used, the cascade connection between the switching hubs has no logical limit for the number of
cascades.
For the limit, contact the switching hub manufacturer.
Use the straight cable.
GT14 models compatible with Ethernet connection are only GT1455-QTBDE and GT1450-QLBDE.
 PLC Side Setting
Make the communication settings as shown below. For details of the communication settings, refer to the following
manual.
Peripheral Software Manual for YOKOGAWA PLC
POINT
Connection between STARDOM and the PC for communication settings
For the communication settings of STARDOM, STARDOM and the PC for communication settings must be
connected to Ethernet using the Resource Configurator (peripheral software).
5 - 12
5. MODBUS(R)/TCP CONNECTION
5.6 Example of Connection
To set the communication settings for STARDOM, an installation of Modbus Communication Portfolio License is
required.
For details of the communication settings, refer to the following manual.
STARDOM FCN/FCJ Guide
(2) Defining Logic POU
2
Define Logic POU using Logic Designer (peripheral software), and download the project to STARDOM.
MICROCOMPUTER
CONNECTION
(SERIAL)
(a) Start Logic Designer and create a new project using a template.
Use [STARDOM Serial Communication] template.
(b) Insert Firmware Library to the new project.
• Right-click [Library] under the project tree in Logic Designer.
• Right-click [Insert] and select [Firmware Library].
• Double-click the [SD_FCXPLCE_LIB] folder and double-click [SD_FCXPLCE_LIB.fwl] to select it.
• The library path inserted in the procedures above is as follows.
{Install Folder}\LogicDesigner\Mwt\Plc\Fw_lib\SD_FCXPLCE_LIB\SD_FCXPLCE_LIB.fwl
(d) Copy a sample project POU to the new project.
• Open "SD_CMODBUSE_Sample1.mwt".
• Right-click [ComEServerModbus*] in the Logic POU under the project tree in the
SD_CMODBUSE_Sample1 project, and select [Copy].
• Right-click the [Logic POU] under the project tree in the previously created project, and select [Paste].
• Double-click the [ComEServerModbus*] file in the [ComEServerModbus*] folder.
• For the following terminals, set as shown below.
4
MODBUS(R)/RTU
CONNECTION
Insert User Library to the new project.
• Right-click [Library] under the project tree in Logic Designer.
• Right-click [Insert] and select [User Library].
• Double-click [SD_CMODBUSE_PF.mwt], [SD_CUTIL_PF.mwt] and [SD_CMODBUSS_PF.mwt] to
select it.
(When [STARDOM Serial Communication] is used for the template, [SD_CUTIL_PF.mwt] is inserted as
default.)
• The library path inserted in the procedures above is as follows.
{Install Folder}\LogicDesigner\Libraries\SD_CMODBUSE_PF.mwt
{Install Folder}\LogicDesigner\Libraries\SD_CUTIL_PF.mwt
{Install Folder}\LogicDesigner\Libraries\SD_CMODBUSS_PF.mwt
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
5
MODBUS(R)/TCP
CONNECTION
(c)
PREPARATORY
PROCEDURES FOR
MONITORING
1
(1) Modbus Communication Portfolio License
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
5. MODBUS(R)/TCP CONNECTION
5.6 Example of Connection
5 - 13
(e) Set devices to be monitored by a GOT.
• Right-click the [ComEServerModbus*] file in the [ComEServerModbus*] folder in the logic POU under
the project tree and select [Insert] - [Cord worksheet].
• Set the variable devices to be monitored.
Instantiate Logic POU.Define an already defined instance to Task0.
• Right-click [Physical hardware] - [Configuration:IPC_33/FCX01:FCX/Tasks/Task0:CYCLIC] and select
[Insert] - [Program instance].
• Define the program instance name and select ComEServerModbus for the program type.
(f)
Defining Target Setting
Define the IP address of STARDOM to set the communication settings.
Double-click [Physical hardware] - [Configuration:IPC_33/FCX01:FCX/Target Setting] and input the IP
address or the host name.
(g) Downloading the project
• Execute [Build] - [Make].
(Same as when pressing the function key F9).
• Download after confirming that the compile error does not occur. Select [Download] in the project control
dialog displayed when [Online] - [Project control] is selected.
• When the download is completed, select [Cold] and start STARDOM.
 Device range
When performing monitoring with the GOT connected to a YOKOGAWA PLC and setting devices for objects, use
devices within the device range of the YOKOGAWA PLC.
When a device outside the range is set on an object, an indefinite value is displayed on the object.
(No error is displayed in the system alarm.)
For details on the device range of YOKOGAWA PLCs, refer to the following manual:
YOKOGAWA PLC user's Manual
 Precautions
(1) For dual-redundant configuration
When STARDOM is configured with a redundant system, the connection is not supported.
(2) Not communicating with GOT and STARDOM in a specified period
When the GOT does not communicate with STARDOM in a specified period during the GOT is turned on,
STARDOM disconnects the line for the GOT. As the line is disconnected, the GOT displays an error when the
GOT monitors STARDAM after the disconnection.
After the error displayed as the system alarm (No.402: timeout error) on the GOT, the normal communication is
recovered and the GOT can monitor STARDOM.
5 - 14
5. MODBUS(R)/TCP CONNECTION
5.6 Example of Connection
(1) Setting PLC No.
When connecting two or more GOTs in the MODBUS®/
TCP network, set each [PLC No.] to the GOT.
5.3.1 Setting communication interface
(Communication settings)
 MODBUS communication control function on
the GS device
At GOT startup, set MODBUS communication control
function with project scripts, etc.
If settings are changed after communication start, a
communication error may occur.
(2) Setting IP address
Do not use the IP address "192.168.0.18" when using
multiple GOTs.
A communication error may occur on the GOT with the
IP address.
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
 When setting IP address
Do not use "0" and "255" at the end of an IP address.
(Numbers of *.*.*.0 and *.*.*.255 are used by the
system)
The GOT may not monitor the controller correctly with
the above numbers.
4
MODBUS(R)/RTU
CONNECTION
Consult with the administrator of the network before
setting an IP address to the GOT and controller.
 When connecting to the multiple network
equipment (including GOT) in a segment
By increasing the network load, the transmission speed
between the GOT and PLC may be reduced.
2
MICROCOMPUTER
CONNECTION
(SERIAL)
 When connecting to multiple GOTs
PREPARATORY
PROCEDURES FOR
MONITORING
1
5.7 Precautions
5
Setting example for project script
MODBUS(R)/TCP
CONNECTION
The following actions may improve the communication
performance.
• Using a switching hub
• More high speed by 100BASE-TX (100Mbps)
• Reduction of the monitoring points on GOT
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
5. MODBUS(R)/TCP CONNECTION
5.7 Precautions
5 - 15
5 - 16
5. MODBUS(R)/TCP CONNECTION
5.7 Precautions
CONNECTIONS TO PERIPHERAL
EQUIPMENT
6.
CONNECTION TO SOUND OUTPUT UNIT . . . . . . . . . . . . 6 - 1
7.
CONNECTION TO EXTERNAL I/O DEVICE . . . . . . . . . . . . 7 - 1
8.
FINGERPRINT AUTHENTICATION DEVICE CONNECTION
............................................... 8-1
9.
BAR CODE READER CONNECTION . . . . . . . . . . . . . . . . . 9 - 1
10. PC REMOTE CONNECTION. . . . . . . . . . . . . . . . . . . . . . . 10 - 1
11.
VNC(R) SERVER CONNECTION . . . . . . . . . . . . . . . . . . . .11 - 1
12. VIDEO/RGB CONNECTION . . . . . . . . . . . . . . . . . . . . . . . 12 - 1
13. PRINTER CONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . 13 - 1
14. MULTIMEDIA CONNECTION . . . . . . . . . . . . . . . . . . . . . . 14 - 1
15. RFID CONNECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 - 1
6
PREPARATORY
PROCEDURES FOR
MONITORING
1
MICROCOMPUTER
CONNECTION
(SERIAL)
2
CONNECTION TO SOUND
OUTPUT UNIT
6.
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
4
MODBUS(R)/RTU
CONNECTION
6.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 2
6.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 2
6.3 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 3
5
MODBUS(R)/TCP
CONNECTION
6.4 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 - 4
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
6-1
6.
CONNECTION TO SOUND OUTPUT
UNIT
6.1 Connectable Model List
For applicable speakers, refer to the following Technical News.
List of valid devices applicable for GOT1000 series (GOT-A-0010)
Visit the Mitsubishi Electric FA Equipment Information Service website (MELFANSweb) to refer to the Technical News.
http://wwwf2.mitsubishielectric.co.jp/english/index.html
6.2 System Configuration
6.2.1
Connecting to sound output unit
Extended function OS
Connection type
dependent
Sound output
Speaker
GOT
Communication driver
PLC
Connection cable
Varies according to
the speaker's specifications.
Speaker
Model name
Varies according to
the connection type.
GOT
Connection cable
For applicable speakers, refer to the following Technical News.
List of valid devices applicable for GOT1000 series (GOT-A-0010)
Option device
Model
GT15-SOUT
HINT
System configuration between the GOT and PLC
For the system configuration between the GOT and PLC, refer to each chapter.
Mitsubishi Products
Non-Mitsubishi Products 1, Non-Mitsubishi Products 2
Microcomputer, MODBUS Products, Peripherals
6-2
6. CONNECTION TO SOUND OUTPUT UNIT
6.1 Connectable Model List
PLC
For the system
configuration
between the GOT
and PLC, refer to
each chapter.
Number of
connectable
equipment
1 speaker for 1
GOT
1
6.3.1
Setting communication
interface
PREPARATORY
PROCEDURES FOR
MONITORING
6.3 GOT Side Settings
 Sound output unit setting
 Controller setting
2.
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Set the channel of the equipment to be connected to
the GOT.
2.
Click!
3.
4.
1.
2.
Select [Common]
[Peripheral Setting]
[Sound Output] from the menu.
Set the interface to which the sound output unit is
connected.
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
4
2.
3.
4.
Select [Common]
menu.
[Controller Setting] from the
The Controller Setting window is displayed. Select the
channel to be used from the list menu.
Set Manufacturer, Controller Type, I/F, and Driver
according to the connected equipment to be used.
(1) Communication interface setting by the Utility
The communication interface setting can be
changed on the Utility's [Communication setting]
after writing [Communication Settings] of project
data.
For details on the Utility, refer to the following
manual.
User's Manual of GOT used.
(2) Precedence in communication settings
When settings are made by GT Designer3 or the
Utility, the latest setting is effective.
The detailed setting is displayed after Manufacturer,
Controller Type, I/F, and Driver are set.
Make the settings according to the usage
environment.
5
6
CONNECTION TO
SOUND OUTPUT
UNIT
1.
POINT
MODBUS(R)/TCP
CONNECTION
Click!
MODBUS(R)/RTU
CONNECTION
Click the [OK] button when settings are completed.
Click the [OK] button when settings are completed.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
POINT
The settings of connecting equipment can be set and
confirmed in [II/F Communication Setting]. For details,
refer to the following.
1.1.2 I/F communication setting
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
6. CONNECTION TO SOUND OUTPUT UNIT
6.3 GOT Side Settings
6-3
6.4 Precautions
 Sound output function setting on GT
Designer3
Before connecting the sound output unit, make the
sound output file setting.
For details, refer to the following manual.
GT Designer3 Version1 Screen Design Manual
6-4
6. CONNECTION TO SOUND OUTPUT UNIT
6.4 Precautions
7
PREPARATORY
PROCEDURES FOR
MONITORING
1
MICROCOMPUTER
CONNECTION
(SERIAL)
2
CONNECTION TO EXTERNAL I/O
DEVICE
7.
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
4
MODBUS(R)/RTU
CONNECTION
7.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 2
7.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 2
7.3 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 4
5
7.4 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 12
MODBUS(R)/TCP
CONNECTION
7.5 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 - 13
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
7-1
7.
CONNECTION TO EXTERNAL I/O
DEVICE
7.1 Connectable Model List
The following table shows the connectable models.
Series
Clock
External I/O device
*1
*1
Refer to
7.2.1
Varies with the connected type.
7.2 System Configuration
7.2.1
Connecting to the external I/O device
 When only inputting
Extended function OS
External I/O /Operation panel
Operation panel
GOT
Connection cable
DC power supply
Connection cable*1
External device
Name
Operation panel
*1
*2
7-2
GOT*2
Connection diagram number
Connection diagram number
Option device
Connection diagram 2)
Connection diagram 1)
GT15-DIO
Connection diagram 4)
Connection diagram 3)
GT15-DIOR
Model
The power supply of 24VDC must be applied for the external I/O unit.
When the power supply of the external I/O unit is stopped in the operation, the operation panel becomes nonfunctional.
For using the operation panel again, reset the GOT after supplying the power to the external I/O unit.
When starting, turn on the external power supply to the external I/O unit and turn on the GOT.
When turning off the external power supply, a system alarm occurs.
When a system alarm is generated, input/output cannot be performed.
In this case, turn on the main power of the GOT or reset the GOT.
(When bus connection is used, the reset switch on the GOT does not function.)
7. CONNECTION TO EXTERNAL I/O DEVICE
7.1 Connectable Model List
Extended function OS
External I/O /Operation panel
General input device
(Push button,etc.)
MICROCOMPUTER
CONNECTION
(SERIAL)
2
Operation panel
Connector/terminal
block convertor
module
Connection cable 1)
3
GOT
MICROCOMPUTER
CONNECTION
(ETHERNET)
Connection cable 2)
General output device
(Lamp, relay)
PREPARATORY
PROCEDURES FOR
MONITORING
1
 When inputting and outputting
Connection cable 1)
DC power supply
Connection diagram
number
Connection
diagram 7)
Connection
diagram 8)
Connection
General output device
(Lamp, relay)
diagram 9)
Connection
diagram 10)
*1
*2
*3
A6TBY54-Es
Connection diagram 8)
A6TBY36-E
Connection diagram 9)
A6TBY54-Es
Connection diagram 10)
Connection
diagram 5)
Connection
diagram 6)
Option device
Model
GT15-DIO
5
GT15-DIOR
The power supply of 24VDC must be applied for the external I/O unit.
When the power supply of the external I/O unit is stopped in the operation, the operation panel becomes nonfunctional.
For using the operation panel again, reset the GOT after supplying the power to the external I/O unit.
When the connector/terminal block converter module is used, the maximum input points are 64 points.
When starting, turn on the external power supply to the external I/O unit and turn on the GOT.
When turning off the external power supply, a system alarm occurs.
When a system alarm is generated, input/output cannot be performed.
In this case, turn on the main power of the GOT or reset the GOT.
(When bus connection is used, the reset switch on the GOT does not function.)
6
CONNECTION TO
SOUND OUTPUT
UNIT
Operation panel
A6TBY36-E
Connection diagram 7)
Connection diagram
number
7
CONNECTION TO
EXTERNAL I/O
DEVICE
General input device
(Push button, etc.)
module*1*2
GOT*3
Connection cable 2)
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
Name
Connector/terminal block converter
MODBUS(R)/TCP
CONNECTION
Connection cable 1)
MODBUS(R)/RTU
CONNECTION
4
7. CONNECTION TO EXTERNAL I/O DEVICE
7.2 System Configuration
7-3
7.3 Connection Diagram
7.3.1
Connection cable between
external I/O unit and operation
panel
Connection diagram 2)
For 16-point input
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
XD08
XD09
XD0A
XD0B
XD0C
XD0D
XD0E
XD0F
The connection cable between the external I/O unit and the
operation panel must be prepared by the user referring to
the followings.
 For GT15-DIO
Connection diagram 1)
External I/O unit side
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
XD08
XD09
XD0A
XD0B
XD0C
XD0D
XD0E
XD0F
XSCN00
XSCN01
XSCN02
XSCN03
XSCN04
XSCN05
XSCN06
XSCN07
YD00
YD01
YD02
YD03
YD04
YD05
YD06
YD07
YD08
YD09
YD0A
YD0B
YD0C
YD0D
YD0E
YD0F
RUN
DC24V
DC24V
DC24V
DC24V
COM
COM
COM
COM
N.C.
7-4
Original operation panel
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
XD08
XD09
XD0A
XD0B
XD0C
XD0D
XD0E
XD0F
XSCN00
XSCN01
XSCN02
XSCN03
XSCN04
XSCN05
XSCN06
XSCN07
18
43
19
44
20
45
21
46
22
47
23
48
24
49
25
50
14
39
15
40
16
41
17
42
XSCN00
XSCN01
XSCN02
XSCN03
XSCN04
XSCN05
XSCN06
XSCN07
For 128-point input*1
X070
X060
X050
X040
X030
X020
X010
X000
XD00
X001
X002
X003
X004
X005
X006
X007
X008
6
X009
31
X00A
7
X00B
32
X00C
8
33
X00D
9
X00E
34
X00F
10
XD01
XD02
XD03
XD04
XD05
XD06
XD07
XD08
XD09
XD0A
XD0B
XD0C
XD0D
XD0E
XD0F
35
11
XSCN00
36
XSCN01
12
XSCN02
37
13
38
XSCN03
Cable for connecting an external
input power supply
XSCN04
30
XSCN05
4
XSCN06
3
2
XSCN07
DC24V
*2
1
29
28
27
*1
26
5
*2
7. CONNECTION TO EXTERNAL I/O DEVICE
7.3 Connection Diagram
The 128-point input can be executed with using a 16-point
input signal (XD00 to XD0F) with an 8-point scan signal
(XSCN00 to XSCN07).
When two or more switches are pressed simultaneously, be
sure to put the diode to each switch. (Only for 128-point
input)
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
XD08
XD09
XD0A
XD0B
XD0C
XD0D
XD0E
XD0F
44
20
45
21
46
22
47
23
48
24
49
25
50
14
39
15
40
16
41
17
42
XSCN00
XSCN01
XSCN02
XSCN03
XSCN04
XSCN05
XSCN06
XSCN07
X070
X060
X050
X040
X030
X020
X010
4
X000
XD00
X001
6
X002
7
X003
32
X004
8
X005
33
X006
9
X007
34
10
X008
35
X009
11
X00A
36
X00B
12
X00C
37
38
3
For 128-point input*1
31
13
2
MICROCOMPUTER
CONNECTION
(ETHERNET)
19
Cable for connecting an external
input power supply
X00D
X00E
30
X00F
4
XD01
MODBUS(R)/RTU
CONNECTION
43
XD02
XD03
XD04
XD05
XD06
5
XD07
XD08
XD09
MODBUS(R)/TCP
CONNECTION
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
XD08
XD09
XD0A
XD0B
XD0C
XD0D
XD0E
XD0F
XSCN00
XSCN01
XSCN02
XSCN03
XSCN04
XSCN05
XSCN06
XSCN07
18
MICROCOMPUTER
CONNECTION
(SERIAL)
Original operation panel
XD0A
XD0B
XD0C
XD0D
XD0E
6
XD0F
XSCN00
DC24V
1
XSCN01
29
XSCN02
28
XSCN03
27
XSCN04
26
XSCN05
5
7
XSCN06
XSCN07
*2
*1
*2
The 128-point input can be executed with using a 16-point
input signal (XD00 to XD0F) with an 8-point scan signal
(XSCN00 to XSCN07).
When two or more switches are pressed simultaneously, be
sure to put the diode to each switch. (Only for 128-point
input)
7. CONNECTION TO EXTERNAL I/O DEVICE
7.3 Connection Diagram
7-5
CONNECTION TO
EXTERNAL I/O
DEVICE
2
CONNECTION TO
SOUND OUTPUT
UNIT
3
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
XD08
XD09
XD0A
XD0B
XD0C
XD0D
XD0E
XD0F
XSCN00
XSCN01
XSCN02
XSCN03
XSCN04
XSCN05
XSCN06
XSCN07
YD00
YD01
YD02
YD03
YD04
YD05
YD06
YD07
YD08
YD09
YD0A
YD0B
YD0C
YD0D
YD0E
YD0F
RUN
DC24V
DC24V
DC24V
DC24V
0V
0V
0V
0V
N.C.
PREPARATORY
PROCEDURES FOR
MONITORING
For 16-point input
Connection diagram 3)
External I/O unit side
1
Connection diagram 4)
 For GT15-DIOR
7.3.2
 Connector specifications
1) 2) 4)
24VDC
power supply
3)
Connection cable between
external I/O unit and
connector/terminal block
converter module
Any connector
selected by the user
The connection cable between the external I/O unit and the
connector/terminal block converter module must be
prepared by the user referring to the followings.
No.
1)
2)
3)
4)
Name
Model name
Manufacturer
PCR-E50FS+
(GT15-DIO)
Connector
PCS-E50FS+
(GT15-DIOR)
Connector
cover
PCS-E50LA
Cable
UL 2464 AWG28 or
equivalent
Cable for
connecting an
external input
power supply
Connection diagram 5)
External I/O unit side
Honda Tsushin Kogyo
Co., Ltd.
UL 1007 AWG24 or
equivalent
───
───
 Precautions when preparing a cable
(1) Cable length
Maximum cable length differs depending on the cable
used.Make the cable length within the range that can
satisfy the I/O specifications of the external I/O unit.
(2) GOT side connector
For the GOT side connector, refer to the following.
1.4.1 GOT connector specifications
7-6
 For GT15-DIO
7. CONNECTION TO EXTERNAL I/O DEVICE
7.3 Connection Diagram
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
XD08
XD09
XD0A
XD0B
XD0C
XD0D
XD0E
XD0F
XSCN00
XSCN01
XSCN02
XSCN03
XSCN04
XSCN05
XSCN06
XSCN07
YD00
YD01
YD02
YD03
YD04
YD05
YD06
YD07
YD08
YD09
YD0A
YD0B
YD0C
YD0D
YD0E
YD0F
RUN
DC24V
DC24V
DC24V
DC24V
COM
COM
COM
COM
N.C.
Terminal block converter side
18
B20
43
A20
19
B19
44
A19
20
B18
45
A18
21
B17
46
A17
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
22
47
23
48
24
49
25
50
14
B16
39
A16
15
B15
40
A15
16
B14
41
A14
17
B13
42
A13
6
B12
31
A12
7
B11
32
A11
8
B10
33
A10
9
B9
34
A9
10
B8
35
A8
11
B7
36
A7
12
B6
37
A6
13
B5
38
A5
XSCN00
XSCN01
XSCN02
XSCN03
XSCN04
XSCN05
XSCN06
XSCN07
YD00
YD01
YD02
YD03
YD04
YD05
YD06
YD07
YD08
YD09
YD0A
YD0B
YD0C
YD0D
YD0E
YD0F
30
4
B4
3
A4
2
B3
24V
24V
24V
1
29
A3
28
B2
27
A2
26
B1
5
A1
0V
0V
Empty
Empty
Empty
5)
3) 4)
Terminal block converter side
A20
19
B19
44
A19
20
B18
45
A18
21
B17
46
A17
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
2
22
47
Name
48
24
49
1)
Connector
2)
Connector
cover
PCS-E50LA
3)
4)
Connector
(with a cover)
A6CON1
5)
Connector
FCN-361J040-AU
6)
Connector
cover
FCN-360C040-B
7)
Cable
UL 2464 AWG28 or
equivalent
25
50
14
B16
39
A16
15
B15
40
A15
16
B14
41
A14
17
B13
42
A13
6
B12
31
A12
7
B11
32
A11
8
B10
33
A10
9
B9
34
A9
10
B8
35
A8
11
B7
36
A7
12
B6
37
A6
13
B5
38
A5
XSCN00
XSCN01
XSCN02
XSCN03
XSCN04
XSCN05
XSCN06
XSCN07
YD00
YD01
YD02
YD03
YD04
YD05
YD06
YD07
YD08
YD09
YD0A
YD0B
YD0C
YD0D
YD0E
YD0F
Model name
Manufacturer
3
PCR-E50FS+
(GT15-DIO)
PCS-E50FS+
(GT15-DIOR)
Honda Tsushin Kogyo
Co., Ltd.
Mitsubishi Electric
Corporation
FUJITSU
COMPONENT LIMITED
───
 Precautions when preparing a cable
5
(1) Cable length
Maximum cable length differs depending on the cable
used. Make the cable length within the range that can
satisfy the I/O specifications of the external I/O unit.
(2) GOT side connector
For the GOT side connector, refer to the following.
1.4.1 GOT connector specifications
6
30
B4
3
A4
2
B3
24V
24V
24V
CONNECTION TO
SOUND OUTPUT
UNIT
4
1
A3
28
B2
27
A2
26
B1
5
A1
0V
0V
Empty
Empty
Empty
7
CONNECTION TO
EXTERNAL I/O
DEVICE
29
4
MODBUS(R)/RTU
CONNECTION
No.
23
MICROCOMPUTER
CONNECTION
(SERIAL)
B20
43
MICROCOMPUTER
CONNECTION
(ETHERNET)
18
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
XD08
XD09
XD0A
XD0B
XD0C
XD0D
XD0E
XD0F
XSCN00
XSCN01
XSCN02
XSCN03
XSCN04
XSCN05
XSCN06
XSCN07
YD00
YD01
YD02
YD03
YD04
YD05
YD06
YD07
YD08
YD09
YD0A
YD0B
YD0C
YD0D
YD0E
YD0F
RUN
DC24V
DC24V
DC24V
DC24V
0V
0V
0V
0V
N.C.
1) 2)
PREPARATORY
PROCEDURES FOR
MONITORING
Connection diagram 6)
External I/O unit side
1
 Connector specifications
MODBUS(R)/TCP
CONNECTION
 For GT15-DIOR
7. CONNECTION TO EXTERNAL I/O DEVICE
7.3 Connection Diagram
7-7
7.3.3
Connection diagram between connector/terminal block converter module
and user-created original operation panel
The connection cable among the original operation panel, the connector/terminal block converter module and the
general output device must be prepared by the user referring to the followings.
 For GT15-DIO
Connection diagram 7)
When using A6TBY36-E connector/terminal block module
User-created original operation panel
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
70
71
72
73
74
75
76
77
XSCN07
60
61
62
63
64
65
66
67
XSCN06
50
51
52
53
54
55
56
57
XSCN05
40
41
42
43
44
45
46
47
XSCN04
30
31
32
33
34
35
36
37
XSCN03
20
21
22
23
24
25
26
27
XSCN02
10
11
12
13
14
15
16
17
XSCN01
00
01
02
03
04
05
06
07
XSCN00
24V
B20
A20
B19
A19
B18
A18
B17
A17
B16
A16
B15
A15
B14
A14
B13
A13
B12
A12
B11
A11
B10
A10
B9
A9
B8
A8
B7
A7
B6
A6
B5
A5
B4
A4
B3
A3
B2
A2
B1
A1
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
XSCN0
XSCN1
XSCN2
XSCN3
XSCN4
XSCN5
XSCN6
XSCN7
YD00
YD01
YD02
YD03
YD04
YD05
YD06
YD07
YD08
YD09
YD0A
YD0B
YD0C
YD0D
YD0E
YD0F
24V
24V
24V
0V
0V
A6TBY36-E
10
11
12
13
14
15
16
17
18
1A
1B
1C
1D
1E
1F
24V
0V
Load
Load
Load
Load
Load
Load
7. CONNECTION TO EXTERNAL I/O DEVICE
7.3 Connection Diagram
19
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load : Lamp,relay,etc.
7-8
0V
24V
1
PREPARATORY
PROCEDURES FOR
MONITORING
Connection diagram 8)
When using A6TBY54-E connector/terminal block module
User-created original operation panel
XD03
XD04
XD05
XD06
XD07
71
72
73
74
75
76
77
XSCN07
60
61
62
63
64
65
66
67
XSCN06
50
51
52
53
54
55
56
57
XSCN05
40
41
42
43
44
45
46
47
XSCN04
30
31
32
33
34
35
36
37
XSCN03
20
21
22
23
24
25
26
27
XSCN02
10
11
12
13
14
15
16
17
XSCN01
00
01
02
03
04
05
06
07
XSCN00
2
MICROCOMPUTER
CONNECTION
(SERIAL)
XD02
70
3
-C
-C
-C
-C
-C
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
XSCN0
XSCN1
XSCN2
XSCN3
XSCN4
XSCN5
XSCN6
XSCN7
YD00
YD01
YD02
YD03
YD04
YD05
YD06
YD07
YD08
YD09
YD0A
YD0B
YD0C
YD0D
YD0E
YD0F
24V
24V
24V
0V
0V
-C
0V
24V
-C
MODBUS(R)/RTU
CONNECTION
4
A6TBY54-E
MODBUS(R)/TCP
CONNECTION
5
CONNECTION TO
SOUND OUTPUT
UNIT
6
10
-C
11
12
-C
14
13
-C
15
16
-C
18
17
-C
19
1A
-C
1C
1B
-C
1D
1E
-C
0V
7
24V
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load : Lamp,relay,etc.
-C
1F
DC24V
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
B20
A20
B19
A19
B18
A18
B17
A17
B16
A16
B15
A15
B14
A14
B13
A13
B12
A12
B11
A11
B10
A10
B9
A9
B8
A8
B7
A7
B6
A6
B5
A5
B4
A4
B3
A3
B2
A2
B1
A1
-C
-C
MICROCOMPUTER
CONNECTION
(ETHERNET)
XD01
CONNECTION TO
EXTERNAL I/O
DEVICE
XD00
7. CONNECTION TO EXTERNAL I/O DEVICE
7.3 Connection Diagram
7-9
 For GT15-DIOR
Connection diagram 9)
When using A6TBY36-E connector/terminal block module
User-created original operation panel
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
70
71
72
73
74
75
76
77
XSCN07
60
61
62
63
64
65
66
67
XSCN06
50
51
52
53
54
55
56
57
XSCN05
40
41
42
43
44
45
46
47
XSCN04
30
31
32
33
34
35
36
37
XSCN03
20
21
22
23
24
25
26
27
XSCN02
10
11
12
13
14
15
16
17
XSCN01
00
01
02
03
04
05
06
07
XSCN00
24V
B20
A20
B19
A19
B18
A18
B17
A17
B16
A16
B15
A15
B14
A14
B13
A13
B12
A12
B11
A11
B10
A10
B9
A9
B8
A8
B7
A7
B6
A6
B5
A5
B4
A4
B3
A3
B2
A2
B1
A1
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
XSCN0
XSCN1
XSCN2
XSCN3
XSCN4
XSCN5
XSCN6
XSCN7
YD00
YD01
YD02
YD03
YD04
YD05
YD06
YD07
YD08
YD09
YD0A
YD0B
YD0C
YD0D
YD0E
YD0F
24V
24V
24V
0V
0V
A6TBY36-E
10
11
12
13
14
15
16
17
18
1A
1B
1C
1D
1E
1F
24V
0V
Load
Load
Load
Load
Load
Load
7. CONNECTION TO EXTERNAL I/O DEVICE
7.3 Connection Diagram
19
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load : Lamp,relay,etc.
7 - 10
0V
DC24V
1
PREPARATORY
PROCEDURES FOR
MONITORING
Connection diagram 10)
When using A6TBY54-E connector/terminal block module
User-created original operation panel
XD03
XD04
XD05
XD06
XD07
71
72
73
74
75
76
77
XSCN07
60
61
62
63
64
65
66
67
XSCN06
50
51
52
53
54
55
56
57
XSCN05
40
41
42
43
44
45
46
47
XSCN04
30
31
32
33
34
35
36
37
XSCN03
20
21
22
23
24
25
26
27
XSCN02
10
11
12
13
14
15
16
17
XSCN01
00
01
02
03
04
05
06
07
XSCN00
-C
-C
XD00
XD01
XD02
XD03
XD04
XD05
XD06
XD07
XSCN0
XSCN1
XSCN2
XSCN3
XSCN4
XSCN5
XSCN6
XSCN7
YD00
YD01
YD02
YD03
YD04
YD05
YD06
YD07
YD08
YD09
YD0A
YD0B
YD0C
YD0D
YD0E
YD0F
24V
24V
24V
0V
0V
-C
-C
3
-C
-C
-C
-C
24V
0V
MODBUS(R)/RTU
CONNECTION
4
A6TBY54-E
MODBUS(R)/TCP
CONNECTION
5
CONNECTION TO
SOUND OUTPUT
UNIT
6
10
11
-C
-C
12
13
14
15
-C
-C
16
17
18
19
-C
-C
1A
1B
1C
1D
-C
-C
1F
-C
24V
0V
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load
Load : Lamp,relay,etc.
1E
DC24V
7
8
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
B20
A20
B19
A19
B18
A18
B17
A17
B16
A16
B15
A15
B14
A14
B13
A13
B12
A12
B11
A11
B10
A10
B9
A9
B8
A8
B7
A7
B6
A6
B5
A5
B4
A4
B3
A3
B2
A2
B1
A1
-C
2
MICROCOMPUTER
CONNECTION
(SERIAL)
XD02
70
MICROCOMPUTER
CONNECTION
(ETHERNET)
XD01
CONNECTION TO
EXTERNAL I/O
DEVICE
XD00
7. CONNECTION TO EXTERNAL I/O DEVICE
7.3 Connection Diagram
7 - 11
7.4 GOT Side Settings
7.4.1
Setting communication
interface
 External I/O device setting
2.
 Controller setting
3.
Set the channel of the equipment to be connected to
the GOT.
2.
3.
4.
Click!
1.
2.
3.
4.
Select [Common]
menu.
[Controller Setting] from the
Click!
1.
The Controller Setting window is displayed. Select the
channel to be used from the list menu.
2.
Set Manufacturer, Controller Type, I/F, and Driver
according to the connected equipment to be used.
3.
The detailed setting is displayed after Manufacturer,
Controller Type, I/F, and Driver are set.
Make the settings according to the usage
environment.
Click the [OK] button when settings are completed.
POINT
The settings of connecting equipment can be set and
confirmed in [I/F Communication Setting]. For details,
refer to the following.
1.1.2 I/F communication setting
Select [Common]
[Peripheral Setting]
[Operation Panel] from the menu.
Set the interface to which the external I/O device is
connected.
Check the [Use Operation Panel] to set the operation
panel. For details on the operation panel settings,
refer to the following manual.
GT Designer3 Version1 Screen Design Manual
Click the [OK] button when settings are completed.
POINT
(1) Communication interface setting by the Utility
The communication interface setting can be
changed on the Utility's [Communication setting]
after writing [Communication Settings] of project
data.
For details on the Utility, refer to the following
manual.
User's Manual of GOT used.
(2) Precedence in communication settings
When settings are made by GT Designer3 or the
Utility, the latest setting is effective.
7 - 12
7. CONNECTION TO EXTERNAL I/O DEVICE
7.4 GOT Side Settings
1
PREPARATORY
PROCEDURES FOR
MONITORING
7.5 Precautions
 External I/O function setting on GT
Designer3
Before using the operation panel, make the operation
panel setting.
2
For details, refer to the following manual.
MICROCOMPUTER
CONNECTION
(SERIAL)
GT Designer3 Version1 Screen Design Manual
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
MODBUS(R)/RTU
CONNECTION
4
MODBUS(R)/TCP
CONNECTION
5
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
7. CONNECTION TO EXTERNAL I/O DEVICE
7.5 Precautions
7 - 13
7 - 14
7. CONNECTION TO EXTERNAL I/O DEVICE
7.5 Precautions
8
PREPARATORY
PROCEDURES FOR
MONITORING
1
MICROCOMPUTER
CONNECTION
(SERIAL)
2
FINGERPRINT
AUTHENTICATION DEVICE
CONNECTION
8.
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
MODBUS(R)/RTU
CONNECTION
4
8.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 2
8.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 2
5
MODBUS(R)/TCP
CONNECTION
8.3 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 3
8.4 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 - 4
CONNECTION TO
SOUND OUTPUT
UNIT
6
CONNECTION TO
EXTERNAL I/O
DEVICE
7
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
8-1
8.
FINGERPRINT AUTHENTICATION
DEVICE CONNECTION
8.1 Connectable Model List
The following table shows the connectable models.
Series
Clock
Fingerprint authentication
device
*1
*1
Refer to
8.2.1
Varies with the connected type.
8.2 System Configuration
8.2.1
Connecting to fingerprint authentication device
Extended function OS
Fingerprint
Authentication
Fingerprint
unit
Extended function OS
Operator authentication
Communication driver
Connection type
dependent
PLC
GOT
Connection cable
Varies according to
the fingerprint unit's
specifications.
Varies according to the
connection type.
Fingerprint unit
GOT
Connection cable
Model name
GT15-80FPA
Option
device
- (Built into GOT)
PLC
Model
For the system configuration
between the GOT and PLC, refer to
each chapter.
HINT
System configuration between the GOT and PLC
For the system configuration between the GOT and PLC, refer to each chapter.
Mitsubishi Products
Non-Mitsubishi Products 1, Non-Mitsubishi Products 2
Microcomputer, MODBUS Products, Peripherals
8-2
8. FINGERPRINT AUTHENTICATION DEVICE CONNECTION
8.1 Connectable Model List
Number of connectable
equipment
1 fingerprint
authentication device
for 1 GOT
1
8.3.1
Setting communication
interface
PREPARATORY
PROCEDURES FOR
MONITORING
8.3 GOT Side Settings
 Fingerprint authentication device setting
2.
 Controller setting
2
MICROCOMPUTER
CONNECTION
(SERIAL)
Set the channel of the equipment to be connected to
the GOT.
2.
Click!
Set the interface to which the fingerprint
authentication device is connected.
4
Click the [OK] button when settings are completed.
Click!
1.
2.
3.
4.
Select [Common]
menu.
[Controller Setting] from the
The Controller Setting window is displayed. Select the
channel to be used from the list menu.
Set Manufacturer, Controller Type, I/F, and Driver
according to the connected equipment to be used.
The detailed setting is displayed after Manufacturer,
Controller Type, I/F, and Driver are set.
Make the settings according to the usage
environment.
Click the [OK] button when settings are completed.
POINT
The settings of connecting equipment can be set and
confirmed in [I/F Communication Setting]. For details,
refer to the following.
POINT
(1) For communication interface setting
For the fingerprint authentication device
connection, use the channel No.8 of standard
interface.
The following external devices, which use Channel
No.8, cannot be connected at the same time.
• RFID controller that uses the external
authentication
• Barcode reader and RFID controller that require
the power supply
(2) Communication interface setting by the Utility
The communication interface setting can be
changed on the Utility's [Communication setting]
after writing [Communication Settings] of project
data.
For details on the Utility, refer to the following
manuals.
GT16 User’s Manual (Hardware)
GT15 User's Manual
(3) Precedence in communication settings
When settings are made by GT Designer3 or the
Utility, the latest setting is effective.
1.1.2 I/F communication setting
MODBUS(R)/RTU
CONNECTION
2.
5
MODBUS(R)/TCP
CONNECTION
4.
Select [Common]
[Peripheral Setting]
[Fingerprint Authentication] from the menu.
6
CONNECTION TO
SOUND OUTPUT
UNIT
1.
7
CONNECTION TO
EXTERNAL I/O
DEVICE
3.
MICROCOMPUTER
CONNECTION
(ETHERNET)
3
FINGERPRINT
AUTHENTICATION
DEVICE CONNECTION
8
8. FINGERPRINT AUTHENTICATION DEVICE CONNECTION
8.3 GOT Side Settings
8-3
8.4 Precautions
 Fingerprint authentication setting
Set the fingerprint authentication and operator
authentication on the GT Designer3 and GOT.
For details, refer to the following manuals.
GT Designer3 Version1 Screen Design Manual
User's Manual of GOT used.
 Controller setting
The fingerprint authentication device requires the
power supply from the GOT. Therefore, set Channel
No. 8 using the standard interface.
If the channel No. other than Channel No. 8 is set, the
GOT does not recognize the device as a controller.
8-4
8. FINGERPRINT AUTHENTICATION DEVICE CONNECTION
8.4 Precautions
9
BAR CODE READER
CONNECTION
10
PC REMOTE
CONNECTION
BAR CODE READER
CONNECTION
11
VNC(R) SERVER
CONNECTION
9.
9
12
VIDEO/RGB
CONNECTION
9.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 - 2
9.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 - 2
9.3 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 - 3
13
9.4 System Configuration Examples . . . . . . . . . . . . . . . . . . . . . 9 - 5
PRINTER
CONNECTION
9.5 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 - 7
MULTIMEDIA
CONNECTION
14
RFID CONNECTION
15
9-1
9.
BAR CODE READER CONNECTION
9.1 Connectable Model List
For connectable bar code readers and system equipment, refer to the following Technical News.
List of valid devices applicable for GOT1000 series (GOT-A-0010)
Visit the Mitsubishi Electric FA Equipment Information Service website (MELFANSweb) to refer to the Technical News.
http://wwwf2.mitsubishielectric.co.jp/english/index.html
9.2 System Configuration
9.2.1
Connecting to bar code reader
Extended function OS
Communication driver
Connection type
dependent
Barcode*
* For GT10, writing of the extended function OS is not required.
Bar code reader
GOT
Connection cable 1)
PLC
Connection cable 2)
Varies according to the connection type.
Bar code reader
GOT
Connection
cable 1)
Connection
cable 2)
Option device
*1
-
- (Built into GOT)
Model
*1
*1
*1
GT10-C02H-6PT9P
(0.2m)
- (Built into GOT)
*1
-
GT15-RS2-9P
PLC
Number of
connectable
equipment
For the system
configuration between
the GOT and PLC,
refer to each chapter.
1 bar code reader
for 1 GOT
For connectable bar code readers, system equipment, available bar code types and connection cables, refer to the following
Technical News.
List of valid devices applicable for GOT1000 series (GOT-A-0010)
POINT
When using the RS-232 communication unit
Use the RS-232 communication unit of the GOT for connecting to a barcode reader.
However, when the RS-232 communication unit is used, the power cannot be supplied to a bar code reader from
the GOT.
HINT
System configuration between the GOT and PLC
For the system configuration between the GOT and PLC, refer to each chapter.
Mitsubishi Products
Non-Mitsubishi Products 1, Non-Mitsubishi Products 2
Microcomputer, MODBUS Products, Peripherals
9-2
9. BAR CODE READER CONNECTION
9.1 Connectable Model List
9
9.3.1
Setting communication
interface
BAR CODE READER
CONNECTION
9.3 GOT Side Settings
 Bar code reader setting
2.
 Controller setting
4.
10
PC REMOTE
CONNECTION
Set the channel of the equipment to be connected to
the GOT.
2.
11
Click!
3.
1.
2.
3.
4.
Select [Common]
menu.
[Controller Setting] from the
The Controller Setting window is displayed. Select the
channel to be used from the list menu.
Set Manufacturer, Controller Type, I/F, and Driver
according to the connected equipment to be used.
The detailed setting is displayed after Manufacturer,
Controller Type, I/F, and Driver are set.
Make the settings according to the usage
environment.
Click the [OK] button when settings are completed.
POINT
The settings of connecting equipment can be set and
confirmed in [I/F Communication Setting]. For details,
refer to the following.
1.1.2 I/F communication setting
3.
Set the interface to which the bar code reader is
connected.
Check the [Use Bar Code] to set the function. For
details on the function setting, refer to the following
manual.
GT Designer3 Version1 Screen Design Manual
4.
Clicking the detail setting button displays the
Communication Detail Settings dialog box for each
communication driver.Make the settings according to
the usage environment.
9.3.2 Communication detail settings
Click the [OK] button when settings are completed.
POINT
(1) Communication interface setting
When Channel No.8 is used, the following external
devices, which use Channel No.8, cannot be
connected at the same time.
• Fingerprint authentication device
• RFID controller that uses the external
authentication
• RFID controller that requires the power supply
When connecting the above-mentioned devices at
the same time, set [Bar Code] to Channels No. 5
to 7.
(2) Setting for the driver
To Channels No. 5 to 8, multiple [Bar Code]
cannot be set.
9. BAR CODE READER CONNECTION
9.3 GOT Side Settings
VIDEO/RGB
CONNECTION
2.
[Bar
13
14
MULTIMEDIA
CONNECTION
Click!
Select [Common]
[Peripheral Setting]
Code] from the menu.
PRINTER
CONNECTION
1.
12
9-3
15
RFID CONNECTION
4.
VNC(R) SERVER
CONNECTION
3.
9.3.2
Communication detail settings
Make the settings according to the usage environment.
POINT
(1) Communication interface setting by the Utility
The communication interface setting can be
changed on the Utility's [Communication setting]
after writing [Communication Settings] of project
data.
For details on the Utility, refer to the following
manual.
User's Manual of GOT used.
(2) Precedence in communication settings
When settings are made by GT Designer3 or the
Utility, the latest setting is effective.
Item
Description
Range
Transmission
Speed
Set this item when change the
transmission speed used for
communication with the connected
equipment.
(Default: 9600bps)
4800bps,
9600bps,
19200bps,
38400bps,
57600bps,
115200bps
Data Bit
Set this item when change the
data length used for
communication with the connected
equipment.
(Default: 8bits)
7bits/8bits
Stop Bit
Specify the stop bit length for
communications.
(Default: 1bit)
1bit/2bits
Parity
Specify whether or not to perform
a parity check, and how it is
performed during communication.
(Default: Even)
None
Even
Odd
9-4
9. BAR CODE READER CONNECTION
9.3 GOT Side Settings
 Bar code reader setting
The bar code reader shall be configured as shown
below.
D0
D1
D2
Barcode
D3
D4
D5
123456789
9
(00H)
2
(32H)
4
(34H)
6
(36H)
8
(38H)
SP
(20H)
(09H)
1
(31H)
3
(33H)
5
( 35H)
7
(37H)
9
(39H)
Item
Read bytes
Transmission Speed
9600bps
Data Bit
Stored data
8bit
Stop Bit
1bit
Parity
Even
Header
None
Terminator
*1
<GOT>
11
CR
POINT
Read data
1
2
3
31H
32H
*1
33H
Terminator
4
5
6
7
8
9
CR
34H
35H
36H
37H
38H
39H
0DH
The GOT and QCPU (Q mode) are connected through a
bus.
For bus connection, refer to the following manual.
GOT1000 Series Connection Manual (Mitsubishi
Products) for GT Works3
1.
Bar code reader setting
For the bar code reader setting, refer to the following
manual.
User's Manual of the bar code reader
 Setting of [Controller Setting] of GT
Designer3
(1) Controller setting
The bar code is read with the bar code reader.
13
■ Bar code reader setting
The GOT receives the data sent from the bar code
reader.
PRINTER
CONNECTION
2.
■ Setting of [Controller Setting] of GT
Designer3
3.
The received data are written to the PLC CPU.
14
■ Setting of [Bar Code] of GT Designer3
The data read with the bar code reader are written
into the PLC CPU devices.
■ Confirmation on PLC side
(2) Communication detail settings
Keep consistency with the bar code reader setting.
Item
Transmission Speed
Setting (Use default value.)
9600bps
Data Bit
8bit
Stop Bit
1bit
Parity
Even
POINT
[Controller Setting] of GT Designer3
For the setting method of [Controller Setting] of GT
Designer3, refer to the following.
9.3.1Setting communication interface
9. BAR CODE READER CONNECTION
9.4 System Configuration Examples
15
RFID CONNECTION
4.
12
VIDEO/RGB
CONNECTION
<QCPU (Q mode)>
10
Set value
PC REMOTE
CONNECTION
Read data
"123456789"
VNC(R) SERVER
CONNECTION
 System configuration
MULTIMEDIA
CONNECTION
A system configuration example for bar code reader
connection is shown below.
BAR CODE READER
CONNECTION
9
9.4 System Configuration Examples
9-5
 Setting of [Bar Code] of GT Designer3
 Confirmation on PLC side
Connect GX Developer to the QCPU (Q-mode) and
check if the data, which has been read with the bar
code reader, are written in D0 to D5.
For the GX Developer operation method, refer to the
following manual.
GX Developer Version
Operating Manual
(1) Confirming the device values of D0 to D5 (when
using GX Developer Version 8)
Startup procedure
GX Developer
batch]
Item
Set value
Read Data Direct Input to Object
No
Device
D0
Device Points
6
*1
None
Header
*1
CR
Terminator
Writing Byte Order
Low
Fills a blank when Imported data is
not filled in Writing Points
Filling Data
*1
High
Check (Filling Data is available)
Space (020)
Keep consistency with the bar code reader setting.
POINT
[Bar Code] of GT Designer3
For the [Bar Code] setting in GT Designer3, refer to the
following manual.
GT Designer3 Version1 Screen Design Manual
9-6
9. BAR CODE READER CONNECTION
9.4 System Configuration Examples
[Online]
[Monitor]
[Device
ASCII codes are hexadecimals.
Specify [HEX] for [Value] of the GX
Developer and confirm the read data.
9
BAR CODE READER
CONNECTION
9.5 Precautions
 Bar code function setting on GT Designer3
Before connecting the bar code reader, make the bar
code function and system data settings.
For details, refer to the following manual.
10
GT Designer3 Version1 Screen Design Manual
PC REMOTE
CONNECTION
 Controller setting
When using the barcode reader, which requires the
power supply from the GOT, set Channel No. 8 using
the standard interface.
With Channels No. 5 to 7 of the extension interface, the
power cannot be supplied.
VNC(R) SERVER
CONNECTION
11
VIDEO/RGB
CONNECTION
12
PRINTER
CONNECTION
13
MULTIMEDIA
CONNECTION
14
RFID CONNECTION
15
9. BAR CODE READER CONNECTION
9.5 Precautions
9-7
9-8
9. BAR CODE READER CONNECTION
9.5 Precautions
PC REMOTE
CONNECTION
PC REMOTE CONNECTION
10
11
10.2 Serial Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 - 2
VNC(R) SERVER
CONNECTION
10.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 - 2
10.3 Ethernet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 - 7
VIDEO/RGB
CONNECTION
12
PRINTER
CONNECTION
13
MULTIMEDIA
CONNECTION
14
15
RFID CONNECTION
10.
BAR CODE READER
CONNECTION
10
9
10 - 1
10. PC REMOTE CONNECTION
10.1 Connectable Model List
The RGB display is used for the remote personal computer operation connection.
The following GOT models support the remote personal computer operation connection.
Connection type
GOT model
Serial connection
GT16*1,
Ethernet connection
GT16*2
*1
*2
GT1585V-S, GT1575V-S
GT1675-VN, GT1672-VN, GT1662-VN, and 1665-V cannot be used.
GT1675-VN, GT1672-VN, and GT1662-VN cannot be used.
10.2 Serial Connection
10.2.1
System Configuration
PC
Extended function OS
Extended function OS
PC remote operation
(serial)
Video/RGB input
GOT
Communication driver
Connection type
dependent
PLC
Connection cable 1)
Connection cable 2)
Varies according to the
connection type.
Connection cable 1)*2
Personal computer
Cable model
GT01-C30R2-9S
or
RS232 connection
diagram 1)
GOT
Max.
distance
Cable model
GT15-C50VG
or
Analog RGB connection
diagram 1)
*1
*2
Model
15m
GT15-RS2-9P
GOT
Max.
distance
Option device
Model
GT16M-R2
*1
For the system
configuration between
the GOT and PLC,
refer to each chapter.
1 personal
computer for 1
GOT
GT16M-V4R1
GT15V-75R1
GT15V-75V4R1
The cable length differs depending on the specification of the personal computer to be used. Use the cable that is compatible
with the personal computer to be used.
The connection cable 1) (RS-232 cable) and the connection cable 2) (analog cable) should be connected between the personal
computer and the GOT.
HINT
System configuration between the GOT and PLC
For the system configuration between the GOT and PLC, refer to each chapter.
Mitsubishi Products
Non-Mitsubishi Products 1, Non-Mitsubishi Products 2
Microcomputer, MODBUS Products, Peripherals
10 - 2
Number of
connectable
equipment
- (Built into GOT)
Connection cable 2)*2
To be selected by the
user.
Option device
PLC
10. PC REMOTE CONNECTION
10.1 Connectable Model List
GOT side
PC side
CD
1
1
CD
RD
2
3
SD
SD
3
2
RD
DTR
4
6
DSR
SG(GND)
5
5
SG(GND)
DSR
6
4
DTR
RTS
7
7
RTS
CTS
8
8
CTS
9
9
CI
Shell
Shell
FG
BAR CODE READER
CONNECTION
PC side
GOT side
R
1
1
R
RGND
6
6
RGND
G
2
2
G
GGND
7
7
GGND
B
3
3
B
BGND
8
8
BGND
DGND
10
10
GND
HSYNC
13
13
HSYNC
VSYNC
14
14
VSYNC
DGND
5
5
GND
NC
4
4
GND
Twisted pair
NC
9
9
NC
NC
11
11
GND
NC
12
12
SDA
NC
15
15
SCL
(2) Precautions when preparing a cable
(a) Cable length
The length of the RS-232 cable must be 15m or
less.
(b) GOT side connector
For the GOT side connector, refer to the following.
1.4.1 GOT connector specifications
(c) Personal computer side connector
Use a connector compatible with the personal
computer to be used.
(2) Precautions when preparing a cable
(a) Cable length
The cable length differs depending on the
specification of the personal computer to be used.
Create a cable under the specifications of the
personal computer.
(b) GOT side connector
Use the following as the video/RGB input unit and
the RGB input unit connectors.
For the GOT side connector and connector cover
of the analog RGB cable, use the ones applicable
to the GOT connector.
GOT
Connector type
Connector
type
17HE-R13150-73MC2
D-Sub 15
pin (female)
Manufacturer
GT16M-R2
GT16M-V4R1
GT15V-75R1
DDK Ltd.
(DDK)
GT15V-75V4R1
(c) Personal computer side connector
Use a connector compatible with the personal
computer to be used.
10. PC REMOTE CONNECTION
10.2 Serial Connection
10 - 3
10
PC REMOTE
CONNECTION
RS232 connection diagram 1)
75Ω drohmcoaxial
11
VNC(R) SERVER
CONNECTION
(1) Connection diagram
Analog RGB connection diagram 1)
12
VIDEO/RGB
CONNECTION
 RS-232 cable
(1) Connection diagram
13
PRINTER
CONNECTION
When using a 3m or longer RS-232 cable for connecting a
GOT to a personal computer, the cable must be prepared
by the user.
The following shows each cable connection diagram.
FG
9
 Analog RGB cable
14
MULTIMEDIA
CONNECTION
Connection Diagram
15
RFID CONNECTION
10.2.2
10.2.3
GOT Side Settings
 Settings for the remote personal computer
operation
 Setting communication interface
(Communication settings)
2.
Set the channel of the equipment to be connected to
the GOT.
2.
3.
4.
Click!
Click!
1.
1.
2.
3.
4.
Select [Common]
menu.
[Controller Setting] from the
The Controller Setting window is displayed. Select the
channel to be used from the list menu.
Set Manufacturer, Controller Type, I/F, and Driver
according to the connected equipment to be used.
The detailed setting is displayed after Manufacturer,
Controller Type, I/F, and Driver are set.
Make the settings according to the usage
environment.
Click the [OK] button when settings are completed.
POINT
The settings of connecting equipment can be set and
confirmed in [I/F Communication Setting]. For details,
refer to the following.
1.1.2 I/F communication setting
10 - 4
10. PC REMOTE CONNECTION
10.2 Serial Connection
2.
Select [Common]
[Peripheral Setting]
Remote Operation] from the menu.
[PC
Set the interface to which the personal computer is
connected for the [Connecting I/F] of [PC Remote
Operation (serial)].
Click the [OK] button when settings are completed.
Communication detail settings
(1) Serial connection
2.
4.
Make the settings according to the usage environment.
9
BAR CODE READER
CONNECTION
10.2.4
 Settings for the video/RGB equipment
PC REMOTE
CONNECTION
10
11
Resolution
*1
1.
2.
3.
Select [Common]
[Peripheral Setting]
RGB Input] from the menu.
[Video/
Set the interface to which the video/RGB equipment is
connected.
Check the [Use Video/RGB Input] to set the function.
For details on the function setting, refer to the
following manual.
GT Designer3 Version1 Screen Design Manual
4.
Clicking the detail setting button displays the
Communication Detail Settings dialog box for each
communication driver.Make the settings according to
the usage environment.
10.2.4 Communication detail settings
Click the [OK] button when settings are completed.
POINT
Setting for the driver
To Channels No. 5 to 8, multiple [PC Remote
Operation] cannot be set.
*2
*3
Set the video resolution.
(Default: 640 480)
640
720
480,
480,
768
576*3
When NTSC format is selected, the resolution is fixed to
640 480.
For GT1675M-V and GT1665M-V, the resolution is fixed to
640 480.
768 576 can be set only for the GT16.
POINT
(1) Communication interface setting
When Channel No.8 is used, the following external
devices, which use Channel No.8, cannot be
connected at the same time.
• Fingerprint authentication device
• RFID controller that uses the external
authentication
• Barcode reader and RFID controller that require
the power supply
When connecting the above-mentioned devices at
the same time, set [PC Remote Operation] to
Channels No. 5 to 7.
(2) Communication interface setting by the Utility
The communication interface setting can be
changed on the Utility's [Communication setting]
after writing [Communication Settings] of project
data.
For details on the Utility, refer to the following
manual.
User's Manual of GOT used.
(3) Precedence in communication settings
When settings are made by GT Designer3 or the
Utility, the latest setting is effective.
10. PC REMOTE CONNECTION
10.2 Serial Connection
10 - 5
VNC(R) SERVER
CONNECTION
3.
*2
NTSC, PAL
12
VIDEO/RGB
CONNECTION
Video
Click!
Set the video input signal.
(Default: NTSC)
13
PRINTER
CONNECTION
Signal*1
Range
14
MULTIMEDIA
CONNECTION
Video Input
Description
15
RFID CONNECTION
Item
10.2.5
Installing and setting up
computer remote operation
driver.
Install and set up the remote personal computer operation
driver to the personal computer.
For installing and setting up the remote personal computer
operation driver, refer to the following manual.
GT Designer3 Version1 Screen Design Manual
10.2.6
Precautions
 Personal computer side setting
Before using the remote personal computer operation
function, install the remote personal computer
operation driver on the personal computer.
After the driver installation, check that the driver is
correctly installed.
For details of the remote personal computer operation
driver, refer to the following manual.
GT Designer3 Version1 Screen Design Manual
10 - 6
10. PC REMOTE CONNECTION
10.2 Serial Connection
System Configuration
Connection type
dependent
Ethernet system
GOT
PLC
Connection cable
length*4
To be selected by the
user.
Twisted pair cable*1
• 10BASE-T
Shielded twisted pair cable (STP)
or unshielded twisted pair cable
(UTP): Category 3, 4, and 5
• 100BASE-TX
Shielded twisted pair cable (STP):
Category 5 and 5e
*1
*2
*3
100m
GOT
Option device
- (Built into GOT)
Model
*3
PLC
Number of
connectable
equipment
For the system
configuration between
the GOT and PLC,
refer to each chapter.
1 personal
computer for 1
GOT
12
The destination connected with the twisted pair cable varies with the configuration of the applicable Ethernet network system.
Connect to the Ethernet module, hub, transceiver, wireless LAN adapter (NZ2WL-JPA or NZ2WL-JPS), or other system
equipment corresponding to the applicable Ethernet network system.
Use cables, connectors, and hubs that meet the IEEE802.3 10BASE-T/100BASE-TX standard.
For the controllers that can be connected to the wireless LAN adapters and how to set the wireless LAN adapter, refer to the
manual of the wireless LAN adapter used.
A straight cable is available.
When connecting the GOT and PC directly with Ethernet cable, remember that the by cross cable is available.
When connecting GT16 of the function version A to an equipment that meets the 10BASE (-T/2/5) standard, use the switching
hub and operate in a 10Mbps/100Mbps mixed environment.
For how to check the function version, refer to the following.
GT16 User’s Manual (Hardware)
*4
A length between a hub and a node.
The maximum distance differs depending on the Ethernet device to be used.
The following shows the number of the connectable nodes when a repeater hub is used.
• 10BASE-T: Max. 4 nodes for a cascade connection (500m)
• 100BASE-TX: Max. 2 nodes for a cascade connection (205m)
When switching hubs are used, the cascade connection between the switching hubs has no logical limit for the number of
cascades.
For the limit, contact the switching hub manufacturer.
VIDEO/RGB
CONNECTION
Maximum
segment
13
PRINTER
CONNECTION
Connection cable*2
VNC(R) SERVER
CONNECTION
11
Varies according to the
connection type.
Personal computer
10
PC REMOTE
CONNECTION
PC remote operation
(Ethernet)
PC
Communication driver
Communication driver
Extended function OS
14
MULTIMEDIA
CONNECTION
10.3.1
BAR CODE READER
CONNECTION
9
10.3 Ethernet Connection
15
RFID CONNECTION
HINT
System configuration between the GOT and PLC
For the system configuration between the GOT and PLC, refer to each chapter.
Mitsubishi Products
Non-Mitsubishi Products 1, Non-Mitsubishi Products 2
Microcomputer, MODBUS Products, Peripherals
10. PC REMOTE CONNECTION
10.3 Ethernet Connection
10 - 7
10.3.2
GOT Side Settings
 Settings for the PC remote operation
 Setting communication interface
2.
(Communication settings)
Set the channel of the equipment to be connected to
the GOT.
2.
3.
4.
3.
Click!
1.
2.
3.
4.
Select [Common]
menu.
[Controller Setting] from the
The Controller Setting window is displayed. Select the
channel to be used from the list menu.
Set Manufacturer, Controller Type, I/F, and Driver
according to the connected equipment to be used.
The detailed setting is displayed after Manufacturer,
Controller Type, I/F, and Driver are set.
Make the settings according to the usage
environment.
Click the [OK] button when settings are completed.
1.
2.
3.
Click!
Select [Common]
[Peripheral Setting]
Remote Operation] from the menu.
[PC
Set [Connecting I/F] of [PC Remote Operation] to
[Disconnect].
Check the [Use PC Remote Operation (Ethernet)] of
[PC Remote Operation (Ethernet)] to set. For details
on the settings, refer to the following manual.
GT Designer3 Version1 Screen Design Manual
Click the [OK] button when settings are completed.
10.3.3
Install and setting the required
software
Install and set the required software according to the
system configuration.
For the settings, refer to the following manual.
POINT
GT Designer3 Version1 Screen Design Manual
The settings of connecting equipment can be set and
confirmed in [I/F Communication Setting]. For details,
refer to the following.
1.1.2 I/F communication setting
10.3.4
Precautions
 Ethernet system driver
Before using the PC remote operation function
(Ethernet), install an Ethernet system communication
driver to the GOT.
Set the Ethernet system communication driver for the
controller setting or peripheral setting.
For the settings, refer to the following manual.
GT Designer3 Version1 Screen Design Manual
10 - 8
10. PC REMOTE CONNECTION
10.3 Ethernet Connection
PC REMOTE
CONNECTION
VNC(R) SERVER CONNECTION
10
11.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 - 2
11.3 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 - 3
11.4 Setting in Personal Computer . . . . . . . . . . . . . . . . . . . . . . .11 - 4
12
VIDEO/RGB
CONNECTION
11.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 - 2
VNC(R) SERVER
CONNECTION
11
PRINTER
CONNECTION
13
MULTIMEDIA
CONNECTION
14
15
RFID CONNECTION
11.
BAR CODE READER
CONNECTION
11
9
11 - 1
11. VNC(R) SERVER CONNECTION
11.1 Connectable Model List
The VNC® server can be connected to the following VNC® client.
CPU
Software
PC
Ultra VNC
11.2 System Configuration
Communication driver
Extended function OS
Ethernet system
VNC Server
GOT
(VNC R server)
PC
(VNC R client)
Communication driver
Connection type
dependent
PLC
Connection cable
Varies according to the
connection type.
Personal computer
®
(VNC client)
Connection cable*1*2
To be selected by the
user.
Twisted pair cable
• 10BASE-T
Shielded twisted pair cable (STP)
or unshielded twisted pair cable
(UTP): Category 3, 4, and 5
• 100BASE-TX
Shielded twisted pair cable (STP):
Category 5 and 5e
Maximum
segment
length*4
*1
*2
*3
100m
®
GOT (VNC server)
Option device
- (Built into GOT)
PLC
Number of
connectable
equipment
For the system
configuration between
the GOT and PLC,
refer to each chapter.
1 personal
computer for 1
GOT
Model
*3
The destination connected with the twisted pair cable varies with the configuration of the applicable Ethernet network system.
Connect to the Ethernet module, hub, transceiver, wireless LAN adapter (NZ2WL-JPA or NZ2WL-JPS), or other system
equipment corresponding to the applicable Ethernet network system.
Use cables, connectors, and hubs that meet the IEEE802.3 10BASE-T/100BASE-TX standard.
For the controllers that can be connected to the wireless LAN adapters and how to set the wireless LAN adapter, refer to the
manual of the wireless LAN adapter used.
A straight cable is available.
When connecting the GOT and PC directly with Ethernet cable, remember that the by cross cable is available.
When connecting GT16 of the function version A to an equipment that meets the 10BASE (-T/2/5) standard, use the switching
hub and operate in a 10Mbps/100Mbps mixed environment.
For how to check the function version, refer to the following.
GT16 User’s Manual (Hardware)
*4
11 - 2
A length between a hub and a node.
The maximum distance differs depending on the Ethernet device to be used.
The following shows the number of the connectable nodes when a repeater hub is used.
• 10BASE-T: Max. 4 nodes for a cascade connection (500m)
• 100BASE-TX: Max. 2 nodes for a cascade connection (205m)
When switching hubs are used, the cascade connection between the switching hubs has no logical limit for the number of
cascades.
For the limit, contact the switching hub manufacturer.
11. VNC(R) SERVER CONNECTION
11.1 Connectable Model List
Mitsubishi Products
BAR CODE READER
CONNECTION
9
Non-Mitsubishi Products 1, Non-Mitsubishi Products 2
10
HINT
System configuration between the GOT and PLC
For the system configuration between the GOT and PLC, refer to each chapter.
PC REMOTE
CONNECTION
Microcomputer, MODBUS Products, Peripherals
11.3 GOT Side Settings
11
Setting communication
interface (Communication
settings)
VNC(R) SERVER
CONNECTION
11.3.2
2.
For using the VNC® server, Ethernet
communication drivers must be set on the GOT,
and set the Communication settings
12
2.
3.
4.
VIDEO/RGB
CONNECTION
VNC(R) server function setting
13
PRINTER
CONNECTION
11.3.1
14
2.
Select [Common]
[Peripheral Setting]
Server] from the menu.
Check the [VNC Server] of [Use VNC Server] to set.
For details on the settings, refer to the following
manual.
GT Designer3 Version1 Screen Design Manual
(Functions)
3.
Click!
[VNC
Click the [OK] button when settings are completed.
1.
2.
3.
4.
Select [Common]
menu.
[Controller Setting] from the
The Controller Setting window is displayed. Select the
channel to be used from the list menu.
Set Manufacturer, Controller Type, I/F, and Driver
according to the connected equipment to be used.
The detailed setting is displayed after Manufacturer,
Controller Type, I/F, and Driver are set.
Make the settings according to the usage
environment.
Click the [OK] button when settings are completed.
11. VNC(R) SERVER CONNECTION
11.3 GOT Side Settings
11 - 3
15
RFID CONNECTION
1.
MULTIMEDIA
CONNECTION
Click!
POINT
Ethernet-based driver
For using the VNC® server, any of the following Ethernet communication drivers must be set on the GOT.
• Gateway
• Ethernet Download
• Ethernet (MELSEC), Q17nNC, CRnD-700
• Ethernet (MELSEC), Q17nNC, CRnD-700, Gateway
• Ethernet (FX), Gateway
• Ethernet (OMRON), Gateway
• Ethernet (TOSHIBA nv), Gateway
• Ethernet (YASKAWA), Gateway
• Ethernet (YOKOGAWA), Gateway
• EtherNet/IP (AB), Gateway
• Ethernet (SIEMENS S7), Gateway
• MODBUS/TCP, Gateway
• Ethernet (MICROCOMPUTER)
In the peripheral setting, set [Destination I/F] in [Ethernet Download] for the [PC (Data Transfer)] dialog box.
To connect controllers including a programmable controller to the GOT by using the Ethernet connection, no setting
is required.
For the details of [Ethernet Download] , refer to the following
GT Designer3 Version1 Screen Design Manual (Fundamentals)
11.4 Setting in Personal Computer
For connecting the VNC® server to the personal computer (VNC® client), it is necessary to install the VNC® client
software to the personal computer to be connected and set it.
Refer to the following for details of the VNC® client software installation method and setting method.
11 - 4
11. VNC(R) SERVER CONNECTION
11.4 Setting in Personal Computer
10
PC REMOTE
CONNECTION
VIDEO/RGB CONNECTION
BAR CODE READER
CONNECTION
12
9
12.
12.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 - 3
12.3 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 - 5
12.4 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 - 7
13
PRINTER
CONNECTION
12.5 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 - 8
12
VIDEO/RGB
CONNECTION
12.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 - 2
VNC(R) SERVER
CONNECTION
11
MULTIMEDIA
CONNECTION
14
RFID CONNECTION
15
12 - 1
12. VIDEO/RGB CONNECTION
12.1 Connectable Model List
The following GOT models support the Video/RGB connection.
GOT model
GT16*1, GT1585V-S, GT1575V-S
*1
GT1675-VN, GT1672-VN, GT1662-VN, and GT1655-V cannot be used.
For the type of the video camera that can be connected, refer to the following Technical News.
List of valid devices applicable for GOT1000 series (GOT-A-0010)
Visit the Mitsubishi Electric FA Equipment Information Service website (MELFANSweb) to refer to the Technical News.
http://wwwf2.mitsubishielectric.co.jp/english/index.html
12 - 2
12. VIDEO/RGB CONNECTION
12.1 Connectable Model List
Displaying video image on GOT
Extended function OS
Video/RGB equipment including
video cameras, vision sensors,
and personal computers
GOT
Connection cable
Equipment including video cameras*1 and vision
sensors*2 that outputs images by using the NTSC or
PAL signal
*1
*2
Equipment including video cameras , vision sensors ,
and personal computers*2 that outputs images by using
the RGB signal
Cable model
Connection diagram
number
Option device
Coaxial connection
diagram 1)
GT15-C50VG(5m)
or
Analog RGB
connection diagram 1)
Number of
connectable
equipment
Model
GT16M-V4
GT16M-V4R1
GT15V-75V4
GT15V-75V4R1
GT16M-R2*4
GT16M-V4R1
GT15V-75R1
GT15V-75V4R1
12
4 video equipment
for 1 GOT
2 RGB equipment
for 1 GOT
1 RGB equipment
for 1 GOT
*1
For connectable video camera types, refer to the following Technical News.
*2
*3
*4
List of valid devices applicable for GOT1000 series (GOT-A-0010)
The user must select a vision sensor or a personal computer to be used.
The cable length differs according to the specifications of the video/RGB equipment.
RGB can be input with two channels. For the switching between two channels, refer to the following manual.
13
GT Designer3 Version1 Screen Design Manual
14
MULTIMEDIA
CONNECTION
Analog RGB
GOT
15
RFID CONNECTION
NTSC/PAL
Connection cable*3
VNC(R) SERVER
CONNECTION
Video/RGB equipment
11
PRINTER
CONNECTION
Signal type
10
PC REMOTE
CONNECTION
Video/RGB input
VIDEO/RGB
CONNECTION
12.2.1
BAR CODE READER
CONNECTION
9
12.2 System Configuration
12. VIDEO/RGB CONNECTION
12.2 System Configuration
12 - 3
POINT
(1) Power supply of video camera
Depending on the video camera type, noises from the power supply cable of the camera may cause a
malfunction on the PLC or the GOT.In this case, apply the following line filter to the power line of the camera.
Recommended line filter: TDK ZHC2203-11 (or equivalent)
(2) Power supply of vision sensor
If a video camera is used via a vision sensor, a power supply module may be required depending on the vision
sensor to be used.
(3) Selection of Video signal output source
Depending on the video camera or the system to be used, both the power supply module and the video
camera can output video signals. If video signals are output from both the video camera and the power supply
module, the voltage level of the signals become lower and the video image cannot be correctly displayed. In
this case, use the output from the video camera.
(4) Power-On of video camera
Turn on the video camera simultaneously with the GOT.
12.2.2
Displaying GOT screen on external monitor
External monitor
GOT
Connection cable
External monitor
Signal
type
Analog
RGB
Model name
Model name
For connectable external monitor types, refer to the
following Technical News.
GT15-C50VG(5m)
or
List of valid devices applicable for GOT1000
series (GOT-A-0010)
*1
12 - 4
Connection cable
Analog RGB connection
diagram 2)
GOT
Distance
Option device
GT16M-ROUT
*1
1 for 1 GOT
GT15V-75ROUT
The cable length differs depending on the specification of the external monitor used by the user.
12. VIDEO/RGB CONNECTION
12.2 System Configuration
Model
Number of
connectable
equipment
9
BAR CODE READER
CONNECTION
12.3 Connection Diagram
The following shows each cable connection diagram and
relevant connectors.
12.3.1
Coaxial cable
The following provides the specifications, the connectors
and creation method of the coaxial cable to connect the
GOT to the video output equipment.
 Connection diagram
Coaxial connection diagram 1)
HINT
When the coaxial cable is long
When the coaxial cable is long, video signals are
attenuated by the cable.
The use of a video signal amplifier is recommended to
correct the attenuated signals.
Connect a video signal amplifier in reference to the
following:
• Coaxial cable: The cable length is 100m or more
when 3C-2V is used.
• Coaxial cable: The cable length is 200m or more
when 5C-2V is used.
10
PC REMOTE
CONNECTION
The coaxial cable/analog RGB cable to connect the GOT
to the Video/RGB equipment must be prepared by the user.
11
 Connection diagram
Analog RGB connection diagram 1)
Vision sensor/PC side
Item
Applicable cable
12
Displaying video image on GOT
Cable specification
Specifications
3C-2V, 5C-2V (JIS C 3501 compliant)
 Connecting the BNC connector to the coaxial
cable
For how to connect the BNC connector and coaxial
cable, refer to the following.
1.4.2 Coaxial cable connector connection
method
 Precautions when preparing a cable
R
RGND
G
GGND
B
BGND
GND
HSYNC
VSYNC
GND
GND
NC
GND
SDA
SC
75Ω drohmcoaxial
GOT side
1
1
6
6
2
2
7
7
3
3
8
8
10
10
13
13
14
14
5
5
4
4
9
9
Twisted pair
11
11
12
12
15
15
R
RGND
G
GGND
B
BGND
GND
HSYNC
VSYNC
GND
NC
NC
NC
NC
NC
(1) Cable length
The cable length differs depending on the specification
of the video camera or vision sensor to be used.
Create a cable under the specifications of the video
camera/vision sensor.
(2) GOT side connector
Use the following as the video input unit connector.
For the GOT side connector of the coaxial cable, use
the ones compatible with the GOT connector.
GOT
Connector
model
Connector
type
Manufacturer
GT16M-V4
GT16M-V4R1
227161-4
BNC
Tyco International, Ltd.
GT15V-75V4
GT15V-75V4R1
(3) Video camera/vision sensor side connector
Use a connector compatible with the video camera/
vision sensor to be used.
VIDEO/RGB
CONNECTION
Signal
BNC connector
GND
Analog RGB cable
13
PRINTER
CONNECTION
Signal
GND
12.3.2
14
Analog RGB connection diagram 2)
Displaying GOT screen on external monitor
GOT side
R
RGND
G
GGND
B
BGND
DGND
HSYNC
VSYNC
DGND
NC
NC
NC
NC
NC
75Ω drohmcoaxial
External monitor
side
1
1
6
6
2
2
7
7
3
3
8
8
10
10
13
13
14
14
5
5
4
4
9
Twisted pair
9
11
11
12
12
15
15
12. VIDEO/RGB CONNECTION
12.3 Connection Diagram
R
RGND
G
GGND
B
BGND
GND
HSYNC
VSYNC
GND
GND
NC
GND
SDA
SCL
12 - 5
MULTIMEDIA
CONNECTION
BNC connector
Video camera/
vision sensor side
15
RFID CONNECTION
75Ω drohmcoaxial
GOT side
VNC(R) SERVER
CONNECTION
Displaying video image on GOT
 Precautions when preparing a cable
(1) Cable length
The cable length differs depending on the specification
of the vision sensor/PC to be used. Create a cable
under the specifications of the vision sensor/PC.
(2) GOT side connector
Use the following as the video/RGB input unit, RGB
input unit, and RGB output unit connectors.
For the GOT side connector and connector cover of the
analog RGB cable, use the ones applicable to the GOT
connector.
GOT
Connector model
Connector
type
17HE-R13150-73MC2
D-Sub 15-pin
(female)
Manufacturer
GT16M-R2
GT16M-V4R1
GT16M-ROUT
GT15V-75R1
DDK Ltd.
(DDK)
GT15V-75V4R1
GT15V-75ROUT
(3) Vision sensor/PC side connector
Use a connector compatible with the vision sensor/
personal computer to be used.
12 - 6
12. VIDEO/RGB CONNECTION
12.3 Connection Diagram
9
12.4.1
Setting communication
interface
BAR CODE READER
CONNECTION
12.4 GOT Side Settings
 Settings for the video/RGB equipment
 Controller setting
2.
10
4.
PC REMOTE
CONNECTION
Set the channel of the equipment to be connected to
the GOT.
2.
11
VNC(R) SERVER
CONNECTION
3.
4.
12
1.
1.
2.
3.
4.
Select [Common]
menu.
[Controller Setting] from the
The Controller Setting window is displayed. Select the
channel to be used from the list menu.
2.
3.
Set Manufacturer, Controller Type, I/F, and Driver
according to the connected equipment to be used.
The detailed setting is displayed after Manufacturer,
Controller Type, I/F, and Driver are set.
Make the settings according to the usage
environment.
Select [Common]
[Peripheral Setting]
RGB Input] from the menu.
[Video/
Set the interface to which the video/RGB equipment is
connected.
Check the [Use Video/RGB Input] to set the function.
For details on the function setting, refer to the
following manual.
GT Designer3 Version1 Screen Design Manual
4.
Clicking the detail setting button displays the
Communication Detail Settings dialog box for each
communication driver.Make the settings according to
the usage environment.
12.4.2 Communication detail settings
Click the [OK] button when settings are completed.
13
PRINTER
CONNECTION
Click!
VIDEO/RGB
CONNECTION
Click!
14
MULTIMEDIA
CONNECTION
3.
15
Click the [OK] button when settings are completed.
RFID CONNECTION
POINT
The settings of connecting equipment can be set and
confirmed in [I/F Communication Setting]. For details,
refer to the following.
1.1.2 I/F communication setting
12. VIDEO/RGB CONNECTION
12.4 GOT Side Settings
12 - 7
12.4.2
Communication detail settings
Make the settings according to the usage environment.
12.4.3
Setting the video/RGB function
Set the video/RGB function.
For the video/RGB function setting, refer to the following
manual.
GT Designer3 Version1 Screen Design Manual
Item
Video Input
Signal*1
Video
Description
Set the video input signal.
(Default: NTSC)
Set the video resolution.
*2
Resolution
*1
*2
*3
(Default: 640
480)
Range
NTSC, PAL
640
480,
720
480,
768
576*3
When NTSC format is selected, the resolution is fixed to
640 480.
For GT1675M-V and GT1665M-V, the resolution is fixed to
640 480.
768 576 can be set only for the GT16.
POINT
(1) Communication interface setting by the Utility
The communication interface setting can be
changed on the Utility's [Communication setting]
after writing [Communication Settings] of project
data.
For details on the Utility, refer to the following
manual.
User's Manual of GOT used.
(2) Precedence in communication settings
When settings are made by GT Designer3 or the
Utility, the latest setting is effective.
12.5 Precautions
 Connecting to PC
When connecting to a PC, ground the earth wire of the
PC.
12 - 8
12. VIDEO/RGB CONNECTION
12.5 Precautions
10
PC REMOTE
CONNECTION
PRINTER CONNECTION
BAR CODE READER
CONNECTION
13
9
13.
13.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 - 2
13.3 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 - 4
13.4 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 - 6
12
VIDEO/RGB
CONNECTION
13.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 - 2
VNC(R) SERVER
CONNECTION
11
PRINTER
CONNECTION
13
MULTIMEDIA
CONNECTION
14
RFID CONNECTION
15
13 - 1
13. PRINTER CONNECTION
13.1 Connectable Model List
For connectable printers and system equipment, refer to the following Technical News.
List of valid devices applicable for GOT1000 series (GOT-A-0010)
Visit the Mitsubishi Electric FA Equipment Information Service website (MELFANSweb) to refer to the Technical News.
http://wwwf2.mitsubishielectric.co.jp/english/index.html
13.2 System Configuration
13.2.1
Connecting to PictBridge compatible printer
Extended function OS Communication driver
Printer (PictBridge)
PictBridge
compatible
printer
GOT
Connection type
dependent
PLC
Connection cable
Varies according to the connection type.
Printer
Connection cable
Model name
Model name
For connectable printers and system equipment,
refer to the following Technical News.
List of valid devices applicable for
GOT1000 series (GOT-A-0010)
*1
GT09-C30USB-5P(3m)
(packed together with the
printer unit)
GOT
Option device
Model
GT15-PRN*1
For the system
configuration between
the GOT and PLC,
refer to each chapter.
Number of
connectable
equipment
1 printer for
1 GOT
Communication unit between the GOT and the PictBridge compatible printer.
GOT does not support some PictBridge Compatible Printers. For the precautions for printer connection, refer to the following
Technical News.
List of valid devices applicable for GOT1000 series (GOT-A-0010)
HINT
System configuration between the GOT and PLC
For the system configuration between the GOT and PLC, refer to each chapter.
Mitsubishi Products
Non-Mitsubishi Products 1, Non-Mitsubishi Products 2
Microcomputer, MODBUS Products, Peripherals
13 - 2
PLC
13. PRINTER CONNECTION
13.1 Connectable Model List
Extended function OS Communication driver
Connection type
dependent
Serial
printer
GOT
Connection cable 2)
PC REMOTE
CONNECTION
Connection cable 1)
10
PLC
Varies according to the connection type.
Printer
Connection cable 1)
Connection cable 2)
Model name
Model name
Model name
Option device
-
- (Built into
GOT)
GT10-C02H-6PT9P
(0.2m)
- (Built into
GOT)
-
GT15-RS2-9P
For connectable printers and
system equipment, refer to the
following Technical News.
List of valid devices
applicable for GOT1000
series (GOT-A-0010)
*1
RS-232 cable
GOT
Model
PLC
For the system
configuration
between the GOT
and PLC, refer to
each chapter.
Number of
connectable
equipment
1 printer for
1 GOT
11
VNC(R) SERVER
CONNECTION
Printer (serial)
BAR CODE READER
CONNECTION
9
Connecting to serial printer
12
The RS-232 cable differs depending on the specification of the printer to be used. Use the RS-232 cable that is compatible with
the printer to be used.
HINT
VIDEO/RGB
CONNECTION
13.2.2
13
System configuration between the GOT and PLC
For the system configuration between the GOT and PLC, refer to each chapter.
PRINTER
CONNECTION
Mitsubishi Products
Non-Mitsubishi Products 1, Non-Mitsubishi Products 2
Microcomputer, MODBUS Products, Peripherals
MULTIMEDIA
CONNECTION
14
RFID CONNECTION
15
13. PRINTER CONNECTION
13.2 System Configuration
13 - 3
13.3 GOT Side Settings
13.3.1
Setting communication
interface
 Printer setting
 Controller setting
(For GT16, GT15)
2.
4.
Set the channel of the equipment to be connected to
the GOT.
2.
Click!
3.
3.
4.
1.
2.
3.
Click!
1.
2.
3.
4.
Select [Common]
menu.
[Controller Setting] from the
The Controller Setting window is displayed. Select the
channel to be used from the list menu.
Set Manufacturer, Controller Type, I/F, and Driver
according to the connected equipment to be used.
The detailed setting is displayed after Manufacturer,
Controller Type, I/F, and Driver are set.
Make the settings according to the usage
environment.
Click the [OK] button when settings are completed.
POINT
The settings of connecting equipment can be set and
confirmed in [I/F Communication Setting]. For details,
refer to the following.
1.1.2 I/F communication setting
13 - 4
13. PRINTER CONNECTION
13.3 GOT Side Settings
4.
Select [Common]
from the menu.
[Peripheral Setting]
[Printer]
Select the printer type.
For GT14 and GT10, only "Serial" can be selected.
Set the interface to which the printer is connected.
When Serial is selected in Printer type, clicking the
detail setting button displays the Communication
Detail Settings dialog box for the communication
driver. Make the settings according to the usage
environment.
13.3.2 Communication detail settings
Click the [OK] button when settings are completed.
POINT
(1) Setting the communication interface
When Channel No.8 is used for the serial printer,
the following external devices, which use Channel
No.8, cannot be connected at the same time.
• Fingerprint authentication device
• Barcode reader that requires the power supply
When connecting the above-mentioned devices at
the same time, set the serial printer to Channels
No. 5 to 7.
For GT14 and GT11, the serial printer and
barcode reader cannot be connected at the same
time.
(2) Setting for the driver
Regardless of the printer type, multiple printers
are cannot be set.
Make the settings according to the usage environment.
POINT
(1) Communication interface setting by the Utility
The communication interface setting can be
changed on the Utility's [Communication setting]
after writing [Communication Settings] of project
data.
For details on the Utility, refer to the following
manual.
User's Manual of GOT used.
(2) Precedence in communication settings
When settings are made by GT Designer3 or the
Utility, the latest setting is effective.
BAR CODE READER
CONNECTION
9
Communication detail settings
10
PC REMOTE
CONNECTION
13.3.2
Range
Set this item when change the
transmission speed used for
communication with printer.
(Default: 19200bps)
4800bps,
9600bps,
19200bps,
38400bps,
57600bps,
115200bps
Set this item when change the
data length used for
communication with printer.
(Default: 8bits)
7bits/8bits
Stop Bit
Specify the stop bit length for
communications.
(Default: 1bit)
1bit/2bits
Parity
Specify whether or not to
perform a parity check, and how
it is performed during
communication.
(Default: None)
None
Even
Odd
Retry
Set the number of retries to be
performed when a
communication error occurs.
(Default: 0times)
0 to 5times
Timeout Time
Set the time period for a
communication to time out.
(Default: 30sec)
3 to 90sec
Delay Time
Set this item to adjust the
transmission timing of the
communication request from the
GOT.
(Default: 0ms)
0 to 300ms
Control Method
Set this item when selecting the
XON/XOFF control for the
control method.
(Default: XON/XOFF)
XON/XOFF,
fixed
*1
13
PRINTER
CONNECTION
Data
Bit*1
12
14
MULTIMEDIA
CONNECTION
Transmission
Speed
VIDEO/RGB
CONNECTION
Description
15
RFID CONNECTION
Item
VNC(R) SERVER
CONNECTION
11
When using the hard copy function, set to 8bit.
13. PRINTER CONNECTION
13.3 GOT Side Settings
13 - 5
13.4 Precautions
 Connection/disconnection of USB cable
during print operation
When the USB cable is disconnected during print
operation, the printer hangs up depending on the model
of PictBridge compatible printer. In this case, turn on
the main power of the printer and then restart it.
 When a printer cannot perform print
operation
While the initialization of the printer is being carried out
at boot time, some models of PictBridge compatible
printers send "Print Ready" signal to GOT.If printing
operation is started from GOT, an error will occur and
the printing operation will be disabled.If this occurs,
restart a printer with the following procedure.
1.
Disconnect the USB cable from the printer.
2.
Turn the power of the printer OFF.
3.
4.
5.
6.
Disconnect the power supply cable of the printer and
stop the printer completely.
Connect the power supply cable to the printer.
Turn the power of the printer ON and wait until the
initialization processing of the printer is completed.
Connect the USB cable to the printer.
For the handling errors occurred on the printer, refer to
the following.
Manual for the printer being used
13 - 6
13. PRINTER CONNECTION
13.4 Precautions
10
PC REMOTE
CONNECTION
MULTIMEDIA CONNECTION
BAR CODE READER
CONNECTION
14
9
14.
14.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 - 2
14.3 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 - 4
14.4 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 - 5
13
PRINTER
CONNECTION
14.5 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 - 7
12
VIDEO/RGB
CONNECTION
14.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 - 2
VNC(R) SERVER
CONNECTION
11
MULTIMEDIA
CONNECTION
14
RFID CONNECTION
15
14 - 1
14. MULTIMEDIA CONNECTION
14.1 Connectable Model List
For the type of CF card that can be inserted or connectable video camera types, refer to the following Technical News.
List of valid devices applicable for GOT1000 series (GOT-A-0010)
Visit the Mitsubishi Electric FA Equipment Information Service website (MELFANSweb) to refer to the Technical News.
http://wwwf2.mitsubishielectric.co.jp/english/index.html
POINT
Before making the multimedia connection
Update the software version of the multimedia unit to the latest version.
For the version upgrade of the multimedia unit, refer to the following manual.
GT16 User’s Manual (Hardware)
14.2 System Configuration
14.2.1
Saving video image and displaying it on GOT
Extended function OS
Multimedia
Video camera,
Microphone,
Speaker
GOT
Connection cable
Multimedia controller
Signal type
*3
NTSC/PAL
*1
*2
Connection cable
Coaxial connection
diagram 1)
GOT
Max.
distance
Option device
*1
GT16M-MMR*2
Model
*4
The cable length differs depending on the specification of the video camera used by the user.
For the CF card to be inserted into the multimedia unit, refer to the following.
• Type of CF card that can be inserted
List of valid devices applicable for GOT1000 series (GOT-A-0010)
• Precautions for using the CF card
14 - 2
*3
14.4 GOT Side Settings
For the type of the video camera that can be connected, refer to the following Technical News.
*4
List of valid devices applicable for GOT1000 series (GOT-A-0010)
GT1675-VN, GT1672-VN, GT1662-VN, and GT1655-V cannot be used.
14. MULTIMEDIA CONNECTION
14.1 Connectable Model List
Number of connectable
equipment
1 multimedia controller for 1
GOT
Extended function OS
Multimedia
Video camera,
Microphone,
Speaker
Ethernet
Interface
(Built into GOT)
Coaxial
connection
diagram 1)
*1
*2
*3
*4
*1
GT16M-MMR
*4
*7
GT16M-MMR
PC REMOTE
CONNECTION
length*8
Twisted pair cable
• 10BASE-T
Shielded twisted
pair cable (STP) or
unshielded twisted
pair cable (UTP):
Category 3, 4, and 5
• 100BASE-TX
Shielded twisted pair
cable (STP):
Category 5 and 5e
100m
Personal
computer
*6
To be
selected
by the
user.
Number of
connectable
equipment
1 multimedia
controller for 1
GOT
The cable length differs depending on the specification of the video camera used by the user.
The destination connected with the twisted pair cable varies with the configuration of the applicable Ethernet network system.
Connect to the Ethernet module, hub, transceiver, wireless LAN adapter (NZ2WL-JPA or NZ2WL-JPS), or other system
equipment corresponding to the applicable Ethernet network system.
Use cables, connectors, and hubs that meet the IEEE802.3 10BASE-T/100BASE-TX standards.
For the controllers that can be connected to the wireless LAN adapters and how to set the wireless LAN adapter, refer to the
manual of the wireless LAN adapter used.
When connecting GT16 of the function version A to an equipment that meets the 10BASE (-T/2/5) standard, use the switching
hub and operate in a 10Mbps/100Mbps mixed environment.
For how to check the function version, refer to the following.
GT16 User’s Manual (Hardware)
For the CF card to be inserted into the multimedia unit, refer to the following.
• Type of CF card that can be inserted
List of valid devices applicable for GOT1000 series (GOT-A-0010)
• Precautions for using the CF card
*5
*6
*7
*8
11
12
13
14
14.4 GOT Side Settings
For the type of the video camera that can be connected, refer to the following Technical News.
List of valid devices applicable for GOT1000 series (GOT-A-0010)
Install the multimedia interaction tool before use.
For details of the multimedia interaction tool, refer to the following manual.
GT Designer3 Version1 Screen Design Manual
GT1675-VN, GT1672-VN, and GT1662-VN cannot be used.
A length between a hub and a node.
The maximum distance differs depending on the Ethernet device to be used.
The following shows the number of the connectable nodes when a repeater hub is used.
• 10BASE-T: Max. 4 nodes for a cascade connection (500m)
• 100BASE-TX: Max. 2 nodes for a cascade connection (205m)
When switching hubs are used, the cascade connection between the switching hubs has no logical limit for the number of
cascades.
For the limit, contact the switching hub manufacturer.
POINT
Power supply of video camera
Depending on the video camera type, noises from the power supply cable of the camera may cause a malfunction
on the PLC or the GOT. In this case, apply the following line filter to the power line of the camera.
Recommended line filter: TDK ZHC2203-11 (or equivalent)
14. MULTIMEDIA CONNECTION
14.2 System Configuration
14 - 3
MULTIMEDIA
CONNECTION
*5
NTSC
/PAL
Cable model
Maximum
segment
VNC(R) SERVER
CONNECTION
Model
Option device
(Interface 2))
VIDEO/RGB
CONNECTION
Option device
(Interface 1))
Connection cable 2)
PRINTER
CONNECTION
Model name
Max.
distance
interface 2)
GOT*2*3
Connection cable 1)
10
PC
Connection cable 2)
interface 1)
Signal
type
Connection type
dependent
Gateway (FTP)
GOT
Connection cable 1)
Multimedia
controller
Communication driver
Option OS
BAR CODE READER
CONNECTION
9
Sending video image to personal computer
15
RFID CONNECTION
14.2.2
14.3 Connection Diagram
The coaxial cable used for connecting the GOT to a video
camera should be prepared by the user.
The following shows each cable connection diagram.
14.3.1
Coaxial cable
The following shows the connection diagrams and
connector specifications of the coaxial cable used for
connecting the GOT to a video camera.
 Connection diagram
Coaxial connection diagram 1)
Displaying video image on GOT
75Ω drohmcoaxial
GOT side
BNC connector
Signal
GND
Video camera/
vision sensor side
Signal
BNC connector
GND
Cable specification
Item
Specifications
Applicable cable
3C-2V, 5C-2V (JIS C 3501 compliant)
 Connecting the BNC connector to the coaxial
cable
For connecting the BNC connector and coaxial cable,
refer to the following.
1.4.2 Coaxial cable connector connection
method
 Precautions when preparing a cable
(1) Cable length
The cable length differs depending on the specification
of the video camera to be used.
Create a cable under the specification of the video
camera.
(2) GOT side connector
Use the following as the multimedia unit connector.
For the GOT side connector of the coaxial cable, use
the ones compatible with the GOT connector.
GOT
GT16M-MMR
Connector
model
227161-4
Connector
type
Manufacturer
BNC
Tyco International, Ltd.
(3) Video camera side connector
Use a connector compatible with the video camera to
be used.
14 - 4
14. MULTIMEDIA CONNECTION
14.3 Connection Diagram
HINT
When the coaxial cable is long
When the coaxial cable is long, video signals are
attenuated by the cable.
The use of a video signal amplifier is recommended to
correct the attenuated signals.
Connect a video signal amplifier in reference to the
following:
• Coaxial cable: The cable length is 100m or more
when 3C-2V is used.
• Coaxial cable: The cable length is 200m or more
when 5C-2V is used.
9
14.4.1
Setting communication
interface
BAR CODE READER
CONNECTION
14.4 GOT Side Settings
 Multimedia setting
2.
 Controller setting
4.
10
PC REMOTE
CONNECTION
Set the channel of the equipment to be connected to
the GOT.
2.
11
VNC(R) SERVER
CONNECTION
3.
4.
3.
4.
3.
[Controller Setting] from the
The Controller Setting window is displayed. Select the
channel to be used from the list menu.
1.
Set Manufacturer, Controller Type, I/F, and Driver
according to the connected equipment to be used.
2.
The detailed setting is displayed after Manufacturer,
Controller Type, I/F, and Driver are set.
Make the settings according to the usage
environment.
3.
Click!
Select [Common]
[Peripheral Setting]
[Multimedia] from the menu.
Set the interface to which the multimedia controller is
connected.
Check the [Enable the setting of Multimedia] to set the
function. For details on the communication settings,
refer to the following manual.
GT Designer3 Version1 Screen Design Manual
Click the [OK] button when settings are completed.
POINT
The settings of connecting equipment can be set and
confirmed in [I/F Communication Setting]. For details,
refer to the following.
1.1.2 I/F communication setting
4.
Clicking the detail setting button displays the
Communication Detail Settings dialog box for each
communication driver.Make the settings according to
the usage environment.
14.4.2 Communication detail settings
Click the [OK] button when settings are completed.
14. MULTIMEDIA CONNECTION
14.4 GOT Side Settings
14 - 5
13
PRINTER
CONNECTION
2.
Select [Common]
menu.
14
MULTIMEDIA
CONNECTION
1.
15
RFID CONNECTION
Click!
VIDEO/RGB
CONNECTION
12
14.4.2
Communication detail settings
14.4.3
Make the settings according to the usage environment.
Installing and setting
multimedia interaction tool
onto personal computer
Install the multimedia interaction tool onto the personal
computer and set it.
For how to install and set multimedia interaction tool, refer
to the following manual.
GT Designer3 Version1 Screen Design Manual
POINT
When saving a video image and displaying it on the
GOT, the installation and setting of the multimedia
interaction tool onto the personal computer are
unnecessary.
14.4.4
(1) Video Setting
Item
Description
Video Input
Signal
*1
Video Resolution*2
*1
*2
Range
Set the video input signal.
(Default: NTSC)
NTSC, PAL
Set the video resolution.
640
480,
720
480,
768
576
When NTSC format is selected, the resolution is fixed to
640 480.When PAL format is selected, the resolution is
fixed to 768 576.
For GT1675M-V and GT1665M-V, the resolution is fixed to
640 480.
Set the multimedia function.
For the multimedia function setting, refer to the following
manual.
GT Designer3 Version1 Screen Design Manual
14.4.5
For the gateway function setting, refer to the following.
GOT1000 Series Gateway Functions Manual
for GT Works3
Set the network settings for connecting from the
multimedia unit via Ethernet.
Description
Range
IP Address
Set the IP address of the
multimedia unit.
(Default: 192.168.3.51)
0.0.0.0 to
255.255.255.255
Subnet Mask
Set the subnet mask for the sub
network. (Only for connection via
router) If the sub network is not
used, the default value is set.
(Default: 255.255.255.0)
0.0.0.0 to
255.255.255.255
Default
Gateway
Set the router address of the
default gateway on the side to
which the multimedia unit is
connected. (Only for connection
via router)
(Default: 0.0.0.0)
0.0.0.0 to
255.255.255.255
POINT
Network settings with the utility
The network setting can be changed on the Utility's
[Communication setting] after writing [Communication
Settings] of project data.
For details on the Utility, refer to the following manual.
User's Manual of GOT used.
14 - 6
14. MULTIMEDIA CONNECTION
14.4 GOT Side Settings
Set the gateway function
Set the gateway function for using FTP.
(2) IP Address Setting for Multimedia Unit
Item
Setting the multimedia function
POINT
To save a video image and display it on the GOT
When saving a video image and displaying it on the
GOT, the gateway function setting is unnecessary.
9
BAR CODE READER
CONNECTION
14.5 Precautions
 When the multimedia function is used
The multimedia function and the video/RGB function
are written exclusively.
Select either of them to use.
10
 CF card on the multimedia unit
PC REMOTE
CONNECTION
For the CF card that can be inserted into the
multimedia unit, formatting in FAT32 is recommended.
If the CF card formatted in FAT16 is inserted, the
following phenomena may occur.
• Reading, writing or saving of movie files takes time.
• When a movie file is played, the movie momentarily
looks like as if it stopped.
VNC(R) SERVER
CONNECTION
11
VIDEO/RGB
CONNECTION
12
PRINTER
CONNECTION
13
MULTIMEDIA
CONNECTION
14
RFID CONNECTION
15
14. MULTIMEDIA CONNECTION
14.5 Precautions
14 - 7
14 - 8
14. MULTIMEDIA CONNECTION
14.5 Precautions
10
PC REMOTE
CONNECTION
RFID CONNECTION
BAR CODE READER
CONNECTION
15
9
15.
15.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 - 2
15.3 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 - 3
15.4 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 - 5
12
VIDEO/RGB
CONNECTION
15.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 - 2
VNC(R) SERVER
CONNECTION
11
PRINTER
CONNECTION
13
MULTIMEDIA
CONNECTION
14
RFID CONNECTION
15
15 - 1
15. RFID CONNECTION
15.1 Connectable Model List
For connectable RFID controllers and system equipment, refer to the following Technical bulletin.
List of valid devices applicable for GOT1000 series (GOT-A-0010)
Visit the Mitsubishi Electric FA Equipment Information Service website (MELFANSweb) to refer to the Technical News.
http://wwwf2.mitsubishielectric.co.jp/english/index.html
15.2 System Configuration
15.2.1
Connecting to RFID
Extended function OS
Communication driver
Connection type
dependent
RFID
RFID controller
GOT
PLC
Connection cable
Varies according to the connection type.
RFID controller
Connection cable
Model name
For connectable RFID controllers and system
equipment, refer to the following Technical
bulletin.
List of valid devices applicable for
GOT1000 series (GOT-A-0010)
Varies according to
specification of RFID
controllers.
GOT
Option device
PLC
Model
- (Built into
GOT)
For the system
configuration
between the GOT
and PLC, refer to
each chapter.
Number of connectable
equipment
1 RFID controller for
1 GOT
GT15-RS2-9P
POINT
When using the RS-232 communication unit
Use the RS-232 communication unit of the GOT for connecting to an RFID controller.
However, when the RS-232 communication unit is used, the following operations cannot be supported.
(a) Using the external authentication
(b) Supplying the power to an RFID controller from the GOT
HINT
System configuration between the GOT and PLC
For the system configuration between the GOT and PLC, refer to each chapter.
Mitsubishi Products
Non-Mitsubishi Products 1, Non-Mitsubishi Products 2
Microcomputer, MODBUS Products, Peripherals
15 - 2
15. RFID CONNECTION
15.1 Connectable Model List
9
 RFID setting
Set the channel of the equipment to be connected to
the GOT.
2.
10
4.
PC REMOTE
CONNECTION
2.
3.
VNC(R) SERVER
CONNECTION
11
4.
1.
2.
3.
4.
Select [Common]
menu.
[Controller Setting] from the
The Controller Setting window is displayed. Select the
channel to be used from the list menu.
Set Manufacturer, Controller Type, I/F, and Driver
according to the connected equipment to be used.
The detailed setting is displayed after Manufacturer,
Controller Type, I/F, and Driver are set.
Make the settings according to the usage
environment.
1.
2.
3.
Select [Common]
from the menu.
[Peripheral Setting]
[RFID]
13
Set the interface to which the RFID controller is
connected.
Check the [Use RFID] to set the function. For details
on the function setting, refer to the following manual.
GT Designer3 Version1 Screen Design Manual
4.
Clicking the detail setting button displays the
Communication Detail Settings dialog box for each
communication driver.Make the settings according to
the usage environment.
15.3.2 Communication detail settings
Click the [OK] button when settings are completed.
Click the [OK] button when settings are completed.
POINT
The settings of connecting equipment can be set and
confirmed in [I/F Communication Setting]. For details,
refer to the following.
1.1.2 I/F communication setting
VIDEO/RGB
CONNECTION
3.
Click!
12
Click!
PRINTER
CONNECTION
 Controller setting
14
MULTIMEDIA
CONNECTION
Setting communication interface
15
POINT
(1) Communication interface setting
When Channel No.8 is used, the following external
devices, which use Channel No.8, cannot be
connected at the same time.
• Fingerprint authentication device
• Barcode reader that requires the power supply
When connecting the above-mentioned devices at
the same time, set [RFID] to Channels No. 5 to 7.
(2) Setting for the driver
To Channels No. 5 to 8, multiple [RFID] cannot be
set.
15. RFID CONNECTION
15.3 GOT Side Settings
15 - 3
RFID CONNECTION
15.3.1
BAR CODE READER
CONNECTION
15.3 GOT Side Settings
15.3.2
Communication detail settings
POINT
(1) Communication interface setting by the Utility
The communication interface setting can be
changed on the Utility's [Communication setting]
after writing [Communication Settings] of project
data.
For details on the Utility, refer to the following
manuals.
User's Manual of GOT used.
(2) Precedence in communication settings
When settings are made by GT Designer3 or the
Utility, the latest setting is effective.
Item
Description
Range
Transmission
Speed
Set this item when change the
transmission speed used for
communication with the connected
equipment.
(Default: 9600bps)
4800bps,
9600bps,
19200bps,
38400bps,
57600bps,
115200bps
Data Bit
Set this item when change the data
length used for communication with
the connected equipment.
(Default: 8bits)
7bits/8bits
Stop Bit
Specify the stop bit length for
communications.
(Default: 1bit)
1bit/2bits
Parity
Specify whether or not to perform a
parity check, and how it is performed
during communication.
(Default: Even)
None
Even
Odd
Sum Check
Set whether or not to perform a sum
check during communication.
(Default: Done)
Yes or No
Retry
Set the number of retries to be
performed when a communication
timeout occurs.
When receiving no response after
retries, the communication times
out. (Default: 0time)
0 to 5times
Timeout Time
Set the time period for a
communication to time out.
(Default: 3sec)
3 to 30sec
Delay Time
Set this item to adjust the
transmission timing of the
communication request from the
GOT.
(Default: 0ms)
0 to 3000ms
Format
Select the communication format.
(Default: 15)
Dedicated protocol
• Format 10 (LS Industrial Systems
Co., Ltd. LSR)
• Format 11 (MARS TECHNO
SCIENCE Corp. ICU-60S)
• Format 12 (MARS TECHNO
SCIENCE Corp. ICU-215
(Mifare))
Nonprocedural protocol
• Format 15
10/11/12/15
15 - 4
15. RFID CONNECTION
15.3 GOT Side Settings
9
BAR CODE READER
CONNECTION
15.4 Precautions
 RFID function setting on GT Designer3
Before connecting the RFID controller, set the RFID
function and system data.
For details, refer to the following manual.
10
GT Designer3 Version1 Screen Design Manual
PC REMOTE
CONNECTION
 Controller setting
(1) When using the external authentication
When using the external authentication on the RFID
controller, set Channel No. 8 using the standard
interface.
When connecting the RFID using Channels No. 5 to 7
of the extension interface, extension interface cannot
be used.
For details on the external authentication, refer to the
following manual.
VNC(R) SERVER
CONNECTION
11
GT Designer3 Version1 Screen Design Manual
(2) When requiring the power supply
12
VIDEO/RGB
CONNECTION
When using the RFID controller, which requires the
power supply from the GOT, set Channel No. 8 using
the standard interface.
With Channels No. 5 to 7 of the extension interface, the
power cannot be supplied.
 Communication in multiple RFID readers/
When connecting multiple RFID readers/writers, some
controllers may communicate with each RFID reader/
writer.
13
For communicating the RFID controller with the each
RFID reader/writer, set an interlock so that the RFID
controller does not communicate with RFID readers/
writers until the executing communication is completed.
PRINTER
CONNECTION
writers connection
MULTIMEDIA
CONNECTION
14
RFID CONNECTION
15
15. RFID CONNECTION
15.4 Precautions
15 - 5
15 - 6
15. RFID CONNECTION
15.4 Precautions
MICROCOMPUTER CONNECTION
(SERIAL) .......................................................... 2-77
MODBUS(R)/RTU CONNECTION................... 4-12
MODBUS(R)/TCP CONNECTION ..................... 5-3
MULTIMEDIA CONNECTION.......................... 14-5
PC REMOTE CONNECTION................... 10-4,10-8
PRINTER CONNECTION ................................ 13-4
RFID CONNECTION........................................ 15-3
VIDEO/RGB CONNECTION ............................ 12-7
VNC(R) SERVER CONNECTION.................... 11-3
[B]
BAR CODE READER CONNECTION................... 9-1
[C]
Coaxial cable ....................................................... 1-27
Communication module....................................... 1-15
Connectable Model List
BAR CODE READER CONNECTION ............... 9-2
CONNECTION TO EXTERNAL I/O DEVICE..... 7-2
CONNECTION TO SOUND OUTPUT UNIT...... 6-2
FINGERPRINT AUTHENTICATION DEVICE
CONNECTION................................................... 8-2
MODBUS(R)/RTU CONNECTION..................... 4-2
MODBUS(R)/TCP CONNECTION..................... 5-2
MULTIMEDIA CONNECTION.......................... 14-2
PC REMOTE CONNECTION .......................... 10-2
PRINTER CONNECTION ................................ 13-2
RFID CONNECTION ....................................... 15-2
VIDEO/RGB CONNECTION............................ 12-2
VNC(R) SERVER CONNECTION ................... 11-2
Connection Diagram
CONNECTION TO EXTERNAL I/O DEVICE..... 7-4
MICROCOMPUTER CONNECTION
(SERIAL)............................................................ 2-6
MODBUS(R)/RTU CONNECTION..................... 4-4
MULTIMEDIA CONNECTION.......................... 14-4
PC REMOTE CONNECTION .......................... 10-3
VIDEO/RGB CONNECTION............................ 12-5
CONNECTION TO EXTERNAL I/O DEVICE ........ 7-1
CONNECTION TO SOUND OUTPUT UNIT ......... 6-1
Controller Type ...................................................... 1-5
Conversion cable................................................. 1-16
[D]
Device Range that Can Be Set
MICROCOMPUTER CONNECTION
(SERIAL).......................................................... 2-82
MODBUS(R)/TCP CONNECTION..................... 5-6
[F]
FINGERPRINT AUTHENTICATION DEVICE
CONNECTION ...................................................... 8-1
[G]
GOT connector specifications ............................. 1-24
GOT Side Settings
BAR CODE READER CONNECTION ............... 9-3
CONNECTION TO EXTERNAL I/O DEVICE... 7-12
CONNECTION TO SOUND OUTPUT UNIT...... 6-3
FINGERPRINT AUTHENTICATION DEVICE
CONNECTION................................................... 8-3
MICROCOMPUTER CONNECTION
(ETHERNET) ................................................... 3-69
[I]
I/F........................................................................... 1-6
I/F communication setting.................................... 1-10
[M]
MICROCOMPUTER CONNECTION
(ETHERNET) ......................................................... 3-1
MICROCOMPUTER CONNECTION (SERIAL)..... 2-1
MODBUS(R)/RTU CONNECTION ........................ 4-1
MODBUS(R)/TCP CONNECTION......................... 5-1
MULTIMEDIA CONNECTION ............................. 14-1
[O]
Option unit ........................................................... 1-16
[P]
PC REMOTE CONNECTION .............................. 10-1
Precautions
BAR CODE READER CONNECTION ............... 9-7
CONNECTION TO EXTERNAL I/O DEVICE... 7-13
CONNECTION TO SOUND OUTPUT UNIT...... 6-4
FINGERPRINT AUTHENTICATION DEVICE
CONNECTION ................................................... 8-4
MICROCOMPUTER CONNECTION
(ETHERNET) ................................................... 3-74
MICROCOMPUTER CONNECTION
(SERIAL) .......................................................... 2-83
MODBUS(R)/RTU CONNECTION................... 4-17
MODBUS(R)/TCP CONNECTION ................... 5-15
MULTIMEDIA CONNECTION.......................... 14-7
PRINTER CONNECTION ................................ 13-6
VIDEO/RGB CONNECTION ............................ 12-8
PREPARATORY PROCEDURES FOR
MONITORING ....................................................... 1-1
PRINTER CONNECTION.................................... 13-1
[R]
RFID CONNECTION ........................................... 15-1
[S]
Station No. settings
MODBUS(R)/RTU CONNECTION................... 4-17
Index-1
INDEX
INDEX
System Configuration
BAR CODE READER CONNECTION ............... 9-2
CONNECTION TO EXTERNAL I/O DEVICE
..................................................................... 7-2,7-3
CONNECTION TO SOUND OUTPUT UNIT...... 6-2
FINGERPRINT AUTHENTICATION DEVICE
CONNECTION ................................................... 8-2
MICROCOMPUTER CONNECTION
(ETHERNET) ..................................................... 3-2
MICROCOMPUTER CONNECTION
(SERIAL) ............................................................ 2-4
MODBUS(R)/RTU CONNECTION..................... 4-3
MULTIMEDIA CONNECTION.................. 14-2,14-3
PC REMOTE CONNECTION................... 10-2,10-7
PRINTER CONNECTION ................................ 13-2
RFID CONNECTION........................................ 15-2
VIDEO/RGB CONNECTION .................... 12-3,12-4
VNC(R) SERVER CONNECTION.................... 11-2
[T]
Terminating resistors of GOT .............................. 1-28
[V]
VIDEO/RGB CONNECTION ............................... 12-1
VNC(R) SERVER CONNECTION ....................... 11-1
Index-2
REVISIONS
* The manual number is given on the bottom left of the back cover.
Print Date
* Manual Number
Revision
Oct., 2009
SH(NA)-080871ENG-A
First edition: Compatible with GT Works3 Version1.01B
Jan., 2010
SH(NA)-080871ENG-B
Compatible with GT Works3 Version1.10L
• Correction of writing errors
• Station monitoring function (Ethernet multiple connection compatible, temperature controller connection
compatible), microcomputer (Ethernet connection compatible), PC remote (Ethernet connection compatible)
• In the communication detail settings for the Ethernet connection, the setting range of the GOT communication
port No. is changed.
May., 2010
SH(NA)-080871ENG-C
Compatible with GT Works3 Version1.14Q
• In the communication detail settings for the Ethernet connection, the setting range of the GOT communication
port No. is changed.
Jun., 2010
SH(NA)-080871ENG-D
Compatible with GT Works3 Version1.17T
• GT1675-VN, GT1672-VN, and GT1662-VN are added.
• Microcomputer connection (serial) (multiple-GT10 connection compatible), barcode reader connection, RFID
connection (direct input compatible for numerical input and ASCII input), printer connection (serial printer
compatible)
Oct., 2010
SH(NA)-080871ENG-E
Compatible with GT Works3 Version1.19V
• MODBUS(R)/RTU connection, MODBUS(R)/TCP connection communication control function (multiple
connection) compatible
• Correction of microcomputer connection (Ethernet) formats 6 and 7 (4E frame)
• Microcomputer connection special interrupt code (RFID) compatible
Jan., 2011
SH(NA)-080871ENG-F
Compatible with GT Works3 Version1.23Z
• Microcomputer connection (Ethernet) formats 8 and 9 (QnA compatible 3E frame) compatible
Apr., 2011
SH(NA)-080871ENG-G
Compatible with GT Works3 Version1.28E
• GT1655-VTBD is added.
Jul., 2011
SH(NA)-080871ENG-H
Compatible with GT Works3 Version1.31H
• The GT10 supports specifying a word device by using bits with the microcomputer connection.
Oct., 2011
SH(NA)-080871ENG-I
Compatible with GT Works3 Version1.37P
• GT14, GT12 are added.
• VNC(R) server connection compatible
Jan., 2012
SH(NA)-080871ENG-J
Compatible with GT Works3 Version1.40S
• "I/F Communication Setting" is compatible with "5V power supply".
• RS-232/485 signal conversion adaptor is added.
Apr., 2012
SH(NA)-080871ENG-K
Compatible with GT Works3 Version1.45X
• The supplemental explanation for Ethernet cascade connection is added and the writing errors are corrected.
Jun., 2012
SH(NA)-080871ENG-L
Compatible with GT Works3 Version1.54G
• The printer is compatible for GT14 and GT10.
• Ping test at the GT14 main unit compatible
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.
© 2009 MITSUBISHI ELECTRIC CORPORATION
REVISIONS - 1
REVISIONS - 2
WARRANTY
Please confirm the following product warranty details before using this product.
1. Gratis Warranty Term and Gratis Warranty Range
If any faults or defects (hereinafter "Failure") found to be the responsibility of Mitsubishi occurs during use of the product within the
gratis warranty term, the product shall be repaired at no cost via the sales representative or Mitsubishi Service Company.
However, if repairs are required onsite at domestic or overseas location, expenses to send an engineer will be solely at the
customer's discretion. Mitsubishi shall not be held responsible for any re-commissioning, maintenance, or testing on-site that
involves replacement of the failed module.
[Gratis Warranty Term]
The gratis warranty term of the product shall be for thirty-six (36) months after the date of purchase or delivery to a designated
place.
Note that after manufacture and shipment from Mitsubishi, the maximum distribution period shall be six (6) months, and the
longest gratis warranty term after manufacturing shall be forty-two (42) months. The gratis warranty term of repair parts shall not
exceed the gratis warranty term before repairs.
[Gratis Warranty Range]
(1) The customer shall be responsible for the primary failure diagnosis unless otherwise specified.
If requested by the customer, Mitsubishi Electric Corporation or its representative firm may carry out the primary failure
diagnosis at the customer’s expence.
The primary failure diagnosis will, however, be free of charge should the cause of failure be attributable to Mitsubishi Electric
Corporation.
(2) The range shall be limited to normal use within the usage state, usage methods and usage environment, etc., which follow
the conditions and precautions, etc., given in the instruction manual, user's manual and caution labels on the product.
(3) Even within the gratis warranty term, repairs shall be charged for in the following cases.
1. Failure occurring from inappropriate storage or handling, carelessness or negligence by the user. Failure caused by the
user's hardware or software design.
2. Failure caused by unapproved modifications, etc., to the product by the user.
3. When the Mitsubishi product is assembled into a user's device, Failure that could have been avoided if functions or
structures, judged as necessary in the legal safety measures the user's device is subject to or as necessary by industry
standards, had been provided.
4. Failure that could have been avoided if consumable parts designated in the instruction manual had been correctly
serviced or replaced.
5. Replacing consumable parts such as the battery, backlight and fuses.
6. Failure caused by external irresistible forces such as fires or abnormal voltages, and Failure caused by force majeure
such as earthquakes, lightning, wind and water damage.
7. Failure caused by reasons unpredictable by scientific technology standards at time of shipment from Mitsubishi.
8. Any other failure found not to be the responsibility of Mitsubishi or that admitted not to be so by the user.
2. Onerous repair term after discontinuation of production
(1) Mitsubishi shall accept onerous product repairs for seven (7) years after production of the product is discontinued.
Discontinuation of production shall be notified with Mitsubishi Technical Bulletins, etc.
(2) Product supply (including repair parts) is not available after production is discontinued.
3. Overseas service
Overseas, repairs shall be accepted by Mitsubishi's local overseas FA Center. Note that the repair conditions at each FA Center
may differ.
4. Exclusion of loss in opportunity and secondary loss from warranty liability
Regardless of the gratis warranty term, Mitsubishi shall not be liable for compensation to damages caused by any cause found not
to be the responsibility of Mitsubishi, loss in opportunity, lost profits incurred to the user by Failures of Mitsubishi products, special
damages and secondary damages whether foreseeable or not, compensation for accidents, and compensation for damages to
products other than Mitsubishi products, replacement by the user, maintenance of on-site equipment, start-up test run and other
tasks.
5. Changes in product specifications
The specifications given in the catalogs, manuals or technical documents are subject to change without prior notice.
6. Product application
(1) In using the Mitsubishi graphic operation terminal, the usage conditions shall be that the application will not lead to a major
accident even if any problem or fault should occur in the graphic operation terminal device, and that backup and fail-safe
functions are systematically provided outside of the device for any problem or fault.
(2) The Mitsubishi graphic operation terminal has been designed and manufactured for applications in general industries, etc.
Thus, applications in which the public could be affected such as in nuclear power plants and other power plants operated by
respective power companies, and applications in which a special quality assurance system is required, such as for Railway
companies or Public service purposes shall be excluded from the graphic operation terminal applications.
In addition, applications in which human life or property that could be greatly affected, such as in aircraft, medical applications,
incineration and fuel devices, manned transportation equipment for recreation and amusement, and safety devices, shall also
be excluded from the graphic operation terminal range of applications.
However, in certain cases, some applications may be possible, providing the user consults the local Mitsubishi representative
outlining the special requirements of the project, and providing that all parties concerned agree to the special circumstances,
solely at our discretion.
In some of three cases, however, Mitsubishi Electric Corporation may consider the possibility of an application, provided that
the customer notifies Mitsubishi Electric Corporation of the intention, the application is clearly defined and any special quality is
not required.
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.
Pentium and Celeron are registered trademarks of Intel Corporation in the United States and other countries.
Ethernet is a 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)-080871ENG-L
Series
Connection Manual
(Microcomputer, MODBUS Products, Peripherals) for GT Works3
MODEL
SW1-GTD3-U(CON4)-E
MODEL
CODE
1D7MC5
SH(NA)-080871ENG-L(1206)MEE
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
When exported from Japan, this manual does not require application to the
Ministry of Economy, Trade and Industry for service transaction permission.
Specifications subject to change without notice.
Printed in Japan, June 2012.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement