omronfgv communication server - klinkmannmedia.klinkmann.com/servers/docs/400xxm16.pdf · ethernet...

OMRONFGV

Communication

Server

for Microsoft Windows and InTouch Applications

User Manual

Ver 1.x Rev 1.6

DR 400 10

DR 400 11

KLINKMANN OY P.O. Box 38

FIN-00371 Helsinki Finland tel. int. + 358 9 5404940 fax int. + 358 9 5413541

www.klinkmann.com

Klinkmann OMRONFGV Communication Server i

OMRONFGV Communication Server Ver 1.x User Manual Rev 1.6 400XXM16

Table Of Contents

Overview ........................................................................................................................ 1 Network Environment and Conditions ............................................................................ 2

Communication Protocols .............................................................................................. 3 Accessing Remote Items via the Server ........................................................................ 4 Getting Started Quickly with OMRONFGV Server ......................................................... 5

Ethernet Communication ............................................................................................ 6 Preparing the OMRON PLC to be used on Ethernet network ................................. 6

Configuring FinsGateway to access the Ethernet ................................................... 7 Ethernet Unit configuration example of CV-series PLC using SYSWIN .................. 12 Ethernet Unit configuration example of CS1-series PLC using CX-Programmer ............................................................................................................ 14 Conditions to Start OMRONFGV Server ................................................................. 22

Controller Link ............................................................................................................ 24

Preparing the OMRON PLC to be used on Controller Link network........................ 24 Installing the OMRON Controller Link Support Board ............................................. 25 Installing the OMRON 3G8F5-CLK21-E Controller Link Support Software ............. 25

Configuring the Controller Link network .................................................................. 26 Checking if PLC is accessible ................................................................................. 26

Enabling the Routing Table Enable Bit ................................................................... 26

Creating and Transferring the Routing Tables ........................................................ 27

Configuring FinsGateway to Access Controller Link Network ................................. 28 Conditions to Start OMRONFGV Server ................................................................. 32

SYSMAC LINK ........................................................................................................... 33 Preparing the OMRON PLC to be used on SYSMAC LINK network ....................... 33 Installing the OMRON SYSMAC LINK Support Board ............................................ 33

SYSMAC LINK Unit configuration for CV-series PLC with SYSWIN ....................... 34 Configuring FinsGateway to Access SYSMAC LINK Network ................................ 35

Conditions to Start OMRONFGV Server ................................................................. 38 Serial Communication ................................................................................................ 39

Preparing the OMRON PLC to be used on Serial network ..................................... 39

Configuring CV-series PLC’s Serial Communication by FinsGateway .................... 39 Conditions to Start OMRONFGV Server ................................................................. 44

SYSMAC Board .......................................................................................................... 44

Installing the OMRON SYSMAC Board ................................................................... 45 Configuring FinsGateway to Access SYSMAC Board ............................................. 45

Event Memory ............................................................................................................ 50 Installing the OMRONFGV Server ................................................................................. 51

Installing the Server .................................................................................................... 51

Licensing by using HASP HL key ............................................................................... 54 Software license key ................................................................................................... 54 Transferring the software license to other computer .................................................. 55 Installing the I/O Server Infrastructure ........................................................................ 56

Configuring the OMRONFGV Server ............................................................................. 57 Server Settings Command ......................................................................................... 57 Server Unit Configuration Command .......................................................................... 59

Klinkmann OMRONFGV Communication Server ii


Saving OMRONFGV Configuration File ..................................................................... 60 Configuration File Location ......................................................................................... 60 Topic Definition Command ......................................................................................... 61

Item Names .................................................................................................................... 67

C200HX/C200HG/C200HE PLCs and SYSMAC Board ............................................. 70 CV-series PLCs .......................................................................................................... 72 C/CPM2x PLCs .......................................................................................................... 77 CS1/CJ1 PLCs ........................................................................................................... 80 CQM1 PLCs ............................................................................................................... 82

Event Memory ............................................................................................................ 83 Data Presentation in Text String Items ....................................................................... 85 Monitoring and Controlling Communication with a PLC ............................................. 86

Using the OMRONFGV Server with OPC Clients .......................................................... 89 Configuring DCOM ..................................................................................................... 89 Running OMRONFGV "OPC & DDE" version as Windows NT Service ..................... 91 Using OMRONFGV with OPCLink Server .................................................................. 92

OPCLink Topic Definition ........................................................................................ 92

Accessing OMRONFGV Items via the OPCLink Server .......................................... 93 Using the OMRONFGV Server with Suite Link and DDE Clients ................................... 94 Using the OMRONFGV Server with InTouch ................................................................. 94

Defining the Access Names ....................................................................................... 94 Defining the Tag names ............................................................................................. 96 Monitoring the Status of Communication with InTouch .............................................. 98

Notes on Using Microsoft Excel ..................................................................................... 99

Reading Values into Excel Spreadsheets................................................................... 99 Writing Values to OMRONFGV Points ....................................................................... 99

Notes on Improving Server Performance ....................................................................... 101

Troubleshooting ............................................................................................................. 103 WIN.INI entries ........................................................................................................... 103

Troubleshooting menu ................................................................................................ 106

Klinkmann OMRONFGV Communication Server 1


OMRONFGV

Communication Server

Overview The OMRON FinsGateway Communication Server (hereafter referred to as the "OMRONFGV Server" or "OMRONFGV" or "Server") is a Microsoft Windows 32-bit application program, which can be used on Windows 7 32-bit, and acts as a FINS message communications protocol Server and allows other Windows application programs access to data from OMRON PLCs over the following OMRON FA (Factory Automation) networks: - Ethernet (ETN_UNIT), - Controller Link, - SYSMAC LINK, - Serial Unit, - SYSMAC Board, - SYSMAC NET. Depending on network type the Server can access to data from C200HX/C200HG/C200HE PLCs, CV-series PLCs, C-series PLCs, CPM2x PLCs, CS1-series PLCs, CJ1 PLCs as well as CQM1 PLCs directly (from the network common to the PC and the PLC) or inter-networked from other OMRON FA networks. The Server also accesses data from SYSMAC Board (e.g. C200PC-ISA02-DRM-E) installed on the host computer. Explanation of environment and conditions necessary for each network see in chapters Network Environment and Conditions and Getting started quickly with OMRONFGV Server. The Server can access data simultaneously from different OMRON FA networks. The OMRONFGV Communication Server supports PLC data and memory areas accessible by FINS commands. The OMRONFGV Server also access data in FinsGateway EventMemory. The OMRON FinsGateway software must be installed on MS Windows (NT, 2000 or XP) to run the OMRONFGV Server. The Server may be used by any Microsoft Windows program that is capable of acting as a DDE, FastDDE, SuiteLink or OPC Client. There are two different OMRONFGV Server versions described in this manual: - Server version (ordering number DR 400 10), supporting SuiteLink, FastDDE and

DDE protocols; this version hereafter is referred to as the "Suite Link & DDE" version. - Server version (ordering number DR 400 11), supporting OPC and DDE protocols; this

version hereafter is referred to as the "OPC & DDE" version; The separate installation package is supplied for each version of the Server. In all cases

the name of Server executable file is OMRONFGV.EXE. All further information in this manual is same for all versions of the Server, with the exception of few points where communication protocol specific features are explained.



Network Environment and Conditions The following are environments and conditions necessary for each OMRON FA network as well as PLC types accessible by OMRONFGV Server in each network:

- ETN_UNIT (Ethernet)

Requires an Ethernet Board (which can be used with Windows NT, 2000 or XP) connected to Ethernet network. TCP/IP must be installed. (FINS communication on the Ethernet uses UDP/IP, TCP/IP is included in Windows NT, 2000 or XP). Fixed IP address must be allocated. Cannot be used on a system with DHCP configuration, because the Ethernet unit requires a static IP address. The Server can access to data from C200HX/C200HG/C200HE, CV-series and CS1/CJ1 PLCs (directly from Ethernet network or inter-networked from other OMRON FA networks) as well as from C-series, CQM1 PLCs (only inter-networked from other OMRON FA networks).

- Controller Link

Requires an OMRON Controller Link Support Board (i.e. 3G8F5-CLK21) or OMRON

Controller Link PCI Support Board (i.e., 3G8F7-CLK21) connected to OMRON Controller Link network. Only one Controller Link Support Board 3G8F5-CLK21 can be installed in one computer. Up to four Controller Link PCI Support Boards 3G8F7-CLK21 can be installed in one computer. The Server can access to data from C200HX/C200HG/C200HE, CV-series, CS1/CJ1 PLCs and CQM1 PLCs (directly from Controller Link network or inter-networked from other OMRON FA networks) as well as from C-series PLCs (only inter-networked from other OMRON FA networks).

- SYSMAC LINK

Requires an OMRON SYSMAC LINK Support Board (i.e. 3G8F5-SLK21) or OMRON

SYSMAC LINK PCI Support Board (i.e., 3G8F7-SLK21) connected to OMRON SYSMAC LINK network. Only one SYSMAC LINK Support Board 3G8F5-SLK21 can be installed in one computer. Up to four SYSMAC LINK PCI Support Boards 3G8F7-SLK21 can be installed in one computer. The network gateway function cannot run. The Server can access to data from C200HX/C200HG/C200HE, CV-series, C-series and CS1 PLCs (directly from SYSMAC LINK network or inter-networked from other OMRON FA networks), as well as from CJ1 and CQM1 PLCs (only inter-networked from other OMRON FA networks).

- Serial Unit Requires a PC 95-compliant COM port. The COM port must be used exclusively by FinsGateway. Other application not using FinsGateway cannot use the COM port simultaneously. COM ports that can be specified by the serial communication of FinsGateway are COM1 to COM4.



Data from C200HX/C200HG/C200HE, CV-series, C-series, CPM2x, CS1/CJ1 as well as CQM1 PLCs can be accessed directly or inter-networked from other OMRON FA networks.

- SYSMAC Board

Requires an OMRON SYSMAC Board (C200PC-ISA-01-DRM or other). With the following network the OMRONFGV Server has not been tested:

- SYSMAC NET

Requires an OMRON SYSMAC NET Support Board (e.g. 3G8F5-SNT31) connected to OMRON SYSMAC NET LINK network.

Communication Protocols Dynamic Data Exchange (DDE) is a communication 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 Wonderware InTouch and Microsoft Excel can simultaneously be both a client and a server.

FastDDE provides a means of packing many proprietary Wonderware DDE 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, this extension is being pushed to its performance constraints in distributed environments. The OMRONFGV Communication Server supports the FastDDE Version 3 - an extension to Wonderware’s proprietary FastDDE Version 2. This extension supports the transfer of Value Time Quality (VTQ) information. The original DDE and FastDDE Version 2 formats are still supported, providing full backward compatibility with older DDE clients. FastDDE Version 3 works on Windows 9x systems as well as Windows NT systems.

NetDDE extends the standard Windows DDE functionality to include communication 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-PC based platforms under operating environments such as VMS and UNIX.

SuiteLink uses a TCP/IP based protocol and is designed by Wonderware specifically to meet industrial needs such as data integrity, high-throughput, and easier diagnostics. This protocol standard is only supported on Microsoft Windows NT 4.0 or higher. 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 was designed to be the industrial data network distribution standard and 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 Microsoft Windows NT operating system Performance Monitor. This feature is critical for the scheme 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.

OPC (OLE for Process Control) is an open interface standard to provide data from a data source and communicate the data to any client application in a common standard way. The OPC is based on Microsoft OLE, COM and DCOM technologies and enables simple and standardized data interchange between the industrial or office sector and the production sector. From general point of view many aspects of OPC are similar to DDE, but main difference is in the implementation by using Microsoft's COM (Component Object Model) technology. It enables fast exchange with process automation data and OPC open interface allows access to data from OPC Server in same standard way from OPC client applications supplied by different developers. For more information on the basics of OPC, please refer to the OPC Specification. The OPC Data Access Custom Interface Specification is maintained by OPC Foundation, the current specification is 2.04 dated September 2000. The OPC support for OMRONFGV Server “OPC & DDE” version is implemented based on FactorySoft OPC Server Development Toolkit and it conforms to OPC Data Access Custom Interface Specification 2.04. The OMRONFGV Server “OPC & DDE” version is tested for compliance and is compatible with OPC Foundation OPC Data Access Compliance Test Tool. The Suite Link, FastDDE (Version 3) and DDE support for OMRONFGV Server "Suite Link & DDE" version is implemented by Wonderware I/O Server Toolkit ver. 7.0 (060). The FastDDE (Version 2) and DDE support for OMRONFGV Server "OPC & DDE" version is implemented by Wonderware I/O Server Toolkit ver. 5.0 (008).

Accessing Remote Items via the Server The communication protocol addresses an element of data in a conversation that uses a three-part naming convention that includes the application name, topic name and item name. The following briefly describes each portion of this naming convention: application name The name of the Windows program (server) that will be accessing the data element. In the case of data coming from or going to OMRON Controllers via this Server, the

application portion of the address is OMRONFGV.



topic name Meaningful names are configured in the Server to identify specific devices (PLCs). These names are then used as the topic name in all conversations to that PLC. The OMRONFGV Server considers each node within an OMRON FA network to be a

separate topic. For example, node2.

Note! You can define multiple topic names for the same PLC to poll different points at different rates and/or through different FA networks. item name A specific data element within the specified topic. When using the OMRONFGV Server, an item can be a relay, timer, counter, register, etc., in the PLC. The term "point" is used interchangeably with the term "item" in this User Manual. For more information on item/point names, see the Item Names section later in this manual.

Getting Started Quickly with OMRONFGV Server This section contains some instructions how to quickly prepare the OMRON FA networks hardware and necessary software to be ready for OMRONFGV Communication Server to run. The section does not give sufficient information about each FA network installation; User’s Manual of corresponding network should be investigated in addition. These instructions illustrate correspondence of FA networks configuration parameters and OMRONFGV Server configuration parameters. Configuration of each network is explained in a separate chapter. The one principal is taken into account configuring each network - if data are to be accessed from only one FA network then network number 0 (local network) can be configured. If data are to be accessed simultaneously from several FA networks then network number 0 is not useful. A unique (non-zero) number must be assigned to each FA network. Numbers of network, node and unit are given in the following explanation as example, not mandatory. All configuration examples illustrate local networks. If data are to be accessed from remote networks then Relay Network Tables must be configured in PLCs in addition to Local Network Tables and FinsGateway FINS Route Viewer must be used to configure

remote network access by FinsGateway.

The OMRONFGV Server will not work if OMRON FinsGateway is not installed on the

same computer. The FinsGateway is supplied on CD-ROM and it can be purchased from your local OMRON distributor. The current version of OMRONFGV Server has been tested with FinsGateway Version 2 Runtime Edition for Windows NT 4.0, FinsGateway Version 2.1 and FinsGateway Version 3. Refer to OMRON FinsGateway Help on details

how to install and configure the FinsGateway.

The proper functioning of FinsGateway Services can be tested by FinsGateway Network

Tester utility. Note: FinsGateway does not work properly if WINRT drivers are installed and started on

the same computer. Stop WINRT drivers to access FinsGateway communication.

If FinsGateway is installed and FA network(s) are functioning then OMRONFGV Server can be installed and started.



Ethernet Communication The OMRONFGV Server 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. FinsGateway software must be installed and

CPU_UNIT and ETN_UNIT FinsGateway Services must be started and ETN_UNIT must be configured. Each connected OMRON Controller (with Ethernet Unit installed) must be configured to allow it to function as a node in the Ethernet network. This setup can be done by switches on the module and/or appropriate programming software: - Ethernet Unit configuration for CV-series PLCs can be processed by Programming

Device running CVSS software (see "SYSMAC CV-series Ethernet System Manual" and "CV Support Software Operation Manual" for details of actual setting operations).

- C200HX/C200HG/C200HE PLC's PC Card Unit with Ethernet PC Card installed can be configured by the OMRON SYSMAC Support Software (see "SYSMAC C200HW-PCU01/C200HW-PCS01-EV1 PC Card Unit Operation Manual”).

- For CS1/CJ1 PLCs configuration - the OMRON CX-Programmer Windows Programming Software (see “CX-Programmer Users Manual” and “SYSMAC CS1 Series CS1W-ETN01 Ethernet Unit Operation Manual”) can be used.

Currently the OMRON CX-Programmer Windows Programming Software is useful for Ethernet Unit configuration for a lot of OMRON PLCs. To prepare the Ethernet network for data accessing by OMRONFGV Server do the following: - install the hardware for Ethernet communication,

- install FinsGateway (if not installed yet), - configure FinsGateway Ethernet drivers, start and configure Ethernet network, - configure Routing tables in the PLC, - configure IP Address table in the PLC (your computer must be presented in the IP

Address table by ETN_UNIT). - Start the OMRONFGV Server and configure Topic(s). When configure Topic in the OMRONFGV Server see configuration parameters (Network

Address, Node Address and Unit Address) in FinsGateway configuration utilities. The following explanation is simplified – when describe Configuring the Ethernet by FinsGateway software then consider, that PLC can be recognized by FinsGateway as Ethernet network node (PLC is already partly configured). The same, when explain Ethernet Unit configuration of CV-series PLC then consider, that ETN_UNIT FinsGateway Service’s configuration parameters are accessible. Really configuration can not be finished completely entering configuration utility the first time.

Preparing the OMRON PLC to be used on Ethernet network 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.

Configuring FinsGateway to access the Ethernet If the PLC is connected to the PC and started then configure FinsGateway Ethernet drivers and start and configure Ethernet network.

Ethernet Driver Settings

In FinsGateway Version 3 FinsGateway Services are accessible from the OMRON

FinsGateway Settings program. Start FinsGateway Service Manager (from Windows

Start menu: Start/Programs/FinsGateway/Service Manager) and then start OMRON

FinsGateway Settings application from Windows Start menu

(Start/Programs/FinsGateway/FinsGateway Configuration) or right-click on FinsGateway

Service Manager icon in the task tray, and select Settings.

In the tree-view on Basic tab pane expand Drivers folder and check ETN_UNIT. Click Properties button on Work pane. The ETN_UNIT Properties dialog box will appear.

Note: In FinsGateway version 2.0 you can not start OMRON FinsGateway Settings program. In this case all utilities (e.g. FINS Network Navigator utility) needed to start/configure ETN_UNIT and other FinsGateway Services are accessible from Windows



Start menu (Start/Programs/FinsGateway/… ) or from the OMRON FinsGateway Service Manager. In the ETN_UNIT Properties utility select "Network" tab and configure Ethernet network parameters:

- Usually there is no reason to change Local node number (in example 100) of your PC

and Communication unit number (in example 17) assigned by FINS Gateway, if only one PC access OMRON PLCs in Ethernet network. If there are more PCs in your network communicating with OMRON PLCs, then you have to assign unique node number for each PC (e.g. assign node number 101 to the second PC, number 102 to the third PC …)

Select "Communication Unit" tab and configure (if necessary) UDP port number and FINS-IP Conversion mode. Usually none of the settings here need to be changed.



Starting Ethernet Network

To start ETN_UNIT - from the FinsGateway Configuration Basic tab click the Services icon and check ETN_UNIT. Press "Start" button in Work pane.



