EPB Retrofit ... the way to Stop & Go

I guess you are reffing to this?
I have used the AUTOHOLD switch and indicating LED for a different purpose.
Soon I will disclose publicly its functionality.
@Robert @dnoermann ,I went the EEPROM route to avoid solid state relay wiring headache, but after enabling (P) symbol and Electronic handbrake in eeprom, I am surprised to see the (!) symbol coming up on dash instead, address 17 and 53 do not have any error anyway.....my eeprom is 24c64,

Address 17: Instruments (J285) Labels:| 5K0-920-xxx-17.clb-SRI1
Part No SW: 5K0 920 971 HW: 5K0 920 971
Component: KOMBI H20 0420
Serial number: 00000000000000
Coding: 470F01
Shop #: WSC 48304 001 10485
ASAM Dataset: EV_Kombi_UDS_VDD_RM09 A04089
ROD: EV_Kombi_UDS_VDD_RM09_004_VW32.rod
VCID: 6C8AAC35B602129AC33-8038
 
@Robert @dnoermann ,I went the EEPROM route to avoid solid state relay wiring headache, but after enabling (P) symbol and Electronic handbrake in eeprom, I am surprised to see the (!) symbol coming up on dash instead, address 17 and 53 do not have any error anyway.....my eeprom is 24c64,

Address 17: Instruments (J285) Labels:| 5K0-920-xxx-17.clb-SRI1
Part No SW: 5K0 920 971 HW: 5K0 920 971
Component: KOMBI H20 0420
Serial number: 00000000000000
Coding: 470F01
Shop #: WSC 48304 001 10485
ASAM Dataset: EV_Kombi_UDS_VDD_RM09 A04089
ROD: EV_Kombi_UDS_VDD_RM09_004_VW32.rod
VCID: 6C8AAC35B602129AC33-8038
Did you modify the instrument cluster circuit board as well as editing EEPROM?
 
I removed 1211 resistor to the left of display,then added 2 at the back
Did you modify the instrument cluster circuit board as well as editing EEPROM?
Yes, I removed 1211 resistor to the left of display,removed a 3 legged black resistor at the back then added 1101 & 4990 ,according to these photos, I am not sure is I should have left the black 3 leg in place,my pcb looks like this second photo after mod

ipb1.jpg

ipb2.jpg
 
Was just checking! To me solid state relay wiring is much less of a headache than cluster disassembly and PCB modification but each to their own o_O

Hopefully dnoermann can help you with this :thumbsup:
 
By default the Autohold on T6 ABS module MK100 is disabled in the firmware and therfore it is not available (yet :whistle:).
No, the T6 ABS does not support Autohold.
But i am working on that ....
For the ambitious T6/t5 retrofitters.
danman is using a car which does have an ABS that supports Autohold ... :) probably no T6
For the T6 we first need to patch ABS to support Autohold ....
Already working on it

Just a note for discuss
Found that Audi TT 8S/FV MK100 ABS controller supports Auto-Hold
at Auto Hold Assist MK100 ABS module long coding 8S0 907 379 F (e.g. Audi TT MK3)
Here's how to enable hold assist on a MK100 ABS controller, for example PN 8S0 907 379 in an Audi TT 8S/FV

ABS Module 03 Long Coding

Byte 15: Set bit 3 (Usually 06=>0E)
Byte 16: Set bit 7 (Usually 33=>B3)
Byte 25: Set bit 4 (Usually 60=>70)
Byte 26: Set bit 0 (Usually CC=>CD)

ABS Module 03 Adaptation
Security access: 20103
Adaptation: IDE05263-AUTO HOLD functionality => activated

Note:
You will need to install and wire in the auto hold button and new parking brake switch.


