 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Car Forum / Driving, Maintenance, Tuning / Maintenance and Repair / February 2007OBD-2.com system not connecting
Hello all - I cannot connect, on 2 different computers, and on 2 different cars (2001 Land Rover DiscoII, Lexus LS400 1996). I get an alternating BUSY and TERMINATE button on a window with red captions saying its trying to connect ("Scanning all interfaces. Initialization is taking place"). After 30 seconds it says "Failure to successfullly find a OBD-2 interface." I get the exact same thing if I disconnect the cables completely. Here is the network connection log. Can you tell me what I am doing wrong? Or do I just have a bad connector or cable? Thanks! Dean Brown Network connect log file follows: Sat 03 Feb 2007 version 1.47 00:40:16.3 - initializing serial port 00:40:16.3 - connected rs232 port 1 00:40:16.3 - Initializing vehicle using Blue Router 00:40:16.8 - router F6 rs232 57600 00:40:16.8 - route F2 00:40:16.8 - Log In #1 SAE J1850 VPW @ 120 00:40:17.4 - timeout 3 mode= $01 00:40:17.4 - no response 00:40:17.4 - route F3 00:40:17.4 - Login #1 ISO 9141-2 @ 120 10 25 00:40:17.4 - Login #1 ISO/DIS KWP2000-4 slow @ 120 10 25 00:40:20.0 - Sync=55 W1=63 00:40:20.0 - Key1=08 W2=9 00:40:20.0 - Key2=08 W3=9 00:40:20.0 - Addr=33 W4=39 00:40:21.7 - timeout 3 mode= $01 00:40:21.7 - no response 00:40:22.8 - no response ping loop back 00:40:24.0 - no response ping loop back 00:40:25.2 - no response ping loop back 00:40:25.3 - timeout 3 mode= $01 00:40:25.3 - no response 00:40:25.3 - Login #1 ISO/DIS KWP2000-4 fast @ 120 10 25 00:40:26.7 - no response ping loop back 00:40:27.9 - no response ping loop back 00:40:29.0 - no response ping loop back 00:40:29.1 - timeout 3 mode= $81 00:40:29.1 - no response 00:40:31.2 - router F6 rs232 57600 00:40:31.4 - Log In #2 SAE J1850 VPW @ 120 00:40:32.1 - timeout 3 mode= $01 00:40:32.1 - no response 00:40:32.3 - Login #2 ISO 9141-2 @ 120 10 25 00:40:32.3 - Login #2 ISO/DIS KWP2000-4 slow @ 120 10 25 00:40:35.4 - no response 00:40:35.7 - Login #2 ISO/DIS KWP2000-4 fast @ 120 10 25 00:40:39.5 - timeout 3 mode= $81 00:40:39.5 - no response 00:40:42.2 - Log In #3 SAE J1850 VPW @ 120 00:40:42.2 - under len=01 00:40:42.8 - timeout 3 mode= $01 00:40:42.8 - no response 00:40:42.8 - Login #3 ISO 9141-2 @ 120 10 25 00:40:42.8 - Login #3 ISO/DIS KWP2000-4 slow @ 120 10 25 00:40:45.9 - no response 00:40:45.9 - Login #3 ISO/DIS KWP2000-4 fast @ 120 10 25 00:40:49.8 - timeout 3 mode= $81 00:40:49.8 - no response 00:40:52.5 - Log In #4 SAE J1850 VPW @ 120 00:40:52.5 - under len=01 00:40:53.1 - timeout 3 mode= $01 00:40:53.1 - no response 00:40:53.1 - Login #4 ISO 9141-2 @ 120 10 25 00:40:53.1 - Login #4 ISO/DIS KWP2000-4 slow @ 120 10 25 00:40:56.3 - no response 00:40:56.3 - Login #4 ISO/DIS KWP2000-4 fast @ 120 10 25 00:41:00.1 - timeout 3 mode= $81 00:41:00.1 - no response 00:41:02.7 - router F6 rs232 57600 00:41:02.7 - route F2 00:41:02.7 - Log In #5 SAE J1850 VPW @ 120 00:41:03.4 - timeout 3 mode= $01 00:41:03.4 - no response 00:41:03.4 - route F3 00:41:03.4 - Login #5 ISO 9141-2 @ 120 10 25 00:41:03.4 - Login #5 ISO/DIS KWP2000-4 slow @ 120 10 25 00:41:05.9 - Sync=55 W1=65 00:41:05.9 - Key1=08 W2=10 00:41:05.9 - Key2=08 W3=10 00:41:05.9 - Addr=33 W4=39 00:41:07.6 - timeout 3 mode= $01 00:41:07.6 - no response 00:41:08.7 - no response ping loop back 00:41:09.9 - no response ping loop back 00:41:11.1 - no response ping loop back 00:41:11.2 - timeout 3 mode= $01 00:41:11.2 - no response 00:41:11.2 - Login #5 ISO/DIS KWP2000-4 fast @ 120 10 25 00:41:12.6 - no response ping loop back 00:41:14.7 - no response ping loop back 00:41:15.8 - no response ping loop back 00:41:15.9 - timeout 3 mode= $81 00:41:15.9 - no response 00:41:42.5 - saved 0 messages 2 KB to : C:\OBDSCA~1\NOCONNLR manufacturer files: Core Not Defined none > Hello all - > [quoted text clipped - 5 lines] > OBD-2 interface." I get the exact same thing if I disconnect the > cables completely. I seriously doubt that anyone here will be able to troubleshoot your Car Code scan software from a logfile. Have you tried contacting Alex Peper via email? He writes in fairly cohesive English (I believe he is Russian born but am not sure) and is very knowledgeable about the software as he is the creator. Toyota MDT in MO > > Hello all - > [quoted text clipped - 13 lines] > > Toyota MDT in MO Yes I have sent Alex the log file. Did you have to set anything up before you got a connection? I noticed there is a baud-rate setting in XP for the COM1 port, plus a bunch of other parameters. I tried adjusting the baud rate to match the code reader software, but to no avail. -Dean > > > Hello all - > [quoted text clipped - 20 lines] > other parameters. I tried adjusting the baud rate to match the code > reader software, but to no avail. Sorry, I don't use Car Code. I am affiliated with the same professional network as Alex and have communicated with him before. He impresses me with his knowledge so I'm guessing that he would be the best one to help you here. Other than that option, there are a number of programmers that also are car hobbyists; I have seen posts from these types in various more vehicle-specific forums where they discuss the nuts and bolts of serial communication and the protocols used in OBDII diagnostics. Perhaps a search outside of R.A.T. would be of more help to you. Toyota MDT in MO The first thing that he has to do is review the option menu and read the help section for information on correct setup. He will also find the com port setup and needs to select the correct com port. >> > > Hello all - >> [quoted text clipped - 32 lines] > > Toyota MDT in MO > The first thing that he has to do is review the option menu and read the > help section for information on correct setup. He will also find the com [quoted text clipped - 38 lines] > > - Show quoted text - Hey Woody - I have confirmed that it is set up on port 1. Did you have to change the com port baud rate? By default in XP it was set to 9200, although that is not one of the options in the OBD program. All I can find in the help is what cars need what interfaces, although it seems to search using all interfaces anyway, that's what it says when its first trying to connect. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.