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
palsoft
Posts: 8
hi
I have done my first basic setup following your parking brake example on YouTube.
I have tried to do the same thing with another LED A/T ARM but I have not found any FSUIPC presets, so I used Offset "0x6538", value type "int" Size in bytes "2" found in the "Offset Mapping for PMDG 737NGX.pdf ". I do not find any document on the web that says "mask value with" and i used "0XFFFF". In "Display" I have taken the test, the LED lights up, but when I use "shift R" in fsx to see if the LED lights up, nothing happens. Use of course PMDG 737NGX. and arduino mega 2560 rev 3.

Thanks
[Last edited by palsoft, 2017-03-10 23:28]
2017-03-10 21:19
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Hi
Welcome to Mobiflight !

1. Important. PMDG is different as FSX Standard. You need different Offsets and technics to work with !!!

The Standard Offset for AT Arm is 0810 4 Byte INT (This is for Standard FSX Aircrafts...NOT for PMDG)

The Offset for PMDG 737 is 653A MCP_annunATArm 1 Byte INT Boolean
(Youre used offset 6538 is for the Flight Directors !)

AND REMEMBER.... You need to open Datalink before you can use PMDG Offsets.....
Read the Manual in the PFD you got....

iconQuote:

To enable the data communication output from the PMDG aircraft, you will need to open the file
737NGX_Options.ini (located in the FSX folder PMDG\PMDG 737 NGX, and add the following lines
to the end of the file:
[SDK]
EnableDataBroadcast=1



At Last.... Information about Bitmasking and why some Offsets got 2 Bytes and so on are already anwnserd in this Board. Please use Search Engine.
If you not found help just ask. we will help you !
Good Luck !
2017-03-11 02:09
Avatar
palsoft
Posts: 8
hi
sorry my mistake in fact I used offset 0x653A MCP_annunATArm 1 Byte INT Boolean as provided in "Offset Mapping for PMDG 737NGX.pdf".
data communication output from the PMDG aircraft already done, but the LED still does not light up when active A/T ARM from FSX, as does parking brake. The same thing happens with 0x6538 Byte x2 MCP-annunFD [2], the LED does not light up.
What I m doing bad?

Many Thanks!

Regards
2017-03-11 19:04
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Hi Again

Its difficult to awnser youre question, without see youre config. There can be multiple issues that let the LED not light up.

By the way...
Offset 6538 is not a 2 Byte Offset .... Its a 1 Byte offset (x2) That Means.... The first Byte (Offset 6538) is controlling the FD LED (I think on left) AND th second Byte (Offset 6539) is controlling the FD LED (On right First officer side)


**********

To help you i need more informations !

Does your LED work and is correct wired to Arduino AND is setup correct in the Settings/Mobiflightboard/Device section ?
In Other Words..... Does THIS Led on THIS Board working if you use the "Parking Brake Example" ????

If yes we can exclude a Hardware Issue and just need to check the software part !

**********
You said you already did the data comunication Entry in the ini File. Please recheck and confirm this is 100% Correct. If you install the FSX/PMDG in the /Programmfiles(x86) folder for example maby youre save was not posible cause you got no write permission there.

To check if Data Output is working please Look in the the Mobiflight Main Screen.... Open the Output section and run youre Config.
Then use the Switch in the PMDG and look at the Config line in Mobiflight if the value change from 0 to 1 or 1 to 0 when the virtual LED in the Simulator is goin on or off.

Please report experience !
Good Luck !
2017-03-12 00:35
Avatar
palsoft
Posts: 8
well, I reinstalled FSX, it was in Programmfiles (x86), now in C: /, confirm [SDK]
EnableDataBroadcast = 1 in 737NGX_Options.ini.

HI
I have done again basic setup Following your parking brake example on YouTube. The LED works as it should, in the config line in Mobiflight the value change from 0 (LED off) to 32767 (led on) both for FSUIPC value and for Output Value, the same thing in FSX Led Change on / off

I did the same process for the LED MCP_annunATArm 0x653A 1 byte in configWizard when I did the test the LED lights, with stop switches off. In the Mobiflight Main Screen when clik on Test the led Blink repeatedly came off when stop. When clik on Run unlike parking brake, the LED of A/T ARM comes on and stays on until clik stop (in FSX is off) at the Config line FSUIPC = 200 and Output value = 200

the same with 0x6538 with Test works with Run no, FSUIPC value = 0, Output value = 0

0x6539 the same thing

I do not know how to proceed

tks
2017-03-14 10:55
Avatar
palsoft
Posts: 8
I'm using windows 10, FSX (is in windows mode)

I used the following configuration
LED parking brake offset 0x0bc8
LED A/T ARM offset 0x0810
LED F/D CMD Offset 0x2ee0
they work as they should for ACFT standards

with Ifly
LED parking brake offset 0x0bc8 works well
LED A/T ARM offset 0x0810 He works now and then
LED F/D CMD Offset 0x2ee0 works well

with PMDG
LED parking brake offset 0x0bc8 works well
LED A/T ARM offset 0x0810 not working
LED F/D CMD Offset 0x2ee0 not working

when offset change from 0810 to 653A (LED A/T ARM) and press RUN the FSUIPC value and Output Value go to 200 and the LED goes steady on

when offset change from 2EE0 in 6538 (led FD CMD) and press RUN the FSUIPC Value and Output Value go to 0 but the LED does not turn on "CTRL + F"

I do not know how to proceed

tks
2017-03-14 22:35
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Hi Again !

I think you mixed up lots of different things here.... This is verry confusing !

Lets try to seperate this !

1. You install the Programm new out of /porgrammfiles(86).... this is good. You not need to install fresh maby... You still can use Admin rights to work with.... But now this Problem is fixed already !

2. As I told you..... FORGET the Standard Offsets when you work with a AddOn.... If you use PMDG use ONLY the PMDG Offsets ! Not try to work with Standard Offsets !
I Know the Parking Brake works already...But this is a real eception....

3. I-Fly..... the IFly itself will use maby again other Offsets like PMDG and Other Offsets liek Standard Planes.... I real recommend you to decide for one Aircraft/AddOn and then workout a Config for this. Switching between Ilfy, Standard and PMDG with one Homecockpit is not posible !!! ( Only if you make a different Configs for every Plane each !)

4. Test Mode. the TestMode in Main Screen ( Upper Task near Play and Stop Button ) is just to test the LED if they working and not broke.... This not means youre config is working fine..... this just show if LED is ok.

5. Wrong Value in PMDG ( Value 200)
iconQuote:

when offset change from 0810 to 653A (LED A/T ARM) and press RUN the FSUIPC value and Output Value go to 200 and the LED goes steady on


I can´t reproduce this but i´m pritty shure you just use the Preset for 0810 ( with 4 Bytes) and simply change the OffsetNumber to 653A BUT you not change the Size from 4 Byte to 1 Byte (653A is only a 1 Byte INT ) .... So the Value is 200 in that case.
NOT Use Presets and change them.... Build a Config for PMDG always youreself !!

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

Solution:

Please forget Standard Planes and Ifly and only work with PMDG for the Moment ! ( Or another but pleas not MIX them until you know the technics !! )
Try to Config the 4 Items (Parking Brake, AT-ARM, FD Cpt, and FD FO )
Use Only PMDG Offsets for this and take care you use the right Size of Bytes.

I´m shure this workes !! If not please contact me via Mail Pizman@freenet.de Send me your mcc File.... I will check it four you !
Good Luck !
2017-03-15 00:42
Avatar
palsoft
Posts: 8
Hi Again Pizman82

the PMDG offsets still do not work, confirm that happens only to me?
Anyway, I sent you an email, would you confirm you have received it, otherwise I send it again
p.s.
explain this please:
if($>=0,$-1,359)
and this:
if($<=359,$+1,0)


tks
Antonio
[Last edited by palsoft, 2017-03-19 23:00]
2017-03-19 19:44
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Hi Antonio

Sorry. No Email arrive.... Not in Spam folder, too.... Maby blocked by my Provider.... Please try again.... pizman@freenet.de
If Posible please attach two files to the mail......
1. The MCC File of your Mobiflight Config with the problematic Outputs ( save youre config and send me this file )
2. The PMDG 737NGX_Options.ini ( Just to confirm youre entry is 100% correct.
And please Tell me short your Boardname palsoft in the Header... so i know who i talking to.

**********

To the second Question..... THIS is a IF Function build with the expressions Engine of Mobiflight....
((Look here in the Manual for more information https://www.mobiflight.com/en/documentation/software.html#Expression-Engine ))

For example...
if($>=0,$-1,359)
This means.... IF Value of Offset is bigger then Zero THEN subtract ONE from this value .... If NOT (So Value is not bigger then Zero) then set Value to 359

This example is used for an Encoder to set the Autopilot Heading.... If encoder is turn left it should decrease the value by 1.... From 180 to 179 for example.
The If here is needed cause if we say simply $-1 it would be set 0° not in 359..... With $-1 it will say 0-1 = -1 and then -2 -3 -4 and so on.
With this IF function we get shure it change from 0 to 359
The Second formula is simply the opposit.... this is used for the Increase Value with a right turn of Encoder. So Value go from 359 to 0 and not to 360, 361 362 ....


*********

Hope youre question is awnsered..... Looking forward to youre mail....
Good Luck !
2017-03-20 01:36
Avatar
palsoft
Posts: 8
hi Pizman82

thanks I sent the email again, waiting for you

many thanks for the explanation

antonio
2017-03-20 12:44
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Sorry for Of topic.... but we got no Whisper Tool here

Hi Antonio
I not get youre mail again.... Please check for the correct adress....
Maby you give me youre adress so i can start contact.

thanks
Good Luck !
2017-03-21 07:32
Avatar
palsoft
Posts: 8
hi pizman

thanks I sent the email again, this is my email :gmari@email.it or aryenkiss@gmail.com, I used them both to pizman@freenet.de

p.s.
I take this opportunity to let you know that I used two encoders ky040 with a switch and I found that this increases but not decreases, I have used GND, 5V, clk, DT no SW. while EVE-KE2F2024B works fine standard fsx

ciao antonio
2017-03-21 18:42
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Hi

I send you an email now. Hope it workes if i start contact... ( Not understand why i get no mails from you.... Spam folder empty, too )

To youre Problem....
Normaly the ky040 should work in MF, too.

Problem is i not see what you do....
Maby a electrical Problem.... Wrong Pin setting .... Wrong 5v/Grd use.... Soldering issue ( short circuit)
OR
A Software issue in youre config.
Question is.... Does Mobiflight receive the Commands from the Encoder when you turn it left (decrease)
You can check this with logging mode on (Debug) in the setting tab. Now there is a logging Monitor below the Main Panel. Here you see if "On Left" is checked by Mobiflight

Please confirm you use correct commands, too.... In PMDG the Encoders NOT work with Offsets ( Like youre if($>=0,$-1,359) ) PMDG need it´s OWN EventID for every Input function.... The Standard Event ID from FSX already NOT working with PMDG !

By the Way.... Does youre basic problem with Output Readouts now is solved ??
Good Luck !
2017-03-22 08:13
Avatar
palsoft
Posts: 8
hi Pizman

I sent you an email, I hope you have received it ky040 encoder still does not work.
See you soon hopefully with good news
antonio
2017-03-22 23:50
icon