2016 Passat NMS having issues with ACC retrofit.

[NEtech]

00,Cruise Control System (CCS NOT installed)
20,Cruise Control System (CCS installed)
40,Adaptive Cruise Control (ACC - without FTS support installed)
60,Adaptive Cruise Control (ACC - with FTS support installed)
would be the right Label

How do mean,
The above is for all Engine controllers that exist, for all different ASAM data, that use UDS ?
Or for this CPKA engine, ASAM file EV_ECM18TFS02006K906071AF 001008 ?

To Quote the Bosch EDC Documentation regarding this Bit 6 and 7
00: GRA / ACC deaktiviert
01: GRA aktiv
10: ACC aktiv
11: ACC follow to stop aktiv

So ACC follow to stop aktiv is hex C0?
or do you mean Bit 5 and 6.

 

[teal2]

Yap, i am very shure i reported this "Generic" Error years ago

For ECU´s which support the long Coding with that Byte 5 having 2 bit´s for CCS Coding there it is generic wrong in VCDS

00,Cruise Control System (CCS NOT installed)
20,Cruise Control System (CCS installed)
40,Adaptive Cruise Control (ACC - without FTS support installed)
60,Adaptive Cruise Control (ACC - with FTS support installed)

would be the right Label

To Quote the Bosch EDC Documentation regarding this Bit 6 and 7
00: GRA / ACC deaktiviert
01: GRA aktiv
10: ACC aktiv
11: ACC follow to stop aktiv

Yep. That matches what it should be.

 

[teal2]

How do mean,
The above is for all Engine controllers that exist, for all different ASAM data, that use UDS ?
Or for this CPKA engine, ASAM file EV_ECM18TFS02006K906071AF 001008 ?


So ACC follow to stop aktiv is hex C0?
or do you mean Bit 5 and 6.

It would be bit 5 & 6 as that is the only ACC coding in the ECM. As Uwe said, this particular ECU doesn’t contain any ASAM data from VAG to define the codings off of.

 

[dnoermann]

or do you mean Bit 5 and 6.

Sorry yes, the Bosch guys start counting Bit with 1 in their Documentation

 

[teal2]

Issue Has been solved!
The radar I bought has faulty firmware and will be replaced with one that has the correct, working firmware.
The main issue that was causing ACC to not engage was VCDS having the incorrect Definition in Long Coding in byte 5, bit 5-6. This has to be set to '44' not '64.' Setting it to 64 will tell your car that you have FtS, which while being worked on in the community for the NMS Passat, is currently not working without a comma 3x device running openpilot.
Changing this coding will result in ACC engaging, and Front Assist being on standby so long as you have a radar with working firmware lol.
Guide for the NMS Passat ACC Retrofit coming soon!

 

[dnoermann]

faulty firmware

Thats interesting.
What Chinease Copy Cat CP Remover did you pay to mutch money ?

 

[teal2]

Thats interesting.
What Chinease Copy Cat CP Remover did you pay to mutch money ?

I bought my radar from @lemoncurd who used USB JTAG on the radar to remove CP & flash firmware along with dataset with ODIS-E.

 

[lemoncurd]

Thats interesting.
What Chinease Copy Cat CP Remover did you pay to mutch money ?

Heh, you know about the faulty firmware fiasco.. it even affected my personal radar mounted in lower grille which works perfectly now thanks to you

Teal didn’t pay much teal is a frien

 

[dnoermann]

car-tools/MRRevo14_Patcher.py at master · dnoermann/car-tools

Tools for working with VW PQ25 Plattform Vehicles. Contribute to dnoermann/car-tools development by creating an account on GitHub.

github.com

There is the Manual how to do it right.
That way is for shure a bit more complicated (and my Documentation is as always in a bad state) but it really only changes the needed stuff.
For shure someone in USA is capable of doing it that way.