If Status changes from Stopped to Running - ETN_UNIT is started. Check "Networks and Units" icon on the Basic tab of the Control pane and check "Local Network 0 (Ethernet)". Press "Properties" button in Work pane.

The ETN_UNIT Properties dialog box will appear.

In the ETN_UNIT Properties utility select "Network" tab and set Network number (from 0 to 127) you assign to Ethernet network. Zero could be assigned only if PC is installed in only one local network. Network number 3 is assigned to Ethernet in current example.

Select "Nodes" tab.



Press "Add" button to add new PLC node. To change Node number or IP address (if necessary to modify parameters of already entered node) select node and press "Property" button. The Ethernet Node Definition dialog box appears.

Enter PLC’s FINS Node number and IP address you have configured in hardware. Press "OK". If communication with the specified target succeeds, the node description will be displayed in the "Nodes" tab list under Model.



In current example Node number 54 is assigned to the PLC model CV500. Value should match to settings on the rotary switches on the PLC’s communication module. Enter the same value in Node Address option when configure Topic in OMRONFGV Topic Definition dialog box (see chapter Topic Definition Command). Unit number 0 is used for PLCs in Ethernet network.

Ethernet Unit configuration example of CV-series PLC using SYSWIN The SYSWIN software (running in MS Windows 95 or NT) is useful for Ethernet Unit configuration for lot of OMRON PLCs type. The following is a simple example of OMRON CV-series Ethernet Unit System Setup configuration using SYSWIN). Start SYSWIN, set communication (e.g. HostLink) parameters and establish connection to the PLC (follow SYSWIN User Manual). Then enter Ethernet network number in Routing tables and enter computer ETN_UNIT parameters into IP Address table.

Set Routing tables. Start the "Routing Table Setup" dialog box (Project/Routing tables).



Select Routing table type. Enter I/O unit number (in example 1) matching to Unit number on the rotary switches on the module. Enter Network number (in example 3) you assign to Ethernet network (must match to Ethernet network number assigned in FINS Gateway). Press Write button. Note: In current example only one local network is configured. If PLC is included in SYSMAC LINK or other local and/or remote networks then these networks also must be presented in Routing table.

Set IP Address table. Enter Project/Edit I/O table. The "Edit PLC I/O Table" dialog box appears. Press "Read" button. SYSWIN uploads I/O table. In tree-view - check "SIO Units" to see whole tree of I/O units on the PLC. Select "Ethernet Unit (ET)" on the tree-view. Some new dialog options are offered. Press "Unit Setup..." button. The "Ethernet Setup Dialog" box appears.



Set PLCs IP Address, Sub-net Mask, IP Address Conversion method and FINS UDP Port Number. Edit IP Address Table: the ETN_UNIT must be presented in IP Address Table. To enter it press "Edit..." button. The "IP Address Table..." dialog box appears:

enter the Node Number (in example 100) of ETN_UNIT matching to settings in FINS Gateway. Enter computer’s IP Address (in example 192.168.0.4). Press "Insert". Press "Write" in "Ethernet Setup Dialog" box. Close all dialogs.

Ethernet Unit configuration example of CS1-series PLC using CX-

Programmer Ethernet Unit configuration for CS1-series PLCs can be processed by CX-Programmer Windows Programming Software (see “CX-Programmer Users Manual”). Connect the computer to the PLC CPU unit with Host Link Cable. Install 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 project (e.g. default name NewPLC1), PLC's model (e.g. CS1G) and set 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 tree-view (in CX-Programmer main window) select the PLC (in example "NewPLC1(CS1G) Offline") and click mouse right button. PLC's menu appears. Click "Work Online".)



When CX-Programmer establish communication to the PLC select "Operating Mode" (in the PLC's menu) and set "Program" mode. Double-click on "IO Table" in tree-view. The "PLC IO Table - NewPLC1" dialog box appears. Select "Options" and click "Transfer from the PLC".



When IO Table is received, display slot list under Main Rack (press "+" button in the "PLC IO Table - NewPLC1" dialog box). Select "Ethernet Unit(ET)(0)" and press right button. Ethernet Unit menu appears.



Click "Unit Setup". The "Ethernet Unit CPU Bus Unit" dialog box appears.



Enter Address Conversion type, FINS UDP port number and Sub-net Mask. Edit IP Address Table: the ETN_UNIT must be presented in IP Address Table. To enter it press "Insert" button. The "Insert Router's IP Address" dialog box appears.

Enter the Node Number (in example 100) of ETN_UNIT matching to settings in FINS Gateway. Enter computer’s IP Address. Press "Ok". In the "Ethernet Unit CPU Bus Unit" (or in the "PLC IO Table - NewPLC1") dialog box select "Options" and click "Transfer from to PLC".

Set Routing tables. Routing tables are set by CX-NET Network Configuration Tool in online mode. Start CX-NET Network Configuration Tool (from Start menu: Start/.../CX-Server/ CX-NET Network Configuration Tool or from CX-Programmer's menu: Tools/Network Configuration Tool). Create new project (e.g. proj20) (Project/New in CX-NET Network Configuration Tool 's menu).



Enter Project/Add Device. The "Add PLC" dialog box appears.

Enter Device Name in project (e.g. Node20), PLC's model (e.g. CS1G) and set communication type used to access the configured PLC (SYSMAC WAY - for serial communication). Check settings. Press "Ok". Double click on project name (in example - proj20.cdm) and then double click on device name (in example - Node20) (tree-view "Project Devices" in CX-NET Network Configuration Tool 's main window). CX-NET Network Configuration Tool 's main window shows that the computer is connected to the PLC.



