Part 3 11 Deliverycontrolapplicationv1.06

IFSF
WORKING GROUP
PROPOSAL
PART III.11
DELIVERY CONTROL
APPLICATION
V1.06
Page 2
COPYRIGHT AND INTELLECTUAL PROPERTY RIGHTS STATEMENT
The content (content being images, text or any other medium contained within this document which is
eligible of copyright protection) is Copyright © IFSF Ltd 2011. All rights expressly reserved.
You may print or download to a local hard disk extracts for your own business use. Any other
redistribution or reproduction of part or all of the contents in any form is prohibited.
You may not, except with our express written permission, distribute to any third party.
Where permission to distribute is granted by IFSF, the material must be acknowledged as IFSF copyright
and the document title specified. Where third party material has been identified, permission from the
respective copyright holder must be sought.
You agree to abide by all copyright notices and restrictions attached to the content and not to remove or
alter any such notice or restriction.
USE OF COPYRIGHT MATERIAL
Subject to the following paragraph, you may design, develop and offer for sale products which embody the
functionality described in this document.
No part of the content of this document may be claimed as the Intellectual property of any organisation
other than IFSF Ltd, and you specifically agree not to claim patent rights or other IPR protection that
relates to:
the content of this document; or
any design or part thereof that embodies the content of this document whether in whole or part.
IFSF TANK DELY DRAFT 1.06 IFSF - STANDARD FORECOURT PROTOCOL December 2011
WORKING GROUP PROPOSAL TANK DELIVERY CONTROL APPLICATION
Copyright © IFSF Ltd 2011
Page 3
AUTHORS
This document is written by the Delivery Control working group, September 1996
Name Company Tel/Fax

Sergio Folchitto Agip Petroli Phone: + 39 6 598 86758
Roma (Italy) Fax: +39 6 598 86736
e-Mail
sergio.folchitto@agippetroli.eni.it
Roberto Guazzoni Gruppo Isoil Phone: + 39 2 660271
Milano (Italy) Fax: +39 2 6123202
Pietro Visibelli Logitron Phone: + 39 55 30901
Firenze (Italy) Fax: +39 55 318 603
e-Mail
sw.develop@logitron.it
Mario Gatto Starter Security System Phone: + 39 6 6637688
Roma (Italy) Fax: +39 6 6637690
S. Alexander Vedeer Root Phone: +44 181 392 1355
Richmond(UK) Fax: +44 181 878 6642
e-Mail
STEVE_ALEXANDER@VR-UK-
RICHMOND.CCMAIL.COMPUSERVE.COM
J.J. Thiara SCULLY Signal Co Phone: + 1 617 729 7510
U.S.A: Fax: +1 508 657 8615
H. Hoffmann ARAL AG Phone: +49 234 315 1821
Fax: +49 234 315 2341
N. Healy TEXACO Ltd Phone: +44 171 719 3663
Fax: +44 171 719 5126
Y. Lallinec TOTAL R. D Phone +33 141 358941
H. Hornlein Kathofer ets Phone +49 5244 928 650
Fax +49 5244 928 652
e-Mail
k.roehl@t-online.de
K. Brandts SCHEIDT&BACHMANN GmbH Fax +49 2166 266 342
H..Walraven LON MARK Fax +31 33 453 5445
R. Jacobs B P Oil Europe Phone +32 2 766 38 13
Fax + 32 2 76634 77
e-Mail
JACOBSR@BP.COM
H. Putto B P Oil Europe Phone +31 1041 75380
Fax +31 1041 75449
E. A. Brathe A. Haar Phone +49 40 83 39 10
Fax +49 40 84 49 10
e-Mail
spranges@alfons-haar.de
Philip Prow PetroVend Phone +44 1582 505339
Fax +44 1582 490960
A. D. Stroeder F.A. Sening GmbH Phone +49 4101 3040
Fax +49 4101 30 4255
e-Mail
ADSTROEDER.FASENING@eMails.de
Alan Chandler Tuthill Europe e-Mail
igw@eatl.co.uk
Emco Electronics
R. Decker DIE MASCHE Phone +49 991-37146-0
Fax +49 991-37146-10
e-Mail
rainer@masche.com
M. Pulmann EXXON Company International Phone +32 2 713 6248
Fax + 32 2 713 4342
This document is a draft working group document, changes are controlled by the DELIVERY
CONTROL Working group chairman, Sergio Folchitto to whom all questions should be addressed
Page 4
in the first instance.
Page 5
TABLE OF CONTENTS
0 RECORD OF CHANGES ..................................................................................................................................................................... 6
1 GENERAL ............................................................................................................................................................................................. 7
1.1 DEFINITIONS AND ABBREVIATIONS ................................................................................................................................... 7
1.2 INTRODUCTION TO THE DELIVERY CONTROL PROTOCOL .......................................................................................... 5
1.3 FILLING OPERATION ................................................................................................................................................................. 6
1.4 FILLING BY LEVEL/VOLUME .................................................................................................................................................. 6
1.5 CLASSIFICATION OF THE TANK LORRY DEVICE ............................................................................................................. 6
1.6 DELIVERY CONTROL PROTOCOL: STATUS DESCRIPTION ............................................................................................ 7
2 INITIALIZATION OF THE DELIVERY CONTROL ....................................................................................................................... 7
2.1 STARTING OPERATION OF THE DELIVERY CONTROL: INITIALIZATION .................................................................. 7
2.2 CONFIGURATION ....................................................................................................................................................................... 8
2.3 COMMUNICATION RELATION ................................................................................................................................................ 8
2.4 SPECIAL OPERATING STATES ................................................................................................................................................ 8
2.5 CHECK DIAGRAM ....................................................................................................................................................................... 8
3.1 EVENT DESCRIPTION ............................................................................................................................................................... 9
3.2 COMMUNICATIONS ................................................................................................................................................................. 12
3.3 MAIN STATE .............................................................................................................................................................................. 12
4 STATES ............................................................................................................................................................................................... 13
4.1 STATE DIAGRAM ...................................................................................................................................................................... 13
4.2 STATE TABLE ............................................................................................................................................................................ 14
4.3 STATE DESCRIPTION .............................................................................................................................................................. 15
4.3.1 INOPERATIVE [1] ............................................................................................................................................................... 15
4.3.2 CLOSED [2] .......................................................................................................................................................................... 16
4.3.3 IDLE (SET-UP) [3] ............................................................................................................................................................... 14
4.3.4 OPERATIVE[4] .................................................................................................................................................................... 18
4.3.5 FILLING [5] .......................................................................................................................................................................... 19
4.3.6 FILLING BY THE LEVEL/VOLUME [6] .......................................................................................................................... 22
5 DELIVERY DATA BASE .................................................................................................................................................................. 23
5.1 GENERAL .................................................................................................................................................................................... 23
5.2 DATA BASE OVERVIEW ......................................................................................................................................................... 24
5.3 OBC DATA BASE ADDRESSING ............................................................................................................................................ 24
5.4 FIELD FORMATS ....................................................................................................................................................................... 25
5.5 MAIN ............................................................................................................................................................................................ 26
5.6 MANUFACTURER CONFIGURATION .................................................................................................................................. 36
5.7 SYSTEM CONFIGURATION .................................................................................................................................................... 37
5.8 ERROR CODES ........................................................................................................................................................................... 39
5.9 DATA DOWNLOAD ................................................................................................................................................................... 41
Page 6
0 RECORD OF CHANGES
Date Version Modifications

96/09/21 1.00 Version created.
97/01/28 1.01 Version updated upon the experience of AGIP delivery control.
97/10/08 1.02 Version updating after TWG meeting of Sep 26th 1997.
98/01/23 1.03 Version updated for : Working Group Members.
98/05/29 1.05 Version updated with BP notes.
98/06/18 1.05 Version updated with fiscal printer and price Data ID.
11/12/28 1.06 Copyright and IPR Statement added.
Page 7
1 GENERAL
1.1 DEFINITIONS AND ABBREVIATIONS
DEFINITION ABBREVIATIONS DESCRIPTION

