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

Crank™ OBD-II Guided Workbench

A bright automotive diagnostic workbench for finding the truthful path behind the code. Enter what you know, press the green GO flag, and Crank turns the input card into the data card without moving the environment on you.

A code is a clue, not a convictionFilter first, prove secondWe’re technicians, not part changers
Open Crank™ CalculatorCool Down Page

Crank is the instrument.

The environment stays anchored: Crank holds the same instrument card while it changes from input to output. The v36g recovery pass restores the presenter layer and uses the approved open-hand Crank presenter asset and the yellow-outline card geometry: face and shoulders visible, hands opened into a true presenter pose, boots below, and the chest core revealed through a centered punched card opening.

Workflow: choose the code, vehicle, module, symptom, or quick path → press GO → review the Data Presenter Card → use Next Page, Back, or New Code.

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 entry tiles

These preload the Input Presenter Card. Press GO when ready.

Common quick paths

One-tap preload chips

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 the completed uploaded OBD Advisor source-book segment workflow plus original Dingfelder doctrine and safety boundaries. 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.