My Garage • route / motion / field evidence

Experience Recorder

Experience Recorder captures what happened around a drive, job, machine session or outdoor activity using GPS, motion, events, notes and photos — with or without OBD-II.

OBD-FREE capableGPS + motionDrop-a-point eventsSession reports

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.

Multiple activity contexts

The recorder can be used for vehicle, work, equipment, outdoor, recreation and other motion sessions rather than assuming every record is a commute.

Selected-asset ownership

When a session belongs to a known asset, the record can be bound to that packet instead of living as anonymous phone data.

GPS path recording

Location samples can become route/path evidence and support later map review.

Motion evidence

Phone motion / IMU samples can be preserved alongside the session when useful.

Drop a Point

A quick event marker lets the operator mark a place or moment during the active session.

Photos and notes

Field observations can be attached to the session rather than reconstructed later from memory.

Compass™ access

The live recorder can hand off to heading/orientation tools when route or field context needs them.

Inclinometer™ access

Pitch/roll information is available as a convenience field instrument within the workflow.

Structured raw files

The session can retain report, motion CSV, GPS CSV, GeoJSON/path and event/manifest files as applicable.

Public / support handoff

Completed session artifacts can be packaged for review without requiring a cloud account.

How it fits together.

Step 1Choose experience
Step 2Confirm asset / context
Step 3Record GPS + motion
Step 4Mark events / photos
Step 5Save session package
Crank truth boundary: Experience Recorder remains useful when no code reader is connected. OBD-II can enrich some sessions, but GPS, motion, operator context and evidence are first-class inputs on their own.