7.5 Golf R ACC Misadjusted

freehassan
New Member

Posts: 11

7.5 Golf R ACC Misadjusted Nov 26, 2024 17:48:10 GMT via mobile

Quote

Post by freehassan on Nov 26, 2024 17:48:10 GMT

Hi everyone. I have had this car for almost 3 years now. I've had this fault on there for almost as long, want to sell it and would like to fix it for the potential new owner. It started happening once I took the car to Pandora Car Alarms in Redditch. I had the alarm fitted, the tech and the team said that the fault would clear itself after X amount of miles. It didn't. I've taken it back they refuse to take responsibility and I am past my period of warranty from them. What a surprise huh. I have yet to remove the badge or grill and check the sensor. Or to clean it. If I try to do the calibration in basic settings I get an error saying cancelled due to detected malfunction.

I also have a CCS switch error that says internal malfunction and I am unsure if they are both related. I will include a full scan. Thank you in advance!

Including the engine module as maybe the data bus error is related to something else.

---------------------------------------------------------------
01 Engine

System description: 2.0l R4 TFSI
Software number: 8V0906259J
Software version: 0003
Hardware number: 06K907425B
Hardware version: H13
ODX name: EV_ECM20TFS0208V0906259J
ODX version: 001005
Long coding: 092500122466050B2004

Trouble codes:
P301900 - Exhaust door valve 1 Open circuit
static
Date: 2024-11-26 17:42:17
Mileage: 106366 km
Priority: 2
Malfunction frequency counter: 1
Unlearning counter: 255
Engine speed: 749.00 1/min
Normed load value: 3.9 %
Vehicle speed: 0 km/h
Coolant temperature: 93 °C
Intake air temperature: 42 °C
Ambient air pressure: 990 mbar
Voltage terminal 30: 14.511 V
Dynamic environmental data: 209628110E0211EC0411DC000011ED1F10A6019911EE2011DB06AA
P302300 - Exhaust door valve 2 Open circuit
static
Date: 2024-11-26 17:42:17
Mileage: 106366 km
Priority: 2
Malfunction frequency counter: 1
Unlearning counter: 255
Engine speed: 749.00 1/min
Normed load value: 3.9 %
Vehicle speed: 0 km/h
Coolant temperature: 93 °C
Intake air temperature: 42 °C
Ambient air pressure: 990 mbar
Voltage terminal 30: 14.511 V
Dynamic environmental data: 209628110E0211EC0411DC000011ED1F10A6019911EE2011DB06AA
U112300 - Databus error value received
static
Date: 2024-11-26 17:42:16
Mileage: 106366 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 255
Engine speed: 753.25 1/min
Normed load value: 3.5 %
Vehicle speed: 0 km/h
Coolant temperature: 93 °C
Intake air temperature: 42 °C
Ambient air pressure: 990 mbar
Voltage terminal 30: 14.492 V
Dynamic environmental data: 209628416F03416D0243832080416C02110E02
P003300 - Turbo Charger Bypass Valve Control Circuit
static
Date: 2024-11-26 17:42:17
Mileage: 106366 km
Priority: 2
Malfunction frequency counter: 1
Unlearning counter: 255
Engine speed: 749.00 1/min
Normed load value: 3.9 %
Vehicle speed: 0 km/h
Coolant temperature: 93 °C
Intake air temperature: 42 °C
Ambient air pressure: 990 mbar
Voltage terminal 30: 14.511 V
Dynamic environmental data: 209628110E0211EC0411DC000011ED1F10A6019911EE2011DB06AA

---------------------------------------------------------------

---------------------------------------------------------------
13 Adaptive Cruise Control

System description: ACC BOSCH MQB
Software number: 5Q0907572J
Software version: 0654
Hardware number: 3QF907572
Hardware version: H10
ODX name: EV_ACCBOSCHVW416
ODX version: 002006
Long coding: 3300678159FFC728949C810580400600000000000000000000

Trouble codes:
C110300 - Adaptive cruise control sensor misadjusted
static
Date: 2024-11-26 17:42:18
Mileage: 106366 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 159
Dynamic environmental data: 028D590285901011000010120000102E07
U112300 - Databus error value received
static
Date: 2024-11-26 17:42:18
Mileage: 106366 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 159
Dynamic environmental data: 028D590285901011000010120000102E07
U112300 - Databus error value received
static
Date: 2024-11-26 17:42:18
Mileage: 106366 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 159
Dynamic environmental data: 028D590285901011000010120000102E07

---------------------------------------------------------------

19 Gateway

System description: GW MQB High
Software number: 3Q0907530L
Software version: 4326
Hardware number: 3Q0907530C
Hardware version: 436
Serial number: 0007229182
ODX name: EV_GatewNF
ODX version: 013044
Long coding: 030100047F085900FB00827E1C0F00010001070000000000000000000000

Subsystems:
System description: J367-BDMHella
Software version: 9070
Hardware version: H10
Serial number: 1933626304

System description: E221__MFL-DC1
Software version: 0040
Hardware version: H11
Serial number: 29170002376720017421
Long coding: 2DFFFF

Trouble codes:
B115496 - CCS Switch Internal malfunction
static
Date: 2024-11-26 17:42:21
Mileage: 106366 km
Priority: 2
Malfunction frequency counter: 1
Unlearning counter: 159
Supply voltage, terminal 30: 14.3 V
Terminal 15: On

---------------------------------------------------------------

dv52 (Australia)
Moderator

Posts: 6,089

7.5 Golf R ACC Misadjusted Nov 26, 2024 20:29:39 GMT

Quote

Post by dv52 (Australia) on Nov 26, 2024 20:29:39 GMT

freehassan: Hi.

