Trips and GPS
From GPS points to trips
Section titled “From GPS points to trips”While the truck runs, the kit sends its position and speed. Roudiy groups those points into trips so you can answer everyday questions: where did TRK-103 go yesterday, how long did it take, how many miles?
- A trip starts when the truck reaches 5 mph.
- A trip ends after the truck stays below 5 mph for 5 minutes.
- At a state border the trip ends and a new one opens. That way every trip is in one state, which is what IFTA needs.
So a run from Dallas to Oklahoma City with a fuel stop shows up as several trips: Texas to the fuel stop, the fuel stop to the border, and the Oklahoma part.
Each trip in the Trips tab has a start and end time, duration, vehicle, driver, from and to, miles and state. Next to the miles, Roudiy tells you where they come from: From the engine odometer (ECM) or From GPS (no engine odometer). The engine odometer is preferred when the KD032 provides it. The tab shows the last 7 days by default and up to 31 days at once, and you can export the list as CSV.
Stops and idling
Section titled “Stops and idling”Between trips the truck is stopped. Roudiy separates two kinds of standing still:
- Stop: the truck is not moving. History shows it as Stopped 25 min, for example.
- Idle: the ignition is on and the truck has not moved for 3 minutes. The engine burns fuel while nothing happens, which is why fleets watch idling.
A day without driving still shows stops if the ignition was on: No trips on this day — The truck didn’t move on Sep 14. Stops still appear if the ignition was on.
Fleet View statuses
Section titled “Fleet View statuses”Fleet View gives every truck one status, so you can scan the fleet at a glance.
- MovingIgnition on, 5 mph or faster
- IdleIgnition on, 3 min without moving
- Ignition offShown as Off; kit sleeping
- OfflineKit not reporting
- No dataNothing to show
| Status | What it means | What you can do |
|---|---|---|
| Moving | Ignition on and driving at 5 mph or more. | Follow it live, start a live stream. |
| Idle | Ignition on, not moving for 3 minutes. | Check why the engine is running. |
| Ignition off | The truck is parked with the engine off; the kit sleeps. | Live video and snapshots are unavailable until the truck runs. |
| Offline | The kit stopped reporting. The card says Offline · Last seen 2 h ago. | Check the kit in Device Hub. |
| No data | Roudiy has no data to show for this truck. | Check in Device Hub that a kit is paired and online. |
When a truck is offline, its Live tab says Offline — last seen 2 h ago. Showing the last known location. The pin stays where the truck was last seen; it is not where the truck is now.
The vehicle list and map refresh every 30 seconds. The footer says Live and Updates every 30 s.
GPS gaps
Section titled “GPS gaps”Sometimes the kit has no location for a while, for example in a tunnel. Roudiy does not invent a route for that stretch.
- In History, a GPS gap is drawn as a dotted line from the last known point to the next one, and the timeline shows No GPS data.
- In IFTA, a gap of more than 10 minutes while the truck moved at least 1 mile is listed as a data-quality warning, because those miles may be in the wrong state.
History and playback
Section titled “History and playback”The History tab replays one truck’s day: trips and stops on a timeline, the route on the map coloured by Moving, Idle, Ignition off and No GPS data, and playback at ×1, ×10 (default) or ×60. Below the map, charts show Speed, mph, Fuel, % and RPM.
Engine data needs the KD032
Section titled “Engine data needs the KD032”Speed and position come from the dashcam’s GPS. Fuel level, RPM, coolant, battery, the engine odometer and fault codes come from the engine through the KD032 gateway. Without it, the charts say No engine data, telematics says No ECM data yet, and trip miles come from GPS. Values the truck does not report show Not available.