|
|
Post by ycodryn on Aug 21, 2018 7:59:16 GMT
Strange that I don’t have the skoda/vw/seat or audi selection. There I have only bit 0, bit 1, bit 2 etc. and I read that I have to deselect bit 0 and select bit 1 to have in hex value of 2. But I’m getting that error 😞
Anyway, thank you for reply guys and if is only a minor improvement then I leave it default.
|
|
|
|
Post by snowj720 on Aug 22, 2018 21:52:26 GMT
 Tired it on my Canadian MK7.......minor improvement.....lost the cruise control. Did you find a fix? Reading your post had me curious and sure as shite mine is gone too. I don't know if we can keep the mod and reactivate or if we had to go back to the value as VW. |
|
|
|
Post by snowj720 on Aug 23, 2018 18:49:29 GMT
Reverting to old VW value did not fix CC issue. Anyone know how to fix it?
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 23, 2018 18:54:45 GMT
What does a scan say about the error ?
|
|
|
|
Post by robgti on Aug 23, 2018 18:55:13 GMT
Reverting to old VW value did not fix CC issue. Anyone know how to fix it? Having the same issue.... Don to the rescue ? |
|
|
|
Post by snowj720 on Aug 23, 2018 23:23:05 GMT
Reverting to old VW value did not fix CC issue. Anyone know how to fix it? Having the same issue.... Don to the rescue ? Can't recall the code exactly, but when googling it it says it's related to a short in the CC switch. Recommendation is replace the switch. Vehicle has 8500k on it. |
|
|
|
Post by knightwolf on Sept 6, 2018 4:28:12 GMT
I'd like to give this a shot, but don't want to loose cruise. Anyone able to confirm if cruise actually fails once this is enabled or if it's a switch fault?
|
|
|
|
Post by robgti on Sept 6, 2018 13:25:54 GMT
I'd like to give this a shot, but don't want to loose cruise. Anyone able to confirm if cruise actually fails once this is enabled or if it's a switch fault? Have not been able to confirm if it is a faulty switch or not. All I know is CC has malfunctioned ever since throttle mod. Anyone know how to confirm switch malfunction? Rob |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Sept 10, 2018 10:36:40 GMT
I've been following this thread for a while now and I must agree, I didn't feel much of a difference until I had my tracking done which required steering angle sensor reset. Cleared TPMS/ACC errors and throttle pedal felt much firmer. A huge difference.
Not entirely sure if the above is BS or just in my head but feels great for me.
What fault codes do you fellas get ?
|
|
|
|
Post by snowj720 on Sept 20, 2018 18:52:05 GMT
What fault codes do you fellas get ?
11463 was the fault I got. Still no CC. 😒
|
|
|
|
Post by sutadarkside on Sept 29, 2018 18:24:56 GMT
Having the same issue, tried the throttle response app, then tried the long coding listed here. After that I'm getting the cruise control with an exclamation mark light on the dash. Here is the results of the scan. The only error codes were in engine and brakes. Well also the "no XM radio" but that doesn't matter.
01 Engine
System description: 2.0l R4 TFSI
Software number: 5G0906259D
Software version: 0002
Hardware number: 06K907425B
Hardware version: H13
ODX name: EV_ECM20TFS0205G0906259D
ODX version: 001003
Long coding: 0A1900122424002F0000
Trouble codes:
U112300 - Databus error value received
static
---------------------------------------------------------------
03 Brakes
System description: ESC
Software number: 3Q0907379T
Software version: 0393
Hardware number: 3Q0907379C
Hardware version: H32
Serial number: 53145000000774
ODX name: EV_Brake1UDSContiMK100ESP
ODX version: 034033
Long coding: 01FA6BA13424096C0078020581CA2980D62C9000408194B400430050C009
Trouble codes:
P164700 - Checking coding/versions of control modules in drivetrain
static
-----------------------------------------
|
|
|
|
Post by robgti on Oct 2, 2018 20:50:07 GMT
Having the same issue, tried the throttle response app, then tried the long coding listed here. After that I'm getting the cruise control with an exclamation mark light on the dash. Here is the results of the scan. The only error codes were in engine and brakes. Well also the "no XM radio" but that doesn't matter. 01 Engine System description: 2.0l R4 TFSI Software number: 5G0906259D Software version: 0002 Hardware number: 06K907425B Hardware version: H13 ODX name: EV_ECM20TFS0205G0906259D ODX version: 001003 Long coding: 0A1900122424002F0000 Trouble codes: U112300 - Databus error value received static --------------------------------------------------------------- 03 Brakes System description: ESC Software number: 3Q0907379T Software version: 0393 Hardware number: 3Q0907379C Hardware version: H32 Serial number: 53145000000774 ODX name: EV_Brake1UDSContiMK100ESP ODX version: 034033 Long coding: 01FA6BA13424096C0078020581CA2980D62C9000408194B400430050C009 Trouble codes: P164700 - Checking coding/versions of control modules in drivetrain static ----------------------------------------- I am pulling the same codes...I’m trying to revert to initial settings but didn’t backup the log... Anyone able to revert changes surrounding the pedal mod and regain functionality of the Cruise Control? |
|
|
|
Post by snowj720 on Dec 20, 2018 18:22:23 GMT
Anyone ever figure out how to get CC back? My dealer worked on it and couldn't figure it out.
|
|
|
|
Post by mkviken on Feb 10, 2019 3:27:43 GMT
i just ordered an OBDeleven for my mk7.5 golf gti - would like to try this change but worried about these errors with cruise control etc
anyone know if this works ok on th 7.5 or if a fix for the above issues has been found?
Thanks
|
|
|
|
Post by snowj720 on Feb 26, 2019 23:38:22 GMT
i just ordered an OBDeleven for my mk7.5 golf gti - would like to try this change but worried about these errors with cruise control etc anyone know if this works ok on th 7.5 or if a fix for the above issues has been found? Thanks So far no one has a fix for the cc issue. Avoid doing it. I miss my cc. Dealer couldn't even fix it. |
|
|
|
Post by liam256 on Mar 27, 2019 13:40:51 GMT
I tried this mod on my UK 2017 (Pre-FL) MK7 R, only the steering setting, but not the engine setting, as I wasn't aware of it at the time.
When I used my ACC it went wide open throttle and then threw an error, as per previous posters screenshots. Power cycling the car cleared the error, but as I was concerned about losing ACC permanently, so I switched it back to the default setting, upon switching it back the ACC threw an error once more, but power cycling the car & clearing error codes cleared this again.
This got me thinking that perhaps the ACC also needs to know about the throttle change, so had a look in the long coding of the ACC module and there is another setting for logic, with values 'Skoda/VW' and 'Audi'.
I've not been brave enough to try this again, as I cannot be without ACC, but perhaps all 3 settings need to be amended?
|
|
|
|
Post by newty on Mar 27, 2019 14:32:11 GMT
Generally: Throttle response never had a plausible effect on the cars throttle, but has various side effects, depending on other controllers. We had discussed this in Germany some weeks ago and came to the conclusion that this does not work at all.
ACC is known to work "better safe than sorry" and will drop out as soon as anything unpredicted happens on the bus.
The brand logic in ACC with greatly change the overall communication of the ACC and shall not work in an MQB environment. Stil its funny to have the "Brake!" warning while having the engine off in the parking lot.
|
|
|
|
Post by rickyk138 on Sept 3, 2019 4:35:20 GMT
Sorry for Reviving an old thread, but I did this Audi pedal mod and have the same cruise control! Error.
I was able to resolve the issue though. What I did was clear the code in the engine control module and then changed brand back to VW. After doing so I then went to the brake module and cleared the code there also, then cycle the ignition and the cruise control ! went away and it now functions as normal
|
|
|
|
Post by robgti on Sept 19, 2019 10:06:44 GMT
Sorry for Reviving an old thread, but I did this Audi pedal mod and have the same cruise control! Error. I was able to resolve the issue though. What I did was clear the code in the engine control module and then changed brand back to VW. After doing so I then went to the brake module and cleared the code there also, then cycle the ignition and the cruise control ! went away and it now functions as normal Glad you revived— This worked for me, was able to regain my CC! Finally, it’s been over a year! Thanks |
|
|
|
Post by kubkoski on Mar 31, 2021 19:47:15 GMT
Sorry for Reviving an old thread, but I did this Audi pedal mod and have the same cruise control! Error. I was able to resolve the issue though. What I did was clear the code in the engine control module and then changed brand back to VW. After doing so I then went to the brake module and cleared the code there also, then cycle the ignition and the cruise control ! went away and it now functions as normal Hello can you explaine please how to clear teh code ? Regards |
|
|
|
Post by dv52 (Australia) on Mar 31, 2021 23:33:29 GMT
kubkoski : This tweak has always been problematic - in my experience, it seldom (if ever) results in better pedal response and more often it does nothing but cause the type of errors listed in the posts above. The fix for those that have been fool-hardy to implement the tweak is to revert the changed value back to factory settings. This is done by changing long-code in the Engine module (@ address hex01).
Go to the Engine module - select coding - then navigate to Byte 0 - with the tweak implemented, the value of Byte 0 should be hex02, or binary 0000 0010. Remembering that binary numbers are read from right-to-left (so, Bit 0 is the right-most digit), this means that Bit 1 is set. You need to revert Byte 0 to factory setting, which means Byte 0= hex01=Binary 0000 0001
So on Byte 0, remove tick from Bit 1 and tick Bit 0 - this should result in hex01. After you make this change ONLY Bit 0 should be ticked (all the other Bits should be un-ticked)
The other alternative is to go to the descriptive option in coding and look for the term "audi" - change this to "VW"
After this change is made, clear the errors in the modules
Don
|
|
|
|
Post by PDXore503 on Sept 6, 2021 23:59:59 GMT
Am curious to try this on my '17 Alltrack SE. But seems to be a lot of potential issues with this mod. Found this video walkthrough of a Golf R showing you must do the following. Though they don't state which year & so different models might be affected differently. 1st - Linear Throttle coding in the steering module then 2nd - Engine code to Audi (Byte 00 hex02) then 3rd - Adaptive cruise to Audi (brand-logic)   |
|
burtz
New Member
Posts: 8
|
Post by burtz on Sept 7, 2021 9:16:02 GMT
1st - Linear Throttle coding in the steering module then 2nd - Engine code to Audi (Byte 00 hex02) then 3rd - Adaptive cruise to Audi (brand-logic) I tried these three codings on a 7.5 UK-spec GTI (late 2018), they worked fine - if I remember correctly they did flash up warning lights in the dash, but they went away after cycling the ignition/re-starting the car. But as Don has said there was no actual difference to the throttle response at all & the only discernible difference was that the cruise control adjustment became, IMO, terrible- totally lost the ability to quickly jump up & down in 5mph increments which I much prefer & so could only increase or decrease 1 mph at a time. So after a few days of experimenting & confirming that there was no change to the pedal feel/response or acceleration I returned to original coding & have left it there ever since. |
|
|
|
Post by PDXore503 on Sept 7, 2021 20:14:42 GMT
I set throttle response to Linear and Engine code to Audi. Used the actual menu options in Longcoding vs changing the byte/bits.
It certainly woke the engine response up more, a noticeable change. I have the Neuspeed Power Module in the car too, so with that combo it is nice… poor mans tune. Even in normal drive mode I can feel/hear the difference, not just in sport.
I did not have any issues or errors with my ACC with those two changes as some people report, but did try setting ACC to Audi in the Brand Logic and that DID deactivate it and give errors. An unexpected outcome as you’d think the computer would want both settings to match Audi-for-Audi. Setting back to VW fixed it.
happy with the results.
|
|
