Skip to main content
Flagship Case Study · Logistics & Fleet

Fleet Telematics, From Tracker Hardware to Dashboard

Custom GPS tracker hardware, OBD-II and CAN Bus vehicle data, an AWS backend and live dashboards, delivered as one system that now tracks 935 vehicles.

935Vehicles Tracked
Hardware to CloudLayers Delivered
DirectEngagement

Source: KoderTroop project records for this engagement.

Case Study

Project Overview

Engaged directly by a fleet operations provider, KoderTroop built the tracking system from the vehicle up: GPS tracker hardware, vehicle telemetry from OBD-II and CAN Bus, and a cloud backend on AWS with live dashboards. Each tracker reports over GSM/GPRS straight to the cloud, so data collection never depends on a driver's phone.

System diagram for Fleet Telematics Case Study: 935 Vehicles, Tracker to Cloud
How the system fits together, layer by layer.

The Business Problem

The operator needed to know where every vehicle was, how it was being driven and how its engine was performing, without relying on drivers to report any of it. Off-the-shelf trackers supply position, but rarely the vehicle data behind it.

What We Built

Designing the tracker ourselves is what made that vehicle data available. Each unit reads GPS position together with OBD-II and CAN Bus data and sends it over GSM/GPRS to a backend on AWS, where fleet managers work from live maps and dashboards and receive alerts when a rule is broken.

The Outcome

KoderTroop designed the hardware, firmware and software for all 935 vehicles. The operator runs one system with a single accountable delivery partner, instead of coordinating a tracker vendor, a telematics vendor and a software vendor.

How It Is Built

In the Vehicle
Custom tracker boards combining a u-blox NEO-6M GPS module, a SIM800A GSM/GPRS modem and an ESP32-class controller. We designed the PCBs in-house; a manufacturing partner fabricated them.
Vehicle Data
OBD-II and CAN Bus integration for diagnostics and telemetry, developed with ELM327 adapters and Python OBD.
Uplink
Trackers report over GSM/GPRS directly to the cloud, using MQTT for device telemetry.
Backend and Dashboards
Node.js and PostgreSQL on AWS, serving the live map, trip history, alerts and diagnostics dashboards.

Project Details

DeliveryKoderTroop design, firmware and software; tracker boards fabricated by a manufacturing partner
IndustryLogistics

Inside the Platform

The main screens, walked through one capability at a time.

Live map
Updated 8 seconds ago
Find a vehicle or driverOP
Truck 104Van 052
Truck 104Moving
A. Rao · Trip started 07:42
Speed46 km/h
Trip38.2 km
Fuel61%
VehiclesAllMovingAlerts
Truck 104
A. Rao
Moving
46 km/h
Truck 117
K. Shah
Moving
38 km/h
Van 052
M. Iyer
Idling
0 km/h
Truck 131
P. Nair
Moving
52 km/h
Van 068
S. Das
Parked
Ignition off
Truck 140
R. Menon
Offline
Last seen 14 min
Geofences
6 zones · alerts on entry and exit
Draw zoneOP
North depotRestricted: city centreSouth yardTruck 117Truck 131
Truck 131 entered a restricted zoneOpen
ZoneRestricted: city centre
DriverP. Nair
Time in zone11 min
NotifiedDispatch, SMS
AcknowledgeCall driver
Today's zone events
09:14
Truck 117 left
North depot
Left
09:02
Van 052 entered
Customer site 3
Entered
08:47
Truck 131 entered
Restricted: city centre
Entered
08:31
Truck 104 left
North depot
Left
08:05
Van 068 entered
South yard
Entered
Driver behaviour
Last 7 days · from GPS and CAN Bus data
Today7 days30 daysOP
Speeding events
22
Over 80 km/h for 10 s
Harsh braking
21
Deceleration over 0.4 g
Idling
2 h 48 min
Engine on, stationary
Distance driven
6,412 km
Drivers
DriverScoreSpeedingHarsh brakeIdling
PNP. Nair929318 min
KSK. Shah884641 min
ARA. Rao96119 min
MIM. Iyer81681 h 12 min
SDS. Das97026 min
RMR. Menon942122 min
Events per day
MonTueWedThuFriSatSun
M. Iyer · this week
Idling vs fleet average2.4×
Harsh braking8 events
Speeding6 events
Truck 131 · engine and fuel
OBD-II and CAN Bus · live
ExportOP
Coolant temperature
104 °C
Limit 105 °C
Engine speed
1,880 rpm
Fuel level
43%
≈ 210 km range
Fuel used today
31.6 L
9.8 km/L
Coolant temperature, °CLast 2 hours
Limit 105 °C07:0007:3008:0008:3009:00
Fuel level, %Refuel at 08:10
05:0006:3008:0009:30
Trouble codes
P0217Active
Engine coolant over-temperature
Today 08:52
P0171Cleared
System too lean, bank 1
2 days ago
Battery voltage13.9 V
Engine load64%
Throttle position28%
Tracker devices
GSM/GPRS uplink · MQTT
Device IDUpdate firmwareOP
Reporting now
5 of 7
Weak signal
1
Not reporting
1
Over 10 min
On latest firmware
5 of 7
fw 2.3.1
DevicesGSM signal
DeviceVehicleSignalLast messageFirmwareStatus
TRK-0104Truck 1042 s agofw 2.3.1Reporting
TRK-0117Truck 1173 s agofw 2.3.1Reporting
TRK-0131Truck 1311 s agofw 2.3.1Reporting
TRK-0052Van 0529 s agofw 2.2.0Weak signal
TRK-0140Truck 14014 min agofw 2.3.1Not reporting
TRK-0068Van 068Ignition offfw 2.3.1Sleeping
TRK-0073Truck 0734 s agofw 2.2.0Reporting
TRK-0140 has not reported for 14 minutes. Last position: South yard, ignition on.Show on map

Every vehicle's position on a live map, with past trips available for review.

Technology10 Technologies

Technologies & Delivery Models

Select Category1 Categories
Next Step

Planning a Comparable System?

Tell us about the device, the sites and the systems it has to connect to. A senior specialist will work through the architecture with you.