FieldServer FS-8704-16 User Manual

-

A Sierra Monitor Company

Driver Manual

(Supplement to the FieldServer Instruction Manual)

FS-8704-16 Omron FINS

APPLICABILITY & EFFECTIVITY

Effective for all systems manufactured after May 1, 2004

FS-8704-16 Omron FINS Manual Table of Contents

TABLE OF CONTENTS

1. Omron FINS Description...................................................................................... 1

2. Driver Scope of Supply........................................................................................ 2

1.01 Supplied by FieldServer Technologies for this driver ....................................... 2

1.02 Provided by the Supplier of 3rd Party Equipment.............................................. 2

2.1.1. Required 3rd Party Hardware.........................................................................2

2.1.2. Required 3rd Party Software..........................................................................2

2.1.3. Required 3rd Party Configuration...................................................................2

3. Hardware Connections ........................................................................................3

1.03 Hardware Connection Tips / Hints.................................................................... 3

1.04 Example of Omron PLC Configuration using Omron ETN11 Module. .............. 4

4. Configuring the FieldServer as a FINS Client.................................................... 6

1.05 Data Arrays/Descriptors ................................................................................... 6

1.06 Driver Specific FieldServer Parameters ........................................................... 7

1.07 Client Side Connection Descriptors.................................................................. 7

1.08 Client Side Node Descriptors ...........................................................................8

1.09 Client Side Map Descriptors............................................................................. 9

4.1.1. FieldServer Related Map Descriptor Parameters..........................................9

4.1.2. Driver Related Map Descriptor Parameters................................................... 9

4.1.3. Timing Parameters......................................................................................10

4.1.4. Map Descriptor Example 1 – IO Read.........................................................11

4.1.5. Map Descriptor Example 2 – IO Write.........................................................12

4.1.6. Map Descriptor Example 3: Clock Read:.....................................................13

4.1.7. Map Descriptor Example 4: Clock Write:..................................................... 13

4.1.8. Map Descriptor Example 5: Read CPU Cycle Times: ................................. 13

4.1.9. Map Descriptor Example 6: Run-Stop PLC:................................................ 14

4.1.10. Map Descriptor Example 7: Read CPU Status:........................................14

5. Configuring the FieldServer as a FINS Server.................................................15

1.010 Server Side Connection Descriptors .............................................................. 15

1.011 Server Side Node Descriptors ........................................................................ 16

1.012 Server Side Map Descriptors.......................................................................... 17

5.1.1. FieldServer Specific Map Descriptor Parameters........................................17

5.1.2. Driver Specific Map Descriptor Parameters.................................................17

5.1.3. Map Descriptor Example 1: IO Read...........................................................18

5.1.4. Map Descriptor Example 2: IO Write...........................................................19

5.1.5. Map Descriptor Example 3: Clock Read:.....................................................19

5.1.6. Map Descriptor Example 4: Clock Write:..................................................... 19

5.1.7. Map Descriptor Example 5: CPU Cycle Times:...........................................19

5.1.8. Map Descriptor Example 6: Run-Stop PLC:................................................ 20

5.1.9. Map Descriptor Example 7: CPU Status:.....................................................20

Appendix A. Advanced Topics................................................................................ 21

Appendix A.1. Driver Map Descriptor Parameter’s Bounds ..................................... 21

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8704-16 Omron FINS Manual Table of Contents

Appendix A.2. PLC status to execute commands.................................................... 22

Appendix A.3. End Codes........................................................................................ 23

Appendix B. Driver Notes ........................................................................................ 30

Appendix B.1. Data Storage .................................................................................... 30

Appendix B.2. Driver stats ....................................................................................... 32

Appendix B.3. Driver Error Messages...................................................................... 33

Appendix C. Troubleshooting tips.......................................................................... 35

Appendix C.1. Connection Tips & Hints................................................................... 35

Appendix D. Revision History .................................................................................37

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8704-16 Omron FINS Manual Page 1 of 37

1. Omron FINS Description

The Ethernet Omron FINS driver allows the FieldServer to transfer data to and from
devices over Ethernet using Omron FINS protocol. The FieldServer can emulate either
a Server or Client.

FINS is an Omron protocol which can be used by a PLC program to transfer data and
perform other services with a remote PLC connected on an Ethernet Network. It can
also be used by remote devices such as PC’s and FieldServer’s to transfer data and
perform other services.

The protocol uses the Ethernet protocol called UDP to carry the FINS messages back
and forth. The UDP protocol is not connection based and reliability is achieved by using
confirmation messages.

This Ethernet Driver can be used to transfer data to and from the Nodes supporting
FINS communications.

Max Nodes Supported
FieldServer Mode Nodes Comments

Omron limit the set of permitted nodes to 126. They are

Client 126

