Hi,

Just installed now, in next days I will give you some feedbacks...

It would be nice (at least for me) if you add catalyst temperatures readings: pids 3c, 3d, 3d, 3f sensors.

edit: do you think is possible to have a BOOST light bar?

edit2: it's possible to remove the intro message that warns to set parameters? it appear wvery time the widget is loaded.

HI!

just done 1st trip, all works fine except:

acceleration measurement (I've set min 80 max 120), I've tried several times but it never worked

Gear indication not works properly: @costant speed it show correctly the used gear, but the indicator continuosly swap between neutral and used gear, something like this:

4, n, 4, n, 4, n,
5, n, 5, n, 5, n,

this beaviour is more evident in 4th, 5th and 6th gear (on 1st, 2nd and 3rd also but less evident)

Thanks for your feedback.

I'm going to retest this and make some adjustments.
I publish an update as quickly as I can !

Fabrice

Hi,

An update is available on Play Store.

Changelog for RacingMeter v1.0.1:
- Improved Gear indicator stability.
- Added false-positive filtering on Gear indicator in neutral position.
- Fixed current/best acceleration widgets.
- Welcome message can be removed.

I add to my TODO list the Boost light bar 🙂

Hi Fabrice,

I've done some verifications (on 1.0.0 version):

About gear indicator,

I've seen a little discrepancy on gear ratios between my car datasheet and values retrieved by OBD, on this morning trip i've collected the info (speed @2000 rmp on each gear) by obd readings, and putted the new values on vehicle profile. This evening i will check if it works better. (There was a difference of 3 - 5 km/h between datasheet values and obd reading, maybe that's the cause of strange behaviour).
(I suppose the gear indicator shows the used gear checking the relation between speed and engine RPM, I'm right?)
So if it was this the trouble, for the other users I suggest to set the values collecting data from OBD (speed@rpm) and not using the data from vehicle specifications, because it's possible to have some discrepancies...

About acceleration times widget,

Maybe i've done something wrong with the units (I use km/h): yesterday I've set to measure 80-120 km/h but maybe the program excepted to measure 80-120 mph.
This morning I've set 30-60km/h and it seems that it works fine, this evening I'll check again 80-120km/h interval

Ps. Are you french?

Yes I use OBD speed/rpm data to estimate the gear. In v1.0.1 I increased the margin of error and removed some false-positive.

About acceleration times there was a bug if the starting speed value was 0. I fixed this in v1.0.1.

PS: Yes I'm french and you are Italian ? I have Italian origins but I don't speak it 🙁

Oui je suis italien, comment l'as tu compri? Est ce-que mon accent est evident aussi quand j'ecris anglais ? 😀

_____

Thanks for new version, I will check ASAP.

Edit, if in future if you do multilanguage versions, feel free to ask me italian translation 😉

J'ai aucun mérite! Je le sais grâce à tes coordonnées Google quand tu fais un achat sur le Play Store 🙂

Thank you for your effort. Will test it over the weekend.

In the meantime please confirm whether the Gear indicator works with automatic gear shift vehicles...

Quote from Pwned-PS3 on September 13, 2012
In the meantime please confirm whether the Gear indicator works with automatic gear shift vehicles...

I don't test it with automatic gear but it should work fine.

Hi Fabrice I've done some test with version 1.0.1.

now gear indicator works correctly

acceleration widget works fine also, but sometimes the best result is not updated, example:
I've done some runs from 80 to 120 km/h, the 1st time was 9.21 seconds, the second attempt was 8.93 seconds (this was set as best) the 3rd attempt was 7.56 seconds but it was not set as best, the 4th attemp was 12.7 seconds.
finally on screen the times was best=8.93 current 12.7 instead of 7.56 / 12.7

Edit: on this morning trip always worked fine...

question: how is calculate boost? from map or maf sensor? or uses the same method used on Torque app?

request: could you add the possibility to set pressure range (min-max)? My turbo boosts till 1.9 bars, but the indicator is completely filled when pressure is = 1 bar

Quote from Hiej on September 13, 2012
question: how is calculate boost? from map or maf sensor? or uses the same method used on Torque app?
request: could you add the possibility to set pressure range (min-max)? My turbo boosts till 1.9 bars, but the indicator is completely filled when pressure is = 1 bar
___________

The boost value is the same as in Torque. For now the turbo gauge is auto-calibrated, I'm going to add manual settings for this.

Edit: 1.9 bars !! awesome 🙂

so if in Torque I set to use MAF calculation method instead of MAP method, RacingMeter uses MAF ? That's fine.

____

Yep, 1.9 bars, but it's a Diesel engine (2.2liters 185Cv / 400Nm), I think that value is reached by many performance oriented diesel engines: for example, a friend of mine on Golf GTD 170 HP the boost pressure reaches 2.2 bars

I added the turbo range settings in the last update (available on Play Store in few hours).
_____

I didn't know that stock turbo on diesel can push up so high!!

yes, diesel engines are not subject to detonation issues like gasoline engines, so to have power is possible to
have high boost pressures.

a little report on version 1.0.1: it seems that sometime the readings freezes for some tenths of seconds, this is noticeable on acceleration an in deceleration when you can see that the rpm counter and speed indicator freezes.

maybe thats is due to my obd2 adapter, wait reports from other user to confirm

I don't know if this will resolve your freezes issue but I uploaded an update on Play store which significantly improves the latency. I also added an option to reduce data filtering, this can be useful with some adapters.

Hi Fabrice do you works also on weekend?

Go out and enjoy last summer days 😉

I've done some runs with version 1.0.3, if I enable faster communication it not change: freezes are still present but in addition data reading is more lagging. In fact faster communication drops pid/sec reading from an average of 45/50 to an average of 15/20.

using the same widgets on Torque interface there's no freezes... do you think that is possible that the freezes happens when is checked what gear is used?

Not easy to debug.... with a cheap ELM327 no freeze at all and very acceptable latency... and you have an OBDLink MX...

It is not related to gear checking or UI but to the communication with the ECU (or maybe with torque service).

In fact, "faster communication" simply decreased the data filtering (and so the latency). But if the plugin/ECU communication is laggy, you will see the interface freezes more when "faster communication" is enabled, it's a normal behaviour.

you have more freezes with the v1.0.3 (faster communication disabled) ?

for me with faster communication disabled it's works better. about freezes keep in mind that it's not very noticeable, the indicators does not freeze for seconds but for fractions of second and not every time. so wait reports from other users 😉

maybe with faster adapters this behaviour is more noticeable

you are doing a great job now rpm bar works fine