бахман

Scheidt & Bachmann GmbH Technical Documentation
D-41238 Mönchengladbach Breitestraße 132 Standardised V11 Procedure 85 63506 ( )
Documentation for standardised

V11-Procedure
85 63506 ( ) / 7.1986
V11 Point to Point
DEE DEE
Ls
DEE
V11 Multipoint
DEE DEE
Ls
DEE
© Scheidt & Bachmann GmbH, D-41238 Mönchengladbach GT/Bh / 23/02/2005 / 85 63506.doc Page: 1
Interface according to DIN 66258 and 66019
The interface is based on the following criteria:
1. Polling/selecting operation
2. Half duplex
3. 300 - 9600 Bd.
4. 2- or 4-wire line
5. code-linked data transmission
Symbols used:
0, ENQ Station enquiry / send

1, ENQ Station enquiry / receive
ENQ Station enquiry / status request
STX Start of text

ETB End of data transfer block
ETX End of text
ACK1 Positive acknowledgement DLE 3/1

ACK0 Positive acknowledgement DLE 3/0
NAK Negative acknowledgement
EOT End of transfer
DLE 3/15 WAIT, temporarily not ready to receive
1. Send procedure from control station to DTE
Example 1: one data block

Cs DTE
Setting up the connection
Receive request for DTE 1, ENQ ð
ï ACK0
Transferring a
data block STX,data, ETX ð
ï ACK1
End of data transfer EOT ð
Example 2: several data blocks

Cs DTE
Receive request for DTE 1, ENQ ð
ï ACK0
Data transfer of several

blocks STX,data, ETB ð
ï ACK1
STX, data, ETB ð
ï ACK0
STX, data, EXT ð
ï ACK1
End of data transfer EOT ð
2. Receive procedure of control station to DTE
Example 1: one data block

Cs DTE
Send request for DTE 0, ENQ ð
Transfer of a data block ï STX,data, EXT
ACKO ð
End of transfer ï EOT
Example 2: several data blocks

Cs DTE
Send request for DTE 0, ENQ ð
Transfer of several
data blocks ï STX, data, ETB
ACK0 ð
ï STX, data, ETB
ACK1 ð
ï STX, data, EBT
ACK0 ð
End of data transfer EOT
3. Service procedures
CS DTE
No acknowledgement after
setting up the connection 1, ENQ ð
---
After negative or no
acknowledgement, the transmitting
side can stop transfer with EOT
or start an appropriate repeat procedure
EOT ð
or repeat 3 times
1 ENQ three times 1 ENQ ð
---
No acknowledgement after
three repeats. Stop with EOT ð
EOT (error statement).
On setting up the connection

NAK – acknowledgement 1, ENQ ð
ï NAK
Discontinue the connection EOT ð
or
repeat three times 3 times ð
1, ENQ
ï NAK
After three times repeat NAK

acknowledgement interrupt with
EOT (error statement) EOT ð
Cs DTE
Acknowledgement NAK after

EBT or EXT 1, ENQ ð
ï ACK0
STX, data, ETB ð
ï NAK
Last data block is repeated

three times. If 3 times ð
STX, data, ETB
third repetition negative, ï NAK
then send EOT EOT ð
(error statement)
no acknowledgement after
ETB or ETX 1, ENQ ð
ï ACK0
STX, data, ETB ð
Status enquiry with ENQ ð

Cs DTE
No acknowledgement to
enquiry with ENQ ENQ ð
--
After n times repetition of

ENQ no acknowledgement n times ð
ENQ
---
Interruption with EOT EOT ð
(error statement)
Acknowledgement NAK to ENQ ð

enquiry with ENQ ï NAK
Last data block is repeated.

STX, data, ETB ð
ï ACK (0/1)
EOT ð
Cs DTE
Incorrect acknowledgement to
status enquiry ENQ 1, ENQ ð
ï ACK0
STX, data, ETB ð
---
ENQ ð
ACK0 at this point ï ACK0
means that the last data block
has not been understood.
Repeat last data block. STX, data, ETB ð
Correct acknowledgement of
status enquiry ENQ 1, ENQ ð
ACK0
STX, data, ETB ð
ENQ ð
ACK1 at this point ï ACK1
means that the previous data block
has been understood.
Send next data block. STX, data, ETX ð
4. Positive acknowledgement WAIT

(DTE3/15)
Is not used!!!
Message from the receiving side Cs DTE

to the transmitting side to 1, ENQ ð
wait with further transmission of ï ACK0
data for a programmable period y. STX, data, ETB ð
ï WAIT
The number of further

status enquiries ENQ ENQ ð
is determined by a programmable ï WAIT
counter ”z”.
If the last ENQ enquiry ENQ ð
is also answered with WAIT, ï WAIT
the connection is discontinued EOT ð
with EOT.
If, for example, ACK1 is given ENQ ð

