Omron ETHERNET DIRECT DR 170 14 User manual

OMRON ETHERNET Direct
DAServer
User’s Guide
Ver 1.x Rev 1.4
DR 170 14
KLINKMANN AUTOMATION
P.O. Box 38
FIN-00371 Helsinki Finland
tel. int. + 358 9 5404940
fax int. + 358 9 5413541
www.klinkmann.com

Klinkmann Automation Omron Ethernet DAServer i
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
Contents
Before You Begin .......................................................................................................... 2
About This User Guide............................................................................................... 2
Introduction.................................................................................................................... 2
Overview.................................................................................................................... 2
Communication Protocols.......................................................................................... 3
Application Communications Protocols .................................................................. 3
FINS Message Communication.............................................................................. 4
Accessing Items via the DAServer............................................................................. 4
Features..................................................................................................................... 6
Demo Mode ............................................................................................................... 6
Before starting the OMRON Ethernet DAServer............................................................ 8
Preparing the Hardware to be used with OMRON Ethernet DAServer...................... 8
Ethernet Unit Configuration Example for CS1 PLC.................................................... 9
Example program for sending “unsolicited” data from PLC ....................................... 14
Configuration ................................................................................................................. 17
Getting Started Quickly with the DAServer ................................................................ 17
Configuring the DAServer.......................................................................................... 18
DASOmronEth Hierarchy in the DAServer Manager.................................................. 21
Enabling Software License Key for DASOmronEth ................................................... 26
Configuring Device Group Definitions........................................................................ 27
Configuring Device Item Definitions........................................................................... 31
Hot Configuration.................................................................................................... 33
Item Names................................................................................................................... 35
Item Name General Format ....................................................................................... 35
CS1/CJ1 PLCs........................................................................................................... 38
C200HX/C200HG/C200HE PLCs.............................................................................. 40
CV-series PLCs ......................................................................................................... 41
C/CPM2x PLCs.......................................................................................................... 44
CQM1 PLCs............................................................................................................... 46
DAServer Standard System Items............................................................................. 47
DAServer Global System Item................................................................................ 48
DAServer Device-Specific System Items................................................................ 48
DAServer Device-Group-Specific System Items..................................................... 50
Generic OPC Syntax.................................................................................................. 52
Troubleshooting............................................................................................................. 53
Monitoring Connectivity Status with the PLC ............................................................. 53
Monitoring the Status of DAS Conversations............................................................. 54
Using DDEStatus and IOStatus in Excel................................................................ 54
Reading Values from the DAServer into Excel....................................................... 54
Writing Values to the DAServer from Excel............................................................ 55
Error Messages and Codes ....................................................................................... 56
Server-Specific Error Codes ...................................................................................... 60
FINS Response Codes .............................................................................................. 60
Reference...................................................................................................................... 65
DAServer Architecture ............................................................................................... 65
DAServers.............................................................................................................. 65
Plug-ins................................................................................................................... 66

Klinkmann Automation Omron Ethernet DAServer ii
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
Component Environments ......................................................................................... 67
Before You Begin
About This User Guide
This user’s guide describes the user interface and functions of the KLINKMANN OMRON
Ethernet Direct DAServer. It also provides you with the step-by-step procedures on how
to configure and use the OMRON Ethernet Direct DAServer after it is installed.
The OMRON Ethernet Direct DAServer user’s guide is organized in the following fashion:
• Contents
• Introduction: contains overview information about the OMRON Ethernet Direct
DAServer and the environment in which it works.
• Configuration: contains a detailed description of the user interface elements of this
DAServer in addition to its functionality.
• Item Names: describes the item naming conventions for targeted devices.
• Troubleshooting: provides information about error messages, codes, and conditions
displayed by the OMRON Ethernet Direct DAServer.
• Reference: describes the DAServer architecture in general.
• Index
You can view this document on-line or you can print it, in part or whole, by using the
Adobe Acrobat Reader’s print facility.

