The FieldServer Profibus DP Slave driver can be used to emulate a single Slave station on a
Profibus network. DP Masters can open a connection of up to 244 Bytes of Input and 244 Bytes
of Output data, but not exceeding a combined total of 416 Bytes to the FieldServer. The
FieldServer can be added to the Profibus network with the use of the supplied GSD file for the
ANYBUS card. Connection to the Profibus network is via a DB9 port on the ANYBUS card.
Max Nodes Supported
FieldServer Mode Nodes Comments
Server 1
The FieldServer can only emulate one Profibus DP Slave
station
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
2.2. Provided by the Supplier of 3rd Party Equipment
rd
2.2.1. Required 3
Profibus Network Configuration Tool
Party Software
2.2.2. Required 3rd Party Configuration
Connection to a properly terminated Profibus network.
2.3. Additional files Required for the Driver
Filename
Config.csv
"Anybus
gsd file"
"Always Loaded By
FieldServer
Technologies"
X
External
Application
X
Comments
Template loaded if no custom
configuration ordered, otherwise
Custom configuration loaded.
The Anybus template gsd file is
supplied with the FieldServer and
needs to be built up for the particular
application by the Master
configuration software
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
4. Configuring the FieldServer as a Profibus DP Server
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” filesprovided
with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a Profibus DP Master.
The configuration file tells the FieldServer about its interfaces, and the routing of data required.
In order to enable the FieldServer for Profibus 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. Profibus Settings
Section Title
Bridge
Column Title Function Legal Values
System_Station_Address* Profibus Station Address of the FieldServer 1-125
:
Note
The Profibus Station Address can also be set via the two rotary switches on the side of the
FieldServer in which case the System_Station_Address setting must be omitted from the
configuration file. The settings specified in the configuration file will override the settings on
these switches.
Only one Server Node may be defined for each connection.
If you are interested to know when support for multiple virtual Server Nodes on a single
connection will be provided please contact the Sales Department."
1
The X30 Profibus card auto-senses the Baud rate
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
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
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
Profibus_Data_Type Data Type of local buffer BYTE, WORD, FLOAT, BOOL
Green - Slave is online on the Profibus network
Off - Slave is not online on the Profibus network
LED 3 – Slave Offline Status
Color Frequency Description
Red - Slave is offline on the Profibus network
Off - Slave is not offline on the Profibus network
LED 4 – Fieldbus Diagnostics
Color Frequency Description
Error in configuration: IN and/or OUT length set during
Red 1 Hz
initialization of the Slave is not equal to the length set during
configuration of the network.
Error in User Parameter data: The length/contents of the
Red 2 Hz
User Parameter data set during initialization of the Slave is
not equal to the length/contents set during configuration of
the network.
Red 4 Hz Error in initialization of the Profibus communication ASIC.
Off - No diagnostics present.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
Appendix A.2. Setting the FieldServer’s Profibus Station Address
The Station Address can be set in the FieldServer’s CSV file using the
System_Station_Address, (refer to Section 4.1), or it can be set with the two rotary switches
as indicated on the connection diagram. The left switch selects the left decimal digit and the
right switch the right decimal digit of the Station Address.
Note that the software setting with the System_Station_Address overrides the hardware
setting with the rotary switches.
Appendix A.3. Understanding Driver Communication Statistics
When connecting with Ruinet to the FieldServer, there are communication statistics
displayed on the Connection, Node and Map descriptor screens for the Profibus DP driver.
The Transmit (Tx) message count indicates the number of times the driver wrote output
data into the Profibus hardware card’s output buffers for transmission on the Profibus
network. It does not indicate the actual number of transmissions on the Profibus network.
The Receive (Rx) message count indicates the number of times the driver read input data
from the Profibus hardware card’s input buffers. It does not indicate the number of actual
messages received on the Profibus network.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com
If no communication is being experienced between a Profibus Master and a FieldServer
Profibus Slave, check for the following most common issues:
• The Node_ID must match the System_Station_Address in the configuration
o Having these two parameters match in the configuration tells the FieldServer that
the buffer referenced in the Node_ID refers to the buffers in the Profibus card
attached to the FieldServer.
• The gsd file must match the FieldServer hardware being used
o FieldServer offers several hardware platforms that support Profibus. Each
hardware platform requires its own gsd file. Ensure that the gsd file being used
is the correct file for the hardware platform in use.
o The gsd file can be opened with a text editor. The Vendor and model name can
be checked in this file. For the FieldServer X30 Profibus Slave, the Vendor is
“HMS Industrial Networks AB”, and the Model Name is “ANYBUS-S PDP”. The
current revision is 1.5, which uses Hardware revision 1.6 and software release
1.2.
• The byte count for the gsd profile must match the byte count configured in the
FieldServer
o The gse being used is either going to allow the Client (via the network
configuration tool) to select the bytes to be used, or the byte make-up will be
fixed and specified in the gse. Either way, the largest byte offset used by the
Client must match the largest byte offset configured in the FieldServer.
o When selecting byte count with a network configuration tool, the total amount of
bytes/words/bits setup per Input/Output buffer in the FieldServer configuration
Map Descriptors must match those selected in the network configuration tool
otherwise a connection length mismatch will occur and the connection will not be
established. The FieldServer shows the connection size it expects on the F
(driver message) screen in the RUI utility in order that this value may be checked
against the network configuration tool.
• The direction of the communications (Input/Output Buffer) may be incorrectly configured.
o Buffer names can be confusing, especially when looking at the Slave. The
buffers are named according to their direction of communication in the Master.
Hence, an Input buffer in the Slave will write data to the Master, and data will be
received from the Master in the output buffer.
o Remember that as a Slave, the FieldServer will have to write data into the input
buffer (function=wrbc), and read data from the output buffer (function=rdbc).
• The Profibus card may be faulty.
o If this is the case, then there will be an error message in the FieldServer RUI
error screen indicating that the card could not be reached. Check for this
message. If it is there, try opening up the FieldServer and re-seating the card. If
this does not help, contact FieldServer Technical support for jumper settings on
the card, and further possible troubleshooting or return authorization.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com