(Side Assist) / (Blind Spot Detection & Rear Cross Traffic Alert) retrofit

[F-roger]

Have you finally changed all 4 sensors with ABS last Byte coding 0xF0 or just rear sensors with conding 0x50?

Looked through 1K8919472C xml data set file searching 0x16 (match 4 times), not sure which one to change for 0x04 ))

I also have info that mZAS message is about klemmers that switched-on at the moment (ignition key position), so the Gate should generate id572 packet to CAN-drive.
It is PQ35 feature, but not PQ25

This Can Id572 is in the PQ25 tires on the VW POLO! I think I have a TRACE

 

[Robert]

Have you finally changed all 4 sensors with ABS last Byte coding 0xF0 or just rear sensors with conding 0x50?

Bidirectional ABS sensors are only required on the rear axle. Coding for that is 0x50.
Regarding 0xF0 coding please see below.
I have no clue what VW actually meant with such a setting possibility.

I did an experiment with 0xF0 in ABS coding and discovered something interesting.
Basically when rear bidirectional sensors are coded for reverse operation it messes up accuracy of SAT-NAV on Discover Media. While on the move vehicle is always shifted from its real location and keeps on changing orientation.

This obviously proves that the speed readings from all four wheels are taken into consideration when vehicle location is being established. And the SAT-NAV doesn't rely on GPS signal only.

Looked through 1K8919472C xml data set file searching 0x16 (match 4 times), not sure which one to change for 0x04 ))

No idea if this is the right direction but you could try one at a time. Surely after any modification in the data set the overall CRC would need to be recalculated and saved within the code.

 

[n10n]

Interesting, thank you! If it's only about terminal status it should be fairly straightforward to generate such a packet and send it repeatedly to keep PDC happy.

I will definitely try this at some point, no promises about when though.

EDIT: can confirm 0x572 (1394) message is not present in T6 drivetrain or convenience CAN buses

Looks like 0x572 is indeed the correct message. Based on a DBC file definition I found, I tried sending couple of different static messages every 100ms. The good news is that while sending the message and clearing the missing message fault it did not come back until next start. The bad news is that the PDC stopped working, push of P button did not just do anything anymore although there was no faults recorded.

• For one test message content, P button worked with ignition on until I started the car
• For another test message content, P button did not work at all

While this for sure was not a comprehensive test, I think it shows message content is checked by the PDC module and must match the actual terminal states from some other message. Therefore, it will not be easy to fool the PDC just by sending a simple static message repeatedly - it will need an active translation from some other CAN message such as 0x570. Still, the message itself seems simple enough and probably way easier to get this right than would have been with the steering angle.

 

[strong-max]

0x572 is dynamically generated packet. Need a reference to make it work as expected (a TRACE from any PQ35 car).

 

[n10n]

0x572 is dynamically generated packet. Need a reference to make it work as expected (a TRACE from any PQ35 car).

BO_ 1394 ZAS_1: 2 XXX
 SG_ Fehlerspeichereintrag__ZAS_ : 15|1@1+ (1,0) [0|0] "" XXX
 SG_ Frei_ZAS_1_3 : 8|7@1+ (1,0) [0|0] "" XXX
 SG_ Frei_ZAS_1_2 : 7|1@1+ (1,0) [0|0] "" XXX
 SG_ Klemme_15_SV : 6|1@1+ (1,0) [0|0] "" XXX
 SG_ Frei_ZAS_1_1 : 5|1@1+ (1,0) [0|0] "" XXX
 SG_ Klemme_P__Parklichtstellung_ : 4|1@1+ (1,0) [0|0] "" XXX
 SG_ Klemme_50__Starten_ : 3|1@1+ (1,0) [0|0] "" XXX
 SG_ Klemme_X__Startvorgang_ : 2|1@1+ (1,0) [0|0] "" XXX
 SG_ Klemme_15__Z_ndung_ein_ : 1|1@1+ (1,0) [0|0] "" XXX
 SG_ S_Kontakt__Schl_ssel_steckt_ : 0|1@1+ (1,0) [0|0] "" XXX

DBC 2 bytes, trace 1... anyway, pretty clear 0x07 matches what DBC describes

 

[strong-max]

2232343 - Databus
U1121 00 [009] - Missing Message
[databus message missing - ESP_33]
Confirmed - Tested Since Memory Clear

Have you already tried to set Byte 16 bit 7 to 1 for "RCTA with brake intervention" in ABS Coding?

Have you tried this coding?

5294C420

VCP works 100% problem free, see coding show below -> 5294C4A0

Have the same ESP_33 fault when I use coding 5294C4A0
5294C420 not fits for me at all, not accepted when press Apply

Rear axle ABS sensors installed:
WHT 003 856 C
WHT 003 857 C

PDC unit:
owned 5Q0 919 294 K reflashed for 1K8 919 472 C (correct dataset also)

