MobiFlight Community Support

Welcome to the forum for MobiFlight! Feel free to reach out to the community in case you have questions, issues or just want to share great ideas or details about your latest home cockpit project.

You like MobiFlight? Donate via PayPal and support the MobiFlight development. Thanks! 

05/03/2024 - This forum is read-only

The community support for MobiFlight has moved exclusively over to our Discord server. Register for free and enjoy more interactive functions like image and video upload, voice chat. More than 7,000 registered users around the world make it a great experience!

See you on our MobiFlight Community Discord server.

A HUGE Thank You to everyone who participated in the forum, especially obviously to Pizman and Stephan who did an outstanding job over so many years providing an incredible service to the MobiFlight community.

The forum is still providing a lot of good content, hence we keep this information accessible.

icon
Avatar
dtravlos
Posts: 6
Hello.

I have a problem with my rotary encoder. It just DOESNT work. I tried with crs and ias event id with both left/right click and wheel up/down but nothing is happening on the mcp. I opened the fsuipc console log and I see that the events are sent correctly. Any ideas please?

Thanks
2017-11-21 00:02
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Hi.

icondtravlos:

I opened the fsuipc console log and I see that the events are sent correctly.



So that mean Mobiflight work fine....
You can also check this with the Logging Mode of Mobiflight itself.... Set "Logging Mode Enable Typ Debug"
Then you got a Textstring below the Main Mobiflight Window..... there you can see if Mobiflight detects a "Left" and "Right" AND you see if a Config is executing a command correct.

Simply solution..... If your Commands arrive FSUIPC ( You confirmed with the FSUIPC internal logging9 THEN your used Events or Offset settings are simply wrong !

Please check.... WHAT aircraft do you use ? .... StadardEventID or FSUIPC Offsets are ONLY for Stock Aircrafts.... AddOns mostly work with own systems !
For example PMDG use 98% of Inputs and Outputs NOT from FSUIPC.... You need the PMDG Offsets and Events here!
Good Luck !
2017-11-21 07:16
Avatar
dtravlos
Posts: 6
Thank you for you reply and sorry for the incomplete info. I use the pmdg 738.
The Event ID I sent is 84132 for the left course. For left I use left click param, right = right click param, left fast = wheel down and right fast = wheel up.

MF Log:
iconCode:
11/21/2017 10:07:55 AM(865): Executing OnRight: E CRS@SN-413-fd4
11/21/2017 10:07:55 AM(856): Config found for button: E CRS@SN-413-fd4
11/21/2017 10:07:52 AM(942): Executing OnLeft: E CRS@SN-413-fd4


FSUIPC Log:
iconCode:
771594 *** EVENT: Cntrl= 84132 (0x000148a4), Param= 536870912 (0x20000000)  <84132>
771781 *** EVENT: Cntrl= 84132 (0x000148a4), Param= 536870912 (0x20000000)  <84132>
773000 *** EVENT: Cntrl= 84132 (0x000148a4), Param= 536870912 (0x20000000)  <84132>
773985 *** EVENT: Cntrl= 84132 (0x000148a4), Param= -2147483648 (0x80000000)  <84132>
776469 *** EVENT: Cntrl= 84132 (0x000148a4), Param= -2147483648 (0x80000000)  <84132>


BUT when I left click on the crs encoder I get this:
iconCode:
877985 *** EVENT: Cntrl= 65716 (0x000100b4), Param= 36 (0x00000024) VOR1_SET


I tried as well with 65716 but with no luck :(
2017-11-21 09:06
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
:scared:
You mix up a lot my friend.....

1. Used EventID 84132 is WRONG ! This is a "SET" Event..... Not a manipulating Event !
With THAT you can send for example parameter 123 and then the CRS is SET direkt to 123° .
But this is NOT used for the Encoder you need.

2. The Located Event 65716 is also WRONG, too.
THIS is the VOR1 SET Event from FSX Standard Aircrafts... Strange that this is logged when you push the Button in the Sim.

******

3. The Correct EVENT ID....
For PMDG 737 CRS CPT please use ID .... 70008 ..... You find a full List in Internet... Simply Google!

4. Please also get shure that you have a UP TO DATE FSUIPC and PMDG..... FSUIPC newer then 2016 ..... PMDG must be Servicepack 1d DELTA !

Have Fun !
Good Luck !
2017-11-21 09:53
Avatar
dtravlos
Posts: 6
Thank you very much! It worked! The only problem is that the rotation is not so good... If I move very fast the encoder the value is not changing. But I can deal with it I think.
The next thing is to make the switches work as well :P
:D

EDIT: Nop I think encoder lags so much and the values are not updated normally :(
EDIT 2: Also, I noticed that my encoders are sending a value per 2 detents.
[Last edited by dtravlos, 2017-11-21 13:51]
2017-11-21 13:42
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
First.... The 2 Detents...
If you encoder work with a other logic like 1:1 of "Signals per Detent" then it is a problem..... Pretty shure you got a 1:2 Encoder.
Result is that only every 2nd detent is send a command.

At the moment we BETA Testing a new tool to update the Mobiflight code for those Encoders.... Pretty shure in the near future this get implement and then you can solve that fact..
If Not you fanaly can buy a 1:1 Encoder.... then it works perfect already!

****
The Delay.

In PMDG we need to work with EventID.
A Event must be execute "verry" Difficult. it must be write to 2x4 Byte Offsets.... Then FSUIPC must Read this offsets and must execute it itself..... then PMDG must "see" this command and set the input finaly..... Thats maby 3-4 times more "work" like a simple Offsetwrite in Standard Aircrafts !
At a Button you push single... and that maby every 30 seconds thats abolutly no problem..... BUT A Encoder that is turning fast will execute maby 10 or more Commands in one second. .... If this are Events you reach the Limit what your system can do !
You can try to change the "FSUIPC Polling" in the Settings.... Test this out if this is better.

****
The Missing on Fast !
Thats a part of Problem 1..... The 1:2 Detents.... If only every 2nd detent is checked its difficult to turn it "Fast"
This Problem is solved already if you use a 1:1 Encoder or if our softwareupdate is implement in the future to make this working!

**********
Solution for now....
I recommend to NOT use the Left and Rigthclick parameters. ONLY Use the Mousewheel parameters.
Try it for On Left and On Right ( And let the FAST Entrys empty )

In PMDG the Mousewheel Command look like that it increase the value faster if you turn the encoder faster.... Maby a internal Logic. Please try out !
Good Luck !
2017-11-22 08:24
Avatar
dtravlos
Posts: 6
Thank you very much!
2017-11-22 21:38
icon