---
title: "Troubleshooting: \"Some Asset Meters Show 0\""
description: Understand why Odometer or Run Hours show 0 based on whether the source is Device, Perspio, or Customer (ERP).
---
[Skip to content](https://help.perspio.io/help/troubleshooting-some-asset-meters-show-0#main-content)
English
Show submenu for translations
Open main navigation
Close main navigation
- English
Show submenu for translations
- [Contact us](mailto:servicedesk@perspio.io)
[Contact us](mailto:servicedesk@perspio.io)
How can we help you?
- There are no suggestions because the search field is empty.
1. [Perspio Help Centre](https://help.perspio.io/help?hsLang=en)
2. [Assets](https://help.perspio.io/help/assets?hsLang=en)
3. [Asset Configuration](https://help.perspio.io/help/assets?hsLang=en#asset-configuration)
# Troubleshooting: "Some Asset Meters Show 0"
## Learn why Odometer or Run Hours may show 0 in Perspio Asset Inspector. This guide explains how Device, Perspio, and Customer ERP meter sources behave, when calibration is required, why ignition wiring matters for Run Hours, and why ERP-based meters do not auto-increment.
#### Overview
If **Odometer** or **Run Hours** show **0** in Asset Inspector, the cause is usually related to the **meter source**.
In Perspio, these meters can come from three sources:
- **Device**
- **Perspio**
- **Customer (ERP)**
Understanding the source is the fastest way to identify whether the value is expected, needs calibration, or depends on another system.
#### Why this happens
Odometer and Run Hours do not always behave the same way, because each source updates differently.
A meter may show **0** because:
- The device starts counting from zero
- The meter has not been calibrated
- Ignition is not wired correctly
- The vehicle manufacturer does not expose the data
- The value comes from a customer ERP and does not auto-increment
---
#### Meter sources
#### 1) Device
The **Device** source comes from the telemetry device.
### How it behaves
- On **OBDII trackers**, the value may come from the vehicle **ECU**, but only if the manufacturer allows that data to be collected.
- On **wired devices** such as **G70s**, **FMM130s**, and similar devices, the meter starts from **0**.
### Why it may show 0
A Device meter may show 0 because:
- The device was newly installed and started from zero
- The vehicle manufacturer does not expose ECU data
- The expected meter data is not available through the device
### Important
For OBDII devices, Perspio can only display what the vehicle allows the device to read.
---
#### 2) Perspio
The **Perspio** source is calculated by Perspio.
### How it behaves
- Starts from **0**
- Must be **calibrated at device installation**
- **Run Hours** only increment if **ignition is wired correctly**
- Perspio increments Run Hours based on **Trip Start / Trip End event triggers**
### Why it may show 0
A Perspio meter may show 0 because:
- It was not calibrated after install
- The calibration was missed or entered incorrectly
- Ignition is not wired correctly
- Trip Start / Trip End events are not being triggered as expected
### Important
If a wired device has no proper ignition input, Perspio will not increase **Run Hours** correctly.
---
#### 3) Customer (ERP)
The **Customer** source comes from the customer’s external system, such as:
- **Syrinx**
- **Baseplan**
- Inspection platforms such as **Do Forms**
- **SafetyCulture**
- Other ERP or external systems
### How it behaves
- Value is supplied by the customer system
- It does **not auto-increment in Perspio**
### Why it may show 0
A Customer meter may show 0 because:
- The customer system is sending 0
- The external source has not been updated
- The sync has not occurred yet
- The meter is not being maintained in the external system
### Important
If the source is Customer (ERP), the value must be updated in the source system, not in Perspio.
---
#### What to check
#### If the source is Device
Check:
- whether the asset is using an **OBDII** or **wired** device
- whether the vehicle manufacturer allows ECU meter data to be read
- whether the device was newly installed and started from zero
### Expected behaviour
- **OBDII**: may stay at 0 if ECU data is not available
- **Wired devices**: may start from 0 unless another source or calibration strategy is used
---
#### If the source is Perspio
Check:
- whether the meter was **calibrated at install**
- whether the starting value was entered correctly
- whether **ignition wiring** is connected correctly
- whether **Trip Start / Trip End** events are occurring
### Expected behaviour
A Perspio meter should not remain at 0 after installation if:
- calibration was completed
- ignition is wired correctly
- the asset is generating trip events
---
#### If the source is Customer (ERP)
Check:
- which external system owns the value
- whether that system has the correct meter reading
- whether the integration sync has run
### Expected behaviour
Customer-source meters do not increase automatically in Perspio. They only change when the external source updates them.
---
#### Quick troubleshooting guide
### Odometer shows 0
Possible causes:
- Device source is OBDII and ECU data is unavailable
- Device source is wired and started from 0
- Perspio source was not calibrated
- Customer source is sending 0
### Run Hours shows 0
Possible causes:
- Perspio source was not calibrated
- ignition is not wired correctly
- Trip Start / Trip End events are not firing
- Device source is not receiving engine/run data
- Customer source is sending 0
---
#### Best practice
When installing a new device:
- Confirm which **meter source** will be used
- Calibrate **Perspio** meters immediately after installation
- Verify **ignition wiring** on wired devices
- Confirm whether **OBDII ECU data** is available
- Do not expect **Customer (ERP)** meters to auto-increment in Perspio
- [Introduction](https://help.perspio.io/help/introduction?hsLang=en#main-content)
- [How to's](https://help.perspio.io/help/introduction?hsLang=en#how-tos)
- [Assets](https://help.perspio.io/help/assets?hsLang=en#main-content)
- [Asset Inspector](https://help.perspio.io/help/assets?hsLang=en#asset-inspector)
- [Utilisation Module](https://help.perspio.io/help/assets?hsLang=en#utilisation-module)
- [Configuration](https://help.perspio.io/help/assets?hsLang=en#configuration)
- [Events](https://help.perspio.io/help/assets?hsLang=en#events)
- [Servicing](https://help.perspio.io/help/assets?hsLang=en#servicing)
- [Asset Configuration](https://help.perspio.io/help/assets?hsLang=en#asset-configuration)
- [Device Configuration](https://help.perspio.io/help/assets?hsLang=en#device-configuration)
- [Explorer](https://help.perspio.io/help/explorer?hsLang=en)
- [Dashboards](https://help.perspio.io/help/dashboards?hsLang=en#main-content)
- [Configuration](https://help.perspio.io/help/dashboards?hsLang=en#configuration)
- [Reports](https://help.perspio.io/help/reports?hsLang=en#main-content)
- [Available Reports](https://help.perspio.io/help/reports?hsLang=en#available-reports)
- [Groups](https://help.perspio.io/help/groups?hsLang=en#main-content)
- [Security Groups](https://help.perspio.io/help/groups?hsLang=en#security-groups)
- [Asset Groups](https://help.perspio.io/help/groups?hsLang=en#asset-groups)
- [Geofences](https://help.perspio.io/help/geofences?hsLang=en)
- [Workflows](https://help.perspio.io/help/workflows?hsLang=en)
- [Administration](https://help.perspio.io/help/administration?hsLang=en#main-content)
- [Settings Module](https://help.perspio.io/help/administration?hsLang=en#settings-module)
- [Admin Panel](https://help.perspio.io/help/administration?hsLang=en#admin-panel)
- [Devices](https://help.perspio.io/help/devices?hsLang=en#main-content)
- [Troubleshooting](https://help.perspio.io/help/devices?hsLang=en#troubleshooting)
- [Installation Guides](https://help.perspio.io/help/devices?hsLang=en#installation-guides)
[](https://perspio.io)
2/50 Yeo St, Neutral Bay NSW 2089
[mailto:servicedesk@perspio.io](mailto:servicedesk@perspio.io)
Copyright © 2026 Inauro