Today I had a closer look at the logfiles. In contrast to the roughly 150 values for the capacity from Spirit I have around 3000 values for the current and the capacity using a Jeti sensor MUI150 in the same time. Looking at the quite big difference in the numbers it should be more or less normal to get such differences in capacity from flight to flight. Would it be possible to calculate as many values for the capacity as there are values for the current? Also I had a look at the time differences between two measurements - the first parameter in ms in the logfiles. As these time differences are varying a lot, do you take them into account for the calculation of the capacity?

Hello,

thank you for the details.
Unfortunately the problem is not in the quantity of logged values. It is in the measurement itself.
So whatever number of logged values there will be, it will not improve precision.
Even if there will be 3000 values for capacity, the result will be completely same.
Difference is there, because capacity values are not changing so much as values of the current. Values of the current are important to see as fast as possible, as there are fast transitions.
But values of capacity are changing only in positive direction and the most important is the final value. So even if there will be just 2 reported values, the final value will be same with same precision.

Difference of reported values is there, because all data are going through single bus - EX Bus. This include data of all channels and also telemetry and integration data.
To make it fast enough, there must be some compromises to meet required timing. So we intentionally dont want to send data as fast as possible, because it could negatively impact other, more important things.

MUI is connected by a telemetry sensor connection which is used only for this single purpose. So there is no risk of anything if there are too much data.

The problem with capacity measurement is in invalid data frames from the ESC readings - there is the problem. This is thing that you can't see in the telemetry data or quantity of values.

My question is, if you have tried to test it with disabled governor in the unit? This could make the precision much better. If yes, then we will know what can be improved.

_________________
Spirit System developer

Thanks for your detailed answer - I will test with disabled governor this weekend.

But one question: Does the ESC get a signal if the governor is disabled? The ESC has to stay connected to the Spirit for the telemetry.

Yes, you have to only disable governor in the unit and enable one from the ESC. Wiring is same.

_________________
Spirit System developer

Please check your private message. I am sending you firmware that should fix the problem.

_________________
Spirit System developer

Today I have made 3 tests - the factor was 0.69 and two times 0.70. Great - thanks for your fantastic support.
I assume that you will put the fix into the next official update - correct?

Three more flights today - it is working perfectly.

Thank you for the report! It is looking very promising, so we are also very glad!
We have similar reports from other pilots. Only that each ESC has different correction factor - I-motor shunt.

_________________
Spirit System developer

Due to the fact that the factor has to be set once I see no problem. Maybe you can create a list with possible values.
On my side it is a CC Edge 80 HV with a tuned Align 600 MX -> 70%