Contents

Contents ................................................................................. 2

Computer-linking using Siemens 3964R ............................. 4

_Connections and _settiings .................................................. 4
Communications ... �............................................................. 5
Data interchange......................................................... 5
Data transmission using Procedure 3964R ............. 5
u •••••••.

General remarks on the tr�nsmissiao ..procedure .... :5

Linking to devices of other manufacture ......,............-5
Link set-up................................................................... 6
Transmission .............................................................. 6
Telegram head ............................................................. 6
Data .................................. ····························-··············· 7
Link termination .......................................................... 7
Control characters ...................................................... 7
Block check character ................................................ 7
Job type ............................................................................... 7

CAN bus communication DTC6200...................................... 8

Connections and settings .................................................. 8
Communications ................................................................. 9
Request messages to the DTC6200 ................................... 11
FUNCTION CODE ......................................................... 11
Response messages from the DTC6200 ...........................12
Error codes ........,..........................................................12

Mod bus protocol .................................................................... 13

Connections and settings .................................................. 13

ldent-Nr 37418615 page 2

 Co mmunications ................................................................. 14
Request messages to the DTC6200· ....••............................ 14
Function Codes (READ' I VVRffE MODE ) .................. 1:5

Response messages from the DTC6200 ........................... 1·5

E RROR CODES: .......................................................... 16

DTC6200 data fields (General descrip,tion) ........... �·:··········· 17.

Example of h ow to interpret binary-values ....................... 17
Example of how to interpret 16 bit integer-values ........... 17
Example of how to interpret 32 bit IEEE values ............... 18

Data fields: ........................................................................... 18

Data access to DTC6200 (in detail) ...................................... 22

ldent-Nr 37418615 page 3

Computer-linking. using Siemens 3964R

Connections and settings

The DTC6200 system is circuited for SIEMENS 3964R coupling via an RS485 interface on 1the

PHOENIX connector #7, Pins 2-5

The number of bus nodes is physically restricted to a rna,(1111um of 32 {indudif'l!� the master). The RS485
coupling is implemented in the form of a two-wire bUJs wittl the followifl!� pin assigmnerits:

Pin 2: Rx+ Pairallel to all users (nodes)

Pin 3: Rx- Parallel to all users (nodes)
Pin 4: Tx+ Bridge to Pin 2
Pin.5: Tx- B1ridge to Pin 3

The DTC6200 supports twenty-six different transmission rates. of which one is definecj using the pa rametering
software.
Possible DTC6200 transmission rates in Baud:

1. 125000
2. 62500
3. 41667
4. 31250
5. 20833
6. 15625
7. 10417
8. 9600
9. 7800
10. 5208
11. 4800
12. 3906
13. 2604
14. 2400
15. 1953
16. 1302
17. 1200
18. 977
19. 651
20. 600
21. 488
22. 326
23. 300
24. 244
25. 150
26. 75

The SIEMENS 3964R baudrate is 9600 Baud.

Bear in mind the following when programming tlhe smial interface in the process control system:
• the following are transmitted for transmission of one byte: 1 s tart bit, 8 data bits and ·1 stop bit
• even, odd or no parity can be set (the setting must be the same as on the DTC6200)
• the DTC6200's Baud rate (default setting: 9600 Baud) is needed

ldent.. Nr 374186'15 page 4

Communications

Data interchange
In automation systems, data is frequently interchanged
• between process computers or
• between one process computer and a higher-level rimaster")system
The DTC6200 process computer is able to implement data interchange with the following c:1utornc1tion dev·,ces:

Siemens automation devices of the following series:

• Simatic-SS-U (11SU, 135U, 1SOU, 155U) incorporating the CP 524 communications processor and the RS
485 module (Procedure 3964R and Interpreter RK512)
• communications modules and assemblies compatible with the c:1bove-mentioned Siemens systems ar;d
incorporating the .�ame procedure

Data transmission using Procedure 3964R

General remarks on the transmission procedure

In data transmission between two devices, both parties must have the
same interface and use the same transmission procedure. The procedure
regulates the chronological sequence and operating behaviour of the data
transmission system and consists of the following phases:
• Request for data transmiission(setting-up of the link),
• Data transmission(telegram set-up and data protection)
• Termination of data transmission (termination of the link).

Transmission procedure 3964R, which is used in any computer link

between the DTC6200 and the Siemens CP 524, is described below:
Procedure 3964R is an asynchronous, bit-serial transmission procedure.
The transmission and reception rate (Baud rate) must be set to the same
figure on the active and oin the passive module, since no :signal element
timing circuits are routed between the two devices (asynchronous).
Control and information characters are transmitted via the connecting
links. Further bits are prefixed and suffixed onto the ,characters
transmitted in order to permit recognition of every character by ti1e
recipient and in order to clheck correct transmission.

In Procedure 3964R for computer linking, one start bit, eight information
bits(= character length), one stop bit and the parity bit with a suffix or
verification for even parity are fixed.

Linking to devices of other manufacture

The devices must use the same procedure if a link is to be installed
between the DTC6200 and devices of other manufactures.

ldent-Nr 37418615 page 5

Link set-up
The link set-up checks whether 1the other participant device is ready. In
their default condition, both the active and the rE�cipient device a re ·,n
receiving mode. In order 1to set iup the link, the a dive devioo trainsmits the
STX(= Start of Text) control character. Providod the recipient idev"ice
answers with the OLE (Data Link Escape) character before 1the expiry of
the acknowledgment delay QVZ (two seconds), the .active dev"ice will
change to transmission mode.
If the recipient device answers with INAK (negaflve acknowledge), any
other character (except OLE or :STX) or if the acknowledgment delay
expires without a reaction beinu de1tected, the link. siet-up has.failed. The
procedure will terminate the pn:>Cless after a total ,of six 1unsucce:ssful
attempts and will signalize a fault in the link. set-up.

Transmission
If link set-up is successful!, the payload information character now
contained in the current o utput buffer memory (telegram head and data)
will be transmitted to the ireceivlng device at the selected \ransmiss•on
rate. The receiver device monitors the characters arriving ·111 the,ir
chronological intervals (character delay ZVZ = 220 ms).

Telegram head
The telegram head is ten characters long and contains the following data:
• the ADDRESS (DESTINATION), to which the data is to be delivered
and/or
the source from which the data is to be taken,
• the amount of the data to be transmitted,
• a statement of the coordination flag.

ldent-Nr 37418615 page 6

 The following conventions have been agreed for the telenrarn heaci for
transmission using the DTC6200·.

• command type (Byte 4):

the DTC6200 permits only tile Type D = data module as the
command type, i.e., th,e type of data to be transmitted. This
applies to fetching andl transmission of data.
• Byte number of the coordination flag (Byte 9):
no coordination flag is stated, i.e., the value #FF ·,s
entered at this point.
• Byte number of the coordina1tion flag (Byte 9):
no coordination flag is stated, i.e., 1the value #Fis entemd at
this point.

Data
Transmission of the telegrram head is followed by transmission of the
· ·· data. The DTC6200 is res.trictecl to an amount of 128 byte.

Link termination
The link termination informs the active device that the activity of the
recipient device has termiinated. After sucoessful transmission of the
content of the buffer, the procedure adds the characters OLE, ETX (End
of Text) and BCC (Block Check Character) as ;an end marker and waits to
receive an acknowledgment character. The receiving device transmittil'l!�
the DLE character within tthe acknowledgment delay indicates that the
data block has been transmitted without error. If the receiving devioe
answers with NAK, any otlher d1aracter (except for DLE), a defe1ctive
character or if the acknowledgment delay expires without a reaction being
received, the procedure repeats the transmission of the data block. After
a total of six unsuccessful attempts at transm�tting the data block, the
procedure terminates the process and signalizes an error ·rn the link set­
up.

Control characters
The control characters STX, etc., conform to the DIN 66 033 sltandard (7
bit code) but are transmitted with an 8 bit character length (bit 7 = 0).

Block check character

The block check character BOC transmitted at the end of each data block
enhances the error-proofing of data transmission.

Job type
Two job types are available for communication usirng the DTC6200. These are, for fetching of data
from the DCT6200, the FETCH job, i.e., the device linked to the DTC6200 fetches data from the
DTC6200 on its own initiative. The SEND job is available for the transmission of data 'to the
DTC6200 from the linked device on its own initiative.

ldent-Nr 37418615 page 7

CAN bus communication DTC6200

Connections and settings

For the CAN bus link, the DTC6200 system is circuited via a PC82C250 CAN driver on the

PHOENIX connector #6, Pins 2-5

Die CAN bus link is implemented in the form of a two-w·ire bus with the following pin a5.signrnents:

,Pin 2: CAN + Parallel to all users \nodes)

Pin 3: CAN - Parallel to all users (nodes)

The DTC6200 supports all the bit rates possible using the CAN POB2C200 controller up to a max·1mum of 1
Mbit/s.
The bit rate parameters, CAN ID and acceptance code/mask are preset using the OTC pararnetming program
on the DTC6200.

It should be noted at this point that line resistances and dosecl conductors are usod to minimize reflection ·,n the
case of large bus lengths and/or high transmission rates.
This is of great significance for a high payload data rate and safe transmission.

Attention is drawn to the corresponding data sheets for the Philips CAN PC82C200 contr1oller and the
Philips PC82C250 line driver for a precise description o,f title CAN parameters and the physical bus
characteristics.
The default settings on the DTC6200 are:

BPR 7
TSEC1 11
TSEC2 2 -+ 62500 Baud
SJW 1
SAM 0
AC 0
AM 255

ldenlt-Nr -------
374186'15 page 8
Communications
Data interchange between the host or master comput,er a1nd the DTC6200 ·,s, based on the package-oriented
CAN bus log (protocol), implemented in a certain series of CAN packages.
This occurs as follows, in a master-slave concept:

Using the standard OTC software, a DTC6200 can lbe opmated only as ttle CAN bus slave. The rnaster is
implemented by means of a master computer.
Special test software makes it possible to also operate a DTC6:200 as the master, however.

Communication between a DTC6200 slave and the master is accomplished by means of a requesUresponse
message, the master always transmitting a reqlles:t message and then rec:e·1ving a re�;ponse message from
the slave addressed, provided this is present.

All messages start with a CAN-RTR package (see CAN bllJs literature), followed by one or several CAN data
packages with a data-byte length of eight payload data bytes. Tile message ciondudes with a data package of a
length less than eight payload data bytes (or even no payload data byte).

ldent-Nr 37418615 page 9

Message in CAN packages:

RTR-P'ACKAGE
0-N data pack.ages with a length of 8
payload data bytes
Closed by a data package with a length .
smaller than 8 payload data bytes

The number of payloa<1 data packages is determined by the total number of payload cfata bytes \o be
transmitted in the message.

T he first data byte of a message is always the !;lave address.

Messages wrth the slave address Oare broadcast messages which are received by all sl,:ives and which are n
followed by a response message to the master.

Securement of data is implemented in hardware fom, by1the CAN controller.

The master can either read data fields from the DTC6200 or write into the DTC6200.
If the master system wishes to read a DTC6200 da'ta field, it firstty transmits a request message with the
command code READ the number of the clata field c:md, in case of "write", the data cofltent
If the pa,ckage is not a broadcast package, the slave addressed replies within a time-o:ut fnne ,of five secoods
with a response message, which will contain an error code (O=no error) ano, where appropriate, lthe data
requested by the master.

ldent-Nr 37418615 page 10

 Request messages to the DTC6200
Structure of data bytes in a request message
(from MASTER-> SLAVE):

SLAVE ADDRESS
FUNCTION CODE
DATA INDEX
Always O
DATA (only for write)

The fields for the request message have the followii1ng mei:m·rngs:

SLAVE ADDRESS:
Address of the slave, 0 => all slaves ("broadcast")

DATA INDEX:
Number of the data field to be addressed in the slave (data field No.: see the "Data fields" section)

DATA:
Data bytes for a write command (max. 128 bytes). Tine number of data bytes must be identical to the size of thi
target data field selected in the slave !
This field is empty in the case of the READ command.

HI-BYTE CRC:
Higher-value byte of the 16 bit CRC.

LO-BYTE CRC:
Lower-value byte of the 16 bit CRC.

FUNCTION CODE
Code for reading (data from slave to master) or writing (clata from master to slave)
The following function codes are supported by a DTC6200 siave:

FUNCTION-CODE Message type data bytes

041h READ command none
(dez. 65)
042h WRITE command Data to be written
(dez. 66)

l<jent-Nr 37418615 page 1 ...

Response messages from the DTC6200
Structure of the data bytes ·m a response message
(from SLAVE-> MASTER):

SLAVE ADDRESS
FUNCTION CODE
DATA INDEX
ERROR
DATA (only for READ and ERROR 0) ..

The response message fields have the follow'mg meanings:

SLAVE ADDRESS:
Address of the slave to be transmitted (cannot be 0, since 1110 broadcast replies occur)

FUNCTION CODE:
Fu nction code of the request previously received

DATA INDEX:
Number of the data field in ttle slave requestied by the maste r (data field No.: see the "Data fiek:ls" sedtion)

ERROR:
<>O => Error in the rn�uest. Error codes: see below

DATA:
Data following read c:ornmmld and ERROR= O (max. 128 bytes)

Error codes
The f ollowing error codes may occur in a respon:se message:

:RESPONSE Erro:r:
OOh INo erl.:or
Olh Illegal C��·-Code (see above)
02h Illegal data f:ield
03h IWri·te no·t p,oss:i.ble (I)TC62 00 no t in REMOTE mode)
04h Illegal acoess (READ only or WRITE only)
OSh IRese:r:ved
06h !Number of paylo,ad data tra:nsmitted by the master
for a write command not identical with the size
of the data field se.lect.ed

ldent-Nr 37418615 page 12

Modbus protocol

Connections and settings

Use the following connector to conned the DiC6200 with another MODBUS device

PHOENIX-connector #7, Pin 2-5

The maximum number nodes ·,n the bus is physically limited to 32 (incl. master)
The MODBUS-link is rearized by a 2-w1re-Bu s, the n!quired connections are:

Pin 2: Rx+ ParaUel to all nodes

Pin 3: Rx- Parallel to all nodes
Pin- 4: Tx+ Bridge to Pin 2
Pin 5: Tx- Bridge to Pin 3

The DTC6200 supports 26 Baud rates, the valid Baud rate has to be fixed in the configuration of the system a
may be selected by the req uirernents of the master
Su pported Baud rates are:

1. '125000
2. 62500
3. 41667
4. 31250
5. 20833
6. 15625
7. 10417
8. 9600
9. 7800
10. 5208
1'1. 4800
12. 3!906
13. 2604
14. 2400
15. 1B53
'16. 1302
17. 1200
18. g·n
19. 651
20. 600
2"'1. 488
22. 326
23. 300
24. 244
25. 150
26. 75

For adjusting the serial interface of the DCS keep in mind:

• transferring one byte means: 1 start bit, 8 data bits and 1 stop bit.
• even, odd or no parity bit can be selected (there must be the same
setting in the DTC6200 c•ontroller)

ldent-Nr 37418615 page 13

 • Baud rate of the DTC6200 contr·oller (pre-setting is 9UOO Baud) is mandatory

Communications
The DTC6200 is always handled as a MODBUS-Slav,e. The mas;terwm be the DCS.

The communication is real'rzed by request and answer. The master sends a request and gets an answer �mm
the slave, if the slave with the ID addressed by the rnaste� exists .and the slave received the request w"rt hout
errors (CRC OK).

The first byte is the slave address.

Requests with slave address Oare broadcast-messages, received from all s\aves. The slaves won\ send an
answer to the master.

A safety check will be done by a 16-Bit CRC accoirding to MODBUS specification at the end of each data
transfer.

The mas\er can either mad data fields from the DTC6200 or write ·into the DTC6:200.
If the master system wishes to read a DTCB200 data field, it firstly transmits a request message with the
command code READ the number of the oata field and, in case of ·write", the data content.
If the package is not a broacica st package, the slave addressee! replies within a time-ou t rune of five seconds
with a response message, whiGh will conta·,n an enor ,code (O=no enror) and, where appropriate, the data
requested by the master.

After getting the first byte an end of data:transfer detection mode is activated. If a delay period corresp,ond'mg to
the sending time of 3.5 bytes is oetected, \tie end of a data transfer wil l be recognized.

Request messages to the DTC6200

Structure of a request from MASTER-> SLAVE:

SLAVE ADDRESS
FUNCTION CODE
DATA INDEX
error code, for request always "0"
DATA ( only WRITE-MODE)
HI-BYTE CRC
LO-BY'I'.E CRC

The meanings of the items mentionecj above are:

SLAVE ADDRESS:
address of the slaves, 0 => all siaves (broadcast)

FUNCTION CODE:
reading code (data from slave to master) or writing cod6' (dat.a from master to :slave)

ldent-Nr 37418615 page ·14

DATA INDEX:
ID of the addressed data in the slave (DB No. see charter "Data access to DTC6200 (in detail)")

DATA:
Data bytes if the writing mode is selected (max. 128 bytes). The nrnnber of bytes must be idenrical t,o the
number of data bytes that are system defined for the· selectE.->d ID
This segment is spare in case of defining the reading mode.

HI-BYTE CRC:
high byte of the 16-Bit CRC.

LO-BYTE CRC:
low byte of the 16-Bit CRC.

Function Codes (READ I WRITE MODE )

These function-codes are supported by the DTC6200 slave:

FUNCTION-CODE message mode DATA bytes

041h
(Dec. 65)
command READ no bytes
.
042h command WRITE data that have to be
(Dec. 66) sent to the slave

Response messages from the DTC6200

Structure of a DTC6200 answer SLAVE-> MASTER:

SLAVE ADDRESS
FUNCTION CODE
DATA INDEX
ERROR
DATA (only for REJ� and ERROR;:::0)
HI-BYTE CRC
LO-BYTE CRC

The meanings of the items mentioned above are:

SLAVE ADDRESS:
Add ress of the s lave to be transmitted (cannot be 0)

FUNCTION CODE:
Function Code of the request previously recerved.

ldent-Nr 374'18615 page 15

 ERROR:
<>O => ERROR in the request; see ERROR CODE:S.

DATA INDEX:
ID of the data requested from the master (DB Number see chapter "Data access to DTC6200 (in
detail)")

DATA:
Data bytes if ERROR was "O" and the re,ading mode was requested by \tie master (max. '128 bytes).

HI-BYTE CRC:
high byt�. of the 16-Bit CRC.

LO-BYTE CRC:
low byte of the 16-Bit CRC.

ERROR CODES:
RESPONSE ERROR
OOh no ERROR
Olh no valid COMMAND-Code tsee abm1e)
02h no data with this ID
03h cannot write (DTC6200 not in REl"!OTE-Mode)
04h access den ied (read-o:nly or wci te-only)
OSh reserved
06h number of data to write does not fit the system
requirements of the selected data field

lderl't-Nr ���������-
374'18615 page '\6
DTC6200 data fields (General description)
The DTC6200's various process data can be selected by the master system by means of data fields.
These data fields are numbered and can only be read or written co mpletely.
Immediately a read command arrives for a valid data field, it is copied into a buffer in Hie DTC6200 and data
transmission is performed from this buffer.
If a write command occurs, the data to be written is first tiransferred to a buffer of the DTC620D and transmittec
only following reception of the final byte to be writter. in the DTC6200's target data field.
The data within a data field is organized word-by-word (16 bit}, the higher-value byte of a word being located.
lower-value addresses (i.e., Motorola format).
The data located at lower-value addresses is transmitted first "ir1 a data transm·1ssion operation!

Floating-point numbers are shown in simplified accuracy l1evel ir. the 32 bit IEEE standard draft 754 - format.
Here, too, the highest-value byte is located at the lowest addrnss:

MSB
sign exponent mantissa
1 Bit 8 Bits 23 Bits

Conclusion:

The higher-value bytes of a word (16 bit), a long word (32 bit) or a floating-point number (32 bit IEEE)
are transmitted first.

Example of how to interpret binary-valuies

read DIN 1-16 (0810, OW 0)
The result is:
hexadecimal 3E J:l..A
binary (value of the DIN) 0 0 1 l 1 1 1 0 1 '0 1
0 1 0 1 0
position of the bit or DIN no. 7 6 5 4 3 2 1 () 15 14 13 12 11 10 9 8

Example of how to interpret 16 bit integer-values

read AIN 1 (0820, OW 0)
The result is:
hexadecimal 03 D7 I
decimal value 98:3 digits
meaning the AD co nverter has a range of 0-4096
digits equiv.alent to the OmA - 2 OrnA
signal

ldent-Nr 37418615 page 17

Example of how to interpret 32 bit IIEEE values
read AIN 1 (0830, OW 0/1)
The result is:
hexadecimal 41 I TL I E.2 I 08
decimal value l.'5, 11
meaning the FTlOl transmitter indicates: •.

6p = 15, 11 mbar

Data fields:

(DB x= data field no. x, OW = data word)

DB 10: digital inputs(DIN) read only 4 Words

OW O: DIN Channel1-16 i(Bit 0-15)
DW1: DIN Channel17-32
DW2: DIN Channel33-48
DW3: DIN Channel39-64

DB 11 : digital outputs(DOUT) read only 2 VVords

OW0: DOUT Channel1-16 {Bit0-15)
OW 1: DOUT Channel17-32

DB 20: analog inputs(AIN), read only 64 Words

digits, 16 Bit
o = O mA, 3958 = 20 mA
OW O: AIN Channel 1
OW1: AIN Channel 2

DW63: AIN Channel 64

DB 30: analog inputs (SI-AIN), read only 64 Words

SI units (see parametelring)
32 Bit IEEE floating point v al1ue
OW0/1: AIN Channel 1
OW2/3: AIN Channel 2

DW62/63: AIN Channel 32

DB3 1: analog inputs (SI-AIN); read only 6 4 Words

SI units (see parametering),
32 Bit IEEE floating point va·1ue
OW0/1: AIN Channel 33
OW2/3: AIN Channel 34

ldent-Nr 37410615
���������
page ·1a
 DW62/63: AIN Channel 64

DB 50: analog outputs (AOUT), read only 115Words

Digits, 16 Bit
O = 4 mA, 4095 = 20 mA
DW O: AOUT Channel 1
DW 1: AOUT Channel2

DW 15: AOUT Channel16

DB 60: analog outputs (SI-AOUT), read only 32 Words

SI units (see paramete1ring)
32 Bit IEEE floating point value
DW 0/ 1: AOUT Channel1
DW2/3 : AOUT Channel 2

DW 30/31: AOUT Channel16

DB 70: control parameter, Head/write :34 Words

controller1 -2
controller1:
DWO: Enable (=1 )/Disable (=O)
DW1: Hand (=1)/Auto (=O)
DW2: Extern ( =1)/lntem (==O)
DW3/4: kp (32 Bit IEEE floating point value)
DWS/6: Tn (32 Bit IEEE floating point value)
DW7/8: Tv (.32 Bit IEEE floating point valu e)
DW 9/10: set-point (32. Bit IEEE noatrf'\!J point value)
DW 11/12: manual value (32 Bit IEEE floating point V�tlue)
DW13/14: actual value (read only ) (:�2 Bit IBEE floating point value)
DW15/16: output (read only } (32 Bit IEEE floafmg point value)
controller2:
DW 17-33: ditto

DB 7 1: control parameter, Head/write 34 Worc:ls

controller3-4
controller3:
DW 0-16: ditto (see controller 1)
controller 4:
DW 17-33: ditto

DB 90: calculated values read only 40Wmds

32 Bit IEEE filoatin!J point value
DW 0/1: calculated value 1
DW 2/3: calculated value 2

DW38/39 calculated value 20

ld ent-Nr 37418615 page 19

DB 100: commissionintJ parameters, Read/write 60 Words
(soe description),
32 Bit IEEE 1noating point value
DW 0/'1: parameter O
DW 2/3: parameter'\

DW 5B/59 parameter 29

DB 101: commissioning parameters, Head/write 60 Words

DW 0-59 : parameter 30-59

DB 102: commissioning parameters, Read/write 60 Words

DW 0-59: para rneter 60-89

DB 103: comrri"1ssioning parameters, Head/write 60 Words

OW 0-59: pa,c1meter 90-119

DB 1'IO: operational data read only 12 Words

DW 0/1·. operating seconds (32 B"lt LONG WORD)
DW 2/3: operation since last (32 Bit LOING WORD)
st art (in seconds)
ow 4/5: inumber of starts (32 Bit wONG WiORD)
owen: number of shutdowns (32 Bit LONG WORD)
date ,of last shutdowns:
DW8: year(Hi-Byte), rnonth(Lo-Byte)
DW 9: day(Hi-�te), tiour(Lo-Byte)
DW10: minute (Hi-By\e), second (Lo-Byte)
DW11: re.;1son for last shutdown (alarm-index 0-319)
Bit '15: 10=>shutdown, 1 =>normal stop
Bit 14--9: reserved (always 0)
Bit 8-0: alarm \mjex of last stm\d own

lde nt-Nr 37418615 page 20