in response to an ENQ, ï ACK1
the counters y and z are set to zero.
The transfer is continued STX, data, ETB ð

with the next block.
5. Format of the data block
0 1 0 0 0 0 0 1 STX
1. character
2.
3.
Information field
n. characters
1 1 0 0 0 0 0 0 ETB or ETX
x x x x x x x y BCC block test characters
20 26 P
Character format in accordance with DIN 66003/A and 66022/1
6. Character format
even parity
!
b1 b2 b3 b4 b5 b6 b7 b8 mark, space
<------------------ 8 bit information ------------->
<-- start bit stop bits --> 1 or 2
<-------------------------------- max. 11 bit -------------------------------->
b1 = bit with lowest valency
7. Time monitoring
7.1 Response monitoring: A (refer to DIN 66019/.1.1)
The control station/4 (main control station) starts the time A after polling or
selecting (..., ENQ) to monitor a valid reply.
A transmitting station (CS or DTE after starting polling by polling) starts time A
after transmission of a transfer character sequence (.... ETB, block test character
or. ..., ETX, block test character) to monitor a valid reply.
Time A is reset by receiving a valid acknowledgement:
Polling by control station: STX ... or EOT
Selecting by control station: ACK0 or NAK
Transfer character sequence by transmitting station

a. ACK0 or ACK1
b. NAK
c. WAIT
7.2 Receive monitoring: B (refer to DIN 66019/ 7.1.2)
The receiving station (control station after polling or DTE after selecting) starts
time B at the beginning of a transfer character sequence (STX, ...), in order to
monitor the end of the sequence.
Time B is reset by receiving a valid end of a transfer character sequence:

a. ... ETB, block test character
b. ... ETX, block test character
At the end of B the receipt of ENQ or EOT is synchronised.
7.3 Monitoring operation of dedicated lines: D (refer to DIN 66019/.1.4)
The control station starts the time D after an accepted poll in order to monitor
the transmission authorisation return (absence of EOT).
Time D is reset and restarted by control receipt of transfer character sequences,

acknowledgements, ENQ and EOT.
7.4 WAIT control time F
The transmitting station starts the time F upon receiving the acknowledgement
WAIT in order to make a status enquiry once F has expired.
7.5 Polling control time G ( = 0, or unused)
The control station starts the time G once the poll has been rejected in order to
repeat polling once G has expired.
7.6 Selecting control time H ( = 0, or unused)
The control station as transmitting station starts the time H when selecting has
been rejected in order to repeat selecting after expiry of H.
8. Repeat counters
Z1: control station
- counts repetitions of polls without valid acknowledgement

- is reset upon valid acknowledgement (STX, .. or EOT),
- maximum value Z1MAX until error statement
Z2: Control station as transmitting station
- counts repetitions of selecting without valid acknowledgement

- is reset upon valid acknowledgement (ACK0, NAK),
- maximum value Z2MAX until error statement.
Z3: Transmitting station
- counts repetitions of status enquiries in the absence of a valid response,

- is reset upon valid acknowledgements (ACK0 or ACK1, NAK, WAIT)
- maximal value Z3MAX until error statement.
- counts repetitions of WAIT responses to status enquiry ENQ,

- is reset by positive valid acknowledgement (ACK0 or ACK1),
- counts send repetitions of transfer character sequences following negative

replies NAK,
- is reset by a valid positive response (ACK0 or ACK1, WAIT),
Z6: Control station
- counts repetitions of polls which are rejected with EOT,

- is reset by adoption of transmission authorisation (STX, ...),
- maximum value Z6MAX until error statement
Z7: Control station
- counts repetitions of selections which are rejected with NAK.

- is reset by positive response ACK0,
9. Restoration of exception conditions
9.1 Restoration W1 and W2 (s. DIN 66019/7.3.1)
If there is no valid onward routing (no STX ... or no EOT received in time A),
following polling by the control station, then
W1a: the control station
- will repeat polling by sending EOT to synchronise the station to be

addressed
or alternatively
- will poll a different station after sending EOT and repeat the polling later
on.
W2:
Each polling repetition for a specific station without valid onward routing is
counted with Z1 and an error statement generated once Z1MAX has been
achieved.
W1b:
The control station supervises the return of the send permission after polling
with the operating monitor D. When the time D has expired, EOT is sent and an
error statement generated. Transmitting stations which are not control stations
must accept EOT in their response expectation phase and then forego their send
permission.
Zentrale Sendestation
als
Leitstation und Empfangsstation (aufgerufene

Station)
A starten Sendeaufruf
A löschen STX, ..., ETB
D starten
D starten
ACK0
D starten
STX, ..., ETX
D starten ACK1
D abgelaufen
9.2 Restoring W3 and W4 (refer to DIN 66019/7.3.2)
9.2.1 Selection
W3:
Should no valid acknowledgement (no ACK0 or NAK) be received following a

