Mitsubishi Ethernet Driver

© 2020 PTC Inc. All Rights Reserved.

Mitsubishi Ethernet Driver 2

Table of Contents
M itsubishi Ethernet Driver 1

Table of Contents 2

Mitsubishi Ethernet Driver 4

Overview 4

Setup 4
Channel Properties — General 5
Channel Properties — Ethernet Communications 6
Channel Properties — Write Optimizations 6
Channel Properties — Advanced 7
Device Properties — General 8
Device Properties — Scan Mode 9
Device Properties — Timing 10
Device Properties — Auto-Demotion 11
Device Properties — 32-Bit Data 11
Device Properties — Communications Parameters 12
Device Properties — Time and Date Synchronization 14
Device Properties — Redundancy 14

Multi-Level Networks 16

Optimizing Communications 17

Data Types Description 18

Address Descriptions 19

Mitsubishi A Series Address Descriptions 19

Mitsubishi FX3U Series Address Descriptions 22

Mitsubishi L Series Address Descriptions 25

Mitsubishi Q Series Address Descriptions 30

Mitsubishi iQ-R Series Address Descriptions 35

Mitsubishi iQ-F Series Address Descriptions 40

Mitsubishi QnA Series Address Descriptions 44

Event Log M essages 50

Unable to read from address block on device. The device reported an invalid address or an error.
| Address block = '<address>' to '<address>'. 50
Unable to read from device. The device returned a PC number error. 50
Unable to write to address on device. The device returned a PC number error. | Address =
'<address>'. 50
Unable to write to address on device. The device reported an invalid address or an error. |
Address = '<address>'. 51

www. ptc.com
3 M itsu b ish i Eth ern et Driver

Unable to read from address on device. The device reported an invalid address or an error. |
Address = '<address>'. 51
Unable to read from address on device. Device returned an error. | Address = '<address>', Error
code = <code>. 52
Unable to read from address block on device. Device returned an error. | Address block =
'<address>' to '<address>', Error code = <code>. 52
Unable to write to address on device. Device returned error. | Address = '<address>', Error code
= <code>. 52
Unable to read from address block on device. | Address block = '<address>' to '<address>'. 52
Unable to read from address on device. | Address = '<address>'. 53
Unable to write to address on device. Device must be configured to allow writes while in RUN
mode. | Address = '<address>'. 53
Failed to synchronize time and date for device. | Retry interval = <number> (minutes). 53

Appendix: PLC Setup 55

A Series PLC Setup 55

FX3U Series PLC Setup 57

L Series PLC Setup 61

L Series Built-in Ethernet Port PLC Setup 68

QnA Series PLC Setup 71

Q Series PLC Setup 73

iQ-R Series PLC Setup 78

iQ-F Series PLC Setup 80

Q Series Built-in Ethernet Port PLC Setup 83

Index 87

www. ptc.com
4 M itsu b ish i Eth ern et Driver

M it subishi Et hernet Driver

Help version 1.099

CONTENTS

Overview
What is the Mitsubishi Ethernet Driver?

Device Set up
How do I configure a device for use with this driver?

Opt imizing M it subishi Et hernet Communicat ions

How do I get the best performance from the Mitsubishi Ethernet Driver?

Dat a Types Descript ion

What data types does this driver support?

Address Descript ions

How do I address a data location on a Mitsubishi A Series and Q Series Ethernet devices?

Event Log M essages

What messages does the Mitsubishi Ethernet Driver produce?

Overview
The Mitsubishi Ethernet Driver provides a reliable way to connect Mitsubishi Ethernet devices to OPC client
applications; including HMI, SCADA, Historian, MES, ERP, and countless custom applications. It is intended
for use with Mitsubishi A Series and Mitsubishi Q Series devices communicating via the AJ71E71, A1SJ71E71,
AJ71QE71, A1SJ71QE71, QJ71E71, or LJ71E71 Ethernet communications cards. A built-in Ethernet Port is sup-
ported for Q and L Series devices. This driver also supports the FX3U series PLC via the FX3U-ENET Ethernet
module.

N ote: Communications card model numbers listed are the base model number only. All suffixes are sup-
ported.

Set up
Supported Devices
A Series PLCs
QnA Series PLCs
Q (Q mode) Series PLCs
L Series PLCs
FX3U Series PLCs
iQ-R Series PLCs
iQ-F Series PLCs

Communication Protocol
Ethernet: using Winsock V1.1 or higher
TCP/IP, UDP

Supported Communication Parameters

www. ptc.com
Mitsubishi Ethernet Driver 5

Binary format only

The maximum number of channels that are supported is 256. The maximum number of devices supported is
255 per channel.
Channel Propert ies
Device Propert ies

Channel Propert ies — General

This server supports the use of simultaneous multiple communications drivers. Each protocol or driver used
in a server project is called a channel. A server project may consist of many channels with the same com-
munications driver or with unique communications drivers. A channel acts as the basic building block of an
OPC link. This group is used to specify general channel properties, such as the identification attributes and
operating mode.

Identification

N am e: User-defined identity of this channel. In each server project, each channel name must be unique.
Although names can be up to 256 characters, some client applications have a limited display window when
browsing the OPC server's tag space. The channel name is part of the OPC browser information. The prop-
erty is required for creating a channel.
For information on reserved characters, refer to "How To... Properly Name a Channel, Device, Tag, and Tag
Group" in the server help.

Description: User-defined information about this channel.

Many of these properties, including Description, have an associated system tag.

Driver: Selected protocol / driver for this channel. This property specifies the device driver that was selected
during channel creation. It is a disabled setting in the channel properties. The property is required for cre-
ating a channel.
N ote: With the server's online full-time operation, these properties can be changed at any time. This
includes changing the channel name to prevent clients from registering data with the server. If a client has
already acquired an item from the server before the channel name is changed, the items are unaffected. If,
after the channel name has been changed, the client application releases the item and attempts to re-
acquire using the old channel name, the item is not accepted. With this in mind, changes to the properties
should not be made once a large client application has been developed. Utilize the User Manager to prevent
operators from changing properties and restrict access rights to server features.

Diagnostics

Diagnostics Capture: When enabled, this option makes the channel's diagnostic information available to
OPC applications allows the usage of statistics tags that provide feedback to client applications regarding
the operation of the channel. Because the server's diagnostic features require a minimal amount of

www. ptc.com
6 M itsu b ish i Eth ern et Driver

overhead processing, it is recommended that they be utilized when needed and disabled when not. The
default is disabled.
N ote: This property is not available if the driver does not support diagnostics.
For more information, refer to "Communication Diagnostics" and "Statistics Tags" in the server help.

Channel Propert ies — Et hernet Com m unicat ions

Ethernet Communication can be used to communicate with devices.

Ethernet Settings

N etwork Adapter: Specify the network adapter to bind. When left blank or Default is selected, the oper-
ating system selects the default adapter.

Channel Propert ies — Writ e Opt im izat ions

As with any server, writing data to the device may be the application's most important aspect. The server
intends to ensure that the data written from the client application gets to the device on time. Given this goal,
the server provides optimization properties that can be used to meet specific needs or improve application
responsiveness.

Write Optimizations

Optim ization Method: Controls how write data is passed to the underlying communications driver. The
options are:

l Write All Values for All Tags: This option forces the server to attempt to write every value to the
controller. In this mode, the server continues to gather write requests and add them to the server's
internal write queue. The server processes the write queue and attempts to empty it by writing data
to the device as quickly as possible. This mode ensures that everything written from the client applic-
ations is sent to the target device. This mode should be selected if the write operation order or the
write item's content must uniquely be seen at the target device.
l Write Only Latest Value for N on-Boolean Tags: Many consecutive writes to the same value can
accumulate in the write queue due to the time required to actually send the data to the device. If the
server updates a write value that has already been placed in the write queue, far fewer writes are
needed to reach the same final output value. In this way, no extra writes accumulate in the server's
queue. When the user stops moving the slide switch, the value in the device is at the correct value at
virtually the same time. As the mode states, any value that is not a Boolean value is updated in the

www. ptc.com
Mitsubishi Ethernet Driver 7

server's internal write queue and sent to the device at the next possible opportunity. This can greatly
improve the application performance.
N ote: This option does not attempt to optimize writes to Boolean values. It allows users to optimize
the operation of HMI data without causing problems with Boolean operations, such as a momentary
push button.
l Write Only Latest Value for All Tags: This option takes the theory behind the second optimization
mode and applies it to all tags. It is especially useful if the application only needs to send the latest
value to the device. This mode optimizes all writes by updating the tags currently in the write queue
before they are sent. This is the default mode.

Duty Cycle: is used to control the ratio of write to read operations. The ratio is always based on one read for
every one to ten writes. The duty cycle is set to ten by default, meaning that ten writes occur for each read
operation. Although the application is performing a large number of continuous writes, it must be ensured
that read data is still given time to process. A setting of one results in one read operation for every write
operation. If there are no write operations to perform, reads are processed continuously. This allows optim-
ization for applications with continuous writes versus a more balanced back and forth data flow.
N ote: It is recommended that the application be characterized for compatibility with the write optimization
enhancements before being used in a production environment.

Channel Propert ies — Advanced

This group is used to specify advanced channel properties. Not all drivers support all properties; so the
Advanced group does not appear for those devices.

N on-N orm alized Float Handling: A non-normalized value is defined as Infinity, Not-a-Number (NaN), or as
a Denormalized Number. The default is Replace with Zero. Drivers that have native float handling may
default to Unmodified. Non-normalized float handling allows users to specify how a driver handles non-nor-
malized IEEE-754 floating point data. Descriptions of the options are as follows:

l Replace with Zero: This option allows a driver to replace non-normalized IEEE-754 floating point val-
ues with zero before being transferred to clients.
l Unm odified: This option allows a driver to transfer IEEE-754 denormalized, normalized, non-num-
ber, and infinity values to clients without any conversion or changes.

N ote: This property is not available if the driver does not support floating point values or if it only supports
the option that is displayed. According to the channel's float normalization setting, only real-time driver tags
(such as values and arrays) are subject to float normalization. For example, EFM data is not affected by this
setting.

For more information on the floating point values, refer to "How To ... Work with Non-Normalized Floating
Point Values" in the server help.

Inter-Device Delay: Specify the amount of time the communications channel waits to send new requests to
the next device after data is received from the current device on the same channel. Zero (0) disables the
delay.

N ote: This property is not available for all drivers, models, and dependent settings.

www. ptc.com
8 M itsu b ish i Eth ern et Driver

Device Propert ies — General

Identification

N am e: User-defined identity of this device.

Description: User-defined information about this device.

Channel Assignm ent: User-defined name of the channel to which this device currently belongs.

Driver: Selected protocol driver for this device.

Model: The specific version of the device. Options include A Series (for all A Series PLCs), L Series (for all L
Series PLCs), Q Series (for all Q Series PLCs), QnA Series (for all QnA Series PLCs), and FX3U (for all FX3U
Series PLCs).

ID (PLC N etwork Address): the unique device identity used to specify the IP address with a PC number (and
net number if the device is a Q series PLC).

l A Series: Device IDs are specified as YYY.YYY.YYY.YYY:XXX. The YYY designates the device IP address
(each YYY byte should be in the range of 0 to 255). The XXX designates the PC Number of the target
device and can be in the range of 0 to 64 or 255 for the local PC.
l Q Series: Device IDs are specified as YYY.YYY.YYY.YYY:Nzzz:XXX or YYY.YYY.YYY.YYY:nzzz:XXX. The YYY
designates the device IP address (each YYY byte should be in the range of 0 to 255). The zzz designates
the Network Number of the target device and can be in the range of 0 to 255. The XXX designates the PC
Number of the target device and can be in the range of 0 to 64 or 255 for the local PC.
N ote: For a local connection, which is network 0, the network number can be omitted, resulting in the
format YYY.YYY.YYY.YYY:XXX. For more information, refer to Multi-level Networks.
l QnA Series: Device IDs are specified as YYY.YYY.YYY.YYY:Nzzz:XXX or YYY.YYY.YYY.YYY:nzzz:XXX. The
YYY designates the device IP address (each YYY byte should be in the range of 0 to 255). The zzz des-
ignates the Network Number of the target device and can be in the range of 0 to 255. The XXX des-
ignates the PC Number of the target device and can be in the range of 0 to 64 or 255 for the local PC.
l L Series: Device IDs are specified as YYY.YYY.YYY.YYY:Nzzz:XXX or YYY.YYY.YYY.YYY:nzzz:XXX. The YYY
designates the device IP address (each YYY byte should be in the range of 0 to 255). The zzz designates
the Network Number of the target device and can be in the range of 0 to 255. The XXX designates the PC
Number of the target device and can be in the range of 0 to 64 or 255 for the local PC.

www. ptc.com
Mitsubishi Ethernet Driver 9

l FX3U: Device IDs are specified as YYY.YYY.YYY.YYY:XXX. The YYY designates the device IP address (each
YYY byte should be in the range of 0 to 255). The XXX designates the PC Number of the target device
and can be in the range of 0 to 15 or 255 for the local PC.

N ote: The AJ71E71, A1SJ71E71, AJ71QE71, A1SJ71QE71, LJ71E71, and QJ71E71 families of com-
munications cards occupy ranges of X and Y memory. Writing to this memory may disable the card and
cause loss of communications. For more information, refer to the communications card manual.

Operating M ode

Data Collection: This property controls the device's active state. Although device communications are
enabled by default, this property can be used to disable a physical device. Communications are not attemp-
ted when a device is disabled. From a client standpoint, the data is marked as invalid and write operations
are not accepted. This property can be changed at any time through this property or the device system tags.

Sim ulated: This option places the device into Simulation Mode. In this mode, the driver does not attempt to
communicate with the physical device, but the server continues to return valid OPC data. Simulated stops
physical communications with the device, but allows OPC data to be returned to the OPC client as valid data.
While in Simulation Mode, the server treats all device data as reflective: whatever is written to the simulated
device is read back and each OPC item is treated individually. The item's memory map is based on the group
Update Rate. The data is not saved if the server removes the item (such as when the server is reinitialized).
The default is No.

N otes:

1. This System tag (_Simulated) is read only and cannot be written to for runtime protection. The System
tag allows this property to be monitored from the client.

2. In Simulation mode, the item's memory map is based on client update rate(s) (Group Update Rate for
OPC clients or Scan Rate for native and DDE interfaces). This means that two clients that reference
the same item with different update rates return different data.

Simulation Mode is for test and simulation purposes only. It should never be used in a production envir-
onment.

Device Propert ies — Scan M ode

The Scan Mode specifies the subscribed-client requested scan rate for tags that require device com-
munications. Synchronous and asynchronous device reads and writes are processed as soon as possible;
unaffected by the Scan Mode properties.

Scan Mode: Specifies how tags in the device are scanned for updates sent to subscribing clients. Descrip-
tions of the options are:

l Respect Client-Specified Scan Rate: This mode uses the scan rate requested by the client.
l Request Data N o Faster than Scan Rate: This mode specifies the value set as the maximum scan
rate. The valid range is 10 to 99999990 milliseconds. The default is 1000 milliseconds.
N ote: When the server has an active client and items for the device and the scan rate value is

www. ptc.com
10 M itsu b ish i Eth ern et Driver

increased, the changes take effect immediately. When the scan rate value is decreased, the changes
do not take effect until all client applications have been disconnected.
l Request All Data at Scan Rate: This mode forces tags to be scanned at the specified rate for sub-
scribed clients. The valid range is 10 to 99999990 milliseconds. The default is 1000 milliseconds.
l Do N ot Scan, Dem and Poll Only: This mode does not periodically poll tags that belong to the
device nor perform a read to get an item's initial value once it becomes active. It is the client's
responsibility to poll for updates, either by writing to the _DemandPoll tag or by issuing explicit device
reads for individual items. For more information, refer to "Device Demand Poll" in server help.
l Respect Tag-Specified Scan Rate: This mode forces static tags to be scanned at the rate specified
in their static configuration tag properties. Dynamic tags are scanned at the client-specified scan
rate.

Initial Updates from Cache: When enabled, this option allows the server to provide the first updates for
newly activated tag references from stored (cached) data. Cache updates can only be provided when the
new item reference shares the same address, scan rate, data type, client access, and scaling properties. A
device read is used for the initial update for the first client reference only. The default is disabled; any time a
client activates a tag reference the server attempts to read the initial value from the device.

