FS-8700-20 Profibus DP Driver Manual
Page 19 of 22
FieldServer Technologies
1991 Tarob Court Milpitas, California 95035 USA
Web
:www.fieldServer.com
Tel
: (408) 262-2299
Fax
: (408) 262-9042
Toll_Free
: 888-509-1970
Appendix C. Troubleshooting
Appendix C.1. FieldServer as a Profibus slave
If no communications is being experienced between a Profibus Master and a FieldServer
Profibus Slave, check for the following most common issues:
•
The baud rate for this driver must be specified in the Connections section of the
configuration.
•
Baud rate must match the baud rate being used on the network.
•
The Node_ID must match the System_Station_Address in the configuration - 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 gse file must match the FieldServer hardware being used
o
FieldServer offers several hardware platforms that support Profibus. Each
hardware platform requires it’s own gse file. Make sure that the gse file being
used is the correct file for the hardware platform in use.
o
The gse file can be opened with a text editor. The Vendor and model name can
be checked in this file. For the FieldServer X40 Profibus Master/Slave, the
Vendor is “SST”, and the Model Name is “5136-PFB-ISA”. The current revision is
1.9, which uses Hardware revision 1.0 and software release 1.8.
•
The byte count for the gse 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 config 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 FieldServer may have bridge.bss loaded, which will configure it as a master
o
The bridge.bss file is loaded by default when FieldServers ship with the default
Profibus Master configuration. This file must not exist in applications where
FieldServer is being used as a slave.
o
To check for the file, try uploading the file from the FieldServer using the RUI
Utility. If it uploads successfully, then it will need to be deleted. See the
FieldServer Utilities manual for instructions on how to do this.
•
The FieldServer may be missing the pfbdp.ss1 file
o
This file is compulsory for all SST Profibus applications, and may be missing for
some reason.
o
To check for the file, try uploading the file from the FieldServer using the RUI
Utility. If it uploads successfully, then this is not the problem.
•
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.