selecting process by the control station by the time the response monitor A has
expired, then the control station
- will repeat the polling by sending EOT to synchronise the station to be

addressed, or alternatively
- address another station after transmitting EOT and repeat polling later on.
W4:
Every selection repetition for a specific station without valid acknowledgement

is counted with Z2 and an error statement generated once Z2MAX has been
reached.
9.2.2 Information message
W3:
If no valid acknowledgement (i.e. none of the characters ACK0 or ACK1, NAK,

WAIT or EOT 1*) is received in response to the transmission of an information
message by the time the response monitor A expires, the transmitting station
requests a message with a status enquiry ENQ.
W4:
Every repetition of the status enquiry without valid acknowledgement is counted

with Z3 and once Z3MAX has been reached, the send permission is returned by
sending EOT and an error statement generated.
*1)
If the transmitting station is not a control station, EOT may be received after
expiry of the operating monitor in the control station.
Sendestation Empfangsstation
Prozedurphase: Prozedurphase:
Textaufbereitung Texterwartung
STX B starten
Text senden Textkontrolle

A starten ETX B rücksetzen
Antwort- Antwortbildung
überwachung
A rück- ACK
setzen
Textbildung Texterwartung
STX B starten
Text senden Textkontrolle
A starten ETX
Antwort-
überwachung
A abgelaufen ENQ
Antwortüberwachung Antwortbildung
eingestellte Richtungen
an den Schnittstellen
Halpduplex:
Beispiel zu WB: Keine Antwort auf

Übertragungszeichenfolge
10. Relative time spans of monitoring
10.1 Monitor A
Once the response monitor in the transmitting station has expired, either a status
enquiry ENQ or EOT is transmitted. In order to provide a synchronised state in
the receiving station in expectation of ENQ or EOT, the response monitor A
must expire later than the receive monitor B which must always bring about this
state.
10.2 Monitor B
Since the receive monitoring is intended to monitor the end of the reception of
an information message, the time span of B must be longer than the span of the
longest message block to be expected The agreement of a maximum number of
characters N for information messages has the following significance for B:
B = N * Bd/n + S
N = max. number of characters to be expected in an information
message
Bd = baud rate
n = bits per character:
n = 11 for interface suggestion
S = safety margin for delays in message
Since B is certainly to be kept constant, even with changing message lengths,

and A is to expire later than B, then
A must be > B
10.3 Monitor D
Since the operating monitor D must permit a delayed acknowledgement to a

transmission, the time span of D must be longer than that of A. The upper limit
determines the time which the transmitting station can use to prepare a new
transmission after a transmission:
D>A>B
*1 WAIT 8DLE 3/15) can only be sent by the received (CS or DTE), if (STX ---
ETB/ETX, BCC/BCS) has been received and BCCBCS check is okay but no
*2 After receipt of (STX --- ETB/ETX, BCC/BCS) and check of BCC/BCS.
*3 In order to maintain a clear synchronisation, synchronisation only to EOT with

error statement to the program ”Dialog incomprehensible” is the simplest and
most reliable way of restructuring dialog once unexpected characters have been
received. Every repetition of 1, ENQ or 0, ENQ by the control station Z is
started with EOT in front.
*4 Incorrect acknowledgement number as a direct response to a text communication

is a serious error. Under the assumption that a distortion on the line from ACK0
– ACK1 or vice versa is relatively improbable without parity error, this dialog
should be discontinued by sending EOT and the communication viewed as not
transferred correctly.
Multipoint
Serial interface
- Polling/selecting procedure
- everyone with everyone
Control station (only in the sense of creating a connection)
ð polls all stations with polling procedure

EOT, address (max. 2 positions) ENQ
last position, b1 = 0
ï
a) Rejection: EOT definable as: "no desire to poll"
b) Acceptance: Sending of a "selecting process"

Address (max. 2 positions) ENQ
last position, b1 = 1
É
a) Rejection: NAK definable as: "cannot receive"
ò b) Acceptance: ACK0
ò --> Data transmission
Ä END: Return to control station
ï EOT
De-central transmission to serial Multipoint
1 2 3
L
A text or piece of information is in 1 which is to be transported to 3.
- If a polling is addressed to 1 by L, the former accepts this by addressing a selection to 3.
- Once the procedure has been completed in 3 the next point of call for the
acknowledgement packet can be found from the packet head by the identification of the
sender and the Multipoint receiver address, in this case 1.
- If 3 is addressed by polling, 3 addresses 1 by means of selection and sends the response

packet.
Polling / selection phase
A. Dialog on a Multipoint connection
Cs DTE
... EOT, a1, a0, ð polling only
ENQ
ï a1, a0, ENQ selection only
ACK 0 ð
a1, a0 contain the address and the polling or selection.
bit b1 to b7 from a1 and

bit b2 to b7 from a0 correspond to the address.
bit b1 from a0 correspond to 0 = polling