Device Propert ies — Tim ing

The device Timing properties allow the driver's response to error conditions to be tailored to fit the applic-
ation's needs. In many cases, the environment requires changes to these properties for optimum per-
formance. Factors such as electrically generated noise, modem delays, and poor physical connections can
influence how many errors or timeouts a communications driver encounters. Timing properties are specific
to each configured device.

Communications Timeouts
Connect Tim eout: This property (which is used primarily by Ethernet based drivers) controls the amount of
time required to establish a socket connection to a remote device. The device's connection time often takes
longer than normal communications requests to that same device. The valid range is 1 to 30 seconds. The
default is typically 3 seconds, but can vary depending on the driver's specific nature. If this setting is not sup-
ported by the driver, it is disabled.
N ote: Due to the nature of UDP connections, the connection timeout setting is not applicable when com-
municating via UDP.

Request Tim eout: This property specifies an interval used by all drivers to determine how long the driver
waits for a response from the target device to complete. The valid range is 50 to 9,999,999 milliseconds
(167.6667 minutes). The default is usually 1000 milliseconds, but can vary depending on the driver. The
default timeout for most serial drivers is based on a baud rate of 9600 baud or better. When using a driver
at lower baud rates, increase the timeout to compensate for the increased time required to acquire data.

Attem pts Before Tim eout: This property specifies how many times the driver issues a communications
request before considering the request to have failed and the device to be in error. The valid range is 1 to

www. ptc.com
Mitsubishi Ethernet Driver 11

10. The default is typically 3, but can vary depending on the driver's specific nature. The number of attempts
configured for an application depends largely on the communications environment. This property applies to
both connection attempts and request attempts.

Device Propert ies — Aut o-Dem ot ion

The Auto-Demotion properties can temporarily place a device off-scan in the event that a device is not
responding. By placing a non-responsive device offline for a specific time period, the driver can continue to
optimize its communications with other devices on the same channel. After the time period has been
reached, the driver re-attempts to communicate with the non-responsive device. If the device is responsive,
the device is placed on-scan; otherwise, it restarts its off-scan time period.

Dem ote on Failure: When enabled, the device is automatically taken off-scan until it is responding again.
Tip: Determine when a device is off-scan by monitoring its demoted state using the _AutoDemoted sys-
tem tag.

Tim eouts to Dem ote: Specify how many successive cycles of request timeouts and retries occur before the
device is placed off-scan. The valid range is 1 to 30 successive failures. The default is 3.

Dem otion Period: Indicate how long the device should be placed off-scan when the timeouts value is
reached. During this period, no read requests are sent to the device and all data associated with the read
requests are set to bad quality. When this period expires, the driver places the device on-scan and allows for
another attempt at communications. The valid range is 100 to 3600000 milliseconds. The default is 10000
milliseconds.

Discard Requests when Dem oted: Select whether or not write requests should be attempted during the
off-scan period. Disable to always send write requests regardless of the demotion period. Enable to discard
writes; the server automatically fails any write request received from a client and does not post a message
to the Event Log.

Device Propert ies — 32-Bit Dat a

First Word Low: In a Mitsubishi Ethernet device, the addresses of two consecutive registers are used for
32-bit data types. When this option is enabled, the driver assumes the first word is low for the 32-bit value.
When this option is disabled, the driver assumes that the first word is high for the 32-bit value. The default
setting is enabled.

N ote: This property can't be changed while there are active references on the device.

www. ptc.com
12 M itsu b ish i Eth ern et Driver

Device Propert ies — Com m unicat ions Param et ers

Communications Parameters

IP Protocol: Select the IP protocol: TCP/IP or UDP. TCP/IP is less efficient than UDP and requires a special lad-
der for network error recovery in the A and QnA series PLCs. Furthermore, Q series users planning to com-
municate with devices on a remote network must configure multiple ports in the relay device when using
TCP/IP. As such, UDP is recommended wherever possible.
For more information, refer to Multi-level Networks.

Port N um ber: Specify the port number to use when communicating with the device. The default for UDP is
5000. The default for TCP is 5001.

CPU: Specify the target CPU to connect with. For a single CPU, select Local CPU. The default value is Local
CPU.
N otes:

1. The default settings are based on GX Developer version 8.25B.

2. This property can't be changed while there are active references to the device.

Write Full String Length: Specify if the driver should add NULL character bytes after the end of a string
when writing to the device. Adding NULL character bytes after the end of the string ensures that the device
memory for the string only contains the characters that were written. The default setting is False.

Read Block Size

Bit Mem ory: Set the maximum number of words per read request of bit-based memory. The default value is
the maximum value allowed.

M inimum Bit Block Size M aximum Bit Block Size

A Series One Word 127 Words
Q Series One Word 959 Words
QnA Series One Word 479 Words
L Series One Word 959 Words

www. ptc.com
Mitsubishi Ethernet Driver 13

M inimum Bit Block Size M aximum Bit Block Size

FX3U Series One Word 31 Words
iQ-R Series One Word 959 Words
iQ-F Series One Word 959 Words

Word Mem ory: Set the maximum number of words per read request of word-based memory. The default
value is the maximum value allowed.

M inimum Word Block Size M aximum Word Block Size

A Series One Word 253 Words
Q Series One Word 957 Words
QnA Series One Word 477 Words
L Series One Word 957 Words
FX3U Series One Word 61 Words
iQ-R Series One Word 957 Words
iQ-F Series One Word 957 Words

N ote: If opening an .opf or .xml file from version 6.0 or earlier, the Bit/Word Block Size is initially set to val-
ues shown in the following table to match earlier versions. If opening a JSON file saved with 6.0, the prop-
erties are set to the default values.

Init ial Bit Block Size Init ial Word Block Size
A Series 125 Words 252 Words
Q Series 125 Words 252 Words
FX3U Series 30 Words 60 Words

Write Request Size

Max Bits per Request: Set the maximum number of bit tags to be processed per write request. If writing to
a size larger than this setting, multiple write requests are processed. The default value is the maximum
value allowed.

M inimum Bit s per Request M aximum Bit s per Request

Q Series One Bit 188 Bits
QnA Series One Bit 94 Bits
L Series One Bit 188 Bits
iQ-R Series One Bit 94 Bits
iQ-F Series One Bit 188 Bits

Max Words per Request: Set the maximum number of words to write per request. If writing to a size larger
than this setting, multiple write requests are processed. The default value is the maximum value allowed.

www. ptc.com
14 M itsu b ish i Eth ern et Driver

M inimum Words per Request M aximum Words per Request

Q Series One Word 160 Words
QnA Series One Word 80 Words
L Series One Word 160 Words
iQ-R Series One Word 80 Words
iQ-F Series One Word 160 Words

N ote: If opening an .opf or .xml file from version 6.0 or earlier, Max Bits per Request and Max Words per
Request are initially set to 1. If opening a JSON file saved with 6.0, the properties are set to the default val-
ues.

Device Propert ies — Tim e and Dat e Synchronizat ion

Time and Date Synchronization properties are only available to the Q, QnA, and L Series Model PLCs.

Tim e Sync Method: Choose the synchronization method to define how the time and date are reconciled
between the host system and the device. Options include Disabled, Interval, and Absolute. The default set-
ting is Disabled.

Absolute Sync Tim e: Specify an exact hour and minute of each day to synchronize time between the server
and the device when the synchronization method is Absolute. The default value is set to the local PC time
when the device was created. Only the hour and minute of the day are used to determine if synchronization
is required. The seconds are ignored. As an example, if this property displays as 3:52:00 PM, time syn-
chronization will occur each day at 57120 seconds after midnight.

Sync Interval: Specify the time, in minutes, between synchronizations - how often time and date recon-
ciliation should occur when the synchronization method is Interval. The driver can periodically synchronize
the time and date of the PLC with the time and date of the host computer. The valid range is 5 to 1440
minutes (24 hours). The default setting is 5 minutes.

N ote: For example, if 240 minutes is entered, the driver sets the PLC date and time every 4 hours.

Device Propert ies — Redundancy

www. ptc.com
Mitsubishi Ethernet Driver 15

Redundancy is available with the Media-Level Redundancy Plug-In.

Consult the website, a sales representative, or the user manual for more information.

www. ptc.com
16 M itsu b ish i Eth ern et Driver

M ult i-Level Net works

The Q Series, QnA Series, and L Series models are used to communicate with devices on remote networks.
In the example shown below, PLC 1, PLC 2 and PLC 3 are on the local Ethernet network (Network 0). PLC 4,
PLC 5 and PLC 6 are on a remote NET/H network. PLC 3 serves as a relay device connecting the two net-
works.

If PLC 1, PLC 2 and PLC 3 have QJ71E71-100 Ethernet modules configured with IPs 192.168.111.1,
192.168.111.2 and 192.168.111.3 respectively. In addition to the Ethernet module, PLC 3 also has a
QJ71BR11 NET/H module configured as station 3. Assume that PLC 4, PLC 5 and PLC 6 have NET/H modules
configured as stations 4, 5 and 6 respectively.

To communicate with all six PLCs, six devices would need to be created in the server project. The Device IDs
would be as follows:

PLC Device ID Comment

1 192.168.111.1:N0:255* Local network, local PC
2 192.168.111.2:N0:255* Local network, local PC
3 192.168.111.3:N0:255* Local network, local PC
4 192.168.111.3:N2:4 Network 2, PC 4, via PLC 3
5 192.168.111.3:N2:5 Network 2, PC 5, via PLC 3
6 192.168.111.3:N2:6 Network 2, PC 6, via PLC 3

* This example shows: N0 as the network number for the local network. It is also possible to omit the network
number when it is Network 0 (local network), thus, the Device ID 192.168.111.1:255 would also be valid in
this case.

N otes:

1. For performance and reliability, the driver is designed to use a separate socket for each device. Thus,
if TCP/IP is used, the relay device in this example would need to have at least 4 ports configured - one
to connect to each of the driver's sockets for PLC 3, PLC 4, PLC 5 and PLC 6. However, only a single
port needs to be configured in the relay device if UDP and the "unspecified" destination IP

www. ptc.com
Mitsubishi Ethernet Driver 17

(255.255.255.255) and port number (0xFFFF) are being used. Therefore, UDP is generally recom-
mended for this type of application. For more information, refer to PLC Setup.

2. A relay device may take 5 or more seconds to report a failed read and write to a remote device. It is
recommended that the request timeout for remote devices be set accordingly. For more information,
refer to Device Setup.

Opt im izing Com m unicat ions

The Mitsubishi Ethernet Driver has been designed to provide the best performance with the least amount of
impact on the system's overall performance. While the Mitsubishi Ethernet Driver is fast, there are a couple
of guidelines that can be used to control and optimize the application and gain maximum performance.

This server refers to communications protocols like Mitsubishi Ethernet Device as a channel. Each channel
defined in the application represents a separate path of execution in the server. Once a channel has been
defined, a series of devices must then be defined under that channel. Each of these devices represents a
single Mitsubishi Ethernet device from which data should be collected. While this approach to defining the
application provides a high level of performance, it doesn't take full advantage of the Mitsubishi Ethernet
Driver or the network. An example of how the application may appear when configured using a single chan-
nel is shown below.

Each device appears under a single Mitsubishi Ethernet device channel. In this con-
figuration, the driver must move from one device to the next as quickly as possible
to gather information at an effective rate. As more devices are added or more
information is requested from a single device, the overall update rate begins to suf-
fer.

If the Mitsubishi Ethernet Driver could only define one single channel, then the example shown above would
be the only option available; however, the driver can define up to 256 channels. Using multiple channels dis-
tributes the data collection workload by simultaneously issuing multiple requests to the network. An example
of how the same application may appear when configured using multiple channels to improve performance
is shown below.

Each device has now been defined under its own channel. In this new configuration,
a single path of execution is dedicated to the task of gathering data from each
device. If the application has 256 or fewer devices, it can be optimized exactly how
it is shown here.
The performance improves even if the application has more than 256 devices.
While 256 or fewer devices may be ideal, the application still benefits from addi-
tional channels. Although by spreading the device load across all channels causes
the server to move from device to device again, it can do so with far less devices to
process on a single channel.

Tip: An additional performance gain can be achieved by using UDP instead of TCP/IP. For more inform-
ation, refer to Device Setup and PLC Setup.

www. ptc.com
18 M itsu b ish i Eth ern et Driver

Dat a Types Descript ion

The Mitsubishi Ethernet Driver supports the following data types.

Dat a
Descript ion
Type
Boolean Single bit
Unsigned 16-bit value

Word
bit 0 is the low bit
bit 15 is the high bit
Signed 16-bit value

Short bit 0 is the low bit

bit 14 is the high bit
bit 15 is the sign bit
Unsigned 32-bit value

DWord
Bit 0 is the low bit.
Bit 31 is the high bit.
Signed 32-bit value

Long Bit 0 is the low bit.

Bit 30 is the high bit.
Bit 31 is the sign bit.
Float 32-bit floating point value
Null-terminated ASCII string support includes HiLo and LoHi byte order selection and string
String
lengths up to 128 bytes.
Two byte packed BCD
BCD
Value range is 0-9999. Behavior is undefined for values beyond this range.
Four byte packed BCD
LBCD
Value range is 0-99999999. Behavior is undefined for values beyond this range.
Date 32-bit value
Date Date format: YYYY-MM-DDTHH:MM:SS.000
Example 2000-01-01T12:30:45.000
64-bit floating point value

Double*
The driver interprets four consecutive registers as a Double precision value by making the
first two registers the low DWord and the last two registers the high DWord.
Double If register D0000000 is specified as a Double, bit 0 of register D0000000 would be bit 0 of the
Example* 64-bit data type. Bit 15 of register D0000003 would be bit 63 of the 64-bit data type.

* The descriptions above assume the default first word low data handling of 32-bit data types.

www. ptc.com
Mitsubishi Ethernet Driver 19

Address Descript ions

Address specifications vary depending on the model in use. Select a link from the following list to obtain spe-
cific address information for the model of interest.

A Series
L Series
Q Series
iQ-R Series
iQ-F Series
QnA_Series
FX3U Series

M it subishi A Series Address Descript ions

The default data types for dynamically defined tags are shown in bold.

Device Type Range Dat a Type Access

X000-X1FFF (Hex) Boolean
Inputs* X000-X1FF0 (Hex) Short, Word, BCD Read/Write
X000-X1FE0 (Hex) Long, DWord, LBCD
Y000-Y1FFF (Hex) Boolean
Outputs* Y000-Y1FF0 (Hex) Short, Word, BCD Read/Write
Y000-Y1FE0 (Hex) Long, DWord, LBCD
B000-B1FFF (Hex) Boolean
Link Relays* B000-B1FF0 (Hex) Short, Word, BCD Read/Write
B000-B1FE0 (Hex) Long, DWord, LBCD
M0000-M8191 Boolean
Internal Relays* M0000-M8176 Short, Word, BCD Read/Write
M0000-M8160 Long, DWord, LBCD
M9000-M9255 Boolean
Special Int. Relays* M9000-M9240 Short, Word, BCD Read Only
M9000-M9224 Long, DWord, LBCD
L0000-L8191 Boolean
Latch Relays* L0000-L8176 Short, Word, BCD Read/Write
L0000-L8160 Long, DWord, LBCD
F0000-F2047 Boolean
Annunciator Relays* F0000-F2032 Short, Word, BCD Read/Write
F0000-F2016 Long, DWord, LBCD
TS0000-TS2047 Boolean
Timer Contacts* TS0000-TS2032 Short, Word, BCD Read/Write
TS0000-TS2016 Long, DWord, LBCD
TC0000-TC2047 Boolean
Timer Coils* TC0000-TC2032 Short, Word, BCD Read/Write
TC0000-TC2016 Long, DWord, LBCD
CS0000-CS1023 Boolean
Counter Contacts* Read/Write
CS0000-CS1008 Short, Word, BCD

www. ptc.com
20 M itsu b ish i Eth ern et Driver

Device Type Range Dat a Type Access

CS0000-CS0992 Long, DWord, LBCD
CC0000-CC1023 Boolean
Counter Coils* CC0000-CC1008 Short, Word, BCD Read/Write
CC0000-CC0992 Long, DWord, LBCD

