Table of Contents
Advertisement
1MRS755014
6.5.
6.5.1.
6.5.2.
Profibus-DPV1/SPA Gateway
Installation and Commissioning Manual
Table 6.4.-1
Indirect SPA messages error table (Continued)
SPA Slave-Unknown NACK
SPA GW-Checksum Error
SPA GW-Input Buffer Overflowed 0x8102
SPA GW-Msg too Complicated
SPA GW-Syntax Error
SPA GW-Missing data
SPA Network Timeout
SPA Network Response Pause
SPA Slave off-line
GSD file
For a Profibus device to be fully compliant with the Profibus specification, the
vendor must provide a GSD (Geräte Stamm Datei, Basic Profibus Device
Description) file for the Profibus slave device. A GSD file contains basic data about
the device, such as communication parameters, that make configuration and
commissioning of the device easier.
GSD file and standard configurations
The relation between the GSD file and the standard configuration templates is
logical. That is, there is no strict connection between the two entities. The main issue
is, however, that the size of the configuration of the gateway must match the size of
the module in use. This is because the module defines the size of the data block that
is copied from the Profibus slave to the master in each poll cycle, and if this size does
not match, the communication will not work properly.
Using GSD file
When you have selected, completed and downloaded the configuration of the
gateway, the Profibus master should be configured to accept the gateway device as
a part of the Profibus network.
Because different Profibus masters are configured by using different procedures, it
is strongly advised to consult the user documentation for the master in use. However,
all the masters are equipped with a mechanism for use with the GSD file, which is
provided by the vendor of the slave device.There are also masters using offset
calculations.
When the GSD file has been inserted into the system configuration, you can select
a number of modules for use. Which module should be used for which standard
configuration is documented in the GSD module section in each of the standard
configuration template descriptions.
0x8009
Undefined negative acknowledgement
0x8100
SPA slave response contained a checksum
error
SPA slave response too big for GW input
buffer
0x8103
SPA slave response too complicated for
the gateway
0x8105
SPA slave response can not be interpreted
by gateway
0x8106
SPA slave response is incomplete
0x8200
SPA message has timed out
0x8201
SPA Response Pause time is violated
0x8202
SPA Slave is off-line why the message is
ignored
SPA-ZC 302
55
Advertisement
Table of Contents
