MobiFlight Community Support

Hi,

I would like to add a Master caution, Fire warning and Sixpack recall button for my PMDG 737 NGXu under Prepar3d by using mobiflight. I suppose that is possible? Are there any good Youtube videos or websites explaining how to do exactly that(!) with regards to hardware wiring and software configuration ?
I would like to avoid to read through thousands of manuals giving me the basic knowledge but not explaining how to realize the 3 needed buttons.

Thanks!

Best regards Andi

HI
Your request is not so easy like it seems....
Sure i can give you the needed raw data to do this ( Offsets and Inputs).... And i will do on the End of this Posting

Are there any good Youtube videos or websites explaining how to do exactly that(!) with regards to hardware wiring and software configuration ?

If i should explane you "hardware wiring" and "software configuration" then we are back in a 100+ Page Manual !
I will say.... There is no way to build a Panel without learning the "basic knowledge".

It´s like you ask me to give you a short guide how you can drive to the next BurgerKing. I can tell you the routing and i can also explane you should not drive faster then 35 MpH
But this require you know traffic rules, got a driving licence and you understand how to handle your car ALREADY!

Means.... Learn the basics ... else you will not get successfull!

****************
Needed Offsets for your request:

OUTPUT:

6504 1 BYTE WARN_annunFIRE_WARN (CPT) Boolean
6505 1 BYTE WARN_annunFIRE_WARN (FO) Boolean
6506 1 BYTE WARN_annunMASTER_CAUTION (CPT) Boolean
6507 1 BYTE WARN_annunMASTER_CAUTION (FO) Boolean
6508 1 BYTE WARN_annunFLT_CONT Boolean
6509 1 BYTE WARN_annunIRS Boolean
650A 1 BYTE WARN_annunFUEL Boolean
650B 1 BYTE WARN_annunELEC Boolean
650C 1 BYTE WARN_annunAPU Boolean
650D 1 BYTE WARN_annunOVHT_DET Boolean
650E 1 BYTE WARN_annunANTI_ICE Boolean
650F 1 BYTE WARN_annunHYD Boolean
6510 1 BYTE WARN_annunDOORS Boolean
6511 1 BYTE WARN_annunENG Boolean
6512 1 BYTE WARN_annunOVERHEAD Boolean
6513 1 BYTE WARN_annunAIR_COND Boolean

INPUTS:

EVT_FIRE_WARN_LIGHT_LEFT 69979
EVT_MASTER_CAUTION_LIGHT_LEFT 69980
EVT_FIRE_WARN_LIGHT_RIGHT 70071
EVT_MASTER_CAUTION_LIGHT_RIGHT 70070
EVT_SYSTEM_ANNUNCIATOR_PANEL_LEFT 69981
EVT_SYSTEM_ANNUNCIATOR_PANEL_RIGHT 70069

In case all are momentary Buttons the correct Parameter "should" be Leftclick Single (536870912)


If you get in trouble.... Simple ask again with the deatailed problematic situation..... Then i try to help !

Thanks for your help!!!

I will wait until the hardware is delivered and report back if it worked

I received my arduino board today and already found some time to dig a little bit deeper with the aid of your website tutorials.

Unfortunately I do not understand where to enter the output offsets for the lights.
E.g. for 6504 1 BYTE WARN_annunFIRE_WARN (CPT) Boolean

Basis Einstellungen:
Offset: I suppose 0x6504 here?
Wert Typ: Int?
Maskiere Wert mit: ?
Größe in Bytes: i guess 1?

Should I leave the rest untouched?

The input wizard is clear to me.
Thanks!

Best regards Andi

Hi Andi,

this offset is a bit special. In this case you see a [2] after the offset name. That means that you have two offsets. One is for the CPT and one for the F/O.
For the output you assume right, that is offset 6504, 1 byte INT. Correct also to let the bitmask untouched. This is for the CPT.
For the F/O you have offset 6505, rest is the same.
Then change to the display tab and choose the module and use "pin", below you choose the device which you have setup in the devices you upload to your mega.
At the bottom you can then press the test button and your led should light on.
That's it.
You can also contact us at Discord: https://discord.gg/99vHbK7

Additional Note:

What Stephan Said is correct..... But in case you said you have no knowledge i still "clearup" this in my List i send to you..... There the X2 (2) is no longer shown. and i already write CPT and FO to it.

6504 1 BYTE WARN_annunFIRE_WARN (CPT) Boolean
6505 1 BYTE WARN_annunFIRE_WARN (FO) Boolean