It will be difficult to make an informed response to this matter because alas you have cleared the original fault (probably many times) thereby wiping-out the very first batch of Freeze-frame data. As currently listed in your SCAN extract - ALL the faults happened at the same time, which is likely when the SCAN report was created! So, this situation and the fact that these are "aged faults" means that lots more investigation is needed!!

My hunch (guess, really) is that there might be more than one problem with this car. Your words, "it started happening once I took the car to Pandora Car Alarms" is telling. Of course anything is possible when diagnosing faults - but I assume the alarm system that was retrofitted to this car was not OEM. This raises the fundamental issue about compatibility and the more important question about what actual coding changes were made and to which modules?

It is disturbing that "the team said that the fault would clear itself after X amount of miles". Unless "X" is an infinite number, it's difficult to understand how any of the faults in your SCAN will clear as advised!! In truth, the ONLY way that these faults will ever self-clear is determined by the fault-parameter Unlearning counter=255 (see the SCAN). This means that ONLY if the car has experienced 255 x driving cycles in sequence where the errors do NOT re-appear - the faults will self-clear! A "driving cycle" is a defined term - but it is roughly equivalent to a reasonable driven distance. 255 is the largest number possible for this fault-parameter. So, bottom-line - any fault with Unlearning counter=255 will NEVER self-clear and any self respecting workshop should be aware of this diagnostic idiom!

OK, as for the way forward- it would be extremely useful if Pandora Car Alarms could tell you what coding changes were made to this car and if they removed/replaced the radar module on the front grill. Yes, check that the sensor is correctly seated - but do NOT disconnect the module connector.

Which form of switches is used for ACC on this car- buttons on the steering wheel, or buttons on the stalk?

Do you have records in the History data against your OBD11 account that contains the long-code strings for the problematic modules - BEFORE the alarm was installed? If so, compare the old long-code values for each module with the current values.

Don

Please don't ask questions about car coding/repair via the forum "Message" function. The better place for such dialogue is in the forum proper. That way, the wider expertise of the entire forum community can be applied to solve your problem - thank you

freehassan
New Member

Posts: 11

7.5 Golf R ACC Misadjusted Nov 26, 2024 21:42:03 GMT via mobile

Quote

Post by freehassan on Nov 26, 2024 21:42:03 GMT

Nov 26, 2024 20:29:39 GMT dv52 (Australia) said:

freehassan: Hi.

It will be difficult to make an informed response to this matter because alas you have cleared the original fault (probably many times) thereby wiping-out the very first batch of Freeze-frame data. As currently listed in your SCAN extract - ALL the faults happened at the same time, which is likely when the SCAN report was created! So, this situation and the fact that these are "aged faults" means that lots more investigation is needed!!

My hunch (guess, really) is that there might be more than one problem with this car. Your words, "it started happening once I took the car to Pandora Car Alarms" is telling. Of course anything is possible when diagnosing faults - but I assume the alarm system that was retrofitted to this car was not OEM. This raises the fundamental issue about compatibility and the more important question about what actual coding changes were made and to which modules?

It is disturbing that "the team said that the fault would clear itself after X amount of miles". Unless "X" is an infinite number, it's difficult to understand how any of the faults in your SCAN will clear as advised!! In truth, the ONLY way that these faults will ever self-clear is determined by the fault-parameter Unlearning counter=255 (see the SCAN). This means that ONLY if the car has experienced 255 x driving cycles in sequence where the errors do NOT re-appear - the faults will self-clear! A "driving cycle" is a defined term - but it is roughly equivalent to a reasonable driven distance. 255 is the largest number possible for this fault-parameter. So, bottom-line - any fault with Unlearning counter=255 will NEVER self-clear and any self respecting workshop should be aware of this diagnostic idiom!

OK, as for the way forward- it would be extremely useful if Pandora Car Alarms could tell you what coding changes were made to this car and if they removed/replaced the radar module on the front grill. Yes, check that the sensor is correctly seated - but do NOT disconnect the module connector.

Which form of switches is used for ACC on this car- buttons on the steering wheel, or buttons on the stalk?

Do you have records in the History data against your OBD11 account that contains the long-code strings for the problematic modules - BEFORE the alarm was installed? If so, compare the old long-code values for each module with the current values.

Don

Hi bud. Thank you for the response.

Yes it's an aftermarket alarm and immobilizer. I have a scan I did right after it was installed as I found it odd. By X amount of miles they said a couple hundred. It's definitely compatible. I was speaking to another member who had their alarm fitted after me and didn't have this issue. They claim to have not removed or touched the front bumper. I'll get the original scans from the installation day and paste under here.

---------------------------------------------------------------
Fault
Control unit: 01 Engine
Active faults: 1
Inactive faults: 0
System description: 2.0l R4 TFSI
Software number: 8V0906259J
Software version: 0003
Hardware number: 06K907425B
Hardware version: H13
ODX name: EV_ECM20TFS0208V0906259J
ODX version: 001005
Faults:
17186 - Unknown
static
Date: 2022-02-11 01:53:44
Mileage: 91982 km
Priority: 6
Malfunction frequency counter: 10
Unlearning counter: 255
Engine speed: 0.00 1/min
Normed load value: 0.0 %
Vehicle speed: 0 km/h
Coolant temperature: 40 °C
Intake air temperature: 31 °C
Ambient air pressure: 1010 mbar
Voltage terminal 30: 10.878 V
Dynamic environmental data: 209628416F03416D0243832080416C02110E00

Mileage: 92023 km
Date: 2022-02-11 18:36

---------------------------------------------------------------