Klinkmann Automation Omron Ethernet DAServer 2
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
CHAPTER 1
Introduction
This chapter provides you with an overview of the KLINKMANN OMRON Ethernet Direct
DAServer, including the application- and bus-level communications protocols, item
naming conventions and DAServer features.
Contents
• Overview
• Communications Protocols
• Accessing Items via the DAServer
• Features
• Demo Mode
• Network Environment and Conditions
Overview
The KLINKMANN OMRON Ethernet Direct DAServer (hereafter referred to as the
“OMRON Ethernet DAServer” or “DAServer” or “DASOmronEth” throughout the
remainder of this user’s guide) is a Microsoft ® Windows ® application program that acts
as a FINS message communications protocol server. It allows other Windows application
programs access to data from OMRON PLCs (also referred to as devices) over the
OMRON Ethernet FA (Factory Automation) network.
The OMRON Ethernet Direct DAServer requires an Ethernet card and TCP/IP protocol
installed on the computer to communicate with the Ethernet network. The OMRON
Ethernet Direct DAServer can access to data from Controllers connected to the Ethernet
System directly (with Ethernet Unit installed) or from Controllers interconnected to
Ethernet System through SYSMAC LINK network or any other OMRON FA network
(through PC Gateway - an OMRON Controller which has multiple Communications Units
mounted, including the Ethernet Unit, and therefore that belongs to two networks and can
thus function as an interface between them). The OMRON Ethernet Direct DAServer
supports the Controller Memory Areas accessible by FINS commands.
No additions to Controller’s user program are needed if OMRON Ethernet Direct
DAServer is used in a poll (normal) mode, i.e. the DAServer sends read or write FINS
command to Controller and Controller responds with corresponding response. The
OMRON Ethernet Direct DAServer supports also the possibility to receive “unsolicited”
data from Controller – in this case some additions in Controller program are needed. The
DAServer “slave” mode can be established – at communication start-up DAServer
requests data one time and after it - only unsolicited data can be received from Controller.
At same time the writing of new values to Controller is still possible.
The OMRON Ethernet Direct DAServer can access to data from CS1/CJ1, CV-series and
C200HX/C200HG/C200HE PLCs (directly from Ethernet network or inter-networked from
other OMRON FA networks) as well as from C-series and CQM1 PLCs (only inter-
networked from other OMRON FA networks).
While the OMRON Ethernet Direct DAServer is primarily intended for use with
Wonderware InTouch ® (Version 7.11 Patch 02 and later), it may be used by any

Klinkmann Automation Omron Ethernet DAServer 3
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
Microsoft Windows program capable of acting as a DDE, SuiteLink ™ or OPC client that
can also coexist with FactorySuite ™ 2000 and greater.
Communication Protocols
The OMRON Ethernet Direct DAServer communicates with clients and PLCs using the
following different communications protocols:
• Application communications protocols such as OPC, DDE and SuiteLink to
communicate with clients located on either local or remote nodes.
• FINS message communications protocol to communicate with the Omron controllers
over FA (Factory Automation) networks.
Important! This DAServer is compliant with the OPC Data Access (DA) 2.05
specification.
For more information about the DAServer architecture, see the Reference section.
Application Communications Protocols
The DAServer utilizes the following application communications protocols to
communicate with the clients.
OPC
OPC (OLE for Process Control) is a non-proprietary set of standard interfaces based
upon Microsoft’s OLE/COM technology. This standard makes possible interoperability
between automation/control applications, field systems/devices and business/office
applications.
Avoiding the traditional requirement of software/application developers to write custom
drivers to exchange data with field devices, OPC defines a common, high-performance
interface that permits this work to be done once, and then easily reused by HMI, SCADA,
control and custom applications. Over the network, OPC uses DCOM (Distributed COM)
for remote communications.
SuiteLink
SuiteLink uses a TCP/IP-based protocol and is designed specifically to meet industrial
needs such as data integrity, high throughput, and easier diagnostics. This TCP/IP
standard is supported on Windows NT and Windows NT-technology-based operating
systems (for example, Windows NT, Windows 2000, and Windows XP).
SuiteLink is not a replacement for DDE, FastDDE, or NetDDE. The protocol used
between a client and a server depends on your network connections and configurations.
SuiteLink provides the following features:
• Value Time Quality (VTQ) places a time stamp and quality indicator on all data values
delivered to VTQ-aware clients.
• Extensive diagnostics of the data throughput, server loading, computer resource
consumption, and network transport are made accessible through the operating system’s
performance monitor. This feature is critical for the operation and maintenance of
distributed industrial networks.
• Consistent high data volumes can be maintained between applications regardless if the
applications are on a single node or distributed over a large node count.
• The network transport protocol is TCP/IP using Microsoft’s standard WinSock interface.

