2003 BMW 745i No-Crank: The CAS Was Offline, but the Climate Module Took the Bus Down

Cas Offline? Find Who Pulled The Bus Down

The 2003 BMW 745i already had a battery, starter, main relay and ignition switch. It still would not crank. The dashboard looked alive, the engine computer held no useful fault and the access module could not be reached. Replacing CAS would have matched the symptom. Disconnecting it first produced a better answer: both body buses stayed down, proving CAS was another victim.

A meter/scope that can observe identified automotive bus lines can support the physical-layer screen once BMW topology and safe test points are known. The AUTOOL DM303 is one option for that bounded work. DM303 can screen identified bus voltage, resistance under the correct powered-down conditions and accessible power/ground signals. It cannot map BMW gateway topology, determine which module to unplug by itself or program/code IHKA.

The DME never received the expected wake request, and diagnostic equipment could not communicate with CAS or modules on K-CAN-S and K-CAN-P. PT-CAN remained healthy. Removing CAS did not release either body bus. Branch-by-branch isolation finally restored both networks when the IHKA climate module was unplugged; the car then started. Replacing, programming and coding IHKA completed the repair.

Stop replacing start-system parts

Stop the parts chain and write down what each replaced component failed to change. Confirm the battery under load, starter circuit integrity and exact no-crank behavior. Does the starter relay receive a request? Do exterior lights dim? Save a complete scan from every bus the tool can reach. A bright dashboard proves only that some power and communication exist. It does not prove start authorization or that all vehicle networks are awake.

Follow the missing wake request upstream

The DME did not receive its expected wake or start-related signal from CAS. Verify the signal path in BMW information rather than treating a missing data item as a wire by the same name. Test both keys, CAS powers and grounds, and the physical start request. In the documented case, support circuits were intact and a second key changed nothing. Communication failure then became the more important fact: the tool could not reach CAS to ask what it was deciding.

Map PT-CAN and both body K-buses

The 7 Series does not have one undivided communication line. PT-CAN modules were available, while body modules on K-CAN-S and K-CAN-P were not. Draw the gateway and splice layout, listing which modules bridge or join each segment. Measure resistance only with power removed and networks asleep under BMW procedure; observe voltage with the vehicle awake. A healthy powertrain bus beside two down body buses directs the search toward their shared area rather than the starter motor.

A silent CAS is not automatically a failed CAS

A module that cannot communicate can be failed, unpowered or trapped on a bus another module has shorted. Test CAS supplies at its connector and inspect its lines, then perform the negative experiment: disconnect the suspected CAS and see whether the rest of the bus recovers. It did not. That result is more valuable than another CAS fault description because a module cannot be the sole device holding a network down after it has been physically removed.

Disconnect the suspect and watch whether the bus rises

Now isolate accessible branches systematically. Predict which modules should reappear after each disconnection and keep ignition state consistent. Inspect water-prone connectors before unplugging half the dashboard. Do not power-probe network pins or repeatedly reconnect a suspected short with modules awake. When IHKA was disconnected, both K-buses recovered and the BMW started. That one change supplied cause-and-effect evidence: the climate controller was internally pulling the shared communication path to ground.

Test	Result	Meaning
PT-CAN communication	Normal	Powertrain network is not globally down
K-CAN-S and K-CAN-P	Modules offline	Body-network fault is shared
CAS disconnected	Buses remain down	CAS is not the sole network offender
IHKA disconnected	Both buses recover; car starts	IHKA internally loads the networks

Isolate branches until one module releases both buses

Confirm IHKA has correct power, ground and pin condition before replacing it; an external short on a connected branch can mimic an internal module fault. Match hardware and software and maintain approved power support during programming. The replacement required BMW programming and coding so the module would communicate and operate within the vehicle configuration. A used or mismatched module may restore bus voltage yet leave climate functions, fault memory or security configuration incomplete.

Program and code the replacement IHKA

With the replacement installed, repeat multiple cold and warm start attempts. Confirm CAS, DME, IHKA and every formerly missing K-bus module communicates. Check starter actuation voltage and the expected wake exchange, then operate heating, ventilation and air conditioning through all modes. Rescan after a road test. The original complaint included a no-crank, but the repair touched a climate controller; both the starting network and the module’s intended function must pass.

Verify start authorization and every body network

Save a before/after topology sheet for future BMW network work. The lesson is not “unplug IHKA on every E65 no-crank.” It is to distinguish the module named by the missing function from the module electrically silencing the bus. The negative CAS test prevented one more unnecessary replacement; the positive IHKA isolation test earned the actual repair.

CAS appeared guilty because it was silent and the engine needed its permission. Disconnecting it proved silence was not guilt. The climate module, far from the starter on a conventional diagram, had removed the communication the starter decision required.