---------------------------------------------------------------
Fault
Control unit: 09 Central Electrics
Active faults: 2
Inactive faults: 0
System description: BCM MQBAB M+
Software number: 5Q0937084CP
Software version: 0253
Hardware number: 5Q0937084CF
Hardware version: H36
Serial number: 01001800402562
ODX name: EV_BCMMQB
ODX version: 018001
Faults:
267012 - Unknown
static
Date: 2022-02-11 01:52:22
Mileage: 91982 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 154
Terminal 15 status: On
Terminal 50 status: Off
Voltage: 10.9 V
Outside air temperature: 15.5 °C
Status Bremslichtschalter (HW): Off
Status Bremslichtschalter (CAN): Off
Off: not activated
Parking light: not activated
Automatic high beam assist: operated
Low beam: not activated
Parking light left: not activated
Parking light right: not activated
Letzte Weckursache/ Werte [00;2E]: keine Störschutzursache
CAN-Bus_aktiv: On
267032 - Unknown
static
Date: 2022-02-11 01:52:18
Mileage: 91982 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 154
Terminal 15 status: On
Terminal 50 status: Off
Voltage: 10.9 V
Outside air temperature: 15.5 °C
Status Bremslichtschalter (HW): Off
Status Bremslichtschalter (CAN): Off
Off: not activated
Parking light: not activated
Automatic high beam assist: operated
Low beam: not activated
Parking light left: not activated
Parking light right: not activated
Letzte Weckursache/ Werte [00;2E]: keine Störschutzursache
CAN-Bus_aktiv: On

Mileage: 92023 km
Date: 2022-02-11 18:36

---------------------------------------------------------------
Fault
Control unit: 13 Adaptive Cruise Control
Active faults: 4
Inactive faults: 0
System description: ACC BOSCH MQB
Software number: 5Q0907572J
Software version: 0654
Hardware number: 3QF907572
Hardware version: H10
ODX name: EV_ACCBOSCHVW416
ODX version: 002006
Faults:
267 - Unknown
static
Date: 2022-02-11 01:53:55
Mileage: 91982 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 154
Dynamic environmental data: 028D4B02856C1011000010120000102E07
2127 - Unknown
static
Date: 2022-02-11 01:53:55
Mileage: 91982 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 154
Dynamic environmental data: 028D4B02856C1011000010120000102E07
1116 - Unknown
static
Date: 2022-02-11 01:53:55
Mileage: 91982 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 154
Dynamic environmental data: 028D4B02856C1011000010120000102E07
2068 - Unknown
static
Date: 2022-02-11 01:53:55
Mileage: 91982 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 154
Dynamic environmental data: 028D4B02856C1011000010120000102E07

Mileage: 92023 km
Date: 2022-02-11 18:36

---------------------------------------------------------------

freehassan
New Member

Posts: 11

7.5 Golf R ACC Misadjusted Nov 26, 2024 21:44:50 GMT via mobile

Quote

Post by freehassan on Nov 26, 2024 21:44:50 GMT

Nov 26, 2024 21:42:03 GMT freehassan said:

Nov 26, 2024 20:29:39 GMT dv52 (Australia) said:

freehassan: Hi.

It will be difficult to make an informed response to this matter because alas you have cleared the original fault (probably many times) thereby wiping-out the very first batch of Freeze-frame data. As currently listed in your SCAN extract - ALL the faults happened at the same time, which is likely when the SCAN report was created! So, this situation and the fact that these are "aged faults" means that lots more investigation is needed!!

My hunch (guess, really) is that there might be more than one problem with this car. Your words, "it started happening once I took the car to Pandora Car Alarms" is telling. Of course anything is possible when diagnosing faults - but I assume the alarm system that was retrofitted to this car was not OEM. This raises the fundamental issue about compatibility and the more important question about what actual coding changes were made and to which modules?

It is disturbing that "the team said that the fault would clear itself after X amount of miles". Unless "X" is an infinite number, it's difficult to understand how any of the faults in your SCAN will clear as advised!! In truth, the ONLY way that these faults will ever self-clear is determined by the fault-parameter Unlearning counter=255 (see the SCAN). This means that ONLY if the car has experienced 255 x driving cycles in sequence where the errors do NOT re-appear - the faults will self-clear! A "driving cycle" is a defined term - but it is roughly equivalent to a reasonable driven distance. 255 is the largest number possible for this fault-parameter. So, bottom-line - any fault with Unlearning counter=255 will NEVER self-clear and any self respecting workshop should be aware of this diagnostic idiom!

OK, as for the way forward- it would be extremely useful if Pandora Car Alarms could tell you what coding changes were made to this car and if they removed/replaced the radar module on the front grill. Yes, check that the sensor is correctly seated - but do NOT disconnect the module connector.

Which form of switches is used for ACC on this car- buttons on the steering wheel, or buttons on the stalk?

Do you have records in the History data against your OBD11 account that contains the long-code strings for the problematic modules - BEFORE the alarm was installed? If so, compare the old long-code values for each module with the current values.

Don

Hi bud. Thank you for the response.

Yes it's an aftermarket alarm and immobilizer. I have a scan I did right after it was installed as I found it odd. By X amount of miles they said a couple hundred. It's definitely compatible. I was speaking to another member who had their alarm fitted after me and didn't have this issue. They claim to have not removed or touched the front bumper. I'll get the original scans from the installation day and paste under here.

---------------------------------------------------------------
Fault
Control unit: 01 Engine
Active faults: 1
Inactive faults: 0
System description: 2.0l R4 TFSI
Software number: 8V0906259J
Software version: 0003
Hardware number: 06K907425B
Hardware version: H13
ODX name: EV_ECM20TFS0208V0906259J
ODX version: 001005
Faults:
17186 - Unknown
static
Date: 2022-02-11 01:53:44
Mileage: 91982 km
Priority: 6
Malfunction frequency counter: 10
Unlearning counter: 255
Engine speed: 0.00 1/min
Normed load value: 0.0 %
Vehicle speed: 0 km/h
Coolant temperature: 40 °C
Intake air temperature: 31 °C
Ambient air pressure: 1010 mbar
Voltage terminal 30: 10.878 V
Dynamic environmental data: 209628416F03416D0243832080416C02110E00

