V-Speed Calculator and Setter (XML Gauge)

Hello everyone

I had created an XML gauge to calculate and set V-Speeds in the MJC8 Q400. As the related discussion thread was lost with the death of the old forum, I am listing the URL's here for those who are interested.

(1) The gauge can be downloaded at:
https://www.dropbox.com/sh/mycyc680qj2bnc2/AADA8bFhjQ1gQ4s3hBRTeGTEa?dl=0

(2) The gauge requires the concurrent installation of Tom Aguilo's XML Tools:
FSX: https://www.fsdeveloper.com/forum/resources/xmltools-2-01-xml-expansion-module-for-fsx.148/
P3Dv2: https://www.fsdeveloper.com/forum/resources/xmltools3d-a-common-xml-expansion-module-for-p3d-2-2.132/
P3Dv3: https://www.fsdeveloper.com/forum/resources/xmltools3d-for-p3d-v3-x.168/
P3Dv4: https://www.fsdeveloper.com/forum/resources/xmltools64-for-p3d-v4-v1-0.197/

(3) If you are using the XML Tools version for P3Dv4 you may need to download an update from the thread at:
https://www.fsdeveloper.com/forum/threads/xmltools-xmltables-not-functioning-correctly.440850/

I have attached the latest README to this post.

Regards,

Chakko

Comments

  • I installed everything, but all of a sudden I had no atc. I don't know if it was the xml tool for my p3d 4 or what but I had to reinstall p3d.

  • edited July 30

    It looks interesting, but I managed to open this window only once...
    I probably me it closed it, it no longer appears...
    Maybe incorrectly made changes to configuration files?

    P3DV4\SimObjects\Airplanes\mjc8q400\ panel.cfg
    22 11

    dll.xml
    33

    view
    44

    XMLTools64
    55

    What's wrong?

  • Press the "Alt" key to open the menu bar. Under the vehicle tab/instrument panel, there will be a list of all of the Q400 panels, including the v-speeds gauge.

  • edited July 31

    I alternately pressed both, the left and right ALT key, and the only thing that happens is the Selection of the tab scenario in the upper left corner of the screen...
    what am I doing wrong? :(
    what

  • edited July 31

    You just have to click the "vehicle" tab, then, in the drop down window, move your mouse cursor over "instrument panel", and the list of panels should be displayed. It is then only a matter of moving your mouse down the list to the Q400 V-speed gauge and clicking on it.

  • edited August 1

    exactly :D thx o:)
    but he gauge now displays erratic and spurious results from the V-Speed computation...
    and used the latest version XML Tools, probably the XML Tools module needs to be updated again ...
    speeds

  • edited August 1

    everything works, but only with the XML Tools version from the : https://www.fsdeveloper.com/forum/attachments/xmltools64-zip.40019/
    Thx!

    made a mini comparison for flaps 5 with a similar script but running on Lua Script (in FSUIPC) http://majesticsoftware.com/forums/discussion/494/majestic-q400-v-speed-calculator-
    and-setter#latest

    speeds

    As you can see, the lua script uses accurate data on the table for a weight of 28000 kg, (although the actual one is about ~26400) and it is more logical to use a table with a weight of 26000 maybe?
    at that time, the XML gauge does not use the weight of either 26,000 or 28,000, but takes something in between these weights, I wonder how it would actually be more correct, any thoughts?

  • @niksan29 said:

    made a mini comparison for flaps 5 with a similar script but running on Lua Script (in FSUIPC) http://majesticsoftware.com/forums/discussion/494/majestic-q400-v-speed-calculator-
    and-setter#latest

    speeds

    As you can see, the lua script uses accurate data on the table for a weight of 28000 kg, (although the actual one is about ~26400) and it is more logical to use a table with a weight of 26000 maybe?
    at that time, the XML gauge does not use the weight of either 26,000 or 28,000, but takes something in between these weights, I wonder how it would actually be more correct, any thoughts?

    The gauge is programmed to "linearly interpolate on the weight axis (and altitude axis if applicable) of the MJC8Q400 T/O Speeds Card, and then round up to the next highest integer." This is why you are seeing an intermediate value in the example you have chosen. But the LUA script (not my creation) does not do that; it works with the higher of the two values.

    I chose to interpolate, because the MJC8Q400 T/O Speeds Card tables are actually only a summary of the original tables which contain more intermediate data points on all axes.

    The work of interpolation is done by the functions provided by the XML Tools package.

    The gauge was developed for FSX SP2, which I still use exclusively :-) . I have no experience with its extended use in P3D4, so I leave it to other users to comment on that. It is a pity that the original discussion thread with a lot of relevant information has been lost.

  • @ckovoor said:
    But the LUA script (not my creation) does not do that; it works with the higher of the two values.

    Yes, in the screenshot above, we can just see it

    @ckovoor said:
    t is a pity that the original discussion thread with a lot of relevant information has been lost.

    I completely agree

    I also wanted to ask you what you think about this:
    http://majesticsoftware.com/forums/discussion/509/mjc8-q400-landing-speeds-card-incomplete-data#latest
    ?

  • edited August 7

    noticed a small problem, does not add + 20 to Vref (only flap 35), when icing button pressed
    ice
    it would be great if you fixed it :) o:)

  • @niksan29 said:
    noticed a small problem, does not add + 20 to Vref (only flap 35), when icing button pressed

    Thanks for pointing this out.

    Now, the Majestic Landing Speeds Card says:
    "When flying in icing conditions, Add 20 kts to Vapp, Vref, Vga for Flaps 10, 15 and 35":

    However, the Q400 AOM says:
    "Add 20 kts to Vapp and Vga for Flaps 5, 10 and 15 on initial detection of ice and when flying in icing conditions"
    and:
    "On initial detection of ice and when flying in icing conditions, Add 20 kts to Vref for Flaps 10 and 15 and 15 kts for Flaps 35"

    Currently the code executes this instruction:
    "-- if icing conditions and Flaps 5, 10 or 15 add 20 kts each to Vapp, Vref and Vga and check some flap selected to avoid increasing numbers if ICING pressed alone --"

    I shall consider amending the code to also include this subsequent instruction:
    "-- if icing conditions and Flaps 35 add 15 kts to Vref and check some flap selected to avoid increasing numbers if ICING pressed alone --"

    I'll notify the forum of any revision once I get to doing it.

    Regards,

    Chakko.

  • edited August 10
    > @ckovoor said:
    > Thanks for pointing this out.

    thank you o:)

    > @ckovoor said:
    > Now, the Majestic Landing Speeds Card says:
    > "When flying in icing conditions, Add 20 kts to Vapp, Vref, Vga for Flaps 10, 15 and 35":
    > However, the Q400 AOM says:
    > "Add 20 kts to Vapp and Vga for Flaps 5, 10 and 15 on initial detection of ice and when flying in icing conditions"
    > and:
    > "On initial detection of ice and when flying in icing conditions, Add 20 kts to Vref for Flaps 10 and 15 and 15 kts for Flaps 35"

    Better done and as majestic says o:)

    > @ckovoor said:
    > I'll notify the forum of any revision once I get to doing it.

    I will really wait, flaps 35 are my favorites B)


    p/s FCOM says:
    Holding, Approach and Landing (REF SPEEDS to
    INCR)
    Use Flap 35° for Landing unless CAT II approach or with one engine inoperative.
    Bug increased VREF Speed and VCLIMB + 20 kts.
    And Icing conditions and Ref Speeds Switch – INCR: Increase speed by 20 kts.
Sign In or Register to comment.