DBW randomly fails

I am having these same issues in a MK6 Golf R. Throttlebody is a brand new Bosch 68mm, EPC light on the dash will come on and off and car will lose throttle input. Stumped as to what this could be.

In my instance yes, enough so that both EPC and CEL come on, which usually work independantly.

It sounds just like tps or pps erro. check the calibration of the sensors.

You actually might be right… I have checked them before but maybe I have my tolerance too tight.

Actually I excluded the theory of 2nd cpu reset, what is good, as it would be very serious problem.
Could you explain me how do you use CAN controlled DBW functionality ?

Also, did the problem on 3.037 occur when you modified any data in ECU ? Or just during driving?

It actually started happening on 3.032 after the car had been sitting for a few months, didn’t happen prior to this. So I updated to 3.036, recalibrated the DBW and it drove fine, yesterday was a dyno day and the car wouldn’t stop throwing the EPC light, however I’m currently waiting on a new key.dat because I can’t open up the V3 software. Missed the dyno session unfortunately.

Dbw isn’t controlled by CAN in this instance

It was a question for derUltraTT :slight_smile: Your new key has been just sent.

Ah yes, didn’t mean to hijack haha, thought it may have been the same issue. I’ll comment if I see any resemblance in testing

It happens during driving…independed if PC is connected or not. The 3.037 was also just during decent driving…i updated the vehicle with new SW and same little stuff i changed offline. Then i was driving with PC connected just for logging.

Regarding DBW and CAN control. I use it as an extension for CC logic. CC buttons are connected to a different device and i send them to EMU via CAN.
If i hold +/resume button i send a fixed DBW target via CAN as long as the button is pressed (but i dont send the actual resum button press in this case). If i release the button, then i send button press for “CC set” to be back in the real CC mode (and CAN DBW value 0). In any other situation i don’t use CAN DBW (use CC in emu defined way) but the message is permanently sent with value 0. But the issue doesn’t happen during DBW CAN control…i just happend for now during pedal control.
If u see a CAN relation, i can try to catch up the event with a raw CAN logging. Let me know if this is helpful (and which format u prefere for CAN logging).

There is some additional debugging for DBW in version 3.038. I would very much appreciate it if you installed this version and sent me a log when your throttle fails. This debugging should be very valuable in finding the issue.
Unfortunatelly I’m not able to reproduce the issue on the bench.

1 Like

Thx a lot. Will update tomorrow and perma log then.
Probably it’s a me specific issue. And the occurance is quite rare compared to how much i drive. One time per week to one time per two weeks…and i drive around 600km per week.

Your issue is at the top in our bug tracker system :frowning:

Thats not good…will try my best to support u.
But u can send me as much SW for debug as u want…i daily use the vehicle and drive a lot.

Jadzwin do you still need logs of this issue? We had the same problem last weekend on .37 and managed to improve it slightly by using the second pps sensor in our BMW pedal. But hoping you’ve got it fixed already in .38!

Let me know if you want the logs

if you have a log from 3.037 with this issue please publish it. I will confirm if it is caused by tps / pss error or if it the same problem as derUltraTT has.

Here’s the log - happened consistently towards the end of a drift lap. 06:30 in this one is where a major dropout occurred.
19125534.BG3 (5.2 MB)

You have just DBW error connected to the PPS sensor short to 5V.
Check on the log. It is just configuration issue and it is not connected to derUltraTT issue.

maybe max valid voltage is set to low on this one

for sure the sesnors parameters are not ok.
I would set 4.8V as max voltage

Thanks guys! I’ll set max voltage higher :+1: