Appendix A. Useful Features .................................................................................................................................. 9
Appendix A.1. DeviceNet X30 LED indicators ............................................................................................................ 9
Appendix A.2. Using RSNetWorx ............................................................................................................................... 9
Appendix B. Troubleshooting ............................................................................................................................... 10
Appendix C. Reference ......................................................................................................................................... 10
Appendix C.1. Setting the FieldServer’s DeviceNet MAC ID and Baudrate ............................................................. 10
Appendix C.2. Using the Command and Status Data Arrays ................................................................................... 11
Appendix C.3. Master Status Codes ......................................................................................................................... 11
Appendix C.4. Understanding buffer types and Map Descriptor functions............................................................. 13
Appendix C.5. Accessing Parameter Data in Remote Slaves ................................................................................... 13
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
The FieldServer can only emulate one DeviceNet Master station
Server
63
The driver can communicate with up to 63 Slaves as long as the FieldServer point
count license is not exceeded
FieldServer Technologies PART #
Description
X30-DeviceNet-Master
Anybus-M DeviceNet Card
PART #
Vendor/Manufacturer
Description
-
HMS-Networks
Anybus-M DeviceNet eds file
DEVICE N E T M A S T ER DESCRIPTION
1
The 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 1536 Bytes in each direction to DeviceNet Slaves.
Max Nodes Supported
DRIVER SC O P E O F SU P PLY 2
2.1 Sup plied by FieldServer T e c h n o l o g i e s for this driver
2.2 Provided by the Supplier o f 3
rd
Party Equipment
2.2.1 Required 3
RSNetWorx, RSLogix or another Network Scheduling Tool.
2.2.2 Required 3
Connection to a properly terminated DeviceNet network.
rd
Party Software
rd
Party Configuration
2.2.3 Optional Items
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Provide data format. Each Data Array can only take on one
format.
Float, Bit, Uint16, Sint16,
Uint32, Sint32, Byte.
Data_Array_Length
Number of Data Objects. Must be larger than the data
storage area required by the Map Descriptors for the data
being placed in this array.
1-10, 000
// Data Arrays
Data_Arrays
Data_Array_Name
, Data_Array_Format
, Data_Array_Length
DA_AI_01
, UInt16
, 200
DA_AO_01
, UInt16
, 200
DA_DI_01
, Bit
, 200
DA_DO_01
, Bit
, 200
DATA A R R A Y P A RAMETERS
4
Data Arrays are “protocol neutral” data buffers for storage of data to be passed between protocols. It is necessary
to declare the data format of each of the Data Arrays to facilitate correct storage of the relevant data.
Example
CONFI G U R I N G THE FIELDSERVER AS A DEVI C E NET MASTER 5
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.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Name of a data array declared under Section 4, length of 8 - Bit
data array type recommended
Status_DA_Name
Provide Scanner
status
// Server Side Connections
Connections
Adapter
,Protocol
, DNet_Master_Baudrate
, Command_DA_Name
, Status_DA_Name
DNet
, X30_DNet_Master
, 500K
, Command_Reg
, Status_Reg
1
5.1 DeviceNet Settings
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 C.1 for more information.
Example
5.2 Server Side Connection Parameters
Example
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.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
If there is no 24VDC supply on the DeviceNet Network or if the power supply current is not enough to support the
entire network, then the FieldServer will report that any device configured in the config file is not in the master
scan list, regardless if it is in the scan list or not.
Appendix C. REFERENCE
Appendix C.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.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Appendix C.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 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:
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 C.3. Master Status Codes
The Master Status codes displayed on the F-screen are depicted below:
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Note: The Node_Name determines to
which external DN Slave date will be
sent to or fetched from.
Appendix C.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.
Appendix C.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.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com