Vehicle health context
Use available faults, mileage and engine-hour readings to support maintenance assessment. A fault code indicates a condition for investigation, not a complete repair diagnosis.
Connected technology / OEM & CAN Vehicle Data
Turn available vehicle signals into useful fleet context.
Connect compatible OEM feeds, CAN interfaces and vehicle data sources to support maintenance, fuel analysis and EV fleet decisions.
Plan your integrationMAKE THE CONNECTION USEFULStart with the decision.
Start with the decision.
Design the data around it.
Vehicle data is not uniform. Make, model, year, powertrain, interface and permissions can all affect the signals available. Fleetly integration planning starts with a vehicle-by-vehicle capability assessment, then maps the agreed readings into consistent units and meanings while preserving where each value came from.
PRACTICAL USE CASES
Where this integration can add value.
Fuel and efficiency signals
Separate tank level from fuel used and calculated consumption. Compare similar vehicle classes and show coverage alongside performance.
EV data availability
Assess supported state-of-charge and energy signals. Treat charging status as a distinct field; a parked vehicle is not necessarily connected to a charger.
Mixed-source reconciliation
Where more than one source reports the same measure, agree priority and correction rules. Retain provenance so teams can explain differences.
Every connection has a working path.
Select a stage to see what needs to happen and why it matters.
OEM & CAN Vehicle Data / Assess
Check the vehicle and interface
Confirm make, model, year, powertrain and the exact adapter or OEM service before selecting signals.
Read the complete workflow
- Check the vehicle and interface
Confirm make, model, year, powertrain and the exact adapter or OEM service before selecting signals.
- Collect permitted readings
Use the approved installation or authorised data feed. Confirm units, update frequency and unavailable fields.
- Keep meanings consistent
Map measurements into a common model without converting missing data into zero or merging unlike signals.
- Support an operational decision
Use validated readings for maintenance, fuel or EV analysis within the agreed capability scope.
- Review quality over time
Compare representative readings with trusted evidence and investigate changes after hardware, firmware or vehicle updates.
DATA WITH CONTEXT
Agree the meaning before moving the data.
These are scoping considerations, not field names or a published API schema. Confirm the exact contract for your implementation.
| Data area | Why it matters | What to validate |
|---|---|---|
| Odometer / distance | Supports usage and maintenance context. | Confirm units, source and resets or discontinuities. |
| Fuel level / fuel used | Describes tank quantity or consumption. | Do not substitute one for the other. |
| State of charge | Estimates remaining EV battery charge. | Confirm availability and distinguish charging status. |
| Fault information | Provides diagnostic context. | Retain source and code definitions for qualified assessment. |
Technical background: Teltonika: CAN adapter vehicle compatibility. External guidance does not establish Fleetly compatibility.
PREPARE YOUR INTEGRATION
A useful first conversation starts here.
Mark what you have prepared and use the remaining items to shape your discussion. This checklist stays in this page session.
0 / 5Preparation items checked
Preparation only; this is not a compatibility assessment or production approval.
Opens your email app with an editable summary. Nothing is sent automatically.
COMMON QUESTIONSUnderstand the scope.
Understand the scope.
Plan with confidence.
Will every vehicle provide the same CAN data?
No. Supported signals depend on the vehicle, interface and configuration. Assess the exact vehicle and hardware combination.
Can OEM data replace installed hardware?
For some use cases it may provide required signals. Compare coverage, reporting frequency, permissions and the need for cameras or additional sensors before deciding.
Can Fleetly infer charging from a stationary EV?
Stationary status alone is insufficient. Use a validated charging signal where available and label any derived estimate explicitly.
Does a diagnostic code identify the repair required?
Not on its own. Maintenance teams should interpret the code alongside inspection and appropriate diagnostic procedures.
SUPPORTING RESOURCES
Take the next step with a clear plan.
Confirm your production scope.
Features and integration methods depend on the agreed devices, interfaces, permissions and enabled modules. Request the current technical documentation before implementation; never include passwords or access tokens in an initial enquiry.