Any way to make cruise control less aggressive?

[airbus]

Hi all,

I have a VW Golf 1.6TDI 2011 bluemotion model with 97K miles, CR Engine. The car has been scanned with VCDS and there are no faults logged.

Recently I have been noticing an issue with my Cruise Control at lower speeds, in particular speeds below 60mph. For instance, I set the speed to 50mph on the cruise on flat ground (around 1400rpm), the cruise will then reach the set speed and keep blipping the throttle every couple of seconds or so, maintaining the speed to the point where myself and passengers feel it through the seat constantly. The 'blip' is not enough to change the speed on the speedo but enough to just feel fuel flow coming in then shutting off constantly. Turning the cruise off stops this effect...

I logged lots of data the cruise may be getting using VCDS including MAF, Boost, EGR and all were pretty close between actual/specified. After that I went into engine basic settings and did all the tests available and the car passed all of them. I then tried ABS Sensor logging to see whether the speed data was being miss-fed to the cruise. The front 2 sensors varies between each other by +/- 1kph, unsure whether this is normal but I guess so with the front wheels turning slightly?

Here is a link to a chart I compiled of my ABS Sensor logging.


I am stumped on what could be causing this aggressive attitude to the cruise. When the cruise is turned off power is smooth as expected.

Has anyone else experienced these symptoms and cured it by some other means I may have missed? If not, is there any tweak that can be done in the engine control module by way of adaptation etc to make the cruise a little more docile?

Thanks for reading!

 

[Uwe]

I'm not aware of any way to de-sensitize the cruise.

I don't know what's causing the power fluctuations, but I think a +/- 1km/hr wheel speed variation is to be expected since 1 km/hr is the resolution of the data.

What I would suggest logging is the vehicle speed as the ECU sees perceives it, and the amount of power it's applying. The former should be straightforward enough, the latter is a bit more of a challenge since I really don't know what ECU this engine has. I would urge you to post up an Auto-Scan so we can see what this car is made of.

-Uwe-

 

[airbus]

Hi Uwe, thanks for your reply.

I'm not aware of any way to de-sensitize the cruise.

I don't know what's causing the power fluctuations, but I think a +/- 1km/hr wheel speed variation is to be expected since 1 km/hr is the resolution of the data.

OK, this is the only thing outstanding thing that I was working on, unless you can see anything that I am missing in terms of data anomalies.

What I would suggest logging is the vehicle speed as the ECU sees perceives it, and the amount of power it's applying. The former should be straightforward enough, the latter is a bit more of a challenge since I really don't know what ECU this engine has.

OK, I have logged various parameters in advanced measuring blocks from the ECU that uses the UDS Protocol on my car. These include EGR/Boost/RPM and vehicle speed the ECU is registering. The exert uploaded is when the car was on the motorway with the cruise control on set at 50mph. The CSV File is located HERE.

I would urge you to post up an Auto-Scan so we can see what this car is made of.

Please find attached a full autoscan of my car below. If it would be of benefit for me to upload anything else to help diagnose this cruise pulsing, then please do let me know. As it currently stands, the cruise is essentially non practical below around 60mph as it creates more bother than just pressing the accelerator pedal and watching that speed

Thank you for your help and expertise.

VCDS -- Windows Based VAG/VAS Emulator
VCDS Version: 12.12.2.0
Data version: 20140212


VIN: WVWZZZ1KZBWxxxxxx License Plate: 



--------------------------------------------------------------------------------
--------------------------------------------------------------------------------


Chassis Type: 1K (7N0)
Scan: 01 03 08 09 10 15 16 17 19 25 2E 42 44 46 52 56 61 62 72 77
         

VIN: WVWZZZ1KZBWxxxxxx 

01-Engine -- Status: OK 0000
03-ABS Brakes -- Status: OK 0000
04-Steering Angle -- Status: OK 0000
08-Auto HVAC -- Status: OK 0000
09-Cent. Elect. -- Status: OK 0000
10-Park/Steer Assist -- Status: OK 0000
15-Airbags -- Status: OK 0000
16-Steering wheel -- Status: OK 0000
17-Instruments -- Status: OK 0000
19-CAN Gateway -- Status: OK 0000
25-Immobilizer -- Status: OK 0000
2E-Media Player 3 -- Status: OK 0000
42-Door Elect, Driver -- Status: OK 0000
44-Steering Assist -- Status: OK 0000
46-Central Conv. -- Status: OK 0000
52-Door Elect, Pass. -- Status: OK 0000
56-Radio -- Status: OK 0000
61-Battery Regul. -- Status: OK 0000
62-Door, Rear Left -- Status: OK 0000
72-Door, Rear Right -- Status: OK 0000
77-Telephone -- Status: OK 0000
 