But if you for example do have Access to Genuine Online Odis E with Geko, than you can omit a lot of my complicated stuff and do it like this:
1. Patch Firmware with my Skript (Line 36 to 71 in my Skript) using any Jtag that will work with the MPC55xx/MPC56xx
2. Do online CP Matching like in the Shop (at this point the Development Swap Public Key will be made Active in ACC)
3. Write Development Swap Code generated by your favorite tool (Line 122 to 130) with Odis E
4. Write Dataset with Odis E or VCP

 

[teal2]

Guide Posted! https://forums.ross-tech.com/index.php?threads/42711/

 

[teal2]

Issue Has been solved!
The radar I bought has faulty firmware and will be replaced with one that has the correct, working firmware.
The main issue that was causing ACC to not engage was VCDS having the incorrect Definition in Long Coding in byte 5, bit 5-6. This has to be set to '44' not '64.' Setting it to 64 will tell your car that you have FtS, which while being worked on in the community for the NMS Passat, is currently not working without a comma 3x device running openpilot.
Changing this coding will result in ACC engaging, and Front Assist being on standby so long as you have a radar with working firmware lol.
Guide for the NMS Passat ACC Retrofit coming soon!

Issue sadly came back. The issue I’m having now is faulting the ECM and is caused when braking pressure from the ABS module is needed. I have hopefully traced this back to rear wheel speed sensors, which need to be active instead of passive.

 

[lemoncurd]

important to note that the issue is no longer radar based. the drivetrain coordinator is faulting out now.

                Address 13: Auto Dist. Reg       Labels: 7N0-907-572.clb
Control Module Part Number: 7N0 907 572 C    HW: 7E0 907 572
  Component and/or Version: ACC Bosch PQx H03 0211
           Software Coding: 00001000FE073B
            Work Shop Code: WSC 12345 123 12345
              ASAM Dataset: EV_ACCBEGVW361 001006 (VW41)
                       ROD: EV_ACCBEGVW361.rod
                      VCID: 36353153A8C19BFAA1F-8062
1 Fault Found:

1043 - Automatic Distance Control
          B10E7 F0 [00001000] - Disconnected
          [FAULT_CIS_TSK_IRREV_FAIL]
          Intermittent - Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Priority: 6
                    Fault Frequency: 1
                    Reset counter: 59
                    Mileage: 230308 km
                    Date: 2094.14.25
                    Time: 15:51:07

                    Control Module temperature: 42 °C
                    Voltage terminal 15: 14.2 V
                    Vehicle speed: 16.38 m/s
                    Acceleration: -0.14 m/s²

 

[FLcruising]

The fault codes you're experiencing are the same for when I ran BS 0166 firmware in the ABS. The problem was B11_HydHalten wouldn't send (from the ABS) during the FtS event.

My suspicion in your case is the ABS is not responding properly with BR8_Istbeschl because of the lack of active wheel sensors. A collection of vehicles with MK60EC1 are always coded in byte 18 as 50 / F0 (active rear sensors / inverted active rear sensors) when 13-Auto Dist. Reg is present. (Some have claimed to have success without active sensors with ACC.)

 

[teal2]

The fault codes you're experiencing are the same for when I ran BS 0166 firmware in the ABS. The problem was B11_HydHalten wouldn't send (from the ABS) during the FtS event.

My suspicion in your case is the ABS is not responding properly with BR8_Istbeschl because of the lack of active wheel sensors. A collection of vehicles with MK60EC1 are always coded in byte 18 as 50 / F0 (active rear sensors / inverted active rear sensors) when 13-Auto Dist. Reg is present. (Some have claimed to have success without active sensors with ACC.)

I haven’t seen any success without active sensors in the NMS Passat, maybe haven’t looked deep enough but will update when wheel sensors have been installed.

 

[FLcruising]

FOLLOW-UP!

Address 03: ABS Brakes (J104) Labels:. 1K0-907-379-60EC1F.clb
Part No SW: 1K0 907 379 CC HW: 1K0 907 379 CC
Component: ESP MK60EC1 H46 0175
Revision: 00H46001
Coding: C54BC0F5492300FFA30D03E7921C004120F00012

His byte 16 bit 5 was set which disabled ACC function in the ABS.