1 = selection
b1 is a low-order bit !
Restriction: a1, a0 ∑ ("a" - "z") and ("0" - "9"), since transferable in system
head.
N.B.:
The DTEs should recognise independently whether they are connected to a Multipoint
connection or a point-to-point connection.
DTE to Multipoint
... EOT, a1, a0, ENQ ð

ï a1, a0, ENQ
ACK 0 ð
DTE to Point to Point
... EOT, 0, ENQ ð

ï STX
ACK 0 ð
Dialog structure – dialog head – filling pump control
Dialog head for all V11 dialogs
Dialog name D no. Direction PS channel number

Designation of the dialog xxxx from to
Fn Name Flg Pos Type Designation Data
1 FLPSS 4 -4 ASC PACKET SWITCH
2 FLDN 4 0 ASC DIALOG NUMBER xxxx *A
3 FLGK 2 4 ASC DEVICE IDENTIFICATION xx *B
4 FLGN 2 6 ASC DEVICE NUMBER xx *C
5 FLGM 2 8 ASC DEVICE MODE xx *D
*A) Dialog number

Four-digit number for dialog identification
*B) Device identification

describes, for example, the pump computer type:
'ZC' computer T10/3
'ZD' computer T10/8
After activation the T10/8 appears in status dialog (9) with the device identification
ZD. If the control informs the T10/8 of the device identification ZC in dialog 9998 and
9997, the T10/8 operates in the same way as a T10/3.
*C) Device number

Internally assigned number to identify the pump computer. Is assigned in dialog
[9997] and alters depending on differences in totals during dialog [9999].
*D) Device mode

This two-digit term refers to a sub-function in the device (freely programmable in the
device) or can be initialised via dialog [9999].
Initialisation of Cs and DTE
After activation the control station (Cs) sends a recognition status dialog to the
connected DTEs.
Dialog no. 0000

Cs DTE
1 ENQ ð
ï ACK 0
STX ð
0000
00
00
00
ETX
ï ACK 1
EOT ð
The DTE answers this dialog at the next polling.
Cs DTE
0 ENQ ð
ï STX
0000
x1-x2 a)
x3-x4 b)
x5-x6 c)
x1-xn d)
ETX
ACK 0 ð
ï EOT
a) Device identification
x1-x2 is a fixed programmable value. (Agreement with S & B necessary)
b) Device number
x3-x4 is a value which can be programmed in the DTE.
If this value is equal to oo, a value can be loaded via dialog 9999. This value
must then be stored in the DTE and sent with each response.
c) Device mode
x5-x6 is a value which can be programmed in the DTE (in the same way as b).
d) Status
x1-xn provides the current status of the DTEs. (Agreement with S & B
necessary).
Cs = control station , DTE = data terminal equipment
If the values of a), b) and c) in the response dialog no. 0000 are unequal to 00 and
comply with the agreement, this recognition and status information is filed in the Cs
for the appropriate line.
If the values of b), c) are equal to 00, the DTE is loaded at these positions via the
initialisation dialog 9999 and thus defined.
Cs DTE
1 ENQ ð
ï ACK 0
STX ð
9999
x1-x2
x3-x4
x5-x6
ETX
ï ACK 1
EOT ð
Commissioning procedure (example 1)

Cs DTE
1 ENQ ð
ï ACK 0
STX ð
0000
00
00
00
ETX
ï ACK 1
EOT ð
Response of the DTEs

Cs DTE
0 ENQ ð
ï STX
0000
K4 e.g. cash register type 4
01 e.g. cash register no. 1
02 e.g. mode 2
x1-xn status
ETX
ACK 0 ð
ï EOT
No dialog 9999 necessary, since DTE clearly defined!
(Example 2)
Cs DTE
1 ENQ ð
ï ACK 0
STX ð
0000
00
00
00
ETX
ï ACK 1
EOT ð
Response of the DTEs