On board computer OBC The OBC is the device where the delivery operation are stored and
updated.
Petrol station control PSC The PCS is the device where the station operativity will be follow-
upThe PSC device will normally consist of a computer that communicate
with the OBC through the station bus i a wired or in a wireless
connection.
Deposit Control system DCS The DCS is the system that knows in advance the delivery data of any
petrol station and fill-in the OBC with the discharge information.
Controller device CD The CD is any device that is capable of controlling other devices.
Card Handling Device CHD The CHD is a device that combines one or more of the individual card
handling devices (PIN pads, Card Readers, Receipt Printers, ...).
Bank note Handling Device BHD The BHD is a device that combines one or more of the individual
banknote handling devices (i.e. Banknote Reader, Receipt Printer, etc..).
Payment Handling Device PHD The PHD is a device that combines CHD and the BHD.
Tank Level Gauge TLG A hardware device that controls one or more tank probes. Up to 31 tank
probes can be controlled from one TLG.
Product PR The product is the motor fuel stored in the tank.
Fiscal Printer FPR The FPR is the printer that will prints-out the product discharge report at
the end of the discharge
Tank Probe TP A hardware device which measures the product level of a tank. Some
TP's are also capable of measuring the product temperature and the
product density.
1.2 INTRODUCTION TO THE DELIVERY CONTROL PROTOCOL
The petrol stations are refilled, upon needs, by the tank lorry. The tank lorry may have many compartments and several hoses for
the discharge, that could be computerized. If suitable sensors are installed into tank compartments, density and temperature may be
measured and processed. The tank lorry on board computer (OBC) will be the key factor that processes all discharge information
and parameters.
The safe discharge of the product is under the responsibility of the lorry driver, who will use various electronic or mechanical
devices (grounding of the tank lorry, preventing of the overfilling, filling of the wrong product into a tank*, vapour recovery nozzle,
etc).
In some delivery control system a filling devices updates the OBC with the tank identification number and the product grade.
The discharge operation may be executed in a known mode, in the sense that the OBC knows in advance only the products and
the volumes to discharge for any petrol station and even, in some cases, for each buried tank.
The refilling may be executed, however, in a blind mode, in the sense that the OBC will monitor the discharge transmitting and
receiving data and information to and from the petrol station.
Any petrol station must have as fixed component of the bus a communication node which performs data exchange, adhering to
IFSF standard, in a wire-bound or in a wireless form.
The OBC will be in such way directly connected to the communication bus of the service station, allowing mutual direct exchange
of the available data.
Even the filling by level/volume of any tank of the petrol station can be automatically followed by the tank lorry OBC through the
tank gauge system of the station.
The OBC, the petrol station console (PSC) the tank gauging level (TLG) and the other IFSF devices on the station bus have to be
considered as independent systems:
The PSC will continue to follow the station operation while the OBC is making the product discharge; the OBC will follow the
safety discharge and request the product level and sale data to the PSC, as well as the OBC may also request tank levels directly to
the tank gauging system (TLG) of the petrol station through the station bus.
Page 8
At the discharge end the OBC will sent discharge data to the station bus.
* for ex.: a tag device on the station tank inlet may send an encoded message to the tank lorry OBC using the concept of the
parasitic power.
1.3 FILLING OPERATION (known mode)
The filling operation will be driven by the tank lorry OBC according to the order.
During the filling operation many control will be performed by the OBC, by the TLG and by the PSC:
- in case of excessive filling the TLG itself raises an alarm asking to stop the filling operation;
- during the discharge operation, the TLG will provide the OBC with the current values of the available space in the involved tanks.
The relevant information to make possible the above operations can be performed only if communication will be established
between the OBC and the station node and so on.
1.4 FILLING BY THE LEVEL/VOLUME (blind mode)
Filling of the petrol station tanks by the level/volume refers to the filling level/total volume reference list of the tank gauge. The
process of filling by the level/volume takes place by repeated delivery of specified quantity of product required to the tank lorry
with evaluation by the tank gauge (TLG); the TLG checks the filling operation and informs the OBC and the PSC about the
quantity to be filled and gives the tank designation.
The PSC notify the variable “Tank_Status” in accordance with and makes it available to the OBC after that the connection with has
been established. The filling is then carried out with the supervision of the petrol station staff specialist. In other words the TLG
notifies the quantity to be filled in.
Delivery stop take place in the same way as for the normal delivery.
1.5 CLASSIFICATION OF THE TANK LORRY DEVICE
The basic functionality is determined by the present state of the european and national rules and by the state of the art.
The petrol station may determine further functionality of the device by reading out the list of the names of the associated variables.
- basic functionality:
preconfiguration of the device at manufacturer‟s works
ensuring also of a paperless delivery voucher (sealed parcel), depending upon the country
- options:
ensuring protection from mixing
support filling of buried tanks by the level/volume
download of programs and configuration data
1.6 DELIVERY CONTROL PROTOCOL: STATUS DESCRIPTION

The delivery control protocol follows the delivery operations of the tank lorry OBC. The functions of the delivery control are
shown by the function state diagram.
The function or event state diagram reports the following states:
Inoperative [1]
Closed [2]
Idle [3].
Operative[4].
Filling[5].
Filling by the level/volume[6].
The Inoperative status. after establishing of the communication allows configuration and parameter modification and program
change. (Associated event is the “terminate initialisation” by the PSC when dawnloading has been completed successfully).
The OBC enters the function status “closed” and presents as major error :- no change of function status
and as minor error the unsolicited status.
The closed function status set the application program operative but not active and waits for the “set basic state” instruction from
the PSC. Associate event is “set idle status” entering into the idle status; major error is no change of status; if major error occurs
the device will enter the function status “inoperative” (the basic instruction is “deactivate”) and wait for further instructions;
Page 9
minor error is the unsolicited Status and has as result - no change of function status.
The idle function set operative the basic program that will be executed . The associated event is the “close” instruction whether an
emergency situation has been detected. Whether a major error occurs the device will enter automatically the function status
“inoperative”. In case of minor error the device reacts with no change of status and wait for operation (measures).
The device status may be notified to the PSC either when the console (PSC) reads the status of through an unsolicited message.
The status message contains information about the mode of operation and the operating status as well. Any bit of the status
message is dedicated to a particular device status.
An “information report” may be set-up to evidenciate extra information as individual tank compartment, buried tank, etc.
2 INITIALIZATION OF THE DELIVERY CONTROL

The initialisation of the OBC is carry out by the DEPOSIT CONTROL SYSTEM (DCS), which is entitle of print the official
delivery sheet which reports the discharge data, or by the PSC, that knows in advance the product delivery amounts.
The DCS loads the tank lorry OBC with the discharge data and delivery information.
By contacting the OBC the PSC detects the OBC resources and identifies the device.
2.1 STARTING OPERATION OF THE DELIVERY CONTROL: INITIALIZATION

Whether the initialisation is carry-out by the DCS, it initialises the OBC, at the deposit, with the discharge data and delivery
information, the same data that are reported into the official delivery sheet.
The OBC then switches the status from inoperative to closed.
Upon tank lorry arrival at petrol station, the OBC switches the status from closed to operative and will, through unsolicited
messages:
a - inform the PSC of its arrival;
b - receive tank level status;
c - ask to the PSC the sales data of the discharge period;
d - communicate to the PSC the results of the discharge operation (i.e. the amount of the discharge operation balanced with the
sales quantity must match the tank levels);
At the and of the operation the OBC switches the status from operative to idle.
The OBC then, upon its arrival at the deposit, sends the discharge operation results to the DCS, adding to tank levels data and
balanced amounts.
As alternative the initialisation may be carry-out by the PSC, by consulting the discharge files and extracting the information to
establish the contact with the tank lorry OBC.
The initialisation covers the period from the OBC connection to the station bus up to the start of the delivery functions.
The OBC send the list of variables which are characteristic of the assisted optional functions.
Subsequently the OBC device is set to the basic function state, so it is ready to operate.
Page 10
3 PROCESS FLOW CHART
IFSF
Delivery Control
Loading Tank
Compartments
Truck sealing
system
Transfer loading
information to the
OBC
Lorry reaches the

service station
(FILLING)
Tag message from the
Fill Station tanks station tank inlet
Transfer data to OBC
Transfer data to
Depot or Company
system
Page 11
3.1 CONFIGURATION
The petrol station uses external configuration data determining the delivery functions. Configuration of the device is possible only
in the function state “INOPERATIVE”. The basic configuration pertain the initial or first installation of the device.
3.2 COMMUNICATION RELATIONS

