Throttle gimbal

Can I get some good cheap replacement gimbals somewhere ?
My problem is the throttle gimbal. When it is down it is -100. If I press it down or down and a bit to the sides, it goes to -120..-125 ish. This is not very good. I need a stable lower limit.

Is there better hardware ? Can the software help me ?
Or is the solution to calibrate differently - Say move the throttle stick down, but not too hard down, and have this registered as -100. And then have the endpoint at -100 in software (min limit) ? So that anything lower than -100 will be -100.
Can I set min limit to -100, and still have failsafe at say -150 ? It is throttle I have issues with, and it is throttle failsafe that are most common.

Let me guess it is about a devo7e? I noticed that the stick itself is to thick, so due this the stick blocks to the edges of the gimbal.
Using of aluminum thicker aftermarket sticks on the 7e makes the problem even worse.

Possibly you could dremel some material away from side of sticks??

Nope. It is actually the Devo 10.
I think that software should be able to handle this. If you calibrate the sticks, there should be no way that you can input stick values outside -100..100. Just let the rest be a deadzone.
The EPA could scale the values outside this range, part of the mixer. But I see no reason for sending stick values outside -100..100 into the mixer.

So you agree with me, that it would be better that calibration defines -100..100, and anything beyond that would be capped on stick input ?
Anybody here needs some other behaviour ? Then they can scale the axis, or use endpoint adjustment.

I am now looking in the source, for Devo 10, Devo 8 seems the same

github.com/DeviationTX/deviation/blob/ma...et/devo10/channels.c

It reads calibrated min/max:
s32 max = Transmitter.calibration[channel - 1].max;
s32 min = Transmitter.calibration[channel - 1].min;

But uses another value to actually calculate
value = (value - zero) * CHAN_MIN_VALUE / min;

And should limit min
if (value < CHAN_MIN_VALUE)
value = CHAN_MIN_VALUE;

CHAN_MIN_VALUE is -10000

So it should work as I want it to. But doesn't.

Naybe it is this:
if (channel == INP_THROTTLE || channel == INP_RUDDER)
value = -value;

unless calibration makes sure to switch min/max for these 2 channels as well ?

Looking at calibrationhere:
github.com/DeviationTX/deviation/blob/BR...mmon/_tx_configure.c

there is nothing to swap max/min on throttle/rudder. Does that mean we use the wrong end of the stick for max/min calibration ?
Somebody with a bit deeper code knowledge might be able to help here.

At least this is something I might be able to test on my Tx. Should be trivial

why not just secure the pots into the mechanism properly?

Now I re-calibrated, and could still get to -95 only, and found out that one of the switches (ELEV D/R) caused that.
www.deviationtx.com/forum/model-configs/...0-and-devo-10-mode-2

But the mixer had a simple mix, so I have no idea why the switch was able to add +5 to all throttle values (The Devo 10, E010 model from here), that is both ends.

I could get it to -110 by using the Elev D/R switch, but looking at the init, I can see it is a failsafe switch aka arm/disarm.

After calibrating without pressing too hard, a powercycle or 2 everything works as it should.

Guess I should read the downloaded ini or docs a bit better next time.

The gimbal quality varies among different transmitters. I got 2 devo 10, one is perfect without offset whilst one drifts by a slight percentage. Some users have discussed a fix here