Falcon BMS Altimeter and MFD Exporter issue

[bluc69]

I don't know where to post this but I have a discordance between Falcon BMS Altimeter reading and the one on my pedestal exported by MFD Exporter 0.5.
When I start the program the altimeter from BMS on the main display show a pressure of 1010 Mb while the one on the center pedestal made by MFDE shows 1013 Mb.
If I turn the knob both move but they don't get synchronized.
I also have the pressure flag active on the center pedestal but not on the BMS altimeter.
During the flight the altimeter datas of the two instruments don't show the same altitude but there is a discordance of about 100 feets
What I can do to have both instruments showing the same data?

[CobaltUK]

Bump !

[Red Dog]

If I turn the knob both move but they don't get synchronized.

As far as I know this is not possible because in BMS 4.32, the pressure setting is not externalized and MFDE will remain stuck at his default value.
Although the main needles of the MFDE exported altimeter will show the correct altitude according the the pressure setting inputted in the 3D cockpit.
So in the end, the needles are in sync, but the pressure windows is not, because it is not implemented as a shared mem bit in 4.32
So you will have to use the setting indicated in the 3D pit until 4.33 is released, where all that has been implemented.

I also have the pressure flag active on the center pedestal but not on the BMS altimeter.

Same reason, there is no externalisation yet for that flag in the 4.32 shared mem
It is present  in the next BMS version

During the flight the altimeter datas of the two instruments don't show the same altitude but there is a discordance of about 100 feets
What I can do to have both instruments showing the same data?

I have been using MFDE and BMS 4.32 together for some time know and although there are(were) some inverted needle movement) I don't recall having the altimeter NOT matching unless I encoded a wrong pressure setting. But eventhough in that case, both altimeter (3D and exported) showed the same deviation)

[bluc69]

Red Dog,
many thanks for your message.
I'll look forward to BMS 4.33.

[sagrzmnky]

BMS 4.33 ??

  :rabbits:

Woah... how did that last one get in there. I don't know if I would be that excited, but who knows?  

[junior_1967]

Now that is good news! 

On the MFDExtractor's side, you are right in saying that the values do not match. I debugged the problem and traced it back to the way MFDEx determined if BMS 4.32 is running.
It would seem that the value of ProductMinorPart has been changed from what is now the value of FileMinorPart(Or something similar... working from memory here) to the actual number (32)...
Now the comparaison is no longer valid, reverting to non extended shared mem.

I've changed it for the right value and now my Altimeter displays the correct value.

So I guess Lightning will have to revisit this....

Cheers,

[bluc69]

Now that is good news! 

On the MFDExtractor's side, you are right in saying that the values do not match. I debugged the problem and traced it back to the way MFDEx determined if BMS 4.32 is running.
It would seem that the value of ProductMinorPart has been changed from what is now the value of FileMinorPart(Or something similar... working from memory here) to the actual number (32)...
Now the comparaison is no longer valid, reverting to non extended shared mem.

I've changed it for the right value and now my Altimeter displays the correct value.

So I guess Lightning will have to revisit this....

Cheers,

Could you please explain what I have to change and where?
Thanks

[junior_1967]

In Project MFDExtractor , in the file Extractor.cs find the following block:

                        if (newReader)
                        {
                            string exePath = F4Utils.Process.Util.GetFalconExePath();
                            FileVersionInfo verInfo = null;
                            if (exePath != null) verInfo = System.Diagnostics.FileVersionInfo.GetVersionInfo(exePath);
                            if (format.HasValue && format.Value == FalconDataFormats.BMS4 && verInfo != null && ((verInfo.ProductMajorPart == 4 && verInfo.ProductMinorPart >= 6826 ) || (verInfo.ProductMajorPart > 4)))
                            {
                                EnableBMSAdvancedSharedmemValues();
                            }
                            else
                            {
                                DisableBMSAdvancedSharedmemValues();
                            }

                        }


Replace the bold part by verInfo.ProductMinorPart == 32 && verInfo.ProductBuildPart >= 3  

Then do the same in this block

            else if (currentDataFormat.HasValue && currentDataFormat.Value == FalconDataFormats.BMS4 && verInfo != null &&
                     ((verInfo.ProductMajorPart == 4 && verInfo.ProductMinorPart >= 6826) ||
                      (verInfo.ProductMajorPart > 4)))

Compile and you should be good to go...

Cheers!

[Falcas]

A little voice tells me that a version of MFDE for 4.33 is already being tested. 😉

Gr Falcas

[Tulkas]

A little voice tells me that a version of MFDE for 4.33 is already being tested. 😉

Gr Falcas

And does the little voice say anything regarding how satisfactory the test are so far? 

Cheers

Tulkas

[Venom]

A little voice tells me that a version of MFDE for 4.33 is already being tested. 😉

Gr Falcas

And does the little voice say anything regarding how satisfactory the test are so far? 

Cheers

Tulkas

Extremely well


or at least I hope so.

[Falcas]

Works great. A lot of little changes and fixes for MFDE.
However, there is still a bunch of work that needs to be done.
I'll post a changelog later on.

Gr Falcas

[raptor]

Looking forward for an updated version. 

[Focaldesign]

If I turn the knob both move but they don't get synchronized.

As far as I know this is not possible because in BMS 4.32, the pressure setting is not externalized and MFDE will remain stuck at his default value.
Although the main needles of the MFDE exported altimeter will show the correct altitude according the the pressure setting inputted in the 3D cockpit.
So in the end, the needles are in sync, but the pressure windows is not, because it is not implemented as a shared mem bit in 4.32
So you will have to use the setting indicated in the 3D pit until 4.33 is released, where all that has been implemented.

How are you guys doing QNE/QNH settings in a homebuild pit when BMS empty shell is activated? Seems silly to turn empty shell off just so you can read/set the pressure, but I assume that's the only option now?

[Snowman]

Yes. Thats the only option.
Or set the altimeter to the airfield altitude but that clearly only works when ramping...


Snowman