Contents

Mitsubishi GOT2000 GT25 Microcomputer Connection Manual PDF

1 of 466
1 of 466

Summary of Content for Mitsubishi GOT2000 GT25 Microcomputer Connection Manual PDF

GOT2000 Series Connection Manual (Microcomputers, MODBUS/ Fieldbus Products, Peripherals) For GT Works3 Version1

-GT27 model -GT25 model -GT25 open frame model -GT25 wide model -GT25 rugged model -GT23 model -GT21 model -GT21 wide model

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 "WARNING" and "CAUTION".

Note that failure to observe CAUTION may lead to a serious accident depending on the circumstances. Make sure to observe both warnings and cautions to ensure personal safety. Please save this manual to make it accessible when required and always forward it to the end user.

[DESIGN PRECAUTIONS]

WARNING Some failures of the GOT, communication unit or cable may keep the outputs on or off.

Some failures of a touch panel may cause malfunction of the input objects such as a touch switch. 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.

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.

When the GOT backlight has a failure, the GOT status will be as follows. Failure to observe this instruction may result in an accident due to incorrect output or malfunction. [GT27, GT25, GT23] The POWER LED blinks (orange/blue), the display section dims, and inputs by a touch switch are disabled. [GT2105-Q] The POWER LED blinks (orange/blue), and the display section dims. However, inputs by a touch switch are still available. [GT2107-W, GT2104-R, GT2104-P, GT2103-P, GS21] The display section dims. However, inputs by a touch switch are still available. Even if the display section dims, inputs by a touch switch may still be available. This may cause an unintended operation of the touch switch. For example, if an operator assumes that the display section has dimmed because of the screen save function and touches the display section to cancel the screen save, a touch switch may be activated. The GOT backlight failure can be checked with a system signal of the GOT. (This system signal is not available on GT2107-W, GT2104-R, GT2104-P, GT2103-P, and GS21.)

WARNING

CAUTION

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

Indicates that incorrect handling may cause hazardous conditions, resulting in minor or moderate injury or property damage.

1

2

[DESIGN PRECAUTIONS]

WARNING The display section of the GOT is an analog-resistive type touch panel.

When multiple points of the display section are touched simultaneously, an accident may occur due to incorrect output or malfunction. [GT27] Do not touch three points or more simultaneously on the display section. Doing so may cause an accident due to an incorrect output or malfunction. [GT25, GT23, GT21, GS21] Do not touch two points or more simultaneously on the display section. Doing so may cause a touch switch near the touched points to operate unexpectedly, or may cause an accident due to an 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 turn on the unit again after shutting off the power as soon as possible. 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. (1) For bus connection (GT27 and GT25 only): The GOT becomes inoperative. Power on the PLC CPU again to reestablish communication. (2) 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.

To maintain the security (confidentiality, integrity, and availability) of the GOT and the system against unauthorized access, DoS*1 attacks, computer viruses, and other cyberattacks from unreliable networks and devices via network, take appropriate measures such as firewalls, virtual private networks (VPNs), and antivirus solutions. Mitsubishi Electric shall have no responsibility or liability for any problems involving GOT trouble and system trouble by unauthorized access, DoS attacks, computer viruses, and other cyberattacks. *1 DoS: A denial-of-service (DoS) attack disrupts services by overloading systems or exploiting vulnerabilities, resulting in a denial-of-service (DoS) state.

[DESIGN PRECAUTIONS]

[MOUNTING PRECAUTIONS]

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 connects to an Ethernet network, the IP address setting is restricted according to the system configuration. [GT27, GT25, GT23] When a GOT2000 series model and a GOT1000 series model are on an Ethernet network, do not set the IP address 192.168.0.18 for the GOTs and the controllers on this network. Doing so can cause IP address duplication at the GOT startup, adversely affecting 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. [GT21, GS21] Setting the IP address (192.168.3.18) in the following system configurations can cause IP address duplication at GOT startup, adversely affecting communications of the device whose IP address is 192.168.3.18. The operation at IP address duplication depends on the devices and the system. When multiple GOTs connect to the Ethernet network: Do not set the IP address (192.168.3.18) for the GOTs and the controllers in the network. When one GOT connects to the Ethernet network: Do not set the IP address (192.168.3.18) for the controllers other than the GOT in the network.

When using the Ethernet interfaces, set an IP address for each interface to access a different network.

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.

When the GOT is subject to shock or vibration, or some colors appear on the screen of the GOT, the screen of the GOT might flicker.

WARNING Be sure to shut off all phases of the external power supply used by the system before mounting or

removing the GOT main unit to/from the panel. Not doing so can cause the unit to fail or malfunction.

Be sure to shut off all phases of the external power supply used by the system before mounting or removing the option unit onto/from the GOT. (GT27, GT25 Only)

3

4

[MOUNTING PRECAUTIONS]

CAUTION Use the GOT in the environment that satisfies the general specifications described in this 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 with a Phillips-head screwdriver No. 2. [GT27, GT25-W, GT2512-S, GT2510-V, GT2508-V, GT23, GT2107-W] Specified torque range (0.36 Nm to 0.48 Nm) [GT2505-V, GT2105-Q] Specified torque range (0.30 Nm to 0.50 Nm) [GT2104-R, GT2104-P, GT2103-P] Specified torque range (0.20 Nm to 0.25 Nm) 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 mounting a unit on the GOT, tighten the mounting screws in the following specified torque range. [GT27, GT25 (except GT25-W)] When loading the communication unit or option unit other than wireless LAN unit to the GOT, fit it to the connection interface of the GOT and tighten the mounting screws in the specified torque range (0.36 Nm to 0.48 Nm) with a Phillips-head screwdriver No. 2. When loading the wireless LAN unit to the GOT, fit it to the side interface of GOT and tighten the mounting screws in the specified torque range (0.10 Nm to 0.14 Nm) with a Phillips-head screwdriver No. 1. When the GOT is installed vertically, its side interface is positioned on the bottom. To prevent the falling of the wireless LAN communication unit from the side interface, install or remove the unit while holding it with hands. [GT25-W] When mounting the wireless LAN communication unit on the GOT, fit it to the wireless LAN communication unit interface and tighten the mounting screws in the specified torque range (0.10 Nm to 0.14 Nm) with a Phillips-head screwdriver No.1. [GT2103-P] When mounting the SD card unit on the GOT, fit it to the side of the GOT and tighten the tapping screws in the specified torque range (0.3 Nm to 0.6 Nm) with a Phillips-head screwdriver No. 2. Under tightening 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 closing the USB environmental protection cover, note the following points to ensure the IP rating. [GT27, GT25 (except GT25-W and GT2505-V)] Push the [PUSH] mark on the latch firmly to fix the cover to the GOT. [GT2512-WX, GT2510-WX, GT2507-W, GT2505-V, GT2107-W] Push the USB mark on the latch firmly to fix the cover to the GOT. [GT2105-Q] Tighten the lower fixing screws of the cover in the specified torque range (0.36 Nm to 0.48 Nm) to fix the cover to the GOT.

[MOUNTING PRECAUTIONS]

[WIRING PRECAUTIONS]

CAUTION Remove the protective film of the GOT.

When the user continues using the GOT with the protective film, the film may not be removed. In addition, for the models equipped with the human sensor function, using the GOT with the protective film may cause the human sensor not to function properly.

For GT2512F-S, GT2510F-V, and GT2508F-V, attach an environmental protection sheet dedicated to the open frame model (sold separately) to the display section. Or, attach a user-prepared environmental protection sheet. Not doing so may damage or soil the GOT or cause foreign matter to enter the GOT, resulting in a failure or malfunction.

When installing the supplied fittings on GT2512F-S, GT2510F-V, or GT2508F-V, tighten screws in the specified torque range (0.8 Nm to 1.0 Nm). Meld studs on the control panel to fasten the fittings. The studs must have strength adequate to withstand a tightening torque of 0.9 Nm or more. Make sure that no foreign matter such as welding waste is at and around the bases of the studs. Tighten nuts on the studs in the specified torque range (0.8 Nm to 0.9 Nm) with a wrench for M4 nuts. Undertightening a screw or nut may cause the GOT to drop, short-circuit, or malfunction. Overtightening a screw or nut may damage it or the GOT, causing the GOT to drop, short-circuit, or malfunction.

Do not operate or store the GOT in the environment exposed to direct sunlight, rain, high temperature, dust, humidity, or vibrations.

Although GT2507T-W is ruggedized for environments such as UV rays, temperatures and vibrations, its operation is not guaranteed in all conditions and environments. Make sure to use or store the GOT in an appropriate environment.

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.

Do not operate the GOT with its display section frozen. The water droplets on the display section may freeze at a low temperature. Touch switches and other input objects may malfunction if the display section is frozen.

WARNING 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.

5

6

[WIRING PRECAUTIONS]

CAUTION When grounding the FG terminal and LG terminal of the GOT power supply section, note the following

points. Not doing so may cause an electric shock or malfunction. [GT27, GT25, GT23, GT2107-W, GT2105-Q, GS21] Make sure to ground the FG terminal and LG terminal of the GOT power supply section solely for the GOT (ground resistance: 100 or less, cross-sectional area of the ground cable: 2.0 mm2 or more). (GT2705-V, GT25-W, GT2505-V, GT2107-W, GT2105-Q, and GS21 do not have the LG terminal.) [GT2104-R, GT2104-P, GT2103-P] Make sure to ground the FG terminal of the GOT power supply section with a ground resistance of 100 or less. (For GT2104-PMBLS and GT2103-PMBLS, grounding is unnecessary.)

When tightening the terminal screws, use the following screwdrivers. [GT27, GT25, GT23, GT2107-W, GT2105-Q, GS21] Use a Phillips-head screwdriver No. 2. [GT2104-R, GT2104-P, GT2103-P] For the usable screwdrivers, refer to the following. GOT2000 Series User's Manual (Hardware)

Tighten the terminal screws of the GOT power supply section in the following specified torque range. [GT27, GT25, GT23] Specified torque range (0.5 Nm to 0.8 Nm)

For a terminal processing of a wire to the GOT power supply section, use the following terminal. [GT27, GT25, GT23, GT2107-W, GT2105-Q, GS21] Use applicable solderless terminals for terminal processing of a wire and tighten them with the specified torque. Not doing so can cause a fire, failure or malfunction. [GT2104-R, GT2104-P, GT2103-P] Connect a stranded wire or a solid wire directly, or use a rod terminal with an insulation sleeve.

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 following specified torque range. [GT27, GT25, GT23, GT2107-W, GT2105-Q] Specified torque range (0.5 Nm to 0.8 Nm) [GT2104-R, GT2104-P, GT2103-P] Specified torque range (0.22 Nm to 0.25 Nm) [GS21] Specified torque range (0.5 Nm to 0.6 Nm)

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.

Some models have an ingress prevention label on their top to prevent foreign matter, such as wire offcuts, from entering the GOT during wiring. Do not peel this label during wiring. Before starting system operation, be sure to peel this label because of heat dissipation.

[WIRING PRECAUTIONS]

[TEST OPERATION PRECAUTIONS]

[STARTUP/MAINTENANCE PRECAUTIONS]

CAUTION Plug the communication cable into the GOT interface or the connector of the connected unit, and

tighten the mounting screws and the 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.

WARNING Before testing the operation of a user-created screen (such as turning on or off a bit device, changing

the current value of a word device, changing the set value or current value of a timer or counter, and changing the current value of a buffer memory), thoroughly read the manual to fully understand the operating procedure. During the test operation, never change the data of the devices which are used to perform significant operation for the system. Doing so may cause an accident due to an incorrect output or malfunction.

WARNING 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.

7

8

[STARTUP/MAINTENANCE PRECAUTIONS]

[TOUCH PANEL PRECAUTIONS]

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 from 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 the module or subject it to strong shock. A module damage may result. 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 metals, etc. to discharge static electricity from human body, etc. Not doing so can cause the unit to fail or malfunction.

Use the battery manufactured by Mitsubishi Electric Corporation. Use of other batteries may cause 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.

Be sure to shut off all phases of the external power supply before replacing the battery or using the dip switch of the terminating resistor. Not doing so can cause the unit to fail or malfunction by static electricity.

Before cleaning the GOT, be sure to turn off the power. Before cleaning, check the following items. Ensure that there are no problems with the installation condition of the GOT to the control panel. Ensure that there are no damages on the environmental protection sheet (not replaceable). If the environmental protection sheet peels or the cleaning solution enters between the sheet and the display section during cleaning, stop the cleaning immediately. In such a case, do not use the GOT.

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.

[PRECAUTIONS FOR USING A DATA STORAGE]

[PRECAUTIONS FOR USING A DATA STORAGE]

WARNING Do not remove the SD card from drive A while the SD card is being accessed by the GOT, or the GOT

may stop processing for about 20 seconds. During this stop, you cannot operate the GOT, and the functions running in the background, including the screen refresh, alarm, logging, and script, also stop. This stop may affect the system operation, causing an accident. Before removing the SD card, check the following items. [GT27, GT25, GT23(Excluding GT2505-V and GT25HS-V)] Before removing the SD card, check that the SD card access LED is off. [GT2505-V, GT25HS-V] Make sure to turn off the SD card access switch before removing the SD card.Not doing so may damage the SD card and files. [GT21, GS21] Disable the SD card access in the GOT utility, and then check that the SD card access LED is off before removing the SD card.

Do not remove the data storage from the file server (drive N) that is being accessed by the GOT, or the system operation may be affected. Before removing the data storage, check the relevant system signal to make sure that the data storage is not being accessed.

CAUTION Do not remove the data storage from the GOT while the data storage is being accessed by the GOT,

or the data storage and files may be damaged. Before removing the data storage, check the SD card access LED, relevant system signal, or others to make sure that the data storage is not being accessed.

Turning off the GOT while it accesses the SD card results in damage to the SD card and files. When using the GOT with an SD card inserted, check the following items.

[GT27, GT25, GT23(Excluding GT2505-V and GT25HS-V)] After inserting an SD card into the GOT, make sure to close the SD card cover. Otherwise, data cannot be read or written. [GT2505-V, GT25HS-V] After inserting an SD card into the GOT, make sure to turn on the SD card access switch. Otherwise, data cannot be read or written. [GT21, GS21] After inserting an SD card into the SD card unit, make sure to enable the SD card access in the GOT utility. Otherwise, data cannot be read or written.

9

10

[PRECAUTIONS FOR USING A DATA STORAGE]

[PRECAUTIONS FOR USE]

[PRECAUTIONS FOR REMOTE CONTROL]

CAUTION When removing the SD card from the GOT, make sure to support the SD card by hand as it may pop

out. Not doing so may cause the SD card to drop from the GOT, resulting in a failure or break.

When inserting a USB device into a USB interface of the GOT, make sure to insert the device into the interface firmly. Not doing so may cause the USB device to drop from the GOT, resulting in a failure or break. (GT27, GT25, and GT2107-W)

Before removing the data storage from the GOT, follow the procedure for removal on the utility screen of the GOT. After the successful completion dialog is displayed, remove the data storage by hand carefully. Not doing so may cause the data storage to drop from the GOT, resulting in a failure or break.

CAUTION Do not touch the edges of the touch panel (display section) repeatedly.

Doing so may result in a failure. Do not turn off the GOT while data is being written to the storage memory (ROM) or SD card.

Doing so may corrupt the data, rendering the GOT inoperative. The GOT rugged model uses the environmental protection sheet (not replaceable) with UV protection

function on the front surface. Therefore, it is possible to suppress deterioration of the touch panel or the liquid crystal display panel that may be caused by ultraviolet rays. Note that if the rugged model is exposed to ultraviolet rays for an extended period of time, the front surface may turn yellow. If the rugged model is likely to be exposed to ultraviolet rays for an extended period of time, it is recommended to use a UV protective sheet (option).

WARNING Remote control is available through a network by using GOT functions, including theSoftGOT-GOT

link function, the remote personal computer operation function, the VNC server function, and the GOT Mobile function. If you remotely operate control equipment using such functions, the field operator may not notice the remote operation, leading to an accident. In addition, a communication delay or interruption may occur depending on the network environment, and remote control of control equipment cannot be performed normally in some cases. Before using the above functions to perform remote control, fully grasp the circumstances of the field site and ensure safety.

When operating the server (GOT) of the GOT Mobile function to disconnect a client, notify the operator of the client about the disconnection beforehand. Not doing so may cause an accident.

[PRECAUTIONS FOR EXCLUSIVE AUTHORIZATION CONTROL]

[DISPOSAL PRECAUTIONS]

[TRANSPORTATION PRECAUTIONS]

WARNING Before using the GOT network interaction function to prevent simultaneous operations from multiple

pieces of equipment, make sure you understand the function. You can enable or disable the exclusive authorization control of the GOT network interaction function for each screen. (For all screens, the exclusive authorization control is disabled by default.) Properly determine the screens for which the exclusive authorization control is required, and set the control by screen. A screen for which the exclusive authorization control is disabled is operable simultaneously from multiple pieces of equipment. Make sure to determine the operation period for each operator, fully grasp the circumstances of the field site, and ensure safety to perform operations.

CAUTION When disposing of this product, treat it as industrial waste.

When disposing of batteries, separate them from other wastes according to the local regulations. (Refer to the GOT2000 Series Users Manual (Hardware) for details of the battery directive in the EU member states.)

CAUTION When transporting lithium batteries, make sure to treat them based on the transport regulations.

(Refer to the GOT2000 Series Users Manual (Hardware) for details of the regulated models.) 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 this manual, as they are precision devices. Failure to do so may cause the unit to fail. Check if the unit operates correctly after transportation.

When fumigants that contain halogen materials such as fluorine, chlorine, bromine, and iodine are used for disinfecting and protecting wooden packaging from insects, they cause malfunction when entering our products. Please take necessary precautions to ensure that remaining materials from fumigant do not enter our products, or treat packaging with methods other than fumigation (heat method). Additionally, disinfect and protect wood from insects before packing products.

11

12

CONTENTS SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Manuals for GT Works3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Abbreviations, Generic Terms, and Model Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

PART 1 PREPARATORY PROCEDURES FOR MONITORING

CHAPTER 1 PREPARATORY PROCEDURES FOR MONITORING 30 1.1 Setting the Communication Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Setting connected equipment (Channel setting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 GOT Ethernet Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 I/F communication setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

1.2 Writing the Package Data onto the GOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Writing the Package Data onto the GOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Checking the package data writing on GOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

1.3 Option Devices for the Respective Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Communication module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Option unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Conversion cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Serial Multi-Drop Connection Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Field network adapter unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 RS-232/485 signal conversion adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Precautions when installing units on top of one another . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

1.4 Connection Cables for the Respective Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 GOT connector specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Coaxial cableconnector connection method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Terminating resistors of GOT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Setting the RS-232/485 signal conversion adaptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

1.5 Verifying GOT Recognizes Connected Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 1.6 Checking for Normal Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Check on the GOT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Confirming the communication state on the GOT side (For Ethernet connection) . . . . . . . . . . . . . . . . . . . . . . . 63 Confirming the communication state to each station (Station monitoring function). . . . . . . . . . . . . . . . . . . . . . . 65 Check on the PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

PART 2 MICROCOMPUTER

CHAPTER 2 MICROCOMPUTER CONNECTION (SERIAL) 70 2.1 Microcomputer Connection (Serial). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 2.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

For the microcomputer connection (serial) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 2.3 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

RS-232 cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 RS-422 cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

C O

N TE

N TS

2.4 Device Data Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 D devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 R devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 L devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 M devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 SD devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 SM devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

2.5 Message Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Data format type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 List of commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Formats 1, 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Formats 3 to 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Formats 7 to 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Formats 11 to 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Formats 14, 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

2.6 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Setting communication interface (Controller Setting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

2.7 System Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 2.8 Device Range that Can Be Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 2.9 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

CHAPTER 3 MICROCOMPUTER CONNECTION (ETHERNET) 161 3.1 Microcomputer connection (Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 3.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

For the microcomputer connection (Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 3.3 Device Data Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

D devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 R devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 L devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 M devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 SD devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 SM devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

3.4 Message Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 Data format type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 List of commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Formats 1, 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Formats 3, 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194 Format 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Formats 6, 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Formats 8, 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

3.5 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Setting communication interface (Controller Setting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 GOT Ethernet Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

3.6 System Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 3.7 Device Range that Can Be Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 3.8 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

13

14

PART 3 ODVA

CHAPTER 4 DeviceNet CONNECTION 238 4.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 4.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Connecting to DeviceNet master equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 4.3 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 4.4 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Setting communication interface (Controller Setting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

4.5 Preparation of EDS File for GOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 How to acquire EDS file for GOT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

4.6 DeviceNet master equipment Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 4.7 Device Range that Can Be Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 4.8 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

PART 4 MODBUS

CHAPTER 5 MODBUS/RTU MASTER CONNECTION 248 5.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 5.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

Connecting to MODBUS/RTU slave equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 5.3 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

RS-232 cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252 RS-422/485 cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

5.4 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Setting communication interface (Controller Setting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

5.5 MODBUS/RTU Slave Equipment Side Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263 Station number setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

5.6 Function Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 5.7 MODBUS Communication Control Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 5.8 Device Range that Can Be Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 5.9 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

CHAPTER 6 MODBUS/TCP MASTER CONNECTION 267 6.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267 6.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Connecting to MODBUS/TCP slave equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 6.3 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Setting communication interface (Controller Setting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 GOT Ethernet Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Connected Ethernet controller setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

6.4 MODBUS/TCP Slave Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 6.5 Function Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 6.6 MODBUS Communication Control Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 6.7 Device Range that Can Be Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274 6.8 Example of Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

C O

N TE

N TS

Connecting to SCHNEIDER PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Connecting to YOKOGAWA PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

6.9 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

CHAPTER 7 MODBUS/RTU SLAVE CONNECTION 283 7.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283 7.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Connecting to MODBUS/RTU master equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 7.3 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

RS-232 cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 RS-422/485 cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

7.4 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Setting communication interface (Controller Setting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

7.5 MODBUS/RTU master equipment Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 7.6 Function Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 7.7 GOT (Slave) Operations for All Station Specification (Broadcast) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 7.8 Device Range that Can Be Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 7.9 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

CHAPTER 8 MODBUS/TCP SLAVE CONNECTION 299 8.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299 8.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300

Connecting to MODBUS/TCP master equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 8.3 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

Setting communication interface (Controller Setting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 GOT Ethernet Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

8.4 MODBUS/TCP Master Equipment Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 8.5 Function Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 8.6 Device Range that Can Be Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 8.7 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

PART 5 PROFIBUS

CHAPTER 9 PROFIBUS DP CONNECTION 306 9.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 9.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

Connecting to PROFIBUS DP master equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 9.3 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

Recommended PROFIBUS DP cable and connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 PROFIBUS DP Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

9.4 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Setting communication interface (Controller Setting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

9.5 Preparation of GSD File for GOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 How to acquire GSD file for GOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

9.6 PROFIBUS DP master equipment Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 9.7 Device Range that Can Be Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 9.8 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

15

16

PART 6 CLPA

CHAPTER 10 SLMP CONNECTION 316 10.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 10.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Connecting to SLMP equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 10.3 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

Setting communication interface (Controller Setting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319 GOT Ethernet Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Connected Ethernet controller setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Routing parameter setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

10.4 SLMP Equipment Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 10.5 Device Range that Can Be Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 10.6 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

CHAPTER 11 CC-Link IE Field NETWORK BASIC CONNECTION 325 11.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 11.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

When connecting to the CC-Link IE Field Network Basic master station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 11.3 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Setting communication interface (Controller Setting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329 GOT Ethernet Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

11.4 Master Station Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 11.5 Device Range that Can Be Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331 11.6 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

PART 7 CONNECTIONS TO PERIPHERAL EQUIPMENT

CHAPTER 12 CONNECTION TO SOUND OUTPUT UNIT 334 12.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 12.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Connecting to sound output unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 12.3 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Setting communication interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 12.4 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

CHAPTER 13 CONNECTION TO EXTERNAL I/O DEVICE 337 13.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 13.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Connecting to the external I/O device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338 13.3 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

Connection cable between external I/O unit and connector/terminal block converter module . . . . . . . . . . . . . 340 Connection diagram between connector/terminal block converter module and operation panel . . . . . . . . . . . 343 Connection cable between external I/O unit and operation panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

13.4 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 Setting communication interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

13.5 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

C O

N TE

N TS

CHAPTER 14 BAR CODE READER CONNECTION 355 14.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 14.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

Connecting to bar code reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 14.3 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

RS-232 cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 14.4 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

Setting communication interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

14.5 System Configuration Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 When using a serial bar code reader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 When using a USB bar code reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

14.6 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

CHAPTER 15 PC REMOTE CONNECTION 369 15.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 15.2 Serial Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370

System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372 GOT Side Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 Installing and setting up computer remote operation driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

15.3 Ethernet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 GOT Side Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 Install and setting the required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381

CHAPTER 16 GOT Mobile CONNECTION 383 16.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 16.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 16.3 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

GOT Mobile setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 Setting communication interface (Controller Setting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

16.4 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

CHAPTER 17 VNC SERVER CONNECTION 389 17.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 17.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389 17.3 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

VNC server function setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392 Setting communication interface (Controller Setting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

17.4 Setting in Personal Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

CHAPTER 18 VIDEO, HDMI, AND RGB CONNECTION 395 18.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 18.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

Displaying video image on GOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 Displaying GOT screen on external display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

17

18

18.3 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 Coaxial cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 Analog RGB cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

18.4 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 Setting communication interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 Setting the video/RGB function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

18.5 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

CHAPTER 19 PRINTER CONNECTION 403 19.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 19.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

Connecting to PictBridge compatible printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404 Connecting to serial printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 Connecting an Ethernet printer (ESC/P-R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 Connecting an Ethernet printer (PCL5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408

19.3 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410 RS-232 cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410

19.4 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 Setting communication interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413

19.5 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

CHAPTER 20 MULTIMEDIA CONNECTION 415 20.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 20.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415

Saving video image and displaying it on GOT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 Sending video image to personal computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

20.3 Connection Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 Coaxial cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

20.4 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 Setting communication interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421 Installing and setting multimedia interaction tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422 Setting the multimedia function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422 Set the gateway function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422

20.5 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422

CHAPTER 21 RFID CONNECTION 423 21.1 Connectable Model List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 21.2 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

Connecting to RFID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 21.3 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

Setting communication interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427

21.4 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428

C O

N TE

N TS

CHAPTER 22 WIRELESS LAN CONNECTION 429 22.1 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

Connecting to wireless LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 22.2 GOT Side Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

Wireless LAN setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431 Setting communication interface (GOT Ethernet setting) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431 Communication detail settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432

22.3 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432

APPENDIX 433 Appendix 1 Settable Device Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433

Microcomputer ([Computer]) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 ODVA ([DeviceNet]). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 MODBUS ([MODBUS Slave(GOT:Master)]) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 MODBUS ([MODBUS Master(GOT:Slave)]) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444 PROFIBUS ([PROFIBUS DP]) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 CLPA ([SLMP]) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 CLPA ([CC-Link IE Field Network Basic]) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455

REVISIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459 WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .461 Intellectual Property Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .462

19

20

INTRODUCTION Thank you for choosing Mitsubishi Electric Graphic Operation Terminal (GOT). Before using the product, read this manual carefully and make sure you understand the functions and performance of the GOT for correct use. Manuals for GT Works3 Abbreviations, Generic Terms, and Model Icons

Manuals for GT Works3 The electronic manuals related to this product are installed together with the screen design software. If you need the printed manuals, consult your local sales office.

Manuals for GT Designer3 (GOT2000)

e-Manual refers to the Mitsubishi Electric FA electronic book manuals that can be browsed using a dedicated tool. e-Manual has the following features: Required information can be cross-searched in multiple manuals. Other manuals can be accessed from the links in the manual. Hardware specifications of each part can be found from the product figures. Pages that users often browse can be bookmarked. Sample programs can be copied to the engineering tool.

Screen design software-related manuals

Connection manuals

Manual name Manual number (Model code)

Format

GT Works3 Installation Instructions - PDF

GT Designer3 (GOT2000) Screen Design Manual SH-081220ENG (1D7ML9)

PDF e-Manual

GT Converter2 Version3 Operating Manual for GT Works3 SH-080862ENG (1D7MB2)

PDF e-Manual

GOT2000 Series MES Interface Function Manual for GT Works3 Version1 SH-081228ENG PDF e-Manual

Manual name Manual number (Model code)

Format

GOT2000 Series Connection Manual (Mitsubishi Electric Products) For GT Works3 Version1 SH-081197ENG (1D7MJ8)

PDF e-Manual

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

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

GOT2000 Series Connection Manual (Microcomputers, MODBUS/Fieldbus Products, Peripherals) For GT Works3 Version1

SH-081200ENG PDF e-Manual

GOT2000 Series Handy GOT Connection Manual For GT Works3 Version1 SH-081867ENG (1D7MS9)

PDF e-Manual

GOT2000 Series Connection Manual (2 Connection) for GT Works3 Version1 JY997D52301 PDF e-Manual

GT SoftGOT2000 manuals

GOT2000 series user's manuals

GOT SIMPLE series user's manuals

Manuals related to GT Works3 add-on projects

Manuals for GT Designer3 (GOT1000) Refer to the Help and manuals for GT Designer3 (GOT1000).

Manual name Manual number (Model code)

Format

GT SoftGOT2000 Version1 Operating Manual SH-081201ENG PDF e-Manual

MELSOFT GT OPC UA Client Operating Manual SH-082174ENG PDF

Manual name Manual number (Model code)

Format

GOT2000 Series User's Manual (Hardware) SH-081194ENG (1D7MJ5)

PDF e-Manual

GOT2000 Series User's Manual (Utility) SH-081195ENG (1D7MJ6)

PDF e-Manual

GOT2000 Series User's Manual (Monitor) SH-081196ENG (1D7MJ7)

PDF e-Manual

Manual name Manual number Format GOT SIMPLE Series User's Manual JY997D52901 PDF

e-Manual

Manual name Manual number (Model code)

Format

GT Works3 Add-on License for GOT2000 Enhanced Drive Control (Servo) Project Data Manual (Fundamentals)

SH-082072ENG (1D7MV1)

PDF e-Manual

GT Works3 Add-on License for GOT2000 Enhanced Drive Control (Servo) Project Data Manual (Screen Details)

SH-082074ENG (1D7MV3)

PDF e-Manual

21

22

Abbreviations, Generic Terms, and Model Icons The following shows the abbreviations, generic terms, and model icons used in this manual.

GOT GOT2000 series Abbreviations and generic terms Description Meaning of icon

Available Unavailable GT27 GT27-X GT2715-X GT2715-XTBA

GT2715-XTBD -

GT27-S GT2712-S GT2712-STBA GT2712-STWA GT2712-STBD GT2712-STWD

GT2710-S GT2710-STBA GT2710-STBD

GT2708-S GT2708-STBA GT2708-STBD

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

GT2708-V GT2708-VTBA GT2708-VTBD

GT2705-V GT2705-VTBD

GT25 All GT25 models -

GT25-W GT2512-WX GT2512-WXTBD GT2512-WXTSD

-

GT2510-WX GT2510-WXTBD GT2510-WXTSD

GT2507-W GT2507-WTBD GT2507-WTSD

GT2507T-W GT2507T-WTSD

GT25-S GT2512-S GT2512-STBA GT2512-STBD

GT2512F-S GT2512F-STNA GT2512F-STND

GT25-V GT2510-V GT2510-VTBA GT2510-VTWA GT2510-VTBD GT2510-VTWD

GT2510F-V GT2510F-VTNA GT2510F-VTND

GT2508-V GT2508-VTBA GT2508-VTWA GT2508-VTBD GT2508-VTWD

GT2508F-V GT2508F-VTNA GT2508F-VTND

GT2505-V GT2505-VTBD

GT25HS-V Handy GOT

GT2506HS-V GT2506HS-VTBD -

GT2505HS-V GT2505HS-VTBD -

GT23 GT23-V GT2310-V GT2310-VTBA GT2310-VTBD

-

GT2308-V GT2308-VTBA GT2308-VTBD

GOT SIMPLE series

GOT1000 series, GOT900 series, and GOT800 series

GT21 All GT21 models -

GT21-W GT2107-W GT2107-WTBD GT2107-WTSD

-

GT21-Q GT2105-Q GT2105-QTBDS GT2105-QMBDS

-

GT21-R GT2104-R GT2104-RTBD -

GT21-P GT2104-P GT2104-PMBD -

GT2104-PMBDS -

GT2104-PMBDS2 -

GT2104-PMBLS -

GT2103-P GT2103-PMBD -

GT2103-PMBDS -

GT2103-PMBDS2 -

GT2103-PMBLS -

GT SoftGOT2000 GT SoftGOT2000 Version1 -

Abbreviations and generic terms Description Meaning of icon

Available Unavailable GS21 GS21-W-N GS2110-WTBD-N

GS2107-WTBD-N -

GS21-W GS2110-WTBD GS2107-WTBD

Abbreviations and generic terms Description Meaning of icon

Available Unavailable GOT1000 Series GOT1000 Series -

GOT900 Series GOT-A900 Series GOT-F900 Series

-

GOT800 Series GOT-800 Series -

Abbreviations and generic terms Description Meaning of icon

Available Unavailable

23

24

Communication unit

Option unit

Abbreviations and generic terms Description Bus connection unit GT15-QBUS

GT15-QBUS2 GT15-ABUS GT15-ABUS2 GT15-75QBUSL GT15-75QBUS2L GT15-75ABUSL GT15-75ABUS2L

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

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

CC-Link IE TSN communication unit GT25-J71GN13-T2

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

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

CC-Link communication unit GT15-J61BT13

Wireless LAN communication unit GT25-WLAN

Serial multi-drop connection unit GT01-RS4-M

Connection conversion adapter GT10-9PT5S

Field network adapter unit GT25-FNADP

Ethernet communication unit GT25-J71E71-100

RS-232/485 signal conversion adapter GT14-RS2T4-9P

Abbreviations and generic terms Description Printer unit GT15-PRN

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

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

Video/RGB input unit GT27-V4R1-Z (A set of GT16M-V4R1-Z and GT27-IF1000)

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

Digital video output unit GT27-VHOUT

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

Video signal conversion unit GT27-IF1000

External I/O unit GT15-DIO GT15-DIOR

Sound output unit GT15-SOUT

SD card unit GT21-03SDCD

Option Abbreviations and generic terms Description SD card NZ1MEM-2GBSD

NZ1MEM-4GBSD NZ1MEM-8GBSD NZ1MEM-16GBSD L1MEM-2GBSD L1MEM-4GBSD

Battery GT11-50BAT GT15-BAT

Protective sheet GT27-15PSGC GT25-12WPSGC GT25-12PSGC GT25-10WPSGC GT25-10PSGC GT25-08PSGC GT21-07WPSGC GT25T-07WPSVC GT25-05PSGC GT25-05PSGC-2 GT21-05PSGC GT21-04RPSGC-UC GT21-03PSGC-UC GT21-04PSGC-UC GT27-15PSCC GT25-12WPSCC GT25-12PSCC GT25-10WPSCC GT25-10PSCC GT25-08PSCC GT25-05PSCC GT25-05PSCC-2 GT25-12PSCC-UC GT25-10PSCC-UC GT25-08PSCC-UC GT21-07WPSCC GT21-05PSCC GT21-04RPSCC-UC GT21-04PSCC-UC GT21-03PSCC-UC GT16H-60PSC GT14H-50PSC

Antibacterial/antiviral protective sheet GT25-12PSAC GT25-10PSAC GT25-08PSAC

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

Protective cover for oil GT20-15PCO GT20-12PCO GT20-10PCO GT20-08PCO GT21-12WPCO GT21-10WPCO GT21-07WPCO GT25T-07WPCO GT25-05PCO GT25-05PCO-2 GT05-50PCO GT21-04RPCO GT10-30PCO GT10-20PCO

USB environmental protection cover GT25-UCOV GT25-05UCOV GT21-WUCOV

25

26

Software Software related to GOT

Software related to iQ Works

Stand GT15-90STAND GT15-80STAND GT15-70STAND GT05-50STAND GT25-10WSTAND GT21-07WSTAND GT25T-07WSTAND

Attachment GT15-70ATT-98 GT15-70ATT-87 GT15-60ATT-97 GT15-60ATT-96 GT15-60ATT-87 GT15-60ATT-77 GT21-04RATT-40

Panel-mounted USB port extension GT14-C10EXUSB-4S GT10-C10EXUSB-5S

Connector conversion box GT16H-CNB-42S GT16H-CNB-37S GT11H-CNB-37S

Emergency stop switch guard cover GT16H-60ESCOV GT14H-50ESCOV

Wall-mounting attachment GT14H-50ATT

Abbreviations and generic terms Description GT Works3 SW1DND-GTWK3-J, SW1DND-GTWK3-E, SW1DND-GTWK3-C

GT Designer3 Version1 Screen design software GT Designer3 for GOT2000 and GOT1000 series

GT Designer3 Screen design software for GOT2000 series included in GT Works3

GT Designer3 (GOT2000)

GT Designer3 (GOT1000) Screen design software for GOT1000 series included in GT Works3

Speech synthesis license GT Works Text to Speech License (SW1DND-GTVO-M)

Add-on license GT Works3 add-on license for GOT2000 enhanced drive control (servo) project data (SW1DND-GTSV-MZ)

GENESIS64 Advanced GENESIS64 server application (GEN64-APP)

GENESIS64 Basic SCADA GENESIS64 server application (GEN64-BASIC)

GENESIS64 Generic term of GENESIS64 Advanced and GENESIS64 Basic SCADA

GOT Mobile function license for GT SoftGOT2000 License required to use the GOT Mobile function with GT SoftGOT2000 (SGT2K- WEBSKEY-)

GT Simulator3 Screen simulator GT Simulator3 for GOT2000, GOT1000, and GOT900 series

GT SoftGOT2000 GOT2000 compatible HMI software GT SoftGOT2000

GT OPC UA Client MELSOFT GT OPC UA Client (SW1DNN-GTOUC-MD)

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

GT Designer2 Classic Screen design software GT Designer2 Classic for GOT900 series

GT Designer2 Screen design software GT Designer2 for GOT1000 and GOT900 series

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

Abbreviations and generic terms Description iQ Works iQ Platform compatible engineering environment MELSOFT iQ Works

MELSOFT Navigator Integrated development environment software included in SWDND-IQWK (iQ Platform compatible engineering environment MELSOFT iQ Works) ( represents a version.)

MELSOFT iQ AppPortal SWDND-IQAPL-M type integrated application management software ( represents a version.)

Abbreviations and generic terms Description

Other software

License key (for GT SoftGOT2000)

Abbreviations and generic terms Description GX Works3 SWDND-GXW3-E (-EA, -EAZ) type programmable controller engineering software

( represents a version.)

GX Works2 SWDNC-GXW2-E (-EA, -EAZ) type programmable controller engineering software ( represents a version.)

Controller simulator GX Simulator3 Simulation function of GX Works3

GX Simulator2 Simulation function of GX Works2

GX Simulator SWD5C-LLT-E (-EV) type ladder logic test tool function software package (SW5D5C-LLT (-V) or later versions) ( represents a version.)

GX Developer SWD5C-GPPW-E (-EV)/SWD5F-GPPW (-V) type software package ( represents a version.)

GX LogViewer SWDNN-VIEWER-E type software package ( represents a version.)

MI Configurator Configuration and monitor tool for Mitsubishi Electric industrial computers (SWDNNMICONF-M) ( represents a version.)

PX Developer SWD5C-FBDQ-E type FBD software package for process control ( represents a version.)

MT Works2 Motion controller engineering environment MELSOFT MT Works2 (SWDND-MTW2- E) ( represents a version.)

MT Developer SWRNC-GSV type integrated start-up support software for motion controller Q series ( represents a version.)

CW Configurator Setting/monitoring tools for the C Controller module and MELSECWinCPU (SWDND-RCCPU-E) ( represents a version.)

MR Configurator2 SWDNC-MRC2-E type servo configuration software ( represents a version.)

MR Configurator MRZJW-SETUP type servo configuration software ( represents a version.)

FR Configurator2 Inverter setup software (SWDND-FRC2-E) ( represents a version.)

FR Configurator Inverter setup software (FR-SW-SETUP-WE) ( represents a version.)

NC Configurator2 CNC parameter setting support tool (FCSB1221)

NC Configurator CNC parameter setting support tool

FX Configurator-FP Parameter setting, monitoring, and testing software package for FX3U-20SSC-H (SWD5CFXSSCE) ( represents a version.)

FX Configurator-EN-L FX3U-ENET-L type Ethernet module setting software (SW1D5-FXENETL-E)

FX Configurator-EN FX3U-ENET type Ethernet module setting software (SW1D5C-FXENET-E)

RT ToolBox2 Robot program creation software (3D-11C-WINE)

RT ToolBox3 Robot program creation software (3F-14C-WINE)

MX Component MX Component Version (SWD5C-ACT-E, SWD5C-ACT-EA) ( represents a version.)

MX Sheet MX Sheet Version (SWD5C-SHEET-E, SWD5C-SHEET-EA) ( represents a version.)

CPU Module Logging Configuration Tool CPU module logging configuration tool (SW1DNN-LLUTL-E)

Abbreviations and generic terms Description License key GT27-SGTKEY-U

27

28

Others Abbreviations and generic terms Description IAI IAI Corporation

AZBIL Azbil Corporation

OMRON OMRON Corporation

KEYENCE KEYENCE CORPORATION

KOYO EI KOYO ELECTRONICS INDUSTRIES CO., LTD.

JTEKT JTEKT CORPORATION

SHARP Sharp Corporation

SHINKO Shinko Technos Co., Ltd.

CHINO CHINO CORPORATION

TOSHIBA TOSHIBA CORPORATION

SHIBAURA MACHINE SHIBAURA MACHINE CO., LTD.

PANASONIC Panasonic Corporation

PANASONIC IDS Panasonic Industrial Devices SUNX Co., Ltd.

HITACHI IES Hitachi Industrial Equipment Systems Co., Ltd.

HITACHI Hitachi, Ltd.

HIRATA Hirata Corporation

FUJI FUJI ELECTRIC CO., LTD.

MURATEC Muratec products manufactured by Murata Machinery, Ltd.

YASKAWA YASKAWA Electric Corporation

YOKOGAWA Yokogawa Electric Corporation

RKC RKC INSTRUMENT INC.

ALLEN-BRADLEY Allen-Bradley products manufactured by Rockwell Automation, Inc.

CLPA CC-Link Partner Association

GE GE Intelligent Platforms, Inc.

HMS HMS Industrial Networks

LS IS LS Industrial Systems Co., Ltd.

MITSUBISHI INDIA Mitsubishi Electric India Pvt. Ltd.

ODVA Open DeviceNet Vendor Association, Inc.

SCHNEIDER Schneider Electric SA

SICK SICK AG

SIEMENS Siemens AG

SCHNEIDER EJH Schneider Electric Japan Holdings Ltd.

PLC Programmable controller manufactured by its respective company

Control equipment Control equipment manufactured by its respective company

Temperature controller Temperature controller manufactured by its respective company

Indicating controller Indicating controller manufactured by its respective company

Controller Controller manufactured by its respective company

TSN Switch CC-Link IE TSN Class B (Synchronized Realtime Communication) hub certified by CC-Link Partner Association

General-purpose Switch CC-Link IE TSN Class A (Realtime Communication) hub certified by CC-Link Partner Association

CC-Link IE TSN-equipped module Generic term for the following CC-Link IE TSN master/local modules and CC-Link IE TSN Plus master/local module RJ71GN11-T2 RJ71GN11-EIP FX5-CCLGN-MS

PART 1 PREPARATORY PROCEDURES FOR MONITORING

1 PREPARATORY PROCEDURES FOR MONITORING

29

30

1 PREPARATORY PROCEDURES FOR MONITORING

Page 31 Setting the Communication Interface Page 42 Writing the Package Data onto the GOT Page 44 Option Devices for the Respective Connection Page 49 Connection Cables for the Respective Connection Page 59 Verifying GOT Recognizes Connected Equipment Page 61 Checking for Normal Monitoring The following shows the procedures to be taken before monitoring and corresponding reference sections.

1. Setting the communication interface Determine the connection type and channel No. to be used, and perform the communication setting. Page 31 Setting the Communication Interface Each chapter GOT Side Settings

2. Writing the package data Write the project data, system application onto the GOT. Page 42 Writing the Package Data onto the GOT

3. Verifying the package data Verify the project data, system application are properly written onto the GOT. Page 43 Checking the package data writing on GOT

4. Attaching the communication unit and connecting the cable Mount the optional equipment and prepare/connect the connection cable according to the connection type. Page 44 Option Devices for the Respective Connection Page 49 Connection Cables for the Respective Connection Each chapter System Configuration Each chapter Connection Diagram

5. Verifying GOT recognizes connected equipment Verify the GOT recognizes controllers on [Communication Settings] of the Utility. Page 59 Verifying GOT Recognizes Connected Equipment

6. Verifying the GOT is monitoring normally Verify the GOT is monitoring normally using Utility, Developer, etc. Page 61 Checking for Normal Monitoring

1 PREPARATORY PROCEDURES FOR MONITORING

1

1.1 Setting the Communication Interface 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.

Setting connected equipment (Channel setting) Set the channel of the equipment connected to the GOT.

Setting

1. Select [Common] [Controller Setting] from the menu.

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.

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. GOT2000 Series Connection Manual (Mitsubishi Electric Products) For GT Works3 Version1

1 PREPARATORY PROCEDURES FOR MONITORING 1.1 Setting the Communication Interface 31

32

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*].

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

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.

Type Select the type of the equipment to be connected to the GOT. For the settings, refer to the following. Page 33 Setting [Controller Type]

I/F Select the interface of the GOT to which the equipment is connected. For the settings, refer to the following. Page 34 Setting [I/F]

Driver Select the communication driver to be written to the GOT. For the settings, refer to the following. Page 32 Setting [Driver] When multiple communication drivers can be selected, this item is displayed. When only one communication driver can be selected, the driver name is displayed under [Detail Setting].

Detail Setting 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.

1 PREPARATORY PROCEDURES FOR MONITORING 1.1 Setting the Communication Interface

1

Setting [Controller Type] The type differs depending on the device to be used. For the settings, refer to the following.

Type Connectable device [CC-Link IE Field Network Basic] CC-Link IE Field Network Basic master stations

For the CC-Link IE Field Network Basic master stations validated by Mitsubishi Electric Corporation, refer to the following. List of CC-Link IE Field Network Basic-compatible Equipment Validated to Operate with the GOT2000 Series (GOT-A-0149)

[SLMP] SLMP servers For the SLMP-compatible equipment validated by Mitsubishi Electric Corporation, refer to the following Technical Bulletin. List of SLMP-compatible Equipment Validated to Operate with the GOT2000 Series (GOT-A-0153)

[MODBUS Slave(GOT:Master)] MODBUS slaves For the MODBUS slave equipment validated by Mitsubishi Electric Corporation, refer to the following Technical Bulletin. List of Valid Devices Applicable for GOT2000 Series MODBUS Connection for Overseas (GOT-A-0170)

[MODBUS Master(GOT:Slave)] MODBUS master equipment For the MODBUS master equipment validated by Mitsubishi Electric Corporation, refer to the following Technical Bulletin. List of Valid Devices Applicable for GOT2000 Series MODBUS Connection for Overseas (GOT-A-0170)

[DeviceNet] DeviceNet master equipment

[PROFIBUS DP] PROFIBUS DP master equipment

[Computer] Personal computer, microcomputer board, PLC, or other devices

1 PREPARATORY PROCEDURES FOR MONITORING 1.1 Setting the Communication Interface 33

34

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.

3rd stage

2nd stage

1st stage

(Example: In the case of the GT27)

Extension interface

Standard interface 1 (RS-232 interface built in the GOT)

Standard interface 2 (USB interface built in the GOT)

Standard interface 3 (RS-422/485 interface built in the GOT)

Standard interface 4 (Ethernet interface built in the GOT)

1 PREPARATORY PROCEDURES FOR MONITORING 1.1 Setting the Communication Interface

1

GOT Ethernet Setting The GOT can be connected to a different network by using the following network. 1) GOT IP Address Setting Set the following communication port setting. Standard port (When using GT25-W, port 1) Set [GOT IP Address] and [Subnet Mask] in the standard port with a built-in GOT, or port 1. Extension port (When using GT25-W, port 2) Set [GOT IP Address] and [Subnet Mask] in the extension port (the Ethernet interface for the Ethernet communication module), or port 2 with a built-in GOT. When using the GOT other than GT25-W, BootOS Version Z or later is required to use the extension port. For details on writing the BootOS, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual Wireless LAN Set [GOT IP Address], [Subnet Mask], [Peripheral S/W Communication Port No.], and [Transparent Port No.] for the wireless LAN interface. 2) GOT Ethernet Common Setting Set the following setting which is common to the standard port and the extension port, or port 1 and port 2. [Default Gateway] [Peripheral S/W Communication Port No.] [Transparent Port No.] 3) IP Filter Setting By configuring the IP filter setting, the access from the specific IP address can be permitted or shut off.

GOT IP Address Setting Set the GOT IP address.

[Standard Port] or [Port 1] The following shows an example for [Standard Port].

1. Select [Common] [GOT Ethernet Setting] [GOT IP Address Setting] from the menu to display the [GOT Ethernet Setting] window.

2. On the [Standard Port] tab, configure the following settings.

Item Description Range Update GOT Ethernet standard port setting The GOT Ethernet standard port settings are applied on GOT. -

GOT IP Address Set the IP address of the GOT IP Address. (Default:192.168.3.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

Select from GOT Setting List Select the GOT set in [GOT Setting List] dialog. GT Designer3 (GOT2000) Screen Design Manual

-

1 PREPARATORY PROCEDURES FOR MONITORING 1.1 Setting the Communication Interface 35

36

[Extended Port], or [Port 2] The following shows an example for [Extended Port].

1. Select [Common] [GOT Ethernet Setting] [GOT IP Address Setting] from the menu to display the [GOT Ethernet Setting] window.

2. On the [Extended Port] tab, configure the following settings.

Item Description Range Update GOT Ethernet extended port setting The GOT Ethernet extended port settings are applied on GOT. -

Enable Ethernet extended port Enable the ethernet extended port. -

GOT IP Address Set the IP address of the GOT IP Address. (Default:192.168.5.22)

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

Select from GOT Setting List Select the GOT set in [GOT Setting List] dialog. GT Designer3 (GOT2000) Screen Design Manual

-

1 PREPARATORY PROCEDURES FOR MONITORING 1.1 Setting the Communication Interface

1

[Wireless LAN] 1. Select [Common] [GOT Ethernet Setting] [GOT IP Address Setting] from the menu to display the [GOT Ethernet

Setting] window.

2. On the [Wireless LAN] tab, configure the following settings.

GOT IP address For GOT IP address of each Ethernet setting, set a value that network system is different from each other. (When the subnet mask is [255.255.255.0])

Item Description Range Update GOT Wireless LAN I/F setting The wireless LAN interface settings are applied on GOT. -

Enable Wireless LAN I/F Enable the wireless LAN. -

GOT IP Address Set the IP address of the wireless LAN I/F. (Default:192.168.4.20)

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

Select from GOT Setting List Select the GOT set in [GOT Setting List] dialog. GT Designer3 (GOT2000) Screen Design Manual

-

Specify port No. for Wireless LAN Enable the port number setting for the wireless LAN separately from GOT Ethernet common setting.

-

Peripheral S/W Communication Port No. Set the GOT port No. for the communication with the peripheral S/W. (Default: 5015)

1024 to 65534 (Except for 5011 to 5013, 49153 to 49170)

Transparent Port No. Set the GOT port No. for the transparent function. (Default: 5014)

1024 to 65534 (Except for 5011 to 5013, 49153 to 49170)

Driver setting Display [Detail Settings] dialog, Page 432 Communication detail settings

-

192.168.4.20

Set a value that network system is different from each other.

GOT wireless LAN I/F setting

192.168.3.18

GOT standard Ethernet setting

192.168.5.22

GOT extension Ethernet setting

1 PREPARATORY PROCEDURES FOR MONITORING 1.1 Setting the Communication Interface 37

38

GOT Ethernet Common Setting Set the following setting which is common to the standard port and the extension port, or port 1 and port 2.

1. Select [Common] [GOT Ethernet Setting] [GOT Ethernet Common Setting] from the menu to display the [GOT Ethernet Setting] window.

2. Configure the following settings.

IP Filter Setting 1. Select [Common] [GOT Ethernet Setting] [IP Filter Setting] from the menu to display the [GOT Ethernet Setting]

window.

2. For the detailed settings, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

Item Description Range 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

Peripheral S/W Communication Port No. Set the GOT port No. for the communication with the peripheral S/W. (Default: 5015)

1024 to 65534 (Except for 5011 to 5013, 49153 to 49170)

Transparent Port No. Set the GOT port No. for the transparent function. (Default: 5014)

1024 to 65534 (Except for 5011 to 5013, 49153 to 49170)

1 PREPARATORY PROCEDURES FOR MONITORING 1.1 Setting the Communication Interface

1

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] [I/F Communication Setting] from the menu.

2. The I/F Communication Setting dialog box appears. Make the settings with reference to the following explanation.

1 PREPARATORY PROCEDURES FOR MONITORING 1.1 Setting the Communication Interface 39

40

Setting item The following describes the setting items for the standard I/F setting and extension I/F setting. For the detailed explanations, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

Item Description Standard I/F Setting Set channel No. and drivers to the GOT standard interfaces.

CH No. Set the CH No. according to the intended purpose. 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 8: Used for barcode function, RFID function, remote personal computer operation function (serial) A: Used for the report function (with a serial printer), hard copy function (with a serial printer).

Driver Set the driver for the device to be connected. Each communication driver suitable to the channel numbers Each communication driver for connected devices

Detail Setting Set the detailed settings for the communication driver. Refer to each chapter of the equipment to be connected to the GOT.

I/F-1,I/F-2,I/F-3 The communication type of the GOT standard interface is displayed.

RS232 Setting To validate the 5V power supply function in RS232, mark the [Enable the 5V power supply] checkbox. The RS232 setting is invalid when the CH No. of [I/F-1: RS232] is [9]. Not applicable to GT21 and GS21.

Ethernet Connection Setting Set the channel number and the communication driver to the Ethernet interface with a built-in GOT.

CH No. Set the CH No. according to the intended purpose. 0: Not used 1 to 4: Used for connecting a controller of channel No. 1 to 4 set in Setting connected equipment (Channel setting) 9: Used for connecting Host (PC) or Ethernet download A: Used for the remote personal computer operation function (Ethernet), VNC server function, gateway function, and MES interface function. Multi: Used for multi-channel Ethernet connection

Driver Set the driver for the device to be connected. Each communication driver suitable to the channel numbers Each communication driver for connected devices

Detail Setting Set the detailed settings for the communication driver. Refer to each chapter of the equipment to be connected to the GOT.

When GT2104-P or GT2103-P is selected in the GOT type setting

1 PREPARATORY PROCEDURES FOR MONITORING 1.1 Setting the Communication Interface

1

Channel No., drivers, [RS232 Setting] 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. GOT2000 Series Connection Manual (Mitsubishi Electric Products) For GT Works3 Version1 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 interface] section in each chapter

Precautions

When using the multiple CPU system When using the GOT to monitor the multiple CPU system of other stations, select [MELSEC-Q/QS, Q17nD/M/NC/DR/DSR, CRnD-700] for the type, regardless of the host PLC CPU type (QCPU, QnACPU, or ACPU). When other models are selected, the setting of the CPU No. becomes unavailable.

Precautions for changing model 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.

When the changed Manufacturer or Controller Type does not correspond to the network. The network will be set to the host station.

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].

Extend I/F Setting Set the communication unit attached to the extension interface of the GOT. Not applicable to GT21 and GS21.

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 the controllers of channel numbers 1 to 4 set in controller setting (channel setting). 5 to 8: Used for the barcode function, the RFID function, and the remote personal computer operation function (Serial). A: Used for the video/RGB display function, multimedia function, external I/O function, operation panel function, video output function, report function, hard copy function (with a printer), and sound output function.

Driver Set the driver for the device to be connected. Each communication driver suitable to the channel numbers Each communication driver for connected devices

Detail Setting Set the detailed settings for the communication driver. Refer to each chapter of the equipment to be connected to the GOT.

Item Description

1 PREPARATORY PROCEDURES FOR MONITORING 1.1 Setting the Communication Interface 41

42

1.2 Writing the Package Data onto the GOT Write the package data onto the GOT. For details on writing to GOT, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

Writing the Package Data onto the GOT

1. Select [Package Data] for [Write Data]. The capacity of the transfer data is displayed in [Data Size]. Check that the destination drive has the sufficient available space.

2. Select [Destination Drive].

3. When the system application or the special data is required to be added to the package data or deleted, click the [Write Option] button and configure the setting in the [Write Option] dialog.

4. Click the [GOT Write] button.

5. The package data is written to the GOT.

1.

2.

3.

4.

1 PREPARATORY PROCEDURES FOR MONITORING 1.2 Writing the Package Data onto the GOT

1

Checking the package data writing on GOT Confirm if the package data is properly written onto the GOT by reading from GOT using GT Designer3. For reading from the GOT, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

1. Set [GOT Side] as follows. Select [Project Data] or [Package Data] for [Read Data]. Select the drive where the project data or the package data is stored for [Source Drive].

2. Set [PC Side]. Set the reading destination of the project for [Destination]. To read the project data to GT Designer3, select [GT Designer3]. (When [Read Data] is [Package Data], the project data cannot be read to GT Designer3.) To read the project data as a file, click the [...] button to set the saving format and the saving destination of the file.

3. Click the [GOT Read] button.

4. The project is read.

5. Confirm that the project data is written correctly onto the GOT.

1.

2.

3.

1 PREPARATORY PROCEDURES FOR MONITORING 1.2 Writing the Package Data onto the GOT 43

44

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 Product name Model Specifications Bus connection unit GT15-QBUS For QCPU (Q mode), Motion CPU (Q series)

Bus connection (1ch) unit standard model

GT15-QBUS2 For QCPU (Q mode), Motion CPU (Q series) Bus connection (2ch) unit standard model

GT15-ABUS For A/QnACPU, Motion CPU (A series) Bus connection (1ch) unit standard model

GT15-ABUS2 For A/QnACPU, Motion CPU (A series) Bus connection (2ch) unit standard model

GT15-75QBUSL For QCPU (Q mode), Motion CPU (Q series) Bus connection (1ch) unit slim model

GT15-75QBUS2L For QCPU (Q mode), Motion CPU (Q series) Bus connection (2ch) unit slim model

GT15-75ABUSL For A/QnACPU, Motion CPU (A series) Bus connection (1ch) unit slim model

GT15-75ABUS2L For A/QnACPU, Motion CPU (A series) Bus connection (1ch) unit slim model

Serial communication unit 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)

MELSECNET/H communication unit GT15-J71LP23-25 Optical loop unit

GT15-J71BR13 Coaxial bus unit

MELSECNET/10 communication unit GT15-J71LP23-25 Optical loop unit (MELSECNET/H communication unit used in the MNET/10 mode)

GT15-J71BR13 Coaxial bus unit (MELSECNET/H communication unit used in the MNET/10 mode)

CC-Link IE TSN communication unit GT25-J71GN13-T2 Local station (device station)

CC-Link IE Controller Network communication unit

GT15-J71GP23-SX Optical loop unit

CC-Link IE Field Network communication unit GT15-J71GF13-T2 CC-Link IE Field Network (1000BASE-T) unit

CC-Link communication unit GT15-J61BT13 Intelligent device station unit CC-Link Ver. 2 compatible

Ethernet communication unit GT25-J71E71-100 Ethernet(100Base-TX) unit

Wireless LAN communication unit*1*2 GT25-WLAN Used for the connection to the IEEE802.11b/g/n compliant, built-in antenna, access point (master unit), station (slave unit), personal computers, tablets, and smartphones.

Compliance with Japan Radio Law*3, FCC*4, RE*6 (R&TTE*4), SRRC*5, KC*5, Radio Equipment Regulations (UKCA)*7

1 PREPARATORY PROCEDURES FOR MONITORING 1.3 Option Devices for the Respective Connection

1

*1 Data transfer in wireless LAN communication may not be as stable as that in cable communication. A packet loss may occur depending on the surrounding environment and the installation location. Be sure to perform a confirmation of operation before using this product.

*2 When [Operation Mode] is set to [Access Point] in [Wireless LAN Setting] of GT Designer3, up to five stations are connectable to the wireless LAN access point (base station).

*3 The product with hardware version A or later (manufactured in December 2013) complies with the regulation. The product with hardware version A can be used only in Japan. For information on how to check the hardware version, refer to the following. GOT2000 Series User's Manual (Hardware)

*4 The product with hardware version B or later (manufactured from October 2014) complies with the regulation. The product with hardware version B or later can be used in Japan, the United States, the EU member states, Switzerland, Norway, Iceland, and Liechtenstein. For information on how to check the hardware version, refer to the following. GOT2000 Series User's Manual (Hardware)

*5 The product with hardware version D or later (manufactured from May 2016) complies with the regulation. The product with hardware version D or later can be used in Japan, the United States, the EU member states, Switzerland, Norway, Iceland, Liechtenstein, China (excluding Hong Kong, Macao, and Taiwan), and South Korea. For information on how to check the hardware version, refer to the following. GOT2000 Series User's Manual (Hardware)

*6 The product complies with the RE Directive from March 31, 2017. *7 The product with hardware version G or later (manufactured from October 2021) complies with the regulation.

The product with hardware version G or later can be used in Japan, the United States, the EU member states, the UK, Switzerland, Norway, Iceland, Liechtenstein, China (excluding Hong Kong, Macao, and Taiwan), and South Korea.

1 PREPARATORY PROCEDURES FOR MONITORING 1.3 Option Devices for the Respective Connection 45

46

Option unit

Conversion cables

Serial Multi-Drop Connection Unit

Field network adapter unit

RS-232/485 signal conversion adapter

Product name Model Specifications Multimedia unit GT27-MMR-Z For video input signal (NTSC/PAL) 1 ch, playing movie

Video input unit GT27-V4-Z For video input signal (NTSC/PAL) 4 ch

RGB input unit GT27-R2 GT27-R2-Z

For analog RGB input signal 2 ch

Video/RGB input unit GT27-V4R1-Z For video input signal (NTSC/PAL) 4 ch, for analog RGB mixed input signal 1 ch

RGB output unit GT27-ROUT GT27-ROUT-Z

For analog RGB output signal 1 ch

Digital video output unit GT27-VHOUT For digital video output, 1 channel

Sound output unit GT15-SOUT For sound output

External I/O unit 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-485 terminal block conversion modules

FA-LTBGT2R4CBL05 RS-422/485 (Connector) RS-485 (Terminal block) Supplied connection cable dedicated for the conversion unitFA-LTBGT2R4CBL10

FA-LTBGT2R4CBL20

Product name Model Specifications Serial multi-drop connection unit GT01-RS4-M GOT multi-drop connection module

GOT2000 Series Connection Manual (Mitsubishi Electric Products) For GT Works3 Version1

Product name Model Specifications Field network adapter unit GT25-FNADP The field network adapter unit can be used with the following field networks by using the Anybus

CompactCom M40 network communication module manufactured by HMS (hereinafter referred to as the communication module). Field networks: PROFIBUS DP-V1 DeviceNet

How to incorporate the communication module to the field network adapter unit, and the details of the product name of the communication module, refer to the following manual. GOT2000 Series Field Network Adapter Unit User's Manual

Product name Model Specifications RS-232/485 signal conversion adapter

GT14-RS2T4-9P RS-232 signal (D-Sub 9-pin connector) RS-485 signal (Terminal block)

1 PREPARATORY PROCEDURES FOR MONITORING 1.3 Option Devices for the Respective Connection

1

Precautions when installing units on top of one another When units are mounted on another unit, the mounting position is restricted depending on the combination of the units.

Mounting method of a communication unit and option unit For the mounting method of a communication unit and option unit, refer to the following. GOT2000 Series User's Manual (Hardware) When the multi-channel function is used When the multi-channel function is used, the combination of connection types is restricted. For the combination of connection types, refer to the following. GOT2000 Series Connection Manual (Mitsubishi Electric Products) For GT Works3 Version1

*1 Only one of the units can be mounted on the GOT. *2 Mounting the unit requires two stages. *3 A slim model bus connection unit (GT15-75QBUSL, GT15-75QBUS2L, GT15-75ABUSL, or GT15-75ABUS2L) cannot be mounted on

another unit. *4 The unit cannot be mounted on a unit in group B.

Product name Model Number of occupied slots

Mounting position

Group A *1 Video input unit GT27-V4-Z *2 2 1st stage

RGB input unit GT27-R2

GT27-R2-Z *2

Video/RGB input unit GT27-V4R1-Z *2

RGB output unit GT27-ROUT

GT27-ROUT-Z *2

Multimedia unit GT27-MMR-Z *2

Digital video output unit GT27-VHOUT

Group B *1 Bus connection unit (2 channels) *3 GT15-QBUS2 2 When a unit in group A is mounted: Upper stage of the group A unit

When no unit in group A is mounted: 1st stage When any units in group C are mounted: Lower

stage of the group C units

GT15-ABUS2

MELSECNET/H communication unit GT15-J71LP23-25

GT15-J71BR13

CC-Link IE TSN communication unit GT25-J71GN13-T2

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

Group C Bus connection unit (1 channel) *3*4 GT15-QBUS 1 When a unit in group A is mounted: Upper stage of the group A unit

When a unit in group B is mounted: Upper stage of the group B unit

GT15-ABUS

Ethernet communication unit GT25-J71E71-100

Serial communication unit GT15-RS2-9P

GT15-RS4-9S

GT15-RS4-TE

Sound output unit GT15-SOUT

External I/O unit GT15-DIOR

GT15-DIO

Printer unit GT15-PRN

Field network adapter unit GT25-FNADP 1 Uppermost stage

1 PREPARATORY PROCEDURES FOR MONITORING 1.3 Option Devices for the Respective Connection 47

48

Example) When mounting a video/RGB input unit, MELSECNET/H communication unit, and serial communication unit

Video/RGB input unit

Serial communication unit

Serial communication unit MELSECNET/H communication unit

MELSECNET/H communication unit

Video/RGB input unit

1 PREPARATORY PROCEDURES FOR MONITORING 1.3 Option Devices for the Respective Connection

1

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. For the dimensions of the connection cable and the connector shape, refer to the following. GOT2000 Series User's Manual (Hardware)

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 The following connector or equivalent connector is used for the RS-232 interface of the GOT and the RS-232 communication unit. For the GOT side of the connection cable, use a connector and connector cover applicable to the GOT connector.

Connector specifications

*1 The terminal block (MC1.5/9-ST-3.5 or corresponding product) of the cable side is packed together with the GT2104-RTBD, GT2103- PMBDS2.

*2 The applicable solderless terminal of the terminal block is AI 0.25-6BU (AWG24) (PHOENIX CONTACT Inc.). When fabricating a connection cable, use CRIMPFOX 6 (PHOENIX CONTACT Inc.) for crimping tool.

Connector pin arrangement

GOT Connector type Connector model Manufacturer GT27, GT25, GT23, GT2107-W, GT2105-QTBDS, GT2105- QMBDS, GS21

9-pin D-sub (male) #4-40UNC inch screw thread

17LE-23090-27(D3CH)-FA DDK Ltd.

GT15-RS2-9P 9-pin D-sub (male) #4-40UNC inch screw thread

17LE-23090-27(D3CH)-FA DDK Ltd.

GT01-RS4-M JES-9P-2A3A J.S.T.MFG.CO.,LTD. (JST)

GT2104-RTBD GT2104-PMBDS2 GT2103-PMBDS2

9-pin terminal block *1*2 MC1.5/9-G-3.5BK PHOENIX CONTACT Inc

GT27, GT25, GT23, GT2107-W, GT2105-QTBDS, GT2105- QMBDS, GS21, GT15-RS2-9P, GT01-RS4-M

GT2104-RTBD, GT2104-PMBDS2, GT2103-PMBDS2

9-pin D-sub (male)

GOT main part connector see from the front

1 5

6 9

See from the back of a GOT main part

9-pin terminal block

S D

R D

E R

D R

S G

C S

R S

N C

N C

1 PREPARATORY PROCEDURES FOR MONITORING 1.4 Connection Cables for the Respective Connection 49

50

RS-422/485 interface The following connector or equivalent connector is used for the RS-422/485 interface of the GOT and the RS-422/485 communication unit. For the GOT side of the connection cable, use a connector and connector cover applicable to the GOT connector.

Connector model

*1 The terminal block (MC1.5/5-ST-3.5 or corresponding product) of the cable side is packed together with the GT2103-PMBD. *2 The terminal block (MC1.5/9-ST-3.5 or corresponding product) of the cable side is packed together with the GT2104-RTBD, GT2103-

PMBDS, GT2103-PMBLS. *3 The applicable solderless terminal of the terminal block is AI 0.25-6BU (AWG24) (PHOENIX CONTACT Inc.).

When fabricating a connection cable, use CRIMPFOX 6 (PHOENIX CONTACT Inc.) for crimping tool.

Connector pin arrangement

GOT Connector type Connector model Manufacturer GT27, GT25, GT23, GT2107-W, GT2105-QTBDS, GT2105-QMBDS, GS21

9-pin D-Sub (female) M2.6 metric screw thread

17LE-13090-27(D3AH)-FA DDK Ltd.

GT2104-PMBD GT2103-PMBD

5-pin terminal block *1*3 MC1.5/5-G-3.5BK PHOENIX CONTACT Inc

GT2104-RTBD GT2104-PMBDS GT2104-PMBLS GT2103-PMBDS GT2103-PMBLS

9-pin terminal block *2*3 MC1.5/9-G-3.5BK PHOENIX CONTACT Inc

GT15-RS4-9S 9-pin D-Sub (female) M2.6 metric screw thread

17LE-13090-27(D3AH)-FA DDK Ltd.

GT01-RS4-M JES-9S-2A3B14 J.S.T.MFG.CO.,LTD. (JST)

GT15-RS4-TE - SL-SMT3.5/10/90F BOX Weidmller Interface GmbH & Co. KG

GT27, GT25, GT23, GT2107-W, GT2105- QTBDS, GT2105-QMBDS, GS21, GT15- RS4-9P, GT01-RS4-M

GT2104-PMBD, GT2103-PMBD GT2104-RTBD, GT2104-PMBDS, GT2104- PMBLS, GT2103-PMBDS, GT2103-PMBLS

9-pin D-sub (female)

GOT main part connector see from the front

5 1

9 6

S D

A S

D B

R D

A R

D B

S G

5-pin terminal block

See from the back of a GOT main part

9-pin terminal block

See from the back of a GOT main part

S D

A S

D B

R D

A R

D B

S G

R S

B R

S A

C S

A C

S B

1 PREPARATORY PROCEDURES FOR MONITORING 1.4 Connection Cables for the Respective Connection

1

Coaxial cableconnector connection method The following describes the method for connecting the BNC connector (connector plug for coaxial cable) and the cable.

1. Remove the external sheath of the coaxial cable with dimensions as shown below.

2. Pass the nut, washer, gasket, and clamp through the coaxial cable as shown on the left and loosen the external conductor.

3. 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.

4. Solder the contact to the internal conductor.

Cable in use A 3C-2V 15mm

5C-2V, 5C-2V-CCY 10mm

Cable in use B C 3C-2V 6 mm 3 mm

5C-2V, 5C-2V-CCY 7 mm 5 mm

CAUTION

Solder the coaxial cable connectors properly. Insufficient soldering may result in malfunctions.

Nut Washer Gasket

Clamp Contact

Components of the BNC connector

Plug shell

Outer sheath External conductor

Insulating material

Internal conductor

Structure of the coaxial cable

A

Cut this portion of the outer sheath

Clamp

Gasket Washer

Nut

Internal conductor Insulating material

C B Clamp and external

conductor

Solder here

1 PREPARATORY PROCEDURES FOR MONITORING 1.4 Connection Cables for the Respective Connection 51

52

5. Insert the contact assembly shown in step 4 into the plug shell and screw the nut into the plug shell.

Precautions for soldering 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

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 Set the terminating resistor using the terminating resistor setting switch.

*1 The default setting is "Disable". For RS422/485 communication unit

Terminating resistor*1 Switch No.

1 2 100 OHM ON ON

Disable OFF OFF

SW 1

O N 1 2

O N SW1

ON 1

2

Rear view of RS-422/485 communication unit. Terminating resistor setting switch

1 PREPARATORY PROCEDURES FOR MONITORING 1.4 Connection Cables for the Respective Connection 53

54

GT27 Set the terminating resistor using the terminating resistor setting switch.

*1 The default setting is "Disable". For GT2710-V

Terminating resistor*1 Switch No.

1 2 100 OHM ON ON

Disable OFF OFF

ON

1 2

Terminating resistor setting switch (inside the cover)

1 PREPARATORY PROCEDURES FOR MONITORING 1.4 Connection Cables for the Respective Connection

1

GT25 (except GT25-W and GT2505-V) Set the terminating resistor using the terminating resistor setting switch.

*1 The default setting is "Disable". For GT2510-V

GT25-W Set the terminating resistor using the terminating resistor selector. For GT2510-WX

Terminating resistor*1 Switch No.

1 2 100 OHM ON ON

Disable OFF OFF

ON

1 2

Terminating resistor setting switch (inside the cover)

Terminating resistor selector switch (inside the cover)

1 PREPARATORY PROCEDURES FOR MONITORING 1.4 Connection Cables for the Respective Connection 55

56

GT2505-V Set the terminating resistor using the terminating resistor selector.

GT23 Set the terminating resistor using the terminating resistor setting switch.

*1 The default setting is "Disable". For GT2310-V

Terminating resistor*1 Switch No.

1 2 100 OHM ON ON

Disable OFF OFF

Terminating resistor selector switch

ON

1 2

Terminating resistor setting switch (inside the cover)

1 PREPARATORY PROCEDURES FOR MONITORING 1.4 Connection Cables for the Respective Connection

1

GT21 Set the terminating resistor using the terminating resistor setting switch. For GT2103-PMBD

GS21-W-N Set the terminating resistor using the terminating resistor setting switch. For GS2110-WTBD-N

Terminating resistor selector switch position The position of the terminating resistor selector switch depends on the GOT type. For the details, refer to the following. GOT2000 Series User's Manual (Hardware) Terminating resistor of GS21-W The terminating resistor of GS21-W is fixed to 330 . For the details, refer to the following. GOT SIMPLE Series User's Manual

USB

Terminating resistor selector switch

Terminating resistor selector switch

1 PREPARATORY PROCEDURES FOR MONITORING 1.4 Connection Cables for the Respective Connection 57

58

Setting the RS-232/485 signal conversion adaptor Set the 2-wire/4-wire terminating resistor setting switch according to the connection type.

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. Page 39 I/F communication setting When validating the function using the utility function of the GOT main unit, refer to the following manual. GOT2000 Series User's Manual (Utility)

Setting the 2-wire/4-wire terminating resistor setting switch

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

Setting item Set value Switch No.

1 2 3 4 5 6 2-wire/4-wire 2-wire (1Pair) ON ON - - - OFF

4-wire (2Pair) OFF OFF - - - OFF

Terminating resistor 110 - - ON OFF OFF OFF

OPEN - - OFF OFF OFF OFF

330 - - OFF ON ON OFF

2-wire/4-wire terminating resistor setting switch

1 O

2 N

3 4 5 6

1 PREPARATORY PROCEDURES FOR MONITORING 1.4 Connection Cables for the Respective Connection

1

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. GOT2000 Series User's Manual (Utility)

1. After powering up the GOT, touch [GOT basic set] [Controller] from the Utility.

2. The [Communication Settings] appears.

3. Verify that the communication driver name to be used is displayed in the communication interface box to be used.

4. When the communication driver name is not displayed normally, carry out the following procedure again. Page 31 Setting the Communication Interface

1.

2. 3.

1 PREPARATORY PROCEDURES FOR MONITORING 1.5 Verifying GOT Recognizes Connected Equipment 59

60

Utility How to display Utility (at default)

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. GOT2000 Series User's Manual (Utility) Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective.

Utility call key 1-point press on GOT screen upper-left corner Utility display

1 PREPARATORY PROCEDURES FOR MONITORING 1.5 Verifying GOT Recognizes Connected Equipment

1

1.6 Checking for Normal Monitoring 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. GOT2000 Series User's Manual (Utility)

Alarm popup display With the 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 alarm popup display, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

Error code Communication Channel No.

Error message Time of occurrence (Displayed only for errors)

1 PREPARATORY PROCEDURES FOR MONITORING 1.6 Checking for Normal Monitoring 61

62

Communication monitoring function 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: GOT2000 Series User's Manual (Utility) (Operation of communication monitoring function screen)

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. Page 155 System Configuration Examples

Comm. SettingMain Menu

Comm. Monitor

Touch [Comm. Setting].

Touch [Comm. Monitor].

Microcomputer board

Write command S T X

RW 0163000A0100 0362 E T X

D3

1 PREPARATORY PROCEDURES FOR MONITORING 1.6 Checking for Normal Monitoring

1

Confirming the communication state on the GOT side (For Ethernet connection)

Confirming the communication state on Windows, GT Designer3 When using the Windows Command Prompt Execute a Ping command at the Command Prompt of Windows. At normal communication C:\>Ping 192.168.3.18 Reply from 192.168.3.18: bytes=32 time<1ms TTL=64 At abnormal communication C:\>Ping 192.168.3.18 Request timed out.

When using the [TEST] of GT Designer3 Select [Communication] [Communication settings] from the menu to display [TEST].

1. Set the [PC side I/F] to the [Ethernet].

2. Specify the [GOT IP Address] of the [Communication Configuration] and click the [Test] button.

3. Check if GT Designer3 has been connected to the GOT.

At abnormal communication At abnormal communication, check the followings and execute the Ping command or [TEST] again. Mounting condition of Ethernet communication unit Cable connecting condition Confirmation of [Communication Settings] IP address of GOT specified by Ping command

2.

1.

3.

1 PREPARATORY PROCEDURES FOR MONITORING 1.6 Checking for Normal Monitoring 63

64

Confirming the communication state on the GOT The Ping test can be confirmed by the Utility screen of the GOT. For the operation method of GOT Utility, refer to the following. GOT2000 Series User's Manual (Utility)

1 PREPARATORY PROCEDURES FOR MONITORING 1.6 Checking for Normal Monitoring

1

Confirming the communication state to 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 allocates the data for the faulty station to the GOT special register (GS).

No. of faulty stations Ethernet connection (Except for Ethernet multiple connection) Total No. of the faulty CPU is stored.

Ethernet multiple connection Total No. of the faulty connected equipment is stored.

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 (GOT2000) Screen Design Manual Numerical Display (Data Operation tab)

Device b15 to b8 b7 to b0 GS230 (00H fixed) No. of faulty stations

Channel Device b15 to b8 b7 to b0 Ch1 GS280 (00H fixed) No. of faulty stations

Ch2 GS300 (00H fixed) No. of faulty stations

Ch3 GS320 (00H fixed) No. of faulty stations

Ch4 GS340 (00H fixed) No. of faulty stations

Set [mask processing] to the upper eight bits (b8 to b15) of GS230 on Numerical Display.

1 PREPARATORY PROCEDURES FOR MONITORING 1.6 Checking for Normal Monitoring 65

66

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.

Ethernet connection

The following shows the Ethernet setting numbers for each device in the Ethernet multiple connection.

Device Ethernet setting No.

b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0 GS231 16 15 14 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

Device Ethernet setting 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

GS231 bit 0 GS231 bit 1 GS231 bit 2 GS231 bit 3

Ethernet setting No.

1 PREPARATORY PROCEDURES FOR MONITORING 1.6 Checking for Normal Monitoring

1

CC-Link IE TSN connection

Connection with the temperature controller (AZBIL temperature controller (DMC50))

Connection types other than the above The supported device differs depending on the communication driver to be used. Communication drivers supported by the host station only

The host station uses the 0th bit at the top. Ch1: GS281.b0 Ch2: GS301.b0 Ch3: GS321.b0 Ch4: GS341.b0

Device Station number

b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0 GS1281 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

GS1282 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16

GS1283 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32

GS1284 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48

GS1285 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64

GS1286 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80

GS1287 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96

GS1288 - - - - - - - 120 119 118 117 116 115 114 113 112

Device Station number-Sub Station

Ch1 Ch2 Ch3 Ch4 b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0 GS281 GS301 GS321 GS341 1-15 1-14 1-13 1-12 1-11 1-10 1-9 1-8 1-7 1-6 1-5 1-4 1-3 1-2 1-1 1-0

GS282 GS302 GS322 GS342 2-15 2-14 2-13 2-12 2-11 2-10 2-9 2-8 2-7 2-6 2-5 2-4 2-3 2-2 2-1 2-0

GS283 GS303 GS323 GS343 3-15 3-14 3-13 3-12 3-11 3-10 3-9 3-8 3-7 3-6 3-5 3-4 3-3 3-2 3-1 3-0

GS284 GS304 GS324 GS344 4-15 4-14 4-13 4-12 4-11 4-10 4-9 4-8 4-7 4-6 4-5 4-4 4-3 4-2 4-1 4-0

GS285 GS305 GS325 GS345 5-15 5-14 5-13 5-12 5-11 5-10 5-9 5-8 5-7 5-6 5-5 5-4 5-3 5-2 5-1 5-0

GS286 GS306 GS326 GS346 6-15 6-14 6-13 6-12 6-11 6-10 6-9 6-8 6-7 6-6 6-5 6-4 6-3 6-2 6-1 6-0

GS287 GS307 GS327 GS347 7-15 7-14 7-13 7-12 7-11 7-10 7-9 7-8 7-7 7-6 7-5 7-4 7-3 7-2 7-1 7-0

GS288 GS308 GS328 GS348 8-15 8-14 8-13 8-12 8-11 8-10 8-9 8-8 8-7 8-6 8-5 8-4 8-3 8-2 8-1 8-0

Communication driver list Bus Q Bus A/QnA Serial(MELSEC)

AJ71QC24, MELDAS C6* AJ71C24/UC24 CC-Link(G4)

MELSEC-FX MELSEC-WS OMRON SYSMAC

YASKAWA GL YASKAWA CP9200 (H) YASKAWA CP9300MS (MC compatible)

YASKAWA MP2000/MP900/CP9200SH AB Control/CompactLogix SHARP JW

TOSHIBA PROSEC T/V HITACHI IES HIDIC H HITACHI IES HIDIC H(Protocol2)

PANASONIC MEWNET-FP PANASONIC MEWTOCOL-7 SIEMENS S7-200

YOKOGAWA FA500/FA-M3/STARDOM Serial(KEYENCE) HITACHI S10mini/S10V

FUJI MICREX-SX SPH SHIBAURA MACHINE TCmini SICK Flexi Soft

IAI X-SEL PROFIBUS DP DeviceNet

1 PREPARATORY PROCEDURES FOR MONITORING 1.6 Checking for Normal Monitoring 67

68

Communication drivers supported by the other stations

The following shows the supported devices.

*1 When CC-Link IE Controller network connection is not used. *2 When CC-Link IE Field network connection is not used.

For details on the GS Device, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

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.

Check on the PLC

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 (GOT2000) Screen Design Manual

Communication driver list CC-Link IE Controller Network CC-Link IE Field Network MEI Nexgenie

AB SLC500 AB 1:N connection AB MicroLogix AB MicroLogix(Extended)

SIEMENS S7-300/400 JTEKT TOYOPUC-PC FUJI MICREX-F

GE(SNP-X) KOYO KOSTAC/DL LS Industrial Systems MASTER-K

Hirata HNC IAI robocylinder Panasonic MINAS A4

Panasonic MINAS A5 Muratec MPC MELSERVO-J4,J3,J2S/M,JE

FREQROL 500/700/800,SENSORLESS SERVO FREQROL 800 FREQROL(Batch monitor)

OMRON THERMAC/INPANEL NEO OMRON Digital Temperature Controller AZBIL SDC/DMC

AZBIL DMC50 RKC SR Mini HG (MODBUS) FUJI Temperature Controller/Digital Controller

YOKOGAWA GREEN/UT100/UT2000/ UTAdvanced

SHINKO TECHNOS CONTROLLER CHINO MODBUS device

MODBUS/RTU Master

Device Station number

Ch1 Ch2 Ch3 Ch4 b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0 GS281 GS301 GS321 GS341 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0*1

GS282 GS302 GS322 GS342 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16

GS283 GS303 GS323 GS343 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32

GS284 GS304 GS324 GS344 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48

GS285 GS305 GS325 GS345 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64

GS286 GS306 GS326 GS346 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80

GS287 GS307 GS327 GS347 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96

GS288 GS308 GS328 GS348 127 *1*2

126 *1*2

125 *1*2

124 *1*2

123 *1*2

122 *1*2

121 *1*2

120 119 118 117 116 115 114 113 112

Device 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

PART 2 MICROCOMPUTER

2 MICROCOMPUTER CONNECTION (SERIAL)

3 MICROCOMPUTER CONNECTION (ETHERNET)

69

70

2 MICROCOMPUTER CONNECTION (SERIAL) Page 70 Microcomputer Connection (Serial) Page 73 System Configuration Page 79 Connection Diagram Page 85 Device Data Area Page 99 Message Formats Page 151 GOT Side Settings Page 155 System Configuration Examples Page 160 Device Range that Can Be Set Page 160 Precautions

2.1 Microcomputer Connection (Serial) The microcomputer connection (Serial) is a function by which data can be written or read from a personal computer, microcomputer board, PLC, and others (hereinafter, host) to the virtual devices of the GOT by connecting the host and the GOT by Serial. Interrupt output is also available from the GOT to the host.

Virtual devices inside the GOT The devices inside the GOT are used in the microcomputer connection. (PLC devices are not used) Page 85 Device Data Area

D0

D100

D4095

D163

000A

0362D 0

to 4

09 5

Virtual devices inside GOT

Interrupt output

Microcomputer board

Write,Read Command S T X

RW 0100 000A 0163 0362 E T X

D3

2 MICROCOMPUTER CONNECTION (SERIAL) 2.1 Microcomputer Connection (Serial)

2

Flow of data processing When reading or writing data

1. The host sends a request message (the read or write command) to the GOT.

2. The GOT reads or writes data from or to its virtual devices according to the request from the host.

3. 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 or written from or to the virtual devices. Numerical display object to display the data written by the write command Numerical input object to input data to be uploaded to the host

Host

Display(D4 to 9)

Input(D20)

GOT

2.

3. 1.

Screen data

04/06/01 18:46:49

1254

Screen display Device data area (Virtual devices)*2

Response message*1

Request message*1

2 MICROCOMPUTER CONNECTION (SERIAL) 2.1 Microcomputer Connection (Serial) 71

72

When outputting interrupts

1. Data are written to the virtual devices for interrupt output from the touch switches on the GOT.

2. The GOT sends the written data (interrupt output) to the host. *1 Page 99 Message Formats *2 Page 85 Device Data Area

2.

1.

Host

GOT

Screen data

Interrupt output*1

Screen display Device data area (virtual devices)*2

Interrupt(D13) D13 3139H

31H

output value1 output value2

39H

(When the number of interrupt data bytes is 2)

2 MICROCOMPUTER CONNECTION (SERIAL) 2.1 Microcomputer Connection (Serial)

2

2.2 System Configuration For the microcomputer connection (serial)

When connecting one GOT

*1 When a GT10-C02H-6PT9P unit of the sub version A or B is used, do not ground the case of the D-sub (9-pin) connector. *2 GT25-W, GT2505-V does not support the option device.

Host Connection cable GOT Number of connectable equipmentCommunication

Type Max. distance Connection diagram

number Option device*2 Model

RS-232 Differs according to host side specifications

Page 79 RS-232 connection diagram 1)

- (Built into GOT) 1 GOT for 1 host

GT15-RS2-9P

GT10-C02H-6PT9P*1

Page 80 RS-232 connection diagram 2)

- (Built into GOT)

RS-422 Differs according to host side specifications

Page 83 RS-422 connection diagram 1)

- (Built into GOT)

GT15-RS4-9S

GT10-C02H-9SC

Page 83 RS-422 connection diagram 2)

- (Built into GOT)

Computer

Communication driver

Host GOT

Connection cable

2 MICROCOMPUTER CONNECTION (SERIAL) 2.2 System Configuration 73

74

When connecting multiple GOTs

Computer

Communication driver

Host GOT (n-th)

GOT (n+1th)

Varies according to the connection type.

Connection cable

2 MICROCOMPUTER CONNECTION (SERIAL) 2.2 System Configuration

2

Host GOT (n-th) *1 Connection cable GOT (n+1th) *1 Number of connectable equipment

Connection type

Communic ation Type

Option device

Model Option device

Communica tion Type

Cable model

Max. distance

Option device

Model

For the system configuration between the GOT and host, refer to the following. Page 73 When connecting one GOT

RS-232 - (Built into GOT)

- RS-422 Page 84 RS-422 connection diagram 5)

30m - (Built into GOT)

4 GOT for 1 host

30m GT10- C02H- 9SC

- (Built into GOT)

GT10- C02H-9SC

RS-422 Page 84 RS-422 connection diagram 5)

30m - (Built into GOT)

GT10- C02H- 9SC

- Page 83 RS-422 connection diagram 3)

30m - (Built into GOT)

- Page 84 RS-422 connection diagram 4)

30m - (Built into GOT)

*3

- (Built into GOT)

- RS-232 GT10-C30R2- 6P(3m)*2

3m - (Built into GOT)

GT10- C02H- 6PT9P*5

Page 81 RS-232 connection diagram 4)

15m - (Built into GOT)

GT01-C30R2- 9S(3m) or

Page 82 RS-232 connection diagram 8)

15m - (Built into GOT)

GT10- C02H- 6PT9P*5

2 MICROCOMPUTER CONNECTION (SERIAL) 2.2 System Configuration 75

76

For the system configuration between the GOT and host, refer to the following. Page 73 When connecting one GOT

RS-232 GT10- C02H- 6PT9P*5

GT10- C02H-9SC

RS-422 Page 84 RS-422 connection diagram 5)

30m - (Built into GOT)

4 GOT for 1 host

GT10- C02H- 9SC

- Page 83 RS-422 connection diagram 3)

30m - (Built into GOT)

Page 84 RS-422 connection diagram 4)

30m - (Built into GOT)

*3

GT10- C02H- 6PT9P*5

- RS-232 Page 81 RS-232 connection diagram 5)

15m - (Built into GOT)

RS-232 GT10-C30R2- 6P(3m)*4

3m - (Built into GOT)

RS-232 Page 82 RS-232 connection diagram 7)

30m - (Built into GOT)

GT10- C02H- 6PT9P*5

Host GOT (n-th) *1 Connection cable GOT (n+1th) *1 Number of connectable equipment

Connection type

Communic ation Type

Option device

Model Option device

Communica tion Type

Cable model

Max. distance

Option device

Model

2 MICROCOMPUTER CONNECTION (SERIAL) 2.2 System Configuration

2

For the system configuration between the GOT and host, refer to the following. Page 73 When connecting one GOT

RS-422 - (Built into GOT)

- RS-232 GT01-C30R2- 9S(3m) or

Page 82 RS-232 connection diagram 8)

15m - (Built into GOT)

4 GOT for 1 host

15m GT10- C02H- 6PT9P*5

- (Built into GOT)

- RS-232 Page 81 RS-232 connection diagram 5)

15m - (Built into GOT)

GT10-C30R2- 6P(3m)*4

3m - (Built into GOT)

Page 82 RS-232 connection diagram 7)

30m - (Built into GOT)

GT10- C02H- 6PT9P*5

GT10- C02H- 9SC

- RS-232 Page 81 RS-232 connection diagram 5)

15m - (Built into GOT)

GT10-C30R2- 6P(3m)*4

3m - (Built into GOT)

Page 82 RS-232 connection diagram 7)

30m - (Built into GOT)

GT10- C02H- 6PT9P*5

Host GOT (n-th) *1 Connection cable GOT (n+1th) *1 Number of connectable equipment

Connection type

Communic ation Type

Option device

Model Option device

Communica tion Type

Cable model

Max. distance

Option device

Model

2 MICROCOMPUTER CONNECTION (SERIAL) 2.2 System Configuration 77

78

*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.

Page 80 RS-232 connection diagram 3) *3 When connecting multiple GOTs, set the GT2104-PMBD, GT2103-PMBD in the terminal position and connect them.

The GT2104-PMBD, GT2103-PMBD cannot be connected in any other position. *4 For the connection to GOT, refer to the connection diagram.

Page 81 RS-232 connection diagram 6) *5 When a GT10-C02H-6PT9P unit of the sub version A or B is used, do not ground the case of the D-sub (9-pin) connector.

For the system configuration between the GOT and host, refer to the following. Page 73 When connecting one GOT

RS-422 - (Built into GOT)

- RS-232 GT10-C30R2- 6P(3m)*2

3m - (Built into GOT)

4 GOT for 1 host

GT10- C02H- 6PT9P*5

Page 81 RS-232 connection diagram 4)

15m - (Built into GOT)

GT01-C30R2- 9S(3m) or

Page 82 RS-232 connection diagram 8)

15m - (Built into GOT)

GT10- C02H- 6PT9P*5

GT10- C02H- 9SC

GT10- C02H- 6PT9P*5

RS-232 GT01-C30R2- 9S(3m) or

Page 82 RS-232 connection diagram 8)

15m - (Built into GOT)

GT10- C02H- 6PT9P*5

Page 81 RS-232 connection diagram 4)

15m - (Built into GOT)

- GT10-C30R2- 6P(3m)*2

3m - (Built into GOT)

Host GOT (n-th) *1 Connection cable GOT (n+1th) *1 Number of connectable equipment

Connection type

Communic ation Type

Option device

Model Option device

Communica tion Type

Cable model

Max. distance

Option device

Model

2 MICROCOMPUTER CONNECTION (SERIAL) 2.2 System Configuration

2

2.3 Connection Diagram The following diagram shows the connection between the GOT and the microcomputer.

RS-232 cable

Connection diagram RS-232 connection diagram 1) Example of the case where the DTR/DSR signal is not used

Example of the case where the DTR/DSR signal is used

GOT side Host side

CD

RD(RXD)

SD(TXD)

ER(DTR)

SG

DR(DSR)

RS(RTS)

CS(CTS)

-

1

2

3

4

5

6

7

8

9

FG

SD(TXD)

RD(RXD)

RS(RTS)

SG

CS(CTS)

-

-

ER(DTR)

GOT side Host side

FG

SD(TXD)

RD(RXD)

DR(DSR)

SG

ER(DTR)

RS(RTS)

CS(CTS)

5V

CD

RD(RXD)

SD(TXD)

ER(DTR)

SG

DR(DSR)

RS(RTS)

CS(CTS)

-

1

2

3

4

5

6

7

8

9

2 MICROCOMPUTER CONNECTION (SERIAL) 2.3 Connection Diagram 79

80

RS-232 connection diagram 2) Example of the case where the DTR/DSR signal is not used

Example of the case where the DTR/DSR signal is used

RS-232 connection diagram 3)

GOT side (terminal block) Host side

SD

RD

ER

DR

SG

RS

CS

NC

NC

RD(RXD)

SD(TXD)

RS(RTS)

CS(CTS)

SG

-

-

-

FG

GOT side (terminal block) Host side

SD

RD

ER

DR

SG

RS

CS

NC

NC

RD(RXD)

SD(TXD)

DR(DSR)

ER(DTR)

SG

RS(RTS)

CS(CTS)

-

FG

GOT side (n+1th) (terminal block)

BROWN

RED

BLUE

YELLOW

GREEN

PURPLE

Unfastened cable color of GT10-C30R2-6P

SD

RD

ER

DR

SG

RS

CS

NC

NC

2 MICROCOMPUTER CONNECTION (SERIAL) 2.3 Connection Diagram

2

RS-232 connection diagram 4)

RS-232 connection diagram 5)

RS-232 connection diagram 6)

GOT side (n+1th) (terminal block)

Cable (GT10-C02H-6PT9P) D-Sub 9 pin side

N.C.

RD(RXD)

SD(TXD)

ER(DTR)

SG

DR(DSR)

RS(RTS)

CS(CTS)

-

1

2

3

4

5

6

7

8

9

RS

SD

RD

DR

SG

ER

CS

N.C.

N.C.

GOT side (n-th) (terminal block)

GOT side (n+1th) (terminal block)

N.C.

RD

SD

ER

SG

DR

RS

CS

N.C.

N.C.

SD

RD

DR

SG

ER

CS

RS

N.C.

Unfastened cable color of GT10-C30R2-6P

GOT side (n-th) (terminal block)

SD

RD

ER

DR

SG

RS

CS

NC

NC

BROWN

RED

BLUE

YELLOW

GREEN

PURPLE

2 MICROCOMPUTER CONNECTION (SERIAL) 2.3 Connection Diagram 81

82

RS-232 connection diagram 7)

RS-232 connection diagram 8)

Precautions when preparing a cable Cable length The length of the RS-232 cable must be 15m or less.

GOT side connector For the GOT side connector, refer to the following. Page 49 GOT connector specifications

GOT side (n-th) (terminal block) GOT side (n+1th)

1

2

3

4

5

6

7

8

9

NC

RD(RXD)

SD(TXD)

ER(DTR)

SG

DR(DSR)

RS(RTS)

CS(CTS)

-

RS

SD

RD

DR

SG

ER

CS

NC

NC

GOT side (n-th) GOT side (n+1th)

N.C.

RD(RXD)

SD(TXD)

ER(DTR)

SG

DR(DSR)

RS(RTS)

CS(CTS)

-

1

2

3

4

5

6

7

8

9

1

3

2

6

5

4

8

7

9

N.C.

SD(TXD)

RD(RXD)

DR(DSR)

SG

ER(DTR)

CS(CTS)

RS(RTS)

-

2 MICROCOMPUTER CONNECTION (SERIAL) 2.3 Connection Diagram

2

RS-422 cable

Connection diagram RS-422 connection diagram 1)

RS-422 connection diagram 2)

*1 The signals RSA, RSB, CSA, and CSB are not provided for GT2104-PMBD, GT2103-PMBD. Return connection is not required.

RS-422 connection diagram 3)

GOT side Host side

SDA

SDB

RDA

RDB

-

-

-

-

SHELL

RDA

RDB

SDA

SDB

RSA

RSB

CSA

CSB

SG

2

7

1

6

3

8

4

9

5

GOT side Host side

SDA

SDB

RDA

RDB

-

-

-

-

SHELL

RDA

RDB

SDA

SDB

RSA*1

RSB*1

CSA*1

CSB*1

SG

GOT side (n-th) (terminal block)

SDA

RDA

RSA

CSA

SG

SDB

RDB

RSB

CSB

GOT side (n+1th) (terminal block)

RDA

SDA

CSA

RSA

SG

RDB

SDB

CSB

RSB

2 MICROCOMPUTER CONNECTION (SERIAL) 2.3 Connection Diagram 83

84

RS-422 connection diagram 4)

RS-422 connection diagram 5)

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.

Precautions when preparing a cable 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 RS-422 connection diagram 5) must be 30m or less.

GOT side connector For the GOT side connector, refer to the following. Page 49 GOT connector specifications

Connecting terminating resistors GOT side When connecting a microcomputer to the GOT, a terminating resistor must be connected to the GOT. For GT27, GT25(Except GT2505-V), GT23 Set the terminating resistor setting switch of the GOT main unit to disable. For GT2505-V, GT21, and GS21-W Set the terminating resistor selector to 330 . For GS21-W Since the terminating resistor is fixed to 330 , no setting is required for the terminating resistor. For the procedure to set the terminating resistor, refer to the following. Page 53 Terminating resistors of GOT

GOT side (n-th) (terminal block)

GOT side (n+1th) (terminal block)

SDA

SDB

RDA

RDB

SG

RDA

RDB

SDA

SDB

SG

CSA

CSB

RSA

RSB

TXD+(SDA)

RXD+(RDA)

RTS+(RSA)

CTS+(CSA)

SG

TXD-(SDB)

RXD-(RDB)

RTS-(RSB)

CTS-(CSB)

2

1

4

3

5

7

6

9

8

1

2

3

4

5

6

7

8

9

RXD+(RDA)

TXD+(SDA)

CTS+(CSA)

RTS+(RSA)

SG

RXD-(RDB)

TXD-(SDB)

CTS-(CSB)

RTS-(RSB)

GOT side (n-th) GOT side (n+1th)

2 MICROCOMPUTER CONNECTION (SERIAL) 2.3 Connection Diagram

2

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

*1 For the address specification method for each data format, refer to the following. Page 99 Message Formats

*2 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 (GOT2000) Screen Design Manual

*3 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.

Model Virtual device*2 Address specification value Refer to

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 Page 86 D devices

R 0 to 4095 Word 4096 to 8191 R0 to 4095 R0 to 4095 1000 to 1FFFH 0000 to 1FFFH Page 90 R devices

L 0 to 2047 Bit 8192 to 8319 L0 to 2047 L0 to 2047 2000 to 207FH A000 to A0FFH Page 91 L devices

M 0 to 2047 Bit 8320 to 8447 M0 to 2047 M0 to 2047 2080 to 20FFH 2000 to 20FFH Page 92 M devices

SD 0 to 15 Word 8448 to 8463 D9000 to 9015 SD0 to 15 2100 to 210FH 2100 to 211FH (3000 to 300DH)*3

Page 93 SD devices

SM 0 to 63 Bit 8464 to 8467 M9000 to 9063 SM0 to 63 2110 to 2113H 2200 to 2207H Page 97 SM devices

D 0 to 4095 Word 0 to 4095 - - 0000 to 0FFFH 8000 to 9FFFH Page 86 D devices

R 0 to 4095 Word 4096 to 8191 - - 1000 to 1FFFH 0000 to 1FFFH Page 90 R devices

L 0 to 2047 Bit 8192 to 8319 - - 2000 to 207FH A000 to A0FFH Page 91 L devices

M 0 to 2047 Bit 8320 to 8447 - - 2080 to 20FFH 2000 to 20FFH Page 92 M devices

SD 0 to 15 Word 8448 to 8463 - - 2100 to 210FH 2100 to 211FH (3000 to 300DH)*3

Page 93 SD devices

SM 0 to 63 Bit 8464 to 8467 - - 2110 to 2113H 2200 to 2207H Page 97 SM devices

Formats 1, 2 : GOT-A900 Series microcomputer connection Formats 3 to 6 : A compatible 1C frame Formats 7 to 10 : QnA compatible 3C/4C frame Formats 11 to 13 : SCHNEIDER EJH's memory link method Formats 14, 15 : GOT-F900 Series microcomputer connection

GOT2000 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

2 MICROCOMPUTER CONNECTION (SERIAL) 2.4 Device Data Area 85

86

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.

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

D3 Communication error status Stores the communication error details of GOT.

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.

System

D4 Clock data (year)

D5 Clock data (month)

D6 Clock data (day)

b15 b0 b3

Unused

b4

SIO framing error

b5

SIO parity error SIO overrun error

b6b7

Communication timeout error Unused

b8

0: Normal 1: Error

b15 b0

Lower 2 digits of calendar year stored as 2-digit BCD

b7

Unused

b8

b15 b0

Data of months 01 to 12 stored as 2-digit BCD

b7

Unused

b8

b15 b0

Data of days 01 to 31 stored as 2-digit BCD

b7

Unused

b8

2 MICROCOMPUTER CONNECTION (SERIAL) 2.4 Device Data Area

2

D7 Clock data (hour) System

D8 Clock data (minute)

D9 Clock data (second)

D10 Clock data (day of the week)

D11, D12 Unused

Address Description Set side

b15 b0

Data of hours 00 to 23 stored as 2-digit BCD

b7

Unused

b8

b15 b0

Data of minutes 00 to 59 stored as 2-digit BCD

b7

Unused

b8

b15 b0

Data of seconds 00 to 59 stored as 2-digit BCD

b7

Unused

b8

b15 b0

Day-of-week data stored as 2-digit BCD

b7

Unused

b8

00: Sunday 01: Monday 02: Tuesday 03: Wednesday 04: Thursday 05: Friday 06: Saturday

2 MICROCOMPUTER CONNECTION (SERIAL) 2.4 Device Data Area 87

88

*1 After the interrupt data is written, the data is output within 1 to 10 ms. *2 When data are written to D13 and D14 from the host side, interrupt output is not performed. *3 When 32-bit data are written to D13 and D14, the values are output to the host side regardless of the setting for [32bit Storage] in the

communication detail settings. Example) When outputting 0x12345678 with unsigned 32-bit binary data

D13 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

Set the data amount (bytes) for an interrupt output to [Interrupt Data Byte(Byte)] in the communication detail settings. Page 151 Setting communication interface (Controller Setting) Output value when [1] is set to [Interrupt Data Byte(Byte)] in the communication detail settings

Output value when [2] is set to [Interrupt Data Byte(Byte)] in the communication detail settings

Output value when [4] is set to [Interrupt Data Byte(Byte)] in the communication detail settings*3

(1) When [32bit Storage] in the communication detail settings is set to [LH Order]

(2) When [32bit Storage] in the communication detail settings is set to [HL Order]

User

D14

D15 to 19 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

D2036 to 4095 User area User

Address Description Set side

D13

Lower 8 bits

1 byte

D13

Upper 8 bits Lower 8 bits

2 bytes

Upper 8 bits

D14 D13

Upper 8 bitsLower 8 bits Lower 8 bits

4 bytes

Upper 8 bits

D13 D14

Upper 8 bitsLower 8 bits Lower 8 bits

4 bytes

Upper 8 bits

D14 D13

Upper 8 bitsLower 8 bits Lower 8 bits

4 bytes

0x12 0x34 0x56 0x78

LH Order

HL Order

Upper 8 bits

D13

Upper 8 bitsLower 8 bits Lower 8 bits

4 bytes

0x56 0x78 0x12 0x34

Upper 8 bits

D13 D14

Upper 8 bitsLower 8 bits Lower 8 bits

4 bytes

0x12 0x34 0x56 0x78

Upper 8 bits

D13

Upper 8 bitsLower 8 bits Lower 8 bits

4 bytes

0x12 0x34 0x56 0x78

Interrupt output

Interrupt output

D14

D14

2 MICROCOMPUTER CONNECTION (SERIAL) 2.4 Device Data Area

2

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). Interrupt output (D13, D14) To disable the interrupt output, turn on SM52 (interrupt code output disable flag). Page 97 SM devices To execute the interrupt output in format 1, 2, 11, 14, or 15, set the data length to 8 bits in the communication detail settings. When "7 bits" is set, the MSB (8th bit) is ignored. (Example: FFH 7FH) Page 151 Setting communication interface (Controller Setting)

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.

*1 For the address specification method for each data format, refer to the following. Page 99 Message Formats

Model Address Address specification value

Format 1, 2

Format 3 to 6

Format 7 to 10

Format 11 to 13

Format 14, 15

D0 0 D0 D0 0000H 8000H

8001H

D1 1 D1 D1 0001H 8002H

8003H

: : : : : :

D4095 4095 D4095 D4095 0FFFH 9FFEH

9FFFH

D0 0 - - 0000H 8000H

8001H

D1 1 - - 0001H 8002H

8003H

: : - - : :

D4095 4095 - - 0FFFH 9FFEH

9FFFH

Formats 1, 2 : GOT-A900 Series microcomputer connection Formats 3 to 6 : A compatible 1C frame Formats 7 to 10 : QnA compatible 3C/4C frame Formats 11 to 13 : SCHNEIDER EJH's memory link method Formats 14, 15 : GOT-F900 Series microcomputer connection

Upper 8 bits

8000H

Lower 8 bits

8001H

Upper 8 bits

8002H

Lower 8 bits

8003H

Upper 8 bits

9FFEH

Lower 8 bits

9FFFH

Upper 8 bits

8000H

Lower 8 bits

8001H

Upper 8 bits

8002H

Lower 8 bits

8003H

Upper 8 bits

9FFEH

Lower 8 bits

9FFFH

2 MICROCOMPUTER CONNECTION (SERIAL) 2.4 Device Data Area 89

90

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

*1 For the address specification method for each data format, refer to the following. Page 99 Message Formats

Model Address Address specification value

Format 1, 2

Format 3 to 6

Format 7 to 10

Format 11 to 13

Format 14, 15

R0 4096 R0 R0 1000H 0000H

0001H

R1 4097 R1 R1 1001H 0002H

0003H

: : : : : :

R4095 8191 R4095 R4095 1FFFH 1FFEH

1FFFH

R0 4096 - - 1000H 0000H

0001H

R1 4097 - - 1001H 0002H

0003H

: : - - : :

R4095 8191 - - 1FFFH 1FFEH

1FFFH

Formats 1, 2 : GOT-A900 Series microcomputer connection Formats 3 to 6 : A compatible 1C frame Formats 7 to 10 : QnA compatible 3C/4C frame Formats 11 to 13 : SCHNEIDER EJH's memory link method Formats 14, 15 : GOT-F900 Series microcomputer connection

Upper 8 bits

0000H

Lower 8 bits

0001H

Upper 8 bits

0002H

Lower 8 bits

0003H

Upper 8 bits

1FFEH

Lower 8 bits

1FFFH

Upper 8 bits

0000H

Lower 8 bits

0001H

Upper 8 bits

0002H

Lower 8 bits

0003H

Upper 8 bits

1FFEH

Lower 8 bits

1FFFH

2 MICROCOMPUTER CONNECTION (SERIAL) 2.4 Device Data Area

2

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

*1 For the address specification method for each data format, refer to the following. Page 99 Message Formats

*2 For reading or writing data in word units, specify the addresses in a unit of 16 points. (Example: L0, L16, L32, etc.)

Model Address Address specification value

b7 b6 b5 b4 b3 b2 b1 b0 Format 1, 2

Format 3 to 6

Format 7 to 10

Format 11 to 13

Format 14, 15

L7 L6 L5 L4 L3 L2 L1 L0 8192 Same as address column on left*2

2000H A000H

L15 L14 L13 L12 L11 L10 L9 L8 A001H

L23 L22 L21 L20 L19 L18 L17 L16 8193 2001H A002H

L31 L30 L29 L28 L27 L26 L25 L24 A003H

: : : :

L2039 L2038 L2037 L2036 L2035 L2034 L2033 L2032 8319 207FH A0FEH

L2047 L2046 L2045 L2044 L2043 L2042 L2041 L2040 A0FFH

L7 L6 L5 L4 L3 L2 L1 L0 8192 - 2000H A000H

L15 L14 L13 L12 L11 L10 L9 L8 A001H

L23 L22 L21 L20 L19 L18 L17 L16 8193 2001H A002H

L31 L30 L29 L28 L27 L26 L25 L24 A003H

: : : :

L2039 L2038 L2037 L2036 L2035 L2034 L2033 L2032 8319 207FH A0FEH

L2047 L2046 L2045 L2044 L2043 L2042 L2041 L2040 A0FFH

Formats 1, 2 : GOT-A900 Series microcomputer connection Formats 3 to 6 : A compatible 1C frame Formats 7 to 10 : QnA compatible 3C/4C frame Formats 11 to 13 : SCHNEIDER EJH's memory link method Formats 14, 15 : GOT-F900 Series microcomputer connection

2 MICROCOMPUTER CONNECTION (SERIAL) 2.4 Device Data Area 91

92

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

*1 For the address specification method for each data format, refer to the following. Page 99 Message Formats

*2 For reading or writing data in word units, specify the addresses in a unit of 16 points. (Example: M0, M16, M32, etc.)

Model Address Address specification value

b7 b6 b5 b4 b3 b2 b1 b0 Format 1, 2

Format 3 to 6

Format 7 to 10

Format 11 to 13

Format 14, 15

M7 M6 M5 M4 M3 M2 M1 M0 8320 Same as address column on left *2

2080H 2000H

M15 M14 M13 M12 M11 M10 M9 M8 2H001H

M23 M22 M21 M20 M19 M18 M17 M16 8321 2081H 2002H

M31 M30 M29 M28 M27 M26 M25 M24 2003H

: : : :

M2039 M2038 M2037 M2036 M2035 M2034 M2033 M2032 8447 20FFH 20FEH

M2047 M2046 M2045 M2044 M2043 M2042 M2041 M2040 20FFH

M7 M6 M5 M4 M3 M2 M1 M0 8320 - 2080H 2000H

M15 M14 M13 M12 M11 M10 M9 M8 2001H

M23 M22 M21 M20 M19 M18 M17 M16 8321 2081H 2002H

M31 M30 M29 M28 M27 M26 M25 M24 2003H

: : : :

M2039 M2038 M2037 M2036 M2035 M2034 M2033 M2032 8447 20FFH 20FEH

M2047 M2046 M2045 M2044 M2043 M2042 M2041 M2040 20FFH

Formats 1, 2 : GOT-A900 Series microcomputer connection Formats 3 to 6 : A compatible 1C frame Formats 7 to 10 : QnA compatible 3C/4C frame Formats 11 to 13 : SCHNEIDER EJH's memory link method Formats 14, 15 : GOT-F900 Series microcomputer connection

2 MICROCOMPUTER CONNECTION (SERIAL) 2.4 Device Data Area

2

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).

*1 For details and corrective actions for the errors (error codes) that are stored into SD2, refer to the following: Page 94 Details and actions for errors (error codes) stored into SD2

Address Description Set side SD0 SD1

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 [32bit Storage] in the communication detail settings is set to [LH Order] The lower and upper bits are stored in SD0 and SD1 respectively.

(2) When [32bit Storage] in the communication detail settings is set to [HL Order] The upper and lower bits are stored in SD0 and SD1 respectively.

System

SD2*1 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 Other station (Communication error that occurred on another GOT when multiple GT21 units 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.

SD8 Clock data (year) The last two digits of four-digit year data are stored.

SD9 Clock data (day of the week) Day-of-the-week data is stored. 0: Sunday 1: Monday 2: Tuesday 3: Wednesday 4: Thursday 5: Friday 6: Saturday

SD10 to 15 Unused

SD0SD1

Lower wordUpper word

SD1SD0

Lower wordUpper word

2 MICROCOMPUTER CONNECTION (SERIAL) 2.4 Device Data Area 93

94

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).

Details and actions for errors (error codes) stored into SD2 Error code Description Action 0 No error

1, 101 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.

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.

Review the contents of the message to transmit. Check the commands in the message. Page 101 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.

6, 107 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.

2 MICROCOMPUTER CONNECTION (SERIAL) 2.4 Device Data Area

2

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.

Model Address Address specification value

Formats 1, 2

Formats 3 to 6

Formats 7 to 10

Formats 11 to 13

Formats 14, 15*2

SD0 8448 D9000 SD0 2100H 2100H

2101H

SD1 8449 D9001 SD1 2101H 2102H

2103H

SD2 8450 D9002 SD2 2102H 2104H

2105H

SD3 8451 D9003 SD3 2103H 2106H (3000H)

2107H (3001H)

SD4 8452 D9004 SD4 2104H 2108H (3002H)

2109H (3003H)

SD5 8453 D9005 SD5 2105H 210AH (3004H)

210BH (3005H)

SD6 8454 D9006 SD6 2106H 210CH (3006H)

210DH (3007H)

SD7 8455 D9007 SD7 2107H 210EH (3008H)

210FH (3009H)

SD8 8456 D9008 SD8 2108H 2110H (300AH)

2111H (300BH)

SD9 8457 D9009 SD9 2109H 2112H (300CH)

2113H (300DH)

Upper 8 bits

2100H

Lower 8 bits

2101H

Upper 8 bits

2102H

Lower 8 bits

2103H

Upper 8 bits

2104H

Lower 8 bits

2105H

Upper 8 bits

2106H(3000H)

Lower 8 bits

2107H(3001H)

Upper 8 bits

2108H(3002H)

Lower 8 bits

2109H(3003H)

Upper 8 bits

210AH(3004H)

Lower 8 bits

210BH(3005H)

Upper 8 bits

210CH(3006H)

Lower 8 bits

210DH(3007H)

Upper 8 bits

210EH(3008H)

Lower 8 bits

210FH(3009H)

Upper 8 bits

2110H(300AH)

Lower 8 bits

2111H(300BH)

Upper 8 bits

2112H(300CH)

Lower 8 bits

2113H(300DH)

2 MICROCOMPUTER CONNECTION (SERIAL) 2.4 Device Data Area 95

96

*1 For the address specification method for each data format, refer to the following. Page 99 Message Formats

*2 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.

SD0 8448 D9000 - - 2100H

2101H

SD1 8449 D9001 - - 2102H

2103H

SD2 8450 D9002 - - 2104H

2105H

SD3 8451 D9003 - - 2106H (3000H)

2107H (3001H)

SD4 8452 D9004 - - 2108H (3002H)

2109H (3003H)

SD5 8453 D9005 - - 210AH (3004H)

210BH (3005H)

SD6 8454 D9006 - - 210CH (3006H)

210DH (3007H)

SD7 8455 D9007 - - 210EH (3008H)

210FH (3009H)

SD8 8456 D9008 - - 2110H (300AH)

2111H (300BH)

SD9 8457 D9009 - - 2112H (300CH)

2113H (300DH)

Formats 1, 2 : GOT-A900 Series microcomputer connection Formats 3 to 6 : A compatible 1C frame Formats 7 to 10 : QnA compatible 3C/4C frame Formats 11 to 13 : SCHNEIDER EJH's memory link method Formats 14, 15 : GOT-F900 Series microcomputer connection

Model Address Address specification value

Formats 1, 2

Formats 3 to 6

Formats 7 to 10

Formats 11 to 13

Formats 14, 15*2

Upper 8 bits

2100H

Lower 8 bits

2101H

Upper 8 bits

2102H

Lower 8 bits

2103H

Upper 8 bits

2104H

Lower 8 bits

2105H

Upper 8 bits

2106H(3000H)

Lower 8 bits

2107H(3001H)

Upper 8 bits

2108H(3002H)

Lower 8 bits

2109H(3003H)

Upper 8 bits

210AH(3004H)

Lower 8 bits

210BH(3005H)

Upper 8 bits

210CH(3006H)

Lower 8 bits

210DH(3007H)

Upper 8 bits

210EH(3008H)

Lower 8 bits

210FH(3009H)

Upper 8 bits

2110H(300AH)

Lower 8 bits

2111H(300BH)

Upper 8 bits

2112H(300CH)

Lower 8 bits

2113H(300DH)

2 MICROCOMPUTER CONNECTION (SERIAL) 2.4 Device Data Area

2

SM devices The SM devices are bit devices into which interrupt outputs and clock data that turn ON or OFF at 1-second cycles.

List of SM devices The following shows the SM devices (virtual devices inside the GOT).

*1 After the ON or OFF state is changed, the interrupt data is output within 1 to 10 ms. *2 When the ON or OFF state of SM0 to 49 is changed from the host side, interrupt output is not performed.

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). Interrupt outputs (SM0 to 49) To disable the interrupt output, turn on SM52 (interrupt code output disable flag). Page 97 SM devices To execute the interrupt output in format 1, 2, 11, 14, or 15, set the data length to 8 bits in the communication detail settings. When "7 bits" is set, the MSB (8th bit) is ignored. (Example: FFH 7FH) Page 151 Setting communication interface (Controller Setting)

Address Description Set side SM0 to 49 Interrupt output

When the ON or 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

Set the data amount (bytes) for an interrupt output to [Interrupt Data Byte(Byte)] in the communication detail settings. Page 151 Setting communication interface (Controller Setting)

User

SM50 1-second cycle clock Turns ON and OFF in 1-second cycles.

System

SM51 2-second cycle clock Turns ON and OFF in 2-second cycles.

SM52 Interrupt code output disable flag Enables or disables the output of the interrupt code and special interrupt code. OFF: Output enabled, ON: Output disabled When the output is set to be disabled, no interrupt data are output to the host. (Relevant devices: D13, D14, SM0 to 49)

User

SM53 to 63 Unused

Address Event type

SM0 Changed from OFF to ON

Changed from ON to OFF

Changed from OFF to ON

Changed from ON to OFF

Changed from OFF to ON

Changed from ON to OFF

Changed from OFF to ON

Changed from ON to OFF

Changed from OFF to ON

Changed from ON to OFF

Interrupt code

SM1

SM2

50H

51H

52H

53H

54H

55H

SM48 B0H

B1H

SM49 B2H

B3H

0.5 0.5

1 1

2 MICROCOMPUTER CONNECTION (SERIAL) 2.4 Device Data Area 97

98

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.

*1 For the address specification method for each data format, refer to the following. Page 99 Message Formats

*2 In formats 3 to 6, values are specified within a range of M9000 to 9052. *3 In formats 7 to 10, values are specified within a range of SM0 to 52. *4 For reading or writing data in word units, specify the addresses in a unit of 16 points. (Example: SM0, SM16, SM32, etc.)

Model Address Address specification value

b7 b6 b5 b4 b3 b2 b1 b0 Format 1, 2

Format 3 to 6

Format 7 to 10

Format 11 to 13

Format 14, 15

SM7 SM6 SM5 SM4 SM3 SM2 SM1 SM0 8464 *2*4 *3*4 2110H 2200H

SM15 SM14 SM13 SM12 SM11 SM10 SM9 SM8 2201H

SM23 SM22 SM21 SM20 SM19 SM18 SM17 SM16 8465 2111H 2202H

SM31 SM30 SM29 SM28 SM27 SM26 SM25 SM24 2203H

SM39 SM38 SM37 SM36 SM35 SM34 SM33 SM32 8466 2112H 2204H

SM47 SM46 SM45 SM44 SM43 SM42 SM41 SM40 2205H

Unused SM52 SM51 SM50 SM49 SM48 8467 2113H 2206H

Unused

SM7 SM6 SM5 SM4 SM3 SM2 SM1 SM0 8464 2110H 2200H

SM15 SM14 SM13 SM12 SM11 SM10 SM9 SM8 2201H

SM23 SM22 SM21 SM20 SM19 SM18 SM17 SM16 8465 2111H 2202H

SM31 SM30 SM29 SM28 SM27 SM26 SM25 SM24 2203H

SM39 SM38 SM37 SM36 SM35 SM34 SM33 SM32 8466 2112H 2204H

SM47 SM46 SM45 SM44 SM43 SM42 SM41 SM40 2205H

Unused SM52 SM51 SM50 SM49 SM48 8467 2113H 2206H

Unused

Formats 1, 2 : GOT-A900 Series microcomputer connection Formats 3 to 6 : A compatible 1C frame Formats 7 to 10 : QnA compatible 3C/4C frame Formats 11 to 13 : SCHNEIDER EJH's memory link method Formats 14, 15 : GOT-F900 Series microcomputer connection

2 MICROCOMPUTER CONNECTION (SERIAL) 2.4 Device Data Area

2

2.5 Message Formats This section describes the format of messages that can be used in the microcomputer connection (serial).

Data format type Set the data format in the communication detail settings in GT Designer3. For details of the data format setting method, refer to the following. Page 151 Setting communication interface (Controller Setting)

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.

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.

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.

Formats 11 to 13 (SCHNEIDER EJH's memory link method) This is the same message format as the protocol of the SCHNEIDER EJH's memory link method.

Type Name Description Refer to 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. Page 104 Formats 1, 2

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).

Type Name Description Refer to Format 3 A compatible 1C frame (format 1) This is the basic format of the dedicated protocols. Page 116 Formats 3 to

6Format 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.

Type Name Description Refer to Format 7 QnA compatible 3C/4C frame (format 1) This is the basic format of the MC protocols. Page 121 Formats 7 to

10Format 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.

Type Name Description Refer to Format 11 SCHNEIDER EJH's memory link method

(compatible mode) This is the basic format of the SCHNEIDER EJH's memory link method.

Page 127 Formats 11 to 13

Format 12 SCHNEIDER EJH's memory link method (extended mode, ASCII code 1:1)

This is the format with sum check, CR, and LF appended to the SCHNEIDER EJH's memory link method (compatible mode).

Format 13 SCHNEIDER EJH's memory link method (extended mode, ASCII code 1:n)

This is the format with a station No. appended to the SCHNEIDER EJH's memory link method (extended mode, ASCII code 1:1).

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 99

10

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 Refer to 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.

Page 137 Formats 14, 15

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.

0 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

List of commands The following shows the list of commands available in each data format.

List of commands for formats 1, 2 (GOT-A900 Series microcomputer connection)

*1 Mixed specification of bit devices and word devices is also possible.

List of commands for formats 3 to 6 (A compatible 1C frame)

*1 This is a dedicated command of GOT for the microcomputer connection. *2 Specifies the address of bit devices in 16-point units. (Example: M0, M16, M32, and others)

Command Command name Description Max. number of points processedSymbol ASCII code

RD 52H 44H Batch read in word units Reads bit devices in 16-point units. 99 words (1584 points)

Reads word devices in 1-point units. 99 points

WD 57H 44H Batch write in word units Writes to bit devices in 16-point units. 99 words (1584 points)

Writes to word devices in 1-point units. 99 points

RR 52H 52H Random read in word units *1 Reads multiple different bit devices in 16-point units. 256 words (4096 points)

Reads multiple different word devices in 1-point units. 256 points

RW 52H 57H Random write in word units *1 Writes to multiple different word devices in 16-point units. 128 words (2048 points)

Writes to multiple different word devices in 1-point units. 128 points

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.

Command Command name Description Max. number of points processedSymbol ASCII code

BR JR

42H 52H 4AH 52H

Batch read in bit units Reads bit devices in 1-point units. 64 points

WR QR

57H 52H 51H 52H

Batch read in word units Reads bit devices in 16-point units.*2 64 words (1024 points)

Reads word devices in 1-point units. 64 points

BW JW

42H 57H 4AH 57H

Batch write in bit units Writes to bit devices in 1-point units. 64 points

WW QW

57H 57H 51H 57H

Batch write in word units Writes to bit devices in 16-point units.*2 64 words (1024 points)

Writes to word devices in 1-point units. 64 points

BT JT

42H 54H 4AH 54H

Test in bit units (Random write)

Writes to multiple different bit devices in 1-point units. 64 points

WT QT

57H 54H 51H 54H

Test in word units (Random write)

Writes to multiple different bit devices in 16-point units.*2 64 words (1024 points)

Writes to multiple different word devices in 1-point units. 64 points

TR*1 54H 52H Read clock data Reads the clock data of the GOT.

TS*1 54H 53H Set clock data Sets the clock data of the GOT.

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 101

10

Command lists for formats 7 to 10 (QnA compatible 3C/4C frame)

*1 Mixed specification of bit devices and word devices is also possible. *2 This is a dedicated command of GOT for the microcomputer connection. *3 Specifies the address of bit devices in 16-point units. (Example: M0, M16, M32, and others)

List of commands for formats 11 to 13 (SCHNEIDER EJH's memory link method)

*1 This is a dedicated command of GOT for the microcomputer connection.

Command Sub- command

Command name Description Max. number of points processed

0401 0001 Batch read in bit units Reads bit devices in 1-point units. 64 points

0401 0000 Batch read in word units Reads bit devices in 16-point units.*3 64 words (1024 points)

Reads word devices in 1-point units. 64 points

1401 0001 Batch write in bit units Writes to bit devices in 1-point units. 64 points

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

0403 0000 Random read in word units *1 Reads multiple different bit devices in 16-point and 32- point units.*3

64 words (1024 points)

Reads multiple different word devices in 1-point and 2- point units.

64 points

1402 0001 Random write in bit units Writes to multiple different bit devices in 1-point units. 64 points

1402 0000 Random write in word units *1 Writes to multiple different bit devices in 16-point and 32- point units.*3

64 words (1024 points)

Writes to multiple different word devices in 1-point and 2- point units.

64 points

0406 0000 Multiple block batch read Reads multiple blocks. A bit device (16 bits for 1 point) or a word device (1 word for 1 point) is regarded as one block.*3

64 points

1406 0000 Multiple block batch write Writes multiple blocks. A bit device (16 bits for 1 point) or a word device (1 word for 1 point) is regarded as one block.*3

64 points

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.

Command Command name Description Max. number of points processedSymbol ASCII code

R 52H Batch read in word units Reads bit devices in 16-point units. 256 words (4096 points)

Reads word devices in 1-point units. 256 points

W 57H Batch write in word units Writes to bit devices in 16-point units. Format 11: 496 words (7936 points) Format 12: 256 words (4096 points) Format 13: 256 words (4096 points)

Writes to word devices in 1-point units. Format 11: 496 points Format 12: 256 points Format 13: 256 points

I 49H Interrupt inquiry Issues an interrupt inquiry. (format 13 only)

N*1 4DH Read clock data Reads the clock data of the GOT.

M*1 4EH Set clock data Sets the clock data of the GOT.

2 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

List of commands for formats 14, 15 (GOT-F900 series microcomputer connection) Command Command name Description Max. number of points

processedSymbol ASCII code 0 30H Batch read

(without the station No.) Reads bit devices in byte units. 255 bytes (2040 points)

Reads word devices in byte units. 255 bytes (127 points)

A 41H Batch read (with the station No.)

Reads bit devices in byte units. 255 bytes (2040 points)

Reads word devices in byte units. 255 bytes (127 points)

1 31H Batch write (without the station No.)

Writes to bit devices in byte units. 255 bytes (2040 points)

Writes to word devices in byte units. 255 bytes (127 points)

B 42H Batch write (with the station No.)

Writes to bit devices in byte units. 255 bytes (2040 points)

Writes to word devices in byte units. 255 bytes (127 points)

3 33H Multi-point write in bit units (without the station No.)

Writes bit patterns (bit ON or OFF, inversion, direct specification) in 1-point units (8 bits for 1 point) to a specified device.

70 bytes (560 points)

D 44H Multi-point write in bit units (with the station No.)

4 34H Fill command (without the station No.)

Writes the same value to a range of specified devices.

E 45H Fill command (with the station No.)

5 35H Set clock data (without the station No.)

Sets the clock data of the GOT.

F 46H Set clock data (with the station No.)

6 36H Read clock data (without the station No.)

Reads the clock data of the GOT.

G 47H Read clock data (with the station No.)

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 103

10

Formats 1, 2 The following describes the message formats 1 and 2 (GOT-A900 Series microcomputer connection).

Basic format of data communication

*1 Set the number of interrupt data bytes in the communication detail settings in GT Designer3. For setting the number of interrupt data bytes, refer to the following. Page 151 Setting communication interface (Controller Setting)

*2 Interrupt output can be executed by writing the data to the interrupt output devices (D13 and D14). Page 86 D devices

Item Message format Request message (host GOT)

Response message during normal communication (GOT host)

(1) During processing of read commands

(2) During processing of write commands

Response message during faulty communication (GOT host)

(format 1: GOT-A900 Series microcomputer connection (format 1)) (format 2: GOT-A900 Series microcomputer connection (format 2))

During interrupt output *2

(format 1: GOT-A900 Series microcomputer connection (format 1)) (format 2: GOT-A900 Series microcomputer connection (format 2))

Sum check is performed in this range.

(H) (L)

Command Data

02H

STX

03H

ETX

(H) (L)

Sum Check

Sum check is performed in this range.

Data

02H

STX

03H

ETX

(H) (L)

Sum Check

06H

ACK

15H

NAK

15H

NAK Error Code

Output value

1/2/4 bytes*1

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

Sum checkOutput value

1/2/4 bytes*1

4 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

Details of data items in message format

Data code during communication Communication is performed in ASCII code. (excluding interrupt output)

Control codes

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. Page 101 List of commands

Address Specifies the head No. of the device data to be read or 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. Page 85 Device Data Area

Number of points Specifies the device data points to be read or written. (Setting range: 1 to 99) The address notated in decimal is converted to a 2-digit ASCII code (Hex) and transmitted from the upper digit.

Year, month, day, hour, minute, second and day of the week data Specifies the year, month, day, hour, minute, second, and the day of the week data to be read or 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. Page 112 Read clock data (TR) command Page 113 Set clock data (TS) command

Data Specifies the data to be read from or written 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.

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: Page 115 Error code list

Symbol ASCII code Description STX 02H Start of Text (start marker of message frame)

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 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 105

10

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).

Message Formats Batch read in word units (RD) command 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 Message format Request message (host GOT)

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

(format 1: GOT-A900 Series microcomputer connection (format 1))

(format 2: GOT-A900 Series microcomputer connection (format 2))

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

B C 42H 43H

Sum Check

(H) (L)

Command

R D 52H 44H

(H) (L)

Address

0 1 30H 31H

0 30H

0 30H

(H) (L)

Number of points

0 2 30H 32H

52H + 44H + 30H + 31H + 30H + 30H + 30H + 32H + 03H = 1BCH

D100

D101

0102H

0304H

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

B C 42H 43H

Sum Check

(H) (L)

Command

R D 52H 44H

(H) (L)

Address

0 1 30H 31H

0 30H

0 30H

(H) (L)

Number of points

0 2 30H 32H

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

8 D 38H 44H

Sum Check

(H) (L)

0 1 30H 31H

0 30H

2 32H

(H) (L)

0 3 30H 33H

0 30H

4 34H

Data 1 (D100) Data 2 (D101)

15H

NAK

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

6 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

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 Message format Request message (host GOT)

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

(format 1: GOT-A900 Series microcomputer connection (format 1))

(format 2: GOT-A900 Series microcomputer connection (format 2))

M15 to 0

M31 to 6

0001H

8000H

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

8C 38H43H

Sum Check

(H) (L)

Command

R D 52H 44H

(H) (L)

Address

8 3 38H 33H

2 32H

0 30H

(H) (L)

Number of points

0 2 30H 32H

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

8 C 38H 43H

Sum Check

(H) (L)

Data 1 (M15 to 0)

0 30H

0 30H

1 31H

0 30H

(H) (L)

8 38H

0 30H

0 30H

0 30H

M 1 6

M 1 7

M 1 8

M 1 9

M 2 0

M 2 1

M 2 2

M 2 3

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

00000000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

10000000 00000001 00000000

Data 2 (M31 to 16)

15H

NAK

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 107

10

Batch write in word units (WD) command When writing to a word device The following shows as example of writing "0064H"and "0065H"to virtual devices D100 and D101.

Item Message format Request message (host GOT)

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

(format 1: GOT-A900 Series microcomputer connection (format 1))

(format 2: GOT-A900 Series microcomputer connection (format 2))

D100

D101

0000H

0000H

D100

D101

0064H

0065H

Before execution After execution

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

5 6 35H 36H

Sum Check

(H) (L)

Command

W D 57H 44H

(H) (L)

Address

0 1 30H 31H

0 30H

0 30H

(H) (L)

Number of points

0 2 30H 32H

(H) (L)

Data 1(D100)

0 0 30H 30H

6 36H

4 34H

(H) (L)

Data 2 (D101)

0 0 30H 30H

6 36H

5 35H

06H

ACK

15H

NAK

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

8 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

When writing to a bit device The following shows an example of writing "1"s to virtual devices M0 and M31.

Item Message format Request message (host GOT)

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

(format 1: GOT-A900 Series microcomputer connection (format 1))

(format 2: GOT-A900 Series microcomputer connection (format 2))

M15 to 0 0000H

0000H

0001H

8000H

Before execution After execution

M31 to 16

M15 to 0

M31 to 16

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

5 6 35H 36H

Sum Check

(H) (L)

Data 1 (M15 to 0)

0 30H

0 30H

1 31H

0 30H

(H) (L)

Data 2 (M31 to 16)

8 38H

0 30H

0 30H

0 30H

M 1 6

M 1 7

M 1 8

M 1 9

M 2 0

M 2 1

M 2 2

M 2 3

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

00000000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

10000000 00000001 00000000

(H) (L)

W D 57H 44H

Command

(H) (L)

Address

8 38H

0 30H

2 32H

3 33H

(H) (L)

0 2 30H 32H

Number of points

06H

ACK

15H

NAK

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 109

11

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.)

Item Message format Request message (host GOT)

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

(format 1: GOT-A900 Series microcomputer connection (format 1))

(format 2: GOT-A900 Series microcomputer connection (format 2))

D100 0064H

0001HM15 to 0

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

3 5

33H 35H

Sum Check

(H) (L)

Command

R R

52H 52H

(H) (L)

Address 1

0 1

30H 31H

0

30H

0

30H

(H) (L)

Address 2

8 3

38H 33H

2

32H

0

30H

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

8 E 38H 45H

Sum Check

(H) (L)

Data 1 (D100)

0 30H

6 36H

4 34H

0 30H

00000000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

10000000

(H) (L)

Data 2 (M15 to 0)

0 30H

0 30H

1 31H

0 30H

15H

NAK

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

0 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

Random write in word units (RW) command The following shows an example of writing "0064H" and "1" to virtual devices D100 and M0, respectively.

Item Message format Request message (host GOT)

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

(format 1: GOT-A900 Series microcomputer connection (format 1))

(format 2: GOT-A900 Series microcomputer connection (format 2))

M15 to 0

0000H

Before execution After execution

D100

0000H M15 to 0

0064HD100

0001H

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

C 5 43H 35H

Sum Check

(H) (L)

Address 2

8 38H

2 32H

0 30H

3 33H

00000000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

10000000

(H) (L)

Data 2 (M15 to 0)

0 30H

0 30H

1 31H

0 30H

(H) (L)

R W 52H 57H

Command

(H) (L)

Address 1

0 30H

1 31H

0 30H

0 30H

(H) (L)

Data 1 (D100)

0 30H

6 36H

4 34H

0 30H

*1

Following*1

06H

ACK

15H

NAK

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 111

11

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".)

Item Message format Request message (host GOT)

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

(format 1: GOT-A900 Series microcomputer connection (format 1))

(format 2: GOT-A900 Series microcomputer connection (format 2))

Time display

2004/06/01 18:46:49 TUE

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

A 9 41H 39H

Sum Check

(H) (L)

Command

T R 54H 52H

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

D 0 44H 30H

Sum Check

(H) (L)

Year data

0 4 30H 34H

(H) (L)

Month data

0 6 30H 36H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 2 30H 32H

15H

NAK

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

2 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

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".)

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 corrected day of the week will be set. 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 set.

Item Message format Request message (host GOT)

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

(format 1: GOT-A900 Series microcomputer connection (format 1))

(format 2: GOT-A900 Series microcomputer connection (format 2))

Time display

2004/06/01 18:46:49 TUE

After execution

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

7 37H

Sum Check

7 37H

(H) (L)

Year data

0 4 30H 34H

(H) (L)

Month data

0 6 30H 36H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 2 30H 32H

(H) (L)

Command

T S 54H 53H

06H

ACK

15H

NAK

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 113

11

In the case of interrupt outputs Write data to the interrupt output devices (D13 and D14) to output the data to the host. (Assuming that "3139H" is written to D13 and "AA55H" to D14.)

Item Message format Interrupt output (GOT host)

(1) When [Interrupt Data Byte(Byte)] in the communication detail settings is set to [1]

(2) When [Interrupt Data Byte(Byte)] in the communication detail settings is set to [2]

(3) When [Interrupt Data Byte(Byte)] in the communication detail settings is set to [4] When [32bit Storage] in the communication detail settings is set to [LH Order]

When [32bit Storage] in the communication detail settings is set to [HL Order]

Interrupt

Interrupt output

Example) When [Interrupt Data Byte] in the communication detail settings is set to 2 byte as shown in (2) of the table below

31H

Output value 1

3139HD13

39H

Output value 2

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

3 33H

Sum check

C 43H39H

Output value 1

39H

Output value 1

(format 1: in the case of GOT-A900 Series microcomputer connection (format 1))

(format 2: in the case of GOT-A900 Series microcomputer connection (format 2))

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

6 36H

Sum check

D 44H31H 39H 31H 39H

Output value 1

Output value 2

Output value 1

Output value 2

(format 1: in the case of GOT-A900 Series microcomputer connection (format 1))

(format 2: in the case of GOT-A900 Series microcomputer connection (format 2))

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

6 36H

Sum Check

C 43HAAH

Output value1

55H

Output value2

31H

Output value3

39H

Output value4

AAH

Output value1

55H

Output value2

31H

Output value3

39H

Output value4

(format 1: in the case of GOT-A900 Series microcomputer connection (format 1))

(format 2: in the case of GOT-A900 Series microcomputer connection (format 2))

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

6 36H

Sum Check

C 43H31H

Output value1

39H

Output value2

AAH

Output value3

55H

Output value4

31H

Output value1

39H

Output value2

AAH

Output value3

55H

Output value4

(format 1: in the case of GOT-A900 Series microcomputer connection (format 1))

(format 2: in the case of GOT-A900 Series microcomputer connection (format 2))

4 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

Interrupt output To disable the interrupt output, turn on SM52 (interrupt code output disable flag). Page 97 SM devices To execute the interrupt output in format 1, 2, 11, 14, or 15, set the data length to 8 bits in the communication detail settings. When "7 bits" is set, the MSB (8th bit) is ignored. (Example: FFH 7FH) Page 151 Setting communication interface (Controller Setting)

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.

Precautions Storage order for 32-bit data To use the program of the GOT-A900 series by setting 32-bit data to the GOT1000 series, set [HL Order] for [32bit Storage] in the communication detail settings. If [LH Order] is set, higher-order bits and lower-order bits are reversed when 32-bit data is displayed or written to the GOT.

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.

Review the contents of the message to transmit.

10H Command error An unsupported command was used.

Review the contents of the message to transmit. Check the commands in the message. Page 101 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 in the 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 or write device is out of range.

Review the contents of the message to transmit. Check the devices that can be used and the device ranges. Page 85 Device Data Area7BH Exceeded number of points error

The read or write range has exceeded the device range.

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 115

11

Formats 3 to 6 The following describes the message formats 3 to 6 (A compatible 1C frame).

Basic format of data communication 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: 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))

Details of data items in message format

Data code during communication Communication is performed in ASCII code.

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.

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. Page 151 Setting communication interface (Controller Setting)

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. Page 101 List of commands

Message wait Ignored in a microcomputer connection of the GOT. Specify "0". "0" is converted to a 1-digit ASCII code (hexadecimal) and transmitted.

Sum check is performed in this range.

05H

ENQ

(H) (L)

B A 42H 41H

Sum Check

(H) (L)

Command

R 52H

Q 51H

(H)

Address

D 1 44H 31H

0 30H

0 30H

(H) (L)

Number of points

0 2 30H 32H

(H) (L)

Block No.

0 30H

0 30H

(H) (L)

Station No.

0 30H

0 30H

(H) (L)

PLC No.

0 30H

0 30H 30H

Wait

0

0 30H

(L)

0 30H

0 30H

Character A section

6 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

Address Specifies the head No. of the device data to be read or 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. Page 85 Device Data Area

Number of points Specifies the device data points to be read or 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.

Year, month, day, hour, minute, second and day of the week data Specifies the year, month, day, hour, minute, second, and day of the week data to be read or 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. Page 118 Read clock data (TR) command Page 119 Set clock data (TS) command

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 on error codes generated in formats 3 to 6 (A compatible 1C frame), refer to the following. Page 120 Error code list

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 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 117

11

Message format The following shows the message format of the dedicated commands for a microcomputer connection of GOT.

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".)

Item Message format Request message (host GOT)

Example: Format 3 (A compatible 1C frame (format 1))

Response message during normal communication (GOT host)

Example: Format 3 (A compatible 1C frame (format 1))

Response message during faulty communication (GOT host)

Example: Format 3 (A compatible 1C frame (format 1))

Time display

2004/06/01 18:46:49 TUE

Sum check is performed in this range.

05H

ENQ

(H) (L)

9 6 39H 36H

Sum Check

(H) (L)

Command

R 52H

T 54H

(H) (L)

Station No.

0 30H

0 30H

(H) (L)

PLC No.

0 30H

0 30H 30H

Wait

0

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

9 0 39H 30H

Sum Check

(H) (L)

Year data

0 4 30H 34H

(H) (L)

Month data

0 6 30H 36H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 2 30H 32H

*1

(H) (L)

Station No.

0 30H

0 30H

Following*1

Character B section

(H) (L)

PLC No.

0 30H

0 30H

The above is the case where an overrun error (05H) has occurred.

15H

NAK

(H) (L) 30H 35H

Error code

(H) (L) 30H

Station No.

0 30H

0

(H) (L) 30H

PLC No.

0 30H

0 0 5

8 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

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".)

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 corrected day of the week will be set. 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 set.

Item Message format Request message (host GOT)

Example: Format 3 (A compatible 1C frame (format 1))

Response message during normal communication (GOT host)

Example: Format 3 (A compatible 1C frame (format 1))

Response message during faulty communication (GOT host)

Example: Format 3 (A compatible 1C frame (format 1))

Time display

2004/06/01 18:46:49 TUE

After execution

Sum check is performed in this range.

05H

ENQ

(H) (L)

6 4 36H 34H

Sum Check

(H) (L)

Year data

0 4 30H 34H

(H) (L)

Month data

0 6 30H 36H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 2 30H 32H

*1

(H) (L)

Station No.

0 30H

0 30H

Following*1

Character C section

(H) (L)

PLC No.

0 30H

0 30H

(H) (L)

Command

T 54H

S 53H 30H

Wait

0

06H

ACK

(H) (L) 30H

Station No.

0 30H

0

(H) (L) 30H

PLC No.

0 30H

0

The above is the case where an overrun error (05H) has occurred.

15H

NAK

(H) (L) 30H 35H

Error code

(H) (L) 30H

Station No.

0 30H

0

(H) (L) 30H

PLC No.

0 30H

0 0 5

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 119

12

Error code list The following shows error code, error contents, cause, and measures.

Error code Description Action 01H 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. Page 101 List of commands Check the devices that can be used and the device ranges. Page 85 Device Data Area Check whether the non-existent data is set (e.g. setting "07" at the day of

the week) as clock data.

07H 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.

0 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

Formats 7 to 10 The following describes the message 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 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))

QnA compatible 4C frame (format 5) GOT cannot use the QnA compatible 4C frame (format 5).

Sum check is performed in this range.

05H

ENQ

(H) (L)

5 4 35H 34H

Sum check

(H) (L)

Device code

* 2AH

D 44H

(H) (L)

Block No.

0 30H

0 30H

(H) (L)

Frame ID No.

F 46H

8 38H

(H) (L)

PLC No.

0 30H

0 30H

(H)

Head Device

1 31H

0 30H

0 30H

(L)

0 30H

0 30H

0 30H

Character A section

(H) (L)

Station No.

0 30H

0 30H

(H) (L)

Network No.

0 30H

0 30H

(H)

Request destination module I/O No.

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

Request destination module station No.

0 30H

0 30H

(H) (L)

Host Address No.

0 30H

0 30H

(H)

Command

0 30H

4 34H

(L)

0 30H

1 31H

(H)

Sub-command

0 30H

0 30H

(L)

0 30H

0 30H

(H)

Device points

0 30H

0 30H

(L)

0 30H

2 32H

Following *1

*1

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 121

12

Details of data items in message format

Data code during communication Communication is performed in ASCII code.

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. 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. Page 151 Setting communication interface (Controller Setting)

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. Page 101 List of commands

Device code Specifies the device data points to be read or written. 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. Page 85 Device Data Area

Head device Specifies the head No. of the device data to be read or 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. Page 85 Device Data Area

Device points Specifies the device data points to be read or 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. When using random read or 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 or write commands When setting multiple blocks, limit the total number of points of all blocks to within 64 points.

2 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

Year, month, day, hour, minute, second and day of the week data Specifies the year, month, day, hour, minute, second, and day of the week data to be read or 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. Page 124 Read clock data (1901) command Page 125 Set clock data (0901) command

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 on error codes that are generated in formats 7 to 10 (QnA compatible 3C/4C frame), refer to the following. Page 126 Error code list

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 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 123

12

Message format The following shows the message format of the dedicated commands for a microcomputer connection of GOT.

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".)

Item Message format Request message (host GOT)

Example: Format 7 (QnA compatible 4C frame (format 1))

Response message during normal communication (GOT host)

Example: Format 7 (QnA compatible 4C frame (format 1))

Response message during faulty communication (GOT host)

Example: Format 7 (QnA compatible 4C frame (format 1))

Time display

2004/06/01 18:46:49 TUE

Sum check is performed in this range.

05H

ENQ

(H) (L)

9 39H

Sum check

A 41H

(H) (L)

Frame ID No.

F 46H

8 38H

(H) (L)

PLC No.

0 30H

0 30H

Character A section

(H) (L)

Station No.

0 30H

0 30H

(H) (L)

Network No.

0 30H

0 30H

(H)

Request destination module I/O No.

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

Request destination module station No.

0 30H

0 30H

(H) (L)

Host Address No.

0 30H

0 30H

(H)

Command

9 39H

(L)

0 30H

1 31H

1 31H

(H)

Sub-command

0 30H

0 30H

(L)

0 30H

0 30H

Following *1

*1

Sum check is performed in this range.

02H

STX

(H) (L)

Sum check

E 43H

E 43H

(H) (L)

Frame ID No.

F 46H

8 38H

(H) (L)

PLC No.

0 30H

0 30H

Character B section

(H) (L)

Station No.

0 30H

0 30H

(H) (L)

Network No.

0 30H

0 30H

(H)

Request destination module I/O No.

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

Request destination module station No.

0 30H

0 30H

(H) (L)

Host Address No.

0 30H

0 30H

Following *1

*1

03H

ETX

(H) (L)

Year data

0 4 30H 34H

(H) (L)

Month data

0 6 30H 36H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 2 30H 32H

NAK

15H

(H) (L)

Frame ID No.

F 46H

8 38H

(H) (L)

PLC No.

0 30H

0 30H

(H) (L)

Station No.

0 30H

0 30H

(H) (L)

Network No.

0 30H

0 30H

(H)

Request destination module I/O No.

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

Request destination module station No.

0 30H

0 30H

(H) (L)

Host Address No.

0 30H

0 30H

*1

Following *1

(H)

Error code

7 37H

F 46H

(L)

6 36H

9 39H

The above is the case where a parity error (7F69H) has occurred.

4 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

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".)

Item Message format Request message (host GOT)

Example: Format 7 (QnA compatible 4C frame (format 1))

Response message during normal communication (GOT host)

Example: Format 7 (QnA compatible 4C frame (format 1))

Response message during faulty communication (GOT host)

Example: Format 7 (QnA compatible 4C frame (format 1))

Time display

2004/06/01 18:46:49 TUE

After execution

Sum check is performed in this range.

05H

ENQ

(H) (L)

7 37H

5 35H

(H) (L)

F 46H

8 38H

(H) (L)

0 30H

0 30H

Character C section

(H) (L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

(H)

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

*1

(H) (L)

0 4 30H 34H

(H) (L)

0 6 30H 36H

(H) (L)

0 1 30H 31H

(H) (L)

1 8 31H 38H

(H) (L)

4 6 34H 36H

(H) (L)

4 9 34H 39H

(H) (L)

0 2 30H 32H

(H)

Command

0 30H

9 39H

(L)

0 30H

1 31H

(H)

Sub-command

0 30H

0 30H

(L)

0 30H

0 30H

Character C section

1)

Sum checkFrame ID No. PLC No.Station No. Network

No. Request destination

module I/O No.

Request destination module station No.

Host Address No.

Following *1

Year data Month data Day data Hour data Minute data Second data

Day-of- week data

1)

06H

ACK

(H) (L)

F 46H

8 38H

(H) (L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

(H)

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

Frame ID No. PLC No.Station No. Network

No. Request destination

module I/O No. Request destination module station No.

Host Address No.

NAK

15H

(H) (L)

F 46H

8 38H

(H) (L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

(H)

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

*1

(H)

Error code

7 37H

F 46H

(L)

6 36H

9 39H

The above is the case where a parity error (7F69H) has occurred.

Frame ID No. PLC No.Station No. Network

No. Request destination

module I/O No. Request destination module station No.

Host Address No.

Following*1

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 125

12

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 corrected day of the week will be set. 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 set.

Error code list The following shows error code, error contents, cause, and measures.

Error code Description Action 7E40H Command error

An unsupported command or sub-command was used. Review the contents of the message to transmit. Check the commands in the message. Page 101 List of commands

7E41H Data length error Specified the data points exceeding those that can be communicated during random read or write.

Review the contents of the message to transmit. Check the devices that can be used and the device ranges. Page 85 Device Data Area

7E42H Number of data error The number of requests exceeds the command range.

7E43H Device error A non-existent device has been specified.

Review the contents of the message to transmit. Check the devices that can be used and the device ranges. Page 85 Device Data Area

7E46H 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.

7E4FH Exceeded number of points error The read or write range has exceeded the device range.

Review the contents of the message to transmit. Check the devices that can be used and the device ranges. Page 85 Device Data Area

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 or CR+LF was not found within the upper limit of the receive buffer.

Check the communication cable and communication module attachment. Check the settings in the 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 in the communication detail settings. Decrease the transmission speed.

7F68H Framing error The data bit and/or stop bit are not correct.

Check the communication cable and communication module attachment. Check the settings in the communication detail settings. Match the GOT and host transmission settings.7F69H Parity error

The parity bit does not match.

7F6AH Buffer full error The receive buffer overflowed.

Check the communication cable and communication module attachment. Check the settings in the communication detail settings. Review the contents of the message to transmit.

6 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

Formats 11 to 13 The following describes the message formats 11 to 13 (SCHNEIDER EJH's (former Digital Electronics Corporation) memory link method).

Basic format of data communication This is the same format as the protocol of the SCHNEIDER EJH'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 SCHNEIDER EJH This section describes items whose settings differ from the protocols of the SCHNEIDER EJH's memory link method and dedicated commands for a microcomputer connection of the GOT. Example: Request message for the batch read in word units (R) command in format 13 (SCHNEIDER EJH's memory link method (extended mode, ASCII code 1:n))

Compatibility with the SCHNEIDER EJH's memory link method In the case of formats 12 and 13 (SCHNEIDER EJH's memory link method (extended mode)), a communication error may occur since some communication packets are not compatible with the SCHNEIDER EJH'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.

When the digital compatible signal turns on, interrupt outputs (D13 to D14, SM0 to SM49) are invalid. To use interrupt outputs, turn off the digital compatible signal. For the GOT internal device, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

Sum check is performed in this range.

05H

ENQ

(H) (L)

5 E 35H 45H

Sum Check

(H) (L)

Station No.

0 30H

0 30H

(H)

Address

0 30H

4 34H

(L)

0 30H

6 36H

(H)

Number of points

0 30H

0 30H

(L)

0 30H

2 32H1BH

ESC

52H

R 0DH

CR

0AH

LFCom- mand

Device Function Bit Bit

position Settings

GS580 Microcomputer connection extended setting (CH1)

Digital compatible signal

b0 0: Partly compatible (Default) 1: Fully compatible

GS581 Microcomputer connection extended setting (CH2)

Digital compatible signal

b0 0: Partly compatible (Default) 1: Fully compatible

GS582 Microcomputer connection extended setting (CH3)

Digital compatible signal

b0 0: Partly compatible (Default) 1: Fully compatible

GS583 Microcomputer connection extended setting (CH4)

Digital compatible signal

b0 0: Partly compatible (Default) 1: Fully compatible

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 127

12

Details of data items in message format

Data code during communication Communication is performed in ASCII code.

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. Page 101 List of commands

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. Page 153 Communication detail settings

Address Specifies the head No. of the device data to be read or 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. Page 85 Device Data Area

Number of points Specifies the device data points to be read or written. The address notated in hexadecimal is converted to a 4-digit ASCII code (Hex) and transmitted from the upper digit. The setting range depends on the format and command.

Year, month, day, hour, minute, second and day of the week data Specifies the year, month, day, hour, minute, second, and day of the week data to be read or 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. Page 130 Read clock data (N) command Page 132 Set clock data (M) command

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 on the error codes generated in formats 12 and 13 (SCHNEIDER EJH's memory link method (extended mode)), refer to the following. Page 136 Error code list

Format Command Command name Setting range 11 R Batch read in word units 1 to 100H

W Batch write in word units 1 to 1F0H

12 R Batch read in word units 1 to 100H

W Batch write in word units

13 R Batch read in word units 1 to 100H

W Batch write in word units

8 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

When connecting a microcomputer or others that uses the protocol of the SCHNEIDER EJH's memory link method with the GOT To do so, 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 129

13

Message format The following shows the message format of the dedicated commands for a microcomputer connection of GOT.

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".)

Item Message format Request message (host GOT)

Example: Format 13 (SCHNEIDER EJH's memory link method (extended mode, ASCII code 1:n)) Digital compatible signal (GS580 to GS583): OFF (Partly compatible)

Digital compatible signal (GS580 to GS583): ON (Fully compatible)

Response message during normal communication (GOT host)

Example: Format 13 (SCHNEIDER EJH's memory link method (extended mode, ASCII code 1:n)) Digital compatible signal (GS580 to GS583): OFF (Partly compatible)

Digital compatible signal (GS580 to GS583): ON (Fully compatible)

Time display

2004/06/01 18:46:49 TUE

This range Sum check

05H

ENQ

(H) (L)

C E 43H 45H

Sum Check

(H) (L)

Station No.

0 30H

0 30H 1BH

ESC

4EH

N 0DH

CR

0AH

LFCom- mand

This range Sum check

05H

ENQ

(H) (L)

C 9 43H 39H

Sum Check

(H) (L)

Station No.

0 30H

0 30H 1BH

ESC

4EH

N 0DH

CR

0AH

LFCom- mand

This range Sum check

02H

STX

(H) (L)

8 E 38H 45H

Sum Check

(H) (L)

Station No.

0 30H

0 30H 1BH

ESC

41H

A 0DH

CR

0AH

LF

(H) (L)

Year data

0 4 30H 34H

(H) (L)

Month data

0 6 30H 36H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data 4 9

34H 39H

(H) (L)

Day-of- week data 0 2

30H 32H

*1

Following*1

03H

ETXCom- mand

This range Sum check

02H

STX

(H) (L)

8 C 38H 43H

Sum Check

(H) (L)

Station No.

0 30H

0 30H 1BH

ESC

41H

A 0DH

CR

0AH

LF

(H) (L)

Year data

0 4 30H 34H

(H) (L)

Month data

0 6 30H 36H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data 4 9

34H 39H

(H) (L)

Day-of- week data 0 2

30H 32H

*1

Following*1

03H

ETXCom- mand

0 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

Response message during faulty communication (GOT host)

Example: Format 13 (SCHNEIDER EJH's memory link method (extended mode, ASCII code 1:n))

Item Message format

The above is a case where the sum check error (06H) has occurred.

15H

NAK

(H) (L) 30H 36H

Error code

(H) (L) 30H

Station No.

0 30H

0 0 6 0DH

CR

0AH

LF

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 131

13

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".)

Item Message format Request message (host GOT)

Example: Format 13 (SCHNEIDER EJH's memory link method (extended mode, ASCII code 1:n)) Digital compatible signal (GS580 to GS583): OFF (Partly compatible)

Digital compatible signal (GS580 to GS583): ON (Fully compatible)

Response message during normal communication (GOT host)

Example: Format 13 (SCHNEIDER EJH's memory link method (extended mode, ASCII code 1:n))

Response message during faulty communication (GOT host)

Example: Format 13 (SCHNEIDER EJH's memory link method (extended mode, ASCII code 1:n))

Time display

2004/06/01 18:46:49 TUE

After execution

Sum check is performed in this range.

05H

ENQ

(H) (L)

9 A 39H 41H

Sum Check

(H) (L)

Station No.

0 30H

0 30H 1BH

ESC

4DH

M 0DH

CR

0AH

LF

(H) (L)

Year data

0 4 30H 34H

(H) (L)

Month data

0 6 30H 36H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 2 30H 32H

*1

Following*1

Com- mand

Sum check is performed in this range.

05H

ENQ

(H) (L)

9 5 39H 35H

Sum Check

(H) (L)

Station No.

0 30H

0 30H 1BH

ESC

4DH

M 0DH

CR

0AH

LF

(H) (L)

Year data

0 4 30H 34H

(H) (L)

Month data

0 6 30H 36H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 2 30H 32H

*1

Following*1

Com- mand

06H

ACK

(H) (L) 30H

Station No.

0 30H

0 0DH

CR

0AH

LF

The above is a case where the sum check error (06H) has occurred.

15H

NAK

(H) (L) 30H 36H

Error code

(H) (L) 30H

Station No.

0 30H

0 0 6 0DH

CR

0AH

LF

2 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

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 corrected day of the week will be set. 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 set.

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 133

13

In the case of interrupt inquiry The following shows the 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.)

Item Message format Request message (host GOT)

Example: Format 13 (SCHNEIDER EJH's memory link method (extended mode, ASCII code 1:n)) Digital compatible signal (GS580 to GS583): OFF (Partly compatible)

Digital compatible signal (GS580 to GS583): ON (Fully compatible)

Interrupt inquiry (GOT host)

Example: Format 13 (SCHNEIDER EJH's memory link method (extended mode, ASCII code 1:n)) (1) When [Interrupt Data Byte(Byte)] in the communication detail settings is set to [1]

(2) When [Interrupt Data Byte(Byte)] in the communication detail settings is set to [2]

(3) When [Interrupt Data Byte(Byte)] in the communication detail settings is set to [4]

Interrupt output

Example: When [Interrupt Data Byte(Byte)] is set to [2] in format 11

31H

Output value 1

3139HD13

39H

Output value 2

Interrupt

This range Sum check

05H

ENQ

(H) (L)

C 9 43H 39H

Sum Check

(H) (L)

Station No.

0 30H

0 30H 1BH

ESC

49H

I 0DH

CR

0AH

LFCom- mand

This range Sum check

05H

ENQ

(H) (L)

C 4 43H 34H

Sum Check

(H) (L)

Station No.

0 30H

0 30H 1BH

ESC

49H

I 0DH

CR

0AH

LFCom- mand

This range Sum check is performed.

02H

STX

(H) (L)

Station No.

0 30H

0 30H 1BH

ESC

49H

I 0DH

CR

0AH

LF

(H) (L)

9 4 39H 44H

Sum Check

(H) (L)

3 9 33H 39H

Output value 1

03H

ETXCom- mand

(H) (L)

0 30H 31H

Data quantity

1

Sum check is performed in this range.

02H

STX

(H) (L)

9 39H

Sum Check

F 46H

(H) (L)

Station No.

0 30H

0 30H 1BH

ESC

49H

I 0DH

CR

0AH

LF

(H) (L)

3 1 33H 31H

Output value 1

03H

ETX

(H) (L)

3 9 33H 39H

Output value 2

Com- mand

(H) (L)

0 30H 31H

Data quantity

1

Sum check is performed in this range.

02H

STX

(H) (L)

7 37H

Sum Check

E 45H

(H) (L)

Station No.

0 30H

0 30H 1BH

ESC

49H

I 0DH

CR

0AH

LF

(H) (L)

A 41H

Output value 1

A 41H 03H

ETX

(H) (L)

5 35H

Output value 2

5 35H

(H) (L)

3 1 33H 31H

Output value 3

(H) (L)

3 9 33H 39H

Output value 4

Com- mand

(H) (L)

0 30H 31H

Data quantity

1

4 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

In the case of interrupt outputs Write data to the interrupt output devices (D13 and D14) to output the data to the host. (Assuming that "3139H" is written to D13 and "AA55H" to D14.)

Item Message format Interrupt output (GOT host)

Example: Format 13 (SCHNEIDER EJH's memory link method (extended mode, ASCII code 1:n)) (1) When [Interrupt Data Byte(Byte)] in the communication detail settings is set to [1]

(2) When [Interrupt Data Byte(Byte)] in the communication detail settings is set to [2]

(3) When [Interrupt Data Byte(Byte)] in the communication detail settings is set to [4] When [32bit Storage] in the communication detail settings is set to [LH Order]

When [32bit Storage] in the communication detail settings is set to [HL Order]

Interrupt

Interrupt output

Example) When [Interrupt Data Byte] in the communication detail settings is set to 2 byte as shown in (2) of the table below

31H

Output value 1

3139HD13

39H

Output value 2

This range Sum check is performed.

02H

STX

(H) (L)

Station No.

0 30H

0 30H 1BH

ESC

49H

I 0DH

CR

0AH

LF

(H) (L)

9 4 39H 44H

Sum Check

(H) (L)

3 9 33H 39H

Output value 1

03H

ETXCom- mand

(H) (L)

0 30H 31H

Data quantity

1

Sum check is performed in this range.

02H

STX

(H) (L)

9 39H

Sum Check

F 46H

(H) (L)

Station No.

0 30H

0 30H 1BH

ESC

49H

I 0DH

CR

0AH

LF

(H) (L)

3 1 33H 31H

Output value 1

03H

ETX

(H) (L)

3 9 33H 39H

Output value 2

Com- mand

(H) (L)

0 30H 32H

Data quantity

2

Sum check is performed in this range.

02H

STX

(H) (L)

7 37H

Sum Check

E 45H

(H) (L)

Station No.

0 30H

0 30H 1BH

ESC

49H

I 0DH

CR

0AH

LF

(H) (L)

A 41H

Output value 1

A 41H 03H

ETX

(H) (L)

5 35H

Output value 2

5 35H

(H) (L)

3 1 33H 31H

Output value 3

(H) (L)

3 9 33H 39H

Output value 4

Com- mand

(H) (L)

0 30H 34H

Data quantity

4

Sum check is performed in this range.

02H

STX

(H) (L)

7 37H

Sum Check

E 45H

(H) (L)

Station No.

0 30H

0 30H 1BH

ESC

49H

I 0DH

CR

0AH

LF

(H) (L)

3 33H

Output value 1

1 31H 03H

ETX

(H) (L)

3 33H

Output value 2

9 39H

(H) (L)

A A 41H 41H

Output value 3

(H) (L)

5 5 35H 35H

Output value 4

Com- mand

(H) (L)

0 30H 34H

Data quantity

4

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 135

13

Interrupt output To disable the interrupt output, turn on SM52 (interrupt code output disable flag). Page 97 SM devices To execute the interrupt output in format 1, 2, 11, 14, or 15, set the data length to 8 bits in the communication detail settings. When "7 bits" is set, the MSB (8th bit) is ignored. (Example: FFH 7FH) Page 151 Setting communication interface (Controller Setting)

Error code list In the case of formats 12 and 13 (SCHNEIDER EJH'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.

Precautions Storage order for 32-bit data To use the program of the SCHNEIDER EJH's memory link method by setting 32-bit data to the GOT1000 series, set [HL Order] for [32bit Storage] in the communication detail settings. If [LH Order] is set, higher-order bits and lower-order bits are reversed when 32-bit data is displayed on or written to the GOT.

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.

Review the contents of the message to transmit.

10H Command error An unsupported command was used.

Review the contents of the message to transmit. Check the commands in the message. Page 101 List of commands12H 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 whether the non-existent data is set (e.g. setting "07" at the day of

the week) as clock data.

FAH Address error The start address of the read or write device is out of range.

Review the contents of the message to transmit. Check the data length of the message.(data length of the data section,

etc.)

FBH Exceeded number of points error The read or write range has exceeded the device range.

Review the contents of the message to transmit. Check the devices that can be used and the device ranges. Page 85 Device Data Area

FCH Message format error The format of the received message has error.

Check the settings in the 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 in the communication detail settings. Review the contents of the message to transmit.

6 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

Formats 14, 15 The following describes the message formats 14 and 15 (GOT-F900 Series microcomputer connection).

Basic format of data communication

*1 Set the number of interrupt data bytes in the communication detail settings in GT Designer3. For setting the number of interrupt data bytes, refer to the following. Page 151 Setting communication interface (Controller Setting)

*2 Write data to the interrupt devices (D13 and D14) to enable an interrupt output. Page 86 D devices

Item Message format Request message (host GOT)

(format 14: GOT-F900 Series microcomputer connection (format 1)) (1) w/out station No.

(2) w/station No.

(format 15: GOT-F900 Series microcomputer connection (format 2)) (1) w/out station No.

(2) w/station No.

Response message during normal communication (GOT host)

(1) During processing of read commands (format 14: GOT-F900 Series microcomputer connection (format 1))

(format 15: GOT-F900 Series microcomputer connection (format 2))

(2) During processing of write commands

Response message during faulty communication (GOT host)

During interrupt output *2

02H

STX

0DH

CRDataCom- mand

02H

STX

0DH

CRData

(H) (L)

Station No.Com- mand

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

Sum CheckDataCom-

mand

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

Sum CheckData

(H) (L)

Station No.Com- mand

02H

STX

0DH

CRData

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

Sum CheckData

06H

ACK

15H

NAK

Output value

1/2/4 bytes*1

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 137

13

Details of data items in message format

Data code during communication Communication is performed in ASCII code. (excluding interrupt output)

Control codes

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. Page 101 List of commands

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. Page 151 Setting communication interface (Controller Setting)

Address Specifies the head No. of the device data to be read or 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. Page 85 Device Data Area

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. Page 144 Multi-point write in bit units (3) command (without station No.), multi-point write in bit units (D) command (with station No.)

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. Page 144 Multi-point write in bit units (3) command (without station No.), multi-point write in bit units (D) command (with station No.)

Symbol ASCII code Description STX 02H Start of Text (start marker of message frame)

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

8 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

Number of bytes Specifies the number of bytes of the device data to be batch read or 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.

Number of points 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.

Year, month, day, hour, minute, second and day of the week data Specifies the year, month, day, hour, minute, second, and day of the week data to be read or 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. Page 147 Read clock data (6) command (without station No.), read clock data (G) command (with station No.) Page 148 Set clock data (5) command (w/out station No.), set clock data (F) command (w/station No.)

Data Specifies the data to be read or written from or 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.

Write data Specifies the data to be written 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.

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).

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

B C 42H 43H

Sum Check

(H) (L)

Command

R D 52H 44H

(H) (L)

Address

0 1 30H 31H

0 30H

0 30H

(H) (L)

Number of points

0 2 30H 32H

52H + 44H + 30H + 31H + 30H + 30H + 30H + 32H + 03H = 1BCH

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 139

14

Message format Batch read (0) command (without station No.), batch read (A) command (with station No.) 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 Message format Request message (host GOT)

(format 14: GOT-F900 Series microcomputer connection (format 1))

(format 15: GOT-F900 Series microcomputer connection (format 2))

Response message during normal communication (GOT host)

(format 14: GOT-F900 Series microcomputer connection (format 1))

(format 15: GOT-F900 Series microcomputer connection (format 2))

Response message during faulty communication (GOT host)

R100

R101

3D21H

3604H

02H

STX

0DH

CR

(H) (L)

Station No.

1 5 31H 35H

(H) (L)

Address

0 30H

0 30H

8 38H

(H) (L)

Number of bytes

0 4 30H 34H

A 41H

C 43H

Com- mand

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

E 9 45H 39H

Sum Check

(H) (L)

Station No.

1 5 31H 35H

(H) (L)

Address

0 30H

0 30H

8 38H

(H) (L)

Number of bytes

0 4 30H 34H

A 41H

C 43H

Com- mand

02H

STX

0DH

CR

(H)

Data 1 (R100 upper)

3 33H

(L)

D 44H

(H)

Data 2 (R100 lower)

2 32H

(L)

1 31H

(H)

Data 3 (R101 upper)

3 33H

(L)

6 36H

(H)

Data 4 (R101 lower)

0 30H

(L)

4 34H

02H

STX

03H

ETX

(H) (L)

A 41H

A 41H

(H)

Data 1 (R100 upper)

Data 3 (R101 upper)

3 33H

(L)

D 44H

(H)

Data 2 (R100 lower)

Data 4 (R101 lower)

2 32H

(L)

1 31H

(H)

3 33H

(L)

6 36H

(H)

0 30H

(L)

4 34H

Sum check is performed in this range.

Sum Check

15H

NAK

0 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

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.

Item Message format Request message (host GOT)

(format 14: GOT-F900 Series microcomputer connection (format 1))

(format 15: GOT-F900 Series microcomputer connection (format 2))

Response message during normal communication (GOT host)

(format 14: GOT-F900 Series microcomputer connection (format 1))

(format 15: GOT-F900 Series microcomputer connection (format 2))

Response message during faulty communication (GOT host)

M15 to 0

M31 to 16

0001H

8000H

02H

STX

0DH

CR

(H) (L)

Station No.

1 5 31H 35H

(H) (L)

Address

2 32H

0 30H

(H) (L)

Number of bytes

0 4 30H 34H

A 41H

0 30H

0 30H

Com- mand

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

D 0 44H 30H

Sum Check

(H) (L)

Station No.

1 5 31H 35H

(H) (L)

Address

2 32H

0 30H

(H) (L)

Number of bytes

0 4 30H 34H

A 41H

0 30H

0 30H

Com- mand

02H

STX

0DH

CR

M 1 6

M 1 7

M 1 8

M 1 9

M 2 0

M 2 1

M 2 2

M 2 3

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

00000000 M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

00000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

10000000 00100000000

(H) (L)

Data 1 (M7 to 0)

0 30H

1 31H

(H) (L)

Data 2 (M15 to 8)

0 30H

0 30H

(H) (L)

Data 3 (M23 to 16)

0 30H

0 30H

(H) (L)

Data 4 (M31 to 24)

8 38H

0 30H

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

8 C 38H 43H

Sum Check

M 1 6

M 1 7

M 1 8

M 1 9

M 2 0

M 2 1

M 2 2

M 2 3

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

00000000 M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

00000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

10000000 00100000000

(H) (L)

Data 1 (M7 to 0)

0 30H

1 31H

(H) (L)

Data 2 (M15 to 8)

0 30H

0 30H

(H) (L)

Data 3 (M23 to 16)

0 30H

0 30H

(H) (L)

Data 4 (M31 to 24)

8 38H

0 30H

15H

NAK

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 141

14

Batch write (1) command (without station No.), batch write (B) command (with station No.) 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.

Item Message format Request message (host GOT)

(format 14: GOT-F900 Series microcomputer connection (format 1))

(format 15: GOT-F900 Series microcomputer connection (format 2))

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

R100

R101

0000H

0000H

R100

R101

0064H

0065H

Before execution After execution

02H

STX

0DH

CR

(H) (L)

Station No.

1 5 31H 35H

(H) (L)

Address

0 30H

0 30H

8 38H

(H) (L)

Number of bytes

0 4 30H 34H

B 42H

C 43H

Following*1

Com- mand

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

1 31H

Sum Check

9 39H

(H) (L)

Station No.

1 5 31H 35H

(H) (L)

Address

0 30H

0 30H

8 38H

(H) (L)

Number of bytes

0 4 30H 34H

B 42H

C 43H

(H) (L)

Data 1 (R100 upper)

0 0 30H 30H

(H) (L)

Data 2 (R100 lower)

6 4 36H 34H

(H) (L)

Data 3 (R101 upper)

0 0 30H 30H

(H) (L)

Data 4 (R101 lower)

6 5 36H 35H

Following*1

*1

Com- mand

06H

ACK

15H

NAK

2 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

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.

Item Message format Request message (host GOT)

(format 14: GOT-F900 Series microcomputer connection (format 1))

(format 15: GOT-F900 Series microcomputer connection (format 2))

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

M15 to 0 0000H

0000H

Before execution After execution

M31 to 16

M15 to 0 0001H

8000HM31 to 16

02H

STX

0DH

CR

42H

B

(H) (L)

Station No.

5 35H

1 31H

(H)

Address

0 30H

2 32H

(L)

0 30H

0 30H

(H) (L)

Number of bytes

4 34H

0 30H

Following*1

Com- mand

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

5 A 35H 41H

Sum Check

M 1 6

M 1 7

M 1 8

M 1 9

M 2 0

M 2 1

M 2 2

M 2 3

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

00000000 M 8

M 9

M 1 0

M 1 2

M 1

M 1 4

M 1 5

M 1 1

00000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

10000000 00100000000

(H) (L)

Data 1 (M7 to 0)

0 30H

1 31H

(H) (L)

Data 2 (M15 to 8)

0 30H

0 30H

(H) (L)

Data 3 (M23 to 16)

0 30H

0 30H

(H) (L)

Data 4 (M31 to 24)

8 38H

0 30H

42H

B

(H) (L)

Station No.

5 35H

1 31H

(H)

Address

0 30H

2 32H

(L)

0 30H

0 30H

(H) (L)

Byte Number

4 34H

0 30H

Following*1

*1

3

Com- mand

06H

ACK

15H

NAK

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 143

14

Multi-point write in bit units (3) command (without station No.), multi-point write in bit units (D) command (with 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 Request message (host GOT)

(format 14: GOT-F900 Series microcomputer connection (format 1))

(format 15: GOT-F900 Series microcomputer connection (format 2))

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

02H

STX

0DH

CR

(H) (L)

Station No.

3 33H

1 31H

D 44H

Following*1

(H) (L)

Number of points

0 30H

2 32H

Com- mand

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

C 43H

Sum check

E 45H

(H) (L)

Station No.

3 33H

1 31H

(H) (L)

Address1 Address2

2 32H

0 30H

(H) (L)

Bit pattern1

8 38H

0 30H

D 44H

Following *1

*1

(H) (L)

Number of points

0 30H

2 32H

Write specification 1

1 31H

0 30H

3 33H

(H) (L)

2 32H

0 30H

(H) (L)

Bit pattern2

4 34H

0 30H

Write specification 2

0 30H

F 46

E 45H

*2 *2

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

01010101Source data bit pattern 00000001

01010100Result

(write specification1=1)

M 2 0 3 2

M 2 0 3 3

M 2 0 3 4

M 2 0 3 5

M 2 0 3 6

M 2 0 3 7

M 2 0 3 8

M 2 0 3 9

01010101Source data bit pattern 00000010

01010111Result

(write specification2=0)

Com- mand

06H

ACK

15H

NAK

4 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

*1 The write specification specifies how the data of the specified address is changed in the bit pattern.

Write specification

Function Description Action example

0 ON specification Bits set to "1" by the bit pattern are turned ON. Original data 1010 Bit pattern 1100

Result 1110

1 OFF specification Bits set to "1" by the bit pattern are turned OFF. Original data 1010 Bit pattern 1100

Result 0010

2 Invert specification Bits set to "1" by the bit pattern are inverted. Original data 1010 Bit pattern 1100

Result 0110

3 Write specification The numerical values to write by the bit pattern are specified directly. Original data 1010 Bit pattern 1100

Result 1100

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 145

14

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.

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. Address specifying crossing over different devices The start address and end address can be specified crossing over different devices.

Item Message format Request message (host GOT)

(format 14: GOT-F900 Series microcomputer connection (format 1))

(format 15: GOT-F900 Series microcomputer connection (format 2))

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

R100

0000H

Before execution After execution

R50

0000H

0000H

R100

1616HR50

1616H

1616H

02H

STX

0DH

CR

(H) (L)

Station No.

2 7 32H 37H

(H) (L)

Write Data

1 6 31H 36H

E 45H

(H) (L)

Start address

0 30H

0 30H

4 34H

6 36H

(H) (L)

End address

0 30H

0 30H

9 39H

C 43H

Com- mand

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

B 42H

Sum Check

E 45H

(H) (L)

Station No.

2 7 32H 37H

(H) (L)

Write Data

1 6 31H 36H

E 45H

(H) (L)

Start address

0 30H

0 30H

4 34H

6 36H

(H) (L)

End address

0 30H

0 30H

9 39H

C 43H

Com- mand

06H

ACK

15H

NAK

6 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

Read clock data (6) command (without station No.), read clock data (G) command (with 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".)

Item Message format Request message (host GOT)

(format 14: GOT-F900 Series microcomputer connection (format 1))

(format 15: GOT-F900 Series microcomputer connection (format 2))

Response message during normal communication (GOT host)

(format 14: GOT-F900 Series microcomputer connection (format 1))

(format 15: GOT-F900 Series microcomputer connection (format 2))

Response message during faulty communication (GOT host)

Time display

2004/06/01 18:46:49 TUE

02H

STX

0DH

CR

(H) (L)

Station No.

2 7 32H 37H

G 47H

Com- mand

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

B 42H

Sum Check

3 33H

(H) (L)

Station No.

2 7 32H 37H

G 47H

Com- mand

02H

STX

0DH

CR

(H) (L)

Month data

0 6 30H 36H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 2 30H 32H

(H) (L)

Year data

0 4 30H 34H

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

D 0 44H 30H

Sum Check

(H) (L)

Month data

0 6 30H 36H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 2 30H 32H

(H) (L)

Year data

0 4 30H 34H

15H

NAK

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 147

14

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".)

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 corrected day of the week will be set. 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 set.

Item Message format Request message (host GOT)

(format 14: GOT-F900 Series microcomputer connection (format 1))

(format 15: GOT-F900 Series microcomputer connection (format 2))

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

Time display

2004/06/01 18:46:49 TUE

After execution

46H

F 0DH

CR

(H) (L)

Station No.

2 7 32H 37H

(H) (L)

Month data

0 6 30H 36H

(H) (L)

Day Data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 2 30H 32H

(H) (L)

Year data

0 4 30H 34H02H

STX Com- mand

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

7 F 37H 46H

Sum Check

(H) (L)

Station No.

2 7 32H 37H

(H) (L)

Month data

0 6 30H 36H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 2 30H 32H

(H) (L)

Year data

0 4 30H 34H

46H

F Following*1

*1

Com- mand

06H

ACK

15H

NAK

8 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

In the case of interrupt outputs Write data to the interrupt output devices (D13 and D14) to output the data to the host. (Assuming that "3139H" is written to D13 and "AA55H" to D14.)

Interrupt output To disable the interrupt output, turn on SM52 (interrupt code output disable flag). Page 97 SM devices To execute the interrupt output in format 1, 2, 11, 14, or 15, set the data length to 8 bits in the communication detail settings. When "7 bits" is set, the MSB (8th bit) is ignored. (Example: FFH 7FH) Page 151 Setting communication interface (Controller Setting)

Item Message format Interrupt output (GOT host)

(1) When [Interrupt Data Byte(Byte)] in the communication detail settings is set to [1]

(2) When [Interrupt Data Byte(Byte)] in the communication detail settings is set to [2]

(3) When [Interrupt Data Byte(Byte)] in the communication detail settings is set to [4] When [32bit Storage] in the communication detail settings is set to [LH Order]

When [32bit Storage] in the communication detail settings is set to [HL Order]

Example) When [Interrupt Data Byte] in the communication detail settings is set to 2 byte as shown in (2) of the table below

Interrupt

Interrupt output

31H

Output value 1

3139HD13

39H

Output value 2

39H

Output value 1

31H

Output value 1

39H

Output value 2

AAH

Output value 1

55H

Output value 2

31H

Output value 3

39H

Output value 4

31H

Output value 1

39H

Output value 2

AAH

Output value 3

55H

Output value 4

2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats 149

15

Error code list When faulty, the error code is stored in SD2. For details on error code stored in SD2, the error contents, cause and measures, refer to the following. Page 94 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.

0 2 MICROCOMPUTER CONNECTION (SERIAL) 2.5 Message Formats

2

2.6 GOT Side Settings Setting communication interface (Controller Setting)

Controller setting Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set the following items. [Manufacturer]: [Others] [Controller Type]: [Computer] [I/F]: Interface to be used [Detail Setting]: Configure the settings according to the usage environment. Page 153 Communication detail settings

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

2 MICROCOMPUTER CONNECTION (SERIAL) 2.6 GOT Side Settings 151

15

Extension setting for microcomputer Set the GOT interface connecting to the n+1th GOT. No setting is required for a terminal GOT.

Microcomputer connection extension The setting is required when connecting multiple GOTs for one microcomputer.

1. Select [Common] [Peripheral Setting] [GOT(Extended Computer)] from the menu.

2. Set the interface to which the n+1th GOT is connected.

3. Clicking the detail setting button displays the Communication Detail Settings dialog box for the communication driver.

4. When you have completed the settings, click the [OK] button.

Item Description Range Connection CH No. This CH No. is used for the connection with a microcomputer or n-1th GOT.

(Default: 1) 1 fixed

2. 3.

Click!

2 2 MICROCOMPUTER CONNECTION (SERIAL) 2.6 GOT Side Settings

2

Communication detail settings Make the settings according to the usage environment.

Item Description Range Transmission Speed(BPS) Set this item when change the transmission speed used for communication

with the connected equipment. (Default: 19200bps)

4800bps, 9600bps, 19200bps, 38400bps, 57600bps, 115200bps

Data Bit Set this item when change the data length used for communication with the connected equipment. (Default: 7bits)

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

Format Select the communication format. (Default: 1)

1 to 15

Interrupt Data Byte(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: No)

Yes, 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 MICROCOMPUTER CONNECTION (SERIAL) 2.6 GOT Side Settings 153

15

Special Interrupt Code A special interrupt code is output when each event occurs. However, when multiple events occur simultaneously, the special interrupt code may not be output. The following shows the types of special interrupt codes and events.

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. Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. User's Manual of GOT used. Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective.

Special Interrupt Code (Hex)

Event type

20H

Base screen, overlap window 1 to 5 When the screen is switched by the screen switching device, the special interrupt code will be output. The base screen and each overlap window are switched independently. (Example of output) When all the screen switching device values assigned to the Base Screen and Overlap Window 1 to 2 are changed, 6 special interrupt codes are output.

21H This code is output when a numerical or ASCII input is completed.

22H This code is output when reading or writing of the recipe data is completed.

23H This code is output when a barcode or RFID data is read.

4 2 MICROCOMPUTER CONNECTION (SERIAL) 2.6 GOT Side Settings

2

2.7 System Configuration Examples The following shows a system configuration example in the case of the microcomputer connection (serial).

System configuration The system configuration example illustrated below is explained in this section.

Communication settings on GOT side and monitor screen settings Transmission settings Set the transmission settings of the GOT. Configure the transmission settings for the microcomputer connection (serial) in the communication detail settings in GT Designer3. Page 153 Communication detail settings

Monitor screen settings The following shows the monitor screen settings in this system configuration example. Common settings Set D20 to the screen switching device (base screen).

1. Select [Common] [GOT Environmental Setting] [Screen Switching/Window] to display [Environment Setup] on GT Designer3.

2. Set D20 to the screen switching device (base screen).

Setting item Setting details Transmission Speed(BPS) 38400bps

Data bit 8bits

Stop bit 1bit

Parity Even

Host address (0 to 31) 0

Format 1

Interrupt Data Byte(Byte) 1

Special Interrupt Code None

Control Method None

32bit Storage LH Order

IBM-PC/AT-compatible PC (Microsoft Visual C++ Ver.6.0)

2 MICROCOMPUTER CONNECTION (SERIAL) 2.7 System Configuration Examples 155

15

Monitor screen image Create the following screens by GT Designer3. Base screen 1

1. 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.

2. Switch 1 This is the screen switching switch to [Sample Screen 2]. Touching this changes the base screen to [Sample Screen 2]. Base screen 2

3. Bit lamp The device status of D22.b0 is displayed as a lamp.

4. Switch 2 This is an alternate switch for changing the state of D22.b0.

5. Switch 3 This is the screen switching switch to [Sample Screen 1]. Touching this changes the base screen to [Sample Screen 1]. Numerical display

No. Basic Settings

Device/Style

Device Data Type Format Number Size Digits 1 D21 Unsigned BIN16 Signed Decimal Arbitrary 4

Sample Screen 1

123

Screen 2

Sample Screen 2

Screen 1

6 2 MICROCOMPUTER CONNECTION (SERIAL) 2.7 System Configuration Examples

2

Touch switch

Bit lamp

No. Basic Settings

Action

Action Next Screen Device Data Type Setting Value Action Type 2 Screen Switching

Base Fixed Screen No.2

Word D13 Signed BIN16

Constant 1

4 BIt D22.b0 Alternate

5 Screen Switching Base

Fixed Screen No.1

Word D13 Signed BIN16

Constant 255

No. Basic Settings

Device/Style

Lamp Type Device Shape Shape Attribute 3 BIt D22.b0 Arbitrary Arbitrary

2 MICROCOMPUTER CONNECTION (SERIAL) 2.7 System Configuration Examples 157

15

Outline of system operation The following describes the processing on the host side, display or 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.)

Processing Processing on the host side Packet used for data transfer

Display or processing on the GOT side

Initial processing Opens the port.

Writes "1" to the screen switching device (D20). Screen 1 batch switching Write packet *1

Displays base screen 1.

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). Batch numerical value display write packet *2

Displays "0" on the numerical value display on base screen 1.

Reception of response or interrupt from GOT

When receiving a response to writing to device (D21) from the GOT

Issues the current value acquisition request to device (D21).

Batch numerical value display read packet *3

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 receiving a response to reading of device (D21) from the GOT

Creates the next device value (D21).

Calculates the sum check of the send packet.

Issues the update request of device (D21).

Batch numerical value display write packet *2

When receiving an interrupt requesting the base screen switching from 1 to 2

Sets the state of the base screen to base screen 2.

Interrupt receive packet *6 Touch touch switch 1 to switch to base screen 2. Notify the host by an interrupt.

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 packet *6 Touch touch switch 3 to switch to base screen 1. Notify the host by an interrupt.

End processing (only when receiving an error response)

Close the port.

8 2 MICROCOMPUTER CONNECTION (SERIAL) 2.7 System Configuration Examples

2

*1 Displays the send packet structure of the screen 1 batch switching write packet.

*2 Displays the send packet structure of the numerical value display batch write packet.

*3 Displays the send packet structure of the numerical value display batch read packet.

*4 Displays the receive packet structure of the batch write response packet.

*5 Displays the receive packet structure of the batch read response packet.

*6 Displays the receive packet structure of the interrupt receive packet.

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

8 2 38H 32H

Sum Check

(H) (L)

Command

W D 57H 44H

(H) (L)

Address

0 2 30H 32H

0 30H

0 30H

(H) (L)

Number of points

0 1 30H 31H

(H) (L)

Data 1 (D20)

0 0 30H 30H

1 31H

0 30H

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

Sum check

(Changes according to data section.)

(H) (L)

Command

W D 57H 44H

(H) (L)

Address

0 2 30H 32H

1 31H

0 30H

(H) (L)

Number of points

0 1 30H 31H

(H) (L)

Data 1 (D21)

(any value)

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

B D 42H 44H

Sum Check

(H) (L)

Command

R D 52H 44H

(H) (L)

Address

0 1 30H 31H

2 32H

(H) (L)

Number of points

0 1 30H 31H

0 30H

15H

NAK

When an error occurred

06H

ACK

When normally operated

Sum check is performed in this range.

02H

STX

03H

ETX

(H) (L)

Sum check

(Changes according to data section.)

(H) (L)

Data

(any data)

When normally operated

15H

NAK

When an error occurred

Output value

Interrupt data (value of D13)

2 MICROCOMPUTER CONNECTION (SERIAL) 2.7 System Configuration Examples 159

16

2.8 Device Range that Can Be Set For the device setting dialog and the device range that can be used on the GOT, refer to the following. Page 434 Microcomputer ([Computer])

2.9 Precautions

GOT clock control Even though the time setting function and time notification function are set in the GOT time setting, the settings are disabled. When reading from or writing to the clock data between the GOT and host, use the dedicated command.

Operation in which the GOT shifts to the offline mode Before performing operation in which the GOT shifts to the offline mode such as writing the package data, stop the communication between the GOT and the host. After shifting to the offline mode, the GOT cannot respond to the requests from the host. Even after the GOT returns from the offline mode, the communication may not be performed until the timeout time of the host side elapses.

0 2 MICROCOMPUTER CONNECTION (SERIAL) 2.8 Device Range that Can Be Set

3

3 MICROCOMPUTER CONNECTION (ETHERNET) Page 161 Microcomputer connection (Ethernet) Page 162 System Configuration Page 163 Device Data Area Page 177 Message Formats Page 231 GOT Side Settings Page 234 System Configuration Examples Page 235 Device Range that Can Be Set Page 235 Precautions

3.1 Microcomputer connection (Ethernet) The microcomputer connection (Ethernet) is a function by which data can be written or read from a personal computer, microcomputer board, PLC, and others (hereinafter, host) to the virtual devices of the GOT by connecting the host and the GOT by 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. Page 70 Microcomputer Connection (Serial)

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.1 Microcomputer connection (Ethernet) 161

16

3.2 System Configuration For the microcomputer connection (Ethernet)

*1 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.

*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.

*3 GT25-W, GT2505-V does not support the option device. *4 The number of connectable controllers per GOT channel is indicated. *5 The number of GOTs connectable to one host is indicated.

Host Connection cable GOT Number of connectable equipment

Communication Type

Cable model Maximum segment length*2

Option device*3 Model Per GOT channel*4

Per host*5

UDP TCP UDP TCP Ethernet Twisted pair cable*1

100BASE-TX Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 5 or higher 10BASE-T

Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 3 or higher

100m - (Built into GOT) Unlimited 1 Unlimited Unlimited

GT25-J71E71-100

Ethernet (microcomputer)

Communication driver

Host Hub

Connection cable Connection cable

GOT

2 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.2 System Configuration

3

3.3 Device Data Area 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

*1 For the address specification method for each data format, refer to the following. Page 177 Message Formats

*2 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 (GOT2000) Screen Design Manual

*3 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.

Model Virtual device*2 Address specification value Refer to

Name Device range (decimal)

Device type

Format 1, 2 Format 3, 4 Format 5 Format 6 to 9

D 0 to 4095 Word 0 to 4095 8000 to 9FFFH 0000 to 0FFFH D0 to D4095 Page 164 D devices

R 0 to 4095 Word 4096 to 8191 0000 to 1FFFH 1000 to 1FFFH R0 to R4095 Page 168 R devices

L 0 to 2047 Bit 8192 to 8319 A000 to A0FFH 2000 to 207FH L0 to L2047 Page 169 L devices

M 0 to 2047 Bit 8320 to 8447 2000 to 20FFH 2080 to 20FFH M0 to M2047 Page 170 M devices

SD 0 to 15 Word 8448 to 8463 2100 to 211FH (3000 to 300DH)*3

2100 to 210FH SD0 to SD15 Page 171 SD devices

SM 0 to 63 Bit 8464 to 8467 2200 to 2207H 2110 to 2113H SM0 to SM63 Page 175 SM devices

D 0 to 4095 Word 0000 to 0FFFH D0 to D4095 Page 164 D devices

R 0 to 4095 Word 1000 to 1FFFH R0 to R4095 Page 168 R devices

L 0 to 2047 Bit 2000 to 207FH L0 to L2047 Page 169 L devices

M 0 to 2047 Bit 2080 to 20FFH M0 to M2047 Page 170 M devices

SD 0 to 15 Word 2100 to 210FH SD0 to SD15 Page 171 SD devices

SM 0 to 63 Bit 2110 to 2113H SM0 to SM63 Page 175 SM devices

Formats 1, 2 : GOT-A900 Series microcomputer connection Formats 3, 4 : GOT-F900 series microcomputer connection Formats 5 : SCHNEIDER EJH's memory link method Formats 6, 7 : 4E frame Formats 8, 9 : QnA compatible 3E frame

GOT2000 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

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.3 Device Data Area 163

16

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.

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

D3 Communication error status Stores the communication error details of GOT.

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.

System

D4 Clock data (year)

D5 Clock data (month)

D6 Clock data (day)

b15 b0 b3

Unused

b4

SIO framing error

b5

SIO parity error SIO overrun error

b6b7

Communication timeout error Unused

b8

0: Normal 1: Error

b15 b0

Lower 2 digits of calendar year stored as 2-digit BCD

b7

Unused

b8

b15 b0

Data of months 01 to 12 stored as 2-digit BCD

b7

Unused

b8

b15 b0

Data of days 01 to 31 stored as 2-digit BCD

b7

Unused

b8

4 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.3 Device Data Area

3

D7 Clock data (hour) System

D8 Clock data (minute)

D9 Clock data (second)

D10 Clock data (day of the week)

D11, D12 Unused

Address Description Set side

b15 b0

Data of hours 00 to 23 stored as 2-digit BCD

b7

Unused

b8

b15 b0

Data of minutes 00 to 59 stored as 2-digit BCD

b7

Unused

b8

b15 b0

Data of seconds 00 to 59 stored as 2-digit BCD

b7

Unused

b8

b15 b0

Day-of-week data stored as 2-digit BCD

b7

Unused

b8

00: Sunday 01: Monday 02: Tuesday 03: Wednesday 04: Thursday 05: Friday 06: Saturday

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.3 Device Data Area 165

16

*1 After writing data, the interrupt data is output within a period of 1 to 10 ms. *2 When data are written to D13 and D14 from the host side, interrupt output is not performed. *3 When 32-bit data are written to D13 and D14, the values are output to the host side regardless of the setting for [32bit Storage] in the

communication detail settings. Example) When outputting 0x12345678 with unsigned 32-bit binary data

D13 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

Set the data amount (number of bytes) to execute an interrupt output for [Interrupt Data Byte] in the communication detail settings. Page 231 Setting communication interface (Controller Setting) Output value when [1] is set to [Interrupt Data Byte] in the communication detail settings.

Output value when [2] is set to [Interrupt Data Byte] in the communication detail settings.

Output value when [4] is set to [Interrupt Data Byte] in the communication detail settings.*3

(1) When [32bit Storage] in the communication detail settings is set to [LH Order]

(2) When [32bit Storage] in the communication detail settings is set to [HL Order]

User

D14

D15 to 19 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

D2036 to 4095 User area User

Address Description Set side

D13

Lower 8 bits

1 byte

D13

Upper 8 bits Lower 8 bits

2 bytes

Upper 8 bits

D14 D13

Upper 8 bitsLower 8 bits Lower 8 bits

4 bytes

Upper 8 bits

D13 D14

Upper 8 bitsLower 8 bits Lower 8 bits

4 bytes

Upper 8 bits

D14 D13

Upper 8 bitsLower 8 bits Lower 8 bits

4 bytes

0x12 0x34 0x56 0x78

LH Order

HL Order

Upper 8 bits

D13

Upper 8 bitsLower 8 bits Lower 8 bits

4 bytes

0x56 0x78 0x12 0x34

Upper 8 bits

D13 D14

Upper 8 bitsLower 8 bits Lower 8 bits

4 bytes

0x12 0x34 0x56 0x78

Upper 8 bits

D13

Upper 8 bitsLower 8 bits Lower 8 bits

4 bytes

0x12 0x34 0x56 0x78

Interrupt output

Interrupt output

D14

D14

6 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.3 Device Data Area

3

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). Interrupt output (D13, D14) To disable the interrupt output, turn on SM52 (interrupt code output disable flag). Page 175 SM devices To execute the interrupt output in format 1, 2, 11, 14, or 15, set the data length to 8 bits in the communication detail settings. When "7 bits" is set, the MSB (8th bit) is ignored. (Example: FFH 7FH) Page 231 Setting communication interface (Controller Setting)

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.

*1 For the address specification method for each data format, refer to the following. Page 177 Message Formats

Model Address Address specification value

Format 1, 2 Format 3, 4 Format 5 Format 6 to 9 D0 0 8000H 0000H D0

8001H

D1 1 8002H 0001H D1

8003H

: : : : :

D4095 4095 9FFEH 0FFFH D4095

9FFFH

D0 0000H D0

D1 0001H D1

: : :

D4095 0FFFH D4095

Formats 1, 2 : GOT-A900 Series microcomputer connection Formats 3, 4 : GOT-F900 series microcomputer connection Formats 5 : SCHNEIDER EJH's memory link method Formats 6, 7 : 4E frame Formats 8, 9 : QnA compatible 3E frame

Upper 8 bits

8000H

Lower 8 bits

8001H

Upper 8 bits

8002H

Lower 8 bits

8003H

Upper 8 bits

9FFEH

Lower 8 bits

9FFFH

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.3 Device Data Area 167

16

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

*1 For the address specification method for each data format, refer to the following. Page 177 Message Formats

Model Address Address specification value

Format 1, 2 Format 3, 4 Format 5 Format 6 to 9 R0 4096 0000H 1000H R0

0001H

R1 4097 0002H 1001H R1

0003H

: : : : :

R4095 8191 1FFEH 1FFFH R4095

1FFFH

R0 1000H R0

R1 1001H R1

: : :

R4095 1FFFH R4095

Formats 1, 2 : GOT-A900 Series microcomputer connection Formats 3, 4 : GOT-F900 series microcomputer connection Formats 5 : SCHNEIDER EJH's memory link method Formats 6, 7 : 4E frame Formats 8, 9 : QnA compatible 3E frame

Upper 8 bits

0000H

Lower 8 bits

0001H

Upper 8 bits

0002H

Lower 8 bits

0003H

Upper 8 bits

1FFEH

Lower 8 bits

1FFFH

8 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.3 Device Data Area

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

*1 For the address specification method for each data format, refer to the following. Page 177 Message Formats

*2 For reading or writing data in word units, specify the addresses in 16-point units. (Example: L0, L16, L32, and others)

Model Address Address specification value

b7 b6 b5 b4 b3 b2 b1 b0 Format 1, 2

Format 3, 4 Format 5

Format 6 to 9When

GS580.b8, GS581.b8, GS582.b8, or GS583.b8 is ON

When GS580.b8, GS581.b8, GS582.b8, or GS583.b8 is OFF

L7 L6 L5 L4 L3 L2 L1 L0 8192 A000H A001H 2000H Same as address column on left*2

L15 L14 L13 L12 L11 L10 L9 L8 A001H A000H

L23 L22 L21 L20 L19 L18 L17 L16 8193 A002H A003H 2001H

L31 L30 L29 L28 L27 L26 L25 L24 A003H A002H

: : : : :

L2039 L2038 L2037 L2036 L2035 L2034 L2033 L2032 8319 A0FEH A0FFH 207FH

L2047 L2046 L2045 L2044 L2043 L2042 L2041 L2040 A0FFH A0FEH

L7 L6 L5 L4 L3 L2 L1 L0 2000H Same as address column on left*2

L15 L14 L13 L12 L11 L10 L9 L8

L23 L22 L21 L20 L19 L18 L17 L16 2001H

L31 L30 L29 L28 L27 L26 L25 L24

: :

L2039 L2038 L2037 L2036 L2035 L2034 L2033 L2032 207FH

L2047 L2046 L2045 L2044 L2043 L2042 L2041 L2040

Formats 1, 2 : GOT-A900 Series microcomputer connection Formats 3, 4 : GOT-F900 series microcomputer connection Formats 5 : SCHNEIDER EJH's memory link method Formats 6, 7 : 4E frame Formats 8, 9 : QnA compatible 3E frame

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.3 Device Data Area 169

17

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

*1 For the address specification method for each data format, refer to the following. Page 177 Message Formats

*2 For reading or writing data in word units, specify the addresses in 16-point units. (Example: M0, M16, M32, and others)

Model Address Address specification value

b7 b6 b5 b4 b3 b2 b1 b0 Format 1, 2

Format 3, 4 Format 5

Format 6 to 9When

GS580.b8, GS581.b8, GS582.b8, or GS583.b8 is ON

When GS580.b8, GS581.b8, GS582.b8, or GS583.b8 is OFF

M7 M6 M5 M4 M3 M2 M1 M0 8320 2000H 2001H 2080H Same as address column on left*2

M15 M14 M13 M12 M11 M10 M9 M8 2001H 2000H

M23 M22 M21 M20 M19 M18 M17 M16 8321 2002H 2003H 2081H

M31 M30 M29 M28 M27 M26 M25 M24 2003H 2002H

: : : : :

M2039 M2038 M2037 M2036 M2035 M2034 M2033 M2032 8447 20FEH 20FFH 20FFH

M2047 M2046 M2045 M2044 M2043 M2042 M2041 M2040 20FFH 20FEH

M7 M6 M5 M4 M3 M2 M1 M0 2080H Same as address column on left*2

M15 M14 M13 M12 M11 M10 M9 M8

M23 M22 M21 M20 M19 M18 M17 M16 2081H

M31 M30 M29 M28 M27 M26 M25 M24

: :

M2039 M2038 M2037 M2036 M2035 M2034 M2033 M2032 20FFH

M2047 M2046 M2045 M2044 M2043 M2042 M2041 M2040

Formats 1, 2 : GOT-A900 Series microcomputer connection Formats 3, 4 : GOT-F900 series microcomputer connection Formats 5 : SCHNEIDER EJH's memory link method Formats 6, 7 : 4E frame Formats 8, 9 : QnA compatible 3E frame

0 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.3 Device Data Area

3

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).

*1 For details and corrective actions for the errors (error codes) that are stored into SD2, refer to the following: Page 172 Details and actions for errors (error codes) stored into SD2

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).

Address Description Set side SD0 SD1

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 [32bit Storage] in the communication detail settings is set to [LH Order] The lower and upper bits are stored in SD0 and SD1 respectively.

(2) When [32bit Storage] in the communication detail settings is set to [HL Order] The upper and lower bits are stored in SD0 and SD1 respectively.

System

SD2*1 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

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.

SD8 Clock data (year) The last two digits of four-digit year data are stored.

SD9 Clock data (day of the week) Day-of-the-week data is stored. 0: Sunday 1: Monday 2: Tuesday 3: Wednesday 4: Thursday 5: Friday 6: Saturday

SD10 to 15 Unused

SD0SD1

Lower wordUpper word

SD1SD0

Lower wordUpper word

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.3 Device Data Area 171

17

Details and actions for errors (error codes) stored into SD2 Error code Description Action 0 No error

1, 101 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.

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.

Review the contents of the message to transmit. Check the commands in the message. Page 178 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.

6, 107 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.

2 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.3 Device Data Area

3

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.

Model Address Address specification value

Format 1, 2 Format 3, 4*2 Format 5 Format 6 to 9 SD0 8448 2100H 2100H SD0

2101H

SD1 8449 2102H 2101H SD1

2103H

SD2 8450 2104H 2102H SD2

2105H

SD3 8451 2106H (3000H)

2103H SD3

2107H (3001H)

SD4 8452 2108H (3002H)

2104H SD4

2109H (3003H)

SD5 8453 210AH (3004H)

2105H SD5

210BH (3005H)

SD6 8454 210CH (3006H)

2106H SD6

210DH (3007H)

SD7 8455 210EH (3008H)

2107H SD7

210FH (3009H)

SD8 8456 2110H (300AH)

2108H SD8

2111H (300BH)

SD9 8457 2112H (300CH)

2109H SD9

2113H (300DH)

SD0 2100H SD0

SD1 2101H SD1

SD2 2102H SD2

SD3 2103H SD3

SD4 2104H SD4

SD5 2105H SD5

SD6 2106H SD6

SD7 2107H SD7

SD8 2108H SD8

SD9 2109H SD9

Upper 8 bits

2100H

Lower 8 bits

2101H

Upper 8 bits

2102H

Lower 8 bits

2103H

Upper 8 bits

2104H

Lower 8 bits

2105H

Upper 8 bits

2106H(3000H)

Lower 8 bits

2107H(3001H)

Upper 8 bits

2108H(3002H)

Lower 8 bits

2109H(3003H)

Upper 8 bits

210AH(3004H)

Lower 8 bits

210BH(3005H)

Upper 8 bits

210CH(3006H)

Lower 8 bits

210DH(3007H)

Upper 8 bits

210EH(3008H)

Lower 8 bits

210FH(3009H)

Upper 8 bits

2110H(300AH)

Lower 8 bits

2111H(300BH)

Upper 8 bits

2112H(300CH)

Lower 8 bits

2113H(300DH)

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.3 Device Data Area 173

17

*1 For the address specification method for each data format, refer to the following. Page 177 Message Formats

*2 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.

Formats 1, 2 : GOT-A900 Series microcomputer connection Formats 3, 4 : GOT-F900 series microcomputer connection Formats 5 : SCHNEIDER EJH's memory link method Formats 6, 7 : 4E frame Formats 8, 9 : QnA compatible 3E frame

4 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.3 Device Data Area

3

SM devices The SM devices are bit devices into which interrupt outputs and clock data that turn ON or OFF in 1-second cycles are stored.

List of SM devices The following shows the SM devices (virtual devices inside the GOT).

*1 After the ON or OFF state is changed, the interrupt data is output within a period of 1 to 10 ms. *2 When the ON or OFF state of SM0 to 49 is changed from the host side, interrupt output is not performed.

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). Interrupt outputs (SM0 to 49) To disable the interrupt output, turn on SM52 (interrupt code output disable flag). Page 175 SM devices To execute the interrupt output in format 1, 2, 11, 14, or 15, set the data length to 8 bits in the communication detail settings. When "7 bits" is set, the MSB (8th bit) is ignored. (Example: FFH 7FH) Page 231 Setting communication interface (Controller Setting)

Address Description Set side SM0 to 49 Interrupt output

When the ON or 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

Set the data amount (number of bytes) to execute an interrupt output for [Interrupt Data Byte] in the communication detail settings. Page 231 Setting communication interface (Controller Setting)

User

SM50 1-second cycle clock Turns ON and OFF in 1-second cycles.

System

SM51 2-second cycle clock Turns ON and OFF in 2-second cycles.

SM52 Interrupt code output disable flag Enables or disables the output of the interrupt code and special interrupt code. OFF: Output enabled, ON: Output disabled When the output is set to be disabled, no interrupt data are output to the host. (Relevant devices: D13, D14, SM0 to 49)

User

SM53 to 63 Unused

Address Event type

SM0 Changed from OFF to ON

Changed from ON to OFF

Changed from OFF to ON

Changed from ON to OFF

Changed from OFF to ON

Changed from ON to OFF

Changed from OFF to ON

Changed from ON to OFF

Changed from OFF to ON

Changed from ON to OFF

Interrupt code

SM1

SM2

50H

51H

52H

53H

54H

55H

SM48 B0H

B1H

SM49 B2H

B3H

0.5 0.5

1 1

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.3 Device Data Area 175

17

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.

*1 For the address specification method for each data format, refer to the following. Page 177 Message Formats

*2 In formats 6, 7, values are specified within a range of SM0 to 52. *3 For reading or writing data in word units, specify the addresses in 16-point units. (Example: SM0, SM16, SM32, and others)

Model Address Address specification value

b7 b6 b5 b4 b3 b2 b1 b0 Format 1, 2

Format 3, 4 Format 5

Format 6 to 9When

GS580.b8, GS581.b8, GS582.b8, or GS583.b8 is ON

When GS580.b8, GS581.b8, GS582.b8, or GS583.b8 is OFF

SM7 SM6 SM5 SM4 SM3 SM2 SM1 SM0 8464 2200H 2201H 2110H *2*3

SM15 SM14 SM13 SM12 SM11 SM10 SM9 SM8 2201H 2200H

SM23 SM22 SM21 SM20 SM19 SM18 SM17 SM16 8465 2202H 2203H 2111H

SM31 SM30 SM29 SM28 SM27 SM26 SM25 SM24 2203H 2202H

SM39 SM38 SM37 SM36 SM35 SM34 SM33 SM32 8466 2204H 2205H 2112H

SM47 SM46 SM45 SM44 SM43 SM42 SM41 SM40 2205H 2204H

Unused SM52 SM51 SM50 SM49 SM48 8467 2206H 2207H 2113H

Unused

SM7 SM6 SM5 SM4 SM3 SM2 SM1 SM0 2201H 2110H *2*3

SM15 SM14 SM13 SM12 SM11 SM10 SM9 SM8 2200H

SM23 SM22 SM21 SM20 SM19 SM18 SM17 SM16 2203H 2111H

SM31 SM30 SM29 SM28 SM27 SM26 SM25 SM24 2202H

SM39 SM38 SM37 SM36 SM35 SM34 SM33 SM32 2205H 2112H

SM47 SM46 SM45 SM44 SM43 SM42 SM41 SM40 2204H

Unused SM52 SM51 SM50 SM49 SM48 2207H 2113H

Unused

Formats 1, 2 : GOT-A900 Series microcomputer connection Formats 3, 4 : GOT-F900 series microcomputer connection Formats 5 : SCHNEIDER EJH's memory link method Formats 6, 7 : 4E frame Formats 8, 9 : QnA compatible 3E frame

6 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.3 Device Data Area

3

3.4 Message Formats This section describes the format of messages that can be used in the microcomputer connection (Ethernet).

Data format type Set the data format in the communication detail settings in GT Designer3. For details of the data format setting method, refer to the following. Page 231 Setting communication interface (Controller Setting)

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.

Formats 3, 4 (GOT-F900 series microcomputer connection) This is the compatible message format with when a microcomputer connection is established with the GOT-F900 Series.

Format 5 (SCHNEIDER EJH's memory link method) This is the message format compatible with the protocol of the SCHNEIDER EJH's memory link method.

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.

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 Refer to 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.

Page 182 Formats 1, 2

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.

Type Name Description Refer to 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.

Page 194 Formats 3, 4

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.

Type Name Description Refer to Format 5 SCHNEIDER EJH's memory link

method This is the basic format of the SCHNEIDER EJH's memory link method.

Page 208 Format 5

Type Name Description Refer to Format 6 4E frame (ASCII) This is the basic format of the MC protocols. The data

format is ASCII. Page 212 Formats 6, 7

Format 7 4E frame (Binary) This is the basic format of the MC protocols. The data format is Binary.

Type Name Description Refer to Format 8 QnA compatible 3E frame (ASCII) This is the basic format of the MC protocols. The data

format is ASCII. Page 222 Formats 8, 9

Format 9 QnA compatible 3E frame (Binary) This is the basic format of the MC protocols. The data format is Binary.

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 177

17

List of commands The following shows the list of commands available in each data format. Specify the number of devices within each device range in a request message. If the specified number of devices exceeds the device range, the device value cannot be written or read by a command. For the device range, refer to the following. Page 163 Device Data Area Interrupt output is available in all formats only when [Protocol] is set to [TCP/IP] in the communication detail settings.

List of commands for format 1 (GOT-A900 series microcomputer connection (ASCII))

*1 Mixed specification of bit devices and word devices is also possible.

List of commands for format 2 (GOT-A900 series microcomputer connection (Binary))

*1 Mixed specification of bit devices and word devices is also possible.

Command Command name Description Max. number of points processed

Symbol ASCII code RD 52H 44H Batch read in word units Reads bit devices in 16-point units. 99 words (1584 points)

Reads word devices in 1-point units. 99 points

WD 57H 44H Batch write in word units Writes to bit devices in 16-point units. 99 words (1584 points)

Writes to word devices in 1-point units. 99 points

RR 52H 52H Random read in word units *1 Reads multiple different bit devices in 16- point units.

256 words (4096 points)

Reads multiple different word devices in 1- point units.

256 points

RW 52H 57H Random write in word units *1 Writes to multiple different word devices in 16-point units.

128 words (2048 points)

Writes to multiple different word devices in 1-point units.

128 points

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.

Command Command name Description Max. number of points processed RD Batch read in word units Reads bit devices in 16-point units. 255 words (4080 points)

Reads word devices in 1-point units. 255 points

WD Batch write in word units Writes to bit devices in 16-point units. 255 words (4080 points)

Writes to word devices in 1-point units. 255 points

RR Random read in word units *1 Reads multiple different bit devices in 16-point units. 512 words (8192 points)

Reads multiple different word devices in 1-point units.

512 points

RW Random write in word units *1 Writes to multiple different word devices in 16-point units.

256 words (4096 points)

Writes to multiple different word devices in 1-point units.

256 points

TR Read clock data Reads the clock data of the GOT.

TS Set clock data Sets the clock data of the GOT.

8 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

List of commands for formats 3, 4 (GOT-F900 series microcomputer connection) Command Command name Description Max. number of points processed

Symbol ASCII code 0 30H Batch read (without station No.) Reads bit devices in byte units. 255 bytes (2040 points)

Reads word devices in byte units. 255 bytes (127 points)

A 41H Batch read (with station No.) Reads bit devices in byte units. 255 bytes (2040 points)

Reads word devices in byte units. 255 bytes (127 points)

1 31H Batch write (without station No.) Writes to bit devices in byte units. 255 bytes (2040 points)

Writes to word devices in byte units. 255 bytes (127 points)

B 42H Batch write (with station No.) Writes to bit devices in byte units. 255 bytes (2040 points)

Writes to word devices in byte units. 255 bytes (127 points)

3 33H Multi-point write in bit units (without station No.)

Writes bit patterns (bit ON or OFF, inversion, direct specification) in 1-point units (8 bits for 1 point) to a specified device.

99 points

D 44H Multi-point write in bit units (with station No.)

4 34H Fill command (without station No.) Writes the same value to a range of specified devices.

E 45H Fill command (with station No.)

5 35H Set clock data (without station No.)

Sets the clock data of the GOT.

F 46H Set clock data (with station No.)

6 36H Read clock data (without station No.)

Reads the clock data of the GOT.

G 47H Read clock data (with station No.)

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 179

18

List of commands for format 5 (SCHNEIDER EJH's memory link method)

List of commands for format 6 (4E frame (ASCII)), format 8 (QnA compatible 3E frame (ASCII))

*1 Mixed specification of bit devices and word devices is also possible. *2 This is a dedicated command of GOT for the microcomputer connection. *3 Specifies the address of bit devices in 16-point units. (Example: M0, M16, M32, and others)

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. 512 words (8192 points)

Reads word devices in 1-point units. 512 points

W 57H Batch write in word units Writes to bit devices in 16-point units. 512 words (8192 points)

Writes to word devices in 1-point units. 512 points

I 49H Interrupt inquiry Issues an interrupt inquiry.

Command Sub- command

Command name Description Max. number of points processed

0401 0001 Batch read in bit units Reads bit devices in 1-point units. 896 points

0401 0000 Batch read in word units Reads bit devices in 16-point units.*3 256 words (4096 points)

Reads word devices in 1-point units. 256 points

1401 0001 Batch write in bit units Writes to bit devices in 1-point units. 896 points

1401 0000 Batch write in word units Writes to bit devices in 16-point units.*3 244 words (3904 points)

Writes to word devices in 1-point units. 244 points

0403 0000 Random read in word units *1 Reads multiple different bit devices in 16- point and 32-point units.*3

128 words (2048 points)

Reads multiple different word devices in 1- point and 2-point units.

128 points

1402 0001 Random write in bit units Writes to multiple different bit devices in 1- point units.

96 points

1402 0000 Random write in word units *1 Writes to multiple different bit devices in 16-point and 32-point units.*3

64 words (1024 points)

Writes to multiple different word devices in 1-point and 2-point units.

64 points

0406 0000 Multiple block batch read Reads multiple blocks. A bit device (16 bits for 1 point) or a word device (1 word for 1 point) is regarded as one block.*3

80 points

1406 0000 Multiple block batch write Writes multiple blocks. A bit device (16 bits for 1 point) or a word device (1 word for 1 point) is regarded as one block.*3

64 points

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.

0 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

List of commands for format 7 (4E frame (Binary)), format 9 (QnA compatible 3E frame (Binary))

*1 Mixed specification of bit devices and word devices is also possible. *2 This is a dedicated command of GOT for the microcomputer connection. *3 Specifies the address of bit devices in 16-point units. (Example: M0, M16, M32, and others)

Command Sub- command

Command name Description Max. number of points processed

0401 0001 Batch read in bit units Reads bit devices in 1-point units. 896 points

0401 0000 Batch read in word units Reads bit devices in 16-point units. *3 512 words (8192 points)

Reads word devices in 1-point units. 512 points

1401 0001 Batch write in bit units Writes to bit devices in 1-point units. 896 points

1401 0000 Batch write in word units Writes to bit devices in 16-point units. *3 496 words (7936 points)

Writes to word devices in 1-point units. 496 points

0403 0000 Random read in word units *1 Reads multiple different bit devices in 16- point and 32-point units. *3

255 words (4080 points)

Reads multiple different word devices in 1- point and 2-point units.

255 points

1402 0001 Random write in bit units Writes to multiple different bit devices in 1- point units.

188 points

1402 0000 Random write in word units *1 Writes to multiple different bit devices in 16-point and 32-point units. *3

128 words (2048 points)

Writes to multiple different word devices in 1-point and 2-point units.

128 points

0406 0000 Multiple block batch read Reads multiple blocks. A bit device (16 bits for 1 point) or a word device (1 word for 1 point) is regarded as one block. *3

160 points

1406 0000 Multiple block batch write Writes multiple blocks. A bit device (16 bits for 1 point) or a word device (1 word for 1 point) is regarded as one block. *3

128 points

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.

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 181

18

Formats 1, 2 The following describes the message formats 1 and 2 (GOT-A900 Series microcomputer connection).

Basic format of data communication

*1 Set the number of interrupt data bytes in the communication detail settings in GT Designer3. For setting the number of interrupt data bytes, refer to the following. Page 231 Setting communication interface (Controller Setting)

*2 Interrupt output can be executed by writing the data to the interrupt output devices (D13 and D14). Page 164 D devices

Item Message format Request message (host GOT)

Response message during normal communication (GOT host)

(1) During processing of read commands

(2) During processing of write commands

Response message during faulty communication (GOT host)

During interrupt output *2

(H) (L)

Command Data

Data

06H

ACK

15H

NAK Error Code

Output value

1/2/4 bytes*1

2 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Details of data items in message format

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.

Control codes

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. Page 178 List of commands

Address Specifies the head No. of the device data to be read or 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. Page 163 Device Data Area

Number of points Specifies the device data points to be read or written. (Setting range: Range of the maximum number of points processed for each command) 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.

Year, month, day, hour, minute, second and day of the week data Specifies the year, month, day, hour, minute, second, and day of the week data to be read or 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. Page 190 Read clock data (TR) command Page 191 Set clock data (TS) command

Data Specifies the data to read from or 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.

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. Page 193 Error code list

Symbol ASCII code Description 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) 3.4 Message Formats 183

18

Message Formats Batch read in word units (RD) command 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 Message format Request message (host GOT)

(format 1: GOT-A900 Series microcomputer connection (ASCII))

(format 2: GOT-A900 Series microcomputer connection (Binary))

Response message during normal communication (GOT host)

(format 1: GOT-A900 Series microcomputer connection (ASCII))

(format 2: GOT-A900 Series microcomputer connection (Binary))

Response message during faulty communication (GOT host)

D100

D101

0102H

0304H

(H) (L)

Command

R D 52H 44H

(H) (L)

Address

0 1 30H 31H

0 30H

0 30H

(H) (L)

Number of points

0 2 30H 32H

Command

R D

Address

00H 64H

Number of points

02H

(H) (L)

0 1 30H 31H

0 30H

2 32H

(H) (L)

0 3 30H 33H

0 30H

4 34H

Data 1 (D100) Data 2 (D101)

01H 02H 03H 04H

Data 1 (D100)

Data 2 (D101)

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

4 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

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 Message format Request message (host GOT)

(format 1: GOT-A900 Series microcomputer connection (ASCII))

(format 2: GOT-A900 Series microcomputer connection (Binary))

Response message during normal communication (GOT host)

(format 1: GOT-A900 Series microcomputer connection (ASCII))

(format 2: GOT-A900 Series microcomputer connection (Binary))

Response message during faulty communication (GOT host)

M15 to 0

M31 to 6

0001H

8000H

(H) (L)

Command

R D 52H 44H

(H) (L)

Address

8 3 38H 33H

2 32H

0 30H

(H) (L)

Number of points

0 2 30H 32H

Command

R D

Address

83H 20H

Number of points

02H

(H) (L)

Data 1 (M15 to 0)

0 30H

0 30H

1 31H

0 30H

(H) (L)

8 38H

0 30H

0 30H

0 30H

M 1 6

M 1 7

M 1 8

M 1 9

M 2 0

M 2 1

M 2 2

M 2 3

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

00000000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

10000000 00000001 00000000

Data 2 (M31 to 16)

M 1 6

M 1 7

M 1 8

M 1 9

M 2 0

M 2 1

M 2 2

M 2 3

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

00000000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

10000000 00000001 00000000

00H 01H 80H 00H

Data 1 (M15 to 0)

Data 2 (M31 to 16)

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 185

18

Batch write in word units (WD) command When writing to a word device The following shows as example of writing "0064H"and "0065H"to virtual devices D100 and D101.

Item Message format Request message (host GOT)

(format 1: GOT-A900 Series microcomputer connection (ASCII))

(format 2: GOT-A900 Series microcomputer connection (Binary))

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

D100

D101

0000H

0000H

D100

D101

0064H

0065H

Before execution After execution

(H) (L)

Command

W D 57H 44H

(H) (L)

Address

0 1 30H 31H

0 30H

0 30H

(H) (L)

Number of points

0 2 30H 32H

(H) (L)

Data 1(D100)

0 0 30H 30H

6 36H

4 34H

(H) (L)

Data 2 (D101)

0 0 30H 30H

6 36H

5 35H

Command

W D

Address

00H 64H

Number of points

02H

Data1 (D100)

00H 64H

Data 2 (D101)

00H 65H

06H

ACK

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

6 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

When writing to a bit device The following shows an example of writing "1"s to virtual devices M0 and M31.

Item Message format Request message (host GOT)

(format 1: GOT-A900 Series microcomputer connection (ASCII))

(format 2: GOT-A900 Series microcomputer connection (Binary))

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

M15 to 0 0000H

0000H

0001H

8000H

Before execution After execution

M31 to 16

M15 to 0

M31 to 16

(H) (L)

Data 1 (M15 to 0)

0 30H

0 30H

1 31H

0 30H

(H) (L)

Data 2 (M31 to 16)

8 38H

0 30H

0 30H

0 30H

M 1 6

M 1 7

M 1 8

M 1 9

M 2 0

M 2 1

M 2 2

M 2 3

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

00000000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

10000000 00000001 00000000

(H) (L)

W D 57H 44H

Command

(H) (L)

Address

8 38H

0 30H

2 32H

3 33H

(H) (L)

0 2 30H 32H

Number of points

M 1 6

M 1 7

M 1 8

M 1 9

M 2 0

M 2 1

M 2 2

M 2 3

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

00000000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

10000000 00000001 00000000

Command

W D

Address

20H 80H

Number of points

02H

Data 1 (M15 to 0)

00H 01H

Data 2 (M31 to 16)

80H 00H

06H

ACK

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 187

18

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.)

Item Message format Request message (host GOT)

(format 1: GOT-A900 Series microcomputer connection (ASCII))

(format 2: GOT-A900 Series microcomputer connection (Binary))

Response message during normal communication (GOT host)

(format 1: GOT-A900 Series microcomputer connection (ASCII))

(format 2: GOT-A900 Series microcomputer connection (Binary))

Response message during faulty communication (GOT host)

D100 0064H

0001HM15 to 0

(H) (L)

Command

R R 52H 52H

(H) (L)

Address 1

0 1 30H 31H

0 30H

0 30H

(H) (L)

Address 2

8 3 38H 33H

2 32H

0 30H

Command

R R

Address 1

00H 64H

Address 2

20H 80H

(H) (L)

Data 1 (D100)

0 30H

6 36H

4 34H

0 30H

00000000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

10000000

(H) (L)

Data 2 (M15 to 0)

0 30H

0 30H

1 31H

0 30H

Data 1 (D100)

00H 64H

00000000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

10000000

Data 2 (M15 to 0)

00H 01H

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

8 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Random write in word units (RW) command The following shows an example of writing "0064H" and "1" to virtual devices D100 and M0, respectively.

Item Message format Request message (host GOT)

(format 1: GOT-A900 Series microcomputer connection (ASCII))

(format 2: GOT-A900 Series microcomputer connection (Binary))

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

M15 to 0

0000H

Before execution After execution

D100

0000H M15 to 0

0064HD100

0001H

(H) (L)

Address 2

8 38H

2 32H

0 30H

3 33H

00000000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

10000000

(H) (L)

Data 2 (M15 to 0)

0 30H

0 30H

1 31H

0 30H

(H) (L)

R W 52H 57H

Command

(H) (L)

Address 1

0 30H

1 31H

0 30H

0 30H

(H) (L)

Data 1 (D100)

0 30H

6 36H

4 34H

0 30H

Address 2

20H 80H

00000000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

10000000

Data 2 (M15 to 0)

00H 01HR W

Command Address 1

00H 64H

Data 1 (D100)

00H 00H

06H

ACK

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 189

19

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".)

Item Message format Request message (host GOT)

Response message during normal communication (GOT host)

(format 1: GOT-A900 Series microcomputer connection (ASCII))

(format 2: GOT-A900 Series microcomputer connection (Binary))

Response message during faulty communication (GOT host)

Time display

2009/10/01 18:46:49 THU

(H) (L)

Command

T R 54H 52H

(H) (L)

Year data

0 9 30H 39H

(H) (L)

Month data

1 0 31H 30H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 4 30H 34H

Year data

09H

Month data

0AH

Day data

01H

Hour data

12H

Minute data

2EH

Second data

31H

Day-of- week data

04H

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

0 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

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".)

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 corrected day of the week will be set. 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 set.

Item Message format Request message (host GOT)

(format 1: GOT-A900 Series microcomputer connection (ASCII))

(format 2: GOT-A900 Series microcomputer connection (Binary))

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

Time display

2009/10/01 18:46:49 THU

After execution

(H) (L)

Year data

0 9 30H 39H

(H) (L)

Month data

1 0 31H 30H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 4 30H 34H

(H) (L)

Command

T S 54H 53H

Command

T S

Year data

09H

Month data

0AH

Day data

01H

Hour data

12H

Minute data

2EH

Second data

31H

Day-of- week data

04H

06H

ACK

The above is a case where the sum check error (06H) has occurred.

15H

NAK

06H

Error code

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 191

19

In the case of interrupt outputs Write data to the interrupt output devices (D13 and D14) to output the data to the host. (Assuming that "3139H" is written to D13 and "AA55H" to D14.)

Interrupt output To disable the interrupt output, turn on SM52 (interrupt code output disable flag). Page 175 SM devices

Item Message format Interrupt output (GOT host)

(1) When [Interrupt Data Byte] in the communication detail settings is set to [1]

(2) When [Interrupt Data Byte] in the communication detail settings is set to [2]

(3) When [Interrupt Data Byte] in the communication detail settings is set to [4] When [32bit Storage] in the communication detail settings is set to [LH Order]

When [32bit Storage] in the communication detail settings is set to [HL Order]

Interrupt

Interrupt output

Example) When [Interrupt Data Byte] in the communication detail settings is set to 2 byte as shown in (2) of the table below

31H

Output value 1

3139HD13

39H

Output value 2

39H

Output value 1

31H 39H

Output value 1

Output value 2

AAH

Output value1

55H

Output value2

31H

Output value3

39H

Output value4

31H

Output value1

39H

Output value2

AAH

Output value3

55H

Output value4

2 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

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.

Precautions Storage order for 32-bit data To use the program of the GOT-A900 series by setting 32-bit data to the GOT1000 series, set [HL Order] for [32bit Storage] in the communication detail settings. If [LH Order] is set, higher-order bits and lower-order bits are reversed when 32-bit data is displayed on or written to the GOT.

Error code Description Action 10H Command error

An unsupported command was used. Review the contents of the message to transmit. Check the commands in the message. Page 178 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.)

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 or write device is out of range.

Review the contents of the message to transmit. Check the devices that can be used and the device ranges. Page 163 Device Data Area7EH Exceeded number of points error

The read or write range has exceeded the device range.

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 193

19

Formats 3, 4 The following describes the message formats 3 and 4 (GOT-F900 Series microcomputer connection).

Basic format of data communication

*1 Set the number of interrupt data bytes in the communication detail settings in GT Designer3. For setting the number of interrupt data bytes, refer to the following. Page 231 Setting communication interface (Controller Setting)

*2 Interrupt output can be executed by writing the data to the interrupt output devices (D13 and D14). Page 164 D devices

Item Message format Request message (host GOT)

(1) w/out station No.

(2) w/station No.

Response message during normal communication (GOT host)

(1) During processing of read commands

(2) During processing of write commands

Response message during faulty communication (GOT host)

During interrupt output *2

DataCom- mand

Data

(H) (L)

Station No.Com- mand

Data

06H

ACK

15H

NAK

Output value

1/2/4 bytes*1

4 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Details of data items in message format

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.

Control codes

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. Page 178 List of commands

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. Page 231 Setting communication interface (Controller Setting)

Address Specifies the head No. of the device data to be read or 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. Page 163 Device Data Area

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. Page 201 Multi-point write in bit units (3) command (without station No.), multi-point write in bit units (D) command (with station No.)

Symbol ASCII code Description 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) 3.4 Message Formats 195

19

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. Page 201 Multi-point write in bit units (3) command (without station No.), multi-point write in bit units (D) command (with station No.)

Number of bytes Specifies the number of bytes of the device data to be batch read or 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.

Number of points Specifies the device data points to be written to multi-point in bit units. (Setting range: Range of the maximum number of points processed for each command) 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.

Year, month, day, hour, minute, second and day of the week data Specifies year, month, day, hour, minute, second, and day of the week data to be read or 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. Page 204 Read clock data (6) command (without station No.), read clock data (G) command (with station No.) Page 205 Set clock data (5) command (without station No.), set clock data (F) command (with station No.)

Data Specifies the data to read from or 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.

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 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Message format Batch read (0) command (without station No.), batch read (A) command (with station No.) 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 Message format Request message (host GOT)

(format 3: GOT-F900 Series microcomputer connection (ASCII))

(format 4: GOT-F900 Series microcomputer connection (Binary))

Response message during normal communication (GOT host)

(format 3: GOT-F900 Series microcomputer connection (ASCII))

(format 4: GOT-F900 Series microcomputer connection (Binary))

Response message during faulty communication (GOT host)

R100

R101

3D21H

3604H

(H) (L)

Station No.

1 5 31H 35H

(H) (L)

Address

0 30H

0 30H

8 38H

(H) (L)

Number of bytes

0 4 30H 34H

A 41H

C 43H

Com- mand

Station No.

0FH

Address

C8H

Number of bytes

04HA 00H

Com- mand

(H)

Data 1 (R100 upper)

3 33H

(L)

D 44H

(H)

Data 2 (R100 lower)

2 32H

(L)

1 31H

(H)

Data 3 (R101 upper)

3 33H

(L)

6 36H

(H)

Data 4 (R101 lower)

0 30H

(L)

4 34H

Data 1 (R100 upper)

3DH

Data 2 (R100 lower)

21H

Data 3 (R101 upper)

36H

Data 4 (R101 lower)

04H

15H

NAK

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 197

19

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.)

Item Message format Request message (host GOT)

(format 3: GOT-F900 Series microcomputer connection (ASCII))

(format 4: GOT-F900 Series microcomputer connection (Binary))

Response message during normal communication (GOT host)

(format 3: GOT-F900 Series microcomputer connection (ASCII))

(format 4: GOT-F900 Series microcomputer connection (Binary))

Response message during faulty communication (GOT host)

M15 to 0

M31 to 16

0001H

8000H

(H) (L)

Station No.

1 5 31H 35H

(H) (L)

Address

2 32H

0 30H

(H) (L)

Number of bytes

0 4 30H 34H

A 41H

0 30H

0 30H

Com- mand

Station No.

0FH

Address Number of bytes

04HA 20H 00H

Com- mand

M 1 6

M 1 7

M 1 8

M 1 9

M 2 0

M 2 1

M 2 2

M 2 3

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

00000000 M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

00000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

10000000 00100000000

(H) (L)

Data 1 (M7 to 0)

0 30H

1 31H

(H) (L)

Data 2 (M15 to 8)

0 30H

0 30H

(H) (L)

Data 3 (M23 to 16)

0 30H

0 30H

(H) (L)

Data 4 (M31 to 24)

8 38H

0 30H

M 1 6

M 1 7

M 1 8

M 1 9

M 2 0

M 2 1

M 2 2

M 2 3

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

00000000 M 8

M 9

M 1 0

M 1 2

M 1 3

M 1 4

M 1 5

M 1 1

00000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

10000000 00100000000

Data 1 (M7 to 0)

01H

Data 2 (M15 to 8)

00H

Data 3 (M23 to 16)

00H

Data 4 (M31 to 24)

80H

15H

NAK

8 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Batch write (1) command (without station No.), batch write (B) command (with station No.) 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.

Item Message format Request message (host GOT)

(format 3: GOT-F900 Series microcomputer connection (ASCII))

(format 4: GOT-F900 Series microcomputer connection (Binary))

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

R100

R101

0000H

0000H

R100

R101

0064H

0065H

Before execution After execution

(H) (L)

Data 1 (R100 upper)

3 D 33H 44H

(H) (L)

Data 2 (R100 lower)

2 1 32H 31H

(H) (L)

Data 3 (R101 upper)

3 6 33H 36H

(H) (L)

Data 4 (R101 lower)

0 4 30H 34H

*1

(H) (L)

Station No.

1 5 31H 35H

(H) (L)

Address

0 30H

0 30H

8 38H

(H) (L)

Number of bytes

0 4 30H 34H

B 42H

C 43H

Following*1

Com- mand

Data 1 (R100 upper)

3DH 21H

Data 2 (R100 lower)

Data 3 (R101 upper)

36H 04H

Data 4 (R101 lower)

*2

Station No.

0FH

Address

C8H

Number of bytes

04HB 00H

Following*2

Com- mand

06H

ACK

15H

NAK

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 199

20

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.

Item Message format Request message (host GOT)

(format 3: GOT-F900 Series microcomputer connection (ASCII))

(format 4: GOT-F900 Series microcomputer connection (Binary))

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

M15 to 0 0000H

0000H

Before execution After execution

M31 to 16

M15 to 0 0001H

8000HM31 to 16

(H) (L)

Data 1 (M7 to 0)

0 1 30H 31H

(H) (L)

Data 2 (M15 to 8)

0 0 30H 30H

(H) (L)

Data 3 (M23 to 16)

0 0 30H 30H

(H) (L)

Data 4 (M31 to 24)

8 0 38H 30H

*1

(H) (L)

Station No.

1 5 31H 35H

(H) (L)

Address

2 32H

0 30H

0 30H

(H) (L)

Number of bytes

0 4 30H 34H

B 42H

0 30H

Following*1

Com- mand

M 1 6

M 1 7

M 1 8

M 1 9

M 2 0

M 2 1

M 2 2

M 2 3

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

00000000 M 8

M 9

M 1 0

M 1 2

M 1

M 1 4

M 1 5

M 1 1

00000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

10000000 00100000000

3

Data 1 (M7 to 0)

01H 00H

Data 2 (M15 to 8)

Data 3 (M23 to 16)

00H 80H

Data 4 (M31 to 24)

*2

Station No.

0FH

Address

00H

Number of bytes

04HB 20H

Following*2

Com- mand

M 1 6

M 1 7

M 1 8

M 1 9

M 2 0

M 2 1

M 2 2

M 2 3

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

00000000 M 8

M 9

M 1 0

M 1 2

M 1

M 1 4

M 1 5

M 1 1

00000 M 0

M 1

M 2

M 3

M 4

M 5

M 6

M 7

10000000 00100000000

3

06H

ACK

15H

NAK

0 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Multi-point write in bit units (3) command (without station No.), multi-point write in bit units (D) command (with 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 Request message (host GOT)

(format 3: GOT-F900 Series microcomputer connection (ASCII))

(format 4: GOT-F900 Series microcomputer connection (Binary))

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

(H) (L)

Address1 Address2

2 32H

0 30H

(H) (L)

Bit pattern1

8 38H

0 30H

*2 Write specification 1

1 31H

0 30H

3 33H

(H) (L)

2 32H

0 30H

(H) (L)

Bit pattern2

4 34H

0 30H

Write specification 2

0 30H

F 46

E 45H

*1 *1

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

01010101Source data bit pattern 00000001

01010100Result

(write specification1=1)

M 2 0 3 2

M 2 0 3 3

M 2 0 3 4

M 2 0 3 5

M 2 0 3 6

M 2 0 3 7

M 2 0 3 8

M 2 0 3 9

01010101Source data bit pattern 00000010

01010111Result

(write specification2=0)

(H) (L)

Station No.

3 33H

1 31H

D 44H

Following *2

(H) (L)

Number of points

0 30H

2 32H

Com- mand

Station No.

1FH 02HD

Following *3

Number of points

Com- mand

Address1 Address2

20H 03H

Bit pattern1

80H

*3 Write specification 1

1 20H FEH

Bit pattern2

40H

Write specification 2

0

*1 *1

M 2 4

M 2 5

M 2 6

M 2 7

M 2 8

M 2 9

M 3 0

M 3 1

01010101Source data bit pattern 00000001

01010100Result

(write specification1=1)

M 2 0 3 2

M 2 0 3 3

M 2 0 3 4

M 2 0 3 5

M 2 0 3 6

M 2 0 3 7

M 2 0 3 8

M 2 0 3 9

01010101Source data bit pattern 00000010

01010111Result

(write specification2=0)

06H

ACK

15H

NAK

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 201

20

*1 The write specification specifies how the data of the specified address is changed in the bit pattern.

Write specification Function Description Action example 0 ON specification Bits set to "1" by the bit pattern are turned ON. Original data1010

Bit pattern1100

Result1110

1 OFF specification Bits set to "1" by the bit pattern are turned OFF. Original data1010 Bit pattern1100

Result0010

2 Invert specification Bits set to "1" by the bit pattern are inverted. Original data1010 Bit pattern1100

Result0110

3 Write specification The numerical values to write by the bit pattern are specified directly. Original data1010 Bit pattern1100

Result1100

2 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Fill command (4) (without station No.), fill command (E) (with station No.) The following shows an example of writing "16"s to virtual devices R50 to R100 on the GOT at station No.27.

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. Address specifying crossing over different devices The start address and end address can be specified crossing over different devices.

Item Message format Request message (host GOT)

(format 3: GOT-F900 Series microcomputer connection (ASCII))

(format 4: GOT-F900 Series microcomputer connection (Binary))

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

R100

0000H

Before execution After execution

R50

0000H

0000H

R100

1616HR50

1616H

1616H

(H) (L)

Station No.

2 7 32H 37H

(H) (L)

Write Data

1 6 31H 36H

E 45H

(H) (L)

Start address

0 30H

0 30H

4 34H

6 36H

(H) (L)

End address

0 30H

0 30H

9 39H

C 43H

Com- mand

Station No.

1BH

Write Data

16HE

Start address

64H00H

End address

C9H00H

Com- mand

06H

ACK

15H

NAK

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 203

20

Read clock data (6) command (without station No.), read clock data (G) command (with 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".)

Item Message format Request message (host GOT)

(format 3: GOT-F900 Series microcomputer connection (ASCII))

(format 4: GOT-F900 Series microcomputer connection (Binary))

Response message during normal communication (GOT host)

(format 3: GOT-F900 Series microcomputer connection (ASCII))

(format 4: GOT-F900 Series microcomputer connection (Binary))

Response message during faulty communication (GOT host)

Time display

2009/10/01 18:46:49 THU

(H) (L)

Station No.

2 7 32H 37H

G 47H

Com- mand

Station No.

1BHG

Com- mand

(H) (L)

Month data

1 0 31H 30H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 4 30H 34H

(H) (L)

Year data

0 9 30H 39H

Month data

0AH

Day data

01H

Hour data

12H

Minute data

2EH

Second data

31H

Day-of- week data

04H

Year data

09H

15H

NAK

4 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Set clock data (5) command (without station No.), set clock data (F) command (with 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".)

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 corrected day of the week will be set. 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 set.

Item Message format Request message (host GOT)

(format 3: GOT-F900 Series microcomputer connection (ASCII))

(format 4: GOT-F900 Series microcomputer connection (Binary))

Response message during normal communication (GOT host)

Response message during faulty communication (GOT host)

Time display

2009/10/01 18:46:49 THU

After execution

46H

F

(H) (L)

Station No.

2 7 32H 37H

(H) (L)

Month data

1 0 31H 30H

(H) (L)

Day Data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 4 30H 34H

(H) (L)

Year data

0 9 30H 39H

Com- mand

F

Station No.

1BH

Month data

0AH

Day data

01H

Hour data

12H

Minute data

2EH

Second data

31H

Day-of- week data

04H

Year data

09H

Com- mand

06H

ACK

15H

NAK

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 205

20

In the case of interrupt outputs Write data to the interrupt output devices (D13 and D14) to output the data to the host. (Assuming that "3139H" is written to D13 and "AA55H" to D14.)

Interrupt output To disable the interrupt output, turn on SM52 (interrupt code output disable flag). Page 175 SM devices

Item Message format Interrupt output (GOT host)

(1) When [Interrupt Data Byte] in the communication detail settings is set to [1]

(2) When [Interrupt Data Byte] in the communication detail settings is set to [2]

(3) When [Interrupt Data Byte] in the communication detail settings is set to [4] When [32bit Storage] in the communication detail settings is set to [LH Order]

When [32bit Storage] in the communication detail settings is set to [HL Order]

Interrupt

Interrupt output

Example) When [Interrupt Data Byte] in the communication detail settings is set to 2 byte as shown in (2) of the table below

31H

Output value 1

3139HD13

39H

Output value 2

39H

Output value 1

31H

Output value 1

39H

Output value 2

AAH

Output value 1

55H

Output value 2

31H

Output value 3

39H

Output value 4

31H

Output value 1

39H

Output value 2

AAH

Output value 3

55H

Output value 4

6 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Error code list When faulty, the error code is stored in SD2. For details on error code stored in SD2, the error contents, cause and measures, refer to the following. Page 172 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.

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 207

20

Format 5 The following describes the message format 5 (SCHNEIDER EJH's (former Digital Electronics Corporation) memory link method).

Basic format of data communication This is the same format as the protocol of the SCHNEIDER EJH'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 SCHNEIDER EJH This section describes items whose settings differ from the protocols of the SCHNEIDER EJH's memory link method and dedicated commands for a microcomputer connection of the GOT. Example: Request message for the batch read in word units (R) command in format 5 (SCHNEIDER EJH's memory link method)

Details of data items in message format

Data code during communication Communication is performed in Binary code.

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. Page 178 List of commands

Address Specifies the head No. of the device data to be read or written. The address notated in hexadecimal is converted to a 4-digit Binary code (Hex) and transmitted from the upper digit. For details of the device range that can be accessed, refer to the following. Page 163 Device Data Area

Number of points Specifies the device data points to be read or written. (Setting range: Range of the maximum number of points processed for each command) The address notated in hexadecimal is converted to a 4-digit Binary code (Hex) and transmitted from the upper digit.

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 Binary code (Hex) and transmitted from the upper digit. For details on error code generated in format 5 (SCHNEIDER EJH's memory link method), refer to the following. Page 211 Error code list

When connecting a microcomputer or others that uses the protocol of the SCHNEIDER EJH's memory link method with the GOT To do so, correct the commands to be used and the device ranges to match the specifications of the GOT.

Data length

00H 06H

Address

64H00H

Number of points

00H 02H1BH

ESC

52H

R

Com- mand

00H 00H 00H 00H42H 00H

B

8 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Message Formats The following shows the message format of the dedicated commands for a microcomputer connection of GOT.

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.)

Batch write in word units (WD) command When writing to a word device The following shows as example of writing "0064H"and "0065H"to virtual devices D100 and D101.

Item Message format Request message (host GOT)

Response message during normal communication (GOT host)

Item Message format Request message (host GOT)

Response message during normal communication (GOT host)

D100

D101

0102H

0304H

Data length

00H 06H

Address

64H00H

Number of points

00H 02H1BH

ESC

52H

R

Com- mand

00H 00H 00H 00H42H 00H

B

Data length

00H 06H

Address

02H01H

Number of points

03H 04H1BH

ESC

41H

A

Com- mand

00H 00H 00H 00H42H 00H

b

D100

D101

0000H

0000H

D100

D101

0064H

0065H

Before execution After execution

Data length

00H 0AH

Address

64H00H

Number of points

00H 02H1BH

ESC

57H

W

Com- mand

00H 00H 00H 00H42H 00H

B

Data 1

64H00H

Data 2

00H 65H

Data length

00H 06H 06H

ACK

00H 00H 00H 00H42H 00H

b

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 209

21

In the case of interrupt outputs Write data to the interrupt output devices (D13 and D14) to output the data to the host. (Assuming that "31H" is written to D13.)

Interrupt output To disable the interrupt output, turn on SM52 (interrupt code output disable flag). Page 175 SM devices

Item Message format Interrupt output (GOT host)

When [Interrupt Data Byte] in the communication detail settings is set to [1]

Interrupt

Interrupt output

Example) When [Interrupt Data Byte] in the communication detail settings is set to 1 byte as shown in the table below

31H

Output value 1

31HD13

31H

Output value 1

0 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Error code list In the case of format 5 (SCHNEIDER EJH'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.

Precautions Storage order for 32-bit data To use the program of the SCHNEIDER EJH's memory link method by setting 32-bit data to the GOT1000 series, set [HL Order] for [32bit Storage] in the communication detail settings. If [LH Order] is set, higher-order bits and lower-order bits are reversed when 32-bit data is displayed on or written to the GOT.

Error code Description Action 10H Command error

An unsupported command was used. Review the contents of the message to transmit. Check the commands in the message. Page 178 List of commands12H 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 or write device is out of range.

Review the contents of the message to transmit. Check the data length of the message.(data length of the data

section, etc.)

FBH Exceeded number of points error The read or write range has exceeded the device range.

Review the contents of the message to transmit. Check the devices that can be used and the device ranges. Page 163 Device Data Area

FCH Message format error The format of the received message has error.

Check the settings in the 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 in the communication detail settings. Review the contents of the message to transmit.

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 211

21

Formats 6, 7 The following describes the message formats 6 and 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 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))

(format 7:4E frame (Binary))

(H)

Fixed value

0 30H

0 30H

(H) (L)

PLC No.

0 30H

1 31H

(H) (L)

Network No.

0 30H

1 31H

(H)

Request destination module I/O No.

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

Request destination module station No.

0 30H

0 30H

Following *10 0

30H 30H

(H) (L)(H) (L)

Serial No.

0 30H

0 30H

0 0 30H 30H

(H) (L)(H) (L)

Request type

0 30H

0 30H

5 4 35H 34H

(H) (L)

(H) (L)

Device code

* 2AH

D 44H

(H)

Head Device

1 31H

0 30H

0 30H

(L)

0 30H

0 30H

0 30H

Character A section

(H)

Sub-command

0 30H

0 30H

(L)

0 30H

0 30H

(H)

Device points

0 30H

0 30H

(L)

0 30H

2 32H

(H) (L)

Request data length

0 30H

0 30H

(H) (L)

1 31H

8 38H

(H) (L)

CPU monitoring timer

0 30H

0 30H

(L)

0 30H

0 30H

(H) (H)

Command

0 30H

4 34H

(L)

0 30H

1 31H

*1

1)

1)

Data length target range

Data length target range

00H 00H 00H 00H0CH54H 00H

Request type

Fixed value

00H 00H 00H 00H00H 00H

Serial No.

01H 01H

Data length target range

00H 00H64H 00H02HA8H01H 04H 00H 00H

PLC No.

Network No.

Request destination

module I/O No.

Request destination module

station No.

Device codeHead DeviceSub-

command Device pointsRequest data length

CPU monitoring

timer Command

2 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Details of data items in message format

Data code during communication Communication of format 6 is performed in ASCII code. Communication of the format 7 is performed in Binary code.

The following table shows the contents of the data items.

Data item name Contents

Format 6 Format 7 Request type (Microcomputer side)

Indicates it is a command message.

Command message: ASCII "5400" (Fixed value) Command message: 54H (Upper digit) (Fixed value)

Response type (GOT side) Indicates it is a response message.

Response message: ASCII "D400" (Fixed value) Response message: D4H (Upper digit) (Fixed value)

Serial No. Arbitrary number for recognition of the message appended at the microcomputer side. GOT sends the response message appending this Serial No.

Fixed value Should be ASCII "0000". Should be "0000H".

Network No. Set the same number as the network No. set in the GOT. For setting method of "Communication Detail Settings", refer to the following. Page 231 Setting communication interface (Controller Setting)

Transmit the data converted to a 2-digit ASCII code from the upper digit.

Transmit the data converted to a 2-digit binary code.

PLC No. Set the same number as the PLC No. set in the GOT. For setting method of "Communication Detail Settings", refer to the following. Page 231 Setting communication interface (Controller Setting)

Transmit the data converted to a 2-digit ASCII code from the upper digit.

Transmit the data converted to a 2-digit binary code.

Request destination module I/O No.

Ignore GOT.

Request destination module station No.

Ignore GOT.

Request data length Number of bytes from the start of CPU monitoring timer 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.

Response data length Appended to the response message from the microcomputer side. Number of bytes from the start of end code to the last response data or last error response 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.

CPU monitoring timer Ignore GOT.

Command, Sub-command Specifies the access contents from the microcomputer side to GOT. For details of the commands that can be used, refer to the following. Page 178 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.

Device code Specifies the code by which the device data to be read or written is recognized. For the accessible device range, refer to the following. Page 163 Device Data Area

Transmit the 2-digit ASCII code corresponding to the following device codes.

Transmit the 2-digit binary code corresponding to the following device codes.

D*

R* SD

L*

M* SM

SD

R

L

SM M

D

Device codeDevice name

A8H

AFH A9H

92H

90H 91H

SD

R

L

SM M

D

Device codeDevice name

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 213

21

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.

Head device Specifies the head No. of the device data to be read or written. For details of the device range that can be accessed, refer to the following. Page 163 Device Data Area

Transmit the data notated in decimal converted to a 6-digit ASCII code, from the upper digit.

Transmit the data converted to a 6-digit binary code from the lower two digits.

Device points Specifies the device data points to be read or written. (Setting range: Range of the maximum number of points processed for each command) When setting multiple bit accesses, word accesses or double word accesses, limit the total number of access points to within 64 points. When setting multiple blocks, limit the total number of points of all blocks to within the maximum number of points processed for each command.

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.

Year, month, day, hour, minute, second and day of the week data

Specifies the year, month, day, hour, minute, second, and day of the week data to be read or set to the GOT clock data. Page 215 Read clock data (1901) command Page 218 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.

End code (Microcomputer side)

Appended to the response message from the microcomputer side. If an error occurs at the microcomputer side, the error code is displayed. Page 221 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.

Data item name Contents

Format 6 Format 7

4 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Message format The following shows the message format of the dedicated commands for a microcomputer connection of GOT.

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".)

Item Message format Request message (host GOT)

(format 6:4E frame (ASCII))

(format 7:4E frame (Binary))

Time display

2009/10/01 18:46:49 THU

(L)

Fixed value

0 30H

0 30H

(H) (L)

PLC No.

0 30H

1 31H

(H) (L)

Network No.

0 30H

1 31H

(H)

0 30H

0 30H

(H)

Request data length

0 30H

(L)

0 30H

C 43H

0 30H

(H)

CPU monitoring timer

0 30H

0 30H

(L)

0 30H

0 30H

Following *1

*1

(H)

0 30H

0 30H

(L)

Serial No.

0 30H

0 30H

(H)

0 30H

0 30H

(L)

Request type

0 30H

0 30H

(H)

5 35H

4 34H

Character A section

(H)

Command

9 39H

(L)

0 30H

1 31H

1 31H

(H)

Sub-command

0 30H

0 30H

(L)

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

1)

1)

Request destination module I/O No.

Request destination module station No.

Fixed value

00H

PLC No.

Network No.

06H 00H

Request data length

Following *1

*1

00H 00H

Serial No.

01H00H 01H00H 00H54H 00H

Data length target range

Command

00H 01H 19H00H

Sub- command

00H 00H

Request destination module I/O No.

Request destination module station No.

CPU monitoring timer

Request type

00H

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 215

21

Response message during normal communication (GOT host)

(format 6:4E frame (ASCII))

(format 7:4E frame (Binary))

Item Message format

(L)

Fixed value

0 30H

0 30H

(H) (L)

PLC No.

0 30H

1 31H

(H) (L)

Network No.

0 30H

1 31H

(H)

0 30H

0 30H

(H)

Response data length

0 30H

(L)

1 31H

2 32H

0 30H

(H)

End code

0 30H

0 30H

(L)

0 30H

0 30H

Following *1

*1

(H)

0 30H

0 30H

(L)

Serial No.

0 30H

0 30H

(H)

0 30H

0 30H

(L)

Response type

0 30H

0 30H

(H)

D 44H

4 34H

Character B section

(H) (L)

9 39H

(H) (L)

1 31H

0 30H

0 30H

(H) (L)

0 30H

1 31H

(L)

1 31H

8 38H

(H)

(L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

1)

1)

Request destination module I/O No.

Request destination module station No.

(H) (L)

6 36H

(H) (L)

4 34H

9 39H

4 34H

(H) (L)

0 30H

4 34H

Year data Month data Day data Hour data Minute data Second data

Day-of- week data

Data length target range

End code

00H 00H

*1 Year data

09H 0AH

Month data

01H 12H

Day data

2EH 31H

Hour data

04H

Minute data

Second data

Day-of- week data

Fixed value

00H

PLC No.

Network No.

09H 00H

Response data length

Following *100H 00H

Serial No.

01H 01H00H

Request type

00H 00HD4H 00H

Request destination module I/O No.

00H

Request destination module station No.

6 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Response message during faulty communication (GOT host)

(format 6:4E frame (ASCII))

(format 7:4E frame (Binary))

Item Message format

(L)

Fixed value

0 30H

0 30H

(H) (L)

PLC No.

0 30H

1 31H

(H) (L)

Network No.

0 30H

1 31H

(H)

0 30H

0 30H

(H)

Response data length

0 30H

(L)

1 31H

6 36H

0 30H

(H)

End code

0 30H

0 30H

(L)

5 35H

6 36H

Following *1

*1

(H)

0 30H

0 30H

(L)

Serial No.

0 30H

0 30H

(H)

0 30H

0 30H

(L)

Response type

0 30H

0 30H

(H)

D 44H

4 34H

(L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

1)

1)

Request destination module I/O No.

Request destination module station No.

(H) (L)

PLC No.

0 30H

0 30H

(H) (L)

Network No.

0 30H

0 30H

(H)

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

Request destination module I/O No.

Request destination module station No.

(L)

Sub-command

0 30H

0 30H

(H)

0 30H

0 30H

(L)

Command

0 30H

1 31H

(H)

1 31H

9 39H

Data length target range

End code

56H 00H

*1

Fixed value

00H

PLC No.

0BH 00H

Response data length

Following *1

00H 00H

Serial No.

01H 01H00H

Request type

00H 00HD4H 00H

Request destination module I/O No.

Command

01H 19H

Sub- command

00H 00H00H

PLC No.

00H 00H00H 00H

Request destination module I/O No.

Network No.

Request destination module station No.

00H

Network No.

Request destination module station No.

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 217

21

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".)

Item Message format Request message (host GOT)

(format 6:4E frame (ASCII))

(format 7:4E frame (Binary))

Time display

2009/10/01 18:46:49 THU

After execution

(L)

Fixed value

0 30H

0 30H

(H) (L)

PLC No.

0 30H

1 31H

(H) (L)

Network No.

0 30H

1 31H

(H)

0 30H

0 30H

(H)

Request data length

0 30H

(L)

1 31H

A 41H

0 30H

(H)

CPU monitoring timer

0 30H

0 30H

(L)

0 30H

0 30H

Following *1

*1

(H)

0 30H

0 30H

(L)

Serial No.

0 30H

0 30H

(H)

0 30H

0 30H

(L)

Response type

0 30H

0 30H

(H)

5 35H

4 34H

(L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

1)

Request destination module I/O No.

Request destination module station No.

Character C section

(H) (L)

9 39H

(H) (L)

1 31H

0 30H

0 30H

(H) (L)

0 30H

1 31H

(L)

1 31H

8 38H

(H)

1)

(H) (L)

6 36H

(H) (L)

4 34H

9 39H

4 34H

(H) (L)

0 30H

4 34H

Year data Month data Day data Hour data Minute data Second data

Day-of- week data

(L)

Command

0 30H

1 31H

(H)

0 31H

9 39H

(L)

Sub-command

0 30H

0 30H

(H)

0 30H

0 30H

Data length target range

CPU monitoring timer

00H 00H

*1 Year data

09H 0AH

Month data

01H 12H

Day data

2EH 31H

Hour data

04H

Minute data

Second data

Day-of- week data

Fixed value

00H

PLC No.

Network No.

0DH 00H

Request data length

Following *1

00H 00H

Serial No.

01H 01H00H

Request type

00H 00H54H 00H

Request destination module I/O No.

01H 09H 00H 00H

Command Sub- command

00H

Request destination module station No.

8 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Response message during normal communication (GOT host)

(format 6:4E frame (ASCII))

(format 7:4E frame (Binary))

Response message during faulty communication (GOT host)

(format 6:4E frame (ASCII))

(format 7:4E frame (Binary))

Item Message format

(L)

Fixed value

0 30H

0 30H

(H) (L)

PLC No.

0 30H

1 31H

(H) (L)

Network No.

0 30H

1 31H

(H)

0 30H

0 30H

(H)

Response data length

0 30H

(L)

0 30H

4 34H

0 30H

(H)

End code

0 30H

0 30H

(L)

0 30H

0 30H

Following *1

*1

(H)

0 30H

0 30H

(L)

Serial No.

0 30H

0 30H

(H)

0 30H

0 30H

(L)

Response type

0 30H

0 30H

(H)

D 44H

4 34H

(L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

Request destination module I/O No.

Request destination module station No.

Data length target range

00H 00H

Fixed value

00H

PLC No.

Network No.

02H 00H

Response data length

00H 00H

Serial No.

01H 01H00H00H

Request type

00H 00HD4H 00H

Request destination module I/O No. End code

Request destination module station No.

(L)

Fixed value

0 30H

0 30H

(H) (L)

PLC No.

0 30H

1 31H

(H) (L)

Network No.

0 30H

1 31H

(H)

0 30H

0 30H

(H)

Response data length

0 30H

(L)

1 31H

6 36H

0 30H

(H)

End code

0 30H

0 30H

(L)

5 35H

6 36H

Following *1

*1

(H)

0 30H

0 30H

(L)

Serial No.

0 30H

0 30H

(H)

0 30H

0 30H

(L)

Response type

0 30H

0 30H

(H)

D 44H

4 34H

(L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

1)

1)

Request destination module I/O No.

Request destination module station No.

(H) (L)

PLC No.

0 30H

0 30H

(H) (L)

Network No.

0 30H

0 30H

(H)

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

0 30H

0 30H

Request destination module I/O No.

Request destination module station No.

(L)

Sub-command

0 30H

0 30H

(H)

0 30H

0 30H

(L)

Command

0 30H

1 31H

(H)

0 30H

9 39H

D4H 00H 00H 01H 00H00H 00H00H 01H 00H 00H 0BH 0H

*1

56H 00H 00H 00H 00H 00H 01H 09H 00H 00H00H

Serial No. Fixed value Request type

Request destination module I/O No.

Response data length

Request destination module I/O No.

Following*1

PLC No.

End code PLC No.

Sub- commandCommand

Data length target range

Network No.

Request destination module station No.

Network No.

Request destination module station No.

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 219

22

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 corrected day of the week will be set. 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 set.

In the case of interrupt outputs Write data to the interrupt output devices (D13 and D14) to output the data to the host. (Assuming that "3139H" is written to D13 and "AA55H" to D14.)

Interrupt output To disable the interrupt output, turn on SM52 (interrupt code output disable flag). Page 175 SM devices

Item Message format Interrupt output (GOT host)

(1) When [Interrupt Data Byte] in the communication detail settings is set to [1]

(2) When [Interrupt Data Byte] in the communication detail settings is set to [2]

(3) When [Interrupt Data Byte] in the communication detail settings is set to [4] When [32bit Storage] in the communication detail settings is set to [LH Order]

When [32bit Storage] in the communication detail settings is set to [HL Order]

Interrupt

Interrupt output

Example) When [Interrupt Data Byte] in the communication detail settings is set to 2 byte as shown in (2) of the table below

31H

Output value 1

3139HD13

39H

Output value 2

39H

Output value 1

31H 39H

Output value 1

Output value 2

AAH

Output value1

55H

Output value2

31H

Output value3

39H

Output value4

31H

Output value1

39H

Output value2

AAH

Output value3

55H

Output value4

0 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Error code list The following shows error code, error contents, cause, and measures.

Error code Description Action 0002H Device point error

The specified device range to be read or written is incorrect. Check the specified head device and number of points, and

correct it. Page 163 Device Data Area

0050H Request (command) type or response (response) type code error A code other than the specified value is set for the command type or response type.

Check and correct the command type or response type set in the microcomputer.

0056H Device error A non-existent device has been specified.

Check the devices that can be used and the device ranges. Page 163 Device Data Area

0057H 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.

Correct the specified number of points, or the start address (device number).

Page 163 Device Data Area

When writing data which the command bit length is longer or shorter than the specification, the set number of write data points differs from the specified number of points value.

Check the command data length and set the data again.

0058H The command start address (head device number, start step number) specification from the microcomputer exceeds the range that can be specified.

A value outside the GOT parameter setting range is specified for reading or writing the microcomputer program or file register (R).

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.

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 221

22

Formats 8, 9 The following describes the message formats 8 and 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 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))

(Format 9: QnA compatible 3E frame (Binary))

Details of data items in message format

Data code during communication Communication of format 8 is performed in ASCII code. Communication of the format 9 is performed in Binary code.

(H) (L)

PLC No.

0 30H

(H) (L)

Network No.

0 30H

(H)

Request destination module I/O No.

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

Request destination

module station No.

0 30H

0 30H

Following *1

(H)

Command

0 30H

4 34H

(L)

0 30H

1 31H

*1

(H) (L)

Device code

* 2AH

D 44H

(H)

Start Device

1 31H

0 30H

0 30H

(L)

0 30H

0 30H

0 30H

Character A section

(H)

Sub-command

0 30H

0 30H

(L)

0 30H

0 30H

(H)

Device points

0 30H

0 30H

(L)

0 30H

2 32H

(H) (L)

5 35H

0 30H

(H) (L)

Subheader

0 30H

0 30H

1 1 31H31H

(H) (L)

0 30H

0 30H

(H) (L)

Request data length

1 31H

8 38H

(H) (L)

0 30H

0 30H

(H) (L)

CPU monitoring timer

0 30H

0 30H

Data length target data

00H 00H 00H 00H0CH50H 00H

Subheader PLC No.

Network No.

Request destination

module I/O No.

Request data length

CPU monitoring timer

Request destination

module station No.

00H 00H01H 01H

Sub- command

00H 00H64H

Start Device Device code Device points

00H02HA8H

Command

01H 04H 00H 00H

Data length target data

2 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

The following table shows the contents of the data items.

Data item name Contents

Format 8 Format 9 Subheader (Microcomputer side)

Indicates it is a command message.

Command message: ASCII "5000" (Fixed value) Command message: 50H (Upper digit) (Fixed value)

Subheader (GOT side) Indicates it is a response message.

Response message: ASCII "D000" (Fixed value) Response message: D0H (Upper digit) (Fixed value)

Network No. Set the same number as the network No. set in the GOT. For setting method of "Communication Detail Settings", refer to the following. Page 231 Setting communication interface (Controller Setting)

Transmit the data converted to a 2-digit ASCII code from the upper digit.

Transmit the data converted to a 2-digit binary code.

PLC No. Set the same number as the PLC No. set in the GOT. For setting method of "Communication Detail Settings", refer to the following. Page 231 Setting communication interface (Controller Setting)

Transmit the data converted to a 2-digit ASCII code from the upper digit.

Transmit the data converted to a 2-digit binary code.

Request destination module I/O No.

Ignore GOT.

Request destination module station No.

Ignore GOT.

Request data length Number of bytes from the start of CPU monitoring timer 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.

Response data length Appended to the response message from the microcomputer side. Number of bytes from the start of end code to the last response data or last error response 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.

CPU monitoring timer Ignore GOT.

Command, Sub-command Specifies the access contents from the microcomputer side to GOT. For details of the commands that can be used, refer to the following. Page 178 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.

Device code Specifies the code by which the device data to be read or written is recognized. For details of the device range that can be accessed, refer to the following. Page 163 Device Data Area

Transmit the 2-digit ASCII code corresponding to the following device codes.

Transmit the 2-digit binary code corresponding to the following device codes.

Head device Specifies the head No. of the device data to be read or written. For details of the device range that can be accessed, refer to the following. Page 163 Device Data Area

Transmit the data notated in decimal converted to a 6-digit ASCII code, from the upper digit.

Transmit the data converted to a 6-digit binary code from the lower two digits.

Device points Specifies the device data points to be read or written. (Setting range: Range of the maximum number of points processed for each command) When setting multiple bit accesses, word accesses or double word accesses, limit the total number of access points to within 64 points. When setting multiple blocks, limit the total number of points of all blocks to within the maximum number of points processed for each command.

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.

Device code

D*

R* SD

L*

M* SM

Device name

SD

R

L

SM M

D A8H

AFH A9H

92H

90H 91H

SD

R

L

SM M

D

Device codeDevice name

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 223

22

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.

Year, month, day, hour, minute, second and day of the week data

Specifies the year, month, day, hour, minute, second, and day of the week data to be read or set to the GOT clock data. Page 225 Read clock data (1901) command Page 227 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.

End code (Microcomputer side)

Appended to the response message from the microcomputer side. If an error occurs at the microcomputer side, the error code is displayed. Page 230 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.

Data item name Contents

Format 8 Format 9

4 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

Message format The following shows the message format of the dedicated commands for a microcomputer connection of GOT.

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".)

Item Message format Request message (host GOT)

(format 8:QnA compatible 3E frame (ASCII))

(format 9:QnA compatible 3E frame (Binary))

Response message during normal communication (GOT host)

(format 8:QnA compatible 3E frame (ASCII))

(format 9:QnA compatible 3E frame (Binary))

Time display

2009/10/01 18:46:49 THU

(H) (L)

PLC No.

0 30H

(H) (L)

Network No.

0 30H

(H)

Request destination module I/O No.

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

Request destination module station No.

0 30H

0 30H

Following *1

*1

(H)

0 30H

0 30H

(L)

Request data length

0 30H

C 43H

(H)

0 30H

0 30H

(L)

CPU monitoring timer

0 30H

0 30H

(H)

5 35H

0 30H

(L)

Subheader

0 30H

0 30H

(H)

Command

1 31H

9 39H

(L)

0 30H

1 31H

Character A section

(H)

Sub-command

0 30H

0 30H

(L)

0 30H

0 30H

1 1 31H31H

Data length target data

Command

00H 00H

Data length target data

01H 19H 00H 00H

Sub- command

CPU monitoring timer

00H

Network No.

PLC No.

00H50H

Subheader

00H 00H 00H

Request destination

module I/O No.

Request destination module station No.

Request data length

01H01H 06H

Character B section

(H) (L)

Year data

0 9 30H 39H

(H) (L)

Month data

1 0 31H 30H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 4 30H 34H

(H) (L)

PLC No.

0 30H

(H) (L)

Network No.

0 30H

Following *1

(H)

D 44H

0 30H

(L)

Subheader

0 30H

0 30H

(H)

Request destination module I/O No.

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

Request destination module station No.

0 30H

0 30H

*1

(H)

0 30H

0 30H

(L)

Response data length

1 31H

2 32H

(H)

0 30H

0 30H

(L)

End code

0 30H

0 30H

11 31H31H

Data length target data

00H

Network No.

PLC No.

00HD0H

Subheader

00H 00H 00H

Request destination module I/O No.

Request destination module station No.

Response data length

00H 00H

End code Year data

Month data

Day data

Hour data

09H

Minute data

0AH 01H

Second data

12H 2EH

Day-of- week data

31H 04H01H01H 09H

Data length target data

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 225

22

Response message during faulty communication (GOT host)

(format 8:QnA compatible 3E frame (ASCII))

(format 9:QnA compatible 3E frame (Binary))

Item Message format

(H) (L)

PLC No.

0 30H

(H) (L)

Network No.

0 30H

(H)

Request destination module I/O No.

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

Request destination module station No.

0 30H

0 30H

Following *1

*1

(H)

0 30H

0 30H

(L)

Response data length

1 31H

6 36H

(H)

0 30H

0 30H

(L)

End code

5 35H

6 36H

(H)

D 44H

0 30H

(L)

Subheader

0 30H

0 30H

(H)

Request destination module I/O No.

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

Request destination module station No.

0 30H

0 30H

(H) (L)

PLC No.

0 30H

0 30H

(H) (L)

Network No.

0 30H

0 30H

11 31H 31H

1)

1)

(H)

Command

1 31H

9 39H

(L)

0 30H

1 31H

(H)

Sub-command

0 30H

0 30H

(L)

0 30H

0 30H

Data length target data

Data length target data

01H

*1

Command

01H 19H 00H 00H

Sub- commandEnd code

Network No.

00H

PLC No.

00HD0H

Subheader

00H 00H 00H

Following *1

Request destination

module I/O No.

Request destination module station No.

Response data length

Network No.

PLC No.

00H

01H

00H 00H56H 00H 00H 00H

Request destination module station No.

0BH

Data length target data

Request destination

module I/O No.

6 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

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".)

Item Message format Request message (host GOT)

(format 8:QnA compatible 3E frame (ASCII))

(format 9:QnA compatible 3E frame (Binary))

Time display

2009/10/01 18:46:49 THU

After execution

Character C section

(H) (L)

Year data

0 9 30H 39H

(H) (L)

Month data

1 0 31H 30H

(H) (L)

Day data

0 1 30H 31H

(H) (L)

Hour data

1 8 31H 38H

(H) (L)

Minute data

4 6 34H 36H

(H) (L)

Second data

4 9 34H 39H

(H) (L)

Day-of- week data

0 4 30H 34H

1)

(H) (L)

PLC No.

0 30H

(H) (L)

Network No.

0 30H

Following *1

(H)

5 35H

0 30H

(L)

Subheader

0 30H

0 30H

(H)

Request destination module I/O No.

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

Request destination module station No.

0 30H

0 30H

*1

(H)

0 30H

0 30H

(L)

Response data length

1 31H

A 41H

(H)

0 30H

0 30H

(L)

CPU monitoring timer

0 30H

0 30H

1)

11

(H)

Command

0 31H

9 39H

(L)

0 30H

1 31H

(H)

Sub-command

0 30H

0 30H

(L)

0 30H

0 30H

31H31H

Data length target data

Data length target data

00H

Network No.

00H 0DH50H

Subheader

00H 00H 00H

Following *1

Request destination

module I/O No.

Request destination module station No.

Request data length

00H 00H

CPU monitoring timer

*1 Year data

Month data

Day data

Hour data

09H

Minute data

0AH 01H

Second data

12H 2EH

Day-of- week data

31H 04H

01H 01H

PLC No.

Command

01H 09H 00H 00H

Sub- command

Data length target data

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 227

22

Response message during normal communication (GOT host)

(format 8:QnA compatible 3E frame (ASCII))

(format 9:QnA compatible 3E frame (Binary))

Response message during faulty communication (GOT host)

(format 8:QnA compatible 3E frame (ASCII))

(format 9:QnA compatible 3E frame (Binary))

Item Message format

(H) (L)

PLC No.

0 30H

(H) (L)

Network No.

0 30H

(H)

Request destination module I/O No.

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

Request destination module station No.

0 30H

0 30H

Following *1

*1

(H)

0 30H

0 30H

(L)

Response data length

0 30H

4 34H

(H)

0 30H

0 30H

(L)

End code

0 30H

0 30H

(H)

D 44H

0 30H

(L)

Subheader

0 30H

0 30H

31H 31H

1 1

Data length target data

00H 00H

End code

00H

Network No.

PLC No.

00H 02HD0H

Subheader

00H 01H 01H 00H 00H

Request destination

module I/O No.

Request destination module station No.

Response data length

Data length target data

(H) (L)

PLC No.

0 30H

(H) (L)

Network No.

0 30H

(H)

Request destination module I/O No.

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

Request destination module station No.

0 30H

0 30H

Following *1

*1

(H)

0 30H

0 30H

(L)

Response data length

1 31H

6 36H

(H)

0 30H

0 30H

(L)

End code

5 35H

6 36H

(H)

D 44H

0 30H

(L)

Subheader

0 30H

0 30H

(H)

Request destination module I/O No.

0 30H

0 30H

(L)

0 30H

0 30H

(H) (L)

Request destination module station No.

0 30H

0 30H

(H) (L)

PLC No.

0 30H

0 30H

(H) (L)

Network No.

0 30H

0 30H

11 31H 31H

1)

1)

(H)

Command

0 30H

9 39H

(L)

0 30H

1 31H

(H)

Sub-command

0 30H

0 30H

(L)

0 30H

0 30H

Data length target data

Data length target data

01H

*1

Command

01H 09H 00H 00H

Sub- command

End code

Network No.

00H

PLC No.

00HD0H

Subheader

00H 00H 00H

Following *1

Request destination

module I/O No.

Request destination module station No.

Response data length

Network No.

PLC No.

00H

01H

00H 00H56H 00H 00H 00H

Request destination

module I/O No.

Request destination module station No.

0BH

Data length target data

8 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

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 corrected day of the week will be set. 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 set.

In the case of interrupt outputs Write data to the interrupt output devices (D13 and D14) to output the data to the host. (Assuming that "3139H" is written to D13 and "AA55H" to D14.)

Interrupt output To disable the interrupt output, turn on SM52 (interrupt code output disable flag). Page 175 SM devices

Item Message format Interrupt output (GOT host)

(1) When [Interrupt Data Byte] in the communication detail settings is set to [1]

(2) When [Interrupt Data Byte] in the communication detail settings is set to [2]

(3) When [Interrupt Data Byte] in the communication detail settings is set to [4] When [32bit Storage] in the communication detail settings is set to [LH Order]

When [32bit Storage] in the communication detail settings is set to [HL Order]

Interrupt

Interrupt output

Example) When [Interrupt Data Byte] in the communication detail settings is set to 2 byte as shown in (2) of the table below

31H

Output value 1

3139HD13

39H

Output value 2

39H

Output value 1

31H 39H

Output value 1

Output value 2

AAH

Output value1

55H

Output value2

31H

Output value3

39H

Output value4

31H

Output value1

39H

Output value2

AAH

Output value3

55H

Output value4

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats 229

23

Error code list For the error codes, refer to the following. Page 221 Error code list

0 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.4 Message Formats

3

3.5 GOT Side Settings Setting communication interface (Controller Setting) Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set the following items. [Manufacturer]: [Others] [Controller Type]: [Computer] [I/F]: [Ethernet:Multi] When using the Ethernet communication unit (GT25-J71E71-100), also select [Ethernet:Multi]. [Detail Setting]: Configure the settings according to the usage environment. Page 232 Communication detail settings

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.5 GOT Side Settings 231

23

Communication detail settings Make the settings according to the usage environment.

*1 For the interrupt output, select [TCP/IP]. *2 For GT21 and GS21, refer to the following.

Format: 5 to 9 Default: 6

*3 Select [Yes] only when [Protocol] is [TCP/IP]. *4 The setting value can be changed when the [Living Confirmation] is [Yes]. *5 When assigning the same driver to the multiple channels, in the communication drivers set as the second and following, the default

value of [GOT Communication Port No.] becomes the earliest number in the vacant numbers of No. 6000 and later.

Item Description Range GOT NET No. Set the network No. of the GOT. (Default: 1) 1 to 239

GOT Station Set the station No. of the GOT. (Default: 18) 1 to 64

GOT Communication Port No. Set the GOT port No. for the connection with the Ethernet module. (Default: 5021*5)

1024 to 5010. 5014 to 65534 (Except for 5011, 5012, 5013 and 49153 to 49170)

Startup Time(sec) Specify the time period from the GOT startup until GOT starts the communication with the PLC CPU. (Default: 3sec)

3 to 255sec

Delay Time(ms) Set the send delay time to lower the load of the network and the connected PLCs. (Default: 0ms)

0 to 10000 (ms)

32bit Storage Select the steps to store two words (32-bit data). (Default: LH Order) LH Order or HL Order

Protocol *1 Select the communication protocol (Default: UDP/IP) TCP/IP UDP/IP

Format *2 Select the communication format. (Default: 1)*2 1 to 9

Interrupt Data Length Specify the number of bytes of interrupt data. (Default: 1) 1, 2 or 4

Special Interrupt Code Set whether or not to output the special interrupt code. (Default: No) Yes or No

Living Confirmation *3 Set whether or not to perform a living confirmation. (Default: No) Yes or No

Living Confirmation Cycle *4 Set the sampling to perform a living confirmation. (Default: 20s) 10 to 100s

Destination module I/O number Set the values for the I/O number and the station number of the connection destination module that responds to the request from the controller. Not available to GT21 and GS21. (It operates with [Same as requested value].) (Default: 0)

0 or Same as requested value

2 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.5 GOT Side Settings

3

Special Interrupt Code The special interrupt codes are output at event occurrences. If multiple events occur simultaneously, the special interrupt codes may not be output. The following shows the special interrupt codes and the event types.

Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective.

GOT Ethernet Setting The GOT can be connected to a different network by configuring the following setting.

GOT IP address setting Set the following communication port setting. Standard port (When using GT25-W, port 1) Extension port (When using GT25-W, port 2)

GOT Ethernet common setting Set the following setting which is common to the standard port and the extension port, or port 1 and port 2. [Default Gateway] [Peripheral S/W Communication Port No.] [Transparent Port No.]

IP filter setting By configuring the IP filter setting, the access from the specific IP address can be permitted or shut off. For the detailed settings, refer to the following manual. Page 35 GOT Ethernet Setting

Special Interrupt Code (Hex)

Event type

20H

Base screen, overlap window 1 to 5 When the screen is switched by the screen switching device, the special interrupt code will be output. The base screen and each overlap window are switched independently. (Example of output) When all the screen switching device values assigned to the Base Screen and Overlap Window 1 to 2 are changed, 6 special interrupt codes are output.

21H This code is output when a numerical or ASCII input is completed.

22H This code is output when reading or writing of the recipe data is completed.

23H This code is output when a barcode or RFID data is read.

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.5 GOT Side Settings 233

23

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.

Communication settings on GOT side and monitor screen settings 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. Page 232 Communication detail settings

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). Page 155 System Configuration Examples

IBM-PC/AT-compatible PC (Microsoft Visual C++ Ver.6.0)

4 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.6 System Configuration Examples

3

3.7 Device Range that Can Be Set For the device setting dialog and the device range that can be used on the GOT, refer to the following. Page 434 Microcomputer ([Computer])

3.8 Precautions

GOT clock control Even though the time setting function and time notification function are set in the GOT time setting, the settings are disabled. When reading from or writing to the clock data between the GOT and microcomputer, use the dedicated command.

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 available only for the TCP/IP connection. The interrupt output cannot be executed in the UDP/IP connection.

3 MICROCOMPUTER CONNECTION (ETHERNET) 3.7 Device Range that Can Be Set 235

23

MEMO

6 3 MICROCOMPUTER CONNECTION (ETHERNET) 3.8 Precautions

PART 3 ODVA

4 DeviceNet CONNECTION

237

23

4 DeviceNet CONNECTION Page 238 Connectable Model List Page 239 System Configuration Page 240 Connection Diagram Page 241 GOT Side Settings Page 243 Preparation of EDS File for GOT Page 244 DeviceNet master equipment Side Settings Page 245 Device Range that Can Be Set Page 245 Precautions

4.1 Connectable Model List GOT2000 Series products support the slave function of DeviceNet communication, the open FA network. Thus, the GOT can be connected with each DeviceNet master.

BootOS version of the GOT Install the version N or later of BootOS so that the GOT supports the DeviceNet connection. For the procedure to check the BootOS version and upgrade the version, refer to the following manuals. GT Designer3 (GOT2000) Screen Design Manual GOT2000 Series User's Manual (Utility)

8 4 DeviceNet CONNECTION 4.1 Connectable Model List

4

4.2 System Configuration Connecting to DeviceNet master equipment

*1 The maximum distance varies depending on the transmission speed and cable size. Confirm the specifications on the DeviceNet master equipment side.

*2 Install the communication module (ABCC-M40-DEV, Type number: AB6909-B or AB6909-C) manufactured by HMS to the GT25- FNADP. For the communication module installation method, refer to the following manual. GOT2000 Series Field Network Adapter Unit Instruction Manual

*3 Up to 63 GOT modules (DeviceNet slave equipment) can be connected to one DeviceNet master equipment. *4 Connect terminal resistors at the both ends of the trunk line. *5 GT25-W, GT2505-V does not support the option device.

Controller Communication Type

Connection cable Terminating resistors *4

GOT (DeviceNet slave equipment)

Number of connectable equipment

Cable model Connection diagram number

Max. distance

Option device*5 model

DeviceNet master equipment

DeviceNet Page 240 DeviceNet connection diagram 1)

500m*1 121, 1%, 1/4W GT25-FNADP*2 *3

DeviceNet

Communication driver

Power supply for communication (24 V DC)

DeviceNet master equipment

GOT (DeviceNet slave equipment)

GOT (DeviceNet slave equipment)

GOT (DeviceNet slave equipment)

Connection cable

Terminating resistors Terminating resistors Trunk line

Branch lineBranch line

4 DeviceNet CONNECTION 4.2 System Configuration 239

24

4.3 Connection Diagram The following diagram shows the connection between the GOT and the controller.

Connection Diagram DeviceNet connection diagram 1)

*1 The power supply for communication (24 V DC) is required to supply the power to the power supply (V-) and power supply (V+).

Precautions when preparing a cable Cable length For the Cable length, refer to the following. Page 239 System Configuration

GOT side connector (DeviceNet slave equipment) For the GOT side connector, refer to the following. Manual of Anybus CompactCom M40 Network Communication Module by HMS

DeviceNet master equipment side connector Use the connector compatible with the DeviceNet master equipment side module. For details, refer to the DeviceNet master equipment user's manual.

DeviceNet master equipment

1

2

3

4

5

GOT side (1st)

GOT side (2nd)

Power supply (V-)*1

Communication data Low side (CAN_L)

Communication data High side (CAN_H)

Power supply (V+)*1

1

2

3

4

5

1

2

3

4

5

Shield

power supply cable (V-)

Communication data Low side (CAN_L)

Communication data High side (CAN_H)

power supply cable (V+)

Shield

Cable color : Black

Cable color : Blue

Cable color : White

Cable color : Red

0 4 DeviceNet CONNECTION 4.3 Connection Diagram

4

4.4 GOT Side Settings Setting communication interface (Controller Setting) Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set the following items. [Manufacturer]: [ODVA] [Controller Type]: [DeviceNet] [I/F]: Interface to be used [Detail Setting]: Configure the settings according to the usage environment. Page 242 Communication detail settings

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

4 DeviceNet CONNECTION 4.4 GOT Side Settings 241

24

Communication detail settings Make the settings according to the usage environment.

*1 Align the setting with that on the DeviceNet master equipment side. Page 244 DeviceNet master equipment Side Settings

Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective.

Item Description Range Transmission Speed (BPS)*1 Set this item when change the transmission speed used for communication with

the connected equipment. (Default: Auto) 125K, 250K, 500K, Auto

Station No.*1 Set the station No. (Default: 1) 0 to 63

32bit Storage Select the steps to store two words (32-bit data). (Default: LH Order) LH Order/HL Order

Input Size (Word)*1 Set the Input Size. (Default: 32) 0 to 128

Output Size (Word)*1 Set the Output Size. (Default: 32) 0 to 128

2 4 DeviceNet CONNECTION 4.4 GOT Side Settings

4

4.5 Preparation of EDS File for GOT Prepare the EDS file for the GOT to make available the configuration tool on the DeviceNet master equipment side.

How to acquire EDS file for GOT

Acquisition from the DVD-ROM The EDS file for GOT (GOT2000.eds) is stored in the following folder of the DVD-ROM (GT Works3 Ver.1.130L or later). Disk5ConfigurationFileDeviceNetGOT2000.eds

4 DeviceNet CONNECTION 4.5 Preparation of EDS File for GOT 243

24

4.6 DeviceNet master equipment Side Settings This section explains how to set the DeviceNet master equipment.

DeviceNet master equipment For the details of the DeviceNet master equipment setting method, refer to the manual of the used DeviceNet master equipment.

Installing the EDS file for GOT Install the EDS file for GOT to the configuration tool on the DeviceNet master equipment side, and set the GOT as slave equipment. For how to acquire the EDS file for GOT, refer to the following. Page 243 Preparation of EDS File for GOT

Communication configuration Set the communication parameters on the DeviceNet master equipment side using the switches or configuration tool.

*1 Make sure that the station No. does not overlap. *2 When the setting of Transmission Speed on the GOT side is not set to Automatic, align it with the setting on the master equipment

side. Page 241 GOT Side Settings

*3 Align the settings of Input Size (Word) and Output Size (Word) on the GOT side with the settings on the master equipment side. *4 Align the setting of Station No. on the GOT side with the station No. of the slave equipment.

Page 241 GOT Side Settings

Item Setting range Master equipment Station No.*1 0 to 63

Transmission speed*2 125kbps 250kbps 500kbps

Input Size (Word)*3 0 to 128

Output Size (Word)*3 0 to 128

Slave equipment Station No.*1*4 0 to 63

4 4 DeviceNet CONNECTION 4.6 DeviceNet master equipment Side Settings

4

4.7 Device Range that Can Be Set For the device setting dialog and the device range that can be used on the GOT, refer to the following. Page 437 ODVA ([DeviceNet])

4.8 Precautions

EDS file for GOT Do not edit the EDS file for GOT. Edition may cause communication errors.

Type number of the communication module manufactured by HMS Use the communication module having the type number described in the following manual. GOT2000 Series Field Network Adapter Unit Instruction Manual

Software version of the communication module manufactured by HMS For the software version of the connectable communication module manufactured by HMS, refer to the following technical news. List of DeviceNet-compliant Equipment Validated to Operate with the GOT2000 Series (GOT-A-0084)

Installation of the field network adapter unit (GT25-FNADP) The field network adapter unit (GT25-FNADP) can be installed only at the top stage of the GOT. Page 47 Precautions when installing units on top of one another

4 DeviceNet CONNECTION 4.7 Device Range that Can Be Set 245

24

MEMO

6 4 DeviceNet CONNECTION 4.8 Precautions

PART 4 MODBUS

5 MODBUS/RTU MASTER CONNECTION

6 MODBUS/TCP MASTER CONNECTION

7 MODBUS/RTU SLAVE CONNECTION

8 MODBUS/TCP SLAVE CONNECTION

247

24

5 MODBUS/RTU MASTER CONNECTION Page 248 Connectable Model List Page 249 System Configuration Page 252 Connection Diagram Page 260 GOT Side Settings Page 263 MODBUS/RTU Slave Equipment Side Setting Page 264 Function Code Page 264 MODBUS Communication Control Function Page 264 Device Range that Can Be Set Page 265 Precautions

5.1 Connectable Model List GOT2000 Series products support the master function of MODBUS communication, the open FA network. Thus, the GOT can be connected with each MODBUS slave. For the MODBUS/RTU equipment validated by Mitsubishi Electric Corporation, refer to the following Technical Bulletin. List of Valid Devices Applicable for GOT2000 Series MODBUS Connection for Overseas (GOT-A-0170) For Technical Bulletins, go to the Mitsubishi Electric Factory Automation Global Website. www.MitsubishiElectric.com/fa

8 5 MODBUS/RTU MASTER CONNECTION 5.1 Connectable Model List

5

5.2 System Configuration Connecting to MODBUS/RTU slave equipment

Controller Communication Type

Connection cable GOT Number of connectable equipment

Cable model Connection diagram number

Max. distance

Option device Model

MODBUS/RTU equipment

RS-232 Page 252 RS-232 connection diagram 1)

15m*1 - (Built into GOT) 1 MODBUS equipment for 1 GOT

GT15-RS2-9P

*7*8

GT10-C02H-6PT9P*4

Page 252 RS-232 connection diagram 2)

15m*1 - (Built into GOT)

MODBUS/RTU Master

Communication driver

MODBUS/RTU slave equipment GOT

Connection cable

5 MODBUS/RTU MASTER CONNECTION 5.2 System Configuration 249

25

MODBUS/RTU equipment

RS-422/485 Page 253 RS-422/485 connection diagram 1)(4-wire) or

Page 254 RS-422/485 connection diagram 2)(2-wire)

1200m*1 FA-LTBGT2R4CBL05(0.5m)*2

FA-LTBGT2R4CBL10(1m)*2

FA-LTBGT2R4CBL20(2m)*2

*8

Up to 31 MODBUS equipment for 1 GOT *3*6

Page 254 RS-422/485 connection diagram 3)(4-wire) or

Page 255 RS-422/485 connection diagram 4)(2-wire)

1200m*1 - (Built into GOT)

GT15-RS4-9S

*7*8

GT10-C02H-9SC

Page 254 RS-422/485 connection diagram 3)(4-wire)

1200m *1 - (Built into GOT)

*12

Page 255 RS-422/485 connection diagram 4)(2-wire)

1200m *1 - (Built into GOT)

*13

Page 257 RS-422/485 connection diagram 8)(4-wire) or

Page 257 RS-422/485 connection diagram 9)(2-wire)

1200m*1 GT10-9PT5S*5

*9

Page 255 RS-422/485 connection diagram 5)(2-wire)

1200m*1 GT15-RS4-TE

*7*8

Page 258 RS-422/485 connection diagram 10)(4-wire) or

Page 258 RS-422/485 connection diagram 11)(2-wire)

1200m *1 GT14-RS2T4-9P *10

*11

Page 256 RS-422/485 connection diagram 6)(4-wire) or

Page 256 RS-422/485 connection diagram 7)(2-wire)

1200m*1 - (Built into GOT)

Controller Communication Type

Connection cable GOT Number of connectable equipment

Cable model Connection diagram number

Max. distance

Option device Model

0 5 MODBUS/RTU MASTER CONNECTION 5.2 System Configuration

5

*1 The shortest specification on the MODBUS/RTU equipment side is prioritized. *2 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 When a GT10-C02H-6PT9P unit of the sub version A or B is used, do not ground the case of the D-sub (9-pin) connector. *5 Connect it to the RS-422/485 interface (built into GOT). *6 Up to 10 pieces of MODBUS equipment can be connected to GS21-W. *7 Not available to GT25-W. *8 Not available to GT2505-V. *9 GT2505-V, GT2105-Q only supported. *10 Mount it on the RS-232 interface (GOT built-in). *11 Only available to GT2505-V. *12 For GS21-W, use the RS-422 interface for connection. *13 Only available to GS21-W-N for GS21.

5 MODBUS/RTU MASTER CONNECTION 5.2 System Configuration 251

25

5.3 Connection Diagram The following diagram shows the connection between the GOT and the controller.

RS-232 cable

Connection diagram RS-232 connection diagram 1)

*1 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.

RS-232 connection diagram 2)

*1 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.

Precautions when preparing a cable Cable length The length of the RS-232 cable must be 15m or less.

GOT side connector For the GOT side connector, refer to the following. Page 49 GOT connector specifications

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.

GOT side *1MODBUS equipment side

-

TxD

RxD

-

SG

-

-

-

-

CD

RD(RXD)

SD(TXD)

ER(DTR)

SG

DR(DSR)

RS(RTS)

CS(CTS)

NC

1

2

3

4

5

6

7

8

9

GOT side MODBUS equipment side*1

RxD

TxD

-

-

SG

-

-

SD

RD

ER

DR

SG

RS

CS

2 5 MODBUS/RTU MASTER CONNECTION 5.3 Connection Diagram

5

RS-422/485 cable 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 connection diagram 1)

*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. Make sure to connect the cables and wires as

described in the MODBUS/RTU equipment manual. *3 A terminating resistor is required. Set the terminating resistor selector of the main unit to "Disable" and connect a 110 terminating

resistor. Page 53 Terminating resistors of GOT

*4 For the terminating resistor of MODBUS/RTU equipment, refer to the manual of MODBUS/RTU equipment to be used. *5 Use the twisted pair cable for SDA1/SDB1 and RDA1/RDB1.

CON side(20 pin)*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-)

SDA1(TXD1+) *5

SDB1(TXD1-) *5

RDA1(RXD1+) *5

RDB1(RXD1-) *5

6

8

10

12

2

1

3

4

5

7

9

11

13

14

15

16

17

18

19

20

MODBUS/RTU equipment side*1*2*4

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG

MODBUS/RTU equipment side*1*2*4

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG

*3 R

*3 R

5 MODBUS/RTU MASTER CONNECTION 5.3 Connection Diagram 253

25

RS-422/485 connection diagram 2)

*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 terminating

resistor. Page 53 Terminating resistors of GOT

*4 For the terminating resistor of MODBUS/RTU equipment, refer to the manual of MODBUS/RTU equipment to be used. *5 Use the twisted pair cable for SDA1/SDB1.

RS-422/485 connection diagram 3)

*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.

Make sure to connect the cables and wires as described in the MODBUS/RTU equipment manual. *3 A terminating resistor is required for the terminal GOT. For GT27, GT25(Except GT2505-V), set the terminating resistor selector of the

main unit to "Disable" and connect a 330 terminating resistor. For GT2505-V, GT21, and GS21-W-N, set the terminating resistor setting switch of the GOT to 330 . Since the terminating resistor of GS21-W is fixed to 330 , connecting and setting of the terminating resistor are not required. Page 53 Terminating resistors of GOT

*4 For the terminating resistor of MODBUS/RTU equipment, refer to the manual of MODBUS/RTU equipment to be used.

CON side(20 pin)*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-)

SDA1(TXD1+)*5

SDB1(TXD1-)*5

RDA1(RXD1+)

RDB1(RXD1-)

6

8

10

12

2

1

3

4

5

7

9

11

13

14

15

16

17

18

19

20

MODBUS/RTU equipment side*1*2*4

(+)

(-)

SG

MODBUS/RTU equipment side*1*2*4

(+)

(-)

SG*3 R

SG RSA RSB CSA CSB

SDA

SDB

RDA

RDB

1

6

2

7

5

3

8

4

9

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG*3

*3 R

R

GOT side (D-Sub 9-pin)*3 MODBUS/RTU equipment side*1*2*4

(1st) MODBUS/RTU equipment side*1*2*4

(2nd)

4 5 MODBUS/RTU MASTER CONNECTION 5.3 Connection Diagram

5

RS-422/485 connection diagram 4)

*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 When arranging GT27, GT25 (except GT2505-V), or GT23 in the end position of the system configuration, set the terminating resistor to

Enable. (For GT2505-V, GT21, and GS21-W-N, set 110 ). When arranging GT27, GT25 (except GT2505-V), or GT23 in any position other than the end position, set the terminating resistor to Disable. (For GT2505-V, GT21, and GS21-W-N, set OPEN.) Page 53 Terminating resistors of GOT

*4 For the terminating resistor of MODBUS/RTU equipment, refer to the manual of MODBUS/RTU equipment to be used.

RS-422/485 connection diagram 5)

*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 When placing the GOT to the terminal in the system configuration, set the terminating resistor to "Enable".

When placing the GOT to the position other than the terminal, set the terminating resistor of the GOT to "Disable". Page 53 Terminating resistors of GOT

*4 For the terminating resistor of MODBUS/RTU equipment, refer to the manual of MODBUS/RTU equipment.

SDA SDB RDA RDB

SG RSA RSB CSA CSB

1

6

2

7

5

3

8

4

9

(+)

(-)

SG

(+)

(-)

SG

GOT side (D-Sub 9-pin)*3 MODBUS/RTU equipment side*1*2*4

(1st) MODBUS/RTU equipment side*1*2*4

(2nd)

SDA1

SDB1

RDA1

RDB1

SDA2

SDB2

RDA2

RDB2

SG

FG

1

2

3

4

5

6

7

8

9

10

(+)

(-)

SG

(+)

(-)

SG

GOT side (terminal block)*3 MODBUS/RTU equipment side*1*2*4

(1st) MODBUS/RTU equipment side*1*2*4

(2nd)

5 MODBUS/RTU MASTER CONNECTION 5.3 Connection Diagram 255

25

RS-422/485 connection diagram 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 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 "330".

When placing the GOT to the position other than the terminal, set the terminating resistor of the GOT to "OPEN". Page 53 Terminating resistors of GOT

*4 For the terminating resistor of MODBUS/RTU equipment, refer to the manual of MODBUS/RTU equipment to be used. *5 The signals RSA, RSB, CSA, and CSB are not provided for GT2104-PMBD, GT2103-PMBD.

RS-422/485 connection diagram 7)

*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 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". Page 53 Terminating resistors of GOT

*4 For the terminating resistor of MODBUS/RTU equipment, refer to the manual of MODBUS/RTU equipment to be used. *5 The signals RSA, RSB, CSA, and CSB are not provided for GT2104-PMBD, GT2103-PMBD.

Return connection is not required.

GOT side (terminal block)*3

SDA

SDB

RDA

RDB

SG

RSA

RSB

CSA

CSB

MODBUS/RTU equipment side*1*2*4

(1st) MODBUS/RTU equipment side*1*2*4

(2nd)

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG

*5

*5

*5

*5

SDA

SDB

RDA

RDB

SG

RSA

RSB

CSA

CSB

(+)

(-)

SG

(+)

(-)

SG

*5

*5

*5

*5

GOT side (terminal block)*3 MODBUS/RTU equipment side*1*2*4

(1st) MODBUS/RTU equipment side*1*2*4

(2nd)

6 5 MODBUS/RTU MASTER CONNECTION 5.3 Connection Diagram

5

RS-422/485 connection diagram 8)

*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.

Make sure to connect the cables and wires as described in the MODBUS/RTU equipment manual. *3 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". Page 53 Terminating resistors of GOT Set the 1pair/2pair signal selection switch to "1pair" when using the connection conversion adapter. Connection Conversion Adapter Users manual

*4 For the terminating resistor of MODBUS/RTU equipment, refer to the manual of MODBUS/RTU equipment.

RS-422/485 connection diagram 9)

*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 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". Page 53 Terminating resistors of GOT Set the 1pair/2pair signal selection switch to "1pair" when using the connection conversion adapter. Connection Conversion Adapter Users manual

*4 For the terminating resistor of MODBUS/RTU equipment, refer to the manual of MODBUS/RTU equipment.

SDA

SDB

RDA

RDB

SG

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG

GOT side (terminal block)*3 MODBUS/RTU equipment side*1*2*4

(1st) MODBUS/RTU equipment side*1*2*4

(2nd)

SDA

SDB

RDA

RDB

SG

(+)

(-)

SG

(+)

(-)

SG

GOT side (terminal block)*3 MODBUS/RTU equipment side*1*2*4

(1st) MODBUS/RTU equipment side*1*2*4

(2nd)

5 MODBUS/RTU MASTER CONNECTION 5.3 Connection Diagram 257

25

RS-422/485 connection diagram 10)

*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. In such a case, connect the cables and wires as described in the MODBUS/RTU equipment manual.

*2 Some MODBUS/RTU equipment does not have SG. In this case, the wiring between the GOT and SG is unnecessary.

*3 For the terminating resistor of the MODBUS/RTU equipment, refer to the manual of the MODBUS/RTU equipment to be used. *4 Set the 2-wire/4-wire terminating resistor setting switch of the RS-232/485 signal conversion adapter as shown below.

2-wire/4-wire: 4-wire (2Pair) When placing the GOT to the terminal Set the termination resistor setting to the terminating resistor value of the MODBUS/RTU equipment. However, only 110 and 330 can be set to the termination resistor of the GOT. When the terminating resistor value of the MODBUS/RTU equipment is other than 110 or 330 , set the termination resistor setting of the GOT to OPEN, and connect the terminating resistor according to the terminating resistor value of the MODBUS/RTU equipment externally to the RS-232/485 signal conversion adapter. When placing the GOT to the position other than the terminal Set the termination resistor of the GOT to OPEN. Page 58 Setting the RS-232/485 signal conversion adaptor

*5 Some MODBUS/RTU equipment requires the control line (CS, RS) to be controlled. In such a case, the RS-232/485 signal conversion adapter cannot be used for the connection.

RS-422/485 connection diagram 11)

*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. In such a case, connect the cables and wires as described in the MODBUS/RTU equipment manual.

*2 Some MODBUS/RTU equipment does not have SG. In this case, the wiring between the GOT and SG is unnecessary.

*3 For the terminating resistor of the MODBUS/RTU equipment, refer to the manual of the MODBUS/RTU equipment to be used. *4 Set the 2-wire/4-wire terminating resistor setting switch of the RS-232/485 signal conversion adapter as shown below.

2-wire/4-wire: 2-wire (1Pair) When placing the GOT to the terminal Set the termination resistor setting to the terminating resistor value of the MODBUS/RTU equipment. However, only 110 and 330 can be set to the termination resistor of the GOT. When the terminating resistor value of the MODBUS/RTU equipment is other than 110 or 330 , set the termination resistor setting of the GOT to OPEN, and connect the terminating resistor according to the terminating resistor value of the MODBUS/RTU equipment externally to the RS-232/485 signal conversion adapter. When placing the GOT to the position other than the terminal Set the termination resistor of the GOT to OPEN. Page 58 Setting the RS-232/485 signal conversion adaptor

*5 Some MODBUS/RTU equipment requires the control line (CS, RS) to be controlled. In such a case, the RS-232/485 signal conversion adapter cannot be used for the connection.

GOT side (terminal block) *4*5

SDA SDB RDA RDB

SG

MODBUS/RTU equipment side *1*2*3

(1st) MODBUS/RTU equipment side *1*2*3

(2nd)

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG

GOT side (terminal block) *4*5

SDA

SDB

RDA

RDB

SG

MODBUS/RTU equipment side *1*2*3

(1st) MODBUS/RTU equipment side *1*2*3

(2nd)

(+)

(-)

SG

(+)

(-)

SG

8 5 MODBUS/RTU MASTER CONNECTION 5.3 Connection Diagram

5

Precautions when preparing a cable Cable length The length of the RS-422/485 cable must be 1200m or less.

GOT side connector For the GOT side connector, refer to the following. Page 49 GOT connector specifications

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.

Connecting terminating resistors GOT side When connecting a MODBUS/RTU equipment to the GOT, a terminating resistor must be connected to the GOT. For GT27, GT25(Except GT2505-V), GT23 Set the terminating resistor using the terminating resistor setting switch. For GT2505-V, GT21, and GS21-W-N Set the terminating resistor using the terminating resistor selector. For GS21-W Since the terminating resistor is fixed to 330 , setting the terminating resistor is not necessary. For the procedure to set the terminating resistor, refer to the following. Page 53 Terminating resistors of GOT

MODBUS/RTU equipment side 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.

5 MODBUS/RTU MASTER CONNECTION 5.3 Connection Diagram 259

26

5.4 GOT Side Settings Setting communication interface (Controller Setting) Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set the following items. [Manufacturer]: [MODBUS] [Controller Type]: [MODBUS Slave(GOT:Master)] [I/F]: Interface to be used [Detail Setting]: Configure the settings according to the usage environment. Page 261 Communication detail settings

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

0 5 MODBUS/RTU MASTER CONNECTION 5.4 GOT Side Settings

5

Communication detail settings Make the settings according to the usage environment.

Item Description Range Transmission Speed Set this item when change the transmission speed used for communication with

the connected equipment. (Default: 19200bps)

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

Retry Set the number of retries to be performed when a communication error occurs. (Default: 3times)

0 to 5times

Timeout Time Set the time period for a communication to time out. (Default: 3sec)

1 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 communication request from the GOT. (Default: 0ms)

0 to 300ms

32bit Storage Select the steps to store two words (32-bit data). (Default: LH Order)

LH Order/HL Order

FunctionCode[0F] Select the FunctionCode [0F]. (Default: Used)

Used/Unused

FunctionCode[10] Select the FunctionCode [10]. (Default: Used)

Used/Unused

Coil read times Set the Coil read time. (Default: 2000)

1 to 2000 points

Input relay read time Set the Input relay read time. (Default: 2000)

1 to 2000 points

Holding register read times Set the Holding register read times. (Default: 125)

1 to 125 points

Input register read times Set the Input register read times. (Default: 125)

1 to 125 points

Coil write times Set the Coil write times. (Default: 800)

1 to 1968 points

Holding register write times Set the Holding register write times. (Default: 100)

1 to 123 points

5 MODBUS/RTU MASTER CONNECTION 5.4 GOT Side Settings 261

26

*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.

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. When connecting to MODBUS/RTU equipment which requires a delay longer than 3.5 character time, adjust the send delay time.

Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective.

+=Actual send delay time

Send delay time set in the communication

detail setting 3.5 character

time

Minimum interval for communication frame defined in MODBUS/RTU

2 5 MODBUS/RTU MASTER CONNECTION 5.4 GOT Side Settings

5

5.5 MODBUS/RTU Slave Equipment Side Setting

MODBUS/RTU Slave equipment For details of the MODBUS/RTU Slave equipment, refer to the manual of MODBUS/RTU Slave equipment to be used.

Station number setting In the MODBUS network, a maximum of 31 MODBUS/RTU slave equipment can be connected to one GOT. Assign a non-overlapped station number ranging from 1 to 247 arbitrarily to each MODBUS/RTU slave equipment. In the system configuration, the MODBUS/RTU slave 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.

Direct specification When setting the device, specify the station number of the MODBUS/RTU slave equipment of which data is to be changed.

Indirect specification When setting the device, indirectly specify the station number of the MODBUS/RTU slave equipment of which data is to be changed using the 16-bit GOT internal data register (GD10 to GD16). When specifying the station No. from 248 to 254 on GT Designer3, the value of GD10 to GD16 compatible to the station No. specification will be the station No. of the MODBUS/RTU slave equipment.

All station specification (broadcast) Target station differs depending on write-in operation or read-out operation. For write-in operation, all station will be a target. For read-out operation, only the host station will be a target.

Specification range 1 to 247

Specification station NO. Compatible device Setting range 248 GD10 0 to 255:

0 : All station specification (broadcast) 255 : Host station access For the setting other than the above, an error (dedicated device is out of range) will occur.

249 GD11

250 GD12

251 GD13

252 GD14

253 GD15

254 GD16

Examples of station number setting

Station No.3

Station No.15

Station No.1GOT

5 MODBUS/RTU MASTER CONNECTION 5.5 MODBUS/RTU Slave Equipment Side Setting 263

26

5.6 Function Code The following shows the message format for the MODBUS communication.

The GOT supports the following function codes.

5.7 MODBUS Communication Control Function This function is to prevent a communication response delay by the equipment with different specifications in the MODBUS network. The GOT special register (GS) controls available function codes. Set this function when equipment applicable to the following conditions is used on the MODBUS network. Equipment that supports only some function codes Equipment whose maximum transfer size is small for function codes The following lists the GOT special registers (GS) used for the MODBUS communication control function.

For the details of the GOT special registers (GS), refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

5.8 Device Range that Can Be Set For the device setting dialog and the device range that can be used on the GOT, refer to the following. Page 439 MODBUS ([MODBUS Slave(GOT:Master)])

Function code Function Number of devices that are 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

GOT special register (GS) Description GS579 Specification of the communication setting (common or individual) for each CH

GS570 to GS576 Common communication settings

GS590 to GS596 Individual communication settings for CH1

GS597 to GS603 Individual communication settings for CH2

GS604 to GS610 Individual communication settings for CH3

GS611 to GS617 Individual communication settings for CH4

Address CRCFunction code Data

4 5 MODBUS/RTU MASTER CONNECTION 5.6 Function Code

5

5.9 Precautions

Communication confirmation to connected equipment The GOT reads the following devices for checking whether the GOT can communicate with the controller.

When the controller is a MODBUS/RTU equipment that does not have the holding register (400001), check whether the MODBUS/RTU equipment sends back a response to the request from the GOT. Communication is available when the MODBUS/RTU equipment sends back a response, regardless of the message type (normal or abnormal).

Station No. settings of the MODBUS/RTU slave equipment side In the system configuration, the MODBUS/RTU slave equipment with the station number set with the host address must be included.For details of host address setting, refer to the following. Page 260 Setting communication interface (Controller Setting)

GOT clock control The settings of "time adjusting" or "time broadcast" made on the GOT will be disabled on the PLC.

Disconnecting some of multiple connected equipment 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. GT Designer3 (GOT2000) Screen Design Manual

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.

Setting example for project script

GOT Device GT27, GT25, and GT23 The holding register (400001) is read.

GT21 and GS21 The coil (000001) is read. When reading the coil (000001) fails, the holding register (400001) is read.

5 MODBUS/RTU MASTER CONNECTION 5.9 Precautions 265

26

MEMO

6 5 MODBUS/RTU MASTER CONNECTION 5.9 Precautions

6

6 MODBUS/TCP MASTER CONNECTION Page 267 Connectable Model List Page 268 System Configuration Page 269 GOT Side Settings Page 274 MODBUS/TCP Slave Side Settings Page 274 Function Code Page 274 MODBUS Communication Control Function Page 274 Device Range that Can Be Set Page 275 Example of Connection Page 281 Precautions

6.1 Connectable Model List GOT2000 Series products support the master function of MODBUS/TCP communication, the open FA network. Thus, the GOT can be connected with each MODBUS/TCP slave. For the MODBUS/TCP equipment validated by Mitsubishi Electric Corporation, refer to the following Technical Bulletin. List of Valid Devices Applicable for GOT2000 Series MODBUS Connection for Overseas (GOT-A-0170) For Technical Bulletins, go to the Mitsubishi Electric Factory Automation Global Website. www.MitsubishiElectric.com/fa

6 MODBUS/TCP MASTER CONNECTION 6.1 Connectable Model List 267

26

6.2 System Configuration Connecting to MODBUS/TCP slave equipment

*1 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.

*2 When connecting GT2000 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.

*3 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.

*4 Use the straight cable. *5 For details, refer to the MODBUS/TCP equipment manual. *6 For GT21 or GS21, 4 or less. *7 GT25-W, GT2505-V does not support the option device.

Controller Comm unicati on Type

Connection cable Exte rnal devi ce

Connection cable GOT*2 Number of connectable equipment

Cable model*4 Maximum segment length*3

Cable model Maximum segment length*3

Option device*7 GOT model

MODBUS/ TCP equipment

Ethernet 100BASE-TX Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 5 or higher 10BASE-T

Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 3 or higher

100m Hub*1 100BASE-TX Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 5 or higher 10BASE-T

Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 3 or higher

100m - (Built into GOT) When controller:GOT is N:1 The number of controllers for 1 GOT is TCP: 128 or less.*6

When controller:GOT is 1:N The following shows the number of GOTs for 1 controller Depends on the MODBUS/TCP equipment used.*5

GT25-J71E71-100

MODBUS/TCP Master, Gateway

Communication driver

GOTHub

Connection cable Connection cable

MODBUS/TCP slave equipment

8 6 MODBUS/TCP MASTER CONNECTION 6.2 System Configuration

6

6.3 GOT Side Settings Setting communication interface (Controller Setting) Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set the following items. [Manufacturer]: [MODBUS] [Controller Type]: [MODBUS Slave(GOT:Master)] [I/F]: [Ethernet:Multi] When using the Ethernet communication unit (GT25-J71E71-100), also select [Ethernet:Multi]. [Detail Setting]: Configure the settings according to the usage environment. Page 270 Communication detail settings

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

6 MODBUS/TCP MASTER CONNECTION 6.3 GOT Side Settings 269

27

Communication detail settings Make the settings according to the usage environment.

*1 Set different values for [GOT Station] of [Detail Setting] and [Station] of [Connected Ethernet Controller Setting]. Page 272 Connected Ethernet controller setting

*2 When assigning the same driver to the multiple channels, in the communication drivers set as the second and following, the default value of [GOT Communication Port No.] becomes the earliest number in the vacant numbers of No. 6000 and later.

Item Description Range GOT Net No. Set the network No. of the GOT.

(Default: 1) 1 to 239

GOT Station*1 Set the station No. of the GOT. (Default: 18)

1 to 247

GOT Communication Port No. Set the GOT port No. for the connection with the Ethernet module. (Default: 5020*2)

1024 to 5010, 5014 to 65534 (Except for 5011, 5012, 5013 and 49153 to 49170)

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)

0 to 10000 (ms)

32bit Storage Select the steps to store two words (32-bit data). (Default: LH Order)

LH Order/HL Order

FunctionCode[0F] Set whether to use the function code [0F]. (Default: Used)

Used/Unused

FunctionCode[10] Set whether to use the function code [10]. (Default: Used)

Used/Unused

Coil read times Set the read points of the coil. (Default: 1000 points)

1 to 2000 (points)

Input relay read times Set the read points of the input relay. (Default: 1000 points)

1 to 2000 (points)

Holding registor read times Set the read points of the holding register. (Default: 125 points)

1 to 125 (points)

Input register read times Set the read points of the input register. (Default: 125 points)

1 to 125 (points)

Coil write times Set the write points of the coil. (Default: 800 points)

1 to 800(points)

Holding register write times Set the write points of the holding register. (Default: 100 points)

1 to 100(points)

0 6 MODBUS/TCP MASTER CONNECTION 6.3 GOT Side Settings

6

Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective.

GOT Ethernet Setting The GOT can be connected to a different network by configuring the following setting.

GOT IP address setting Set the following communication port setting. Standard port (When using GT25-W, port 1) Extension port (When using GT25-W, port 2)

GOT Ethernet common setting Set the following setting which is common to the standard port and the extension port, or port 1 and port 2. [Default Gateway] [Peripheral S/W Communication Port No.] [Transparent Port No.]

IP filter setting By configuring the IP filter setting, the access from the specific IP address can be permitted or shut off. For the detailed settings, refer to the following manual. Page 35 GOT Ethernet Setting

6 MODBUS/TCP MASTER CONNECTION 6.3 GOT Side Settings 271

27

Connected Ethernet controller setting

*1 When the module ID is required to be fixed to 255, select [MODBUS/TCP(unit ID fixed)]. *2 Set different values for [GOT Station] of [Detail Setting] and [Station] of [Connected Ethernet Controller Setting].

Page 270 Communication detail settings

Item Description Range Host The host is displayed.

It refers to a station that can be connected without setting a station number. (The host is indicated with an asterisk (*).)

Net No. Set the network No. of the connected Ethernet module. (Default: 1)

1 to 239

Station*2 Set the station No. of the connected Ethernet module. (Default: 1)

1 to 247

Unit Type*1 Select the destination Ethernet module. (Default: MODBUS/TCP)

MODBUS/TCP MODBUS/TCP(unit ID fixed)

IP Address Set the IP address of the connected Ethernet module. (Default: 1.1.1.1)

PLC side IP address

Port No. Set the port No. of the connected Ethernet module. (Default: 502)

1 to 65535

Communication format TCP (fixed) TCP (fixed)

2 6 MODBUS/TCP MASTER CONNECTION 6.3 GOT Side Settings

6

[Connected Ethernet Controller Setting] for GT21 and GS21 Effective range of [Connected Ethernet Controller Setting] Only [1] to [4] of [Connected Ethernet Controller Setting] can be used for GT21 and GS21. If [5] onwards are used, the settings are invalid on GT21 and GS21. [Host] setting Set [Host] within the range from [1] to [4] in [Connected Ethernet Controller Setting].

Changing the host with GOT module The host can be changed by the GOT module Utility. For details of settings, refer to the following. GOT2000 Series User's Manual (Utility)

Only [1] to [4] can be used.

6 MODBUS/TCP MASTER CONNECTION 6.3 GOT Side Settings 273

27

6.4 MODBUS/TCP Slave Side Settings For details of the MODBUS/TCP equipment, refer to the manual of MODBUS/RTU equipment to be used.

6.5 Function Code The following shows the message format for the MODBUS communication.

The GOT supports the following function codes.

6.6 MODBUS Communication Control Function This function is to prevent a communication response delay by the equipment with different specifications in the MODBUS network. The GOT special register (GS) controls available function codes. Set this function when equipment applicable to the following conditions is used on the MODBUS network. Equipment that supports only some function codes Equipment whose maximum transfer size is small for function codes The following lists the GOT special registers (GS) used for the MODBUS communication control function.

For the details of the GOT special registers (GS), refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

6.7 Device Range that Can Be Set For the device setting dialog and the device range that can be used on the GOT, refer to the following. Page 439 MODBUS ([MODBUS Slave(GOT:Master)])

Function code Function Number of devices that are accessible with one message [Unit: point(s)] 0x01 Read Coils 1 to 1000

0x02 Read Discrete Inputs 1 to 1000

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 800

0x10 Write Multiple Register 1 to 123

0x14 Read File Record 1 to 124

0x15 Write File Record 1 to 122

GOT special register (GS) Description GS579 Specification of the communication setting (common or individual) for each CH

GS570 to GS576 Common communication settings

GS590 to GS596 Individual communication settings for CH1

GS597 to GS603 Individual communication settings for CH2

GS604 to GS610 Individual communication settings for CH3

GS611 to GS617 Individual communication settings for CH4

Address CRCFunction code Data

4 6 MODBUS/TCP MASTER CONNECTION 6.4 MODBUS/TCP Slave Side Settings

6

6.8 Example of Connection Connecting to SCHNEIDER PLC

System Configuration

*1 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.

*2 When connecting GT2000 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.

*3 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.

*4 Product manufactured by SCHNEIDER ELECTRIC SA.For details of the product, contact SCHNEIDER ELECTRIC SA. *5 Use the straight cable.

controll er

Ethernet module*4

Commu nication Type

Connection cable Exte rnal devi ce

Connection cable GOT*2 Number of connectable equipment

Cable model*5 Max. dista nce*3

Cable model Max. dista nce*3

Option device

GOT model

Modicon Premium Series

TSX ETY 4102 TSX ETY 5102

Ethernet 100BASE-TX Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 5 or higher 10BASE-T

Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 3 or higher

100m Hub*1 100BASE-TX Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 5 or higher 10BASE-T

Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 3 or higher

100m - (Built into GOT)

64 GOTs for 1 PLC

Modicon Quantum Series

140 NOE 771 00 140 NOE 771 10 140 NWM 100 00

MODBUS/TCP Master, Gateway

Communication driver

Ethernet module

SCHNEIDER PLC GOTHub

Connection cable Connection cable

6 MODBUS/TCP MASTER CONNECTION 6.8 Example of Connection 275

27

PLC Side Setting

SCHNEIDER ELECTRIC PLC For details of SCHNEIDER PLC, refer to the following manual. SCHNEIDER PLC user's Manual

Parameter settings Set the parameter settings with programming software for SCHNEIDER PLC. For Modicon Premium series Set for PL7 Pro programming software.

For Modicon Quantum series Set for Concept programming software.

Item Set value Processors Connected CPU module

Memory cards Memory card to be used

Module Connected Ethernet module

IP Address IP address for Ethernet module

Size of global address fields Setting for device points Bits: Coil, Input Words: Input register, Maintenance register

Item Set value PLC Selection Connected CPU module

TCP/IP Ethernet Numbers of unit

I/O Module Selection Connected Ethernet module

Internet Address IP address for Ethernet module

6 6 MODBUS/TCP MASTER CONNECTION 6.8 Example of Connection

6

Connecting to YOKOGAWA PLC

System Configuration

*1 When connecting STARDOM to MODBUS/TCP, Modbus Communication Portfolio License is required. For details, refer to the following manual. YOKOGAWA PLC user's Manual

*2 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.

*3 When connecting GT2000 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.

*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.

*5 Use the straight cable.

controller Commu nication Type

Connection cable External device

Connection cable GOT*3 Number of connectable equipment

Cable model*5 Max. dista nce*4

Cable model Max. dista nce*4

Option device GOT Model

STARDOM*1

(NFCP100, NFJT100)

Ethernet 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 Hub*2 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 - (Built into GOT) 126 GOTs for 1 PLC

MODBUS/TCP Master, Gateway

Communication driver

YOKOGAWA PLC GOTHub

Connection cable Connection cable

6 MODBUS/TCP MASTER CONNECTION 6.8 Example of Connection 277

27

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

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).

Modbus Communication Portfolio License 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

Defining Logic POU Define Logic POU using Logic Designer (peripheral software), and download the project to STARDOM. Start Logic Designer and create a new project using a template. Use [STARDOM Serial Communication] template. 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 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

8 6 MODBUS/TCP MASTER CONNECTION 6.8 Example of Connection

6

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.

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. 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. 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.

6 MODBUS/TCP MASTER CONNECTION 6.8 Example of Connection 279

28

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 For dual-redundant configuration When STARDOM is configured with a redundant system, the connection is not supported.

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.

0 6 MODBUS/TCP MASTER CONNECTION 6.8 Example of Connection

6

6.9 Precautions

When connecting to multiple GOTs Setting PLC No. When connecting two or more GOTs in the MODBUS/TCP network, set each [PLC No.] to the GOT. Page 269 Setting communication interface (Controller Setting)

Setting IP address Do not use the IP address "192.168.0.18" when using multiple GOTs with the GOT 1000 series mixed. A communication error may occur on the GOT with the IP address.

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. 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. 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

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.

Setting example for project script

6 MODBUS/TCP MASTER CONNECTION 6.9 Precautions 281

28

MEMO

2 6 MODBUS/TCP MASTER CONNECTION 6.9 Precautions

7

7 MODBUS/RTU SLAVE CONNECTION Page 283 Connectable Model List Page 284 System Configuration Page 286 Connection Diagram Page 293 GOT Side Settings Page 295 MODBUS/RTU master equipment Side Settings Page 295 Function Code Page 295 GOT (Slave) Operations for All Station Specification (Broadcast) Page 295 Device Range that Can Be Set Page 296 Precautions

7.1 Connectable Model List The GOT2000 series supports the slave function of the MODBUS communication that is the open FA network. Thus, the GOT can be connected with each MODBUS master equipment. For the MODBUS/RTU equipment validated by Mitsubishi Electric Corporation, refer to the following Technical Bulletin. List of Valid Devices Applicable for GOT2000 Series MODBUS Connection for Overseas (GOT-A-0170) For Technical Bulletins, go to the Mitsubishi Electric Factory Automation Global Website. www.MitsubishiElectric.com/fa

7 MODBUS/RTU SLAVE CONNECTION 7.1 Connectable Model List 283

28

7.2 System Configuration Connecting to MODBUS/RTU master equipment

Controller Communication Type

Connection cable GOT Number of connectable equipment

Cable model Connection diagram number

Max. distance

Option device*7*8 model

MODBUS/RTU master equipment

RS-232 Page 286 RS-232 connection diagram 1)

15m*1 - (Built into GOT) 1 MODBUS/RTU master equipment for 1 GOT

GT15-RS2-9P

GT10-C02H-6PT9P*4

Page 286 RS-232 connection diagram 2)

15m*1 - (Built into GOT)

MODBUS/RTU Slave

Communication driver

MODBUS/RTU master equipment

GOT

Connection cable

4 7 MODBUS/RTU SLAVE CONNECTION 7.2 System Configuration

7

*1 The shortest specification on the MODBUS/RTU master equipment side is prioritized. *2 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 master equipment side will apply. *4 When a GT10-C02H-6PT9P unit of the sub version A or B is used, do not ground the case of the D-sub (9-pin) connector. *5 Connect it to the RS-422/485 interface (built into GOT). *6 GS21-W is connectable with one set of MODBUS/RTU equipment. *7 GT25-W is not compatible to the option devices other than FA-LTBGT2R4CBL. *8 GT2505-V does not support the option device other than GT10-9PT5S. *9 GT2505-V, GT2105-Q only supported. *10 For GS21-W, use the RS-422 interface for connection. *11 Only available to GS21-W-N for GS21.

MODBUS/RTU master equipment

RS-422/485 Page 287 RS-422/485 connection diagram 1)(4-wire) or

Page 288 RS-422/485 connection diagram 2)(2-wire)

1200m*1 FA-LTBGT2R4CBL05(0.5m)*2

FA-LTBGT2R4CBL10(1m)*2

FA-LTBGT2R4CBL20(2m)*2

Up to 31 GOTs for 1 MODBUS/RTU master equipment *3*6

Page 288 RS-422/485 connection diagram 3)(4-wire) or

Page 289 RS-422/485 connection diagram 4)(2-wire)

1200m*1 - (Built into GOT)

GT15-RS4-9S

GT10-C02H-9SC

Page 288 RS-422/485 connection diagram 3)(4-wire)

1200m *1 - (Built into GOT)

*10

Page 289 RS-422/485 connection diagram 4)(2-wire)

1200m *1 - (Built into GOT)

*11

Page 291 RS-422/485 connection diagram 8)(4-wire) or

Page 291 RS-422/485 connection diagram 9)(2-wire)

1200m*1 GT10-9PT5S*5

*9

Page 289 RS-422/485 connection diagram 5)(2-wire)

1200m*1 GT15-RS4-TE

Page 290 RS-422/485 connection diagram 6)(4-wire) or

Page 290 RS-422/485 connection diagram 7)(2-wire)

1200m*1 - (Built into GOT)

Controller Communication Type

Connection cable GOT Number of connectable equipment

Cable model Connection diagram number

Max. distance

Option device*7*8 model

7 MODBUS/RTU SLAVE CONNECTION 7.2 System Configuration 285

28

7.3 Connection Diagram The following diagram shows the connection between the GOT and the controller.

RS-232 cable

Connection diagram RS-232 connection diagram 1)

*1 Some MODBUS/RTU master 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 master equipment manual.

RS-232 connection diagram 2)

*1 Some MODBUS/RTU master 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 master equipment manual.

Precautions when preparing a cable Cable length The length of the RS-232 cable must be 15m or less.

GOT side connector For the GOT side connector, refer to the following. Page 49 GOT connector specifications

MODBUS equipment side connector Use the connector compatible with the MODBUS/RTU master equipment side module. For details, refer to the MODBUS/RTU master equipment user's manual.

GOT side(slave) MODBUS /RTU master equipment side*1

-

TxD

RxD

-

SG

-

-

-

-

CD

RD(RXD)

SD(TXD)

ER(DTR)

SG

DR(DSR)

RS(RTS)

CS(CTS)

NC

1

2

3

4

5

6

7

8

9

GOT side(slave) MODBUS /RTU master equipment side*1

RxD

TxD

-

-

SG

-

-

SD

RD

ER

DR

SG

RS

CS

6 7 MODBUS/RTU SLAVE CONNECTION 7.3 Connection Diagram

7

RS-422/485 cable The following shows the connection diagrams and connector specifications of the RS-422/485 cable used for connecting the GOT to a PLC.

Connection diagram RS-422/485 connection diagram 1)

*1 Some MODBUS/RTU master equipment don't have SG. In this case, the wiring between GOT and SG is unnecessary. *2 Some MODBUS/RTU master 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 master equipment manual. *3 A terminating resistor is required for the terminal GOT. Set the terminating resistor selector of the main unit to "Disable" and connect a

110 terminating resistor. Page 53 Terminating resistors of GOT

*4 For the terminating resistor of MODBUS/RTU master equipment, refer to the manual of MODBUS/RTU master equipment to be used. *5 Use the twisted pair cable for SDA1/SDB1 and RDA1/RDB1.

SG NC NC NC

SDA2(TXD2+) SDB2(TXD2-)

RDA2(RXD2+) RDB2(RXD2-)

NC RSA(RTS+)

NC RSB(RTS-)

NC CSA(CTS+)

NC CSB(CTS-)

SDA1(TXD1+) *5

SDB1(TXD1-) *5

RDA1(RXD1+) *5

RDB1(RXD1-) *5

6

8

10

12

2

1

3

4

5

7

9

11

13

14

15

16

17

18

19

20

MODBUS /RTU master equipment side*1*2*4

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG

*3 R

*3 R

NC NC NC

SDA2(TXD2+) SDB2(TXD2-)

RDA2(RXD2+) RDB2(RXD2-)

NC RSA(RTS+)

NC RSB(RTS-)

NC CSA(CTS+)

NC CSB(CTS-)

SDA1(TXD1+) *5

SDB1(TXD1-) *5

RDA1(RXD1+) *5

RDB1(RXD1-) *5

6

8

10

12

2

1

3

4

5

7

9

11

13

14

15

16

17

18

19

20

SG

GOT side(slave)*3

(1st) GOT side(slave)*3

(2nd)

7 MODBUS/RTU SLAVE CONNECTION 7.3 Connection Diagram 287

28

RS-422/485 connection diagram 2)

*1 The actual terminal layout on the MODBUS/RTU master 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 master equipment manual.

*2 Some MODBUS/RTU master equipment don't have SG. In this case, the wiring between GOT and SG is unnecessary. *3 A terminating resistor is required for the terminal GOT. Set the terminating resistor selector of the main unit to "Disable" and connect a

110 terminating resistor. Page 53 Terminating resistors of GOT

*4 For the terminating resistor of MODBUS/RTU master equipment, refer to the manual of MODBUS/RTU master equipment to be used. *5 Use the twisted pair cable for SDA1/SDB1.

RS-422/485 connection diagram 3)

*1 Some MODBUS/RTU master equipment don't have SG. In this case, the wiring between GOT and SG is unnecessary. *2 Some MODBUS/RTU master 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 master equipment manual. *3 A terminating resistor is required for the terminal GOT. Set the terminating resistor selector of the main unit of GT27 and GT25(Except

GT2505-V) to "Disable" and connect a 330 terminating resistor. For GT2505-V, GT21, and GS21-W-N, set the terminating resistor setting switch of the GOT to 330 . Since the terminating resistor of GS21-W is fixed to 330 , connecting and setting of the terminating resistor are not required. Page 53 Terminating resistors of GOT

*4 For the terminating resistor of MODBUS/RTU master equipment, refer to the manual of MODBUS/RTU master equipment to be used.

SG NC NC NC

SDA2(TXD2+) SDB2(TXD2-)

RDA2(RXD2+) RDB2(RXD2-)

NC RSA(RTS+)

NC RSB(RTS-)

NC CSA(CTS+)

NC CSB(CTS-)

SDA1(TXD1+) *5

SDB1(TXD1-) *5

RDA1(RXD1+) *5

RDB1(RXD1-) *5

6

8

10

12

2

1

3

4

5

7

9

11

13

14

15

16

17

18

19

20

MODBUS /RTU master equipment side*1*2*4

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG*3 R

NC NC NC

SDA2(TXD2+) SDB2(TXD2-)

RDA2(RXD2+) RDB2(RXD2-)

NC RSA(RTS+)

NC RSB(RTS-)

NC CSA(CTS+)

NC CSB(CTS-)

SDA1(TXD1+) *5

SDB1(TXD1-) *5

RDA1(RXD1+) *5

RDB1(RXD1-) *5

6

8

10

12

2

1

3

4

5

7

9

11

13

14

15

16

17

18

19

20

SG

GOT side(slave)*3

(2nd) GOT side(slave)*3

(1st)

SG RSA RSB CSA CSB

SDA

SDB

RDA

RDB

1

6

2

7

5

3

8

4

9

MODBUS /RTU master equipment side*1*2*4

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG*3

*3 R

R

RSA RSB CSA CSB

SDA

SDB

RDA

RDB

SG

1

6

2

7

5

3

8

4

9

GOT side(slave)*3

(1st) GOT side(slave)*3

(2nd)

8 7 MODBUS/RTU SLAVE CONNECTION 7.3 Connection Diagram

7

RS-422/485 connection diagram 4)

*1 The actual terminal layout on the MODBUS/RTU master equipment may differ from the example shown above. SDA/B(+/-) and RDA/ B(+/-) terminals can be separated from each other. In such cases, make sure to connect the cables and wires as described in the MODBUS/RTU master equipment manual.

*2 Some MODBUS/RTU master equipment don't have SG. In this case, the wiring between GOT and SG is unnecessary. *3 When arranging GT27, GT25 (except GT2505-V), or GT23 in the end position of the system configuration, set the terminating resistor to

Enable. (For GT2505-V, GT21, and GS21-W-N, set 110 ). When arranging GT27, GT25 (except GT2505-V), or GT23 in any position other than the end position, set the terminating resistor to Disable. (For GT2505-V, GT21, and GS21-W-N, set OPEN.) Page 53 Terminating resistors of GOT

*4 For the terminating resistor of MODBUS/RTU master equipment, refer to the manual of MODBUS/RTU master equipment.

RS-422/485 connection diagram 5)

*1 The actual terminal layout on the MODBUS/RTU master equipment may differ from the example shown above. SDA/B(+/-) and RDA/ B(+/-) terminals can be separated from each other. In such cases, make sure to connect the cables and wires as described in the MODBUS/RTU master equipment manual.

*2 Some MODBUS/RTU master equipment don'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 "Enable".

When placing the GOT to the position other than the terminal, set the terminating resistor of the GOT to "Disable". Page 53 Terminating resistors of GOT

*4 For the terminating resistor of MODBUS/RTU master equipment, refer to the manual of MODBUS/RTU master equipment.

SG RSA RSB CSA CSB

SDA

SDB

RDA

RDB

1

6

2

7

5

3

8

4

9

(+)

(-)

*3

R

RSA RSB CSA CSB

SDA

SDB

RDA

RDB

SG

1

6

2

7

5

3

8

4

9

MODBUS /RTU master equipment side*1*2*4 GOT side(slave)*3

(1st) GOT side(slave)*3

(2nd)

SDA1

SDB1

RDA1

RDB1

SDA2

SDB2

RDA2

RDB2

SG

FG

1

2

3

4

5

6

7

8

9

10

(+)

(-)

SG

SDA1

SDB1

RDA1

RDB1

SDA2

SDB2

RDA2

RDB2

SG

FG

1

2

3

4

5

6

7

8

9

10

MODBUS /RTU master equipment side*1*2*4 GOT side(slave)*3

(1st) GOT side(slave)*3

(2nd)

7 MODBUS/RTU SLAVE CONNECTION 7.3 Connection Diagram 289

29

RS-422/485 connection diagram 6)

*1 The actual terminal layout on the MODBUS/RTU master equipment may differ from the example shown above. SDA/B(+/-) and RDA/ B(+/-) terminals can be separated from each other. In such cases, make sure to connect the cables and wires as described in the MODBUS/RTU master equipment manual.

*2 Some MODBUS/RTU master equipment don'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 "330 ". When placing the GOT to the

position other than the terminal, set the terminating resistor of the GOT to "OPEN". Page 53 Terminating resistors of GOT

*4 For the terminating resistor of MODBUS/RTU master equipment, refer to the manual of MODBUS/RTU master equipment. *5 The signals RSA, RSB, CSA, and CSB are not provided for GT2104-PMBD, GT2103-PMBD.

RS-422/485 connection diagram 7)

*1 The actual terminal layout on the MODBUS/RTU master equipment may differ from the example shown above. SDA/B(+/-) and RDA/ B(+/-) terminals can be separated from each other. In such cases, make sure to connect the cables and wires as described in the MODBUS/RTU master equipment manual.

*2 Some MODBUS/RTU master equipment don'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". Page 53 Terminating resistors of GOT

*4 For the terminating resistor of MODBUS/RTU master equipment, refer to the manual of MODBUS/RTU master equipment. *5 The signals RSA, RSB, CSA, and CSB are not provided for GT2104-PMBD, GT2103-PMBD. Return connection is not required.

SDA

SDB

RDA

RDB

SG

RSA

RSB

CSA

CSB

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG

*5

*5

*5

*5

SDA

SDB

RDA

RDB

SG

RSA

RSB

CSA

CSB

*5

*5

*5

*5

MODBUS /RTU master equipment side*1*2*4 GOT side(slave)*3

(1st) GOT side(slave)*3

(2nd)

SDA

SDB

RDA

RDB

SG

RSA

RSB

CSA

CSB

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG

*5

*5

*5

*5

SDA

SDB

RDA

RDB

SG

RSA

RSB

CSA

CSB

*5

*5

*5

*5

MODBUS /RTU master equipment side*1*2*4 GOT side(slave)*3

(1st) GOT side(slave)*3

(2nd)

0 7 MODBUS/RTU SLAVE CONNECTION 7.3 Connection Diagram

7

RS-422/485 connection diagram 8)

*1 Some MODBUS/RTU master equipment doesn't have SG. In this case, the wiring between GOT and SG is unnecessary. *2 Some MODBUS/RTU master 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 master equipment manual. *3 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". Page 53 Terminating resistors of GOT Set the 1pair/2pair signal selection switch to "2pair" when using the connection conversion adapter. Connection Conversion Adapter Users manual

*4 For the terminating resistor of MODBUS/RTU master equipment, refer to the manual of MODBUS/RTU master equipment.

RS-422/485 connection diagram 9)

*1 The actual terminal layout on the MODBUS/RTU master 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 master equipment manual.

*2 Some MODBUS/RTU master 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". Page 53 Terminating resistors of GOT Set the 1pair/2pair signal selection switch to "1pair" when using the connection conversion adapter. Connection Conversion Adapter Users manual

*4 For the terminating resistor of MODBUS/RTU master equipment, refer to the manual of MODBUS/RTU master equipment.

SDA

SDB

RDA

RDB

SG

RDA(+)

RDB(-)

SDA(+)

SDB(-)

SG

SDA

SDB

RDA

RDB

SG

MODBUS /RTU master equipment side*1*2*4 GOT side(slave)*3

(1st) GOT side(slave)*3

(2nd)

SDA

SDB

RDA

RDB

SG

(+)

(-)

SG

SDA

SDB

RDA

RDB SG

MODBUS /RTU master equipment side*1*2*4 GOT side(slave)*3

(1st) GOT side(slave)*3

(2nd)

7 MODBUS/RTU SLAVE CONNECTION 7.3 Connection Diagram 291

29

Precautions when preparing a cable Cable length The length of the RS-422/485 cable must be 1200m or less.

GOT side connector For the GOT side connector, refer to the following. Page 49 GOT connector specifications

MODBUS/RTU master equipment side connector Use the connector compatible with the MODBUS/RTU master equipment side module. For details, refer to the MODBUS/RTU master equipment user's manual.

Connecting terminating resistors GOT side When connecting a MODBUS/RTU master equipment to the GOT, a terminating resistor must be connected to the GOT. For GT27, GT25(Except GT2505-V), GT23 Set the terminating resistor using the terminating resistor setting switch. For GT2505-V, GT21, and GS21-W-N Set the terminating resistor using the terminating resistor selector. For GS21-W Since the terminating resistor is fixed to 330 , setting the terminating resistor is not necessary. For the procedure to set the terminating resistor, refer to the following. Page 53 Terminating resistors of GOT

MODBUS/RTU equipment side When connecting a MODBUS/RTU master equipment to the GOT, a terminating resistor must be connected to the MODBUS/ RTU master equipment. For details, refer to the MODBUS/RTU master equipment user's manual.

2 7 MODBUS/RTU SLAVE CONNECTION 7.3 Connection Diagram

7

7.4 GOT Side Settings Setting communication interface (Controller Setting) Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Select the following items and the detail setting is displayed. [Manufacturer]: [MODBUS] [Controller Type]: [MODBUS Master(GOT:Slave)] [I/F]: Interface to be used [Detail Setting]: Configure the settings according to the usage environment. Page 294 Communication detail settings

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

7 MODBUS/RTU SLAVE CONNECTION 7.4 GOT Side Settings 293

29

Communication detail settings Make the settings according to the usage environment.

*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.

If the communication with MODBUS/RTU master equipment is not established, some equipment which requires a delay longer than 3.5 character time may be connected. When connecting to MODBUS/RTU master equipment which requires a delay longer than 3.5 character time, adjust the send delay time.

Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting]after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) 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: 19200bps)

9600bps, 19200bps, 38400bps, 57600bps, 115200bps

Data Bit Set this item when change the data length used for communication with the connected equipment. (Default: 8bits)

7bit/8bit

Stop Bit Specify the stop bit length for communications. (Default: 1bit)

1bit/2bit

Parity Specify whether or not to perform a parity check, and how it is performed during communication. (Default: Even)

None Even Odd

Delay Time*1 Set this item to adjust the transmission timing of the communication request from the GOT. (Default: 0ms)

0 to 300ms

GOT Station Set the station No. of the GOT. (Default: 1)

1 to 247

32bit Storage Select the steps to store two words (32-bit data). (Default: LH Order)

LH Order/HL Order

= +Actual send delay time

Send delay time set in the communication detail setting 3.5 character time

Minimum interval for communication frame defined in MODBUS/RTU

4 7 MODBUS/RTU SLAVE CONNECTION 7.4 GOT Side Settings

7

7.5 MODBUS/RTU master equipment Side Settings

MODBUS/RTU master equipment For details of the MODBUS/RTU master equipment, refer to the manual of MODBUS/RTU master equipment to be used.

7.6 Function Code The following shows the message format for the MODBUS communication.

The GOT (slave) supports the following function codes.

*1 Only available to the loopback (sub function code 0x0000).

7.7 GOT (Slave) Operations for All Station Specification (Broadcast)

The all station specification (broadcast) operates when [0] is specified as the slave address in the request packet. The following describes the GOT (slave) operations for all station specification (broadcast) from the MODBUS/RTU master equipment. The GOT (slave) will not respond to the read-out requests specifying all stations from the MODBUS/RTU master equipment

(read-out disabled). The GOT (slave) will perform the write-in requests specifying all stations from the MODBUS/RTU master equipment but will

not respond. The GOT (slave) will not respond to the diagnosis requests specifying all stations from the MODBUS/RTU master

equipment (loopback disabled).

7.8 Device Range that Can Be Set For the device setting dialog and the device range that can be used on the GOT, refer to the following. Page 444 MODBUS ([MODBUS Master(GOT:Slave)])

Function code Function Number of devices that are 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

0x08*1 Diagnostics -

0x0F Write Multiple Coils 1 to 1968

0x10 Write Multiple Register 1 to 123

Address CRCFunction code Data

7 MODBUS/RTU SLAVE CONNECTION 7.5 MODBUS/RTU master equipment Side Settings 295

29

7.9 Precautions

Errors that occur in the GOT at MODBUS/RTU slave connection In MODBUS/RTU slave connection, contents of the message display, causes, and countermeasures when an error occurs in the GOT are described below. When the following errors occur, the GOT will generate a system alarm.

*1 This may occur even when the MODBUS/RTU slave is not connected.

Error codes (MODBUS Exception Codes) returned from GOT (slave) to MODBUS master equipment The GOT (slave) supports the following error codes (MODBUS Exception Codes) in respect to the request from the MODBUS master equipment. When the following errors occur, the GOT will not generate a system alarm. The description, causes and countermeasures for each error code are explained below.

Error codes issued in common in respect to request from master equipment

Error code issued in response to read request from master equipment

Error code issued in response to write request from master equipment

Error code issued when diagnosis occurs (function code 0x08)

Error code Contents of the message display Causes Countermeasures 309*1 Device reading error. Correct device. An error occurred when reading

consecutive devices. A device that is out of the monitor range is

specified at a place where consecutive device is specified, such as graph function or system information.

Correct so that a device No. in the monitor range is specified.

315*1 Device writing error. Correct device. Writing was executed to a device No. that is out of the monitor range.

Writing was executed to a write-prohibit device.

Review the write target device and the device No.

322*1 The specified device No. is out of range. Confirm the available device range.

A device read error occurs. The GOT accesses the device that is out of

range specified by the master station.

To take corrective actions, check the range that is allocated to the master station and range of the monitoring target device.

Error code (HEX)

Category Description Causes Countermeasures

0x01 - ILLEGAL FUNCTION A function code not supported by the GOT was received.

Use only function codes supported by GOT. Refer to the following for details on function codes supported by the GOT. Page 295 Function Code

Error code (HEX)

Category Description Causes Countermeasures

0x02 Read/Write ILLEGAL DATA ADDRESS An out-of-range device was accessed.

Check that the device being accessed is correct.

Error code (HEX)

Category Description Causes Countermeasures

0x02 Read/Write ILLEGAL DATA ADDRESS An out-of-range device was accessed.

Check that the device being accessed is correct.

0x03 Write ILLEGAL DATA VALUE The request packet (number of write points, number of write data bytes, and number of write data items) is inconsistent.

Check that a correct packet is sent from the master equipment.

Error code (HEX)

Category Description Causes Countermeasures

0x01 - ILLEGAL FUNCTION The GOT received an unsupported sub-function code.

Use only 0x0000 (loopback) for the sub-function codes.

6 7 MODBUS/RTU SLAVE CONNECTION 7.9 Precautions

7

Operation in which the GOT shifts to the offline mode Before performing operation in which the GOT shifts to the offline mode such as writing the package data, stop the communication between the GOT and the MODBUS/RTU master equipment. After shifting to the offline mode, the GOT cannot respond to the requests from the MODBUS/RTU master equipment. Even after the GOT returns from the offline mode, the communication may not be performed until the timeout time of the MODBUS/RTU master equipment side elapses.

7 MODBUS/RTU SLAVE CONNECTION 7.9 Precautions 297

29

MEMO

8 7 MODBUS/RTU SLAVE CONNECTION 7.9 Precautions

8

8 MODBUS/TCP SLAVE CONNECTION Page 299 Connectable Model List Page 300 System Configuration Page 301 GOT Side Settings Page 303 MODBUS/TCP Master Equipment Side Settings Page 303 Function Code Page 303 Device Range that Can Be Set Page 304 Precautions

8.1 Connectable Model List The GOT2000 series supports the slave function of the MODBUS/TCP communication that is the open FA network. Thus, the GOT can be connected with each MODBUS master equipment. For the MODBUS/TCP equipment validated by Mitsubishi Electric Corporation, refer to the following Technical Bulletin. List of Valid Devices Applicable for GOT2000 Series MODBUS Connection for Overseas (GOT-A-0170) For Technical Bulletins, go to the Mitsubishi Electric Factory Automation Global Website. www.MitsubishiElectric.com/fa

8 MODBUS/TCP SLAVE CONNECTION 8.1 Connectable Model List 299

30

8.2 System Configuration Connecting to MODBUS/TCP master equipment

*1 Connect the GOT to the MODBUS/TCP master equipment via a hub. Use cables, connectors, and hubs that meet the IEEE802.3 10BASE-T/100BASE-TX standards.

*2 When connecting GT2000 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.

*3 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 hub s has no logical limit for the number of cascades. For the limit, contact the switching hub manufacturer.

*4 Use the straight cable. *5 For details, refer to the MODBUS/TCP master equipment manual. *6 GT25-W, GT2505-V does not support the option device.

Controller Commu nication Type

Connection cable Exte rnal devi ce

Connection cable GOT*2 Number of connectable equipment

Cable model*4 Maximum segment length*3

Cable model Maximum segment length*3

Option device*6

GOT model

MODBUS/ TCP master equipment

Ethernet 100BASE-TX Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 5 or higher 10BASE-T

Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 3 or higher

100m Hub*1 100BASE-TX Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 5 or higher 10BASE-T

Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 3 or higher

100m - (Built into GOT)

When the ratio of master equipment to the GOT is N:1 16 or less (4 or less for GT21 or GS21) When the ratio of master equipment to the GOT is N:1 The following shows the number of GOTs for 1 master equipment Depends on the MODBUS/TCP master equipment used*5.

GT25- J71E71-100

MODBUS/TCP Slave, Gateway

Communication driver

GOTHub

Connection cable Connection cable

MODBUS/TCP master equipment

0 8 MODBUS/TCP SLAVE CONNECTION 8.2 System Configuration

8

8.3 GOT Side Settings Setting communication interface (Controller Setting) Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Select the following items and the detail setting is displayed. [Manufacturer]: [MODBUS] [Controller Type]: [MODBUS Master(GOT:Slave)] [I/F]: [Ethernet:Multi] When using the Ethernet communication unit (GT25-J71E71-100), also select [Ethernet:Multi]. [Detail Setting]: Configure the settings according to the usage environment. Page 302 Communication detail settings

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

8 MODBUS/TCP SLAVE CONNECTION 8.3 GOT Side Settings 301

30

Communication detail settings Make the settings according to the usage environment.

*1 When assigning the same driver to the multiple channels, in the communication drivers set as the second and following, the default value of [GOT Communication Port No.] becomes the earliest number in the vacant numbers of No. 6000 and later.

Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective.

GOT Ethernet Setting The GOT can be connected to a different network by configuring the following setting.

GOT IP address setting Set the following communication port setting. Standard port (When using GT25-W, port 1) Extension port (When using GT25-W, port 2)

GOT Ethernet common setting Set the following setting which is common to the standard port and the extension port, or port 1 and port 2. [Default Gateway] [Peripheral S/W Communication Port No.] [Transparent Port No.]

IP filter setting By configuring the IP filter setting, the access from the specific IP address can be permitted or shut off. For the detailed settings, refer to the following manual. Page 35 GOT Ethernet Setting

Item Description Range GOT Net No. Not used -

GOT Station Not used -

GOT Communication Port No. Set the GOT port No. for the connection with the Ethernet module. (Default: 502*1)

502 to 65534 (Except for 503 to 1023, 5011 to 5013 and 49153 to 49170)

Delay Time Set the delay time for reducing the load of the network/destination PLC. (Default: 0ms)

0 to 10000 (ms)

32bit Storage Select the steps to store two words (32-bit data). (Default: LH Order)

LH Order/HL Order

2 8 MODBUS/TCP SLAVE CONNECTION 8.3 GOT Side Settings

8

8.4 MODBUS/TCP Master Equipment Side Settings For details of the MODBUS/TCP master equipment, refer to the manual of MODBUS/TCP master equipment to be used.

8.5 Function Code The following shows the message format for the MODBUS communication.

The GOT (slave) supports the following function codes (sub function codes).

8.6 Device Range that Can Be Set For the device setting dialog and the device range that can be used on the GOT, refer to the following. Page 444 MODBUS ([MODBUS Master(GOT:Slave)])

Function code Function Number of devices that are 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

Address CRCFunction code Data

8 MODBUS/TCP SLAVE CONNECTION 8.4 MODBUS/TCP Master Equipment Side Settings 303

30

8.7 Precautions

Send delay "Send delay" is a setting used for low-speed devices that cannot respond when the send response is too fast. When "Send delay" is set with the GOT's communication devices detail settings, the "Send delay" is enabled for all master devices that are connected.

Errors that occur in the GOT at MODBUS/TCP slave connection In MODBUS/TCP slave connection, contents of the message display, causes, and countermeasures when an error occurs in the GOT are described below. When the following errors occur, the GOT will generate a system alarm.

*1 This may occur even when the MODBUS/TCP slave is not connected.

Error codes (MODBUS Exception Codes) returned from GOT (slave) to MODBUS master equipment The GOT (slave) supports the following error codes (MODBUS Exception Codes) in respect to the request from the MODBUS master equipment. When the following errors occur, the GOT will not generate a system alarm. The description, causes and countermeasures for each error code are explained below.

Error codes issued in common in respect to request from master equipment

Error code issued in response to read request from master equipment

Error code issued in response to write request from master equipment

Error code Contents of the message display Causes Countermeasures 309*1 Device reading error. Correct device. An error occurred when reading

consecutive devices. A device that is out of the monitor range is

specified at a place where consecutive device is specified, such as graph function or system information.

Correct so that a device No. in the monitor range is specified.

315*1 Device writing error. Correct device. Writing was executed to a device No. that is out of the monitor range.

Writing was executed to a write-prohibit device.

Review the write target device and the device No.

322*1 The specified device No. is out of range. Confirm the available device range.

A device read error occurs. The GOT accesses the device that is out of

range specified by the master station.

To take corrective actions, check the range that is allocated to the master station and range of the monitoring target device.

Error code (HEX)

Category Description Causes Countermeasures

0x01 - ILLEGAL FUNCTION A function code not supported by the GOT was received.

Use only function codes supported by GOT. Refer to the following for details on function codes supported by the GOT. Page 303 Function Code

Error code (HEX)

Category Description Causes Countermeasures

0x02 Read/Write ILLEGAL DATA ADDRESS An out-of-range device was accessed.

Check that the device being accessed is correct.

Error code (HEX)

Category Description Causes Countermeasures

0x02 Read/Write ILLEGAL DATA ADDRESS An out-of-range device was accessed.

Check that the device being accessed is correct.

0x03 Write ILLEGAL DATA VALUE The request packet (number of write points, number of write data bytes, and number of write data items) is inconsistent.

Check that a correct packet is sent from the master equipment.

4 8 MODBUS/TCP SLAVE CONNECTION 8.7 Precautions

PART 5 PROFIBUS

9 PROFIBUS DP CONNECTION

305

30

9 PROFIBUS DP CONNECTION Page 306 Connectable Model List Page 307 System Configuration Page 308 Connection Diagram Page 310 GOT Side Settings Page 312 Preparation of GSD File for GOT Page 313 PROFIBUS DP master equipment Side Settings Page 314 Device Range that Can Be Set Page 314 Precautions

9.1 Connectable Model List GOT2000 Series products support the slave function of PROFIBUS DP communication, the open FA network. Thus, the GOT can be connected with each PROFIBUS DP master.

BootOS version of GOT main unit Install the version N or later of BootOS so that the GOT supports the PROFIBUS DP connection. For the procedure to check the BootOS version and upgrade the version, refer to the following manuals. GT Designer3 (GOT2000) Screen Design Manual GOT2000 Series User's Manual (Utility)

6 9 PROFIBUS DP CONNECTION 9.1 Connectable Model List

9

9.2 System Configuration Connecting to PROFIBUS DP master equipment

*1 The maximum distance varies depending on the transmission speed. Confirm the specification on the PROFIBUS DP master equipment side.

*2 Install the communication module (ABCC-M40-DPV1, Type number: AB6910-B or AB6910-C) manufactured by HMS to the GT25- FNADP The communication module manufactured by HMS must be prepared by the user. For the communication module installation method, refer to the following manual. GOT2000 Series Field Network Adapter Unit Instruction Manual

*3 The number of connectable GOT modules (PROFIBUS DP slave equipment) to one PROFIBUS DP master equipment varies depending on the presence/absence of repeater units. Up to 9 repeater units can be used. When repeater units are not installed: Up to 32 GOT modules (PROFIBUS DP slave equipment) can be connected to each segment. When repeater units are installed: Up to 125 GOT modules (PROFIBUS DP slave equipment) can be connected to each segment.

*4 GT25-W, GT2505-V does not support the option device.

Controller Communication Type

Connection cable GOT Number of connectable equipment

Connection diagram number

Max. distance

Option device*4 model

PROFIBUS DP master equipment

PROFIBUS DP Page 308 PROFIBUS DP connection diagram 1)

1200m*1 GT25-FNADP*2 *3

PROFIBUS DP

Communication driver

PROFIBUS DP master equipment

GOT PROFIBUS DP slave equipment

Connection cable

GOT PROFIBUS DP slave equipment

9 PROFIBUS DP CONNECTION 9.2 System Configuration 307

30

9.3 Connection Diagram The following shows the specifications of the cables used to connect the GOT and the controller and the connection diagrams.

Recommended PROFIBUS DP cable and connectors

Cable specification Use the A type cable for PROFIBUS DP. For the specifications, refer to the table below.

Recommended cable

Recommended connectors

PROFIBUS DP Cable The figure below shows the connection diagram of PROFIBUS DP cables connecting the GOT and PLC.

PROFIBUS DP connection diagram 1)

*1 Connect a terminal resistor to the PROFIBUS DP equipment located at the end of a segment. When using the cable (6XV1830-0EH10) manufactured by SIEMENS, set to ON the terminal resistor switch provided in the cable connector.

Item specification Impedance 135 to 165 Ohm / 3 to 20 MHz

Capacity 30 pF/m maximum

Resistance 110 Ohm/km maximum

Conductor diameter 0.64 mm minimum

Conductor area 0.34 mm2 minimum

Manufacturer name

Model name Remarks

SIEMENS 6XV1830-0EH10 PROFIBUS cable having standard specifications

Manufacturer name

Model name Remarks

SIEMENS 6ES7 972-0BA52-0XA0 PROFIBUS DP bus connector (For wiring at 90, without PG port)

6ES7 972-0BB52-0XA0 PROFIBUS DP bus connector (For wiring at 90, with PG port)

6ES7 972-0BA60-0XA0 PROFIBUS DP bus connector (For wiring at 35, without PG port)

6ES7 972-0BB60-0XA0 PROFIBUS DP bus connector (For wiring at 35, with PG port)

PROFIBUS DP master equipment*1

6

3

8

5

GOT side (1st)

GOT side (2nd)*1

220

390

390

VPa +5V Power supply

RxD/TxD-P LineB(Red)

RxD/TxD-N LineA(Green)

DGND Data ground

6

3

8

5

6

3

8

5

220

390

390

VPa +5V Power supply

RxD/TxD-P LineB(Red)

RxD/TxD-N LineA(Green)

DGND Data ground

8 9 PROFIBUS DP CONNECTION 9.3 Connection Diagram

9

Precautions when preparing a cable Cable length For the Cable length, refer to the following. Page 307 System Configuration

GOT side connector (PROFIBUS DP slave equipment) For the GOT side connector, refer to the following. Manual of Anybus CompactCom M40 Network Communication Module by HMS

PROFIBUS DP master equipment side connector Use the connector compatible with the PROFIBUS DP master equipment side module. For details, refer to the PROFIBUS DP master equipment user's manual.

9 PROFIBUS DP CONNECTION 9.3 Connection Diagram 309

31

9.4 GOT Side Settings Setting communication interface (Controller Setting) Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Select the following items and the detail setting is displayed. [Manufacturer]: [PROFIBUS] [Controller Type]: [PROFIBUS DP] [I/F]: Interface to be used [Detail Setting]: Configure the settings according to the usage environment. Page 311 Communication detail settings

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

0 9 PROFIBUS DP CONNECTION 9.4 GOT Side Settings

9

Communication detail settings Make the settings according to the usage environment.

*1 Align the setting with the station No. of the slave equipment set on the master equipment side. *2 Align the setting with the specification of the PROFIBUS DP master equipment.

Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective.

Item Description Range Station No.*1 Set the station No.

(Default: 1) 1 to 125

Format*2 Set the following format. Format 1: Big endian Format 2: Little endian (Default: 1)

1, 2

9 PROFIBUS DP CONNECTION 9.4 GOT Side Settings 311

31

9.5 Preparation of GSD File for GOT Prepare the GSD file for the GOT to make available the configuration tool on the PROFIBUS DP master equipment side.

How to acquire GSD file for GOT

Acquisition from the DVD-ROM The GSD file for GOT (GOT_0F39.gsd) is stored in the following folder of the DVD-ROM (GT Works3 Ver. 1.130L or later). Disk5ConfigurationFilePROFIBUS DPGOT_0F39.gsd Disk5ConfigurationFilePROFIBUS DPGOT.bmp *: GOT.bmp is a bitmap image of GOT.

2 9 PROFIBUS DP CONNECTION 9.5 Preparation of GSD File for GOT

9

9.6 PROFIBUS DP master equipment Side Settings This section explains how to set the PROFIBUS DP master equipment.

PROFIBUS DP master equipment For the details of the PROFIBUS DP master equipment setting method, refer to the manual of the used PROFIBUS DP master equipment.

Installing the GSD file for GOT Install the GSD file for GOT to the configuration tool on the PROFIBUS DP master equipment side, and set the GOT as slave equipment. For how to acquire the GSD file for GOT, refer to the following. Page 312 Preparation of GSD File for GOT

Communication configuration Set the following communication parameters using the configuration tool on the PROFIBUS DP master equipment side.

*1 Make sure that the station No. does not overlap. *2 Align the setting of Station No. on the GOT side with the station No. of the slave equipment.

Page 310 GOT Side Settings

Item Setting range/Setting method Master equipment Station No.*1 0 to 125

Transmission speed 9.6kbps 19.2kbps 45.45kbps 93.75kbps 187.5kbps 500kbps 1.5Mbps 12Mbps

Slave equipment Station No.*1*2 0 to 125

Device setting For the setting method, refer to the following manual. Manual of PROFIBUS DP master equipment

9 PROFIBUS DP CONNECTION 9.6 PROFIBUS DP master equipment Side Settings 313

31

9.7 Device Range that Can Be Set For the device setting dialog and the device range that can be used on the GOT, refer to the following. Page 447 PROFIBUS ([PROFIBUS DP])

9.8 Precautions

GSD file for GOT Do not edit the GSD file for GOT. Edition may cause communication errors.

Type number of the communication module manufactured by HMS Use the communication module having the type number described in the following manual. GOT2000 Series Field Network Adapter Unit Instruction Manual

Software version of the communication module manufactured by HMS For the software version of the connectable communication module manufactured by HMS, refer to the following technical news. List of PROFIBUS DP-compliant Equipment Validated to Operate with the GOT2000 Series (GOT-A-0083)

Installation of the field network adapter unit (GT25-FNADP) The field network adapter unit (GT25-FNADP) can be installed only at the top stage of the GOT. Page 47 Precautions when installing units on top of one another

4 9 PROFIBUS DP CONNECTION 9.7 Device Range that Can Be Set

PART 6 CLPA

10 SLMP CONNECTION

11 CC-Link IE Field NETWORK BASIC CONNECTION

315

31

10 SLMP CONNECTION Page 316 Connectable Model List Page 317 System Configuration Page 318 GOT Side Settings Page 324 SLMP Equipment Side Settings Page 324 Device Range that Can Be Set Page 324 Precautions

10.1 Connectable Model List GOT2000 Series products support the master function of SLMP communication, the open FA network. Thus, the GOT can be connected with each SLMP server. For the SLMP-compatible equipment validated by Mitsubishi Electric Corporation, refer to the following Technical Bulletin. List of SLMP-compatible Equipment Validated to Operate with the GOT2000 Series (GOT-A-0153) For Technical Bulletins, go to the Mitsubishi Electric Factory Automation Global Website. www.MitsubishiElectric.com/fa

6 10 SLMP CONNECTION 10.1 Connectable Model List

10

10.2 System Configuration Connecting to SLMP equipment

*1 Connect the GOT to the SLMP equipment via a hub. Use cables, connectors, and hubs that meet the IEEE802.3 10BASE-T/100BASE-TX/1000BASE-T standards.

*2 When connecting GT2000 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.

*3 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.

*4 Use the straight cable. *5 For details, refer to the SLMP equipment manual. *6 GT25-W, GT2505-V does not support the option device.

Controller Commu nication Type

Connection cable External device

Connection cable GOT*2 Number of connectable equipment

Cable model*4

Maximum segment length*3

Cable model Maximum segment length*3

Option device*6 GOT model

SLMP equipment

Ethernet 1000BASE-T 100BASE-TX Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 5 or higher 10BASE-T

Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 3 or higher

100m Hub*1 1000BASE-T 100BASE-TX Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 5 or higher 10BASE-T

Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 3 or higher

100m - (Built into GOT) When SLMP equipment:GOT is N:1 The number of SLMP equipment for 1 GOT is TCP: 128 or less. When SLMP equipment:GOT is 1:N The following shows the number of GOTs for 1 SLMP equipment Depends on the SLMP equipment used.*5

GT25-J71E71-100

GOTHub

Connection cable Connection cable

SLMP equipment

10 SLMP CONNECTION 10.2 System Configuration 317

31

10.3 GOT Side Settings Setting communication interface (Controller Setting) Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Select the following items and the detail setting is displayed. [Manufacturer]: [CLPA] [Controller Type]: [SLMP] [I/F]: [Ethernet:Multi] When using the Ethernet communication unit (GT25-J71E71-100), also select [Ethernet:Multi]. [Detail Setting]: Configure the settings according to the usage environment. Page 319 Communication detail settings

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting].For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

8 10 SLMP CONNECTION 10.3 GOT Side Settings

10

Communication detail settings Make the settings according to the usage environment.

*1 Set different values for [GOT Station] of [Detail Setting] and [Station] of [Connected Ethernet Controller Setting]. Page 321 Connected Ethernet controller setting

*2 Pay attention to the following items for read/write points. Set the points to be processed at one-time communication. The point is in word device units. The point is to be 16 times of the set value for the bit device. The points could be less than the set value when UDP protocol or ASCII code are used. Refer to the following Technical News for details. List of SLMP-compatible Equipment Validated to Operate with the GOT2000 Series (GOT-A-0153)

*3 When assigning the same driver to the multiple channels, in the communication drivers set as the second and following, the default value of [GOT Communication Port No.] becomes the earliest number in the vacant numbers of No. 6000 and later.

Item Description Range GOT Net No. Set the network No. of the GOT.

(Default: 1) 1 to 239

GOT Station*1 Set the station No. of the GOT. (Default: 18)

1 to 120

GOT Communication Port No. Set the GOT port No. for the connection with the Ethernet module. (Default: 5031*3)

1024 to 5010, 5014 to 49152, 49171 to 65534 (Except for 49153 to 49170)

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: 3times)

0 to 5times

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)

1 to 90sec

Delay Time Set the delay time for reducing the load of the network/destination PLC. (Default: 0ms)

0 to 10000 (ms)

Message Format Set the message format. (Default: 4E frame)

QnA compatible 3E frame, 4E frame

Communication data code Set the communication data code. (Default: Binary code)

ASCII code, Binary code

Device read points*2 Set the device read points. (Default: 960 points)

1 to 960 points

Device write points*2 Set the device write points. (Default: 960 points)

1 to 960 points

Device read random points*2 Device read random points (Default: 0 point)

0 to 192 points

Device write random points*2 Device write random points (Default: 0 point)

0 to 160 points

10 SLMP CONNECTION 10.3 GOT Side Settings 319

32

Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective.

GOT Ethernet Setting The GOT can be connected to a different network by configuring the following setting.

GOT IP address setting Set the following communication port setting. Standard port (When using GT25-W, port 1) Extension port (When using GT25-W, port 2)

GOT Ethernet common setting Set the following setting which is common to the standard port and the extension port, or port 1 and port 2. [Default Gateway] [Peripheral S/W Communication Port No.] [Transparent Port No.]

IP filter setting By configuring the IP filter setting, the access from the specific IP address can be permitted or shut off. For the detailed settings, refer to the following manual. Page 35 GOT Ethernet Setting

0 10 SLMP CONNECTION 10.3 GOT Side Settings

10

Connected Ethernet controller setting

*1 Set different values for [GOT Station] of [Detail Setting] and [Station] of [Connected Ethernet Controller Setting]. Page 319 Communication detail settings

*2 Set 125 to [Station] to access the master station of the CC-Link IE TSN network.

Item Description Range Host The host is displayed.

It refers to a station that can be connected without setting a station number. (The host is indicated with an asterisk (*).)

Net No. Set the network No. of the connected Ethernet module. (Default: 1)

1 to 239

Station*1 Set the station No. of the connected Ethernet module. (Default: 1)

1 to 120, 125 *2

Unit Type SLMP (fixed)

IP Address Set the IP address of the connected Ethernet module. (Default: 1.1.1.1)

SLMP equipment side IP address

Port No. Set the port number of the SLMP compatible device. (Default: 49152)

1 to 65535

Communication format UDP, TCP (Default: UDP)

Adjust the setting with the communication format of the SLMP compatible device.

10 SLMP CONNECTION 10.3 GOT Side Settings 321

32

[Connected Ethernet Controller Setting] for GT21 and GS21 Effective range of [Connected Ethernet Controller Setting] Only [1] to [4] of [Connected Ethernet Controller Setting] can be used for GT21 and GS21. If [5] onwards are used, the settings are invalid on GT21 and GS21. [Host] setting Set [Host] within the range from [1] to [4] in [Connected Ethernet Controller Setting].

Changing the host with GOT module The host can be changed by the GOT module Utility. For details of settings, refer to the following. GOT2000 Series User's Manual (Utility)

Only [1] to [4] can be used.

2 10 SLMP CONNECTION 10.3 GOT Side Settings

10

Routing parameter setting Up to 64 [Transfer Network No.]s can be set. However, the same transfer network number cannot be set twice or more (multiple times). Therefore, the one that can access to other station from there quest source host GOT is 64 kinds of [Transfer NetworkNo.]s.

Routing parameter setting When communicating within the host network, routing parameter setting is unnecessary. For details of routing parameters, refer to the following manual. Manuals of SLMP equipment

*1 When 125 is set to [Relay Station No.], the master station of CC-Link IE TSN can be accessed.

Routing parameter setting of relay station Routing parameter setting may also be necessary for the relay station. For the setting, refer to the following. Manuals of SLMP equipment Parameter reflection function of MELSOFT Navigator The color of the cells for the items which are reflected to GT Designer3 from MELSOFT Navigator changes to green. Set items, which are displayed in green cells, from the MELSOFT Navigator. When the settings of Transfer network No., Relay network No. or Relay station No. are reflected to the parameter from the MELSOFT Navigator, those settings are added. Items set in advance are not deleted. However, if the target network No. overlaps, the item set in advance is overwritten. The routing information is used manually by the user when the data is created. Therefore, after changing the network configuration by MELSOFT Navigator, create a routing information again. For details of the creation of the routing information, refer to the MELSOFT Navigator help.

Item Range Transfer Network No. 1 to 239

Relay Network No. 1 to 239

Relay Station No. 0 to 120, 125 *1

10 SLMP CONNECTION 10.3 GOT Side Settings 323

32

10.4 SLMP Equipment Side Settings Refer to the following manual for the setting of the SLMP compatible devices. Manuals of SLMP equipment

10.5 Device Range that Can Be Set For the device setting dialog and the device range that can be used on the GOT, refer to the following. Page 450 CLPA ([SLMP])

10.6 Precautions

Replacing SLMP compatible device After replacing an external device or a SLMP compatible device due to failure and so on, the devices may not communicate by changing the MAC address. (When replaced with a device that has the same IP address) When a device in the Ethernet network is replaced, restart all devices in the network.

The deviation between MC protocol and SLMP protocol When using our products used in MC protocol for SLMP protocol, there is a difference between the corresponding commands. Refer to the following manual and check if they are convertible. SLMP Reference Manual

Setting the message format When the message format setting is not consistent with the communication frame type, monitoring may not be performed properly. Set the message format according to the communication frame type of the SLMP-compatible equipment. ST type: QnA compatible 3E frame MT type: 4E frame For details of the communication frame of the SLMP-compatible equipment, refer to the following. Manuals of SLMP equipment For setting the message format, refer to the following. Page 319 Communication detail settings

4 10 SLMP CONNECTION 10.4 SLMP Equipment Side Settings

11

11 CC-Link IE Field NETWORK BASIC CONNECTION

Page 325 Connectable Model List Page 326 System Configuration Page 328 GOT Side Settings Page 331 Master Station Side Settings Page 331 Device Range that Can Be Set Page 331 Precautions

11.1 Connectable Model List The GOT2000 series supports the remote station function of the CC-Link IE Field Network Basic communication, which is an open FA network. Therefore, the GOT2000 series can communicate with various CC-Link IE Field Network Basic master stations. For the CC-Link IE Field Network Basic master stations validated by Mitsubishi Electric Corporation, refer to the following. List of CC-Link IE Field Network Basic-compatible Equipment Validated to Operate with the GOT2000 Series (GOT-A- 0149) For Technical Bulletins, go to the Mitsubishi Electric Factory Automation Global Website. www.MitsubishiElectric.com/fa

11 CC-Link IE Field NETWORK BASIC CONNECTION 11.1 Connectable Model List 325

32

11.2 System Configuration When connecting to the CC-Link IE Field Network Basic master station

When connecting to one master station

*1 GT25-W, GT2505-V does not support the option device.

Controller Communication Type

Connection cable GOT (remote station) Number of connectable equipment

Cable model Maximum segment length

Option device *1 GOT model

CC-Link IE Field Network Basic master station

Ethernet 100BASE-TX Shielded twisted pair cable (STP) of category 5 or higher

100m - (Built into GOT) 1 GOT for 1 master station

GT25-J71E71-100

GOT

Connection cable

CC-Link IE Field Network Basic master station

6 11 CC-Link IE Field NETWORK BASIC CONNECTION 11.2 System Configuration

11

When multiple GOTs (remote stations) are connected to one master station

*1 Use hubs that satisfy the following conditions. Conform to the IEEE802.3 (100BASE-TX) standard. Include Auto MDI/MDI-X. Include an automatic negotiation function. Switching hub (layer 2 switch) (Do not use repeater hubs)

*1 Connect the GOT to the CC-Link IE Field Network Basic master station via a hub. Use cables, connectors, and hubs that meet the IEEE802.3 100BASE-TX standards.

*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. 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.

*3 Use the straight cable. *4 CC-Link IE Field Network Basic communication does not support connection beyond routers. *5 GT25-W, GT2505-V does not support the option device.

Controller Commun ication Type

Connection cable External device

Connection cable GOT (remote station) Number of connectable equipment

Cable model*3

Maximum segment length*2

Cable model Maximum segment length*2

Option device*5

GOT model

CC-Link IE Field Network Basic master station

Ethernet*4 100BASE-TX Shielded twisted pair cable (STP) of category 5 or higher

100m Hub*1 100BASE-TX Shielded twisted pair cable (STP) of category 5 or higher

100m - (Built into GOT) Up to 64 GOTs (remote stations) for 1 master station

GT25-J71E71-100

GOTHub*1

Connection cable Connection cable

CC-Link IE Field Network Basic master station

GOT

Connection cable

11 CC-Link IE Field NETWORK BASIC CONNECTION 11.2 System Configuration 327

32

11.3 GOT Side Settings Setting communication interface (Controller Setting) Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Select the following items and the detail setting is displayed. [Manufacturer]: [CLPA] [Controller Type]: [CC-Link IE Field Network Basic] [I/F]: [Ethernet:Multi] When using the Ethernet communication unit (GT25-J71E71-100), also select [Ethernet:Multi]. [Detail Setting]: Configure the settings according to the usage environment. Page 329 Communication detail settings

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting].For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

8 11 CC-Link IE Field NETWORK BASIC CONNECTION 11.3 GOT Side Settings

11

Communication detail settings Make the settings according to the usage environment.

Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective. Port No. [61451] For CC-Link IE Field Network Basic, the port No. [61451] is used as a port for device detection. When the port No. [61451] is used for other communication functions, CC-Link IE Field Network Basic connection cannot be used.

Item Description Range GOT Net No. Not used -

GOT Station Not used -

GOT Communication Port No. Displays the port No. that is used by cyclic transmission of CC-Link IE Field Network Basic for the GOT.

61450 (fixed)

Output HOLD/CLEAR setting Select whether the GOT holds or clears its device value (output data of the master and remote stations(GOT)) when the master station stops running. (Default: HOLD)

HOLD, CLEAR

11 CC-Link IE Field NETWORK BASIC CONNECTION 11.3 GOT Side Settings 329

33

GOT Ethernet Setting The GOT can be connected to a different network by configuring the following setting.

GOT IP address setting Set the following communication port setting. Standard port (When using GT25-W, port 1) Extension port (When using GT25-W, port 2)

GOT Ethernet common setting Set the following setting which is common to the standard port and the extension port, or port 1 and port 2. [Default Gateway] [Peripheral S/W Communication Port No.] [Transparent Port No.]

IP filter setting By configuring the IP filter setting, the access from the specific IP address can be permitted or shut off. For the detailed settings, refer to the following manual. Page 35 GOT Ethernet Setting

0 11 CC-Link IE Field NETWORK BASIC CONNECTION 11.3 GOT Side Settings

11

11.4 Master Station Side Settings For the settings of the CC-Link IE Field Network Basic master station, refer to the following manual. Manual for CC-Link IE Field Network Basic master station

11.5 Device Range that Can Be Set For the device setting dialog and the device range that can be used on the GOT, refer to the following. Page 455 CLPA ([CC-Link IE Field Network Basic])

11.6 Precautions

Port No. [61451] For CC-Link IE Field Network Basic, the port No. [61451] is used as a port for device detection. When the port No. [61451] is used for other communication functions, CC-Link IE Field Network Basic connection cannot be used.

Errors that occurs in the GOT at CC-Link IE Field Network Basic connection In CC-Link IE Field Network Basic connection, contents of the message display, causes, and countermeasures when an error occurs in the GOT are described below.

*1 May occurs even if CC-Link IE Field Network connection is not used. *2 Occurs only when CC-Link IE Field Network connection is used.

Network errors that occurs in CC-Link IE Field Network Basic connection In CC-Link IE Field Network Basic connection, contents of the message display, causes, and countermeasures for the following network errors are described below.

*1 Occurs only when CC-Link IE Field Network connection is used.

Response performance of the GOT The GOT carries out many object functions as well as CC-Link IE Field Network Basic connection so that the response performance for the master station may deteriorate. If this occurs, adjust the link scan time or timeout time at the master station side The following setting values are recommended.

Error code Contents of the message display Causes Countermeasures 322*1 The specified device No. is out of range.

Confirm the available device range. A device read error occurs. The GOT accesses the device that is out of

range specified by the master station.

To take corrective actions, check the range that is allocated to the master station and range of the monitoring target device.

402*1 The specified device No. is out of range. Confirm the available device range.

When the GOT is turned on, the master station is powered off.

Start the master station, and then turn on the GOT.

496*2 Settings for the GOT is not satisfied operation conditions of the communication driver.

Unusable IP address in CC-Link IE Field Network Basic is set.

The port No. 61451 that is used in CC-Link IE Field Network Basic is used by other functions.

Set the IP address within the range of 0.0.0.1 to 223.255.255.254.

When setting the IP address and subnet mask to each Ethernet I/F, set the network differently from each other.

Change the port No. of the function that uses the port No. 61451.

Error code Contents of the message display Causes Countermeasures 854*1 The master station is duplicated in the same

network. The master station is duplicated in the same network.

Correct it so that one master station is in the same network.

855*1 Parallel-off status Waiting for the request from the master station

Confirm the status of the master station.

Model Recommendation value of link scan time/timeout time GT27 50 ms and more

GT25

GT23 150 ms and more

11 CC-Link IE Field NETWORK BASIC CONNECTION 11.4 Master Station Side Settings 331

33

MEMO

2 11 CC-Link IE Field NETWORK BASIC CONNECTION 11.6 Precautions

PART 7 CONNECTIONS TO PERIPHERAL EQUIPMENT

12 CONNECTION TO SOUND OUTPUT UNIT

13 CONNECTION TO EXTERNAL I/O DEVICE

14 BAR CODE READER CONNECTION

15 PC REMOTE CONNECTION

16 GOT Mobile CONNECTION

17 VNC SERVER CONNECTION

18 VIDEO, HDMI, AND RGB CONNECTION

19 PRINTER CONNECTION

20 MULTIMEDIA CONNECTION

21 RFID CONNECTION

22 WIRELESS LAN CONNECTION

333

33

12 CONNECTION TO SOUND OUTPUT UNIT Page 334 Connectable Model List Page 334 System Configuration Page 335 GOT Side Settings Page 336 Precautions

12.1 Connectable Model List For applicable speakers, refer to the following Technical Bulletin. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160) For Technical Bulletins, go to the Mitsubishi Electric Factory Automation Global Website. www.MitsubishiElectric.com/fa

12.2 System Configuration Connecting to sound output unit

*1 GT25-W incorporates GT15-SOUT. *2 GT2505-V does not support the option device.

System configuration between the GOT and PLC For the system configuration between the GOT and PLC, refer to each chapter. GOT2000 Series Connection Manual (Mitsubishi Electric Product) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 1) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 2) For GT Works3 Version1 GOT2000 Series Connection Manual (Microcomputer, MODBUS, Products, Peripherals) For GT Works3 Version1

Speaker Connection cable GOT PLC Number of connectable equipment

Model name Option device*1*2

Model

For applicable speakers, refer to the following Technical News. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

GT15-SOUT For the system configuration between the GOT and PLC, refer to each chapter.

1 speaker for 1 GOT

Extended function OS

Sound output Connection type dependent

Communication driver

PLCGOTSpeaker

Varies according to the connection type.

Varies according to the speaker's specifications.

Connection cable

4 12 CONNECTION TO SOUND OUTPUT UNIT 12.1 Connectable Model List

12

12.3 GOT Side Settings Setting communication interface

Controller setting Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set [Manufacturer], [Controller Type], [I/F], and [Detail Setting] according to the controller used.

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [II/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

Sound output unit setting

1. Select [Common] [Peripheral Setting] [Sound Output] from the menu.

2. Set the interface to which the sound output unit is connected.

3. When you have completed the settings, click the [OK] button.

2.

3.

Click!

2.

Click!

12 CONNECTION TO SOUND OUTPUT UNIT 12.3 GOT Side Settings 335

33

Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective.

12.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 (GOT2000) Screen Design Manual

6 12 CONNECTION TO SOUND OUTPUT UNIT 12.4 Precautions

13

13 CONNECTION TO EXTERNAL I/O DEVICE Page 337 Connectable Model List Page 338 System Configuration Page 340 Connection Diagram Page 352 GOT Side Settings Page 353 Precautions

13.1 Connectable Model List The following table shows the connectable models.

*1 Varies with the connected type.

Series Clock Connectable GOT Refer to External I/O device *1 Page 338 Connecting to the external I/O device

13 CONNECTION TO EXTERNAL I/O DEVICE 13.1 Connectable Model List 337

33

13.2 System Configuration Connecting to the external I/O device

When inputting and outputting

*1 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.

*2 When the connector/terminal block converter module is used, the maximum input points are 64 points. *3 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.)

*4 GT25-W, GT2505-V does not support the option device.

Name Connection cable 1) Connector/terminal block converter module*1*2

Connection cable 2) GOT*3

Connection diagram number

Connection diagram number

Option device*4 Model

General input device (Push button, etc.) Operation panel General output device (Lamp, relay)

Page 343 Connection diagram 3)

A6TBY36-E Page 343 Connection diagram 3)

Page 340 Connection diagram 1)

GT15-DIO

Page 344 Connection diagram 4)

A6TBY54-E Page 344 Connection diagram 4)

Page 345 Connection diagram 5)

A6TBY36-E Page 345 Connection diagram 5)

Page 341 Connection diagram 2)

GT15-DIOR

Page 346 Connection diagram 6)

A6TBY54-E Page 346 Connection diagram 6)

Extended function OS

External I/O /Operation panel

GOTConnection cable 1)

Connection cable 2)

Connector/terminal block convertor module

General input device (Push button,etc.)

General output device (Lamp, relay)

Operation panel

DC power supply

Connection cable 1)

8 13 CONNECTION TO EXTERNAL I/O DEVICE 13.2 System Configuration

13

When only inputting

*1 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.

*2 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.)

*3 GT25-W, GT2505-V does not support the option device.

External device Connection cable*1 GOT*2

Name Connection diagram number Connection diagram number Option device*3 Model Operation panel Page 348 Connection diagram 8) Page 347 Connection diagram 7) GT15-DIO

Page 350 Connection diagram 10) Page 349 Connection diagram 9) GT15-DIOR

Extended function OS

External I/O /Operation panel

Operation panel GOT

Connection cable

DC power supply

13 CONNECTION TO EXTERNAL I/O DEVICE 13.2 System Configuration 339

34

13.3 Connection Diagram Connection cable between external I/O unit and connector/ terminal block converter module 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.

For GT15-DIO Connection diagram 1)

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.

XD00 XD01 XD02 XD03 XD04 XD05 XD06 XD07

18

43

19

44

20

45

21

46

22

47

23

48

24

49

25

50

14

39

15

40

16

41

17

42

6

31

7

32

8

33

9

34

10

35

11

36

12

37

13

38

30

4

3

2

1

29

28

27

26

5

B20

A20

B19

A19

B18

A18

B17

A17

XSCN00 XSCN01 XSCN02 XSCN03 XSCN04 XSCN05 XSCN06 XSCN07

YD00 YD01 YD02 YD03 YD04 YD05 YD06 YD07 YD08 YD09 YD0A YD0B YD0C YD0D YD0E YD0F

24V 24V 24V

0V 0V

Empty Empty Empty

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

External I/O unit side Terminal block converter side

0 13 CONNECTION TO EXTERNAL I/O DEVICE 13.3 Connection Diagram

13

For GT15-DIOR Connection diagram 2)

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.

XD00 XD01 XD02 XD03 XD04 XD05 XD06 XD07

XSCN00 XSCN01 XSCN02 XSCN03 XSCN04 XSCN05 XSCN06 XSCN07

YD00 YD01 YD02 YD03 YD04 YD05 YD06 YD07 YD08 YD09 YD0A YD0B YD0C YD0D YD0E YD0F

24V 24V 24V

0V 0V

Empty Empty Empty

18

43

19

44

20

45

21

46

22

47

23

48

24

49

25

50

14

39

15

40

16

41

17

42

6

31

7

32

8

33

9

34

10

35

11

36

12

37

13

38

30

4

3

2

1

29

28

27

26

5

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

External I/O unit side Terminal block converter side

13 CONNECTION TO EXTERNAL I/O DEVICE 13.3 Connection Diagram 341

34

Connector specifications

*1 The former product PCS-E50LA can also be used.

Precautions when preparing a cable 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.

GOT side connector For the GOT side connector, refer to the following. Page 49 GOT connector specifications

No. Name Model name Manufacturer 1) Connector PCR-E50FS+

(GT15-DIO) Honda Tsushin Kogyo Co., Ltd.

PCS-E50FS+ (GT15-DIOR)

2) Connector cover PCS-E50LPA+R *1

3) 4)

Connector (with a cover)

A6CON1 Mitsubishi Electric Corporation

5) Connector FCN-361J040-AU FUJITSU COMPONENT LIMITED

6) Connector cover FCN-360C040-B

7) Cable UL 2464 AWG28 or equivalent -

1) 2) 3) 4)5)

2 13 CONNECTION TO EXTERNAL I/O DEVICE 13.3 Connection Diagram

13

Connection diagram between connector/terminal block converter module and operation panel The connection cable among the user-created 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 3) When using A6TBY36-E connector/terminal block module

User-created original operation panel

B20 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

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

0V

10 12 14 16 18 1A 1C 1E 0V1F1D1B1917151311

24V

0V

A6TBY36-E

24V

24VLoad : Lamp,relay,etc.

XD00 XD01 XD02 XD03 XD04 XD05 XD06 XD07 70 71

61

51

41

31

11

21

60

50

40

30

20

10

00 01

72

62

52

42

32

12

02

22

73

63

53

43

33

13

03

23

74

64

54

44

34

14

04

24

75

65

55

45

35

15

05

25

76

66

56

46

36

16

06

26

77

67

57

47

37

17

07

27

XSCN07

XSCN06

XSCN05

XSCN04

XSCN03

XSCN02

XSCN01

XSCN00

Load Load

Load Load

Load Load Load Load

Load Load

Load Load

Load Load Load Load

13 CONNECTION TO EXTERNAL I/O DEVICE 13.3 Connection Diagram 343

34

Connection diagram 4) When using A6TBY54-E connector/terminal block module

B20 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

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

0V

0V-C-C-C-C-C -C-C-C-C

A6TBY54-E

24V

0V-C-C-C-C-C -C-C-C-C

12 13

14 15

16 17

18 19

1A 1B

1C 1D

1E 1F

10 11 24V

XD00 XD01 XD02 XD03 XD04 XD05 XD06 XD07 70 71

61

51

41

31

11

21

60

50

40

30

20

10

00 01

72

62

52

42

32

12

02

22

XSCN07

XSCN06

XSCN05

XSCN04

XSCN03

XSCN02

XSCN01

XSCN00

73

63

53

43

33

13

03

23

74

64

54

44

34

14

04

24

75

65

55

45

35

15

05

25

76

66

56

46

36

16

06

26

77

67

57

47

37

17

07

27

User-created original operation panel

DC24VLoad : Lamp,relay,etc.

Load Load

Load Load

Load Load

Load Load

Load Load

Load Load

Load Load

Load Load

4 13 CONNECTION TO EXTERNAL I/O DEVICE 13.3 Connection Diagram

13

For GT15-DIOR Connection diagram 5) When using A6TBY36-E connector/terminal block module

B20 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

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

0V

10 12 14 16 18 1A 1C 1E 0V1F1D1B1917151311

24V

0V

A6TBY36-E

24V

XD00 XD01 XD02 XD03 XD04 XD05 XD06 XD07 70 71

61

51

41

31

11

21

60

50

40

30

20

10

00 01

72

62

52

42

32

12

02

22

XSCN07

XSCN06

XSCN05

XSCN04

XSCN03

XSCN02

XSCN01

XSCN00

73

63

53

43

33

13

03

23

74

64

54

44

34

14

04

24

75

65

55

45

35

15

05

25

76

66

56

46

36

16

06

26

77

67

57

47

37

17

07

27

User-created original operation panel

DC24VLoad : Lamp,relay,etc.

Load Load Load Load Load Load Load Load Load Load Load Load Load Load Load Load

13 CONNECTION TO EXTERNAL I/O DEVICE 13.3 Connection Diagram 345

34

Connection diagram 6) When using A6TBY54-E connector/terminal block module

B20 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

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

0V

0V-C-C-C-C-C -C-C-C-C

A6TBY54-E

24V

0V-C-C-C-C-C -C-C-C-C

12 13

14 15

16 17

18 19

1A 1B

1C 1D

1E 1F

10 11 24V

XD00 XD01 XD02 XD03 XD04 XD05 XD06 XD07 70 71

61

51

41

31

11

21

60

50

40

30

20

10

00 01

72

62

52

42

32

12

02

22

XSCN07

XSCN06

XSCN05

XSCN04

XSCN03

XSCN02

XSCN01

XSCN00

73

63

53

43

33

13

03

23

74

64

54

44

34

14

04

24

75

65

55

45

35

15

05

25

76

66

56

46

36

16

06

26

77

67

57

47

37

17

07

27

User-created original operation panel

DC24VLoad : Lamp,relay,etc.

Load Load

Load Load

Load Load

Load Load Load Load

Load Load

Load Load

Load Load

6 13 CONNECTION TO EXTERNAL I/O DEVICE 13.3 Connection Diagram

13

Connection cable between external I/O unit and operation panel 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 7)

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.

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 6 31 7 32 8 33 9 34 10 35 11 36 12 37 13 38 30 4 3 2 1 29 28 27 26 5

DC24V

External I/O unit side Original operation panel

Cable for connecting an external input power supply

13 CONNECTION TO EXTERNAL I/O DEVICE 13.3 Connection Diagram 347

34

Connection diagram 8) For 16-point input

For 128-point input*1

*1 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).

*2 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

XSCN00 XSCN01 XSCN02 XSCN03 XSCN04 XSCN05 XSCN06 XSCN07

X000X010X020X030X040X050X060X070

X001

X002

X003

X004

X005

X006

X007

X008

X009

X00A

X00B

X00C

X00D

X00E

X00F

*2

XD00

XD01

XD02

XD03

XD04

XD05

XD06

XD07

XD08

XD09

XD0A

XD0B

XD0C

XD0D

XD0E

XD0F

XSCN00

XSCN01

XSCN02

XSCN03

XSCN04

XSCN05

XSCN06

XSCN07

8 13 CONNECTION TO EXTERNAL I/O DEVICE 13.3 Connection Diagram

13

For GT15-DIOR Connection diagram 9)

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.

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 6 31 7 32 8 33 9 34 10 35 11 36 12 37 13 38 30 4 3 2 1 29 28 27 26 5

DC24V

External I/O unit side Original operation panel

Cable for connecting an external input power supply

13 CONNECTION TO EXTERNAL I/O DEVICE 13.3 Connection Diagram 349

35

Connection diagram 10) For 16-point input

For 128-point input*1

*1 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).

*2 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

XSCN00 XSCN01 XSCN02 XSCN03 XSCN04 XSCN05 XSCN06 XSCN07

X000X010X020X030X040X050X060X070

X001

X002

X003

X004

X005

X006

X007

X008

X009

X00A

X00B

X00C

X00D

X00E

X00F

*2

XD00

XD01

XD02

XD03

XD04

XD05

XD06

XD07

XD08

XD09

XD0A

XD0B

XD0C

XD0D

XD0E

XD0F

XSCN00

XSCN01

XSCN02

XSCN03

XSCN04

XSCN05

XSCN06

XSCN07

0 13 CONNECTION TO EXTERNAL I/O DEVICE 13.3 Connection Diagram

13

Connector specifications

*1 The former product PCS-E50LA can also be used.

Precautions when preparing a cable 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.

GOT side connector For the GOT side connector, refer to the following. Page 49 GOT connector specifications

No. Name Model name Manufacturer 1) Connector PCR-E50FS+

(GT15-DIO) Honda Tsushin Kogyo Co., Ltd.

PCS-E50FS+ (GT15-DIOR)

2) Connector cover PCS-E50LPA+R *1

3) Cable UL 2464 AWG28 or equivalent

4) Cable for connecting an external input power supply

UL 1007 AWG24 or equivalent

Any connector selected by the user

24VDC power supply

1) 2) 4) 3)

13 CONNECTION TO EXTERNAL I/O DEVICE 13.3 Connection Diagram 351

35

13.4 GOT Side Settings Setting communication interface

Controller setting Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set [Manufacturer], [Controller Type], [I/F], and [Detail Setting] according to the controller used.

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

2 13 CONNECTION TO EXTERNAL I/O DEVICE 13.4 GOT Side Settings

13

External I/O device setting

1. Select [Common] [Peripheral Setting] [External I/O / Operation Panel] from the menu.

2. Set the interface to which the external I/O device is connected.

3. Check the [Use Operation Panel] to set the operation panel. For details on the operation panel settings,refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

4. When you have completed the settings, click the [OK] button.

Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective.

13.5 Precautions

External I/O function setting on GT Designer3 Before using the operation panel, make the operation panel setting. For details, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

2.

Click!

3.

13 CONNECTION TO EXTERNAL I/O DEVICE 13.5 Precautions 353

35

MEMO

4 13 CONNECTION TO EXTERNAL I/O DEVICE 13.5 Precautions

14

14 BAR CODE READER CONNECTION Page 355 Connectable Model List Page 355 System Configuration Page 357 Connection Diagram Page 358 GOT Side Settings Page 362 System Configuration Examples Page 368 Precautions

14.1 Connectable Model List For connectable bar code readers and system equipment, refer to the following Technical Bulletin. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160) For Technical Bulletins, go to the Mitsubishi Electric Factory Automation Global Website. www.MitsubishiElectric.com/fa

14.2 System Configuration Connecting to bar code reader

Barcode*

Extended function OS

Connection type dependent

Communication driver

GOTBar code reader

Connection cable 1)

PLC

Varies according to the connection type.

Connection cable 2)

14 BAR CODE READER CONNECTION 14.1 Connectable Model List 355

35

*1 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 GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

*2 When a GT10-C02H-6PT9P unit of the sub version A or B is used, do not ground the case of the D-sub (9-pin) connector. *3 GT25-W, GT2505-V does not support the option device.

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. System configuration between the GOT and PLC For the system configuration between the GOT and PLC, refer to each chapter. GOT2000 Series Connection Manual (Mitsubishi Electric Product) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 1) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 2) For GT Works3 Version1 GOT2000 Series Connection Manual (Microcomputer, MODBUS, Products, Peripherals) For GT Works3 Version1

Bar code reader

Communication Type

Connection cable 1)

Connection cable 2) GOT PLC Number of connectable equipment

Option device*3 Model

*1 USB *1 - - (Built into GOT) For the system configuration between the GOT and PLC, refer to each chapter.

One serial barcode reader and one USB barcode reader for one GOT

RS-232 *1 - - (Built into GOT)

Page 357 RS-232 connection diagram 1)

- (Built into GOT)

GT10-C02H-6PT9P*2

(0.2m) - (Built into GOT)

- GT15-RS2-9P

RS-422/485 *1 - - (Built into GOT)

- GT15-RS4-9S

- GT15-RS4-TE

- - (Built into GOT)

6 14 BAR CODE READER CONNECTION 14.2 System Configuration

14

14.3 Connection Diagram The following diagram shows the connection between the GOT and the barcode.

RS-232 cable

Connection diagram RS-232 connection diagram 1)

Precautions when preparing a cable Cable length The length of the RS-232 cable must be 15m or less.

GOT side connector For the GOT side connector, refer to the following. Page 49 GOT connector specifications

Barcode side (D-Sub 9 pin)

GOT side (terminal block)

N.C.

RD(RXD)

SD(TXD)

ER(DTR)

SG

DR(DSR)

RS(RTS)

CS(CTS)

-

1

2

3

4

5

6

7

8

9

N.C.

RD

SD

ER

SG

DR

RS

CS

N.C.

14 BAR CODE READER CONNECTION 14.3 Connection Diagram 357

35

14.4 GOT Side Settings Setting communication interface

Controller setting Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set [Manufacturer], [Controller Type], [I/F], and [Detail Setting] according to the controller used.

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

8 14 BAR CODE READER CONNECTION 14.4 GOT Side Settings

14

Bar code reader setting When using a serial barcode reader

1. Select [Common] [Peripheral Setting] [Bar Code] from the menu.

2. Select the [Serial] tab in the [Bar Code] dialog.

3. Set the interface to which the bar code reader is connected.

4. Select [Use Serial Bar Code] to configure the function setting. For details on the function setting, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

5. Click the [Detail Setting] button to display the [Detail Setting] dialog for each communication driver. Make the settings according to the usage environment. Page 361 Communication detail settings

6. When you have completed the settings, click the [OK] button.

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. 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. Setting for the driver To Channels No. 5 to 8, multiple [Bar Code] cannot be set.

Click!

3.

4.

5.2.

14 BAR CODE READER CONNECTION 14.4 GOT Side Settings 359

36

When using a USB barcode reader

1. Select [Common] [Peripheral Setting] [Bar Code] from the menu.

2. Select the [USB] tab in the [Bar Code] dialog.

3. Select [Use USB Bar Code] to configure the function setting. For details on the function setting, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

4. When you have completed the settings, click the [OK] button.

3. Click!

2.

0 14 BAR CODE READER CONNECTION 14.4 GOT Side Settings

14

Communication detail settings Make the settings according to the usage environment.

Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) 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

14 BAR CODE READER CONNECTION 14.4 GOT Side Settings 361

36

14.5 System Configuration Examples A system configuration example for bar code reader connection is shown below.

When using a serial bar code reader

System configuration

*1 The GOT and QCPU (Q mode) are connected through a bus. For bus connection, refer to the following manual. GOT2000 Series Connection Manual (Mitsubishi Electric Products) for GT Works3

1. The bar code is read with the bar code reader. Page 362 Bar code reader setting

2. The GOT receives the data sent from the bar code reader. Page 363 Settings in the [I/F Communication Setting] window Page 363 Settings in the [Detail Setting] dialog

3. The received data are written to the PLC CPU. Page 364 Settings in the [Bar Code] dialog

4. The data read with the bar code reader are written into the PLC CPU devices. Page 365 Confirmation on PLC side

Bar code reader setting The bar code reader shall be configured as shown below.

Bar code reader setting For the bar code reader setting, refer to the following manual. User's Manual of the bar code reader

Item Set value Transmission Speed 9600bps

Data Bit 8bit

Stop Bit 1bit

Parity Even

Header None

Terminator CR

123456789

Barcode

Read data Terminator

CR 0DH

1

31H

2

32H

3

33H

4

34H

5

35H

6

36H

7

37H

8

38H

9

39H

*1

Read data "123456789"

D0

D1

D2

D3

D4

D5

9 (00H) (09H)

2 (32H)

1 (31H)

3 (33H)

4 (34H)

5 ( 35H)

6 (36H)

7 (37H)

8 (38H)

9 (39H)

SP (20H)

Read bytes

Stored data

2 14 BAR CODE READER CONNECTION 14.5 System Configuration Examples

14

Settings in GT Designer3 Settings in the [I/F Communication Setting] window The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

Settings in the [Detail Setting] dialog 1. In the [I/F Communication Setting] window, set the channel and communication driver for the interface to be used, and

click the [Detail Setting] button.

2. Keep consistency with the bar code reader setting.

[Controller Setting] of GT Designer3 For the setting method of [Controller Setting] of GT Designer3, refer to the following. Page 358 Setting communication interface

Item Setting (Use default value.) [Transmission Speed] [9600bps]

[Data Bit] [8bit]

[Stop Bit] [1bit]

[Parity] [Even]

14 BAR CODE READER CONNECTION 14.5 System Configuration Examples 363

36

Settings in the [Bar Code] dialog

*1 Keep consistency with the bar code reader setting.

[Bar Code] of GT Designer3 For the [Bar Code] setting in GT Designer3, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

Item Set value [Read Data Direct Input to Object] [No]

[Device] [D0]

[Device Points] [6]

[Header] *1 [None]

[Terminator] *1 [CR]

[Data Writing Order] [LowHigh]

[Fill up a space when imported data is less than the writing points] Check (Filling Data is available)

[Filling Data] [Space (0x20)]

4 14 BAR CODE READER CONNECTION 14.5 System Configuration Examples

14

Confirmation on PLC side Connect GX Works2 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 Works2 operation method, refer to the following manual. GX Works2 Operating Manual

Confirming the device values of D0 to D5 (when using GX Works2 Startup procedure: GX Works2 [Online] [Monitor] [Device/Buffer Memory Batch Monitor]

ASCII codes are hexadecimals. Specify [HEX] for [Value] of the GX Works2 and confirm the read data.

14 BAR CODE READER CONNECTION 14.5 System Configuration Examples 365

36

When using a USB bar code reader

System configuration

*1 The GOT and QCPU (Q mode) are connected through a bus. For bus connection, refer to the following manual. GOT2000 Series Connection Manual (Mitsubishi Electric Products) for GT Works3

1. The bar code is read with the bar code reader. Page 366 Bar code reader setting

2. The GOT receives the data sent from the bar code reader. Page 367 Settings in the [GOT Setup] window

3. The received data are written to the PLC CPU. Page 367 Settings in the [Bar Code] dialog

4. The data read with the bar code reader are written into the PLC CPU devices. Page 367 Confirmation on PLC side

Bar code reader setting The settings for the USB bar code reader are not necessary.

When using a USB barcode reader, input values are handled as ASCII characters.

123456789

Barcode

Read data Terminator

Enter 1

31H

2

32H

3

33H

4

34H

5

35H

6

36H

7

37H

8

38H

9

39H

*1

Read data "123456789"

D0

D1

D2

D3

D4

D5

9 (00H) (09H)

2 (32H)

1 (31H)

3 (33H)

4 (34H)

5 ( 35H)

6 (36H)

7 (37H)

8 (38H)

9 (39H)

SP (20H)

Read bytes

Stored data

6 14 BAR CODE READER CONNECTION 14.5 System Configuration Examples

14

Settings in GT Designer3 Settings in the [GOT Setup] window In the [GOT Setup] window ([USB Host]), select [Use USB keyboard/USB bar code] and set [Keyboard Type] according to the setting of the USB barcode reader used.

Settings in the [Bar Code] dialog

[Bar Code] of GT Designer3 For the [Bar Code] setting in GT Designer3, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

Confirmation on PLC side For the confirmation on the PLC side, refer to the following. Page 365 Confirmation on PLC side

Item Set value [Device] [D0]

[Device Points] [6]

[Notification Device] [GD500]

[Control Device] [GD501]

[Data Writing Order] [LowHigh]

[Fill up a space when imported data is less than the writing points] Check (Filling Data is available)

[Filling Data] [Space (0x20)]

14 BAR CODE READER CONNECTION 14.5 System Configuration Examples 367

36

14.6 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. GT Designer3 (GOT2000) Screen Design Manual

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.

8 14 BAR CODE READER CONNECTION 14.6 Precautions

15

15 PC REMOTE CONNECTION Page 369 Connectable Model List Page 370 Serial Connection Page 378 Ethernet Connection

15.1 Connectable Model List The RGB display is used for the remote personal computer operation connection. The following table lists the GOT models that support the remote personal computer operation connection.

*1 GT2705-V is not supported.

Connection type Model Serial connection

*1

Ethernet connection

15 PC REMOTE CONNECTION 15.1 Connectable Model List 369

37

15.2 Serial Connection System Configuration

*1 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.

*2 The connection cable 1) (RS-232 cable) and the connection cable 2) (analog cable) should be connected between the personal computer and the GOT.

*3 GT2705-V is not supported. *4 The unit installation position, and the number of units, refer to the following.

Page 47 Precautions when installing units on top of one another *5 Usable for channel 1 only.

Personal computer

Connection cable 1)*2 GOT PLC Number of connectable equipment

Cable model Max. distance

Option device Model

To be selected by the user.

GT01-C30R2-9S or

RS232 connection diagram 1)

15m - (Built into GOT)

*3

For the system configuration between the GOT and PLC, refer to each chapter.

1 personal computer for 1 GOT

GT15-RS2-9P

*3

Personal computer

Connection cable 1)*2 GOT PLC Number of connectable equipment

Cable model Max. distance

Option device Model

To be selected by the user.

GT15-C50VG or

Analog RGB connection diagram 1)

*1 GT27-R2*5

*3

For the system configuration between the GOT and PLC, refer to each chapter.

1 personal computer for 1 GOT

GT27-R2-Z*5

*3

GT27-V4R1-Z

*3

Extended function OS

PC remote operation (serial) Video/RGB input

Extended function OS

Connection type dependent

Communication driver

PC GOT Connection cable 1)

PLC

Varies according to the connection type.

Connection cable 2)

0 15 PC REMOTE CONNECTION 15.2 Serial Connection

15

System configuration between the GOT and PLC For the system configuration between the GOT and PLC, refer to each chapter. GOT2000 Series Connection Manual (Mitsubishi Electric Product) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 1) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 2) For GT Works3 Version1 GOT2000 Series Connection Manual (Microcomputer, MODBUS, Products, Peripherals) For GT Works3 Version1

15 PC REMOTE CONNECTION 15.2 Serial Connection 371

37

Connection Diagram 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.

RS-232 cable Connection diagram RS232 connection diagram 1)

Precautions when preparing a cable Cable length The length of the RS-232 cable must be 15m or less. GOT side connector For the GOT side connector, refer to the following. Page 49 GOT connector specifications Personal computer side connector Use a connector compatible with the personal computer to be used.

PC side

CD

RD

SD

DTR

SG(GND)

DSR

RTS

CTS

FG

1

2

3

4

5

6

7

8

9

Shell

1

3

2

6

5

4

7

8

9

Shell

CD

SD

RD

DSR

SG(GND)

DTR

RTS

CTS

CI

FG

GOT side

2 15 PC REMOTE CONNECTION 15.2 Serial Connection

15

Analog RGB cable Connection diagram Analog RGB connection diagram 1)

Precautions when preparing a cable 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. 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.

Personal computer side connector Use a connector compatible with the personal computer to be used.

GOT Connector type Connector type Manufacturer GT16M-R2 17HE-R13150-73MC2 D-Sub 15 pin (female) DDK Ltd. (DDK)

GT16M-V4R1

GT15V-75R1

GT15V-75V4R1

R

RGND

G

GGND

B

BGND

DGND

HSYNC

VSYNC

DGND

NC

NC

NC

NC

NC

R

RGND

G

GGND

B

BGND

GND

HSYNC

VSYNC

GND

GND

NC

GND

SDA

SCL

1

6

2

7

3

8

10

13

14

5

4

9

11

12

15

1

6

2

7

3

8

10

13

14

5

4

9

11

12

15

PC side GOT side

75 drohmcoaxial

Twisted pair

15 PC REMOTE CONNECTION 15.2 Serial Connection 373

37

GOT Side Settings

Setting communication interface (Controller Setting) Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set [Manufacturer], [Controller Type], [I/F], and [Detail Setting] according to the controller used.

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

4 15 PC REMOTE CONNECTION 15.2 Serial Connection

15

Communication detail settings

Serial connection Make the settings according to the usage environment.

*1 When NTSC format is selected, the resolution is fixed to 640480.

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. 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. Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective.

Item Description Range Video Input Signal*1 Set the video input signal. (Default: NTSC) NTSC, PAL

Video Resolution Set the video resolution. (Default: 640480) 640480, 720480, 768576

15 PC REMOTE CONNECTION 15.2 Serial Connection 375

37

Settings for the remote personal computer operation

1. Select [Common] [Peripheral Setting] [PC Remote Operation] from the menu.

2. Set the interface to which the personal computer is connected for the [Connecting I/F] of [PC Remote Operation (serial)].

3. When you have completed the settings, click the [OK] button.

Settings for the video/RGB equipment

1. Select [Common] [Peripheral Setting] [Video/RGB Input] from the menu.

2. Set the interface to which the video/RGB equipment is connected.

3. Check the [Use Video/RGB Input] to set the function. For details on the function setting, refer to the following manual. GT Designer3 (GOT2000) 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.

Page 375 Communication detail settings

5. When you have completed the settings, click the [OK] button.

2.

Click!

2.

3.

4.

Click!

6 15 PC REMOTE CONNECTION 15.2 Serial Connection

15

Setting for the driver To Channels No. 5 to 8, multiple [PC Remote Operation] cannot be set.

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 (GOT2000) Screen Design Manual

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 (GOT2000) Screen Design Manual

15 PC REMOTE CONNECTION 15.2 Serial Connection 377

37

15.3 Ethernet Connection System Configuration

When using the Ethernet connection cable

*1 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.

*2 When connecting the GOT and personal computer via a hub, use a cable according to the PC configuration. *3 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.

*4 GT25-W, GT2505-V does not support the option device.

Personal computer

Connection cable*1*2 Maximum segment length*3

GOT PLC Number of connectable equipment

Option device*4 Model

To be selected by the user.

100BASE-TX Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 5 or higher 10BASE-T

Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 3 or higher

100m - (Built into GOT) For the system configuration between the GOT and PLC, refer to each chapter.

1 personal computer for 1 GOT

GT25-J71E71-100

Extended function OS

PC remote operation (Ethernet)

Communication driver

Ethernet system Connection type dependent

Communication driver

PC GOT PLC

Varies according to the connection type.

Hub

Connection cable Connection cable

8 15 PC REMOTE CONNECTION 15.3 Ethernet Connection

15

When using the wireless LAN

*1 Select [Station] in [Operation mode] of [Wireless LAN setting] of the [GOT Setup] dialog. Page 429 WIRELESS LAN CONNECTION

*2 Select [Access point] in [Operation mode] of [Wireless LAN setting] of the [GOT Setup] dialog. Page 429 WIRELESS LAN CONNECTION

*3 GT2505-V does not support the option device.

System configuration between the GOT and PLC For the system configuration between the GOT and PLC, refer to each chapter. GOT2000 Series Connection Manual (Mitsubishi Electric Product) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 1) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 2) For GT Works3 Version1 GOT2000 Series Connection Manual (Microcomputer, MODBUS, Products, Peripherals) For GT Works3 Version1

Personal computer

Wireless LAN access point GOT PLC Number of connectable equipmentModel name Option device*3 Model

To be selected by the user.

Wireless access point For the connectable access point and system devices, refer to the following Technical News List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

GT25-WLAN

*1

For the system configuration between the GOT and PLC, refer to each chapter.

1 personal computer for 1 GOT

- GT25-WLAN

*2

System Application (Extended function)

Wireless LAN Connection type dependent

Communication driver

PC Wireless

LAN access point

GOT Wireless LAN

Communication Unit

PLC

Varies according to the connection type.

15 PC REMOTE CONNECTION 15.3 Ethernet Connection 379

38

GOT Side Settings

Setting communication interface (Controller Setting) When using the Ethernet connection cable Ethernet communication drivers must be set on the GOT, and set the communication interface setting.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set [Manufacturer], [Controller Type], [I/F], and [Detail Setting] according to the controller used.

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

When using the wireless LAN For details of the wireless LAN setting, refer to the following. Page 429 WIRELESS LAN CONNECTION

2.

3.

Click!

0 15 PC REMOTE CONNECTION 15.3 Ethernet Connection

15

Settings for the PC remote operation

1. Select [Common] [Peripheral Setting] [PC Remote Operation] from the menu.

2. Set [Connecting I/F] of [PC Remote Operation] to [Disconnect].

3. 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 (GOT2000) Screen Design Manual

4. When you have completed the settings, click the [OK] button.

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. GT Designer3 (GOT2000) Screen Design Manual

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 (GOT2000) Screen Design Manual

2. Click!

3.

15 PC REMOTE CONNECTION 15.3 Ethernet Connection 381

38

MEMO

2 15 PC REMOTE CONNECTION 15.3 Ethernet Connection

16

16 GOT Mobile CONNECTION Page 383 Connectable Model List Page 384 System Configuration Page 386 GOT Side Settings Page 387 Precautions

16.1 Connectable Model List The following table lists the GOT models that support the GOT Mobile connection. GT27 GT25 For connectable devices and usable browsers as clients, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

CoreOS version of the GOT To use GOT Mobile connection, install CoreOS version L or later on the GOT. For the procedure to check the CoreOS version and upgrade the version, refer to the following. GT Designer3 (GOT2000) Screen Design Manual GOT2000 Series User's Manual (Utility)

16 GOT Mobile CONNECTION 16.1 Connectable Model List 383

38

16.2 System Configuration

PC, Tablet, smartphone (GOT Mobile client)

Connection cable *1*2

Wireless LAN access point Maximum segment length *3

GOT (GOT Mobile server) PLC Number of connectable equipment

Option device *6 Model

To be selected by the user. 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 - (Built into GOT) For the system configuration between the GOT and PLC, refer to each chapter.

1 personal computer for 5 client

- - GT25-WLAN

*4

For the connectable access point and system devices, refer to the following Technical News. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

- GT25-WLAN

*5

System Application (Extended function)

Wireless LAN

Extended function OS

GOT Mobile Connection type dependent

Communication driver

GOT Mobile client

PC

Tablet, smartphone

PLC

Varies according to the connection type.

GOT (GOT Mobile server)

Wireless LAN access point

Connection cable

Connection cable, Hub, Wireless LAN access point

Hub

4 16 GOT Mobile CONNECTION 16.2 System Configuration

16

*1 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.

*2 When connecting the GOT and personal computer via a hub, use a cable according to the client configuration. *3 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.

*4 Select [Access point] in [Operation mode] of [Wireless LAN setting] of the [GOT Setup] dialog. Page 429 WIRELESS LAN CONNECTION

*5 Select [Station] in [Operation mode] of [Wireless LAN setting] of the [GOT Setup] dialog. Page 429 WIRELESS LAN CONNECTION

*6 GT2505-V does not support the option device.

System configuration between the GOT and PLC For the system configuration between the GOT and PLC, refer to each chapter. GOT2000 Series Connection Manual (Mitsubishi Electric Product) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 1) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 2) For GT Works3 Version1 GOT2000 Series Connection Manual (Microcomputer, MODBUS, Products, Peripherals) For GT Works3 Version1

16 GOT Mobile CONNECTION 16.2 System Configuration 385

38

16.3 GOT Side Settings GOT Mobile setting

1. Select [Common] [GOT Mobile Setting] from the menu.

2. Check the [Use GOT Mobile function] of [GOT Mobile Setting] to set. For details on the settings, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

3. When you have completed the settings, click the [OK] button.

6 16 GOT Mobile CONNECTION 16.3 GOT Side Settings

16

Setting communication interface (Controller Setting)

When using the wireless LAN For using the system configuration given in this chapter (Page 384 System Configuration), the wireless LAN setting is required. For details of the setting, refer to the following. Page 429 WIRELESS LAN CONNECTION

When using the Ethernet connection cable Ethernet communication drivers must be set on the GOT, and set the Communication settings.

Ethernet communication driver setting

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set [Manufacturer], [Controller Type], [I/F], and [Detail Setting] according to the controller used.

4. When you have completed the settings, click the [OK] button.

16.4 Precautions For cautions or troubleshooting of the GOT Mobile function, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

2.

3.

Click!

16 GOT Mobile CONNECTION 16.4 Precautions 387

38

MEMO

8 16 GOT Mobile CONNECTION 16.4 Precautions

17

17 VNC SERVER CONNECTION Page 389 Connectable Model List Page 389 System Configuration Page 392 GOT Side Settings Page 393 Setting in Personal Computer

17.1 Connectable Model List The VNC server can be connected to the following VNC client.

17.2 System Configuration

When using the Ethernet connection cable

CPU Software PC Ultra VNC

Personal computer (VNC client)

Connection cable*1*2 Maximum segment length*3

GOT (VNC server) PLC Number of connectable equipment

Option device*4 Model

To be selected by the user.

100BASE-TX Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 5 or higher 10BASE-T

Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 3 or higher

100m - (Built into GOT)

*5

For the system configuration between the GOT and PLC, refer to each chapter.

1 personal computer for 1 GOT

GT25-J71E71-100

Extended function OS

VNC Server

Communication driver

Ethernet system Connection type dependent

Communication driver

PC (VNC client) PLC

Varies according to the connection type.

GOT (VNC server)Hub

Connection cable Connection cable

17 VNC SERVER CONNECTION 17.1 Connectable Model List 389

39

*1 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.

*2 When connecting the GOT and personal computer (VNC client) via a hub, use a cable according to the client configuration. *3 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.

*4 GT25-W, GT2505-V does not support the option device. *5 Only available to GS21-W-N for GS21.

0 17 VNC SERVER CONNECTION 17.2 System Configuration

17

When using the wireless LAN

*1 Select [Station] in [Operation mode] of [Wireless LAN setting] of the [GOT Setup] dialog. Page 429 WIRELESS LAN CONNECTION

*2 Select [Access point] in [Operation mode] of [Wireless LAN setting] of the [GOT Setup] dialog. Page 429 WIRELESS LAN CONNECTION

*3 GT2505-V does not support the option device.

System configuration between the GOT and PLC For the system configuration between the GOT and PLC, refer to each chapter. GOT2000 Series Connection Manual (Mitsubishi Electric Product) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 1) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 2) For GT Works3 Version1 GOT2000 Series Connection Manual (Microcomputer, MODBUS, Products, Peripherals) For GT Works3 Version1

Personal computer

Wireless LAN access point GOT PLC Number of connectable equipmentModel name Option device*3 Model

To be selected by the user.

Wireless access point For the connectable access point and system devices, refer to the following Technical News List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

GT25-WLAN

*1

For the system configuration between the GOT and PLC, refer to each chapter.

1 personal computer for 1 GOT

- GT25-WLAN

*2

System Application (Extended function)

Wireless LAN Connection type dependent

Communication driver

Wireless LAN

access point GOT

Wireless LAN Communication

Unit PLC

Varies according to the connection type.

PC (VNC client)

17 VNC SERVER CONNECTION 17.2 System Configuration 391

39

17.3 GOT Side Settings VNC server function setting

1. Select [Common] [Peripheral Setting] [VNC Server] from the menu.

2. Check the [VNC Server] of [Use VNC Server] to set. For details on the settings, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

3. When you have completed the settings, click the [OK] button.

Click!

2.

2 17 VNC SERVER CONNECTION 17.3 GOT Side Settings

17

Setting communication interface (Controller Setting)

When using the Ethernet connection cable For using the VNC server, Ethernet communication drivers must be set on the GOT, and set the Communication settings

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set [Manufacturer], [Controller Type], [I/F], and [Detail Setting] according to the controller used.

4. When you have completed the settings, click the [OK] button.

When using the wireless LAN For details of the wireless LAN setting, refer to the following. Page 429 WIRELESS LAN CONNECTION

17.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. GT Designer3 (GOT2000) Screen Design Manual

2.

3.

Click!

17 VNC SERVER CONNECTION 17.4 Setting in Personal Computer 393

39

MEMO

4 17 VNC SERVER CONNECTION 17.4 Setting in Personal Computer

18

18 VIDEO, HDMI, AND RGB CONNECTION Page 395 Connectable Model List Page 396 System Configuration Page 398 Connection Diagram Page 400 GOT Side Settings Page 402 Precautions

18.1 Connectable Model List The following table lists the GOT models that support the video, HDMI, and RGB connection. GT27 (excluding GT2705-V) For the type of the video camera that can be connected, refer to the following Technical Bulletin. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160) For Technical Bulletins, go to the Mitsubishi Electric Factory Automation Global Website. www.MitsubishiElectric.com/fa

BootOS version of the GOT To use GT27-R2 or GT27-ROUT, install BootOS version N or later on the GOT. To use GT27-VHOUT, install BootOS version AK or later on the GOT. For the procedure to check the BootOS version and upgrade the version, refer to the following. GT Designer3 (GOT2000) Screen Design Manual GOT2000 Series User's Manual (Utility)

18 VIDEO, HDMI, AND RGB CONNECTION 18.1 Connectable Model List 395

39

18.2 System Configuration Displaying video image on GOT

*1 For connectable video camera types, refer to the following Technical News. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

*2 The user must select a vision sensor or a personal computer to be used. *3 The cable length differs according to the specifications of the video/RGB equipment. *4 RGB can be input with two channels. For the switching between two channels, refer to the following manual.

GT Designer3 (GOT2000) Screen Design Manual *5 GT2705-V is not supported. *6 For the unit installation position and the number of installed units, refer to the following.

Page 47 Precautions when installing units on top of one another

Signal type Video, RGB equipment Connection cable*3 GOT Number of connectable equipment

Cable model Connection diagram number

Option device*6 Model

NTSC/PAL Equipment including video cameras*1 and vision sensors*2 that outputs images by using the NTSC or PAL signal

Page 398 Coaxial connection diagram 1)

GT27-V4-Z GT27-V4R1-Z

*5

4 video equipment for 1 GOT

Analog RGB Equipment including video cameras*1, vision sensors*2, and personal computers*2 that outputs images by using the RGB signal

GT15-C50VG(5m) or

Page 399 Analog RGB connection diagram 1)

GT27-R2-Z*4

GT27-R2

*5

2 RGB equipment for 1 GOT

GT27-V4R1-Z

*5

1 RGB equipment for 1 GOT

Video/RGB

Extended function OS

Connection cable

GOT Video, RGB equipment including video cameras, vision sensors, and personal computers

6 18 VIDEO, HDMI, AND RGB CONNECTION 18.2 System Configuration

18

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) 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. 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. Power-On of NTSC/PAL compatible video camera Turn on the NTSC/PAL compatible video camera simultaneously with the GOT. Distortion of the image caused by the noise When the screen is distorted by the noise from the RGB cable, install the following ferrite core to the input part of the RGB cable. Recommended ferrite core: TDK ZCAT3035-1330 (or equivalent)

Displaying GOT screen on external display

*1 The maximum cable length varies depending on the specifications of the external display used. *2 GT2705-V is not supported. *3 For the unit installation position and the number of installed units, refer to the following.

Page 47 Precautions when installing units on top of one another

Signal type

External display Connection cable Maximum cable length

GOT Number of connectable equipment

Model name Model name Option device*3 Model

TMDS HDMI-certified display HDMI-certified cable *1 GT27-VHOUT

*2

1 external display for 1 GOT

Analog RGB

Monitor that supports VESA-compliant GOT screen resolution For the supported scanning frequency, refer to the following. GOT2000 Series RGB Output Unit User's Manual

GT15-C50VG(5m) or

Page 399 Analog RGB connection diagram 2)

GT27-ROUT-Z GT27-ROUT

Video/RGB

Extended function OS

External display GOT

Connection cable

18 VIDEO, HDMI, AND RGB CONNECTION 18.2 System Configuration 397

39

18.3 Connection Diagram The coaxial cable or analog RGB cable to connect the GOT to the video, RGB equipment, or external display must be prepared by the user. The following shows each cable connection diagram and relevant connectors.

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) Displaying video image on GOT

Cable specification

Connecting the BNC connector to the coaxial cable For how to connect the BNC connector and coaxial cable, refer to the following. Page 51 Coaxial cableconnector connection method

Precautions when preparing a cable 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.

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.

Video camera/vision sensor side connector Use a connector compatible with the video camera/vision sensor to be used.

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.

Item Specifications Applicable cable 3C-2V, 5C-2V (JIS C 3501 compliant)

GOT Connector model Connector type Manufacturer GT27-V4-Z 227161-4 BNC Tyco International, Ltd.

GT27-V4R1-Z

GOT side 75 drohmcoaxial

Signal Signal BNC connector BNC connectorGND GND

Video camera/ vision sensor side

8 18 VIDEO, HDMI, AND RGB CONNECTION 18.3 Connection Diagram

18

Analog RGB cable

Connection diagram Analog RGB connection diagram 1) Displaying video image on GOT

Analog RGB connection diagram 2) Displaying GOT screen on external display

Precautions when preparing a cable 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.

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.

Vision sensor/PC side connector Use a connector compatible with the vision sensor/personal computer to be used.

GOT Connector model Connector type Manufacturer GT27-R2-Z 17HE-R13150-73MC2 D-Sub 15-pin

(female) DDK Ltd. (DDK)GT27-V4R1-Z

GT27-ROUT-Z

Vision sensor/PC side

R RGND

G GGND

B BGND GND

HSYNC VSYNC

GND GND NC

GND SDA SC

R RGND

G GGND

B BGND GND

HSYNC VSYNC

GND NC NC NC NC NC

1

6

2

7

3

8

10

13

14

5

4

9

11

12

15

1

6

2

7

3

8

10

13

14

5

4

9

11

12

15

GOT side75 drohmcoaxial

Twisted pair

GOT side

R RGND

G GGND

B BGND DGND HSYNC VSYNC DGND

NC NC NC NC NC

R RGND

G GGND

B BGND GND

HSYNC VSYNC

GND GND NC

GND SDA SCL

1

6

2

7

3

8

10

13

14

5

4

9

11

12

15

1

6

2

7

3

8

10

13

14

5

4

9

11

12

15

External display side75 drohmcoaxial

Twisted pair

18 VIDEO, HDMI, AND RGB CONNECTION 18.3 Connection Diagram 399

40

18.4 GOT Side Settings Setting communication interface

Controller setting Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set [Manufacturer], [Controller Type], [I/F], and [Detail Setting] according to the controller used.

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

0 18 VIDEO, HDMI, AND RGB CONNECTION 18.4 GOT Side Settings

18

Communication detail settings Make the settings according to the usage environment.

*1 When NTSC format is selected, the resolution is fixed to 640480. *2 For GT2710-V and GT2708-V, the resolution is fixed to 640480.

Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective.

Item Description Range Video Input Signal*1 Set the video input signal.

(Default: NTSC) NTSC, PAL

Video Resolution*2 Set the video resolution. (Default: 640480)

640480, 720480, 768576

18 VIDEO, HDMI, AND RGB CONNECTION 18.4 GOT Side Settings 401

40

Settings for the video/RGB equipment

1. Select [Common] [Peripheral Setting] [Video/RGB Input] from the menu.

2. Set the interface to which the video/RGB equipment is connected.

3. Check the [Use Video/RGB Input] to set the function. For details on the function setting, refer to the following manual. GT Designer3 (GOT2000) 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.

Page 401 Communication detail settings

5. When you have completed the settings, click the [OK] button.

Setting the video/RGB function Set the video/RGB function. For the video/RGB function setting, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

18.5 Precautions

Connecting to PC When connecting to a PC, ground the earth wire of the PC.

2.

3.

4.

Click!

2 18 VIDEO, HDMI, AND RGB CONNECTION 18.5 Precautions

19

19 PRINTER CONNECTION Page 403 Connectable Model List Page 404 System Configuration Page 410 Connection Diagram Page 411 GOT Side Settings Page 414 Precautions

19.1 Connectable Model List For connectable printers and system equipment, refer to the following Technical Bulletin. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160) For Technical Bulletins, go to the Mitsubishi Electric Factory Automation Global Website. www.MitsubishiElectric.com/fa

BootOS version of the GOT To use an Ethernet printer, install version AJ or later of BootOS on the GOT. For the procedure to check the BootOS version and upgrade the version, refer to the following. GT Designer3 (GOT2000) Screen Design Manual GOT2000 Series User's Manual (Utility)

19 PRINTER CONNECTION 19.1 Connectable Model List 403

40

19.2 System Configuration Connecting to PictBridge compatible printer

*1 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 GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

*2 GT25-W, GT2505-V does not support the option device.

System configuration between the GOT and PLC For the system configuration between the GOT and PLC, refer to each chapter. GOT2000 Series Connection Manual (Mitsubishi Electric Product) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 1) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 2) For GT Works3 Version1 GOT2000 Series Connection Manual (Microcomputer, MODBUS, Products, Peripherals) For GT Works3 Version1

Printer Connection cable GOT PLC Number of connectable equipment

Model name Model name Option device*2 Model

For connectable printers and system equipment, refer to the following Technical News. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

GT09-C30USB-5P(3m) (packed together with the printer unit)

GT15-PRN*1 For the system configuration between the GOT and PLC, refer to each chapter.

1 printer for 1 GOT

Printer (PictBridge)

Extended function OS

Connection type dependent

Communication driver

PLCGOT PictBridge compatible

printer Connection cable

Varies according to the connection type.

4 19 PRINTER CONNECTION 19.2 System Configuration

19

Connecting to serial printer

*1 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.

*2 When a GT10-C02H-6PT9P unit of the sub version A or B is used, do not ground the case of the D-sub (9-pin) connector. *3 GT25-W, GT2505-V does not support the option device.

System configuration between the GOT and PLC For the system configuration between the GOT and PLC, refer to each chapter. GOT2000 Series Connection Manual (Mitsubishi Electric Product) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 1) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 2) For GT Works3 Version1 GOT2000 Series Connection Manual (Microcomputer, MODBUS, Products, Peripherals) For GT Works3 Version1

Printer Connection cable 1)

Connection cable 2)

GOT PLC Number of connectable equipmentModel name Model name Model name Option device*3 Model

For connectable printers and system equipment, refer to the following Technical News. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

RS-232 cable*1 - - (Built into GOT) For the system configuration between the GOT and PLC, refer to each chapter.

1 printer for 1 GOT

Page 410 RS-232 connection diagram 1)

- (Built into GOT)

GT10-C02H-6PT9P*2

(0.2m) - (Built into GOT)

- GT15-RS2-9P

Printer (serial)

Extended function OS

Connection type dependent

Communication driver

PLCGOT Serial printer

Connection cable 1) Connection cable 2)

Varies according to the connection type.

19 PRINTER CONNECTION 19.2 System Configuration 405

40

Connecting an Ethernet printer (ESC/P-R)

Printer Connection cable *1*2, wireless LAN access point

Maximum segment length *3

GOT PLC Number of connectable equipment

Option device Model

For connectable printers and system equipment, refer to the following Technical News. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

100BASE-TX Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 5 or higher 10BASE-T

Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 3 or higher

100m - (Built into GOT) For the system configuration between the GOT and PLC, refer to each chapter.

One printer for one GOT

GT25-J71E71-100

*6

- - GT25-WLAN

*4

*4*7

Wireless LAN access point

For the connectable wireless LAN access points and system devices, refer to the following Technical News. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

- GT25-WLAN

*5

*5*7

Printer (ESC/P-R)

Extended function OS

Connection type dependent

Communication driver

Ethernet printer (ESC/P-R)

The system configuration between GOT and PLC depends on the connection type.

GOT PLC

Wireless LAN access point

Connection cable

Connection cable, Hub, Wireless LAN access point

Hub

6 19 PRINTER CONNECTION 19.2 System Configuration

19

*1 The applicable destination to connect the twisted pair cable depends on the configuration of the Ethernet network system. Connect to the applicable Ethernet module, hub, transceiver, wireless LAN adapter (NZ2WL-JPA or NZ2WL-JPS), or other system equipment according to the Ethernet network system. Use the cable, connector, or hub that meets the IEEE802.3 10BASE-T/100BASE-TX standard. For the controller to which the wireless LAN adapter can be connected and how to configure the settings for the wireless LAN adapter, refer to the manual of the wireless LAN adapter you use.

*2 When connecting the GOT and printer via a hub, use a cable according to the printer configuration. *3 The length between the hub and node.

The maximum length depends on the Ethernet equipment you use. When a repeater hub is used, the number of connectable personal computers is as follows. 10BASE-T: Up to 4 personal computers for a cascade connection (500m) 100BASE-TX: Up to 2 personal computers for a cascade connection (205m) For the cascade connection between the switching hubs, there is no theoretical limit to the number of cascades. For the limit, contact the switching hub manufacturer.

*4 Set [Operation Mode] to [Access Point] in [Wireless LAN Setting] in the [GOT Setup] window. GT Designer3 (GOT2000) Screen Design Manual

*5 Set [Operation Mode] to [Station] in [Wireless LAN Setting] in the [GOT Setup] window. GT Designer3 (GOT2000) Screen Design Manual

*6 GT25-W and GT2505-V are excluded. *7 GT2505-V is excluded.

System configuration between the GOT and PLC For the system configuration between the GOT and PLC, refer to each chapter. GOT2000 Series Connection Manual (Mitsubishi Electric Products) For GT Works3 Version1 GOT2000 Series Connection Manual (Non-Mitsubishi Electric Products 1) For GT Works3 Version1 GOT2000 Series Connection Manual (Non-Mitsubishi Electric Products 2) For GT Works3 Version1 GOT2000 Series Connection Manual (Microcomputer, MODBUS, Products, Peripherals) For GT Works3 Version1

19 PRINTER CONNECTION 19.2 System Configuration 407

40

Connecting an Ethernet printer (PCL5)

Printer Connection cable *1*2, wireless LAN access point

Maximum segment length *3

GOT PLC Number of connectable equipment

Option device Model

For connectable printers and system equipment, refer to the following Technical News. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

100BASE-TX Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 5 or higher 10BASE-T

Shielded twisted pair cable (STP) or unshielded twisted pair cable (UTP) of category 3 or higher

100m - (Built into GOT)

*8

For the system configuration between the GOT and PLC, refer to each chapter.

One printer for one GOT

GT25-J71E71-100

*6

- - GT25-WLAN

*4*7

Wireless LAN access point

For the connectable wireless LAN access points and system devices, refer to the following Technical News. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

- GT25-WLAN

*5*7

Printer (PCL5)

Extended function OS

Connection type dependent

Communication driver

The system configuration between GOT and PLC depends on the connection type.

Ethernet printer (PCL5) GOT PLC

Wireless LAN access point

Connection cable

Connection cable, Hub, Wireless LAN access point

Hub

8 19 PRINTER CONNECTION 19.2 System Configuration

19

*1 The applicable destination to connect the twisted pair cable depends on the configuration of the Ethernet network system. Connect to the applicable Ethernet module, hub, transceiver, wireless LAN adapter (NZ2WL-JPA or NZ2WL-JPS), or other system equipment according to the Ethernet network system. Use the cable, connector, or hub that meets the IEEE802.3 10BASE-T/100BASE-TX standard. For the controller to which the wireless LAN adapter can be connected and how to configure the settings for the wireless LAN adapter, refer to the manual of the wireless LAN adapter you use.

*2 When connecting the GOT and printer via a hub, use a cable according to the printer configuration. *3 The length between the hub and node.

The maximum length depends on the Ethernet equipment you use. When a repeater hub is used, the number of connectable personal computers is as follows. 10BASE-T: Up to 4 personal computers for a cascade connection (500m) 100BASE-TX: Up to 2 personal computers for a cascade connection (205m) For the cascade connection between the switching hubs, there is no theoretical limit to the number of cascades. For the limit, contact the switching hub manufacturer.

*4 Set [Operation Mode] to [Access Point] in [Wireless LAN Setting] in the [GOT Setup] window. GT Designer3 (GOT2000) Screen Design Manual

*5 Set [Operation Mode] to [Station] in [Wireless LAN Setting] in the [GOT Setup] window. GT Designer3 (GOT2000) Screen Design Manual

*6 GT25-W and GT2505-V are excluded. *7 GT2505-V is excluded. *8 GT2105-Q is excluded.

System configuration between the GOT and PLC For the system configuration between the GOT and PLC, refer to each chapter. GOT2000 Series Connection Manual (Mitsubishi Electric Products) For GT Works3 Version1 GOT2000 Series Connection Manual (Non-Mitsubishi Electric Products 1) For GT Works3 Version1 GOT2000 Series Connection Manual (Non-Mitsubishi Electric Products 2) For GT Works3 Version1 GOT2000 Series Connection Manual (Microcomputer, MODBUS, Products, Peripherals) For GT Works3 Version1

19 PRINTER CONNECTION 19.2 System Configuration 409

41

19.3 Connection Diagram The following diagram shows the connection between the GOT and the barcode.

RS-232 cable

Connection diagram RS-232 connection diagram 1)

Precautions when preparing a cable Cable length The length of the RS-232 cable must be 15m or less.

GOT side connector For the GOT side connector, refer to the following. Page 49 GOT connector specifications

Barcode side (D-Sub 9 pin)

GOT side (terminal block)

N.C.

RD(RXD)

SD(TXD)

ER(DTR)

SG

DR(DSR)

RS(RTS)

CS(CTS)

-

1

2

3

4

5

6

7

8

9

N.C.

RD

SD

ER

SG

DR

RS

CS

N.C.

0 19 PRINTER CONNECTION 19.3 Connection Diagram

19

19.4 GOT Side Settings Setting communication interface

Controller setting Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set [Manufacturer], [Controller Type], [I/F], and [Detail Setting] according to the controller used.

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

19 PRINTER CONNECTION 19.4 GOT Side Settings 411

41

Printer setting

1. Select [Common] [Peripheral Setting] [Printer] from the menu.

2. Select [Use Printer].

3. Select [Connection Type].

4. When [Connection Type] is set to [Ethernet], select [Printer Type].

5. The operation differs depending on [Connection Type]. For [USB] Select [Destination I/F]. For [Serial] Select [Destination I/F]. Click the [Detail Setting] button to display the [Detail Setting] dialog. Set the details of the communication driver according to the usage environment. For [Ethernet] Select [Set IP Address] to set the IP address of the printer used.

6. When you have completed the settings, click the [OK] button.

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. 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. Setting for the driver Regardless of the printer type, multiple printers are cannot be set. Port number of the Ethernet printer Use 515 for the port number of the Ethernet printer.

2.

Click!

3. 5. 2.

Click!

3. 5.

When [Connection Type] is set to [USB] or [Serial] When [Connection Type] is set to [Ethernet]

4.

2 19 PRINTER CONNECTION 19.4 GOT Side Settings

19

Communication detail settings Make the settings according to the usage environment.

*1 When using the hard copy function, set to 8bit.

Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) 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 printer. (Default: 19200bps)

4800bps, 9600bps, 19200bps, 38400bps, 57600bps, 115200bps

Data Bit*1 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 None

19 PRINTER CONNECTION 19.4 GOT Side Settings 413

41

19.5 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. Disconnect the power supply cable of the printer and stop the printer completely.

4. Connect the power supply cable to the printer.

5. Turn the power of the printer ON and wait until the initialization processing of the printer is completed.

6. 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

IP address setting When the IP addresses of the Ethernet printer and the GOT are the same, a system alarm may occur. Set different IP addresses for the Ethernet printer and the GOT.

4 19 PRINTER CONNECTION 19.5 Precautions

20

20 MULTIMEDIA CONNECTION Page 415 Connectable Model List Page 415 System Configuration Page 418 Connection Diagram Page 419 GOT Side Settings Page 422 Precautions

20.1 Connectable Model List For the type of CF card that can be inserted or connectable video camera types, refer to the following Technical Bulletin. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160) For Technical Bulletins, go to the Mitsubishi Electric Factory Automation Global Website. www.MitsubishiElectric.com/fa

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. GOT2000 Series User's Manual (Utility)

20.2 System Configuration Saving video image and displaying it on GOT

*1 The cable length differs depending on the specification of the video camera used by the user. *2 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 GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160) Precautions for using the CF card Page 419 GOT Side Settings

*3 For the type of the video camera that can be connected, refer to the following Technical News. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

*4 GT2705-V is not supported. *5 The unit installation position, and the number of units, refer to the following.

Page 47 Precautions when installing units on top of one another

Multimedia controller Signal type Connection cable Max. distance

GOT Number of connectable equipmentOption device*5 Model

*3 NTSC/PAL Page 418 Coaxial connection diagram 1)

*1 GT27M-MMR-Z*2

*4

1 multimedia controller for 1 GOT

Multimedia

Extended function OS

GOT Video camera, Microphone, Speaker

Connection cable

20 MULTIMEDIA CONNECTION 20.1 Connectable Model List 415

41

Sending video image to personal computer

When using the Ethernet connection cable

*1 The cable length differs depending on the specification of the video camera used by the user. *2 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.

*3 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 GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160) Precautions for using the CF card Page 419 GOT Side Settings

*4 For the type of the video camera that can be connected, refer to the following Technical News. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

*5 Install the multimedia interaction tool before use. For details of the multimedia interaction tool, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

*6 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.

*7 GT2705-V is not supported. *8 The unit installation position, and the number of units, refer to the following.

Page 47 Precautions when installing units on top of one another

Multim edia controll er

Sign al type

Connection cable 1)

GOT*2*3 Connection cable 2) Person al comput er*5

Number of connecta ble equipme nt

Model name

Max. distan ce

Option device*8

(Interface 1))

Model Option device*8

(Interface 2))

Cable model Maximum segment length*6

*4 NTSC /PAL

Page 418 Coaxial connection diagram 1)

*1 GT27-MMR-Z*3

*7

Ethernet Interface (Built into GOT) GT25-J71E71-100

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 To be selected by the user.

1 multimedia controller for 1 GOT

GT27M-MMR-Z

System Application (Extended function)

Wireless LAN Multimedia

Extended function OS

Gateway (FTP)

Option OS

Connection type dependent

Communication driver

GOT

interface 1) interface 2)

PC Video camera, Microphone, Speaker

Hub Connection

cable 1) Connection

cable 2) Connection

cable 2)

6 20 MULTIMEDIA CONNECTION 20.2 System Configuration

20

When using the wireless LAN

*1 The cable length differs depending on the specification of the video camera used by the user. *2 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 GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160) Precautions for using the CF card Page 419 GOT Side Settings

*3 For the type of the video camera that can be connected, refer to the following Technical News. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

*4 Install the multimedia interaction tool before use. For details of the multimedia interaction tool, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

*5 GT2705-V is not supported. *6 The unit installation position, and the number of units, refer to the following.

Page 47 Precautions when installing units on top of one another *7 The wireless LAN setting is required. Refer to the following.

Page 429 WIRELESS LAN CONNECTION *8 When the [Access point] is set to the [Operation mode] using the wireless LAN function for the GOT, the wireless LAN access point is

not required.

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)

Multimedia controller

Signal type

Connection cable 1) GOT*2 Wireless LAN access point

PC*4 Number of connectable Model name equipment

Model name

Max. distan ce

Option device*6

(Interface 1))

Model Option device*6

(Wireless LAN Communication Unit)

Model name

*3 NTSC/ PAL

Page 418 Coaxial connection diagram 1)

*1 GT27-MMR-Z*2

*5

GT25-WLAN*7 Wireless access point For the connectable access point and system devices, refer to the following Technical News List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A- 0160)

To be selected by the user.

1 multimedia controller for 1 GOT

*8

System Application (Extended function)

Wireless LAN Multimedia

Extended function OS

Gateway (FTP)

Option OS

Connection type dependent

Communication driver

Connection cable 1)

interface 1)

Video camera, Microphone, Speaker

PC Wireless LAN

access point

GOT Wireless LAN

Communication Unit

20 MULTIMEDIA CONNECTION 20.2 System Configuration 417

41

20.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.

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

Cable specification

Connecting the BNC connector to the coaxial cable For connecting the BNC connector and coaxial cable, refer to the following. Page 51 Coaxial cableconnector connection method

Precautions when preparing a cable 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.

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.

Video camera side connector Use a connector compatible with the video camera to be used.

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.

Item Specifications Applicable cable 3C-2V, 5C-2V (JIS C 3501 compliant)

GOT Connector model Connector type Manufacturer GT16M-MMR 227161-4 BNC Tyco International, Ltd.

GOT side 75 drohmcoaxial

Signal Signal BNC connector BNC connectorGND GND

Video camera/ vision sensor side

8 20 MULTIMEDIA CONNECTION 20.3 Connection Diagram

20

20.4 GOT Side Settings Setting communication interface

Controller setting Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set [Manufacturer], [Controller Type], [I/F], and [Detail Setting] according to the controller used.

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

20 MULTIMEDIA CONNECTION 20.4 GOT Side Settings 419

42

Multimedia setting

1. Select [Common] [Peripheral Setting] [Multimedia] from the menu.

2. Set the interface to which the multimedia controller is connected.

3. Check the [Enable the setting of Multimedia] to set the function. For details on the communication settings, refer to the following manual.

GT Designer3 (GOT2000) 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.

Page 421 Communication detail settings

5. When you have completed the settings, click the [OK] button.

2.

3.

4.

Click!

0 20 MULTIMEDIA CONNECTION 20.4 GOT Side Settings

20

Communication detail settings Make the settings according to the usage environment.

Video Setting

*1 When NTSC format is selected, the resolution is fixed to 640480.When PAL format is selected, the resolution is fixed to 768576. *2 For GT2710-V and GT2708-V, the resolution is fixed to 640480.

IP Address Setting for Multimedia Unit Set the network settings for connecting from the multimedia unit via Ethernet.

Network settings with the utility The network setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility)

Item Description Range Video Input Signal*1 Set the video input signal.

(Default: NTSC) NTSC, PAL

Video Resolution*2 Set the video resolution. 640480, 720480, 768576

Item 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

20 MULTIMEDIA CONNECTION 20.4 GOT Side Settings 421

42

Installing and setting multimedia interaction tool 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 (GOT2000) Screen Design Manual

To save a video image and display it on the GOT 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.

Setting the multimedia function Set the multimedia function. For the multimedia function setting, refer to the following manual. GT Designer3 (GOT2000) Screen Design Manual

Set the gateway function Set the gateway function for using FTP. For the gateway function setting, refer to the following. GT Designer3 (GOT2000) Screen Design Manual

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.

20.5 Precautions

When the multimedia function is used Select one of the following functions to use. Video display function RGB display function Multimedia function Video output function

CF card on the multimedia unit 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.

2 20 MULTIMEDIA CONNECTION 20.5 Precautions

21

21 RFID CONNECTION Page 423 Connectable Model List Page 423 System Configuration Page 425 GOT Side Settings Page 428 Precautions

21.1 Connectable Model List For connectable RFID controllers and system equipment, refer to the following Technical Bulletin. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160) For Technical Bulletins, go to the Mitsubishi Electric Factory Automation Global Website. www.MitsubishiElectric.com/fa

21.2 System Configuration Connecting to RFID

RFID controller Communication Type

Connection cable GOT PLC Number of connectable equipment

Option device*3 Model

*1 RS-232 *1 - (Built into GOT) For the system configuration between the GOT and PLC, refer to each chapter.

*1

- (Built into GOT)

GT15-RS2-9P

GT10-C02H-6PT9P*2

RFID

Extended function OS

Connection type dependent

Communication driver

GOT

Connection cable

PLC

Varies according to the connection type.

RFID controller

21 RFID CONNECTION 21.1 Connectable Model List 423

42

*1 For applicable RFID controller of the type/number, configuration equipment, and for connection cables, refer to the following Technical News. List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

*2 When a GT10-C02H-6PT9P unit of the sub version A or B is used, do not ground the case of the D-sub (9-pin) connector. *3 GT25-W, GT2505-V does not support the option device.

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. Using the external authentication Supplying the power to an RFID controller from the GOT System configuration between the GOT and PLC For the system configuration between the GOT and PLC, refer to each chapter. GOT2000 Series Connection Manual (Mitsubishi Electric Product) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 1) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 2) For GT Works3 Version1 GOT2000 Series Connection Manual (Microcomputer, MODBUS, Products, Peripherals) For GT Works3 Version1

*1 RS-422/485 *1 - (Built into GOT) For the system configuration between the GOT and PLC, refer to each chapter.

*1

GT15-RS4-9S

GT15-RS4-TE

- (Built into GOT)

RFID controller Communication Type

Connection cable GOT PLC Number of connectable equipment

Option device*3 Model

4 21 RFID CONNECTION 21.2 System Configuration

21

21.3 GOT Side Settings Setting communication interface

Controller setting Set the channel of the equipment to be connected to the GOT.

1. Select [Common] [Controller Setting] from the menu.

2. In the [Controller Setting] window, select the channel No. to be used from the list menu.

3. Set [Manufacturer], [Controller Type], [I/F], and [Detail Setting] according to the controller used.

4. When you have completed the settings, click the [OK] button.

The settings of connecting equipment can be set and confirmed in [I/F Communication Setting]. For details, refer to the following. Page 39 I/F communication setting

2.

3.

Click!

21 RFID CONNECTION 21.3 GOT Side Settings 425

42

RFID setting

1. Select [Common] [Peripheral Setting] [RFID] from the menu.

2. Set the interface to which the RFID controller is connected.

3. Check the [Use RFID] to set the function. For details on the function setting, refer to the following manual. GT Designer3 (GOT2000) 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.

Page 427 Communication detail settings

5. When you have completed the settings, click the [OK] button.

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. 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. Setting for the driver To Channels No. 5 to 8, multiple [RFID] cannot be set.

2.

3.

4.

Click!

6 21 RFID CONNECTION 21.3 GOT Side Settings

21

Communication detail settings

Communication interface setting by the Utility The communication interface setting can be changed on the Utility's [Communication setting] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manuals. User's Manual of GOT used. Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective.

Item Description Range Transmission Speed(BPS)

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)

7bit, 8bit

Stop Bit Specify the stop bit length for communications. (Default: 1bit)

1bit, 2bit

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)

Done or None

Retry(Times) 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(Sec) Set the time period for a communication to time out. (Default: 3sec)

3 to 30sec

Delay Time(ms) 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 TOHKEN SOLUTION CO.LTD. ICU-60S) Format 12 (MARS TOHKEN SOLUTION CO.LTD. ICU-215 (Mifare))

Nonprocedural protocol Format 15

10, 11, 12, 15

21 RFID CONNECTION 21.3 GOT Side Settings 427

42

21.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. GT Designer3 (GOT2000) Screen Design Manual

Controller setting 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. GT Designer3 (GOT2000) Screen Design Manual

When requiring the power supply 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/writers connection When connecting multiple RFID readers/writers, some controllers may communicate with each RFID reader/writer. 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.

8 21 RFID CONNECTION 21.4 Precautions

22

22 WIRELESS LAN CONNECTION Page 429 System Configuration Page 431 GOT Side Settings Page 432 Precautions

Wireless LAN connection precautions Check whether the wireless LAN communication unit (GT25-WLAN) is in compliance with the standards. For the standards that the wireless LAN communication unit (GT25-WLAN) is in compliance with, refer to the following. Page 44 Communication module

22.1 System Configuration Connecting to wireless LAN

*1 Select [Station] in [Operation mode] of [Wireless LAN setting] of the [GOT Setup] dialog. Page 431 Wireless LAN setting

*2 Select [Access point] in [Operation mode] of [Wireless LAN setting] of the [GOT Setup] dialog. Page 431 Wireless LAN setting

*3 The number of connectable GOTs depends on the specifications of wireless LAN access point. *4 GT2505-V does not support the option device.

Personal computer

Wireless LAN access point GOT PLC Number of connectable equipmentModel name Option device*4 Model

To be selected by the user.

Wireless access point For the connectable access point and system devices, refer to the following Technical News List of Valid Devices Applicable for GOT2000 Series and GOT SIMPLE Series (for Overseas) (GOT-A-0160)

GT25-WLAN

*1

For the system configuration between the GOT and PLC, refer to each chapter.

The multiple GOTs can be connected to one wireless LAN access point.*3

- GT25-WLAN

*2

Up to five personal computers can be connected to one GOT.

System Application (Extended function)

Wireless LAN Connection type dependent

Communication driver

Personal computer

Wireless LAN access point

Wireless LAN Communication

Unit GOT PLC

Varies according to the connection type.

22 WIRELESS LAN CONNECTION 22.1 System Configuration 429

43

System configuration between the GOT and PLC For the system configuration between the GOT and PLC, refer to each chapter. GOT2000 Series Connection Manual (Mitsubishi Electric Product) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 1) For GT Works3 Version1 GOT2000 Series Connection Manual (Non Mitsubishi Electric Product 2) For GT Works3 Version1 GOT2000 Series Connection Manual (Microcomputer, MODBUS, Products, Peripherals) For GT Works3 Version1

0 22 WIRELESS LAN CONNECTION 22.1 System Configuration

22

22.2 GOT Side Settings Wireless LAN setting

1. Select [Common] [GOT Setup] [Advanced Setting] [Wireless LAN setting] from the menu.

2. As necessary, Select [Station] or [Access Point] to [Operation Mode]. For details of the setting, refer to the following. GT Designer3 (GOT2000) Screen Design Manual

3. When you have completed the settings, click the [OK] button.

Setting communication interface (GOT Ethernet setting)

1. Select [Common] [GOT Ethernet Setting] [GOT IP Address Setting] to display the [GOT Ethernet Setting] window.

2. Select the [Wireless LAN] tab.

3. Set the wireless LAN interface according to the usage environment. For the details of the setting, refer to the following. Page 37 [Wireless LAN]

4. When you have completed the settings, click the [OK] button.

2.

3.

Click!

22 WIRELESS LAN CONNECTION 22.2 GOT Side Settings 431

43

Communication detail settings Make the settings according to the usage environment. Display the [Detail Setting] dialog in the following procedure.

1. Select [Common] [GOT Ethernet Setting] [GOT IP Address Setting] to display the [GOT Ethernet Setting] window.

2. Select the [Wireless LAN] tab.

3. Select [Enable Wireless LAN I/F] then click the [Driver Setting] button.

Communication interface setting by Utility The communication interface setting can be changed on the Utility's [Communication Settings] after writing [Controller Setting] of project data. For details on the Utility, refer to the following manual. GOT2000 Series User's Manual (Utility) Precedence in communication settings When settings are made by GT Designer3 or the Utility, the latest setting is effective.

22.3 Precautions

When connecting to multiple GOTs Do not use the IP address "192.168.0.18" when using multiple GOTs with the GOT 1000 series mixed. A communication error may occur on the GOT with the IP address.

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. Consult with the administrator of the network before setting an IP address to the GOT and controller.

Item Description Range GOT Net No. Set the network No. of the GOT.

(Default: 1) 1 to 239

GOT Station Set the station No. of the GOT. (Default: 1)

1 to 64

2 22 WIRELESS LAN CONNECTION 22.3 Precautions

A

APPENDIX Appendix 1 Settable Device Range This section describes the range of devices settable in GT Designer3 for each of non-Mitsubishi Electric products connected to the GOT. The settable range varies with the selection for [Controller Type] in the [Controller Setting] window. Configure the device setting according to the specifications of the controller to be used. Device specifications differ depending on the controller model even among the controllers of the same series. If a non-existent device or a device number out of the range is set for an object, other objects for which correct devices are set may not be monitored. Page 434 Microcomputer ([Computer]) Page 437 ODVA ([DeviceNet]) Page 439 MODBUS ([MODBUS Slave(GOT:Master)]) Page 444 MODBUS ([MODBUS Master(GOT:Slave)]) Page 447 PROFIBUS ([PROFIBUS DP]) Page 450 CLPA ([SLMP]) Page 455 CLPA ([CC-Link IE Field Network Basic])

APPX Appendix 1 Settable Device Range 433

43

Microcomputer ([Computer])

Device setting dialog ([Computer]) Set a device to be monitored.

1) Title Data type and channel number of the device to be set 2) [Device] Set the device name and device number. If a bit number needs to be specified, the setting item is displayed. Example) Setting of M0

3) [Information] Displays the setting range of each setting item according to the selected device.

Item Reference Device setting dialog Page 434 Device setting dialog ([Computer])

Specifications of bit devices Page 435 Monitoring-supported bit devices ([Computer])

Page 435 Availability of writing/reading data to/from bit devices ([Computer])

Specifications of word devices Page 436 Monitoring-supported word devices ([Computer])

Page 436 Availability of writing/reading data to/from word devices ([Computer])

2) 3)

1)

M0

Device name Device number

4 APPX Appendix 1 Settable Device Range

A

Monitoring-supported bit devices ([Computer]) The following table shows monitoring-supported bit devices. To check whether writing/reading data to/from each device is available, refer to the following. Page 435 Availability of writing/reading data to/from bit devices ([Computer]) For the formats of devices, refer to the following. GT Designer3 (GOT2000) Screen Design Manual : Available : Not available

*1 For the devices assigned to EG devices (gateway devices) and the compatible clients, refer to the following. GT Designer3 (GOT2000) Screen Design Manual

Availability of writing/reading data to/from bit devices ([Computer]) The following shows whether writing/reading data to/from bit devices is available by device type. When the device type is other than the bit type, set the device No. in multiples of 16. R/W: Both read and write R/-: Read only -/W: Write only -/-: No read/write access

Device name Device No. representation

Setting range Specifications of EG devices*1

Assignment to EG devices

Access using a client

M Internal relay Decimal 0 to 2047

L Latch relay Decimal 0 to 2047

SM Special relay Decimal 0 to 63

Device name Device type

Bit Byte (8 bits) Word (16 bits) Double-word (32 bits)

Quad-word (64 bits)

M R/W -/- R/W R/W -/-

L R/W -/- R/W R/W -/-

SM R/W -/- R/W R/W -/-

APPX Appendix 1 Settable Device Range 435

43

Monitoring-supported word devices ([Computer]) The following table shows monitoring-supported word devices. To check whether writing/reading data to/from each device is available, refer to the following. Page 436 Availability of writing/reading data to/from word devices ([Computer]) For the formats of devices, refer to the following. GT Designer3 (GOT2000) Screen Design Manual : Available : Not available

*1 For the devices assigned to EG devices (gateway devices) and the compatible clients, refer to the following. GT Designer3 (GOT2000) Screen Design Manual

Availability of writing/reading data to/from word devices ([Computer]) The following shows whether writing/reading data to/from word devices is available by device type. R/W: Both read and write R/-: Read only -/W: Write only -/-: No read/write access

Device name Device No. representation

Setting range Specifications of EG devices*1

Assignment to EG devices

Access using a client

D Data register Decimal 0 to 4095

SD Special register Decimal 0 to 15

R File register Decimal 0 to 4095

Device name Device type

Word (16 bits) Double-word (32 bits) Quad-word (64 bits) Bit of word data D R/W R/W -/- R/W

SD R/W R/W -/- R/W

R R/W R/W -/- R/W

6 APPX Appendix 1 Settable Device Range

A

ODVA ([DeviceNet])

Device setting dialog ([DeviceNet]) Set a device to be monitored.

1) Title Data type and channel number of the device to be set 2) [Device] Set the device name and device number. If a bit number needs to be specified, the setting item is displayed. Example) Setting of I0

3) [Information] Displays the setting range of each setting item according to the selected device.

Item Reference Device setting dialog Page 437 Device setting dialog ([DeviceNet])

Specifications of word devices Page 438 Monitoring-supported word devices ([DeviceNet])

Page 438 Availability of writing/reading data to/from word devices ([DeviceNet])

2) 3)

1)

I0

Device name Device number

APPX Appendix 1 Settable Device Range 437

43

Monitoring-supported word devices ([DeviceNet]) The following table shows monitoring-supported word devices. To check whether writing/reading data to/from each device is available, refer to the following. Page 438 Availability of writing/reading data to/from word devices ([DeviceNet]) For the formats of devices, refer to the following. GT Designer3 (GOT2000) Screen Design Manual : Available : Not available

*1 For the devices assigned to EG devices (gateway devices) and the compatible clients, refer to the following. GT Designer3 (GOT2000) Screen Design Manual

Availability of writing/reading data to/from word devices ([DeviceNet]) The following shows whether writing/reading data to/from word devices is available by device type. R/W: Both read and write R/-: Read only -/W: Write only -/-: No read/write access

Device name Device No. representation

Setting range Specifications of EG devices*1

Assignment to EG devices

Access using a client

I Input Decimal 0 to 127

O Output Decimal 0 to 127

Device name Device type

Word (16 bits) Double-word (32 bits) Quad-word (64 bits) Bit of word data I R/W R/W -/- R/W

O R/- R/- -/- R/-

8 APPX Appendix 1 Settable Device Range

A

MODBUS ([MODBUS Slave(GOT:Master)])

Device setting dialog ([MODBUS Slave(GOT:Master)]) Set a device to be monitored.

1) Title Data type and channel number of the device to be set 2) [Device] Set the device name and device number. If a bit number needs to be specified, the setting item is displayed. Example) Setting of 100001

3) [Information] Displays the setting range of each setting item according to the selected device. 4) [Network] The setting depends on the connection type. Page 440 Network setting for the MODBUS/RTU connection ([MODBUS Slave(GOT:Master)]) Page 441 Network setting for the MODBUS/TCP connection ([MODBUS Slave(GOT:Master)])

Item Reference Device setting dialog Page 439 Device setting dialog ([MODBUS Slave(GOT:Master)])

Specifications of bit devices Page 441 Monitoring-supported bit devices ([MODBUS Slave(GOT:Master)])

Page 442 Availability of writing/reading data to/from bit devices ([MODBUS Slave(GOT:Master)])

Specifications of word devices Page 442 Monitoring-supported word devices ([MODBUS Slave(GOT:Master)])

Page 442 Availability of writing/reading data to/from word devices ([MODBUS Slave(GOT:Master)])

Notation of devices Page 443 Notation of devices ([MODBUS Slave(GOT:Master)])

2) 3)

1)

4)

100001

Device name Device number

APPX Appendix 1 Settable Device Range 439

44

Network setting for the MODBUS/RTU connection ([MODBUS Slave(GOT:Master)])

1) Monitor target specification Set the monitor target of the set device.

2) [Network No.] This item appears when [Other] is selected for the station type. For the MODBUS/RTU connection, set 1. 3) [Station No.] This item appears when [Other] is selected for the station type. Set the station number. The setting range is [1] to [247] (direct) or [248] to [254] (indirect). For indirect specification of a station number, refer to the following. Page 440 Indirect specification of a station number for the MODBUS/RTU master connection ([MODBUS Slave(GOT:Master)])

Indirect specification of a station number for the MODBUS/RTU master connection ([MODBUS Slave(GOT:Master)])

When you specify any of 248 to 254 for the station number, the value of the corresponding GOT data register (GD10 to GD16) is used as the station number. The following shows the correspondence between station number setting values and GOT data registers (GD).

Item Description [All] Select this item when writing data to all the connected controllers.

During monitoring, the controller set for [Host Address] of the [Controller Setting] window is monitored. When data is input from a numerical input object, the data is written to all the connected controllers. When no data is input, the controller set for [Host Address] is monitored.

[Host] Select this item when monitoring the controller set as the host station.

[Other] Select this item when monitoring the controller that has the specified station number.

Station No. GOT data register (GD) Setting range 248 GD10 [0] to [255]

Setting a value outside the above range causes a device range error. When "0" is set, "All station specification (broadcast)" is specified. When "255" is set, the host station is specified.

249 GD11

: :

253 GD15

254 GD16

1) 2)

3)

0 APPX Appendix 1 Settable Device Range

A

Network setting for the MODBUS/TCP connection ([MODBUS Slave(GOT:Master)])

1) Monitor target specification Set the monitor target of the set device.

2) [Network No.] This item appears when [Other] is selected for the station type. Specify a network number. The setting range is [1] to [239]. 3) [Station No.] This item appears when [Other] is selected for the station type. Set the station number. The setting range is [1] to [247].

Monitoring-supported bit devices ([MODBUS Slave(GOT:Master)]) The following table shows monitoring-supported bit devices. The device range of MODBUS equipment varies by model. When a model whose device range is not a specified using a multiple of 16 is used, monitoring to the maximum within the range may not be possible. In this case, the device range is up to the number divisible by 16. Example) For a model whose coil device range is from 0 to 9999 The range that can be actually monitored is from 0 to 9984.

To check whether writing/reading data to/from each device is available, refer to the following. Page 442 Availability of writing/reading data to/from bit devices ([MODBUS Slave(GOT:Master)]) For the formats of devices, refer to the following. GT Designer3 (GOT2000) Screen Design Manual : Available : Not available

*1 For the devices assigned to EG devices (gateway devices) and the compatible clients, refer to the following. GT Designer3 (GOT2000) Screen Design Manual

Item Description [All] Not available to the MODBUS/TCP connection.

[Host] Select this item when monitoring the controller set as the host station.

[Other] Select this item when monitoring the controller that has the specified station number.

Device name Device No. representation

Setting range Specifications of EG devices*1

Assignment to EG devices

Access using a client

1 Input relay Decimal 00001 to 65536 (Not usable as word data)

0 Coils Decimal 00001 to 65536 (Not usable as word data)

1) 2)

3)

APPX Appendix 1 Settable Device Range 441

44

Availability of writing/reading data to/from bit devices ([MODBUS Slave(GOT:Master)]) The following shows whether writing/reading data to/from bit devices is available by device type. When the device type is other than the bit type, set the device No. in multiples of 16. R/W: Both read and write R/-: Read only -/W: Write only -/-: No read/write access

Monitoring-supported word devices ([MODBUS Slave(GOT:Master)]) The following table shows monitoring-supported word devices. To check whether writing/reading data to/from each device is available, refer to the following. Page 442 Availability of writing/reading data to/from word devices ([MODBUS Slave(GOT:Master)]) For the formats of devices, refer to the following. GT Designer3 (GOT2000) Screen Design Manual : Available : Not available

*1 For the devices assigned to EG devices (gateway devices) and the compatible clients, refer to the following. GT Designer3 (GOT2000) Screen Design Manual

Availability of writing/reading data to/from word devices ([MODBUS Slave(GOT:Master)]) The following shows whether writing/reading data to/from word devices is available by device type. R/W: Both read and write R/-: Read only -/W: Write only -/-: No read/write access

Device name Device type

Bit Byte (8 bits) Word (16 bits) Double-word (32 bits)

Quad-word (64 bits)

1 R/- -/- -/- -/- -/-

0 R/W -/- -/- -/- -/-

Device name Device No. representation

Setting range Specifications of EG devices*1

Assignment to EG devices

Access using a client

4 Holding register Decimal 00001 to 65536 (Not usable as bit data)

3 Input register Decimal 00001 to 65536 (Not usable as bit data)

6 Extension file register Decimal (File No.)-6(Device) Notation example: 418-600000 File No. (decimal): 0 to 418 Device (decimal): 00000 to 09999

(Not usable as bit data)

Device name Device type

Word (16 bits) Double-word (32 bits) Quad-word (64 bits) Bit of word data 4 R/W R/W -/- R/W

3 R/- R/- -/- R/-

6 R/W R/W -/- R/W

2 APPX Appendix 1 Settable Device Range

A

Notation of devices ([MODBUS Slave(GOT:Master)]) The notation of addresses and that of devices differ between the MODBUS/RTU communication protocol and GT Designer3. Set the devices using the notation used in GT Designer3.

Example) Monitoring the holding register 1234 (hexadecimal) Set 404661 in GT Designer3.

Notation in the communication protocol Notation in the GOT

Device name Address (hexadecimal) Device name Device No. (decimal) Coils 0000 to FFFF 0 00001 to 65536

Input relay 0000 to FFFF 1 00001 to 65536

Input register 0000 to FFFF 3 00001 to 65536

Holding register 0000 to FFFF 4 00001 to 65536

Extension file register 0000 to 270F 6 00000 to 09999

Notation in the communication protocol Holding register 1234 (hexadecimal)

Device name: 4 Device No.: 04660 (decimal) + 1

Notation in GT Designer3 404661 (decimal)

APPX Appendix 1 Settable Device Range 443

44

MODBUS ([MODBUS Master(GOT:Slave)])

Device setting dialog ([MODBUS Master(GOT:Slave)]) Set a device to be monitored.

1) Title Data type and channel number of the device to be set 2) [Device] Set the device name and device number. If a bit number needs to be specified, the setting item is displayed. Example) Setting of 100001

3) [Information] Displays the setting range of each setting item according to the selected device.

Item Reference Device setting dialog Page 444 Device setting dialog ([MODBUS Master(GOT:Slave)])

Specifications of bit devices Page 445 Monitoring-supported bit devices ([MODBUS Master(GOT:Slave)])

Page 445 Availability of writing/reading data to/from bit devices ([MODBUS Master(GOT:Slave)])

Specifications of word devices Page 446 Monitoring-supported word devices ([MODBUS Master(GOT:Slave)])

Page 446 Availability of writing/reading data to/from word devices ([MODBUS Master(GOT:Slave)])

Notation of devices Page 443 Notation of devices ([MODBUS Slave(GOT:Master)])

2) 3)

1)

100001

Device name Device number

4 APPX Appendix 1 Settable Device Range

A

Monitoring-supported bit devices ([MODBUS Master(GOT:Slave)]) The following table shows monitoring-supported bit devices. To check whether writing/reading data to/from each device is available, refer to the following. Page 445 Availability of writing/reading data to/from bit devices ([MODBUS Master(GOT:Slave)]) For the formats of devices, refer to the following. GT Designer3 (GOT2000) Screen Design Manual : Available : Not available

*1 For the devices assigned to EG devices (gateway devices) and the compatible clients, refer to the following. GT Designer3 (GOT2000) Screen Design Manual

Availability of writing/reading data to/from bit devices ([MODBUS Master(GOT:Slave)]) The following shows whether writing/reading data to/from bit devices is available by device type. When the device type is other than the bit type, set the device No. in multiples of 16. R/W: Both read and write R/-: Read only -/W: Write only -/-: No read/write access

Device name Device No. representation

Setting range Specifications of EG devices*1

GT27, GT25, GT23, and SoftGOT2000

GT21 and GS21 Assignment to EG devices

Access using a client

1 Input relay Decimal 00001 to 65536 00001 to 10000

0 Coils Decimal 00001 to 65536 00001 to 10000

Device name Device type

Bit Byte (8 bits) Word (16 bits) Double-word (32 bits)

Quad-word (64 bits)

1 R/W -/- R/W R/W -/-

0 R/W -/- R/W R/W -/-

APPX Appendix 1 Settable Device Range 445

44

Monitoring-supported word devices ([MODBUS Master(GOT:Slave)]) The following table shows monitoring-supported word devices. To check whether writing/reading data to/from each device is available, refer to the following. Page 446 Availability of writing/reading data to/from word devices ([MODBUS Master(GOT:Slave)]) For the formats of devices, refer to the following. GT Designer3 (GOT2000) Screen Design Manual : Available : Not available

*1 For the devices assigned to EG devices (gateway devices) and the compatible clients, refer to the following. GT Designer3 (GOT2000) Screen Design Manual

Availability of writing/reading data to/from word devices ([MODBUS Master(GOT:Slave)]) The following shows whether writing/reading data to/from word devices is available by device type. R/W: Both read and write R/-: Read only -/W: Write only -/-: No read/write access

Device name Device No. representation

Setting range Specifications of EG devices*1

GT27, GT25, GT23, and SoftGOT2000

GT21 and GS21 Assignment to EG devices

Access using a client

4 Holding register Decimal 00001 to 65536 00001 to 10000

3 Input register Decimal 00001 to 65536 00001 to 10000

Device name Device type

Word (16 bits) Double-word (32 bits) Quad-word (64 bits) Bit of word data 4 R/W R/W -/- R/W

3 R/W R/W -/- R/W

6 APPX Appendix 1 Settable Device Range

A

PROFIBUS ([PROFIBUS DP])

Device setting dialog ([PROFIBUS DP]) Set a device to be monitored.

1) Title Data type and channel number of the device to be set 2) [Device] Set the device name and device number. If a bit number needs to be specified, the setting item is displayed. Example) Setting of PI0000

3) [Information] Displays the setting range of each setting item according to the selected device.

Item Reference Device setting dialog Page 447 Device setting dialog ([PROFIBUS DP])

Specifications of bit devices Page 448 Monitoring-supported bit devices ([PROFIBUS DP])

Page 448 Availability of writing/reading data to/from bit devices ([PROFIBUS DP])

Specifications of word devices Page 449 Monitoring-supported word devices ([PROFIBUS DP])

Page 449 Availability of writing/reading data to/from word devices ([PROFIBUS DP])

2) 3)

1)

PI0000

Device name Device number

APPX Appendix 1 Settable Device Range 447

44

Monitoring-supported bit devices ([PROFIBUS DP]) The following table shows monitoring-supported bit devices. To check whether writing/reading data to/from each device is available, refer to the following. Page 448 Availability of writing/reading data to/from bit devices ([PROFIBUS DP]) For the formats of devices, refer to the following. GT Designer3 (GOT2000) Screen Design Manual : Available : Not available

*1 For the devices assigned to EG devices (gateway devices) and the compatible clients, refer to the following. GT Designer3 (GOT2000) Screen Design Manual

Availability of writing/reading data to/from bit devices ([PROFIBUS DP]) The following shows whether writing/reading data to/from bit devices is available by device type. When the device type is other than the bit type, set the device No. in multiples of 16. To use the device as word data, use the word device that has the same device name appended with "W". Example) Use PIW for PI. R/W: Both read and write R/-: Read only -/W: Write only -/-: No read/write access

Device name Device No. representation

Setting range Specifications of EG devices*1

Assignment to EG devices

Access using a client

PI Input relay Decimal + octal PI(Byte address)(Bit address) Notation example: PI2430 Byte address (decimal): 000 to 243 Bit address (octal): 0 to 7

(Not usable as word data)

PQ Output relay Decimal + octal PQ(Byte address)(Bit address) Notation example: PQ2430 Byte address (decimal): 000 to 243 Bit address (octal): 0 to 7

(Not usable as word data)

Device name Device type

Bit Byte (8 bits) Word (16 bits) Double-word (32 bits)

Quad-word (64 bits)

PI R/W -/- -/- -/- -/-

PQ R/- -/- -/- -/- -/-

8 APPX Appendix 1 Settable Device Range

A

Monitoring-supported word devices ([PROFIBUS DP]) The following table shows monitoring-supported word devices. To check whether writing/reading data to/from each device is available, refer to the following. Page 449 Availability of writing/reading data to/from word devices ([PROFIBUS DP]) For the formats of devices, refer to the following. GT Designer3 (GOT2000) Screen Design Manual : Available : Not available

*1 For the devices assigned to EG devices (gateway devices) and the compatible clients, refer to the following. GT Designer3 (GOT2000) Screen Design Manual

*2 When the device type is the word (16 bits) type, set the device number with an even number. When the device type is the double-word (32 bits) type, set the device number in multiples of 4.

Availability of writing/reading data to/from word devices ([PROFIBUS DP]) The following shows whether writing/reading data to/from word devices is available by device type. To use the device as bit data, use the bit device that has the same device name without "W". Example) Use PI for PIW. R/W: Both read and write R/-: Read only -/W: Write only -/-: No read/write access

Device name Device No. representation

Setting range Specifications of EG devices*1

Assignment to EG devices

Access using a client

PIW*2 Input relay Decimal 0 to 242 (Not usable as bit data)

PQW*2 Output relay Decimal 0 to 242 (Not usable as bit data)

Device name Device type

Word (16 bits) Double-word (32 bits) Quad-word (64 bits) Bit of word data PIW R/W R/W -/- -/-

PQW R/- R/- -/- -/-

APPX Appendix 1 Settable Device Range 449

45

CLPA ([SLMP])

Device setting dialog ([SLMP]) Set a device to be monitored.

1) Title Data type and channel number of the device to be set 2) [Device] Set the device name and device number. If a bit number needs to be specified, the setting item is displayed. Example) Setting of X000000

3) [Information] Displays the setting range of each setting item according to the selected device. 4) [CPU No.] Set the CPU number of the controller. 5) Station type specification Select the station type (host or other) for the controller to be monitored. [Host]: The controller to be monitored is the host station. [Other]: The controller to be monitored is not the host station. 6) [Network No.] This item appears when [Other] is selected for the station type. Specify a network number. 7) [Station No.] This item appears when [Other] is selected for the station type. Specify a station number.

Item Reference Device setting dialog Page 450 Device setting dialog ([SLMP])

Specifications of bit devices Page 451 Monitoring-supported bit devices ([SLMP])

Page 452 Availability of writing/reading data to/from bit devices ([SLMP])

Specifications of word devices Page 453 Monitoring-supported word devices ([SLMP])

Page 454 Availability of writing/reading data to/from word devices ([SLMP])

2) 3)

1)

4) 5)

6)

7)

X000000

Device name Device number

0 APPX Appendix 1 Settable Device Range

A

Monitoring-supported bit devices ([SLMP]) The following table shows monitoring-supported bit devices. To check whether writing/reading data to/from each device is available, refer to the following. Page 452 Availability of writing/reading data to/from bit devices ([SLMP]) For the formats of devices, refer to the following. GT Designer3 (GOT2000) Screen Design Manual : Available : Not available

*1 For the devices assigned to EG devices (gateway devices) and the compatible clients, refer to the following. GT Designer3 (GOT2000) Screen Design Manual

*2 Not available to GT21 and GS21.

Device name Device No. representation

Setting range Specifications of EG devices*1

Assignment to EG devices

Access using a client

X Input Hexadecimal 000000 to FFFFFF

Y Output Hexadecimal 000000 to FFFFFF

B Link relay Hexadecimal 000000 to FFFFFF

M Internal relay Decimal 0 to 16777215

L Latch relay Decimal 0 to 16777215

F Annunciator Decimal 0 to 16777215

V Edge relay Decimal 0 to 16777215

TC Timer Coil Decimal 0 to 16777215 (Not usable as word data)

TS Timer contact Decimal 0 to 16777215 (Not usable as word data)

CC Counter Coil Decimal 0 to 16777215 (Not usable as word data)

CS Counter contact Decimal 0 to 16777215 (Not usable as word data)

STC Retentive timer Coil Decimal 0 to 16777215 (Not usable as word data)

STS Retentive timer Contact

Decimal 0 to 16777215 (Not usable as word data)

SB Link special relay Hexadecimal 000000 to FFFFFF

SM Special relay Decimal 0 to 16777215

DX Direct access input Hexadecimal 000000 to FFFFFF

DY Direct access output Hexadecimal 000000 to FFFFFF

JnX*2 Link input (link direct device)

Hexadecimal J(Network No.)-X(Device) Notation example: J1-X000000 Network No. (decimal): 1 to 239 Device (hexadecimal): 000000 to FFFFFF

JnY*2 Link output (link direct device)

Hexadecimal J(Network No.)-Y(Device) Notation example: J1-Y000000 Network No. (decimal): 1 to 239 Device (hexadecimal): 000000 to FFFFFF

JnB*2 Link relay (link direct device)

Hexadecimal J(Network No.)-B(Device) Notation example: J1-B000000 Network No. (decimal): 1 to 239 Device (hexadecimal): 000000 to FFFFFF

JnSB*2 Link special relay (link direct device)

Hexadecimal J(Network No.)-SB(Device) Notation example: J1-SB000000 Network No. (decimal): 1 to 239 Device (hexadecimal): 000000 to FFFFFF

APPX Appendix 1 Settable Device Range 451

45

Availability of writing/reading data to/from bit devices ([SLMP]) The following shows whether writing/reading data to/from bit devices is available by device type. When the device type is other than the bit type, set the device No. in multiples of 16. R/W: Both read and write R/-: Read only -/W: Write only -/-: No read/write access

Device name Device type

Bit Byte (8 bits) Word (16 bits) Double-word (32 bits)

Quad-word (64 bits)

X R/W -/- R/W R/W -/-

Y R/W -/- R/W R/W -/-

B R/W -/- R/W R/W -/-

M R/W -/- R/W R/W -/-

L R/W -/- R/W R/W -/-

F R/W -/- R/W R/W -/-

V R/W -/- R/W R/W -/-

TC R/W -/- -/- -/- -/-

TS R/W -/- -/- -/- -/-

CC R/W -/- -/- -/- -/-

CS R/W -/- -/- -/- -/-

STC R/W -/- -/- -/- -/-

STS R/W -/- -/- -/- -/-

SB R/W -/- R/W R/W -/-

SM R/W -/- R/W R/W -/-

DX R/W -/- R/W R/W -/-

DY R/W -/- R/W R/W -/-

JnX R/W -/- R/W R/W -/-

JnY R/W -/- R/W R/W -/-

JnB R/W -/- R/W R/W -/-

JnSB R/W -/- R/W R/W -/-

2 APPX Appendix 1 Settable Device Range

A

Monitoring-supported word devices ([SLMP]) The following table shows monitoring-supported word devices. To check whether writing/reading data to/from each device is available, refer to the following. Page 454 Availability of writing/reading data to/from word devices ([SLMP]) For the formats of devices, refer to the following. GT Designer3 (GOT2000) Screen Design Manual : Available : Not available

Device name Device No. representation

Setting range Specifications of EG devices*1

Assignment to EG devices

Access using a client

TN Timer (current value) Decimal 0 to 16777215 (Not usable as bit data)

CN Counter (current value)

Decimal 0 to 16777215 (Not usable as bit data)

STN Retentive timer (current value)

Decimal 0 to 16777215 (Not usable as bit data)

D Data register Decimal 0 to 16777215

SD Special register Decimal 0 to 16777215

W Link register Hexadecimal 000000 to FFFFFF

SW Link special register Hexadecimal 000000 to FFFFFF

R File register (Block switching method)

Decimal 0 to 16777215

ZR File register (Serial number access method)

Hexadecimal 000000 to FFFFFF

Z Index register Decimal 0 to 16777215

G*2 Module access device (buffer memory)

Decimal U(Unit No.)-G(Device) Notation example: UFF-G0 Unit No.(hexadecimal): 00 to FF Device (decimal): 0 to 16777215

U3E0G*

2 CPU buffer memory Decimal U3E0-G(Device)

Notation example: U3E0-G0 Device (decimal): 0 to 16777215

U3E1G*

2 CPU buffer memory Decimal U3E1-G(Device)

Notation example: U3E1-G0 Device (decimal): 0 to 16777215

U3E2G*

2 CPU buffer memory Decimal U3E2-G(Device)

Notation example: U3E2-G0 Device (decimal): 0 to 16777215

U3E3G*

2 CPU buffer memory Decimal U3E3-G (Device)

Notation example: U3E3-G0 Device (decimal): 0 to 16777215

U3E0H G*2

Fixed-cycle area of the CPU buffer memory (multiple CPU high speed transmission memory)

Decimal U3E0-HG(Device) Notation example: U3E0-HG0 Device (decimal): 0 to 16777215

U3E1H G*2

Fixed-cycle area of the CPU buffer memory (multiple CPU high speed transmission memory)

Decimal U3E1-HG(Device) Notation example: U3E1-HG0 Device (decimal): 0 to 16777215

U3E2H G*2

Fixed-cycle area of the CPU buffer memory (multiple CPU high speed transmission memory)

Decimal U3E2-HG(Device) Notation example: U3E2-HG0 Device (decimal): 0 to 16777215

APPX Appendix 1 Settable Device Range 453

45

*1 For the devices assigned to EG devices (gateway devices) and the compatible clients, refer to the following. GT Designer3 (GOT2000) Screen Design Manual

*2 Not available to GT21 and GS21.

Availability of writing/reading data to/from word devices ([SLMP]) The following shows whether writing/reading data to/from word devices is available by device type. R/W: Both read and write R/-: Read only -/W: Write only -/-: No read/write access

*1 When bit specification of word device is performed, the GOT reads the value from a device and then write a value to the device. Do not change the device value with a sequence program until the GOT completes writing a value to the device.

U3E3H G*2

Fixed-cycle area of the CPU buffer memory (multiple CPU high speed transmission memory)

Decimal U3E3-HG(Device) Notation example: U3E3-HG0 Device (decimal): 0 to 16777215

JnW*2 Link register (link direct device)

Hexadecimal J(Network No.)-W(Device) Notation example: J1-W000000 Network No. (decimal): 1 to 239 Device (hexadecimal): 000000 to FFFFFF

JnSW*2 Link special register (link direct device)

Hexadecimal J(Network No.)-SW(Device) Notation example: J1-SW000000 Network No. (decimal): 1 to 239 Device (hexadecimal): 000000 to FFFFFF

RD*2 Refresh data register Decimal 0 to 4294967295

Device name Device type

Word (16 bits) Double-word (32 bits) Quad-word (64 bits) Bit of word data TN R/W R/W -/- -/-

CN R/W R/W -/- -/-

STN R/W R/W -/- -/-

D*1 R/W R/W -/- R/W

SD*1 R/W R/W -/- R/W

W*1 R/W R/W -/- R/W

SW*1 R/W R/W -/- R/W

R*1 R/W R/W -/- R/W

ZR*1 R/W R/W -/- R/W

Z R/W R/W -/- -/-

G R/W R/W -/- R/W

U3E0G R/W R/W -/- R/W

U3E1G R/W R/W -/- R/W

U3E2G R/W R/W -/- R/W

U3E3G R/W R/W -/- R/W

U3E0HG R/W R/W -/- R/W

U3E1HG R/W R/W -/- R/W

U3E2HG R/W R/W -/- R/W

U3E3HG R/W R/W -/- R/W

JnW R/W R/W -/- R/W

JnSW R/W R/W -/- R/W

RD R/W R/W -/- R/W

Device name Device No. representation

Setting range Specifications of EG devices*1

Assignment to EG devices

Access using a client

4 APPX Appendix 1 Settable Device Range

A

CLPA ([CC-Link IE Field Network Basic])

Device setting dialog ([CC-Link IE Field Network Basic]) Set a device to be monitored.

1) Title Data type and channel number of the device to be set 2) [Device] Set the device name and device number. If a bit number needs to be specified, the setting item is displayed. Example) Setting of RX000

3) [Information] Displays the setting range of each setting item according to the selected device.

Item Reference Device setting dialog Page 455 Device setting dialog ([CC-Link IE Field Network Basic])

Specifications of bit devices Page 456 Monitoring-supported bit devices ([CC-Link IE Field Network Basic])

Page 456 Availability of writing/reading data to/from bit devices ([CC-Link IE Field Network Basic])

Specifications of word devices Page 457 Monitoring-supported word devices ([CC-Link IE Field Network Basic])

Page 457 Availability of writing/reading data to/from word devices ([CC-Link IE Field Network Basic])

Remote device setting of the GOT (remote station)

Page 458 Remote device setting of the GOT (remote station) ([CC-Link IE Field Network Basic])

2) 3)

1)

RX000

Device name Device number

APPX Appendix 1 Settable Device Range 455

45

Monitoring-supported bit devices ([CC-Link IE Field Network Basic]) The following table shows monitoring-supported bit devices. The device range shown in this section indicates the maximum settable values in GT Designer3. The range of devices that can actually be monitored depends on the number of stations occupied by remote stations that are set in the master station. Before setting the device range, check the number of occupied stations that are assigned to the GOT. If a non-existent device or a device number out of the range is set for an object, other objects for which correct devices are set may not be monitored. To check whether writing/reading data to/from each device is available, refer to the following. Page 456 Availability of writing/reading data to/from bit devices ([CC-Link IE Field Network Basic]) For the formats of devices, refer to the following. GT Designer3 (GOT2000) Screen Design Manual : Available : Not available

*1 For the devices assigned to EG devices (gateway devices) and the compatible clients, refer to the following. GT Designer3 (GOT2000) Screen Design Manual

Availability of writing/reading data to/from bit devices ([CC-Link IE Field Network Basic]) The following shows whether writing/reading data to/from bit devices is available by device type. When the device type is other than the bit type, set the device No. in multiples of 16. R/W: Both read and write R/-: Read only -/W: Write only -/-: No read/write access

Device name Device No. representation

Setting range Specifications of EG devices*1

Assignment to EG devices

Access using a client

RX Remote input Hexadecimal 000 to 3FF

RY Remote output Hexadecimal 000 to 3FF

Device name Device type

Bit Byte (8 bits) Word (16 bits) Double-word (32 bits)

Quad-word (64 bits)

RX R/W -/- R/W R/W -/-

RY R/W -/- R/W R/W -/-

6 APPX Appendix 1 Settable Device Range

A

Monitoring-supported word devices ([CC-Link IE Field Network Basic]) The following table shows monitoring-supported word devices. The device range shown in this section indicates the maximum settable values in GT Designer3. The range of devices that can actually be monitored depends on the number of stations occupied by remote stations that are set in the master station. Before setting the device range, check the number of occupied stations that are assigned to the GOT. If a non-existent device or a device number out of the range is set for an object, other objects for which correct devices are set may not be monitored. To check whether writing/reading data to/from each device is available, refer to the following. Page 457 Availability of writing/reading data to/from word devices ([CC-Link IE Field Network Basic]) For the formats of devices, refer to the following. GT Designer3 (GOT2000) Screen Design Manual : Available : Not available

*1 For the devices assigned to EG devices (gateway devices) and the compatible clients, refer to the following. GT Designer3 (GOT2000) Screen Design Manual

Availability of writing/reading data to/from word devices ([CC-Link IE Field Network Basic]) The following shows whether writing/reading data to/from word devices is available by device type. R/W: Both read and write R/-: Read only -/W: Write only -/-: No read/write access

Device name Device No. representation

Setting range Specifications of EG devices*1

Assignment to EG devices

Access using a client

Ww Remote register Hexadecimal 000 to 1FF

Wr Remote register Hexadecimal 000 to 1FF

Device name Device type

Word (16 bits) Double-word (32 bits) Quad-word (64 bits) Bit of word data Ww R/W R/W -/- R/W

Wr R/W R/W -/- R/W

APPX Appendix 1 Settable Device Range 457

45

Remote device setting of the GOT (remote station) ([CC-Link IE Field Network Basic]) The devices assigned to the GOT in the master station are allocated in the range starting from the first number in the GOT. The following shows the examples of device assignment in the master station and in the GOT (remote station). In the example of remote device assignment (RX/RY 1 station occupied), the remote devices assigned to the GOT (remote station) are RX100 to RX13F and RY100 to RY13F in the master station. Note that the corresponding remote devices in the GOT are RX000 to RX03F and RY000 to RY03F.

Example of remote device assignment RX/RY 1 station occupied

Example of remote device assignment Ww/Wr 1 station occupied

Master station RX/RY

GOT (remote station) RX/RY

Master station Ww/Wr

GOT (remote station) Ww/Wr

100

13F

000

03F 100

11F

000

01F

Example of remote device assignment RX/RY 2 station occupied

Example of remote device assignment Ww/Wr 2 station occupied

Master station RX/RY

GOT (remote station) RX/RY

Master station Ww/Wr

GOT (remote station) Ww/Wr

100

17F

000

07F

100

13F

000

03F

8 APPX Appendix 1 Settable Device Range

REVISIONS * The manual number is given on the bottom left of the back cover.

Revision date * Manual Number Revision Sep. 2013 SH(NA)-081200ENG-A Compatible with GT Works3 Version1.100E

Nov. 2013 SH(NA)-081200ENG-B Compatible with GT Works3 Version1.104J Compatible with printer connection Compatible with wireless LAN connection (To be supported soon) Changing the icons of the supported models

Jan. 2014 SH(NA)-081200ENG-C Compatible with GT Works3 Version1.108N Compatible with wireless LAN connection The operation panel function is supported.

Apr. 2014 SH(NA)-081200ENG-D Compatible with GT Works3 Version1.112S GT25 and GS21 have been added. Indirect specification and all station specification for the station No. of MODBUS/RTU are supported.

Jun. 2014 SH(NA)-081200ENG-E Compatible with GT Works3 Version1.117X Communication driver (Serial (MELSEC)) compatible.

Oct. 2014 SH(NA)-081200ENG-F Compatible with GT Works3 Version1.122C GT21 is added. IP filter setting compatible.

Jan. 2015 SH(NA)-081200ENG-G Compatible with GT Works3 Version1.126G GT21 corresponding to MODBUS/TCP connection. BAR CODE READER

Compatible with Communication Type of the RS-422/485 RFID connection Change the manufacturer name (MARS TECHNO SCIENCE MARS TOHKEN

SOLUTION)

Apr. 2015 SH(NA)-081200ENG-H Compatible with GT Works3 Version1.130L DeviceNet connection is supported. PROFIBUS DP connection is supported. GT27 is added (GT2705-VTBD). GT21 is added (GT2104-RTBD, GT2103-PMBDS2, GT2103-PMBLS).

Jun. 2015 SH(NA)-081200ENG-I Compatible with GT Works3 Version1.134Q SLMP connection is supported. Microcomputer connection (Ethernet) of GT21 is supported.

Jul. 2015 SH(NA)-081200ENG-J Some corrections

Oct. 2015 SH(NA)-081200ENG-K Compatible with GT Works3 Version1.144A GT21 is added (GT2104-PMBD, GT2104-PMBDS). GOT Mobile connection is supported. Using the wireless LAN communication unit as an access point is supported. MODBUS/TCP connection Port No. extension compatible

Dec. 2015 SH(NA)-081200ENG-L Compatible with GT Works3 Version1.150G Station blocking function compatible Ethernet connection Station monitoring function of the following connection

CC-Link IE Controller network connection CC-Link IE Field Network connection The corresponding to the function extension of the Microcomputer connection (Serial/Ethernet) format 1,2 SLMP connection of GT21 is supported.

May 2016 SH(NA)-081200ENG-M Compatible with GT Works3 Version1.155M GT21 is added (GT2105-QTBDS, GT2105-QMBDS, GT2104-PMBDS2, GT2104-PMBLS). Compatible with DeviceNet communication module type number AB6909-C Compatible with PROFIBUS communication module type number AB6910-C

Aug. 2016 SH(NA)-081200ENG-N Compatible with GT Works3 Version1.160S GOT2000 series Ethernet communication unit is supported.

Oct. 2016 SH(NA)-081200ENG-O Compatible with GT Works3 Version1.165X CC-Link IE Field Network Basic connection is supported.

459

46

2013 MITSUBISHI ELECTRIC CORPORATION

Jan. 2017 SH(NA)-081200ENG-P Compatible with GT Works3 Version1.170C GT2107-W is added (GT2107-WTBD, GT2107-WTSD). MODBUS/RTU SLAVE connection is supported. MODBUS/TCP SLAVE connection is supported.

Apr. 2017 SH(NA)-081200ENG-Q Compatible with GT Works3 Version1.175H GT25 is added (GT25-W). USB Bar code is supported. GT21 CC-Link IE Field Network Basic connection is supported. GT2107-W VNC server function is supported.

Jun. 2017 SH(NA)-081200ENG-R Compatible with GT Works3 Version1.180N GT25 is added (GT2505-V) For Ethernet connection, the default value of the GOT station No. is changed to [18].

Oct. 2017 SH(NA)-081200ENG-S Some corrections

Dec. 2017 SH(NA)-081200ENG-T Compatible with GT Works3 Version 1.190Y Compatible with avoiding overlapping of [GOT Communication Port No.]

Apr. 2018 SH(NA)-081200ENG-U Compatible with GT Works3 Version1.195D CC-Link IE Field Network Basic connection the following function is supported.

When the operation of the master station is stopped, select HOLD/CLEAR.

Jul. 2018 SH(NA)-081200ENG-V Compatible with GT Works3 Version1.200J The connection to Ethernet printer is supported. In the communication detail settings of the microcomputer connection (Ethernet), setting the request

destination module I/O number is supported. For the MODBUS/TCP master connection, the connection with the device where the module ID is fixed to

255.

Oct. 2018 SH(NA)-081200ENG-W Compatible with GT Works3 Version1.205P GT2505-V supports the following connection using the RS-232/485 signal conversion adapter (GT14-

RS2T4-9P). MODBUS/RTU master connection Digital video output unit (GT27-VHOUT) is supported.

Jan. 2019 SH(NA)-081200ENG-X Compatible with GT Works3 Version 1.210U Some corrections

Apr. 2019 SH(NA)-081200ENG-Y Compatible with GT Works3 Version1.215Z The connection to Ethernet printer (PCL5) is supported.

Jul. 2019 SH(NA)-081200ENG-Z Compatible with GT Works3 Version1.220E The manufacturer name has been changed. (Digital Electronics Corporation Schneider Electric Japan

Holdings Ltd.) For the SLMP connection, the connection with the CC-Link IE TSN master/local module (RJ71GN11-T2) is

supported.

Oct. 2019 SH(NA)-081200ENG-AA Some corrections

Jan. 2020 SH(NA)-081200ENG-AB Some corrections

Apr. 2020 SH(NA)-081200ENG-AC Compatible with GT Works3 Version1.235V SLMP-compatible devices have been added.

Oct. 2020 SH(NA)-081200ENG-AD Compatible with GT Works3 Version1.245F The company name of TOSHIBA MACHINE CO., LTD. has been changed to SHIBAURA MACHINE CO.,

LTD.

Jan. 2021 SH(NA)-081200ENG-AE Compatible with GT Works3 Version1.250L GT25 is added (GT2512-WXTBD, GT2512-WXTSD). GS21 is added (GS2110-WTBD-N, GS2107-WTBD-N).

Apr. 2021 SH(NA)-081200ENG-AF Some corrections

Jul. 2021 SH(NA)-081200ENG-AG Some corrections

Oct. 2021 SH(NA)-081200ENG-AH Some corrections

Jan. 2022 SH(NA)-081200ENG-AI Some corrections

Apr. 2022 SH(NA)-081200ENG-AJ Some corrections

Jul. 2022 SH(NA)-081200ENG-AK Some corrections

Oct. 2022 SH(NA)-081200ENG-AL Some corrections

Jan. 2023 SH(NA)-081200ENG-AM Some corrections

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.

Revision date * Manual Number Revision

0

WARRANTY Please check the following product warranty details before using this product.

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.

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.

Failure occurring from inappropriate storage or handling, carelessness or negligence by the user. Failure caused by the user's hardware or software design.

Failure caused by unapproved modifications, etc., to the product by the user. 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.

Failure that could have been avoided if consumable parts designated in the instruction manual had been correctly serviced or replaced.

Replacing consumable parts such as a battery, backlight, and fuse. 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. Failure caused by reasons that could not be predicted by scientific technology standards at the time of shipment from

Mitsubishi. Any other failure found not to be the responsibility of Mitsubishi or that admitted not to be so by the user.

(1) Gratis Warranty Term

(2) Gratis Warranty Range (a) 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 customers expense. The primary failure diagnosis will, however, be free of charge should the cause of failure be attributable to Mitsubishi Electric Corporation.

(b) 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.

(c) Even within the gratis warranty term, repairs shall be charged in the following cases.

Gratis Warranty Term and Gratis Warranty Range

(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) Mitsubishi shall not accept a request for product supply (including spare parts) after production is discontinued.

Onerous repair term after discontinuation of production

Overseas, repairs shall be accepted by Mitsubishi's local overseas FA Center. Note that the repair conditions at each FA Center may differ.

Overseas service

Regardless of the gratis warranty term, Mitsubishi shall not be liable for compensation to: Exclusion of loss in opportunity and secondary loss from warranty liability

The specifications given in the catalogs, manuals, or technical documents are subject to change without prior notice. Changes in product specifications

(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 shall be excluded from the graphic operation terminal applications. In addition, applications in which human life or property could be greatly affected, such as in aircraft, medical, railway applications, incineration and fuel devices, manned transportation equipment, recreation and amusement devices, safety devices, shall also be excluded from the graphic operation terminal. Even for the above applications, 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, after the user consults the local Mitsubishi representative.

Product application

(1) Damages caused by any cause found not to be the responsibility of Mitsubishi. (2) Loss in opportunity, lost profits incurred to the user by Failures of Mitsubishi products. (3) Special damages and secondary damages whether foreseeable or not, compensation for accidents, and compensation for

damages to products other than Mitsubishi products. (4) Replacement by the user, maintenance of on-site equipment, start-up test run and other tasks.

461

462 SH(NA)-081200ENG-AM

Intellectual Property Rights Trademarks MELDAS, MELSEC, iQ Platform, MELSOFT, GOT, CC-Link, CC-Link/LT, and CC-Link IE are trademarks or registered trademarks of Mitsubishi Electric Corporation in Japan and other countries. Microsoft, Microsoft Access, Excel, SQL Server, Visual Basic, Visual C++, Visual C#, Windows, Windows NT, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies. MODBUS is a trademark of Schneider Electric SA. DeviceNet is a trademark of ODVA (Open DeviceNet Vendor Association, Inc.). VNC is a registered trademark of RealVNC Ltd. in the United States and other countries. Unicode is a trademark or registered trademark of Unicode, Inc. in the United States and other countries. PictBridge is a registered trademark of Canon Inc. Adobe and Adobe Reader are registered trademarks of Adobe Systems Incorporated. Oracle and JavaScript are registered trademarks of Oracle Corporation and/or its affiliates in the United States and other countries. QR Code is a trademark or registered trademark of DENSO WAVE INCORPORATED in Japan, the United States, and/or other countries. Anybus is a registered trademark of HMS Industrial Networks AB. Android and Google Chrome are trademarks or registered trademarks of Google Inc. IOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used under license. Safari and iPhone are trademarks of Apple Inc. registered in the United States and other countries. The iPhone trademark is used under license from AIPHONE CO., LTD. Intel and Intel Core are trademarks or registered trademarks of Intel Corporation in the United States and other countries. Other company and product names herein are trademarks or registered trademarks of their respective owners. Copyrights The screens (screenshots) are used in accordance with the Microsoft Corporation guideline.

SH(NA

Manualsnet FAQs

If you want to find out how the GOT2000 Mitsubishi works, you can view and download the Mitsubishi GOT2000 GT25 Microcomputer Connection Manual on the Manualsnet website.

Yes, we have the Connection Manual for Mitsubishi GOT2000 as well as other Mitsubishi manuals. All you need to do is to use our search bar and find the user manual that you are looking for.

The Connection Manual should include all the details that are needed to use a Mitsubishi GOT2000. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.

The best way to navigate the Mitsubishi GOT2000 GT25 Microcomputer Connection Manual is by checking the Table of Contents at the top of the page where available. This allows you to navigate a manual by jumping to the section you are looking for.

This Mitsubishi GOT2000 GT25 Microcomputer Connection Manual consists of sections like Table of Contents, to name a few. For easier navigation, use the Table of Contents in the upper left corner.

You can download Mitsubishi GOT2000 GT25 Microcomputer Connection Manual free of charge simply by clicking the “download” button in the upper right corner of any manuals page. This feature allows you to download any manual in a couple of seconds and is generally in PDF format. You can also save a manual for later by adding it to your saved documents in the user profile.

To be able to print Mitsubishi GOT2000 GT25 Microcomputer Connection Manual, simply download the document to your computer. Once downloaded, open the PDF file and print the Mitsubishi GOT2000 GT25 Microcomputer Connection Manual as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.