Announcement

Collapse
No announcement yet.

OBDII in Centrafuse and Scantool.net elmscan tool...

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

  • OBDII in Centrafuse and Scantool.net elmscan tool...

    Hey all,

    From some reason, the centrafuse built in OBDII reader does not translate the readouts from the scantool. I can see it communicating since the scantool is transmitting and receiving and the little indicator in centrafuse shows that it is connected... but i get zero readouts. It is an ELM 327 device so that has been set up properly in the settings.

    Any suggestions?

  • #2
    Many people have this issue, David has it on his list of things to deal with.

    As a test, try one of the freebie OBD II apps around and verify that it's not an issue with the reader or cabling... There's a list of apps here:

    http://www.obdpros.com/obd_software.php#free_software
    :: Mark

    Comment


    • #3
      This issues is strange to me because scantool.net devices is what I built the OBDII plugin around...

      I have 3 of them, from the older to the newer elmscan5 and done testing with many cars and many computers...

      I plan to look into it... That and some XM issues are my biggest two things left to track down...

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

      Comment


      • #4
        Originally posted by veetid View Post
        This issues is strange to me because scantool.net devices is what I built the OBDII plugin around...

        I have 3 of them, from the older to the newer elmscan5 and done testing with many cars and many computers...

        I plan to look into it... That and some XM issues are my biggest two things left to track down...

        david
        You know, the more I am tinkering with this, the more I think this is an issue with the scantool itself. I got the bluetooth one that they offer (actually my wonderful girlfriend did for my birthday since she knows my hate for cables). As of now, only my freaking PPC can actually communicate with it properly and only at 9600 BAUD. If I set it to 38400, no dice. When the PC reads it - thats even stranger. Every app I have used communicates with the scantool just fine and dandy right, but after 3-4 seconds, the scantool stops receiving from the car - it would transmit to the car, it would transmit to the computer and receive from the computer, but the orange RX light on the OBD side of the scantool does not blink. As I mentioned earlier - it does work fine with my PPC non stop... and this is totally bugging me...

        Comment


        • #5
          I believe you should have it set at 9600 baud unless you have a CAN bus car...

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

          Comment


          • #6
            Originally posted by veetid View Post
            I believe you should have it set at 9600 baud unless you have a CAN bus car...

            david
            Even at 9600 BAUD it would communicate with the car's OBD system for 3 seconds then stop when the whole unit is connected to the PC; but with my HTC Wizard PPC - all is well...

            Comment


            • #7
              Hey David,

              I think I now know why the scantool and the CF plugin don't wanna communicate after a few seconds. apparenlty it has to do with the cafr OBD system. Some cars, when they get a request for a PID they do not recognize or understand, would drop into standby mode. the scantool would keep transmitting but the cars would be like "wtf? no" and would stop transmitting. if you disable the offending PIDs, the car would be keep transmitting without going to standby mode. Unfortunately, CFs plugin tries each one of the pids and then it hits the "offending" ones and no more readouts. I wouldn't be surprised if I am not the only one that has the same problem. The obvious suggestion for that would be to allow the user to be able to disable PIDs from being queried at all so that it doesn't **** the cars OBD system off.

              Cheers,

              Gene.

              Comment


              • #8
                I will look into allowing you to manually disable PID's...

                The thing is I run a query to the car to get supported PID's and do not request a PID that your car says it does not support...

                It was to fix this exact issue reported in earlier versions...

                I will verify it's working and maybe that is the only issue...

                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
                  The thing is I run a query to the car to get supported PID's and do not request a PID that your car says it does not support...
                  Ummm... if so, then something's broke. I see the OBD module trying to display a number of things that I know I don't support.

                  I have an interface for a Palm that does this query process as well. You're definitely trying to show elements that the Palm doesn't. In specific, Fuel Pressure, Intake Manifold Pressure, PTO Status, Engine Run Time.

                  I always thought you just had static elements, 'cause I don't have a FP sensor, nor a MAP sensor, no PTO element and I know the ECU doesn't expose run time.
                  :: Mark

                  Comment


                  • #10
                    those should just stay at NA if the plugin detected that your car did not support those PID's

                    I will look over the code, but instead of making the user manually disable sensors, I generally try to disable them by the first call after connect is build a list of all supported PID's in a hash, this is a call that I thought all cars supported...

                    maybe some cars don't support the actual call to get the supported pids... didn't think of that...

                    for example in my car it doesn't support multiple items, but they just stay at NA and it never try's to query for them...

                    I could have an error in the code as well or some car again might not support the call to get supported PID's... I will look into it...

                    it's a good place to start for sure.. I can start by making a debug version that just gets speed and if it works for everyone and connects and updates, then I know it's me asking for an un-supported PID causing problems...

                    I have something to start on now, this a good thing!

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

                    Comment


                    • #11
                      Originally posted by veetid View Post
                      I will look into allowing you to manually disable PID's...

                      The thing is I run a query to the car to get supported PID's and do not request a PID that your car says it does not support...

                      It was to fix this exact issue reported in earlier versions...

                      I will verify it's working and maybe that is the only issue...

                      david
                      I am going to have to say that the feature you described is not working properly. As I mentioned before, OBDGauge on my PPC tries to seek every possible PID that is programmed into it from the OBD system - and when the car says "NO", the program does not request it again; seems like CF's plugin keeps asking for them over and over and over again which freaks the car's OBD system out.

                      Comment


                      • #12
                        Originally posted by veetid View Post
                        those should just stay at NA if the plugin detected that your car did not support those PID's

                        I will look over the code, but instead of making the user manually disable sensors, I generally try to disable them by the first call after connect is build a list of all supported PID's in a hash, this is a call that I thought all cars supported...

                        maybe some cars don't support the actual call to get the supported pids... didn't think of that...

                        for example in my car it doesn't support multiple items, but they just stay at NA and it never try's to query for them...

                        I could have an error in the code as well or some car again might not support the call to get supported PID's... I will look into it...

                        it's a good place to start for sure.. I can start by making a debug version that just gets speed and if it works for everyone and connects and updates, then I know it's me asking for an un-supported PID causing problems...

                        I have something to start on now, this a good thing!

                        david

                        Well I can tell you exactly what works for me and what doesnt work for me; also from my experience it seems like the CF plugin tries and contact every PID once, gets an N/A then tries to contact them AGAIN and thats what throws the car off. I can see random readouts, but then it just stops transmitting. If you can perhaps make a debug version with the ability to completely disable a PID - I'd be happy to test it out and let you know the results.

                        Comment


                        • #13
                          bump cuz i really want to get it working ^_^

                          Comment


                          • #14
                            Originally posted by ComradeJew View Post
                            bump cuz i really want to get it working ^_^
                            Easy dude, David's a bit busy, he knows this is here...

                            If you wanna help him out, load this up and pull a trace on the virtual COM port that's being used for the OBD interface. It should tell you exactly what's going on:

                            http://www.serial-port-monitor.com/

                            I was planning to do it this weekend, but a whole mess of "life stuff" came up.
                            :: Mark

                            Comment


                            • #15
                              Originally posted by midiwall View Post
                              Easy dude, David's a bit busy, he knows this is here...

                              If you wanna help him out, load this up and pull a trace on the virtual COM port that's being used for the OBD interface. It should tell you exactly what's going on:

                              http://www.serial-port-monitor.com/

                              I was planning to do it this weekend, but a whole mess of "life stuff" came up.
                              Ahh okay - I'll give it a shot when I have time

                              Comment

                              Working...
                              X