-------------------------------------------------------------------------------
Address 01: Engine (J623-CAYC)       Labels: 03L-906-023-CAY.clb
   Part No SW: 03L 906 023 DQ    HW: 03L 906 023 A
   Component: 1,6l R4 CR td H23 9638  
   Revision: --H23---    Serial number: 00000000000000
   Coding: 00114034032501080000
   Shop #: WSC 01357 011 00200
   ASAM Dataset: EV_ECM16TDI02103L906023DQ 003011
   ROD: EV_ECM16TDI02103L906023DQ.rod
   VCID: 78D9DB3DC3D22BDEA37-802D

No fault code found.
Readiness: 0000 0000

-------------------------------------------------------------------------------
Address 03: ABS Brakes (J104)       Labels: 1K0-907-379-60EC1F.clb
   Part No SW: 1K0 907 379 AT    HW: 1K0 907 379 AT
   Component: ESP MK60EC1   H30 0105  
   Revision: 00H30001    
   Coding: 133B200D09230002C81004EA90200091310000
   Shop #: WSC 01357 011 00200
   VCID: 84213FCD071AFF3E3FF-80D1

No fault code found.

-------------------------------------------------------------------------------
Address 08: Auto HVAC (J301)       Labels: 3C8-907-336.clb
   Part No SW: 3C8 907 336 AB    HW: 3C8 907 336 AB
   Component: Climatic      H14 0305  
   Revision: 00009001    
   Coding: 0000000003
   Shop #: WSC 01357 011 00200
   ASAM Dataset: EV_Climatic A01005
   ROD: EV_ClimaBasis_SE36.rod
   VCID: 6DF7FA69BC909E76401-8038

No fault code found.

-------------------------------------------------------------------------------
Address 09: Cent. Elect. (J519)       Labels: 1K0-937-08x-09.clb
   Part No SW: 1K0 937 084 D    HW: 1K0 937 084 D
   Component: BCM PQ35  B   103 0615  
   Revision: 00103 AD    
   Coding: 48180A3A8823F1C040080080340000E443510088436D8160648087200041
   Shop #: WSC 01357 011 00200
   VCID: 2F4B20617E1C2C6632D-807A

   Subsystem 1 - Part No: 1K2 955 119 F  Labels: 1KX-955-119.CLB
   Component: Wischer 27051  21  0512 
   Coding: 009F95

   Subsystem 2 - Part No: 1K0 955 559 AH  Labels: 1K0-955-559-AG.CLB
   Component: RLS 040610 05  54  0403 
   Coding: 0330AD

   Subsystem 3 - Part No: 1K8 951 171 
   Component: DWA-Sensor 00  001 0104 

   Subsystem 4 - Part No: 1K8 951 605 A
   Component: LIN BACKUP HO  H11 9004 

No fault code found.

-------------------------------------------------------------------------------
Address 10: Park/Steer Assist (J446)       Labels: 3C8-919-475.clb
   Part No SW: 5K0 919 475 C    HW: 5K0 919 475 
   Component: PARKHILFE 8K  H07 0008  
   Revision: --------    Serial number: 12991009638098
   Coding: 100001
   Shop #: WSC 01357 011 00200
   VCID: 3645150581461DAE71B-8063

No fault code found.

