Diagnostic trouble codes
Receive supported DTCs with source, time and vehicle context.
Use compatible fault codes, warning data, mileage and engine hours to identify issues, prioritise investigation and protect uptime.
Compatible telematics, CAN and OEM sources can provide diagnostic trouble codes and vehicle condition signals. Fleetly brings the available information into the vehicle record and connects it with maintenance history, driver defects and current use.
Rules can prioritise new or recurring warnings for assessment rather than expecting teams to interpret every code in isolation.
Each capability works with the wider Fleetly platform, keeping vehicles, drivers, events, evidence and outcomes connected.
Receive supported DTCs with source, time and vehicle context.
Surface available vehicle warnings and relevant changes.
Use connected usage measures to support service planning.
Identify recurring issues across the vehicle history.
Notify the right team when configured diagnostic conditions occur.
Move an assessed issue into accountable inspection or repair.
This capability works inside Fleetly One Platform, sharing the same vehicles, drivers, events, workflows and reporting as the wider fleet operation.
Fleetly makes sophisticated fleet technology usable by connecting each signal to a decision, an owner and an outcome.
Fleetly collects available diagnostic and vehicle-health data.
The platform applies source context and customer rules.
Relevant issues enter an alert, inspection or work-order workflow.
Outcome and recurrence remain connected to the vehicle history.
Diagnostic data vary significantly by vehicle, interface and device. Fleetly confirms the available signals and their practical use before defining the solution.
Remote information supports maintenance decisions but does not replace appropriate technical inspection by a qualified person.
Explore the open Fleetly ecosystemTalk to Fleetly for a solution assessment based on your vehicles, devices, operating model and required outcomes.
Diagnostic trouble codes are standard or manufacturer-specific indicators generated by a vehicle system when a monitored condition is detected.
No. Availability depends on the vehicle, interface, device and integration.
Yes. An authorised workflow can move a relevant issue into inspection or repair.
Yes, where reliable engine-hour data are available.
No. It supports prioritisation and evidence; qualified inspection and repair remain essential.
We will focus the demonstration on your vehicles, risks, workflows and existing technology.