Sign in Talk to us Start a trial
Start a trial

Design and software studio
Color

Odometer and trips from the driver app

Type an odometer reading and start and end a trip on your truck from the Shift tab.

For
DriverDispatcherFleet managerAdministrator
Hosting
Any hosting
Devices
All devices
Business
TowingFleet

Checked against Pop Dispatch 0.1.0

The Shift tab holds a Trip card and an Odometer card under the shift controls. You will be able to start a trip, end it with the closing reading, and add an odometer reading at any time.

Before you start #

  • A driver account linked to a driver record, and a truck that is in service.
  • The Fleet license flag is on (dispatch_fleet).
  • Type the odometer as a whole number in the truck's own unit, kilometers or miles. The label shows the unit.
  • Your location is shared while a trip runs, as it is during a shift. Keep the screen open.

Add an odometer reading #

  1. Open the Shift tab and find Odometer.
  2. Choose the truck and type the Reading from the dashboard. Add a note if it helps.
  3. Press Save reading. The message says "Sent." or that it is saved on the phone.
  4. A reading lower than the last one is kept, and the page says "This is lower than the last reading. The office will confirm it." A very large jump is kept and flagged too. A manager confirms, corrects or marks a meter replacement.

Start and end a trip #

  1. Open the Shift tab and find Trip. It says "No trip is running" until you start one.
  2. Choose the truck. A truck that is out of service cannot start a trip.
  3. Add the Purpose, From, To and Odometer if you have them. All four are optional. Press Start trip.
  4. The card then says "Trip running since" with the start time. Only one trip runs on a truck at a time.
  5. When you arrive, type the closing Odometer (optional) and press End trip. The app sends your last positions first, then ends the trip.
  6. Both readings join the meter log with source trip.
Technical details
  • API calls: POST /fleet/assets/:id/meters (meter, value, read_at, optional note), POST /fleet/trips (asset_id, person_id, and optionally purpose, origin, destination, odometer) and POST /fleet/trips/:id/end (optional odometer). Correcting a flagged reading is POST /fleet/meters/:id/correct, for dispatchers and managers.
  • A trip started without a signal waits in the Outbox. Ending it waits behind it, and the Outbox shows "Waits for an earlier item to be sent." A trip end uses the id the start receives.

If something goes wrong #

  • "Enter the reading as a whole number." Remove decimals and spaces.
  • "Choose a truck for this trip." Pick the truck first.
  • conflict (409): "This cannot be done right now." A trip is already running or ended on this truck, or the truck is out of service.
  • not_found (404): "That record has been removed."
  • feature_not_licensed (403) or licence_read_only (403): ask your manager to restore the license.