Kunbus XPS-E User manual

User Manual
XPS-E
100205 • 02/03/2017

KUNBUS GmbH
ii XPS-E
1 Working with XPS ...........................................................................................................................3
1.1 Validity .......................................................................................................................................3
1.2 User ...........................................................................................................................................3
1.3 Symbols.....................................................................................................................................3
1.4 Safe Work..................................................................................................................................4
1.5 Limitation of Liability ..................................................................................................................5
1.6 Customer Service ......................................................................................................................5
2 Introduction .....................................................................................................................................6
3 Put into operation ...........................................................................................................................7
3.1 Connect the Gateway ................................................................................................................7
3.2 Test the PROFIBUS connection................................................................................................8
3.3 Parametrization .........................................................................................................................9
3.4 set_prm Parametrization .........................................................................................................10
4 Data exchange...............................................................................................................................15
4.1 Send Data................................................................................................................................15
4.2 Receive Data ...........................................................................................................................15
4.3 Send and Receive Data...........................................................................................................24
5 Status and Error Messages..........................................................................................................25
5.1 External Device Diagnostics....................................................................................................25
5.2 Communication Status ............................................................................................................26
6 Connector Assignment and Cabling ...........................................................................................27
6.1 PROFIBUS ..............................................................................................................................27
6.2 Serial Interface ........................................................................................................................29
7 FAQ.................................................................................................................................................32
8 Technical Data...............................................................................................................................33

XPS-E 3 / 36
1 Working with XPS
1.1 Validity
This Document is valid for the following products:
– 100205
1.2 User
The Art may only be assembled, installed and put into operation by
trained, qualified personnel. Before assembly, it is absolutely
essential that this documentation has been read carefully and
understood. Expertise in the following fields is assumed:
– Electronic circuits,
– Basic knowledge of PROFIBUS,
– work in electrostatic protected areas,
– Locally applicable rules and regulations for occupational safety.
1.3 Symbols
The symbols used have the following meaning:
DANGER Hazard
Observe this information without fail!
There is a safety hazard that can lead to serious injuries and death.
WARNING Caution
There is a safety hazard that can result in minor injuries and material
damage.
NOTICE Note
There is a safety hazard that can result in material damage.
Working with XPS-E

XPS-E 4 / 36
1.4 Safe Work
WARNING Damage and serious personal injury due wrong power supply
XPS-E is designed exclusively for PELV operation according to EN 60950 /
EN 60204 / VDE 0805-1
èOnly protective extra-low voltages according to the defined standards
may be used to supply and connect the alarm contact.
NOTICE Electrostatic discharge
The device contains components that can be damaged or destroyed by
electrostatic discharge
èWhen handling the device, observe the necessary safety precautions
against electrostatic discharge (ESD), in accordance with EN 61340-5-1
and EN 61340-5-2, as well as IEC 61340-5-1 and IEC 61340-5-2.
NOTICE Shielding
The shielding ground of the connected twisted pair cables is electrically
connected to the female connector.
èWhen connecting network segments, avoid ground loops, potential
transfers, and voltage equalization currents via the braided shield.
NOTICE Damage due to subsequent processing
Avoid subsequent processing of the FNL.
ØSoldering can cause components to become detached and thus
damage or destroy the module.
ØPlease note that the warranty shall become invalid if the products are
changed technically.
èSpeak to your contact person at the KUNBUS GmbH about customised
solutions.
Working with XPS-E

XPS-E 5 / 36
1.5 Limitation of Liability
Warranty and liability claims will lapse if:
– the product has been used incorrectly,
– damage is due to non-observance of the operating manual,
– damage is caused by inadequately qualified personnel,
– damage is caused by technical modification to the product (e.g.
soldering).
1.6 Customer Service
If you have any questions or suggestions concerning this product,
please do not hesitate to contact us:
KUNBUS GmbH
Heerweg 15 C
73770 Denkendorf
Germany
[phone]
[email protected]
www.kunbus.com
Working with XPS-E

XPS-E 6 / 36
2 Introduction
The intelligent PROFIBUS-DP gateways of the KUNBUS XPS-E
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:
Illustration1: Typical Connection
Introduction

