ACC Retrofit Advice Please for Golf MK7

[guile]

-------------------------------------------------------------------------------
Address 14: Susp. Elect. (J250) Labels: 5Q0-907-376.clb
Part No SW: 5Q0 907 376 HW: 5Q0 907 376
Component: DAEMPFUNGS-SG H16 0115
Serial number: 19011541350032
ASAM Dataset: EV_DRCONTITEMIC 001019
ROD: EV_DRCONTITEMIC_VW37.rod
VCID: 76E3E2FBC91413396B-8022

No fault code found.

-------------------------------------------------------------------------------
Address 15: Airbags (J234) Labels:| 5Q0-959-655.clb
Part No SW: 5Q0 959 655 D HW: 5Q0 959 655 D
Component: AirbagVW20 014 0385
Serial number: 003F6R0G6FAC
Coding: 98CCC000000000005C00000000C800000065
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_AirbaVW20SMEVW37X 002130
ROD: EV_AirbaVW20SMEVW37X_VW37.rod
VCID: 41894127D05AE4810E-8014

Crash sensor for side airbag: driver side:
Subsystem 1 - Part No SW: ----------- HW: 480 001 102 15
Component: SideSensor_Df 001 0887
Serial number: 3576700000060274E21L
Coding: 2D2D2D

Front Passenger's Side Airbag Crash Sensor:
Subsystem 2 - Part No SW: ----------- HW: 480 001 102 15
Component: SideSensor_Pf 001 0887
Serial number: 3586700000036134E21K
Coding: 2D2D2D

