Omron Fins Ethernet Manual
Omron Fins Ethernet Manual
Table of Contents
Table of Contents 2
Omron FINS Ethernet Driver Help 4
Overview 4
Channel Setup 5
Device Setup 6
Communications Parameters 9
Run Mode Settings 10
FINS Network Configuration 11
FINS Networks 12
Multihoming 16
Address Descriptions 19
C200H Addressing 19
C500 Addressing 23
C1000H Addressing 26
C2000H Addressing 29
CV500 Addressing 32
CV1000 Addressing 36
CV2000 Addressing 40
CVM1-CPU01 Addressing 45
CVM1-CPU11 Addressing 48
CVM1-CPU21 Addressing 52
CS1 Addressing 56
CJ1 Addressing 61
CJ2 Addressing 64
Error Descriptions 69
Address <address> is out of range for the specified device or register. 70
Data type <type> is not valid for device address <address>. 70
Device address <address> is not supported by model <model name>. 70
Device address <address> is read only. 70
Device address <address> contains a syntax error. 70
Device <device name> access right denied (tag <address>). [Main, Sub: <main code, sub code>]. 70
Device <device name> deactivated due to network settings conflict with device <device name>. 71
Device <device name> responded with a command format error (tag <address>, size <bytes>).
[Main, Sub: <main code, sub code>]. 71
Device <device name> cannot process command (tag <address>, size <bytes>). [Main, Sub: <main
code, sub code>]. 71
Device <device name> cannot accept command (tag <address>, size <bytes>). [Main, Sub: <main
code, sub code>]. 71
Device <device name> responded with a command parameter error (tag <address>, size <bytes>).
[Main, Sub: <main code, sub code>]. 72
www. kepware.com
Omron FINS Ethernet Driver Help 3
Device <device name> responded with local node error. [Main, Sub: <main code, sub code>]. 72
Device <device name> responded with non-fatal CPU unit error. [End code: <end code>]. 72
Device <device name> responded with read not possible (tag <address>, size <bytes>). [Main,
Sub: <main code, sub code>]. 72
Device <device name> responded with error <error code> (tag <address>, size <bytes>). [Main,
Sub: <main code, sub code>]. 72
Device <device name> responded with network relay error. [Net Addr, Node Addr: <network
address, node address>], [Main, Sub: <main code, sub code>], [End code: <end code>]. 73
Device <device name> responded with write not possible (tag <address>, size <bytes>). [Main,
Sub: <main code, sub code>]. 73
Device <device name> responded with destination node error. [Main, Sub: <main code, sub code>]. 73
Device <device name> responded with routing table error. [Main, Sub: <main code, sub code>]. 73
Device <device name> responded with error in unit. [Main, Sub: <main code, sub code>]. 74
Device <device name> responded with fatal CPU unit error. [End code: <end code>]. 74
Device <device name> is not responding. 74
Device <device name> responded with a communications error. [Main, Sub: <main code, sub
code>]. 74
Missing address. 75
The current project was created with an older version of this driver. Examine device properties to
validate network parameters. 75
Unable to write to <address> on device <device name>. 75
Unable to write to register <register address> for device <device name>. The device is in run mode. 76
Unable to bind to adapter: <adapter>. Connect failed. 76
Winsock initialization failed (OS error = n). 76
Winsock V1.1 or higher must be installed to use the Omron FINS Ethernet device driver. 76
Main and Sub Error Codes 77
Remote Network Error 83
Index 84
www. kepware.com
4 Omron FINS Ethernet Driver Help
CONTENTS
Overview
What is the Omron FINS Ethernet Driver?
Device Setup
How do I configure a device for use with this driver?
Address Descriptions
How do I address a data location on an Omron FINS Ethernet device?
Error Descriptions
What error messages does the Omron FINS Ethernet Driver produce?
Overview
The Omron FINS Ethernet Driver provides a reliable way to connect Omron FINS Ethernet controller to OPC client
applications, including HMI, SCADA, Historian, MES, ERP, and countless custom applications.
www. kepware.com
Omron FINS Ethernet Driver Help 5
Channel Setup
Communications Parameters
l Port Number: This parameter specifies the port number that will be used by the devices on the local
Ethernet network. FINS requires that the source and destination port number be the same. The valid
range is 1 to 65535. The default setting is 9600.
Note: Communication to multiple physical devices (with different port numbers configured in the devices) from
the same channel in the OPC server is not allowed. This is because both the port number and adapter are
configured at the channel level.
Important: To communicate to the same device (or multiple physical devices with the same port number
configured in the devices) across multiple OPC server channels, the same port number must be used for each
channel. Each channel, however, must be configured to use a unique network adapter and IP. For more
information, refer to Multihoming.
www. kepware.com
6 Omron FINS Ethernet Driver Help
Device Setup
Supported Devices
This driver supports the FINS protocol via UDP/IP. For a list of models that support the FINS Communications
Service, refer to the manufacturer's website.
Communication Protocol
Omron FINS using UDP/IP.
Device IDs
The Device ID specifies the IP address of the controller that is in direct contact with the host computer. This
controller may not necessarily be the destination device, but instead be a relay device. The destination device is
specified by its FINS network parameters. For all parameters specified in Device Properties (except the Device ID
when a relay device is used) refer to the destination device.
For example, if the host computer has an IP of 111.222.333.123 and the subnet mask is 255.255.255.000, the
source node number should be 123. If the target PLC is configured to use an address table, then the table must
have an entry for the host computer's IP. The node number in this table entry must agree with the source node
number entered for the driver.
Note: When a channel is duplicated using the Copy and Paste commands, the new channel will retain the original
channel's FINS network configuration parameters. Unless the Source Node Number is changed to a unique value,
however, correct data transmission cannot be guaranteed.
Caution: Pay particular attention to the FINS network and node numbers configured for each device, as well as
the IP address calculation method used by the target PLCs. Inconsistent values will result in communications
problems. For example, when using the default Source and Destination Network Address of 0 (Local network),
the Destination Node Number and Source Node Number cannot be the same.
Network Configuration
www. kepware.com
Omron FINS Ethernet Driver Help 7
For optimum reliability, care should be taken to properly isolate all cables and components from electrical noise.
Coaxial cables should have lengths of integral multiples of 2.5 meters up to a maximum of 500 meters.
Depending on the transceiver used, 10BASE-T twisted-pair cable can be substituted for 10BASE5 coax.
Transceiver Cable
All PLC to transceiver cabling should conform to the IEEE802.3 standards, where each of the three signal wire
pairs are individually shielded in addition to an external shield.
www. kepware.com
8 Omron FINS Ethernet Driver Help
www. kepware.com
Omron FINS Ethernet Driver Help 9
Communications Parameters
l Request Size: This parameter specifies the number of bytes that may be requested from a device at one
time. To refine the driver's performance, set the request size to one of the following settings: 32, 64,
128, 256, 512, 1024, or 1984 bytes. The default setting is 512 bytes.
www. kepware.com
10 Omron FINS Ethernet Driver Help
l Writing to CS and TS addresses in Run mode: This parameter specifies the driver's behavior when
the device makes writes while in Run mode. Options include Fail write and log message, Set PLC to Monitor
mode and perform write, and Set PLC to Monitor mode, write, reset to Run. The default setting is Fail write
and log message. Descriptions of the options are as follows:
l Fail write and log message: When selected, this option will fail the write and then post a
message to the Event Log.
l Set PLC to Monitor mode and perform write: When selected, the PLC will be set to Monitor
mode before performing the write.
l Set PLC to Monitor mode, write, reset to Run: When selected, the PLC will be set to Monitor
mode before performing the write. Once complete, the PLC will reset to Run mode.
www. kepware.com
Omron FINS Ethernet Driver Help 11
The default value for network addresses is zero. This is interpreted by FINS as instruction to use the local
network. Actual network numbers can range from 1 to 127. Using zero is convenient if there is only one network
level. When using gateway devices, however, specify the actual network number (1–127) to avoid routing
ambiguities.
l Source Network Address Number: This parameter specifies the address number of the source
network. The default setting is 0.
l Source Node Number: This parameter specifies the number of the source node. The default setting is
the last octet of the network adapter specified in Channel Properties.
l Destination Network Address Number: This parameter specifies the address number of the
destination address. The default setting is 0.
l Destination Node Number: This parameter specifies the number of the destination node. The default
setting is the last octet specified in the Device ID. The correct setting value is obtained from the specific
Omron Ethernet module being accessed.
l Destination Unit Number: This parameter specifies the number of the destination unit. The default
setting is 0. The correct setting value is obtained from the specific Omron Ethernet module being
accessed.
Tip: Many Omron Ethernet modules have rotary switches for setting the Destination Node Number. Generally
there are two node number switches: x16 and x1. The switches can be difficult to read due to their small size and
because the arrow can appear to fall between numbers. It may be necessary to try several Destination Node
Numbers to confirm the correct one. For example; on the x16 switch, the arrow may appear between 9 and A
and, on the x1 switch, the arrow may appear between 2 and 3. The correct Destination Node Number is one of the
following numbers: 163 (for hex A3), 162 (for hex A2), 147 (for hex 93), or 146 (for hex 92).
Note: Misconfiguration of the network, in combination with some errors, can cause a Remote Network Error.
www. kepware.com
12 Omron FINS Ethernet Driver Help
FINS Networks
The FINS communications service was developed by Omron to provide a consistent way for PLCs and computers
on various networks to communicate. Compatible network types include Ethernet, Host Link, Controller Link,
SYSMAC LINK, SYSMAC WAY, and Toolbus. FINS allows communications between nodes up to three network
levels. A direct connection between a computer and a PLC via Host Link is not considered a network level.
The diagram below shows a FINS network comprised of interconnected Ethernet and Controller Link networks,
and will serve as an example for the following discussion. FINS allows communication between any pair of devices
in the diagram. PLC 1 acts as a gateway between the two networks. The host PC sends a data request command
(shown in red) to PLC 3 via PLC 1. The response is shown in blue.
Note: In principle, PLC 3 or 4 could act as a gateway to a third network layer that could also be reached by the
host PC.
FINS Messages
FINS messages contain two parts: a header and a data portion. The header contains source and destination
information, among other things. The data portion contains command codes and optional command parameters.
The six source and destination parameters contained in the header are as follows:
This driver will always set DA2 and SA2 to zero; meaning, communication will be between the host computer and
the destination node's CPU module.
Ethernet Communications
This driver is able to communicate with any FINS compatible device on an Ethernet network. The FINS device can
process a given FINS command if it is the destination node or relay the message to another device if it is not. In
the figure above, it is desired to send a data request from the host PC to PLC 3. The driver constructs a FINS
message with appropriate source and destination parameters set in the header, encapsulates that message in a
UDP/IP datagram, and then sends it off to PLC 1. The message cannot be sent directly to PLC 3 because it is not
on the same network as the PC. PLC 1 examines the FINS message header and determines that node 1 on network
www. kepware.com
Omron FINS Ethernet Driver Help 13
2 (which is PLC 3) is the intended destination. PLC 1 relays the FINS message to PLC 3. Since PLC 3 is not on an
Ethernet network, the UDP/IP wrapper is removed. PLC 3 then sends its reply back to the host PC via PLC 1.
A problem arises when PLC 1 must forward the reply from PLC 3 to the host PC. The reply from PLC 3 addresses
the destination using FINS network parameters only: it does not explicitly give the destination IP address. Omron
has devised three methods for a PLC to determine destination IPs from FINS network parameters. The method is
chosen when the PLC is configured and will determine what node numbers should be assigned to each device on
the Ethernet network. The three methods are Automatic Address Generation, IP Address Table, and Combined
Address Conversion. Descriptions of the methods are as follows:
l Automatic Address Generation: This method uses the relay device to construct the destination IP from
its own IP, the subnet mask, and the FINS destination node number. IP addresses are made up of two
parts: the network number (which is the same for all nodes on the local network) and the host number
(which is unique to each node on the local network). The Automatic Address Generation method requires
that the host number portion of each node's IP be the same as its FINS node number.
Note: In this example, PLC 1 would calculate the network number by first performing a logical AND
operation between its own IP address and subnet mask. In Boolean algebra terms, 130.25.36.2 AND
255.255.255.0 equals 130.25.36.0. The destination IP would then be calculated by adding the FINS
destination node number to the network number. For the Destination IP, 130.25.36.0 + 1 = 130.25.36.1.
l IP Address Table: This method uses an IP address table, which is a list of FINS node numbers and their
associated IP addresses. In this method, the host number portion of the IP address does not need to be
the same as the FINS node number. If used, the IP address tables must be programmed into the PLCs on
the Ethernet networks.
l Combined Address Conversion: This method uses a device to look up the FINS destination node
number in its IP address table. If the node number is found, the corresponding IP address will be taken
from the table and used to construct the UDP/IP datagram. If the node number is not found, the
destination IP will be computed using the Automatic Address Generation method.
Note: PLC 1 also needs to know on what port the host PC is listening. Since FINS requires that all nodes on an
Ethernet network listen on the same port number, the PLC will use the port number on which it has been
configured to listen.
1. To start, create a channel that uses this driver to communicate with devices on the Ethernet network.
FINS requires that all nodes on an Ethernet network use the same port number to send and receive data.
For this example, use the default value 9600.
2. Next, create a device on that channel that represents the destination node. For this example, use PLC 3.
3. Set the Device ID, which must be the IP address of the PLC with which the driver will be in direct
communication. For this example, use PLC 1 (130.25.36.2).
Note: The Device ID should be the IP address of the destination device if that device is on the host PC's
local Ethernet network. This would be the case with PLC 2.
4. Next, set the FINS network parameters to identify the source (host PC ) and destination (PLC 3). In this
example, the settings are as follows:
*The default value for network addresses is zero. This is interpreted by FINS as instruction to use the
local network. Actual network numbers can range from 1 to 127. Using zero is convenient if there is only
one network level. When using gateway devices, however, specify the actual network number (1–127) to
avoid routing ambiguities.
Notes:
www. kepware.com
14 Omron FINS Ethernet Driver Help
Routing Tables
With multi-level networks, additional information must be programmed into the PLCs so they can send messages
to other nodes in the system. This is accomplished using FINS routing tables, which come in two types: Local and
Remote. Local routing tables associate a network number with one of the communication modules or Special
Input/Output Units (SIOU) installed in the PLC's rack. Remote routing tables give directions on how to reach one
of the next network levels. The routing tables for the given example would appear as shown below.
PLC 1 (Local)
Network Number Unit
1 2
2 1
There are two local networks for PLC 1. The Ethernet and Controller Link network numbers are assigned as 1 and
2, respectively. The Ethernet and Controller Link modules are assigned unit numbers 2 and 1, respectively. The
network node number of each of these modules is configured by the user and must be unique within its
associated network.
Note: Both of the communications modules in PLC 1 node 10 could have been called since they are on different
networks. There are no remote networks for PLC 1.
PLC 2 (Local)
Network Number Unit
1 1
PLC 2 has only one communications module: the Ethernet module, and only one entry in its local routing table.
PLC 2 (Remote)
Remote Network Number Relay Network Relay Node
2 1 2
Network 2 is a remote network for PLC 2. To send a message to a node on network 2, PLC 2 must send that
message to a relay node (the gateway) on one of its local networks. This local network is called the relay network
and must be network 1 in the given example. The Ethernet module in the gateway (PLC 1) is node number 2.
Therefore, the relay node for PLC 2 is 2.
Likewise, routing tables for PLC 3 and 4 must appear like the following. They happen to be the same in the given
example because the Controller Link modules in both PLCs are unit number 1. These modules must be assigned
node numbers that are unique in network 2.
Duplicate Devices
It is generally recommended that the communications load be distributed over multiple channels. Significant
performance gains can be achieved since the Windows operation system allows each channel to operate on an
independent thread. The idea is to have as few devices on each channel as possible, so that no one device can
significantly impact the update rate of the others. For more information, refer to Optimizing Your Omron FINS
Ethernet Communications.
www. kepware.com
Omron FINS Ethernet Driver Help 15
Although it is not usually advantageous to create multiple server device objects that communicate with a single
physical device, it is necessary to do so when using a multi-level FINS network. In the example above, device
objects are needed for PLC 3 and PLC 4. The driver will actually be in direct communications with PLC 1. This
means that the device number configured for both device objects must be the IP address of PLC 1. With most
Ethernet drivers, this sort of thing is perfectly safe. Because FINS requires that all nodes on an Ethernet network
use the same port number to send and receive data, however, a problem arises.
If the device objects for PLC 3 and 4 were created on the same channel, everything will work fine. Users will
encounter the problem when attempting to improve performance by placing the device objects on separate
channels. It is important to know that this driver will give each one of these channels an Ethernet
communications socket. For example, if the host PC has only one IP associated with it, then both of these sockets
must use that IP as its source address and both of these sockets will need to use the same port number according
to the FINS protocol. If the driver allowed users to do this, the UDP/IP datagrams from PLC 1 would contain the
same source and destination address information (where source is 130.25.36.2/9600 and destination is
130.25.36.1/9600) regardless of the intended destination device object. Users cannot be guaranteed that the
operating system will send the datagrams to the correct socket if both happen to be waiting for responses from
PLC 3 and 4. The only way to remove the ambiguity is to associate each channel/socket with a unique IP address.
To associate a unique IP address with each channel, users must multihome the host computer. This means that
the computer must have multiple NICs installed or users must associate multiple IP addresses with a single NIC.
Things will work if both devices are on the same channel because all transactions are carried out serially on a
given channel. It doesn't matter if the source and destination addresses (IP/port) in responses from PLC 3 and 4
look the same because the socket will be waiting for a response from only one PLC at a time. This is only relevant
when multi-level FINS networks are being used.
Caution: Pay particular attention to the FINS network and node numbers configured for each device, as well as
the IP address calculation method being used by the target PLCs. Inconsistent values will result in
communications problems.
www. kepware.com
16 Omron FINS Ethernet Driver Help
Multihoming
Some applications require users to associate a unique IP address with each channel. In these cases, the host
computer must be multihomed; meaning, it must be configured to have more than one IP address. This may be
accomplished by installing multiple Network Adapter Cards (NIC) in the computer or by assigning multiple IP
addresses to a single NIC.
6. Click OK.
2. Click Local Area Connection (or any other icon associated with the NIC of interest).
7. Click OK.
2. Next, click Control Panel | Network and Internet. Then, select the connection that will be changed
(such as the Local Area Connection).
3. Click Properties, and then provide the administrator password or confirmation (if prompted).
4. Select the Networking tab. Beneath This connection uses the following items, click Internet
Protocol Version 4 (TCP/IPv4).
5. Next, click Properties. Ensure that the connection is set to use an IP address by clicking Use the
following IP address.
6. Next, specify the IP address settings in the IP Address, Subnet Mask, and Default Gateway fields.
7. To add a second IP address, click Advanced | IP Settings. Beneath IP Address, click Add. Then, enter
a new IP address and subnet mask.
Note 1: Windows NT can add up to five IP addresses for each NIC via the control panel. More IP addresses can
be added to the registry manually as necessary. To browse, look under HEKY_LOCAL_MACHINE | SYSTEM |
CurrentControlSet | Services. Then, select the service associated with the adapter card in question. Under
the service, go to the Parameters | TCPIP subkey. Add the IP addresses to IPAddress and then edit
SubnetMask and add an entry for each new IP address.
Note 2: There will be additional operating system overhead when running on a multihomed system. Unless
users are using very fast devices, this overhead should not entirely cancel out the performance gain achieved
from distributing the communications load over multiple channels.
www. kepware.com
Omron FINS Ethernet Driver Help 17
The server refers to communications protocols like Omron FINS Ethernet 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 Omron FINS
Ethernet controller from which data will be collected. While this approach to defining the application will provide
a high level of performance, it won't take full advantage of the Omron FINS Ethernet Driver or the network. An
example of how the application may appear when configured using a single channel is shown below.
Each device appears under a single Omron FINS Ethernet channel. In this
configuration, 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 suffer.
If the Omron FINS Ethernet Driver could only define one single channel, then the example shown above would be
the only option available; however, the Omron FINS Ethernet Driver can define up to 512 channels. Using
multiple channels distributes 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 512 or fewer
devices, it can be optimized exactly how it is shown here.
The performance will improve even if the application has more than 512
devices. While 512 or fewer devices may be ideal, the application will still
benefit from additional channels. Although by spreading the device load
across all channels will cause the server to move from device to device
again, it can now do so with far less devices to process on a single channel.
The Device Request Size parameter can also affect the Omron FINS Ethernet Driver's performance. The request
size refers to the number of bytes that may be requested from a device at one time. If data is being read from a
large number of contiguous addresses, it may be advantageous to use a large request size. To refine the
performance of this driver, the request size may be configured from 32 to 512 bytes for each device.
Important: If using a multi-leveled FINS network, multiple device objects may need to be created in the server
that will all be in direct communication with the same gateway PLC. Since FINS requires all nodes on an Ethernet
network to use the same port number to send and receive data, this driver must impose some constraints that
become relevant when distributing the communications load over multiple channels. For more information, refer
to Channel Setup.
www. kepware.com
18 Omron FINS Ethernet Driver Help
Value range is 0-9999. Behavior is undefined for values beyond this range.
LBCD Four byte packed BCD
Value range is 0-99999999. Behavior is undefined for values beyond this range.
String Null terminated ASCII string.
Support includes string lengths up to 512 characters, and selection of HiLo byte order,
LoHi byte order, Only High byte and Only Low byte.
www. kepware.com
Omron FINS Ethernet Driver Help 19
Address Descriptions
Address specifications vary depending on the model in use. Select a link from the following list to obtain specific
address information for the model of interest.
C200H Addressing
C500 Addressing
C1000H Addressing
C2000H Addressing
CV500 Addressing
CV1000 Addressing
CV2000 Addressing
CVM1-CPU01 Addressing
CVM1-CPU11 Addressing
CVM1-CPU21 Addressing
CS1 Addressing
CJ1 Addressing
CJ2 Addressing
C200H Addressing
The default data types for dynamically defined tags are shown in bold. For more information, refer below the
table for notes and restrictions on BCD Support, String Support, and Array Support.
www. kepware.com
20 Omron FINS Ethernet Driver Help
www. kepware.com
Omron FINS Ethernet Driver Help 21
www. kepware.com
22 Omron FINS Ethernet Driver Help
BCD Support
16-bit and 32-bit data can be referenced as signed and unsigned BCD values.
Unsigned BCD support is accomplished by appending a 'D' to any Word or DWord tag address or by using the
BCD and LBCD data types. The value range is as follows:
Signed BCD support is accomplished by appending a 'D' to any Short or Long tag address. The most significant
bit of the Short/Long is set to 1 for negative values, 0 for positive values. The value range is as follows:
Example
IR0D @ Short = -50
IR0D @ Word = 8050 (MSB set)
IR0 @ BCD = 8050
IR0D @ Short = 50
IR0D @ Word = 50
IR0 @ BCD = 50
Note: Boolean, Float, and String data types do not support appending 'D' to the tag address. Furthermore, 'D'
cannot be appended to BCD or LBCD tags, or tags with a default data type of BCD or LBCD (such as Counter and
Timer tags).
String Support
The C200H model supports reading and writing numerous device types as an ASCII string. When using data
memory for string data, each register will contain two bytes (two characters) of ASCII data. The order of the
ASCII data within a given register can be selected when the string is defined. The length of the string can be from
2 to 512 characters and is entered in place of a bit number. The string length cannot exceed the request size that
has been assigned to the device up to a request size of 512. For request size values greater than 512, string
length cannot exceed 512. The length must be entered as an even number. The range of registers spanned by
the string cannot exceed the range of the device type. The byte order is specified by appending either a "H" or "L"
to the address.
When using one byte of ASCII data per register, the length of the string can be from 1 to 256 characters and is
entered in place of a bit number. The string length times 2 cannot exceed the request size that has been
assigned to the device up to a request size of 512. For request size values greater than 512, string length cannot
exceed 256. The range of registers spanned by the string cannot exceed the range of the device type. The byte to
use within a register is specified by appending either a "D" or "E" to the address. For more information, refer to
Device Setup.
Examples
1. To address a string starting at DM1000 with a length of 100 bytes and HiLo byte order, enter:
DM1000.100H
2. To address a string starting at DM1100 with a length of 78 bytes and LoHi byte order, enter:
DM1100.078L
3. To address a string starting at DM2000 with a length of 55 bytes and Only the High Order byte, enter:
DM2000.055D
4. To address a string starting at DM2200 with a length of 37 bytes and Only the Low Order byte, enter:
DM2200.037E
Array Support
www. kepware.com
Omron FINS Ethernet Driver Help 23
Arrays are supported for all data types except Boolean. There are two methods of addressing an array. Examples
are given using data memory locations.
Rows multiplied by cols multiplied by data size in bytes (2 for Word, Short, and BCD; 4 for DWord, Long, LBCD,
and Float) cannot exceed the request size that has been assigned to the device. For example, a 10 X 10 array of
words results in an array size of 200 bytes, which would require a request size of at least 256.
Note: Use caution when modifying 32-bit values (DWord, Long, LBCD, and Float). Each address for which these
data types are allowed starts at a word offset within the device. DWords DM0 and DM1 overlap at word DM1.
Writing to DM0 will also modify the value held in DM1. It is recommended that users utilize these data types so
that overlapping does not occur. For example, when using DWords, users may want to use DM0, DM2, DM4, and
so on to prevent overlapping Words.
C500 Addressing
The default data types for dynamically defined tags are shown in bold. For more information, refer below the
table for notes and restrictions on BCD Support, String Support, and Array Support.
www. kepware.com
24 Omron FINS Ethernet Driver Help
www. kepware.com
Omron FINS Ethernet Driver Help 25
BCD Support
16-bit and 32-bit data can be referenced as signed and unsigned BCD values.
Unsigned BCD support is accomplished by appending a 'D' to any Word or DWord tag address or by using the
BCD and LBCD data types. The value range is as follows:
Signed BCD support is accomplished by appending a 'D' to any Short or Long tag address. The most significant
bit of the Short/Long is set to 1 for negative values, 0 for positive values. The value range is as follows:
Example
IR0D @ Short = -50
IR0D @ Word = 8050 (MSB set)
IR0 @ BCD = 8050
IR0D @ Short = 50
IR0D @ Word = 50
IR0 @ BCD = 50
Note: Boolean, Float, and String data types do not support appending 'D' to the tag address. Furthermore, 'D'
cannot be appended to BCD or LBCD tags, or tags with a default data type of BCD or LBCD (such as Counter and
Timer tags).
String Support
The C500 model supports reading and writing numerous device types as an ASCII string. When using data
memory for string data, each register will contain two bytes (two characters) of ASCII data. The order of the
ASCII data within a given register can be selected when the string is defined. The length of the string can be from
2 to 512 characters and is entered in place of a bit number.The string length cannot exceed the request size that
has been assigned to the device up to a request size of 512. For request size values greater than 512, string
length cannot exceed 512. The length must be entered as an even number. The range of registers spanned by
the string cannot exceed the range of the device type. The byte order is specified by appending either a "H" or "L"
to the address.
When using one byte of ASCII data per register, the length of the string can be from 1 to 256 characters and is
entered in place of a bit number. The string length times 2 cannot exceed the request size that has been
assigned to the device up to a request size of 512. For request size values greater than 512, string length cannot
exceed 256. The range of registers spanned by the string cannot exceed the range of the device type. The byte to
use within a register is specified by appending either a "D" or "E" to the address. For more information, refer to
Device Setup.
Examples
1. To address a string starting at DM100 with a length of 100 bytes and HiLo byte order, enter:
DM100.100H
2. To address a string starting at DM110 with a length of 78 bytes and LoHi byte order, enter:
DM110.078L
3. To address a string starting at DM200 with a length of 55 bytes and Only the High Order byte, enter:
DM200.055D
4. To address a string starting at DM220 with a length of 37 bytes and Only the Low Order byte, enter:
DM220.037E
Array Support
Arrays are supported for all data types except Boolean. There are two methods of addressing an array. Examples
are given using data memory locations.
www. kepware.com
26 Omron FINS Ethernet Driver Help
Rows multiplied by cols multiplied by data size in bytes (2 for Word, Short, and BCD; 4 for DWord, Long, LBCD,
and Float) cannot exceed the request size that has been assigned to the device. For example, a 10 X 10 array of
words results in an array size of 200 bytes, which would require a request size of at least 256.
Note: Use caution when modifying 32-bit values (DWord, Long, LBCD, and Float). Each address for which these
data types are allowed starts at a word offset within the device. DWords DM0 and DM1 overlap at word DM1.
Writing to DM0 will also modify the value held in DM1. It is recommended that users utilize these data types so
that overlapping does not occur. For example, when using DWords, use DM0, DM2, DM4, and so on to prevent
overlapping Words.
C1000H Addressing
The default data types for dynamically defined tags are shown in bold. For more information, refer below the
table for notes and restrictions on BCD Support, String Support, and Array Support.
www. kepware.com
Omron FINS Ethernet Driver Help 27
www. kepware.com
28 Omron FINS Ethernet Driver Help
BCD Support
16-bit and 32-bit data can be referenced as signed and unsigned BCD values. Unsigned BCD support is
accomplished by appending a 'D' to any Word or DWord tag address or by using the BCD and LBCD data types.
The value range is as follows:
Signed BCD support is accomplished by appending a 'D' to any Short or Long tag address. The most significant
bit of the Short/Long is set to 1 for negative values, 0 for positive values. The value range is as follows:
Example:
IR0D @ Short = -50
IR0D @ Word = 8050 (MSB set)
IR0 @ BCD = 8050
IR0D @ Short = 50
IR0D @ Word = 50
IR0 @ BCD = 50
Note: Boolean, Float, and String data types do not support appending 'D' to the tag address. Furthermore, 'D'
cannot be appended to BCD or LBCD tags, or tags with a default data type of BCD or LBCD (such as Counter and
Timer tags).
String Support
The C1000H model supports reading and writing numerous device types as an ASCII string. When using data
memory for string data, each register will contain two bytes (two characters) of ASCII data. The order of the
ASCII data within a given register can be selected when the string is defined. The length of the string can be from
2 to 512 characters and is entered in place of a bit number. The string length cannot exceed the request size that
has been assigned to the device up to a request size of 512. For request size values greater than 512, string
length cannot exceed 512. The length must be entered as an even number. The range of registers spanned by
the string cannot exceed the range of the device type. The byte order is specified by appending either a "H" or "L"
to the address.
When using one byte of ASCII data per register, the length of the string can be from 1 to 256 characters and is
entered in place of a bit number. The string length times 2 cannot exceed the request size that has been
assigned to the device up to a request size of 512. For request size values greater than 512, string length cannot
exceed 256. The range of registers spanned by the string cannot exceed the range of the device type. The byte to
www. kepware.com
Omron FINS Ethernet Driver Help 29
use within a register is specified by appending either a "D" or "E" to the address. For more information, refer to
Device Setup.
Examples
1. To address a string starting at DM1000 with a length of 100 bytes and HiLo byte order, enter:
DM1000.100H
2. To address a string starting at DM1100 with a length of 78 bytes and LoHi byte order, enter:
DM1100.078L
3. To address a string starting at DM2000 with a length of 55 bytes and Only the High Order byte, enter:
DM2000.055D
4. To address a string starting at DM2200 with a length of 37 bytes and Only the Low Order byte, enter:
DM2200.037E
Array Support
Arrays are supported for all data types except Boolean. There are two methods of addressing an array. Examples
are given using data memory locations.
Rows multiplied by cols multiplied by data size in bytes (2 for Word, Short, and BCD; 4 for DWord, Long, LBCD,
and Float) cannot exceed the request size that has been assigned to the device. For example, a 10 X 10 array of
words results in an array size of 200 bytes, which would require a request size of at least 256.
Note: Use caution when modifying 32-bit values (DWord, Long, LBCD, and Float). Each address for which these
data types are allowed starts at a word offset within the device. DWords DM0 and DM1 overlap at word DM1.
Writing to DM0 will also modify the value held in DM1. It is recommended that users utilize these data types so
that overlapping does not occur. For example, when using DWords, use DM0, DM2, DM4, and so on, to prevent
overlapping Words.
C2000H Addressing
The default data types for dynamically defined tags are shown in bold. For more information, refer below the
table for notes and restrictions on BCD Support, String Support, and Array Support.
www. kepware.com
30 Omron FINS Ethernet Driver Help
www. kepware.com
Omron FINS Ethernet Driver Help 31
BCD Support
16-bit and 32-bit data can be referenced as signed and unsigned BCD values. Unsigned BCD support is
accomplished by appending a 'D' to any Word or DWord tag address or by using the BCD and LBCD data types.
The value range is as follows:
Signed BCD support is accomplished by appending a 'D' to any Short or Long tag address. The most significant
bit of the Short/Long is set to 1 for negative values, 0 for positive values. The value range is as follows:
Example
IR0D @ Short = -50
IR0D @ Word = 8050 (MSB set)
IR0 @ BCD = 8050
IR0D @ Short = 50
IR0D @ Word = 50
IR0 @ BCD = 50
www. kepware.com
32 Omron FINS Ethernet Driver Help
Note: Boolean, Float, and String data types do not support appending 'D' to the tag address. Furthermore, 'D'
cannot be appended to BCD or LBCD tags, or tags with a default data type of BCD or LBCD (such as Counter and
Timer tags).
String Support
The C2000H model supports reading and writing numerous device types as an ASCII string. When using data
memory for string data, each register will contain two bytes (two characters) of ASCII data. The order of the
ASCII data within a given register can be selected when the string is defined. The length of the string can be from
2 to 512 characters and is entered in place of a bit number. The string length cannot exceed the request size that
has been assigned to the device up to a request size of 512. For request size values greater than 512, string
length cannot exceed 512. The length must be entered as an even number. The range of registers spanned by
the string cannot exceed the range of the device type. The byte order is specified by appending either a "H" or "L"
to the address.
When using one byte of ASCII data per register, the length of the string can be from 1 to 256 characters and is
entered in place of a bit number. The string length times 2 cannot exceed the request size that has been
assigned to the device up to a request size of 512. For request size values greater than 512, string length cannot
exceed 256. The range of registers spanned by the string cannot exceed the range of the device type. The byte to
use within a register is specified by appending either a "D" or "E" to the address. For more information, refer to
Device Setup.
Examples
1. To address a string starting at DM1000 with a length of 100 bytes and HiLo byte order, enter:
DM1000.100H
2. To address a string starting at DM1100 with a length of 78 bytes and LoHi byte order, enter:
DM1100.078L
3. To address a string starting at DM2000 with a length of 55 bytes and Only the High Order byte, enter:
DM2000.055D
4. To address a string starting at DM2200 with a length of 37 bytes and Only the Low Order byte, enter:
DM2200.037E
Array Support
Arrays are supported for all data types except Boolean. There are two methods of addressing an array. Examples
are given using data memory locations.
Rows multiplied by cols multiplied by data size in bytes (2 for Word, Short, and BCD; 4 for DWord, Long, LBCD,
and Float) cannot exceed the request size that has been assigned to the device. For example, a 10 X 10 array of
words results in an array size of 200 bytes, which would require a request size of at least 256.
Note: Use caution when modifying 32-bit values (DWord, Long, LBCD, and Float). Each address for which these
data types are allowed starts at a word offset within the device. DWords DM0 and DM1 overlap at word DM1.
Writing to DM0 will also modify the value held in DM1. It is recommended that users utilize these data types so
that overlapping does not occur. For example, when using DWords, use DM0, DM2, DM4, and so on to prevent
overlapping Words.
CV500 Addressing
The default data types for dynamically defined tags are shown in bold. For more information, refer below the
table for notes and restrictions on BCD Support, String Support, and Array Support.
www. kepware.com
Omron FINS Ethernet Driver Help 33
www. kepware.com
34 Omron FINS Ethernet Driver Help
www. kepware.com
Omron FINS Ethernet Driver Help 35
BCD Support
16-bit and 32-bit data can be referenced as signed and unsigned BCD values.
Unsigned BCD support is accomplished by appending a 'D' to any Word or DWord tag address or by using the
BCD and LBCD data types. The value range is as follows:
Signed BCD support is accomplished by appending a 'D' to any Short or Long tag address. The most significant
bit of the Short/Long is set to 1 for negative values, 0 for positive values. The value range is as follows:
Example
IR0D @ Short = -50
IR0D @ Word = 8050 (MSB set)
IR0 @ BCD = 8050
IR0D @ Short = 50
IR0D @ Word = 50
IR0 @ BCD = 50
Note: Boolean, Float, and String data types do not support appending 'D' to the tag address. Furthermore, 'D'
cannot be appended to BCD or LBCD tags, or tags with a default data type of BCD or LBCD (such as Counter and
Timer tags).
String Support
The CV500 model supports reading and writing numerous device types as an ASCII string. When using data
memory for string data, each register will contain two bytes (two characters) of ASCII data. The order of the
ASCII data within a given register can be selected when the string is defined. The length of the string can be from
2 to 512 characters and is entered in place of a bit number. The string length cannot exceed the request size that
has been assigned to the device up to a request size of 512. For request size values greater than 512, string
length cannot exceed 512. The length must be entered as an even number. The range of registers spanned by
the string cannot exceed the range of the device type. The byte order is specified by appending either a "H" or "L"
to the address.
When using one byte of ASCII data per register, the length of the string can be from 1 to 256 characters and is
entered in place of a bit number. The string length times 2 cannot exceed the request size that has been
assigned to the device up to a request size of 512. For request size values greater than 512, string length cannot
exceed 256. The range of registers spanned by the string cannot exceed the range of the device type. The byte to
use within a register is specified by appending either a "D" or "E" to the address. For more information, refer to
Device Setup.
Examples
www. kepware.com
36 Omron FINS Ethernet Driver Help
1. To address a string starting at D1000 with a length of 100 bytes and HiLo byte order, enter:
D1000.100H
2. To address a string starting at D1100 with a length of 78 bytes and LoHi byte order, enter: D1100.078L
3. To address a string starting at D2000 with a length of 55 bytes and Only the High Order byte, enter:
D2000.055D
4. To address a string starting at D2200 with a length of 37 bytes and Only the Low Order byte, enter:
D2200.037E
Array Support
Arrays are supported for all data types except Boolean, Data Register, Index Register, and Step Timer. There are
two methods of addressing an array. Examples are given using data memory locations.
Rows multiplied by cols multiplied by data size in bytes (2 for Word, Short, and BCD; 4 for DWord, Long, LBCD,
and Float) cannot exceed the request size that has been assigned to the device. For example, a 10 X 10 array of
words results in an array size of 200 bytes, which would require a request size of at least 256.
Note: Use caution when modifying 32-bit values (DWord, Long, LBCD, and Float). Each address for which these
data types are allowed starts at a word offset within the device. DWords DM0 and DM1 overlap at word DM1.
Writing to DM0 will also modify the value held in DM1. It is recommended that users utilize these data types so
that overlapping does not occur. For example, when using DWords, use DM0, DM2, DM4, and so on to prevent
overlapping Words.
CV1000 Addressing
The default data types for dynamically defined tags are shown in bold. For more information, refer below the
table for notes and restrictions on BCD Support, String Support, and Array Support.
www. kepware.com
Omron FINS Ethernet Driver Help 37
www. kepware.com
38 Omron FINS Ethernet Driver Help
www. kepware.com
Omron FINS Ethernet Driver Help 39
BCD Support
16-bit and 32-bit data can be referenced as signed and unsigned BCD values. Unsigned BCD support is
accomplished by appending a 'D' to any Word or DWord tag address or by using the BCD and LBCD data types.
The value range is as follows:
Signed BCD support is accomplished by appending a 'D' to any Short or Long tag address. The most significant
bit of the Short/Long is set to 1 for negative values, 0 for positive values. The value range is as follows:
Example
IR0D @ Short = -50
IR0D @ Word = 8050 (MSB set)
IR0 @ BCD = 8050
IR0D @ Short = 50
www. kepware.com
40 Omron FINS Ethernet Driver Help
IR0D @ Word = 50
IR0 @ BCD = 50
Note: Boolean, Float, and String data types do not support appending 'D' to the tag address. Furthermore, 'D'
cannot be appended to BCD or LBCD tags, or tags with a default data type of BCD or LBCD (such as Counter and
Timer tags).
String Support
The CV1000 model supports reading and writing numerous device types as an ASCII string. When using data
memory for string data, each register will contain two bytes (two characters) of ASCII data. The order of the
ASCII data within a given register can be selected when the string is defined. The length of the string can be from
2 to 512 characters and is entered in place of a bit number. The string length cannot exceed the request size that
has been assigned to the device up to a request size of 512. For request size values greater than 512, string
length cannot exceed 512. The length must be entered as an even number. The range of registers spanned by
the string cannot exceed the range of the device type. The byte order is specified by appending either a "H" or "L"
to the address.
When using one byte of ASCII data per register, the length of the string can be from 1 to 256 characters and is
entered in place of a bit number. The string length times 2 cannot exceed the request size that has been
assigned to the device up to a request size of 512. For request size values greater than 512, string length cannot
exceed 256. The range of registers spanned by the string cannot exceed the range of the device type. The byte to
use within a register is specified by appending either a "D" or "E" to the address. For more information, refer to
Device Setup.
Examples
1. To address a string starting at D01000 with a length of 100 bytes and HiLo byte order, enter:
D01000.100H
2. To address a string starting at D01100 with a length of 78 bytes and LoHi byte order, enter:
D01100.078L
3. To address a string starting at D02000 with a length of 55 bytes and Only the High Order byte, enter:
D02000.055D
4. To address a string starting at D02200 with a length of 37 bytes and Only the Low Order byte, enter:
D02200.037E
Array Support
Arrays are supported for all data types except Boolean, Data Register, Index Register, and Step Timer. There are
two methods of addressing an array. Examples are given using data memory locations.
Rows multiplied by cols multiplied by data size in bytes (2 for Word, Short, and BCD; 4 for DWord, Long, LBCD,
and Float) cannot exceed the request size that has been assigned to the device. For example, a 10 X 10 array of
words results in an array size of 200 bytes, which would require a request size of at least 256.
Note: Use caution when modifying 32-bit values (DWord, Long, LBCD, and Float). Each address for which these
data types are allowed starts at a word offset within the device. DWords D0 and D1 overlap at word D1. Writing to
D0 will also modify the value held in D1. It is recommended that users utilize these data types so that overlapping
does not occur. For example, when using DWords, use D0, D2, D4, and so on to prevent overlapping Words.
CV2000 Addressing
The default data types for dynamically defined tags are shown in bold. For more information, refer below the
table for notes and restrictions on BCD Support, String Support, and Array Support.
www. kepware.com
Omron FINS Ethernet Driver Help 41
www. kepware.com
42 Omron FINS Ethernet Driver Help
www. kepware.com
Omron FINS Ethernet Driver Help 43
BCD Support
16-bit and 32-bit data can be referenced as signed and unsigned BCD values.
www. kepware.com
44 Omron FINS Ethernet Driver Help
Unsigned BCD support is accomplished by appending a 'D' to any Word or DWord tag address or by using the
BCD and LBCD data types. The value range is as follows:
Signed BCD support is accomplished by appending a 'D' to any Short or Long tag address. The most significant
bit of the Short/Long is set to 1 for negative values, 0 for positive values. The value range is as follows:
Example
IR0D @ Short = -50
IR0D @ Word = 8050 (MSB set)
IR0 @ BCD = 8050
IR0D @ Short = 50
IR0D @ Word = 50
IR0 @ BCD = 50
Note: Boolean, Float, and String data types do not support appending 'D' to the tag address. Furthermore, 'D'
cannot be appended to BCD or LBCD tags, or tags with a default data type of BCD or LBCD (such as Counter and
Timer tags).
String Support
The CV2000 model supports reading and writing numerous device types as an ASCII string. When using data
memory for string data, each register will contain two bytes (two characters) of ASCII data. The order of the
ASCII data within a given register can be selected when the string is defined. The length of the string can be from
2 to 512 characters and is entered in place of a bit number. The string length cannot exceed the request size that
has been assigned to the device up to a request size of 512. For request size values greater than 512, string
length cannot exceed 512. The length must be entered as an even number. The range of registers spanned by
the string cannot exceed the range of the device type. The byte order is specified by appending either a "H" or "L"
to the address.
When using one byte of ASCII data per register, the length of the string can be from 1 to 256 characters and is
entered in place of a bit number. The string length times 2 cannot exceed the request size that has been
assigned to the device up to a request size of 512. For request size values greater than 512, string length cannot
exceed 256. The range of registers spanned by the string cannot exceed the range of the device type. The byte to
use within a register is specified by appending either a "D" or "E" to the address. For more information, refer to
Device Setup.
Examples
1. To address a string starting at D01000 with a length of 100 bytes and HiLo byte order, enter:
D01000.100H
2. To address a string starting at D01100 with a length of 78 bytes and LoHi byte order, enter:
D01100.078L
3. To address a string starting at D02000 with a length of 55 bytes and Only the High Order byte, enter:
D02000.055D
4. To address a string starting at D02200 with a length of 37 bytes and Only the Low Order byte, enter:
D02200.037E
Array Support
Arrays are supported for all data types except Boolean, Data Register, Index Register, and Step Timer. There are
two methods of addressing an array. Examples are given using data memory locations.
www. kepware.com
Omron FINS Ethernet Driver Help 45
Dxxxx [cols]*
Rows multiplied by cols multiplied by data size in bytes (2 for Word, Short, and BCD; 4 for DWord, Long, LBCD,
and Float) cannot exceed the request size that has been assigned to the device. For example, a 10 X 10 array of
words results in an array size of 200 bytes, which would require a request size of at least 256.
Note: Use caution when modifying 32-bit values (DWord, Long, LBCD, and Float). Each address for which these
data types are allowed starts at a word offset within the device. DWords D0 and D1 overlap at word D1. Writing to
D0 will also modify the value held in D1. It is recommended that users utilize these data types so that overlapping
does not occur. For example, when using DWords, use D0, D2, D4, and so on to prevent overlapping Words.
CVM1-CPU01 Addressing
The default data types for dynamically defined tags are shown in bold. For more information, refer below the
table for notes and restrictions on BCD Support, String Support, and Array Support.
www. kepware.com
46 Omron FINS Ethernet Driver Help
www. kepware.com
Omron FINS Ethernet Driver Help 47
BCD Support
16-bit and 32-bit data can be referenced as signed and unsigned BCD values.
Unsigned BCD support is accomplished by appending a 'D' to any Word or DWord tag address or by using the
BCD and LBCD data types. The value range is as follows:
Signed BCD support is accomplished by appending a 'D' to any Short or Long tag address. The most significant
bit of the Short/Long is set to 1 for negative values, 0 for positive values. The value range is as follows:
Example
IR0D @ Short = -50
IR0D @ Word = 8050 (MSB set)
IR0 @ BCD = 8050
IR0D @ Short = 50
IR0D @ Word = 50
IR0 @ BCD = 50
Note: Boolean, Float, and String data types do not support appending 'D' to the tag address. Furthermore, 'D'
cannot be appended to BCD or LBCD tags, or tags with a default data type of BCD or LBCD (such as Counter and
Timer tags).
String Support
www. kepware.com
48 Omron FINS Ethernet Driver Help
The CVM1-CPU01 model supports reading and writing numerous device types as an ASCII string. When using
data memory for string data, each register will contain two bytes (two characters) of ASCII data. The order of the
ASCII data within a given register can be selected when the string is defined. The length of the string can be from
2 to 512 characters and is entered in place of a bit number. The string length cannot exceed the request size that
has been assigned to the device up to a request size of 512. For request size values greater than 512, string
length cannot exceed 512. The length must be entered as an even number. The range of registers spanned by
the string cannot exceed the range of the device type. The byte order is specified by appending either a "H" or "L"
to the address.
When using one byte of ASCII data per register, the length of the string can be from 1 to 256 characters and is
entered in place of a bit number. The string length times 2 cannot exceed the request size that has been
assigned to the device up to a request size of 512. For request size values greater than 512, string length cannot
exceed 256. The range of registers spanned by the string cannot exceed the range of the device type. The byte to
use within a register is specified by appending either a "D" or "E" to the address. For more information, refer to
Device Setup.
Examples
1. To address a string starting at D1000 with a length of 100 bytes and HiLo byte order, enter:
D1000.100H
2. To address a string starting at D1100 with a length of 78 bytes and LoHi byte order, enter: D1100.078L
3. To address a string starting at D2000 with a length of 55 bytes and Only the High Order byte, enter:
D2000.055D
4. To address a string starting at D2200 with a length of 37 bytes and Only the Low Order byte, enter:
D2200.037E
Array Support
Arrays are supported for all data types except Boolean, Data Register, and Index Register. There are two methods
of addressing an array. Examples are given using data memory locations.
Rows multiplied by cols multiplied by data size in bytes (2 for Word, Short, and BCD; 4 for DWord, Long, LBCD,
and Float) cannot exceed the request size that has been assigned to the device. For example, a 10 X 10 array of
words results in an array size of 200 bytes, which would require a request size of at least 256.
Note: Use caution when modifying 32-bit values (DWord, Long, LBCD, and Float). Each address for which these
data types are allowed starts at a word offset within the device. DWords DM0 and DM1 overlap at word DM1.
Writing to DM0 will also modify the value held in DM1. It is recommended that users utilize these data types so
that overlapping does not occur. For example, when using DWords, use DM0, DM2, DM4, and so on to prevent
overlapping Words.
CVM1-CPU11 Addressing
The default data types for dynamically defined tags are shown in bold. For more information, refer below the
table for notes and restrictions on BCD Support, String Support, and Array Support.
www. kepware.com
Omron FINS Ethernet Driver Help 49
www. kepware.com
50 Omron FINS Ethernet Driver Help
www. kepware.com
Omron FINS Ethernet Driver Help 51
BCD Support
16-bit and 32-bit data can be referenced as signed and unsigned BCD values.
Unsigned BCD support is accomplished by appending a 'D' to any Word or DWord tag address or by using the
BCD and LBCD data types. The value range is as follows:
Signed BCD support is accomplished by appending a 'D' to any Short or Long tag address. The most significant
bit of the Short/Long is set to 1 for negative values, 0 for positive values. The value range is as follows:
Example
IR0D @ Short = -50
IR0D @ Word = 8050 (MSB set)
IR0 @ BCD = 8050
IR0D @ Short = 50
IR0D @ Word = 50
IR0 @ BCD = 50
Note: Boolean, Float, and String data types do not support appending 'D' to the tag address. Furthermore, 'D'
cannot be appended to BCD or LBCD tags, or tags with a default data type of BCD or LBCD (such as Counter and
Timer tags).
String Support
The CVM1-CPU11 model supports reading and writing numerous device types as an ASCII string. When using
data memory for string data, each register will contain two bytes (two characters) of ASCII data. The order of the
ASCII data within a given register can be selected when the string is defined. The length of the string can be from
2 to 512 characters and is entered in place of a bit number. The string length cannot exceed the request size that
has been assigned to the device up to a request size of 512. For request size values greater than 512, string
length cannot exceed 512. The length must be entered as an even number. The range of registers spanned by
the string cannot exceed the range of the device type. The byte order is specified by appending either a "H" or "L"
to the address.
When using one byte of ASCII data per register, the length of the string can be from 1 to 256 characters and is
entered in place of a bit number. The string length times 2 cannot exceed the request size that has been
assigned to the device up to a request size of 512. For request size values greater than 512, string length cannot
exceed 256. The range of registers spanned by the string cannot exceed the range of the device type. The byte to
use within a register is specified by appending either a "D" or "E" to the address. For more information, refer to
Device Setup.
Examples
1. To address a string starting at D01000 with a length of 100 bytes and HiLo byte order, enter:
D01000.100H
2. To address a string starting at D01100 with a length of 78 bytes and LoHi byte order, enter:
D01100.078L
3. To address a string starting at D02000 with a length of 55 bytes and Only the High Order byte, enter:
D02000.055D
4. To address a string starting at D02200 with a length of 37 bytes and Only the Low Order byte, enter:
D02200.037E
Array Support
Arrays are supported for all data types except Boolean, Data Register, and Index Register. There are two methods
of addressing an array. Examples are given using data memory locations.
www. kepware.com
52 Omron FINS Ethernet Driver Help
Rows multiplied by cols multiplied by data size in bytes (2 for Word, Short, and BCD; 4 for DWord, Long, LBCD,
and Float) cannot exceed the request size that has been assigned to the device. For example, a 10 X 10 array of
words results in an array size of 200 bytes, which would require a request size of at least 256.
Note: Use caution when modifying 32-bit values (DWord, Long, LBCD, and Float). Each address for which these
data types are allowed starts at a word offset within the device. DWords DM0 and DM1 overlap at word DM1.
Writing to DM0 will also modify the value held in DM1. It is recommended that users utilize these data types so
that overlapping does not occur. For example, when using DWords, use DM0, DM2, DM4, and so on to prevent
overlapping Words.
CVM1-CPU21 Addressing
The default data types for dynamically defined tags are shown in bold. For more information, refer below the
table for notes and restrictions on BCD Support, String Support, and Array Support.
www. kepware.com
Omron FINS Ethernet Driver Help 53
www. kepware.com
54 Omron FINS Ethernet Driver Help
www. kepware.com
Omron FINS Ethernet Driver Help 55
BCD Support
16-bit and 32-bit data can be referenced as signed and unsigned BCD values.
Unsigned BCD support is accomplished by appending a 'D' to any Word or DWord tag address or by using the
BCD and LBCD data types. The value range is as follows:
Signed BCD support is accomplished by appending a 'D' to any Short or Long tag address. The most significant
bit of the Short/Long is set to 1 for negative values, 0 for positive values. The value range is as follows:
Example
IR0D @ Short = -50
IR0D @ Word = 8050 (MSB set)
IR0 @ BCD = 8050
IR0D @ Short = 50
IR0D @ Word = 50
IR0 @ BCD = 50
Note: Boolean, Float, and String data types do not support appending 'D' to the tag address. Furthermore, 'D'
cannot be appended to BCD or LBCD tags, or tags with a default data type of BCD or LBCD (such as Counter and
Timer tags).
String Support
The CVM1-CPU21 model supports reading and writing numerous device types as an ASCII string. When using
data memory for string data, each register will contain two bytes (two characters) of ASCII data. The order of the
ASCII data within a given register can be selected when the string is defined. The length of the string can be from
2 to 512 characters and is entered in place of a bit number. The string length cannot exceed the request size that
has been assigned to the device up to a request size of 512. For request size values greater than 512, string
length cannot exceed 512. The length must be entered as an even number. The range of registers spanned by
the string cannot exceed the range of the device type. The byte order is specified by appending either a "H" or "L"
to the address.
When using one byte of ASCII data per register, the length of the string can be from 1 to 256 characters and is
entered in place of a bit number. The string length times 2 cannot exceed the request size that has been
assigned to the device up to a request size of 512. For request size values greater than 512, string length cannot
exceed 256. The range of registers spanned by the string cannot exceed the range of the device type. The byte to
use within a register is specified by appending either a "D" or "E" to the address. For more information, refer to
Device Setup.
Examples
www. kepware.com
56 Omron FINS Ethernet Driver Help
1. To address a string starting at D01000 with a length of 100 bytes and HiLo byte order, enter:
D01000.100H
2. To address a string starting at D01100 with a length of 78 bytes and LoHi byte order, enter:
D01100.078L
3. To address a string starting at D02000 with a length of 55 bytes and Only the High Order byte, enter:
D02000.055D
4. To address a string starting at D02200 with a length of 37 bytes and Only the Low Order byte, enter:
D02200.037E
Array Support
Arrays are supported for all data types except Boolean, Data Register, and Index Register. There are two methods
of addressing an array. Examples are given using data memory locations.
Rows multiplied by cols multiplied by data size in bytes (2 for Word, Short, and BCD; 4 for DWord, Long, LBCD,
and Float) cannot exceed the request size that has been assigned to the device. For example, a 10 X 10 array of
words results in an array size of 200 bytes, which would require a request size of at least 256.
Note: Use caution when modifying 32-bit values (DWord, Long, LBCD, and Float). Each address for which these
data types are allowed starts at a word offset within the device. DWords DM0 and DM1 overlap at word DM1.
Writing to DM0 will also modify the value held in DM1. It is recommended that users utilize these data types so
that overlapping does not occur. For example, when using DWords, use DM0, DM2, DM4, and so on to prevent
overlapping Words.
CS1 Addressing
The default data types for dynamically defined tags are shown in bold. For more information, refer below the
table for notes and restrictions on BCD Support, String Support, and Array Support.
www. kepware.com
Omron FINS Ethernet Driver Help 57
www. kepware.com
58 Omron FINS Ethernet Driver Help
www. kepware.com
Omron FINS Ethernet Driver Help 59
*Use caution when modifying 32-bit values (DWord, Long, LBCD, and Float). Each address for which these data
types are allowed starts at a word offset within the device. Therefore, DWords D0 and D1 overlap at word D1 and
writing to D0 will also modify the value held in D1. It is recommended that users utilize these data types so that
overlapping does not occur. When using DWords, users may want to use D0, D2, D4, and so on to prevent
overlapping Words. The exception to this is IR tags, which are native 32-bit values with MSB to LSB byte ordering
for the CS1-series PLCs.
BCD Support
16-bit and 32-bit data can be referenced as signed and unsigned BCD values.
Unsigned BCD support is accomplished by appending a 'D' to any Word or DWord tag address or by using the
BCD and LBCD data types. The value range is as follows:
www. kepware.com
60 Omron FINS Ethernet Driver Help
Signed BCD support is accomplished by appending a 'D' to any Short or Long tag address. The most significant
bit of the Short/Long is set to 1 for negative values, 0 for positive values. The value range is as follows:
Example
D0D @ Short = -50
D0D @ Word = 8050 (MSB set)
D0 @ BCD = 8050
D0D @ Short = 50
D0D @ Word = 50
D0 @ BCD = 50
Note: Boolean, Float, and String data types do not support appending 'D' to the tag address. Furthermore, 'D'
cannot be appended to BCD or LBCD tags, or tags with a default data type of BCD or LBCD (such as Counter and
Timer tags).
String Support
The CS1 model supports reading and writing numerous device types as an ASCII string. When using data
memory for string data, each register will contain two bytes (two characters) of ASCII data. The order of the
ASCII data within a given register can be selected when the string is defined. The length of the string can be from
2 to 512 characters and is entered in place of a bit number. The string length cannot exceed the request size that
has been assigned to the device up to a request size of 512. For request size values greater than 512, string
length cannot exceed 512. The length must be entered as an even number. The range of registers spanned by
the string cannot exceed the range of the device type. The byte order is specified by appending either a "H" or "L"
to the address.
When using one byte of ASCII data per register, the length of the string can be from 1 to 256 characters and is
entered in place of a bit number. The string length times 2 cannot exceed the request size that has been
assigned to the device up to a request size of 512. For request size values greater than 512, string length cannot
exceed 256. The range of registers spanned by the string cannot exceed the range of the device type. The byte to
use within a register is specified by appending either a "D" or "E" to the address. For more information, refer to
Device Setup.
Examples
1. To address a string starting at D01000 with a length of 100 bytes and HiLo byte order, enter:
D01000.100H
2. To address a string starting at D01100 with a length of 78 bytes and LoHi byte order, enter:
D01100.078L
3. To address a string starting at D02000 with a length of 55 bytes and Only the High Order byte, enter:
D02000.055D
4. To address a string starting at D02200 with a length of 37 bytes and Only the Low Order byte, enter:
D02200.037E
Array Support
Arrays are supported for all data types except Boolean. There are two methods of addressing an array. Examples
are given using data memory locations.
Rows multiplied by cols multiplied by data size in bytes (2 for Word, Short, and BCD; 4 for DWord, Long, LBCD,
and Float) cannot exceed the request size that has been assigned to the device. For example, a 10 X 10 array of
words results in an array size of 200 bytes, which would require a request size of at least 256.
www. kepware.com
Omron FINS Ethernet Driver Help 61
CS and TS registers can be written to only when the device is in Monitor Mode or Programming Mode. DR and IR
registers can be written to only when the device is in Programming Mode. CS, TS, DR, and IR registers cannot be
written to in Run Mode. If the device is in Run Mode and a write is attempted to one of these registers, the value in
the device will not change. The following will occur:
l If the device is in Run Mode and a write is attempted to a CS or TS register, an "unable to write" error
message will be returned.
l If the device is in Run Mode and a write is attempted to a DR or IR register, the write will succeed.
Although no error message will be returned, the value in the device will not change because the device
is in Run Mode.
CJ1 Addressing
The default data types for dynamically defined tags are shown in bold. For more information, refer below the
table for notes and restrictions on BCD Support, String Support, and Array Support.
www. kepware.com
62 Omron FINS Ethernet Driver Help
www. kepware.com
Omron FINS Ethernet Driver Help 63
*Use caution when modifying 32-bit values (DWord, Long, LBCD, and Float). Each address for which these data
types are allowed starts at a word offset within the device. Therefore, DWords D0 and D1 overlap at word D1 and
writing to D0 will also modify the value held in D1. It is recommended that users utilize these data types so that
overlapping does not occur. When using DWords, users may want to use D0, D2, D4, and so on to prevent
overlapping Words. The exception to this is IR tags, which are native 32-bit values with MSB to LSB byte ordering
for the CJ1-series PLCs.
BCD Support
16-bit and 32-bit data can be referenced as signed and unsigned BCD values.
Unsigned BCD support is accomplished by appending a 'D' to any Word or DWord tag address or by using the
BCD and LBCD data types. The value range is as follows:
Signed BCD support is accomplished by appending a 'D' to any Short or Long tag address. The most significant
bit of the Short/Long is set to 1 for negative values, 0 for positive values. The value range is as follows:
Example
D0D @ Short = -50
D0D @ Word = 8050 (MSB set)
D0 @ BCD = 8050
D0D @ Short = 50
D0D @ Word = 50
D0 @ BCD = 50
Note: Boolean, Float, and String data types do not support appending 'D' to the tag address. Furthermore, 'D'
cannot be appended to BCD or LBCD tags, or tags with a default data type of BCD or LBCD (such as Counter and
Timer tags).
www. kepware.com
64 Omron FINS Ethernet Driver Help
String Support
The CJ1 model supports reading and writing numerous device types as an ASCII string. When using data
memory for string data, each register will contain two bytes (two characters) of ASCII data. The order of the
ASCII data within a given register can be selected when the string is defined. The length of the string can be from
2 to 512 characters and is entered in place of a bit number. The string length cannot exceed the request size that
has been assigned to the device up to a request size of 512. For request size values greater than 512, string
length cannot exceed 512. The length must be entered as an even number. The range of registers spanned by
the string cannot exceed the range of the device type. The byte order is specified by appending either a "H" or "L"
to the address.
When using one byte of ASCII data per register, the length of the string can be from 1 to 256 characters and is
entered in place of a bit number. The string length times 2 cannot exceed the request size that has been
assigned to the device up to a request size of 512. For request size values greater than 512, string length cannot
exceed 256. The range of registers spanned by the string cannot exceed the range of the device type. The byte to
use within a register is specified by appending either a "D" or "E" to the address. For more information, refer to
Device Setup.
Examples
1. To address a string starting at D01000 with a length of 100 bytes and HiLo byte order, enter:
D01000.100H
2. To address a string starting at D01100 with a length of 78 bytes and LoHi byte order, enter:
D01100.078L
3. To address a string starting at D02000 with a length of 55 bytes and Only the High Order byte, enter:
D02000.055D
4. To address a string starting at D02200 with a length of 37 bytes and Only the Low Order byte, enter:
D02200.037E
Array Support
Arrays are supported for all data types except Boolean. There are two methods of addressing an array. Examples
are given using data memory locations.
Rows multiplied by cols multiplied by data size in bytes (2 for Word, Short, and BCD; 4 for DWord, Long, LBCD,
and Float) cannot exceed the request size that has been assigned to the device. For example, a 10 X 10 array of
words results in an array size of 200 bytes, which would require a request size of at least 256.
l If the device is in Run Mode and a write is attempted to a CS or TS register, an "unable to write" error
message will be returned.
l If the device is in Run Mode and a write is attempted to a DR or IR register, the write will succeed.
Although no error message will be returned, the value in the device will not change because the device
is in Run Mode.
CJ2 Addressing
The default data types for dynamically defined tags are shown in bold. For more information, refer below the
table for notes and restrictions on BCD Support, String Support, and Array Support.
www. kepware.com
Omron FINS Ethernet Driver Help 65
A10000.00-A10000.15-
A11535.00-A11535.15
Auxiliary Relay as String A000.512H-A447.002H String Read Only
with HiLo Byte Order A448.512H-A1471.002H String
A10000.512H-A11535.002H String Read/Write
www. kepware.com
66 Omron FINS Ethernet Driver Help
www. kepware.com
Omron FINS Ethernet Driver Help 67
*Use caution when modifying 32-bit values (DWord, Long, LBCD, and Float). Each address for which these data
types are allowed starts at a word offset within the device. Therefore, DWords D0 and D1 overlap at word D1 and
writing to D0 will also modify the value held in D1. It is recommended that users utilize these data types so that
overlapping does not occur. When using DWords, users may want to use D0, D2, D4, and so on to prevent
overlapping Words. The exception to this is IR tags, which are native 32-bit values with MSB to LSB byte ordering
for the CJ2-series PLCs.
BCD Support
16-bit and 32-bit data can be referenced as signed and unsigned BCD values.
Unsigned BCD support is accomplished by appending a 'D' to any Word or DWord tag address or by using the
BCD and LBCD data types. The value range is as follows:
Signed BCD support is accomplished by appending a 'D' to any Short or Long tag address. The most significant
bit of the Short/Long is set to 1 for negative values, 0 for positive values. The value range is as follows:
Example
D0D @ Short = -50
D0D @ Word = 8050 (MSB set)
D0 @ BCD = 8050
D0D @ Short = 50
D0D @ Word = 50
D0 @ BCD = 50
Note: Boolean, Float, and String data types do not support appending 'D' to the tag address. Furthermore, 'D'
cannot be appended to BCD or LBCD tags, or tags with a default data type of BCD or LBCD (such as Counter and
Timer tags).
String Support
The CJ2 model supports reading and writing numerous device types as an ASCII string. When using data
memory for string data, each register will contain two bytes (two characters) of ASCII data. The order of the
ASCII data within a given register can be selected when the string is defined. The length of the string can be from
2 to 512 characters and is entered in place of a bit number. The string length cannot exceed the request size that
has been assigned to the device up to a request size of 512. For request size values greater than 512, string
length cannot exceed 512. The length must be entered as an even number. The range of registers spanned by
the string cannot exceed the range of the device type. The byte order is specified by appending either a "H" or "L"
to the address.
www. kepware.com
68 Omron FINS Ethernet Driver Help
When using one byte of ASCII data per register, the length of the string can be from 1 to 256 characters and is
entered in place of a bit number. The string length times 2 cannot exceed the request size that has been
assigned to the device up to a request size of 512. For request size values greater than 512, string length cannot
exceed 256. The range of registers spanned by the string cannot exceed the range of the device type. The byte to
use within a register is specified by appending either a "D" or "E" to the address. For more information, refer to
Device Setup.
Examples
1. To address a string starting at D01000 with a length of 100 bytes and HiLo byte order, enter:
D01000.100H
2. To address a string starting at D01100 with a length of 78 bytes and LoHi byte order, enter:
D01100.078L
3. To address a string starting at D02000 with a length of 55 bytes and Only the High Order byte, enter:
D02000.055D
4. To address a string starting at D02200 with a length of 37 bytes and Only the Low Order byte, enter:
D02200.037E
Array Support
Arrays are supported for all data types except Boolean. There are two methods of addressing an array. Examples
are given using data memory locations.
Rows multiplied by cols multiplied by data size in bytes (2 for Word, Short, and BCD; 4 for DWord, Long, LBCD,
and Float) cannot exceed the request size that has been assigned to the device. For example, a 10 X 10 array of
words results in an array size of 200 bytes, which would require a request size of at least 256.
l If the device is in Run Mode and a write is attempted to a CS or TS register, an "unable to write" error
message will be returned.
l If the device is in Run Mode and a write is attempted to a DR or IR register, the write will succeed.
Although no error message will be returned, the value in the device will not change because the device
is in Run Mode.
www. kepware.com
Omron FINS Ethernet Driver Help 69
Error Descriptions
The following error/warning messages may be generated. Click on the link for a description of the message.
See Also:
Main and Sub Error Codes
Remote Network Error
www. kepware.com
70 Omron FINS Ethernet Driver Help
Possible Cause:
A tag address that has been specified statically references a location that is beyond the range of supported
locations for the device.
Solution:
Verify the address is correct; if it is not, re-enter it in the client application.
Possible Cause:
A tag address that has been specified statically has been assigned an invalid data type.
Solution:
Modify the requested data type in the client application.
Possible Cause:
A tag address that has been specified statically references a location that is valid for the communications protocol
but not supported by the target device.
Solution:
Verify that the address is correct; if it is not, re-enter it in the client application. Also verify that the selected
model name for the device is correct.
Possible Cause:
A tag address that has been specified statically has a requested access mode that is not compatible with what the
device supports for that address.
Solution:
Change the access mode in the client application.
Possible Cause:
A tag address that has been specified statically contains one or more invalid characters.
Solution:
Re-enter the address in the client application.
Device <device name> access right denied (tag <address>). [Main, Sub:
<main code, sub code>].
Error Type:
Warning
www. kepware.com
Omron FINS Ethernet Driver Help 71
Possible Cause:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
possible causes.
Solution:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
corrections.
Possible Cause:
The network parameters for the stated device were changed during run time and were found to be in conflict with
another device. Communication with this device will not be possible until the conflict is resolved.
Solution:
Change one or more of the following: channel network adapter, port number or device ID.
Note:
For more information, refer to the "Duplicate Devices" section of FINS Networks.
Possible Cause:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
possible causes.
Solution:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
corrections.
Possible Cause:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
possible causes.
Solution:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
corrections.
Possible Cause:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
possible causes.
Solution:
www. kepware.com
72 Omron FINS Ethernet Driver Help
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
corrections.
Possible Cause:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
possible causes.
Solution:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
corrections.
Device <device name> responded with local node error. [Main, Sub: <main
code, sub code>].
Error Type:
Serious
Possible Cause:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
possible causes.
Solution:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
corrections.
Device <device name> responded with non-fatal CPU unit error. [End code:
<end code>].
Error Type:
Warning
Possible Cause:
Refer to Main and Sub Error Codes for a description of the end code word bits 6, 7, and 15. The description
includes possible causes.
Solution:
Refer to Main and Sub Error Codes for a description of the end code word bits 6, 7, and 15. The description
includes corrections.
Device <device name> responded with read not possible (tag <address>, size
<bytes>). [Main, Sub: <main code, sub code>].
Error Type:
Warning
Possible Cause:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
possible causes.
Solution:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
corrections.
Device <device name> responded with error <error code> (tag <address>,
size <bytes>). [Main, Sub: <main code, sub code>].
Error Type:
Warning
www. kepware.com
Omron FINS Ethernet Driver Help 73
Possible Cause:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
possible causes.
Solution:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
corrections.
Device <device name> responded with network relay error. [Net Addr, Node
Addr: <network address, node address>], [Main, Sub: <main code, sub code>],
[End code: <end code>].
Error Type:
Warning
Possible Cause:
Refer to Main and Sub Error Codes for a description of the end code word bits 6, 7, and 15. The description
includes possible causes.
Note:
A network relay error in combination with other conditions and configuration can cause a Remote Network
Error.
Solution:
Refer to Main and Sub Error Codes for a description of the end code word bits 6, 7, and 15. The description
includes corrections.
Device <device name> responded with write not possible (tag <address>, size
<bytes>). [Main, Sub: <main code, sub code>].
Error Type:
Warning
Possible Cause:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
possible causes.
Solution:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
corrections.
Device <device name> responded with destination node error. [Main, Sub:
<main code, sub code>].
Error Type:
Serious
Possible Cause:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
possible causes.
Solution:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
corrections.
Device <device name> responded with routing table error. [Main, Sub: <main
code, sub code>].
Error Type:
Serious
Possible Cause:
www. kepware.com
74 Omron FINS Ethernet Driver Help
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
possible causes.
Solution:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
corrections.
Device <device name> responded with error in unit. [Main, Sub: <main code,
sub code>].
Error Type:
Serious
Possible Cause:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
possible causes.
Solution:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
corrections.
Device <device name> responded with fatal CPU unit error. [End code: <end
code>].
Error Type:
Warning
Possible Cause:
Refer to Main and Sub Error Codes for a description of the end code word bits 6, 7, and 15. The description
includes possible causes.
Solution:
Refer to Main and Sub Error Codes for a description of the end code word bits 6, 7, and 15. The description
includes corrections.
Possible Cause:
1. The connection between the device and the host PC is broken.
3. The named device may have been assigned an incorrect network ID.
4. The response from the device took longer to receive than the amount of time specified in the "Request
Timeout" device setting.
Solution:
1. Verify the cabling between the PC and the PLC device.
2. Verify that the IP address given to the named device matches that of the actual device.
3. Verify that the network ID given to the named device matches that of the actual device.
4. Increase the Request Timeout setting so that the entire response can be handled.
www. kepware.com
Omron FINS Ethernet Driver Help 75
Possible Cause:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
possible causes.
Solution:
Refer to Main and Sub Error Codes for a description of the Main and Sub Codes. The description includes
corrections.
Missing address.
Error Type:
Warning
Possible Cause:
A tag address that has been specified statically has no length.
Solution:
Re-enter the address in the client application.
The current project was created with an older version of this driver. Examine
device properties to validate network parameters.
Error Type:
Warning
Possible Cause:
The current project was created using a version of this driver that checked for network parameter conflicts
during runtime. This version only performs runtime checks on parameters that can be changed with system
tags. All other parameters are now checked when Device Properties are edited.
Solution:
Examine the properties of each device. Change the value of any property and then change it back to its original
value to alter the property sheet. Then, click "Accept" or "OK" to validate all of the network parameters associated
with the device. Once the devices are validated, save the project.
Note:
This solution will not have to be repeated. Any new devices that are added to the project will be validated
automatically.
See Also:
FINS Networks
Possible Cause:
3. The named device may have been assigned an incorrect network ID.
Solution:
2. Verify the IP address given to the named device matches that of the actual device.
3. Verify the network ID given to the named device matches that of the actual device.
www. kepware.com
76 Omron FINS Ethernet Driver Help
Unable to write to register <register address> for device <device name>. The
device is in run mode.
Error Type:
Warning
Possible Cause:
The device is in Run Mode. CS and TS registers can only be written to when the device is in Programming Mode.
Solution:
Set the device to Programming Mode.
Possible Cause:
Two or more devices in different channels are using the same source IP address and port number.
Solution:
To communicate to the same device across multiple OPC server channels, users must do one of the following:
1. Use a unique port number for each channel.
2. Use the same port number but configure each channel to use a unique network adapter and IP.
See Also:
Channel Setup
Multihoming
Winsock V1.1 or higher must be installed to use the Omron FINS Ethernet
device driver.
Error Type:
Fatal
Possible Cause:
The version number of the Winsock DLL found on the system is less than 1.1.
Solution:
Upgrade Winsock to version 1.1 or higher.
www. kepware.com
Omron FINS Ethernet Driver Help 77
www. kepware.com
78 Omron FINS Ethernet Driver Help
www. kepware.com
Omron FINS Ethernet Driver Help 79
www. kepware.com
80 Omron FINS Ethernet Driver Help
www. kepware.com
Omron FINS Ethernet Driver Help 81
www. kepware.com
82 Omron FINS Ethernet Driver Help
Flags
There are specific flags in the end code word (bits 6, 7, and 15) that may also be ON. The following dialog
displays the contents of the end code word.
If bit 6 or 7 is ON, an error has occurred in the destination CPU unit. If this occurs, refer to the operation manuals
for the CPU unit where the error occurred and then remove the cause of the error.
www. kepware.com
Omron FINS Ethernet Driver Help 83
If bit 15 is ON, an error has occurred during a network relay operation. The end code contains an additional two-
byte (one word) network relay error code that can be used to determine the location of the relay error. The
following diagram displays the response data of a network relay error. This information can be used to determine
the node where the error occurred so that appropriate measures may be taken.
The following conditions and configuration, when they occur, are considered a remote network error and the
device enters error state.
2. Main code (MRES) in end code word equals destination node error (02).
3. The device FINS network configuration source network address number or destination network address
number parameters have a value of 1 to 127, which indicates a remote network address.
See Also:
Main and Sub Error Codes
FINS Network Configuration
www. kepware.com
84 Omron FINS Ethernet Driver Help
Index
BCD 18
Boolean 18
C1000H Addressing 26
C2000H Addressing 29
C200H Addressing 19
C500 Addressing 23
Channel Setup 5
CJ1 Addressing 61
CJ2 Addressing 64
Communications Parameters 9
CS1 Addressing 56
CV1000 Addressing 36
CV2000 Addressing 40
CV500 Addressing 32
CVM1-CPU01 Addressing 45
CVM1-CPU11 Addressing 48
CVM1-CPU21 Addressing 52
www. kepware.com
Omron FINS Ethernet Driver Help 85
Device <device name> responded with a command parameter error (tag <address>, size <bytes>). [Main,
Sub: <main code, sub code>]. 72
Device <device name> responded with a communications error. [Main, Sub: <main code, sub code>]. 74
Device <device name> responded with destination node error. [Main, Sub: <main code, sub code>]. 73
Device <device name> responded with error <error code> (tag <address>, size <bytes>). [Main, Sub:
<main code, sub code>]. 72
Device <device name> responded with error in unit. [Main, Sub: <main code, sub code>]. 74
Device <device name> responded with fatal CPU unit error. [End code: <end code>]. 74
Device <device name> responded with local node error. [Main, Sub: <main code, sub code>]. 72
Device <device name> responded with network relay error. [Net Addr, Node Addr: <network address, node
address>], [Main, Sub: <main code, sub code>], [End code
<end code>]. 73
Device <device name> responded with non-fatal CPU unit error. [End code: <end code>]. 72
Device <device name> responded with routing table error. [Main, Sub: <main code, sub code>]. 73
Device <device name> responded with write not possible (tag <address>, size <bytes>). [Main, Sub:
<main code, sub code>]. 73
Device address <address> contains a syntax error. 70
Device address <address> is not supported by model <model name>. 70
Device address <address> is read only. 70
Device ID 6
Device Setup 6
Error Descriptions 69
FINS Networks 12
FINS Networks Configuration 11
www. kepware.com
86 Omron FINS Ethernet Driver Help
Short 18
Supported Devices 6
The current project was created with an older version of this driver. Examine device properties to validate
network parameters 75
www. kepware.com