Move cursor on PLC drawing and click mouse right button. CX-NET Network Configuration Tool offers pop-up menu: PLC Device/Open. Click on "Open". Now CX-NET Network Configuration Tool is in online mode. Enter Routing Table/Setup option (CX-NET Network Configuration Tool's main window). The "Routing Table Setup" dialog box appears.

Select "Local Table" and press "Edit". The "Routing Table Editor (FINS)" dialog box appears.



Press "Insert Item" button (or select Table/Insert Table Item). The "Add Local Network Item" dialog box appears.

Enter Local Network Number (in current example - 3) and Ethernet Communication Unit Number (in current example - 0) and press "Ok" In the "Routing Table Editor (FINS)" dialog box enter "File" and press "Save". In the "Routing Table Setup" dialog box press "Update" button. Download Routing Tables to the PLC by pressing button "Write". Close PLC Device and exit CX-NET Network Configuration Tool.

Conditions to Start OMRONFGV Server CPU_UNIT and ETN_UNIT FinsGateway Services must be started and running before starting the OMRONFGV Server. The proper functioning of FinsGateway Ethernet

Service (ETN_UNIT) and Ethernet network can be tested by FinsGateway Network

Tester utility. Start utility from FinsGateway Settings application’s menu (Network->FINS Communication Test).



If FinsGateway is installed and Ethernet network is functioning then OMRONFGV Server can be installed and started.

Correspondence between PLC’s Ethernet Unit setup, FinsGateway Services setup and OMRONFGV Server configuration values is the following: - Network Number in Routing tables (in current example 3) matches to Network Number in FinsGateway ETN_UNIT Properties utility and matches to Network Address in "OMRONFGV TOPIC Definition" dialog box (see chapter Topic Definition Command). - Node Number on rotary switches (in current examples 19 and 20) matches to Node Number in SYSWIN dialog boxes, matches to Node Number in FinsGateway ETN_UNIT Properties utility and matches to Node Address in "OMRONFGV TOPIC Definition" dialog box. - Assign 0 to Unit Number in "OMRONFGV TOPIC Definition" dialog box when configure Topic in Controller Link network. Node Number of ETN_UNIT assigned by FINS Gateway matches to Node number of computer in PLC’s IP Address table.



Controller Link The following explanation assumes it is a first time Controller Link network is created. The OMRONFGV Server requires Controller Link Support Board to be installed on the computer to communicate with the OMRON PLCs over the Controller Link network.

FinsGateway software must be installed and CPU_UNIT and CLK_UNIT0 FinsGateway

Services must be started and CLK_UNIT0 must be configured. Each connected OMRON Controller (with Controller Link Unit installed) must be configured to allow it to function as a node in the Controller Link network. This setup can be done by appropriate programming software, such as OMRON CV Support Software (see "SYSMAC C200HW-CLK21/CVM1-CLK21 Controller Link Unit Operation Manual" and "CV Support Software Operation Manual" for details of actual setting operations), or CX-Programmer or SYSWIN. To prepare the Controller Link network for data access by OMRONFGV Server do the following: - install the hardware for Controller Link communication, - configure PLC(s) as Controller Link node(s); set selected Network number into

Routing tables,

- install FinsGateway (if not installed yet), - configure FinsGateway to access Controller Link Network, - start the FinsGateway Controller Link drivers and start and configure Controller Link

network. - Start the OMRONFGV Server and configure Topic(s). When configure Topic in the OMRONFGV Server see configuration parameters (Network

Address, Node Address and Unit Address) in FinsGateway configuration utilities.

Preparing the OMRON PLC to be used on Controller Link network The OMRON C200HX/C200HG/C200HE PLCs, CV-series PLCs, CS1/CJ1 PLCs and CQM1 PLCs can be used as nodes on Controller Link network. The following Controller Link Units are available: C200HW-CLK21 for C200HX/C200HG/C200HE PLCs, CVM1-CLK21 for CV-series PLCs, CS1W-CLK21 for CS1 PLCs, CJ1W-CLK21 for CJ1 PLCs and CQM1H-CLK21 for CQM1 PLCs. For example, the following steps can be done to prepare the C200HW-CLK21 unit on C200HE PLC:

- set the node address 04 on the front rotary switches;

- set the baud rate 2 M (Pin 1 to OFF and Pin2 to OFF) and Operating Level 0 (Pin 4 to ON) on the front DIP switch;

- set the termination resistance on the bottom switch to ON;

- set the Routing Table Enable Bit (bit 12 on DM6400) to 1 (ON); this can be done by peripheral devices used to program OMRON PLCs, e.g. by Programming Console or later by OMRON Controller Link Support Software (see below). Note: If C200HW-CLK21 unit is configured to Operating Level 1 (Pin 4 to OFF on the

front DIP switch) then set to 1 (ON) the Routing Table Enable Bit (bit 12) on DM6420. See the OMRON SYSMAC C200HW-CLK21/ CVM1-CLK21 Controller Link Unit Operation Manual on details how to prepare OMRON PLC to be used on Controller Link network.



Installing the OMRON Controller Link Support Board The following settings must be made on a Controller Link Support Board:

- set the Memory Area address to some value not overlapping with another resource

currently used by computer; for example, use address D8000;

- set the Interrupt Level, e.g. IRQ11; take care if this interrupt is not already used by another resource on the computer;

- set the Termination Resistance to ON. See the OMRON 3G8F5-CLK21-E Controller Link Support Board Operation Manual on details how to install a Controller Link Support Board.

Installing the OMRON 3G8F5-CLK21-E Controller Link Support

Software The Controller Link Support Software can run on MS-DOS or MS Windows 95. So, if your computer supports only MS Windows NT then you must prepare a special MS-DOS bootable floppy where to copy all files from 3G8F5-CLK21-E Controller Link Support Software installation disk and where to made necessary modifications in CONFIG.SYS file. There are two main points to enable the Controller Link Support Software to work: 1. Insert the Controller Link Support Software disk into a floppy drive and run the INSTALL.EXE program (or use the prepared MS-DOS bootable floppy with all necessary files). 2. Include device drivers (Controller Link BIOS (CLKBIOS.SYS) and Controller Link Driver (CLKDRV.SYS) in the CONFIG.SYS. Set the valid parameters for these drivers in CONFIG.SYS. For example, the following parameters can be used:

DEVICE=C:\CLK\CLKBIOS.SYS /AD800 /E /I11 /N1 /U0 /B3 /C2

DEVICE=C:\CLK\CLKDRV.SYS /E /B3 The above parameters mean the following:

For CLKBIOS.SYS:

/AD800 – the leftmost four digits in hexadecimal of the base address of the memory area () that was set using the memory allocation setting switch on the Board;

/E – the device driver startup message will be displayed in English;

/I11 – the interrupt level 11 is used;

/N1 – the node address of the Board on the Controller Link network is 1 (default setting);

/U0 – the unit number of the Board is 0 (default setting);

/B3 – the baud rate 2 Mbps is used (default setting);

/C2 – the XMS memory as a data link cache is used (default setting); For CLKDRV.SYS:

/E – the device driver startup message will be displayed in English;

/B3 – the number of send/receive buffers is 3 (1 send buffer and 2 receive buffers, default setting);



If the device driver or a Board cannot be started due to an error then error message will be displayed. In this case the settings on the Board and device driver parameters must be changed until device drivers are started successfully. See the OMRON 3G8F5-CLK21-E Controller Link Support Board Operation Manual and OMRON C200HW-ZW3AT2-E/3G8F5-CLK21-E Controller Link Support Software Operation Manual on details how to install the Controller Link Support Software.

Configuring the Controller Link network To configure the Controller Link network, start the Controller Link Support Software (CLKSS.BAT or CLK.EXE). If the Support Board is activated normally, the Controller Link Support Software will be automatically connected to Controller Link network nodes when started.

Checking if PLC is accessible The following steps can be done to be sure the node 4 is accessible: - set the "Watchdog Timer" value (if default value 5 seconds is not enough) in "Main menu/I:System setup"; - enter the "Main menu/C:Monitor network"; select the "Network address" equal to 000 and press the F6 (Execute) key - there should be "YES" in "In netwk" column both for nodes 1 and 4; - enter the "Main menu/N:Echoback test" and check if Controller Link Support Software can communicate normally with node 4; - if there are no errors in above tests then quit from Controller Link Support Software by selecting "Main menu/Q:Exit to DOS".

Enabling the Routing Table Enable Bit If the Routing Table Enable Bit (bit 12 on DM6400) is not yet set to 1 (ON) then this can be done now by running the MSCSMPL.EXE (the MS-C sample program, it is located at the \CLK\MSC subdirectory on the Controller Link Support Software installation disk, refer to OMRON 3G8F5-CLK21-E Controller Link Support Board Operation Manual for details). After starting, the following sequence can be executed (the information to be entered by user is underlined, the <CR> means carriage return key): - open the Controller Link driver and add the Support Board to the network: 1<CR> Return value: 0 (everything is O.K., no errors) - to set bit 12 on DM6400 to 1, send the FINS command containing the writing of value 4096 (1000 in hexadecimal) to DM6400: 3<CR> Net (0 – 127): 0<CR> Node (0 – 126,255): 4<CR> Unit (0,1,2): 0<CR> Type (0 – 127): 0<CR> Sid (0 - 255): 0<CR> Length (0 – 2002 byte): 10<CR> Data (0 – 9, a - f): 01028219000000011000<CR> Return value: 0 (everything is O.K., value written without errors)



- close the Controller Link driver and remove the Support Board from the network: 0<CR> Return value: 0 (everything is O.K., no errors)

Creating and Transferring the Routing Tables This is a last step needed when configuring the Controller Link network consisting of two nodes: Support Board (node 1) and C200HE PLC (node 4). Network number 2 is

assigned. If the Routing Table Enable Bit (bit 12 on DM6400) is set to 1 (ON) then following can be done.

At first, the PC IDs must be assigned to both nodes. It can be done by invoking the "Main menu/W:Edit PC ID" and filling the "PC ID Edit Screen" as follows:

R Netwk Node PC ID

001 000 001 1

002 000 004 2

Register the entered PC IDs by invoking F3 (Write) and then exit by F10 (End). The PC IDs now are assigned.

The next step is creating and transferring the Local Network Table. Invoke the "Main menu/R:Routing Table", select "E:Edit" from Routing Table Menu and enter the following on the "Local Network Table Screen":

No. Loc netwk SIOU unit #

1 002 00

Then select F2 (S menu) and "T:Transfer" from Routing Table Menu. The window where

to specify the target node appears. Enter the PC ID: 001, Network address: 000 and

Node address: 001. Then press F6 (Execute) and select "W: Computer -> PC/Board" from the Transfer Routing Table Menu. The routing table write processing to node 1 will start. If the routing table writing terminates normally, the "Normal" appears on the window.

Return to window where to specify the target node and enter the PC ID: 002, Network

address: 000 and Node address: 004. Then press F6 (Execute) and select "W: Computer -> PC/Board" from the Transfer Routing Table Menu. The routing table writing processing to node 4 will start. If the routing table writing terminates normally, the "Normal" appears on the window. If there are no errors recognized when transferring Routing tables then exit from Controller Link Support Software.



Configuring FinsGateway to Access Controller Link Network If the PLC is connected to the PC and started then configure FinsGateway Controller Link drivers and start and configure Controller Link network.

CLK Driver Settings







In the tree-view on Basic tab expand Drivers folder and check Controller Link item. Click Properties button on Work pane. The Controller Link Properties dialog box will appear.

Note: In FinsGateway version 2.0 you can not start OMRON FinsGateway Settings program. In this case all utilities (e.g. FINS Network Navigator utility) needed to start/configure CLK_UNIT and other FinsGateway Services are accessible from Windows Start menu (Start/Programs/FinsGateway/… ) or from the OMRON FinsGateway Service Manager.

In the Controller Link Properties dialog box select "Driver" tab and enter Controller Link Support Board’s settings - Memory Area and Interrupt Level – matching to settings on the Board.



Starting/Configuring Controller Link Network To start Controller Link click the Services icon from the FinsGateway Configuration Basic tab. Click the CLK_UNIT0 item. Press the Start button on Work pane.

To perform the settings for Controller Link already running do the following. In the Basic tab of the Control pane click the the Networks and Units icon. Click the Controller Link icon in the display. Click the Properties button on Work pane. The Controller Link Properties dialog box will be displayed. Select the "Network" tab and configure Controller Link network parameters:



- Set the Network number (from 0 to 127) you assign to Controller Link network. Zero

could be assigned only if PC is installed in only one local network. Network number must match to settings in PLC’s Routing table (in current example 2).

- Usually there is no reason to change Local node number (in example 1) and Communication unit number (in example 18) assigned by FINS Gateway.

If there are PLCs configured as Controller Link network nodes in your Controller Link network then these nodes (with model type and Node number) must be seen when enter Nodes tab.



Conditions to Start OMRONFGV Server CPU_UNIT and CLK_UNIT0 FinsGateway Services must be started and running before starting the OMRONFGV Server. The proper functioning of FinsGateway Controller Link

Service (CLK_UNIT0) and Controller Link network can be tested by FinsGateway

Network Tester utility. Start utility from FinsGateway Settings program menu (Network->FINS Communication Test).

Correspondence between PLC’s Controller Link Unit setup, FinsGateway Services setup and OMRONFGV Server configuration values is the following: - Network Number in Routing tables (in current example 2) matches to Network Number in FinsGateway Controller Link utilities and matches to Network Address in "OMRONFGV TOPIC Definition" dialog box (see chapter Topic Definition Command). - Node Number on rotary switches (in current example 4) matches to Node Number in Controller Link network configuration utilities, matches to Node Number in FinsGateway Controller Link utilities and matches to Node Address in "OMRONFGV TOPIC Definition" dialog box. - Assign 0 to Unit Address in "OMRONFGV TOPIC Definition" dialog box when configure Topic in Controller Link network.



SYSMAC LINK The OMRONFGV Server requires SYSMAC LINK Support Board to be installed on the computer to communicate with the OMRON PLCs over the SYSMAC LINK network.

FinsGateway software must be installed and CPU_UNIT and SysmacLink unit

FinsGateway Services must be started. SysmacLink unit Service must be configured. Each connected OMRON Controller (with SYSMAC LINK Unit installed) must be configured to allow it to function as a node in the SYSMAC LINK network. This setup can be done by appropriate programming software, such as OMRON SYSMAC LINK Support Software (see "SYSMAC LINK Support Board OPERATION MANUAL"), OMRON CV Support Software (see "SYSMAC LINK System Manual" and "CV Support Software Operation Manual" for details of actual setting operations), or CX-Programmer or SYSWIN. To prepare the SYSMAC LINK network for data access by OMRONFGV Server do the following: - install the hardware for SYSMAC LINK communication, - configure PLC(s) as SYSMAC LINK node(s). Set Network number of your choice into

Routing tables,

- install FinsGateway on PC (if not installed yet), - configure FinsGateway to access SYSMAC LINK Network , - start the FinsGateway Sysmac Link drivers and start and configure Sysmac Link

network. - Start the OMRONFGV Server. When configure Topic(s) in the OMRONFGV Server

see configuration parameters (Network Address, Node Address and Unit Address) in

FinsGateway configuration utilities.

Preparing the OMRON PLC to be used on SYSMAC LINK network OMRON C200HX/C200HG/C200HE PLCs, CV-series PLCs, C-series PLCs and CS1 PLCs can be used as nodes on SYSMAC LINK network. PLCs must be supplied with SYSMAC LINK Communication Units; e.g. C200HW-SLK23 - for C200HX/C200HG/C200HE PLCs, CV500-SLK21 – for CV-series PLCs, C1000H-SLK21 – for C-series PLCs and CS1W-SLK21 – for CS1 PLCs. Set Node Number in range from 1 to 62 (and Unit Number on CV500-SLK21 unit) on the rotary switches. (See the OMRON SYSMAC LINK System Manual on details how to prepare OMRON PLC to be used on SYSMAC LINK network.)

Installing the OMRON SYSMAC LINK Support Board The following settings must be made on a SYSMAC LINK Support Board:

- Set the Memory Area address to some value not overlapping with another resource

currently used by computer; for example, use address D0000;

- Set the Interrupt Level, e.g. IRQ10; take care if this interrupt is not already used by another resource on the computer. (See the OMRON SYSMAC Link Support Board Operation Manual on details how to install a SYSMAC LINK Support Board.)



SYSMAC LINK Unit configuration for CV-series PLC with SYSWIN SYSMAC LINK Unit configuration for CV-series PLCs can be processed by Programming Device running CVSS software or the SYSWIN or CX-Programmer software (running in MS Windows). Follow SYSMAC LINK System Manual to configure SYSMAC LINK unit to allow PLC to function as a node in the SYSMAC LINK network. The Network number of your choice must be configured in Routing tables in the PLC. Start SYSWIN, set communication (e.g. HostLink) parameters and establish connection to the PLC (follow SYSWIN User Manual). Enter SYSMAC LINK network number in Routing table. To do it - start the Routing Table Setup dialog (Project/Routing tables).

Select Routing table Type. Enter I/O unit number matching to settings on the rotary switches on the module. Enter Network number (0 to 127) you assign to SYSMAC LINK network (must match to SYSMAC LINK network number assigned later in FINS Gateway). Press Write button. Note: In current example only one local network is configured. If PLC is included in Controller Link or other local and/or remote networks then these networks also must be presented in Routing tables.



Configuring FinsGateway to Access SYSMAC LINK Network If the PLC is connected to the PC and started then configure FinsGateway SYSMAC LINK drivers and start and configure SYSMAC LINK network.

SLK Driver Settings







In the tree-view on Basic tab expand Drivers folder and check SysmacLink item. Click Properties button on Work pane. The SYSMAC LINK Properties dialog box will appear.

Note: In FinsGateway version 2.0 you can not start OMRON FinsGateway Settings program. In this case all utilities (e.g. FINS Network Navigator utility) needed to start/configure SysmacLink Unit and other FinsGateway Services are accessible from Windows Start menu (Start/Programs/FinsGateway/… ) or from the OMRON FinsGateway Service Manager.

In the SYSMAC LINK Properties dialog box select "Driver" tab and enter SYSMAC LINK Support Board’s settings - Memory Area and Interrupt Number – matching to settings on the Board.



Starting/Configuring SYSMAC LINK Network To start SYSMAC LINK click the Services icon from the FinsGateway Configuration Basic tab. Click the SysmacLink Unit item. Press the Start button on Work pane.

To perform the settings for SYSMAC LINK already running do the following. In the Basic tab of the Control pane click the Networks and Units icon. Click the SysmacLink Unit icon



in the display. Click the Properties button on Work pane. The SYSMAC LINK Properties dialog box will be displayed. Select the "Network" tab and configure SYSMAC LINK network parameters:

- Set the Network number in range (0 to 127 decimal) you assign to SYSMAC LINK

network. Zero could be assigned only if the computer is installed in only one network. Network number must match to settings in PLC’s Routing table.

- Usually there is no reason to change Local node number (in example - 1) and Communication unit number (in example - 16) assigned by FINS Gateway.

If there are PLCs configured as SYSMAC LINK network nodes in your SYSMAC LINK network, then these nodes (with correct model type and Node number) must be seen when enter Nodes tab.



Conditions to Start OMRONFGV Server CPU_UNIT and SysmacLink Unit FinsGateway Services must be started and running before starting the OMRONFGV Server. The proper functioning of FinsGateway SYSMAC LINK Service (SysmacLink Unit) and SYSMAC LINK network can be tested by

FinsGateway Network Tester utility. Start utility from FinsGateway Settings program menu (Network->FINS Communication Test).

If FinsGateway is installed and SYSMAC LINK network is functioning then OMRONFGV Server can be installed and started.

Correspondence between SysmacLink Unit setup, FinsGateway Services setup and OMRONFGV Server configuration values is the following: - Network Number in Routing tables (in current example 1) matches to Network Number in FinsGateway SYSMAC LINK utilities and matches to Network Address in "OMRONFGV TOPIC Definition" dialog box (see chapter Topic Definition Command). - Node Address on rotary switches (in current example 3) matches to Node Number in FinsGateway SYSMAC LINK service and matches to Node Address in "OMRONFGV TOPIC Definition" dialog box. - Unit Number on rotary switches (in current example 2) matches to I/O Unit Number in SYSWIN’s Routing Table Setup dialog box when configure Routing tables. PLC’s Unit Number is not assigned when configuring FinsGateway. Assign 0 to Unit Address in "OMRONFGV TOPIC Definition" dialog box when configure Topic in SYSMAC LINK network.



Serial Communication To prepare the Serial Unit network do the following: - install the hardware for serial communication,

- install FinsGateway (if not installed yet), - configure Serial unit using FinsGateway application,

- start CPU_UNIT and SerialUnit FinsGateway Services. - Start the OMRONFGV Server and configure Topic(s). When configure Topic in the OMRONFGV Server see configuration parameters (Network

Address, Node Address and Unit Address) in FinsGateway configuration utilities.

Preparing the OMRON PLC to be used on Serial network OMRON C200HX/C200HG/C200HE PLCs, CV-series PLCs, C-series PLCs, CPM2x PLCs, CS1 PLCs, CJ1 PLCs and CQM1 PLCs can be used as nodes on Serial Unit network. The CPU of the C200HX/C200HG/C200HE PLCs has a built-in RS-232C port that can be used for communication with the PC. Communication Board (e.g. C200HW-COM02) can be used also. The CV-series PLCs can be connected to a PC with the HostLink connector via the CPU or a CV500-LK201 Host Link Unit mounted to a Rack (see SYSMAC CV-series Programmable Controllers OPERATION MANUAL). The C-series PLCs need additional Host Link Unit to be installed, e.g. C500-LK203 or 3G2A6-LK201-EV1. The CPM2x PLCs have built-in RS-232 port. The CS1 PLCs can be connected to a PC via the RS-232 port on CPU Unit. The CJ1 PLCs have built-in RS-232 port on CPU as well as can be supplied with CJ1W-SCU41 Serial Communication module. The CQM1 PLCs are supplied with built-in RS-232 port on CPU. Connect PLC and PC’s COM port by the HostLink connector.

Configuring CV-series PLC’s Serial Communication by FinsGateway FinsGateway serial communications handle the COM port as a network. FinsGateway must be set to use a specific COM port.

Specifying the Communications Path









In the tree-view on Basic tab expand Drivers folder and check SerialUnit item. Click Properties button on Work pane. The Serial Unit Properties dialog box will appear.

Note: In FinsGateway version 2.0 you can not start OMRON FinsGateway Settings program. In this case all utilities (e.g. Serial Config utility, FINS Network Navigator utility) needed to start/configure Serial Unit and other FinsGateway Services are accessible from Windows Start menu (Start/Programs/FinsGateway/… ) or from the OMRON FinsGateway Service Manager.

In the Serial Unit Properties dialog box check the COM ports to use (in "Lines" tab)



In the "Communication Unit" tab configure communication parameters matching to settings on the PLC.

Starting/Configuring Serial Communications To start Serial communication click the Services icon from the FinsGateway Configuration Basic tab. Click the SerialUInit item. Press the Start button on Work pane.



To perform the settings for serial communications already running, do the following. Click the Networks and Units icon on the Basic tab of the Control pane. Click the SerialUnit-COMx icon in the display. Click the Properties button in Work pane.

The COMx Serial Unit Properties dialog box will be displayed. Select "Network" tab.

Set the Network number (from 0 to 254) you assign to COM port (FinsGateway consider computer COM port as one network). Zero could be assigned only if PC is installed in only one network. There is no reason to change Local node number (in example 31) and Communication unit number (in example 24) assigned by FINS Gateway.



To add a node to the serial communications - click the "Nodes" tab in the SerialUnit Properties dialog box and click the Add button. (To correct existing node parameters -press "Property" button.) In both cases the "Add/Edit Serial Node" dialog box is displayed.

The Host Link and CompoWay/F unit number 0, which cannot be used in FinsGateway is preset to be node address 240.

Select target node type and appropriate Protocol from list boxes. Note: If SYSMAC WAY protocol is selected, then you can not poke values into some model PLCs (e.g. CS1) started in RUN mode. To access data writing into such PLCs - select SYSMAC WAY-CV protocol (if your PLC support this kind of protocol) or start PLC (e.g. CPM2x PLCs) in MONITOR mode. If the Protocol is set to SYSMAC WAY, SYSMAC WAY-CV, or CompoWay, specify the Host Link or CompoWay/F unit number for Unit No./Data. For Data Size, set 1. Press "OK".

Node number and Unit number of the PLC assigned by FinsGateway software you can see in "Nodes" tab.



In current example Node number 240 and Unit number 0 are assigned to the PLC model C200HE. Enter these values when configuring Topic in OMRONFGV Topic Definition dialog box (see chapter Topic Definition Command).

Conditions to Start OMRONFGV Server The CPU_UNIT and SerialUnit FinsGateway Services must be started and running before starting the OMRONFGV Server. The proper functioning of FinsGateway

SerialUnit Service and serial communication can be tested by FinsGateway Network

Tester utility. Start utility from FinsGateway Settings program menu (Network->FINS Communication Test).

If FinsGateway is installed and SerialUnit FinsGateway Service is functioning then OMRONFGV Server can be installed and started.

Correspondence between PLC’s Serial communication setup, FinsGateway Services setup and OMRONFGV Server configuration values is the following: - Network Number in FinsGateway COM1 Serial Unit Properties dialog box matches to Network Address in "OMRONFGV TOPIC Definition" dialog box (see chapter Topic Definition Command). - Node Number in FinsGateway COM1 Serial Unit Properties utility matches to Node Address in "OMRONFGV TOPIC Definition" dialog box. - Unit Number in FinsGateway COM1 Serial Unit Properties utility matches to Unit Address in "OMRONFGV TOPIC Definition" dialog box.

SYSMAC Board The OMRONFGV Server requires SYSMAC Board to be installed as an expansion board

in the computer. FinsGateway software must be installed and CPU_UNIT and

SysmacBoard unit FinsGateway Services must be started. SysmacBoard unit Service



must be configured to allow the SYSMAC Board to function as a fully functional PLC. This

setup can be done by FinsGateway's SYSMAC BOARD Config utility. To prepare the SYSMAC Board for data access by OMRONFGV Server do the following: - install into PC the SYSMAC Board with all connected units you need,

- install FinsGateway on PC (if not installed yet), - configure FinsGateway to access SYSMAC Board,

- configure SysmacBoard driver and start SYSMAC Board Unit. Test SYSMAC Board access by FinsGateway,

- set Network number of your choice, - Start the OMRONFGV Server. When configure Topic(s) in the OMRONFGV Server

see configuration parameters (Network Address, Node Address and Unit Address) in

FinsGateway configuration utilities.

Installing the OMRON SYSMAC Board The following settings must be made on a SYSMAC Board by Board's DIP switch: - set the I/O port address used for communications between the SYSMAC Board and

the computer, for example, 03A0 to 03A4. Confirm that I/O port address of your choice is available for use by the SYSMAC Board (address is not used by another resource). If none of the I/O ports (presented in "SYSMAC Board OPERATION MANUAL") are available then reset another resource so that one of the ranges can be used by the SYSMAC Board,

- set other operating parameters (see the SYSMAC Board OPERATIONAL MANUAL on details how to install a SYSMAC Board into computer.)

Configuring FinsGateway to Access SYSMAC Board If the SYSMAC Board is installed and FinsGateway is installed then the driver settings must be performed and SYSMAC Board Unit can be started.

SysmacBoard Driver Settings









In the tree-view on Basic tab expand Drivers folder and check SysmacBoard Unit item. Click Properties button on Work pane. The SYSMAC Board Unit Properties dialog box will appear.

Note: In FinsGateway version 2.0 you can not start OMRON FinsGateway Settings program. In this case all utilities (e.g. FINS Network Navigator utility) needed to start/configure Sysmac Board Unit and other FinsGateway Services are accessible from Windows Start menu (Start/Programs/FinsGateway/… ) or from the OMRON FinsGateway Service Manager.

In the SYSMAC Board Unit Properties dialog box select "Driver" tab and enter SYSMAC Board’s settings - Shared Memory Address and I/O Port address.



- Confirm that I/O port address and Shared Memory address of your choice are available for use by the SYSMAC Board (addresses are not used by other resources). If none of the I/O ports or Shared Memory address (presented in "SYSMAC Board OPERATION MANUAL") are available then reset another resource so that one of the ranges by the SYSMAC Board.

Starting/Configuring the SysmacBoard

To start the SysmacBoard Unit click the Services icon from the FinsGateway Configuration Basic tab. Click the SysmacBoard Unit item. Press the Start button on Work pane.



Note: If SysmacBoard Unit does not start then firstly check whether selected I/O port address and Shared Memory address do not conflict with other resources. If not, then check SysmacBoard device (e.g. in Windows NT access from Start menu: Start/Settings/Control Panel/Devices/HW Profiles...). Enable (if Disabled) and start SysmacBoard device. To perform the settings for a SysmacBoard Unit already running, do the following: click the Networks and Units icon on the Basic tab of the control pane. Click the

SysmacBoard icon in the display. Click the Properties button. The SYSMAC BOARD Unit

Properties dialog box will be displayed:

- Set the Network number in range (0 to 127 decimal) you assign to SYSMAC Board

network. (The ISA bus with the SYSMAC Board installed is considered one network for the FinsGateway). Zero could be assigned only if the computer is installed in only one FA network. Network number 5 is assigned in current example.

- Usually there is no reason to change SYSMAC ISA Unit FINS addresses - Local node number (in example 100) and Communication unit number (in example 30) assigned by FINS Gateway.

Restart the SysmacBoard Unit to make the new settings effective.

Select the "Node" tab (in SYSMAC BOARD Unit Properties dialog box) to see parameters of SYSMAC CPU unit in SYSMAC Board:



The default Node number (230) and Unit number (fixed to 0) assigned by FINS Gateway to SYSMAC CPU unit are useful to access data from SYSMAC Board.

CPU_UNIT and SysmacBoard Unit FinsGateway Services must be started and running before starting the OMRONFGV Server. The proper functioning of FinsGateway

SYSMAC Board service (SysmacBoard Unit) can be tested by FinsGateway Network

Tester utility. Start utility from FinsGateway Settings program menu (Network->FINS Communication Test).

If FinsGateway is installed and SysmacBoard Unit service is functioning, then OMRONFGV Server can be installed and started. Select Sysmac Board in Communication Type option ("OMRONFGV Topic Definition" dialog box, chapter Topic Definition Command). Select Sysmac Board in Controller Type option ("OMRONFGV Topic Definition" dialog box, chapter Topic Definition Command).

Correspondence between SysmacBoard's CPU unit setup, FinsGateway Services setup and OMRONFGV Server configuration values is the following: - Network Number (in current example 5) assigned in FinsGateway's SYSMAC Board Config utility matches to Network Address in "OMRONFGV TOPIC Definition" dialog box (see chapter Topic Definition Command). - Node Number of SYSMAC CPU (in current example 230) assigned by FinsGateway (see SYSMAC Board Config utility) matches to Node Address in "OMRONFGV Topic Definition" dialog box. - Unit Number of SYSMAC CPU (fixed to 0) (see SYSMAC Board Config utility) matches to Unit Address in "OMRONFGV TOPIC Definition" dialog box.



Event Memory The OMRONFGV Server can access Shared Memory of FinsGateway EventMemory. The following Shared Memory areas are accessible: DM (32768 words) and CIO (32768 words).

To access EventMemory - FinsGateway software must be installed and CPU_UNIT FinsGateway Service must be started. In FinsGateway Version 3 FinsGateway Services

are accessible from the OMRON FinsGateway Settings program. Start FinsGateway

Service Manager (from Windows Start menu: Start/Programs/FinsGateway/Service

Manager) and then start OMRON FinsGateway Settings application from Windows Start menu (Start/Programs/FinsGateway/FinsGateway Configuration) or right-click on

FinsGateway Service Manager icon in the task tray, and select Settings. In the tree-view on Basic tab expand Memories folder and check EventMemories item. Work pane offers options to access EventMemory. Note: In FinsGateway version 2.0 you can not start OMRON FinsGateway Settings program. In this case all utilities (e.g. FINS Network Navigator utility) needed to start/configure Sysmac Board Unit and other FinsGateway Services are accessible from Windows Start menu (Start/Programs/FinsGateway/… ) or from the OMRON FinsGateway Service Manager. The EventMemory Utility and EventMemory Information utility of FinsGateway can be used to monitor/change EventMemory data.

If FinsGateway is installed and CPU_UNIT service is functioning, then OMRONFGV Server can be installed and started. Select Event Memory in Communication Type option ("OMRONFGV Topic Definition" dialog box, chapter Topic Definition Command). Select FinsGateway (CPU_UNIT) in Controller Type option ("OMRONFGV Topic Definition" dialog box, chapter Topic Definition Command). Network Address, Node Address and Unit Address - all must be set to zero (n.n.u = 0.0.0).



Installing the OMRONFGV Server

Installing the Server The OMRONFGV Server installation package is supplied as a Microsoft Installer file DR40010_xxx.msi, where xxx is the current (latest) version of OMRONFGV Server. To install the OMRONFGV Server, run the DR40010_xxx.msi and proceed as directed by the OMRONFGV Server Setup Wizard. The installation is simple and straightforward,

only it is important to select the correct protection (HASP key or software license) in “Custom Setup” dialog: The HASP key or software license key is needed for full time running of OMRONFGV

Server. The HASP key is an USB key (dongle) to be installed into PC USB port and needs the SafeNet Sentinel LDK Run-time Environment (HASP HL Runtime Package) to be installed and running – see details in “Licensing by using HASP HL key” section

below. The software license key is a 16-character alphanumeric “computer-dependent” string, provided after purchasing the OMRONFGV Server (for more information, see “Software license key” section below. Without HASP key installed or software license key entered, the OMRONFGV Server will run one hour in demo mode. After purchasing the OMRONFGV Server, the appropriate HASP key or software license key is provided and no re-installation of OMRONFGV Server is needed.

In case “HASP Device driver” and “HASP Files” are not selected then HASP USB key

will not be supported and only the software license will be available (files needed for HASP USB key will not be installed):



In case “HASP Device driver” and “HASP Files” are selected then HASP USB key will be supported and both HASP-key and software license will be available (files needed for HASP USB key will be installed):

Note: In case the SafeNet Sentinel LDK Run-time Environment (HASP HL Runtime Package) is already installed on your computer (separately or by some other software) then it can be disabled: When installation is finished, the subdirectory specified as a folder where to install the OMRONFGV Server files will contain the following files:

OMRONFGV.EXE The OMRONFGV Server Program. This is a Microsoft Windows 32-bit application program.

OMRONFGV.CHM The OMRONFGV Server Help file.

OMRONFGV.CFG An example configuration file.

KLSERVER.DLL

Dynamic Link Library necessary for “OPC & DDE”version of the Server.

WWDLG32.DLL

Dynamic Link Library necessary only for “OPC & DDE”version of the Server.



hasp_windows_44

42.dll

Dynamic Link Library installed only if “HASP Files” is selected during the installation in “Custom Setup” dialog.

haspdinst.exe Sentinel LDK Run-time Environment Installer (HASP HL Runtime Package), copied to OMRONFGV Server folder only if “HASP Device driver” is selected during the installation in “Custom Setup” dialog.

LICENSE.RTF

Klinkmann Automation software license file.

In case the “HASP Device driver” is selected during the installation in “Custom Setup” dialog, the Sentinel LDK Run-time Environment (HASP HL Runtime Package) is installed during the OMRONFGV Server installation (and will be uninstalled during the OMRONFGV Server uninstallation). The presence of Sentinel LDK Run-time Environment can be checked after the OMRONFGV Server installation by looking-up in Control Panel / Administrative Tools Services – the Service “Sentinel Local License Manager” must be started. Notes: 1. The OMRONFGV Server is developed with Wonderware I/O Server Toolkit (ver 7,2,1,6) and needs the Wonderware FS 2000 Common Components to be installed on computer where the OMRONFGV Server is running. If using Wonderware InTouch 8.0 or newer, install the FS 2000 Common Components before installing InTouch (see also Wonderware Tech Notes 404 and 313). The Wonderware FS2000 Common Components are installed automatically when any of Wonderware product (e.g. InTouch or some Wonderware I/O server) is installed. 2. If OMRONFGV Server “Suite Link & DDE” version will run on PC where Wonderware FS2000 Common Components are not installed then a special I/O Server Infrastructure installation package can be obtained from Klinkmann (see Installing the I/O Server Infrastructure section below). This I/O Server Infrastructure installation package contains the minimum set of software needed to run the OMRONFGV Server and these infrastructure files must be install prior to executing the OMRONFGV Server.The I/O Server Infrastructure does not support using OMRONFGV Server as a Windows Service and remote access to OMRONFGV Server (when DDE/SuiteLink Client is not located on same computer as OMRONFGV Server). To uninstall the OMRONFGV Server, start Control Panel, select “Uninstall a program” (“Add/Remove Programs” on XP/2003) and select the “OMRON Controller Link FINS GATEWAY SuiteLink and DDE Server” from the list of available software products. Click on “Uninstall” (“Add/Remove…” on XP/2003) and proceed as directed by the Uninstall Wizard.



Licensing by using HASP HL key The following should be done to enable the licensing by HASP HL key:

- The “HASP Device driver” and “HASP Files” are selected during the OMRONFGV Server installation in “Custom Setup” dialog – that causes correspondingly haspdinst.exe and hasp_windows_4442.dll files are copied to OMRONFGV Server folder and Sentinel LDK Run-time Environment (HASP HL Runtime Package) is installed and started, enabling the OMRONFGV Server can detect the HASP HL USB dongle;

- insert the received HASP key into USB port, and wait until “Installing device driver software” message disappears and “Device driver software installed successfully” message appears;

- start OMRONFGV Server and check - if “Sofware key or HASP HL key not found!” message does not appear then it means everything is done correctly and OMRONFGV Server runs in full mode with licensing by HASP HL key enabled.

Software license key OMRONFGV Server supports the “computer dependent” software licensing. The following steps are required to enable it: 1) Start OMRONFGV Server, click on "Help" menu item (also short-cut Alt+H can be used) and pop-up menu with "Help" menu commands will appear:

Select “License” and “License” dialog will appear:

2) Here the “Customer PC Code” is “computer-dependent” string generated by OMRONFGV Server and it is unique for this computer. Write it down or Copy/Paste to e-mail when ordering the OMRONFGV Server. 3) After purchasing the OMRONFGV Server, you will get the software license key - 16-character alphanumeric string. Open the “License” dialog again and Copy/Paste it to “Software Key” field:



