Announcement

Collapse
No announcement yet.

OBDII connectivity

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

  • OBDII connectivity

    Evening guys.

    I finally got my ODB2 cables through from scantool.net. Im connecting using the serial connector using the ELM323 ISO connector to my renaultsport megane (2004)



    Anyways...... I am using com 1 and am able to connect to the ECU to get readings when not using CF. When i replicate the settings within CF i am unable to connect to the ECU. If you see the attached image you will see the interfaces which the scantool is able to connect to the vehicle.

    Interface: ELM323
    Protocol: ISO 9131-2 / ISO 1423-4 (KWP2000)
    OBD System: EOBD (Europe)

    I was using RC4 to connect to the vehicle. I am in the process up upgradign to RC 4.4 to see if this makes any difference.

    Any assistance/tips would be greatfully appreciated as i really like the graphical interface and intergration to the whole incar pc package and dont want to have to use a tacky looking external application.

    Thanks,
    Alex
    Attached Files

  • #2
    I have the same problem... any solution found for this allready?

    Greetz

    Dj NRG

    Comment


    • #3
      I am using the Cobb Accessport via a serial-to-usb connector and it does not work. Not sure what to do.

      Comment


      • #4
        Originally posted by f1anatic View Post
        I am using the Cobb Accessport via a serial-to-usb connector and it does not work. Not sure what to do.
        It continues to be an ongoing issue. It's been reported again and David says he's going to look into it.
        :: Mark

        Comment


        • #5
          Originally posted by midiwall View Post
          It continues to be an ongoing issue. It's been reported again and David says he's going to look into it.
          I have never used this cable, but I do have an older ELM327 and an ElmScan 5... I have hooked it up to five cars now, completly different models, and I have no connection issues with RC5, or previous versions...

          The data polling could be a little faster, but it works...

          I'm hoping to get an error.log from someone or something because if I can't get it to break, it makes it hard to fix

          david
          __________________
          CENTRAFUSE http://www.centrafuse.com
          01 Jeep Cherokee Sport 4x4 Installed
          M10000/512Mb/20GB, Lilliput 7", Holux GM-210

          Comment


          • #6
            If you keep clicking connect/disconnect button text area does it ever connect?

            please check for an error.log file in your installation directory to help me see why it is not connecting, it works fine with the simulators and multiple cars and with multiple devices on my end...

            Are you using USB-Serial adapter? Maybe that has something to do with it... I have used one, but only the Belkin... It has lights, if the one you have does, is it sending/receiving data?

            david
            __________________
            CENTRAFUSE http://www.centrafuse.com
            01 Jeep Cherokee Sport 4x4 Installed
            M10000/512Mb/20GB, Lilliput 7", Holux GM-210

            Comment


            • #7
              Originally posted by veetid View Post
              I have never used this cable, but I do have an older ELM327 and an ElmScan 5... I have hooked it up to five cars now, completly different models, and I have no connection issues with RC5, or previous versions...

              I'm hoping to get an error.log from someone or something because if I can't get it to break, it makes it hard to fix
              Understood. But it's rarely worked for me, and there's never been anything in the error.log


              If you keep clicking connect/disconnect button text area does it ever connect?
              Once in maybe 50 times, but after doing so it will lose the connection after 1-2 minutes.


              Are you using USB-Serial adapter?
              I am, but it's embedded in the unit. This is what's in my truck:
              http://www.obd2allinone.com/sc/details.asp?item=obd2usb

              Regardless of this possibly being an issue, 100% of the time I can exit out of CF, load {insert freebie OBD II app here} and it will connect immediately.

              If I had to guess, by the connection issues and the way the indicator lamps on this unit look, it feels like there's something in CF fighting for the COM port. I've gotten the best results in connection attempts right after juggling the COM port for the OBD interface. Start on 3, move to 5, then to 8, then to 4... Somewhere in there I can usually get CF to connect - but like I said above, it'll drop the connection fairly soon.
              :: Mark

              Comment


              • #8
                Originally posted by midiwall View Post
                Understood. But it's rarely worked for me, and there's never been anything in the error.log


                Once in maybe 50 times, but after doing so it will lose the connection after 1-2 minutes.


                I am, but it's embedded in the unit. This is what's in my truck:
                http://www.obd2allinone.com/sc/details.asp?item=obd2usb

                Regardless of this possibly being an issue, 100% of the time I can exit out of CF, load {insert freebie OBD II app here} and it will connect immediately.

                If I had to guess, by the connection issues and the way the indicator lamps on this unit look, it feels like there's something in CF fighting for the COM port. I've gotten the best results in connection attempts right after juggling the COM port for the OBD interface. Start on 3, move to 5, then to 8, then to 4... Somewhere in there I can usually get CF to connect - but like I said above, it'll drop the connection fairly soon.
                strange... I will track it down, but I don't have much to go on...

                I use Belkin USB-Serial adapters and serial ElmScan5 devices from scantool.net and everything works perfect... I get a dropped connection every once in awhile, but it usually connects right back up...

                I will look into it and try to figure something out, see if I spot something in the code... Maybe create a debug version that writes everything I get back from the serial port and everything I send to the error.log for users to run to get me debug information...

                david
                __________________
                CENTRAFUSE http://www.centrafuse.com
                01 Jeep Cherokee Sport 4x4 Installed
                M10000/512Mb/20GB, Lilliput 7", Holux GM-210

                Comment


                • #9
                  Originally posted by veetid View Post
                  Maybe create a debug version that writes everything I get back from the serial port and everything I send to the error.log for users to run to get me debug information...
                  That would be great.

                  fwiw, I'm still out of my truck for probably another 2 weeks.
                  :: Mark

                  Comment


                  • #10
                    Thanks. I use this Cobb Accessport cable

                    which I use for my data logging. I was using it thru a serial-to-usb connector but it should be fine since it worked for the data logger application. So my converter does its job. I wonder if the Cobb Accessport does not use some of the proprietary Subaru technology since it allows access via the software to all the sensors on that car.

                    I do not get any errors; it just says"connecting" and never does. I waited about 2 min at most - I find that plenty of time for something to connect. Even dial-up is faster :-)

                    What fail-safe cables are out there for Subaru folks ? Tactrix ? with which people report the same issues of no connectivity ?

                    Comment


                    • #11
                      yeah, obd worked great in either rc3 or rc4.x, but now i cant get it to work at all. i tried pressing the connect button maybe 3 times then gave up.

                      ill search for a error log if i get a chance.

                      Comment


                      • #12
                        Originally posted by tibby01 View Post
                        yeah, obd worked great in either rc3 or rc4.x, but now i cant get it to work at all. i tried pressing the connect button maybe 3 times then gave up.
                        I think I last saw it work somewhat reliably around Beta 1.6, maybe 1.7.
                        :: Mark

                        Comment


                        • #13
                          I also use this cable.
                          mine connects in CF, but does not show any data, allthough the data leds are flashing...
                          I also will look into my error.log file tomorrow..

                          Greetz

                          Dj NRG

                          Comment


                          • #14
                            Originally posted by Dj-[NRG] View Post
                            I also use this cable.
                            mine connects in CF, but does not show any data, allthough the data leds are flashing...
                            Make sure you have the baud rate set right in CF. The OBD2AllInOne defaults to 9600 but can be set internally to 38400. If the baud rate in CF doesn't match the device, then you could get symptoms like you're seeing.
                            :: Mark

                            Comment


                            • #15
                              i thought i allready played with the baud rate...
                              will check again tomorrow...
                              didn't have the chance to check my error log file today, hopefully i will get to that tomorrow...

                              Greetz

                              Dj NRG

                              Comment

                              Working...
                              X