MobiFlight Community Support

Hi,

I actually show the vertical speed as follows : ---- ; -1500 ; 1500

I would like to show the vertical speed as follows : -15oo and 15oo (the letter o instead of the 0 (zero)). How can I do this?

I'm using MSFS2020 and FSUIPC and fly the A320Neo.

Thanks!

Hi
This is a verry special Request.....
In theory possible ..... But not with a simple short codeline or by clicking a checkmark. This need some investigation ( cause i not know eactly how airbus handle this display and how the FS2020 Offsets work) . Whatever..... Finaly it should be posible.

At first we must know....
1. How does it need to look like ?
Do we talk just about the LAST 2 Diggits so 1500 gets to 15oo OR Do we also talk about the 3rd number ? So e.g. 2000 should be 2ooo or 20oo ?

2. How does the VS System work in Airbus (I´m a Boeing guy.... so i don´t know).
Does Value increase by 100 ? So can we say the last two diggits are ALWAYS Zero or - - ? OR can it also show 50 e.g.

3. Does this Display only show VS or other things like FPA.

****************

The Problem : We not can simply say "0=o" in transform or Compare.
But we can use some tricky formulas..... Whatever kind of Optic you prefer we will work with a split display.... Or Placeholder Variables and "String Compares".

Tell me HOW it must look like and work....... Then we can figure out this together !

I am following this cause I also thought about.
My ideas were:
1. show an „8“ instead of the last 2 00 and paint the upper 3 segments black
2. show „8“ and try to figure out which wires do I need to plug out that the upper 3 segments will not illuminate

I know - weird ideas - I would also prefer a better solution.

@Pizman:
VS values: the last 2 00 are always 00. Values increase or decrease by 100 steps.

So either - - - - or 15oo/16oo/17oo and so on

I know - weird ideas - I would also prefer a better solution.

@Pizman:
VS values: the last 2 00 are always 00. Values increase or decrease by 100 steps.
So either - - - - or 15oo/16oo/17oo and so on

This Ideas are not weird..... I think about the same, cause the most easy solution is the best one aslong it fit the requested quality.
Whatever "Painting" is realy a bit lame.... More effective is your 2nd Option is what i decide.

BUT:
Thats why i ask the questions..... The "Electrical Way" by change the segment wires is only possible if....
1. These Displays ALWAYS show "o" , "-" or "Blank". If it show other things, too ( e.g. in FPA Mode it show Numbers from 0-9) then our rewire system will kill the usage of the Display for other Numbers !
2. We use a Display that have Single Diggits.... Like a 5x1 Display . If he use a 1x5 Display ( One Block with 13 Pins) it is not possible. If we change here the Segemnt Lines also the 3 Diggits on the Left are involved and no longer would use the upper Segments !

***********

Finaly my First Question is also important here..... If 1000 must be shown as "10oo" then we basicly just need to find a solution for the last 2 Diggits And thats verry easy with a little formula..... Here we would simply divide the Raw Value by 100 So e.g. 1500 gets into 15 ..... -900 gets into -9 and so on.
In Compare we simply say $+'oo' .... means it sill execute the current value and it "add behind" two "oo" characters.

BUT if it need to show "1ooo" then we need a more complex formula. Here we need to say something like IF Value divide through 100 result in a 2 digit number and the second digit is a zero then divide through 10 again and now show Value+'ooo' ..... IF NOT then just show Value+'oo'.

For this system it´s also interesting how "far" the range of the VS is in the Airbus. If it´s just -2000 to +2000 we just got 2 Situations ( 1000 and 2000) we need to handle.... So we could hardcode it. If it´s from -6000 to +6000 we got 6 Situations so a "formula" that check the 3.rd diggit is more effective.

*************

So.... Tell me how the "Hundret" Part must look like and how the range is..... thn i can already figure out the correct formula for you.

Hey and thx for the reply.

From what I see a it is really "just" the last 2 "00" which looks like "oo". The range is from -6000 to +6000 but still just the last 2 "00" are "oo" not the 3rd 0 (60oo)

Actually FPA is INOP with the A320 - so cannot test it.

But I tried your suggestion and also tried it in the almost same way before but it is not working with $+'oo'

I am using the 0x07F2 Offset
Transform the value: $/100

Compare:
If value !=0
Than: $+'oo'
or:

Display:
4 digits are in use (I dont use the + or - digit)
Use left padding is false


