The Memory Map must cater for storing the Fueling Sequence.
There are many possible vehicle
identification systems that we have a more could be added in the future and
each might be enough to identify the vehicle or a combination of technologies.
Like the Camera system could report the Vehicles Registration presence in the
Fueling Bay and the NRT could be used with that.
The LCD will indicate
immediately if the vehicle is detected by displaying the Registration and will
prompt for the next FUELING SEQUENCE’s required. E.g. Driver Tag please! - on the next LCD line.
Ideally we like this to be flexible;
E.g.1 Do we start the vehicle from the Nozzle System's RFID tag read only or do we use the RFID Tag read on the MID and then only ask for the Odometer to start fueling
E.g.2 Do we use Camera Recognition to identify the Vehicle and ask for an Attendant.
So these are rules that control the sequence of whats needed for an authorization to occur.
|
FuelingActionSeq
|
Action1
|
Action2
|
Action3
|
Action4
|
|
Type1
|
Get
Vehicle Tag
|
Get
odo/
HourMeter
or both
|
Get
Driver
|
Get
Web Auth Query/ Start Pump
|
|
Type2
|
Get
Vehicle Tag
|
Get
Driver
|
Get
Driver PIN#
|
Get
Web Auth Query/ Start Pump
|
|
Type3
|
Get
Vehicle Tag
|
Get
Driver PIN#
|
Get
Attendant
|
Start
Pump
|
|
Type3
|
Get
Vehicle Tag
|
Get
Web Auth
|
Get
Attendant
|
Start
Pump
|
NB: The Vehicle Tag - should be Vehicle Identification TYPE as this could be identified by Camera, NRT or RFID
Command Code [0x0E] - reserved for this function, but the nature of how it is Stored still needs more clarification
Locked