Klinkmann Automation Omron Ethernet DAServer 4
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
FastDDE
FastDDE provides a means of packing many proprietary Wonderware Dynamic Data
Exchange messages into a single Microsoft DDE message. This packing improves
efficiency and performance by reducing the total number of DDE transactions required
between a client and a server.
Although Wonderware's FastDDE has extended the usefulness of DDE for our industry,
this extension is being pushed to its performance constraints in distributed environments.
DDE
DDE is a communications protocol developed by Microsoft to allow applications in the
Windows environment to send/receive data and instructions to/from each other. It
implements a Client/Server relationship between two concurrently running applications.
The server application provides the data and accepts requests from any other application
interested in its data. Requesting applications are called clients. Some applications such
as InTouch and Microsoft Excel can simultaneously be both a client and a server.
NetDDE
NetDDE is a communications protocol that extends the standard DDE functionality to
include communications over local area networks and through serial ports. Network
extensions are available to allow DDE links between applications running on different
computers connected via networks or modems.
For example, NetDDE supports DDE between applications running on IBM-compatible
computers connected via LAN or modem, and DDE-aware applications running on non-
IBM-compatible computers under operating environments such as VMS and UNIX.
FINS Message Communication
The FINS Messages system is developed by OMRON for its Factory Automation
networks. FINS Communications allow PLCs on these networks to be controlled by
reading and/or writing memory area data without the need to program these operations
into the controller’s user program.
Accessing Items via the DAServer
The method for accessing items through the DAServer depends on the communications
protocol being used.
OPC
In the case of OPC communications, the protocol addresses an element of data in a
conversation with six characteristics: node name, program name, group name, device
group, link name, and item name.
• The node name (required for remote access) and device group are optional.
• A fully qualified OPC Item name (ItemID) is composed of the link name and item name.
• All other characteristics are specified through separate DAServer means.

Klinkmann Automation Omron Ethernet DAServer 5
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
To access an OPC item, the OPC client needs to connect to the DAServer (either in-
process or out-of-process) and create an OPC group defining the data-acquisition
properties for the collection of items to be added. OPC groups
can be either public or private. Public OPC groups are shared across multiple clients,
whereas private OPC groups are local to a single client. Optionally, a device group, which
indicates the access path to the items for read/write, can
be specified from the DAServer.
The following briefly describes each characteristic of the OPC protocol:
• node name: Computer (host) name identifying a specific node on the network (for
Remote Access ONLY).
• program name: The registered OPC server name uniquely identifying a specific server
(ProgID). For this DAServer, the program name is ArchestrA.OmronEth.1.
• group name: The OPC group created from the client for organizing a collection of items
logically with the same data acquisition properties between the client and the server, such
as update rate.
• device group: Meaningful names configured in the DAServer under a specific controller
for the common custom attributes between the DAServer and the device, such as update
interval. If not specified from the client, the default device group using the global
configuration attribute values from the DAServer is assumed. Functionally, a device group
is equivalent to an access path (optional).
• link name: The set of hierarchy node names, representing the specific devices on a
communications path link from the hierarchy root to a specific controller as configured for
this DAServer under the DAServer Manager, separated by delimiters.
• item name: A specific data element, the leaf of the hierarchy tree of this DAServer,
within the specified group. For example, when using this DAServer, an item can be a
relay, timer, counter, register, and so on, in the controller.
DDE/SuiteLink
In the case of DDE/SuiteLink communications, the protocol addresses an element of data
in a conversation that uses a four-part naming convention that includes the node name,
application name, topic name, and item name. The fully qualified DDE/SuiteLink naming
convention includes all four parts, although the node name part (required for remote
access only) is optional. The following briefly describes each portion of this naming
convention:
• node name: Computer (host) name identifying a specific node on the network (for
Remote Access ONLY).
• application name: The name of the Windows program (this DAServer) that will be
accessing the data element. In the case of data coming from or going to the Modicon
devices via the DDE/SuiteLink PlugIn of this DAServer, the application name portion of
the address is DASOmronEth.