XPS-E 7 / 36
3 Put into operation
3.1 Connect the Gateway
1 2 3 4
5
678
9
10
Illustration2: Connectors and Interfaces of the XPS-E
1 Bus Fail LED 2 Run LED
3 Address Switch x10 4 Address Switch x1
5 Connector for power supply 6 Mode-LED
7 TxD LED 8 RxD LED
9 Serial Interface 10 PROFIBUS Interface
Put into operation

XPS-E 8 / 36
By executing the following steps, the XPS-E Gateway can be set into
operation:
◦ Connect 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 Cabling
[}27]“ and follow the Installation Guidelines for PROFIBUS (No. 2.112,
PNO).
◦ Connect the serial end device with XPS-E
◦ Check your PROFIBUS network with regard to an unused Slave
address and adjust this free address at the coding switch of XPS-E.
◦ Plug in the power supply. 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.
NOTICE The Status/Busfail LED is flashing red until the device is
parameterized and configured
In this status, no data exchange can take place (neither send nor receive).
Only after successful parameterization and configuration the Status/Run
LED is flashing green. Now, the device is ready for data exchange.
3.2 Test the PROFIBUS connection
If you have a PROFIBUS-DP configuration tool, you can test the
PROFIBUS connection to the XPS-E Gateway. For this purpose,
load the deliverable GSD file into your configuration tool.
The DP Master shall now configure 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 (User_Prm_Data) in the GSD
file, please refer to the following chapters for the parameterization.
Put into operation

XPS-E 9 / 36
3.3 Parametrization
The parameterization data of XPS-E consists of 7 DP-Slave standard
bytes and 16 device-specific parameters bytes (User_Prm_data, ->
user_prm_len = 16). As user diagnostic data, 8 additional diagnostics
bytes are available. (diag_len = 8).
◦ For initialisation of XPS-E send a set_prm telegram. For this purpose,
use the parameters for PROFIBUS-DP and the serial interface
described in chapter 2.5.
◦ Check the parameterization with slave_diag.
◦ Then use the command chk_cfg to configure the XPS-E. Prior to that,
the configuration can be read with the command get_cfg from XPS-E. If
chk_cfg is executed directly after the initialization, the maximum
data_exchange telegram length is loaded from XPE-E. For shorter
data_exchange telegram length select one of the possible
configurations which are defined in the GSD file or select those
arbitrarily according to the PROFIBUS-DP standard.
ðAfter successful parameterization XPS-E is prepared for data exchange.
The Status/Run LED is now flashing green.
NOTICE You can verify the parametrization and configuration telegram by
means of slave_diag.
In the following, only those parameters are described that are required for
operating the XPS-E. For the significance of the remaining PROFIBUS- DP
standard parameters please refer to the standard EN50170 and the GSD
file.
Also see about this
2set_prm Parametrization [}10]
Put into operation

