Fast route access
Drive / Travel keeps common route and trip actions on Crank Main instead of burying them inside diagnostic menus.
Crank Main • OBD-FREE route context
Drive / Travel
Drive / Travel is the fast Crank Main path for route and trip context. It keeps mapping, travel and recording functions useful even when no OBD-II reader is connected.
OBD-FREEMap / TrackTravel contextGPS utilities
Current capability map
What this section does.
This page describes the capability architecture represented in the current Crank development build. Interface wording may continue to be polished, but the functions below are the working product structure.
Map / Track
GPS route recording and later path review support work, travel and evidence use cases.
Experience bridge
The operator can move into Experience Recorder when the trip needs a richer session record.
GPS favorites
Stored locations and Return Compass tools support repeat field visits and wayfinding.
Travel assistance
Travel resource handoffs can support lodging, food, fuel and transportation searches.
Rental context
Travel/rental workflows can stay separate from the operator’s permanent owned-vehicle history.
Works without OBD-II
The route path remains useful on old vehicles, rentals, equipment and other contexts where there is no code reader.
Selected asset context
When the route belongs to a known asset, the record can stay with that asset packet.
Evidence handoff
Route context can support Motorheads, Driver Suite, Experience Recorder and incident records without needing to duplicate the path.
Operating flow
How it fits together.
Step 1Open Drive / Travel
Step 2Choose route / trip task
Step 3Record GPS context
Step 4Add events / notes
Step 5Save or hand off
Crank truth boundary: Crank does not make OBD-II the price of admission for useful driving records. Route and trip evidence can stand on GPS and operator context alone.