4) Click OK and restart OMRONFGV Server. OMRONFGV Server software license now is enabled. Note – the “Software Key” string is saved to MS Windows system directory (e.g. C:\Windows) WIN.INI file [OMRONFGV] section to enable it is automatically detected at OMRONFGV Server next start-up.

Transferring the software license to other computer The transfer of Software License Key might be needed in very rare situations when it is necessary to move Klinkmann software to other computer (or operation system change is planned for same computer). Such transfer PERMANENTLY removes the Software License Key, so be very careful when deciding to use this option. The following steps are required to transfer the Software License Key:

1) Start the OMRONFGV Server. For OMRONFGV Server “Suite Link & DDE” version, the ArchestrA SMC Log Viewer (or Wonderware Logger) or must be started. Select Help/License from main menu and click the “Transfer” button on “License” dialog:

2) Confirm the transfer of Software License Key by clicking on Yes button:

The “License” dialog now will contain the empty “Customer PC Code” and “Software Key” fields:



3) Take the screenshot from ArchestrA SMC Logger or OMRONFGV Internal Log file window containing the “Software License Key removal message”, like below:

or take the string with “Software License Key removal message” directly from ArchestrA SMC Logger or OMRONFGV Internal Log file, like following:

Software Key 124b-b759-8f10-7ad4 removed. PC Code: 2496-0e75-8b8b-9a91,

Product Code: DR40010 114

4) Provide the obtained “Software License Key removal message” screenshot or string together with new “Customer PC Code” when applying for new Software License Key without purchasing the new license (in situations when it is necessary to move Klinkmann software to other computer or operation system change is planned).

Note! Without providing the “Software License Key removal message” screenshot or string, the new Software License Key will not be assigned.

Installing the I/O Server Infrastructure The I/O Server Infrastructure installation package is supplied as a self-extracting archive (IOServerInfrastructure.exe) and can be downloaded from Klinkmann’s web site.

To install the I/O Server Infrastructure from the self-extracting archive, run the IOServerInfrastructure.exe and proceed as directed by the I/O Server Infrastructure Setup program.



To uninstall the I/O Server Infrastructure, start Control Panel, select “Add/Remove Programs” and select the “IO Server Infrastructure” from the list of available software products. Click on “Add/Remove…” and proceed as directed by the UnInstallShield program. Note: The I/O Server Infrastructure installation will be rejected if Wonderware FS2000 Common Components are already installed on same computer. The I/O Server Infrastructure does not support using OMRONFGV Server as a Windows Service and remote access to OMRONFGV Server (when DDE/SuiteLink Client is not located on same computer as OMRONFGV Server).

Configuring the OMRONFGV Server After the OMRONFGV Server is initially installed, a little of configuration is required. Configuring the Server automatically creates an OMRONFGV.CFG file that holds all of the topics (nodes) definitions entered, as well as the communication port configurations. This file will be placed automatically in the same directory in which OMRONFGV is located unless the path where the configuration file will be placed is specified via the /Configure/Server Settings... command. To perform the required configurations, start up the OMRONFGV program. If the Server starts up as an icon, double-click on the icon to open the server's window. The following will appear:

To access the commands used for the various configurations, open the /Configure menu:

Server Settings Command A number of parameters that control the internal operation of the Server can be set. In most cases, the default settings for these parameters provide good performance and do not require changing. However, they can be changed to fine-tune the Server for a specific environment. To change the Server's internal parameters, invoke the Configure/Server Settings... command. The "Server Settings" dialog box will appear:



