We’re technicians, not part changers.
Crank™ exists to prove the recipe before replacing parts.
Don’t let Crank turn into Cranky. If frustration starts driving the diagnostic path, use the Cool Down Page, write down what is known, and return to evidence.
A trouble code is a clue, not a conviction. A symptom is evidence, not the full diagnosis. The truthful path of least resistance is the one with the fewest guesses and the strongest proof.
S.W.A.T. — Swift. Waste. Attack. Team. A rapid field response method used when waste, downtime, defects, confusion, rework, unsafe drift, or process failure needs to be attacked at the source.
Opening Crank™ Doctrine
Diagnosis is education with a purpose. Guessing is tuition paid to the wrong teacher.
Two hours proving the truth is faster than two hours installing the wrong answer. Strong diagnosis is a value-added component of the technician’s skill set because it protects the customer, the shop, the technician, and the next repair.
Good educations are expensive; bad educations can be exponentially so.
The Engine Recipe
Controlled engine operation occurs when the required variables converge: fuel + air + spark or compression heat + compression + timing + power + ground + sensor truth + actuator response + mechanical condition.
First Crank™ Field Manual Sections
Automotive System Evolution
The computer did not replace the recipe. It became part of the recipe. Crank™ covers mechanical baseline systems, carburetor/points ignition, electronic ignition, OBD-I, OBD-II, CAN/networked modules, drive-by-wire, hybrid/EV, ADAS, and software-controlled responsibility.
OBD-II Library Direction
Crank™ uses dropdown-first filters for code family, code type, make, model, year, engine, module, symptom, and test path. No giant code wall. No parts-cannon guessing. Filter first, prove second.
Safety / Scope Boundary
Crank™ supports diagnostic thinking and documentation. It does not replace OEM service manuals, qualified mechanical inspection, safety procedures, emissions/legal requirements, high-voltage EV/hybrid training, scan-tool documentation, or professional judgment.
OBD-II Guided Workbench
Filter first, prove second. Use manufacturer, model, year, engine, module, symptom, and code-family filters before turning a code into a test path.
Source Notes / References
This page is original Dingfelder field doctrine and practical diagnostic guidance. Verify vehicle-specific procedures, torque specifications, safety requirements, emissions rules, high-voltage boundaries, service information, TSBs, wiring diagrams, and OEM documentation before performing work.