Mileage: 92023 km
Date: 2022-02-11 18:36

---------------------------------------------------------------

---------------------------------------------------------------
Fault
Control unit: 09 Central Electrics
Active faults: 2
Inactive faults: 0
System description: BCM MQBAB M+
Software number: 5Q0937084CP
Software version: 0253
Hardware number: 5Q0937084CF
Hardware version: H36
Serial number: 01001800402562
ODX name: EV_BCMMQB
ODX version: 018001
Faults:
267012 - Unknown
static
Date: 2022-02-11 01:52:22
Mileage: 91982 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 154
Terminal 15 status: On
Terminal 50 status: Off
Voltage: 10.9 V
Outside air temperature: 15.5 °C
Status Bremslichtschalter (HW): Off
Status Bremslichtschalter (CAN): Off
Off: not activated
Parking light: not activated
Automatic high beam assist: operated
Low beam: not activated
Parking light left: not activated
Parking light right: not activated
Letzte Weckursache/ Werte [00;2E]: keine Störschutzursache
CAN-Bus_aktiv: On
267032 - Unknown
static
Date: 2022-02-11 01:52:18
Mileage: 91982 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 154
Terminal 15 status: On
Terminal 50 status: Off
Voltage: 10.9 V
Outside air temperature: 15.5 °C
Status Bremslichtschalter (HW): Off
Status Bremslichtschalter (CAN): Off
Off: not activated
Parking light: not activated
Automatic high beam assist: operated
Low beam: not activated
Parking light left: not activated
Parking light right: not activated
Letzte Weckursache/ Werte [00;2E]: keine Störschutzursache
CAN-Bus_aktiv: On

Mileage: 92023 km
Date: 2022-02-11 18:36

---------------------------------------------------------------
Fault
Control unit: 13 Adaptive Cruise Control
Active faults: 4
Inactive faults: 0
System description: ACC BOSCH MQB
Software number: 5Q0907572J
Software version: 0654
Hardware number: 3QF907572
Hardware version: H10
ODX name: EV_ACCBOSCHVW416
ODX version: 002006
Faults:
267 - Unknown
static
Date: 2022-02-11 01:53:55
Mileage: 91982 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 154
Dynamic environmental data: 028D4B02856C1011000010120000102E07
2127 - Unknown
static
Date: 2022-02-11 01:53:55
Mileage: 91982 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 154
Dynamic environmental data: 028D4B02856C1011000010120000102E07
1116 - Unknown
static
Date: 2022-02-11 01:53:55
Mileage: 91982 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 154
Dynamic environmental data: 028D4B02856C1011000010120000102E07
2068 - Unknown
static
Date: 2022-02-11 01:53:55
Mileage: 91982 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 154
Dynamic environmental data: 028D4B02856C1011000010120000102E07

Mileage: 92023 km
Date: 2022-02-11 18:36

---------------------------------------------------------------

Apologies. I have exported them properly in this response.

---------------------------------------------------------------
01 Engine

System description: 2.0l R4 TFSI
Software number: 8V0906259J
Software version: 0003
Hardware number: 06K907425B
Hardware version: H13
ODX name: EV_ECM20TFS0208V0906259J
ODX version: 001005
Long coding: 092500122466050B2004

Trouble codes:
U112300 - Databus error value received
static
Date: 2022-02-11 01:53:44
Mileage: 91982 km
Priority: 6
Malfunction frequency counter: 10
Unlearning counter: 255
Engine speed: 0.00 1/min
Normed load value: 0.0 %
Vehicle speed: 0 km/h
Coolant temperature: 40 °C
Intake air temperature: 31 °C
Ambient air pressure: 1010 mbar
Voltage terminal 30: 10.878 V
Dynamic environmental data: 209628416F03416D0243832080416C02110E00

---------------------------------------------------------------
13 Adaptive Cruise Control

System description: ACC BOSCH MQB
Software number: 5Q0907572J
Software version: 0654
Hardware number: 3QF907572
Hardware version: H10
ODX name: EV_ACCBOSCHVW416
ODX version: 002006
Long coding: 3300678159FFC728949C810580400600000000000000000000

Trouble codes:
C110300 - Adaptive cruise control sensor misadjusted
static
Date: 2022-02-11 01:53:55
Mileage: 91982 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 154
Dynamic environmental data: 028D4B02856C1011000010120000102E07
U112300 - Databus error value received
static
Date: 2022-02-11 01:53:55
Mileage: 91982 km
Priority: 4
Malfunction frequency counter: 1
Unlearning counter: 154
Dynamic environmental data: 028D4B02856C1011000010120000102E07
U112200 - Databus implausible message
static
Date: 2022-02-11 01:53:55
Mileage: 91982 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 154
Dynamic environmental data: 028D4B02856C1011000010120000102E07
U112300 - Databus error value received
static
Date: 2022-02-11 01:53:55
Mileage: 91982 km
Priority: 6
Malfunction frequency counter: 1
Unlearning counter: 154
Dynamic environmental data: 028D4B02856C1011000010120000102E07

---------------------------------------------------------------
19 Gateway

System description: GW MQB High
Software number: 3Q0907530L
Software version: 4326
Hardware number: 3Q0907530C
Hardware version: 436
Serial number: 0007229182
ODX name: EV_GatewNF
ODX version: 013044
Long coding: 030100047F085900FB00827E1C0F00010001070000000000000000000000