XPS-E 10 / 36
3.4 set_prm Parametrization
The Bytes 1-7 are PROFIBUS-DP standard parameters, Byte 8-23
are device- specific parameters (usr_prm).
Oktet Parameter Name Value
1 Station_status 0x80*
2 WD_fact_1 0x00
3 WD_fact_2 0x00
4 Min TSDR 55
5 Ident_Number [0] 0x95
6 Ident_Number [1] 0x10
7 Group_Ident 0x00
8..11 Reserved -
12 Baud Rate setting of serial interface See Table „Baud Rate of
Serial Interface“ [}10]
13 Character Transmission Mode of serial
interface
See Table „Character
Transmission Mode
“ [}10]
14 Handshake setting of serial interface See Table „Handshake-
Mode“ [}10]
15 XOFF-Timeout of serial interface See Section „Timeout Soft-
ware Handshake/Mod-
bus“ [}10]
16 Receive Mode of PROFIBUS interface See Table „Data Transmis-
sion Mode“ [}10]
17 Receive Mode of PROFIBUS interface See Table „Extended
Gateway configuration
data“ [}10]
18 Trigger character for serial triggered
mode
(usually LF (0x0A)
-
19..23 Reserved -
Table1: set_prm
*Sync_Req and Freeze_Req are not supported.
Put into operation

XPS-E 11 / 36
Next to standard parameters the parameters for the serial interface
are included in the GSD file. They are listed under the
User_Prm_Data. The values correspond to those described under
chapter „set_prm Parameterization”. 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-E are listed.
9600 Baud / 8Bit / No Parity / 1 Stopbit / no Handshake / no
Timeout / Poll- Mode / RS232-Mode
This corresponds to the following entry in the GSD file:
User_Prm_Data = 0 0 0 0 96 56 78 0 80 0 0 0 0 0 0 0
Octet 1-7 are PROFIBUS-DP Standard, Octet 8-14 are the device-
specific diagnostics parameters (external diagnostics).
Oktet Parameter Value
1 Station_status_1 Bit7 Diag.Master_Lock
Bit6 Diag.Prm_Fault
Bit5 Diag.Invalid_Slave_Response
Bit4 Diag.Not_Supported
Bit3 Diag.Ext_Diag
Bit2 Diag.Cfg_Fault
Bit1 Diag.Station_Not_Ready
Bit0 Diag.Station_Non_Existent
2 Station_status_2 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
3 Station_status_3 Bit7 Diag.Ext_Diag_Overflow
Bit6..0 reserved
4 Master_Address Master address or 0xFF, if Slave is not yet
parameterised.
5 Ident_Number[0] 0x95
6 Ident_Number[1] 0x10
7 Number of ext.
diagnostic bytes
8
Put into operation

XPS-E 12 / 36
8 XPS-E Status See Chapter „External Device
Diagnostics” [}25]
9 Baud Rate of the serial
interface
See Chapter „Parameterization“, Section
„Baud Rate“ [}10]
10 Character Transmis-
sion Mode of serial
interface
See Chapter „Parameterization“, Section
„Character Transmission Mode“ [}10]
11 Handshake setting
serial interface
See Chapter „Parameterization“,
Section „Handshake“ [}10]
12 XOFF-Timeout of
serial interface
See Chapter „Parameterization“,
Section „XOFF“ [}10]
13 Receive Mode of DP-
interface
See Chapter „Parameterization“, Section
„Data Transmission Mode“ [}10]
14 Setting of driver phys-
ics of serial interface
(RS232/485)
See Chapter„Parameterization“,
Section „Data Transmission Mode“ [}10]
15 Trigger character for
Serial triggerd Mode
0x0A
Table2: slave_diag
Parameter Description
The parameters marked with (*) are the default values. These are
used if inadmissible parameters are entered during parameterization.
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 Oktet 12
Put into operation

XPS-E 13 / 36
Character Transmission
Mode Transmission-Mode Value
(dec)
Value
(hex)
Value
(ASCII)
8 Datenbits, No Parity, 1 Stopbit (8N1) * 56 0x38 ‘8’
7 Datenbits, No Parity, 2 Stopbits (7N2) 78 0x4E ‘N’
7 Datenbits, Even Parity, 1 Stopbit (7E1) 69 0x45 ‘E’
7 Datenbits, Odd Parity, 1 Stopbit (7O1) 79 0x4F ‘O’
Table4: Character Transmisson Mode Oktet 13
NOTICE The operating mode: 7 data bits, No Parity, 1 StopBit is not supported.
Handshake Flow Control If data is exchanged via the serial interface, 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 „S [}29]erial Interface“.
– 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-E (See Chapter„Communication
Status [}26]“ ) by means of the bit XOFF_CTS_FLAG.
Handshake-Mode Value
(dec)
Value
(hex)
Value
(ASCII)
Hardware Handshake (CTS, RTS for RS232
and CONTROL/INDICATION for RS422)
72 0x48 ‘H’
Software Handshake 83 0x53 ‘S’
NoHandshake * 78 0x4E ‘N’
Table5: Handshake-Modi Oktet 14
XOFF/ Modbus_timeout –
Timeout Software
Handshake/Modbus
The XOFF/Modbus timeout is calculated by means of VALUE *
100ms. This value is entered into Octet15 of the parametrization
data. If no software handshake or no Modbus Mode is selected, this
value is insignificant.
NOTICE If the value 0 is given, the timeout is set to 10 seconds.
Put into operation