After that the connection between the OBC and the petrol station console PSC has been established, the OBC, the TLG and the
PSC will take part of the communication.
The OBC needs to receive data from the PSC for what concerns technical, physical and commercial data pertinent to the buried
tank and the product sales during the delivery itself.
The PSC needs the data of the tank compartments and the delivery data.
The station tanks are identified by the tank gauging concentrator.
A specified check is to be done regarding the time consuming of the OBC device when connected to the station in order to prevent
the malfunctioning, i.e. discharge protection and so on; in such case the alarm must be evidenciate in the due time.
3.3 SPECIAL OPERATING STATES

The refilling of the buried tanks requires communication to the tank lorry OBC and to the PSC.
It is assumed that, in this special event, the OBC will drive the data requirements from the TLG. The same data will be received
from the PSC.
In case that a major error happens, the device will change the state to inoperative, and the automatic filling operation will be
interrupted, but they can proceed manually by the driver.
4 CHECK DIAGRAMM
3.1 Check Connection and id of the tank lorry at depot
Tank lorry connected
Transmission active
Tank lorry leaves the depot
3.2 Check Connection and id of station tank to be refilled
Tank lorry connected
Ready for discharge
Discharge active
Discharge stop
Discharge terminated
Tank lorry leaves petrol station
4.1
Page 12
EVENT DESCRIPTION
‘EVENT_DESCRIPTION’ = internal event.
„EVENT_DESCRIPTION‟ = external event (controller device).
„***‟ = all other events/commands which are not included in the list.
The Data_Id is an unique identifier for a data element in a data base. The data base is defined by the data base address “DB_Ad”
(for details see document “Part II, Communication Specification”).
In the second column the name of the data element is defined. In this column is also the description of the data element.
The field types in the column three are described in chapter 0, page 25 of this document.
The “Read/Write in state” column indicates if the related data can be Read and/or Written by any device and which OBC state
(states are indicated between brackets). The following notations can be used:
R/W(*) Read/Write operation allowed in all states.

R/W(3) Read/Write operation only allowed in state 3.
R/W(2, 4 & 6) Read/Write operation allowed in state 2, 4 and 6.
R/W(2-5) Read/Write operation allowed in state 2 up to 5 (5 is included).
The “M/O” column (Mandatory/Optional) indicates if the data element must be supported/implemented by the OBC and any
controller devices controlling the OBC. “M” indicates that the data element must be supported, “O” indicates that the data element
is optional.
NOTE: All mandatory data elements must be supported/implemented for a device to be IFSF compatible and pass the
certifications.
The fields from 200 up to 255 of each data base are free to use by the manufacturer or the oil company.
4.2 COMMUNICATIONS
Independent to the state that the OBC is located, the OBC must respond always to all communications (read, write instructions and
commands) from the controller device.
Please note that the OBC will evaluate the write messages from left to right (compliant the IFSF STANDARD FORECOURT
PROTOCOL, PART II) and verify/validate all the data fields up to the first command field (included). All the data and command
fields after the first command field will be rejected either with „1 - Invalid value (too big / too small / not accepted)„ or „6 -
Command not accepted‟. In case no validation/consistency error is detected within the first part (up to the first command field),
than the first command will be executed. Meaning also, if any data field preceding the first command is rejected (Data
Acknowledge Status = 1, 3, 5 or 6), the command will not be executed, but however the valid data elements will be stored in the
database.
4.3 MAIN STATE

The state value of the main is stored in the OBC_State field of the „OBC‟ data base. All state changes are sent as an unsolicited
(without acknowledge) data array in the OBC_Status.
Page 13
STATES
5.1 STATE DIAGRAM
2
IDLE INOPERATIVE
[3] [1]
3
1
2
CLOSED
10 [2]
11
4
5
OPERATIVE
[4]
9 11
6
7
PROCESSING
(FILLING)
[5] 11
8
POCESSING
(BY THE L/V)
[6] 11
1. Automatically when: - No major error.

- Data bases are initialised.
2. OBC_SetUp command received.
3. OBC_ExitSetUp, OBCDD_Restart (Data Download) command received or major error occured.
4. OBC_Open command received.
5. OBC_Terminate command received.
6. Delivery accepted/started
7. Delivery completed, OBC_Terminate command received or minor error occured.
8. Filling by the level/volume.
9. Connection abolished or OBC_Terminate command received
10. Delivery accepted/completed command received.
11. Major error occured.
Page 14
5.2 STATE TABLE
STATE 1 2 3 4 5 6
EVENT INOPERATIVE CLOSED IDLE OPERATIVE FILLING FILLING BY
THE
LEVEL/VOLUM
INOPERATIVE # 1 1 1 1 1
OPERATIVE 2 # # # # #
DEL. STARTED - 4 - - - -
OBC.CONNECTED - - - 4 4
DEL. ACCEPTED - - - 5 4 4
IDLE(SET-UP) 3 3 - - - -
ACTIVATE - - # - - -
RESTART - - 1 - - -
EXIT IDLE - - 1 - - -
OPERATIVE - 4 - - -
DEL: REJ/COM - - - - 2 2
CON. ABOLISHED - - - - 4 4
STOP DISCH. - - - - 4 4
TERMINATE - - - 2 4 4
MAJOR ERROR # 1 1 1 1 1
MINOR ERROR # # # # 4 #
*** (OTHER) - - - - - -
Description:
# No state change.
n State change to n.
- Not applicable (state error).
NOTE: When an event occurs which puts the system in an inoperative state and this event is not defined in the document,
then the application must move or stay in the state which is defined in the 'INOPERATIVE' event. The above
defined 'INOPERATIVE' event (which is not defined in the state descriptions) should be considered as an
emergency break or fall back event.
Page 15
5.3 STATE DESCRIPTION
5.3.1 INOPERATIVE [1]
STATE DESCRIPTION
INOPERATIVE The OBC is in the INOPERATIVE state when it is not possible to function. The reason for
this is that essential operational data is missing or a major error has been detected. The OBC is
also in the INOPERATIVE state after a system boot and after an exit from the IDLE state.
While in the INOPERATIVE state the OBC should continuously run a self test to establish if
the device is still inoperative or if the device has been configured to allow it to operate.
EVENT DESCRIPTION
OPERATIVE When the OBC have been configured with the essential data to operate and no major errors are
detected, the OBC goes to the CLOSED state.
Action: The OBC sends the unsolicited data OBC_Status.

IDLE When the OBC_Set-Up command is received from a controller device, the OBC moves into
the IDLE state.

MAJOR ERROR If a major error event occurs, the OBC stays in the INOPERATIVE state.
Action: The OBC sends the unsolicited data OBC_Status and OBCEC_ErrMsg1.
MINOR ERROR If a minor error event occurs, the OBC stays in the INOPERATIVE state.
Action: The OBC sends the unsolicited data OBCEC_ErrMsg1.

*** In case of a command is sent which is not included in this event description, the command will
be rejected and the OBC stays in the same state.
Action: The OBC sends a „NAK - Command refused in this state‟.
Page 16
5.3.2 CLOSED [2]
STATE DESCRIPTION
CLOSED The OBC is completely configured and no major error has been detected. In this state, the OBC
is ready to operate, but, the OBC will not perform any delivery operation.
EVENT DESCRIPTION
IDLE When the OBC_Set-Up command is received from a controller device, the OBC moves into
the IDLE state.

OPERATIVE When the OBC_Open command is received from a controller device, the OBC moves into the
OPERATIVE state. This command must be issued to enable the OBC to perform delivery
operations.

MAJOR ERROR If a major error event occurs, the OBC moves into the INOPERATIVE state.
MINOR ERROR If a minor error event occurs, the OBC stays in the CLOSED state.

Page 17
5.3.3 IDLE[3]
STATE DESCRIPTION
IDLE The OBC is put into the IDLE state as a result of a OBC_SetUp command issued by the
controller device.
The IDLE state allows the controller device to write to the following data bases:
- OBCSC (SYSTEM CONFIGURATION)
- OBCDD (DATA DOWNLOAD)
- OBCEC (ERROR CODES)
EVENT DESCRIPTION
ACTIVATE When the OBCDD_Activate command (Data Download data base) is received from a
controller device, the OBC is forced activate and verify (when necessary) the downloaded data.

