Fuel calibration, reading the chart, and making sense of trips
Calibrate the fuel sensor in the FleetCommando UI, learn to read the fuel chart, walk through a real fill-up step-by-step, and understand the difference between trips, replays, and the trips list on a driver's profile.
1. What the fuel calibration is for
GPS trackers report fuel as raw sensor counts, not litres. The calibration tells FleetCommando: "raw value X means Y litres." Without it, the dashboard cannot tell you "65 L remaining" or "burned 18 L on this trip" — every fuel chart and trip burn number would be guesses.
Calibration is per-vehicle (each truck's sensor has its own quirks) and two numbers:
- Offset — the raw reading the sensor produces when the tank is empty. Sets the bottom anchor.
- Scale — how many litres each raw count above the offset is worth. Sets the slope.
You almost never type these numbers by hand. The UI guides you through a two-step wizard at the filling station and stamps both values for you.
2. The fuel calibration card — UI tour
Open Vehicles → pick a truck → Fuel tab. The card called Fuel sensor calibration is the cockpit. From the top:
- Current values — your saved scale and offset. The first time you open a freshly added truck both are blank; the chart will say "calibration required".
- Suggest from history — if the truck has been reporting for at least a week, FleetCommando reads the raw sensor distribution and proposes a calibration based on percentile statistics. Click Suggested to see the proposed scale + offset and the litre values the sensor's typical near-full reading would translate to. Hit Apply to save, or Edit first to nudge before saving.
- Calibrate as empty (orange) — use this when you're standing at the truck, you've physically confirmed the tank is empty, and you want the dashboard to start reading 0 L. This is step 1 of 2 for the standard filling-station calibration.
- I refueled this truck — fit the scale (gold, appears under the step-1 banner) — step 2 of 2. After step 1, you fill the tank, type how many litres the pump added, and click Apply. The system computes the slope that makes the new sensor reading match the litres you added.
- Sensor reading is wrong (blue) — for trucks that aren't empty but the sensor is lying ("we know it has ~210 L right now but the dashboard says 353 L"). You enter the real level; the system anchors the sensor there. Same engine, different target.
- Apply to history — replays the current calibration over a window of past readings. Fixes the fuel chart and trip burn numbers retroactively. Useful after you discover an older calibration was wrong.
3. Real-case scenario — calibrating at the filling station
This is the walk-through to do once per truck, ideally on the day you install the tracker. After it's done the sensor will read true litres for the life of the install (re-calibrate only if the LLS probe is replaced or the tank is re-sized).
What you need
- The truck at the pump, engine off.
- The vehicle's tank capacity entered in FleetCommando (Vehicles → edit → Fuel tank capacity (L)). Calibration is blocked without it.
- A phone or laptop signed in to FleetCommando with vehicles.write permission.
- A pump that can fill the tank to full and prints / shows the litre count for the fill (every filling station does — the receipt is the proof).
Step 1 — run the tank dry (or close to it)
- Drive the truck until the tank is as empty as you safely can. Most operators do this on the morning of the calibration — last delivery of the previous day ends near a pump, truck is parked overnight roughly empty.
- Park at the pump with the engine off and the ignition off. Wait ~60 seconds so the fuel-level sensor's reading settles (LLS probes oscillate while fuel sloshes).
Step 2 — anchor the sensor at empty (UI)
- Open the truck on your dashboard: Vehicles → tap the truck → Fuel tab.
- On the Fuel sensor calibration card, click Calibrate as empty.
- A confirm dialog appears asking you to confirm the tank is physically empty. Confirm. The system records the current raw sensor reading as "this is 0 L".
- A green banner appears: "Step 1 of 2 — Empty anchored ✓". The next sensor fix will display ~0 L on the fuel chart.
Step 3 — fill the tank and capture the litre count
- Fill the tank to the level you normally run (full is best; the wider the gap between empty and the fill, the more accurate the slope).
- Note the litres dispensed from the pump display or receipt. Whole litres is fine — "203" is good, "203.4" is fine too.
- Wait another ~60 seconds for the sensor reading to stabilise after fuelling.
Step 4 — fit the scale (UI)
- On the same Fuel tab, under the green "Step 1 ✓" banner, click I refueled this truck — fit the scale.
- A small inline form opens: "How many litres did you just add?"
-
Type the number from the pump (e.g.
203) and click Apply. - A new banner appears: "Step 2 of 2 — Fuel sensor calibrated ✓". The fuel chart starts showing real litres on the next telemetry tick. You're done.
4. How to read the fuel chart
The fuel chart on Vehicles → truck → Fuel plots tank level over time. The Y-axis is litres (assuming calibration is done), the X-axis is wall-clock time. Things you can read off it:
- Steady downward slope while the truck is moving — normal fuel consumption. The steeper the slope, the harder the work (loaded climb, fast highway).
- Flat horizontal line while parked — tank not being touched. Healthy.
- Sharp upward step — a refuel. The size of the step is the litres added.
- Sharp downward step while parked — flagged as a possible fuel anomaly. The system creates an alert; investigate via the Alerts page.
- Wiggle / saw-tooth while moving — fuel sloshing in the tank. The smoother (the engine on the chart applies a moving average) reduces this but can't eliminate it on bumpy ground. A wiggle is not a leak.
- Two flat lines stacked (a long horizontal segment that "jumps" to a different value) — usually the LLS probe missed a packet; the chart resumes where the next valid reading lands. Not a refuel and not a theft.
The chart's tooltip on hover gives the exact litre reading + the timestamp. Click + drag a window on the chart to zoom in on a specific period (e.g. the hour around an alert).
5. Understanding fuel burnt
Every Trip on the Trips page and every trip row on a driver's profile shows a Fuel column — the litres consumed across that one trip. FleetCommando computes this on a three-tier cascade so a number is always available:
- Tier 1 — sensor delta. If the LLS probe was calibrated and reported a clean start and end value for the trip, fuel burnt = start L − end L. Most accurate.
- Tier 2 — distance × consumption. When the sensor delta isn't trustworthy (sensor offline, slosh too wild, trip too short for a stable reading), we estimate from kilometres × the vehicle's running L/100 km rate. Less accurate but always available.
- Tier 3 — Idle burn. If the engine ran while stationary (ignition on, speed = 0), the idle-burn rate is added. Important for trucks that spend long minutes idling at the terminal.
On the Trips page each row also shows a 📦 badge if the trip overlapped a captured port visit, and a coloured classification chip (Trip / Yard / Dwell / Noise) — see the next section for what those mean.
6. Trips, replays, and trips under drivers
Trips page
Sidebar → Trips. Every closed journey across the fleet, newest first. Each row shows From → To, distance, fuel, status, classification, and a Replay button. The page filters to real trips by default; yard shuffles, dwells, and GPS-noise rows hide behind the Show all toggle so the operator's first read is signal, not noise.
Trip classifications
- Trip — real transport activity (the default view).
- Yard movement — reshuffling inside the depot or terminal. Real motion but not customer-facing.
- Dwell / Idle — vehicle moved a few metres while parked. Often sensor jitter while the engine warms.
- GPS noise — coordinate drift that looked like motion but wasn't. Excluded from totals.
Replay
Every trip row carries a Replay button. Click it → FleetCommando opens Journey playback filtered to that trip's exact time window. From there you get:
- Cinema chase-cam following the truck along the snapped-to-road polyline.
- Heatmap of dwell points, traffic-jam-style coloured trail.
- Per-point hover with speed, fuel level, and heading.
- The exact stops list (terminals, customers, fuel stops) overlaid on the route.
Replay is the answer when the chairman asks "what did this driver actually do on that run?" — you can show the route, the stops, the speed envelope, and the fuel burn in one shared screen.
Trips on a driver's profile
Sidebar → Drivers → tap a driver → Trips tab. The same data scoped to that driver's last 50 closed trips. Same default filter (real trips only) + same Replay button per row. A toggle at the top tells you how many rows are hidden as yard / dwell / noise — flip it on for audit.
Same-label loops collapse: a round-trip starting and ending in "Toma" renders as Toma · round trip in italic instead of repeating "Toma → Toma", so the list reads cleanly when a driver did three loops inside the same area on one shift.
7. Common questions
- Why does the fuel chart show 0 L on a vehicle I know has fuel? The calibration is missing or wrong. Run the filling-station walkthrough.
- Why is the trip's fuel burnt different from "start L − end L" by eye? Idle minutes count. A trip that drove 30 km AND idled 18 minutes will show more litres than 30 km × L/100km alone.
- Why does Replay say "no data" for a Yard or Dwell row? Those classifications correspond to tiny movements (a few metres) — there's no route worth replaying. Toggle Show all to confirm the row exists, and use the Live Map to inspect the dwell location.
- I see "Toma → Toma" with 0.0 km — that's a GPS-noise row. With the default filter on, those rows are hidden. Click Show all only when auditing.
Related: Vehicles & drivers (registering a truck and entering the tank capacity), Live Map (watching the truck in real time), Alerts (responding to fuel anomalies).