The direct connection
Crank’s core expression remains: “The direct connection between you and your car.”
My Garage • mission / public resources
About Crank explains the product’s mission, privacy posture and relationship to Dingfelder Enterprises, A.I.R.O.N., V.A.U.L.T. and the public technical resources behind the app.
Current capability map
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.
Crank’s core expression remains: “The direct connection between you and your car.”
The same asset-owned evidence architecture now extends to equipment where CrankScope, PM Center, documents and other workflows need a persistent machine identity.
The app is designed around records controlled by the operator rather than an account-first or cloud-first business model.
Supported OBD-II data can enrich Crank, but GPS, phone sensors, records, photos, PM, field tools and equipment workflows do not depend on an OBD port.
Crank carries industrial evidence, monitoring and workflow discipline into an operator-facing automotive/equipment product.
Evidence is organized for later review instead of treated as disposable screen output.
The website and Field Handbook provide deeper explanations, training and diagnostic reference.
Crank is designed to support decisions and documentation without pretending to be emergency services or a manufacturer programming tool.
Crank is designed and developed by Dingfelder Enterprises as part of a larger family of practical engineering and industrial-intelligence systems.
Operating flow