RESTART When the OBCDD_Restart command (Data Download data base) is received from a controller
device, the OBC is forced to restart the system.
Action: Before rebooting the system, the OBC must change the state to INOPERATIVE
and sends the unsolicited data OBC_Status.
EXIT IDLE When the OBC_ExitIdle command is received from a controller device, the OBC moves into
the INOPERATIVE state.

MAJOR ERROR If a major error event occurs, the OBC moves into the INOPERATIVE state.
MINOR ERROR If a minor error event occurs, the OBC stays in the IDLE state.

Page 18
5.3.4 OPERATIVE [4]
STATE DESCRIPTION
OPERATIVE In this state the OBC is waiting for a tank lorry to perform the delivery operations. Once a
delivery operation has been started, the OBC will follow the delivery operation up to the
completion.
In case of the filling by the level/volume event, then the OBC device should in this state
automatically enable the delivery by this mechanism.
EVENT DESCRIPTION
DELIVERY When no error occurred, the OBC moves into the OPERATIVE state.
STARTED
TERMINATE When the OBC_Terminate command is received from a controller device, the OBC is forced
to cancel the current operation, stop any operation follow-up (if applicable) and to move into
the CLOSED state.
Action: When the operation follow-up has been executed (if applicable), the OBC sends
the unsolicited data OBC_Status.
MAJOR ERROR If a major error event occurs, the OBC stops the delivery operation (if applicable, wait until it is
stopped externally) and moves into the INOPERATIVE state.
Action: When the operation has been stopped (if applicable), the OBC sends the
unsolicited data OBC_Status and OBCEC_ErrMsg1.
MINOR ERROR If a minor error event occurs, the OBC ejects the bank note (if applicable, wait until it is
removed) and stays in the OPERATIVE state.

Page 19
5.3.5 FILLING [5]
STATE DESCRIPTION
PROCESSING Check connection
The OBC will move to this state after that communication connection with the petrol station
has been established. The connection will be estabilished as soon as one of the following
switches will become active (on):
a) tank shutter switch is enabled by opening the tank lorry meter compartment door;
or
b) the first hose junction between a tank compartment of the tank lorry and the filling/vapour
rec. socket of the buried tank has been estabilished.
or
c) any other.
Connection estabilished
The OBC supports the communication protocol;
Action: the OBC sends. to the station node the function state “OBC_Connected”.
Electrical connection
The tank lorry does not have an OBC or the petrol station does not support the tank
lorry available protocol.
EVENT DESCRIPTION
OBC CONNECTED The OBC node reaches this condition when the connection with the PSC/TLG has been
succesfully made and until the the discharge has been completed.
After that the connection has been made the OBC and the PSC must ensure that the time-
critical condition are met until the end of the filling operations.
The OBC checks whether the right petrol station has been stopped at.
It also checks that:

the PSC is using the configuration variable “Tanks_Config”.
the OBC node transmit the variable “TKW_Config” and “TKW_Status” as
information report to the PSC.
The PSC writes in turn the variable “Tanks_Status”.
At that point in time the OBC node knows whether the PSC consents to the filling operation,
the available information to the tank lorry driver and possibly what function the tank gauge
desires or what function is ready (filling by level/volume, discharge protection control). After
that a discharge connection has been made, a check for connection with the ordered quality and
the order is made.
Upon a discharge operation completed, cheks will be made for the total order “Completely
_executed”. In case an additional discharge will be initiated.
For an invalid connection, the OBC waits until it is removed and moves into the OPERATIVE
state.
Action: When the invalid connection has been removed, the OBC sends the unsolicited
data OBC_Status.
Page 20
DELIVERY The tank lorry has stopped at the right petrol station.
ACCEPTED The petrol station is ready to accept the delivery:
The tank lorry has been notified that the hose connection between the lorry compartment and
the right tank has been estabilished in accordance with the ordered quality.
The station node driven by the PSC or by the TLG enters the function “Ready_for
_discharge”.
When a delivery accepted is recognised, the OBC moves into the FILLING state.
Action: The OBC sends the unsolicited data OBC_Status and OBC_Info.
DELIVERY Change in function state may happen for:
REJECTED/COMPL - Tank lorry stopped at wrong station;
ETED - Filling was rejected by the PSC;
- The tank lorry has executed the order totally or partially;
- Safety reasons interrupted the delivery.
- The PSC send the function state “Tank_lorry_may_leave_the_petrol_station”
Interruption of the connection sole hose connection

Action: Whether the sole connection to the tank lorry was interrupted the state emigrates
versus the function “Check_connection”.
When a delivery rejected/completed is recognised, the OBC moves into the CLOSED state.
Action: The OBC sends the unsolicited data OBC_Status and OBC_Info
READY FOR The PSC receives the information Report “Tank_Delivery” to unambigously address the due
DISCHARGE tank variable. The PSC then send the variable “Space_Available” for nornall filling or filling
by level/volume and additionally the variable “Gross specified volume”.
At the end the PSC writes the variable “Tank_Status”.
PERMITTED The petrol station and the tank lorry are ready for discharge.
DISCHARGE The OBC enters the function state “Discharge active”
NON-PERMITTED The petrol station or the tank lorry are not ready for discharge.
DISCHARGE The station node driven by the TLG or by the PSC enters the function state “Discharge stop”
Interruption of the sole hose connection:

DISCHARGE The tank lorry OBC continously checks its own safety devices and the specified values, in case
ACTIVE of availability.
The tank lorry OBC continously monitors an eventually stop request made by the PSC.
STOP DISCHARGE Filling is stopped by the tank lorry when:
The delivery to the specified tank has been completed;
The delivery for the connected tank compartment has been executed;
The tank compartment becomes empty;
The presetting and filling by the level/volume has been complied with;
The tank lorry discharge protection has answered;
HiHi level alarm warns from the tank gauge;
Other safety device from the tank lorry have send alarm messages;
PSC requires an emergency stop;
The available room has been exceeded, because the values from the tank gauging
are not plausible;
Data transmission between the devices are disturbed.
The station nodes then enters the function “Discharge_stop”

Discharge Stop
The tank lorry assesses the reason for stop the discharge.
Page 21
CONTINUE Change of the function state may happen for.
DISCHARGE a non permissible discharge is invalid;
filling of the connected tank by the level/volume is continued;
filling of the tank beyond the order is requested;
The station nodes driven by the PSC sends the request “Ready_for_discharge”
TERMINATE Terminate discharge
The filling will be terminated for:
The PSC dictates the discharge termination into a tank;
The tang gauge TLG has triggered the HiHi level alert;
Filling by the level/volume is completed;
The delivery order has been executed or the tank compartment is empty;
Lack of safety requires the discharge stop;
The function “Discharge terminated” will become active:
Interruption of the sole hose connection

Discharge terminated
The tank lorry or the petrol station have terminated the discharge operations.
The PSC may finally read the final level of the buried tank and will be notified by the OBC of
the delivered product quantity.
At that point in time, the connection between the OBC and PSC may be truncated.
When the OBC_Terminate command is issued, the OBC moves into the OPERATIVE state.
CONNECTION Any connection between the tank compartement and the station tank will be abolished.
ABOLISHED Transition to the function “OPEN” status will take place.
Interruption of the sole hose connection
TANK LORRY Communication between the OBC and PSC is no longer required. The tank lorry may leave the
LEAVES THE petrol station.
PETROL STATION
Action: When the communication has been removed, the OBC sends the unsolicited data
OBC_Status.
MAJOR ERROR If a major error event occurs, the OBC waits until it is removed and moves into the
INOPERATIVE state.
MINOR ERROR If a minor error event occurs, the OBC waits until it is removed and move into the
OPERATIVE state.
Page 22
5.3.6 FILLING BY THE LEVEL/VOLUME[6]
STATE DESCRIPTION
PROCESSING In this state the OBC will wait for instruction to start filling:
with specified values from the PSC
or
filling by the level/volume
EVENT DESCRIPTION
When this special filling will be issued the OBCwill wait for special instruction by the
PSC/TLG and the events will take place exactly as per the FILLING [5] case..
Page 23
6 DELIVERY DATA BASE
6.1 GENERAL
This part of the document details the standard data organisation for a Tank Lorry Delivery Application.
Every data element in the Tank Lorry Delivery data base is described in this chapter. The access to the data element is done by a
Data Base Address “DB_Ad” and a Data Identifier “Data_Id”.
DELIVERY CONTROL XXXX DATA BASE

