This documentation has been drawn up carefully, but, in spite of all efforts, errors may occur. Information from the part of our customers tha
will help to improve comprehensibility of the document and remove errors will be appreciated.
The information contained therein can be amended without prior notice and does not represent any obligation on the part of COMSOFT. We do
not assume any kind of responsibility for possible inconsistencies and their consequences. This work including all its parts is copyrighted.
Every usage of it which lies beyond the tight limits of the copyright are prohibited and punishable. This applies especially to copies,
translations, microfilms as well as to feeding into and processing in electronic systems.
All other product or company names mentioned in this document may present trademarks of the respective owners.
The intelligent PROFIBUS-DP gateways of COMSOFT's XPS series allow the
coupling of any serial devices with RS232 or RS422/485 interface to
PROFIBUS-DP according to the European Standard EN50170. The protocol
conversions required for the coupling are executed either by means of a
transparent universal driver or by loadable device-specific converters. The
following figure shows a typical connection:
Serial End Device
RS232/RS422 – XPS-E
Figure 1: Typical Connection of an XPS/XPS-E Gateway
XPS-E
XPS
DP-MASTER
PROFIBUS-DPRS232 – XPS
COMSOFT 1
Page 8
Contents XPS/XPS-EUser's Manual
2 Setting into Operation
When developing the XPS products, COMSOFT put great stress on an easy
installation. Following this aim, no external devices, e.g. configuration tools on
a PC are required to execute the configuration. All connections are realised by
D-SUB connectors, power plug (EN 60320) or spring clip terminals which can
all be accessed and loosened easily. The PROFIBUS station address is set via
coding switches. All further settings are done via UserParameter of the
SetParam telegram of PROFIBUS-DP. This parameterisation is executed,
simplified by the deliverable GSD file either via the configuration tool of the
connected PROFIBUS-DP Master or by the user program.
2 COMSOFT
Page 9
XPS/XPS-E User's Manual Contents
2.1 Connection of the Gateway
2.1.1 XPS Desk Model
Front Side
Status LED
Address
Switch
Rear Side
Figure 2: Connectors and Interfaces of XPS
RS232Interface
Terminator ON/OFF
Power Supply
PROFIBUS-DP
Interface
COMSOFT 3
Page 10
Contents XPS/XPS-EUser's Manual
2.1.2 XPS-E Top Hat Rail Model
PROFIBUS
Interface
Serial
Interface
Figure 3: Connectors and Interfaces of XPS-E
Address Switch
RUN-LED
BUS-FAIL-LED
MODE-LED
TX-LED
RX-LED
Power Supply
Connector
4 COMSOFT
Page 11
XPS/XPS-E User's Manual Contents
2.1.3 Proceeding
By executing the following steps, the XPS/XPS-E Gateway can be set into
operation:
1. Connect XPS/XPS-E to PROFIBUS by using a standard PROFIBUS cable
with corresponding D-SUB PROFIBUS connector. For the connector
assignment please refer to chapter Connector Assignment and follow the
Installation Guidelines for PROFIBUS (No. 2.112, PNO).
2. Connect the serial end device with XPS/XPS-E (Connector Assignment
refer to 5.2).
3. Check your PROFIBUS network with regard to an unused Slave address
and adjust this free address at the coding switch of XPS/XPS-E.
4. Plug in the power supply. In case of XPS this is done by means of a power
plug (EN 60320) at the rear side of the device. The power supply of the
XPS-E is connected by spring clips at the front side.
As soon as the device is powered, the Status/Busfail LED is flashing red.
Note
The Status/Busfail LED is flashing red until the device is parameterised and
configured. In this status, no data exchange can take place (neither send nor
receive). Only after successful parameterisation and configuration the
Status/Run LED is flashing green. Now, the device is ready for data exchange.
2.2 Test of PROFIBUS Connection
If you have a PROFIBUS-DP configuration tool, you can test the PROFIBUS
connection to the XPS/XPS-E Gateway. For this purpose, load the deliverable
GSD file into your configuration tool.
The DP Master shall now configure XPS/XPS-E. If this configuration is
successful, the Status/Run LED is flashing green.
If you do not have a PROFIBUS-DP configuration tool or if you wish to
change the pre-defined parameters (
refer to the following chapters for the parameterisation.
COMSOFT 5
User_Prm_Data) in the GSD file, please
Page 12
Contents XPS/XPS-EUser's Manual
2.3 Parameterisation
The parameterisation data of XPS/XPS-E consists of 7 DP-Slave standard
bytes and 16 device-specific parameters bytes (
user_prm_len = 16). As user diagnostic data, 8 additional diagnostics bytes
are available. (
diag_len = 8).
User_Prm_data, ->
Note
1. For initialisation of XPS/XPS-E send a
purpose, use the parameters for PROFIBUS-DP and the serial interface
described in chapter 2.4.
2. Check the parameterisation with
3. Then use the command
that, the configuration can be read with the command
XPS/XPS-E. If
maximum
For shorter
configurations which are defined in the GSD file or select those arbitrarily
according to the PROFIBUS-DP standard.
After successful parameterisation XPS/XPS-E is prepared for data exchange.
The Status/Run LED is now flashing green.
You can verify the parameterisation and configuration telegram by means of
slave_diag.
chk_cfg is executed directly after the initialisation, the
data_exchange telegram length is loaded from XPS/XPE-E.
data_exchange telegram length select one of the possible
chk_cfg to configure the XPS/XPS-E. Prior to
slave_diag.
set_prm telegram. For this
get_cfg from
In the following, only those parameters are described that are required for
operating the XPS/XPS-E. For the significance of the remaining PROFIBUSDP standard parameters please refer to the standard EN50170 and the GSD
file.
6 COMSOFT
Page 13
XPS/XPS-E User's Manual Contents
2.4 set_prm Parameterisation
The Bytes 1-7 are PROFIBUS-DP standard parameters, Byte 8-23 are devicespecific parameters (
Octet Parameter Name Value
usr_prm).
1
2
3
4
5
6
7
8..11 Reserved ---
12 Baud Rate setting of serial interface See Table 3
13 Character Transmission Mode of serial interface See Table 4
14 Handshake setting of serial interface See Table 5
15 XOFF-Timeout of serial interface See 2.4.3.4
16 Receive Mode of PROFIBUS interface See Table 6
18 Trigger character for serial triggered mode
Station_status
WD_fact_1
WD_fact_2
Min T
Ident_Number [0]
Ident_Number [1]
Group_Ident
(usually LF (0x0A))
SDR
0x80*
0x00
0x00
55
0x95
0x10
0x00
See Table 8
19..23 Reserved ---
Table 1: set_prm
(*)
Freeze_Req and Sync-Req are not supported.
COMSOFT 7
Page 14
Contents XPS/XPS-EUser's Manual
2.4.1 GSD File
Next to standard parameters the parameters for the serial interface are included
in the GSD file. They are listed under the
correspond to those described under chapter 2.3. A modification of these
parameters can be made by any kind of ASCII editor. Please note that the
number of parameters must not be changed and that the first four and last six
parameter bytes are to be set to 0.
In the following, the default settings of the GSD for serial interfaces of
XPS/XPS-E are listed.
9600 Baud / 8Bit / No Parity / 1 Stopbit / no Handshake / no Timeout / PollMode / RS232-Mode
This corresponds to the following entry in the GSD file:
Bit7 Diag.Deactivated
Bit6 reserved
Bit5 Diag.Sync_Mode
Bit4 Diag.Freeze_Mode
Bit3 Diag.WD_On
Bit2 must be set to 1
Bit1 Diag.Stat_Diag
Bit0 Diag.Prm_Req
Bit7 Diag.Ext_Diag_Overflow
Bit6..0 reserved
Master address or 0xFF, if Slave is not yet
parameterised.
0x95
6
7 Number of ext. diagnostic bytes 8
8 XPS/XPS-E state See 4.1
9 Baud Rate of the serial interface See 2.4.3.1
10 Character Transmission Mode of
11 Handshake setting serial interface See 2.4.3.3
12 XOFF-Timeout of serial interface See 2.4.3.4
13 Receive Mode of DP- interface See 2.4.3.5
14 Setting of driver physics of serial
15 Trigger character for Serial
Table 2: slave_diag
Ident_Number[1]
serial interface
interface (RS232/485)
triggerd Mode
0x10
See 2.4.3.2
See 2.4.3.6
0x0A
COMSOFT 9
Page 16
Contents XPS/XPS-EUser's Manual
2.4.3 Parameter Description
The parameters marked with (*) are the default values. These are used if
inadmissible parameters are entered during parameterisation.
2.4.3.1 Baud Rate
Baud Rate (bit/s) Value (dec) Value (hex)
150 1 0x01
300 3 0x03
600 6 0x06
1.200 12 0x0C
2.400 24 0x18
4.800 48 0x30
9.600 * 96 0x60
19.200 192 0xC0
Table 3: Baud Rate of Serial Interface Octet 12
2.4.3.2 Character Transmission Mode
Transmission Mode Value (dec) Value (hex)
8 Data bits, No Parity, 1 Stopbit (8N1) * 56 0x38
7 Data bits, No Parity, 2 Stopbits (7N2) 78 0x4E
7 Data bits, Even Parity, 1 Stopbit (7E1) 69 0x45
7 Data bits, Odd Parity, 1 Stopbit (7O1) 79 0x4F
Table 4: Character Transmission Modes Octet 13
Note
10 COMSOFT
The operating mode: 7 data bits, No Parity, 1 StopBit is not supported.
Page 17
XPS/XPS-E User's Manual Contents
2.4.3.3 Handshake Flow Control
If data is exchanged via the serial interface, XPS/XPS-E supports the following
modes for the handshake:
• No Handshake
• Hardware Handshake. The receive data flow can be controlled at the
respective device by setting or re-setting the RTS-/CONTROL signal
(CTS/INDICATION=0 -> no sending). A corresponding example for
cabling can be found under chapter 5.2.2 and 5.2.3.
• Software Handshake. The receive data flow can be stopped by the
respective device by sending the control character XOFF (0x13). The
sending procedure will only be re-started if a XON character (0x11) is
received or a Timeout (XOFF-Timeout) for the receipt of the XON
character.
The interruption of the sending procedure or the XOFF timeout is shown in the
status byte of XPS/XPS-E (see chapter 4.2) by means of the bit
XOFF_CTS_FLAG.
Handshake Mode Value (dec) Value (hex)
Hardware Handshake (CTS, RTS for RS232
72 0x48
and CONTROL/INDICATION for RS422)
Software Handshake 83 0x53
No Handshake * 78 0x4E
Table 5: Handshake Modes Octet 14
2.4.3.4 XOFF_timeout – Timeout of Software Handshake
The XOFF timeout is calculated by means of VALUE * 100ms. This value is
entered into Octet15 of the parameterisation data. If no software handshake is
entered, this value is insignificant.
Note
If the value 0 is given, the timeout is set to 10 seconds.
COMSOFT 11
Page 18
Contents XPS/XPS-EUser's Manual
2.4.3.5 DP-Data Transmission Mode
To offer the user several possibilities to adapt his application optimally to the
gateway functionality of XPS/XPS-E, 3 data transmission modes can be used.
The corresponding description is found under chapter 3.
Data Transmission Modes Value (dec) Value (hex)
Poll Mode * 80 0x50
Request Mode 82 0x52
Serial triggered Mode 83 0x53
Table 6: Data Transmission Modes Octet 16
2.4.3.6 Extended Gateway configuration data
ext. Configuration byte Bit Function
Bit7 ..Bit2 Reserved
Bit1 Double baud rate
Bit0 RS232(0)<->RS422(1)
Table 7: ext. configuration byte Octet 17
BIT0: RS232<->RS422 – Serial interface physics
With this parameter the interface physics can be set to RS232(0) or RS485(1).
This parameter is only applicable for XPS-E. The desktop model (XPS) does
only have an RS232 physics.
BIT1: double Baudrate
Setting this bit doubles the baudrate for the serial interface
Exp: A selected baudrate of 19200 Baud can be increased to 38400 Baud by
setting this bit.
BIT7 – Bit2: reserved
12 COMSOFT
Page 19
XPS/XPS-E User's Manual Contents
2.4.3.7 Trigger character for Serial triggert mode
Here the trigger character for the serial triggerd mode is set. If the seriell
receive data stream contains the same sign, all received data up to this
character are sent to the DP-Master inclusive the trigger character.
Triggerzeichen Wert (dez) Wert
(hex)
Wert
(ASCII)
LF * 10 0x0A LF
Table 8: Triggerzeichen Octett 18
COMSOFT 13
Page 20
Contents XPS/XPS-EUser's Manual
3 Data Exchange
Data exchange of XPS/XPS-E is exclusively realised by means of the
PROFIBUS-DP service
correspond to the output data of
correspond to the input data of
For each send or receive job, at max. 240 Bytes are available while 3 Bytes are
headers and the remaining 237 Bytes are user data. If more than 237 Bytes user
data shall be sent or received, the application on part of the PROFIBUS-DP
Master must split this job into several telegrams.
The data transmission format used from/to XPS/XPS-E has the following
structure:
Byte Telegram Element Value Range (dec)
data_exchange. The data to be sent by the master
data_exchange.req, the data received
data_exchange.res.
1 Receive request number (only request
mode)
2 Send request number 0 – 255 (see 3.1)
3 Data length N of the following user data 0 – 237*
4..4+N Telegram data (user data) 0 – 255
Table 9: Data Transmission Format at data_exchange_req
Byte Telegram Element Value Range (dec)
1 Status of XPS/XPS-E 0 – 255 (see 4.2)
2 Receive Confirmation number of
XPS/XPS-E
3 Data length N of the following user data 0 – 237*
4..4+N Telegram data (user data) 0 – 255
Table 10: Data Transmission Format at data_exchange_res
0 – 255 (see 3.2)
0 – 255 (see 3.2)
(*) maximum number of user data depends on how the DP-Master has
configured XPS/XPS-E via the
Data can be arbitrary characters in the value range 0..255. This however is
only valid if XON/XOFF is not used as handshake.
14 COMSOFT
chk_cfg service.
Page 21
XPS/XPS-E User's Manual Contents
3.1 Send Data
To send data via XPS/XPS-E onto a serial end device, the send flag of
XPS/XPS-E must be reset (ref. 4.2 Communication Status, Bit 0 = 0), as
otherwise the send data to XPS/XPS-E will be discarded. For a send job, the
following data must be included into the telegram.
• Send job number. This job number must be different for each send
procedure. Reasonably, the value should be incremented by 1 at every send
procedure.
• Send data length. If the data length is set to 0, no data is sent via the serial
interface. Otherwise this byte includes the number of the following user
data.
• Send data (user data)
3.2 Receive Data
XPE/XPS-E has a 2Kbyte receive data buffer to temporarily store data received
from the connected serial end device. For data transfer to the PROFIBUS-DP
Master the operating modes Poll mode and Request-Mode are available. The
mode will be selected during parameterisation of XPS/XPS-E by the Master
(ref. 2.4.3.5). In the Poll mode available receive data will be sent at every
data_exchange.req with the corresponding data_exchange.res
from XPS/XPS-E to the PROFIBUS-DP Master. In the Request mode the
XPS/XPS-E sends this data only if in
has been changed (the receive request number). Thus, the polling of existing
receive data can be controlled by the Master.
The request mode is recommended for Masters that are polling the slaves
cyclically to generate a process image. (application may be too slow to process
the current data of the process image).
data_exchange.req a defined byte
COMSOFT 15
Page 22
Contents XPS/XPS-EUser's Manual
3.2.1 Poll Mode
In this mode XPS/XPS-E returns with every data_exchange the data
received up to the present time. Apart from the receive data and their lengths a
receive data number is entered into the telegram. This confirmation number is
automatically incremented if new receive data is available in the telegram. If
the receive telegram does not contain new data (data length = 0), the
confirmation number remains unchanged.
Note:
If this mode is used when the Master is generating a Process Image according
to a Poll List it must be paid attention that this Poll List can be read quickly
enough as with every data_exchange the process image will be
overwritten. This may cause loss of data on part of the application. Loss of
data can be noticed when the confirmation number is not subsequent.
PROFIBUS Data Traffic
DP-MasterReceive Buffer
X
X
DATA_EXCHANGE.REQ
DATA_EXCHANGE.RES
XPS/XPS-E
S 1 2
S 2 5
XPS/XPS-E
TE
TE
STDAT
STDAT
X
X
X = Receive Request Number
S = Status
S 2 0
S 3 2
EN
EN
EN
Figure 4: Data Reception in Poll Mode
16 COMSOFT
Page 23
XPS/XPS-E User's Manual Contents
The telegrams mentioned above can either be started automatically by the
Master (cyclically during automatic polling) or by the application.
Note:
The receive request number (X) in Poll Mode may not be set.
❶ The data_exchange.req telegram is sent to XPS/XPS-E. XPS/XPS-E
has already received the first characters at the interface. It returns them in
the response telegram
data_exchange.res to the Master. The
confirmation is incremented by 1 and the length of the reception data is
entered. Moreover, the status (S) of XPS/XPS-E is returned.
❷ New data_exchange.req telegram. XPS/XPS-E returns the new data
by incrementing the confirmation number by 1.
❸ As response telegram to the data_exchange.req telegram,
XPS/XPS-E enters the old confirmation number as no new data has been
received at the serial interface. The receive data length is set to 0.
❹ XPS/XPS-E has again received new data. The confirmation number is
incremented by one and the data returned correspondingly by the
data_exchange.res telegram to the Master.
If no time guarantee can be given and if data loss has to be excluded under all
circumstances, XPS/XPS-E must be run in the request mode.
COMSOFT 17
Page 24
Contents XPS/XPS-EUser's Manual
3.2.2 Serial triggered Mode
In serial triggered mode XPS/XPS-E waits for the termination of the receive
data by the trigger character defined within the external user parameters of
XPS/XPS-E (usually LF in ASCII-strings). The receive confirmation number is
not increased as long as no trigger character is received. After the trigger
character is received the Data Exchange Resp.-buffer is updated with the
received data inclusive the trigger character. The data Exchange Resp.-buffer
does not change as long as the next trigger character is received.
PROFIBUS Data traffic
DP-Master Receive buffer
X
X
1.:
DATA_EXCHANGE.REQ
DATA_EXCHANGE.RES
2.:
XPS/XPS-E
S 1 4
S 1 4
XPS/XPS-E
"T01",0x0A
"T01",0x0A
"T2"
"T01",0x0A
3.:
X
S 1 4
"T01",0x0A
4.:
X
S 2 3 "T2",0x0A
0x0A
X = Receive request number
S = Status
Figure 5: Receive data in serial triggered mode (trigger character : 0x0A)
Hinweis:
Please note, that it is not necessary to set the receive request number (X) in
polling/serial Mode
18 COMSOFT
Page 25
XPS/XPS-E User's Manual Contents
1. The data_exchange.req is transmitted to the XPS/XPS-E.
XPS/XPS-E has already received data via the serial interface. This data
are transmitted with
data_exchange.res back to the DP-Master.
The receive confirmation number is incremented and data length and
status are updated.
2. Next
3. Next
4. Next
3.2.3 Request Mode
In the request mode the XPS/XPS-E only sends receive data if a modified
receive-request number is contained in the request telegram. The data are not
returned in the first response telegram but in the response telegram of the
subsequent
always only in the subsequent cycle of the request. If the response telegram
contains received data, the XPS/XPS-E confirmation number is incremented by
one and returned in the response telegram (as in the poll mode).
data_exchange.req service. XPS/PS-E responds with the
old data. New data are in fact received, but they do not contain the
trigger character.
data_exchange.req service. XPS/PS-E responds with the
old data, because no further serial data were received.
data_exchange.req service. XPS/PS-E has received in the
meantime the serial trigger character. The receive confirmation number
is incremented, data length, status and
data_exchange.res buffer
are updated with the actual data.
data_exchange service. This means that the data are returned
Note:
If this mode is used while the master is automatically polling the slaves
according to the poll list, the data that have been received last remain in the
process image.
COMSOFT 19
Page 26
Contents XPS/XPS-EUser's Manual
PROFIBUS Data Traffic
DP-MasterReceive Buffer
1
2
3
3
3
DATA_EXCHANGE.REQ
DATA_EXCHANGE.RES
XPS/XPS-E
S 0 0
S 1 2
S 2 5
S 2 5
TE
STDAT
STDAT
XPS/XPS-E
TE
STDAT
EN
EN
EN
EN
4
4
S = Status
S 2 5
S 2 5
S 3 2
STDAT
STDAT
EN
EN
EN
Figure 6: Data Reception in Request Mode
The data_exchange.req telegram is sent to the XPS/XPS-E which
already has received the first characters. It returns them, however, only in
the subsequent response telegram
data_exchange.res.
20 COMSOFT
Page 27
XPS/XPS-E User's Manual Contents
New data_exchange.req telegram with increased receive-request
number (further reception command). XPS/XPS-E returns the data received
at point in time
Another reception command to XPS/XPS-E (receive-request number has
. The confirmation number is increased by one.
been increased). The data that are returned are the data received at point in
time
.
No further reception command to XPS/XPS-E. XPS/XPS-E returns again
the last sent data. XPS/XPS-E has already received new data.
No further reception command to XPS/XPS-E. XPS/XPS-E returns again
the last sent data.
This data_exchange.req contains another reception command. The
data are returned, however, only at the next cycle.
No further reception command because the request number has not been
increased. The data that are returned are the data received until the point in
time of the last read command (
).
COMSOFT 21
Page 28
Contents XPS/XPS-EUser's Manual
3.3 Send and Receive Data
It is generally possible in both modes to send and receive data simultaneously.
The request telegrams described in the previous chapters then have to be
completed only by the entries of the transmission command (transmission
command number, length of transmission data, data).
Please note that the data are only accepted and transmitted by the XPS/XPS-E
if the transmission command number in the
to the XPS has changed.
PROFIBUS Data Traffic
data_exchange.req telegram
DP-MasterReceive Buffer
X15
SEN
X = Receive Request Number
S = Status
Figure 7: Combined Send- and Receive Request
DATA_EXCHANGE.REQ
DATA_EXCHANGE.RES
S 1 2
XPS/XPS-E
XPS/XPS-E
TE
TE
22 COMSOFT
Page 29
XPS/XPS-E User's Manual Contents
p
4 Status and Error Messages
4.1 External Device Diagnostics
External device diagnostics can be realised by means of the service
slave_diag Octet 8 of the response telegram contains the device status and
is encoded as follows:
70
Octet 8
xxxxx
Figure 8: Byte Definition of external Device Diagnostics
xx
RS_PORT_CFG_ERROR
Invalid parameter at
arameterisation of serial interface.
not significant
COMSOFT 23
Page 30
Contents XPS/XPS-EUser's Manual
f
N
4.2 Communication Status
In the status of the confirmation telegram of the service data_exchange the
status of the serial interface is encoded as follows:
70
RS_PORT_TX_DATA
Data are being transmitted.
not significant
RS_PORT_PARITY_ERROR
Parity error of receive data o
serial interface.
RS_PORT_RX_DATA_AVAIL
XPS/XPS-E has data in receive
buffer.
XOFF_CTS_FLAG
XOFF was received or CTS is
inactive.
OUTPUT_DATA_LEN_FAILURE
user data length exceeds maximal
data_exchange
(on part of PROFIBUS)
RS_PORT_RX_OVERFLOW
Receive buffer overflow
length minus 3
XOFF_TIMEOUT
o XON received after XOFFTimeout. Sending process was restarted.
Figure 9: Byte Definition of Communication Status
24 COMSOFT
Page 31
XPS/XPS-E User's Manual Contents
5 Connector Assignment and Cabling
5.1 PROFIBUS
5.1.1 Connector Assignment
The PROFIBUS connection is executed according to EN50170 as 9-pin female
D-SUB with the following assignment:
Pin RS485
Ref.
1 - - Shielding -
2 - - NC -
3 B/B´ RxD/TxD-P Data (+) I/O
4 - CNTR-P Control character (+) O
5 C/C´ DGND Data Ground -
6 - VP Supply for Terminator (+5V) -
7 - - NC -
8 A/A´ RxD/TxD-N Data (-) I/O
9 - CNTR-N Control character (-) O
Table 11: Pin Assignment PROFIBUS
O = Output
I = Input
Signal Function Direction
COMSOFT 25
Page 32
Contents XPS/XPS-EUser's Manual
5.1.2 PROFIBUS Terminating Resistor
For correct operation of XPS/XPS-E both bus terminations of the line segment
must be provided with a terminator. This terminator must match with the
impedance level of the line. Typically, in case of new PROFIBUS installations,
Type A will be used. The assignment of the individual terminating resistors of
the terminator is depicted in the following figure.
Note
6385
390R220R390R
+5VData+Data-0V
Figure 10: Assignment of PROFIBUS Terminator Type A
You can also order the PROFIBUS Terminator in pre-configured condition
(Order No.: 4000-7-002-H, Type A).
26 COMSOFT
Page 33
XPS/XPS-E User's Manual Contents
5.1.3 Cabling
M
TT
S1S2
....
Sn
T= Terminator
M=Master
S=Slave, n
≤
31
Figure 11: Connection of a PROFIBUS-DP Slave within a Segment
If no terminator with independent power supply shall be used (active
terminator), the termination must be realised directly at the last stations of the
bus. This station must then supply the terminator with power. For details
regarding the PROFIBUS installation please refer to the PROFIBUS
Installation Guidelines of the PROFIBUS User Organisation (PNO, Order No.:
2.112).
NOTE
In case of XPS a bus termination is integrated and can be activated via the
switch at the front side of the device.
COMSOFT 27
Page 34
Contents XPS/XPS-EUser's Manual
5.2 Serial Interface
5.2.1 Connector Assignment RS232 (XPS and XPS-E)
The connection is realised via a 9-pin D-SUB plug.
Pin Signal FNI CCITTFunction Direction
1 DCD M5 109 Data Carrier Detect I
2 RxD D2 104 Receive Data I
3 TxD D1 103 Transmit Data O
4 DTR S1 108.2 Data Terminal Ready O
5 GND E2 102 Ground ---
6 DSR M1 107 Data Set Ready I
7 RTS S2 105 Request to Send O
8 CTS M2 106 Clear To Send I
9 --- --- --- Not connected ---
Table 12: Connector Assignment RS232 Interface
O = Output
I = Input
28 COMSOFT
Page 35
XPS/XPS-E User's Manual Contents
5.2.2 Cabling RS232
5.2.2.1 Cabling without Hardware Handshake
XPS/XPS-EEnd Device
AssignmentAssignment
9pol9pol25pol
PinSignalSignalPinPin
2RxDTxD2 3
3TxDRxD3 2
5GNDGND57
Figure 12: RS232 Cabling without Hardware Handshake
5.2.2.2 Cabling with Hardware Handshake
XPS/XPS-EEnd Device
AssignmentAssignment
9pol9pol25pol
PinSignalSignalPinPin
2RxDTxD2 3
3TxDRxD3 2
7RTSRTS 7 4
8CTSCTS 8 5
5GNDGND57
Figure 13: RS232 Cabling with Hardware Handshake
COMSOFT 29
Page 36
Contents XPS/XPS-EUser's Manual
5.2.3 Connector Assignment RS422/485 (XPS-E only)
The connection is realised via a 9-pin D-SUB plug.
This section is treating the most frequent application problems and their
solutions.
The most current questions and answers can be found under
http://www.comsoft.de
DP-Master Status Message: Status 0xC2 (SAP/Service not activated)
Make sure that the parameterisation sequence of the parameterisation described
in section 2.3 has correctly been executed. If necessary, repeat
parameterisation.
DP-Master Status message: Status 0xC3 (no acknowledge)
Check the following points:
• Does the station address of the XPS/XPS-E correspond to the setting of the
PROFIBUS Master device?
• Are the bus parameters set correctly?
• Is the bus terminated correctly (switch position of the terminator integrated
in XPS)?
• Has XPS/XPS-E been connected correctly?
DP-Master Status message: Status 0xC4 (bad telegram)
Check the terminating resistors at the bus. Pay attention to the switch position
of the terminating resistor at the XPS.
32 COMSOFT
Page 39
XPS/XPS-E User's Manual Contents
7 Technical Data
7.1 XPS
7.1.1 PROFIBUS-DP Interface
Transmission protocol: PROFIBUS-DP according to EN50170-3