-------------------------------------------------------------------------------
Address 15: Airbags (J234)       Labels: 5K0-959-655.clb
   Part No SW: 5K0 959 655 D    HW: 5K0 959 655 D
   Component: AirbagVW10    037 0606  
   Serial number: 003FKRA8NJXT  
   Coding: 00003133
   Shop #: WSC 01357 011 00200
   ASAM Dataset: EV_AirbaVW10SMEVW360 A01011
   ROD: EV_AirbaVW10SMEVW360.rod
   VCID: 3B530431B264C0C68E5-806E

   Crash sensor for side airbag; driver side: 
   Subsystem 1 - Part No SW: 5K0 959 354     HW: 5K0 959 354 
   Component: S.Sens.Fahr.V  H01 ---- 
   Serial number: 3572MSME32216253ZZZH

   Crash sensor for side airbag; passenger side: 
   Subsystem 2 - Part No SW: 5K0 959 354     HW: 5K0 959 354 
   Component: S.Sens.Beif.V  H01 ---- 
   Serial number: 3582MSME49596553ZZZ/

   Crash sensor for side airbag; rear driver side: 
   Component: S.Sens.Fahr.H  --- ---- 
   Serial number: 3512QSME3C306029ZZZQ

   Crash sensor for side airbag; rear passenger side: 
   Component: S.Sens.Beif.H  --- ---- 
   Serial number: 3522QSME3635614EZZZY

No fault code found.

-------------------------------------------------------------------------------
Address 16: Steering wheel (J527)       Labels: 5K0-953-569.clb
   Part No SW: 5K0 953 507 BC    HW: 5K0 953 549 E
   Component: Lenks.Modul   007 0080  
   Revision: --------    Serial number:  90440JF4000XU
   Coding: 1082140000
   Shop #: WSC 01357 011 00200
   ASAM Dataset: EV_SMLSNGKUDS A05001
   ROD: EV_SMLSNGKUDS_SE36.rod
   VCID: 72CDE915A5AE418E9D3-8027

   Multi Function Steering Wheel Control Module: 
   Subsystem 1 - Part No SW: 3C8 959 537 D    HW: 3C8 959 537 D
   Component: E221__MFL-TK6  H06 0022 
   Serial number: 70000000000000012586
   Coding: E20000

No fault code found.

-------------------------------------------------------------------------------
Address 17: Instruments (J285)       Labels: 5K0-920-xxx-17.clb
   Part No SW: 5K0 920 971 A    HW: 5K0 920 971 A
   Component: KOMBI         H03 0406  
   Serial number: 00000000000000
   Coding: 170B00
   Shop #: WSC 01357 011 00200
   ASAM Dataset: EV_Kombi_UDS_VDD_RM09 A04089
   ROD: EV_Kombi_UDS_VDD_RM09_VW21.rod
   VCID: 2D773A697C105E76001-8078

No fault code found.

-------------------------------------------------------------------------------
Address 19: CAN Gateway        Labels: 7N0-907-530-V1.clb
   Part No SW: 7N0 907 530 A    HW: 1K0 907 951 
   Component: J533  Gateway   H25 0602  
   Revision:   H25       Serial number: 290510F2000109
   Coding: E9A07F0600061204000003
   Shop #: WSC 01357 011 00200
   VCID: 2E753D65B916256E39B-807B

No fault code found.

-------------------------------------------------------------------------------
Address 25: Immobilizer (J334)       Labels: 5K0-920-xxx-25.clb
   Part No SW: 5K0 953 234     HW: 5K0 953 234 
   Component: IMMO          H03 0406  
   Serial number: 00000000000000
   Coding: 000000
   Shop #: WSC 00000 000 00000
   ASAM Dataset: EV_Immo_UDS_VDD_RM09 A03008
   ROD: EV_Immo_UDS_VDD_RM09_SE36.rod
   VCID: EAFD71750D7E094EA53-80BF

No fault code found.

-------------------------------------------------------------------------------
Address 2E: Media Player 3 (J650)       Labels: 5N0-035-342.lbl
   Part No SW: 5N0 035 342 C    HW: 5N0 035 342 C
   Component: SG EXT.PLAYER H13 0111  
   Revision: A1001003    Serial number: 7668119412    
   Coding: 010000
   Shop #: WSC 01357 011 00200
   VCID: 277BC84156EC7426FAD-8072

No fault code found.

-------------------------------------------------------------------------------
Address 42: Door Elect, Driver        Labels: 1K0-959-701-MIN3.lbl
   Part No SW: 5K0 959 701 B    HW: 5K0 959 701 B
   Component: Tuer-SG         009 2114  
   Coding: 0131764
   Shop #: WSC 01357 011 00200
   VCID: 314F2619A8283A96249-8064

No fault code found.

