FieldServer FS-8700-22 X30 User Manual

Driver Version:

1.00

A Sierra Monitor Company

Driver Manual

(Supplement to the FieldServer Instruction Manual)

FS-8700-22 X30 DeviceNet Slave Adapter

Driver

APPLICABILITY & EFFECTIVITY

Effective for all systems manufactured after May 1, 2001

Document Revision: 2

FS-8700-22_X30_DeviceNet_Slave Manual Table of Contents

TABLE OF CONTENTS

1.

X30 DEVICENET SLAVE DESCRIPTION....................................................................... 3

2.

DRIVER SCOPE OF SUPPLY......................................................................................... 4

2.1.

Supplied by FieldServer Technologies for this driver.................................................. 4

2.2.

Provided by the Supplier of 3rd Party Equipment ........................................................ 4

2.2.1. Required 3rd Party Software .................................................................................... 4

2.2.2. Required 3rd Party Configuration ............................................................................. 4

2.2.3. Optional Items......................................................................................................... 4

3.

HARDWARE CONNECTIONS ........................................................................................ 5

3.1.

Hardware Connection Tips / Hints.............................................................................. 5

4.

CONFIGURING THE FIELDSERVER AS A DEVICENET SLAVE .................................. 6

4.1.

DeviceNet Settings..................................................................................................... 6

4.2.

Server Side Connection Descriptors........................................................................... 7

4.3.

Server Side Node Descriptors .................................................................................... 7

4.4.

Server Side Map Descriptors...................................................................................... 8

4.4.1. FieldServer Specific Map Descriptor Parameters .................................................... 8

4.4.2. Driver Specific Map Descriptor Parameters............................................................. 8

4.4.3. Map Descriptor Example......................................................................................... 9

APPENDIX A. ADVANCED TOPICS .................................................................................... 10

Appendix A.1. DeviceNet X30 LED indicators .................................................................... 10

Appendix A.2. Using RSNetWorx ....................................................................................... 10

Appendix A.3. Using RSLogix 5000.................................................................................... 10

APPENDIX B. DRIVER NOTES............................................................................................ 11

Appendix B.1. Setting the FieldServer’s DeviceNet MAC ID and Baudrate......................... 11

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-8700-22_X30_DeviceNet_Slave Manual Page 3 of 12

1. X30 DeviceNet Slave Description

The X30 DeviceNet Slave Adapter driver can be used to emulate a single slave station on a
DeviceNet network. The FieldServer DeviceNet adapter is implemented as an ODVA profile 12
communications adapter and acts as a group 2 only server on the DeviceNet network.
Standard DeviceNet baudrates of 125k, 250k and 500kbit/s are supported. DeviceNet
masters/scanners can open an IO connection of up to 512 Bytes in each direction to the
FieldServer.

Max Nodes Supported

FieldServer Mode Nodes Comments

Server 1 The FieldServer can only emulate one DeviceNet Slave station

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-8700-22_X30_DeviceNet_Slave Manual Page 4 of 12

2. Driver Scope of Supply

2.1. Supplied by FieldServer Technologies for this driver

FieldServer Technologies
PART #

FS-8700-22 Driver Manual.
X30-DeviceNet-Slave Anybus-S DeviceNet Card

Description

2.2. Provided by the Supplier of 3rd Party Equipment

rd

2.2.1. Required 3

RSNetWorx, RSLogix or another Network Scheduling Tool.

Party Software

2.2.2. Required 3rd Party Configuration

Connection to a properly terminated DeviceNet network.

2.2.3. Optional Items

PART # Vendor/Manufacturer Description

-

HMS-Networks Anybus-S DeviceNet eds file

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-8700-22_X30_DeviceNet_Slave Manual Page 5 of 12

3. Hardware Connections

The FieldServer is connected to the DeviceNet network as shown in the connection drawing
below.

3.1. Hardware Connection Tips / Hints

Use the recommended network cable and terminators as specified by the DeviceNet
network organization and/or the manufacturer of your network equipment.

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-8700-22_X30_DeviceNet_Slave Manual Page 6 of 12

4. Configuring the FieldServer as a DeviceNet Slave

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” files
provided with the FieldServer).

This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a DeviceNet Master/Scanner.

The configuration file tells the FieldServer about its interfaces, and the routing of data required.
In order to enable the FieldServer for DeviceNet communications, the driver independent
FieldServer buffers need to be declared in the “Data Arrays” section, the FieldServer virtual
node(s) needs to be declared in the “Server Side Nodes” section, and the data to be provided to
the clients needs to be mapped in the “Server 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.

4.1. DeviceNet Settings

Section Title

FieldServer

Column Title Function Legal Values

System_Station_Address* DeviceNet MAC ID of the FieldServer 0-63

:

Note

