Vanos Rebuild Start Hesitation

[jamesfoley]

Any idea what might have caused this? Both intake valves bent? Wrong VANOS timing could cause this when rotating the cranking during timing checking.

Both valves left an impression on the piston, but unsure if both are bent. I'd imagine if the piston kissed them both then they are equally unhappy, at least one of them is leaking air that you can hear through the plenum.

VANOS was also found to be timed wrong again it seems, so the assumption is it was caused by timing at some point. Odd that its just a single cylinder though.

Next step is head refresh and new valves. Car still ran and drove fine so pretty sure nothing else is technically wrong.

[sapote]

Small update, leak down test found bent intake valves on cylinder 5. ☹

Any idea what might have caused this? Both intake valves bent? Wrong VANOS timing could cause this when rotating the cranking during timing checking.

[jamesfoley]

Small update, leak down test found bent intake valves on cylinder 5. ☹

[Tomba]

would prefer tool32. Your US car right? If possible send a PM with your VIN

[jamesfoley]

Could be, if you read [aif_lesen] in Tool32, we could see which S/W is in and check which one is available.

I have these from DIS and the ECUWorx DME Utility to hand if they're of any use?

Software Ver: 211322001301-J424
Flashes remaining: 30

Programmed control module: 7833144
Basic control module: 7833145
Hardware number: 1B
Software number: 13
Diagnosis index: 30

Coding index: 00
Bus index: 60
Modification index: 01

Date: 03.11. 1
Supplier: SIEMENS


If not I'll pop out later and run the Tool32 job

[Tomba]

The DME flash counter is still at 30 which suggest it has never been touched since 2001? That's the only thing that feels kinda weird.

Could be, if you read [aif_lesen] in Tool32, we could see which S/W is in and check which one is available.

[jamesfoley]

Can't find anything unusual yet in the results shared.
Are we now tracking 2 problems 1. hard start and 2 fuel status 8? Or do these seem to be linked?

Like sapote, I would rather back up your DME data and check it. Eventually also flash it with latest software.

Yea thats correct.

1. Intermittent hard start regardless of how long the car has been sitting or engine temperature.
2. Fuel system status 8 appearing randomly when driving, though doesn't seem to affect performance. O2 sensors appear to drop to 0v when this occurs suggesting unburnt mixture?

The fuel status issue was discovered when capturing logs to figure out what might be causing the hard starts. Currently no evidence to suggest that they are related however.

Writing to the DME myself scares me a little, however if there was a way to safely dump the map from the DME to compare it with a known good map I could maybe try that.

The DME flash counter is still at 30 which suggest it has never been touched since 2001? That's the only thing that feels kinda weird.

[Tomba]

Can't find anything unusual yet in the results shared.
Are we now tracking 2 problems 1. hard start and 2 fuel status 8? Or do these seem to be linked?

Like sapote, I would rather back up your DME data and check it. Eventually also flash it with latest software.

[jamesfoley]

For normal engine, it should be status 4 and not 8:

1 Open loop due to insufficient engine temperature (Engine temperature is not used much these days to determine Closed Loop status, usually O2 sensor activity is used to determine when to switch to Closes Loop status)
2 Closed loop, using oxygen sensor feedback to determine fuel mix
4 Open loop due to engine load OR fuel cut due to deceleration
8 Open loop due to system failure
16 Closed loop, using at least one oxygen sensor but there is a fault in the feedback system

The STATUS_DIGITAL data only displays fuel cut as 1 for cut, 0 for no cut. The graph makes it look weird as it does some smoothing to show half values.

I'm not 100% sure how I'd get both the fuel status and the fuel cut data logging together though.

STAT_KL50_EIN is another odd looking one. Tool32 says this is Status Anlasser which is Starter state, not sure if this related to speed or something.

[sapote]

For normal engine, it should be status 4 and not 8:

1 Open loop due to insufficient engine temperature (Engine temperature is not used much these days to determine Closed Loop status, usually O2 sensor activity is used to determine when to switch to Closes Loop status)
2 Closed loop, using oxygen sensor feedback to determine fuel mix
4 Open loop due to engine load OR fuel cut due to deceleration
8 Open loop due to system failure
16 Closed loop, using at least one oxygen sensor but there is a fault in the feedback system

[jamesfoley]

Tomba Should be attached. Looks like this is the data that DIS uses for its status pages...

[Tomba]

comment : Status Schubabschaltung

mean fuel cut during deceleration (throttle pedal 0%).





Can you read,
STATUS_ADAPTIONSBLOCK_06
STATUS_ADAPTIONSBLOCK_16
STATUS_ADAPTIONSBLOCK_26 and
STATUS_ADAPTIONSBLOCK_83

and post results in a text file by copy-ing the results from the results screen?

[jamesfoley]

I don't suppose anyone has the translations for the results of the Tool32 STATUS_DIGITAL job?

I have a rolling log with some suspect graphs, but I'm not sure what the datapoints translate to. STAT_SA_EIN for example. https://datazap.me/u/jamesfoley/e46-...?log=0&data=42

[jamesfoley]

So not during idling?

Correct, it’s never happened just leaving the car to idle. It also doesn’t seem to happen when the car is cruising at a fixed RPM. Only when there is a change in RPM.

[sapote]

Not sure anything has changed, looking through all of my logs I get fuel status 8's at all sorts of RPM, its never been just high RPM. Just seems to be when coming off throttle, so even little throttle inputs cause it.

So not during idling?