In loading the Tagging structure, it might be best to use the 0xFF Command as each Tag can be individually added as this sort of this is a regular occurrence.The map will be maintain by the WEB DB and it will manage the use of the structure for each of the Tags.
Memory
Map Concept |
|
|
|
|
Description |
Starting @ |
Ending @ |
#ofBytes |
QTY |
Setup Config
Data |
0x000000 |
0x0003E8 |
1000 |
1000 characters |
GAP |
|
|
500 |
|
Tag Structure
(12 Bytes) |
0x0001FA |
0x0034BC |
12000 |
1000 Tags |
GAP |
|
|
50 |
|
Attendant info |
0x0034EE |
0x003782 |
660 |
30 Attendant |
GAP |
|
|
50 |
|
Driver info |
0x0037B4 |
0x004114 |
2400 |
100 Drivers |
GAP |
|
|
50 |
|
Vehicle info |
0x004146 |
0x00BE46 |
|
1000 Vehicles |
GAP |
|
|
50 |
|
Account info |
etc |
etc |
|
|
GAP |
|
|
50 |
|
Stock items |
etc |
etc |
|
|
GAP |
|
|
50 |
|
Transaction
Queue |
etc |
etc |
|
|
This is the most important table in managing the Tags as this is where the Tag is identified and the direction on what to do with it indexes from here
Tag
Structure (sample) |
|
|
|
|
|
Tag CRC (1 byte) |
Tag # (6Bytes) |
TagType (1 Byte) |
Status (1Byte) |
MemoryIndex(3Bytes) |
Total Bytes |
0x8C |
00006545BC30 |
A,D,V |
Active/ Blocked |
0x01240F |
12Byte |
|
|
|
|
|
|
All this tables below are best managed by have a replication on the Web DB
Att info |
|
|
|
|
|
|
|
|
|
|
|
Att name (12 Bytes) |
Employer # (6 Bytes) |
Rights (1byte) |
Total Bytes |
|
|
|
|
|
|
|
|
John Smith |
123456 |
1 |
20 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Driver info |
|
|
|
|
|
|
|
|
|
|
|
Driver name (12 Bytes) |
Employer # (6 Bytes) |
Rights (1byte) |
PIN (2Bytes) |
Total Bytes |
|
|
|
|
|
|
|
Harry Smith |
123456 |
1 |
1234 |
21 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Vehicle Info |
|
|
|
|
|
|
|
|
|
|
|
Veh Reg (10Bytes) |
AccountCode(4) |
Description (15Bytes) |
Fueling Mode(1byte) |
Rights(1byte) |
Fuel Grade(1byte) |
Tank Cap |
HrsBetwFills |
AllocatedMoney |
AllocatedLitres |
AllocateINDays |
Total bytes |
GFH456GP |
045DC6BC |
Blue Nissan Van |
1 |
1 |
0 |
50 |
24 |
0 |
200 |
30 |
38 |
|
|
|
|
|
|
|
|
|
|
|
|
Account Info |
|
|
|
|
|
|
|
|
|
|
|
AccountCode (4Bytes) |
Accname (15) |
Type (1 bytes) |
Authorization Level |
Total Bytes |
|
|
|
|
|
|
|
045DC6BC |
Sugar
Farm |
1 |
0 |
21 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Type |
1-
Internal 2- External Contractor 3 –
Prepaid 4- Cash etc |
|
|
|
|
|
|
|
|
Authorization
Level |
0-No
Limit 1-Local 2-Web |
|
|
|
|
|
|
|
|
|
Stock items |
|
|
|
|
|
|
|
|
|
|
|
Stock Code(6ytes) |
BarCode (14Bytes) |
Description (20Bytes) |
Price (6 bytes) |
VatCode (1byte) |
|
|
|
|
|
|
|
123456 |
04009900376570 |
Fanta Orange 330ml |
12.55 |
A |
|
|
|
|
|
|
|
The Vehicle Structure should 38 Bytes and it needs to have a Tank Capacity and HBF (Hour between Fills) with Allocation per Period and Money & Liter limits.If the Vehicle is allowed 200 liters per week and it has a Tank Capacity of 50 Liters, then for the last 7 days, it will check in the Transaction log, how many liters has the vehicle acquired and if there is still liters available, then it will allow fueling but not more than Tank capacity per fill (Actually this is controlled by the Fuelling Rights