MobiFlight Community Support

Hi guys, I've managed to have all annunciators working on my MIP, all except the AFDS. The test switch works and so do the buttons to cancel the alarms but the lights do not. I have tried numerous options including the FSUIPC offsets and also the P/RST and Dsp L/R options in Simconnect but still nothing. They are the only things left on my MIP to get working. The thing that makes this more of a head scratcher is that when I load a flight from the saved flights, they work. Am I missing something silly? Are there issues with the PMDG AFDS? I understand some presets were not working, is this still the case? I am currently using the offset 65F1 for the A/P P/RST, 65F5 for the A/T and 65F9 for the FMC. All with INT and 1 bytes.
Many thanks in advance.

These work for me:
Select FSUIPC Offset instead of SimConnect
Value: Int Size in bytes: 2

A/T Red - 65F5
A/T Amber - 65F7
A/P Red - 65F1
A/P Amber - 65F3
FMC - 65F9

For the switch, try: 65FB 2 BYTE 0: 1 1: OFF 2: 2

You may need to set a precondition for A/T and/or A/P lights - ex. AP ANNUN=0 (AND)

I copied and pasted this from another post I replied to. Looks like the only difference is the byte size. I use 2. Also, I have a precondition set

You guys not need Preconditions .... Using 2 Bytes is Wrong also !

A/T Red - 65F5
A/T Amber - 65F7
A/P Red - 65F1
A/P Amber - 65F3
FMC - 65F9

These are all "2 x 1Byte Offsets" Badly PMDG and FSUIPC write this a little strange.

There exist TWO ADFS Pannels ( One CPT one FO ) So each Information exist twice!

For example:

A/T Red - 65F5 means....
Captain Side ADFS AT (Red) is Offset 65F5 1 Byte INT.
First Officer Side ADFS AT (Red) is Offset 65F6 1 Byte INT.

There are many many Offsets in PMDG that work that way.... Also some with 3 Bytes.... E.g. the Radios where you got one for CPT, FO and one in the Overhead.

************
About basic Problem:

There was a issue in the Offsets for ADFS in the First Beta Release of FSUIPC. Some bytes struggle and some was missing.
I recommend..... Get sure your PMDG is UpToDate (Patch) and also get sure you have the newest Release of FSUIPC !
I expect your problems comes in case one (or both) are not up to date and still use the old bugged Offsets.

Hi guys, many thanks for your insight in to this. I have tried it with 1 byte and 2, adding a precondition and with no precondition and still nothing. All my other annunciators are working including the lights test switch and the AFDS test switch but the AFDS lights are the only ones where I've had to use FSUIPC and not SimConnect which makes me question FSUIPC. I'm using version 7.3.15. I have the latest update with PMDG too. It's become quite a headscratcher especially when it should be working.

Ok.... I Missunderstand your question !

As i know some of the Outputs not work via Simconnect.... The AFDS was part of them. So maybe your right and they still not possible via WASM
In case you talk about FSUIPC in your initial Request i still think we no longer talk about Simconnect anymore.
So all i asaid is adressed to FSUIPC !

And in case you say you use FSUIPC i also expect ALL OTHER Outputs ( You said they working) are done ALSO via FSUIPC.
Now you say they are done via SimConnect..... And here is your Problem!

For Simconnect you not need a modification in the PMDG..... For FSUIPC Stuff you need it !

You need to include a Line in the PMDG Ini File to enable the Data Interface to FSUIPC. Without this Entry all FSUIPC Offsets are Empty !

Check the FSUIPC Manual for PMDG.....

To enable the data communication output from the PMDG aircraft, you will first need to enable
data broadcasts. To do this, open the 737_Options.ini file which for Steam installations is located
under the folder
[User]\AppData\Roaming\Microsoft Flight Simulator\Packages\pmdg-aircraft-737\work
and for MS Store installations under the folder
[User]\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\p
mdg-aircraft-737\work
and add the following lines to the end of the file:
[SDK]
EnableDataBroadcast=1
For CDU screen data you also need one or both of these lines:
EnableCDUBroadcast.0=1
EnableCDUBroadcast.1=1

Well I found out my silly mistake...... I was working on the PMDG 737-800 and had not added the EnableBroadcastData line in the options folder. I had for the -700 and assumed it covered both variants (Doh!). The only question I have now is for the programming of the co-pilot AFDS. The A/P and A/T are working perfectly. Can you explain how the FMC button would be programmed and also the test switch for the copilot AFDS as these are different to the Captain side. I have added one for the A/P and A/T but the FMC is 65F9 so a bit unsure. Also with the programming at the moment, when I test the switch, it turns on the Captain side.
Thank you so so much for helping the lightbulb in my head come on

Always for those e.g. 2x1 Byte things add +1 to the main adress to get the second one.....
For sure in Hexadecimal .... Offset for the FMC is 65F9 so +1 = 65FA
Hexa = 0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F, so e.g. 65FF+1 = 6600

About Input.... There would be also FSUIPC EventID.... But i expect those exist also as Simconnect Events....
Check those .... https://hubhop.mobiflight.com/preset/?id=c10dce89-4017-4f1c-b533-d45101bb8056

Hi there and thank you so much for the help. It now works perfectly. The only thing I'm stuck on is the test switch for the copilots AFDS. The only events I can see on hubhop are for the captains side. I have also tried the PMDG Event ID 70074 with Custom Parameter 1:0 for the lower one and Custom Param 2:0 for the upper part of the switch. Is this correct?

I not test it..... Whatever i planed to buy the new PMDG last time.... I not find i a spot in case i got so much work in reallife.

Normaly the PMDG EventID work with a straight logic.... Latching Switches or Multi Pos Switches always work with "SET" Parameters from UP to DOWN or from LEFT to RIGHT.

So if the logic is the same like all the years before then its "0" for the upper position, 1 for the Mid Position and 2 for the lower position.

Maybe the "EventID" have changed in case a lot of new elements come into the system. So NOT test the old EventID we have listed (Those was build for the P3D Version).

I high recoommend to talk to "Jaime Leon" on our Discord (He is a Mod and is colored in Orange).
He is the guy who make most of the existing Presets..... And Mostly he create just the CPT Side in case 9)% of Cockpitbuilders plan for a "OneSeater" and not take care of the second Input.

Solution:
1. Talk to Jaime to ask him if he can incluede the FO Side Presets
2. Use EventID and just check the "SDK.h" File to explore the right Event ID Number.

If you not have sucess.... Request here again..... Then i can have a look next week and can try to support you direct.
Also here DISCORD is the best way to contact me directly ! https://discord.gg/99vHbK7

Hi there, just applied your logic to it and it now works perfectly. I had applied the wrong logic to it. I assumed the centre position would be 0, up would be 1 and down would be 2. But I can confirm that for the copilots side, the fsuipc - pmdg- event ID 70074 does work with the logic 1=centre, 0=up and 2=down. Thank you soo much for your assistance, You guys are amazing.