THE CHALLENGEA Generic GPS Tracker Goes Blind on an EV
An EV fleet runs on different questions than a diesel one. Operators need usable state-of-charge per vehicle, honest range under real payload and weather, and a charging plan that does not trip the depot supply. A standard tracker reports position and ignition but knows nothing about the pack, so dispatchers guess at range and chargers run uncoordinated. Closing that gap means pulling battery data straight off the vehicle and turning it into decisions about routing, charging, and pack health.
Sits inside the Telematics and GPS Tracking stack and shares hardware and platform building blocks with Fleet Tracking and Monitoring.
WHAT'S INCLUDED
Hardware and Software for Electric Fleets
BMS-over-CAN Tracker
A tracker built around an STM32 MCU, an automotive CAN transceiver, and a Quectel EC200 LTE Cat-1 modem. It taps the vehicle CAN bus and decodes battery management system frames for state-of-charge, pack voltage, cell temperatures, and charge current, then forwards them over MQTT.
State-of-Charge and Range Analytics
Usable state-of-charge and remaining range are computed from recent consumption per kilometer, payload, ambient temperature, and route grade. The estimate adapts to conditions instead of mapping a fixed percentage to a fixed distance.
Charge-Session Logging
Every charge is logged with start and stop time, energy delivered, peak power, and stop reason. On depot chargers these read from an OCPP 1.6J context and correlate with the vehicle and trip that preceded each session.
Geofencing and Trip Records
Depots, routes, and customer sites are defined as geofences with entry, exit, and dwell alerts. Each trip ties together distance, energy used, and the charge state at departure and arrival for a complete operational record.
Depot Charging Coordination
Live state-of-charge and next-trip departure times feed a scheduler that staggers charging across the depot. Vehicles leaving soonest and sitting lowest charge first, keeping the site within its power envelope.
Battery Health Tracking
Usable capacity is trended against nameplate using logged cycles, depth of discharge, and cell temperature spread. Operators see which packs degrade faster than the fleet average, which supports warranty action and replacement planning.
ARCHITECTURE
From CAN Frame to Charging Decision
The tracker reads the bus, decodes the pack, and publishes normalized telemetry. The backend turns that into range, health, and charging decisions, then closes the loop with the chargers in the depot.
On-Vehicle Edge
STM32 firmware on FreeRTOS samples CAN frames, applies the per-model decode profile, and buffers telemetry with store-and-forward so nothing is lost during cellular dropouts. Supercapacitor ride-through keeps the unit alive across ignition cycles.
Telemetry Backend
Decoded data lands over MQTT into a time-series store. Range prediction, cycle counting, and capacity trending run as stream processors so the dashboard reflects pack state within seconds of the last frame.
Charger Integration
An OCPP 1.6J context links depot chargers to the scheduler. The platform reads session data back and issues a charging order that respects each vehicle departure time and the site power limit.
FAQ
Common Questions
How do you read battery data from the EV?
Battery data comes off the vehicle CAN bus, where the battery management system frames are decoded. For OEM EVs that publish a documented PID set, state-of-charge, pack voltage, cell temperatures, and current read directly. For vehicles with proprietary frames, the relevant message IDs are reverse-engineered against a reference vehicle and the scaling factors validated before deployment.
Can range be predicted accurately?
Range is computed from usable state-of-charge, recent energy consumption per kilometer, and route grade where map data is available. The model adapts to payload, ambient temperature, and HVAC load, so the figure stays useful in cold weather when fixed-percentage estimates fall apart.
Does it integrate with charging infrastructure?
Yes. On the charger side, an OCPP 1.6J context lets the backend read charge-session start, energy delivered, and stop reason from depot chargers. Those sessions correlate with the vehicle telematics record so each charge maps to a specific vehicle and trip.
How is depot charging coordinated?
Each vehicle state-of-charge and next-trip departure time feeds a scheduling layer that staggers charging to stay within the depot power envelope. Vehicles needed earliest and sitting lowest charge first. The same coordination logic applies to depot charging work.
What hardware does the tracker use?
A typical build pairs an STM32 application MCU with a Quectel EC200 LTE Cat-1 modem and an automotive CAN transceiver, powered from the 12V auxiliary rail with supercapacitor ride-through. Firmware runs on FreeRTOS with a store-and-forward buffer so no telemetry is lost during cellular dropouts.
How is battery health tracked over time?
Full charge and discharge cycles, depth of discharge, and cell temperature spread are logged, then usable capacity is trended against nameplate. Operators see which packs are degrading faster than the fleet average, which supports warranty claims and end-of-life planning.
Does the system work across mixed EV makes?
Yes. A decoder profile per vehicle model lets a fleet running buses, vans, and cars from different OEMs report into one normalized data model. Adding a new model means adding a decode profile, not rebuilding the platform.
Ready to See Your EV Fleet's Real Range?
Share your vehicle makes, depot power limits, and charging setup to get a tailored approach and a realistic timeline.
Schedule a Free Consultation