The fleet vehicle tracker, pulled apartAn exploded view of the fleet tracker: the platform screen showing a fleet map, above the small tracker board with its modules and fuse tap lead, above the enclosure base, lined up on guidesPlatformBoardEnclosureOne specification

Fleet vehicle tracker

One small board, powered from a vehicle fuse, that reads the vehicle through a standard diagnostic dongle and sends position, motion and vehicle readings to a web platform.

A concept design under Example systems. It shows how we would specify a tracker as one system, across the board, the firmware, the enclosure and the platform. Nothing here has been built, and no figure is a measured result.

Next: the board

A small board that buys in the hard parts

An ESP32 module runs the firmware and talks to the diagnostic dongle over Bluetooth Low Energy. A satellite navigation module gives position, speed and time, and a cellular module on a header sends it all to the platform. A three-axis accelerometer catches harsh braking and impact.

A power stage turns the vehicle supply into the voltages the modules need, with reverse-polarity protection, a surge suppressor and a fuse at the connector edge, so a fault stays out of the rest of the board. Power comes in through a fuse tap lead, which also tells the board when the ignition is on.

Next: the firmware

Firmware that keeps every reading and sends it in order

Readings are grouped into trips, which open when the supply comes on and close when it goes. They are stored in flash and sent to the platform in order, and removed only once the platform confirms them, so a drive through a signal gap arrives whole when signal returns.

A value the vehicle does not provide is sent as empty, never as zero. If the dongle is missing, the device still reports position and motion and flags the fault. Updates install only if they carry our signature, and the previous image is kept in case the new one fails to start.

Next: the enclosure

A housing that mounts beside the fuse box

The enclosure holds the board, the cellular module and the satellite antenna in fixed positions, with one slot for the fuse tap lead and strain relief so a pull never reaches the board. A flat back takes a cable tie or a mounting pad.

It opens with screws for service, shows the status LED through a light pipe, keeps metal away from the antennas, and carries a label with the device identity so an installer can pair it with a phone.

Next: the platform

A platform that shows the fleet as it is

An intake service checks each device's identity, discards duplicates and stores every reading with the time it happened. The web application shows every vehicle's last known position with the time of its last report, so a stale position is never mistaken for a live one.

Trip history is drawn as a route with its gaps left as gaps. Alerts fire when a vehicle leaves an area, moves outside set hours, stops reporting or reports a fault code. Each customer sees its own vehicles only, with separate roles for administrators and viewers.

Next: full stack or semi-stack

Full stack, or the layers you do not have

  • Software only: the platform, for trackers you already have
  • Board and firmware, for an enclosure you supply
  • Device only: board, firmware and enclosure, sending to your platform
  • Full stack: all four layers, and every joint between them

In a full-stack project we own every joint, so each one is written down once and tested from both sides. In a semi-stack project the joint to your layer becomes the written agreement between us.

Next: the full specification

System overview

The tracker is one small ESP32 board, powered from a vehicle fuse. It reads vehicle data from a standard OBD-II Bluetooth dongle, adds its own position and motion readings, and sends everything to a web platform. Power and vehicle data reach the board without any wiring into the vehicle's data network.

Why this design

  • Power from a fuse. A fuse tap is a standard, reversible way to take power. Choosing a fuse that is only live with the ignition on also tells the board when a trip starts and ends, with no extra circuit.
  • Vehicle data from an OBD-II dongle. A ready-made Bluetooth Low Energy dongle in the diagnostic port gives speed, engine state and fault codes in a standard form. The board needs no vehicle connector, no CAN wiring and no vehicle-specific code.
  • Limits. Which values appear depends on the vehicle and the dongle, so fields can be blank. The dongle must stay plugged in, and it can be removed by anyone with access to the port.

Full stack and semi-stack

VariantLayers we designThe client supplies
Full stackBoard, firmware, enclosure and platformVehicles, and the mobile data plan
Semi-stack: device onlyBoard, firmware and enclosureA platform, using our message format
Semi-stack: board and firmwareBoard and firmwareAn enclosure
Semi-stack: software onlyPlatformTracker hardware that can send to it

Requirements

The tracker reports where a vehicle is and how it is being used, and shows that to a fleet manager. Each requirement is a statement that can be tested, and the acceptance tests at the end say how.

