MobiFlight Community Support

Hi all

First of all I wanted to say thank you for creating and supporting such a great project

I am building myself an autopilot console, with Alt, Spd, and Hdg displays and encoders. I have knocked some hardware up and the displays are working without issue (at least in the 787).

The main issue I have is with the encoders - more specifically the effect of the Event IDs... For example, AP_SPD_VAR_INC sometimes increases the speed by 1, sometimes it increases it by 10:

2750250 WRITE0[16064] 3114, 4 bytes: 01 00 00 00 ....
2750250 WRITE0[16064] 3110, 4 bytes: 68 01 01 00 h...
2750281 *** EVENT: Cntrl= 65896 (0x00010168), Param= 1 (0x00000001) AP_SPD_VAR_INC
2750281 Monitor IPC:07E2 (U16) = 190
2750281 SimRead: 07E2="AUTOPILOT AIRSPEED HOLD VAR"
INT32: 190 (0x000000BE)
2752969 WRITE0[16064] 3114, 4 bytes: 01 00 00 00 ....
2752969 WRITE0[16064] 3110, 4 bytes: 68 01 01 00 h...
2753000 *** EVENT: Cntrl= 65896 (0x00010168), Param= 1 (0x00000001) AP_SPD_VAR_INC
2753000 Monitor IPC:07E2 (U16) = 200
2753000 SimRead: 07E2="AUTOPILOT AIRSPEED HOLD VAR"
INT32: 200 (0x000000C8)
2754297 WRITE0[16064] 3114, 4 bytes: 01 00 00 00 ....
2754297 WRITE0[16064] 3110, 4 bytes: 68 01 01 00 h...
2754328 *** EVENT: Cntrl= 65896 (0x00010168), Param= 1 (0x00000001) AP_SPD_VAR_INC
2754344 Monitor IPC:07E2 (U16) = 210
2754344 SimRead: 07E2="AUTOPILOT AIRSPEED HOLD VAR"
INT32: 210 (0x000000D2)
2755484 WRITE0[16064] 3114, 4 bytes: 01 00 00 00 ....
2755484 WRITE0[16064] 3110, 4 bytes: 68 01 01 00 h...
2755500 *** EVENT: Cntrl= 65896 (0x00010168), Param= 1 (0x00000001) AP_SPD_VAR_INC
2755516 Monitor IPC:07E2 (U16) = 211
2755516 SimRead: 07E2="AUTOPILOT AIRSPEED HOLD VAR"
INT32: 211 (0x000000D3)

Can anyone help me to resolve this?

Thanks in advance

Hi

You see in the Logging..... MF send EventID in all 4 testings in the same way.... So all is fine from our side.
Maybe this is a feature from FS2020 we not understand or this is a bug in the FS2020 version (maybe simconnect or FSUIPC7)

On first view i would say..... Try the standard Parameter. Execute Events are used normaly "0" Zero ( not 1 like you do).
Confirm Problem occure also with "0".

Also confirm if the turning speed ( the time between 2 events) have a effect to your problem.
In theory this can be a feature to make "fast increase" posible.... So "If multiple commands are done in a fast sequence THEN Increase by more then 1 (e.g. 10) "

Thanks for the reply.

I ended up with parameter as 1 just to match the log when performing the action using the mouse on screen. Also tried speed of rotation and there is no pattern.

As you say, seems it must be a problem with FS2020 or FSUIPC7 because it all works fine in the twin prop diamond.

Question for you... what USB controls are you using? Do you see different behavior when different controllers are plugged in?

I ask because I was playing with HEADING_BUG_INC/DEC and they were operating by 1 initially.

Then when I got my Honeycomb Alpha yoke, it switched to 10 per step.

So, I've been wondering if there is something wrong in the profile for that yoke (or maybe others).

hello, im currently having the same issue. Mobiflight runs faultless until i plug in my honeycomb throttle. At which point the heading starts to act erratic. It seems like the honeycomb interferes with the comands or even overwrites the information. Very fustrating for a £250 throttle, was going to buy the yoke but im holding off now. rather have mobiflights functions than a cool yoke lol.

I wondering....

I got the Alpha.... No Problems.
And we also have some users with Bravo... No Problems reported expect this here 1,5 years ago.

Maybe we can check this via a Discord Live Seasson.
I not see the situation but this sounds to me like a fault in the settings of the Honneycomp or in the MF Configs.
On first view the situation should work without any problems !