Recent Posts

Pages: 1 2 3 [4] 5 6 ... 10
31
OBDwiz/TouchScan / Re: OBD Wiz Pro issue with reports
« Last post by mjo151 on September 01, 2015, 06:10:07 PM »
Hello,

Can you email your license information to service@obdsoftware.net so that I can take a look?

Regards,
Matt
32
OBDwiz/TouchScan / Fuel System Status
« Last post by vol96 on September 01, 2015, 05:39:45 PM »
Why does Fuel System Status SAE 0x03 appear on my PID Setup screen but not on Data Logging screen?

33
Developer Forum / Re: All commands ignored for all KWP protocols for ECUSIM 5100
« Last post by STN-Brian on September 01, 2015, 04:45:27 PM »
You are close, try this:

SR
EDA
EA 3
EP 3, 4 //you can set this directly for kwp
EAP 3, hh //set your physical header for kwp
EAF 3, hh //set your functional header for kwp
E 3, 1
PA 3, 01, 00 07 6D 00
SP 4

Also you may choose to turn off DTC and MIL auto updating with:
PAUDC 3, off
PAUMS 3, off

Let me know if you still get the wrong response.
34
ScanTool.net Software / Re: Windows 8.1 ?
« Last post by Alonzo Canales on September 01, 2015, 04:32:21 PM »
I apologize that the auto detect is not working for you. Please find what com port that Windows has assigned and try to connect to that one.
35
Developer Forum / Re: STCSEGT1 and SPTX Returning a ? - OBDLink MX
« Last post by STN-Brian on September 01, 2015, 04:25:10 PM »
I would try updating your firmware.  The OBDLink app has that functionality built in.  Please post the results of the STDIX command.
36
OBDLink LX / Re: Connection Failure on 2004 Acura TL
« Last post by Alonzo Canales on September 01, 2015, 04:20:22 PM »
Make sure the Communication type is set to 'Bluetooth'
1. Go to 'Settings' on the OBDLink app.
2. Then go to 'Communications'
3. 'Communication Type' and select 'Bluetooth'

Also, make sure that the 'Bluetooth Device' is set to 'OBDLink LX '
1. Go to 'Settings' on the OBDLink app.
2. Then go to 'Communications'
3. 'Bluetooth Device' and select 'OBDLink LX'

This should fix the issue.
37
Unfortunately, I have the same registration failure for me.
38
OBDLink LX / Re: Connection Failure on 2004 Acura TL
« Last post by AzJazz on September 01, 2015, 04:08:31 PM »
Hi, Alonzo - The car was purchased in the United States. I am using the OBDLink Android App.

I tried it on two different devices: My Android phone and my Android tablet.

AzJazz
39
OBDLink App / Re: Custom PID's not working for Ford C-Max Hybrid (2013)
« Last post by Chris Fincher on September 01, 2015, 03:39:22 PM »
Generally, Torque and OBDLink have you enter the data in a very similar way.  They differ on the address though.  Whatever address you are using for Torque, subtract 8 from it and use that instead if you want to put it in the OBDLink app.  7EC would then be 7E4, 7E8 would be 7E0, and 7EE would be 7E6.

I'm not sure if the OBDLink app supports signed numbers or how to do it if it does but I will ask the developer to find out.

Regards,
Chris
40
OBDLink / Re: Can the OBDLink LX prevent a Check Engine Light?
« Last post by Chris Fincher on September 01, 2015, 03:24:02 PM »
There have been reports that the LX or MX have caused the check engine light to come on due to a brief error in communication, but no one have ever stated it prevented a code from registering.  You can clear your codes and turn off the check engine light with a tool and still have the problem but until the problem is fixed, it won't stay off.

Regards,
Chris
Pages: 1 2 3 [4] 5 6 ... 10