Forums
Forums
Notifications
Clear all
Topic starter
I have the Scantool OBDLink and it connects but once i go into Fault Codes on my Nexus One the light for Rx on the scan tool stops flicking and the revs no longer move to match the car revs like it is frozen and the scan for error codes only ever gets to 30% as at this point i suspect the freeze starts, is this linked to the bluetooth driver issue as it works with my laptop sw. Would appreciate any support and can provide any logs or suggestions. Have the most recent version of Torque installed.
What i tried:
I clicked the check box for hang fix under general preferences and i disabled ELM327 auto timing under settings. I have set it up to use alternate header in vehicle preferences.
Posted : 03/08/2011 11:07 pm
Hi
You probably don't want the 'alternate header' ticked in the settings - this is for older vehicle (around 1999) that require special headers to work.
How are you reading RPM in the fault code activity, as there's no dial for it?
Can you reproduce the fault, then(without quitting) go to the 'realtime information' screen and hit menu->more...->'send debugging info' and I'll have a look to see what's going on
Ian
Posted : 04/08/2011 7:04 am
Topic starter
Debug log sent it is a 99 car so most likely need the alternate header as it communicates okay it just freezes when i go into the fault code reader. Sent with my Forum ID as an identifier in the description of the debug log. Thanks would be great to get this working for my phone.
Was reading the revs from one of the dials it remains at its last rev number after i come out of the fault code section ie frozen and no rx light on obdlink scan tool.
Posted : 04/08/2011 7:00 pm
Hi
Got the debug, thanks!
A couple of things I noticed from it:
* You have 'Faster communication' ticked (which is okay), but also 'Disable ELM327 auto timing adjust' as well (these two don't work well together - untick the 'Disable ELM327 auto timing adjust' (you don't want it ticked, and unticking it will improve read speeds a lot)
* Your adapter crashed when the fault codes were requested - this is a problem with the OBDLink itself - you may need to contact their support as I've seen this happen a couple of times with adapters running firmware v2.2.2 (debug pasted below at the end of the post)
Untick the setting, and try again - it should work fine - raise the issue with Scantool.net's support and they should be able to help on this (how warm was the unit when it happened? if it was very hot (ie: in sunlight) then it could cause instabilty
(a bit from the debug which their support should be able to help you with if you send it to them)
Adapter: SCANTOOL.NET LLC
Adapter Version: STN1100 v2.2.2, identifying as: ELM327 v1.3a
Adapter: J1850 PWM(41.6K)
1312484044571 {-- 03
1312484044648 --} 020000
1312484044653 --} +020000
1312484044723 --} +020000
1312484044725 --} +020000
1312484044775 --} +020000
1312484044801 --} +020000
1312484044827 --} +020000
1312484044877 --} +020000
1312484044903 --} +020000
1312484044930 --} +020000
1312484044956 --} +020000
1312484045006 --} +020000
1312484045033 --} +020000
1312484045082 --} +020000
1312484045108 --} +020000
1312484045134 --} +020000
1312484045160 --} +020000
1312484045213 --} +020000
1312484045241 --} +020000
1312484045291 --} +020000
1312484045298 --} +020000
1312484045343 --} +020000
1312484045369 --} +020000
1312484045396 --} +020000
1312484045445 --} +020000
1312484045471 --} +020000
1312484045498 --} +020000
(and so on as the adapter is stuck in a loop)
Posted : 04/08/2011 7:34 pm