Trouble codes:
B115496 - CCS Switch Internal malfunction
static
Date: 2022-02-11 01:54:02
Mileage: 91982 km
Priority: 2
Malfunction frequency counter: 68
Unlearning counter: 155
Supply voltage, terminal 30: 10.7 V
Terminal 15: On
B1802F1 - NV-Energy management Alarm triggered
Intermittent
Date: 2022-02-11 01:54:02
Mileage: 91982 km
Priority: 4
Malfunction frequency counter: 3
Unlearning counter: 194
Supply voltage, terminal 30: 10.7 V
Terminal 15: On

freehassan
New Member

Posts: 11

7.5 Golf R ACC Misadjusted Nov 26, 2024 21:48:34 GMT via mobile

Quote

Post by freehassan on Nov 26, 2024 21:48:34 GMT

These are before the alarm was installed.

---------------------------------------------------------------
01 Engine

System description: 2.0l R4 TFSI
Software number: 8V0906259J
Software version: 0003
Hardware number: 06K907425B
Hardware version: H13
ODX name: EV_ECM20TFS0208V0906259J
ODX version: 001005
Long coding: 092500122466050B2004

Trouble codes:
No trouble codes found

---------------------------------------------------------------
13 Adaptive Cruise Control

System description: ACC BOSCH MQB
Software number: 5Q0907572J
Software version: 0654
Hardware number: 3QF907572
Hardware version: H10
ODX name: EV_ACCBOSCHVW416
ODX version: 002006
Long coding: 3300678159FFC728949C810580400600000000000000000000

Trouble codes:
No trouble codes found

---------------------------------------------------------------
19 Gateway

System description: GW MQB High
Software number: 3Q0907530L
Software version: 4326
Hardware number: 3Q0907530C
Hardware version: 436
Serial number: 0007229182
ODX name: EV_GatewNF
ODX version: 013044
Long coding: 030100047F085900FB00827E1C0F00010001070000000000000000000000

Trouble codes:
U140600 - Static current too high
Intermittent
Priority: 7
Malfunction frequency counter: 205
Unlearning counter: 185
Supply voltage, terminal 30: 12.4 V
Terminal 15: Off

dv52 (Australia)
Moderator

Posts: 6,089

7.5 Golf R ACC Misadjusted Nov 26, 2024 23:04:18 GMT

Quote

Post by dv52 (Australia) on Nov 26, 2024 23:04:18 GMT

hmm........ more truncated SCAN reports!! It happens a lot on forums - but I've never understood this practice. It's like asking someone to read a technical document - but only supplying the page describing the conclusion!!

Understanding stuff (as distinct to just knowing stuff) is all about placing facts into their proper context! There is often more information in the "uninteresting modules" in a SCAN than in the modules that report errors. And even if not, remote diagnostics for the type of problems on this car is an exercise of nuance - so ALL data is useful and missing data is often the reason for failure!

Anyway, I can't find any long-code changes in the before/after SCANs on the 3 x modules that you have provided.

However, the first registration of the errors on these modules is shown in the date stamp - 2022-02-11 (which was a Wednesday). I suggest that you check with your receipts if this is the same day as the date that the new alarm was installed.

Nevertheless and even if the dates lines-up - I very much doubt that Pandora Car Alarms was working on this car at the time shown on the time-stamp for the errors - which is 01:52 hrs! What was this car doing at this time - was it likely being driven?

Don

Last Edit: Nov 26, 2024 23:12:09 GMT by dv52 (Australia)

Please don't ask questions about car coding/repair via the forum "Message" function. The better place for such dialogue is in the forum proper. That way, the wider expertise of the entire forum community can be applied to solve your problem - thank you

freehassan
New Member

Posts: 11

7.5 Golf R ACC Misadjusted Nov 26, 2024 23:24:22 GMT via mobile

Quote

Post by freehassan on Nov 26, 2024 23:24:22 GMT

Nov 26, 2024 23:04:18 GMT dv52 (Australia) said:

hmm........ more truncated SCAN reports!! It happens a lot on forums - but I've never understood this practice. It's like asking someone to read a technical document - but only supplying the page describing the conclusion!!

Understanding stuff (as distinct to just knowing stuff) is all about placing facts into their proper context! There is often more information in the "uninteresting modules" in a SCAN than in the modules that report errors. And even if not, remote diagnostics for the type of problems on this car is an exercise of nuance - so ALL data is useful and missing data is often the reason for failure!

Anyway, I can't find any long-code changes in the before/after SCANs on the 3 x modules that you have provided.

However, the first registration of the errors on these modules is shown in the date stamp - 2022-02-11 (which was a Wednesday). I suggest that you check with your receipts if this is the same day as the date that the new alarm was installed.

Nevertheless and even if the dates lines-up - I very much doubt that Pandora Car Alarms was working on this car at the time shown on the time-stamp for the errors - which is 01:52 hrs! What was this car doing at this time - was it likely being driven?

Don

