Messages

The Messages section gives you a raw, timestamped stream of every update a unit sends to AVL (parameters + sensors). Use it to diagnose connectivity, validate sensor behavior, and investigate incidents at the most granular level.

Permissions

• Users must have view access to the selected unit(s).
• If units are shared via Shared Groups, users with View Only / Inherit can read messages for those units.
• Admins can query a single unit at a time, even within shared accounts, in accordance with the tenant setup permissions.

Tracing Messages

Follow these steps to trace messages for any unit:

1. Select Unit(s)
• Use the Unit Search field.
• Search by Unit Name or IMEI.
• Only a single unit can be added at a time.
• Units shared via Shared Groups are visible if you have view permission.
2. Choose Source

3. Set Time Range

4. Run Query
• Click Execute to fetch messages.
• Click Cancel to stop a long-running query.
• Use Reset to clear all filters.
5. Review Summary

After execution, a summary strip appears below the mentioned input:

1. Duration: span of time covered.
2. Distance: total route length.
3. Average Speed.
4. Maximum Speed.
6. Explore Results
• Switch between Table View and Graph View using the toggle.
• Use Export to download results to Excel.

Table View

The Table View lists each message as a row with full details.

Columns

Displayed columns depend on unit profile and installed sensors. Common fields include:

• Timestamps: Device Time, Server Time
• Location: Latitude, Longitude, Address, Altitude
• Movement: Speed, Motion/ACC, RPM
• Sensors: Fuel level, Temperature(s), Weight/Axle load
• Electrical: Main/Backup Voltage, Satellites, Accuracy

No assignments displayed in messages table

Graph View

The Graph View visualizes selected parameters over time.

Common Tasks

A) Check if a vehicle stopped sending data

1. Source = Both → Unit = target vehicle → Time = Today (last 2–4h) → Execute
2. Confirm timestamp gaps in Table; verify Voltages/ACC for power issues.
3. If there’s a gap: check SIM/connectivity/device power.

B) Investigate a fuel‑theft claim

1. Source = Sensors → choose the unit → Custom time covering the incident (≤ 6h) → Execute
2. In Graph, add Fuel Level + Speed; look for sharp drops while stationary.
3. Cross‑check exact timestamps & values in Table; export if needed.

C) Validate overspeed complaint

1. Source = Parameters → select unit → relevant Custom range → Execute
2. In Table, sort by Speed (desc) and review Max speed in summary.
3. Use Graph to visualize peaks; check satellites/accuracy for GPS jumps.

Troubleshooting

• No rows returned
• Confirm time window and unit selection; ensure device actually transmitted.
• If querying multiple units, test each unit separately.
• Slow queries
• Reduce window length, limit to a single unit.
• Use Sensors or Parameters (not Both) when you only need one side.

Tracking

API Documentation