The DeviceNet MAC ID can also be set via the DIP switches on the side of the FieldServer
but then the system station address parameter must be removed from the configuration file.
Refer to Appendix B.1 for more information.

Example

// FieldServer

FieldServer
Title, System_Station_Address
DeviceNet_Test, 5

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-8700-22_X30_DeviceNet_Slave Manual Page 7 of 12

4.2. Server Side Connection Descriptors

Section Title

Connections

Column Title Function Legal Values

Adapter Adapter Name DNet
Protocol Protocol name X30_DNet_Slave
DNet_Slave_Baudrate Baudrate 125K , 250K , 500K

Example

// Server Side Connections

Connections
Adapter, Protocol, DNet_Slave_Baudrate
DNet, X30_DNet_Slave, 500K

4.3. Server Side Node Descriptors

Section Title

Nodes

Column Title Function Legal Values

Node_Name Provide name for node Up to 32 alphanumeric characters
Node_Id MACID 0 - 63 (same as system_station_address)
Protocol Specify protocol used X30_DNet_Slave

Example

// Server Side Nodes

Nodes
Node_Name, Node_Id, Protocol
DN5, 01, X30_DNet_Slave

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-8700-22_X30_DeviceNet_Slave Manual Page 8 of 12

4.4. Server Side Map Descriptors

4.4.1. FieldServer Specific Map Descriptor Parameters

Column Title Function Legal Values

Map_Descriptor_Name Name of this Map Descriptor

Name of Data Array where

Data_Array_Name

Data_Array_Offset

Function

Scan_Interval Buffers Update Period > 0.001s

data is to be stored in the
FieldServer
Starting location in Data
Array

Function of Server 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 -Reads data from the
local input buffer
WRBC -Writes data to the
local output buffer

4.4.2. Driver Specific Map Descriptor Parameters

Column Title Function Legal Values

One of the node names

Node_Name Name of Node

DeviceNet_Data_Type Data Type of local buffer

Address Byte offset into local buffer

Number of

Length

DeviceNet_Data_Type
items in local buffer

specified in “Server Node
Descriptor” above
BYTE, WORD, DWORD,
FLOAT, BOOL
RDBC: 0 – 511
WRBC: 0 – 511
BYTE: 1 – 512
WORD: 1 – 256
DWORD: 1 – 128
FLOAT: 1 –128
BOOL: 1 – 4096

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]

Note that each address

refers to an individual

local input and output

buffer. Each buffer can

contain up to 512 bytes.

Write function map

descriptor puts

data from the

Output_Data data

array onto the

DeviceNet

network.

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

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

Read function map

descriptor gets data

from the DeviceNet

network and stores it

in the Input_Data

data array.

4.4.3. Map Descriptor Example.

FS-8700-22_X30_DeviceNet_Slave Manual Page 9 of 12

// Client side Map Descriptors

Map_Descriptors

Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, DeviceNet_Data_Type, Address, Length, Scan_Interval

Get_Data, Input_Data, 0, RDBC, CN5, WORD, 0, 10, 1s

Put_Data, Output_Data, 0. WRBC, CN5, WORD, 0, 10, 1s

FS-8700-22_X30_DeviceNet_Slave Manual Page 10 of 12

Appendix A. Advanced Topics

Appendix A.1. DeviceNet X30 LED indicators

LED 1 – Reserved

LED 2 – Network Status

Color Frequency Description

- Off Not powered / Not online
Green On Link OK, online, connected
Green Flashing Online, not connected
Red On Critical link failure
Red Flashing Connection timeout

LED 3 – Module Status

Color Frequency Description

- Off Not powered
Green On Device operational
Green Flashing Data size bigger than configured
Red On Unrecoverable fault
Red Flashing Minor fault

LED 4 – Reserved

Appendix A.2. Using RSNetWorx

Please refer to the following document on the HMS website, www.anybus.com
APPLICATION NOTE: Establishing I/O communication between AnyBus-S DeviceNet
using RsNetWorx for DeviceNet

Appendix A.3. Using RSLogix 5000

Please refer to the following document on the HMS website, www.anybus.com
APPLICATION NOTE: Reading/writing data from AnyBus-S DeviceNet using
ControlLogix5000 MSG instruction

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-8700-22_X30_DeviceNet_Slave Manual Page 11 of 12

Appendix B. Driver Notes

Appendix B.1. Setting the FieldServer’s DeviceNet MAC ID and Baudrate

The MAC ID and Baudrate can be set in the FieldServer’s CSV file using the
System_Station_Address and DNet_Slave_Baudrate parameters or it can be set with the
DIP switches. Note that the System_Station_Address parameter must be removed from the
config file if the DIP switch settings is to be used.

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-8700-22_X30_DeviceNet_Slave Manual Page 12 of 12

THIS PAGE INTENTIONALLY LEFT BLANK

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]