-------------------------------------------------------------------------------
Address 44: Steering Assist        Labels: 1Kx-909-14x-44.clb
   Part No: 1K0 909 144 J
   Component: EPS_ZFLS Kl. 69     3001  
   Revision: 00H17000    
   Shop #: WSC 01357 011 00200
   VCID: 314F2619A8283A96249-8064

No fault code found.

-------------------------------------------------------------------------------
Address 52: Door Elect, Pass.        Labels: 1K0-959-702-MAX3.lbl
   Part No SW: 5K0 959 702 C    HW: 5K0 959 702 C
   Component: Tuer-SG         009 2114  
   Coding: 0132020
   Shop #: WSC 01357 011 00200
   VCID: 33432C1152340886565-8066

No fault code found.

-------------------------------------------------------------------------------
Address 56: Radio (J0503)       Labels: 5M0-035-1xx-56.clb
   Part No SW: 3C8 035 195 A    HW: 3C8 035 195 A
   Component: Radio RCD510  040 0166  
   Revision: 00000001    Serial number: VWZ1Z3K6478048
   Coding: 0100040004
   Shop #: WSC 01357 011 00200
   VCID: 2665C54551E66D2EC1B-8073

No fault code found.

-------------------------------------------------------------------------------
Address 61: Battery Regul. (J840)       Labels: 1K0-907-534.clb
   Part No SW: 7N0 907 534     HW: 1K0 907 951 
   Component: Batt.regelung H25 0602  
   Serial number: 290510F2000109
   Coding: 030B185A
   Shop #: WSC 01357 011 00200
   VCID: F1CF661928A8FA96E49-80A4

   Subsystem 1 - Part No SW: 1K0 915 181 C    HW: 1K0 915 181 A
   Component: J367-BDM  H07 0125 

No fault code found.

-------------------------------------------------------------------------------
Address 62: Door, Rear Left        Labels: 1K0-959-703-GEN3.lbl
   Part No SW: 5K0 959 703 C    HW: 5K0 959 703 C
   Component: Tuer-SG         007 2101  
   Coding: 0131216
   Shop #: WSC 01357 011 1012552
   VCID: 34412F0D573A0FBE4FF-8061

No fault code found.

-------------------------------------------------------------------------------
Address 72: Door, Rear Right        Labels: 1K0-959-704-GEN3.lbl
   Part No SW: 5K0 959 704 C    HW: 5K0 959 704 C
   Component: Tuer-SG         007 2101  
   Coding: 0131216
   Shop #: WSC 01357 011 1012552
   VCID: 354712095C4016B6781-8060

No fault code found.

-------------------------------------------------------------------------------
Address 77: Telephone (J412)       Labels: 7P6-035-730.clb
   Part No SW: 7P6 035 730 B    HW: 7P6 035 730 B
   Component: TELEFON       H05 0440  
   Revision: 1B001001    Serial number: 00007668036283
   Coding: 0A01000000010101
   Shop #: WSC 01357 011 00200
   ASAM Dataset: UHVNA A01007
   ROD: UHVNA.rod
   VCID: 314F261960283A96249-8064

No fault code found.

End   ---------------------------------------------------------------------

 

[jyoung8607]

Does this always happen under every load condition? In other words, is it consistent during uphill, downhill and level travel, or no? Some cars can have a very perceptible transition from under-load to overrun (engine braking). If it happens when you're driving uphill, you can probably rule out load-to-overrun transition slop since you would still be under load the whole time.

Are your front tires identical in model, tread-wear and inflation? A difference here could account for your speed readings. Severe differences have even been known to produce false ABS and traction control engagements on some cars.

Is your ECU chipped/remapped?

Jason

 

[Uwe]

The CSV File is located HERE.

This link doesn't work for me. I'm going to suggest that the best way to share log files is to make 'em a Google Spreadsheet; they are after all intended to be looked at and analyzed in a spreadsheet application.

-Uwe-

 

[airbus]

This link doesn't work for me. I'm going to suggest that the best way to share log files is to make 'em a Google Spreadsheet; they are after all intended to be looked at and analyzed in a spreadsheet application.

-Uwe-

Hi, I need to work out the Google Spreadsheet sharing thing. In the meantime, can you check this link to the CSV file please..http://jmp.sh/DnRCz48

 

[airbus]

Hi Jason, thanks for replying.