The following describes each field in this dialog box: Protocol Timer Tick This field is used to change the frequency at which the Server checks for work to do (at this frequency the Server tries to send one data request to PLC and receive one reply from PLC. If the send/response cycle is too long then more than one activation of Server is necessary to process it. If computer is very busy or some other MS Windows application is taking over the computer then the Server is activated rarely than setting in

the Protocol Timer Tick. Note: The default value is 50 milliseconds. The minimum value is 10 milliseconds. NetDDE being used Select this option if you are networking using NetDDE.

Configuration File Directory The first field is used to specify the path (disk drive and directory) in which OMRONFGV will save its current configuration file. OMRONFGV will use this path to load the configuration file the next time it is started. Note: Only the "path" may be modified with this field. The configuration file is always named OMRONFGV.CFG. Note: There is no limit to the number of configuration files created, although each must be in a separate directory. When using the OMRONFGV Server with InTouch, it is good practice to place the configuration file in the application directory.

Start automatically as Windows NT Service Enabling this option will cause the server to start as a Windows NT service. Windows NT offers the capability of running applications even when a user is not logged on to the system. This is valuable when systems must operate in an unattended mode. Enabling this option and rebooting the system will cause the Server to run as a Windows NT service. However, to view configuration information or to reconfigure the Server, the user must log on to the system. Any Server related problems that may arise such as missing adapter cards, licensing failures or device drivers not loading will not be visible to the user until a log on is performed. Disabling this option and rebooting the system will cause the Server to run as a Windows NT application program once again.



Notes: 1. The Start automatically as Windows NT Service feature can be activated only with OMRONFGV Server "Suite Link & DDE" version. To start the OMRONFGV Server "OPC

& DDE" version as Windows NT Service, refer to Running OMRONFGV "OPC & DDE"

version as Windows NT Service section of this manual.

2. The Service Startup configuration can be changed by MS Windows NT Control

Panel/Services configuration dialogs. The Allow Service to Interact with Desktop checkbox in "Service" dialog box must be checked (the "Service" dialog box can be invoked by pressing the "Startup" button on "Services" dialog box when Service

OMRONFGV_IOServer is selected). If Allow Service to Interact with Desktop is not selected then OMRONFGV Server full functionality is not ensured (e.g. the Server configuration can not be changed, no message boxes will be displayed, etc.). Once all entries have been made, click on OK.

Server Unit Configuration Command The OMRONFGV Server uses OMRON FinsGateway environment to access the data over OMRON FA networks. In FinsGateway, the Win32 applications are virtualized as high-function units of the PLC, so that PCs as nodes on the network can be treated equally with the PLCs. To configure the OMRONFGV Server Unit, invoke the /Configure/Server Unit Configuration... command. The "Server Unit Settings" dialog box will appear:

Only one OMRONFGV Server Unit is supported. Click on New… to create a new unit or click on Modify to examine the settings of already created Unit. The "OMRONFGV Server Unit Settings" dialog box will appear:



The following describes each dialog field in this dialog box: Server Unit Name This field is used to enter the name associated with Server Unit. This name is used only for Server internal purposes and it is not used to connect to FinsGateway. Unit Address This field is used to enter the address of the unit to connect to FinsGateway. This unit address will be used to generate the network handle required by FINS API. The default value is 1, range of allowed values is from 1 to 15. Unit Name This field is used to enter the name of the unit to connect to FinsGateway. This unit name will be used to generate the network handle required by FINS API. The maximum length of this name is 15 characters. The default Unit Name is "FGVSERVER".

Reply Timeout This field is used to enter the amount of time (in seconds) all nodes accessed from OMRONFGV Server will be given to reply to commands from the Server. Note: The default value of 3 seconds should be sufficient for most configurations. Once all entries have been made, select OK to process the configuration for Server Unit.

Select Done in the "Server Unit Settings" dialog box when Server Unit configuration has been performed.

Saving OMRONFGV Configuration File If the configuration file does not currently exist, or a new configuration path has been specified, the Server will display the "Save Configuration" dialog box:

This dialog box displays the path where the Server is going to save the current configuration file. The path may be changed if necessary. Also, the path can optionally be recorded in the WIN.INI file by selecting the "Make this the default configuration file" option. Doing so will allow the OMRONFGV Server to find the configuration file automatically each time it is started.

Configuration File Location When the OMRONFGV Server starts up, it first attempts to locate its configuration file by, first checking the WIN.INI file for a path that was previously specified. If the path is not present in the WIN.INI file, the Server will assume that the current working directory is to be used.



To start the Server from an application directory configuration file other than the default configuration file a special switch (/d:) is used. For example, invoke the File/Run command and enter the following: OMRONFGV /d:c:\directoryname Note: There is no limit to the number of configuration files that may be created, although each must be in a separate directory.

Topic Definition Command The user provides each node with an arbitrary name that is used as the Topic Name for all references to the node. The following steps are taken to define the topics (nodes) attached to (or inter-networked from) one of Omron FA networks: 1. Invoke the Configure/Topic Definition… command. The "Topic Definition" dialog box

will appear:

2. To modify an existing topic, select the topic name and click on Modify. To define a

new topic, click on New. The "OMRONFGV Topic Definition" dialog box will appear:



3. Enter the Topic Name. Note: If using InTouch the same Topic Name is to be entered in the "Add Access

Name" dialog box described in the Using the OMRONFGV Server with InTouch section.

4. Choose the Server Unit to associate it with the topic (additional topics may be

associated with the same Server Unit at a later time) 5. Enter the value in the Network Address field (to each network in the OMRON

system can be assigned a unique network address between 1 and 127). When communicating with a node on another (Remote) network, the entered value must be consistent with the network address assigned in the routing tables. The Network Address in this case must be non-zero. The network address of 0 indicates the local network. Note: The default Network Address is 0.

6. Enter the value in the Node Address field (each OMRON PLC attached to the (or

inter-networked from) Omron FA network must have its own unique node address. Attention should be paid to select a node address that would not conflict with other PLCs over the same OMRON FA network.

7. Enter the value in the Unit Address field (unit number of OMRON PLC’s

communication module set by rotary switches and/or by configuration software).



Note: Detailed explanation of configuring of Network Address, Node Address and Unit Address parameters for different FA networks see in chapter Getting started quickly with OMRONFGV Server.

8. Set the Update Interval field to indicate the frequency the items/points on this topic will be read (polled). Default value is 1000 milliseconds.

9. Enter the value of the PLC Access Delay (in milliseconds). This is a delay what

Server can make in communication with the selected PLC after each read or write

command execution. The default value of PLC Access Delay is 0 (zero). Enter non-

zero value in the PLC Access Delay field only if you consider that selected PLC is not fast enough to correctly react to the Server's frequently sent requests.

The Server processes topics sequentially and therefore there should not be timing problems for a separate PLC, if Server communicates with a group of PLCs. If Server processes only one topic or group of topics within same PLC Node Address, then this PLC is accessed more frequently. Even in this case the Server makes a short pause (depending of Server configuration) after each request/response processing. The main timing problems for PLC can cause the writing of separate Bit status into Word areas (for C200HX/C200HG/C200HE and CQM1 PLCs - into IR, LR, HR, AR, DM and EM areas; for CV-series PLCs - into CIO, G, A, DM, EM, EA…EH areas; for C/CPM2x PLCs - into IR, LR, HR, AR and DM areas; for CS1/CJ1 PLCs - into CIO, W, H, A, DM, and EM areas; (see Item Names section). Writing of the Bit status into Word area is performed by executing the following sequential steps:

- reading of corresponding Word value from PLC memory, - setting a Bit to be written into the Word value, - writing the changed Word value into PLC memory.

If PLC Access Delay is 0 milliseconds, then Server tries to execute all steps as fast as Omron network can do it (with no pauses between processing steps). It can put the selected PLC into hard timing conditions. When unsuccessful Bit writing happens time by time - then it is important to recognize the reason of fault. Most possible reason of fault usually is a bad communication; therefore at first recognize, whether communication is going

correctly. Check the ShowBadWrites option in the Server System Menu. Now the Server logs (to WWLogger and (or) to OMRONFGV Internal Logger) the information about each unsuccessful write command if network communication error happens. If communication is processed correctly (no information about fault in WWLogger or OMRONFGV Internal Logger), but write command is not executed then the possible reason of fault may be the hard timing conditions in the accessed PLC. In this case

the setting non-zero value for PLC Access Delay can make the topic processing more reliable.

Note: By setting the PLC Access Delay to non-zero value you can seriously reduce the real data update rate for selected topic as well as for topics with the same PLC Node Address.



Do not configure great values for PLC Access Delay. To increase the timeout

between Bit writing steps - configure the PLC Access Delay a bit greater as

Protocol Timer Tick value (see Server Settings Command section).

Note: If Server processes a group of topics with the same PLC Node Address and

each of topic is configured to different PLC Access Delay, then Server takes into account the greatest of all configured values and attaches it to all topics with the same PLC Node Address.

10. Select the Communication Type the PLC is accessed by FINS Gateway. If

Communication Type is checked, then the dialog box offers prompt for correct

FINS Message Maximum Size values, as well as offers controller types compatible to selected Communication Type. Note: One PLC can be accessed by the OMRONFGV Server simultaneously over different FA networks, if a separate topic is associated to a PLC for each communication network. Note: In case of SLK, CLK, Ethernet, Serial and Sysmac Net this setting does not affect real communication type. Communication type depends on FINS Gateway service that supports communication to PLC (identified by Network Address, Node Address and Unit Address).

11. Make selection in Controller type option, it is, select PLC type

(C200HX/C200HG/C200HE, CV-series, C/CPM2/CPM2C, CS1/CJ1, CQM1) or Sysmac Board or FinsGateway (CPU_UNIT). When accessing data from SYSMAC Board, then select Sysmac Board in Communication Type option as well as select Sysmac Board in Controller Type option. When accessing data from Event Memory of FinsGateway then select Event Memory in Communication Type option as well as select FinsGateway (CPU_UNIT) in Controller Type option. Network, Node and Unit address accessing Event Memory is n.n.u = 0.0.0.

12. For CV-series PLCs as well as C/CPM2/CPM2C PLCs - select the CV/C Controller

Type. To select the Controller model type, click on the combo box button and make your choice from list box.

13. Enter the values of FINS Message Maximum Size for relevant data part of read and write command. Each value from 16 to prompted (maximal for selected network) number of bytes is valid. The default value is 512 bytes (maximum size for SLK, Serial or Sysmac Board). For other networks OMRONFGV Server supports the following maximum sizes of relevant data part: CLK – 1990, Ethernet or Sysmac Net

– 1984. When Accessing Event Memory – FINS Message Maximum Size is 2038. If PLC is not accessed directly (from the network common to the PC and the PLC) but inter-networked from other network then the maximum amount of data is limited by any network the data passes through, i.e. the network with the smallest capacity will determine the limit. The greater value is configured the faster data update rate

can be achieved. Therefore reduce the FINS Message Maximum Size value only if selected PLC has timing problems to process great amount of data in a short time period.



All Omron PLCs support the requests of maximum length, but not all PLC models can process a lot of such requests without communication errors. If a PLC time by time reports an error message to valid read or write command then one of possible error reasons can be too long command. In this case it is recommended to reduce

the FINS Message Maximum Size for the selected PLC. The smaller Read FINS

Message Maximum Size must be set for topics configured to process Multiple Memory Area Read commands. For write messages the value of FINS Command

Maximum Size is relevant if WIN.INI entries MultiWrite=1 or MultiWrite=2 are used (see WIN.INI entries section). Note: The real maximum length of each command's relevant data part depends on the request and/or structure of response what can be different for different

commands. Values configured for FINS Message Maximum Size limit the length of data part either for request or response command depending on which command (request or response) contains greater number of bytes.

14. Check or uncheck the Multiple Memory Area Read check box to choose the type

of FINS read commands used for this topic. If Multiple Memory Area Read is unchecked (default setting), then Server uses Memory Area Read FINS commands

and maximum (Read FINS Message Maximum Size – 14) / 2 consecutive words

can be read from this topic by one command. If Multiple Memory Area Read is checked then Server uses Multiple Memory Area Read FINS commands and

maximum 128 non-consecutive words (also from different memory areas) can be read from this topic by one command (this mode does not support, strings, long values, floating point values as well as memory areas with forced status).

Once all entries have been made, click on OK.

Update Interval for Multiple Topics

The OMRONFGV Server supports the possibility to enter the new Update Interval value for multiple Topics in a single operation. At first these multiple Topics must be selected in the "Topic Definition" dialog box by holding the CTRL key while clicking on the selected ones:



Then click on Update Interval… . The "UPDATE INTERVAL" dialog box will appear:

Enter the new value in the Update Interval field and select the appropriate time measuring units (milliseconds, seconds, minutes or hours):

Click on OK to change the Update Interval value for all selected Topics or click on

Cancel. The "Topic Definition" dialog box will appear again.

The Update Interval can be changed also at run-time (for each Topic separately, not for several ones at once) after Topic is activated by client application (see description of

UPDATEINTERVAL item in Item Names section).

Select Done when configuration for all Topics has been performed.



Item Names Within the OMRONFGV Server, item/point naming depends on data and memory area naming conventions for Omron PLCs and possible read or write command messages. The OMRONFGV Server supports the fixed set of item names. Each Integer, Discrete or Floating Point item generally may be described as: PnS Each ASCII string item (supported by Server version 1.11 and higher) generally may be described as: Pn-hS Each Text string item generally may be described as: PnTmS where: n - specifies the Memory area word/bit address of the specific word, flag or bit or

lowest-numbered address of Text string or ASCII string. The rightmost two digits of the bit address (when indicate a separate bit in word

area) specify bit number in word and the leftmost digits - specify word address. Depending on number of digits in name (leading zeroes must be in name if necessary) the Server recognizes, whether item/point represents a whole word or only a separate bit in word.

Since Server version 1.11 additionally a letter ‘:’ (or ‘.’) can be used as a separator between word address and bit address. Each item, representing bit in word, may be described as, Pn:b (or Pn:bb or Pn.b or Pn.bb) where n is word address and b (bb) is bit number in word (b can be 0…9 and bb can be 00…15). Number of digits in bit item name with separator is not relevant (leading zeroes are not necessary). Note: Bit separator is supported with WIN.INI entry (see chapter WIN.INI entries) ItemNaming= 2 or ItemNaming=3. Note: If item/point name prefix concerning naming conventions, implemented additionally into version 1.11, differs from former (up to version 1.10) naming conventions (see chapters CV-series PLCs and CS1/CJ1 PLCs), then Bit separator is compatible only with item/point names with prefixes, implemented additionally into version 1.11.

h - Specifies the highest -numbered address of ASCII string.

P - optionally used prefix, one, two or three characters before Memory area address,

and designates the type of Memory area. T - character "T" (or "t") following word/bit address indicates Text string item and is not

presented in Integer, Discrete, Floating Point or ASCII Text string item name. For details see chapter Data Presentation in Text String Items.

m - specifies the length of Text string item and is not presented in Integer, Discrete,

Floating Point or ASCII Text string item name. If Text string item deals with Integer memory area then m is a number of sequential words presented in Text string. If Text string item deals with Discrete memory area then m is a number of sequential Bits presented in Text string. (The length of Text string contents (value) usually is the following: 4*m - for unforced Integer memory areas, 8*m - for forced Integer memory areas and m - for Discrete memory areas.)



S - optionally used suffix - a letter after address (or after length of Text string item), which is used to change the default format of data. The following presents the OMRONFGV Server supported data formats and suffixes, indicating corresponding format.

Unsigned/Signed Format The server interprets 16-bit word in a PLC in 16-bit unsigned format (value limits 0 to 65535) or signed format (value limits -32768 to 32767). Unsigned quantities may be read by one of two methods - by entering item name without suffix or appending

the suffix 'U' (or 'u') (suffix supported since Server version v1.11) to the item name. For example, channel DM100 in a PLC contains 8000 hex. In this case item name DM100 or DM100U would be displayed in InTouch or Excel as 32768. Signed

quantities may be read from the same channel by appending the suffix 'S' (or 's') to the item name. So, item name DM100S would be displayed in InTouch or Excel as -32768.

BCD Format

To read/write data using BCD format - append the suffix 'B' (or ‘b’) to the item name, e.g. DM100B.

Long Format (Signed/BCD) Two consecutive 16-bit words in a PLC can be interpreted as a 32-bit long integer (supported since Server version v1.11). It can be formatted as either signed (-2,147,483,648 to 2,147,483,648) or BCD (0 to 99,999,999). To read/write an item

in signed long format - append the letter 'L' (or 'l') to the item name. To read/write

an item in BCD long format - append the letter 'M' (or 'm') to the item name. For example, if DM100 contains 0234 hex and DM101 contains 1356 hex, DM100L returns 324,403,764 and DM100M returns 13,560,234. Note: Long format is not supported if Multiple Memory Area Read FINS commands are used.

Floating Point Format (IEEE/BCD) Two consecutive 16-bit words in a PLC can be interpreted as a single precision floating point number. It is formatted as either IEEE (-3.402823 * 1038 to 3.402823 * 1038) or BCD (0.0000001 * 10-7 to 0.9999999 * 107). To read/write an item in IEEE floating point format, append one of the following letters to the item name:

'F', 'f', ‘R’ or ‘r’. To read/write an item in BCD floating point format - append the

letter 'G' (or 'g') to the item name. For example, if D100 contains 9620 hex and D101 contains 2436 hex in a CV500 PLC, D100F returns 3.959212 * 10-17 and D100G returns 0.4369620 * 102. Floating point format is relevant only with items, indicating memory areas word contents. Note: IEEE format is NOT supported in the C-Series PLC family

Note: If WIN.INI entry ItemNaming (see chapter WIN.INI entries) is set to value 1 (OMRONFGV Server validates items/points according to naming conventions

supported by Server up to version 1.10) then letter 'F' (‘f’) is interpreted as forced point indication of word, flag or bit (not supported for C-series as well as C200HX,



C200HG and C200HE Omron PLCs). To indicate Floating point number in this

case – only suffix ‘R’ (or ‘r’) can be used.

Note: Floating point format is not supported if Multiple Memory Area Read FINS commands are used.

ASCII Strings Format Multiple consecutive 16-bit words (block size of 1 to 29) in a PLC can be interpreted as a string of ASCII characters. The ASCII string is stored/retrieved from the lowest-numbered address to the highest and from the high-order byte to the low-order byte with each address. To define a range of words, use a '-' between the two address locations. For example, DM10-DM12 indicates locations from DM10 to DM12. ASCII string characters can be specified to come from the high-order byte, low-order byte, or both bytes of the words. Low-order Byte Only the low-order byte (LSB - least significant 8-bits) of each

word is used for read. To use this format, append the suffix 'E' to the item name.

High-order Byte Only the high-order byte (MSB - most significant 8-bits) of each

word is used for read. To use this format, append the suffix 'D' to the item name.

Both Bytes Both bytes of each word are used for read/write. To use this

format, append the suffix 'C' to the item name. Note: All bytes in the specified memory range will be used. If the string is shorter than the range of memory specified, it will be padded with '\0'. If the string is longer than the range of memory specified, the string will be truncated. For example, assume the following memory contents (numeric values shown in hex): MSB LSB

DM10 41 42 "AB" DM11 43 44 "CD" DM12 45 46 "EF"

Read: DM10 - DM12C Returns ABCDEF DM10 - DM11D returns AC DM10 - DM12E returns BDF

Write: DM10 - DM12C after written with "ABCD" MSB LSB

DM10 54 65 "AB" DM11 73 74 "CD" DM12 0 0 " "

DM10 - DM12E after written with "ABCDE"



MSB LSB

DM10 0 41 "A" DM11 0 42 "B" DM12 0 43 "C"

Note: If item/point name prefix concerning naming conventions, implemented additionally into version 1.11, differs from former (up to version 1.10) naming conventions (see chapters CV-series PLCs and CS1/CJ1 PLCs), then ASCII

Strings format with suffixes 'E', 'D' and 'C' is compatible only with item/point names with prefixes, implemented additionally into version 1.11.

C200HX/C200HG/C200HE PLCs and SYSMAC Board The following table lists the supported item names for the C200HX, C200HG and

C200HE PLCs. Item list is also useful for SYSMAC Board because of the SYSMAC Board is functionally equivalent to the SYSMAC C200HG-CPU43-E or C200HX-CPU64-E PLC.

Memory Area Prefix Tag Type

Address Range Value Range

Suffix

Internal Relay Area 1, 2 Special Relay Area 1, 2

(Bit status)

IR Discrete IR0:00...IR511:15 or

00000...51115

0, 1

Internal Relay Area 1, 2 Special Relay Area 1, 2

(Word contents)

IR Integer IR0... IR511 or

0…511

(*) u s b f r g l m d e c

Link Relay Area (Bit status)

LR Discrete LR0:00...LR63:15 or

LR0000...LR6315

0, 1

Link Relay Area (Word contents)

LR Integer LR0... LR63 (*)

Holding Relay Area (Bit status)

HR Discrete HR0:00... HR99:15 or

HR0000...HR9915

0, 1

Holding Relay Area (Word contents)

HR Integer HR0... HR99 (*) u s b f r g l m d e c

Auxiliary Relay Area (Bit status)

AR Discrete AR0:00... AR27:15 or

AR0000...AR2715

0, 1

Auxiliary Relay Area (Word contents)

AR Integer AR0... AR27 (*) u s b f r g l m d e c

Timer/Counter Area Completion Flag(****)

TC Discrete TC0... TC511 0, 1

Timer/Counter Area (PV)

PV Integer PV0... PV511 (*) u s b f r g l m d e c



Data Memory Area (Bit status)(**)

DM Discrete DM000000... DM999915

or DM0:00...

DM9999:15

0, 1

Data Memory Area (Word contents)(**)

DM Integer DM0... DM9999


Extended Data Memory Area (Bit status)(***)

EM Discrete EM000000... EM614315

or EM0:00...

EM6143:15

0, 1

Extended Data Memory Area Word contents(***)

EM Integer EM0... EM6143 (*) u s b f r g l m d e c

Item/point names, corresponding to Internal Relay/Special Relay Area may be without prefix. (Up to version 1.10 the OMRONFGV Server supports Internal Relay/Special Relay Area item/point names only without prefix.)

(*) Value range for unsigned integer is from 0 to 65535 (item/point name with suffix "U"

("u") or without suffix), for signed integers from –32768 to 32767 (item/point name with

suffix "S" ("s")) and for 16-bit BCD is from 0 to 9999. The value range for 32-bit integer is from -2147483648 to 2147483647 and for 32-bit BCD is from 0 to 99999999. Default value range for Integer Tag Type is unsigned integer. (**) Memory area range DM7000…DM9999 is supported only if Expansion DM Area is allocated on the PLC. (***) Current bank only (Memory Area code 98). (****) Read only Note! Do not operate with item names, which have addresses outside really existing PLC data and memory area! It will lead to communication failures, because the Server recognizes item name error only if item name goes out of range represented in the item names table. Usually the information like following will be logged to WWLogger and (or) to OMRONFGV Internal Logger if some item with address in inaccessible memory area is used (MRC:11 and SRC:03 informs about "Parameter error: the first address is in an inaccessible area")

/OMRONFGV/Received Response Code Error (MRC:11 SRC:03 NTW:00 NOD:00

DA1:01 SA1:09) from Topic ‘node9’, node #9

If item/point represents a separate bit in word area (relevant in Internal/Special Relay,

LR, HR, AR, DM or EM areas), then two conventions are useful for item/point naming: 1) Since Server version 1.11 a letter ‘:’ (or ‘.’) can be used as a separator between

word address and bit address. For example, bit number 3 in word number 100 of IR area can be specified as IR100:03 (or IR100.03).

2) All Server versions support item/point names without word/bit separator. In this case the rightmost two digits of the address specify bit 00 to 15.

The word address in this case is specified by the leftmost four digits (DM and EM

areas), three digits (Internal/Special Relay Area) and the leftmost two digits (LR,



HR or AR areas items). Therefore every item name, representing Bit status, must

contain at least 6 digits (DM and EM areas), 5 digits (Internal/Special Relay Area)

or 4 digits (LR, HR and AR area items). If necessary, then item name contains leading zeroes. Note: Since Server version 1.11 set WIN.INI entry ItemNaming=1 (see chapter

WIN.INI entries) to validate item/point names without word/bit separator.

Note: Only Server version 1.11 (and higher) supports Bit Status Items of DM and EM areas.

The following examples show the correct format for item names for C200HX, C200HG, C200HE PLCs and SYSMAC Board:

00201 - Internal Relay Area (Bit status), word address 2, bit number 1 IR2:01 - Internal Relay Area (Bit status), word address 2, bit number 1. Name

valid since Server version 1.11 257 - Special Relay Area (Word contents), word address 257

LR6210 - Link Relay Area (Bit status), word address 62, bit number 10 DM21 - Data Memory Area (Word contents), word address 21

CV-series PLCs The following table lists the supported item names for the CV-series PLCs:


Address Range Value Range

Forced Value Range

Suffix

Input/Output register area CIO

(Bit status)

CIO Discrete/Integer

CIO0:00... CIO2555:15

or 00000...255515

0, 1

0,1,2,3 f

Input/Output register area CIO (Word contents)

CIO Integer CIO0... CIO2555 or

0…2555

(*)

(**) u s b f r g l m d e c

Bus Link Area G (Bit status)

G Discrete/Integer

G0:00... G255:15 or

G00000….G25515

0, 1 0,1,2,3 f

Bus Link Area G (Word contents)

G Integer G0... G255 (*) (**) u s b f r g l m d e c

Auxiliary Relay area A (Bit status)

A Discrete A0:00... A511:15 or

A00000... A51115

0, 1 -

Auxiliary Relay area A (Words)

A Integer A0... A511 (*) - u s b f r g l m d e c

Timer Completion flags TIM (***)

T Discrete/Integer

T0...T1023(****) 0, 1 0,1,2,3 f

Counter Completion flags

CNT (***)

C Discrete/Integer

C0... C1023(****) 0, 1 0,1,2,3 f



Timer Present Value

PVT

/PT

Integer PVT0... PVT1023(****)

(*) - u s b f r g l m d e c

Counter Present Value

PVC

/PC

Integer PVC0... PVC1023(****)


Data Memory area (Bit status)

D

/DM

Discrete D0:00… D24575:15

or DM0000000… DM2457515(*****)

0, 1 -

Data Memory area (Word contents)

D

/DM

Integer D0...D24575(*****) or

DM0...DM24575


Transition Area flags (***)

TN Discrete /Integer

TN0... TN1023(****)

0,1 0,1,2,3

Step Area Flag status (***)

ST

/SA

Integer ST0...ST1023 or

SA0...SA1023(****)

0,1,2,3 -

Step Area status (***)

-

/SS

Integer SS0... SS1023(****)

0,1,2,3 -

Step Timer Present Value (***)

-

/ST

Integer ST0... ST1023(****)


Expansion area Current bank (Bit status)

E

/EM

Discrete E0:00...E32765:15or EM0000000...

EM3276515

0, 1 -

Expansion area Current bank

(Word contents)

E

/EM

Integer E0...E32765 or

EM0...EM32765


Expansion area A (Bit status)

EA /-

Discrete EA0:00... EA32765:15

0, 1 -

Expansion area A (Word contents)

EA /-

Integer EA0... EA32765


Expansion area B (Bit status)

EB /-

Discrete EB0:00... EB32765:15

0, 1 -

Expansion area B (Word contents)

EB /-

Integer EB0... EB32765

(*) u s b f g l m d e c

Expansion area C (Bit status)

EC /-

Discrete EC0:00... EC32765:15

0, 1 -

Expansion area C (Word contents)

EC /-

Integer EC0... EC32765


Expansion area D (Bit status)

ED /-

Discrete ED0:00... ED32765:15

0, 1 -

Expansion area D (Word contents)

ED /-

Integer ED0... ED32765


Expansion area E (Bit status)

EE /-

Discrete EE0:00... EE32765:15

0, 1 -

Expansion area E (Word contents)

EE /-

Integer EE0... EE32765


Expansion area F (Bit status)

EF /-

Discrete EF0:00... EF32765:15

0, 1 -



Expansion area F (Word contents)

EF /-

Integer EF0... EF32765


Expansion area G (Bit status)

EG /-

Discrete EG0:00... EG32765:15

0, 1 -

Expansion area G (Word contents)

EG /-

Integer EG0... EG32765


Expansion area H (Bit status)

EH /-

Discrete EH0:00... EH32765:15

0, 1 -

Expansion area H (Word contents)

EH /-

Integer EH0... EH32765


Action Area Flag status

-

/AC

Discrete AC0... AC2047

0, 1 -

Register Area contents IR (***)

IR Integer IR0...IR2 (*) u s b f r g l m d e c

Register Area contents DR (***)

DR Integer DR0...DR2 (*) u s b f r g l m d e c

Item/point names, corresponding to Input/Output register area CIO, may be without prefix. (Up to version 1.10 the OMRONFGV Server supports CIO item/point names only without prefix.) For other memory areas, if item/point name prefix concerning naming conventions, implemented additionally into version 1.11, differs from former (up to version 1.10) naming conventions, then implemented prefix is presented in the table the first and former prefix – the second, after a slash. For example, since version 1.11 Timer Present Values are indicated by prefix “PVT” while

former prefix is “PT” and in column “Prefix” you see “PVT /PT”. With WIN.INI entry

ItemNaming=1 (see chapter WIN.INI entries) you can operate only with prefix PT, with

WIN.INI entry ItemNaming=2 you can operate only with prefix PVT and with WIN.INI

entry ItemNaming=3 you can operate with both prefixes – PT and PVT.

If you see something like the follows “- /SS”, then it means, that corresponding memory

area is not supported with WIN.INI entry ItemNaming=2.

If you see something like the follows “EB/-”, then it means, that corresponding memory

area is not supported with WIN.INI entry ItemNaming=1.


("u") or without suffix), for signed integers from 32768 to 32767 (item/point name with

suffix "S" ("s")) and for 16-bit BCD is from 0 to 9999. The value range for 32-bit integer is from -2147483648 to 2147483647 and for 32-bit BCD is from 0 to 99999999. Default value range for Integer Tag Type is unsigned integer.

