Announcement

Collapse
No announcement yet.

ELMScan 5 - USB on Subaru Forester.

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

  • ELMScan 5 - USB on Subaru Forester.

    Got an ELMSCAN05 USB version(ELM327 inside) from tunertools. Do i need any trick to know to connect this to my car? My forester is 1998 version and it is OBD2 compliant. Checked
    Cable plug into the car, then turn key in ON position, start engine, etc..
    i have tried all softwares i got and the power LED is red not green, but red. When i start a software (OBD Diag for example) the power led turns green on the interface, but still dont get it connected even though both protocol leds (PC and CAR) flashes like is tring to send/rec data)
    BTW, i have tried all possible COM settings, and yes, the driver were corectly installed and appear in the device manager exactly as it supposed to be.
    And i have checked also the car plug and it is ok, no broken cables or such.

    I am asking here because i try to understand if it is any "test" plug like on imprezza(green plug connector) that needs to be pluged before i connect the OBD interface.

    many thanks for any help.

    Mugur
    My second Subaru skin
    Full screenshots second skin
    My car photos

    CarPC Progress
    ■■■■■■■ - 75%

  • #2
    Liberty B4 '92

    Hmmm. I seem to have a similar problem on my B4. I'm using elm327-usb interface and my LED's seem to behave in the same way, except for changing of power LED. Used Proscan and Digimoto however the best result was that I had live data for Coolant and Air intake temp, nothing else.
    When I looked at the log, there seems to be no response to any other codes.

    I'm starting to think that I may have a fault interface but can't tell for sure since it's new and I never used it successfully.
    May give it a go on another car to eliminate at least one factor in this puzzle.

    As to the ports and communication problem I would check you ports again especially if you are using a bluetooth dongle. I have one and if I try to map my usb port to com3 (which is used by bt serial) I can't get it to talk through obd2 software. This is after making sure that port numbers have been manually remapped to avoid any conflicts. Try to set a higher port that has not been used before for anything else.

    Anyways, if there is someone out there that knows the solution to our issues it would be great.

    Comment


    • #3
      Sorry, I forgot to mention that my software tells me that I'm connected just no data seems to be received. Also LEDs on the usb side of the interface flash both on Rx and Tx but on the RS232 side I only get Tx flashing.

      Comment


      • #4
        here are some news.

        Here are my OBD pins:


        And here is a short movie (800k size) that shows what happen when i try to connect. The power led stays RED until ANY soft calls the interface on the corect COM (in this movie is PCMSCAN) , in wich case turns instantly green and stays green untill you close the software.

        http://images-team.ro/carpc/elm327.avi


        My hyperterminal log is this:

        >
        atz


        ELM327 v1.1

        >0100
        SEARCHING...
        UNABLE TO CONNECT

        >0101
        SEARCHING...
        UNABLE TO CONNECT


        >ath0
        OK
        My second Subaru skin
        Full screenshots second skin
        My car photos

        CarPC Progress
        ■■■■■■■ - 75%

        Comment


        • #5
          That will not be such a big deal...at least i want to know what i should do next.
          Tomorrow my ELMScan will meet a Touareg and a Touran, both made in 2006 for european market.
          My second Subaru skin
          Full screenshots second skin
          My car photos

          CarPC Progress
          ■■■■■■■ - 75%

          Comment


          • #6


            It did'nt.
            The result is identical with the one i get from my car...
            My second Subaru skin
            Full screenshots second skin
            My car photos

            CarPC Progress
            ■■■■■■■ - 75%

            Comment


            • #7
              Originally posted by mugurg View Post
              Here are my OBD pins:
              The car is not OBDII compliant. None of the pins present in the connector correspond to an OBDII communication bus. For more information, see Which OBD-II protocol is supported by my vehicle?

              [snip]

              My hyperterminal log is this:

              >
              atz


              ELM327 v1.1

              >0100
              SEARCHING...
              UNABLE TO CONNECT

              >0101
              SEARCHING...
              UNABLE TO CONNECT


              >ath0
              OK
              As expected, the scan tool was unable to connect.
              OBDLink MX: world's smallest, fastest, most advanced OBD/Bluetooth adapter with SW and MS CAN support. Read the review to learn more.
              Need to look up a diagnostic trouble code? Try the most up-to-date, free DTCsearch.com!

              You cannot send me a private message using this forum. Use my email instead: vitaliy[@]scantool.net.

              Comment


              • #8
                Originally posted by mugurg View Post
                Got an ELMSCAN05 USB version(ELM327 inside) from tunertools. Do i need any trick to know to connect this to my car? My forester is 1998 version and it is OBD2 compliant. Checked
                Cable plug into the car, then turn key in ON position, start engine, etc..
                i have tried all softwares i got and the power LED is red not green, but red. When i start a software (OBD Diag for example) the power led turns green on the interface, but still dont get it connected even though both protocol leds (PC and CAR) flashes like is tring to send/rec data)
                BTW, i have tried all possible COM settings, and yes, the driver were corectly installed and appear in the device manager exactly as it supposed to be.
                And i have checked also the car plug and it is ok, no broken cables or such.

                I am asking here because i try to understand if it is any "test" plug like on imprezza(green plug connector) that needs to be pluged before i connect the OBD interface.

                many thanks for any help.

                Mugur
                The "Power" LED in the new version of ElmScan 5 USB has three states:

                1. Red = OBD power is on
                2. Yellow = USB cable plugged in
                3. Green = Virtual COM port is open

                OBD Diag doesn't sound like a program that is compatible with ElmScan 5. I would suggest trying a different software package, unfortunately it's not going to help you as your car is not OBDII compliant (see my previous post).

                Best regards,

                Vitaliy
                OBDLink MX: world's smallest, fastest, most advanced OBD/Bluetooth adapter with SW and MS CAN support. Read the review to learn more.
                Need to look up a diagnostic trouble code? Try the most up-to-date, free DTCsearch.com!

                You cannot send me a private message using this forum. Use my email instead: vitaliy[@]scantool.net.

                Comment


                • #9
                  Originally posted by apiniuta View Post
                  Hmmm. I seem to have a similar problem on my B4. I'm using elm327-usb interface and my LED's seem to behave in the same way, except for changing of power LED. Used Proscan and Digimoto however the best result was that I had live data for Coolant and Air intake temp, nothing else.
                  When I looked at the log, there seems to be no response to any other codes.

                  I'm starting to think that I may have a fault interface but can't tell for sure since it's new and I never used it successfully.
                  May give it a go on another car to eliminate at least one factor in this puzzle.
                  If you are getting correct Coolant and Air Temp values, there's nothing wrong with the interface. The interface simply translates requests from RS232 to OBD and back. Inability to get other parameters would point to a non-OBDII compliant ECU.

                  Best regards,

                  Vitaliy
                  OBDLink MX: world's smallest, fastest, most advanced OBD/Bluetooth adapter with SW and MS CAN support. Read the review to learn more.
                  Need to look up a diagnostic trouble code? Try the most up-to-date, free DTCsearch.com!

                  You cannot send me a private message using this forum. Use my email instead: vitaliy[@]scantool.net.

                  Comment


                  • #10
                    Vitaliy, the new LED explains a lot from my ELM behavior, but the car is definitely OBD2, i am not saying so, the Subaru staff does based on the vechicle ID. The problem is: seems that someone moved the pins to 12-13 and i have no idea why. Maybe to reach the pins of an obscurous cable interface...no idea, but this is a potential reason according to Subaru staff.
                    I bought the car as a used car, so this is a dark area for me. Anyone can take the pins out and move them to another location in the plug. Even i can...
                    I don't held anyone responsible for my experience! I will do my best to get it work, or if not, it will be just another experience, as many others i had. Still learning...
                    My second Subaru skin
                    Full screenshots second skin
                    My car photos

                    CarPC Progress
                    ■■■■■■■ - 75%

                    Comment


                    • #11
                      mugur, vvmaks seems right! As we know that pins 12 & 13 are for SSM and not OBD-II, we can see that the ones you are left with do not comply with OBD-II.......these are just power and ground?

                      It sounds like your Subaru dealer does not know much!

                      Comment


                      • #12
                        sad but true..in the end i will figure it out a way to solve this...
                        My second Subaru skin
                        Full screenshots second skin
                        My car photos

                        CarPC Progress
                        ■■■■■■■ - 75%

                        Comment

                        Working...
                        X