* Users can specify a Long data type by appending a space and an "L" to the address. For example, "CS0000"
would be entered as "CS0000 L". This does not apply to arrays or bit accessed registers.

N ote: All Boolean device types can be accessed as Short, Word, BCD, Long, DWord and LBCD; however,
the device must be addressed on a 16-bit boundary.

Device Type Range Dat a Type Access

Timer Value TN0000-TN2047 Short, Word, BCD Read/Write
Counter Value CN0000-CN1023 Short, Word, BCD Read/Write
Short, Word, BCD
D0000-D8191
Data Long, DWord,
D0000-D8190 Read/Write
Registers* * * LBCD, Float, Date
D0000-D8188
Double
Short, Word, BCD,
Data Register D0000.00-D8191.15* Boolean
Read/Write
Bit Access D0000.00-D8190.31* Long, DWord,
LBCD
DSH00000.002-DSH08190.002
Data Registers DSH00000.128-DSH08127.128
String Access
String Read/Write
HiLo Byte Order- The string length may also be specified using a colon.
ing The string length must be between
2-128 bytes and even.
DSL00000.002–DSL08190.002
Data Registers DSL00000.128-DSL08127.128
String Access
String Read/Write
LoHi Byte Order- The string length may also be specified using a colon.
ing The string length must be between
2-128 bytes and even.
Short, Word, BCD
D9000-D9255
Special Data Long, DWord,
D9000-D9254 Read Only
Registers* * * LBCD, Float, Date
D9000-D9252
Double
Short, Word, BCD,
Data Register D9000.00-D9255.15* Boolean* *
Read Only
Bit Access D9000.00-D9254.31* Long, DWord,
LBCD
Short, Word, BCD
W0000-W1FFF (Hex)
Link Long, DWord,
W0000-W1FFE (Hex) Read/Write
Registers* * * LBCD, Float, Date
W0000-W1FFC (Hex)
Double

www. ptc.com
Mitsubishi Ethernet Driver 21

Device Type Range Dat a Type Access

Short, Word, BCD,
Link Register Bit W0000.00-W1FFF.15* Boolean* *
Read/Write
Access W0000.00-W1FFE.31* Long, DWord,
LBCD
WSH0000.002-WSH1FFE.002
Link Registers WSH0000.128-WSH1FBF.128
String Access
String Read/Write
HiLo Byte Order- The string length may also be specified using a colon.
ing The string length must be between
2-128 bytes and even.
WSL0000.002-WSL1FFE.002
Link Registers WSL0000.128-WSL1FBF.128
String Access
String Read/Write
LoHi Byte Order- The string length may also be specified using a colon.
ing The string length must be between
2-128 bytes and even.
Short, Word, BCD
R0000-R8191
Long, DWord,
File Register* * * R0000-R8190 Read/Write
LBCD, Float, Date
R0000-R8188
Double
Short, Word, BCD,
File Register Bit R0000.00-R8191.15* Boolean* *
Read/Write
Access R0000.00-R8190.31* Long, DWord,
LBCD
RSH00000.002-RSH08190.002
File Registers RSH00000.128-RSH08127.128
String Access
String Read/Write
HiLo Byte Order- The string length may also be specified using a colon.
ing The string length must be between
2-128 bytes and even.
RSL00000.002-RSL08190.002
File Registers RSL00000.128-RSL08127.128
String Access
String Read/Write
LoHi Byte Order- The string length may also be specified using a colon.
ing The string length must be between
2-128 bytes and even.

* For register memory, the data types Short, Word, BCD, DWord, Long, LBCD and Boolean may append an
optional ".bb" (dot bit) or ":bb" (colon bit) to the address to reference a bit in a particular value. The valid
ranges for the optional bit are 0-15 for Short, Word, BCD, Boolean; and 0-31 for Long, DWord and LBCD.
Strings use the bit number to specify length. The valid length of a string in D memory is 2 to 128 bytes. The
string length must be an even number. Float types do not support bit operations. The bit number is always in
decimal notation.
* * When accessing register memory as Boolean, a bit number is required.
* * * Users can specify a Long data type by appending a space and an "L" to the address. For example,
"CS0000" would be entered as "CS0000 L". This does not apply to arrays or bit accessed registers.

Array Access

www. ptc.com
22 M itsu b ish i Eth ern et Driver

Many device types can be accessed as arrays. Boolean arrays and Date arrays are not supported. The
default array tag for device types is Word. The size of the array depends on both the data type and the
device type. Arrays may be one or two dimensions and the total number of Words being requested cannot
exceed the Max Read Block Size specified for the device.

N ote: An array is created when array notation is appended onto a normal device reference.

Exam ples

1. D100 [4] Single dimension includes the following register addresses: D100, D101, D102, D103.

2. M016 [3][4] Two Dimensions includes the following device addresses as words: M016, M032, M048,
M064, M080, M096, M112, M128, M144, M160, M176, M192 3 rows x 4 columns = 12 words 12 x 16
(word) =192 total bits.

Additional Device Examples

1. Access X device memory as Word: X??? where the ??? is a hex number on 16-bit boundaries such as
010, 020, 030, and so forth.

2. Access M device memory as Long: M???? where the ???? is a decimal number on 16-bit boundaries
such as 0, 16, 32, 48, and so forth.

M it subishi FX3U Series Address Descript ions

The default data types for dynamically defined tags are shown in bold.

Device Type Range Dat a Type Access

X000-X377 (Oct) Boolean
Inputs* X000-X360 (Oct) Short, Word, BCD Read/Write
X000-X340 (Oct) Long, DWord, LBCD
Y000-Y377 (Oct) Boolean
Outputs* Y000-Y360 (Oct) Short, Word, BCD Read/Write
Y000-Y340 (Oct) Long, DWord, LBCD
M0000-M7679 Boolean
Internal Relays* M0000-M7664 Short, Word, BCD Read/Write
M0000-M7648 Long, DWord, LBCD
M8000-M8511 Boolean
Special Int. Relays* M8000-M8496 Short, Word, BCD Read/Write
M8000-M8480 Long, DWord, LBCD
S0000-S4095 Boolean
Step Relays* S0000-S4080 Short, Word, BCD Read/Write
S0000-S4064 Long, DWord, LBCD
TS000-TS511 Boolean
Timer Contacts* TS000-TS496 Short, Word, BCD Read/Write
TS000-TS480 Long, DWord, LBCD
CS000-CS255 Boolean
Counter Contacts* CS000-CS240 Short, Word, BCD Read/Write
CS000-CS224 Long, DWord, LBCD

www. ptc.com
Mitsubishi Ethernet Driver 23

* Users can specify a Long data type by appending a space and an "L" to the address. For example, "CS0000"
would be entered as "CS0000 L". This does not apply to arrays or bit accessed registers.

N ote: All Boolean device types can be accessed as Short, Word, BCD, Long, DWord and LBCD; however,
the device must be addressed on a 16-bit boundary.

Device Type Range Dat a Type Access

Short, Word,
Timer Value TN000-TN511 Read/Write
BCD
Short, Word,
Counter CN000-CN199 BCD
Read/Write
Value* * * CN200-CN255 Long, DWord,
LBCD
Short, Word,
BCD
D0000-D7999
Data Long, DWord,
D0000-D7998 Read/Write
Registers* * * LBCD, Float,
D0000-D7996
Date
Double
Short, Word,
Data Register D0000.00-D7999.15* BCD, Boolean
Read/Write
Bit Access D0000.00-D7998.31* Long, DWord,
LBCD
Data DSH0000.002-DSH7998.002
Registers DSH0000.128-DSH7935.128
String
String Access Read/Write
HiLo Byte The string length may also be specified using a colon. The
Ordering string length must be between 2-128 bytes and even.
Data DSL0000.002-DSL7998.002
Registers DSL0000.128-DSL7935.128
String
String Access Read/Write
LoHi Byte The string length may also be specified using a colon. The
Ordering string length must be between 2-128 bytes and even.
Short, Word,
BCD
D8000-D8511
Special Data Long, DWord,
D8000-D8510 Read/Write
Registers* * * LBCD, Float,
D8000-D8508
Date
Double
Short, Word,
Special Data BCD,
D8000.00-D8511.15*
Register Boolean* * Read/Write
D8000.00-D8510.31*
Bit Access Long, DWord,
LBCD
R00000-R32767 Short, Word,
File
R00000-R32766 BCD Read/Write
Register* * *
R00000-R32764 Long, DWord,

www. ptc.com
24 M itsu b ish i Eth ern et Driver

Device Type Range Dat a Type Access

LBCD, Float,
Date
Double
Short, Word,
BCD,
File Register R00000.00-R32767.15*
Boolean* * Read/Write
Bit Access R00000.00-R32766.31*
Long, DWord,
LBCD
RSH00000.002-RSH32766.002
File Registers
RSH00000.128-RSH32703.128 String
String Access
Read/Write
HiLo Byte
The string length may also be specified using a colon. The
Ordering
string length must be between 2-128 bytes and even.
RSL00000.002-RSL32766.002
File Registers
RSL00000.128-RSL32703.128 String
String Access
Read/Write
LoHi Byte
The string length may also be specified using a colon. The
Ordering
string length must be between 2-128 bytes and even.

* For register memory, the data types Short, Word, BCD, DWord, Long, LBCD and Boolean append an
optional ".bb" (dot bit) or ":bb" (colon bit) to the address to reference a bit in a particular value. The valid
ranges for the optional bit are 0-15 for Short, Word, BCD and Boolean; and 0-31 for Long, DWord and LBCD.
Strings use the bit number to specify length. The valid length of a string is 2 to 128 bytes. The string length
must be an even number. Float types do not support bit operations. The bit number is always in decimal nota-
tion.
* * When accessing register memory as Boolean, a bit number is required.
* * * Users can specify a Long data type by appending a space and an "L" to the address. For example,
"CS0000" would be entered as "CS0000 L". This does not apply to arrays or bit accessed registers.

Array Access
Many device types can be accessed as arrays. Boolean arrays and Date arrays are not supported. The
default array tag for device types is Word. The size of the array depends on both the data type and the
device type. Arrays may be one or two dimensions and the total number of Words being requested cannot
exceed the Max Read Block Size specified for the device.

N otes:

1. An array is created when array notation is appended onto a normal device reference.

2. Due to a limit of the protocol, the largest bit memory array that can be written to is 10 Word-
s/Shorts/BCDs (or 5 DWords/Longs/LBCDs). Although this limit differs from the largest bit memory
array that can be read (32 words), the maximum Read/Write array size for register memory type is
the same (64 words).

Exam ples

www. ptc.com
Mitsubishi Ethernet Driver 25

1. D100 [4] Single dimension includes the following register addresses: D100, D101, D102, D103.

2. M016 [3][4] Two Dimensions includes the following device addresses as words: M016, M032, M048,
M064, M080, M096, M112, M128, M144, M160, M176, M192 3 rowsx4 columns=12 words 12 x 16
(word) = 192 total bits.

Additional Device Examples

1. Access M device memory as Long: M???? where the ???? is a decimal number on 16-bit boundaries
such as 0, 16, 32, 48, and so forth.

2. Access Y device memory as Short: Y??? where the ??? is an Octal number on 16-bit boundaries such
as 020, 040, 060, and so forth.

M it subishi L Series Address Descript ions

The default data types for dynamically defined tags are shown in bold.

Device Type Range Dat a Type Access

X0000-X3FFF (Hex) Boolean
Inputs* X0000-X3FF0 (Hex) Short, Word, BCD Read/Write
X0000-X3FE0 (Hex) Long, DWord, LBCD
DX0000-DX3FFF (Hex) Boolean
Direct Inputs* DX0000-DX3FF0 (Hex) Short, Word, BCD Read/Write
DX0000-DX3FE0 (Hex) Long, DWord, LBCD
Y0000-Y3FFF (Hex) Boolean
Outputs* Y0000-Y3FF0 (Hex) Short, Word, BCD Read/Write
Y0000-Y3FE0 (Hex) Long, DWord, LBCD
DY0000-DY3FFF (Hex) Boolean
Direct Outputs* DY0000-DY3FF0 (Hex) Short, Word, BCD Read/Write
DY0000-DY3FE0 (Hex) Long, DWord, LBCD
B0000-BEA6F (Hex) Boolean
Link Relays* B0000-BEA60 (Hex) Short, Word, BCD Read/Write
B0000-BEA50 (Hex) Long, DWord, LBCD
SB0000-SB7D0F (Hex) Boolean
Special Link Relays* SB0000-SB7D00 (Hex) Short, Word, BCD Read/Write
SB0000-SB7CF0 (Hex) Long, DWord, LBCD
M0000-M60015 Boolean
Internal Relays* M0000-M60000 Short, Word, BCD Read/Write
M0000-M59984 Long, DWord, LBCD
SM0000-SM2047 Boolean
Special Int. Relays* SM0000-SM2032 Short, Word, BCD Read/Write
SM0000-SM2016 Long, DWord, LBCD
L0000-L32015 Boolean
Latch Relays* L0000-L32000 Short, Word, BCD Read/Write
L0000-L31984 Long, DWord, LBCD
F0000-F32015 Boolean
Annunciator Relays* Read/Write
F0000-F32000 Short, Word, BCD

www. ptc.com
26 M itsu b ish i Eth ern et Driver

Device Type Range Dat a Type Access

F0000-F31984 Long, DWord, LBCD
V0000-V32015 Boolean
Edge Relays* V0000-V32000 Short, Word, BCD Read/Write
V0000-V31984 Long, DWord, LBCD
S0000-S16383 Boolean
Step Relays* S0000-S16368 Short, Word, BCD Read/Write
S0000-S16352 Long, DWord, LBCD
TS0000-TS32015 Boolean
Timer Contacts* TS0000-TS32000 Short, Word, BCD Read/Write
TS0000-TS31984 Long, DWord, LBCD
TC0000-TC32015 Boolean
Timer Coils* TC0000-TC32000 Short, Word, BCD Read/Write
TC0000-TC31984 Long, DWord, LBCD
SS0000-SS2047 Boolean
Integrating Timer Contacts* SS0000-SS2032 Short, Word, BCD Read/Write
SS0000-SS2016 Long, DWord, LBCD
SC0000-SC2047 Boolean
Integrating Timer Coils* SC0000-SC2032 Short, Word, BCD Read/Write
SC0000-SC2016 Long, DWord, LBCD
CS0000-CS32015 Boolean
Counter Contacts* CS0000-CS32000 Short, Word, BCD Read/Write
CS0000-CS31984 Long, DWord, LBCD
CC0000-CC32015 Boolean
Counter Coils* CC0000-CC32000 Short, Word, BCD Read/Write
CC0000-CC31984 Long, DWord, LBCD

* Users can specify a Long data type by appending a space and an "L" to the address. For example, "CS0000"
would be entered as "CS0000 L". This does not apply to arrays or bit accessed registers.

N ote: All Boolean device types can be accessed as Short, Word, BCD, Long, DWord and LBCD; however,
the device must be addressed on a 16-bit boundary.

Device Type Range Dat a Type Access

Short, Word,
Timer Value TN0000-TN32000 Read/Write
BCD
Integrating Short, Word,
SN0000-SN2047 Read/Write
Timer Value BCD
Short, Word,
Counter Value CN0000-CN32000 Read/Write
BCD
Short, Word,
D0000000-D4184063 BCD
D0000000-D4184062 Long, DWord,
Data
D0000000-D4184060 LBCD, Float, Read/Write
Registers* * *
Date
See Also:Extended Registers Double

www. ptc.com
Mitsubishi Ethernet Driver 27

Device Type Range Dat a Type Access

Short, Word,
D0000000.00–D4184063.15* BCD,
Data Register D0000000.00–D4184062.31* Boolean* *
Read/Write
Bit Access Long, DWord,
See Also:Extended Registers LBCD