Klinkmann Automation Omron Ethernet DAServer 6
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
• topic name: Meaningful names are configured in the DAServer to identify specific
devices. These names are then used as the topic names in all conversations with that
device. For example, OmronPLC. Topic name maps to a device group defined in the
DAServer.
Note: You can define multiple device-group (topic) names for the same device (PLC) to
poll different points at different rates.
• item name: A specific data element within the specified topic. For example, when using
this DAServer, an item can be a relay, timer, counter, register, and so on, in the PLC.
Note: The term "point" is used interchangeably with the term "item" in this user's guide.
For more information on item/point names, see the Item Names section of this user's
guide.
Features
The KLINKMANN OMRON Ethernet Direct DAServer provides the following features:
• The ability to communicate over multiple application-level protocols at the same time.
• The ability to add new application-level protocols on the fly.
• The ability to be configured remotely.
• New, robust diagnostic abilities.
For more in-depth information on the DAServer architecture, see the Reference section.
Demo Mode
Demo Mode allows you to test the functionality of the OMRON Ethernet Direct DAServer
(with all features enabled) for 60 minutes. To use OMRON Ethernet Direct DAServer in
unlimited mode, the HASP key or Software License Key is needed.
The HASP key is the USB or parallel key (dongle) to be installed into PC USB or parallel
port and needs the HASP Device Driver to be installed on same computer. The Software
License Key is16-character alphanumeric “computer-dependent” string, provided after
purchasing the OMRON Ethernet Direct DAServer (for more information, see “Enabling
Software License Key for DASOmronEth” section later in this manual.
Without HASP key installed or Software License Key entered, the OMRON Ethernet
Direct DAServer will run 1-hour in demo mode with all features supported - after 1-hour
DAServer stops the updating read/write on all device items and will reject the addition of
any new items, but connected Clients can continue to function normally (for example, you
can still add or remove an item, but its value is not updated).
After purchasing the OMRON Ethernet Direct DAServer, the appropriate HASP key or
Software License Key is provided and no re-installation of DASOmronEth is needed.
Notes:
1. Unlike the previous OMRON Ethernet Direct DAServer versions (up to v1.18), the
HASP Device Driver should be installed separately – as its installation is not included and
not performed during the OMRON Ethernet Direct DAServer setup. The HASP Device
Driver installation (“HASP Device Driver v4.99 for MS Windows 9x / ME / NT4 / 2000 / XP

Klinkmann Automation Omron Ethernet DAServer 7
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
/2003 installation package, Commandline Installation”) can be obtained from Klinkmann
software downloads page:
http://www.klinkmann.com/automation/klinkmann-software-products/communication-
software-products-prices/
and it is located in “Additional and service software” section.
2. The $SYS$Licensed system item value with OMRON Ethernet Direct DAServer is not
relevant.

Klinkmann Automation Omron Ethernet DAServer 8
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
CHAPTER 2
Before starting the OMRON Ethernet DAServer
This chapter contains instructions how to configure OMRON PLCs to be accessible by
Omron Ethernet DAServer in OMRON Ethernet FA network.
Configuration example deals with local network. If data are to be accessed from remote
networks then Relay Network Tables must be additionally configured in the PLC.
Contents
•Preparing the Hardware to be Used with Omron Ethernet DAServer
•Ethernet Unit Configuration Example for CS1 PLC
•Example program for sending “unsolicited” data from PLC
Preparing the Hardware to be used with OMRON Ethernet
DAServer
The Omron Ethernet DAServer requires an Ethernet card and TCP/IP protocol supporting
Windows Sockets interface to be installed on the computer to communicate with the
OMRON PLCs over the Ethernet network.
Each connected OMRON Controller (with Ethernet Unit installed) must be configured to
allow it to function as a node on the Ethernet network. This setup can be done by
switches on the module and/or appropriate programming software.
The OMRON C200HX/C200HG/C200HE PLCs (except CPU11), CV-series PLCs, CS1
PLCs as well as CJ1 PLCs can be used as nodes on Ethernet network. The
C200HX/C200HG/C200HE PLCs must be supplied with communication module:
C200HW-PCS01-EV1 Ethernet Set or C200HW-PCU01 PC Card Unit supplied with the
Ethernet PC Card (e.g. Kingston T.C. EtheRxEthernet PC Card models: KNE-PCM/M –
for coaxial and twisted pair connection, KNE-PCM/T – for twisted pair connection).
The CS1-series PLCs must be supplied with CS1W-ETN01 Ethernet Unit.
The CJ1-series PLCs must be supplied with CJ1W-ETN11 Ethernet Unit.
The CV-series PLCs must be supplied with CV500-ETN01 communication module.
The Ethernet PC Card installed in the C200HW-PCU01 PC Card Unit in the
C200HX/C200HG/C200HE PLC is configured by software supplied with communication
hardware.
Node number and Unit number of CV500-ETN01 (in CV-series PLC) is set by rotary
switches on the module. Software (CVSS software, SYSWIN or CX-Programmer) is used
to configure IP Address, Routing tables and IP Address tables.
Node number and Unit number of CS1W-ETN01 Ethernet Unit (in CS1-series PLC) is set
by rotary switches on the front side of module. Local IP Address is set by switches SW1,
SW2, ..., SW8 on the back side of module. Software (CX-Programmer) is used to
configure Routing tables and IP Address tables.
Node number and Unit number of CJ1W-ETN11 Ethernet Unit (in CJ1-series PLC) is set
by rotary switches on the front side of module. Software (CX-Programmer) is used to
configure Routing tables, local IP Address and IP Address tables.

Klinkmann Automation Omron Ethernet DAServer 9
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
Configuration software tool, appropriate (and recommended) for all OMRON controllers is
OMRON CX-Programmer Windows Programing Software (see “OMRON CX-Programmer
Users Manual”) .
Ethernet Unit Configuration Example for CS1 PLC
Connect the computer to the PLC CPU unit with Host Link Cable. Install the CX-
Programmer software.
Set IP Address table. Start CX-Programmer (from Start menu: Start/.../CX-
Programmer/CX-Programmer). Create new project (option "New" in CX-Programmer's
system menu). The "Change PLC" dialog box appears.
Enter PLC's name in the project (e.g. default name NewPLC1), PLC's model (e.g. CS1G)
and set the communication type used to access the configured PLC (SYSMAC WAY - for
serial communication).
Press "Work Online" pushbutton (or Ctrl+W) to establish communication to the PLC. (The
same can be done the following: in treeview (on CX-Programmer main window) select the
PLC (in example "NewPLC1(CS1G) Offline") and click the mouse right button. The PLC's
menu appears. Click "Work Online".)

Klinkmann Automation Omron Ethernet DAServer 10
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
When CX-Programmer establishes communication with PLC, select "Operating Mode"
(from PLC's menu) and set "Program" mode.
Note:
If you do not know (or have forgotten) the communication settings currently configured in
the PLC, the Auto Online feature can be useful – from CX-Programmer’s main menu
select “PLC/Auto Online/Auto Online” and CX-Programmer will search for all possible
settings until the proper ones are found; after that the current PLC program will be
automatically uploaded to CX-Programmer and it will go to online state with operating
mode set "Program" mode.
Double-click on "IO Table" in treeview. The "PLC IO Table - NewPLC1" dialog box
appears. Select "Options" and click "Transfer from the PLC":

Klinkmann Automation Omron Ethernet DAServer 11
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
When IO Table is received, display the slot list under Main Rack (press "+" button in the
"PLC IO Table - NewPLC1" dialog box). Select "Ethernet Unit(ET)(0)" and press the
mouse right button. The Ethernet Unit menu appears:

Klinkmann Automation Omron Ethernet DAServer 12
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
Click "Unit Setup". The "Ethernet Unit CPU Bus Unit" dialog box appears:

Klinkmann Automation Omron Ethernet DAServer 13
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
Enter Address Conversion type, FINS UDP port number and Sub-net Mask.
Edit the IP Address Table: the computer where Omron Ethernet DAServer is running
must be added to the IP Address Table. To add it, press "Insert" button. The "Insert
Router's IP Address" dialog box appears:
Enter the Node Number (in example 55) matching to the last octet in IP Address of
computer where Omron Ethernet DAServer is running. Enter the IP Address of computer
where Omron Ethernet DAServer is running (in example 195.2.103.55). Press "Ok".
Insert the Node Number and IP Address of PLC. (In case of CS1-series PLCs the Node
Number must match with settings on the rotary switch on the front side of Ethernet
communication unit, IP Address – must match with settings of rotary switches on the back
side of Ethernet communication unit).

Klinkmann Automation Omron Ethernet DAServer 14
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
To complete the configuration: from the "Ethernet Unit CPU Bus Unit" (or from the "PLC
IO Table - NewPLC1") dialog box select "Options" and click "Transfer to PLC".
Example program for sending “unsolicited” data from PLC
The PLC example program presented in Plcprg.cxp project incorporates the SEND(090)
instruction for transferring unsolicited data from PLC to the OMRON ETHERNET
DAServer (for programming details see SYSMAC CS1 Series CS1W-ETN01 Ethernet
Unit OPERATION MANUAL, section 5).
The program transfers 10 words of data from D10 (notation in ladder diagram - D00010)
from the PLC to the OMRON ETHERNET Server (into address D500). The computer
where Omron Ethernet DAServer is running has the IP Address: 195.2.103.55 and the
destination node number is assigned to 55 (37 in hex).
Comments on example program ladder diagram:
(0) Periodically (once per second) the execution condition flag CIO 000000 turns ON.
Note: There can be different logic to turn ON execution condition flag in real
application.
(1) If the Communication Port Enabled Flag for port 7 is ON, the send execution program
will start when the execution condition flag CIO 000000 turns ON. Input CIO 120000
remains ON from the start of SEND execution until completion. Note: The CS1-series
CPU Unit’s Communication Port Enabled Flags are allocated the following way - in Word
A202: Bit 0 – is associated with Port 0, Bit 1 – is associated with Port 1, … , Bit 7 – is
associated with Port 7. Bit’s status OFF - means execution enabled, ON – means
execution disabled.
(2) Control data (D0, D1, … D4) creation
Word Contents Meaning
D0000 00 0A Number of send words = 10
D0001 00 00 Destination network number = 0 (local
network)
D0002 37 00 Destination node number = 55 (37 hex)
Destination unit address = 0
D0003 87 05 Response not required
Communication port No = 7
Number of retries = 5
D0004 00 64 Response monitor time = 10 s
Ten words with data from D10 from PLC are sent to D500 onwards on the local network,
node number 55, unit address 0 (the computer where Omron Ethernet DAServer is
running) – to receive all these data the items with addresses D500…D509 can be
correspondingly activated for Omron Ethernet DAServer.
Important! With current example program an application will periodically toggle values of
areas D500…D509 with values of areas D10…D19. This is because of DAServer time-

Klinkmann Automation Omron Ethernet DAServer 15
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
by-time poll area D500…D509 and time-by-time gets unsolicited command assigning to
items D500…D509 values of PLCs D10…D19 area. Even if corresponding Controller is
configured to be processed in slave mode – at communication start-up DAServer process
several general data reading commands, accessing toggle effect.
If your application does not need toggling effect – configure SEND(090) instruction so,
that source area matches to destination area. In example – source data must start at
D500, if data are sent to D500 onwards.
(3) Reset the Input creation.
(4) Turn ON error information flag CIO 001300 if error happens. In this case CIO 001300
is not mandatory; any other flag may be used. Note: The CS1-series CPU Unit’s
Communication Port Error Flags are allocated the following - in Word A219: Bit 0 – is
associated with Port 0, Bit 1 – is associated with Port 1, … , Bit 7 – is associated with
Port 7. Bit’s status OFF - means Normal completion, ON – means Abnormal completion.
(5) The end of example program.
The example program ladder diagram is following:

Klinkmann Automation Omron Ethernet DAServer 16
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14

Klinkmann Automation Omron Ethernet DAServer 17
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
CHAPTER 3
Configuration
Once the KLINKMANN Omron Ethernet DAServer has been installed, a small amount of
configuration is required. This configuration is performed using the DAServer Manager
hosted in the System Management Console after it is started through the Programs
menu of the Windows Start button.
Before the DAServer is activated, the device hierarchy, simulating the physical hardware
layout, must first be built to establish communications to each of the controllers. Once the
Omron Ethernet hierarchy has been built, the respective devices for communications can
be configured. Finally, the desired Device Groups for each controller may be created.
Note: To run the Omron Ethernet DAServer as a service, use the context menu on the
DAServer name and select “Configure As Service”. You can configure it as an auto
service or manual service. For more information about configuring your DAServer as a
service, see the “Activation/Deactivation/Service Component” of the DAServer Manager
documentation.
Contents
• Getting Started Quickly with the DAServer
• Configuring the DAServer
• Configuring Device Group Definitions
• Configuring Device Item Definitions
• Hot Configuration
Getting Started Quickly with the DAServer
This section briefly describes the procedures required to prepare the Omron Ethernet
DAServer for use. Detailed descriptions of each step can be found in later sections of this
documentation. This section is intended for people who are familiar with DAServers.
Note: If you are not familiar with DAServer functionality, please proceed to the more-
detailed procedures following this section.
The following procedures assume that you have:
• Configured the PLC with which you wish to communicate.
To prepare the Omron Ethernet DAServer
1. Install the KLINKMANN Omron Ethernet DAServer on Windows by running the
Setup.exe program.
Note: DAServer installation instructions are included in a separate Help file (.chm
extension).
• Accept all the default settings during the installation.
Important! Since there are no default values for security settings, you must take note of
the user name and password selected during the install.
2. Start the Wonderware DAServer Manager by selecting the Programs menu from the
Start button on the taskbar.
3. Navigate to the Wonderware folder that contains the System Management Console,
then click System Management Console.

Klinkmann Automation Omron Ethernet DAServer 18
Omron Ethernet DAServer Ver 1.x User Manual Rev 1.4 17014m14
4. From the System Management Console, find the Omron Ethernet DAServer in the
DAServer Manager tree, the location in which it is installed.
• Under the Local branch node, the name of the DAServer is
Archestra.DASOmronEth.1.
• See the DAServer Manager documentation for general information about working in this
snap-in environment.
5. The new Omron Ethernet DAServer must now be configured.
• Before proceeding, determine the hierarchical structure of the network/PLC environment
to which you plan to connect.
6. Right-click the Configuration object that already exists in the tree, and select Add
SOCKET Object from the shortcut menu.
• A new SOCKET object is created as a node in the hierarchy tree and is named
New_SOCKET_000 by default.
• In this step, in addition to Step 7, the hierarchy entry is added in "edit mode," providing a
convenient place for you to appropriately describe components of your specific hardware
environment.
• If you do not rename the object at this time, a numeric sequencing system is applied.
• Any hierarchy entry can be renamed at a later time.
7. Right-click on the new SOCKET object, and from the shortcut menu, select
Add CONTROLLER Object
8. Configure the respective device objects, created in the preceding steps, with the
appropriate parameter values, if applicable.
• Optionally, the desired device groups can be created under the Device Groups tabbed
page with each of the Controller objects.
• Desired device items can also be optionally created under the Device Items tabbed
page with each of the Controller objects.
Note: The hierarchy entry is added in the "edit mode," providing a convenient place for
you to appropriately describe components of your specific hardware environment. Both
hierarchy node name and device group name are numerically sequenced by default.
They can be renamed at any time.
The DAServer is now ready for use. In order to use the DAServer, you must activate it
from the DAServer Manager using either the shortcut menu’s Activate Server command
from the Archestra.DASOmronEth.1 node, or from OPC Client.
Note: To run the Omron Ethernet DAServer as a service, right-click on the DAServer
name and select Configure As Service from the shortcut menu. You can configure it as
an auto service or manual service. For more information about configuring your DAServer
as a service, see the Activation/Deactivation/Service Component of the DAServer
Manager documentation.
Configuring the DAServer
Note: This DAServer is hosted by DAServer Manager, a Microsoft Management Console
(MMC) snap-in, which is a part of the ArchestrA System Management Console (SMC)
suite of utilities. Many high-level functions and user-interface elements of the DAServer
Manager are universal to all DAServers, and only the documentation for the DAServer
Manager contains descriptions of those universal functions/UI elements. Therefore,
reading the documentation for both the MMC and the DAServer Manager is critical to
understanding this user’s guide. To read the documentation about the MMC and