Free OBD2 Software anyone? (No Longer Free)

**malcom2073** · 01-24-2009, 09:37 AM

Hey, just a suggestion. If you use portmon: http://technet.microsoft.com/en-us/s.../bb896644.aspx you can see the serial port traffic. Maybe this will give you a clue what the elmscan software is doing that mjo151's software is not.

**mjo151** · 01-24-2009, 11:04 AM

Not sure if I'll time today, but I think Scantool is open source so I'll take a look and see what they're sending to the device on connect. It's possible that what I'm sending is only compatible with the obdpro scantool.

**Vitaliy** · 01-25-2009, 02:35 AM

Originally Posted by mjo151

Not sure if I'll time today, but I think Scantool is open source so I'll take a look and see what they're sending to the device on connect. It's possible that what I'm sending is only compatible with the obdpro scantool.

It is indeed open source. ScanTool.net doesn't do anything special. On startup, it resets the chip (ATZ), turns off echo and linefeeds, sets the protocol to automatic, and waits for the ECU to time out. Somewhere in between, it asks for the chip version and manufacturer.

One thing I noticed is that your software did not issue the ATZ command to reset the chip. IMHO, it's a good idea to do that, it gives you reasonable assurance that you are starting with a more or less standard setup.

Best regards,

Vitaliy

**drewbp** · 01-25-2009, 10:08 PM

Have you embedded this into Ride Runner yet. If so I would love to know your window name for the embed.

Thanks.

Edit: Figured it Out.

**mjo151** · 01-25-2009, 10:38 PM

OK so I should be getting an ElmScan 5 to test from the good guys at scantool.net. I'll update when I have something new to try.

**drewbp** · 01-27-2009, 02:11 PM

I have an obdpros connector and have never been able to get it to connect to this program. I use dashcommand which sometimes takes 2 tries to connect, the first I guess does a reset, and then times out before reconnecting but always connects by the second try.

I also use the obdpros scantool, and have only been able to get it to connect when I physically disconnect the usb connection. If I use dashcommand at all, I cannot get it to reconnect.

However, I have never been able to get your program to connect. I will keep trying, but do you have any suggestions, or can I help you in any way to debug.

**michbound** · 01-27-2009, 02:47 PM

I suspect it might be the baud rate setting that the program defaults did you ensure that the speed was set to 9600 on the setup screen?

of course mjo151 might have additional suggestions...

Thanks
Paul
www.obdpros.com

**mjo151** · 01-27-2009, 06:59 PM

As michbound suggested, I would first verify that you are using the correct com port and baud rate. If you have these set correctly, then the following will help me debug exactly what is going on:

1) Try to connect to the device
2) Goto the Device Traffic tab on the Diag page
3) Send me a screen shot of the output (sorry the save button apparently doesn't work correctly)

Please note that you'll need the second install that I posted in order to get debug output on the Diag page.

**drewbp** · 01-29-2009, 12:31 AM

Okay so I set the program to 9600 and it connected. My question is then why the other speed settings. My OBDPro connector is set at 38400, so how can I get it to connect at the faster speeds.

Also, the overall MPG seems to be accurate, but the instantaneous seems very eratic, sometimes going up over 50MPG. It starts at 19 or 20 MPG and then slowly climbs to up and over 50MPG.