2Q0 radars dataset V03935308HF (Tiguan's one)

• Last byte of 03 changed to 50, checked measurements to show correct move direction
• Byte 16 bit 7 set to 1 for "RCTA with brake intervention" 28 -> A8

Seems that ABS coding is still not correct. What else I'm missing? Some of values need to be dublicated to other Bytes or not?

---------------------------
Adress 03 -  7E0 907 379 Q    АО: 7E0 907 379 N  ESC H06 0133
Coding: 307EC098656386820C7C037FA683614BA8F750
---------------------------
Adress 10 -  1K8 919 472 C    АО: 5Q0 919 294 A   PARKHILFE 8K  H03 0480
Coding: 0071155111

1 fault found:
12718592 - Data bus
          U1121 00 [009] - no communication
          [Steuergerдt fьr Lenksдulenelektronik-J527/BCM - mZAS_1 - kein Signal/keine Kommunikation]
---------------------------
Adress 3C -  2Q0 907 686 B    АО: 2Q0 907 686 B  HRE3_Kl15_Mst H06 0150
Coding: 629524A0
---------------------------
Adress 5F -  5K7 035 200 L    АО: 5K7 035 200 F MU-S--ER      H30 0480
Coding: 02140600FF0000001111000100090A001F0500D40020010003

This vehicle also has trailer, ACC and RDKS system installed if this does matter

---------------------------
Adress 13 - 7N0 907 572 C    АО: 7N0 907 572 ACC Bosch PQx H03 0211
Coding: 001C5800FE0779
---------------------------
Adress 65 -  2H6 907 273     АО: 5Q0 907 273 RDKBERU30     H04 0003
---------------------------
Adress 69 -  1K0 907 383 F    АО: 1K0 907 383 F Anhaenger     H09 0100
Coding: 410D000100000000

 

[n10n]

Have the same ESP_33 fault when I use coding 5294C4A0

I ended up with 529524A0. I also thought there was still some issues with 03 (ABS) coding but it was all 3C (Lane Change).

As tipped by @Shadow109: auto brake for RCTA, since its not supported by our ABS, and thats why your RCTA didn’t work

 

[strong-max]

Have you already tried to set Byte 16 bit 7 to 1 for "RCTA with brake intervention" in ABS Coding?

@Robert Could you please share what's an ABS module on your car and coding? Can you confirm that brake intervention (emergency stop with RCTA) works on MK100 ? Perhaps depends on module version P or Q. I was sure it supports this feature hmmm..

 

[Robert]

Have you already tried to set Byte 16 bit 7 to 1 for "RCTA with brake intervention" in ABS Coding?

This coding originates from VW documentation.

@Robert Could you please share what's an ABS module on your car and coding?

Remaind me later and I'll get you fresh scan.

Can you confirm that brake intervention (emergency stop with RCTA) works on MK100 ?

Unfortunately it doesn't work (yet).
It is confusing cause coding setting mentioned above suggest it should. Maybe there are other conditions or settings that I haven't figured out yet.
Or maybe this functionality is purposely disabled in the firmware similarly like AutoHold.
@dnoermann is working hard in his spare time to crack down MK100 firmware so maybe some day we will know more.

Perhaps depends on module version P or Q. I was sure it supports this feature hmmm..

The only difference that I am aware of is braking efficiency/performance over prolonged time.
Basically the unit with higher performance allows to perform braking over long time with no issues.
The unit with lower performance will function the same way but if braking is very frequent and for a long time it will get overheated and report corresponding fault.

 

[Lez78]

I ended up with 529524A0. I also thought there was still some issues with 03 (ABS) coding but it was all 3C (Lane Change).

As tipped by @Shadow109: auto brake for RCTA, since its not supported by our ABS, and thats why your RCTA didn’t work

ABS support auto brake... the PDC module not....

 

[mencey]

I am trying to install side assist on a VW ID.3 Pro perfomance204 hp, 58kw 2021 model with 2Q0 907 685 G and 686 G control units.
I have already defined the wiring connections but I am missing the coding. Does anyone have the side assist coding for OBDEleven or ODIS ?

 

[mencey]

 

[mmi]

2Q0 907 685 G and 686 G control units.

>>> 2Q0 907 685 G <<<



.

 

[mencey]

If I was wrong, it's 2Q0 907 685/6 F

 

[n10n]

If I was wrong, it's 2Q0 907 685/6 F

The radars in your picture are 2QD 907 685/6 F

 

[mmi]

2QD might be a challenge...

>>> 2QD 907 685... <<<

 

[mencey]

2QD might be a challenge...

>>> 2QD 907 685... <<

They sold them to me in a specific kit for VW ID.3, it brings the two control units, the two LED indicators of the mirrors and the wiring. Why do you say it's a challenge?

 

[mencey]

 

[mmi]

Why do you say it's a challenge?

In the linked threads there were quite a few difficulties getting them to work.

They sold them to me in a specific kit for VW ID.3

So it seems the seller has done all the programming for you - including the coding?

 

[mencey]

No, he didn't provide me with the coding or any dongle to carry it out. That's why I asked if anyone knows how to code it.