numbered 1 to 126 corresponding to the last byte of the

remote node IP address.

Server 20

The FieldServer can emulate a maximum of 20 Omron

FINS servers.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8704-16 Omron FINS Manual Page 2 of 37

2. Driver Scope of Supply

1.01 Supplied by FieldServer Technologies for this driver

FieldServer Technologies
PART #

Description

FS-8915-10 UTP cable (7 foot) for Ethernet connection
FS-8704-16 Driver Manual.

1.02 Provided by the Supplier of 3rd Party Equipment

2.1.1. Required 3rd Party Hardware

Part # Description

2.1.2. Required 3rd Party Software

CX-Programmer Software or any other compatible Software by Omron to setup
the PLC

2.1.3. Required 3rd Party Configuration

The Omron PLC device needs to be set into the Automatic Address Generation

mode using the CX-Programmer or any other compatible Software.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8704-16 Omron FINS Manual Page 3 of 37

3. Hardware Connections

The FieldServer is connected to the PLC as shown in connection drawing.

Configure the PLC according to manufacturer’s instructions to work with other FINS
supported device.

1.03 Hardware Connection Tips / Hints

If communication doesn’t start check the following.

1. Are the FieldServer and PLC on the same network?

2. Are all intended Nodes configured to communicate on FINS?

3. Are all FINS Nodes configured to use the same Port Number?

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8704-16 Omron FINS Manual Page 4 of 37

4. Is the Network healthy?

1.04 Example of Omron PLC Configuration using Omron ETN11 Module.1

Setting the Node Number

With the FINS communications service, when there are multiple Ethernet Units connected to the
Ethernet network, the Ethernet Units are identified by node numbers. Use the node number switches
to set the node number between 01 and 7E hexadecimal (1 to 126 decimal). Do not set a number
that has already been set for another node on the same network.

The left switch sets the sixteens digit (most significant digit) and the right switch sets the ones digit
(least significant digit). The node number is factory set to 01. When using the automatic generation
method for address conversion, set the node number to the same value as that of the local IP
address switches. If this is not possible, then either the IP address table method or the combined

method must be used for address conversion. For details, refer to 4-2 CPU
Bus Unit System Setup. If the FINS communications service is not being used over the Ethernet

network, then there is no problem if the node number duplicates that of another Ethernet Unit. The
node number must still be set from 01 to 7E, however, or the ERC indicator will light.

Note Turn OFF the power supply before setting the node number.

Setting the Local IP Address

The nodes on an Ethernet network are identified by IP addresses. Each IP address is set with 32 bits
of binary data. These 32 bits are divided into four 8- bit fields called octets, and each octet is
expressed as four decimal numbers. At CS-series Ethernet Units, four bits are expressed as a
hexadecimal digit, and the eight hexadecimal rotary switches (the local IP address switches) on the
back of the Unit are used to set the local IP address. Set the eight switches in hexadecimal as shown
below, combining SW1 and SW2, SW3 and SW4, SW5 and SW6, and SW7 and SW8. Each switch
can be set from 0 to F.

1

The following notes are extracted from the Omron Manual “W343-E1-05 9/03”

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8704-16 Omron FINS Manual Page 5 of 37

The switches are all factory-set to 0 (00.00.00.00). The Ethernet Unit cannot be used with this
setting; a proper IP address must be set.
The following settings cannot be made for the IP address, or the ERC indicator will flash.
All bits in the network number field set to 0 or 1.
All bits in the host number field set to 0 or 1.
All bits in the subnet number field set to 1.
The beginning of the IP address set to 127 (7F Hex) Example: 127.35.21.16

Note 1. When using the automatic generation method for address conversion, set switches 7 and 8

to the same values as the node number setting, and set the rest of the host number to zeroes. For

details regarding the host number, refer to 1-7 IP Addresses. The value for the host number field in

the IP address must match the value for the node number or the ERC indicator will flash.

2. If a subnet mask is to be set, use the CX-Programmer to set it in the CPU Bus Unit System Setup.

For details, refer to 4-2 CPU Bus Unit System Setup.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8704-16 Omron FINS Manual Page 6 of 37

4. Configuring the FieldServer as a FINS Client

For a detailed discussion on FieldServer configuration, please refer to the FieldServer
Configuration Manual. The information that follows describes how to expand upon the
factory defaults provided in the configuration files included with the FieldServer (See
“.csv” sample files provided with the FieldServer).

This section documents and describes the parameters necessary for configuring the
FieldServer to communicate with a FINS Server. As a Client this driver reads and writes
data to Server Nodes. Server nodes should be FINS capable and be configured to

communicate over FINS

1.05 Data Arrays/Descriptors

