Pro Logging stick pos error

I'm logging the stick positions using the Pro Logging app. I notice that the outputs for aileron and elevator are not 50 when the stick is centered.

At the beginning, Elevator is 51, the others look fine.
13.10.2021 13:28:07;;Bat(S);Coll;Elev;Ail;Tail;NEO(RPM);NEO(out)
13.10.2021 13:28:07;0;0;1;50;51;50;0;1
13.10.2021 13:28:07;0;0;1;50;51;50;0;1

At the end, Elev and Ail are at 51.
13.10.2021 13:34:18;0;46;1;51;51;50;0;1
13.10.2021 13:34:18;0;46;1;51;51;50;0;1
13.10.2021 13:34:19;0;46;1;51;51;50;0;1
13.10.2021 13:34:19;0;46;1;51;51;50;0;1
13.10.2021 13:34:20;0;0;1;51;51;50;0;1

My other flights do something similar. My sticks are calibrated and show 0% at rest.
Are you logging the raw stick position instead of the calibrated stick position?

Thanks
Rich

Hi Rich,

give them eyesight, and they start seeing problems they never had before

Could be that these are rounding effects, emphasized by the fact that you have to sacrifice precision (like the original 3,200 steps resolution, or 1/32 increments) for bandwidth, and slightly affected by temperature drift etc., which—in normal operation—falls within the very narrow (hardly palpable) dead band.

If you do not experience drift on either axis with that logged (rounded) 1 % deviation, all is well, technically.

But let's did deeper: if you check the calibration for Elev or Ail, what offsets do you see? Is it on edge, like .5, so a tiny change in the rounded decimal could cause an integer increment?

Kind regards

Eddi

Born to fly ...
forced to work.



Edited 1 time(s). Last edit at 10/14/2021 10:13AM by Eddi E. aus G..

> give them eyesight, and they start seeing problems
> they never had before
Well, you can only blame yourselves for giving us more than we wanted

The calibration on Elev/Ail is 1.2 and -0.98 respectively so it's probably that.
I'm happy that I'm not getting drift and the calibration is within a comfortable range, so no problems there.

I was just thinking about writing something that could replay the stick positions and output a video for overlay into a flight video, and the numbers just looked odd.

Thanks for the reply.

Hi Rich,

I know ... shouldn't have started with logging in the first place, makes everything way too transparent and then, there's the support effort ...

I guess if you were visualizing stick inputs, on a screen, 1 % wouldn't be critical for understanding the maneuver.
You could even pull 1 or 2 % to center all the time, to make it look clean

If I look at the stick display in simulators, they're also not always that precise, or somewhat damped, simplified, or so it seems.

Kind regards

Eddi

Born to fly ...
forced to work.

It almost works. 2 logs per second makes it look a bit rough, but I could interpolate the positions up to 60 frames a second to make it smoother.
https://www.youtube.com/watch?v=gn0vavWTsRw

Edit: Never mind, 2 a second isn't enough for piro moves. Back to the drawing board.

Rich



Edited 1 time(s). Last edit at 10/14/2021 12:52PM by RichardV.