Data DSH00000.002-DSH4184062.002
String
Registers DSH00000.128-DSH4183999.128
String Access Read/Write
HiLo Byte The string length may also be specified using a colon. The
Ordering string length must be between 2-128 bytes and even.
Data DSL00000.002-DSL4184062.002
String
Registers DSL00000.128-DSL4183999.128
String Access Read/Write
LoHi Byte The string length may also be specified using a colon. The
Ordering string length must be between 2-128 bytes and even.
Short, Word,
BCD
SD0000-SD2047
Special Data Long, DWord,
SD0000-SD2046 Read/Write
Registers* * * LBCD, Float,
SD0000-SD2044
Date
Double
Short, Word,
BCD,
Data Register SD0000.00-SD2047.15*
Boolean* * Read/Write
Bit Access SD0000.00-SD2046.31*
Long, DWord,
LBCD
Short, Word,
W0000-W3FD7FF (Hex) BCD
W0000-W3FD7FE (Hex) Long, DWord,
Link LBCD, Float,
W0000-W3FD7FC (Hex) Read/Write
Registers* * * Date
See Also:Extended Registers Double

Short, Word,
W0000.00-W3FD7FF.15*
BCD,
Link Register W0000.00-W3FD7FE.31*
Boolean* * Read/Write
Bit Access
Long, DWord,
See Also:Extended Registers
LBCD
WSH0000.002-WSH3FD7FE.002
Link Registers
WSH0000.128-WSH3FD7BF.128 String
String Access
Read/Write
HiLo Byte
The string length may also be specified using a colon. The
Ordering
string length must be between 2-128 bytes and even.
Link Registers WSL0000.002-WSL3FD7FE.002 String Read/Write

www. ptc.com
28 M itsu b ish i Eth ern et Driver

Device Type Range Dat a Type Access

WSL0000.128-WSL3FD7BF.128
String Access
LoHi Byte
The string length may also be specified using a colon. The
Ordering
string length must be between 2-128 bytes and even.
Short, Word,
BCD
SW0000-SW7D00 (Hex)
Special Link Long, DWord,
SW0000-SW7CFF (Hex) Read/Write
Registers* * * LBCD, Float,
SW0000-SW7CFD (Hex)
Date
Double
Short, Word,
BCD,
Link Register SW0000.00-SW7D00.15*
Boolean* * Read/Write
Bit Access SW0000.00-SW7CFF.31*
Long, DWord,
LBCD
Short, Word,
BCD
Long, DWord,
R00000-R32767 LBCD, Float,
R00000-R32766 Date
R00000-R32764 Double
File
Read/Write
Register* * *
ZR0000-ZR3FD7FF (Hex) Short, Word,
ZR0000-ZR3FD7FE (Hex) BCD
ZR0000-ZR3FD7FC (Hex) Long, DWord,
LBCD, Float,
Date
Double
Short, Word,
BCD,
Boolean* *
R00000.00-R32767.15* Long, DWord,
R00000.00-R32766.31* LBCD
File Register
Read/Write
Bit Access
ZR0000.00-ZR3FD7FF.15* Short, Word,
ZR0000.00-ZR3FD7FE.31* BCD,
Boolean* *
Long, DWord,
LBCD
RSH00000.002-RSH32766.002
RSH00000.128-RSH32703.128 String
File Registers
String Access ZRSH0000.002-ZRSH3FD7FE.002
Read/Write
HiLo Byte ZRSH0000.128-ZRSH3FD7BF.128 String
Ordering
The string length may also be specified using a colon. The
string length must be between 2-128 bytes and even.

www. ptc.com
Mitsubishi Ethernet Driver 29

Device Type Range Dat a Type Access

RSL00000.002-RSL32766.002
RSL00000.128-RSL32703.128 String
File Registers
String Access ZRSL0000.002-ZRSL3FD7FE.002
Read/Write
LoHi Byte ZRSL0000.128-ZRSL3FD7BF.128 String
Ordering
The string length may also be specified using a colon. The
string length must be between 2-128 bytes and even.
Short, Word,
BCD
Z00-Z20
Index Long, DWord,
Z00-Z19 Read/Write
Registers* * * LBCD, Float,
Z00-Z17
Date
Double
Short, Word,
BCD,
Index Register Z00.00-Z20.15*
Boolean* * Read/Write
Bit Access Z00.00-Z19.31*
Long, DWord,
LBCD

* For register memory, the data types Short, Word, BCD, DWord, Long, LBCD and Boolean may append an
optional ".bb" (dot bit) or ":bb" (colon bit) to the address to reference a bit in a particular value. The valid
ranges for the optional bit are 0-15 for Short, Word, BCD and Boolean; and 0-31 for Long, DWord and LBCD.
Strings use the bit number to specify length. The valid length of a string in D memory is 2 to 128 bytes. The
string length must be an even number. Float types do not support bit operations. The bit number is always in
decimal notation.
* * When accessing register memory as Boolean, a bit number is required.
* * * Users can specify a Long data type by appending a space and an "L" to the address. For example,
"CS0000" would be entered as "CS0000 L". This does not apply to arrays or bit accessed registers.

Extended Registers
The extended range for Data Registers is D12288 to D4184063. The extended range for Link Registers is
W3FFF (Hex) to W3FD7FF (Hex). These must be configured on the device.

Array Access
Many device types can be accessed as arrays. Boolean arrays and Date arrays are not supported. The
default array tag for device types is Word. The size of the array depends on both the data type and the
device type. Arrays may be one or two dimensions and the total number of Words being requested cannot
exceed the Max Read Block Size specified for the device.

N ote: An array is created when array notation is appended onto a normal device reference.

Exam ples:

1. D100 [4] Single dimension includes the following register addresses: D100, D101, D102, D103.

2. M016 [3][4] Two Dimensions includes the following device addresses as words: M016, M032, M048,
M064, M080, M096, M112, M128, M144, M160, M176, M192 3 rows x 4 columns =12 words 12 x 16
(word) =192 total bits.

www. ptc.com
30 M itsu b ish i Eth ern et Driver

Additional Device Examples

1. Access X device memory as Word: X??? where the ??? is a hex number on 16-bit boundaries such as
010, 020, 030, and so forth.

2. Access M device memory as Long: M???? where the ???? is a decimal number on 16-bit boundaries
such as 0, 16, 32, 48, and so forth.

M it subishi Q Series Address Descript ions

The default data types for dynamically defined tags are shown in bold.

Device Type Range Dat a Type Access

X0000-X3FFF (Hex) Boolean
Inputs* X0000-X3FF0 (Hex) Short, Word, BCD Read/Write
X0000-X3FE0 (Hex) Long, DWord, LBCD
DX0000-DX3FFF (Hex) Boolean
Direct Inputs* DX0000-DX3FF0 (Hex) Short, Word, BCD Read/Write
DX0000-DX3FE0 (Hex) Long, DWord, LBCD
Y0000-Y3FFF (Hex) Boolean
Outputs* Y0000-Y3FF0 (Hex) Short, Word, BCD Read/Write
Y0000-Y3FE0 (Hex) Long, DWord, LBCD
DY0000-DY3FFF (Hex) Boolean
Direct Outputs* DY0000-DY3FF0 (Hex) Short, Word, BCD Read/Write
DY0000-DY3FE0 (Hex) Long, DWord, LBCD
B0000-BEA6F (Hex) Boolean
Link Relays* B0000-BEA60 (Hex) Short, Word, BCD Read/Write
B0000-BEA50 (Hex) Long, DWord, LBCD
SB0000-SB7D0F (Hex) Boolean
Special Link Relays* SB0000-SB7D00 (Hex) Short, Word, BCD Read/Write
SB0000-SB7CF0 (Hex) Long, DWord, LBCD
M0000-M60015 Boolean
Internal Relays* M0000-M60000 Short, Word, BCD Read/Write
M0000-M59984 Long, DWord, LBCD
SM0000-SM2047 Boolean
Special Int. Relays* SM0000-SM2032 Short, Word, BCD Read/Write
SM0000-SM2016 Long, DWord, LBCD
L0000-L32015 Boolean
Latch Relays* L0000-L32000 Short, Word, BCD Read/Write
L0000-L31984 Long, DWord, LBCD
F0000-F32015 Boolean
Annunciator Relays* F0000-F32000 Short, Word, BCD Read/Write
F0000-F31984 Long, DWord, LBCD
V0000-V32015 Boolean
Edge Relays* V0000-V32000 Short, Word, BCD Read/Write
V0000-V31984 Long, DWord, LBCD
Step Relays* S0000-S16383 Boolean Read/Write

www. ptc.com
Mitsubishi Ethernet Driver 31

Device Type Range Dat a Type Access

S0000-S16368 Short, Word, BCD
S0000-S16352 Long, DWord, LBCD
TS0000-TS32015 Boolean
Timer Contacts* TS0000-TS32000 Short, Word, BCD Read/Write
TS0000-TS31984 Long, DWord, LBCD
TC0000-TC32015 Boolean
Timer Coils* TC0000-TC32000 Short, Word, BCD Read/Write
TC0000-TC31984 Long, DWord, LBCD
SS0000-SS2047 Boolean
Integrating Timer Contacts* SS0000-SS2032 Short, Word, BCD Read/Write
SS0000-SS2016 Long, DWord, LBCD
SC0000-SC2047 Boolean
Integrating Timer Coils* SC0000-SC2032 Short, Word, BCD Read/Write
SC0000-SC2016 Long, DWord, LBCD
CS0000-CS32015 Boolean
Counter Contacts* CS0000-CS32000 Short, Word, BCD Read/Write
CS0000-CS31984 Long, DWord, LBCD
CC0000-CC32015 Boolean
Counter Coils* CC0000-CC32000 Short, Word, BCD Read/Write
CC0000-CC31984 Long, DWord, LBCD

* Users can specify a Long data type by appending a space and an "L" to the address. For example, "CS0000"
would be entered as "CS0000 L". This does not apply to arrays or bit accessed registers.

N ote: All Boolean device types can be accessed as Short, Word, BCD, Long, DWord and LBCD; however,
the device must be addressed on a 16-bit boundary.

Device Type Range Dat a Type Access

Short, Word,
Timer Value TN0000-TN32000 Read/Write
BCD
Integrating Short, Word,
SN0000-SN2047 Read/Write
Timer Value BCD
Short, Word,
Counter Value CN0000-CN32000 Read/Write
BCD
Short, Word,
BCD
D0000000-D4184063
Long, DWord,
D0000000-D4184062
Data LBCD, Float,
D0000000-D4184060 Read/Write
Registers* * * Date
Double
See Also:Extended Registers

D0000000.00–D4184063.15* Short, Word,

Data Register D0000000.00–D4184062.31* BCD,
Read/Write
Bit Access Boolean* *
See Also:Extended Registers Long, DWord,

www. ptc.com
32 M itsu b ish i Eth ern et Driver

Device Type Range Dat a Type Access

LBCD
Data DSH00000.002-DSH4184062.002
Registers DSH00000.128-DSH4183999.128
String Access String Read/Write
HiLo Byte The string length may also be specified using a colon. The
Ordering string length must be between 2-128 bytes and even.
Data DSL00000.002-DSL4184062.002
Registers DSL00000.128-DSL4183999.128
String Access String Read/Write
LoHi Byte The string length may also be specified using a colon. The
Ordering string length must be between 2-128 bytes and even.
Short, Word,
BCD
SD0000-SD2047
Special Data Long, DWord,
SD0000-SD2046 Read/Write
Registers* * * LBCD, Float,
SD0000-SD2044
Date
Double
Short, Word,
BCD,
Data Register SD0000.00-SD2047.15*
Boolean* * Read/Write
Bit Access SD0000.00-SD2046.31*
Long, DWord,
LBCD
Short, Word,
BCD
W0000-W3FD7FF (Hex)
Long, DWord,
W0000-W3FD7FE (Hex)
Link LBCD, Float,
W0000-W3FD7FC (Hex) Read/Write
Registers* * * Date,
Double
See Also:Extended Registers

Short, Word,
BCD,
W0000.00-W3FD7FF.15*
Boolean* *
Link Register W0000.00-W3FD7FE.31*
Long, DWord, Read/Write
Bit Access
LBCD
See Also:Extended Registers

WSH0000.002-WSH3FD7FE.002
Link Registers
WSH0000.128-WSH3FD7BF.128
String Access String
Read/Write
HiLo Byte
The string length may also be specified using a colon. The
Ordering
string length must be between 2-128 bytes and even.
WSL0000.002-WSL3FD7FE.002
Link Registers
WSL0000.128-WSL3FD7BF.128
String Access String
Read/Write
LoHi Byte
The string length may also be specified using a colon. The
Ordering
string length must be between 2-128 bytes and even.

www. ptc.com
Mitsubishi Ethernet Driver 33

Device Type Range Dat a Type Access

Short, Word,
BCD
SW0000-SW7D00 (Hex)
Special Link Long, DWord,
SW0000-SW7CFF (Hex) Read/Write
Registers* * * LBCD, Float,
SW0000-SW7CFD (Hex)
Date
Double
Short, Word,
BCD,
Link Register SW0000.00-SW7D00.15*
Boolean* * Read/Write
Bit Access SW0000.00-SW7CFF.31*
Long, DWord,
LBCD
Short, Word,
BCD
Long, DWord,
R00000-R32767 LBCD, Float,
R00000-R32766 Date
R00000-R32764 Double
File
Read/Write
Register* * *
ZR0000-ZR3FD7FF (Hex) Short, Word,
ZR0000-ZR3FD7FE (Hex) BCD
ZR0000-ZR3FD7FC (Hex) Long, DWord,
LBCD, Float,
Date
Double
Short, Word,
BCD,
Boolean* *
R00000.00-R32767.15* Long, DWord,
R00000.00-R32766.31* LBCD
File Register
Read/Write
Bit Access
ZR0000.00-ZR3FD7FF.15* Short, Word,
ZR0000.00-ZR3FD7FE.31* BCD,
Boolean* *
Long, DWord,
LBCD
RSH00000.002-RSH32766.002
RSH00000.128-RSH32703.128
String
File Registers
String Access ZRSH0000.002-ZRSH3FD7FE.002
Read/Write
HiLo Byte ZRSH0000.128-ZRSH3FD7BF.128
String
Ordering
The string length may also be specified using a colon. The
string length must be between 2-128 bytes and even.
RSL00000.002-RSL32766.002 String
File Registers
RSL00000.128-RSL32703.128
String Access
Read/Write
LoHi Byte
ZRSL0000.002-ZRSL3FD7FE.002 String
Ordering
ZRSL0000.128-ZRSL3FD7BF.128

www. ptc.com
34 M itsu b ish i Eth ern et Driver

Device Type Range Dat a Type Access

The string length may also be specified using a colon. The

string length must be between 2-128 bytes and even.
Short, Word,
BCD
Z00-Z20
Index Long, DWord,
Z00-Z19 Read/Write
Registers* * * LBCD, Float,
Z00-Z17
Date
Double
Short, Word,
BCD,
Index Register Z00.00-Z20.15*
Boolean* * Read/Write
Bit Access Z00.00-Z19.31*
Long, DWord,
LBCD

* For register memory, the data types Short, Word, BCD, DWord, Long, LBCD and Boolean may append an
optional ".bb" (dot bit) or ":bb" (colon bit) to the address to reference a bit in a particular value. The valid
ranges for the optional bit are 0-15 for Short, Word, BCD and Boolean; and 0-31 for Long, DWord and LBCD.
Strings use the bit number to specify length. The valid length of a string in D memory is 2 to 128 bytes. The
string length must be an even number. Float types do not support bit operations. The bit number is always in
decimal notation.
* * When accessing register memory as Boolean, a bit number is required.
* * * Users can specify a Long data type by appending a space and an "L" to the address. For example,
"CS0000" would be entered as "CS0000 L". This does not apply to arrays or bit accessed registers.

Extended Registers
The extended range for Data Registers is D12288 to D4184063. The extended range for Link Registers is
W3FFF (Hex) to W3FD7FF (Hex). These must be configured on the device.

Array Access
Many device types can be accessed as arrays. Boolean arrays and Date arrays are not supported. The
default array tag for device types is Word. The size of the array depends on both the data type and the
device type. Arrays may be one or two dimensions and the total number of Words being requested cannot
exceed the Max Read Block Size specified for the device.

N ote: An array is created when array notation is appended onto a normal device reference.

Exam ples:

1. D100 [4] Single dimension includes the following register addresses: D100, D101, D102, D103.

2. M016 [3][4] Two Dimensions includes the following device addresses as words: M016, M032, M048,
M064, M080, M096, M112, M128, M144, M160, M176, M192 3 rows x 4 columns =12 words 12 x 16
(word) =192 total bits.