But in that way it is not working. are you sure that this could work with "letters"?

I got it working and might be useful to others

It's possible like this:


I use a personalized FSUIPC offset in output, 0x5302, and @ is set to that personalized offset 0x5302 in the configs below.

In my config, the 0x5302 becomes 0 when managed VS (-----) and 1 when selected VS. When I push the button of the VS rotary, I set the value of the x5302 offset to 0. When I turn the VS-rotary, I set the x5302-value to 1 and increment/decrement the VS value (0x07F2) in 100-steps


Output the following offset twice to the SAME led display (5 digits) : 0x07F2

First output (the digits) :

Transform on : if(@=0 || $=0,-999,$/100)
Compare : if current value = -999
set it to ---
Display : number of digits = 5
first three are selected (in use display)
Use left padding is on (and set to space)

Second output (the 'oo') :

Transform on : if(@=0 || $=0,-999,$/100)
Compare : if current value = -999
set it to --
else set it to oo
Display : number of digits = 5
last 2 are selected (in use display)
Use left padding is on (and set to space)


As a result I get the following displays:

Managed : -----
Selected : 7oo / 15oo / 10oo / -7oo / -15oo / -10oo etc...
When the A320 reaches the desired altitude/FL, it levels off and in selected mode the display will become ----- as well.

Hi Guys.

Exactly Saphke already explane the "3rd" Way i initial like to provide.

Way 1... Electrical Soultion with the Diggits.
Way 2... Rework of the Offset ( by adding oo )

Way 3... Splitting of the Displays. In case only the last 2 Diggits are involved AND they not need to show something else and are always "oo" thats possible.

***********************

@ Reensel

But in that way it is not working. are you sure that this could work with "letters"?

YES.... But i´m not sure what was the correct syntax.
if $+'oo' not work try $+oo without the "string symbol" . OR Try $oo (Without the + operator )

I´m sorry.... I figure this out for a other user months ago..... I know it is possible but i forgot how exactly. Can not try out myself at the moment !

I got it working and might be useful to others

It's possible like this:


I use a personalized FSUIPC offset in output, 0x5302, and @ is set to that personalized offset 0x5302 in the configs below.

In my config, the 0x5302 becomes 0 when managed VS (-----) and 1 when selected VS. When I push the button of the VS rotary, I set the value of the x5302 offset to 0. When I turn the VS-rotary, I set the x5302-value to 1 and increment/decrement the VS value (0x07F2) in 100-steps


Output the following offset twice to the SAME led display (5 digits) : 0x07F2

First output (the digits) :

Transform on : if(@=0 || $=0,-999,$/100)
Compare : if current value = -999
set it to ---
Display : number of digits = 5
first three are selected (in use display)
Use left padding is on (and set to space)

Second output (the 'oo') :

Transform on : if(@=0 || $=0,-999,$/100)
Compare : if current value = -999
set it to --
else set it to oo
Display : number of digits = 5
last 2 are selected (in use display)
Use left padding is on (and set to space)


As a result I get the following displays:

Managed : -----
Selected : 7oo / 15oo / 10oo / -7oo / -15oo / -10oo etc...
When the A320 reaches the desired altitude/FL, it levels off and in selected mode the display will become ----- as well.

Hey and thanks for that

One general question - are u using MSFS 2020 with the A320 and FSUIPC 7?

Actually I dont get the formulas at all - also the -999.
Esspecially: if(@=0 || $=0,-999,$/100) --> What does the @ etc mean?

Besides that could u give me a few more details about your personalized Offset and how this is set up? I have a rough idea but I am not sure.

By the way which EVENT IDs are u using for Push and Pull of the V/S knob?

Thanks in advance and sry for maybe supid question

HI

Saphke hopefully will guide you.....
Whatever please not "trash up" the toppings in the future..... Here we talk about the "oo" in VS Display.... Not about a personal guide for the A320Neo in FS2020 and Inputs like the "managed Mode" Switch.

About your technical question......
The "personalized" Offset pretty sure mean.... That guy create a own code.... For example a LUA Script that run in FUIPC itself.... And this Code will do something.
As he said he build a "own" Offset that show him if Display should be active (VS) or inactive (-----) by setting that Offset to 1 and 0.
THIS is external of Mobiflight..... Thats a advanced tool used by professional Cockpitbuilders who be able to programming own scripts.

