THEMA:

29-5 last friday - 2 flights OneBattery total 1000mAh.
Today on the slope : reset to zero. It was zero and having a new propeller I looked at the first launch and OneBattery said 180 mAh for the first climb.
So I am sure One B was reset to zero before to start.
Then : end of first flight 560 mAh.
Second flight started with 560mAh but at the end OneB indicated 2990mAh. You can see from telemetry (photo off DataExplorer statistics) how much I consumed.
Not 2990 mAh ! (Lipo is 3500mAh) - I can add that when strange value appeared on OneB I scroll Jeti menù to look to second page and %Battery was indicating 77,4%
(this means impossible 2990 mAh!)
At the end of second flight I pushed the reset momentary switch and instead of 0 the value was 1300mAh -(today total consumption)
I pushed again reset and value indicated was 1000 mAh. ( value of first fly session on 29-5 with OneB?) -
I pushed again and finally went to zero.

Miko schrieb:

29-5 last friday - 2 flights OneBattery total 1000mAh.
Today on the slope : reset to zero. It was zero and having a new propeller I looked at the first launch and OneBattery said 180 mAh for the first climb.
So I am sure One B was reset to zero before to start.
Then : end of first flight 560 mAh.
Second flight started with 560mAh but at the end OneB indicated 2990mAh. You can see from telemetry (photo off DataExplorer statistics) how much I consumed.
Not 2990 mAh ! (Lipo is 3500mAh) - I can add that when strange value appeared on OneB I scroll Jeti menù to look to second page and %Battery was indicating 77,4%
(this means impossible 2990 mAh!)

I would assume this is a multiplicator error, could you please send me the log-file for the second flight where this 2990 happened?

At the end of second flight I pushed the reset momentary switch and instead of 0 the value was 1300mAh -(today total consumption)
I pushed again reset and value indicated was 1000 mAh. ( value of first fly session on 29-5 with OneB?) -
I pushed again and finally went to zero.

The 1000 could happen if sensor does not report "Ah" as unit. I need to see the log-file to see if this could be the case.
I think it would be wiser to give user the selection of selecting "Ah/mAh" and not trust the sensor, this would suggest there's some issues with that.

Tero,
here's the log that at the end gave 2990mAh.
I underline again, first flight 560mAh, as you can see it's the starting point in this seconds flight - and as you can see total "Kapazitat" for this flight session is is 1310 mAh
Some value, like Entfernung/distance pilot-glider - has a straight line from minute 25- Not all values have this strange line from 25 to end of flight.
I think there was something wrong only in the GPS datas, not communication sensor/RX/TX but you're the expert !
Probably this is the problem? but Qrx for JetiRX11 / A1 / A2 always good in shape.

Thanks

Miko

Tero,
I put this report as a "BETA-TESTER" of Onebattery. I hope others will report their results !
Hoping this can help.
Consumptjon 2010mAh on screen 5340 mAh

If I've to stop to report, tell me, I'll do it !

Sorry for extra work on this app !

With my set up - Link Vario Pro from WSTech - seems that this app can't be used.

Reading my report dated 5th june (previous post) it's clear that Onebattery takes last value in "Kapazitat" and sun-up in sequence.
Kapazitat is the same value that OneBattery must calculate. Switching on and off the radio OneBattery sum-up the value indicated by LinkVarioPro.
In effect 1780 x 3 time = 5340 mAh.
---
Today the same : first flight 410mAh, when restart to log (launch at slope) One Battery has 410 min memory and takes again 410 from sensor, so on the screen
820 mAh.

Probably this app is not compatible with system of calculation (in Ah) of LinkVarioPro. Probably with Unisens it's another story but I can't help !


Thanks, it was anycase interesting make some test for Tero !