MobiFlight Community Support

As i know there was no big change here.
Yes we implement the "simulated detents" for the 2:1 and 4:1 Encoders..... And Yes This can occure in your reported Problem with wrong direction.
BUT Then this symptom must also happen i you turn Standard NAV instead of the Jeehell Datapipe. this wrong Direction ( In case of Mobiflight Firmware) is global i think..... not related to the Datapipe itself.

The Datapipe is working same way as before as i know.
What change is a new system of Inputs.... That build a cascade if to much Inputs ocure ( Encoder mostly) ..... so Mobiflight send them with a little delay if needed.
And here maybe the problem occure.

Jeehell Data Pipe looks cool but this is stoneadge as it best. So Difficult and so many bypasses. Lots of people still report it is verry slow. But we can not change.

When you turn the Encoder 1 detent Mobiflight must read the current Value from the Display.... Export that data from the Read Config to the Input Config.... Must calculate $+1 must send data to FSUIPC .... Then it must send the Data Pipe activation to FSUIPC..... In FSUIPC there must be a recalculation and a action fired. Jeehell must recive this command and execute it in FMGS..... so 5+ Steps instead of 1 step if we would use a simple Joystick Button Input.

Solution.
Does Airbus Jeehell got a Switch that change between 1000/100 above the Encoder ?
Why not simply rework this switch temporary in 2000/100 .
So if you press that button/switch you swap into Slow LEft/Rigth permanent to +-2000 ( instead of 1000) and another press go back to standrad +/- 100

Hi pizman,

The switch for altitude change (100 / 1000) is available but the reverse action with Fast happens with speed, heading, and vertical speed datapipe as well, which do not have the switch option
I am now can work around by tuning the encoder at speed of 4-5 detent increment/decrement, then it will work, seem there is a timing restriction somewhere in Mobiflight input code.

Thanks
Vu

Ok....

But this not awnser the question finaly.....

If you set e.g. NAV for on Fast.... and you turn also "too fast" as you do in the other example.... Does it also send wrong direction commands random ?

If you can confirm 100% this wrong direction only happen with Jeehell ( so you test 100% same situation and turning speed) THEN we must rethink the config.
I basicly not understand why you use +20 ( +2000 ft) here. Thats way to much i think. +500 for on fast should be better and more logical!

So do this simple test.... May you find out at what value you get into trouble.

To confirm my idea.... You can also use just On Left and right without FAST commands..... But you use here the +20 Inputs. If my idea is right then the issue also ocure now with slower turning and the problem is basicly the big steps !

Hi Pizman,

Today I have a chance to test 2 things as your suggestion for Jeehell DataPipe.
- Test 1/Datapipe ALT: use only on Left / Right with big step $+20 and $-20.(Fast command set to None) ... The behavior is correct, no reverse action
- Test 2/Datapipe ALT: use Left FAST and Right FAST, with smaller step $+5 and $-5, the reverse action still happened. Turn right Fast continuously on ALT encoder, the altitude sometimes reduced 500ft then increase

So I think the big step is not the problem.