Rear Side Airbag Crash Sensor (on driver's side):
Subsystem 3 - Part No SW: ----------- HW: 480 400 602 15
Component: SideSensor_Dr 001 6149
Serial number: 3516502A1196FF53D06K
Coding: 2D2D2D

Passenger side rear thorax airbag crash sensor:
Subsystem 4 - Part No SW: ----------- HW: 480 400 602 15
Component: SideSensor_Pr 001 6149
Serial number: 3526502BB196FF54804Q
Coding: 2D2D2D

Crash sensor for front airbag: driver side:
Subsystem 5 - Part No SW: ----------- HW: 480 400 502 15
Component: FrontSensor_D 001 6149
Serial number: 3556502C5192BC734039
Coding: 2D2D2D

No fault code found.

-------------------------------------------------------------------------------
Address 16: Steering wheel (J524) Labels:| 5Q0-953-549.clb
Part No SW: 5Q0 953 521 P HW: 5Q0 953 569 A
Component: Lenks.Modul 075 0175
Revision: FF032032 Serial number: 20150212400803
Coding: 0410
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_SMLSVALEOMQB 001015
ROD: EV_SMLSVALEOMQB.rod
VCID: 3F8D47DFA6AE927178-806A

No fault code found.

-------------------------------------------------------------------------------
Address 17: Instruments (J285) Labels:| 5G0-920-XXX-17.clb-SRI3
Part No SW: 5G1 920 756 HW: 5G1 920 756
Component: KOMBI 301 4310
Coding: 27AD09083F80000800802A011400000000000000
Shop #: WSC 00046 412 12345
ASAM Dataset: EV_DashBoardVDDMQBAB 009043
ROD: EV_DashBoardVDDMQBAB_009_VW26.rod
VCID: 6ADBC68B8DACC7D9FF-803E

No fault code found.

-------------------------------------------------------------------------------
Address 19: CAN Gateway (J533) Labels:| 5Q0-907-530-V1.clb
Part No SW: 5Q0 907 530 AC HW: 5Q0 907 530 F
Component: GW MQB High 128 1204
Revision: -------- Serial number: 0003097448
Coding: 030100342F085900FF00026B9C0F0001000105000000000000 0000000000
Shop #: WSC 00046 412 12345
GVL: 01543C5000000000400C90000000CC00000000000000000000 00000000000000
ASAM Dataset: EV_GatewLear 011020
ROD: EV_GatewLear_011.rod
VCID: 72EBDEEBA57C0F1947-8026

Generator:

Multifunction steering wheel control module:
Subsystem 2 - Part No SW: 5G0 959 442 N HW: 5G0 959 442 N
Labels: 3C8-959-537.CLB
Component: E221__MFL-DC1 H06 0038
Serial number: 29140000427050064121
Coding: 2DFFFF

Battery Monitoring Control Module:
Subsystem 3 - Part No SW: 5Q0 915 181 G HW: 5Q0 915 181 G
Component: J367-BDMHella H04 8050
Serial number: 4199495603

No fault code found.

-------------------------------------------------------------------------------
Address 32: Differential Locks (J492) Labels:* 0CQ-907-554.clb
Part No SW: 0CQ 907 554 E HW: 0CQ 907 554 E
Component: Quersperre H52 8040
Serial number: HA1-00002.12.14
Coding: 0001
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_LockElectHA1VW37X 001001
ROD: EV_LockElectHA1VW37X.rod
VCID: 479D5F3FFE7EDAB1C0-8012

No fault code found.

-------------------------------------------------------------------------------
Address 42: Door Elect, Driver (J386) Labels:| 5QX-959-X93-42.clb
Part No SW: 5Q0 959 593 D HW: 5Q0 959 593 B
Component: TSG FS 020 0028
Serial number: 270115BAP14609
Coding: 003E02208001040000000000
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_DCUDriveSideEWMAXKLO 006003
ROD: EV_DCUDriveSideEWMAXCONT.rod
VCID: 428B4E2BD55CFF9917-8016

Rear Driver Side Door Control Module:
Subsystem 1 - Part No SW: 5Q0 959 812 HW: 5Q0 959 812 Labels:
5QX-959-81X-V1.CLB
Component: FOND_FHSG_DRV 005 0005
Serial number: 00000000000005296446
Coding: 0D0000

No fault code found.

-------------------------------------------------------------------------------
Address 44: Steering Assist (J500) Labels:| 5Q0-909-144.clb
Part No SW: 3Q0 909 144 H HW: 3Q0 909 144 H
Component: EPS_MQB_ZFLS 505 5061
Coding: 8103
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_SteerAssisMQB 012140
ROD: EV_SteerAssisMQB_012_VW37.rod
VCID: 377D2FFF8E9EAA31B0-8062

No fault code found.

-------------------------------------------------------------------------------
Address 52: Door Elect, Pass. (J387) Labels:| 5QX-959-X92-52.clb
Part No SW: 5Q0 959 592 D HW: 5Q0 959 592 B
Component: TSG BFS 020 0028
Serial number: 060215BB515856
Coding: 003E02208E01040000800000
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_DCUPasseSideEWMAXKLO 006003
ROD: EV_DCUPasseSideEWMAXCONT.rod
VCID: 41894127D05AE4810E-8014

Rear Passenger Door Control Module:
Subsystem 1 - Part No SW: 5Q0 959 811 HW: 5Q0 959 811 Labels:
5QX-959-81X-V1.CLB
Component: FOND_FHSG_PSG 005 0005
Serial number: 00000000000005331087
Coding: 150000

No fault code found.

-------------------------------------------------------------------------------
Address 55: Headlight Range (J745) Labels:| 7P6-907-357.clb
Part No SW: 7P6 907 357 D HW: 7P6 907 357 A
Component: AFS-ECU H07 0090
Revision: -------- Serial number: --------------
Coding: 029603000B000200
Shop #: WSC 01357 011 00200
ASAM Dataset: EV_HeadlRegulVWAFSMQB 001120
ROD: EV_HeadlRegulVWAFSMQB.rod
VCID: 408F4423DB50ED8901-8014

Left Headlamp Power Output Stage:
Subsystem 1 - Part No SW: 3D0 941 329 E HW: 3D0 941 329 E
Labels: 3D0-941-329.CLB
Component: LeiMo links H01 0002
Coding: 2E0000

Right Headlamp Power Output Stage:
Subsystem 2 - Part No SW: 3D0 941 329 E HW: 3D0 941 329 E
Labels: 3D0-941-329.CLB
Component: LeiMo rechts H01 0002
Coding: 2E0000

No fault code found.

-------------------------------------------------------------------------------
Address 5F: Information Electr.
Cannot be reached

-------------------------------------------------------------------------------
Address A9: Struct. Borne Sound (J869) Labels: 4H0-907-159.clb
Part No SW: 5G0 907 159 HW: 4H0 907 159 A
Component: SAS-GEN 2 H06 0014
Serial number: 150118201063
ASAM Dataset: EV_SoundActuaGen2AU64X 003010
ROD: EV_SoundActuaGen2AU64X.rod
VCID: 6BD5C38F8256DED184-803E

No fault code found.

End-------------------------(Elapsed Time: 05:21)--------------------------

[guile]

just pasting this here from another website as i have a feeling it may come handy for abs coding...

MK100 ABS Coding | Ross-Tech Forums

Retrofitting Adaptive Cruise Control to Mk7 (oh the fun you shall have!) | VW Vortex - Volkswagen Forum

This is an extract from the link above:

"There's a .pdf floating around out there by "Xagico" that lists a pile of different retrofits and mods that can be done on the Mk7; it has a lot of the coding changes to be made. So that's where I started.

In ABS coding, however, the recommendations on Byte24 ( F4 or F8 ) were not accepted by my car. (I'm guessing this is because Xagico is Spanish(?), and the European cars came with some hardware as standard that were not offered on our cars).
Anyway, using the Somnus's spreadsheet, I was able to calculate that Byte24 on my car should be either 16 or 18; I tried 16 there and it worked. Again, YMMV, so do the math for yourself.

Next, I changed Byte26 to F0 - if you install the new rear wheel ABS sensors first and continue to drive your car without making any other changes, you'll probably have a pile of errors on your display. Change this byte and the errors should disappear literally as you're sitting there.
(Xagico's pdf said to change this to 50, and when I had my just the wheel sensors in my car - without swapping the ABS module - "50" made the errors go away. But once the new module was in the car, while I didn't have any errors, ACC would not work. Helpful user at ross-tech forum suggested to try "F0"....and just like that, everything, ACC worked. Not sure how he arrived at F0, but I'm glad he did.

Lastly in Byte29, Xagico said to change it to 39, but that didn't work for me. A user over at Ross-tech's forums helping me out suggested 22 - and that one worked."

[MIG]

It's good to hear you got it sorted; I like to use the VCDS coding helper for these types of things and cross-check other cars' scan logs with the setup you are trying to match.

Don't worry about any coding of the 5F unit, that's only for the menus to show up on the radio.


With your component protection issue, you need to find someone who has access to ODIS, 5054a or vas6154 and access to geko; I know due to the right to repair stuff, some good VAG specialists have access to this now.


There is a shady market of companies "renting" their accounts out in 15min\20min blocks, not going to recommend that here.

[DV52]

@guile: hmmm........ the coding for the ABS module in your VCDS scan doesn't make sense (it doesn't comply with your words about the changes made).

Here's a more elucidating form of the hex03 long-code string from your SCAN report:

Byte	Hex	Binary
00	01	00000001
01	FA	11111010
02	93	10010011
03	A1	10100001
04	54	01010100
05	27	00100111
06	29	00101001
07	6C	01101100
08	07	00000111
09	7B	01111011
10	06	00000110
11	05	00000101
12	41	01000001
13	C5	11000101
14	69	01101001
15	80	10000000
16	C9	11001001
17	2A	00101010
18	94	10010100
19	E0	11100000
20	60	01100000
21	82	10000010
22	96	10010110
23	F7	11110111
24	00	00000000
25	42	01000010
26	00	00000000
27	B9	10111001
28	C2	11000010
29	09	00001001

As you can see - the coding values that you describe are NOT consistent with the list above. Maybe these are the pre-change coding values? If so, please post up the actual SCAN results post changes (the old long-code isn't of much value if you are describing the coding values that worked!)

Don

[guile]

It's good to hear you got it sorted; I like to use the VCDS coding helper for these types of things and cross-check other cars' scan logs with the setup you are trying to match.

Don't worry about any coding of the 5F unit, that's only for the menus to show up on the radio.


With your component protection issue, you need to find someone who has access to ODIS, 5054a or vas6154 and access to geko; I know due to the right to repair stuff, some good VAG specialists have access to this now.


There is a shady market of companies "renting" their accounts out in 15min\20min blocks, not going to recommend that here.

thanks mate and thanks for the reassurance regarding the 5F unit, i wondered if that would be the case. panic over...

I've also managed to get it booked in with VW for component protection removal, lets hope i walk out of there without having to remortgage the house...

[guile]

@guile: hmmm........ the coding for the ABS module in your VCDS scan doesn't make sense (it doesn't comply with your words about the changes made).

As you can see - the coding values that you describe are NOT consistent with the list above. Maybe these are the pre-change coding values? If so, please post up the actual SCAN results post changes (the old long-code isn't of much value if you are describing the coding values that worked!)

Don

thanks for the feedback Don, is there a reason Byte 14 and 22 are bold? the original coding didn't work as per the rejection photos i posted...

I'm not sure if its linked to the fact that component protection has not been removed yet or if the coding is incorrect. I'm planning to try the revised coding as per the feedback below from another forum, Nuje on VW Vortex:

"In ABS coding, however, the recommendations on Byte24 ( F4 or F8 ) were not accepted by my car. (I'm guessing this is because Xagico is Spanish(?), and the European cars came with some hardware as standard that were not offered on our cars).
Anyway, using the Somnus's spreadsheet, I was able to calculate that Byte24 on my car should be either 16 or 18; I tried 16 there and it worked. Again, YMMV, so do the math for yourself.

Next, I changed Byte26 to F0 - if you install the new rear wheel ABS sensors first and continue to drive your car without making any other changes, you'll probably have a pile of errors on your display. Change this byte and the errors should disappear literally as you're sitting there.
(Xagico's pdf said to change this to 50, and when I had my just the wheel sensors in my car - without swapping the ABS module - "50" made the errors go away. But once the new module was in the car, while I didn't have any errors, ACC would not work. Helpful user at ross-tech forum suggested to try "F0"....and just like that, everything, ACC worked. Not sure how he arrived at F0, but I'm glad he did.

Lastly in Byte29, Xagico said to change it to 39, but that didn't work for me. A user over at Ross-tech's forums helping me out suggested 22 - and that one worked."

[DV52]

...........is there a reason Byte 14 and 22 are bold? the original coding didn't work as per the rejection photos i posted...

NO- my bolded Byte 14 and Byte 22 was not relevant to your purpose (which is why I didn't address these Bytes in my response). I simply wanted to confirm (to myself) that the sequence in these Bytes was consistent with the Ross-Tech coding spreadsheet - which says that Byte 22 is the mirror of Byte 14.

But, since you have raised it, from my table:

• Byte 22 = 10010110
  
• Byte 14 = 01101001

As you can see - the 2 x Bytes are indeed mirrored!!

I'm not sure if its linked to the fact that component protection has not been removed yet or if the coding is incorrect.

Again "NO". Component Protection errors do NOT affect coding values. As you have observed, modules with CP errors can have both their adaptation channel and long-code values changed without restriction! CP errors ostensibly limit the way that the modules operate-rather than how they are coded (and modules with CP can NOT correct Basic Setting errors)

I'm planning to try the revised coding as per the feedback below from another forum, Nuje on VW Vortex:

hmm...... without intending any offense to the original Vortex authors - I would caution against modifying Bytes based on a suggestion to change the entire hex value.

To explain- as you will be aware, a Byte consists of 8 x Bits. It's important to acknowledge that each of these 8 x Bytes is independent - meaning that while a set of Bits might be associated with a particular function, each individual Bit is a separate (software) switch that has it's own singular purpose.

The ABS module on your car has 30 x Bytes - so this module has 240 separate (software) switches in its long-code string.

Here's an example of my concern about making whole-of-Byte changes as per the Vortex suggestion: Consider Byte 24 - According to the Ross-Tech spreadsheet, these are the Bit descriptors:

Byte 24

• Bit 0 = Restart when reversing
• Bit 1-4 = ACC Setting
  
  • Bit 1~4 unchecked - Without ACC, Without Front Assist, Without AEB (PR. 8T0, 8T2)
  • Bit 4 checked - Without ACC, With Front Assist, With AEB (PR. 8T0, 8T2)
  • Bit 2 & 4 checked - With ACC, With Front Assist, With AEB (PR. 8T5/8T7)
  • Bit 1, 2 & 4 checked - With ACC (Follow to Stop), With Front Assist, With AEB (MK100IPB)
  • Bit 3 & 4 checked - With ACC (Stop & Go), With Front Assist, With AEB (MK100IPB)
• Bit 5 = PLA3.0 Installed
• Bit 6 = PLA3.0 related
• Bit 7 = Trailer Assist Installed

Assume for this example that ACC is retrofitted on a car that was factory installed with- PLA2.0 (i.e. NOT PLA3.0), No trailer, No ACC, No restart when reversing. The factory value on Byte 24 on this car would be 00000000=hex00. This is the same as on your car - see my previous table

If you followed "the recommendations on Byte24 ( F4 or F8 )" from VW Vortex - the change would mean

• Byte 24 = F8 =11111000, OR
• Byte 24 = F4 =11110100

Remember that Bit 0 is the right-most digit and Bit 7 is the left-most digit in a Binary number

So in following the Vortex recommendation- not only are you telling the ABS module to enable ACC, the change also tells the module to start operating PL3.0 AND Trailer Assist!!

Moral of my story (which of course you can entirely ignore) = when modifying Byte values after a retrofit - ALWAYS (capital letters for emphasis) make changes to individual Bits. Or said another way =NEVER change whole-of-Byte hexadecimal values!!!

[guile]

thanks again for the info Don, i'm pretty new to this level of coding so some of the info is taking a while to sink in...

I'll use the somnus guide to revise Bit values when I'm back home next based on the hexadecimal table below...

Decimal.....Hex digit.....Binary code
0...................0...............0000
1...................1...............0001
2...................2...............0010
3...................3...............0011
4...................4...............0100
5...................5...............0101
6...................6...............0110
7...................7...............0111
8...................8...............1000
9...................9...............1001
10.................A...............1010
11.................B...............1011
12.................C...............1100
13.................D...............1101
14.................E...............1110
15.................F................1111

[guile]

Based on the above conversion chart please confirm if your codes below are missing a zero at the end:

"If you followed "the recommendations on Byte24 ( F4 or F8 )" from VW Vortex - the change would mean
Byte 24 = F8 =1111100, OR
Byte 24 = F4 =1111010"

I'm just trying to make sure i understand this correctly...

[DV52]

@guile: Ooops - my bad (good pick-up on your part)

Yes, indeed - I failed to make the Binary equivalent an 8 x Bit number. (now fixed - thanks)

As for your efforts to convert Hexadecimal to Binary (Hex2Bin) and vice-a-versa (Bin2Hex) - there are lots of websites that will do this automatically - like HERE

Don