The configuration file tells the FieldServer about its interfaces, and the routing of
data required. In order to enable the FieldServer for FINS communications, the
driver independent FieldServer buffers need to be declared in the “Data Arrays”
section, the destination device addresses need to be declared in the “Client Side
Nodes” section, and the data required from the servers needs to be mapped in the
“Client Side Map Descriptors” section. Details on how to do this can be found below.

Note that in the tables, * indicates an optional parameter, with the bold legal value
being the default.

Section Title

Data_Arrays

Column Title Function Legal Values

Data_Array_Name Provide name for Data Array

Provide data format. Each Data

Data_Array_Format

Array can only take on one
format.

Up to 15 alphanumeric
characters
Float, Bit, UInt16,
SInt16, Packed_Bit,
Byte, Packed_Byte,

Swapped_Byte
Number of Data Objects. Must
be larger than the data storage

Data_Array_Length

area required by the Map

1-32767
Descriptors for the data being
placed in this array.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8704-16 Omron FINS Manual Page 7 of 37

Example

// Data Arrays
Data_Arrays
Data_Array_Name, Data_Format, Data_Array_Length,
DA_CIO, UInt16, 5143
DA_WR, UInt16, 511
DA_HR, Uint16, 511

DA_DM, Uint16, 32767

1.06 Driver Specific FieldServer Parameters

Section Title

FieldServer

Column Title Function Legal Values

Title Name for FieldServer Text

Specify physical node Id on
network.
This is the last byte of the
IP Address of the

System_Node_Id

FieldServer. eg. If

1-126

FieldServer’s IP Address is

192.168.1.81 then this
parameter should be set to
81

Example

// FieldServer Driver specific parameters
FieldServer
Title, System_Node_Id
Fins Client, 81

1.07 Client Side Connection Descriptors

Section Title

Adapter

Column Title Function Legal Values

Adapter Adapter Name N1, N22
Protocol Specify protocol used Fins, omn_fins or fins_udp

Udp_port_number Specify UDP port number 0, 9600 etc

2

Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for

details of the ports available on specific hardware.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8704-16 Omron FINS Manual Page 8 of 37

Example

// Client Side
Connections

Adapters
Adapter, Protocol, Udp_port_number
N1, Fins, 9600

1.08 Client Side Node Descriptors

Section Title

Nodes

Column Title Function Legal Values

Node_Name Provide name for node

Up to 32 alphanumeric
characters

IP_Address Provide IP Address of PLC Eg. 192.168.1.105

Node number set at PLC

The node number should

Node_ID

correspond to the last byte of

1-126
the IP address. Eg. 105
corresponds to the example IP
address above.

Protocol Specify protocol used Fins, omn_fins or fins_udp

Adapter

*Net_Number

Specify which port the device is
connected to the FieldServer
Provide the network number of
PLC

N1, N23

1-255

Example

// Client Side Nodes

Nodes
Node_Name, IP_Address, Node_ID, Protocol, Adapter, Net_Number
PLC 1, 192.168.1.5, 1, Fins, N1, 1

3

Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for

details of the ports available on specific hardware.

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]

FS-8704-16 Omron FINS Manual Page 9 of 37

1.09 Client Side Map Descriptors

4.1.1. FieldServer Related Map Descriptor Parameters
Column Title Function Legal Values

Map_Descriptor_Na
me

Data_Array_Name

Data_Array_Offset

Function

Name of this Map
Descriptor
Name of Data Array
where data is to be
stored in the
FieldServer
Starting location in
Data Array
Function of Client Map
Descriptor

Up to 32 alphanumeric
characters

One of the Data Array names
from “Data Array” section
above

0 to maximum specified in
“Data Array” section above

RDBC, WRBC, WRBX

4.1.2. Driver Related Map Descriptor Parameters
Column Title Function Legal Values

One of the node names
specified in “Client Node
Descriptor” above

CIO-WORD, WR-WORD, HR­WORD, AR-WORD, EM­WORD

Node_Name

*Data_Type
(see Note 1

Appendix A.1)

Name of Node to fetch
data from

Data type

Length

Address

*Memory_Code
(see Note 1
Appendix A.1)

Command_Name
(see Note 2 section

6.1)

*MRC
(see Note 2
Appendix A.1)
*SRC
(see Note 2
Appendix A.1)

Length of Map
Descriptor
Starting address of
read block

Memory code for PLC
memory type

1- 729

0, 1,…100, etc
see Appendix A.1 for details

B0, B1, B2, B3, 82, 98 and
A0 ---- AC

MEMORY AREA READ
MEMORY AREA WRITE
RUN-STOP

Name of the command

CLOCK READ
CLOCK WRITE
CYCLE TIME READ
CPU UNIT STATUS READ

Main Request Code 1,4,6,7

Sub Request Code 1,2,20

FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com

Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: [e-mail]