Cs DTE
0 ENQ ð
ï STX
0000
K4 e.g. cash register type 4
00
00
x1-xn status
ETX
ACK 0 ð
ï EOT
Dialog 9999 necessary.
Cs DTE
1 ENQ ð
ï ACK 0
STX ð
9999
K4
02 e.g. cash register no. 2
01 e.g. mode 1
ETX
ï ACK 1
EOT ð
The DTE accepts the values and responds as from this point with this definition,
e.g. send recognition status
Cs DTE
1 ENQ ð
ï ACK 0
STX ð
0000
K4
02
01
ETX
ï ACK 1
EOT ð
0 ENQ ð
ï STX
0000
K4
02
01
x1-xn status
ETX
ACK 0 ð
ï EOT
Definition time A
Cs DTE
0 ENQ ð
ï STX
Data 1
ETB start
time A = 3 sec.
ACK 0 ð EOT stop
ï STX
Data 2
start
time A = 3 sec.
ï ENQ stop
ACK 0 ð
Definition time B
Cs DTE
1 ENQ ð
ï ACK 0
STX ð start
Data 1 time B = 500 ms
ETB stop
ï ACK 1
ßßßßß
STX ð Start
Data 2 Time B = 500 ms
Stop
ENQ ð
ï ACK 1
ßßßßß
STX ð
Data 2
ETB
ï ACK 0
Description of the PS layer
1. General remarks
The Packet Switch Service (PSS) provides up to 256 logical channels on one physical channel.
PSS is the transport system for data from the transmitter (S) via a logical channel (K) to the receiver
(E).
The data transport can be directed via several other devices (equipped with a bypass channel).
The data are then merely directed from one physical to another physical channel within this device
whereby the channel number is converted.
This creates a virtual link between transmitter and receiver.
The following shows this data exchange via three logical channels.
A C E
B D F
Physical channels
Logical connections
A C
B E
D F
Fig. 1 Virtual connection via 3 logical channels
The protocol of the Packet Switch Service distinguishes between three types of packet.
• U packets control packets without sequence number

(U = unnumbered)
are used to reset a logical channel on the packet

level or its acknowledgement.
• I packets data packet (I = Information)
contain, in addition to control information of the packet

level (level 3), the actual useful data of level 7
(dialog packets).
Since the dialog packets are relatively short,

they are not divided into smaller blocks by the
PSS as in the X.25 protocol, but are transferred
as a whole in one I packet.
• S packets control packets with sequence number (S = supervisory)
are used for control tasks as well as for sequence

supervision of the data packets.
The following overview provides an idea of the different Packet Switch Service (PSS) packet types:
Packet Designation Function

U packet Reset with poll flag Request to the receiver to reset the logical channel.
Wait for reset acknowledgement.
Reset without poll flag Request to the receiver to reset the logical channel.
Wait for reset acknowledgement or reset.
Reset Acknowledgement on one channel reset.
acknowledgement
I Packet Data packet Sending of level 7 data (dialog packets).
Each I packet contains a receive sequence number N (R) and a transmission sequence
number N(S) in addition to data.
S packet Receiver Ready Command shows that the transmitter of this packet is
ready to receive.
Receiver not Ready Command shows that the transmitter of this packet is
not ready to receive.
Reject Response to an I packet if the I packet was not
accepted. The transmitter then repeats all I packets
as from the receive sequence number N (R).
An S packet contains a receive sequence number N (R).
2. Sequence check by means of sequence numbers
The following provides general information on communication on the sequence-checked

packet level.
Two packet counters are used for the sequence check of the I packets. The transmitter
sequence counter V (S) and the receive sequence counter V (R). Both counters are set
to zero for every channel reset. They can accept values from zero to a maximum value
ZMAX. This value is generally described as window size.
The window size specifies the number of I packets which may be sent via this channel
without requiring a confirmation from the receiver. If the counter reaches the maximum
value it is automatically set to zero (ring counter).
In the case of the Packet Switch Service (PSS) the window size is adjustable in the
range between 1 to 7 (3-bit sequence counter).
The receiver sequence number of S and I packets specifies which following I packet is
expected by the other side. At the same time all I packets are acknowledged as having
been correctly received up to receive number ”N (R)-1” .
Before transmitting the receive sequence number this is synchronised with the receiver
sequence counter of the transmitter.
The following provides information on the S packet types.
2.1 Receiver not ready
The S packet "Receiver not ready" is sent by a PS communication partner who is not
directly ready to accept I packets.
This may be the case in the absence of a buffer for storage purposes.
2.2 Receiver ready
The S packet "Receiver Ready" is used in order
• to display readiness to receive an I packet;
• to acknowledge previous I packets (up to and including the

sequence number N(R)-1) if the confirmation cannot be transmitted
with another I packet;
• to end a period of non-readiness which was introduced with the S

