MobiFlight Community Support

Hey guys.

Anyone has the knowledge of Offset Values for generic Flap & Gear "In Transit" annunciators ? I can't find them anywhere.

I'll use them for default P3D planes.

Hi slammer,

0BE0 4 Flaps position indicator (left). This gives the proportional amount, with 16383=full deflection. It doesn’t correspond to the equally spaced notches used for the control lever. If you know the maximum deflection angle you can derive the current angle by ((max * position indicator) / 16383). This only gives the (inboard?) trailing edge flaps. Please see
offsets 30E0–30FF for greater details where needed.

0BE4 4 Flaps position indicator (right). This gives the correct proportional amount, with 16384=full deflection. It doesn’t correspond to the equally spaced notches used for the control lever. This only gives the inboard trailing edge flaps. Please see offsets 30E0–30FF for greater details where needed.

0BE8 4 Gear control: 0=Up, 16383=Down Ok-SimC Ok-SimC
0BEC 4 Gear position (nose): 0=full up, 16383=full down Ok-SimC Ok-SimC
0BF0 4 Gear position (right): 0=full up, 16383=full down Ok-SimC Ok-SimC
0BF4 4 Gear position (left): 0=full up, 16383=full down Ok-SimC Ok-Sim

For all generic Offsets see this link:

http://www.schiratti.com/dowson.html

The Offset are in the downloadable File FSUIPC SDK

You can also look into your P3D\modules\-Folder. There you find a Folder with documents (pdf). Very usefull

Hi slammer,

0BE0 4 Flaps position indicator (left). This gives the proportional amount, with 16383=full deflection. It doesn’t correspond to the equally spaced notches used for the control lever. If you know the maximum deflection angle you can derive the current angle by ((max * position indicator) / 16383). This only gives the (inboard?) trailing edge flaps. Please see
offsets 30E0–30FF for greater details where needed.

0BE4 4 Flaps position indicator (right). This gives the correct proportional amount, with 16384=full deflection. It doesn’t correspond to the equally spaced notches used for the control lever. This only gives the inboard trailing edge flaps. Please see offsets 30E0–30FF for greater details where needed.

0BE8 4 Gear control: 0=Up, 16383=Down Ok-SimC Ok-SimC
0BEC 4 Gear position (nose): 0=full up, 16383=full down Ok-SimC Ok-SimC
0BF0 4 Gear position (right): 0=full up, 16383=full down Ok-SimC Ok-SimC
0BF4 4 Gear position (left): 0=full up, 16383=full down Ok-SimC Ok-Sim

For all generic Offsets see this link:

http://www.schiratti.com/dowson.html

The Offset are in the downloadable File FSUIPC SDK

You can also look into your P3D\modules\-Folder. There you find a Folder with documents (pdf). Very usefull

Hi Stephan, thanks for your answer.

I've been actually working on this Offset to find my way out, as there's no native Offset's specially set for this function.

What i was trying to do is creating a "pseudo" thing like this;

