BMW E90 2A9A intermittent cam crank synchronization fault live data test

An intermittent 2A9A on an E9X N53 does not tell me to replace a crankshaft sensor or condemn the timing chain. It tells me that the DME could not accept the relationship between crankshaft and intake camshaft information. I want to catch what changes when the fault appears, then test the branch supported by that evidence.

2A9A DME: Crankshaft - inlet camshaft, synchronization

I start by preserving the fault details before clearing anything. I record whether 2A9A is currently present, how many times it has occurred, the engine speed and temperatures in the freeze frame, system voltage, and any companion DME faults. A one-time event during cranking is a different problem from a repeatable hesitation at warm part load.

That distinction matters in the owner discussions behind this article. The N53 E90Post owner had already replaced the crankshaft sensor. The saved fault was initially intermittent, and the owner later saw system voltage move from about 14 V to 12.5 V around repeated hesitations. That observation is useful, but it does not prove a charging fault. I would time-align voltage with the symptom, check for undervoltage faults in other modules, and test the charging system before blaming the alternator.

A BMW-capable scan tool should record, where the DME exposes them:

• engine speed
• intake camshaft actual angle
• exhaust camshaft actual angle
• intake and exhaust requested angles
• VANOS command or activation values
• system voltage
• oil and coolant temperature
• fault status during the capture

I collect a cold start, a settled idle, a gentle increase in engine speed, and the operating condition that usually triggers the complaint. I do not compare numbers from separate drives by eye if I can log them together. An intermittent event may last less time than it takes to look from one data tile to another.

Read the code as a synchronization problem

The owner reports describe 2A9A as a crankshaft to intake-camshaft synchronization fault. BMW's VANOS training explains why the diagnosis must compare several systems: the DME uses the camshaft sensors to identify cam position, watches those signals as VANOS feedback, and depends on oil pressure to move the camshafts.

That architecture gives me a sensible order. I check fault context and the electrical signal first, compare requested and actual cam position, then move to oil-controlled VANOS behavior and mechanical timing only when the evidence points there. The code is not a parts verdict.

Code descriptions can also vary with the DME and scan tool. A generic reader may show P0016, while BMW software may show 2A9A with wording about crankshaft and inlet camshaft synchronization or an invalid intake cam signal. I record the exact BMW fault text and control-unit variant rather than treating every internet result for P0016 as identical.

The adjacent faults matter. An intake VANOS movement fault, an exhaust-side synchronization fault, several undervoltage faults, or a group of sensor supply faults changes the direction of the test. If 2A9A is the only relevant DME fault, I keep the first round focused on the intake cam signal and the conditions in its fault record.

Separate the sensor, circuit and VANOS clues

I inspect before disturbing parts. Oil or moisture in the intake cam sensor connector, backed-out terminals, poor pin tension, chafing near the front of the cylinder head, or recent work around the valve cover can create an intermittent signal without failing a static resistance check. I also inspect the harness where engine movement can flex it.

A sensor swap can narrow the search if the intake and exhaust sensors are the same correct part. I mark them, inspect both connectors, clear the fault, and reproduce the same operating condition. A fault that moves to the exhaust side points toward the moved sensor. A fault that remains 2A9A keeps the intake-side wiring, connector, reluctor and mechanical system in play. It does not prove the wiring is good.

A multimeter can confirm powers, grounds, obvious shorts and continuity, but it can miss a brief dropout. I use the correct wiring diagram for the exact car and avoid piercing insulation. Loaded circuit tests and terminal checks are more persuasive than an unloaded continuity beep. If manipulating the harness changes the running condition or signal, I stop and inspect that area rather than continuing to shake a damaged circuit.

VANOS deserves a separate look because the N53 uses oil pressure to move both camshafts. ImportCar notes that contaminated oil, incorrect viscosity, inadequate supply, or a hydraulic fault can prevent a camshaft from reaching its requested position in time. I check oil level and condition, verify the oil fitted meets the correct requirement for the car, and compare requested versus actual cam movement. A clean electrical waveform with an actual angle that cannot follow a sensible request points away from a simple signal dropout.

Use a scope when the scan trace cannot settle it

A dual-trace oscilloscope capture is the decisive electrical test when 2A9A is brief and scan data is too slow. I capture crankshaft and intake camshaft signals at the same time, first under a known repeatable condition and then during the failure. The aim is to see whether the intake cam signal disappears, distorts, changes timing, or remains clean while the reported angle goes wrong.

Pico Technology's diagnostic guide gives a relevant example: a cam and crank synchronization complaint returned after a cam sensor was replaced, while a waveform capture and harness wiggle exposed chafed cam sensor wiring. Its cam and crank test also stresses looking at the pattern across 720 degrees of crankshaft rotation. For mechanical correlation, I need a verified known-good waveform from the same engine configuration and the manufacturer's test conditions.

Variable valve timing can move the cam waveform by design. A reputable N53 technical reference advises disabling the oil control valve for a correlation capture so commanded movement does not look like a timing error. That is an advanced workshop test. I follow vehicle-specific technical information, expect related faults to be stored, and do not disconnect controls during a road test.

Decide from the pattern, not the loudest symptom

The result should point to a branch, not a guess. A cam signal dropout while crank remains stable supports an intake cam sensor, connector or signal-circuit fault. A fault that follows a swapped sensor supports that sensor. Several signals changing with system voltage calls for power, ground and charging tests. Clean signals with repeatable cam-to-crank displacement at the specified mechanical test condition justify checking reluctor position, chain timing and tensioner condition.

Requested and actual cam data adds another split. If the requested angle changes and the actual angle follows smoothly, VANOS is responding in that sample. If actual angle lags, sticks or moves erratically while the electrical position signal remains valid, I investigate oil supply, the control solenoid and the mechanical adjuster using the correct N53 procedure. I do not apply an N52 service bulletin to an N53 simply because some fault numbers overlap.

After any repair, I repeat the original capture under the same cold or warm condition, confirm the relevant signals remain stable, rescan all modules, and check that 2A9A does not return. One clean idle is not enough when the original complaint only happened during a warm acceleration. The proof is a matched before-and-after test that covers the event which used to set the fault.