RefRequirementLayer
R1Report position and time from satellite navigation, at an interval the fleet manager can set.Board, firmware, platform
R2Keep readings when there is no mobile signal, and send them in order when signal returns.Firmware
R3Start a trip when the vehicle supply comes on and end it when the supply goes, using a fuse that is live only with the ignition on.Board, firmware
R4Detect harsh braking, harsh acceleration and impact, with thresholds set in the platform.Board, firmware, platform
R5Run from a 12 V vehicle supply, and withstand the supply faults normal in vehicles, such as reverse connection and voltage spikes. A 24 V version is a variant.Board
R6Read speed, engine state and fault codes from an OBD-II Bluetooth Low Energy dongle, and show a blank where the vehicle does not provide a value.Firmware, platform
R7Save the open trip when the supply is cut, and send it when power returns.Board, firmware
R8Accept firmware updates over the air, and install only updates signed by us.Firmware, platform
R9Show the current position and trip history on a map, per vehicle and for the whole fleet.Platform
R10Raise alerts when a vehicle leaves a set area, moves outside set hours, stops reporting, or reports a fault code.Platform
R11Give each customer access to its own vehicles only, with separate roles for administrators and viewers.Platform
R12Fit in a small housing that mounts beside the fuse box and can be removed for service.Enclosure
R13Let an installer pair a device with a vehicle and confirm it is reporting, using a phone.Enclosure, platform

Hardware

The board is small because most of the work is done by parts we buy ready made. An ESP32 module runs the firmware and talks to the OBD-II dongle over Bluetooth Low Energy. A power stage turns the vehicle supply into the voltages the modules need. Everything else is a module on a header or a small circuit around one.

BlockPart typeJobNotes
Fuse tap leadAdd-a-circuit fuse holder with an inline leadTakes the vehicle supply from a fuse slotSwitched slot: supply is live with ignition. Always-on slot is a variant.
Input protectionReverse-polarity protection, surge suppressor, fuseSurvives a wrong connection and the spikes normal in vehiclesRated for a 12 V system. A 24 V board needs a different input stage.
Power stageWide-input step-down regulator, then a 3.3 V railPowers the ESP32, GNSS and motion sensorThe cellular module needs its own supply path for transmit peaks.
ControllerESP32 module with on-board antennaRuns the firmware, Bluetooth Low Energy and, in the Wi-Fi variant, the uplinkBluetooth Low Energy is the link to the OBD-II dongle.
GNSSSatellite navigation module with its antennaPosition, speed and timeThe ESP32 has no satellite receiver, so this stays.
CellularCat-M or LTE module on a headerSends data to the platformOptional in the Wi-Fi offload variant, where the device uploads when it reaches a known network.
MotionThree-axis accelerometerHarsh events and impactReads over a serial bus.
StatusOne LEDPower, pairing and faultSeen through a light pipe.

Layout rules

  • Keep the step-down regulator and its inductor away from the GNSS module and its antenna feed.
  • Put the GNSS antenna on the edge nearest the windscreen side of the housing, with clear ground around it.
  • Keep the ESP32 antenna area free of copper and metal, and away from the cellular antenna.
  • Place input protection at the connector edge so a fault stays out of the rest of the board.
  • Label every test point and the supply, ground and serial lines.

Hardware outputs

Schematic, board layout and manufacturing files, a bill of materials with part numbers and alternates, a built prototype board with its test notes, and a short fitting guide for the fuse tap.

Firmware

The firmware runs on the ESP32. It reads the satellite receiver, the motion sensor and the OBD-II dongle, groups readings into trips, stores them, and sends them to the platform. It is written as separate parts so each can be tested alone.

PartJobRequirement
Power and trip managerDetects supply on and off, opens and closes trips, saves the open trip when supply is cutR3, R7
Position readerReads the GNSS module and applies the reporting intervalR1
Motion readerDetects harsh braking, harsh acceleration and impact against platform thresholdsR4
OBD-II linkFinds and pairs with the dongle over Bluetooth Low Energy, requests speed, engine state and fault codes, and reconnects when the link dropsR6
Store and forwardKeeps readings in flash, sends them in order, and removes them only after the platform confirmsR2
UplinkSends over cellular, or over Wi-Fi in the offload variantR1, R2
Update clientDownloads, checks and installs signed firmwareR8

Rules the firmware follows

  • A value the vehicle does not provide is sent as empty, never as zero.
  • If the dongle is missing or will not pair, the device still reports position and motion, and flags the fault.
  • Readings carry the time the event happened, not the time it was sent.
  • Storage is a ring: when full, the oldest routine readings go first and events are kept.
  • Settings come from the platform and are checked before they are used.