About the other question..... THATS are the basics i talk about!.

You ask what INT mean..... INT is "Integer" and its one of 3 different Data Typs next to FLT (Float) and STR (String)
INT means a Full Number .... like 1,2,3,4,5, -123 , -9999,
FLT means a Deciamal Value.... like 1,234 -- 0,0004 -- 9999,1
STR means a "Text" .... like HELLO , 1A2B3C , AlphaBRavo

The Size is 1,2, or 4 Byte for INT , 4 or 8 Byte for FLT , and minimum 2 Bytes or MORE for STRING.
So you know.... "1" Byte size MUST be a INT, cause it´s the only kind that can be "1".

Also the other settings.... You not need them here.... But its pretty usefull to know what BCD means or what "Bitmask" means.


I recommend.... You not need to read books for 5 years to build a homecockpit..... But simply use GOOGLE.... If you not know what INT means.... Put it in.
The first hit is..... https://en.wikipedia.org/wiki/Integer_(computer_science)

So not "learn" in the dark everything.... BUT invest some hours to learn exact that stuff you get stuck at the moment and you need to understand to get a stepp forward !

AND
Feel free to join our Discord.... We help ( Via Voice and shared screen) as best we can.

Firstable thank you for your great support guys!!

I'm still waiting for my 737 Engine control panel, IRS Panel, AFDS panel and Sixpack annunciators to be delivered.

Meanwhile I already looked up the right offsets and events for the PMDG NGXu. I think I found all of them except the light offsets for these 3 buttons:

EVT_DSP_CPT_AP_RESET_SWITCH 339 69971
EVT_DSP_CPT_AT_RESET_SWITCH 340 69972
EVT_DSP_CPT_FMC_RESET_SWITCH 341 69973

I would be very thankful if you could give me a hint here!

Best regards Andi

Hi again.

Simply check the Document that is included in your FSUIPC Folder..... "Offset Mapping for PMDG 737NGX and 737NGXu.pdf"

6550 1 BYTE MAIN_annunAP CPT
6551 1 BYTE MAIN_annunAP FO
6552 1 BYTE MAIN_annunAT CPT
6553 1 BYTE MAIN_annunAT FO
6554 1 BYTE MAIN_annunFMC CPT
6555 1 BYTE MAIN_annunFMC FO
....
6C0C 1 BYTE MAIN_annunAP_Amber CPT
6C0D 1 BYTE MAIN_annunAP_Amber FO
6C0E 1 BYTE MAIN_annunAT_Amber CPT
6C0F 1 BYTE MAIN_annunAT_Amber FO

And to include Stephans Information with the x2 (2) Notes....
In the original List is written e.g.

6C0E 2 BYTE X 2 MAIN_annunAT_Amber[2] Boolean

i just split it already up into the 2 Offsets for you....

6C0E 1 BYTE MAIN_annunAT_Amber CPT
6C0F 1 BYTE MAIN_annunAT_Amber FO

Great. Thank you for the hint!

Hi,

the hardware finally arrived, but I unfortunately I'm not able to get a light or switch to work with the NGXu
I'm using FSUIPC 6.0.11. I suppose that is fine?

I started with the EEC panel and tried to realize the following
input: EVT_OH_EEC_L_SWITCH Event ID 69900
output: ENG_EECSwitch[2] 6430

I created the output light under settings - modules section on PIN 3 (PWM) (Does it matter if I use PWM ports or not? I suppose that is ok or?)
And I created a switch for the EEC button on PIN 2.
I uploaded both successfully to the board!


Then I created a new line under Output and opened the wizard. Under display I can press test and the light comes up. So hardware wiring is ok
Under FSUIPC I entered the following values:

Offset: 0x6430
Wert Typ Int
Größe in Bytes: 1
Maskiere Wert 0xFF
Check at Transform $

Under input I opened the wizard and went to the input tab.
I selected the switch and entered for
ON Press:
PMDG - Event ID
Preset laden 737
EVT_OH_EEC_L_SWITCH and clicked OK
That filled in Event ID 69900
I chose further Maus Param: MOUSE_FLAG_LEFTSINGLE
I entered exactly the same for ON RELEASE.

When I click the Button/Switch I can see a tiny LED light coming up on the arduino board (MEGA 2560 R3) so the hardware switch seems to be ok as well!