packet "Receiver not Ready".
2.3 Reject
The S packet "Reject" demands the repetition of I packets starting with the sequence
number N(R) after receiving an I packet with incorrect sequence number. All I packets
with sequence numbers up to and including N(R)-1 are confirmed as received.
I packets are transmitted with a transmission sequence number N(S) as well as with a
receive sequence number N(R). N(S) must agree with the transmission sequence
counter of the transmitter V(S), and N(R) with the receive sequence counter of the
transmitter V(R).
After sending the I packet, the transmitter increases its transmission sequence counter
V(S) by 1. The transmitter can send a maximum ZMAX I packets without
acknowledgement from the receiver. After that he must wait until I packets are
acknowledged. Only then can further I packets be sent.
The receive sequence counter specifies the sequence number of the next I packet
received. V(R) is then increased by 1 if an I packet has been received free from error
and in the correct sequence. The sequence will be correct if N(S) of the received I
packet agrees with V(R) of the receiver.
If an I packet is received whose transmission sequence number N(S) does not agree
with the current value of the receive sequence counter V(R), then neither this nor
subsequent I packets may be accepted (no increase in the receive sequence counter
V(R) ), until the I packet has been received with the correct sequence number.
In this case an S packet "Reject" with the receive sequence number N(E) = V(E) is
returned in order to request the partner to repeat the I packets as from this sequence
number.
3. Time monitoring
Communication on the packet level is monitored by three different timers per logical
canal. These are:
• an input timer
• an output timer
• an idle timer
3.1 Input timer
The input timer is restarted for every valid receipt of an S, U or I packet to monitor the
respective logical channel. Once the input timer has expired (30 seconds), the PSS
sends a U packet (reset with poll flag) and expects a reset acknowledgement.
3.2 Output timer
The output timer is restarted each time an I packet is sent. It monitors the
acknowledgement for sent I packets within a finite period of time (15 seconds).
After acknowledgement of a sent I packet, the timer is similarly restarted. After the
output time has run out, all I packets which have not yet been acknowledged are
repeated for a maximum of twice.
A U-Packet (reset with poll flag) is then sent to reset the logical channel. This occurs
every 15 seconds until an acknowledgement is received ("reset acknowledgement").
3.3 Idle timer
The idle timer is restarted each time an I-, U-, or S packet is sent. It serves to monitor
the line and is the counterpart to the input timer.
Once the time runs out, i.e. if nothing has been sent for 20 seconds, the PSS
automatically sends an S packet ("receiver ready" or "receiver not ready").
This ensures that an S packet is sent every 20 seconds for line monitoring, although no
I packets run through the lines. This means that the input timer cannot respond. This
also means that the time for the input timer must be larger than that for the idle timers.
4. Status diagram on packet level
The packet level can be shown in a status diagram.
A distinction can be made between the following statuses:
4.1 Initialisation status (Z 1)
This status is assumed after switching on.
4.2 Channel reset sent (Z 2)
This status is assumed after requesting the receiver to perform a channel reset. The
system remains in this status until such time as a U-Packet "reset" or "reset
acknowledgement" has been received.
4.3 Ready to receive and transmission permitted (Z 3)
This is the "normal" status of the packet level.
4.4 Receive locked and transmission permitted (Z 4)
This status can only be assumed by the internal event "no memory available for
input buffer" based on the status "ready" (Z3). If sufficient memory is available again,
the system returns to status Z3.
4.5 Receive permitted and transmission blocked (Z 5)
If a communication partner receives an S packet "receiver not ready", the other

partner is not able at that moment to receive packets. A change is made to the status
”output locked” so that no further packets are sent to this partner.
4.6 Receive and transmission locked (Z 6)
This status can only be assumed from "output locked" (Z5) by the internal event "no
memory available for input buffer". Once sufficient memory is available again, the
system reverts to the original status Z5.
The following diagram shows the complete status diagram for the packet level.
State of the receiver (PS level)

Z1 Z2 Z3 Z4 Z5 Z6
Nothing Reset sent Ready to re- Reception Ready to receive Reception and
yet sent ceive, transm. locked,transm. Transm. Transm.
permitted permitted locked locked
permitte
Reset without Send reset Send reset Send reset Send reset Send reset
poll flag acknowled. acknowled. acknowled. acknowled. acknowled.
Z3 Z3 Z3 Z3 Z3 Z3
Reset with Send reset Send reset Send reset Send reset Send reset Send reset
poll flag acknowled. acknowled. acknowled. acknowled acknowled. acknowled.
Z3 Z3 Z3 Z3 Z3 Z3
Reset
acknowled. Ignore Ignore Ignore Ignore Ignore
ment
Z1 Z3 Z3 Z4 Z5 Z6
Receiver Ignore Ignore Ignore Ignore

Ready
Z1 Z2 Z3 Z4 Z3 Z4
Receiver Ignore Ignore Ignore Ignore

not Ready
Z1 Z2 Z5 Z6 Z5 Z6
Reject Ignore Ignore Repeat Repeat Repeat Repeat

output output output output
Z1 Z2 Z3 Z4 Z3 Z4
Send Send
Data packet Ignore Ignore acknowled. or Ignore acknowled. or Ignore
reject reject
Z1 Z2 Z3 Z4 Z5 Z6
Fig. 2 Status diagram packet level
The following figure shows by way of example a section from a communication between two partners
on the packet level. Window size equals 2.
PS communication PS communication
partner 1 (P1) partner 2 (P2)
Reset with P flag
P2 wishes to reset log. channel
: (repeat if output time runs out

until acknowledgement has been) given
Reset with P flag :
Reset acknowledgement
set V(S) =V(R) =0 set V(S) =V(R) =0
I(S=0, R=0) P2 sends data to P1
P1 replies. I(S=0, R=1)