DB_Ad = ....
Data_Id Data Element Name Field Type Read/Write in State M/O
Description (Name of the state
field)
The Data_Id is an unique identifier for a data element in a data base. The data base is defined by the data base address “DB_Ad”
(for details see document “Part II, Communication Specification”).
In the second column the name of the data element is defined. In this column is also the description of the data element.
The field types in the column three are described in chapter 0, page 25 of this document.
The “Read/Write in state” column indicates if the related data can be Read and/or Written by any device and which Tank Lorry
Delivery state (states are indicated between brackets). The following notations can be used:
R/W(*) Read/Write operation allowed in all states.

R/W(3) Read/Write operation only allowed in state 3.
R/W(2, 4 & 6) Read/Write operation allowed in state 2, 4 and 6.
R/W(2-5) Read/Write operation allowed in state 2 up to 5 (5 is included).
The “M/O” column (Mandatory/Optional) indicates if the data element must be supported/implemented by the Tanl Lorry
Delivery and any controller devices controlling the Tank Lorry Delievery. “M” indicates that the data element must be supported,
“O” indicates that the data element is optional.
NOTE: All mandatory data elements must be supported/implemented for a device to be IFSF compatible and pass the
certifications.
The fields from 200 up to 255 of each data base are free to use by the manufacturer or the oil company.
Page 24
6.2 DATA BASE OVERVIEW
OBC_ID
MAIN
OBCMC_ID MANUFACTURE
CONFIGURATION
OBCSC_ID SYSTEM
CONFIGURATION
OBCEC_ENTRY ERROR_ID
ERROR CODE
OBCDD_ID DATA
DOWNLOAD
6.3 OBC DATA BASE ADDRESSING

The different records described here are accessible through an address which is defined in the following way.
DELIVERY CONTROL DATA BASE ADDRESS DB_Ad

BYTE 1 BYTE 2 BYTE 3 BYTE 4 ... DATA BASE
COMS_SV Communication
00H Service
OBC_ID Main
01H
OBCMC_ID CNCY_ID Manufacturer
02H 01H-XXH1 Configuration
OBCSC_ID CNCY_ID System
03H 01H-XXH Configuration
OBCEC_ENTRY ERROR_ID Error
41H 01H-3FH Codes
OBCDD_ID Data
A1H Download
The following data bases must be stored in non volatile memory (the data may not be lost after a power down):
- Manufacturer Configuration.
- System Configuration.
- Error Codes.
NOTE: In case the „Communication Service‟ data base is stored in volatile memory, then the Tank Lorry Delivery must
send during the system boot a broadcast heartbeat2 message with bit 1 (configuration needed) of the
DEVICE_STATUS set. Also, the Tank Lorry Delivery must wait at least 8 seconds3 before moving from the
INOPERATIVE state to another state. This to give a controller device time to set-up the communication service
data base.
1
The maximum number is defined by the manufacturer
2
Ref.: Standard Forecourt Protocol, PART II, Communication Specification.
3
Ref.: Standard Forecourt Protocol, PART II, Communication Specification.
Page 25
6.4 FIELD FORMATS
FIELD FORMAT DESCRIPTION

BitX - X = number of binary bits, where X can be 8 (for one byte) or a multiple of 8.
The most right bit is the lowest bit and the bit numbering starts from 1.
Byte - Range value from 00H to FFH, where the most right bit is the lowest bit.
Bin16 - Range value from 0000H to FFFFH, where the most right bit is the lowest bit.
Bin24 - Range value from 000000H to FFFFFFH, where the most right bit is the lowest bit.
Bin32 - Range value from 00000000H to FFFFFFFFH, where the most right bit is the lowest
bit.
ByteX - X = number of bytes (see Byte).
Xbytes - Variable numbers of bytes (see Byte).
BcdX - X = number of bcd digits. X is an even number because two bcd digits are one byte
(e.g. Bcd4 are four bcd digits in two bytes).
AscX - X = number of ASCII bytes.
Cmd - Command with no data.
Sdpp - Sign and Decimal Point Position from left:
Bit8: 0 = positive value, 1 = negative value.
Bit7-1: decimal point position from left (0-127)
E.g.: SignDec + Bcd8
06 / 12 34 56 78 = 123456.78
0B / 12 34 56 78 = 12345678000
08 / 00 00 12 34 = 1234
Limit Sdpp + Bcd8 Transaction limit value.
Date Bcd8 YYYYMMDD
Example: 19950512 = 12 May 1995.
Page 26
6.5 MAIN
This database provides access to the OBC ID. This access to the main database is done by the database address OBC_ID
TANK DELIVERY APPLICATION DATA BASE

DB_Ad = OBC_ID (01H)
Description
1 OBC_State Byte R(*) M
Used to indicate the state of the OBC. The following
states will indicated:
01H INOPERATIVE
02H CLOSED
03H IDLE
04H OPERATIVE
05H FILLING
06H FILLING BY THE LEVEL/VOLUME
3 OBC_Switch Bit16 R(*) O
To allow the controller device to interrogate the status of
the switches (bit on, means switch on). A switch can be
used to control a light, slot, LED, shutter switch....
(manufacturer depended).
4 FPR_State Byte R(*) M
Used to indicate the main state of the communication
device. The following states will indicated:
1 = INOPERATIVE
2 = SET-UP
3 = IDLE
4 = ASSIGNED
5 = BUFFER FULL
6 = RELEASING
5 FPR_StationState Bit16 R(*) M
Used to indicate the state of the sub device and paper.
Bit 1 on Fiscal printer out of order.

Bit 2 on Fiscal printer low paper detected.
Bit 3 on Fiscal printer paper out.
Bit 4 on Fiscal printer paper jammed.
Bit 5 to 12 Reserved for future use.
Bit 13 on Slip printer out of order.
Bit 14 on No paper in slip printer
NOTE: In case a state is not supported (e.g. slip

printer), then the corresponding bit(s) will
be always off.
TANK DELIVERY OPERATION DATA

Global operating variables
Page 27
Description
21 Tank_status Bit16 R/W M
Describes the tank lorry function required by the PSC
The field is a structure consisting of:

Specification of the variable TANK-STATUS
bit 0 on Safety Discarge

All safety requirements are met by
the petrol station:
Discharge Permitted
bit 1 on Request Made
Request for delivery made
by the petrol station
bit 2 on Contact Controller
Prior to start the delivery contact the
petrol station manager
bit 3 on Leave_Ser_Station
Tank lorry may leave service station
bit 4 on Hig_Level_Alarm
The max safe filling level reached
for a tank
bit 5 on Dispensing Active
Tank gauge alarms while filling by
the level/volume for at list one tank
bit 6 on Filling Active
Tank gauge alarms at least one tank
while filling by the level/volume
bit 7 on Disch_Prot_Act
tank gauge is ready to monitor the
discharge operation to allow the
protection function to operate.
Page 28
Description
22 Tank_Config Bit16 R/W M
Describes the technical device of the tank lorry

Specification of variables Delivery Configuration
bit 0 on Quality Assurance

Not active or not ready for
operation, not available, or defective
bit 1 on: Discharge Hose prot.
bit 2 on: Discharge protection
bit 3,4 Coding communication
path:
00 = radio link;
01 = hose;
10 = GWG connection;
11 = infrared.
bit 5 free
bit 6 free
bit 7 Coding Counter
mechanical or electronic counter
bit 8 - 12 Coding Compensation
0000 = no counter;
0001 = without compensation;
0010 1111 = value of the C°
compensation
bit 13 on Tank Gauge Discharge
Monitoring
Tank lorry will support
discharge monitoring
function
bit 14-15 free
23 Filling_Protection. 0 - 99999 R O
Describes the filling protection option for the OBC/PSC.
Page 29
Description
24 Petrol_Station_St Bit8 R/W M
Describes all petrol station function required by the tank
lorry.