Updates and security

The device installs a new firmware image only if it carries our signature, and keeps the previous image so it can go back if the new one fails to start. Each device has its own identity and key, and the platform rejects messages from any other.

Enclosure

The enclosure is a small housing for the board, designed around the fuse tap lead and mounted beside the fuse box. It is a prototype housing, not a finished production part.

Design requirements

  • Holds the board, the cellular module and the satellite antenna in fixed positions.
  • Has one slot for the fuse tap lead, with strain relief so a pull does not reach the board.
  • Fits in the space beside a typical fuse box, with a flat back for a cable tie or double-sided mounting.
  • Opens with screws so it can be serviced, and shows the status LED through a light pipe.
  • Keeps metal away from the antenna areas.
  • Carries a label with the device identity for pairing (R13).

Materials to evaluate

Vehicle interiors get hot and cold. We would test a heat-resistant material such as PETG or ASA against the temperatures at the chosen fitting position before choosing one. No material is chosen yet.

Enclosure outputs

Solid models and production files for the chosen method, a prototype housing that fits the prototype board, and a fitting note for the chosen position.

Platform software

The platform receives what the devices send, keeps it, and shows it to the right people. It has three parts.

Intake service
Accepts messages from devices over an encrypted connection, checks the device identity, discards duplicates and stores each reading with its time.
Trip and event store
Groups readings into trips, keeps events such as harsh braking and power loss, and records each device's settings and firmware version.
Web application
Shows vehicles on a map, trip history, alerts and device status, and lets administrators change settings and manage users.

What the web application shows

  • Fleet map. Every vehicle's last known position, with the time of the last report, so a stale position is never mistaken for a live one (R9).
  • Trip history. A selected vehicle and date range drawn as a route, with start, end, distance and stops. Gaps from lost signal are shown as gaps.
  • Alerts. Rules for leaving an area, moving outside set hours, a device that has stopped reporting, and loss of supply. Alerts go by email, and other channels are added as agreed (R10).
  • Device status. Firmware version, last report, restarts and update progress for each device.
  • Installer view. A phone page where an installer scans the device label, assigns it to a vehicle and sees the first report arrive (R13).

Accounts and access

Each customer sees its own vehicles and nobody else's. Administrators manage users, areas and alert rules, and viewers can only look (R11). Sign-in uses a one-time code or a security key in addition to a password. Every change to settings and users is recorded with who made it and when.

Platform outputs

The running service, the source code and its documentation, a description of the device message format, and a plan for backups and for moving the service to another host.

Interfaces between the layers

In a full-stack project we own every joint below, so each one is written down once and tested from both sides. In a semi-stack project the customer owns one side, and the joint becomes the written agreement between us.

JointBetweenWhat is agreed
Board and firmwareBoard, firmwarePin map, supply states, serial bus addresses, and the boot and fault behaviour
Board and enclosureBoard, enclosureBoard outline, mounting holes, antenna positions, LED position, lead slot and keep-out zones
Device and dongleFirmware, OBD-II dongleBluetooth Low Energy services used, the data requested, polling rate and what happens when it drops
Device and platformFirmware, platformMessage format, authentication, time, retry and confirmation rules
Platform and web applicationPlatform, web appData model, access rules and the alert rules
Installer and devicePerson, deviceFitting steps, pairing, and the checks that show it is reporting

Example device message

The values below are invented to show the shape. Fields the vehicle does not provide are null.

{
  "device": "example-0001",
  "sent": "2026-01-01T09:30:05Z",
  "trip": "t-000123",
  "readings": [
    {
      "time": "2026-01-01T09:30:00Z",
      "lat": 52.0000,
      "lon": 1.0000,
      "speed_kmh": 48,
      "obd": { "speed_kmh": 47, "engine_on": true, "fault_codes": [] },
      "event": null
    },
    {
      "time": "2026-01-01T09:30:04Z",
      "lat": 52.0001,
      "lon": 1.0002,
      "speed_kmh": 31,
      "obd": { "speed_kmh": null, "engine_on": true, "fault_codes": ["P0300"] },
      "event": "harsh_braking"
    }
  ]
}

Data protection

A vehicle's position is personal data whenever a driver can be identified from it, which is usually the case in a fleet. The customer deciding to track its vehicles is the controller under UK GDPR. Where we host the data for a customer, we act as its processor under a written agreement. This section sets out how the design supports the customer. It is not legal advice, and the customer should take its own.

