MobiFlight Community Support

Hello

With the last version of MB I had that the HEADING get NEGATIVE values I check all but the number that I received from FSUIPC is negative. For example: if you put Heading=295 MB give -66, but with 118 MB give 117. It´s rare... I think that is an error from FSUIPC that send negatives values for heading. Also if in Autopilot I get 4.000, MB send me 3999. The formula it´s something variable I think. If I try to get the altitude in each moment the differences are more bigest.

I know that it´s difficult with too much variables get Ok results, but I hope that this was a common problem. Not only my own problem with MB.

MB is a great program.Clever, but I find it too much rigid. It´s impossible to go out from it´s limitations. I´m sorry for the comparations, but I find LINK2FS more flexible, however it´s necessary to know a lot of programation of Arduino in C & C++. I´ve programed with LINKS2FS for my loved FSX, and I was trying do the same with MB for FS2020 but I´m going to surrender with a lot of limitations and problems now. Perhaps because the MB 10.1 and FS2020 are too young. However the same programation that I did with MB for FSX it´s working Ok qith FS2020. Only Buttons an Leds. All the values was with LINKS2FS and they do not work now because LINKS2FS need to know if the sim is connected and oly is seen to find FSX not FS2020.

Tanks for your help and congratulations to Sebastian for his brain and work.And I-sorry to give you a lot of problems, perhaps because me are also young with MB 10.1 and FS2020...

Sincerelly,

Hi Julesta,

about FS2020 please wait that this buggy software is adjusted, same for FSUIPC7. They have Beta-Status.

Regarding to your Heading-problem:
If you got negative values you can compensate them. Use a transform formula: if($<0,$+360,$)
Means, that if the FSUIPC-Value is negative, so add 360 otherwise take the FSUIPC value. By your example of a value of -66 add 360 and you got +294. If this value is not exact then is this an issue of internal rounding.
So you can try: if($<0,(Round($+360,0),Round($,0)).
The result of a transform formular is always an integer value.

Same maybe with your altitude.

Note: MF is not for programmers, only for sim users who want to realize their cockpit affairs in an easy way without any knowledge of programming. Who is able to do so, is not wrong with MF because this knowledge can help you to understand how MF works

Thank you very much StephanHo

Really MB is a great program and easy, but you must know a lot of SW, HW, etc. I´m getting severals problems with the FSUIPC, the Offsets, and the union between FSUIPC+MB+FS2020. Really some times is frustrating, but with your help I´m going up in this job.

When I used MB to programed the FSX it was very easy. All worked at the first time without problems. Perhaps next 2021 all will have less bugs.

Thank you about your idea, but: in my case HEADING There is a transform $*(360/65536)/65536 then How to put your new comparation in the transform?...

Best regards.

Hi Julesta,

that can be done ;-)

1st let your HEADING - config as it is. Copy only the display settings to a new config and empty the display settings in your HEADING config.
If you have $*(360/65536)/65536 in this tranformline, let it untouched.

2nd name your new config i.e. HEADING_2 and activate it

3rd go to your HEADING_2 config open the config wizard by clicking the three dots (EDIT)

4th click the FSUIPC-tab and go to the bottom where you find the config references

5th set the hook at the first config reference click the arrow-down and select here the HEADING-config and assign it on the right side as "a"

6th set the hook in front of the transformline and insert the following formular:
if(a<0,a+360,a) or with the round-variation if(a<0,(Round(a+360,0),Round(a,0))

7th if you have copied your old DISPLAY-config from HEADING here to HEADING_2 you are ready

Now you have your old transform formula (a) and the new comparision formular both working for your fun.

Regarding FS2020 you have to know that the FS2020 is yet a bit buggy especially the SIM_CONNECT interface, which correspondents with FSUIPC7
Also FSUIPC 7 is yet in beta-status, so not all will work. So if you try to work with it it has to be frustrating!

Please report whether it works.

Hi my friend StephanHo

Very clever. Yes You can , but not me

I studied your solution and, yes: it work perfectly with if(a<0,a+360,a), not with if(a<0,(Round(a+360,0),Round(a,0)), then the encoder it does´nt work.... But no more degrees negatives on LCD now with the first solution.

I hope that FSUIPC and FS2020 will be better in the future, because trying to solution theirs problems is very tricky and a great work for all of us. If all will work Ok, the use of MB will be easier than now and direct, without several variables more.

Thank you very much for all your clever help.

Saludos cordiales!!!!

You're right, the 2nd formular has an error:

if(a<0,Round(a+360,0),Round(a,0))

The "(" before the first Round has been wrong. Without it should work

Hi Guys.

Basicly all is OK.... And i realy honnor you to use this Systems ( cause you now see the deepnes and posibility we got)
BUT
In that case this is way much to difficult.... No "placeholder" is needed.... No second config is needed..... No difficult double-round is needed !
Sure all is correct.... And there exist 1000 ways to do this and all working fine..... But lets use the most easy one !


Step 1:
Read the Heading in ONE Config.

Step 2:
Use Transform in that Config to make the recalculation of FSUIPC AND!! Make the Round there !
Transform: Round($*(360/65536)/65536,0)
This result in a "rounded" Heading ( whatever it is still negative now)

Step 3:
Use the Compare Tab enable to make the Negative Swap of the already rounded Value from Transform
Compare : IF Value less 0 <0 ........ THEN $+360 ..... ELSE can be empty or you use $ both will do the same

Yes, is clever. I know that MB is a strong piece of SW, however I´m fiighting with it since several weeks... But: I finished my work.

I have been a lot of problems. The worst: I lost my config several times. I save the config always, but when I star again MB !!!!! the config has gone...or something more usual: MB do not find the 2560 (I´ve two 2560 connected with differents items...). Always is the arduino2560 where I have instaled 2 LCD (20x4) 8 encoders and 7 buttons. Now I save also the devices that I have connected in each arduino...Differents save....


Saludos cordiales