Diagnostics

Most likely yes for standard J1939 / OBD-II data (engine hours, fuel flow, RPM, basic fault codes). For OEM-proprietary data points (machine mode, attachment status, hydraulic state, payload), we'll check whether your OEM and model are in our standard libraries — TrakaX® Series 2 and Teltonika FMM650 / FMC650 have the broadest coverage. If not, custom library work scopes the build. Tell us the OEM list and we'll quote.

J1939 is the heavy diesel CAN protocol — used on trucks, heavy plant, generators, agricultural and mining equipment. OBD-II is the light-vehicle protocol — used on cars, utes, vans, and light commercial trucks. Most Teletrack hardwired devices support both. OBD plug-ins (FMM003, Plug5) are OBD-II only.

Yes — fault codes carry severity flags. Critical faults (e.g. low oil pressure, overheating, transmission warnings) open as high-priority work orders. Informational faults (e.g. service-due reminders, minor sensor warnings) route to a review queue. Your maintenance manager configures the severity rules per OEM / model.

It's logged with the raw code and timestamp even if the description isn't in the library. Maintenance manager can flag it for investigation, and we can add the code to the library for future occurrences. For OEM-specific codes outside the standard set, a small custom library expansion is usually low-cost.

Yes — modern emissions-compliant diesels publish more J1939 data than older machines, not less. DEF / AdBlue level, regen status, DPF differential pressure, NOx readings — all available if the OEM publishes them. Useful for fleet managers tracking emissions compliance and DEF consumption.

Yes. Diagnostic data is available via the public API, webhooks, and CSV export — same as all other Teletrack data. Common use case is pushing fault codes into an existing CMMS or ERP. See fleet intelligence.

The device needs to be wired into the machine's CAN bus. On most modern plant and trucks this is a straightforward connection at the diagnostic port or a tap into the CAN backbone. Standard professional install handles it — typically 30–60 minutes per asset. OBD plug-ins are tool-less DIY but limited to OBD-II only.

CANBUS data is sent to the system either on the next update or on each occurrence. Fault codes are sent instantly. Continuous parameters like RPM are reported as the latest record at the next update — not as a live stream. A vehicle can publish RPM every 500ms internally on the CAN bus, and that's data overload neither you nor we need pushed to the server, stored, and billed against your data plan. The cadence is tuned per asset to send what's useful and ignore what isn't.