hobDrive Support

just in case, the file should look like

<gauges>
<gauge id="*" cache-interval="2000"/>
</gauges>

but there could be other lines if you've customized the UI.

I did that, still the main tab takes 330-380ms to get a new reading, I'm also not sure if that improved anything.

Hm.. just to make sure - try to switch off "draw charts" option in system menu.

Did that, still the same.

Hm. At least its good the bottleneck is not in graphics. I'll try to reproduce this on my hardware.
The strange thing is that I don't see such issue even on slow winCE hardware.

OK, please let me know if you need anything or you did any progress on that, getting the data to refresh 5 times a second is much better than 3.

Any progress Cali?

Alawadhi, sorry - android consumes all the time.

It seems the root cause is that all your sensors are in a single request. In moments when it on 'General' screen, hobdrive requires more sensors to be analysed from a single request.

I however don't understand why it slows down because cpu power is enough. I'll look more precisly inthere.

BTW, in latest beta there is a quite realistic power and torque measurements. You can give it a try (PMed you a beta)

Thanks I will, currently I took the PC out of my car for maintenance. When you have some time please take a lot at my matter, perhaps you can simplyfy some of the formulas for faster performance.

The only other thing that comes to my mind is if you save and retrive from the harddisk, the access time of the HDD can cause a delay of like 10-100ms.

Thanks Cali.

Any updates on my issue Cali?

Also how can I set the fuel price from two digits after the decimal point to three? I've went through all .layout files and I found nothing.

BTW if there's a new Beta please send me the download link for it, I currently have the 1.1.47 Beta.

Sorry, no progress. It definitely should be improved, but I still cant find the rootcause.

To use three dec points, add precision="3" parameter to the layout "item".

PMed you as well.

Thanks for the link, the max power and torque calculation is still some way off but better than before at least.

I have to extract more config data into settings (roll resistance, frontal area, etc).. They are hardcoded now. Will do that soon.