tlsmikey,

The refresh rate of the data is dependent on how fast your ECU is sending data and how many items your logging and displays on your screen. If you look under the "Adapter Status" you'll see the Adapter PID read speed. For example on my car I usually have a rate of 16-18 PID's a second. This means I'll be able so if I am logging 16 PID's they all will refresh roughly every second. This is the reason I use a 1 second logging rate. To get a higher refresh rate you would need to log fewer PID's maybe 1 or 2 depending on the Adapter PID read speed.

Regards,

Road_Wx

GFK, ND

Quote from tlsmikey on July 19, 2011
I was logging this last weekend at 0.1 second intervals and while all of the data rows are there, the data is repeated and only really updated once per second.

Is there any way to get 0.1 second updates?

There's also a really secret option in the 'OBD2 Adapter Settings' called "Faster Communication" - make sure that is ticked and it will allow for much faster PID read speeds if your adapter supports it!

(make sure the 'Disable ELM327 auto timing' is disabled though as that will slow things down if it is enabled)

Thanks for all the help.

My PID speed is 8 (ELM327 ebay OBDII bluetooth adapter). I am only recording 4 items (rpm, speed, temp, throttle) but even if i enable "fast connection" and make sure that the other settings are correct, it still only provides one update per second.

I did notice that it is also sending the four acceleration values as well, but i think these are recorded from the phone internally.

Is there a faster bluetooth adapter that would have a PID of 20+?

Just thinking out loud here. Would a hard connection work better? say USB to Droid?

It all depends on your ECU. If your ECU can only provide 8 PIDs/Second then getting another adapter (bluetooth or wired) will not help anything. But if for whatever reason your ECU is capable of 10, 15, 20, etc your adapter would be the bottleneck.

I kind of doubt going wired would be any faster as it seems the bluetooth spec can handle the data throughput. But, this is just a guess and not all that educated.

Hi 🙂

Unfortunately this is not really an adapter issue at these kinds of speeds, it's more down to the speed at which the ECU can supply the information
On older vehicles, this can be quite slow. In your paticular case, I don't think a different adapter will help greatly, even if it was wired.

Oh, i see now. I thought you were both referring to the ECU within the adapter, but we're talking about the car ECU.

OK, well that's too bad. Looks like i'm stuck for now.

I'm not convinced that this is a limitation of the adapter or the ECU. If that were the case, you would see the same characteristic in the gauges.

I have 13 gauges on my dashboard, and they are absolutely refreshing multiple times per second.

I logged 5 PIDs today, and saw them all refresh every .7-.8s. That gives me 3.75 PIDs/sec.

Now that I think about it, I started logging from my dashboard, so I guess it was also trying to update the gauges.

Hi!

Torque will refresh more or fewer sensors per cycle depending on:

* What you have visible on the screen in terms of gauges at that moment in time
* What you are logging (more sensors == slower refresh cycles)
* Any dependant sensors dependent on the values that you are logging

The refresh cycles are variable, and depend on your setup in the app.

If you're using a newer vehicle which uses canbus, then that protocol allows for a really quick refresh of sensors. On canbus systems the adapter speed is usually the limitation. On clone adpaters you could get up to 26PIDs/second read, and with something like an OBDLink you could get over a hundered per second.

On ecu systems before canbus, then the protocol is usually the limiting factor (if you're ECU uses the ISO9141 for example then you may only get up to 5 sensors read per second). Each protocol runs at different speeds and also has different latencies depending on the adapter and ECU.

To find your refresh speed, look in the 'Adapter Status' screen in the pro version, which will tell you the protocol, and how fast your refresh rate is

To stop duplication of values on slower systems, change the logging options to synchronous logging. This will only log 1 line per full refresh of the sensors and is likely what you want

Thank you for the reply.

I tested again today. This time logging 4 PIDs: AFR commanded, AFR measured, RPM, and throttle position. I changed to a completely blank dashboard before starting the log, so I should have only been refreshing the 4 logged sensors.

Still, the log file has values repeating for 7 intervals.

Something else is going on here. What do you think?

I checked the adapter status and was averaging 16 PIDs/sec.

That should mean comfortably logging 4 PIDs at .25 sec intervals. Yet, I'm seeing only about 1/3 that data rate.

Any thoughts?

I was really hoping the developer would take an issue like this seriously, and help paying customers get their money's worth.

:/

I just tried a quick log with a friend's Kiwi adapter.

Torque reported that we were averaging 19 PIDs/s, and we logged 4 PIDs. This should have resulted in new data every 0.21 seconds on average.

Instead, most values are repeated 6 times in the log file.

New adapter, same issue: only logging at 33% of the data rate we should be.

Are you sure TP is not calculating fuel consumption, perhaps even in advanced mode (using even more pids the normal), but not logging it? IMHO, this could result in much more PIDs being requested per sweep than you may be aware of ....

I have TP talking to a 'software accelerated' adapter and this afternoon, TP managed to perform little over 100.000 requests in on hour time. This is about 28 requests per second. Some of these requests even retrieve multi frame responses directly from the HW adapter. So, personally I don't think TP itself would / should limit you to 6 pids per second.

Hi!

If you have trip logging enabled and have log trip fuel consumed enabled then torque may request several sensors to log the MPG, as anko has suggested.
(Automatic trip recording is enabled by default - the mpg logging option is part of the trip recording section)

Also, can you supply the logfile you have itself, unedited

Quote from anko on April 5, 2016
Are you sure TP is not calculating fuel consumption, perhaps even in advanced mode (using even more pids the normal), but not logging it? IMHO, this could result in much more PIDs being requested per sweep than you may be aware of ....

I have TP talking to a 'software accelerated' adapter and this afternoon, TP managed to perform little over 100.000 requests in on hour time. This is about 28 requests per second. Some of these requests even retrieve multi frame responses directly from the HW adapter. So, personally I don't think TP itself would / should limit you to 6 pids per second.

I have that disabled. Plus, I am getting 1/3 the logging rate I should, which would mean it is logging 8 extra PIDs.

Quote from admin on April 6, 2016
Hi!

If you have trip logging enabled and have log trip fuel consumed enabled then torque may request several sensors to log the MPG, as anko has suggested.
(Automatic trip recording is enabled by default - the mpg logging option is part of the trip recording section)

Also, can you supply the logfile you have itself, unedited

Neither are enabled.

Here is the log: https://dl.dropboxusercontent.com/u/60958586/zipExport-2016-04-05_14-00-55.zip

Thank you

Can you tell me if you have any of the MPG displays (including averaging) present on any of your dashboard screens? in the 'realtime information' screen

And in the main 'OBD2 Adapter Settings' have *ticked* the 'Don't calculate MPG/Fuel' setting