max. number unconfirmed packets
reached. (Output timer running) I(S=1, R=1)
Both packets have been correctly
I(S=1, R=2) received and are confirmed.
I(S=2, R=2)
Since no I packet waiting to be sent,
an S packet confirms. RR(R=0)
I(S=0, R=2) This packet is not received by P1

owing to a transfer error.
I(S=1, R=2)
Rejection ! I packet with N(s)=0 is REJ(R=0)

expected.
I(S=0, R=2)
Repeat as from N(S)=0
I(S=1, R=2)
I(S=2, R=2)
Confirmation for both packets
Currently no data exchange. RR(R=2)

Monitored by idle time.
The idle timer runs also
RR(R=0) for P2.
:
: RR(R=2)
RR(R=0)
I(S=0,
R=2)
RNR(R=1) Buffer bottleneck in P2
and simultaneous acknowledgement
I(S=2, of I packet. P2 is not ready to
R=1) receive but can continue to transmit
Not confirmed by an I
packet owing to buffer bottle RR(R=0) .
neck in P2
RR(R=1) P2 is ready to receive again
Now a further I packet I(S=1,

can be sent since P2 R=0)
is ready to receive again. RR(R=2) Confirmation
:
:
Fig. 3 Communication on packet level (window size = 2)
Following the description of the sequence control mechanisms on the packet level, below are
the variations realised for communication between the devices in the filling station system.
Since the PSS must always intermediately store the last ZMAX I packets for any repetition
request, a window size of ZMAX = 1 is always used for communication between the devices
in the filling station system.
The sequence numbers must always be 0 or 1. This means that acknowledgement must be
given after every sent I packet since only a maximum of one packet may remain
unacknowledged.
The following diagram shows by way of example the section for communication at packet level for the
conditions valid in the following of ZMAX = 1.
PS Communication PS Communication
partner 1 (P1) partner 2 (P2)
Reset with P flag
P2 wishes to reset logical channel
: (repeat if output timer runs out before
acknowledgement has been made)
Reset with P flag :
Reset acknowledgement
set V(S) =V(R) =0 set V(S) =V(R) =0
I(S=0, R=0) P2 sends data to P1

P1 responds with 1 packet. I(S=0, R=1)
Since window=1, the acknow-
ledgement must first be given before the RR(R=1) Acknowledgement by S packet
second packet is sent.
I(S=1, R=1)
RR(R=0) Acknowledgement by S packet
I(S=1, R=0) This packet is not received at P1

owing to a transfer error.
Repetition after the idle timer

I(S=1, R=2) has run out.
RR(R=0)
Acknowledgement by S packet
Currently no data exchange. RR(R=0)

Monitored by idle timer.
The idle timer also runs out
RR(R=0) at P2.
:
: RR(R=0)
RR(R=0)
I(S=0, R=0)
Buffer bottleneck at P1 and
simultaneous acknowledgement of the RNR(R=1)
I packet.
RR(R=1)
P1 ready to receive again.
I(S=1, R=0)
Now a further I packet can be sent
since the P1 is ready to receive again.
Confirmation
:
:
Fig. 4 Section ”Communication on the packet level (window size = 1)”
5. Structure of the U, I and S packets with code-linked transfer

The following shows the detailed structure of the different packet types.
5.1 Structure of the U packets
Packet type Function

U packet Reset with poll flag
No. Field Length Pos. Designation Type Data
1 FLPSKN 2 0 Channel number ASC X1,X2 *1
2 FLPSFC 2 2 Function code ASC ?<
3 FLPSS 2 4 PS status ASC X1,X2 *2

U-Packet Reset without poll flag
2 FLPSFC 2 2 Function code ASC ?4

U packet Reset acknowledgement
2 FLPSFC 2 2 Function code ASC <6
*1 The hexadecimal channel number (00H-FFH)

is converted to printable ASCII characters.
X1 = High-order half byte + 30H

X2 = Low-order half byte + 30H
*2 X1 = '0': Reset from own channel

X1 = '1': Reset from partner channel
X2 = '0': Logical channel reset

X2 = '1': Channel not functioning
X2 = '2': No connection to partner (time out)
X2 = '3': Max. number of repetitions reached
X2 = '4': two directly consecutive rejects on reject
X2 = '5': unknown command
X2 = '6': unexpected reset acknowledgement
5.2 Structure of I packets

I packet Data packet
2 FLPSSN 1 2 Transmission sequence ASC X *3
number
3 FLPSEN 1 3 Receive sequence no. ASC X *3
4 - n 4 Dialog packet - *4
*3 Since in this example the window size is equal to 1, the values can only
vary between 0 and 1.
*4 The dialog packet (with the dialog number) of the application level
starts here. The length depends on the respective dialog packet.
5.3 Structure of S packets

S packet Control packet
No. Field Length Pos Designation Type Data
2 FLPSSB 1 2 Control byte ASC X *5
3 FLPEN 1 3 Receive sequence no. ASC X *3
*5 The control byte specifies the function of the control packet.