Additional Device Examples

www. ptc.com
Mitsubishi Ethernet Driver 35

1. Access X device memory as Word: X??? where the ??? is a hex number on 16-bit boundaries such as
010, 020, 030, and so forth.

2. Access M device memory as Long: M???? where the ???? is a decimal number on 16-bit boundaries
such as 0, 16, 32, 48, and so forth.

M it subishi iQ-R Series Address Descript ions

The default data types for dynamically defined tags are shown in bold.

Device Type Range Dat a Type Access

X0000-XFFFF (Hex) Boolean
Inputs* X0000-XFFF0 (Hex) Short, Word, BCD Read/Write
X0000-XFFE0 (Hex) Long, DWord, LBCD
DX0000-DXFFFF (Hex) Boolean
Direct Inputs* DX0000-DXFFF0 (Hex) Short, Word, BCD Read/Write
DX0000-DXFFE0 (Hex)) Long, DWord, LBCD
Y0000-YFFFF (Hex) Boolean
Outputs* Y0000-YFFF0 (Hex) Short, Word, BCD Read/Write
Y0000-YFFE0 (Hex) Long, DWord, LBCD
DY0000-DYFFFF (Hex) Boolean
Direct Outputs* DY0000-DYFFF0 (Hex) Short, Word, BCD Read/Write
DY0000-DYFFE0 (Hex) Long, DWord, LBCD
B0000-B7FFFFFFF (Hex) Boolean
Link Relays* B0000-B7FFFFFF0 (Hex) Short, Word, BCD Read/Write
B0000-B7FFFFFE0 (Hex) Long, DWord, LBCD
SB0000-SB7FFFFFFF (Hex) Boolean
Special Link Relays* SB0000-SB7FFFFFF0 (Hex) Short, Word, BCD Read/Write
SB0000-SB7FFFFFE0 (Hex) Long, DWord, LBCD
M0000-M2147483647 Boolean
Internal Relays* M0000-M2147483632 Short, Word, BCD Read/Write
M0000-M2147483616 Long, DWord, LBCD
SM0000-SM65535 Boolean
Special Int. Relays* SM0000-SM65520 Short, Word, BCD Read/Write
SM0000-SM65504 Long, DWord, LBCD
L0000-L66535 Boolean
Latch Relays* L0000-L65520 Short, Word, BCD Read/Write
L0000-L65504 Long, DWord, LBCD
F0000-F65535 Boolean
Annunciator Relays* F0000-F65520 Short, Word, BCD Read/Write
F0000-F65504 Long, DWord, LBCD
V0000-V65535 Boolean
Edge Relays* V0000-V65520 Short, Word, BCD Read/Write
V0000-V65504 Long, DWord, LBCD
S0000-S65535 Boolean
Step Relays* S0000-S65520 Short, Word, BCD Read/Write
S0000-S65504 Long, DWord, LBCD

www. ptc.com
36 M itsu b ish i Eth ern et Driver

Device Type Range Dat a Type Access

TS0000-TS16777215 Boolean
Timer Contacts* TS0000-TS16777200 Short, Word, BCD Read/Write
TS0000-TS16777184 Long, DWord, LBCD
TC0000-TC16777215 Boolean
Timer Coils* TC0000-TC16777200 Short, Word, BCD Read/Write
TC0000-TC16777184 Long, DWord, LBCD
STS000-STS16777215 Boolean
Retentive Timer Contacts* STS000-STS16777200 Short, Word, BCD Read/Write
STS000-STS16777184 Long, DWord, LBCD
SC000-SC16777215 Boolean
Retentive Timer Coils* SC000-SC16777200 Short, Word, BCD Read/Write
SC000-SC16777184 Long, DWord, LBCD
CS0000-CS16777215 Boolean
Counter Contacts* CS0000-CS16777200 Short, Word, BCD Read/Write
CS0000-CS16777184 Long, DWord, LBCD
CC0000-CC16777215 Boolean
Counter Coils* CC0000-CC16777200 Short, Word, BCD Read/Write
CC0000-CC16777184 Long, DWord, LBCD

* Users can specify a Long data type by appending a space and an "L" to the address. For example, "CS0000"
would be entered as "CS0000 L". This does not apply to arrays or bit accessed registers.

N ote: All Boolean device types can be accessed as Short, Word, BCD, Long, DWord and LBCD; however,
the device must be addressed on a 16-bit boundary.

Device Type Range Dat a Type Access

Short, Word,
Timer Value TN0000-TN16777215 Read/Write
BCD
Retentive Short, Word,
SN0000-SN16777215 Read/Write
Timer Value BCD
Short, Word,
Counter Value CN0000-CN16777215 Read/Write
BCD
Short, Word,
BCD
D0000000-D16777215 Long, DWord,
Data D0000000-D16777214 LBCD, Float,
Read/Write
Registers* * * D0000000-D16777212 Date
See Also:Extended Registers Double

Short, Word,
D0000000.00–D16777215.15*
BCD,
Data Register D0000000.00–16777212.31*
Boolean* * Read/Write
Bit Access
Long, DWord,
See Also:Extended Registers
LBCD
Data DSH00000.002-DSH16777214.002 String Read/Write

www. ptc.com
Mitsubishi Ethernet Driver 37

Device Type Range Dat a Type Access

Registers DSH00000.128-DSH16777151.128
String Access
HiLo Byte The string length may also be specified using a colon. The
Ordering string length must be between 2-128 bytes and even.
Data DSL00000.002-DSL16777214.002
Registers DSL00000.128-DSL16777151.128
String Access String Read/Write
LoHi Byte The string length may also be specified using a colon. The
Ordering string length must be between 2-128 bytes and even.
Short, Word,
BCD
SD0000-SD65535
Special Data Long, DWord,
SD0000-SD65534 Read/Write
Registers* * * LBCD, Float,
SD0000-SD65532
Date
Double
Short, Word,
BCD,
Data Register SD0000.00-SD65535.15*
Boolean* * Read/Write
Bit Access SD0000.00-SD65534.31*
Long, DWord,
LBCD
Short, Word,
BCD
W0000-WFFFFFF(Hex)
Long, DWord,
W0000-WFFFFFE(Hex)
Link LBCD, Float,
W0000-WFFFFFC(Hex) Read/Write
Registers* * * Date,
Double
See Also:Extended Registers

Short, Word,
BCD,
W0000.00-WFFFFFF.15*
Boolean* *
Link Register W0000.00-WFFFFFE.31*
Long, DWord, Read/Write
Bit Access
LBCD
See Also:Extended Registers

WSH0000.002-WSHFFFFFE.002
Link Registers
WSH0000.128-WSH3FD7BF.128
String Access String
Read/Write
HiLo Byte
The string length may also be specified using a colon. The
Ordering
string length must be between 2-128 bytes and even.
WSL0000.002-WSLFFFFFE.002
Link Registers
WSL0000.128-WSLFFFFBF.128
String Access String
Read/Write
LoHi Byte
The string length may also be specified using a colon. The
Ordering
string length must be between 2-128 bytes and even.
Special Link SW0000-SWFFFFFF (Hex) Short, Word,
Read/Write
Registers* * * SW0000-SWFFFFFE (Hex) BCD

www. ptc.com
38 M itsu b ish i Eth ern et Driver

Device Type Range Dat a Type Access

Long, DWord,
LBCD, Float,
SW0000-SWFFFFFC (Hex)
Date
Double
Short, Word,
BCD,
Link Register SW0000.00-SWFFFFFF.15*
Boolean* * Read/Write
Bit Access SW0000.00-SWFFFFFE.31*
Long, DWord,
LBCD
Short, Word,
BCD
Long, DWord,
R00000-R65535 LBCD, Float,
R00000-R65534 Date
R00000-R65532 Double
File
Read/Write
Register* * *
ZR0000-ZRFFFFFF (Hex) Short, Word,
ZR0000-ZRFFFFFE (Hex) BCD
ZR0000-ZRFFFFFC (Hex) Long, DWord,
LBCD, Float,
Date
Double
Short, Word,
BCD,
Boolean* *
R00000.00-R65535.15* Long, DWord,
R00000.00-R65534.31* LBCD
File Register
Read/Write
Bit Access
ZR0000.00-ZRFFFFFF.15* Short, Word,
ZR0000.00-ZRFFFFFE.31* BCD,
Boolean* *
Long, DWord,
LBCD
RSH00000.002-RSH65534.002
RSH00000.128-RSH65471.128 String
File Registers
ZRSH0000.002-ZRSHFFFFFE.002
String Access
ZRSH0000.128-ZRSHFFFFBF.128 Read/Write
HiLo Byte
String
Ordering
The string length may also be specified using a colon. The
string length must be between 2-128 bytes and even.
RSL00000.002-RSL65534.002
RSL00000.128-RSL16777151.128 String
File Registers
ZRSL0000.002-ZRSLFFFFFE.002
String Access
ZRSL0000.128-ZRSLFFFFBF.128 Read/Write
LoHi Byte
String
Ordering
The string length may also be specified using a colon. The
string length must be between 2-128 bytes and even.

www. ptc.com
Mitsubishi Ethernet Driver 39

Device Type Range Dat a Type Access

Short, Word,
BCD
Z00-Z255
Index Long, DWord,
Z00-Z254 Read/Write
Registers* * * LBCD, Float,
Z00-Z252
Date
Double
Short, Word,
BCD,
Index Register Z00.00-Z255.15*
Boolean* * Read/Write
Bit Access Z00.00-Z254.31*
Long, DWord,
LBCD

* For register memory, the data types Short, Word, BCD, DWord, Long, LBCD and Boolean may append an
optional ".bb" (dot bit) or ":bb" (colon bit) to the address to reference a bit in a particular value. The valid
ranges for the optional bit are 0-15 for Short, Word, BCD and Boolean; and 0-31 for Long, DWord and LBCD.
Strings use the bit number to specify length. The valid length of a string in D memory is 2 to 128 bytes. The
string length must be an even number. Float types do not support bit operations. The bit number is always in
decimal notation.
* * When accessing register memory as Boolean, a bit number is required.
* * * Users can specify a Long data type by appending a space and an "L" to the address. For example,
"CS0000" would be entered as "CS0000 L". This does not apply to arrays or bit accessed registers.

Extended Registers
The extended range for Data Registers is D12288 to D16777215. The extended range for Link Registers is
W3FFF (Hex) to WFFFFFF (Hex). These must be configured on the device.

Array Access
Many device types can be accessed as arrays. Boolean arrays and Date arrays are not supported. The
default array tag for device types is Word. The size of the array depends on both the data type and the
device type. Arrays may be one or two dimensions and the total number of Words being requested cannot
exceed the Max Read Block Size specified for the device.

N ote: An array is created when array notation is appended onto a normal device reference.

Exam ples:

1. D100 [4] Single dimension includes the following register addresses: D100, D101, D102, D103.

2. M016 [3][4] Two Dimensions includes the following device addresses as words: M016, M032, M048,
M064, M080, M096, M112, M128, M144, M160, M176, M192 3 rows x 4 columns =12 words 12 x 16
(word) =192 total bits.

Additional Device Examples

1. Access X device memory as Word: X??? where the ??? is a hex number on 16-bit boundaries such as
010, 020, 030, and so forth.

2. Access M device memory as Long: M???? where the ???? is a decimal number on 16-bit boundaries
such as 0, 16, 32, 48, and so forth.

www. ptc.com
40 M itsu b ish i Eth ern et Driver

M it subishi iQ-F Series Address Descript ions

The default data types for dynamically defined tags are shown in bold.

Device Type Range Dat a Type Access

X0000-X177777 (Octal) Boolean
Inputs* X0000-X177760 (Octal) Short, Word, BCD Read/Write
X0000-X177740 (Octal) Long, DWord, LBCD
Y0000-Y177777 (Octal) Boolean
Outputs* Y0000-Y177760 (Octal) Short, Word, BCD Read/Write
Y0000-Y177740 (Octal) Long, DWord, LBCD
B0000-BFFFF (Hex) Boolean
Link Relays* B0000-BFFF0 (Hex) Short, Word, BCD Read/Write
B0000-BFFE0 (Hex) Long, DWord, LBCD
SB0000-SBFFFF (Hex) Boolean
Special Link Relays* SB0000-SBFFF0 (Hex) Short, Word, BCD Read/Write
SB0000-SBFFE0 (Hex) Long, DWord, LBCD
M0000-M65535 Boolean
Internal Relays* M0000-M65520 Short, Word, BCD Read/Write
M0000-M65504 Long, DWord, LBCD
SM0000-SM65535 Boolean
Special Int. Relays* SM0000-SM65520 Short, Word, BCD Read/Write
SM0000-SM65504 Long, DWord, LBCD
L0000-L66535 Boolean
Latch Relays* L0000-L65520 Short, Word, BCD Read/Write
L0000-L65504 Long, DWord, LBCD
F0000-F65535 Boolean
Annunciator Relays* F0000-F65520 Short, Word, BCD Read/Write
F0000-F65504 Long, DWord, LBCD
S0000-S65535 Boolean
Step Relays* S0000-S65520 Short, Word, BCD Read/Write
S0000-S65504 Long, DWord, LBCD
TS0000-TS65535 Boolean
Timer Contacts* TS0000-TS65520 Short, Word, BCD Read/Write
TS0000-TS65504 Long, DWord, LBCD
TC0000-TC65535 Boolean
Timer Coils* TC0000-TC65520 Short, Word, BCD Read/Write
TC0000-TC65504 Long, DWord, LBCD
STS0000-STS65535 Boolean
Retentive Timer Contacts* STS0000-STS65520 Short, Word, BCD Read/Write
STS0000-STS65504 Long, DWord, LBCD
SC000-SC16777215 Boolean
Retentive Timer Coils* SC000-SC16777200 Short, Word, BCD Read/Write
SC000-SC16777184 Long, DWord, LBCD
CS0000-CS65535 Boolean
Counter Contacts* CS0000-CS65520 Short, Word, BCD Read/Write
CS0000-CS65504 Long, DWord, LBCD

www. ptc.com
Mitsubishi Ethernet Driver 41

Device Type Range Dat a Type Access

CC0000-CC65535 Boolean
Counter Coils* CC0000-CC65520 Short, Word, BCD Read/Write
CC0000-CC65504 Long, DWord, LBCD

* Users can specify a Long data type by appending a space and an "L" to the address. For example, "CS0000"
would be entered as "CS0000 L". This does not apply to arrays or bit accessed registers.

N ote: All Boolean device types can be accessed as Short, Word, BCD, Long, DWord and LBCD; however,
the device must be addressed on a 16-bit boundary.

Device Type Range Dat a Type Access

Short, Word,
Timer Value TN0000-TN65535 Read/Write
BCD
Retentive Short, Word,
STN0000-STN65535 Read/Write
Timer Value BCD
Short, Word,
Counter Value CN0000-CN65535 Read/Write
BCD
Short, Word,
BCD
D0000000-D65535 Long, DWord,
Data D0000000-D65534 LBCD, Float,
Read/Write
Registers* * * D0000000-D65532 Date
See Also: Extended Registers Double

Short, Word,
D0000000.00–D65535.15*
BCD,
Data Register D0000000.00–D65534.31*
Boolean* * Read/Write
Bit Access
Long, DWord,
See Also: Extended Registers
LBCD
Data DSH00000.002-DSH65534.002
Registers DSH00000.128-DSH65471.128
String Access String Read/Write
HiLo Byte The string length may also be specified using a colon. The
Ordering string length must be between 2-128 bytes and even.
Data DSL00000.002-DSL65534.002
Registers DSL00000.128-DSL65471.128
String Access String Read/Write
LoHi Byte The string length may also be specified using a colon. The
Ordering string length must be between 2-128 bytes and even.
Short, Word,
BCD
SD0000-SD65535
Special Data Long, DWord,
SD0000-SD65534 Read/Write
Registers* * * LBCD, Float,
SD0000-SD65532
Date
Double

www. ptc.com
42 M itsu b ish i Eth ern et Driver

Device Type Range Dat a Type Access

Short, Word,
BCD,
Data Register SD0000.00-SD65535.15*
Boolean* * Read/Write
Bit Access SD0000.00-SD65534.31*
Long, DWord,
LBCD
Short, Word,
BCD
W0000-WFFFF(Hex)
Long, DWord,
W0000-WFFFE(Hex)
Link LBCD, Float,
W0000-WFFFC(Hex) Read/Write
Registers* * * Date,
Double
See Also: Extended Registers