XPS-E 14 / 36
DP-Data Transmission Mode To offer the user several possibilities to adapt his application
optimally to the gateway functionality of XPS-E, 3 data transmission
modes can be used. The corresponding description is found under
chapter „Data Exchange“ ff. [}15]
Data Transmission Mode Value
(dec)
Value
(hex)
Value
(ASCII)
Poll-Mode * 80 0x50 ‘P’
Request-Mode 82 0x52 ‘R’
Serial triggered-Mode 83 0x53 ‘S’
Modbus RTU 83 0x4D ‘M’
Modbus ASCII 83 0x41 ‘A’
Table6: Data Transmission Mode Oktet 16
Extended Gateway
configuration data Extended configura-
tion byte
Bit Function
Bit7 ..Bit2 reserved
Bit1 Double baud rate
Bit0 RS232<->RS422
Table7: Extended configuration byte Oktet 17
– BIT0: RS232<->RS422 – Serial interface physics
With this parameter the interface physics can be set to RS232(0) or
RS485(1).
– 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.
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 eingetragen werden.
Trigger character Value
(dec)
Value
(hex)
Value
(ASCII)
LF * 10 0x0A LF
Table8: Trigger character Oktet 18
Also see about this
2set_prm Parametrization [}10]
Put into operation

XPS-E 15 / 36
4 Data exchange
4.1 Send Data
To send data via XPS-E onto a serial end device, the send flag of
XPS-E must be reset (ref. Communication Status, Bit 0 = 0), as
otherwise the send data to 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)
4.2 Receive Data
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
parameterization of XPS-E by the Master (See Chapter„s
[}10]et_prm Parameterization“, Section „DP-Data Transmission
Mode“). In the Poll mode available receive data will be sent at every
data_exchange.req with the corresponding data_exchange.res from
XPS-E to the PROFIBUS-DP Master. In the Request mode the XPS-
E sends this data only if in data_exchange.req a defined byte 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

XPS-E 16 / 36
Poll Mode
In this mode 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.
NOTICE 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.
Illustration3: Data Reception in Poll Mode
x= Receive Request Number S= Status
The telegrams mentioned above can either be started automatically
by the Master (cyclically during automatic polling) or by the
application.
NOTICE The receive request number (X) in Poll Mode may not be set.
Data exchange

XPS-E 17 / 36
1. The data_exchange.req telegram is sent to XPS-E. 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-E is returned.
¬
2. New data_exchange.req telegram.XPS-E returns the new data by
incrementing the confirmation number by 1.
¬
3. 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.
¬
4. 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-E must be run in the request mode.
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-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.
Illustration4: Empfang im Seriell getriggerten–Modus(Endezeichen:0x0A)
x= Receive request number S= Status
Data exchange

XPS-E 18 / 36
NOTICE Please note, that it is not necessary to set the receive request number (X)
in polling/serial Mode
1. The data_exchange.req is transmitted to the XPS-E. 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 data_exchange.req service. XPS-E responds with the old data.
New data are in fact received, but they do not contain the trigger
character.
¬
3. Next data_exchange.req service. XPS-E responds with the old data,
because no further serial data were received.
¬
4. Next data_exchange.req service. XPS-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.
¬
Request-Mode
In the request mode the 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 data_exchange service. This
means that the data are returned always only in the subsequent
cycle of the request. If the response telegram contains received data,
the XPS-E confirmation number is incremented by one and returned
in the response telegram (as in the poll mode).
NOTICE 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
Data exchange

XPS-E 19 / 36
Illustration5: Data Reception in Request Mode
S= Status
Data exchange

XPS-E 20 / 36
1. The data_exchange.req telegram is sent to the XPS-E which already
has received the first characters. It returns them, however, only in the
subsequent response telegram data_exchange.res.
¬
2. New data_exchange.req telegram with increased receive-request
number (further reception command). XPS-E returns the data received
at point in time. The confirmation number is increased by one.
¬
3. Another reception command to XPS-E (receive-request number has
been increased). The data that are returned are the data received at
point in time.
¬
4. No further reception command to XPS-E. XPS-E returns again the last
sent data. XPS-E has already received new data.
¬
5. No further reception command to XPS-E. XPS-E returns again the last
sent data.
¬
6. This data_exchange.req contains another reception command. The
data are returned, however, only at the next cycle.
¬
7. 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.
¬
Data exchange