No Click and No Crank: Follow the Missing Command

A no-click, no-crank diagnosis is not a starter guess. Follow the start command from the driver input through authorization, interlocks, module command, relay control, and starter activation.

What no click and no crank means

A no-click, no-crank condition means the engine does not rotate when Start is requested and there is no obvious relay or starter solenoid click. Separate this from slow crank and click/no-crank complaints. Those symptoms use different diagnostic branches.

Start with basic power

Before chasing the command path, check battery condition, cable condition, terminals, and grounds. Weak available power or poor connections can make modules, relays, and the starter act dead. If basic power is suspect, correct that direction and retest before continuing.

Scan, but do not let codes make the decision

Use a scan tool to check communication, codes, and live data when supported. Helpful data may include start request, security or authorization status, park/neutral or clutch/brake status, and crank command. A code points to a diagnostic direction, not a failed part. No codes do not prove the start system is good. Generic OBD-II may not display the needed body, security, interlock, or starter-control data.

Follow the command path in order

The generic path is driver input, start authorization, interlocks, module command, relay control, and starter activation. If the module does not see the start request, stay on the input branch. If start-request scan data are not available, use vehicle-specific service information and a wiring-diagram-based method to prove whether the start input reaches the appropriate module or control point before moving to authorization. If the request is proven but authorization or an interlock is blocked, diagnose that blocked input before moving downstream.

When authorization or interlock data are missing

Unavailable authorization or interlock scan data are not the same as good data. If the scan tool does not show the needed security, range, clutch, brake, or related permission information, verify that stage with service information, approved circuit tests, or enhanced diagnostic access. If the permission inputs cannot be verified with the available tooling or information, stop rather than continuing as though crank permission is proven.

When the module should command crank

If request and permission data or approved alternate tests look correct, check whether a crank command or starter-relay command is being issued. If no command is issued, the next direction is module power, ground, network, configuration, or service-information-guided module testing. Do not condemn a module from one data screen alone.

Relay control and starter activation

If the module commands crank, test the starter relay control side, feed side, and switched output path with the wiring diagram. If the relay output is present, check whether the solenoid command reaches the starter and whether the high-current feed and ground path can support starter operation. Exact test points and specifications require vehicle-specific service information.

Confirm the repair direction

After the fault direction is corrected, retest the same no-click, no-crank condition. Confirm normal cranking and recheck related codes or data. If the symptom remains, return to the first point in the path that was not proven instead of replacing parts by guesswork.