MobiFlight Community Support

Would like to use 2 Increment Rotary Encoders for Altitude and Heading.

My question is after checking out forum and can´t find any real answers to this is: Do I use Event ID or FSUIPC for configure this?
And How to do it?

This is what I have now, and I have tested a lot of change in "Param" because that is the only setting I do believe I can change for any effect.
Using one encoder for ALTITUDE in Event ID as: On Left: "AP_ALT_VAR_INC", Event ID "65892" , Param "0", On Right: "AP_ALT_VAR_DEC", Event ID "65893", Param "0".
Using one encoder for HEADING in Event ID as: On Left: "HEADING_BUG_INC", Event ID: "65879", Param "0", On Right: "HEADING_BUG_DEC", Event ID: "65880", Param "0",
This works, but in steps of 1000 feet! I would like to have steps with 100 feet.

Using FSUIPC I have no clue what ever to do...

Regards from a noob...

Here's how I have it set up.

Heading

I'm using HEADING_BUG_INC and HEADING_BUG_DEC. This works but only increases or decreases in 10 degree increments. I believe this is a known issue with FS2020.

Altitude

Use the FSUIPC Offset for Autopilot - AP Altitude Value. I have On Left configured to do set value $-1997537. On Right is configured to do set value $+1997537. On Left (Fast) is configured to do set value $-19975370. On Right (Fast) is configured to do set value $+19975370.

Seems to work fine. The fast is kinda inconsistent but it works well enough for me to set my autopilot altitude.

Here's how I have it set up.

Heading

I'm using HEADING_BUG_INC and HEADING_BUG_DEC. This works but only increases or decreases in 10 degree increments. I believe this is a known issue with FS2020.

Altitude

Use the FSUIPC Offset for Autopilot - AP Altitude Value. I have On Left configured to do set value $-1997537. On Right is configured to do set value $+1997537. On Left (Fast) is configured to do set value $-19975370. On Right (Fast) is configured to do set value $+19975370.

Seems to work fine. The fast is kinda inconsistent but it works well enough for me to set my autopilot altitude.

Thank you!
Got me on right track!

I use FSUIPC to BOTH Altitude and Heading!
And I can use it in smal increments, heading in 1 degree and 10 degree! ($+182) and ($+1820) for left value. ($-182) and ($-1820) right
Altitude is in 100 feet! Using numbers from you! And fast right or left works to, 1000 feet.

Thanks!!

I'll have to give those values a try for heading!

Hi Guys

Please use the correct terms in the future.... "Via FSUIPC" and "via Event" is confusing.... Cause also the EventID is send via FSUIPC ! .
There exist two Types of Inputs: EventID and Offset . Thats more logical... So what you call "FSUIPC" means you make a INput by writing a Offset !


About problem:

EventID are the more comfortable way... AddOns like PMDG basicly need Events cause there exist no writeable Offsets in the system.
Your problem was that those Events maybe not already work correct ( FSUIPC Beta status) OR you did another mistake.

PLEASE CONFIRM:
Does the EventID Inputs occure in the "10 degrees Heading" and "1000 feet Altitude" on your self build Display OR in the virtual Display in the Sim Cockpit ?

It´s just a idea.... Altitude start at 0000 feet. If you encrease it by eventID it should show 100 feet. But if your self build display got wrong setting in Left Padding field then it will show 100feet as "1000" .... So it looks like you increase by 1000 whatever it is still correctly!
Same for Heading. With wrong Left padding setting a Heading of e.g. 21 degree is shown as 210 .... If you increase by 1° it will show 220 ( like it increase by 10 whatever it is still 1 correctly ) .

Hi

I understand what you mean. I think...

I use was using EventID for Altitude and Heading, but no self built display, only the virtual display in Sim Cockpit, MSFS 2020

And with using EventID I could not make it work. Giving me the possibility to change any inputs from my Encoders to 100 or 1000 feet, 1 or 10 degrees with Normal or Fast turning on Encoder.

