Quote: Originally Posted by
michbound 
What vehicle are you running this on?
When you connect via serial cable you should be connecting to COM1. COM7 is what the bluetooth software driver installed but over the serial cable it should be com1 or the first hardware com port....
Paul
www.obdpros.com
Michbound, thank you for your kind reply.
I am running this on a 2002 Pontiac Grand Prix an OBD II compliant vehicle. The protocol is SAE J1850 VPW, which is supported by the multi-protocl ElmScan 5 as you probably know.
In terms of the COM ports.
On my car PC i was never able to get far, since my PC just shut down and didnt turn back on as soon as I connected ElmScan to the serial port. While on bluetooth I used COM7.
I did bring out my laptop and tried to use the serial connection there, I got further than on my car PC. I still got the "No Interface Found" message in the ScanTool.net FreeWare App. However I was able to get some sort of response out of it from the HyperTerminal.
If i put in "ATZ" I got a response of "OK" back. I forgot the other commands, so I was trying to put random stuff in, which it ignored. I noticed however if I put in something like "ATGDGERWEG" I get an "ERROR" back. It looks like its reading the first 2 bytes as the command and then the rest as an input. I need to go back out and with the right commands and try it again.
I am a software engineer, if there is a documentation for all of the "commands" that the ElmScan interface takes, I will write my own scan tool for all I care. Essentially all I want is to be able to communicate with my OBDII port.
The problem is I wanted to integrated it with my StreetDeck, and obviously it is not finding an interface on the correct port. If my custom scan tool works then I will have to then write a custom AddIn for StreetDeck..but I am getting ahead of myself.
Let me go out there with my laptop and with the proper commands and see what it tells me, I will report back here with the results..if you guys still care or not.
Stan.