MobiFlight Community Support

Hello,

I do my first trial with MobiFlight, but I must be missing something I followed the first simple tutorial, but I can't get my LED lighting up when I switch on the Landing Lights of a Cessna in FSX (I used this simple airplane to start with).

Here is my setup:

• I have FSX (steam) running
• FSUIPC (registered version) is running, and I am able to see it in the Add-On menu
• MobiFlight is connected with my Arduino Mega - both "Modules" and "FSUIPC Status" are green
• All steps in the tutorial work up to testing the LED output on pin 22, so the output configuration is ok
• I used the preset "Cockpit - Landing Lights"
• But when I press ok, run MobiFlight, and then switch on/off the landing lights, I don't see anything happening

I also tried the Parking Brake on the Cessna (literally using the tutorial). In that case I used the preset "Controls - Brake parking", but same result. The LED stays off when I enable/disable the Parking Brake.

I tried to use the FSUIPC Console Log to find out if I have the correct Offset, but I guess that I'm even more lost now. When I toggle the landing lights, I see the following:

2219469 *** EVENT: Cntrl= 65751 (0x000100d7), Param= 0 (0x00000000) LANDING_LIGHTS_TOGGLE

But when I use preset "Lights - Landing Lights", I see completely different values - Offset is 0x0D0C - I would have expected 0x100D7.

I'm sure I'm doing something completely wrong!

Ok, I did indeed something completely wrong

Call me stupid... but I forgot to make the Output "Active". Now it works like a chime, both Output (LED) and Input (Switch). They are now connected with the Parking Brake of the Cessna.

Suggestion: To avoid other people to make this stupid mistake, maybe not a bad idea to mention this explicitly in the tutorial - I checked again, and this is not mentioned.

Still, my last question remains. What is the relationship between the logs of FSUIPC, and the offsets I'm seeing in MobiFlight. Because these seem completely different. I would like to know, because if I was expecting to be able to use the FSUIPC logging facilities to easily identify offsets, but this seems not that obvious. Can somebody still answer this question?

Hi

This is a beginner issue.
I know at starting this function sounds strange ( so Configs are disabled at creating) But if you gain more experience and you build your own panels then you will see it´s more logical to have the Configs "disabled" while create them,
Whatever this sound a bit strange..... But in a manual of your Car there is also not directly written you have to start the motor to have a indication of RMP in the gauge.... It´s just logical that you enable a config before you can use it.

About your question.

Here you must understand the difference between INPUT and OUTPUT. A Output is always a OFFSET..... But a Input is mostly a EVENT-ID ( and sure in some cases a Offset).
The EventID´s have other adresses. Decimal e.g. 65751 witch mean in Hexadecimal 100D7 ..... But w EventID is only a INPUT. So you can NOT read it. See it like a "additional" area in the System that is used for more easy inputs.

The regulary Offsets for OUTPUT are form 0000 to FFFF . You find a list in the FSUIPC Subfolder as a PDF File !

Summary..... Not try< to read a EventID.... this is not possibel !

It's indeed a beginners issue At least, it's been a good learning experience already, and I'm sure I won't forget to enable anymore in the future.

And thanks a lot for your clarifications! I have now used EVENT in stead, and now it makes totally sense. The values do perfectly match the ones that I can see in FSUIPC. And it works!

I ordered my 8-digit 7-segment display (based on MAX7219), and look forward to continue experimenting. Exciting stuff!!!!!!!