Above Forum Ad

Collapse

Announcement

Collapse
No announcement yet.

Number of Faults on Start Up

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Number of Faults on Start Up

    Hey folks. Twice in the past 2 months after the car has been sat all day at work (8hrs) on start up all these faults pop up and gradually they all go away as I start to drive off. They look like communication errors so I’m thinking my battery is on its way out. It’s never happened in a morning in the garage but only after work. Car seems to start fine with no hint of a struggle but the last time it went there was no warning. I remember my mk6 GTI through lots of faults when it was about to go but not this R. Any other thoughts would be greatly appreciated or should I be looking for a new battery sooner rather than later?

    Cheers

    OBDeleven data log

    Date: 2020-07-08 10:30

    VIN: WVWZZZAUZFW075389
    Car: Volkswagen Golf R
    Year: 2015
    Body type: 5-dr hatchback
    Engine: CJXB 206 kW (280 HP) 2.0 l
    Mileage: 151043 KM

    ---------------------------------------------------------------
    76 Parking Assistance

    System description: PARKHILFE 8K
    Software number: 5Q0919294E
    Software version: 0048
    Hardware number: 5Q0919294A
    Hardware version: H03
    Serial number: 39331420700621
    ODX name: EV_EPHVA18AU3700000
    ODX version: 002024
    Long coding: 0071151001

    Trouble codes:
    U112300 - Databus error value received
    Intermittent


    OBDeleven data log

    Date: 2020-07-08 10:24

    VIN: WVWZZZAUZFW075389
    Car: Volkswagen Golf R
    Year: 2015
    Body type: 5-dr hatchback
    Engine: CJXB 206 kW (280 HP) 2.0 l
    Mileage: 151043 KM

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

    System description: 2.0l R4 TFSI
    Software number: 5G0906259E
    Software version: 0003
    Hardware number: 06K907425B
    Hardware version: H13
    ODX name: EV_ECM20TFS0205G0906259E
    ODX version: 001003
    Long coding: 091900322446050B3000

    Trouble codes:
    U112300 - Databus error value received
    Intermittent


    OBDeleven data log

    Date: 2020-07-08 10:23

    VIN: WVWZZZAUZFW075389
    Car: Volkswagen Golf R
    Year: 2015
    Body type: 5-dr hatchback
    Engine: CJXB 206 kW (280 HP) 2.0 l
    Mileage: 151043 KM

    ---------------------------------------------------------------
    03 Brakes

    System description: ESC
    Software number: 5Q0907379CK
    Software version: 0472
    Hardware number: 5Q0907379G
    Hardware version: H31
    Serial number: 62024000001320
    ODX name: EV_Brake1UDSContiMK100IPB
    ODX version: 033001
    Long coding: 01FA93A154272971037A070841CC6980C92A94C0E08296F7F4 4050B8C008

    Trouble codes:
    B1168F2 - Steering angle sensor no initialization
    Intermittent
    C114602 - Tire pressure monitoring display Signal error
    Intermittent


    OBDeleven data log

    Date: 2020-07-08 10:19

    VIN: WVWZZZAUZFW075389
    Car: Volkswagen Golf R
    Year: 2015
    Body type: 5-dr hatchback
    Engine: CJXB 206 kW (280 HP) 2.0 l
    Mileage: 151043 KM

    ---------------------------------------------------------------
    15 Airbag

    System description: AirbagVW20
    Software number: 5Q0959655AA
    Software version: 0386
    Hardware number: 5Q0959655AA
    Hardware version: 014
    Serial number: 003MLR07KVHJ
    ODX name: EV_AirbaVW20SMEVW37X
    ODX version: 002130
    Long coding: 98CCC000000000005C00000000C800000065

    Subsystems:
    System description: BeltPretRevFL
    Software version: 0341
    Hardware version: H35
    Serial number: 34169677B31071441382
    Long coding: 333135

    System description: BeltPretRevFR
    Software version: 0341
    Hardware version: H35
    Serial number: 34169676B30071471086
    Long coding: 333135

    System description: SideSensor_Df
    Software version: 0887
    Hardware version: 001
    Serial number: 3576700000057838A01R
    Long coding: 2D2D2D

    System description: SideSensor_Pf
    Software version: 0887
    Hardware version: 001
    Serial number: 358670000007CB8C6010
    Long coding: 2D2D2D

    System description: SideSensor_Dr
    Software version: 6149
    Hardware version: 001
    Serial number: 35165029916DB80431CD
    Long coding: 2D2D2D

    System description: SideSensor_Pr
    Software version: 6149
    Hardware version: 001
    Serial number: 3526502B51656B92B07B
    Long coding: 2D2D2D

    System description: FrontSensor_D
    Software version: 6149
    Hardware version: 001
    Serial number: 3556502C516DB80592EQ
    Long coding: 2D2D2D

    Trouble codes:
    U112300 - Databus error value received
    Intermittent
    Date: 2020-06-18 15:56:10
    Mileage: 149701 km
    Priority: 6
    Malfunction frequency counter: 1
    Unlearning counter: 200


    OBDeleven data log

    Date: 2020-07-08 10:17

    VIN: WVWZZZAUZFW075389
    Car: Volkswagen Golf R
    Year: 2015
    Body type: 5-dr hatchback
    Engine: CJXB 206 kW (280 HP) 2.0 l
    Mileage: 151043 KM

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

    System description: ACC Bosch MQB
    Software number: 5Q0907572D
    Software version: 0304
    Hardware number: 5Q0907572D
    Hardware version: H05
    Serial number: 31071476510988
    ODX name: EV_ACCMRRBoschVW372
    ODX version: 001015
    Long coding: 00000300FE0739

    Trouble codes:
    U112300 - Databus error value received
    Intermittent
    Date: 2020-06-18 15:56:08
    Mileage: 149701 km
    Priority: 6
    Malfunction frequency counter: 1
    Unlearning counter: 200
    U112300 - Databus error value received
    Intermittent
    Date: 2020-06-18 15:56:08
    Mileage: 149701 km
    Priority: 6
    Malfunction frequency counter: 1
    Unlearning counter: 200
    U112300 - Databus error value received
    Intermittent
    Date: 2020-06-18 15:56:10
    Mileage: 149701 km
    Priority: 6
    Malfunction frequency counter: 1
    Unlearning counter: 200
    B10E7F0 - Cruise Control Front Distance Range Sensor separated
    Intermittent
    Date: 2020-06-18 15:56:08
    Mileage: 149701 km
    Priority: 6
    Malfunction frequency counter: 1
    Unlearning counter: 201


    OBDeleven data log

    Date: 2020-07-08 10:16

    VIN: WVWZZZAUZFW075389
    Car: Volkswagen Golf R
    Year: 2015
    Body type: 5-dr hatchback
    Engine: CJXB 206 kW (280 HP) 2.0 l
    Mileage: 151043 KM

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

    System description: ACC Bosch MQB
    Software number: 5Q0907572D
    Software version: 0304
    Hardware number: 5Q0907572D
    Hardware version: H05
    Serial number: 31071476510988
    ODX name: EV_ACCMRRBoschVW372
    ODX version: 001015
    Long coding: 00000300FE0739

    Trouble codes:
    U112300 - Databus error value received
    Intermittent
    Date: 2020-06-18 15:56:08
    Mileage: 149701 km
    Priority: 6
    Malfunction frequency counter: 1
    Unlearning counter: 200
    U112300 - Databus error value received
    Intermittent
    Date: 2020-06-18 15:56:08
    Mileage: 149701 km
    Priority: 6
    Malfunction frequency counter: 1
    Unlearning counter: 200
    U112300 - Databus error value received
    Intermittent
    Date: 2020-06-18 15:56:10
    Mileage: 149701 km
    Priority: 6
    Malfunction frequency counter: 1
    Unlearning counter: 200
    B10E7F0 - Cruise Control Front Distance Range Sensor separated
    Intermittent
    Date: 2020-06-18 15:56:08
    Mileage: 149701 km
    Priority: 6
    Malfunction frequency counter: 1
    Unlearning counter: 201


    Sent from my iPhone using Tapatalk
    2015 Golf R. Lapiz Blue.

  • #2
    Looks like typical voltage weirdisms to me.

    If you have a decent battery charger it might be worth seeing if the battery can be recovered, but in reality they are a consumable item in this world of stop/start systems. 5 years isn't too bad though.
    Cheers

    Comment


    • #3
      Had the same in a Passat Battery for sure

      When the OBDEleven connects to the car what is the battery voltage and is the icon green, orange or red.
      2021 Kamiq LE 110 , Moon White, BV cameras F & B
      Mamba Ebike to replace Tiguan

      Comment


      • #4
        Time for a new battery. 5 years and 150,000km is very good going from the original battery. Here is a suitable replacement to suit the Mk7 R: Buy Delkor LN370EFB (DIN65LH) 12V 720cca Automotive Battery | Delkor AGM Batteries
        2017 Ford Fiesta ST the go kart

        2015 Audi SQ5 bi-turbo V6 TDI family hauler

        Comment


        • #5
          Originally posted by Hillbilly View Post
          Had the same in a Passat Battery for sure

          When the OBDEleven connects to the car what is the battery voltage and is the icon green, orange or red.
          Thanks for that, battery colour is orange.


          Sent from my iPhone using Tapatalk
          2015 Golf R. Lapiz Blue.

          Comment


          • #6
            Originally posted by Lucas_R View Post
            Time for a new battery. 5 years and 150,000km is very good going from the original battery. Here is a suitable replacement to suit the Mk7 R: Buy Delkor LN370EFB (DIN65LH) 12V 720cca Automotive Battery | Delkor AGM Batteries
            This is my second battery. 1st one went about 3 years ago and got it replaced under warranty. Thanks again for advice. I had a feeling it was going to be the battery just wanted to confirm. On my obdeleven the battery voltage is 12.6 and that’s after a drive.


            Sent from my iPhone using Tapatalk
            2015 Golf R. Lapiz Blue.

            Comment


            • #7
              Originally posted by Reedy View Post
              This is my second battery. 1st one went about 3 years ago and got it replaced under warranty. Thanks again for advice. I had a feeling it was going to be the battery just wanted to confirm. On my obdeleven the battery voltage is 12.6 and that’s after a drive.


              Sent from my iPhone using Tapatalk
              Lots of Mk7 Golf batteries (and other VW's of the same era) died prematurely - im guessing whoever makes their batteries (Varta?) had a bad batch or something. Either that or the demands of the stop/start system killed them quickly.
              2017 Ford Fiesta ST the go kart

              2015 Audi SQ5 bi-turbo V6 TDI family hauler

              Comment


              • #8
                Originally posted by Reedy View Post
                This is my second battery. 1st one went about 3 years ago and got it replaced under warranty. Thanks again for advice. I had a feeling it was going to be the battery just wanted to confirm. On my obdeleven the battery voltage is 12.6 and that’s after a drive.


                Sent from my iPhone using Tapatalk
                Yeah it would be but what is it when app connects and is orange bet its about 11.5 or similar
                2021 Kamiq LE 110 , Moon White, BV cameras F & B
                Mamba Ebike to replace Tiguan

                Comment


                • #9
                  Originally posted by Reedy View Post
                  Hey folks. Twice in the past 2 months after the car has been sat all day at work (8hrs) on start up all these faults pop up and gradually they all go away as I start to drive off. They look like communication errors so I’m thinking my battery is on its way out. It’s never happened in a morning in the garage but only after work. Car seems to start fine with no hint of a struggle but the last time it went there was no warning. I remember my mk6 GTI through lots of faults when it was about to go but not this R. Any other thoughts would be greatly appreciated or should I be looking for a new battery sooner rather than later?

                  Cheers
                  Reedy: hi. I apologize in advance for not agreeing with other responses, and your battery may well be approaching the end of its useful life - but I very much doubt that the DTCs in your scan report were caused by this problem.

                  The principal reason for my doubt is that your scan report is full of what I call "aged errors" and more particularly because of the single date stamp that permeates ALL DTC records.

                  The odd thing about the DTCs on your scan report and the reason why they are "aged errors" is the date/time, itself and the fact that the Malfunction frequency counter= 1. This combination means that ALL faults in the scan were first recorded on the CAN network in the car on a single day/time and the faults have NOT been re-recorded on any subsequent ignition cycle up to the time that you made the scan report

                  So - what happened to the car on Thursday the 18th June 2020 @ a little before 4PM? According to the hex13 module, someone appears to have detached the front facing radar (this is the hex13 module) from the car! It appears from my reading of your scan report that this act has resulted in the loss of the steering angle reference calibration from the Brake module as well as the generation of a number of Database anomalies in multiple modules. Please advise


                  I might well be wrong (I often am), but this simply doesn't look like a battery problem to me!

                  Don
                  Last edited by DV52; 09-07-2020, 11:08 AM.
                  Please don't PM to ask questions about coding, or vehicle repairs. The better place to deal with these matters is in the forum proper. That way you get the benefit of the wider expertise of other forum members! Thank you.

                  Comment


                  • #10
                    Originally posted by DV52 View Post
                    So - what happened to the car on Thursday the 18th June 2020 @ a little before 4PM? According to the hex13 module, someone appears to have detached the front facing radar (this is the hex13 module) from the car! It appears from my reading of your scan report that this act has resulted in the loss of the steering angle reference calibration from the Brake module as well as the generation of a number of Database anomalies in multiple modules. Please advise


                    I might well be wrong (I often am), but this simply doesn't look like a battery problem to me!

                    Don
                    Looking at the scan in more detail your point is justified mate.
                    2017 Ford Fiesta ST the go kart

                    2015 Audi SQ5 bi-turbo V6 TDI family hauler

                    Comment


                    • #11
                      On this date and time my car had been sat all day at work from 7.30 to 4.00 approx. All I did is return to the car unlock it, get in and start it. That’s when all the se faults came up and as I drive off they go away one by one except the front radar, I have to turn the car off and then back on for this to work properly. They are aged as I’ve only just got round to clearing them yesterday and it’s not happened since that date.


                      Sent from my iPhone using Tapatalk
                      2015 Golf R. Lapiz Blue.

                      Comment


                      • #12
                        Thanks for the feedback by the way. The only other issue that I do have is that when I’m driving the front radar does pop up as a fault and stops working but then within a minute or 2 will just reactivate and start working again.


                        Sent from my iPhone using Tapatalk
                        2015 Golf R. Lapiz Blue.

                        Comment


                        • #13
                          Originally posted by Reedy View Post
                          On this date and time my car had been sat all day at work from 7.30 to 4.00 approx. All I did is return to the car unlock it, get in and start it. That’s when all the se faults came up and as I drive off they go away one by one except the front radar, I have to turn the car off and then back on for this to work properly. They are aged as I’ve only just got round to clearing them yesterday and it’s not happened since that date.

                          Sent from my iPhone using Tapatalk
                          ^^^ ^hmm........ OK. Fact is though that the DTC is quite specific (Cruise Control Front Distance Range Sensor separated). So, either the module is lying, or it really happened through someone else's intervention, or it resulted from a loose wire/connector.

                          But this really doesn't matter for the purposes of the discussion. There were no "low battery volts" errors on your scan report. By all means, change the battery if you want - but do it because of a concern about its age, rather than as a result of a need from a diagnostic scan report!!!

                          Don
                          Please don't PM to ask questions about coding, or vehicle repairs. The better place to deal with these matters is in the forum proper. That way you get the benefit of the wider expertise of other forum members! Thank you.

                          Comment


                          • #14
                            Thanks for that mate. I’ll just let the battery run it’s due cause and carry on. Could the faulty front sensor be causing all the other problems?


                            Sent from my iPhone using Tapatalk
                            2015 Golf R. Lapiz Blue.

                            Comment


                            • #15
                              Originally posted by Reedy View Post
                              Could the faulty front sensor be causing all the other problems?


                              Sent from my iPhone using Tapatalk
                              Difficult to be precise as to whether it's the sensor,itself. But,if the front radar errors keep reappearing intermittently - it strongly suggests that you have a recurring problem either with the module, or with a connector/pin somewhere, or with a section of the wiring loom. If you want to fault-find it yourself, I suggest that you grab a wiring diagram (using the car's VIN) and a multi-meter and trace the circuit wiring (perhaps start with the module earth wires). Please be aware that if you loose the module calibration parameters (by disconnecting wires), you will need to go back to the dealer because the radar calibration needs a special aiming screen

                              Don
                              Last edited by DV52; 10-07-2020, 11:23 AM.
                              Please don't PM to ask questions about coding, or vehicle repairs. The better place to deal with these matters is in the forum proper. That way you get the benefit of the wider expertise of other forum members! Thank you.

                              Comment

                              Working...
                              X