I have full scans in my history, it was definitely on the 11th of February 2022 at 9am. If you show me how to get the full data I will provide it. I must've scanned it some time when I got home. It would have been parked up with ignition on likely. I feel as if some wiring somewhere is damaged but have no idea how to find out where. I've taken the badge off and confirmed the sensor is snapped in place. If I manually go into EOL mode and set the misalignment and vertical (can't remember the name of the values) to 0.0. The front assist error disappears and I can clear it, it doesn't show on mib, but still get ACC error and the databus errors remain.

dv52 (Australia)
Moderator

Posts: 6,089

7.5 Golf R ACC Misadjusted Nov 27, 2024 22:29:19 GMT

Quote

Post by dv52 (Australia) on Nov 27, 2024 22:29:19 GMT

Nov 26, 2024 23:24:22 GMT freehassan said:

I have full scans in my history, it was definitely on the 11th of February 2022 at 9am. ................... I must've scanned it some time when I got home. It would have been parked up with ignition on likely. I feel as if some wiring somewhere is damaged but have no idea how to find out where.

I assume "it" means the date/time of the first SCAN after the alarm/immobilizer was installed.

" It would have been parked up with ignition on likely". Hmmm...... I'm not sure why a Professional workshop would leave a car with ignition-ON overnight because of the battery drain that it causes. But you might be correct because the Freeze frame data field for some of the errors that are reported on the SCAN @ 01:52hrs says:

Supply voltage, terminal 30: 10.7V.
Terminal 15:ON

Terminal 15:ON=ignition-ON

Terminal 30 = permanent battery volts

However, even if you are correct - it's still very odd that these errors happened at 01:52 hrs! How does a C110300 - Adaptive cruise control sensor misadjusted error happen when the car was just sitting stationary in the workshop with no driver - even with ignition-ON and engine-OFF ?

Plus, if the battery rail voltage on this car was 10.7V @ 01:52 hrs on the morning of the day that you picked-up the car - it would have been very low indeed when you actually started the engine when you arrived at the workshop, presumably 6-7 hours later!!

Nov 26, 2024 23:24:22 GMT freehassan said:

If you show me how to get the full data I will provide it.............. I feel as if some wiring somewhere is damaged but have no idea how to find out where.

Yes, the B115496 - CCS Switch Internal malfunction error on the Gateway module could be a physical problem with either the wiring, or the switch(es)

But again, the same question arises - how does this error happen on a car that is not being driven and has no driver? If Pandora damaged the wiring, we would reasonably both expect the time-stamp for the error would be during working hours!!

The way to digitize the History file is using the procedure below. However, because this problem has a long history - please don't bombard me with a huge data-dump of information (it's been done before and it's not helpful!). Review the SCANs yourself and pick-out just the two that are immediately before the alarm fitment and the first time that the errors appear.

AND - please don't dump the contents of the files directly into a post - instead use the attachment facility to append the file itself to the post. The procedure is below (the first screenshot is the History screen):

Nov 26, 2024 23:24:22 GMT freehassan said:

I've taken the badge off and confirmed the sensor is snapped in place. If I manually go into EOL mode and set the misalignment and vertical (can't remember the name of the values) to 0.0. The front assist error disappears and I can clear it, it doesn't show on mib, but still get ACC error and the databus errors remain.

Hmm.........OK, new information!

Because the operation of the front radar is a safety issue for the car occupants, I never play with the calibration settings on the A5 module. But I doubt that just manually setting the horizontal/vertical alignment readings to zero is a kosher way of calibrating the type 1 radar on a Golf mk7. The manufacturer's procedure for calibration is not trivial and it involves a sophisticated target - like the unit below.

Regardless of how these errors were originally created and by whom - this may be the reason why at least the C110300 - Adaptive cruise control sensor misadjusted error persists

Last Edit: Nov 27, 2024 22:30:53 GMT by dv52 (Australia)

Please don't ask questions about car coding/repair via the forum "Message" function. The better place for such dialogue is in the forum proper. That way, the wider expertise of the entire forum community can be applied to solve your problem - thank you

freehassan
New Member

Posts: 11

7.5 Golf R ACC Misadjusted Nov 28, 2024 0:44:43 GMT via mobile

Quote

Post by freehassan on Nov 28, 2024 0:44:43 GMT

Nov 27, 2024 22:29:19 GMT dv52 (Australia) said:

Nov 26, 2024 23:24:22 GMT freehassan said:

I have full scans in my history, it was definitely on the 11th of February 2022 at 9am. ................... I must've scanned it some time when I got home. It would have been parked up with ignition on likely. I feel as if some wiring somewhere is damaged but have no idea how to find out where.

I assume "it" means the date/time of the first SCAN after the alarm/immobilizer was installed.

" It would have been parked up with ignition on likely". Hmmm...... I'm not sure why a Professional workshop would leave a car with ignition-ON overnight because of the battery drain that it causes. But you might be correct because the Freeze frame data field for some of the errors that are reported on the SCAN @ 01:52hrs says:

Supply voltage, terminal 30: 10.7V.
Terminal 15:ON

Terminal 15:ON=ignition-ON

Terminal 30 = permanent battery volts

However, even if you are correct - it's still very odd that these errors happened at 01:52 hrs! How does a C110300 - Adaptive cruise control sensor misadjusted error happen when the car was just sitting stationary in the workshop with no driver - even with ignition-ON and engine-OFF ?

Plus, if the battery rail voltage on this car was 10.7V @ 01:52 hrs on the morning of the day that you picked-up the car - it would have been very low indeed when you actually started the engine when you arrived at the workshop, presumably 6-7 hours later!!

Nov 26, 2024 23:24:22 GMT freehassan said:

If you show me how to get the full data I will provide it.............. I feel as if some wiring somewhere is damaged but have no idea how to find out where.

Yes, the B115496 - CCS Switch Internal malfunction error on the Gateway module could be a physical problem with either the wiring, or the switch(es)

But again, the same question arises - how does this error happen on a car that is not being driven and has no driver? If Pandora damaged the wiring, we would reasonably both expect the time-stamp for the error would be during working hours!!

The way to digitize the History file is using the procedure below. However, because this problem has a long history - please don't bombard me with a huge data-dump of information (it's been done before and it's not helpful!). Review the SCANs yourself and pick-out just the two that are immediately before the alarm fitment and the first time that the errors appear.

AND - please don't dump the contents of the files directly into a post - instead use the attachment facility to append the file itself to the post. The procedure is below (the first screenshot is the History screen):

Nov 26, 2024 23:24:22 GMT freehassan said:

I've taken the badge off and confirmed the sensor is snapped in place. If I manually go into EOL mode and set the misalignment and vertical (can't remember the name of the values) to 0.0. The front assist error disappears and I can clear it, it doesn't show on mib, but still get ACC error and the databus errors remain.

Hmm.........OK, new information!

Because the operation of the front radar is a safety issue for the car occupants, I never play with the calibration settings on the A5 module. But I doubt that just manually setting the horizontal/vertical alignment readings to zero is a kosher way of calibrating the type 1 radar on a Golf mk7. The manufacturer's procedure for calibration is not trivial and it involves a sophisticated target - like the unit below.

Regardless of how these errors were originally created and by whom - this may be the reason why at least the C110300 - Adaptive cruise control sensor misadjusted error persists

Hi bud. Thank you again very much for all your help. I didn't explain that very well sorry. As far as I can remember (plus the date in my booking email) it was 11th Feb 22. My scan of before would've been prior to that either the day I bought the car or the day after. The scan at 01:52 was my own scan, I was there from 9am till about 6pm call it 7 due to the hour drive home. The late scan was probably me finding time to actually scan it.

My brother actually found the whole ordeal very odd which is why I scanned it in the first place. We originally thought they took the bumper off to fit their own horns and had broken the bracket for the ACC sensor, they then explained they don't remove the bumper so we assumed a car had rolled into it. We recently checked the grill and the sensor is in place perfectly.

The reason we thought this is that the turbo on the car failed shortly after the alarm, the garage I took to replace the turbo said they thought the bracket was snapped. They also raised concerns about the battery being weak but the car was stood for 2 weeks due to the turbo being broken. Regardless of that I replaced and coded the new battery to the car (faults were already here before that)

I now think there is a damaged wire somewhere, or a connector left unplugged. I have no idea where as they installed the alarm behind closed doors. My hunch is somewhere by the anti theft system as that is the only module with no communication showing.

I'm going to add this as I just realised what you meant about the Freeze frame. I have no idea, maybe the time in the car was incorrect but we were there between 9-6 and it happened somewhere in there.

I will follow those instructions and attach the files in the next post, I don't see the option on mobile.

freehassan New Member Posts: 11	7.5 Golf R ACC Misadjusted Nov 28, 2024 0:54:28 GMT Quote Select Post Deselect Post Link to Post Back to Top Post by freehassan on Nov 28, 2024 0:54:28 GMT I cannot see a button to upload the txt files, maybe as a new user I do not have access yet, I have added them to GDrive. drive.google.com/drive/folders/1jMYAmdHpH2J3yzN_rmXpMq2bMkxMIKwz?usp=sharing

freehassan
New Member

Posts: 11

7.5 Golf R ACC Misadjusted Nov 28, 2024 1:04:44 GMT via mobile

Quote

Post by freehassan on Nov 28, 2024 1:04:44 GMT

Just to add one more thing sorry.

I rebooked with them to view the car. I was there for a few hours, where they removed the alarm, run tests and then re fit the alarm.

They said that with and without the alarm the faults were apparent, this is where they explained that they do not remove the bumper from the vehicle. They attempted to shift the blame onto the garage who replaced the turbo, but the faults were there before the turbo was replaced. They offered to find CCTV footage and also claimed a tech had damaged the seats on a brand new M5 competition and that they had replaced them because they take liability for things like this.

Alas no CCTV footage was sent, and after me calling up multiple times and being told that they were waiting for the specialist from London to book a time to see the car, I gave up on asking them.

I'm just trying to ascertain if the fault was caused by them, if it's a simple fix that I can do myself I am happy to do it, otherwise I will take it to a specialist, get it fixed and bill the alarm company. If they refuse to pay it, I will take them to small claims court.

Last Edit: Nov 28, 2024 1:05:21 GMT by freehassan: Misspelled bumper

freehassan New Member Posts: 11	7.5 Golf R ACC Misadjusted Nov 28, 2024 1:18:09 GMT via mobile Quote Select Post Deselect Post Link to Post Back to Top Post by freehassan on Nov 28, 2024 1:18:09 GMT I also dug this up from their reviews. Seems I'm not the only one with wiring faults Pandora Car Alarms & immobilisers g.co/kgs/AXxVxnr

dv52 (Australia)
Moderator

Posts: 6,089

7.5 Golf R ACC Misadjusted Nov 28, 2024 10:50:57 GMT

Quote

Post by dv52 (Australia) on Nov 28, 2024 10:50:57 GMT

freehassan : Again, more truncated SCAN reports! Both of the SCANs in your last post have had their headers deleted

This is an example of a header from an OBD11 SCAN:

-------------------------------------------------------------------

OBDeleven vehicle history log
Date: 2024-09-03 16:27:16

VIN: 3VW6T7AU6MM016425
Car: Volkswagen
Year: 2021
Body type: D5 Hatchback
Engine: DKFA kW ( hp) l
Mileage: 18656 km
----------------------------------------------------------------------------

Notice that the header tells you when the SCAN was made - plus it identifies the car. Both of these bits of data are important when trying to analyze this problem. With the header missing from ALL of your SCANs in ALL your previous posts, how is it possible to understand when the SCANs were made?

PLUS - this car apparently contains 22 x modules (it says so in your latest SCANs). However:

Beforeinstall.txt shows just 18 x modules and the crucial 13 ACC Module is missing - so the status of this module before the alarm install is unknown
Afterinstall,txt shows 20 modules.

I say again- it is simply NOT helpful if you continue to provide only part of a FULL SCAN! So, once more I ask - please, please please do NOT make ANY amendments (meaning ZERO changes) to the SCAN reports - and I shouldn't need to add that it's important that a FULL SCAN report showing ALL modules is included in your posts!!