Short, Word,
BCD,
W0000.00-WFFFF.15*
Boolean* *
Link Register W0000.00-WFFFE.31*
Long, DWord, Read/Write
Bit Access
LBCD
See Also: Extended Registers

WSH0000.002-WSHFFFE.002
Link Registers
WSH0000.128-WSHFFBF.128
String Access String
Read/Write
HiLo Byte
The string length may also be specified using a colon. The
Ordering
string length must be between 2-128 bytes and even.
WSL0000.002-WSLFFFE.002
Link Registers
WSL0000.128-WSLFFBF.128
String Access String
Read/Write
LoHi Byte
The string length may also be specified using a colon. The
Ordering
string length must be between 2-128 bytes and even.
Short, Word,
BCD
SW0000-SWFFFF(Hex)
Special Link Long, DWord,
SW0000-SWFFFE(Hex) Read/Write
Registers* * * LBCD, Float,
SW0000-SWFFFC(Hex)
Date
Double
Short, Word,
BCD,
Link Register SW0000.00-SWFFFF.15*
Boolean* * Read/Write
Bit Access SW0000.00-SWFFFE.31*
Long, DWord,
LBCD
Short, Word,
BCD
R00000-R65535
File Long, DWord,
R00000-R65534 Read/Write
Register* * * LBCD, Float,
R00000-R65532
Date
Double

www. ptc.com
Mitsubishi Ethernet Driver 43

Device Type Range Dat a Type Access

Short, Word,
BCD,
File Register R00000.00-R65535.15*
Boolean* * Read/Write
Bit Access R00000.00-R65534.31*
Long, DWord,
LBCD
RSH00000.002-RSH65534.002
File Registers
RSH00000.128-RSH65471.128
String Access String
Read/Write
HiLo Byte
The string length may also be specified using a colon. The
Ordering
string length must be between 2-128 bytes and even.
RSL00000.002-RSL65534.002
File Registers
RSL00000.128-RSL65471.128
String Access String
Read/Write
LoHi Byte
The string length may also be specified using a colon. The
Ordering
string length must be between 2-128 bytes and even.
Short, Word,
BCD
Z00-Z255
Index Long, DWord,
Z00-Z254 Read/Write
Registers* * * LBCD, Float,
Z00-Z252
Date
Double
Short, Word,
BCD,
Index Register Z00.00-Z255.15*
Boolean* * Read/Write
Bit Access Z00.00-Z254.31*
Long, DWord,
LBCD

* For register memory, the data types Short, Word, BCD, DWord, Long, LBCD and Boolean may append an
optional ".bb" (dot bit) or ":bb" (colon bit) to the address to reference a bit in a particular value. The valid
ranges for the optional bit are 0-15 for Short, Word, BCD and Boolean; and 0-31 for Long, DWord and LBCD.
Strings use the bit number to specify length. The valid length of a string in D memory is 2 to 128 bytes. The
string length must be an even number. Float types do not support bit operations. The bit number is always in
decimal notation.
* * When accessing register memory as Boolean, a bit number is required.
* * * Users can specify a Long data type by appending a space and an "L" to the address. For example,
"CS0000" would be entered as "CS0000 L". This does not apply to arrays or bit accessed registers.

Extended Registers
The extended range for Data Registers is D12288 to D65535. The extended range for Link Registers is
W3FFF (Hex) to WFFFF (Hex). These must be configured on the device.

Array Access
Many device types can be accessed as arrays. Boolean arrays and Date arrays are not supported. The
default array tag for device types is Word. The size of the array depends on both the data type and the
device type. Arrays may be one or two dimensions and the total number of Words being requested cannot
exceed the Max Read Block Size specified for the device.

N ote: An array is created when array notation is appended onto a normal device reference.

www. ptc.com
44 M itsu b ish i Eth ern et Driver

Exam ples:

1. D100 [4] Single dimension includes the following register addresses: D100, D101, D102, D103.

2. M016 [3][4] Two Dimensions includes the following device addresses as words: M016, M032, M048,
M064, M080, M096, M112, M128, M144, M160, M176, M192 3 rows x 4 columns =12 words 12 x 16
(word) =192 total bits.

Additional Device Examples

1. Access X device memory as Word: X??? where the ??? is a hex number on 16-bit boundaries such as
010, 020, 030, and so forth.

2. Access M device memory as Long: M???? where the ???? is a decimal number on 16-bit boundaries
such as 0, 16, 32, 48, and so forth.

M it subishi QnA Series Address Descript ions

The default data types for dynamically defined tags are shown in bold.

Device Type Range Dat a Type Access

X0000-X3FFF (Hex) Boolean
Inputs* X0000-X3FF0 (Hex) Short, Word, BCD Read/Write
X0000-X3FE0 (Hex) Long, DWord, LBCD
DX0000-DX3FFF (Hex) Boolean
Direct Inputs* DX0000-DX3FF0 (Hex) Short, Word, BCD Read/Write
DX0000-DX3FE0 (Hex) Long, DWord, LBCD
Y0000-Y3FFF (Hex) Boolean
Outputs* Y0000-Y3FF0 (Hex) Short, Word, BCD Read/Write
Y0000-Y3FE0 (Hex) Long, DWord, LBCD
DY0000-DY3FFF (Hex) Boolean
Direct Outputs* DY0000-DY3FF0 (Hex) Short, Word, BCD Read/Write
DY0000-DY3FE0 (Hex) Long, DWord, LBCD
B0000-BEA6F (Hex) Boolean
Link Relays* B0000-BEA50 (Hex) Short, Word, BCD Read/Write
B0000-BEA40 (Hex) Long, DWord, LBCD
SB0000-SB7D0F (Hex) Boolean
Special Link Relays* SB0000-SB7CF0 (Hex) Short, Word, BCD Read/Write
SB0000-SB7CE0 (Hex) Long, DWord, LBCD
M0000-M60015 Boolean
Internal Relays* M0000-M59984 Short, Word, BCD Read/Write
M0000-M59968 Long, DWord, LBCD
SM0000-SM2047 Boolean
Special Int. Relays* SM0000-SM2032 Short, Word, BCD Read/Write
SM0000-SM2016 Long, DWord, LBCD
L0000-L32015 Boolean
Latch Relays* L0000-L31984 Short, Word, BCD Read/Write
L0000-L31968 Long, DWord, LBCD

www. ptc.com
Mitsubishi Ethernet Driver 45

Device Type Range Dat a Type Access

F0000-F32015 Boolean
Annunciator Relays* F0000-F31984 Short, Word, BCD Read/Write
F0000-F31968 Long, DWord, LBCD
V0000-V32015 Boolean
Edge Relays* V0000-V31984 Short, Word, BCD Read/Write
V0000-V31968 Long, DWord, LBCD
S0000-S16383 Boolean
Step Relays* S0000-S16368 Short, Word, BCD Read/Write
S0000-S16352 Long, DWord, LBCD
TS0000-TS32015 Boolean
Timer Contacts* TS0000-TS31984 Short, Word, BCD Read/Write
TS0000-TS31968 Long, DWord, LBCD
TC0000-TC32015 Boolean
Timer Coils* TC0000-TC31984 Short, Word, BCD Read/Write
TC0000-TC31968 Long, DWord, LBCD
SS0000-SS2047 Boolean
Integrating Timer Contacts* SS0000-SS2032 Short, Word, BCD Read/Write
SS0000-SS2016 Long, DWord, LBCD
SC0000-SC2047 Boolean
Integrating Timer Coils* SC0000-SC2032 Short, Word, BCD Read/Write
SC0000-SC2016 Long, DWord, LBCD
CS0000-CS32015 Boolean
Counter Contacts* CS0000-CS31984 Short, Word, BCD Read/Write
CS0000-CS31968 Long, DWord, LBCD
CC0000-CC32015 Boolean
Counter Coils* CC0000-CC31984 Short, Word, BCD Read/Write
CC0000-CC31968 Long, DWord, LBCD

* Users can specify a Long data type by appending a space and an "L" to the address. For example, "CS0000"
would be entered as "CS0000 L". This does not apply to arrays or bit accessed registers.

N ote: All Boolean device types can be accessed as Short, Word, BCD, Long, DWord and LBCD; however,
the device must be addressed on a 16-bit boundary.

Device Type Range Dat a Type Access

Short, Word,
Timer Value TN0000-TN32000 Read/Write
BCD
Integrating Short, Word,
SN0000-SN2047 Read/Write
Timer Value BCD
Short, Word,
Counter Value CN0000-CN32000 Read/Write
BCD
D0000000-D4184063 Short, Word,
D0000000-D4184062 BCD
Data
D0000000-D4184060 Long, DWord, Read/Write
Registers* * *
LBCD, Float,
See Also: Extended Registers Date

www. ptc.com
46 M itsu b ish i Eth ern et Driver

Device Type Range Dat a Type Access

Double

Short, Word,
D0000000.00–D4184063.15*
BCD,
Data Register D0000000.00–D4184062.31*
Boolean* * Read/Write
Bit Access
Long, DWord,
See Also:Extended Registers
LBCD
Data DSH00000.002-DSH4184062.002
Registers DSH00000.128-DSH4183999.128
String Access String Read/Write
HiLo Byte The string length may also be specified using a colon. The
Ordering string length must be between 2-128 bytes and even.
Data DSL00000.002-DSL4184062.002
Registers DSL00000.128-DSL4183999.128
String Access String Read/Write
LoHi Byte The string length may also be specified using a colon. The
Ordering string length must be between 2-128 bytes and even.
Short, Word,
BCD
SD0000-SD2047
Special Data Long, DWord,
SD0000-SD2046 Read/Write
Registers* * * LBCD, Float,
SD0000-SD2044
Date
Double
Short, Word,
BCD,
Data Register SD0000.00-SD2047.15*
Boolean* * Read/Write
Bit Access SD0000.00-SD2046.31*
Long, DWord,
LBCD
Short, Word,
W0000-W3FD7FF (Hex) BCD
W0000-W3FD7FE (Hex) Long, DWord,
Link
W0000-W3FD7FC (Hex) LBCD, Float, Read/Write
Registers* * *
Date
See Also:Extended Registers Double

Short, Word,
W0000.00-W3FD7FF.15*
BCD,
Link Register W0000.00-W3FD7FE.31*
Boolean* * Read/Write
Bit Access
Long, DWord,
See Also:Extended Registers
LBCD
WSH0000.002-WSH3FD7FE.002
Link Registers String
WSH0000.128-WSH3FD7BF.128
String Access
Read/Write
HiLo Byte
The string length may also be specified using a colon. The
Ordering
string length must be between 2-128 bytes and even.
Link Registers WSL0000.002-WSL3FD7FE.002 String Read/Write

www. ptc.com
Mitsubishi Ethernet Driver 47

Device Type Range Dat a Type Access

WSL0000.128-WSL3FD7BF.128
String Access
LoHi Byte
The string length may also be specified using a colon. The
Ordering
string length must be between 2-128 bytes and even.
Short, Word,
BCD
SW0000-SW7D00 (Hex)
Special Link Long, DWord,
SW0000-SW7CFF (Hex) Read/Write
Registers* * * LBCD, Float,
SW0000-SW7CFD (Hex)
Date
Double
Short, Word,
BCD,
Link Register SW0000.00-SW7D00.15*
Boolean* * Read/Write
Bit Access SW0000.00-SW7CFF.31*
Long, DWord,
LBCD
Short, Word,
BCD
Long, DWord,
R00000-R32767 LBCD, Float,
R00000-R32766 Date
R00000-R32764 Double
File
Read/Write
Register* * *
ZR0000-ZR3FD7FF (Hex) Short, Word,
ZR0000-ZR3FD7FE (Hex) BCD
ZR0000-ZR3FD7FC (Hex) Long, DWord,
LBCD, Float,
Date
Double
Short, Word,
BCD,
Boolean* *
R00000.00-R32767.15* Long, DWord,
R00000.00-R32766.31* LBCD
File Register
Read/Write
Bit Access
ZR0000.00-ZR3FD7FF.15* Short, Word,
ZR0000.00-ZR3FD7FE.31* BCD,
Boolean* *
Long, DWord,
LBCD
RSH00000.002-RSH32766.002
RSH00000.128-RSH32703.128 String
File Registers
String Access ZRSH0000.002-ZRSH3FD7FE.002
Read/Write
HiLo Byte ZRSH0000.128-ZRSH3FD7BF.128 String
Ordering
The string length may also be specified using a colon. The
string length must be between 2-128 bytes and even.

www. ptc.com
48 M itsu b ish i Eth ern et Driver

Device Type Range Dat a Type Access

RSL00000.002-RSL32766.002
RSL00000.128-RSL32703.128 String
File Registers
String Access ZRSL0000.002-ZRSL3FD7FE.002
Read/Write
LoHi Byte ZRSL0000.128-ZRSL3FD7BF.128 String
Ordering
The string length may also be specified using a colon. The
string length must be between 2-128 bytes and even.
Short, Word,
BCD
Z00-Z20
Index Long, DWord,
Z00-Z19 Read/Write
Registers* * * LBCD, Float,
Z00-Z17
Date
Double
Short, Word,
BCD,
Index Register Z00.00-Z20.15*
Boolean* * Read/Write
Bit Access Z00.00-Z19.31*
Long, DWord,
LBCD

* For register memory, the data types Short, Word, BCD, DWord, Long, LBCD and Boolean may append an
optional ".bb" (dot bit) or ":bb" (colon bit) to the address to reference a bit in a particular value. The valid
ranges for the optional bit are 0-15 for Short, Word, BCD and Boolean; and 0-31 for Long, DWord and LBCD.
Strings use the bit number to specify length. The valid length of a string in D memory is 2 to 128 bytes. The
string length must be an even number. Float types do not support bit operations. The bit number is always in
decimal notation.
* * When accessing register memory as Boolean, a bit number is required.
* * * Users can specify a Long data type by appending a space and an "L" to the address. For example,
"CS0000" would be entered as "CS0000 L". This does not apply to arrays or bit accessed registers.

Extended Registers
The extended range for Data Registers is D12288 to D4184063. The extended range for Link Registers is
W3FFF (Hex) to W3FD7FF (Hex). These must be configured on the device.

Array Access
Many device types can be accessed as arrays. Boolean arrays and Date arrays are not supported. The
default array tag for device types is Word. The size of the array depends on both the data type and the
device type. Arrays may be one or two dimensions and the total number of Words being requested cannot
exceed the Max Read Block Size specified for the device.

N ote: An array is created when array notation is appended onto a normal device reference.

Exam ples:

1. D100 [4] Single dimension includes the following register addresses: D100, D101, D102, D103.

2. M016 [3][4] Two Dimensions includes the following device addresses as words: M016, M032, M048,

www. ptc.com
Mitsubishi Ethernet Driver 49

M064, M080, M096, M112, M128, M144, M160, M176, M192 3 rows x 4 columns =12 words 12 x 16
(word) =192 total bits.

Additional Device Examples

1. Access X device memory as Word: X??? where the ??? is a hex number on 16-bit boundaries such as
010, 020, 030, and so forth.

2. Access M device memory as Long: M???? where the ???? is a decimal number on 16-bit boundaries
such as 0, 16, 32, 48, and so forth.

www. ptc.com
50 M itsu b ish i Eth ern et Driver

Event Log Messages

The following information concerns messages posted to the Event Log pane in the main user interface. Con-
sult the server help on filtering and sorting the Event Log detail view. Server help contains many common
messages, so should also be searched. Generally, the type of message (informational, warning) and
troubleshooting information is provided whenever possible.

Unable t o read from address block on device. The device report ed an

invalid address or an error. | Address block = '<address>' t o '<address>'.
Error Type:
Error

Possible Cause:
1. An attempt has been made to read a non-existent location in the specified device.

2. An attempt has been made to read from an address in a device that is not located on the specified
network node.

Possible Solution:
1. Verify or correct the tags assigned to addresses in the specified range on the device. Eliminate or
update any that reference invalid locations.

2. Verify that the node ID referenced in the device address is correct.

Unable t o read from device. The device ret urned a PC num ber error.
Error Type:
Error

