A Sierra Monitor Company
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-114 X30 DeviceNet Master Adapter
Driver
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after September 2008
Driver Version:
Document Revision:
1.01
3
FS-8700-114 DeviceNet Master Manual
Page 3 of 15
1.
X30 DeviceNet Master Description
The X30 DeviceNet Master Adapter driver can be used to emulate a single Master Scanner station on a
DeviceNet network. The FieldServer DeviceNet adapter is implemented as an ODVA profile 12
communications adapter. Standard DeviceNet Baudrates of 125k, 250k and 500kbit/s are supported.
The DeviceNet Master Scanner can open IO connections of up to a total of 512 Bytes in each direction to
DeviceNet Slaves.
Max Nodes Supported
FieldServer
Nodes Comments
Mode
Client
1
The FieldServer can only emulate one DeviceNet Master station
The driver can communicate with up to 63 Slaves as long as the FieldServer
point count license is not exceeded
Server
63
FS-8700-114 DeviceNet Master Manual
Page 4 of 15
2.
Driver Scope of Supply
2.1. Supplied by FieldServer Technologies for this driver
FieldServer Technologies PART # Description
FS-8700-114
Driver Manual.
X30-DeviceNet-Master
Anybus-M DeviceNet Card
2.2.
2.2.1.
Provided by the Supplier of 3rd Party Equipment
Required 3rd Party Software
RSNetWorx, RSLogix or another Network Scheduling Tool.
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-M DeviceNet eds file
FS-8700-114 DeviceNet Master Manual
Page 5 of 15
3.
Hardware Connections
The FieldServer is connected to the DeviceNet network as shown in the connection drawing below.
Connector Pinouts
Pin Signal
Description
Wire color
1
2
3
4
5
V-
Negative supply voltage black
CAN_L CAN_L Bus line
SHIELD Cable Shield
CAN_H CAN_H Bus line
blue
(bare)
white
V+
Positive Supply Voltage red
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.
Terminate each end of the DeviceNet network with a 121 Ω resistor
The bus interface shall be supplied with 24DC ± 10% on the Fieldbus connector
FS-8700-114 DeviceNet Master Manual
Page 6 of 15
4.
Configuring the FieldServer as a DeviceNet Master
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 Slave.
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
Bridge
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
Bridge
Title,
DeviceNet_Test,
System_Station_Address
5
FS-8700-114 DeviceNet Master Manual
Page 7 of 15
4.2.
Client Side Connection Descriptors
Section Title
Connections
Column Title
Adapter
Function
Adapter Name
Legal Values
DNet
Protocol
Protocol name
Baudrate
X30_DNet_Master
125K , 250K , 500K
DNet_Master_Baudrate1
Command_DA_Name
Status_DA_Name
Commanding Scanner
Provide Scanner status
Name of a data array declared
under Data Arrays section, length of
8 - Bit data array type recommended
Example
// Server Side Connections
Connections
Adapter, Protocol,
DNet_Master_Baudrate, Command_DA_Name, Status_DA_Name
DNet,
X30_DNet_Master, 500K, Command_Reg, Status_Reg
4.3.
Client Side Node Descriptors
Section Title
Nodes
Column Title
Node_Name
Node_ID
Function
Provide name for node
MAC ID of Slave to scan
Specify protocol used
Legal Values
Up to 32 alphanumeric characters
0 - 63
Protocol
X30_DNet_Master
Example
// Server Side Nodes
Nodes
Node_Name,
DN1,
Node_ID,
01,
Protocol
X30_DNet_Master
1
If System_Station_Address has not been defined in the CSV file, the DIP switch value for both MacID
and Baudrate will be used and the baud parameter in the CSV file will be ignored.
FS-8700-114 DeviceNet Master Manual
Page 8 of 15
4.4.
4.4.1.
Client Side Map Descriptors
FieldServer Specific Map Descriptor Parameters
Column Title
Function
Legal Values
Up
characters
Name of Data Array where data One of the Data Array names
to
32
alphanumeric
Map_Descriptor_Name Name of this Map Descriptor
Data_Array_Name
Data_Array_Offset
is to be stored in the FieldServer
from “Data Array” section above
0 to maximum specified in “Data
Array” section above
Starting location in Data Array
RDBC -Reads data from the
Function
Descriptor
of
Server
Map remote input buffer
Function
WRBC -Writes data to the remote
output buffer
Scan_Interval
Buffers Update Period
> 0.001s
4.4.2.
Driver Specific Map Descriptor Parameters
Function
Column Title
Node_Name
DeviceNet_Data_Type Data Type of remote buffer
Legal Values
One of the Node names
specified in “Server Node
Descriptor” above
Name of Node
Byte, Word, Dword, Float, Bool
RDBC: 0 – 511
WRBC: 0 – 511
Address
Byte offset into remote buffer
BYTE: 1 – 512
WORD: 1 – 256
DWORD: 1 – 128
FLOAT: 1 –128
Number of DeviceNet_Data_Type
items in remote buffer
Length
BOOL: 1 – 4096
FS-8700-114 DeviceNet Master Manual
Appendix A. Advanced Topics
Page 10 of 15
Appendix A.1.
DeviceNet X30 LED indicators
LED 1 – Reserved
LED 2 – Network Status
Color
Frequency
Description
-
Off
On
Flashing
On
No power, not initialized or no connections established
Online, one or more connections established
Online, no connections established
Green
Green
Red
Critical link failure
Red
Flashing
Minor fault, one or more connections have a minor fault
LED 3 – Module Status
Color
Frequency
Off
On
On
Description
No power or not initialized
Module status is OK
Major fault
-
Green
Red
Red
Flashing
Minor fault
LED 4 – Operation Mode
Color
Frequency
Off
Flashing
On
Description
No power or not initialized
Idle mode
-
Green
Green
Run mode
FS-8700-114 DeviceNet Master Manual
Page 11 of 15
Appendix A.2.
Using RSNetWorx
ANYBUS-M DEVICENET MASTER/SCANNER APPENDIX Revision 1.02
“Configuration with RSNetworx”.
-
Section 5.3
FS-8700-114 DeviceNet Master Manual
Appendix B. Driver Notes
Page 12 of 15
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_Master_Baudrate parameters or it can be set with DIP switches
as depicted below.
Note:
The System_Station_Address parameter must be removed from the configuration file if the DIP
switch setting is to be used.
If System_Station_Address has not been defined in the CSV file, the DIP switch value for both MacID
and Baudrate will be used and the baud parameter in the CSV file will be ignored.
Appendix B.2.
Using the Command and Status Data Arrays
The Command Data Array controls the Scanner’s mode which can be either Run or Idle. The Scanner
can only be configured when in Idle mode. A non-zero value at offset zero in the Command Data
Array will place the Scanner in Run mode; a value of zero will place it in Idle mode. The Scanner
FS-8700-114 DeviceNet Master Manual
Page 13 of 15
always powers up in Idle mode and can be set to Run mode automatically with a preload section or
from the Server side protocol of the FieldServer. The following preload section can be placed in the
configuration file to place the scanner in Run mode at power-up:
Preloads
Data_Array_Name,
Command_Reg,
Preload_Data_Format,
Bit,
Preload_Data_Value,
1,
Location
0
Offset zero of the Status Data Array indicates the Scanner’s actual mode achieved. A non-zero value
indicates the Scanner is in Run mode and a value of zero indicates the scanner is in Idle mode.
Appendix B.3.
Master Status Codes
The Master Status codes displayed on the F-screen are depicted below:
FS-8700-114 DeviceNet Master Manual
Page 14 of 15
Example:
If the Master reports a network failure the following screenshot will be displayed:
FS-8700-114 DeviceNet Master Manual
Page 15 of 15
Appendix B.4.
Understanding buffer types and Map Descriptor functions
The diagram below explains the data flows for both buffers when using the FieldServer as a DN
Master:
Note that for the Input buffer, the data is coming from the external DN Slave and is transferred into
the DN Master card’s internal input buffer. The Rdbc (Read Data Block Continuous) Map Descriptor
transfers the data from the card buffer into the FieldServer’s Data Array packing it correctly according
to the specified DeviceNet_Data_Type.
For the Output buffer, the data is written from the FieldServer’s Data Array by the WRBC function
Map Descriptor (Write Data Block Continuous) into the DN Master card’s internal output buffer from
where it is transferred across the DeviceNet network to the external DN Slave’s input buffer.
FieldServer
Data Array
Data Array
RDBC Map Descriptor
WRBC Map Descriptor
DeviceNet Card
Card input buffer
External DN Slave 01
Card output buffer
DeviceNet
Network
243
0
1
0
0
243
1
….
….
Card output buffer
Card input buffer
243
0
1
1
243
….
….
DN Master
External DN Slave 126
Card output buffer
Note: The Node_Name determines to
which external DN Slave date will be
sent to or fetched from.
0
243
1
….
Card input buffer
0
1
243
….
Appendix B.5.
Accessing Parameter Data in Remote Slaves
The DeviceNet driver only supports IO data. To access parameter data on Slaves it is necessary to
refer to the Slave device's user manuals for information on how to map their parameter data to IO
data locations.
|