Hi!

It's usually the weight - if you're using the manufacturers weight specs then you'll likely need to add a bit on as they're always on the conservative (sometimes not including fluids, persons, etc). Weight is the only field used for the HP/Torque tests in the vehicle profile

Also, it's important to do the following to get an accurate reading:

* Start from a slow rolling start (not a standstill which will likely cause the wheels to spin), so from 10mph upwards you should get a good reading

* Make sure 'Faster Communications' is enabled (this is fairly important if you have an older vehicle). Also make sure the GPS is enabled (this augments the OBD speed and provides some error checking for certain situations)

* Only have the Torque/HP displays visible on the screen, and turn off logging of other non-speed related sensors (the reason here is that the more displays on the screen there are, the more sensors are requested/polled, slowing down the overall refresh rate. If you have several displays on screen that all show the speed, then this is fine as that means only one sensor is requested, however if you have several displays showing several /different/ sensors, then this means that you're asking for several sensors, making things 7 times slower for a full refresh of all the sensors)

That's about it - if you're doing the above then you should have accurate results!

The weight in germany is with 100% liquids, driver etc. There is not much room for adding additional fictive 200kg I guess. And I cannot imagine to have a 2 tonnes car :-O

Performance should be no problem on modern quadcore smartphones I guess?!? Bu I'll try to reduce gadgets.

I've also experienced on a race 0-100 kph, the the value is displayed when the car is at ~120 kph. The range of 4 exacly same sprints is from 5.5 - 6.5. Seems the polling interval is too big?!?

Hi!

Just to clarify, the performance of the smartphone isn't the issue, it's the number of sensors to poll and the speed of the physical communications link to the ECU from the Adapter

Each sensor over OBD can take from 2-3ms to over 200ms to retrieve data from (depending on the speed of the communications link and protocol used) - this is not defined by the speed of the phone, but by the physical protocol used by the ECU to talk (on newer vehicles, this is nice and quick)

For example for 1 sensor at 200ms you may only get the ability to read 5 sensors/second. This means that you can read 1 sensor 5 times a second, Or 5 sensors once a second (or anywhere inbetween)

Making sure 'Faster Communications' in the app settings is enabled is important as this improves the speed of the communications to the OBD2 adapter and reduces the time taken to request each sensor (PID). Reducing the number of displays will (if they are viewing different sensors) reduce the number of sensors polled. So the fewer sensors polled, the faster the updates

I've added up to 500 kg but didn't get over 280 hp? What is wrong? How is the math? Should I enter 5 t, which makes no sense at all? Do I think wrong?