So I’ll lay this out simply: There is too much stuff being accessed (according to the active sensor list) despite what I’m actually asking for; this cripples the refresh rate on both the screen and makes anything but half second or slower logging useless. When attempting to log at .1 second intervals, I normally get between 5 and 7 repeated values per PID.

In fact, having so many active sensors means the tablet (a modified Nook Color specifically flashed for use in my car) will actually lock up and reboot if I try to do anything other than view the one screen I have configured; trying to modify things ends horribly.

I have one screen active with the following sensors being monitored:

Engine coolant temp
DI PSI (custom pid)
Vacuum/boost
Actual AFR (custom pid)
Speed
RPM
Barometer

I have the following items set to log (logging has been disabled due to the issue at hand):

Engine coolant temp
DI PSI (custom pid)
Vacuum/boost
Actual AFR (custom pid)
Speed
RPM
Barometer
Throttle position (manifold)

I begrudgingly accept the fact that the accelerometers are forced to not only be active, but logged as well; they aren’t in the datastream pulled from the ECU so they “shouldn’t” be a part of the problem.

I really would like to know why the following are forced to poll on the active list when I’ve never configured them to be used before:

Air Fuel ratio (Commanded)
Air-Fuel ratio (Measured)
Ambient Air Temp
Catalyst temperature (bank 1, sensor 1)
Commanded Equivalence Ratio
EGR Commanded
Engine Load
Intake Air Temperature
Intake Manifold Pressure
Relative Throttle Position (Alternate)
Trip Distance (This has never actually updated anyways)
Voltage (Control Module)
Voltage (OBD Adapter)

I’m also kind of curious as to why the following are still listed as active, even though I no longer have them on any screen/logging:

Engine Load
Mass Air-Flow Rate
Timing Advance
LTFT (Custom PID)
STFT (Custom PID)

Not including accelerometer data, this totals up to 18 active sensors that shouldn’t be active.

Also, it would be nice if we could both turn off the accelerometer monitoring and logging (or at least reduce it to nearest hundredth.

I have a lot of time and a fair bit of money invested to using Torque as a platform for ECU monitoring, but I’m beginning to regret my choice.

If there is ANYTHING I can do to help with the resolution of the issues outlined in this post, please contact me; I am willing to do what it takes to make this work.

TLDR:
“OH GOD THE GOGGLES, THEY DO NOTHING!”

Hi

The screen corruption you have in the active sensors screen is something wrong with Android itself and should not ever happen on a properly functioning system (is this an original ROM that the manufacturer has supplied?). The active sensor screen is fluid on all other devices (even a lowly X10 mini pro and huawei low-end phones) so I highly suspect this is a problem with the version of android you are using

As to the refresh rate of sensors, there are several reasons for slow readings. Unfortunately you haven’t sent a comms debug whilst connected so I can’t offer any extra guidance.

Have you ‘ticked’ “Faster Communication” in the OBD2 settings and *UN*ticked “Disable ELM327 Auto Timing”?

ECU’s can also determine the speed at which sensors can be read. My Smart Roadster can only update at around 7 PIDs/sec, where as my newer Smart ForTwo(which uses the can protocol) updates at 31PID/sec – this is simply due to the way ECUs implement the protocol.

The adapters can also limit the speed at which sensors can be read. For example, the OBDKey can be quite slow at updating on some protocols, whereas the clone units from ebay are often faster, and the fastest adapter being the Scantool.net OBDLink

Also, make sure you are on the *latest* version of Torque from the Android Market. In an ancient version (ie: older than a month) there was a screen update issue with the sensor screen, it was a bit laggy, though it wouldn’t cause screen corruption like that (the screen corruption is a bug in android there and I suspect you’re not using the original firmware?)

Ian

Debug data sent from both my phone and the tablet. Note that the phone has no memory card, so I did not migrate torque settings and just cleared all but the main screen; other settings should be identical.

I tested the lower framerate setting and found it to leave the UI less responsive than with it off. I’ve also had it log again and found that it still repeats values for 5-7 rows.

I’ve tested bluetooth speed and can transfer files at about 100 KBPS, so a few PIDs should not be an issue. Maybe later tonight I’ll try an overclock and some settings tweaks to see if that helps at all.

Hi

Some of the PIDs don’t require data to be sent over bluetooth (and are calculated from the 4/5 that are pulled over OBD, or are calculated from other sensors (GPS for instance if you have a GPS speed widget visible)

Logging is independent of PID read cycles, so if your reads only update slowly, then you will get duplicate lines.

Your ECU responds to PIDs at intervals of 80ms from requesting the data to getting a response, this is the limiting factor. You are limited to an approximate max of 12 PIDs /second – if you have 8 displays, then you would get a refresh rate of just over once per second. You are being limited by the rate the ECU supplies the data and/or the adapter.

Ian,

The PLX support people say that the Kiwi Bluetooth polls at a rate of 10ms; I’m trying to find out how many it can poll at once at that speed, but as of this moment, it doesn’t look like that is the issue.

There’s at least one other person on another forum I frequent who can’t get high speed logging to work properly either.

Do you have some sort of speed/latency test that can be run?

Kickass, that would be awesome man.

Thanks again.