Closed azaz44 closed 2 months ago
The solution is to reset telemetry. I use a SF triggered when my throttle is first armed.
The solution is to reset telemetry. I use a SF triggered when my throttle is first armed.
I do the same.
Hmm I can try, but do you use stickies? I wonder how it will work with resetting flights. I would need to reset it only on first arming and not subsequent ones.
I also use one of the function switches for a manual reset, especially on a new model, when I don't necessarily want to arm and disarm the throttle.
This works, I think I will incorporate it into my settings. But unfortunately it doesn't work with calculated sensors. For example "min cell voltage" (which is "min voltage" divided by numer of cells) does not get reset with "Reset Telemetry". But this is I think a different issue to fix.
Ethos 1.5.9
I show statistics like
and check them after each flight. But some of them are not usable. For example min voltage is always zero. I think this is because voltage is growing when connecting the pack.
Min BEC voltage is fine, but only as long as I keep system powered. If I disconnect the pack, sensors become lost, but just before that the BEC value drops and affects the "min" value. So here it works correct, but it could be more usable.
All of this happens because sensors get weird values, growing or rising when connecting and disconnecting the power.
Example situation after filght:
And after disconnecting power:
Proposed solution
I wonder if we could have an option:
"Update min/max" [ !Throttle Cut ]
So we could set a condition when statistics are actually captured. We could then set it to !Throttle_Cut and be happy. This could be an option per each sensor, or one global per model.