Hi Ian,

I’m having further problems with trying to log data with the “only log while connected to the ECU” ticked. Torque will log and display OBD PIDs for the 1st trip that I take in a car, however if I stop, torque refuses to start logging again, and any of the gauges just freeze at the previous value they were at. I have the most up to date torque version, and am using KBC OBD dongles.

Do you have any idea where the problem might lie, is it in torque, the signal from the ECU, or the bluetooth? I really need torque to be able to log by itself for at least a week, and it will not do this at the minute.

Yep I know about the issue of it cycling through the protocols, which seems to take about 30s/1min on average for my car (2003 civic on ISO protocol), but the issue I am having is separate.

Slightly different topic here, but a suggestion to speed up the reconnection to the ECU would be that torque scans for the previous protocol used firstly? Or maybe have the protocol saved as in the vehicle profile setting?

Ok bit more info on this problem. I let the torque running on a phone yesterday in the car, it was still running when I checked it this morning before I drove off. It attempted to connect with the ECU, but just got stuck on the Can protocol. I left it for 10/15mins to see if it would manage to connect, but it did not so I just restarted torque, and it linked quick enough with my car then. Weather this is an issue with just my car and can, or something else I don’t know.

I was thinking about the other issue of having torque scan through all the protocols once the ECU has disconnected, could you put a setting in the adapter settings that forces torque to one scan for one protocol (for my own car, ISO, I don’t need torque to look for the others). This would speed up the time it takes torque to refind the connect.

Ian, did you have any luck with this? Does anyone else have problems like this.

I am also coming across an issue with the torque app just closing after say 12/18hours of logging, whereas I need the app to be able to reliably record for much longer then this!! What could possibly be causing torque to close, and is there anyway of forcing it to restart if it closes (ie an app in the background that monitors if torque is running, and if its not then restart it).

Yep, I’m on the most up to date version. I tried it again on a different vehicle overnight (an 03 525, running the ISO standard also), and the very same thing happened with this, torque displays all the graphs grand, and logs fine, and then when you turn off the vehicle at a stop etc, it starts to cycle through the protocols, and once it hits CAN it stays trying to connect to CAN, and wont cycle around again to the other protocols. I will have to go out and test this on a non ISO OBD vehicle, if I can get hold of one.

The other issue of where it stops logging after 12/18hrs is generally when torque is not connected to the ECU. I use the torque app to try just the GPS data for vehicles that do not have an OBD port, and in these cases, torque will never really log more then 12/18hrs, and when I check the phone, the torque app has closed. Could the torquelogs.csv file be getting too big, and causing the torque app to forceclose?

Any help would be great on this, I really need to get the torque app to reliably record at least a weeks amount of data from a vehicle, without the driver having to check the phone each trip to ensure its logging!

I cant remember off hand which CAN protocol it gets stuck on. I tried to set the vehicle profile to iso14230 (which is what my honda is). As I understand, torque will still try to cycle through the other protocols if it cannot pickup the preferred one, the preferred one is just cycled 1stly? Perhaps a checkbox that makes torque only look for the one protocol would make sense, if you know the phone is only going to be used with the same vehicle the whole time.

In terms of the other issue, I have used torque on a few different phones, including a samsung i5500 running 2.1, and a very recently out vodafone 858 running 2.2, and it does not seem to make any difference. I don’t use any task managers etc.

Could it possibly be a google licence issue? The 3g signal isnt great where the car would be parked overnight.

I’m after digging out the cheap ebay bluetooth dongle that I got ages ago, and connecting this to the vehicle instead. Torque picked up the protocol no problem after a stop using this! So it must be a problem with the obd key (http://www.obdkey.com) dongle that I am using! Do you have any idea what the issue might be with this? I had a quick look on their website, but didn’t find any sort of firmware update for it (if it has a firmware, I’m not sure?).

Edit: I’m just after looking on your wiki page, I didn’t know that the OBD key device is not officially supported by torque? I just assumed that it was, because its from a reputable manufacturer. Are there any other specific issues you know of with this dongle, or have you ever come across on? I have a few of them from use with a previous college project I did, if you are interested in borrowing one to test yourself, I can post you over one for a few weeks etc.

Hi,
i have the same problem using the dashboard while driving.
If torque looses the connection, it never tries to reconnect.

So i need to leave torque and call it again. this is not good during driving.

if you can make a reconnect button as long as there is no connection it will be safer.

OpaLothar