Above Forum Ad

Collapse

Announcement

Collapse
No announcement yet.

OBDII Reader ELM327

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

  • OBDII Reader ELM327

    Hey guys,

    Just purchased a $35 OBDII reader for my 2002 GTI Golf and im using the Torque Pro app for android via bluetooth and its failing to find the ECU i also noticed the reader was a little tight to plug into the OBD port. Is this normal for these golfs? Do they not have a true OBD port / is it not readable?

    Little confused why it wouldnt just work, if anyone else has gotten theres to work please tell me how!

  • #2
    Do you have an aftermarket radio?

    If so, unplug it and try again.
    '07 Transporter 1.9 TDI
    '01 Beetle 2.0

    Comment


    • #3
      Originally posted by Umai Naa!! View Post
      Do you have an aftermarket radio?

      If so, unplug it and try again.
      As in stereo radio? No mate its still the genuine CD player

      Comment


      • #4
        I also have an OBDii ELM27 connected to torque pro on my Samsung galaxy S7. It works on my XTrail but does not on my new Tiguan.

        I looked at the the 2 units that support VW and ended up biting the bullet and got the Ross -Tech VCDS HEXNET v2 usb.

        This is the most expensive but it gives you the most number of options and modifying the ECU is basically select from the drop list rather than entering long strings of code with the chance of a typo stuffing everything up.

        Sent from my SM-G930F using Tapatalk
        Ordered: 2017 build date Tiguan 162 TSI Highline with DAP in Tungsten Silver and rear luggage tray. ETA: late April / Early May. I did not have to wait. I took delivery on 11 March 2017.

        Comment


        • #5
          Originally posted by Delewin View Post
          I also have an OBDii ELM27 connected to torque pro on my Samsung galaxy S7. It works on my XTrail but does not on my new Tiguan.

          I looked at the the 2 units that support VW and ended up biting the bullet and got the Ross -Tech VCDS HEXNET v2 usb.

          This is the most expensive but it gives you the most number of options and modifying the ECU is basically select from the drop list rather than entering long strings of code with the chance of a typo stuffing everything up.

          Sent from my SM-G930F using Tapatalk
          Thanks for that mate, thats a little extreme for what i want to use it for.
          I just want to scan codes and watch some fancy gauges its a bummer its not working. I'm going to try some software on my laptop this afternoon and see if that works to eliminate my phone being an issue.

          Comment


          • #6
            Originally posted by Stocky789 View Post
            Hey guys,

            Just purchased a $35 OBDII reader for my 2002 GTI Golf and im using the Torque Pro app for android via bluetooth and its failing to find the ECU i also noticed the reader was a little tight to plug into the OBD port. Is this normal for these golfs? Do they not have a true OBD port / is it not readable?

            Little confused why it wouldnt just work, if anyone else has gotten theres to work please tell me how!
            I have a similar setup on my MK5 GTI and it all works perfectly, there might be something wrong with the obd2 device if it doesn't detect your ecu. I use a unit like below which is wifi not Bluetooth.

            Comment


            • #7
              Originally posted by adey88 View Post
              I have a similar setup on my MK5 GTI and it all works perfectly, there might be something wrong with the obd2 device if it doesn't detect your ecu. I use a unit like below which is wifi not Bluetooth.

              https://www.ebay.com.au/itm/231177929373
              Yeh thanks mate I'll buy that one and see how it goes. I have a strange feeling there bluetooth driver issued with my phone. It connects to the OBD reader but on all the apps i try it always fails to find a protocol to read the ECU. Any possibility this car isnt OBD compatible?

              Comment


              • #8
                I'm no expert but why would it have an odb2 port if it wasn't?

                At $30 or whatever the adaptor costs it's a small risk to take especially if myself and others have got it working. I don't see why the mk6/7 would be that different.

                Good luck either way

                Comment


                • #9
                  Originally posted by Stocky789 View Post
                  Hey guys,

                  Just purchased a $35 OBDII reader for my 2002 GTI Golf and im using the Torque Pro app for android via bluetooth and its failing to find the ECU i also noticed the reader was a little tight to plug into the OBD port. Is this normal for these golfs? Do they not have a true OBD port / is it not readable?

                  Little confused why it wouldnt just work, if anyone else has gotten theres to work please tell me how!
                  Do you have the key turned to on?

                  Comment


                  • #10
                    6789 is the key code that came with mine.
                    Good luck.

                    Sent from my SM-G930F using Tapatalk
                    Ordered: 2017 build date Tiguan 162 TSI Highline with DAP in Tungsten Silver and rear luggage tray. ETA: late April / Early May. I did not have to wait. I took delivery on 11 March 2017.

                    Comment


                    • #11
                      Originally posted by HaydEn View Post
                      Do you have the key turned to on?
                      Yeh mate tried it with ignition and motor running. I'll try it out on another vehicle tomorrow that i know for sure works with OBD2 devices, I have ordered a WiFi one anyway since that's what I see most people using. But any reason why it was tight to get on? Its like the plug was slightly a different shape.

                      Comment


                      • #12
                        Alright blokes so i purchased another OBD2 reader this time a WiFi one and again still no ECU connection, powers up and connects to OBD reader and begins to search for a protocol but fails
                        One thing i did notice is pin 16 on my OBD port has no power, but if this is the case why does my OBD device still power up?
                        Also is it possible that even though my radio is genuine that it could still be stuffing this up?

                        Comment


                        • #13
                          Do you have a early mk4?
                          If so need a mk3 suited reader.

                          Comment


                          • #14
                            Originally posted by HaydEn View Post
                            Do you have a early mk4?
                            If so need a mk3 suited reader.
                            I've got an 02 model? Does this count as an early model or?
                            Do you know why I wouldn't have power to pin 16 and is this the supply of power to the OBD reader usually or something else? Little confused why my unit is still powering up even though pin 16 has no voltage on it and have been told by numerous people now to check that pin for power.

                            Comment


                            • #15
                              No idea on the pin issue.

                              Mates handheld reader works on his mk3 and another mates early 4mo bora, but does not work on the R32.

                              Comment

                              Working...
                              X