If 0BE0 = 0, then LED is 0
If 0BE0 = between 1 and 3275, then LED is 1,
If 0BE0 = is 3276 (first detent, lets say), then LED is 0,
If 0BE0 = is between 3277 and 16383, then LED is 1 again,
If 0BE0 = 16384 (2nd//final detent), then LED is 0

I've tried to make this but failed somehow, LED is either rapidly blinking due to conflict of at least two separate values', or stay lit/unlit.

I guess there's something to do with Preconditions but i'm not familiar with those settings. Some help would be awesome !

Cheers!

I think your values are in parts to precise.

Why don't you have a look on the value while your flaps are stopping at the detents?
0 is ok, flaps up, then set flap position 1 and wait until the flaps are stopping and read the value.
Same at flap-position 2 and position full.
Then give the values an area around, for safety and define the complete area.
So 0 LED is 0, from 1 to n1 LED is 1 (way to detent 1), from n1 + 1 to n1+10 (detent 1 - LED is 0), n1+11 to n2 led is 1 (way to detent 2) and from n2 + 1 to n2+10 (detent 2) led is again 0 and so on.

You also can use the transform-input:

if($=0,0,if($=value of detent1,0,if($=value of detent2,0,1)))

So the LED ist 0 when the value is 0 or has the value of your defined detents. In all other cases the led is 1.
pizman can this much more better than I, so I hope he don't kill me

I think your values are in parts to precise.

Why don't you have a look on the value while your flaps are stopping at the detents?
0 is ok, flaps up, then set flap position 1 and wait until the flaps are stopping and read the value.
Same at flap-position 2 and position full.
Then give the values an area around, for safety and define the complete area.
So 0 LED is 0, from 1 to n1 LED is 1 (way to detent 1), from n1 + 1 to n1+10 (detent 1 - LED is 0), n1+11 to n2 led is 1 (way to detent 2) and from n2 + 1 to n2+10 (detent 2) led is again 0 and so on.

You also can use the transform-input:

if($=0,0,if($=value of detent1,0,if($=value of detent2,0,1)))

So the LED ist 0 when the value is 0 or has the value of your defined detents. In all other cases the led is 1.
pizman can this much more better than I, so I hope he don't kill me

Those values are so precise because they are the actual values of Mooney's Flap offset

Shall i use this transform-input value on a single Input config ?

sure, the whole line, adapted with your values

With that formula, i'm getting the following error;

27/09/2017 16:19:05(642): Error on config execution. An error occured on parsing your value formula. Please review and correct any errors.
27/09/2017 16:19:05(636): checkPrecondition : Exception on NCalc evaluate

It now seems like this, according to the precise values ;

if($=0,0,if($=8192,1,0,if($=16383,1,0)))

This part of the Transform works well though;

if($=0,0,if($=8192,0,1))

I think the LED should be OFF if you reach a detent?

if($=0,0,if($=8192,0,if($=16384,0,1)))

means
if flaps are up LED is OFF,
if $=8192 (detent 1 is reached) LED is OFF
if $=16384 (detent 2 is reched) LED is OFF
In all other cases, if the value is NOT 0 and NOT 8192 and NOT 16384 the LED is 1

if($=0,0,if($=8192,1,0,if($=16383,0,1)))

there is one value too much

I think the LED should be OFF if you reach a detent?

if($=0,0,if($=8192,0,if($=16384,0,1)))

means
if flaps are up LED is OFF,
if $=8192 (detent 1 is reached) LED is OFF
if $=16384 (detent 2 is reched) LED is OFF
In all other cases, if the value is NOT 0 and NOT 8192 and NOT 16384 the LED is 1

Ah, yes! Now it works! Thank you so much!

I'll try the same tactic for the gears as well!

Gear On works well with Compare function,

Gear Transit however doesnt go off when reached 0,

Used "if($=0,0)" on Transform; gave me the same error,

So i used at Compare "if value smaller then 16382, then 1, else 0", aint work.

Any ideas ?

Edit : Done, if($=0,0,if($=16383,0,1)) worked pretty well.

Hey, great if it works!

An if-condition has the following syntax: if($=value, then x, otherwise y)

So your compare should be: if($<16382,1,0)

In your first line if($=0,0) is a value missing: if($=0,0,1)

With your edit is the LED OFF if the value is 0 or 16383 otherwise always ON - correct?

pizman can this much more better than I, so I hope he don't kill me

Keep Cool....

@ Topic....

i See you already solve the problems..... whatever sometimes in a verry difficult technic.
by the Way... THIS ( Flaps and Gear) was explaned Multiple times in other Threads.... PLEASE Use Search engine in the future if possible !

Shortly about the used "to much difficult" parts..... Just for information so it is much easyer next time.....

For example the GEAR

Edit : Done, if($=0,0,if($=16383,0,1)) worked pretty well.

Here you can use much easyer if($=16383,0,$)
For a LED its no mater if Value is 1 or maby 99, 99999, or something else.... ZERO "0" is OFF.... EVERY other Value is ON.
With this compare ONLY 16383 will change to Zero.... All Other Value will be shown 1:1 ... If Gear is UP (Value 0) the LED is off, too... Simply cause value is 0 this time.

***
Or for the Transit....

if($=0,0,if($=8192,0,if($=16384,0,1)))

Here the same logic.... You not need 0=0 if you use $ on last position...
if($=8192,0,if($=16384,0,$))

But there existing lots of different technics, too.

Myself i would use a OR instead of ELSEIF in this situation, cause both Factors change to same result ... So you not need the second IF....
if($=8192||$=16384,0,$) ......... "||" is the sytax for OR..... So it says IF Value is 8192 OR 16384 THEN Change to Zero Else use Original Value.

NOTE: The "|" Symbol is left of Y in german keyboards pushed additional with ALT GR.... Not know the position on English Keyboards
For a AND Logic the Syntax is && ....
For Example if($>5&&$<10,1,0) If Valie is bigger then 5 AND smaller then 10 set to 1 Else set to Zero) .. So 6,7,8,9 will be "1" All Other will be "Zero".


Alternate you can work with Preconditions and 3 Configs ( ON Config, OFF Config and READOUT Config), too..... But THIS is much mor difficult finaly.

*****
Last Note....
Please look up. In FSX the different Standard Aircrafts NOT use same Values ( Whatever why) Some for example use for GEAR DOWN 16382 instead of 16383.
Here i recommend to create a Puffer.... Simply say If Value is "BIGGER Then 16380" ... ">16380" instead of a fixed value in the IF Function.
Then ALL Values above 16380 will work whatever plane use 16381, 16382 or 16383.
If you only use ONE Aircraft all the time THIS is not needed but i recommend to make the Config compatible for all aircrafts !

I think the LED should be OFF if you reach a detent?

if($=0,0,if($=8192,0,if($=16384,0,1)))

means
if flaps are up LED is OFF,
if $=8192 (detent 1 is reached) LED is OFF
if $=16384 (detent 2 is reched) LED is OFF
In all other cases, if the value is NOT 0 and NOT 8192 and NOT 16384 the LED is 1

HI StephanHO, I would like to know on what page and exactly where you insert your formula. Is it in the FSUIPC page under ''more options'' in the transform line? if it is on the Compare page then where do you insert it? I'm lost with that. Thanks in advance! I would appreciate some help.

Another question, what can I use as an offset for LE FLAPS TRANSIT? can't fin it. :-)

Expressions ( like if functions) will be used in the Transform field ( For Outputs) or additional in the Compare field... the Compare field is only used if you need MORE then 1 Function.... Normaly this is not recommend cause it´s much more difficult !

In INPUT configs via FSUIPC OFFSET you use the Expressions in the Value field.

****
About the LE Flaps..... What Aircraft do you use.... For Exmpale Addons like PMDG support a own offset for that Warning Anounciator !