(**) Word Contents with Forced Status contains four Bytes: the first Byte - contents of Bits 0 to 7; the second Byte - contents of Bits 8 to 15; the third Byte - Forced/not forced designation for Bits 0 to 7; the fourth Byte - Forced/not forced designation for Bits 8 to 15; (ON = Forced). Value range for word areas with forced status is from –2147483648 to 2147483647. Tag type of the Flag or Bit with Forced Status is Integer. The configuration of the Flag or Bit with Forced Status is as follows:

0: Bit is OFF but not Forced;



1: Bit is ON but not Forced; 2: Bit has been forced OFF; 3: Bit has been forced ON;

If there are no values (or “**”) presented in the column " Forced Value Range", then the Server does not support corresponding Memory area with forced status. If two Tag Types ("Discrete/Integer") are given in the table for the same item, it means, that item with unforced status has the first type (Discrete), but item with forced status - the second type (Integer). Note: You can force values into Timer Completion flags, Counter Completion flags and Transition Area flags memory areas of CV-series PLCs by operating with item/point names (correspondent to former naming conditions up to Server version 1.10) with suffix

"F" or "f". Since Server version 1.11 there must be WIN.INI entry ItemNaming=1 (see chapter WIN.INI entries) to operate with forced values. (***) Read only (****) Represented memory area ranges are for CV1000, CV2000 and CVM1-CPU11-E (except Transition Area and Step Area Flag status) type controllers. For models CV500 and CVM1-CPU01-E (except Transition Area and Step Area Flag status) - accessible memory area ranges are 0:00...511:15 for Discrete items and 0...511 - for Integer items. Transition Area TN and Step Area Flag status area ST are not supported on CVM1 PLCs. Note! Do not operate with item names, which have addresses outside really existing PLC data and memory area! It will lead to communication failures, because the Server recognizes item name error only if item name goes out of range represented in the item names table. Usually the information like following will be logged to WWLogger and (or) to OMRONFGV Internal Logger if some item with address in inaccessible memory area is used (MRC:11 and SRC:03 informs about "Parameter error: the first address is in an inaccessible area")


DA1:01 SA1:09) from Topic ‘node9’, ... (*****) Represented memory area ranges are for CV1000, CV2000 and CVM1-CPU11-E type controllers. For models CV500 and CVM1-CPU01-E - accessible memory area ranges are 0...8191. Expansion area Current bank as well as Expansion areas (from EA to EH) is relevant only with CV1000 and CV2000 PLCs.

Item names IR and DR are valid with following Omron PLC models: CV1000, CV2000 and CVM1-CPU11-E. Note: If WIN.INI entry ItemNaming (see chapter WIN.INI entries) is set to value 2 (or 3),

then items with prefix "ST"("st") are interpreted as Step Area Flag status. If WIN.INI entry

ItemNaming is set to value 1, then items with prefix "ST"("st") are interpreted as Step Timer Present Value concerning former (up to version 1.10) OMRONFGV Server item



naming conventions. In this case item representing Step Area Flag status must have

prefix "SA" ("sa").

If item/point represents a separate bit in word area (relevant in CIO, G, A, DM, EM or EA

…EH areas), then two conventions are useful for item/point naming: 1) Since Server version 1.11 a letter ‘:’ (or ‘.’) can be used as a separator between word

address and bit address. For example, bit number 3 in word number 100 of CIO area can be specified as CIO100:03 (or CIO100.03).

2) All Server versions support item/point names without word/bit separator. The word

address in this case is specified by the leftmost five digits (DM and EM areas), four

digits (Input/Output register area CIO) and the leftmost three digits (G and A items).

Therefore every item name, representing Bit status, must contain at least 7 digits (DM

and EM areas), 6 digits (Input/Output register area CIO) and 5 digits (G and A area items). If necessary, then item name contains leading zeroes. Note: Since Server version 1.11 set WIN.INI entry ItemNaming=1 (see chapter



The configuration of the discrete data can be as follows:

Flag or Bit Status 0: Bit is OFF;

1: Bit is ON;

Step Status 0: INACTIVE;

1: HALT;

2: PAUSE; 3: EXECUTE;

The following examples show the correct format for item names for CV-series PLCs:

002113 - CIO area (Bit status), word address 21, bit number 13 CIO1:15 - CIO area (Bit status), word address 1, bit number 15. Name valid

since Server version 1.11 211 - CIO area (Word contents), word address 211 TN200F - Transition Area flag with Forced status, address 200 SS0007 - Step Area status, address 7 (address in item name contains leading

zeroes, but number of digits in item name does not exceed the limit according to table)

AC6 - Action Area Flag status, address 6 DM3R - real (floating point) item, value is taken from words DM3 and DM4.



C/CPM2x PLCs The following table lists the supported item names for the C-series PLCs:


Range Value Range

Format Suffix

CIO area (Bit status)

IR Discrete IR0:00...IR511:15 or 00000...51115 (**)

0, 1

CIO area (Word contents)

IR Integer IR0... IR511 or 0...511 (**)


Latching Relay area (Bit status)

LR Discrete LR0:00... LR63:15 or LR0000...LR6315

0, 1

Latching Relay area (Word contents)

LR Integer LR0... LR63 (*) u s b f r g l m d e c

Holding Relay area (Bit status)

HR Discrete HR0:00... HR99:15 or HR0000...HR9915

0, 1

Holding Relay area (Word contents)


Auxiliary Relay area (Bit status)

AR Discrete AR0:00... AR27:15 or AR0000... AR2715

0, 1

Auxiliary Relay area (Word contents)


Completion flags for Timers/Counters(***)


Present Values for Timers/Counters


Data Memory area (Bit status)

DM Discrete DM0:0...DM9999:15 or DM000000...

DM999915

0, 1

Data Memory area (Word contents)



Item/point names, corresponding to Input/Output register area CIO, may be without prefix. (Up to version 1.10 the OMRONFGV Server supports CIO item/point names only without prefix.)



suffix "S" ("s")) and for 16-bit BCD is from 0 to 9999. The value range for 32-bit integer is from -2147483648 to 2147483647 and for 32-bit BCD is from 0 to 99999999. Default value range for Integer Tag Type is unsigned integer. (**) Represented memory area range is for C200HS type controller. For models C200H, C1000H and C2000H - accessible memory area ranges are 0:00...255:15 for Discrete items and 000...255 for Integer items. Note! Do not operate with item names, which have addresses outside really existing PLC data and memory area! It will lead to communication failures, because the Server recognizes item name error only if item name goes out of range represented in the item names table. Usually the information like following will be logged to WWLogger and



(or) to OMRONFGV Internal Logger if some item with address in inaccessible memory area is used (MRC:11 and SRC:03 informs about "Parameter error: the first address is in an inaccessible area")


DA1:01 SA1:09) from Topic ‘node9’, ... (***) Read only

The following table lists the supported item names for the CPM2x PLCs:


Range Value Range

Format Suffix

IR & SR areas (Bit status)(***)

IR Discrete IR0:00...IR255:15 or 00000...25515

0, 1

IR & SR areas (Word contents) (***)

IR Integer IR0...IR255 or 0...255


Latching Relay area (Bit status)


0, 1

Latching Relay area (Word contents)


Holding Relay area (Bit status)


0, 1

Holding Relay area (Word contents)


Auxiliary Relay area (Bit status)


0, 1

Auxiliary Relay area (Word contents)


Completion flags for Timers/Counters(**)




Data Memory area (Bit status) (****)


DM665515

0, 1

Data Memory area (Word contents) (****)



Item/point names, corresponding to IR and SR areas, may be without prefix. (Up to version 1.10 the OMRONFGV Server supports IR and SR item/point names only without prefix.)



suffix "S" ("s")) and for 16-bit BCD is from 0 to 9999. The value range for 32-bit integer is from -2147483648 to 2147483647 and for 32-bit BCD is from 0 to 99999999. Default value range for Integer Tag Type is unsigned integer.



(**) Read only (***) Addresses 50 to 199 in IR & SR area in CPM2A/CPM2C PLCs and 20 to 199 in IR & SR area in CPM1/CPM1A/SRM1(-V2) PLCs are read only. (****) Addresses DM1024 to DM6143 in CPM1/CPM1A PCs and DM2048 to DM6143 in CPM2A/CPM2C/SRM1(-V2) PCs are read only.

If item/point represents a separate bit in word area (relevant in CIO, IR&SR, LR, HR, AR

or DM areas), then two conventions are useful for item/point naming: 1) Since Server version 1.11 a letter ‘:’ (or ‘.’) can be used as a separator between word

address and bit address. For example, bit number 3 in word number 100 of CIO area can be specified as IR100:03 (or IR100.03).


address in this case is specified by the leftmost four digits (DM area), by the leftmost

three digits (Input/Output register area CIO or IR&SR area) and by the leftmost two

digits (LR, HR and AR areas). Therefore every item name, representing Bit status,

must contain at least 6 digits (DM area), 5 digits (Input/Output register area CIO or

IR&SR area) and 4 digits (LR, HR and AR areas items). If necessary, then item name contains leading zeroes. Note: Since Server version 1.11 set WIN.INI entry ItemNaming=1 (see chapter



The following examples show the correct format for item names for C/CPM2x PLCs:

00201 - CIO area (Bit status), word address 2, bit number 1.

IR2:01 - CIO area (Bit status), word address 2, bit number 1. Name valid since Server version 1.11

211 - CIO area (Word contents), word address 211. LR6210 - Latching Relay area (Bit status), word address 62, bit number 10. DM21 - Data Memory area (Word contents), word address 21.



CS1/CJ1 PLCs The following table lists the supported item names for the CS1/CJ1 PLCs:


Range Value Range

Format Suffix

CIO Area (Bit status)

CIO Discrete CIO0:00...CIO6143:15 or 000000...614315

0, 1

CIO Area (Word contents)

CIO Integer CIO0... CIO6143 or 0...6143


Work Area (Bit status)

W Discrete W0:00... W511:15 or W00000... W51115

0, 1

Work Area (Word contents)

W Integer W0... W511


Holding Area (Bit status)

H Discrete H0:00... H511:15 or H00000... H51115

0, 1

Holding Area (Word contents)

H Integer H0... H511 (*) u s b f r g l m d e c

Auxiliary Area (Bit status) (**)

A Discrete A0:00... A959:15 or A00000... A95915

0, 1

Auxiliary Area (Word contents) (**)

A Integer A0... A959


Data Memory DM Area (Bit status)

D

/DM

Discrete D0:00...D32767:15 or DM0000000...

DM3276715

0, 1

Data Memory DM Area (Word cont.)

D

/DM

Integer D0...D32767 or DM0...DM32767


Extended Data (Bit status) (***)

E

/EM

Discrete E0:00...E32767:15 or EM0000000...

EM3276715

0, 1

Extended Data (Word cont.) (***)

E

/EM

Integer E0... E32767 (*) u s b f r g l m d e c

Timer Completion Flags (****)

T Discrete T0... T4095 0, 1

Counter Completion Flags (****)

C Discrete C0... C4095 0, 1

Timer PVs PVT

/ PT

Integer PVT0... PVT4095 or PT0... PT4095


Counter PVs PVC

/ PC

Integer PVC0... PVC4095 or PC0... PC4095


Index Registers IR Long IR0... IR15 (*) m

Data Registers (*****)

DR Integer DR0... DR15 (*) u s b

Item/point names, corresponding to CIO Area, may be without prefix. (Up to version 1.10 the OMRONFGV Server supports CIO item/point names only without prefix.)





suffix "S" ("s")) and for 16-bit BCD is from 0 to 9999. The value range for long or 32-bit integer is from -2147483648 to 2147483647 and for 32-bit BCD is from 0 to 99999999. Default value range for Integer Tag Type is unsigned integer.

Value range for integers with forced status (item/point name with suffix "F" ("f")) is from -

2147483648 to 2147483647. CIO Area, Work Area and Holding Area integers (and bits of words) can be forced.

Value range of bits with forced status (Timer Completion Flags and Counter

Completion Flags can be forced) is the following:

0: Bit is OFF but not Forced; 1: Bit is ON but not Forced; 2: Bit has been forced OFF; 3: Bit has been forced ON;

(**) Data cannot be written to addresses A000…A447 in the Auxiliary Area. (***) Current bank only (Memory Area code 98). (****) Timer Completion flags and Counter Completion flags on CS1 are read only. (*****) Not supported on CJ1 controllers.

If item/point represents a separate bit in word area (relevant in CIO, W, H, A, DM, and

EM areas), then two conventions are useful for item/point naming: 1) Since Server version 1.11 a letter ‘:’ (or ‘.’) can be used as a separator between word

address and bit address. For example, bit number 3 in word number 100 of CIO area can be specified as CIO100:03 (or CIO100.03).


address in this case is specified by the leftmost five digits (DM and EM area items), by

the leftmost four digits (CIO area) and by the leftmost three digits (W, H or A items).

Therefore every item name, representing the Bit, must contain at least 7 digits (DM

and EM area items), 6 digits (CIO area items) and 5 digits (W, H and A items). If necessary, item name contains leading zeroes. Note: Since Server version 1.11 set WIN.INI entry ItemNaming=1 (see chapter



The following examples show the correct format for item names for CS1 and CJ1 PLCs:

00201 - CIO Area (Bit), word address 2, bit number 1 CIO2:01 - CIO area (Bit status), word address 2, bit number 1. Name valid

since Server version 1.11 257 - CIO Area (Word contents), word address 257

H6210 - Holding Area (Bit), word address 62, bit number 10 DM21 - Data Memory Area with word address 21



CQM1 PLCs The following table lists the supported item names for the CQM1 PLCs:


Range Value Range

Format Suffix

IR & SR area (Bit status)

IR Discrete IR0:00...IR255:15 or 00000... 25515 (**)

0, 1

IR & SR area (Word contents)

IR Integer IR0... IR255 or 0... 255 (**)


LR area (Bit status)


0, 1

LR area (Word contents)


HR area (Bit status)


0, 1

HR area (Word contents)


AR area (Bit status)


0, 1

AR area (Word contents)


Completion flags for Timers/Counters(***)




DM area (Bit status)


DM665515

0, 1

DM area (Word contents)

DM Integer DM0...DM6655 (*) u s b f r g l m d e c

EM area (Bit status)

EM Discrete DM0:0...DM6143:15 or DM000000...

DM614315

0, 1

EM area (Word contents)

EM Integer DM0...DM6143 (*) u s b f r g l m d e c

Item/point names, corresponding to IR and SR areas, may be without prefix.



suffix "S" ("s")) and for 16-bit BCD is from 0 to 9999. The value range for 32-bit integer is from -2147483648 to 2147483647 and for 32-bit BCD is from 0 to 99999999. Default value range for Integer Tag Type is unsigned integer. (**) Represented memory area available in CQM1H-CPU61 CPU. (***) Read only



If item/point represents a separate bit in word area (relevant in IR, SR, LR, HR, AR, DM

and EM areas), then two conventions are useful for item/point naming: 1) A letter ‘:’ (or ‘.’) can be used as a separator between word address and bit address.

For example, bit number 3 in word number 100 of IR & SR area can be specified as IR100:03 (or IR100.03).

2) Item/point name may be without word/bit separator. The word address in this case is

specified by the leftmost four digits (DM and EM areas), the leftmost three digits (IR

and SR areas) and the leftmost two digits (LR, HR and AR areas items). Therefore

every item name, representing Bit status, must contain at least 6 digits (DM and EM

areas), 5 digits (IR and SR areas) and 4 digits (LR, HR and AR areas items). If necessary, then item name must contain leading zeroes. Note: Set WIN.INI entry ItemNaming=1 (see chapter WIN.INI entries) to validate item/point names without word/bit separator.

The following examples show the correct format for item names for CQM1 PLCs:

00201 - IR Input area (Bit status), word address 2, bit number 1. Name valid

with WIN.INI entry ItemNaming=1. IR2:01 - IR Input area (Bit status), word address 2, bit number 1. Name

valid with WIN.INI entry ItemNaming=2 or ItemNaming=3. 102 - IR Output area (Word contents), word address 102

LR62.10 - LR area (Bit status), word address 62, bit number 10 DM21 - DM area (Word contents), word address 21

Event Memory The following table lists the supported item names for the FinsGateway Event Memory.


Range Value Range

Format Suffix

CIO area (Bit status)

Discrete 0:00...32767:15 or 0000000... 3276715

0, 1

CIO area (Word contents)

Integer 0... 32767 (*) u s b f r g l m d e c

DM area (Bit status)


DM3276715

0, 1

DM area (Word contents)

DM Integer DM0...DM32767 (*) u s b f r g l m d e c

Item/point names, corresponding CIO area, are without prefix.



suffix "S" ("s")) and for 16-bit BCD is from 0 to 9999. The value range for 32-bit integer is from -2147483648 to 2147483647 and for 32-bit BCD is from 0 to 99999999. Default value range for Integer Tag Type is unsigned integer



If item/point represents a separate bit in word, then two conventions are useful for item/point naming: 1) A letter ‘:’ (or ‘.’) can be used as a separator between word address and bit address.

For example, bit number 3 in word number 100 of DM area can be specified as DM100:03 (or DM100.03).

2) Item/point name may be without word/bit separator. The word address in this case is specified by the leftmost five digits. Therefore, every item name, representing Bit status, must contain at least 7 digits. If necessary, then item name contains leading zeroes. Note: Set WIN.INI entry ItemNaming=1 (see chapter WIN.INI entries) to validate item/point names without word/bit separator.

The following examples show the correct format for item names for FinsGateway Event Memory:

0000201 - CIO area (Bit status), word address 2, bit number 1.

2:01 - CIO area (Bit status), word address 2, bit number 1. Name valid with WIN.INI entry ItemNaming=1.

257 - CIO area (Word contents), word address 257. DM21 - Data Memory area (Word contents), word address 21. DM0000312 - Data Memory area (Bit status), word address 3, bit number 12.