Specification of variable “Petrol_Station_St”
bit 0 on OK_Discharge
All tank compartment ready for
discharge
bit 1 on Trans_In_Prog
. Active when discharge takes place
bit 2 on Faucet_Guard_Bar_St
All valve locked
bit 3 on Sealed_Parcel_Ok
In all tank compartments, the
gauged volume loaded is
complete
bit 4 on Tamper_Warning
Indicate violation of one of the
criterions of tampering for tank
compartment
bit 5 on Order_Completed
Indicate that the delivery for the
petrol station is completed
bit 6 on Cops_Warning
Alarm the mixing danger for one
delivery hose ???
bit 7 on Vapour_Recovery_Warn
. The vapour return hose present a
mulfunctioning
bit 8 on OBC_St_Fail
The OBC does not operate properly
bit 9 on Tractor_Trailer_Con
Indicate the state of the connection
between the tractor and the trailer
bi1 10 on Tank_Gauge_Protection
The tank lorry OBC request the
tank gauge assistence for operating
discharge protection
bit 11on Tank_Gauge_Disc._Def.
Indicate problems connected with
the data tank-gauging and whether
tank gauge monitoring has been
required, the delivery must be
stopped or not started.
bit 12.15 free
25 Compart_num Bit16 R M
Number of compartments in the tank lorry
26 Volume_Num Bit16 R M
Number of volume meters in the tank lorry
Page 30
Description
27 Change_St Bit4 R/W M
Command to change of the status of the reuter
communication device.
00 = terminate
01 =deactivate
10 = set idle state
11 = close
28 Free
Position free for the customer.
50 Truck_Com Asc10 R O
Truck Company
51 Truck_Haul Asc10 R O
Truck hauler id.
52 Tractor_Id Asc16 R O
Identification of the truck; read from truck mounted tag
on arm coupling into black box
53 Driver_id Asc10 R O
Identification of the driver
54 Comptm id Asc10 R O
Compartment identification; read on truck mounted tag
on arm coupling, into black box
55 Product id Asc10 R O
Identification by arm???
56 Prod Litres @ Ambient Asc10 R O
Meter pulses counted by measurements device
57 Prod Litres @ 15° Deg C Asc10 R O
From W&M device
58 Prod temp Asc10 R O
59 Prod mass Asc10 R O
60 Prod weight Asc10 R O
61 Prod density Asc10 R O
62 Batch id Asc10 R O
Generated by system
62 Date Asc10 R O
Of loading
63 Time Asc10 R O
End of loading
64 Meter id Asc10 R O
65 Terminal id Asc10 R O
66 FRT_DType Byte R/W M
This Data_Id is used to select the data type to be printed
(see also FPRMC_DType).
67 FPR_Font Byte R/W M
This Data_Id is used to select the font (see also
FPRMC_Font).
68 FPR_DfltData Byte R/W M
This Data_Id is used to select the default data buffer to
be printed. The range is from 1 to 4 (see also
FPRSC_DfltDataX, 1 = data of field 1 of the FPRSC
data base).
69 FPR_Data Xbyte R/W M
This Data_Id is used to write the data to be printed to the
printer station(s). The controller device can write from 1
to 255 characters/bytes of printable data. The PRT is
responsible for automaticaly handling line returns where
the data is longer than the printer width.
Page 31
Description
70 Digits_Unit_Price Bcd2 R(1-9) O
W(1-2)
Configure layout of the Unit Price field.
LNIB = unit price display field length

HNIB = decimal point position left justified
Please note that OBC may be loaded with this Data_Id

by
- remotely by Depot system.
- manually by the driver, who must set the Data_Id to
the hardcoded value.
70bis Unit_Price_Mult_Fact Bin8 R(1-9) O

W(1-2)
Specifies the multiplication factor (ten to the power of
x = 10 x ) between the displayed Unit Price value and
the Unit_Price field.
The range of the field is: +/-, 0-9.
bit8: = 0 -> positive

= 1 -> negative
bit4-1: = 0 - 9
LOCAL CONFIGURATION VARIABLES

30 Tank_Id Asc5 R/W M
Identification of the petrol station tanks
31 Product_Code Bit256 R/W M
Product code according to the company ref-table
32 Product_Des Asc16 R/W M
Designation of the product
33 Product_des Asc12 R/W O
Description of the product
34 Tank_Feat 0 - 99999 R/W O
Describes the tank feature of the in use tank.
The OBC can use these description to assign the filling
level/volume whether a tank level is not known.
35 Max_Volume 0 - 99999 R/W O
Indicate the maximum volume that the tank can safely
accomodate
LOCAL OPERATING VARIABLES

The local operating variables refer to the individual buried tanks of the petrol station or to the individual compartments
of the tank lorry.
The petrol station variables are loaded into the PSC (petrol station console) and may be read by the OBC, while the
OBC variables may be read by the PSC.
LOCAL OPERATING VARIABLE
Page 32
Description
71 Tank_Status Bit8 R/W M
The variable is generated by the PSC according to the
tank status

Specification of variable “Tank Status”
Bit 0 on Ok_To_Disch.
Permission to filling the indicated
tank
bit 1 on HI_HI_Level_Alarm
The maximum allovable level has
been reached
bit 2 on HI_Level_Alarm
The maximum allovable level is
quite reached
bit 3 on Lo_Level_Alarm
The minimum allovable level is
(nearly) reached
bit 4 on Delivery_Request
Made request or heach tank
bit 5 on Exceeding_Permitted
Permission to fill beyond the
delivery quantity
bit 6 on Filling_by_Level/Volume
Tank lorry OBC requires that the
tank will be filled by the
level/volume
bit7 on Filling_by_Level/Volume
The tank lorry OBC fills the tank
by the level/volume
72 Total_Volume 0 - 99999 R/W M

Indicates the total volume of each individual tank
(sediment and water included)
73 Available_Volume 0 - 99999 R/W M
Indicates the free space that can still be filled into the
tank.
74 Product_Temp 0 - 99999 R/W O
Mean product temperature with the precision of the
1/10°C
75 Product_Density 0 - 99999 R/W O
Mean product density in Kg/cm3 related to +15°C
76 Gross_Vol._To_Disch. 0 - 99999 R/W O
Indicate the requested quantity by the OBC or by the
PSC when the filling by level/volume is required.
77 Net_Vol_To_Disch. 0 - 99999 R/W O
Indicate the amount (related to 15°C) requested by the
OBC or by the PSC for a tank when filled normally or by
the level/volume
78 Deliv._Gross_Vol. 0 - 99999 R/W O
Indicate volume delivered by the tank lorry after
discharge
79 Deliv._Net_Vol. 0 - 99999 R/W O
Indicate the volume deliverd by the tank lorry, related to
15°C. Indication in level/volume
Page 33
Description
81 Compartment_Status Bit16 R M
The variable is generated by OBC according to the tank
compartment status
Specification of variable
“Tank_Compartment_Status”
Bit 0 on OK_Discharge
The tank compartment is ready for
discharge
bit 1 on Trans_In_Prog.
Active when discharge takes place
from the indicated compartment
bit 2 on Discharge_Stop
bit 3 on Discharge_Finished
bit 4 on Sealed_Parcel_Ok
The tank compartments still contains
the complete volume filled by the
level/volume
Indicate violation of one of the
criterions of tampering for tank
compartment
bit 6 on Manual_Entry_Of_Qty
Indicate that the tank quantity was
inserted manually
bit 7 on Compartment_Empty
Alarm that tank compartment is
empty
bit 8 on Preset_Value_Reached
Active when product is filled by
level/volume
bit 9 on Discharge_Beyond_Order
Active when the discharge hose is
connected to tank containing other
product
bit 11 on As_Warning
Active when discharge
protection will be activated during
filling
bit 12 on Ass_Warning
Active when the discharge hose
protection will be activated
during filling
bit 13 on Vapour_Recovery_Warn
. The vapour return hose present a
mulfunctioning
bit 14 on Meter_Warning
Alarm the meter instrument
malfunctioning
bit 15 on Not assigned
Page 34
Description
82 Product_Code Bit256 R M
Indicates the product code as reported by the
general list
83 Product_Designation Asc5 R M
Indicates the product designation code as
reported by the general list.
84 Connected_Tank_Id Bit256 R M
Identifies the buried tank connected to the
lorry compartment
85 Gross_Vol._ 0 - 99999 R O
Indicate the quantity of the tank
compartmennt (in level/volume)
86 Net_Vol 0 - 99999 R O
Indicate the amount (related to 15°C) in the
tank compartment
COMMANDS
90 OBC_Setup Cmd W(1-3) M
Forces the OBC to move to the „IDLE‟ state.
91 OBC_ExitSetup Cmd W(2) M
Forces the OBC to move to the „INOPERATIVE‟ state.
92 OBC_Open Cmd W(3) M
Forces the OBC to move to the „OPERATIVE‟ state.
93 OBC_Connected Cmd W(6) M
Forces the OBC to move to the „FILLING‟ state.
94 OBC_Terminate Cmd W(6) M
Forces the OBC to move to the „CLOSED‟ state.
95 OBC_Check_Connection Cmd W(6) M
Forces the OBC to stop the discharge and to wait until
the stop has been removed and to move to the „OPEN‟
state.
96 OBC_SwitchOn Bit16 W(4-6) M
Forces the OBC to set on the selected (one or multiple
bits on) switch(es).
NOTE: A write to this field must be considered as a

