FM-AUTO · Crank™ · Field Handbook™ Rev v36l

Crank™ OBD-II Guided Workbench

Crank™ — the direct connection between you and your car. This Field Handbook library is the technical reference behind Crank’s OBD-II thinking. Search the library, build a clearer repair story, and help your mechanic understand what you mean. Crank helps you speak the same language.

A code is a clue, not a convictionFilter first, prove secondWe’re technicians, not part changers
Open Guided WorkbenchLearn About the Crank AppCool Down Page

OBD-II Library · Mechanic-ready context · Driver-controlled records

Connect Your Car. Speak Its Language.

Crank helps you speak the same language. This library is the public Field Handbook path behind Crank’s OBD-II thinking: search the code, keep the context, and remember that the code is the beginning of the conversation — not the end of the diagnosis.

A code is a clue, not a convictionDiagnose first. Replace second.My V.A.U.L.T. Records stay yoursNo parts guessing

For drivers

Look up what the vehicle may be reporting, collect notes, and understand the safer next question to ask.

For DIY repairs

Save the record before unplugging parts, clearing codes, or chasing symptoms without a path.

For your mechanic

Share clearer context before you drive in, schedule repairs, or have the vehicle towed to the shop.

Help your mechanic understand what you mean

Bring a better story than “the light came on.”

You drive the vehicle every day. You are usually the first person to notice the rattle, scrape, vibration, pull, smell, leak, warning light, or odd behavior. Crank helps turn those observations into organized repair context.

Supported diagnostic codes and selected code recordsVehicle, adapter, symptom, and operator notesPhotos of visible concerns such as tires, brakes, exhaust, connectors, leaks, or warning lightsBefore-and-after repair records stored locally under your control

Repair boundary

Crank does not guess parts.

A reputable diagnostic path verifies before replacing. Codes can point toward a system, circuit, or condition, but many problems come from wiring, connectors, grounds, fuses, moisture, corrosion, mechanical faults, or vehicle-specific procedures.

Crank helps organize the conversation. It does not replace a qualified diagnosis, prescribe parts, or claim that a component is bad just because a code appears.

How these pages work together

Product page up front. Field reference underneath.

/crank/ is the public product page for the app: what Crank does, how it protects vehicle and mobile-device data, and how it works with or without an OBD-II adapter.

This OBD-II Library stays in the Field Handbook as the technical reference: code lookup, guided context, safety boundaries, and diagnostic discipline.

Crank helps you speak the same language. The app organizes the record. The library helps explain the code path.

Mechanic-ready context

Share the story, not a parts guess.

Crank helps drivers organize supported code-reader data, notes, photos, and condition records before they drive in, schedule repair, ask family for help, or have the vehicle towed.

It does not tell the user what part to replace. Many problems come from wiring, connectors, grounds, fuses, moisture, corrosion, mechanical faults, or vehicle-specific procedures.

Open Crank™ Product PageWhy codes are clues

Using the Crank app?

The Crank™ product page stays simple on purpose. It explains the app, the privacy promise, My V.A.U.L.T. Records, OBD-II connected use, and no-adapter daily-driver tools.

This Field Handbook page stays deeper. Use it as the technical reference behind the app: search the code, build the diagnostic context, and remember that a code is the beginning of the conversation — not the end of the diagnosis.

Best path: use the Crank app to capture supported records, photos, notes, and reports. Use this library to understand the code family and prepare better repair questions.

Learn About the Crank AppSearch the OBD-II Library
Crank™ automotive diagnostic presenter

Input Presenter Card

Build the diagnostic path

Start with what you know.

Library: 13,258Hunt Requests: crank@dingfelder.co
Generic OBD-II emblem

Start fast

Guided workbench lanes

Start from the symptom or code family. Crank loads the path, keeps the context, and reminds you that evidence comes before parts.

Common quick paths

Quick-launch code paths

Smart filter workbench

Master filters

The master filters mirror into the Input Presenter Card and keep the compact results honest.

Ready.

Library coverage

13,258 loaded records / condition paths

Current source-book run is closed. Crank now pivots from bulk import to guided presentation, hunt requests, and verified path expansion.

PPowertrainEngine, fuel/air, ignition, transmission, diesel, hybrid, manufacturer-enhanced paths.
BBody / SRSBody, cabin, restraint clues with information-only SRS boundaries.
CChassisABS, brake, traction, stability, suspension, vehicle-control caution paths.
UNetworkCommunication, missing data, no-response, gateway, module truth paths.
GOHunt RequestsNo verified path yet? Crank captures the context and routes it to crank@dingfelder.co.
✓Truth PathEvery code remains a clue. Power, ground, mechanical, sensor, actuator, and network truth come first.

Compact results

Scannable rows first

Load a row into the Data Presenter Card for full depth. This prevents a giant wall of full cards.

Crank doctrine

Teaching cards

1A code is a clueA DTC reports a monitored condition. It does not automatically prove the named part failed.
2Low voltage liesBattery, charging, grounds, fuses, voltage drop, and sleep/wake behavior can create false paths.
3U-codes need proofPower, ground, connector, network integrity, scan-tool reachability, and wake state come before modules.
4Misfire needs evidenceSpark, fuel, compression, air, timing, and cylinder contribution beat plugs-by-default.
5Fuel trim needs contextTrim, O2/lambda, exhaust, air leaks, fuel pressure, and sensor plausibility must agree.
☕Don’t let Crank turn into CrankyStop, breathe, regroup, document facts, and return with proof.

Safety / scope boundary

SRS / airbag / pretensioner records are information only. Do not probe, jump, meter, unplug, repair, or disturb SRS circuits, airbags, pretensioners, squibs, or crash sensors without verified service procedures, battery-disconnect/wait-time rules, correct tooling, and qualified repair guidance.

Brake / ABS / stability records affect stopping, steering, traction, suspension, and vehicle control. Do not road-test, disable, bypass, bleed, repair, or calibrate brake/ABS/stability/suspension systems without verified service procedures, proper tooling, and safe test conditions.

Network / module boundary: U-codes do not prove a bad module until power, ground, network integrity, connector condition, software/configuration, battery voltage, scan-tool communication, and wake/sleep behavior are verified.

Hybrid / high-voltage boundary: high-voltage records require qualified procedures, correct PPE, isolation rules, and verified service guidance.

Source notes / references

Crank™ includes controlled imports from completed OBD source-book work plus original Dingfelder doctrine, safety boundaries, and public app positioning. Imported definitions are diagnostic starting points and must be verified by make, model, year, engine, module, calibration, vehicle-specific service information, wiring diagrams, TSBs, and safe procedures before repair decisions.