Possible Cause:
The PC number entered for the device ID is invalid. This may occur if the MelsecNet station is not available.

Possible Solution:
1. If attempting to communicate with a PC located on MelsecNet, verify the PC number of the target PC.

2. If intending to communicate directly with the local PC with the Ethernet connection, specify a PC num-
ber of 255.

Note:
All tag reads fail until the PC number is corrected.

Unable t o writ e t o address on device. The device ret urned a PC num ber
error. | Address = '<address>'.
Error Type:

www. ptc.com
Mitsubishi Ethernet Driver 51

Error

Possible Cause:
The PC number entered for the device ID is invalid. This may occur if the MelsecNet station is not available.

Possible Solution:
1. If attempting to communicate with a PC located on MelsecNet, verify the PC number of the target PC.

2. If intending to communicate directly with the local PC with the Ethernet connection, specify a PC num-
ber of 255.

Unable t o writ e t o address on device. The device report ed an invalid

address or an error. | Address = '<address>'.
Error Type:
Error

Possible Cause:
1. An attempt has been made to write a non-existent location in the specified device.

2. An attempt has been made to write from an address in a device that is not located on the specified
network node.

Possible Solution:
1. Verify or correct the tags assigned to addresses in the specified range on the device. Eliminate or
update any that reference invalid locations.

2. Verify that the node ID referenced in the device address is correct.

Unable t o read from address on device. The device report ed an invalid

address or an error. | Address = '<address>'.
Error Type:
Error

Possible Cause:
1. An attempt has been made to read a non-existent location in the specified device.

2. An attempt has been made to read from an address in a device that is not located on the specified
network node.

Possible Solution:
1. Verify or correct the tags assigned to addresses in the specified range on the device. Eliminate or
update any that reference invalid locations.

2. Verify that the node ID referenced in the device address is correct.

www. ptc.com
52 M itsu b ish i Eth ern et Driver

Unable t o read from address on device. Device ret urned an error. |

Address = '<address>', Error code = <code>.
Error Type:
Error

Possible Cause:
Communication with the device succeeded, but the device reported a problem.

Possible Solution:
Consult the device documentation for information about the error code provided.

Unable t o read from address block on device. Device ret urned an error. |
Address block = '<address>' t o '<address>', Error code = <code>.
Error Type:
Error

Possible Cause:
Communication with the device succeeded, but the device reported a problem.

Possible Solution:
Consult the device documentation for information about the error code provided.

Unable t o writ e t o address on device. Device ret urned error. | Address =

'<address>', Error code = <code>.
Error Type:
Error

Possible Cause:
Communication with the device succeeded, but the device reported a problem.

Possible Solution:
Consult the device documentation for information about the error code provided.

Unable t o read from address block on device. | Address block = '<address>'

t o '<address>'.
Error Type:
Error

Possible Cause:
The driver could not allocate the resources required to read from the device.

Possible Solution:
Shut down unnecessary applications and try again.

www. ptc.com
Mitsubishi Ethernet Driver 53

Unable t o read from address on device. | Address = '<address>'.

Error Type:
Error

Possible Cause:
The driver could not allocate the resources required to read from the device.

Possible Solution:
Shut down unnecessary applications and try again.

Unable t o writ e t o address on device. Device m ust be configured t o allow

writ es while in RUN m ode. | Address = '<address>'.
Error Type:
Warning

Possible Cause:
The device is not configured to allow transactions during RUN mode.

Possible Solution:
1. For A-Series and QnA-Series PLCs, configure the AJ71E71 card to allow writes to occur during RUN by
setting DIP switch 7 to the ON position.

2. For Q-Series and L-Series PLCs, use GX Developer to enable the setting "Enable Write at RUN time" in
Ethernet Operations settings.

See Also:
1. A-Series PLC Setup

2. QnA-Series PLC Setup

3. Q-Series PLC Setup

Failed t o synchronize t im e and dat e for device. | Ret ry int erval = <num -
ber> (m inut es).
Error Type:
Warning

Possible Cause:
The driver failed to write time and date data to the PLC.

Possible Solution:
1. Verify the cabling between the PC and the PLC device.

2. Verify that the specified communications parameters match those of the device.

3. Verify that the network ID given to the named device matches that of the actual device.

www. ptc.com
54 M itsu b ish i Eth ern et Driver

Note:
The driver automatically retries after the indicated time interval.

www. ptc.com
Mitsubishi Ethernet Driver 55

Appendix: PLC Setup

The hardware must be configured for Ethernet communications. For information on a specific hardware
series, select a link from the list below.

The following is provided for convenience only. Refer to the manufacturer's documentation for current and offi-
cial instructions.

A Series PLC Set up

FX3U Series PLC Set up
L Series PLC Set up
Q Series PLC Set up
iQ-R Series PLC Set up
iQ-F Series PLC Set up
QnA Series PLC Set up
Q Series Built -in Et hernet Port PLC Set up

A Series PLC Set up

N ote: The following is provided for convenience only. Refer to the manufacturer's documentation for cur-
rent and official instructions.

Hardw are Settings

The DIP switches on the AJ71E71 Ethernet interface card must be set as follows.

l DIP switches 1-6 must be set to OFF.

l DIP switch 7 must be set to ON.
l DIP switch 8 must be set to OFF.

Ladder Program
The Mitsubishi A Series PLC requires that a ladder program be used to initialize the AJ71E71 or A1SJ71E71
Ethernet interface card and define the desired open system. TCP/IP and UDP open systems may be used
with this driver. In the case of TCP/IP, error handling code should also be implemented.

N ote: TCP/IP is less efficient than UDP and requires special ladder to handle network error recovery. Also,
if planning to communicate with devices on a remote network, TCP/IP requires that multiple ports be con-
figured in the relay device. Thus, UDP is recommended wherever possible. For more information, refer to
Multi-level N etworks.

Initialization Ladder
The following initialization code sets the IP address of the device and triggers execution of the open code.
For this example, an IP of 192.168.111.123 (C0.A8.6F.7B Hex) is assumed.

www. ptc.com
56 M itsu b ish i Eth ern et Driver

Open and Error Handling Ladder for TCP/ IP

The following open and error handling code assumes TCP/IP communications, unpassive mode, on port
5001 (1389 Hex).

This code is for the first communications buffer of the AJ71E71 card. Similar code must be implemented for
each additional buffer needed. Simply ensure that the proper interface bits are used as well as separate
error handling bits and timers for each buffer.

N ote: It is strongly recommended that users follow the code fragment as closely as possible. Without
proper error handling and recovery on the PLC side of the connection, communications with the PLC may not
be reestablished after a physical error, such as a cable break, occurs. Without the error handling rep-
resented here, PLC may have to be reset to reestablish communications.

Given the ladder fragment shown here for TCP/IP port operation, the AJ71E71 will be forced to close and re-
enable the port for a connection if the current connection is lost. This will occur 2 seconds after the error is
detected as controlled by T0. Reloading the port mode and port number and the set of Y008 resets the port.

Open Ladder for UDP

The following open code assumes UDP communications on port 5000 (1388 Hex). The UDP open system
requires that the destination address be specified. This would be the IP and port that the driver will use to

www. ptc.com
Mitsubishi Ethernet Driver 57

communicate with the PLC. To prevent issues with conflicting port usage, the Mitsubishi Ethernet Driver
allows Windows to assign any unused UDP port to each device configured in the driver on startup. Thus, the
port that the driver will use is not predictable. Therefore, the destination port must be configured in the PLC
as "unspecified". This is done by entering FFFF (Hex) as shown below. The exact IP address that the driver
will use may be specified. This example assumes 192.168.111.24 (C0.A8.6F.18 Hex). However, the des-
tination may also be left as "unspecified" with 255.255.255.255 (FF.FF.FF.FF Hex).

N ote: If a specific IP address is put into the ladder code, only the machine with that IP address will be able
to communicate with the PLC via UDP. If the IP address is left as "unspecified," then any IP address can com-
municate with the PLC.

FX3U Series PLC Set up

For the Mitsubishi Ethernet Driver to communicate with the FX3U PLC via the FX3U-ENET block, some net-
work parameters have to be configured in the FX3U PLC. The Mitsubishi GXDeveloper-FX software is neces-
sary for the following process.

Device Configuration
1. To start, create a new GXDeveloper project for a FX3U model. Then click Tools | FX Special Func-
tion Utility.

2. Next, select FX Configurator-EN .

www. ptc.com
58 M itsu b ish i Eth ern et Driver

N ote: The FX Configurator-EN dialog should appear as shown below.

3. Next, specify the FX3U-ENET block's minimum required configuration information. Select a module
from the first drop-down list and then click Operational Settings.

www. ptc.com
Mitsubishi Ethernet Driver 59

4. Specify the settings so that they appear similar to the ones shown above.

5. Click End.

6. In FX Configurator-EN , click Open Settings.

7. The open settings depend on the chosen IP protocol: TCP or UDP.

Open Settings for TCP

Enter TCP in the Protocol field. For simplicity, the Unpassive open system is recommended. By using the
unpassive open system, the IP and port that the driver will use do not need to be configured. The Procedure
exist(MC) communications procedure sets the correct protocol in the FX3U-ENET block to communicate with
this driver. In the example below, 5001 (1389 Hex) is specified in the Host station Port No. field.

N ote: The example shown below includes only one connection. To make multiple connections to the
device from the OPC server, add another entry on this screen and configure another open port (such as, Port
5002). Check the device's manual to verify the device's available ports.

www. ptc.com
60 M itsu b ish i Eth ern et Driver

Open Settings for UDP

1. Enter UDP in the Protocol field. There are no open system options for UDP. The Procedure exist
(MC) communications procedure sets the correct protocol in the FX3U-ENET block to communicate
with this driver. In the example below, 5000 (1388 Hex) is specified in the Host station Port No. field.

2. To allow this driver to choose any port for communications, configure the target port as "unspecified"
by entering 65535 (FFFFHex) in the Transmission target device Port No. field. The IP address that the
driver uses can be specified or not. To enter the "unspecified" address of 255.255.255.255, do as
shown below.

Write Netw ork Parameters to PLC

www. ptc.com
Mitsubishi Ethernet Driver 61

After all of the network parameters have been specified, they must be written to the PLC. To do so, click
Write from the main FX-Configurator-ENwindow.

N ote: There must be a serial connection to the FX3U PLC. The configuration settings are written to the PLC
via this serial link. Also make sure that the communication parameters are correct. Settings can be checked
by clicking Transfer Setup or be selecting Online | Transfer Setup from the main menu.

Users must cycle the power on the PLC for the network parameter changes to take effect.

L Series PLC Set up

The following is provided for convenience only. Refer to the manufacturer's documentation for current and offi-
cial instructions.

Like the Q series models, the newest L Series Ethernet modules (LJ71E71-100) do not have DIP switches that
need to be set. Furthermore, special ladder logic to enable Ethernet communications is not required. Users
must set network related parameters in the controller, however, using the Mitsubishi GX Developer soft-
ware. Ports may be configured to use TCP/IP or UDP.

N ote: TCP/IP is less efficient than UDP. Users planning to communicate with devices on a remote network
should note that TCP/IP requires multiple ports be configured in the relay device. UDP is recommended
wherever possible. For more information, refer to Multi-level Networks.

Device Configuration
1. To start, create a new GX Developer project for a L Series (LCPU) PLC. Alternatively, open and edit an
existing project.

2. Next, select N etwork Param .

www. ptc.com
62 M itsu b ish i Eth ern et Driver

3. In Network Parameter, click MELSECN ET/ Ethernet.

www. ptc.com
Mitsubishi Ethernet Driver 63

4. Fill in the required information for the Ethernet module. Although the network type must be Ethernet,
other settings will depend on the particular application. The example below is for station 1 on net-
work 1. The starting I/O No. is 0 in this case because the LJ71E71-100 Ethernet module is installed in
the slot adjacent to the CPU. If there are other modules between the CPU and Ethernet unit, determ-
ine the total I/O mapped to those and set the starting I/O of the Ethernet unit accordingly. Once these
basic network settings are specified, click on Operational Settings.

www. ptc.com
64 M itsu b ish i Eth ern et Driver

5. The Ethernet Operations dialog is used to define the device's IP address. Except for the IP address,
the settings should be as shown below.
N ote: Unless security or safety concerns require otherwise, make sure Enable Write at RUN
tim e is checked. If this is left unchecked, all writes will fail when the PLC is in Run mode.

www. ptc.com
Mitsubishi Ethernet Driver 65

6. Click End.

7. Upon returning to the basic network parameters dialog, click Open settings.

www. ptc.com
66 M itsu b ish i Eth ern et Driver

8. Specify the desired open settings. These depend on the chosen IP protocol, which may be TCP or
UDP.

Open Settings for TCP

Enter TCP for the protocol. For simplicity, the Unpassive open system is recommended. By using the unpass-
ive open system, users will not have to configure the IP and port that the driver will use. In the example
below, the local port number 5001 (1389 Hex) is specified.

Tip: Consult the Knowledge Base and the Mitsubishi Technical Bulletin "Existence Confirmation Con-
figuration using Fixed Buffer Communications with a QJ71E71-100 Ethernet Module" for detailed information
about device configuration for TCP communications.

Open Settings for UDP

1. Enter UDP for the protocol. There are no open system options for UDP. In the example below, the
local port number 5000 (1388 Hex) is specified.

2. Next, specify the destination IP and port. This would be the IP and port that the driver will use to com-
municate with the PLC. To prevent issues with conflicting port usage, the Mitsubishi Ethernet Driver
allows Windows to assign any unused UDP port to each device configured in the driver on startup.
Thus, the port that the driver will use is not predictable. Users must configure the destination port in
the PLC as "unspecified". This is done by entering FFFF (Hex) as shown below.

3. Finally, click on the Destination IP address button.

4. Either specify the IP address that the driver will be using or leave it at the "unspecified" address of
255.255.255.255 as shown below.

www. ptc.com
Mitsubishi Ethernet Driver 67

Write Netw ork Parameters to PLC

After all of the network parameters have been specified, they must be written to the PLC. This can be done
by selecting the Online | Write To PLC... menu option. Check the network parameters file selection and then
click Execute.

N ote: Users must cycle the power on the PLC for the network parameter changes to take effect.

www. ptc.com
68 M itsu b ish i Eth ern et Driver

L Series Built -in Et hernet Port PLC Set up

The following is provided for convenience only. Refer to the manufacturer's documentation for current and offi-
cial instructions.

For the Mitsubishi Ethernet Driver to communicate with the Mitsubishi L Series CPU's built-in Ethernet port,
some network parameters must be configured in the PLC.

Device Configuration
The following instructions were created using Mitsubishi GX Works2 software.

1. To start, create a new project for an L Series (LCPU) PLC. Alternatively, open and edit an existing pro-
ject.

2. Next, select PLC Param eter.

3. Open the Built-in Ethernet Port Setting tab, and then make the following changes:

l Beneath IP Address Setting, fill in all required information.

l Beneath Com m unication Data Code, select Binary Code.

www. ptc.com
Mitsubishi Ethernet Driver 69

4. Next, click Open Setting, and then make the following changes:

l Specify the Protocol. Options include UDP or TCP.

l Specify the Open System as MC Protocol.

l Specify the Host Station Port N o.

www. ptc.com
70 M itsu b ish i Eth ern et Driver

N ote: In the example above, the local port numbers 4998 (1386H) and 4999 (1387H) are
used.
Im portant: The driver's default port settings of 5000 UDP and 5001 TCP are not valid port
numbers for the built-in Ethernet port. The driver uses decimal numbers for the port num-
ber; GX Works2 uses hexadecimal number for the port numbers. Valid port number setting
ranges are 0401H (1025) to 1387H (4999), and 1392H (5010) to FFFEH (65534).

5. Click End.

Writing the Netw ork Parameters to the PLC

After all network parameters have been specified, they must be written to the PLC. To do so, click Online |
Write To PLC.... Then, check Param eter (located beneath Target) and then click Execute.

www. ptc.com
Mitsubishi Ethernet Driver 71

N ote: Users must cycle the power on the PLC for the network parameter changes to take effect.

QnA Series PLC Set up

The following is provided for convenience only. Refer to the manufacturer's documentation for current and offi-
cial instructions.

Hardw are Settings