request to execute the command.
97 OBC_SwitchOff Bit16 W(1-6) O
Forces the OBC to set on the selected (one or multiple
bits on) switch(es).
NOTE: A write to this field must be considered as

a request to execute the command.
98 FPR_PrintData Cmd W M
Forces the MT to print the data (see FPR_Data).
99 FPR_FF Cmd W M
Forces the OBC to execute a form feed.
100 FPR_Release Cmd W M
Forces the OBC to move to the „RELEASING‟ state
Page 35
Description
UNSOLICITED DATA
101 OBC_Status Byte M
This status message (= OBC_State)must be sent
unsolicited (without acknowledge) by the OBC when
ever a change has occurred in the OBC_State.
102 OBC_Info Byte M
This message (= OBC_Note) must be sent unsolicited + Bin16
(without acknowledge) by the OBC before the state + Asc3
change from „PROCESSING‟ state to the „DELIVERY + Bin24
ACCEPTED‟ state.
103 OBC_FKeySignal Byte O
This message must be sent unsolicited (with
acknowledge) by the OBC when ever a key is pressed .
01H to 7FH Reserved for IFSF.
80H to FFH Reserved for manufacturers.
104 FPR_Status Byte M
This status message must be sent unsolicited (without +Bit16
acknowledge) by the MT when ever a change has
occurred in the FPR_State or in FPR_StationState.
Byte FPR_State
Bit16 FPR_StationState
201 OBC_Polling Bytes 12 R O
acknowledge) by the OBC to identify the petrol station
devices
202 OBC_LevelRequest Bytes 12 W O
acknowledge) by the OBC to request the station tank
topology and data
203 OBC_SalesRequest Bytes 12 W O
acknowledge) by the OBC to start product sales
accumulation during the discharge by the PSC
204 OBC_EndDischarge Bytes 12 R O
acknowledge) by the OBC the communicate to the
station devices the discharge end
205 PSC_DischargeRequest Bytes 12 R O
acknowledge) by the PSC to request all discharge data
206 OBC_StationReset Bytes 12 R O
acknowledge) by the OBC to reset all involved station
devices at the end of the discharge
Page 36
6.6 MANUFACTURER CONFIGURATION

This database provides access to the OBC Configuration data. This access to the main database is done by the database address
OBCMC_ID
TANK LORRY DELIVERY MANUFACTURER CONFIGURATION DATA BASE

DB_Ad = OBCMC_ID (02H)
Description (OBC_State)
1 OBCMC_Manufacturer Asc3 R(*) M
To allow the controller device to interrogate the
manufacturer identity.
2 OBCMC_Model Asc3 R(*) M
To allow the controller device to interrogate the model.
3 OBCMC_Type Asc3 R(*) M
To allow the controller device to interrogate the type.
4 OBCMC_Country Bcd4 R(*) M
Country where the OBC device is installed. This
contains the international ISO 3166 (with leading zero‟s)
for the country where it is installed.
0000 Country independed.
> Country depended.
5 OBCMC_SerialNo Asc12 R(*) M
To allow the controller device to interrogate the serial
number.
6 OBCMC_ProtocolVersion Asc12 R(*) M
To allow the controller device to interrogate the version
number of the protocol application software.
7 OBCMC_SoftwareVersion Asc12 R(*) M
To allow the controller device to interrogate the version
number of the main application software.
12 OBCMC_SupportedSwitches Bit16 R(*) M
To allow the controller device to interrogate the number
of supported switches (bit on means supported). The
functionality of switches are manufacturer depended.
13 FPRMC_Manufacturer Asc3 R(*) M
To allow other devices to interrogate the manufacturer
identity.
14 FPRMC_Model Asc3 R(*) M
To allow other devices to interrogate the model.
15 FPRMC_Type Asc3 R(*) M
To allow other devices to interrogate the type.
16 FPRMC_Country Bcd4 R(*) M
Country where the PRT device is installed. This contains
the international phone dialling code (with leading
zero‟s) from the country where it is installed.
0000 Country in-depended.
> Country depended.
17 FPRMC_SerialNo Asc12 R(*) M
To allow other devices to interrogate the serial number.
18 FPRMC_ProtocolVersion Asc12 R(*) M
To allow other devices to interrogate the version number
of the protocol application software.
19 FPRMC_SoftwareVersion Asc12 R(*) M
To allow other devices to interrogate the version number
of the main application software.
Page 37
TANK LORRY DELIVERY MANUFACTURER CONFIGURATION DATA BASE
DB_Ad = OBCMC_ID (02H)
20 FPRMC_DType Bit8 R(*) M
To allow other devices to interrogate the supported
format.
Bit 1 on ASCII (all printable charareters from 20H
to 7EH and the 0AH, 0DH control
characters).
Bit 2 on Graphics/Bit map.
Bit 3 on Security Telegram.
21 FPRMC_Font Bit8 R(*) M
To allow other devices to interrogate the supported font
of the printable data.
Bit 1 on Normal.
Bit 2 on Bold.
Bit 3 on Double width.
Bit 4 on Double Hight.
Bit 5 on Underline.
Bit 6 on Centralise.
22 FPRMC_Columns Byte R(*) M
To allow other devices to interrogate the maximum
number of columns of one line.
6.7 SYSTEM CONFIGURATION

This database provides access to the OBC System Configuration data. This access to the main database is done by the database
address OBCSC_ID
TANK LORRY DELIVERY SYSTEM CONFIGURATION DATA BASE

DB_Ad = OBCSC_ID (03H) + [ CNCY_ID (01H-XXH) ]
LOCAL CONFIGURATION VARIABLES
11 Tankst_Confg Bit8 R/W M

The byte describes the petrol station equipment
significant for the tank station;
12 Tank_Num Bit256 R/W O

Number of tanks supported by tank gauge
13 Product_Num Bit16 R/W O

Number of different product whose level is measured
14 Sys_Time Char12 R/W O

System time as YYMMDDhhmmss.
15 Softw_Inst_Datum Char12 R/W O

Date of installation of software in the device.
16 Personal-Ident. Char14 R/W O

Identification of software installer.
17 Petrol_Num Asc14 R/W M

Petrol station number
Page 38
TANK LORRY DELIVERY SYSTEM CONFIGURATION DATA BASE
DB_Ad = OBCSC_ID (03H) + [ CNCY_ID (01H-XXH) ]
18 Petrol station name Asc30 R/W M
Name of the company managing the petrol station
19 Address Asc30 R/W M

Address of the petrol station. street

Address of the petrol station: city

Address of the petrol station: country, area
22 Customer_name Asc30 R/W M

Name of the customer
23 Emerg_contact Asc24 R/W M

