MobiFlight Community Support

Hello ALL:

I'm sorry if my doubt sounds too stupidy but I'm relatively new in MobiFlight and I do need your help on this:

I'm working on a home-made Overhead that has been working pretty fine with my PMDG 737. I am using MobiFlight to manage its lights.
The problema begins when I tried to use it with my PMDG 777.
For instance: on 737 one of the FuelPump light's offset is 646A, so I simply puts 0x646A on the offset field and it is ok.
On the 777, however, the left forward fuel pump light offset is 69632 + 103 and it is a single bit.
My understand is that 69735 is the decimal offset of the byte where the first bit controls the light I want. Is that correct?
So I've converted it to hex and used the value 0x11067, but it does not work. I'm sure I missed up something but I can't figure out by myself.

thanks,

Decio Pedroso

Hello decioapn,

Welcome to MobiFlight!

There is a difference between EventIDs and Offsets. With the EventIDs, I set something outside the Sim and share it with the simulator (input from the point of view of the simulator), e.g. through a switch. The offset, in turn, reads something out of the sim, so it is an output, e.g. an annunciator (output from the point of view of the simulator).
You must not commit the error and make an offset from an EventID. That can not work. In the exhaust of a car, you can not fill up with fuel - at least that does not fill the tank - so it makes no sense.
So it's always important to distinguish what I want to do. Setting something in the sim from the outside is done with an EventID and something out of the sim, always with an offset. Therefore you can not write on an output and not read from an input.
To see the difference directly, EventIDs are always decimal and offsets are always hexadecimal.
The EventID 69735 is thus always an EventID, ie an input, and can never become an offset 0xABCD. You should also have noticed that offsets are always four digits after 0x, never 5 digits. By then you would have left the conversion.
Certainly the data are internally converted to hex, but this has no influence on the external data evaluation (event = dec, offset = hex).

Your example 69735 is an input, so it can be used to set the LED. For the indication of the condition of the LED you need an own offset which you have to find out from the list.

Just as there is a separate table for the PMDG 737 NGX for both the EventIDs and the Offsets, this list is also available for the PMDG 777. The respective values ​​may or may not be identical. This is already evident from the different textual names in the lists.

I hope you understand the basics of handling EventIDs and offsets and can now complete your work successfully.
If you have further Questions, don't hezitate to ask!

Hi

At PMDG 737 the FuelPump Fwd Low Pressure Light is offset 646A ( 2 Byte for two Lights ) So 646A is Light 1.... 646B is Light 2. All Correct !

On the 777, however, the left forward fuel pump light offset is 69632 + 103 and it is a single bit.
My understand is that 69735 is the decimal offset of the byte where the first bit controls the light I want. Is that correct?

THATS the INPUT .... Not the Output ! And its not a BIT its a EVENT ID !
69632 + 103 = 69735 ... And THATS The Event ID like you can find in the List....

Code:

EVT_OH_FUEL_PUMP_1_FORWARD----- 103 ---- 69735

You can use it with Parameter for mouse actions like all other inputs, too.

For the OUTPUT of that LED you need like in the 737, a FSUIPC Offset List for the PMDG 777 ... Its located in the /Modules Folder of your FSX (Offset Mapping for PMDG777X.pdf)
Here you find the corrrect Offset: 64B1 .... Fuel Low Press Fwd 2 Byte for 2 LED.... So... 64B1 for Light 1 and 64B2 for Light 2.

NOTE: PMDG use same Offsetrange for all of its products.... But every aircraft got a own logic and sequence.... So you need different mcc Config Files for each aircraft !
Have Fun !

Double awnser.... It start again

and can never become an offset 0xABCD. You should also have noticed that offsets are always four digits after 0x, never 5 digits.

I think thats basicly a good hint for him.... BUT Thats "maby" not correct meanwhile.
I not use FSUIPC 5 ( cause i not own P3Dv4 until now) ... BUT thats a 64Bit Version of FSUIPC..... So it should be possible to work with 8 diggit Hexa Codes there....
Same is also possible with XPUIPC allready !.

So thats just for Information..... Your correct a Decimal Number mostly shows a EventID.... BUT Offsets can have 5 (or more) Numbers , too! ( Hope thats affirmative)

First of all, thank you, guys for so many replies in so short time.
Now I did got that the address I was trying to use was actually an EventID and not an offset. That was mainly because I couldn't find the 777 offset table that I easily got for 737.
Now I found it under Modules folder.

Thank you again and Merry Christmas. HO-HO-HO

Great, that you found the list by yourself!

That is real learning

Actually, pizman82 deserves the credit for telling me where to find it.
But it is all learning!

By the way my overhead prototype is now working for T7 as it was for 737 NGX

Thank all of you again.

Decio Pedroso