About your question to the "@"
This is a part of Mobiflight we call "Variabe or Placeholder, or Config Refferences" The Area in the FSUIPC Tab of a Output Config on the lower half .
Here you can use a OTHER Output Config that still exist and use it as a Variable..... You define in the left dropdown WHAT config you like to use and in the Right field you choose for a Symbol..... Saphke use the Symbol "@" in that example.
So he create a Output Config that read his personal Offset 5302 and he use THAT Value as @ now in the Display Config.

And this usage happen in the transform field..... Here @ NOW is a variable and represent the value of that config.
Lets say this Config is "1" at the moment. If we would say in trasnform 5+@ it will result in 6.... Cause @ is 1 at the moment.

In that example:
if(@=0 || $=0,-999,$/100)
Means.... IF the value from the Other Config ( we define as symbol @) is currently "0" OR if Value of current Config ($) is 0 THEN set current value to -999 ELSE divide current Value through 100 and show this result.

About the -999 .
THIS is a little helpfull trick.
As i explane in the past.... We can NOT use Strings (characters) in the Transform.
Basicly you guys like to say "IF situation is X then show "----" on the Display.. But that is not allowed in Transform.... Only in Compare we could use "symbols and characters"!
SO something like if(@=0 || $=0,'-----',$/100) will not work ! And thats why he use this "tricky" way.
-999 is a value that will never happen by itself here ( VS is not exactly -999) So he create this FAKE Value to define the "----" situation
Finaly in COMPARE he use it again......

Transform on : if(@=0 || $=0,-999,$/100)
Compare : if current value = -999
set it to ---

You see.... Here he say IF -999 Then ---

In easy words.... He do the Calculation ( IF condition) in the Transform ..... Set a temporary Fake Value for this .... And in Compare he just do the final change from -999 into ---

Thank Pizman82 for your extended explanations. I'm not good at words, I'm better off with code

And you are right, I shouldn't have mixed up VS with managed/selected, guess I just got overexcited when it actually worked

@ Reensel

Is it more clear to you now? Or is there anything I can do to help you further? What I suggest you to do is to get the 'oo' configured first in a more simple config, and bring in the managed stuff later if needed.

The offset I used for the display is FSUIPC 0x07F2 and indeed I'm using MSFS2020.

For display 1 (first three digits)
The simplified formula in transform would be like this then : if ($=0,-999, $/100)
and in the compare : if current value = -999 set it to ---

For display 2 (last two digits)
The simplified formula in transform would be like this then : if ($=0,-999, $/100)
and in the compare : if current value = -999 set it to -- else set it to oo

Give it a try

@ Spahke.

Normaly i would send this by a Private Message..... But Forum not allow this.

I´m realy thankfull you support other users. The last weeks my time is verry limmited and i´m happy if the community can help each other already without a comment from myself

Just one little request to you !


Most Users.... specialy Beginners with verry low experience mostly copy/paste formulas we give them directly from Forum into Mobiflight!

So please if possible use the correct Syntax !
For example your..... if ($=0,-999, $/100) include "SPACES" ..... That occure in a Error when you use it.
I know its more harder to read.... But if($=0,-999,$/100) is pore practicable.
Also aways get sure if is written small ( not If) .... Round is Big ( not round) .... And check you use point and decimal correctly.

Thank you !

@pizman82

I'll keep it in mind regarding the spaces

Cheers!

Thanks to both of you

Today I just built all the special switches Pull/Push etc

It is now clearer for me - honestly the last time I worked with Mobiflight there wasn’t the feature with the @ etc that’s why I was confused.

I think I do almost the same like u with that offset. I just created one for a „Readout Output“ for 0 and 1 and steer the managed/selected mode via preconditions and of course the switches.

And why I was asking which event ID or maybe something different you are using (on the Input side was that when I do it like I described that managed (- - - - -) display will be triggered by Push and I for example Pull the V/S knob it switches to the selected fine but in your case what you described when reaching the correct ALT flightlevel where the V/S changed automatically into managed mode back it will not work with my approach because I just can trigger it by the Pull/Push Switch.

By the way when I use MSFS the V/S - was kind of buggy to me. Did you also recognize it?

Tomorrow I will try it again
I really have to say thank you for your help. It really push me in the right direction and brighter view in solving things.

Hi Saphke.

I think I made it with the display.

Just one question in terms of the V/S Input.
What would be the right Event or sth similar to use?

V/S slotted index is not working properly.

Means which event would be the correct one for either Pull and Push.
Thanks in advance for your help „again“