Do you support trackers from several vendors?

Yes. RideControl is brand-agnostic, and new tracker models are added during onboarding.

What counts as a faulty device?

A unit that stops reporting, reports far less often than expected, or sends GPS and battery values that fail sanity checks.

Can diagnostics create repairs automatically?

A flagged device can be turned into a service request that appears on the maintenance kanban.

Will we be told before reports go wrong?

That is the point of the module: gaps appear as a device list rather than as missing rows in a report.

Does this need new hardware?

No, it works with the IoT units you already run, once they are integrated.

Can we export device health data?

Yes, to CSV, and the same data is available through the API.

Feature

Device diagnostics: catch broken trackers, not broken reports

A fleet system is only as good as the hardware reporting into it. RideControl checks IoT units, GPS quality and battery telemetry continuously, and puts failing devices on a list someone can actually work through.

Book a demo See pricing

RideControl operations screen showing vehicle connectivity and device status

Device health

Trackers checked continuously

What diagnostics does

Monitors whether each IoT unit is reporting, and how recently.
Flags poor GPS quality that would otherwise corrupt trips and zone alerts.
Watches battery telemetry for units that stop sending or report implausible values.
Turns silent data gaps into an explicit worklist per hub.
Feeds a service request so a faulty unit gets replaced like any other repair.

How it works

Step 1
Baseline the hardware
Every vehicle's tracker model and expected reporting behaviour is recorded during onboarding.
Step 2
Check continuously
Reporting frequency, GPS fix quality and telemetry sanity are evaluated as data arrives.
Step 3
Raise the exception
Devices outside expected behaviour appear as a diagnostics list scoped to the hub.
Step 4
Fix it
A service request sends the vehicle to the workshop for a tracker swap or reinstall.
Step 5
Confirm recovery
Once the unit reports normally again it drops off the list, and the gap is visible in history.

Who uses it

Role	What they use it for
Operations manager	Trusting the numbers before acting on them
Hub lead	A short list of vehicles whose hardware needs attention
Mechanic	Tracker swaps handled as normal service work
Data / BI owner	Knowing which gaps in reporting are hardware, not behaviour

Data you get out

Device status list per hub with last report time.
History of outages per vehicle and per tracker model.
Service requests created from diagnostics.
CSV export and API access for hardware planning.

Related modules

Service Flow handles the physical fix, ride analytics depends on clean telemetry, and Control Tower shows offline vehicles in the live view. Field work can be run with RideCare on the same software.

Frequently asked questions

See it on your own fleet

Book a 30-minute walkthrough. We open the panel with your vehicle types, hubs and countries in mind — no slides.

Book a demo