Does this always happen under every load condition? In other words, is it consistent during uphill, downhill and level travel, or no? Some cars can have a very perceptible transition from under-load to overrun (engine braking). If it happens when you're driving uphill, you can probably rule out load-to-overrun transition slop since you would still be under load the whole time.

I do get the symptoms out on the level, uphill, and downhill. Essentially all phases of driving, I would say to different degrees though. It does appear more prevalent when going downhill even at a very slight gradient. Going uphill less so, on level I do still feel it but about in the middle of the other two.

Are your front tires identical in model, tread-wear and inflation? A difference here could account for your speed readings. Severe differences have even been known to produce false ABS and traction control engagements on some cars.

Tyres are identical all round with 32psi.

Is your ECU chipped/remapped?

No, pure stock everything.

Things I did today:
I did remove the two front abs sensors today, there was a little grime and rust sitting on them so I cleaned all this and put them back. It had no effect on the oscillations so as Uwe said I guess this to be normal. So now I am wondering if I should do the same to the rear sensors....Perhaps not, since they have much less speed variations between the 2.
I then tried to pinpoint where the ecu is getting it's speed input from. A couple of sources suggested the front left speed sensor so I disconnected it and went for a drive, the result was just an abs error...speed was working and so was cruise (although still pulsing).

So unfortunately I am non the wiser as to what the cause may be. I have rarely had the cruise control set below 60 in the past but with the extensive roadworks in my area recently (with average speed cameras), I have come to notice the symptoms a lot more when the cruise is engaged. Perhaps the cruise is not meant to be useful below 1800rpm or so on my particular engine (1.6TDI, engine CAYC) or my 5 speed gearbox with high gearing (bluemotion fuel efficiency model). The cruise seems far more comfortable at higher revs (2000+rpm). I am not so sure though as I'dd expect it to work properly at above 1500rpm, or just not work at all like it doesn't below around 20mph...

I appreciate the input, I have lots of logs but just can't see any real anomalies, perhaps I am calling up the wrong data here. Any advice for anything else I am missing or not checking would be appreciated. Thanks!

 

[Uwe]

Hi, I need to work out the Google Spreadsheet sharing thing. In the meantime, can you check this link to the CSV file please..http://jmp.sh/DnRCz48

That works well. However, I don't see anything obvious in that data that screams "there's the source of the problem!" to me.

-Uwe-

 

[jyoung8607]

... Essentially all phases of driving, I would say to different degrees though. It does appear more prevalent when going downhill even at a very slight gradient. Going uphill less so, on level I do still feel it but about in the middle of the other two.

... Perhaps the cruise is not meant to be useful below 1800rpm or so on my particular engine (1.6TDI, engine CAYC) or my 5 speed gearbox with high gearing (bluemotion fuel efficiency model). The cruise seems far more comfortable at higher revs (2000+rpm). I am not so sure though as I'dd expect it to work properly at above 1500rpm, or just not work at all like it doesn't below around 20mph...

I don't think you have a speed-measurement problem. I think you have a mild engine problem in a certain RPM/load range. The ECU cruise algorithm calls for a certain amount of torque/fuel to keep you going at your current speed based on built-in maps, and it doesn't quite happen. When your speed starts to fall, the the ECU has to step on it harder. Once you're back up to speed, the cycle repeats.

If you cruise in 4th instead of 5th gear, does the problem go away?

Jason

 

[airbus]

That works well. However, I don't see anything obvious in that data that screams "there's the source of the problem!" to me.

-Uwe-

OK, thanks for casting your eye over it Uwe, much appreciated!

 

[airbus]

I don't think you have a speed-measurement problem. I think you have a mild engine problem in a certain RPM/load range. The ECU cruise algorithm calls for a certain amount of torque/fuel to keep you going at your current speed based on built-in maps, and it doesn't quite happen. When your speed starts to fall, the the ECU has to step on it harder. Once you're back up to speed, the cycle repeats.

If you cruise in 4th instead of 5th gear, does the problem go away?

Jason

It becomes much less noticeable if I am maintaining the same speed in 4th gear under cruise control, as opposed to 5th. Generally higher rpms lead to a more satisfying cruise control experience. The problem virtually goes away past 2000rpm so I think what you're saying is making tremendous sense. I wonder if I can change anything in VCDS that may help to solve the issue somewhat, or perhaps there is a software update available for my car that 'might' address the issue... Or even a way to reset the engine so it can start learning again, maybe this is not possible though if it's a mechanical problem.

