Inspect⚓︎
Fleet managers rely on real-time data and alerts to monitor vehicle status and respond quickly when problems arise. This FAQ helps you understand GPS updates, data quality, and event reporting in INVERS FleetControl.
GNSS Position⚓︎
What Does “GPS Position Is Probably Outdated” Mean, and What Can I Do to Update It?⚓︎
Use case: “Check why a vehicle’s position is not updating and know what to do next.”
When in standby, devices update position periodically (e.g., CloudBoxx: every 30 minutes).
- During vehicle use (immobilizer unlocked), updates occur more frequently.
- The most recent known position is used for reporting. If it is less than one minute old, it is up-to-date. If older, FleetControl displays that the position might be outdated.
Possible causes for outdated positions:
- Weak GNSS signal (e.g., underground parking) - the position updates as soon as possible.
- The telematics unit may have powered down - check the device’s heartbeats for more info.
What Is Live Mode?⚓︎
Use case: “Track a vehicle precisely in real time, for example during theft recovery.”
In Live Mode, a connected vehicle continuously updates its GNSS position.
- Enables accurate tracking but uses more cellular data and API calls.
Status Data⚓︎
Why Are Some Data Points Not Visible on the Inspect Page?⚓︎
Use case: “Understand why certain sensor values do not appear when inspecting a vehicle.”
If you cannot see some data points:
- They are probably not configured for the fleet unit.
- FleetControl hides all unconfigured data points automatically.
What Is the Health?⚓︎
Use case: “Quickly check a unit’s connectivity and usage quality.”
Health rates a unit’s connectivity and usage frequency.
- Calculated from: Events, Heartbeats, and signal strength.
Why Is the Fuel Level Incorrect?⚓︎
Use case: “Explain fluctuating fuel readings for vehicles in motion or on a slope.”
Fuel level is measured by a tank sensor and sent to the CAN bus.
- Measurements can fluctuate if the vehicle is moving or parked on uneven ground.
- Fuel levels can change by up to 15% during trips.
Why Is the Fuel Level Stuck at 100%?⚓︎
Use case: “Know why a full tank keeps displaying 100% even after some driving.”
Most sensors report 100% before the tank reaches full capacity.
- A newly filled vehicle may still show 100% until some fuel is consumed.
Example
A car’s tank holds 50 liters. The sensor reads 100% at only 45 liters. After refueling, it stays at 100% until the car burns 5 liters.
What Are Heartbeats?⚓︎
Use case: “Ensure your vehicle’s telematics unit is still connected to the network.”
A heartbeat is a periodic connectivity update from the telematics device.
- Includes: network provider, signal strength, timestamp.
- Not triggered by events, but sent on a schedule (CloudBoxx: every 15 minutes).
Note
Heartbeats are only available on telematics units that support this feature.
Why Are Heartbeats Missing?⚓︎
Use case: “Troubleshoot missing connectivity updates from a telematics device.”
Common reasons for missing heartbeats:
- One heartbeat missing: Likely due to the SIM briefly reconnecting while passing through a “dead spot” or scanning networks. This is normal.
- Extended missing heartbeats: May mean loose wiring, disconnected antenna, or power loss. Device may need maintenance.
- Vehicle parked in a dead spot: The device has limited or no connectivity.
- SIM blocked by provider: Usually due to data usage limits. INVERS will be notified and work to resolve.
Events⚓︎
What Are Events?⚓︎
Use case: “Track fleet activity and specific triggers using event logs.”
A telematics unit creates an event each time a specific action or condition is detected. Each event includes:
- Event type
- Timestamp
- Current unit status
Some events also include:
- Location
What Are Event Types?⚓︎
Use case: “Understand what each event means for fleet monitoring and reporting.”
Event types are predefined conditions that trigger event creation (e.g., ignition on, doors unlocked).
- View all event types in FleetControl for deeper insights.
- See a full list of event types here.