Built into the design

  • Retention. The customer sets how long trip data is kept, and older data is deleted automatically.
  • Private use. A vehicle can be set so that tracking pauses outside working hours, or can be switched to a privacy mode, for fleets that allow private trips.
  • Access. Roles limit who can see positions, and every view of a driver's history is recorded.
  • Export and deletion. An administrator can export or delete one driver's data on request.
  • Minimum data. The device sends position, motion events and device status. It records no audio, no images and no data from the vehicle's own systems unless a variant is agreed.

What the customer needs to do

Tell drivers what is tracked and why, record the lawful basis for tracking, and consider an impact assessment before the trackers go in. The Information Commissioner's Office publishes guidance on monitoring workers that covers these steps.

What this design does not claim

This is a concept design written to show how we specify a system that spans software, a circuit board and an enclosure. It describes what we would build and how we would check it. It does not describe a product that exists.

  • No part has been built or tested, and no figure here is a measured result.
  • No electromagnetic, vehicle-electrical or safety certification is claimed or implied.
  • No ingress or temperature rating is claimed for the enclosure.
  • The device reads data from the vehicle and does not control it.
  • Dongle support depends on the vehicle and the dongle model, and is confirmed per vehicle type.
  • Part types are examples. Specific parts are chosen and checked at the start of a real project.

Deliverables by stage

A full-stack project delivers all four stages. A semi-stack project delivers the stages for the layers we own, plus the written interface for the layers we do not.

StageFull stackSemi-stack
SpecificationRequirements, interfaces and test plan for all layersRequirements and interfaces for our layers, and the joint to the customer's layer
PrototypeBoard, firmware, enclosure and platform, working togetherOur layers working against the customer's, or against a simple stand-in
TestTests run against each requirement, with results written upTests for our layers and the joint
HandoverSource, design files, models, documentation and fitting guideThe same for our layers, and the interface document

Indicative costs

These are the scale of costs for a project of this shape, excluding VAT. They are indicative, not a quote: a quote follows the specification, and parts prices move with quantity and supplier. Buying the modules ready made, rather than designing a radio or a satellite receiver from parts, is what keeps the board and the project small.

StageFull stackWhat it covers
Specification£2,000 to £3,000Requirements, interfaces and the test plan for all four layers
Prototype£9,000 to £14,000Board, firmware, enclosure and platform, working together
Test£2,000 to £3,000Every requirement tested, including the supply faults and the signal gap, and written up
Handover£1,500 to £2,500Source, design files, models, documentation and fitting guide
Design and build£14,500 to £22,500Device only, about £9,500 to £15,000. Board and firmware, about £6,000 to £10,000. Software only, about £6,000 to £9,500.

Per device, at prototype quantities

ItemIndicative costNote
ESP32 module£3 to £4
Satellite navigation module£6 to £10With its antenna
Cellular module£10 to £15Not needed in the Wi-Fi offload variant
Board and assembly£15 to £25A small batch of bare boards, assembled
Enclosure£5 to £10Prototype housing
Fuse tap, protection and small parts£4 to £6
Per device£45 to £70Falls at volume. Hosting the platform for a small fleet is in the order of £20 to £40 a month, and the mobile data plan, which the customer holds, a few pounds per device a month.

Acceptance tests and open decisions

Each requirement has a test that anyone can repeat.

RefTest
R1Drive a set route and compare reported positions with the route at the set interval.
R2Remove signal part way through a trip, restore it, and check that every reading arrives in order.
R3Switch the fuse supply on and off and check that a trip opens and closes.
R4Replay known braking and impact patterns and check the events raised.
R5Apply reverse connection and a supply spike to the input and check the board survives.
R6Pair the dongle, compare speed and engine state with the dashboard, and check blanks where a value is missing.
R7Cut the supply during a trip and check the trip is sent when power returns.
R8Install a signed update, then try an unsigned one and check it is refused.
R9 to R11Check the map, alerts and access rules with test customers and test vehicles.
R12, R13Fit the prototype housing beside a fuse box and pair it using a phone.

Open decisions

  • Switched or always-on fuse as the baseline. Switched is assumed.
  • Cellular or Wi-Fi offload as the uplink.
  • Which OBD-II dongle model to support first.
  • Where the satellite antenna sits when the fuse box is in a footwell.
  • Whether to add a small backup cell so the final report is sent as power is lost.

Have a system like this in mind?

Tell us what it has to do, who will use it and which layers you already have. We will reply to arrange a conversation.