SIST EN 15969-1:2022
(Main)Tanks for transport of dangerous goods - Digital interface for the data transfer between tank vehicle and with stationary facilities - Part 1: Protocol specification - Control, measurement and event data
Tanks for transport of dangerous goods - Digital interface for the data transfer between tank vehicle and with stationary facilities - Part 1: Protocol specification - Control, measurement and event data
This document specifies data protocols and data format for the communication between electronic
equipment (TVE), on-board computer (OBC) of the tank vehicle and stationary equipment.
This document specifies the basic protocol FTL used in the communication (basic protocol layer), the
format and structure of FTL-data to be transmitted (data protocol layer) and describes the content of the
FTL-data.
This data protocol can be used for other application e.g. between stationary tank equipment and offices.
Tanks für die Beförderung gefährlicher Güter - Digitale Schnittstelle für den Datenaustausch zwischen Tankfahrzeugen und stationären Einrichtungen - Teil 1: Protokollspezifikation - Steuerungs-, Mess- und Ereignisdaten
Dieses Dokument legt Datenprotokolle und formate für die Kommunikation zwischen elektronischen Einrichtungen (TVE), Bordcomputer (OBC) des Tankfahrzeugs und stationären Einrichtungen fest.
Dieses Dokument legt das für die Kommunikation verwendete Basisprotokoll FTL (basic protocol layer) sowie die Formate und die Struktur der übertragenen FTL Daten (data protocol layer) fest und beschreibt die Inhalte der FTL Daten.
Dieses Datenprotokoll kann auch für andere Anwendungen, z. B. zwischen stationären Tankeinrichtungen und Büros, verwendet werden.
Citernes destinées au transport de matières dangereuses - Interface numérique pour le transfert de données entre des véhicules-citernes et des installations fixes - Partie 1 : Spécifications du protocole - Contrôle, données de mesure et d’événements
This European Standard specifies data protocols and data format for the interfaces between electronic equipment (TVE), on-board computer (OBC) of the tank vehicle and stationary equipment for all interconnecting communication paths.
This European Standard specifies the basic protocol FTL used in the communication (basic protocol layer), the format and structure of FTL-data to be transmitted (data protocol layer) and describes the content of the FTL-data.
This data protocol may be used for other application e.g. between stationary tank equipment and offices.
Cisterne za prevoz nevarnega blaga - Digitalni vmesnik za prenos podatkov med cisterno in stacionarnimi napravami - 1. del: Opredelitev protokola - Upravljanje, merjenje in zajem podatkov
General Information
Relations
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 15969-1:2022
01-december-2022
Nadomešča:
SIST EN 15969-1:2018
Cisterne za prevoz nevarnega blaga - Digitalni vmesnik za prenos podatkov med
cisterno in stacionarnimi napravami - 1. del: Opredelitev protokola - Upravljanje,
merjenje in zajem podatkov
Tanks for transport of dangerous goods - Digital interface for the data transfer between
tank vehicle and with stationary facilities - Part 1: Protocol specification - Control,
measurement and event data
Tanks für die Beförderung gefährlicher Güter - Digitale Schnittstelle für den
Datenaustausch zwischen Tankfahrzeugen und stationären Einrichtungen - Teil 1:
Protokollspezifikation - Steuerungs-, Mess- und Ereignisdaten
Citernes destinées au transport de matières dangereuses - Interface numérique pour le
transfert de données entre des véhicules-citernes et des installations fixes - Partie 1 :
Spécifications du protocole - Contrôle, données de mesure et d’événements
Ta slovenski standard je istoveten z: EN 15969-1:2022
ICS:
13.300 Varstvo pred nevarnimi Protection against dangerous
izdelki goods
23.020.10 Nepremične posode in Stationary containers and
rezervoarji tanks
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
SIST EN 15969-1:2022 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 15969-1:2022
---------------------- Page: 2 ----------------------
SIST EN 15969-1:2022
EN 15969-1
EUROPEAN STANDARD
NORME EUROPÉENNE
October 2022
EUROPÄISCHE NORM
ICS 13.300; 23.020.10; 35.240.60 Supersedes EN 15969-1:2017
English Version
Tanks for transport of dangerous goods - Digital interface
for the data transfer between tank vehicle and with
stationary facilities - Part 1: Protocol specification -
Control, measurement and event data
Citernes destinées au transport de matières Tanks für die Beförderung gefährlicher Güter - Digitale
dangereuses - Interface numérique pour le transfert de Schnittstelle für den Datenaustausch zwischen
données entre des véhicules-citernes et des Tankfahrzeugen und stationären Einrichtungen - Teil
installations fixes - Partie 1 : Spécifications du 1: Protokollspezifikation - Steuerungs-, Mess- und
protocole - Contrôle, données de mesure et Ereignisdaten
d'événements
This European Standard was approved by CEN on 19 September 2022.
CEN members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references
concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN
member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC Management
Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2022 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 15969-1:2022 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
SIST EN 15969-1:2022
EN 15969-1:2022 (E)
Contents Page
European foreword . 4
Introduction . 6
1 Scope . 7
2 Normative references . 7
3 Terms and definitions, abbreviations and conventions . 7
3.1 Terms and definitions . 7
3.2 Abbreviations . 9
3.3 Conventions . 9
4 Hardware interface . 10
5 Basic protocol layer . 10
5.1 FTL-frame (frame) . 10
5.2 Frame flow (handshake) . 11
5.3 Delay and timeout . 16
5.4 CRC16 Checksum . 16
6 Data protocol layer (FTL-data protocol) . 16
6.1 Client (OBC) and server (TVE) . 16
6.2 Syntax of data in datagrams . 17
6.3 Nodes, subnodes, variables . 17
6.4 Format identifiers . 17
6.5 Types of variable values . 20
6.6 Kinds of nodes . 21
7 FTL-Data . 22
7.1 General . 22
7.2 Record and field types . 22
7.3 Systemwide variables (subnode SYSTEM) . 23
7.4 Variables related to global positioning system (subnode GPS) . 27
7.5 Accessing a printer on TVE-side (subnode PRN) . 27
7.6 Compartment information (subnode COMP) . 30
7.7 Notification about changes (subnode NOTIFY) . 32
7.8 Information about driver (subnode DRIVER) . 33
7.9 Information about the vehicle (variable VEHICLE_ID) . 34
7.10 Information about current operation (subnode OPERATION) . 34
7.11 Access to filesystem on TVE (subnode FS) . 36
7.12 Auxiliary (subnode AUX) . 41
7.13 Order management (subnode ORDER) . 42
7.14 Goods and service database (subnode PRODUCT) . 46
7.15 FTL—logfile (subnodes LOG) . 49
7.16 Required variables . 81
7.17 NAK ID . 82
8 Routing for multiple TVE . 83
8.1 Purpose . 83
8.2 Routing solution . 83
8.3 Routing example . 84
9 Communication with office . 84
2
---------------------- Page: 4 ----------------------
SIST EN 15969-1:2022
EN 15969-1:2022 (E)
9.1 General . 84
9.2 Simple file transfer . 85
9.3 FTL over TCP/IP . 87
10 Communication Examples . 89
10.1 Examples for Basic Protocol Layer level . 89
10.2 Examples for data protocol layer . 91
Annex A (normative) Node tree . 94
Annex B (normative) Test FTL . 95
B.1 Overview . 95
B.2 Basic Protocol Layer . 95
B.2.1 Frame Tests. 95
B.2.2 CRC-error . 96
B.2.3 Delay and Timeout . 96
B.3 Data Protocol Layer . 96
B.3.1 Test of Toggling . 96
B.3.2 Test of the FTL data layer . 98
B.3.3 Test of the required FTL nodes . 98
B.3.4 Optional System Subnodes . 101
B.3.5 Optional Node Prn . 103
B.3.6 Node Comp . 105
B.4 Application Layer. 111
B.4.1 Test of the L-File . 111
B.4.2 Test of the LH-File . 111
B.4.3 Test for the Filling of the NodeList . 111
B.4.4 Sequence Test . 112
Bibliography . 114
3
---------------------- Page: 5 ----------------------
SIST EN 15969-1:2022
EN 15969-1:2022 (E)
European foreword
This document (EN 15969-1:2022) has been prepared by Technical Committee CEN/TC 296 “Tanks for
the transport of dangerous goods”, the secretariat of which is held by AFNOR.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by April 2023, and conflicting national standards shall be
withdrawn at the latest by April 2023.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document supersedes EN 15969-1:2017.
In comparison with the previous edition, the following technical modifications have been made:
— Figure 11 corrected;
— Subclause 7.3.11 “Trailer coupled (variable TRAILER)” added;
— Subclause 7.5.9 “Duplicate print (DUPLICATE)” added;
— Table 55 “Fields of records of ORDER.PLAN” Index 19 to 21 added;
— In subclause 7.13.4 Value V for planned transaction in process and unplanned transaction in process
added;
— Table 67 “L file record types” in Index L1137 Bit 3 added;
— Table 67 “L file record types” Index L1147 added;
— Table 67 “L file record types” Index L1205 added;
— Table 67 “L file record types” in Index L2002 event codes 80 to > 100 added;
— Table 67 “L file record types” Index L4007 and L4008 added;
— Table 67 “L file record types” in Index L4206 delivery path 25 to 36 and 80 to 86 added;
— Table 67 “L file record types” Index L4207 and L4208 added;
— Table 67 “L file record types” Index 94 Diagnose added;
— Node tree in Figure A.1 revised.
EN 15969, Tanks for transport of dangerous goods — Digital interface for the data transfer between tank
vehicle and with stationary facilities, consists of 2 parts:
— Part 1: Protocol specification — Control, measurement and event data;
— Part 2: Commercial and logistic data.
4
---------------------- Page: 6 ----------------------
SIST EN 15969-1:2022
EN 15969-1:2022 (E)
This document forms part of a coherent standards programme comprising the following standards:
— EN 13616-1, Overfill prevention devices for static tanks for liquid fuels — Part 1: Overfill prevention
devices with closure device;
— EN 13616-2, Overfill prevention devices for static tanks for liquid fuels — Part 2: Overfill prevention
devices without a closure device;
— EN 13922, Tanks for transport of dangerous goods — Service equipment for tanks — Overfill
prevention systems for liquid fuels;
— EN 14116, Tanks for transport of dangerous goods — Digital interface for product recognition devices
for liquid fuels;
— EN 15207, Tanks for the transport of dangerous goods — Plug/socket connection and supply
characteristics for service equipment in hazardous areas with 24 V nominal supply voltage;
— EN 15208, Tanks for transport of dangerous goods — Sealed parcel delivery systems — Working
principles and interface specifications;
— EN 15969-2, Tanks for transport of dangerous goods — Digital interface for the data transfer between
tank vehicle and with stationary facilities — Part 2: Commercial and logistic data.
Any feedback and questions on this document should be directed to the users’ national standards body.
A complete listing of these bodies can be found on the CEN website.
According to the CEN-CENELEC Internal Regulations, the national standards organisations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia,
Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland,
Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of North
Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and the United
Kingdom.
5
---------------------- Page: 7 ----------------------
SIST EN 15969-1:2022
EN 15969-1:2022 (E)
Introduction
FTL is an acronym for Fuel Truck Link, the interface between electronic system(s) on board of a tank
vehicle (tank-vehicle-equipment) and any external computer, e.g. an on-board-computer installed in the
driver’s cabin; for illustration see Figure 1.
Key
→ direction of communication (client → server)
a may be either two independent units or one single unit which incorporates both functions OBC and TVE
Figure 1
6
---------------------- Page: 8 ----------------------
SIST EN 15969-1:2022
EN 15969-1:2022 (E)
1 Scope
This document specifies data protocols and data format for the communication between electronic
equipment (TVE), on-board computer (OBC) of the tank vehicle and stationary equipment.
This document specifies the basic protocol FTL used in the communication (basic protocol layer), the
format and structure of FTL-data to be transmitted (data protocol layer) and describes the content of the
FTL-data.
This data protocol can be used for other application e.g. between stationary tank equipment and offices.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
DIN 51757:2011, Testing of mineral oils and related materials — Determination of density
EN 13616-2, Overfill prevention devices for static tanks for liquid fuels — Part 2: Overfill prevention devices
without a closure device
EN 13922, Tanks for transport of dangerous goods — Service equipment for tanks — Overfill prevention
systems for liquid fuels
EN 14116:2012+A2:2018, Tanks for transport of dangerous goods — Digital interface for product
recognition devices for liquid fuels
EN 15208:2014, Tanks for transport of dangerous goods — Sealed parcel delivery systems — Working
principles and interface specifications
ISO 639-1, Codes for the representation of names of languages — Part 1: Alpha-2 code
3 Terms and definitions, abbreviations and conventions
For the purposes of this document, the following terms and definitions, abbreviations and conventions
apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
• IEC Electropedia: available at https://www.electropedia.org/
• ISO Online browsing platform: available at https://www.iso.org/obp
3.1 Terms and definitions
3.1.1
downgrade
intentional loading and discharge of a higher grade product (substance) into a lower grade product of the
same group
3.1.2
answer time
time between last frame character transmitted from OBC (client) and first character frame received from
TVE (server)
7
---------------------- Page: 9 ----------------------
SIST EN 15969-1:2022
EN 15969-1:2022 (E)
3.1.3
array
collection of elements which have the same structure and are able to be accessed individually by means
of an index
3.1.4
client
responsible for initiation and control of data exchange
3.1.5
field
element of a datagram delimited by separators
3.1.6
frame
data packet with variable length and specified structure
3.1.7
list
type of variables consisting of a number of records
3.1.8
MaxFrameSize
maximum number of characters in a frame
3.1.9
node
part of an address of a variable
3.1.10
graphic character
character, other than a control function or a format character, that has a visual representation normally
handwritten, printed or displayed
[SOURCE: ISO/IEC 10646:2020, 3.28]
3.1.11
record
ordered set of fields, stored contiguously
3.1.12
server
program which provides service to client programs
3.1.13
subnode
subpart of an address of a variable
3.1.14
datagram
instruction or answer to an instruction which comprises an OpCode and operand
8
---------------------- Page: 10 ----------------------
SIST EN 15969-1:2022
EN 15969-1:2022 (E)
3.1.15
transaction
complete request-answer-cycle
3.1.16
type identifier
character code for the frame type
3.2 Abbreviations
ACK acknowledge controlframe
ADF additional dataframe
ASCII American Standard Code for Information Interchange
CAN cancel controlframe
CRC cyclic redundancy checksum
CSV comma separated variable record
COP crossover prevention
EOR end of record dataframe
EOT end of transmission dataframe
FTL fuel-truck-link name of the interface
FTP file transfer protocol
L_FILE log file
LH_FILE log file header
NAK not acknowledge controlframe
OBC on-board-computer
NOTE 1 The OBC is one party in the FTL-communication (the client).
PID product identification device according to EN 14116
SYN synchronization controlframe
SPDS sealed parcel delivery system according to EN 15208
TEF CRC transmission error controlframe
TVE tank-vehicle-equipment
NOTE 2 The TVE is one party in the FTL-communication (the server).
OpCode operation code
3.3 Conventions
3.3.1 Syntax conventions
When describing the syntax of e.g. a datagram, some parts are required.
Every abstract part shall get a name, which is encapsulated by “<” and “>”. Optional arguments are
additionally encapsulated in square brackets.
9
---------------------- Page: 11 ----------------------
SIST EN 15969-1:2022
EN 15969-1:2022 (E)
EXAMPLE [,]
has always to be given (required). is optional, but when given, it shall be
preceded by a comma.
3.3.2 Presentation of communication exchange
In this document several examples can be found, demonstrating the flow of communication.
To illustrate the direction, data sent by the TVE (server) is shown indented.
EXAMPLE
client request 1
server response 1
server response 2
server response 3
client request 2
This means, that the command “client request n” shall be transmitted by the OBC, whereas the lines
“server response n” were transmitted by the TVE.
3.3.3 Numbers
Numbers may either be coded in decimal format (e.g. 12) or in hexadecimal format (e.g. 1Bh). In the latter
case, the number shall be followed by the character “h”.
4 Hardware interface
Communication shall only take place between two parties (point-to-point) the TVE and OBC.
For communication an asynchronous line shall be used (RS232, RS422 or RS485). The OBC and TVE start
up and default settings shall be 9 600 baud, 8 data bits, 1 stop bit and no parity.
The TVE may optionally support other baud rates (switching and switching back see 7.3.6).
5 Basic protocol layer
5.1 FTL-frame (frame)
The FTL-frame shall be according to Figure 2.
Figure 2
10
---------------------- Page: 12 ----------------------
SIST EN 15969-1:2022
EN 15969-1:2022 (E)
A frame shall have the following minimum requirements:
— always starts with a Start—Flag;
— always followed by type identifier;
— 1 End-Flag;
— 4 character Checksum (valid or invalid);
— frame length limited to MaxFrameSize.
Frames which do not fulfil these requirements shall be ignored and not answered. A new frame starts
upon the receipt of a Start-Flag. Any character received before the Start-Flag shall be ignored. All devices
using the FTL-protocol shall be able to receive complete frames of MaxFrameSize characters. A frame
shall be answered even if it contains an invalid checksum or incorrect characters (see 5.2).
If the type identifier in a frame is unknown a NAK shall be sent.
MaxFrameSize
The MaxFrameSize shall be 255 characters.
Start—Flag
The ASCII code 02h (start of text ) shall be used as the Start-Flag.
Type identifier
The type identifier shall be according to Table 1.
Content
The content may be empty or shall contain up to MaxFrameSize minus 7 characters. All characters in the
content shall be printable characters.
End-Flag
The ASCII code 03h (End of Text ) shall be used as the End—Flag.
Checksum
The Checksum verifies the integrity of a frame. It covers all characters from Start—Flag to End—
Flag including these flags. A CRC16 (16 bit) value in hexadecimal format (always 4 characters long) is
used and shall consist of the printable ASCII character “0” “9” or “A” “F” (example: the value 1AC9h shall
be sent with 4 ASCII character “1AC9”). The algorithm for the calculation is described in 5.4.
5.2 Frame flow (handshake)
The character immediately following the Start-Flag specifies the frame type. The different frame groups
and their frame types are described in Table 1.
11
---------------------- Page: 13 ----------------------
SIST EN 15969-1:2022
EN 15969-1:2022 (E)
Table 1 — Frame groups and frame types
Type identifier
Additional
Frame group Frame type Abbreviation
Client to Server to
fields
server client
Dataframe end of record frame EOR data R, V r, v
additional dataframe
ADF data L, P l, p
following frame
end of transmission
EOT data E, I e, i
frame
Controlframe acknowledge frame ACK no A a
synchronization/wait
a
SYN no s
—
frame
cancel frame CAN no C c
CRC transmission error
TEF no T t
frame
not acknowledge frame NAK-ID
a
NAK according to n
—
Table 71
a
Not applicable.
To distinguish the direction of data (client to server or server to client) upper and lower case type
character shall be used.
Every communication shall start with a dataframe.
Every dataframe from the server shall be answered by the client.
Every frame from the client shall be answered by a frame from the server.
If a dataframe is received by the server when an acknowledge is expected it shall be treated as a cancel
frame (CAN) regarding the preceding transaction.
Every data frame on each side, independently, shall be flagged alternatively (toggled) with the secondary
(V,P,I) and primary (R,L,E) type identifier. If subsequent dataframes with identical type identifier are
received, these shall be treated as a repetition with identical data but shall be answered as the original,
see Figure 11. This prevents redundant entries in lists resulting from communication faults.
After the startup of the system the first dataframe on each side shall start with the primary type identifier
(R,L,E). The first request after startup shall not be a SET-request to a list.
Examples of frame flows:
— Transaction that requires only one datagram in either direction, each fitting into a single frame,
see Figure 3.
12
---------------------- Page: 14 ----------------------
SIST EN 15969-1:2022
EN 15969-1:2022 (E)
a) b)
Figure 3
— Transactions that require more than one datagram (e.g. multi record transfer), EOR—frames shall
indicate that additional datagrames will follow. An EOT—frame shall be the last dataframe of the
transaction, see Figure 4.
a) b)
Figure 4
— Datagrams that require more than o
...
SLOVENSKI STANDARD
oSIST prEN 15969-1:2021
01-junij-2021
Cisterne za prevoz nevarnega blaga - Digitalni vmesnik za prenos podatkov med
cisterno in stacionarnimi napravami - 1. del: Opredelitev protokola - Upravljanje,
merjenje in zajem podatkov
Tanks for transport of dangerous goods - Digital interface for the data transfer between
tank vehicle and with stationary facilities - Part 1: Protocol specification - Control,
measurement and event data
Tanks für die Beförderung gefährlicher Güter - Digitale Schnittstelle für den
Datenaustausch zwischen Tankfahrzeugen und stationären Einrichtungen - Teil 1:
Protokollspezifikation - Steuerungs-, Mess- und Ereignisdaten
Citernes destinées au transport de matières dangereuses - Interface numérique pour le
transfert de données entre des véhicules-citernes et des installations fixes - Partie 1:
Spécifications du protocole - Contrôle, données de mesure et dévénements
Ta slovenski standard je istoveten z: prEN 15969-1
ICS:
13.300 Varstvo pred nevarnimi Protection against dangerous
izdelki goods
23.020.10 Nepremične posode in Stationary containers and
rezervoarji tanks
35.240.60 Uporabniške rešitve IT v IT applications in transport
prometu
oSIST prEN 15969-1:2021 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
oSIST prEN 15969-1:2021
---------------------- Page: 2 ----------------------
oSIST prEN 15969-1:2021
DRAFT
EUROPEAN STANDARD
prEN 15969-1
NORME EUROPÉENNE
EUROPÄISCHE NORM
June 2021
ICS 13.300; 23.020.10; 35.240.60 Will supersede EN 15969-1:2017
English Version
Tanks for transport of dangerous goods - Digital interface
for the data transfer between tank vehicle and with
stationary facilities - Part 1: Protocol specification -
Control, measurement and event data
Citernes destinées au transport de matières Tanks für die Beförderung gefährlicher Güter - Digitale
dangereuses - Interface numérique pour le transfert de Schnittstelle für den Datenaustausch zwischen
données entre des véhicules-citernes et des Tankfahrzeugen und stationären Einrichtungen - Teil
installations fixes - Partie 1: Spécifications du protocole 1: Protokollspezifikation - Steuerungs-, Mess- und
- Contrôle, données de mesure et d¿événements Ereignisdaten
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee
CEN/TC 296.
If this draft becomes a European Standard, CEN members are bound to comply with the CEN/CENELEC Internal Regulations
which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.
This draft European Standard was established by CEN in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC
Management Centre has the same status as the official versions.
CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and
United Kingdom.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.
Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION
EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2021 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 15969-1:2021 E
worldwide for CEN national Members.
---------------------- Page: 3 ----------------------
oSIST prEN 15969-1:2021
prEN 15969-1:2021 (E)
Contents Page
European foreword . 4
Introduction . 6
1 Scope . 7
2 Normative references . 7
3 Terms and definitions, abbreviations and conventions . 7
3.1 Terms and definitions . 7
3.2 Abbreviations . 9
3.3 Conventions . 10
4 Hardware interface . 10
5 Basic protocol layer . 10
5.1 FTL-frame (frame) . 10
5.2 Frame flow (handshake) . 11
5.3 Delay and timeout . 16
5.4 CRC16 Checksum . 17
6 Data protocol layer (FTL-data protocol) . 17
6.1 Client (OBC) and server (TVE) . 17
6.2 Syntax of data in datagrams . 17
6.3 Nodes, subnodes, variables . 18
6.4 Format identifiers . 18
6.5 Types of variable values . 21
6.6 Kinds of nodes . 21
7 FTL-Data . 23
7.1 General . 23
7.2 Record and field types . 23
7.3 Systemwide variables (subnode SYSTEM) . 24
7.4 Variables related to global positioning system (subnode GPS) . 27
7.5 Accessing a printer on TVE-side (subnode PRN) . 28
7.6 Compartment information (subnode COMP) . 31
7.7 Notification about changes (subnode NOTIFY) . 33
7.8 Information about driver (subnode DRIVER) . 34
7.9 Information about the vehicle (variable VEHICLE_ID) . 35
7.10 Information about current operation (subnode OPERATION) . 35
7.11 Access to filesystem on TVE (subnode FS) . 38
7.12 Auxiliary (subnode AUX) . 43
7.13 Order management (subnode ORDER) . 43
7.14 Goods and service database (subnode PRODUCT) . 48
7.15 FTL—logfile (subnodes LOG) . 51
7.16 Required variables . 84
7.17 NAK ID . 84
8 Routing for multiple TVE . 85
8.1 Purpose . 85
8.2 Routing solution . 85
8.3 Routing example . 86
9 Communication with office . 86
2
---------------------- Page: 4 ----------------------
oSIST prEN 15969-1:2021
prEN 15969-1:2021 (E)
9.1 General . 86
9.2 Simple file transfer . 87
9.3 FTL over TCP/IP . 89
10 Communication Examples . 91
10.1 Examples for Basic Protocol Layer level . 91
10.2 Examples for data protocol layer . 93
Annex A (normative) Node tree . 96
Annex B (normative) Test FTL . 97
B.1 Overview . 97
B.2 Basic Protocol Layer . 97
B.2.1 Frame Tests. 97
B.2.2 CRC-error . 98
B.2.3 Delay and Timeout . 98
B.3 Data Protocol Layer . 98
B.3.1 Test of Toggling . 98
B.3.2 Test of the FTL data layer . 99
B.3.3 Test of the required FTL nodes . 100
B.3.4 Optional System Subnodes . 103
B.3.5 Optional Node Prn . 105
B.3.6 Node Comp . 107
B.4 Application Layer. 113
B.4.1 Test of the L-File . 113
B.4.2 Test of the LH-File . 113
B.4.3 Test for the Filling of the NodeList . 113
B.4.4 Sequence Test . 114
Bibliography . 116
3
---------------------- Page: 5 ----------------------
oSIST prEN 15969-1:2021
prEN 15969-1:2021 (E)
European foreword
This document (prEN 15969-1:2021) has been prepared by Technical Committee CEN/TC 296 “Tanks
for the transport of dangerous goods”, the secretariat of which is held by AFNOR.
This document is currently submitted to the CEN Enquiry.
This document will supersede EN 15969-1:2017.
With regard to EN 15969-1:2017, the following fundamental changes are given:
Figure 11 corrected;
Subclause 7.3.11 "Trailer coupled (variable TRAILER)" added;
Subclause 7.5.9 "Duplicate print (DUPLICATE)" added;
Table 55 "Fields of records of ORDER.PLAN" Index 19 to 21 added;
In subclause 7.13.4 Value V for planned transaction in process and unplanned transaction in
process added;
Table 67 "L file record types" in Index L1137 Bit 3 added;
Table 67 "L file record types" Index L1147 added;
Table 67 "L file record types" Index L1205 added;
Table 67 "L file record types" in Index L2002 event codes 80 to > 100 added;
Table 67 "L file record types" Index L4007 and L4008 added;
Table 67 "L file record types" in Index L4206 delivery path 25 to 36 and 80 to 86 added;
Table 67 "L file record types" Index L4207 and L4208 added;
Table 67 "L file record types" Index 94 Diagnose added;
Node tree in Figure A.1 revised.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent
rights of which they are aware and to provide supporting documentation.
EN 15969, Tanks for transport of dangerous goods — Digital interface for the data transfer between tank
vehicle and with stationary facilities, consists of 2 parts:
— Part 1: Protocol specification — Control, measurement and event data;
— Part 2: Commercial and logistic data.
4
---------------------- Page: 6 ----------------------
oSIST prEN 15969-1:2021
prEN 15969-1:2021 (E)
This European Standard forms part of a coherent standards programme comprising the following
standards:
— EN 13616-1, Overfill prevention devices for static tanks for liquid fuels — Part 1: Overfill prevention
devices with closure device;
— EN 13616-2, Overfill prevention devices for static tanks for liquid fuels — Part 2: Overfill prevention
devices without a closure device;
— EN 13922, Tanks for transport of dangerous goods — Service equipment for tanks — Overfill
prevention systems for liquid fuels;
— EN 14116, Tanks for transport of dangerous goods — Digital interface for product recognition devices
for liquid fuels;
— EN 15207, Tanks for the transport of dangerous goods — Plug/socket connection and supply
characteristics for service equipment in hazardous areas with 24 V nominal supply voltage;
— EN 15208, Tanks for transport of dangerous goods — Sealed parcel delivery systems — Working
principles and interface specifications;
— EN 15969-2, Tanks for transport of dangerous goods — Digital interface for the data transfer
between tank vehicle and with stationary facilities — Part 2: Commercial and logistic data.
5
---------------------- Page: 7 ----------------------
oSIST prEN 15969-1:2021
prEN 15969-1:2021 (E)
Introduction
FTL is an acronym for Fuel Truck Link, the interface between electronic system(s) on board of a tank
vehicle (tank-vehicle-equipment) and any external computer, e.g. an on-board-computer installed in the
driver’s cabin; for illustration see Figure 1.
Key
→ direction of communication (client → server)
a may be either two independent units or one single unit which incorporates both functions OBC and TVE
Figure 1
6
---------------------- Page: 8 ----------------------
oSIST prEN 15969-1:2021
prEN 15969-1:2021 (E)
1 Scope
This document specifies data protocols and data format for the interfaces between electronic
equipment (TVE), on-board computer (OBC) of the tank vehicle and stationary equipment for all
interconnecting communication paths.
This document specifies the basic protocol FTL used in the communication (basic protocol layer), the
format and structure of FTL-data to be transmitted (data protocol layer) and describes the content of
the FTL-data.
This data protocol may be used for other application e.g. between stationary tank equipment and
offices.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
EN 13616-2, Overfill prevention devices for static tanks for liquid fuels - Part 2: Overfill prevention devices
without a closure device
EN 13922, Tanks for transport of dangerous goods - Service equipment for tanks - Overfill prevention
systems for liquid fuels
EN 14116:2012+A2:2018, Tanks for transport of dangerous goods - Digital interface for product
recognition devices for liquid fuels
EN 15208:2014, Tanks for transport of dangerous goods - Sealed parcel delivery systems - Working
principles and interface specifications
prEN 15969-2:2021, Tanks for transport of dangerous goods — Digital interface for the data transfer
between tank vehicle and with stationary facilities — Part 2: Commercial and logistic data
ISO 639-1, Codes for the representation of names of languages — Part 1: Alpha-2 code
ISO/IEC 10646:2020, Information technology — Universal coded character set (UCS)
DIN 51757:2011, Testing of mineral oils and related materials — Determination of density
3 Terms and definitions, abbreviations and conventions
For the purposes of this document, the following terms and definitions, abbreviations and conventions
apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
3.1 Terms and definitions
3.1.1
downgrade
intentional loading and discharge of a higher grade product (substance) into a lower grade product of
the same group
7
---------------------- Page: 9 ----------------------
oSIST prEN 15969-1:2021
prEN 15969-1:2021 (E)
3.1.2
answer time
time between last frame character transmitted from OBC (client) and first character frame received
from TVE (server)
3.1.3
array
collection of elements which have the same structure and are able to be accessed individually by means
of an index
3.1.4
client
responsible for initiation and control of data exchange
3.1.5
field
element of a datagram delimited by separators
3.1.6
frame
data packet with variable length and defined structure
3.1.7
list
type of variables consisting of a number of records
3.1.8
MaxFrameSize
maximum number of characters in a frame
3.1.9
node
part of an address of a variable
3.1.10
graphic character
character, other than a control function or a format character, that has a visual representation normally
handwritten, printed or displayed
[SOURCE: ISO/IEC 10646:2020, 3.28]
3.1.11
record
ordered set of fields, stored contiguously
3.1.12
server
program which provides service to client programs
3.1.13
subnode
subpart of an address of a variable
8
---------------------- Page: 10 ----------------------
oSIST prEN 15969-1:2021
prEN 15969-1:2021 (E)
3.1.14
datagram
instruction or answer to an instruction, which comprises an OpCode and operand
3.1.15
transaction
complete request-answer-cycle
3.1.16
type identifier
character code for the frame type
3.2 Abbreviations
ACK acknowledge controlframe
ADF additional dataframe
ASCII American Standard Code for Information Interchange
CAN cancel controlframe
CRC cyclic redundancy checksum
CSV comma separated variable record
COP crossover prevention
EOR end of record dataframe
EOT end of transmission dataframe
FTL fuel-truck-link name of the interface
FTP file transfer protocol
L_FILE log file
LH_FILE log file header
NAK not acknowledge controlframe
OBC on-board-computer
NOTE 1 The OBC is one party in the FTL-communication (the client).
PID product identification device according to EN 14116
SYN synchronization controlframe
SPDS sealed parcel delivery system according to EN 15208
TEF CRC transmission error controlframe
TVE tank-vehicle-equipment
NOTE 2 The TVE is one party in the FTL-communication (the server).
OpCode operation code
9
---------------------- Page: 11 ----------------------
oSIST prEN 15969-1:2021
prEN 15969-1:2021 (E)
3.3 Conventions
3.3.1 Syntax conventions
When describing the syntax of e.g. a datagram, some parts are required.
Every abstract part shall get a name, which is encapsulated by “<” and “>”. Optional arguments are
additionally encapsulated in square brackets.
EXAMPLE [,]
has always to be given (required). is optional, but when given, it shall be
preceded by a comma.
3.3.2 Presentation of communication exchange
In this document several examples can be found, demonstrating the flow of communication.
To illustrate the direction, data sent by the TVE (server) is shown indented.
EXAMPLE
client request 1
server response 1
server response 2
server response 3
client request 2
This means, that the command “client request n” shall be transmitted by the OBC, whereas the lines
“server response n” were transmitted by the TVE.
3.3.3 Numbers
Numbers may either be coded in decimal format (e.g. 12) or in hexadecimal format (e.g. 1Bh). In the
latter case, the number shall be followed by the character “h”.
4 Hardware interface
Communication shall only take place between two parties (point-to-point) the TVE and OBC.
For communication an asynchronous line shall be used (RS232, RS422 or RS485). The OBC and TVE
start up and default settings shall be 9 600 baud, 8 data bits, 1 stop bit and no parity.
The TVE may optionally support other baud rates (switching and switching back see 7.3.6).
5 Basic protocol layer
5.1 FTL-frame (frame)
The FTL-frame shall be according to Figure 2.
10
---------------------- Page: 12 ----------------------
oSIST prEN 15969-1:2021
prEN 15969-1:2021 (E)
Figure 2
A frame shall have the following minimum requirements:
— always starts with a Start—Flag;
— always followed by type identifier;
— 1 End-Flag;
— 4 character Checksum (valid or invalid);
— frame length limited to MaxFrameSize.
Frames which do not fulfil these requirements shall be ignored and not answered. A new frame starts
upon the receipt of a Start-Flag. Any character received before the Start-Flag shall be ignored. All
devices using the FTL-protocol shall be able to receive complete frames of MaxFrameSize characters. A
frame shall be answered even if it contains an invalid checksum or incorrect characters (see 5.2).
If the type identifier in a frame is unknown a NAK shall be sent.
MaxFrameSize
The MaxFrameSize shall be 255 characters.
Start—Flag
The ASCII code 02h (start of text ) shall be used as the Start-Flag.
Type identifier
The type identifier shall be according to Table 1.
Content
The content may be empty or shall contain up to MaxFrameSize minus 7 characters. All characters in
the content shall be printable characters.
End-Flag
The ASCII code 03h (End of Text ) shall be used as the End—Flag.
Checksum
The Checksum verifies the integrity of a frame. It covers all characters from Start—Flag to End—
Flag including these flags. A CRC16 (16 bit) value in hexadecimal format (always 4 characters long) is
used and shall consist of the printable ASCII character “0” “9” or “A” “F” (example: the value 1AC9h shall
be sent with 4 ASCII character “1AC9”). The algorithm for the calculation is described in 5.4.
5.2 Frame flow (handshake)
The character immediately following the Start-Flag defines the frame type. The different frame groups
and their frame types are described in Table 1.
11
---------------------- Page: 13 ----------------------
oSIST prEN 15969-1:2021
prEN 15969-1:2021 (E)
Table 1 — Frame groups and frame types
Type identifier
Additional
Frame group Frame type Abbreviation
Client to Server to
fields
server client
Dataframe end of record frame EOR data R, V r, v
additional dataframe
ADF data L, P l, p
following frame
end of transmission
EOT data E, I e, i
frame
Controlframe acknowledge frame ACK no A a
synchronization/wait
a
SYN no s
—
frame
cancel frame CAN no C c
CRC transmission
TEF no T t
error frame
not acknowledge NAK-ID
a
frame NAK according to n
—
Table 71
a
Not applicable.
To distinguish the direction of data (client to server or server to client) upper and lower case type
character shall be used.
Every communication shall start with a dataframe.
Every dataframe from the server shall be answered by the client.
Every frame from the client shall be answered by a frame from the server.
If a dataframe is received by the server when an acknowledge is expected it shall be treated as a cancel
frame (CAN) regarding the preceding transaction.
Every data frame on each side, independently, shall be flagged alternatively (toggled) with the
secondary (V,P,I) and primary (R,L,E) type identifier. If subsequent dataframes with identical type
identifier are received, these shall be treated as a repetition with identical data but shall be answered as
the original, see Figure 11. This prevents redundant entries in lists resulting from communication faults.
After the startup of the system the first dataframe on each side shall start with the primary type
identifier (R,L,E). The first request after startup shall not be a SET-request to a list.
Examples of frame flows:
— Transaction that requires only one datagram in either direction, each fitting into a single frame,
see Figure 3.
12
---------------------- Page: 14 ----------------------
oSIST prEN 15969-1:2021
prEN 15969-1:2021 (E)
a) b)
Figure 3
— Transactions that require more than one datagram (e.g multi record transfer), EOR—frames shall
indicate that additional datagrames will follow. An EOT—frame shall be the last dataframe of the
transaction, see Figure 4.
a) b)
Figure 4
— Datagrams that require more than one frame, because MaxFrameSize is too small to hold a
complete datagram shall be split into one or more ADF—frames and an EOT—frame or EOR-frame
as appropriate, see Figure 5.
a) b)
Figure 5
13
---------------------- Page: 15 ----
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.