GPS Fleet Tracking System: Hardware, Video and Platform

Layer 1: the tracking device

A wired tracker draws power from the battery, detects ignition through an ACC line, and reports position, speed and alarms over 4G. That ignition line separates a fleet report from a dot on a map: without it, the platform cannot tell idling from parked.

Trackers use GT06, a compact binary protocol: a position packet is roughly 30 bytes on the wire versus 200+ bytes for an equivalent NMEA-over-TCP message. The GT06 reference covers message types for teams integrating directly.

Layer 2: the video device

A fleet dash cam supplies what a GPS trail cannot: who was driving and whether the claim against you is accurate. Cameras run JT/T 808 and add ADAS on the road-facing lens, DMS on the driver-facing lens and BSD on the sides. They are not a per-vehicle default; fit them where claim exposure is largest.

Layer 3: the platform

Traqcare covers live tracking, route playback, alerts, geofences, fuel management, reports, device management and user roles, as a web app with iOS and Android apps.

Hardware is not locked to it: devices are compatible with third-party platforms such as Traccar, Wialon, Navixy and GPS-Trace. See developer resources for the integration path.

Fuel

• ACC on with zero speed for a sustained period is an idling event. The J10 uploads ACC on/off status with every report, which is what makes idling reporting possible.
• Route playback exposes the gap between assigned and driven routes.
• Fuel management compares tank movement against distance. The WD10 takes an oil-level sensor as an expansion input for measured rather than inferred consumption.

Utilisation

• Engine hours and daily distance separate the trucks that earn from the ones parked on a yard — the input for a fleet-size decision.
• Trip and stop reports expose dwell time at each site, the hidden cost in a delivery round.
• Geofences around depots and customer sites turn arrivals into timestamps instead of phone calls.

Safety

• Overspeed, harsh acceleration, harsh braking, sharp cornering and collision alarms come from device firmware, not later inference; the J10 lists all five.
• ADAS warns the driver in the cab: the D9 supports FCWS, LDWS, PCWS, HMW and FVSA.
• DMS detects smoking, yawning, closed eyes, distraction and camera occlusion, with an audible cab alert and a platform event.
• BSD covers left and right blind areas on lane changes, where urban fleets collect scrape damage.

Theft and tamper

• Power-cut alarms fire the moment supply is interrupted: the GX3 on illegal power cut, the J10 when vehicle voltage drops below 5 V on backup battery.
• Displacement and vibration alarms catch towing outside working hours; the GT06 4G reports both.
• Blind-area buffering matters: the J10 buffers positions while out of coverage and resends on reconnect.

Compliance

Requirements for device type, certification and record retention vary by market, so check local regulations for the country you are deploying in before you specify hardware. We can assist with the additional certifications a specific market asks for.

Certifications across the range are CE, FCC, PTCRB, IC, RoHS, REACH and ISO 9001. Region-specific certifications and test reports for your import market can be provided on request; see the product page for a specific model and our certifications page.

What white-label covers

• Your brand name, logo, app name and domain across web and both mobile apps.
• Your own user hierarchy and user roles across the platform, for sub-dealers and end customers.
• Device management under your own account, for onboarding and administering batches of devices.
• Detail: white-label platform and the reseller programme.

Running hardware on your own platform

Resellers with an existing stack need not move. Trackers speak GT06 and dashcams and MDVRs speak JT/T 808, so devices are compatible with third-party platforms such as Traccar, Wialon, Navixy and GPS-Trace as well as Traqcare — see the developer hub. The GT06 protocol guide covers the message-level detail.

Weighing the two routes: see the build-versus-buy comparison and the platform round-up.

Reports worth configuring on day one

• Daily distance and engine hours per vehicle.
• Idling report with a threshold set to your tolerance, not a default.
• Geofence entry and exit for depots and key customer sites.
• Weekly driver behaviour summary, ranked — ranking changes behaviour faster than a score.

Worked example: tracker data per vehicle

Let N be the reporting interval in seconds and B the bytes per report including overhead. Daily usage is (86400 / N) x B.

A GT06 position packet is roughly 30 bytes on the wire; allowing for retries and acknowledgements, B near 120 bytes is a workable planning figure. At N = 30: 2,880 reports x 120 bytes, about 346 KB per vehicle per day, roughly 10 MB a month.

Halving the interval to N = 15 doubles it to about 20 MB.

Worked example: camera data per vehicle

Let R be the live-stream bitrate in kbps and M the daily minutes of live viewing. Daily usage is R x 60 x M / 8 / 1000 MB.

At R = 512 and M = 20: about 77 MB a day, roughly 2.3 GB a month per vehicle, before snapshots and playback downloads. Halve the viewing minutes and you halve consumption, so live view should be an exception workflow.

The data usage calculator runs these numbers for your channel count, and the storage calculator sizes the card or disk for your retention target.

What drives camera data up

• Channels streamed at once: four-channel live view costs four times single-channel.
• Bitrate and resolution per channel. H.265, supported on the W108, makes smaller files than H.264 at the same quality.
• Event volume: every ADAS or DMS event uploading a snapshot is data, so tuning sensitivity tunes consumption.
• Remote playback over 4G is the largest line item when used casually; prefer depot Wi-Fi.

Storage on the device

Loop recording overwrites the oldest files, so retention depends on card size, channel count and bitrate, not a fixed number of days. The WD02 takes two microSD cards up to 128 GB each; the WD10 adds a 2 TB SSD or disk.