MobiFlight Community Support

hi i need a preset to switch test 1/2 (L) CPT on MIP. Can anyone help ?

Hi


Do we talk about this ?.....



There is a wrong name here i explore some mins ago,

this Panel is called in real ADFS
But in Hubhop Database its litsted as ADSF

Simply check these Inputs ( just one as example..... https://hubhop.mobiflight.com/preset/?id=c10dce89-4017-4f1c-b533-d45101bb8056

it worked, thanks!
Another question, what can the preset for these red lights be? I found something but still not lit up: /
it's about A / P and A / T

i tried this:
(L: switch_4452_73X, number) 0>
and nothing: /

Try that...

https://hubhop.mobiflight.com/preset/?id=3d8c09a0-1ebf-4bb7-a935-6db0376c8e13

Some Things are missing.... Just report and we can have a look.
And always for search try different wordings.
In that example i also not find it by ADFS..... So i try "AT" And there was the hit.

If you can't get SimConnect values to work, try the Offset Mapping for PMDG 737-700.pdf located in the documents folder of FSUIPC.

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)

@treeb52

Thanks for your posting.

At first to make this more clear....
Your recommend way require to install FSUIPC7 ( Newest Version) on the Sim Computer... Freeware is OK. You not need Payware Version!
In case most Fs2020 no longer use FSUIPC anymore, this information is very important.
Also get sure you make the INI File entry in the PMDG Files..... Explained in the FSUIPC PDF Files.

The Offsets looks good but the last idea is wrong.
The SWITCH Data is also just a Output and show the satus of the sitches. They are NOT be able to make inputs.
ALL PMDG Offsets are pure Outputs and are Read Only !

Finally i not understand the logic of the Precondition here. Make no sense to me !

You're right. I wasn't thinking about the using offset for the switch input. That, of course, doesn't work. My bad.

Here are your input settings (Select FSUIPC - Event ID). For all Event ID's, use 66587 (Rotor Brake), then input the following "para" entries:
For position 1:
On Press - 34202
On Release - 34204

For Position 2:
On Press - 34201
On Release - 34204

Yes, you will need at least the freeware version of FSUIPC7. Follow the PMDG directions in the documents file "Offset Mapping for PMDG 737-700.pdf) which state:
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


Also, if you are having trouble finding the right settings for any particular switch, let me teach you how to fish. You can assume the event ID is "Rotor Brake" and then in FSUIPC, go to the LOG menu and check "Events" and then check "open console". Then, resize MSFS window so you can see the console and your cockpit. Use your mouse to click buttons to find the parameter. Click it several times so you can notice a trend, as there may be some erroneous codes logged. Notice that a click shows one parameter and a release shows another. These will be the codes you use. This is the method I used to find the codes you wanted for the switch. Note: just moving your mouse around the cockpit throws codes. So after you get your mouse pointer onto your switch, start writing down your parameter codes. The lines will look similar to this:
1378797 *** EVENT: Cntrl=66587 (0x0001041b), Param= 46803 (0x000182bb) ROTOR_BRAKE

You only need the "Param=" number because all of the event ID's are 66587 (ROTOR BRAKE)

Also this is wrong i think !

I be thankfull you like to make some inputs for new users.....
But you must get sure your right when you recommend something!

(NOTE: Maybe my information is no longer correct.... But for now (as i know) all is same like in the past!)

And here "RotorBrake" is no factor cause via FSUIPC we use the SDK Inputs!

And here a Value of "On Press - 34202 .... On Release - 34204 is (as i know) simply worng !


For FSUIPC Event ID we must use the listed parameters !

e.g. for a Leftclick we use same like in the past.... 536870912 .... for a Mousewheel Up we use e.g. 16384


Again NOTE: If this have change (without my knowledge) i apollogy for my wrong comment....
But please be so kind and confirm your information with a Link!
All i read till now says that it is same way as in P3D/FSX.... And here "RotorBrake" and "34202/34204" is not correct !

Ok if you say so.

I used the method I describe to research the parameters on my valuable free time to specifically to help out a fellow simmer (you) and answer your question...and it worked for me.

You CAN use the mouse click method, but you don't have to

Soooo.. done helping you, bro. Peace, and good luck

Please not feel atacked....
It simply not make sense to me and is a different information like all i use the last 8 years!

E.g. FSUIPC for those Commands is "Bit Sensitive". For example "128" is 1000.0000 in binary....
Means whatever i send 128, 129, 130 and up to 255 .... All Inputs do the same.... Cause FSUIPC only see the first bit and not care about everything behind......

If i´m right and the logic not change ( as i know) then.... 34202 is binary 1000 0101 1001 1010 Means the bit #15 is high .....
So each parameter from 32768 to 65535 should do exaclty the same ! cause its simply 1xxx.xxxx.xxxx.xxxx

Have you tried it?