The following values are possible:
'8': "Receiver ready"

'9': "Reject"
'A': "Receiver not ready"
*3 Since in this case the window size is equal to 1, the numbers

can only ever be values between ‘0’ and ‘1’.
6. Structure of U, I and S packets of code-independent transfer
The structure of the dialog packets is slightly different in this case from that of a code-
dependent transfer. These are described in detail in the following.
6.1. Structure of U packets

U packet Reset with poll flag
1 FLPSKN 1 0 Channel number BIN X *6
2 FLPSSC 1 1 Sequence Control Byte BIN FCH
(U packets)
3 FLPSS 1 2 PS status BIN X *7

U packet Reset without poll flag
2 FLPSSC 1 1 Sequence Control Byte BIN F4H
(U packets)

U packet Reset acknowledgement
2 FLPSSC 1 1 Sequence Control Byte BIN C6H
(U packets)
*6 Channel number 0-FFH
*7 Status byte
D7 : 0 : Reset from own channel

1 : Reset from partner channel
D6-D0 : 0000000 logical channel reset

0000001 Channel not functioning
0000010 No connection to partner (time out)
0000011 Max. number of repetitions reached
0000100 Two directly consecutive rejects on reject
0000101 unknown command
0000110 unexpected reset acknowledgement
6.2. Structure of the I packets

I packet Data packet
2 FLPSSC 1 1 Sequence Control Byte BIN X *8
(I packets)
3 - n 2 Dialog packet - *4
*8 Sequence Control Byte for data packets
D7 D6 D5 D4 D3 D2 D1 D0
0 X X X 0 Y Y Y
XXX 000 - 111 Transmission sequence number

YYY 000 - 111 Receive sequence number
6.3 Structure of S packets

S packet Control packet
2 FLPSSC 1 1 Sequence Control Byte BIN X *9
(S packets)
*9 Sequence Control Byte for control packets
D7 D6 D5 D4 D3 D2 D1 D0
1 0 X X 0 Y Y Y
XX : 00 Receiver ready
10 Receiver not ready
01 Reject
YYY 000 - 111 Receive sequence number

бахман

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

бахман

Uploaded by

Copyright:

Available Formats

Scheidt & Bachmann GmbH Technical Documentation

D-41238 Mönchengladbach Breitestraße 132 Standardised V11 Procedure 85 63506 ( )

Documentation for standardised

V11 Point to Point

Interface according to DIN 66258 and 66019

The interface is based on the following criteria:

0, ENQ Station enquiry / send

STX Start of text

ACK1 Positive acknowledgement DLE 3/1

1. Send procedure from control station to DTE

Example 1: one data block

Example 2: several data blocks

Data transfer of several

2. Receive procedure of control station to DTE

Example 1: one data block

Example 2: several data blocks

On setting up the connection

After three times repeat NAK

Acknowledgement NAK after

Last data block is repeated

Status enquiry with ENQ ð

After n times repetition of

Acknowledgement NAK to ENQ ð

Last data block is repeated.

Send next data block. STX, data, ETX ð

4. Positive acknowledgement WAIT

Message from the receiving side Cs DTE

The number of further

If, for example, ACK1 is given ENQ ð

The transfer is continued STX, data, ETB ð

5. Format of the data block

Character format in accordance with DIN 66003/A and 66022/1

<------------------ 8 bit information ------------->

<-- start bit stop bits --> 1 or 2

<-------------------------------- max. 11 bit -------------------------------->

b1 = bit with lowest valency

7.1 Response monitoring: A (refer to DIN 66019/.1.1)

Time A is reset by receiving a valid acknowledgement:

Polling by control station: STX ... or EOT

Selecting by control station: ACK0 or NAK

Transfer character sequence by transmitting station

7.2 Receive monitoring: B (refer to DIN 66019/ 7.1.2)

Time B is reset by receiving a valid end of a transfer character sequence:

At the end of B the receipt of ENQ or EOT is synchronised.

7.3 Monitoring operation of dedicated lines: D (refer to DIN 66019/.1.4)

Time D is reset and restarted by control receipt of transfer character sequences,

7.4 WAIT control time F

7.5 Polling control time G ( = 0, or unused)

7.6 Selecting control time H ( = 0, or unused)

Z1: control station

- counts repetitions of polls without valid acknowledgement

Z2: Control station as transmitting station

- counts repetitions of selecting without valid acknowledgement

Z3: Transmitting station

- counts repetitions of status enquiries in the absence of a valid response,

Z4: Transmitting station

- counts repetitions of WAIT responses to status enquiry ENQ,

Z5: Transmitting station

- counts send repetitions of transfer character sequences following negative

Z6: Control station

- counts repetitions of polls which are rejected with EOT,

Z7: Control station

- counts repetitions of selections which are rejected with NAK.

9. Restoration of exception conditions