The DIP switches on the A1SJ71QE71 Ethernet interface card must be set as follows:

l DIP switches 1-2 must be set to OFF.

l DIP switch 3 must be set to ON.
l DIP switches 4-6 must be set to OFF.
l DIP switch 7 must be set to ON.
l DIP switch 8 must be set to OFF.

Ladder Program
The Mitsubishi QnA Series PLC requires that a ladder program be used to initialize the AJ71QE71 or
A1SJ71QE71 Ethernet interface card and define the desired open system. TCP/IP and UDP open systems
may be used with this driver. In the case of TCP/IP, error handling code should also be implemented. Note
that TCP/IP is less efficient than UDP and requires a special ladder to handle network error recovery. Also, if
planning to communicate with devices on a remote network, TCP/IP requires that multiple ports be con-
figured in the relay device. Thus, UDP is recommended wherever possible. For more information, refer to
Multi-level N etworks.

N ote: Power must be cycled to the PLC for any network configuration to take effect.

www. ptc.com
72 M itsu b ish i Eth ern et Driver

Initialization Ladder
The following initialization code sets the IP address of the device and triggers execution of the open code.
For this example, an IP of 192.168.111.123 (C0.A8.6F.7B Hex) is assumed.

Open and Error Handling Ladder for TCP/ IP

The following open and error handling code assumes TCP/IP communications, unpassive mode, on port
5001 (1389 Hex).

This code is for the first communications buffer of the A1SJ71QE71 card. Similar code must be implemented
for each addition buffer needed. Simply ensure that the proper interface bits are used as well as separate
error handling bits and timers for each buffer.

N ote: It is strongly recommended that users follow the code fragment as closely as possible. Without
proper error handling and recovery on the PLC side of the connection, communications may not able to be
reestablished with the PLC after a physical error, such as a cable break, occurs. Without the error handling
represented here, the PLC may need to be reset to reestablish communications.

Given the ladder fragment shown here for TCP/IP port operation, the A1SJ71QE71 will be forced to close and
re-enable the port for a connection if the current connection is lost. This will occur 2 seconds after the error

www. ptc.com
Mitsubishi Ethernet Driver 73

is detected as controlled by T0. Reloading the port mode and port number and the set of Y008 resets the
port.

Open Ladder for UDP

The following open code assumes UDP communications on port 5000 (1388 Hex). The UDP open system
requires that the destination address be specified. This would be the IP and port that the driver will use to
communicate with the PLC. To prevent issues with conflicting port usage, the Mitsubishi Ethernet Driver
allows Windows to assign any unused UDP port to each device configured in the driver on startup. Thus, the
port that the driver will use is not predictable. Users must configure the destination port in the PLC as "unspe-
cified". This is done by entering FFFF (Hex) as shown below. The exact IP address the driver will use may be
specified. This example assumes 192.168.111.24 (C0.A8.6F.18 Hex). However, the destination may also be
left as "unspecified" with 255.255.255.255 (FF.FF.FF.FF Hex).

N ote: If a specific IP address is put into the ladder code, only the machine with that IP address will be able
to communicate with the PLC via UDP. If the IP address is left as "unspecified," then any IP address can com-
municate with the PLC.

Q Series PLC Set up

The following is provided for convenience only. Refer to the manufacturer's documentation for current and offi-
cial instructions.

Unlike the A and QnA series, the newest Q Series Ethernet modules (QJ71E71-100) do not have DIP switches
that need to be set. Furthermore, special ladder logic to enable Ethernet communications is not required.
Users must set network related parameters in the controller, however, using the Mitsubishi GX Developer
software. Ports may be configured to use TCP/IP or UDP.

N ote: TCP/IP is less efficient than UDP. Users planning to communicate with devices on a remote net-
work should note that TCP/IP requires multiple ports be configured in the relay device. UDP is recommended
wherever possible. For more information, refer to Multi-level N etworks.

Device Configuration
1. To start, create a new GX Developer project for a Q Series (Q mode) PLC. Alternatively, open and edit
an existing project.

2. Next, select N etwork Param .

www. ptc.com
74 M itsu b ish i Eth ern et Driver

3. In N etwork Param eter, click MELSECN ET/ Ethernet.

4. Fill in the required information for the Ethernet module. Although the network type must be Ethernet,
other settings will depend on the particular application. The example below is for station 1 on net-
work 1. The starting I/O No. is 0 in this case because the QJ71E71 Ethernet module is installed in the

www. ptc.com
Mitsubishi Ethernet Driver 75

slot adjacent to the CPU. If there are other modules between the CPU and Ethernet unit, determine
the total I/O mapped to those and set the starting I/O of the Ethernet unit accordingly. Once these
basic network settings are specified, click on Operational Settings.

5. The Ethernet Operations dialog is used to define the device's IP address. Except for the IP address,
the settings should be as shown below.

N ote: Unless security or safety concerns require otherwise, make sure "Enable Write at RUN
time" is checked. If this is left unchecked, all writes will fail when the PLC is in Run mode.

6. Click End.

7. Upon returning to the basic network parameters dialog, click Open settings.

www. ptc.com
76 M itsu b ish i Eth ern et Driver

8. Specify the desired open settings. These depend on the chosen IP protocol, which may be TCP or
UDP.

Open Settings for TCP

Enter TCP for the protocol. For simplicity, the Unpassive open system is recommended. By using the unpass-
ive open system, users will not have to configure the IP and port that the driver will use. In the example
below, the local port number 5001 (1389 Hex) is specified.

Tip: Consult the Knowledge Base and the Mitsubishi Technical Bulletin "Existence Confirmation Con-
figuration using Fixed Buffer Communications with a QJ71E71-100 Ethernet Module" for detailed information
about device configuration for TCP communications.

Open Settings for UDP

1. Enter UDP for the protocol. There are no open system options for UDP. In the example below, the
local port number 5000 (1388 Hex) is specified.

2. Next, specify the destination IP and port. This would be the IP and port that the driver will use to com-
municate with the PLC. To prevent issues with conflicting port usage, the Mitsubishi Ethernet Driver
allows Windows to assign any unused UDP port to each device configured in the driver on startup.
Thus, the port that the driver will use is not predictable. Users must configure the destination port in
the PLC as "unspecified". This is done by entering FFFF (Hex) as shown below.

3. Finally, click on the Destination IP address button.

www. ptc.com
Mitsubishi Ethernet Driver 77

4. Either specify the IP address that the driver will be using or leave it at the "unspecified" address of
255.255.255.255 as shown below.

Write Netw ork Parameters to PLC

After all of the network parameters have been specified, they must be written to the PLC. This can be done
by selecting the Online | Write To PLC... menu option. Check the network parameters file selection and
then click Execute.

www. ptc.com
78 M itsu b ish i Eth ern et Driver

N ote: Users must cycle the power on the PLC for the network parameter changes to take effect.

iQ-R Series PLC Set up

The following is provided for convenience only. Refer to the manufacturer's documentation for current and offi-
cial instructions.

Like the Q series models, the newest iQ-R Series Ethernet modules (R08 CPU) do not have DIP switches that
need to be set. Furthermore, special ladder logic to enable Ethernet communications is required. Users
must set network related parameters in the controller via the Mitsubishi GX Developer software. Ports may
be configured to use TCP/IP or UDP.

N ote: TCP/IP is less efficient than UDP. Users planning to communicate with devices on a remote net-
work should note that TCP/IP requires multiple ports be configured in the relay device. UDP is recommended
wherever possible. For more information, refer to Multi-level N etworks.

Device Configuration
1. To start, create a new GX Developer project for a iQ-R Series (R08) PLC. Alternatively, open and edit
an existing project.

N ote: Use GX Works3 for iQ-F and iQ-R series.

2. Connect GX Works3 to the CPU module and set the parameters.

3. Set the CPU module as follows:

l Series: RCPU

l Type: R08

l Program Language: Ladder

4. Click Yes to add the module labels of the CPU module.

www. ptc.com
Mitsubishi Ethernet Driver 79

5. Set the IP Address settings by selecting Basic Settings in the Navigation window under Param eter |
R08CPU | Module Param eter | Ethernet Port.

www. ptc.com
80 M itsu b ish i Eth ern et Driver

6. Set the External Device Configuration in the Navigation window under Param eter | R08CPU |
Module Param eter | Ethernet Port | Basic Settings.

7. Specify the desired open settings. These depend on the chosen IP protocol, which may be TCP or
UDP.

Write Netw ork Parameters to PLC

After all of the network parameters have been specified, they must be written to the PLC. Select Online |
Write To PLC... to specify the network parameters.

N ote: Users must cycle the power on the PLC for the network parameter changes to take effect.

iQ-F Series PLC Set up

The following is provided for convenience only. Refer to the manufacturer's documentation for current and offi-
cial instructions.

Like the Q series models, the newest iQ-F Series Ethernet modules (FX5U-32M) do not have DIP switches
that need to be set. Furthermore, special ladder logic to enable Ethernet communications is required. Users

www. ptc.com
Mitsubishi Ethernet Driver 81

must set network related parameters in the controller via the Mitsubishi GX Developer software. Ports may
be configured to use TCP/IP or UDP.

N ote: TCP/IP is less efficient than UDP. Users planning to communicate with devices on a remote net-
work should note that TCP/IP requires multiple ports be configured in the relay device. UDP is recommended
wherever possible. For more information, refer to Multi-level N etworks.

Device Configuration
1. To start, create a new GX Developer project for a iQ-F Series (FX5) PLC. Alternatively, open and edit
an existing project.

N ote: Use GX Works3 for iQ-F and iQ-R series.

2. Connect GX Works3 to the CPU module and set the parameters.

3. Set the CPU module as follows:

l Series: FX5CPU

l Type: FX5U

l Program Language: Ladder

4. Click Yes to add the module labels of the CPU module.

www. ptc.com
82 M itsu b ish i Eth ern et Driver

5. Set the IP Address settings by selecting Basic Settings in the Navigation window under Param eter |
FX5UCPU | Module Param eter | Ethernet Port.

6. Set the External Device Configuration in the Navigation window under Param eter | FX5UCPU |
Module Param eter | Ethernet Port | Basic Settings.

7. Specify the desired open settings. These depend on the chosen IP protocol, which may be TCP or
UDP.

Setting up the Ladder Program

1. Create a new ladder logic file by accessing Program | Scan | Main | ProgPou | Program in the Nav-
igation window.

N ote:For UDP Protocol Sensor/Device IP Address, the IP of the machine where the server is run-
ning must be specified.

www. ptc.com
Mitsubishi Ethernet Driver 83

2. To convert the ladder program, select the Convert from the main window menu options and click
Convert.

N ote:When the ladder program is incorrect, text in the Navigation window is red. Once suc-
cessfully configured, the text returns to the default color (white).

Write Netw ork Parameters to PLC

After all of the network parameters have been specified, they must be written to the PLC. Select Online |
Write To PLC... to specify the network parameters.

N ote: Users must cycle the power on the PLC for the network parameter changes to take effect.

Q Series Built -in Et hernet Port PLC Set up

The following is provided for convenience only. Refer to the manufacturer's documentation for current and offi-
cial instructions.

For the Mitsubishi Ethernet Driver to communicate with the Mitsubishi Q Series CPU's built-in Ethernet port,
some network parameters must be configured in the PLC.

Device Configuration
The following instructions were created using Mitsubishi GX Works2 software.

www. ptc.com
84 M itsu b ish i Eth ern et Driver

1. To start, create a new project for a Q Series (Q mode) PLC. Alternatively, open and edit an existing
project.

2. Next, select PLC Param eter.

3. Open the Built-in Ethernet Port Setting tab, and then make the following changes:

l Beneath IP Address Setting, fill in all required information.

l Beneath Com m unication Data Code, select Binary Code.

www. ptc.com
Mitsubishi Ethernet Driver 85

4. Next, click Open Setting, and then make the following changes:

l Specify the Protocol. Options include UDP or TCP.

l Specify the Open System as MC Protocol.

l Specify the Host Station Port N o.

N ote: In the example above, the local port numbers 4998 (1386H) and 4999 (1387H) are
used.
Im portant: The driver's default port settings of 5000 UDP and 5001 TCP are not valid port
numbers for the built-in Ethernet port. The driver uses decimal numbers for the port num-
ber; GX Works2 uses hexadecimal number for the port numbers. Valid port number setting
ranges are 0401H (1025) to 1387H (4999), and 1392H (5010) to FFFEH (65534).

5. Click End.

Writing the Netw ork Parameters to the PLC

After all network parameters have been specified, they must be written to the PLC. To do so, click Online |
Write To PLC.... Then, check Param eter (located beneath Target) and then click Execute.

www. ptc.com
86 M itsu b ish i Eth ern et Driver

N ote: Users must cycle the power on the PLC for the network parameter changes to take effect.

www. ptc.com
Mitsubishi Ethernet Driver 87

Index

32-Bit Data 11

A Series PLC Setup 55

Absolute 14
Address Descriptions 19
Array Access 21, 24, 29, 34, 39, 43, 48
Attempts Before Timeout 11
Auto-Demotion 11

BCD 18
Binary 5
Boolean 18

Channel Assignment 8
Communication Protocol 4
Communications Parameters 12
Communications Timeouts 10
Connect Timeout 10
CPU 12

Data Collection 9
Data Types Description 18
Date 18
Demote on Failure 11
Demotion Period 11

www. ptc.com
88 M itsu b ish i Eth ern et Driver

Discard Requests when Demoted 11

Do Not Scan, Demand Poll Only 10
Double 18
Driver 8
DWord 18

Event Log Messages 50

Extended Registers 29, 34, 39, 43, 48

Failed to synchronize time and date for device. | Retry interval = <number> (minutes). 53
First Word Low 11
Float 18
FX3U Series PLC Setup 57

General 8
GX Developer 12

Help Contents 4

ID 8
Identification 8
Initial Updates from Cache 10
IP Protocol 12
iQ-F Series PLC Setup 80
iQ-R Series PLC Setup 78

www. ptc.com
Mitsubishi Ethernet Driver 89

L Series Built-in Ethernet Port PLC Setup 68

L Series PLC Setup 61
LBCD 18
Long 18

Mitsubishi A Series Address Descriptions 19

Mitsubishi FX3U Series Address Descriptions 22
Mitsubishi iQ-F Series Address Descriptions 40
Mitsubishi iQ-R Series Address Descriptions 35
Mitsubishi L Series Address Descriptions 25
Mitsubishi Q Series Address Descriptions 30
Mitsubishi QnA Series Address Descriptions 44
Model 8
Multi-Level Networks 16

Network 8

Optimizing Your Mitsubishi Ethernet Communications 17

Overview 4

PLC Setup 55
Port 12

Q Series Built-in Ethernet Port PLC Setup 83

Q Series PLC Setup 73
QnA Series PLC Setup 71

www. ptc.com
90 M itsu b ish i Eth ern et Driver

Redundancy 14
Request Timeout 10
Respect Tag-Specified Scan Rate 10

Scan Mode 9
Setup 4
Short 18
Simulated 9
String 18
Supported Communication Parameters 4
Supported Devices 4
Sync Interval 14

TCP/IP 17
Time and Date Synchronization 14
Timeouts to Demote 11

UDP 17
Unable to read from address block on device. | Address block = '<address>' to '<address>'. 52
Unable to read from address block on device. Device returned an error. | Address block = '<address>' to
'<address>', Error code = <code>. 52
Unable to read from address block on device. The device reported an invalid address or an error. |
Address block = '<address>' to '<address>'. 50
Unable to read from address on device. | Address = '<address>'. 53
Unable to read from address on device. Device returned an error. | Address = '<address>', Error code =
<code>. 52
Unable to read from address on device. The device reported an invalid address or an error. | Address =
'<address>'. 51
Unable to read from device. The device returned a PC number error. 50
Unable to write to address on device. Device must be configured to allow writes while in RUN mode. |
Address = '<address>'. 53

www. ptc.com
Mitsubishi Ethernet Driver 91

Unable to write to address on device. Device returned error. | Address = '<address>', Error code =
<code>. 52
Unable to write to address on device. The device reported an invalid address or an error. | Address =
'<address>'. 51
Unable to write to address on device. The device returned a PC number error. | Address =
'<address>'. 50
Unsigned 18

Word 18
Write Full String Length 12

www. ptc.com