Emergency contact
24 Prod_Price Unit_ R(1-9) O
Price W(1-9)
Specifies the product Unit Price.
Please note that a write can occur to this Data_Id in
any state. However, the new value will only become
active when the FP next goes into states 1 to 5.
24 FPRSC_DfltData1 Byte3 R(*) M
To allow to configure the first default data buffer. This +Xbytes W(2)
buffer can be used to store header or footer data.
Byte Data type (See FPRMC_DType).
Byte Color (See FPRMC_Color).
Byte Font (See FPRMC_Font).
Xbytes Printable data (from 1 to 255 bytes).
To allow to configure the second default data buffer. +Xbytes W(2)
See also above.
To allow to configure the third default data buffer. +Xbytes W(2)
See also above.
To allow to configure the fourth default data buffer. +Xbytes W(2)
See also above.
Page 39
6.8 ERROR CODES

This data allows the CD to handle the error data from a OBC. The access to the error data is done by the database address
OBCEC_ENTRY + ERROR_ID. The OBCEC_ENTRY = 40H is used to ask for all error code data. Please note that the OBC
should return all error codes supported (this means, that all error types listed below must be sent).
TANK LORRY DELIVERY ERROR CODE DATA BASE

DB_Ad = OBCEC_ENTRY (41H) + ERROR_ID (01H-3FH)
ERROR DATA
1 OBCEC_Type Byte R(*) M
Every error has a unique error code. This number is the W(2)
same number as used in the address ERROR_ID of this
data base.
A list off all errors is at the end of this table.
An unsolicited message is generated by the OBC when a
major or minor error occurs.
2 OBCEC_Description Asc20 R(*) O
Description of the error. W(2)
3 OBCEC_Total Byte R(*) M
Total of error having that code. If more than 255 errors W(2)
are counted, the value remains 255. When a value is
written in this field, the total is cleared and the date is
recorded.
5 OBCEC_ErrorState Byte R(*) M
Specifies the OBC state during which the latest error
(with the selected ERROR_ID) occurred. The OBC state
numbering described in chapter 0, page 13 are used.
6 OBCEC_ErrorOriginator Byte R(*) O
Specifies the OBC originator data base address during + Byte8
which the latest error (with the selected ERROR_ID)
occurred.
The following address is valid:

Byte Length of the data base address.
Byte8 Data base address of the originator.
UNSOLICITED DATA
100 OBCEC_ErrMsg1 Byte M
This message must be sent unsolicited (without + Byte
acknowledge) when ever an error occurs.
The field is structure consisting of:
Byte OBCEC_Type
Byte OBCEC_ErrorState
NOTE: This field will always be used by this

application.
Page 40
TANK LORRY DELIVERY ERROR CODE DATA BASE
DB_Ad = OBCEC_ENTRY (41H) + ERROR_ID (01H-3FH)
101 OBCEC_ErrMsg2 Byte O
This message must be sent unsolicited (without + Byte
acknowledge) when ever an error occurs. + Byte9
Byte OBCEC_Type
Byte OBCEC_ErrorState
Byte9 OBCEC_ErrorOriginatior
NOTE: This field will not be used by this

application (this application has no
multiple states).
Classification ERROR_ID Description.

MAJOR ERROR 01H RAM defect.
02H ROM defect.
03H Configuration or parameter error.
04H Power supply out of order.
05H Main communication error.
06H Main communication error.
07H Device not available.
08H Printer ribbon error.
09H Paper jammed.
0AH Paper out (fiscal).
0BH Time-out.
0CH Mechanical failure.
0DH-1FH Spare
MINOR ERROR 20H Error (general purpose).
21H Power supply error.
22H Communication error.
23H Consistency error.
24H Too few parameters.
25H Illegal request.
26H Reception Error
27H Transmit error
28H Paper low
29H No paper
2AH-3FH Spare.
Page 41
6.9 DATA DOWNLOAD
TANK LORRY DELIVERY DATA DOWNLOAD DATA BASE

DB_Ad = OBCDD_ID (A1H)
DOWNLOAD DATA
1 OBCDD_Type Byte W(2) O
Identifies the type of data to be downloaded.
2 OBCDD_Block Bin24 W(2) O
Identifies the data block within the software program.
3 OBCDD_Address Bin32 W(2) O
Specifies the start address where the first byte from the
OBCDD_Data field must be downloaded.
4 OBCDD_Size Bin16 W(2) O
Specifies the number of bytes which are downloaded by
the OBCDD_Data field.
5 OBCDD_Data Xbytes W(2) O
Contains the data to be downloaded. The length of this
field is maximum 1 Kb (size allocated to communication
buffers).
6 OBCDD_Checksum Byte8 W(2) O
Depending on the requirements, this can be checksum,
MAC, ... which has to be calculated and verified.
DATA DOWNLOAD COMMANDS

80 OBCDD_Activate Cmd W(2) O
This command activates and verifies the downloaded
data.
81 OBCDD_Restart Cmd W(2) O
This command restarts the OBC application to activate
the new software.

Part 3 11 Deliverycontrolapplicationv1.06

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

Part 3 11 Deliverycontrolapplicationv1.06

Uploaded by

Copyright:

Available Formats

IFSF

COPYRIGHT AND INTELLECTUAL PROPERTY RIGHTS STATEMENT

USE OF COPYRIGHT MATERIAL

the content of this document; or

Name Company Tel/Fax

Date Version Modifications

1.1 DEFINITIONS AND ABBREVIATIONS

DEFINITION ABBREVIATIONS DESCRIPTION

1.2 INTRODUCTION TO THE DELIVERY CONTROL PROTOCOL

1.3 FILLING OPERATION (known mode)

1.4 FILLING BY THE LEVEL/VOLUME (blind mode)

1.5 CLASSIFICATION OF THE TANK LORRY DEVICE

1.6 DELIVERY CONTROL PROTOCOL: STATUS DESCRIPTION

2 INITIALIZATION OF THE DELIVERY CONTROL

2.1 STARTING OPERATION OF THE DELIVERY CONTROL: INITIALIZATION

3 PROCESS FLOW CHART

Lorry reaches the

3.2 COMMUNICATION RELATIONS

3.3 SPECIAL OPERATING STATES

3.1 Check Connection and id of the tank lorry at depot

Tank lorry connected

Tank lorry leaves the depot

3.2 Check Connection and id of station tank to be refilled

Tank lorry connected

Ready for discharge

Tank lorry leaves petrol station

R/W(*) Read/Write operation allowed in all states.

4.3 MAIN STATE

5.1 STATE DIAGRAM

1. Automatically when: - No major error.

5.2 STATE TABLE

5.3 STATE DESCRIPTION

5.3.1 INOPERATIVE [1]

Action: The OBC sends the unsolicited data OBC_Status.

Action: The OBC sends the unsolicited data OBC_Status.

Action: The OBC sends the unsolicited data OBCEC_ErrMsg1.

Action: The OBC sends a „NAK - Command refused in this state‟.

5.3.2 CLOSED [2]

Action: The OBC sends the unsolicited data OBC_Status.

Action: The OBC sends the unsolicited data OBC_Status.

Action: The OBC sends the unsolicited data OBCEC_ErrMsg1.

Action: The OBC sends a „NAK - Command refused in this state‟.

Action: The OBC sends the unsolicited data OBC_Status.

Action: The OBC sends the unsolicited data OBC_Status.

Action: The OBC sends the unsolicited data OBCEC_ErrMsg1.

Action: The OBC sends a „NAK - Command refused in this state‟.

5.3.4 OPERATIVE [4]

Action: The OBC sends the unsolicited data OBCEC_ErrMsg1.

Action: The OBC sends a „NAK - Command refused in this state‟.

5.3.5 FILLING [5]

It also checks that:

Interruption of the connection sole hose connection

Interruption of the sole hose connection:

The station nodes then enters the function “Discharge_stop”

Interruption of the sole hose connection

Action: The OBC sends a „NAK - Command refused in this state‟.

5.3.6 FILLING BY THE LEVEL/VOLUME[6]

Action: The OBC sends the unsolicited data OBC_Status.

6 DELIVERY DATA BASE

DELIVERY CONTROL XXXX DATA BASE

R/W(*) Read/Write operation allowed in all states.

6.2 DATA BASE OVERVIEW

6.3 OBC DATA BASE ADDRESSING

DELIVERY CONTROL DATA BASE ADDRESS DB_Ad