From some research the long coding for this module seems to be made up roughly as follows...
Byte 00: Unknown coding
Byte 01: 0xA9 + 11th VIN digit?
Byte 02: Unknown coding
Byte 03: 0x8D + 12th VIN digit?
Byte 04: Unknown coding
Byte 05: 0x99 + 13th VIN digit?
Byte 06: Unknown coding
Byte 07: 0xA9 + 14th VIN digit?
Byte 08: Unknown coding
Byte 09: 0x91 + 15th VIN digit?
Byte 10: Unknown coding
Byte 11: 0x54 + 16th VIN digit?
Byte 12: Unknown coding
Byte 13: 0x91 + 17th VIN digit?
Byte 14: Unknown coding
Byte 15: Bit 3 - Auto hold assist enable
Byte 16: Bit 7 - Auto hold assist enable
Byte 17: Reverse order of bits in byte 00
Byte 18: Reverse order of bits in byte 02
Byte 19: Reverse order of bits in byte 04
Byte 20: Reverse order of bits in byte 06
Byte 21: Reverse order of bits in byte 08
Byte 22: Reverse order of bits in byte 10
Byte 23: Reverse order of bits in byte 12
Byte 24: Reverse order of bits in byte 14
Byte 25: Reverse order of bits in byte 15
Bit 4 - Auto hold assist enable
Byte 26: Reverse order of bits in byte 16
Bit 0 - Auto hold assist enable

The coding, of course, differs from our 7E0907379P / 7E0907379Q
I hope this info will be somehow useful to impulse this topic
It will be great to find out how to bring those functionality to T6 ABS unit for stop and go with ACC
 
Last edited:
Hi there,

I'm from Germany, owning an Eos cabrio and like to retrofit the EPB into the car.
For now my unique Eos (PQ35/PQ46) is equipped with DM, 7N0 ACC, 3Q0 camera, 2Q0 RTA and some minor things.
As I found no other thread with so much knowledge concerning EPB, I've registered an account to share some information.

For realisation I've bought a 56D Control unit at Aliexpress years ago. Now, realizing the project, I thought my unit was also a fake, like so many others but i've figured out, it isn't.
At my "Car On The Table" I could reach and code the unit. Then I was building the cable tree with components from a Sharan cable tree, connected the Module and - nothing.
Verifying the cable tree shows that everything was ok.
After that, I could reach the unit for just one or two times, using a short adapter with Kl.31 (28+30), Kl.30 (13+15), Kl.15 (22) and CAN-Antrieb (16 high + 17 low). Since then, the unit does not respond anymore.
So I've opend it to see, if there was any visible fault. There was none. At that I've desoldered and read the EEPROM (attached for those of you, who are interested. Rename .csv to .bin).

Does anybody have a suggestion, why my Control unit does not work anymore from one minute to the other?

Best regards
Marc

After a short break (for just two years:thumbsup:) because of the frustration with this communication problem with my 56D I'm back, ending this break by trying to find a solution. What shall I say - it was #19. After replacing the 7N0 Getway everyting is fine and communication is stable.
In this context realized, that I've attached an empty EEPROM file. For those who will find this thread and are in search of correct data, I've now attached the correct one. Again rename .csv to .bin.

I'll try to document my journey on my way to retrofit EPB in my VW Eos 2015.

Best regards
 

Attachments

  • 56D907801A_M95320W.csv
    4 KB · Views: 5
After a short break (for just two years:thumbsup:) because of the frustration with this communication problem with my 56D I'm back, ending this break by trying to find a solution. What shall I say - it was #19. After replacing the 7N0 Getway everyting is fine and communication is stable.
In this context realized, that I've attached an empty EEPROM file. For those who will find this thread and are in search of correct data, I've now attached the correct one. Again rename .csv to .bin.

I'll try to document my journey on my way to retrofit EPB in my VW Eos 2015.

Best regards

Hi friend,I have a EPB module 3AA from Sharan,if put your EEPROM file from 56D it's possible working on mk60ec1 abs?thanks
 
3AA and 56D are compleete different Hardware, so near to 0% Chance that you can transfer the Firmware
And 3AA never was used in Sharan
 
3AA and 56D are compleete different Hardware, so near to 0% Chance that you can transfer the Firmware
And 3AA never was used in Sharan

Ok,but it's from sharan the module,I remove all parts for EPB and this module from a Sharan demolished
 
The truth about EPB revealed itself.

My Caravelle, Multivan(you name it :D ) has just passed successfully it's first periodical inspection test with the EPB onboard :thumbsup:.