Data Presentation in Text String Items The contents of consecutive memory areas can be packed into Text strings and accessed by Text string items. The following principles are taking into account: In case of Integer memory area the hex value of each unforced word (short integer) is presented in value string by 4 ASCII chars. For example, if value of Text string item DM0T3 is 'A9FFED00007B' then each value of memory area is calculated as follows: value of area DM0 - is A9FF (here A9 is Hibyte and FF - is Lobyte), it is 43519 decimal; value of area DM1 - is ED00, it is 60672 decimal; value of area DM2 - is 007B, it is 123 decimal. Four chars must be assigned for each memory area in value string otherwise the Server rejects the string. Value string must contain only the following chars: '0', '1', ..., '9', 'A', 'B', ..., 'F'. If there is some other char(s) in value string then the Server rejects whole string (and does not process other (correct) values from this string). Note: The contents of each item in Register Area contents IR in CS1-series PLCs is presented by 8 ASCII chars. The hex value of each forced word in CV-series PLCs and CS1-series PLCs is presented in value string by 8 ASCII chars. For example, if value of Text string item 0T2F is 'AABBCCDD12345678' then value of each memory area is calculated as follows: value of area 0F - is AABBCCDD (here AABB is Hiword for "Forced/Not forced" designation and CCDD - is Loword presenting contents of memory area), it is -1430532899 decimal; value of area 1F - is 12345678, it is 305419896 decimal. Eight chars must be assigned for each memory area in value string otherwise the Server rejects the string. Value string must contain only the following chars: '0', '1', ..., '9', 'A', 'B', ..., 'F'. If there is some other char(s) in value string then the Server rejects whole string (and does not process other (correct) values from this string). In case of Discrete memory areas the value of each forced or unforced bit is presented in value string as 1 ASCII char ('0', '1', '2' or '3'). For example, if value of Text string item T4T3F is '130' then each value of corresponding memory areas is calculated as follows: value of area T4F - is 1 (unforced ON); value of area T5F - is 3 (forced ON); value of area T6F - is 0 (unforced OFF). One char must be assigned for each memory area in value string otherwise the Server rejects the string. Bits of words of Integer memory areas can not be presented as Text string of discrete values. Application in this case must operate with whole words. Item name can not exceed the range of PLC's memory area. For example, invalid is item name DM9999T2 in case of C-series PLC because of memory area range for C-series PLC is from DM0 to DM9999. Value string length can not exceed 128 chars. So, Text string item could represent maximum 32 unforced words, 16 forced words or 128 bits. At the same time number of unforced words, forced words or bits packed in one Text string item also depends on

FINS Message Maximum Size of read and write commands (see OMRONFGV Topic

Definition dialog box in chapter Topic Definition Command) and data read and write commands format. For example, to write one forced word into Input/Output register area CIO (CV-series PLCs and CS1-series PLCs), G area (CV-series PLCs) as well as Work



Area and Holding Area (CS1-series PLCs) it is necessary 4 + 6*16 = 100 bytes in write command. So, number of memory areas what can be packed in one string depends on topic configuration and write command's format. The Server calculates whether it is possible to read (and, if necessary, - to write) whole string contents by one read (or write) command. If impossible - then item is rejected and the following error message is logged in WWLogger and (or) in OMRONFGV Internal Logger:

/OMRONFGV/Invalid point name "xxx" If this error message refers to Text string item then it is reasonable to reduce the length of string, - may be it is a reason of invalid name. Because of write command's format there may be only 2 forced words packed into Text string item in case of SLK or Serial network and about 7 - in other networks. If Text string represents Read/write memory area then Text string item also is Read/write. If memory area is Read only then Text string item also is Read only. If memory area is covered by Text string item then the same memory area is also accessible by single items (Integer, Discrete and Real) in the same topic. Note: Some PLCs do not support multiwrite commands (writing simultaneously into 2 or more addresses) for all memory areas. For example, CV500 model PLC rejects multiwrite commands into Counter Present Value (PC), Register Area contents IR and Register Area contents DR. In such cases it is impossible to write contents of Text string item by one write command. The OMRONFGV Server rejects writing of these strings. Information about rejected strings you can see in WWLogger and (or) in OMRONFGV Internal Logger. If PLC does not support multiwrite commands for some memory area but Server does not recognize it then Server can create multiwrite command and try to process it. In this case the error message like the following will be logged to WWLogger and (or) to OMRONFGV Internal Logger (MRC:11 and SRC:0C informs about "An incorrect parameter code has been specified.")

/OMRONFGV/Received Response Code Error (MRC:11 SRC:0C NTW:00 NOD:00

DA1:01 SA1:09) from Topic ‘node9’, ... Create single items (not strings) to poke values into memory areas not supported for multiwrites.

Monitoring and Controlling Communication with a PLC For each topic, there are following additional items offered by OMRONFGV Server to monitor and control the communication with PLC.

STATUS For each topic, there is a built-in discrete item that indicates the state of communication

with PLC. The discrete item (STATUS) is set to 0 when communication fails and set to 1 when communication is successful.



From InTouch the state of communication may be read by defining an I/O Discrete

tagname and associating it with the topic configured for the PLC and using STATUS as the item name.

From Excel, the status of the communication may be read by entering the following formula in a cell:

=OMRONFGV|topic!STATUS

UPDATEINTERVAL

The UPDATEINTERVAL item is an Integer type Read/Write item used to access the currently set Update Interval (see Topic Definition Command). It indicates the current requested update interval (in milliseconds). The value of this item can be read through DDE or Suite Link. Client can poke new values to this item. The range of valid values is from 10 to 2147483647 milliseconds. The value of zero indicates that no items on this topic are updated. The write commands are still executed (new values written to PLC) if

UPDATEINTERVAL value is 0. Note: By poking a value of zero to the UPDATEINTERVAL item, a client can stop all update activities on the corresponding topic without having to deactivate the items.

MAXINTERVAL

The MAXINTERVAL item is an Integer type Read Only item used to access the measured maximum update interval (in milliseconds) of all items for the corresponding topic for the last completed poll cycle. The range of valid values is from 0 to 2147483647 milliseconds.

The UPDATEINTERVAL and MAXINTERVAL items can be used to tune the performance of communication.

ITEMCOUNT

The ITEMCOUNT item is an Integer type Read Only item used to access the number of active items in the corresponding topic. The range of valid values is from 0 to 2147483647.



ERRORCOUNT

The ERRORCOUNT item is an Integer type Read Only item used to access the number of active items with errors in the corresponding topic. The range of valid values is from 0 to 2147483647.

ERRORITEMS

The ERRORITEMS item is an Integer type Read/Write Only (unique for each topic) used to access the total number of items with invalid item names (these items are rejected by

Server). The ERRORITEMS value can be reset by writing 0 to this item. The range of valid values is from 0 to 2147483647.

WRITECOUNT

The WRITECOUNT item is an Integer type Read Only item used to access the number of write commands (messages) waiting for execution. The range of valid values is from 0 to 2147483647.

For example, in following way the WRITECOUNT item can be used to avoid the increasing of memory occupied by not executed write commands:

- activate the hot link with WRITECOUNT item and start to monitor it;

- activate new write command (by poking new value) only if value of WRITECOUNT becomes equal to 0, e.g. all previous write commands are executed and memory occupied by them is freed.

SUSPEND

Special Read/Write Discrete Item SUSPEND may be used to control the communication

with a separate topic. If application changes SUSPEND value from 0 to 1 then

communication with topic is suspended. If SUSPEND value is changed back to 0 then communication with this topic is resumed. Note: If topic is suspended by setting SUSPEND value to 1, then Server rejects all new

write values to this topic, i.e. no new write messages are created after SUSPEND value has changed from 0 to 1.



Using the OMRONFGV Server with OPC Clients The "OPC & DDE" version of OMRONFGV Server is accessible from OPC Clients. There are the following general steps needed to access an OPC item from OMRONFGV Server: 1. Run OPC Client application and select the "OMRONFGV OPC and DDE Server"

from the list of available OPC Servers. If OMRONFGV Server currently is not running, it will start automatically.

2. Create a new group (or topic if Wonderware OPCLink application is used). 3. If OPC Client supports the validating of items, validate the item before adding it. 4. Add the item. Depending on OPC Client it can be done in several different ways, for

example: a) By entering separately the access path to topic name (valid topic name

configured in OMRONFGV Topic definition) and separately the item name.

b) By entering the full path to item name in the format TopicName.ItemName

where TopicName is the valid topic name configured in OMRONFGV Topic definition. c) By browsing the server address space.

By default the OMRONFGV Server is installed and used as a local OPC Server - both OPC Server and OPC Client reside on same computer. The OMRONFGV Server can run also as a remote OPC Server – in this case OPC Server and OPC Client are located on separate computers. Accessing the remote OPC Server is same as for local OPC Server, but some DCOM (Distributed COM) configuration is required before accessing the remote OPC Server. The DCOM configuration must be done both on OPC Server and OPC Client computers.

Configuring DCOM To access OMRONFGV Server as a remote OPC Server, it is necessary to install OMRONFGV Server on both (OPC Server and OPC Client) computers. (The OMRON FinsGateway software must be installed on both computers otherwise OMRONFGV Server does not run.) Also the DCOM must be configured on both computers. After Server installation the System Administrator must configure DCOM by

Dcomcnfg.exe (or Dcomcnfg32.exe for Win9x) system tool. This utility is located in the Windows system directory – e.g. in \WinNT\system32\ or \Win9x\system\. Below is a simple example how to configure DCOM on NT Workstations for OPC Server computer (computer name JohnB) and on OPC Client computer (computer name SteveL).



Action Remote OPC Server

Computer name – JohnB

OPC Client

Computer name – SteveL

Install the OPC Server.

Run Dcomcnfg.exe

Invoke Default Properties and set

Default Authentication Level to (None),

Default Impersonation Level to Impersonate.

Select OPC Server from Applications list

and click on the Properties… button. Click

on the Location tab, uncheck Run

application on this computer, check

Run application on the following

computer and browse the remote computer JohnB.

Edit Security settings:

1) set the following custom access

permissions: NETWORK, SYSTEM, SteveL;

2) set the following custom launch

permissions: INTERACTIVE, SYSTEM, NETWORK, SteveL;

3) be sure the Default Configuration

Permissions contain SYSTEM.

Click on the Identity tab and select The

interactive user.

Before starting a remote OPC Server, be sure the OPC Server computer and OPC Client computer can access each other on the network. The "Remote Procedure Call" Service should be started on OPC Server computer. Now remote OPC Server is accessible for OPC Client on computer SteveL. To allow the access to more OPC Clients, configure DCOM on each OPC Client computer.



The following table contains most frequent errors when configuring DCOM.

Error message Possible reason

DCOM not installed DCOM has not been installed

Server execution failed 1) OPC Server can not be started

2) Identity for OPC server not properly configured 3) OPC Server is not located on a local hard disk 4) OPC Server path in registry is too long or uses LFN

(Long File Names)

5) DCOMCNFG Location is not set to Run on this

computer.

Class not registered OPC Server has not been registered

RPC server is unavailable 1) Remote Procedure Call service is not running on the OPC Server computer

2) Invalid computer name for remote OPC Server 3) Make sure TCP/IP is installed properly

Interface not supported 1) Permission not granted to OPC Client 2) Guest account disabled

Access is denied 1) DCOM security not configured properly 2) OPC Server application not located on local hard disk

3) SYSTEM account in DCOMCNFG must have Access,

Launch and Configure privileges

Error 80070776 Network error - TCP/IP has not been configured properly

Catastrophic failure 1) Trying to access an object before it is created 2) Unhandled exception is occurs on the OPC Server

Not enough storage SYSTEM account in DCOMCNFG must have Access,

Launch and Configure privileges

Running OMRONFGV "OPC & DDE" version as Windows NT

Service To install OMRONFGV Server "OPC & DDE" version to run as Windows NT Service, the OMRONFGV Server must be started with command line parameter "/Service":

OMRONFGV /Service After this the "OMRONFGV OPC & DDE Server" NT Service will be installed with Startup type "Manual". The Service Startup configuration can be changed by MS Windows NT

Control Panel/Services configuration dialog boxes. The Allow Service to Interact with

Desktop checkbox in "Service" dialog box must be checked (the "Service" dialog box can be invoked by pressing the "Startup" button on "Services" dialog box when Service

OMRONFGV OPC & DDE Server is selected). If Allow Service to Interact with

Desktop is not selected then OMRONFGV Server full functionality is not ensured (e.g. the Server configuration can not be changed, no message boxes will be displayed, etc.). To use OMRONFGV Server "OPC & DDE" version as Windows NT Service you may need to configure DCOM. For details of configuring DCOM refer to Configuring DCOM



section of this manual. If "OMRONFGV OPC & DDE Server" NT Service will be accessed only from local OPC clients (i.e. OMRONFGV Server will not be used as a remote OPC

Server), then custom access and launch permissions "NETWORK" are not needed. To uninstall "OMRONFGV OPC & DDE Server" NT Service, at first the Service must be stopped by Control Panel/Services/Stop and then OMRONFGV Server must be started manually with command line parameter "/DelService":

OMRONFGV /DelService After this the OMRONFGV Server "OPC & DDE" version will be still registered and accessible to OPC clients.

Using OMRONFGV with OPCLink Server The Wonderware OPCLink I/O Server (hereafter referred to as "OPCLink") is a Microsoft Windows application program that acts as a communication protocol converter and allows other Windows application programs access to data from local or remote OPC servers. OPCLink connects to OPC servers, converts client commands to OPC protocol and transfers data back to clients using DDE, FastDDE, or Suite Link protocols. Please refer to Wonderware OPCLink Server and OPC Browser User’s Guide for details how to install, start and use the OPCLink Server. The following information in this section covers only the most important points about using "OPC & DDE" version of OMRONFGV Server with OPCLink Server.

OPCLink Topic Definition The Topic Definition option from OPC Link Configure menu is used to create, modify, or delete OPCLink topic definitions. If OPC Link will communicate with OMRONFGV Server then there must exist one or more topics defined for OMRONFGV Server. There are following important fields on the "OPCLink Topic Definition" dialog box:

Topic Name

Enter a unique name (e.g. PLC2) for the PLC in this field. If using InTouch then same Topic Name is to be entered in the "Add Access Name" dialog box when defining the Access Names for OPCLink Server in InTouch WindowMaker.

OPC Server Name

Select the name of the OPC server (OMRONFGV.OPC_Server) that will be used by this topic. The list box shows the registered OPC servers in the system.

OPC Path

Enter the name of the OPC path (e.g. node2.) used by this topic. This OPC path is the first part of a full OPC item name string common to all items that will be used in this topic. The available OPC paths for OMRONFGV Server can be obtained by clicking on "Browse" button (this allows to view the OMRONFGV Server’s exposed address space).



Update Interval Enter the frequency (in milliseconds) that the server will acquire data for the items/points associated with this topic. If 0 (zero) is entered here, OPCLink will not gather data from OMRONFGV Server.

Browse Clicking on this button initiates the browsing through exposed address space of OMRONFGV Server. All currently available item/point names (including data area names and range of addresses) and names of pre-defined (additional) items will appear on "Browse OPC items:" window in alphabetical order.

Accessing OMRONFGV Items via the OPCLink Server The communication protocol addresses an element of data in a conversation that uses a three-part naming convention that includes the application name, topic name and item name. The following briefly describes each portion of this naming convention: application name The name of the Windows program (server) that will be accessing the data element. In the case of data coming from or going to OMRONFGV Server "OPC & DDE" version, the

application portion of the address is OPCLINK. topic name Meaningful names are configured to identify specific devices (PLCs). These names are then used as the topic name in all conversations to that device (PLC). This must be same

name as Topic Name entered in the "OPCLink Topic Definition" dialog box, for example,

PLC2.

Note! You can define multiple topic names for the same PLC to poll different points at different rates. item name A specific data element within the specified topic. The OPCLink Server item syntax follows the following rules. The item names must start with:

d – discrete value i – integer value r – real value m – message value

The item name added to the OPC path of the topic (without the heading type letter) must give a fully qualified OPC item name for the OMRONFGV Server. Some examples of possible item names acceptable by OPCLink Server/OMRONFGV Server connection:

d002113 discrete CIO area (Bit status), word address 21, bit number 13;

iDM100 integer Data Memory area word 100



rDM3R real real floating point item, value is taken from Data Memory area words DM3 and DM4

Using the OMRONFGV Server with Suite Link and DDE Clients The "Suite Link & DDE" version of OMRONFGV Server is accessible from Suite Link

clients (e.g. InTouch) and DDE clients (e.g. Excel). The "OPC & DDE" version of OMRONFGV Server is accessible from DDE clients.

Using the OMRONFGV Server with InTouch To access items/points on Omron PLCs from InTouch, the Access Names and Tag names should be defined in WindowMaker.

Defining the Access Names InTouch uses Access Names to reference real-time I/O data. Each Access Name

equates to an I/O address, which can contain a Node, Application, and Topic. In a distributed application, I/O references can be set up as global addresses to a network I/O Server or local addresses to a local I/O Server. To define the Access Names in WindowMaker node invoke the /Special/Access Names... command. The "Access Names" dialog box will appear.

Click on Add…. The "Add Access Name" Dialog Box will appear:



Note: If Add is selected, this dialog box will be blank when it initially appears. Data has been entered here to illustrate the entries that are made. The following fields are required entries when entering an Access Name Definition:

Access Name In the Access Name box type the name you want InTouch to use to this Access Name.

(For simplicity, use the same name that you will use for the Topic Name here.)

Node Name If the data resides in a network I/O Server, in the Node Name box, type the remote node's name.

Application Name In the Application Name box, type the actual program name for the I/O Server program from which the data values will be acquired. In case the values are coming from the OMRONFGV Server the OMRONFGV is used. Do not enter the .exe extension portion of the program name.

Topic Name Enter the name defined for the topic in the OMRONFGV Server to identify the topic the OMRONFGV Server will be accessing. The Topic Name is an application-specific sub-group of data elements. In the case of data coming from OMRONFGV Server program, the topic name is the exact same name configured for the topic in the OMRONFGV Server. Note: This will usually be the same as the "Access Name", although, if desired, they may be different. However, it must be the same name used when the topics were configured

in section Configuring the OMRONFGV Server.

Which protocol to use Select the protocol (DDE or Suite Link) that you are using.



When to advise server Select Advise all items if you want the Server program to poll for all data whether or not it is in visible windows, alarmed, logged, trended or used in a script. Selecting this option will impact performance, therefore its use is not recommended. Select Advise only active items if you want the Server program to poll only points in visible windows and points that are alarmed, logged, trended or used in any script.

Click OK to accept the new Access Name and close the "Add Access Name" dialog box. The "Access Names" dialog box will reappear displaying the new Access Name selected in the list.

Click Close to close the "Access Names" dialog box.

Defining the Tag names To define the Tag names associated with the new "Access Name", invoke the /Special/Tagname Dictionary... command (in WindowMaker). The "Tagname Dictionary" dialog box will appear:

Click on New and enter the Tag Name. (The tag name defined here is the name InTouch will use. The OMRONFGV Server does not see this name.) Select the tag type by clicking on the Type:… button. The "Tag Types" dialog box will appear:



To access OMRONFGV items, the type must be I/O Discrete, I/O Integer, I/O Real or I/O Message. Select the Tag type. The "Details" dialog box for the tag name will appear:

Select the Access Name for OMRONFGV Server by clicking on the Access Name:… button. The "Access Names" dialog box will appear:

Select the appropriate Access Name and click on Close. (If the Access Name has not

been defined as previously described, click on Add and define the Access Name now.) The "Details" dialog box will appear displaying the selected Access Name:



For integers and reals fill in the Min EU, Max EU, Min Raw and Max Raw fields. These fields control the range of values, which will be accepted from the Server and how the values are scaled. If no scaling is desired, Min EU should be equal to Min Raw and Max EU equal to Max Raw. Enter the OMRONFGV item name to be associated with this tagname in the Item: field in the "Details" box:

(Refer to the Item Names section below for complete details.) Where applicable, the Use Tagname as Item Name option may be selected to automatically enter the tag name in this field. Note: The tag name can only be used if it follows the conventions listed in the Item Names section. Once all entries have been made, click on the Save button (in the top dialog box) to accept the new tagname. To define additional tagnames click on the New button. To return to the WindowMaker main screen, select Close.

Monitoring the Status of Communication with InTouch InTouch supports built-in topic names called DDEStatus and IOStatus, which are used to monitor the status of communication between the Server and InTouch. For more information on the built-in topic names DDEStatus and IOStatus, see your online "InTouch User’s Guide".

The status of communication between the Server and InTouch can be read into Excel by entering the following DDE reference formula in a cell on a spreadsheet (in following

examples node2 is the Topic Name configured for OMRONFGV Server):

=view|DDEStatus!node2 or

=view|IOStatus!node2



Notes on Using Microsoft Excel Data from OMRONFGV topics (nodes) may be accessed from Excel spreadsheets. To do so, enter a formula like the following into a cell on the spreadsheet. =OMRONFGV|topic!item Sometimes, Excel requires the topic and/or item to be surrounded by apostrophes. In the formula, topic must be replaced with one of the valid topic names defined during the Server configuration process. Replace item with one of the valid item names described in the Item Names section.

Reading Values into Excel Spreadsheets Values may be read directly into Excel spreadsheets by entering a DDE formatted formula into a cell, as shown in the following examples: =OMRONFGV|'node2'!'125515' =OMRONFGV|'node3'!'SA1000' =OMRONFGV|'node10'!'IR2' Note: Refer to the Microsoft Excel manual for complete details on entering Remote Reference formulas for cells.

Writing Values to OMRONFGV Points Values may be written to the Server from Microsoft Excel by creating an Excel macro that

uses the POKE command. The proper command is entered in Excel as follows:

channel=INITIATE("OMRONFGV","topicname")

=POKE(channel,"itemname", Data_Reference)

=TERMINATE (channel)

=RETURN()

The following describes each of the above POKE macro statements:

channel=INITIATE("OMRONFGV ","topicname") Opens a channel to a specific topic name (defined in the Server) in an application with name OMRONFGV (the executable name less the .EXE) and assigns the number of that

opened channel to channel.

Note: By using the channel=INITIATE statement the word channel must be used in

the =POKE statement instead of the actual cell reference. The "applicationname"

and "topicname" portions of the formula must be enclosed in quotation marks.

=POKE(channel,"itemname", Data_Reference) POKEs the value contained in the Data_Reference to the specified item name (actual location in the Omron PLC) via the channel number returned by the previously executed INITIATE function. Data_Reference is the row/column ID of the cell containing the data value. For "itemname", use some of the valid item names specified like described in the Item Names section.



=TERMINATE(channel) Closes the channel at the end of the macro. Some applications have a limited number of

channels. Therefore they should be closed when finished. Channel is the channel

number returned by the previously executed INITIATE function.

=RETURN() Marks the end of the macro. The following is an example of Excel macro used to poke value from cell B2 to topic

node2 item DM100: PokeMacro -Ctrl a

=INITIATE("OMRONFGV","node2") =POKE(A2,"DM100",B2) =ON.TIME(NOW()+0.01,"TerminateDDEChannel") =RETURN() TerminateDDEChannel =TERMINATE(A2) =RETURN()

Note: Refer to the Microsoft Excel manual for complete details on entering Remote Reference formulas for cells.



Notes on Improving Server Performance

1. The timing problems The combination of two timing values ("Protocol Timer Tick " value from "OMRONFGV Server Settings" dialog box and "Update Interval" value from "OMRONFGV Topic Definition" dialog box) and total number of send messages for each topic determine the performance of the Server. In all cases number of messages sent to the network multiplied by "Protocol Timer Tick" must fit into "Update Interval" for all topics. For example, if there are two topics with 5 messages in one topic and 6 messages in second, "Update Interval" for both topics is 1000 milliseconds and "Protocol Timer Tick" is 50 milliseconds then total Server work time is 50 * 5 + 50 * 6 = 250 + 300 = 550 milliseconds, but in this case if total amount of information sent/received to/from the SYSMAC Link network is great and also processing of received data is time consuming then there would be heavy conditions for other Windows applications (no time to work between each 50 milliseconds). For a great InTouch applications (with 500 items and more) it is recommended to increase "Protocol Timer Tick" value to 100 milliseconds and "Update Interval" value to 1500 milliseconds - this will allow other Windows applications run at better timing conditions.

2. The using of PLC memory areas The OMRONFGV Server uses FINS commands to exchange information with OMRON Controllers and the maximum size of message is: - 992 words if the Controller is directly connected through the Ethernet network or

Sysmac Net network; - 995 words if the Controller is directly connected through the Controller Link network; - 256 words if the Controller is directly connected through the SYSMAC LINK, Serial communication or Sysmac Board. Depending on client application there are two possible choices for each topic (node):

(1) If Multiple Memory Area Read (see Topic Definition Command) is not used then maximum number of consecutive words can be read by one command. The Server uses the following system to create read commands: the words 0...991 for Ethernet network or Sysmac Net network (0...994 for Controller Link network, 0...255 for SYSMAC LINK, Serial or Sysmac Board) are in the memory area's first message, the words 992...1983 for Ethernet network or Sysmac Net network (995...1989 for Controller Link network, 256...511 for SYSMAC LINK, Serial or Sysmac Board) in the second, etc. The data only from one memory area can be read by one read command. In this case the optimal using of PLC memory is very important - there must be as few as possible commands sent to the network and it is strongly recommended to use consecutive memory addresses for items/points - this will considerably improve the performance of the Server. This choice is recommended if large amount of consecutive data must be read from few memory areas.

To find out how many messages are actually sent to network the commands Dump

Screen or Dump from System Menu can be used (Refer to the Troubleshooting

menu section).



(2) If Multiple Memory Area Read is used then maximum 128 non-consecutive words (also from different memory areas) can be read by one command (this mode does not support long values, floating point values and strings). This choice is recommended if non-consecutive data must be read from different memory areas. Note: Not all Omron PLCs support the Multiple Memory Area Read command. Refer to appropriate Omron PLC user manual for more information.

There is no FINS command for direct bit writing to Omron PLCs. To write the bit value to the IR, LR, HR, AR, DM and EM areas (C200HX/C200HG/C200HE PLCs and SYSMAC Board), to CIO, G, A, DM and Expansion areas (for CV-series PLCs), to IR, LR, HR, AR and DM areas (for C/CPM2x PLCs), to CIO, W, H, A, DM and EM areas (for CS1/CJ1 PLCs), ), to IR, LR, HR, AR, DM and EM areas (for CQM1 PLCs) and to CIO and DM areas in Event Memory the Server at first reads a word (including the corresponding bit) from the PLC. Then according to new bit value this received word is modified and written back to PLC. It means that 16 bits are written to PLC instead of 1 bit. If PLC program changes this word contents between above mentioned read and write commands then it will cause PLC program incorrect execution. It is recommended to write the whole word (where it is possible) instead of separate bit writing - it will improve the performance of the Server. Note: The results will be unpredictable if you use the OMRONFGV Server to write to discretes which are also being used in a ladder logic program. For better results, avoid this practice.

3.Some suggestions for processing of alarms (Discrete values) The following actions are recommended if different time intervals must be used to read Integer and Discrete values: - create two different topics for the same PLC and use greater "Update Interval" for topic with Integers (for example 2000 milliseconds) and smaller "Update Interval" for topic with Discretes (for example 500 milliseconds); - if possible then put together all Discretes in one memory area at consecutive addresses (may be in the PLC program) to minimize number of read messages sent at smaller "Update Interval".

4.Other suggestions For great InTouch applications it is recommended to decrease the amount of log information used for historical trending - historical trends are stored on the disk and therefore disk read/write operations will take more time as permissible. If there are problems with the speed of screen redrawing then possible solutions would be the decreasing of total amount of redrawn information (specially texts) or the increasing of Server timing values "Protocol Timer Tick" and "Update Interval".



Troubleshooting

WIN.INI entries The first time you run the OMRONFGV Server configuration, most of the items in the following list will automatically appear in the WIN.INI file, located in the MS Windows NT system directory (e.g. C:\WINNT). It is an ASCII file and can be altered manually if you wish with any text editor, e.g., MS Windows Notepad (do not use a program that formats text, such as MS Word or Write unless the file is saved as a DOS text). The following is a typical entry for the OMRONFGV Server:

[OMRONFGV]

WriteRetryIndefinitely=0

ConfigurationFile=C:\INTOUCH\

WinIconic=0

WinFullScreen=0

WinTop=112

WinLeft=0

WinWidth=200

WinHeight=168

ShowEvents=1

ShowSend=0

ShowReceive=0

ShowErrors=1

MultiWrite=0

SlowPollInterval=15

ItemWritesLimit=0

ConsecutiveWriteErrors=3

ItemNaming=3

The MultiWrite entry is used to enter the data writing principles for the Server. The following values can be entered.

(1) If MultiWrite=0 then for each new write value a separate write message is created. The values in the PLC are changed by the Server in the same sequence as they are changed in the user (client) application. In this case the data update rate is low if application changes values very frequently.

(2) If MultiWrite=1 then the same message can be used for the writing of new values into the consecutive memory addresses for the same memory area (for example, into DM0, DM1, DM2...). Up to 124 consecutive values can be included in the same write command. The new value can be added only to the end of last write message (last message in the list of pending write messages). Therefore some values may be written into the PLC memory simultaneously even if the client application changes them step-by-step. In this case the writing speed can be seriously increased. For example, the client application sequentially changes the values of following 248 items: DM0, DM1, ... , DM247 and the values of following 248 items: 500R, 502R, ... ,



994R. In this case the Server creates only four write messages to write the new values for all the changed items. If the values of the same Items are changed in the following sequence: DM0, 500R, DM1, 502R, DM2, ... then Server creates a separate write message for the each new write value.

(3) If MultiWrite=2 then Server tries to include the new write value into the some of

previously created messages ignoring the sequence of data changing in the client application.

Important! If MultiWrite=2 then maximum writing speed is achieved, but this option is not

recommended if data changing sequence is important for PLC program!

The ItemWritesLimit entry is used to enter the maximum number of non-processed

pending write messages for one item. For example, ItemWritesLimit = 3. An application frequently assigns new values for item DM0. Number of non-processed write pending messages grows because of restricted communication speed, and in some moment there are 3 write messages created by the Server with values for DM0. Now the Server does not create a new write message when receives the next value for DM0, but changes writing value in the last write message. (So, previous value is lost). New message is created again only after at least one write message with DM0 is processed and number of

pending write messages for DM0 is not equal to ItemWritesLimit.

If ItemWritesLimit=0 (default value) then there are no limits to number of write messages for one item. In this case all values assigned to an item by an application are transferred to the PLC. The Server can occupy PC's memory with non-processed write messages if an application pokes new values very frequently. By assigning non-zero value to

ItemWritesLimit you can avoid memory-overfilling problem but in this case some poked values may be lost. This option is not useful when each value assigned by an application must be transferred to the PLC.

ItemWritesLimit and MultiWrite options are compatible.

The ConsecutiveWriteErrors entry is used to enter the number of consecutive

unsuccessful write retries for one write command. If after ConsecutiveWriteErrors the write command still is not executed then write command is deleted from the list of active (pending) write messages and write is finally rejected. The unsuccessful bit writing is

performed ConsecutiveWriteErrors + 1 times. If the total amount of messages in the list of active write messages exceed 300 then every write message is performed only once

not taking into account the ConsecutiveWriteErrors value.

The WriteRetryIndefinitely entry is used to disable the deleting of pending write messages when slow poll mode is started. As default (no WriteRetryIndefinitely entry in WN.INI or WriteRetryIndefinitely=0) all write messages for this topic are deleted when topic enters the slow poll mode. To disable this the following entry can be used: WriteRetryIndefinitely=1

Note! Be careful when using this setting if PLC is switched off but client application continues to generate new values to be written to this PLC - it can cause the computer memory overfill with memory allocated for write messages.

The SlowPollInterval entry is used to enter the slow poll mode update interval (in seconds). The slow poll mode will be set for the topic that either does not respond or for



consecutive response errors. If the Server reinitializes the communication with the Board

then SlowPollInterval value is used as a re-initialization retries interval.

The ItemNaming entry is relevant since OMRONFGV Server version 1.11, when the following very significant additions to item/point naming conventions were implemented:

- items, representing bit in word, can contain a letter ‘:’ (or ‘.’) as a word/bit separator, - additional memory areas are supported (e.g. Expansion DM Areas Banks 0 to 7 in

CV-series PLCs). - new (additional) item/point name prefixes implemented to designate memory areas of

CV-series and CS1/CJ1 PLCs already supported in former Server versions (see chapter Item Names).

The following are additional data formats implemented in Server version 1.11: - Long format, - BCD long format, - BCD floating point format, - ASCII strings using Low-order-Byte, - ASCII strings using High-order-Byte, - ASCII strings using Both-Bytes.

By using entry ItemNaming you can configure the OMRONFGV Server to validate item/points only concerning former (up to Server version 1.10) naming conventions, or only naming conventions, implemented in Server version 1.11, or both naming conventions simultaneously.

If ItemNaming=1, then Server validates item/point names only concerning former (up to OMRONFGV Server version 1.10) naming conventions. This option is recommended with application already developed for communication with former Server versions. If

ItemNaming=2, then Server validates item/point names only concerning naming

conventions implemented additionally into version 1.11. If ItemNaming=3 (default value), then Server validates item/point names concerning all naming conventions, presented in chapter Item Names. In this case, if item/point name prefix or suffix for the same area (or data type) differs in former and implemented naming conventions, then with

ItemNaming=3 you can operate with both item names simultaneously. In case of naming convention conflict (it is, the same prefix or suffix in different conventions indicates different memory areas or data types), then items/points are validate concerning naming conventions implemented additionally into version 1.11. The following are item/point naming conventions conflict cases:

1. Concerning former item/point naming conventions suffix ‘F’ (or ‘f’) is used to indicate forced addresses. Since version 1.11 suffix ‘F’ (or ‘f’) is used to indicate Floating-point format. So, you can operate with forced addresses only with WIN.INI

entry ItemNaming=1. 2. Concerning former item/point naming conventions the Step Area Flag Status in

CV-series PLCs (memory area code 04) is indicated by prefix “SA” (or “sa”) and the Step Timer Present Value (memory area code 84) is indicated by prefix “ST” (or “st”). Concerning naming conventions implemented additionally into version 1.11 the Step Area Flag Status in CV-series PLCs is indicated by prefix “ST” (or “st”), but Step Timer Present Value is not supported at all. So, in CV-series PLCs you can operate with Step Timer Present Value (memory area code 84) by using prefix “ST” (or “st”) and Step Area status (memory area code 44) by using prefix

“SS” (or “ss”) only with WIN.INI entry ItemNaming=1.



The default values (they are used if WIN.INI file does not contain these entries) are the

following: ConsequtiveWriteErrors=3, SlowPollInterval=15, ItemWritesLimit=0,

MultiWrite=0 and ItemNaming=3.

Troubleshooting menu The following debugging choices are appended to the Server’s System Menu (the menu that appears when you click on the "-" box in the upper left hand corner of the Server window):

Suspend Protocol / Resume Protocol - these choices permit you to turn protocol processing on and off, what means that you can suspend access to the PLC.

Show Send - if checked then all outgoing user data is displayed in hexadecimal format.

Show Receive - if checked then all incoming user data is displayed in hexadecimal format.

Show Errors - if checked then all information about errors is displayed.

ShowEvents - if checked then Server logs the information about situations when the total number of active (pending) write messages exceeds 300. It may happen when the Server has timing problems when executing write commands. When such warnings appear then it is recommended to modify the Server timing settings or to reduce the total amount of write data in the client application. Otherwise the possibility of loosing write data increases. Information about suspended and resumed topics is displayed if

ShowEvents is checked.

ShowBadWrites - if checked then Server displays information about all situations when data write commands are not executed successfully and after

ConsecutiveWriteErrors retries the write is rejected and write message is deleted from list of active (pending) write messages. This option (if checked) is effective even if other error logging is stopped.

ShowAllRejectedWrites - option is useful when communication with a separate topic (topics) is suspended by Item SUSPEND (see chapter Item Names) and the Server rejects each write to this topic (topics). If checked then information about each rejected write value is reported to WWLogger and (or) to OMRONFGV Internal Logger. If not checked then Server rejects each write to suspended topic(s) without logging any information.

Verbose - if checked then all information about errors (except errors indicated in other choices) is displayed. This option is useful for getting additional information about error situations:

When this option is checked simultaneously with the option Show

Errors then outgoing user data as well as incoming user data is displayed in addition to the error report. For some types of errors the Server gives explanation of possible error reason. If client application closes communication with a topic then the Server immediately deletes all this topic's messages from message lists. If write messages are still in the list of active (pending) messages these



write messages are deleted not trying to perform them. If Verbose

option is checked simultaneously with the option ShowBadWrites then information about not performed and deleted write messages is displayed.

Dump - displays all information about board, active topics and data items.

DumpScreen - if checked information about active topics and messages is displayed in OMRONFGV main window.

All debugging information (except DumpScreen option) is displayed via the Wonderware Logger (and also to OMRONFGV Internal Logger if Show Logger checked), which must be active for these commands to work.

Warning: if you check Show Send and/or Show Receive debug output grows very fast.



KLINKMANN OY OMRONFGV Communication Server

Revision History

Jul 99 Rev 1.0 First Release Nov 99 Rev 1.1 CS1-series PLCs support added. SYSMAC Board

configuration example added Mar 2000 Rev 1.2 Text string items added Jun 2001 Rev 1.3 OPC compliance information added Mar 2002 Rev 1.4 Installation from CD information added. Jan 2003 Rev 1.5 CQM1, CPM2x, CJ1 and EventMemory support added.

Additional item/point naming conventions added. Modified chapter Getting Started Quickly with OMRONFGV Server.

Oct 2014 Rev 1.6 Modifications made for Windows 7 32-bit support: “Installing the OMRONFGV Server” section modified, “Licensing by using HASP HL key” and “Software license key” sub-sections added.

omronfgv communication server - klinkmannmedia.klinkmann.com/servers/docs/400xxm16.pdf · ethernet...

Documents