If anyone has access as to whether an update is available as a last course of action, that would be great.....Only issue is that I am way out of manufacturers warranty but at least the dealer can't charge me over the odds if I know what I am asking for :-)

One thing though, which sensor does the speed signal work off for the speedo, I thought it was the front left, it's not as I disconnected it and it carried on working.

Irrespective on where the speed sensor input is for speedo and cruise, at this stage I am going to discount the speed readings as a wild goose chase and concentrate on engine stuff, what stuff I am not sure of but perhaps I might get to the source as I learn more from you guys...

Thanks again for the replies both of you, some good information provided, this has certainly broadened my mindset in to what may be causing the issue.

 

[Uwe]

One thing though, which sensor does the speed signal work off for the speedo, I thought it was the front left, it's not as I disconnected it and it carried on working.

On newer cars, there's no longer a single speed sensor like there was in the past (typically on the output side of the transmission). What I believe happens now is that the ABS produces calculates vehicle speed from a composite of all four wheel speeds and puts that on the powertain CAN bus for the instrument cluster and ECU to use as they see fit. My guess is you can disconnect any of the four wheel speed sensors (and possibly any 3 of them) and still get a vehicle speed.

-Uwe-

 

[airbus]

On newer cars, there's no longer a single speed sensor like there was in the past (typically on the output side of the transmission)....

I had a hunch that this may be the case but couldn't find it documented anywhere. Thanks for passing your knowledge on for this.

Now if only I could figure out how to fix this cruise issue, like Jason said it may be a software map issue... Do any of you guys have access to whether updates are available for a particular engine and even what they fix? I guess no to the latter but still worth a go if there is an update available I guess....

I love finding out how things work, and more importantly get great satisfaction out of fixing my cars too without paying someone else for the privilege. That's why I bought VCDS, a great piece of kit you devised which has saved me a lot of money over the years.

Thanks.

 

[jyoung8607]

It becomes much less noticeable if I am maintaining the same speed in 4th gear under cruise control, as opposed to 5th. Generally higher rpms lead to a more satisfying cruise control experience. The problem virtually goes away past 2000rpm so I think what you're saying is making tremendous sense. I wonder if I can change anything in VCDS that may help to solve the issue somewhat, or perhaps there is a software update available for my car that 'might' address the issue... Or even a way to reset the engine so it can start learning again, maybe this is not possible though if it's a mechanical problem.

To be clear, I was proposing a mechanical problem rather than a software problem. I think at low RPM the engine isn't delivering the amount of power the ECU is commanding and expecting.

Logically speaking, I feel strongly it's an engine problem. However, I'm not a diesel expert so I would need to step aside and let someone else suggest things to check from here. Could be clogged injectors, a fuel quality problem, problem with the turbo spooling up, etc.

Jason

 

[airbus]

Logically speaking, I feel strongly it's an engine problem. However, I'm not a diesel expert so I would need to step aside and let someone else suggest things to check from here. Could be clogged injectors, a fuel quality problem, problem with the turbo spooling up, etc.

Ah OK. I guess if there were any significant problems they would also exhibit themselves under non cruise control activities, ie under hard acceleration or general motoring throughout all engine rpm ranges. Also there is hardly any injection deviation measured on all 4 cylinders so I guess injectors are ruled out.

Thanks for your input, some good ideas, I just wish some issues would throw out fault codes, would make the whole fixing process easier :-)

 

[Dana]

Hi Adam,

I don't know that engine but the part number (03L 906 023 DQ) resulted in a Workshop campaign 23F7 TPI (Recall, which would need to be checked by VIN at your local dealer) in addition to a whopping list of RoW specific TPIs for a huge list of issues. I cannot copy ALL of the text but I can summarize the newest TPI:

Loud noises (pinking) when accelerating lightly between 1800 to 2000 rpm from engine/front of vehicle.​

The engine judders when driving at constant speed.​

The engine judders at idle speed.​

The engine misfires at idle speed.​

The engine starts cold with a delay.​

TPI # 2021663/10 (/10 means the 10th revision!) is from March 2013 .. so I wonder if it was revised a few more times already?

Based on the scan this engine controller may be up to date..