It was a pass on the first attempt so I am very happy and proud of my work.
Again credit to @dnoermann for the inspiration.

Below is a comparison of my test results.
Manual/Mechanical Parking Brake(test conducted on 14/09/2020)
View attachment 176082
Electronic Parking Brake (test conducted on 14/10/2022)
View attachment 176083

Parking Brake performance has risen from 21% to 26%.
Rear axle brake effort also went up on both sides :waving:
And yet another periodic inspection carried out on the 13/09/2024.
My EPB has be verified again to be functional up to the required standard.
20241003_112515.jpg
 
Interesting. I'm surprised they don't do this already.
I drove a T6.1 with DSG and ACC around May last year - it definitely did Follow To Stop and then automatically started again.
I found that I had to follow the instructions on the dash, which was when coming to a stop brake as instructed and then once the traffic had moved on I could release the brake and the van would start again. I don't remember if there was an auto hold function but being a T6.1 it had a mechanical handbrake.
 
Hi guys, is there a solution to make it work the 5N0 switch?thanks for the information and help
5N0 uses different switches and capacitors instead of diodes.
I have explained the details below.
My play with EPB switches has come to the successful end :).

View attachment 109573View attachment 109574

Unfortunately, as posted here, switch 5N0927225B is not direct replacement for 56D927225.

Unit 5N0927225B uses 6 pins for actual EPB switch with 2 internal capacitors and unit 56D927225 uses 4 pins with 4 internal diodes.
Additionally micro switches are also different, first one has 2 x (separate N/O contacts & separate N/C contacts) against second one with 2 x ( double N/O, C, N/C).

Taking into account the size of internal PCB and SMD components I decided to transfer 2 micro switches from 56D927225 to 5N0927225B.
Illumination and all indicators are used directly from 5N0 PCB with 56D micro switches wired externally to the 56D PCB.

What's worth to mention is that unit 5N0927225B is identical physically and electronically to 5N0927225A.

Alternative method and probably much more straightforward would be to use 7N0927225B unit.
It uses 16 pin plug (part number 1K0927928).
Pins 1, 2, 3 & 4 correspond directly to the wiring of 56D927225 unit.
Pin 5(+) & 6(-) are for illumination.
Pin 9(+) & 10(-) are for EPB ON indicator.
Pin 12(-) & 13(+ in) are for Auto Hold indicator.
Pin 13(+ in) & 14(+ out) are for Auto Hold switch.
Remaining 5 pins are not in use.
View attachment 111612
Summarising all 3 (16 pin) units mentioned above 5N0927225A, 5N0927225B & 7N0927225B look identical externally
but only 7N0927225B has the same electronic internals as 56D927225 :thumbsup:.

View attachment 109575
View attachment 109576

7N0927225B is much easier approach and you should be able to find inexpensive second hand unit somewhere online.
 
...
I drove a T6.1 with DSG and ACC around May last year - it definitely did Follow To Stop and then automatically started again.
Follow To Stop description sounds correct but automatic resume of ACC does not.

I found that I had to follow the instructions on the dash, which was when coming to a stop brake as instructed and then once the traffic had moved on I could release the brake and the van would start again.
...
By putting your foot on the brake pedal the Adaptive Cruise Control gets cancelled. In order to re-engage the ACC functionality, the MFSW button (RES or SET) needs to be pressed again.
 
No not at all - and I would agree that braking would cancel ACC, but I put it to the test on the M25 on the way to Campervan Campout to see how brave I would be.
I even recorded an audio commentary at the time for use in a programme, but I'm pretty sure I deleted it (it wasn't very good).

I had ACC set to 60, the traffic was slowing and the van slowed down to a stop behind the traffic that had stopped. I was then instructed, via the DIS/MFD, to apply the brake but I don't remember the next bit (i.e., whether I released the brake before the traffic moved off or I waited until it did). Once the traffic moved, I didn't need to apply the throttle to get the van to start again. I am certain of that much.
It was a 7 speed DSG Highline spec converted panel van from a hire fleet.
 
Back
Top