Forums
Forums
Notifications
Clear all
Torque main forum
4
Posts
2
Users
0
Reactions
950
Views
Topic starter
Hello
If you have a PLX Kiwi Bluetooth unit and are having difficulty connecting to your vehicles ECU, could you please use the 'Send comms debug logs' menu option in the 'Realtime information' screen as I am interested in getting extra debugs for this particular OBD2 adapter.
The particular symptom I am interested in is where the adapter manages to connect, displays information in (for example) the RPM screen, then as soon as you go into the 'realtime information' screen or add a widget, stops receiving data and goes into a reconnection loop. This does not look like a problem with Torque, but I need extra debugs to confirm it.
Also, if you have a kiwi adapter, and have let the app try to connect to the ECU for a short time (about a minute) please check the "Adapter Error Count" item in the "Adapter status" activity. If it is above 0, then there is a high probability that you have a faulty adapter
Thanks
Ian
Posted : 20/04/2011 8:50 pm
Ian,
I see various problems connecting to my Kiwi bluetooth adapter, but the error count is always 0, and once connected, it stays connected solid with no data loss. So my problems seem to be different from these that you are currently trying to track down.
In my case, when Torque is started, it sometimes enters a Searching for adapter loop; or a Checking proto loop; or says that bluetooth on my phone is not enabled, although I have Torque configured to enable it when it starts; or prompts me to enter the "1234" code though I have entered it previously. It does one or more of those about half the time; the other half of the time Torque connects to the adapter quickly, with no problem. And as I said, once connected, it has always stayed connected until I power down.
I could send you logs if you think this is related to other problems you are seeing with Kiwi.
--Paul
Posted : 28/04/2011 4:31 am
Topic starter
That sounds like your phone may have bad bluetooth drivers. Is it running an original manufacturers firmware, and what model of phone is it? Usually in these cases a reboot of the phone clears the problem.
Posted : 28/04/2011 6:43 am
It's a Samsung SCH-I500. The bluetooth drivers are stock, but I'm running a modified kernel.
Restarting Torque once or twice always manages to get it connected; it's just somewhat annoying if I'm in a hurry :).
--Paul
Posted : 30/04/2011 5:06 am