Address 01: Engine (J623-CAYC) Labels: 03L-906-023-CAY.clb
Part No SW: 03L 906 023 DQ HW: 03L 906 023 A
Component: 1,6l R4 CR td H23 9638

03L-906-023-DQ @ SWL 9638 or higher but I wonder if they (VW) had all of the bugs worked out the last time it was flashed? If that TPI hasn't been updated recently the only way the dealer can confirm is by hooking up and entering SVM code 32EA to see if newer software is available. Keep us posted if you have any luck with newer software but as Jason mentioned this may be a mechanical issue that CCS is amplifying.

-Dana

 

[jyoung8607]

... I don't know that engine but the part number (03L 906 023 DQ) resulted in a Workshop campaign 23F7 TPI (Recall, which would need to be checked by VIN at your local dealer) in addition to a whopping list of RoW specific TPIs for a huge list of issues. I cannot copy ALL of the text but I can summarize the newest TPI:

Loud noises (pinking) when accelerating lightly between 1800 to 2000 rpm from engine/front of vehicle.​

The engine judders when driving at constant speed.​

The engine judders at idle speed.​

The engine misfires at idle speed.​

The engine starts cold with a delay.​

JFC. I knew shipping alpha/beta quality product was becoming the unfortunate norm in the software industry these days, but apparently that's now extended to ECUs. Can't start, can't idle, can't accelerate, and can't cruise. Apparently slowing down works though.

Am I permitted to retroactively revise my diagnosis to the holistic whole-engine package, including electronics? Trying to keep my score up.

Jason

 

[Uwe]

JFC. I knew shipping alpha/beta quality product was becoming the unfortunate norm in the software industry these days

I hate to sound like I'm making excuses but it's at least partly due to the greatly increased level of complexity in the products these days.

The thing is, some people are at least honest enough to tell their customers, "Hey, this is a Beta and may not work quite perfectly just yet!"

 

[airbus]

Hi Dana,

I don't know that engine but the part number (03L 906 023 DQ) resulted in a Workshop campaign 23F7 TPI (Recall, which would need to be checked by VIN at your local dealer) in addition to a whopping list of RoW specific TPIs for a huge list of issues. I cannot copy ALL of the text but I can summarize the newest TPI:

Loud noises (pinking) when accelerating lightly between 1800 to 2000 rpm from engine/front of vehicle.​

The engine judders when driving at constant speed.​

The engine judders at idle speed.​

The engine misfires at idle speed.​

The engine starts cold with a delay.​

TPI # 2021663/10 (/10 means the 10th revision!) is from March 2013 .. so I wonder if it was revised a few more times already?

Based on the scan this engine controller may be up to date..

Thanks for this. So the engine has proven to be reliable then since it's inception My engine does sometimes take a few cranks to start when it's cold, never thought much about it though until now !

03L-906-023-DQ @ SWL 9638 or higher but I wonder if they (VW) had all of the bugs worked out the last time it was flashed? If that TPI hasn't been updated recently the only way the dealer can confirm is by hooking up and entering SVM code 32EA to see if newer software is available. Keep us posted if you have any luck with newer software but as Jason mentioned this may be a mechanical issue that CCS is amplifying.

I will certainly ask the dealer if they are aware of a newer software using the details you provided, and provide this thread with an update in due course. This has to be worth trying considering how many software updates have happened to the engine controller, doesn't really instil me with too much confidence in it's bug free integrity

Thanks for the reply Dana. This will take me somewhere else now but this is definitely worth a shot!

 

[airbus]

JFC. I knew shipping alpha/beta quality product was becoming the unfortunate norm in the software industry these days, but apparently that's now extended to ECUs. Can't start, can't idle, can't accelerate, and can't cruise. Apparently slowing down works though.

Am I permitted to retroactively revise my diagnosis to the holistic whole-engine package, including electronics? Trying to keep my score up.

Jason

Your inputs have proved very helpful Jason, before I started this thread I had enquired on other forums and all I was getting back was the speed input. The information in this thread has certainly broadened my mind in what the cause of my symptoms may be. Perhaps this is the price we pay for a complex product that's released to cope with the ever increasing governmental costs (at least here in the UK) that are levied on pollution causing vehicles. Hence the reason the 1.6TDI is proving more popular, perhaps at the expense of greater failures or 'bugs' as the product is refined... Thanks.