Don

Last Edit: Nov 28, 2024 10:54:45 GMT by dv52 (Australia)

Please don't ask questions about car coding/repair via the forum "Message" function. The better place for such dialogue is in the forum proper. That way, the wider expertise of the entire forum community can be applied to solve your problem - thank you

freehassan
New Member

Posts: 11

7.5 Golf R ACC Misadjusted Nov 28, 2024 18:31:44 GMT via mobile

Quote

Post by freehassan on Nov 28, 2024 18:31:44 GMT

Nov 28, 2024 10:50:57 GMT dv52 (Australia) said:

freehassan : Again, more truncated SCAN reports! Both of the SCANs in your last post have had their headers deleted

This is an example of a header from an OBD11 SCAN:

-------------------------------------------------------------------

OBDeleven vehicle history log
Date: 2024-09-03 16:27:16

VIN: 3VW6T7AU6MM016425
Car: Volkswagen
Year: 2021
Body type: D5 Hatchback
Engine: DKFA kW ( hp) l
Mileage: 18656 km
----------------------------------------------------------------------------

Notice that the header tells you when the SCAN was made - plus it identifies the car. Both of these bits of data are important when trying to analyze this problem. With the header missing from ALL of your SCANs in ALL your previous posts, how is it possible to understand when the SCANs were made?

PLUS - this car apparently contains 22 x modules (it says so in your latest SCANs). However:

Beforeinstall.txt shows just 18 x modules and the crucial 13 ACC Module is missing - so the status of this module before the alarm install is unknown
Afterinstall,txt shows 20 modules.

I say again- it is simply NOT helpful if you continue to provide only part of a FULL SCAN! So, once more I ask - please, please please do NOT make ANY amendments (meaning ZERO changes) to the SCAN reports - and I shouldn't need to add that it's important that a FULL SCAN report showing ALL modules is included in your posts!!

Don

Hi Don,

Sorry about that. I followed the instructions, you said to not bombard with too much information so I just looked for the ones with the dates I wanted and copied the full scans. It exported a file as history.txt and not obdeleven_log. I apologise for that, I have gone and individually gone on both scans and exported them, they are now in the Google drive folder named BeforeFull and AfterFull. I have also included the complete full scan history for the whole car.

dv52 (Australia)
Moderator

Posts: 6,089

7.5 Golf R ACC Misadjusted Nov 28, 2024 21:47:48 GMT

Quote

Post by dv52 (Australia) on Nov 28, 2024 21:47:48 GMT

hmm......... it's a very long stretch of logic to maintain that the ACC module on this car has been error free before the alarm was fitted!

The full history file that you posted confirms that the only SCAN that reports NO errors on the ACC module happened on 2022-02-08 11:52.

But on the very next SCAN, which has the date/time stamp 2022-02-11 18:36 (so 3 x days later) - the ACC module reports 4 x error-codes. Unfortunately the error-codes are "unknown" - but their presence in the SCAN suggests "unknown" problems with the module

PLUS and importantly, every SCAN in the 2 x year period reports a string of errors on the ACC module on this car!!

As for C110300 - Adaptive cruise control sensor misadjusted error - your history file is different to the data that you have provided in your earlier posts. In your History file there are 2 x SCANs with the C110300 error dated as follows:

Date: 2024-11-26 18:59 (Mileage: 106373 km)
Date: 2024-11-26 18:51 (Mileage: 106373 km)

In both these SCANs, the date that the C110300 error was first registered in the module fault memory is 2024-11-26 17:42:18 (Mileage: 106366 km)

Again, in ALL SCANs before and after 2024-11-26, the C110300 error does NOT appear - but "unknown" errors persist! It's possible that the C110300 error has morphed into one of these other errors - I'm guessing!!

This has been a long, strange thread - I am unable to make any further comments on this matter!!

Don

Please don't ask questions about car coding/repair via the forum "Message" function. The better place for such dialogue is in the forum proper. That way, the wider expertise of the entire forum community can be applied to solve your problem - thank you

freehassan
New Member

Posts: 11

7.5 Golf R ACC Misadjusted Nov 29, 2024 1:15:56 GMT via mobile

Quote

Post by freehassan on Nov 29, 2024 1:15:56 GMT

Nov 28, 2024 21:47:48 GMT dv52 (Australia) said:

hmm......... it's a very long stretch of logic to maintain that the ACC module on this car has been error free before the alarm was fitted!

The full history file that you posted confirms that the only SCAN that reports NO errors on the ACC module happened on 2022-02-08 11:52.

But on the very next SCAN, which has the date/time stamp 2022-02-11 18:36 (so 3 x days later) - the ACC module reports 4 x error-codes. Unfortunately the error-codes are "unknown" - but their presence in the SCAN suggests "unknown" problems with the module

PLUS and importantly, every SCAN in the 2 x year period reports a string of errors on the ACC module on this car!!

As for C110300 - Adaptive cruise control sensor misadjusted error - your history file is different to the data that you have provided in your earlier posts. In your History file there are 2 x SCANs with the C110300 error dated as follows:

Date: 2024-11-26 18:59 (Mileage: 106373 km)
Date: 2024-11-26 18:51 (Mileage: 106373 km)

In both these SCANs, the date that the C110300 error was first registered in the module fault memory is 2024-11-26 17:42:18 (Mileage: 106366 km)

Again, in ALL SCANs before and after 2024-11-26, the C110300 error does NOT appear - but "unknown" errors persist! It's possible that the C110300 error has morphed into one of these other errors - I'm guessing!!

This has been a long, strange thread - I am unable to make any further comments on this matter!!

Don

Aww thanks anyways Don. I will take it in to some specialists and let them examine. I'll update this thread with findings though it's unlikely someone else will have this problem.