MobiFlight Community Support

I'm running a couple pro micros, (one for the six pack, running several encoders) and one for the lower panel. The 6-pack is working fine, but the lower switch panel is a mess. Some functions work, while others don't. E.g. "pitot ht" and "alternator" work IN THE COCKPIT, whereas "Taxi lights" and others, do not.

* I've wired them all similarly.
* They're all "button" devices
* My landing light button is set to pin 6, and pitot heat is pin 7 (so its not a digital vs analog thing).
* They're all "inputs".
* They're all checked as "active."
* They're all connecting and using similar input variables, in my case mostly "Microsoft/Generic/xxxxx" Events.
* I have event logging displayed, and they all appear to be functioning in MF, but SOME of them just don't work in the cockpit.

Anyone have any thoughts before I lose my mind?

Hi

Question is mostly ....What aircraft do you use ????

Badly in FS2020 also Asobo itself choose different typs of Data ( e.g. AVars, BVars, HVars, Lvars and so on for every single Aircraft......
So it can hapen that "PitotHeat" work fine for a Stock C172 but not work for a Stock Piper!

Basically..... At first find out if your Switches work..... You pretty know MICRO is not a recommend Board ( only experimental) Means i not know if the issue is Hardware or Software.
You say the logging is fine..... So i expect the problem is Software. Can you confirm this ?
If not sure.... Simply change the INPUT Config from a Button you still KNOW it work ( tested) to the new settings.....
Basic Idea.... If the Button on e.g. Pin 5 that is used for your SixPac is working at the moment..... So you 100% know electrical all is fine.
So simply use THIS Button instead for the PitotHeat..... If Pitot not work you know 100% problem is SOFTWARE!!!!!
Reversed.... Use a problewmatic button ( You try for the "lower switch panel" for testing with a function that work already (sixpack). If it work also there, then you know Button(Hardware) is fine !


In easy words..... Confirm Hardware is fine.... If YES.... then simply the used Events are wrong and in the current used Aircraft you need "other" events for the function you like to controll!

Hi Pizman,
I disconnected the Micro and am now running a Mega. I fly only the Default C172. I swapped switches/wires and they all can activate the pitot heat (one that I know works!).

I opened a flight, went into Dev Mode and looked through windows>Behaviors to see if I could find any clues. There were lots of variables, some seem relevant:

LIGHTING_BEACON_1 - 1.000
LIGHTING_LANDING_1 - 1.000
LIGHTING_TAXI_1 - 1.000
LIGHTING_NAV_0 - 1.000
LIGHTING_STROBE_0 - 1.000
LIGHTING_STROBE_1 - 0.000
LIGHTING_NAV_1 - 0.000

DEICE_Pitot_1 - 1.000 (When my switch was on)
DEICE_Pitot_1 - 0.000 (It changed value when I turned my switch off)
I used an FSUIPC - EventID “PITOT_HEAT_ON” (Event ID 66072) for that one

So, I tried an FSUIPC EventID for Taxi Lights. “TOGGLE_TAXI_LIGHTS” is all I could find, and it did not work.
There is no FSUIPC Offset specifically for Taxi Lights that I could find. HOWEVER, I searched the Offset Status pdf, it references FSUIPC Offset 0280, which references another offset: 0D0C “Lights, a switch for each one(bits from lo to hi):” this lists ALL the lights, but I can’t seem to be able to find the 0D0C offset in any of the pull downs. Or, how to assign the individual variables, if I could.

Seems like I’m close… but I’m stuck. I will Venmo you dinner money if you help me solve this.

You Mix Up "FSUIPC" and "SimConnect" .

Offsets like 0D0C and "EventID" like 66072 are elements from FSUIPC.
This is the "old" System we used in FSX/P3D .... and for sure its also Available and possible in FS2020.

The "Model Behavour" Page you check ( Dev Mode FS2020) are the "internal commands and data" . This is NOT related to FSUIPC!
This data is more important if you use the Mobiflight WASM System..... Our "own" Interface to FS2020 ! ( Build to no longer need to use FSUIPC anymore)

Solution: I not test this myself.... So i can not give you a direct awnser.....
But there are simply some ways.

1. Use our WASM Logic and stop think about FSUIPC.
Choose for the Input in Drowdown "FS2020 Simconnect Events" ( Instead of EventID or OFfset) .
Check the Lists if the needed Input is already included..... If NOT find it out within the the DEV Mode or simply ask Rofl-er on Discord or a other advanced Guiy ( Mods) .
Most of the Inputs are possible ( except B-Events at the moment)

2. Remain with FSUIPC.....
The old way.... E.g. 0D0C is a "Bitwise" Write. I not know if it work in FS2020 . If yes...:
You must Select "Bitmask" here..... Only choose for the assigned bit.

0D0C 2 Lights, a switch for each one (bits from lo to hi):
0 Navigation
1 Beacon
2 Landing
3 Taxi
4 Strobes
5 Instruments
6 Recognition
7 Wing
8 Logo
9 Cabin

So to controll the Landing Lights for example the needed Bit is "2" .... means you disable all Hooks in the "Bitmask" Subwindow expect Bit #2 ( the 3rd Bit from the right)
Value is "1" .... means you write "1" to that Bit if you press your Button ...... For latching switch for sure you also need a Release with "0"

Hi Pizman, I installed the WASM Module, and Downloaded Latest Events. I do not see "FS2020 Simconnect Events".

I see:
None
MSFS2020 Events
MSFS2020 Custom
Mobiflight Variable
Mobiflight Retrigger Switches
FSUIPC EventID
FSUIPC PMDG EventID
FSUIPC Jeehell EventID
FSUIPC LUA Macro
Keyboard Input
Vjoy Virtual Joystick

From the "MSFS2020 Events" I tried all options I find here, such as: Microsoft/Generic/Lights group, TOGGLE_TAXI_LIGHTS. It does not work.

There is no Taxi Light specific variable in the MSFS2020 Events "Cessna_172/Lights" group

Sorry for that.... I not remember the correct Name.... But for sure its logical i talk about "MSFS2020 Events" ( i belive it was called "Simconnect Events in the early Beta Version)

As i said.... I not start building this.... I could find out.... But this is mess time in case pretty sure a lot of other user still do this.
BUT ...: those are not oin this Forum !
Please joind DISCORD https://discord.gg/99vHbK7
There you can write the request in the "FS2020 Subsection"
Or you directly whisper a Private Message to the Pro Users !

I think most of them use the Stock 172 for some time and know the system !