My solution was to use the "FSUIPC Offset" INSTED of EventID and that worked.
Except for a minor problem when I turn "On Right (Fast)" it jumps to 99900 feet! If I turn a bit slower, it works fine with 1000 feet. I do not know why it jumps to 99900 feet.

https://photobucket.com/u/Dr_Strix/p/11f0aefd-8342-4c49-918a-dbb28a7132c8
https://drive.google.com/file/d/1ESy7sZu5inPWMe4EJPIEmmuDnQwtN5l5/view?usp=sharing
(Hopefully there's a picture)

This picture shows how I did set up the "Autopilot - AP Heading Value" Left side only! But Right is the same.

Leftside should decrese..... Why do you "add" 182/1820 ? Left must subtract it !

Again.... I can not test. So you must find out youreself how it work in FS2020.

Massimos Formulas are logical on first view.... But maybe they not complete. There is e.g. no endstop below zero.
If you turn left while Value is "0" it will reduce current value again by 100 feet and result in a negative value. And this is in a signed Offset the highest possible number ( e.g. 99.000 feet)
So.... If you play with offsets you should KNOW what you do ! ( Thats why we recommend to use EventID cause here there is no way to make a misstake)

If FS2020 work same way like in the past P3D then those Values from massimo can not work !
For example you need in the altitude a "zero protection" Like "if value is below 100ft then a leftturn must SET to 0 and no longer say MINUS 100ft.
Formula like if($<1997537,0,$-1997537) Same for the ON FAST just with other numbers.

The HDG will also normaly not work.... Only from 0-179° Here we need again a more complex If formula. Use Forum search. I explane multiple times in the past !

I have the same problem for use encoder to input the ALT OR HEADING in XP11 with stock B737.

I setup input ALT with encoder on left use EVENTID (on left --> AP_ALT_VAR_DEC , the EVENTID 65893 param 0) . (on right --> AP_ALT_VAR_INC , the EVENTID 65892 param 0)

and mobi modules(check) xpuipc state(check)

When I RUN XP11 & mobi. turn encoder , but nothing happen.

I change to setup input ALT with encoder use FSUIPC (on left --> autopilot AP Altitute value, set value (if($<1997537,0,$-1997537)) (on right --> autopilot AP Altitute value, set value $-1997537), and it worked fine.

Is it has something wrong? xpuipc version ? or I should install FSUIPC first?

Hi!

Explaination of the 10-degree-heading bug see https://www.youtube.com/watch?v=dc2dsZY1lXI

I am using for all switches fsuipc and not the simulator binding.

Gruß Andreas

@ axm823

You missunderstanding the difference between FSUIPC and XPUIPC.

The "EventID" is a feature that is only supported by FSUIPC ( FSX, P3D, FS2020) It is NOT usable with XPUIPC and Xplane !
I know its confusing that it is still available in Mobiflight if you use XplaneSim..... But thats cause Mobiflight itself not know or see what sim you use.... It just send it´s command as you define in the Configs..... It send it "blind" to the System and not know if it recived by FSUIPC or XPUIPC.

So simple Rule.... Xplane NOT can handle Event ID´s.

At Last... You can not install FSUIPC to solve this.... Cause FSUIPC only work with FSX/P3D/FS2020 .... Not with Xplane !.

************

@ AndreasH
Thanks for the Video.
As you know i not own FS2020 so i can not reproduce.
maybe if you like.... Check the Config Files of FS2020.
In the Past ( P3D/FSX ) there exist a file that include all Sim Key Binds as code.
THERE it was possible to rework things.... Also Hold/Repeat Modes. The cool thing was we could add HOLD mode on systems that was not offert in the Sim.... and otherwise we could remove Hold Mode from Systems that the Sim basicly have hardcoded and not allowed us ( in the GUI) to change.

MAYBE there is also a Config file in FS2020 where users can beat the System by a trick.

@pizman82

thanks for you reply, and I know the different between fsuipc and xpuipc today.