ZenTRACK OBD – Operations Guide

(For operations, support teams, and fleet admins)

Written By Support Team

1. Purpose & Scope

This guide explains how ZenTRACK OBD behaves in day-to-day operation and what operations / fleet admins should expect once devices are deployed.

2. What ZenTRACK OBD Does

Once installed and configured, ZenTRACK OBD:

  • Collects GNSS data:

    • Location, speed, heading

  • Reads OBD-II parameters:

    • Ignition status, vehicle voltage, and other telematics metrics (based on config file)

  • Communicates via cellular network to:

    • ZenduOne

    • Other backend systems integrated for your deployment

  • Optionally communicates with BLE sensors and beacons if enabled in configuration.

The configuration file (12v vs 24v, region) determines:

  • Thresholds for ignition detection (voltage-based)

  • Event profiles (e.g., harsh braking/acceleration tuned for light vs heavy duty)

  • Reporting intervals and behavior.

3. Daily Operations Flow

  1. Vehicle Use

    • Driver operates the vehicle normally.

    • ZenTRACK OBD powers up from the OBD port when ignition is turned on.

  2. Data Transmission

    • Device sends location and telemetry based on:

      • Ignition state

      • Movement

      • Settings in the configuration file (e.g., periodic or event-based reporting).

  3. Platform Visibility

    • In ZenduOne or your platform, you should see:

      • Vehicle on the map

      • Recent events (ignition on/off, trips)

      • OBD-based metrics (where configured).

  4. Remote Management

    • Firmware updates and config changes can be managed via:

      • Teltonika FOTA (for firmware/config)

      • Platform-specific interfaces (if integrated with FOTA APIs or proprietary tools).

4. Operational Best Practices

  • Keep a mapping of:

    • Vehicle ID ↔ Device IMEI ↔ SIM ICCID.

  • Use appropriate configs:

    • 12V profile for light-duty fleets

    • 24V profile for heavy-duty fleets

  • Use FOTA groups to:

    • Roll out firmware/config updates in a controlled way.

  • Monitor:

    • Devices that have not reported for some time.

    • Devices with frequent disconnects or poor GNSS, and investigate (see Troubleshooting).