Sign up for our newsletter! 
Home News Products Downloads Forum Distributors Store Contact Us
PPE User Forum
December 14, 2017, 04:54:02 am *
Welcome, Guest. Please login or register.

Login with username, password and session length
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Error 109, then 100/101...  (Read 1914 times)
0 Members and 1 Guest are viewing this topic.
avig70
Newbie
*
Offline Offline

Posts: 2


View Profile
« on: September 13, 2015, 04:37:24 am »

Looking into purchasing ScanXL so I installed and tried to connect to the car.
Mazda Protege5, 2.0L, 2002. Using OBDLink MX Bluetooth. 2014 Macbook Pro Retina with Win10.
I connected everything, Paired the laptop with the Bluetooth adapter.

Tried to connect to the car and I got Error 109 (OBD-II interface not found). So I got into the connection parameters in ScanXL and changed the Baud Rate to 9600 and changed the COM Port from AUTO to COM6 and got Error 101 (Interface communication failure). When I pointed it to COM7 I got Error 100 (Failed to open data port).

When using the app from my Android device, everything works properly.

Any Thoughts?


* ScanXL Errors.jpg (358.04 KB, 1064x1077 - viewed 288 times.)

* Device manager.jpg (183.51 KB, 822x1140 - viewed 301 times.)
Logged
Andy@PPE
Administrator
Hero Member
*****
Offline Offline

Posts: I am a geek!!


View Profile
« Reply #1 on: September 14, 2015, 04:50:48 pm »

I have responded to your support ticket, please check your email.  Grin Grin
Logged
avig70
Newbie
*
Offline Offline

Posts: 2


View Profile
« Reply #2 on: September 16, 2015, 12:35:49 pm »

Dear Andy,
Thank you for the reply by mail and here.

As I said on my first post, everything is paired correctly.

After installing OBDWiz and verifying the same error exists, I contacted scantool support as well. Their answer was that there is a bug in windows 10 that doesn't let the software communicate with OBDLink MX. So I borrowed a friend's laptop with Windows 7, he also has the Mazda add on and the pro version, it seems to work properly.

Now it scan's for available PID's and shows the data as I think it should.

The OBD standard shows as EOBD.

One thing I don't see is the air bag data available despite me seeing the relevant info on the supported PID's list. Could it be that Protege5 doesn't let me scan for air bag errors? could it be that the only info available for my car's air bag system is by counting the flashes of the air bag light in the dash?

Is there a way to speed thing up? Getting the baud rate higher then 115,200?
Is there a manual for ScanXL other then the "Getting started" manual that installs with ScanXL?
« Last Edit: September 16, 2015, 12:43:20 pm by avig70 » 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.047 seconds with 20 queries.
Home | News | Products | Downloads | Forum | Distributors | Store | Contact Us
Copyright © 2013 Palmer Performance Engineering, Inc. All Rights Reserved.