ZenTrack Power+ – Operations Guide

(For operations, support teams, and fleet admins)

Written By Support Team

1. Purpose & Scope

This guide explains how the ZenTrack Power+ behaves in day-to-day operation and what operations/fleet admins should expect once the devices are deployed.

2. What ZenTrack Power+ Does

Once installed and configured, the ZenTrack Power+:

  • Collects GNSS data: Location, speed, heading.

  • Monitors external sensors (via BLE): Temperature, door sensors, and other connected BLE sensors (if enabled in configuration).

  • Communicates via cellular network to: Backend platforms (e.g., ZenduOne) or other integrated systems.

  • Optionally communicates with BLE beacons if enabled in the specific deployment configuration.

The configuration file determines:

  • Reporting intervals and behaviors.

  • Event profiles (e.g., motion detection, vibration alerts, speed, ignition alerts).

  • Sensor thresholds (e.g., temperature limits, power loss alerts).

3. Daily Operations Flow

Vehicle Use

  • The driver operates the asset normally.

  • The ZenTrack Power+ powers up via the connected power source (7-60V DC) when the vehicle is turned on.

  • The internal battery (~9600mAh) ensures the device continues to function if external power is disconnected.

Data Transmission

The device sends location and telemetry based on:

  • Ignition state (if configured).

  • Movement (motion detected, vibration alerts, etc.).

  • Reporting rules (e.g., periodic by time, distance, and angle).

Platform Visibility

In your backend platform (e.g., ZenduOne), you should see:

  • The asset on the map with a real-time position.

  • Recent events (ignition on/off, trips, sensor alerts).

  • Telematics metrics (voltage, power loss, sensor data) where configured.

Remote Management

Firmware updates and configuration changes are managed via:

  • Topfly DMS Web Portal: For bulk configuration and firmware lifecycle management.

  • MQTT APIs: For integration with internal workflows.

4. Operational Best Practices

  • Keep a clean mapping: Maintain records of Asset ID ↔ Device IMEI ↔ SIM ICCID for tracking and inventory purposes.

  • Use appropriate configurations:

    • Slow reporting: For assets where you need to conserve battery life.

    • Regular reporting: For devices hardwired to a constant energy source to keep the internal battery full.

  • Monitor System Health:

    • Watch for devices that have not reported for extended periods.

    • Investigate devices with frequent disconnects, poor GNSS signal, or low battery alerts.