I saved everything and closed Mobi Flight Connector.
Then I loaded the newest NGXu under P3D 5.1 and opened Mobi Flight Connector again.

I clicked Start in Mobiflight and noticed that I had all 3 green check ticks for Module, FSUIPC and SimConnect.

But now nothing happens inside P3D
Clicking the hardware button does not click it inside the NGXu and activating the light inside the NGXu does not activate the light on the hardware panel.

I'm a little bit lost here right now and hopefully you can help me.
And not to forget..SDK Data Broadcast is enabled under NGXu Options.ini file. FSUIPC is working fine for several other programs.

Thank you very much!

Best regards Andi

Really embarassing. I just saw that the tick box beside the input and output lines was not set.
That helped
Working fine now.

Yeah....

But just to include a important thing.... Take care about the "Switch" Offsets !!!

In this situation it was right.... These "Korry" Switches have 2 Functions.... ( 2 LED in the switch.... Like 2 Chambers, one on upper half and another on lower half)
The "upper" show a White "ON" Text.... The Lower show a Amber "ALTN" Text.

For the lower ALTN the correct Offset is "6436 2 BYTE x 2 ENG_annunALTN(2) Boolean"
For the upper ON we have no own Offset.... BUT we can use here ( as you do) the Switch Position Offsets.... Cause ON should simply light if switch itself is in ON Position !

For other System this is not a good solution, if there exist own Offsets for the LED itself....

For example the FD in the MCP.....

6533 2 BYTE x 2 MCP_FDSw(2) Boolean
...
6538 2 BYTE x 2 MCP_annunFD(2) Boolean

"annun" means Annunciator .... "Sw" means Switch
The "annun" show the real status of the LED...... the "sw" just show the position of the switch !
The FD is a perfect example.... Cause it not have to light if the Switch is ON ( if e.g. First Office Side FD is master )

So.... Always check if there is a "annun" Offset. The "sw" are only used for stuff that have no "own" Offsets!

Hi,

I'm making really good progress!!

Currently I have 3 problems left.:

1. Engine Control Panel EEC
I think this is the problem you described above. The P3D NGXu has 3 positions.
a) No light on the switch = EEC Off
b) ON Light = EEC On
c) ALTN Light = Alternate Mode on.

However on my hardware panel I see an "ON" Light for a) and b) cases
So when the NGXu EEC is off I have the FSUIPC value 1 which brings up the light on the panel. What do I need to do to get the light off in case a) ?

2. IRS Align Panel
My biggest problem. What do I need to set to get the 2 rotaries for L and R IRS working?
Currently I have it as switch with "FSUIPC Offset" 0x642B (Left) and 0x642C (Right) with Setze Wert 0 oder 1 oder 2 oder 3.
That doesnt work


3. AFDS Panel
All working except the Test 1 and 2 Switch. What are the event Ids or offsets for this one?

Thank you very much!

PS: Is it ok to write german here or shall we continue to write in english?

At First....
German is OK.... Whatever we prefer English..... Simply in case that other poeple with the same problem can easy read it.
I recommend.... Join our Discord.... Put a Headset on. There we can "talk" via Voice. For sure in german !

1)
As written above.... I already give you the 2 Offsets.... I not beliveve it show "1" whatever it should be OFF. Make no sense on first view.
In theory there are formulas to change this.... E.g. if a LED must light ( OFF LED´s) when Offset is "0" .
But in that case i´m pretty sure this is not the point !
So check again the Offsets!. This "should" work..... If not we will check via Discord !

2)
This can NOT work!..... these are OFFSETS. PMDG not allow to write Offsets....: these are the "outputs". Inputs ( so controlls to the aircraft) are done ONLY with EventID´s

EVT_IRU_MSU_LEFT 69887...... EVT_IRU_MSU_RIGHT 69888

Pretty sure with Paramter 0,1,2,3,

3)
Try this....

EVT_DSP_CPT_DISENGAGE_TEST_SWITCH 69974

Summary: Come to Discord.... there we can solve those things much more easy !

Great...point 2) and 3) are working perfectly now
Thank you!!!

However point 1) stays a mystery for me.

Here is a picture showing my offsets and FSUIPC values. On my hardware panel both(!) ON lights are on.
In the sim not!

https://drive.google.com/file/d/1CM1P6RYzsJ8lWFYJNcoHjk0eXaLNYIoS/view?usp=sharing

Maybe we can get this working via the forum. Otherwise we can try it via Discord.
However I have not yet used this program and if possible I would rather renounce on it.