Sign up for our newsletter! 
Home News Products Downloads Forum Distributors Store Contact Us
PPE User Forum
December 15, 2017, 06:12:25 pm *
Welcome, Guest. Please login or register.

Login with username, password and session length
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Faild to open OBD -II connection, Error 104  (Read 5844 times)
0 Members and 1 Guest are viewing this topic.
Adeeb
Newbie
*
Offline Offline

Posts: 4


View Profile
« on: February 25, 2010, 07:51:49 pm »

Hello all:

I am new to ScanXL world, any Advice, hellp , telling me from where I have to start. it seems to be I missed some information.

what I did so far:
-installing the software.
-register my license.
-try to connect to my car but I received an error 104, 109. what that mean?
-do I have to do any setup to my PC and software?

*My cars, Isuzu Rodeo 1998 , SUV. and  the second is Hyundai Elentra 2010.
 
* the interface is OBD-II
* windowa Vista>

and I recieve this error 104. what that mea?

[22:29:03.936] License applied successfully!
[22:29:03.936] Loading OBD-II Parameter Set...
[22:29:04.108] Loading PID scripts...
[22:29:04.113] Loaded 14 PID scripts.
[22:35:28.286] Loading PID scripts...
[22:35:28.306] Loaded 14 PID scripts.
[22:36:09.713] Loading PID scripts...
[22:36:09.735] Loaded 13 PID scripts.
[22:36:46.606] Loading PID scripts...
[22:36:46.608] Loaded 5 PID scripts.
[22:38:12.887] Opening OBD-II Connection...
[22:38:25.846] Failed to open OBD-II connection! Error 104: Error detecting OBD-II protocol.


Thanks.
« Last Edit: March 04, 2010, 05:19:45 pm by Adeeb » Logged
Weston@PPE
Administrator
Hero Member
*****
Offline Offline

Posts: 2234


View Profile
« Reply #1 on: February 27, 2010, 12:59:00 pm »

Can you send me a tech log of this? That will let me look into the problem.

To get a tech log, go to the Help menu > Debug Options, and set Debug Level 9. Then try to connect. After the connection fails, go back to Debug Options and select Save Tech Log. You can attach it to your next post or send it to support@palmerperformance.com.
Logged
Adeeb
Newbie
*
Offline Offline

Posts: 4


View Profile
« Reply #2 on: March 05, 2010, 12:10:19 am »


it workes after I changed the OBD-II setting : Interface to Auto , and baud rate to 38400.

but how long I should keep recording the parametr's data to be full reading and logged ?

Thanks,
Logged
Pierre@PPE
Full Member
***
Offline Offline

Posts: 129


View Profile
« Reply #3 on: March 15, 2010, 01:52:21 pm »

Adeeb,

The amount of time to record a log is up to you. If the PID you are logging don't change much then you don't need to record very long. On the other hand if the PID changes a lot depending on engine speed or other parameters then you may want to record it for a longer period so you can see a pattern.

I also depends on what you are trying to do. If you provide me with more information I may be able to help you better.

Regards,
Pierre.
Logged
billyrb1
Newbie
*
Offline Offline

Posts: 1


View Profile
« Reply #4 on: May 24, 2014, 04:30:51 pm »

I also had the same problem when using my ELM327 interface.  Does this connector cable need to be swapped as well?  I emailed my debug file to the email address listed above, please help as I can't use my software to figure out what's wrong with my truck until this is resolved.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.13 | SMF © 2006-2011, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
Page created in 0.043 seconds with 20 queries.
Home | News | Products | Downloads | Forum | Distributors | Store | Contact Us
Copyright © 2013 Palmer Performance Engineering, Inc. All Rights Reserved.