Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JSBSim tables for MFD speeds outputs #52

Open
HHS81 opened this issue Feb 12, 2017 · 2 comments
Open

JSBSim tables for MFD speeds outputs #52

HHS81 opened this issue Feb 12, 2017 · 2 comments

Comments

@HHS81
Copy link
Owner

HHS81 commented Feb 12, 2017

simply add a table in the jsbsim file based on input given by the user and the various flaps settings, that is less perfomance heavy than nasal as it interpolates the values. With that we can easily also add Vmin and Vmax and other speed limits.

Warning lines: VMIN/VMAX
T/O: V1, VR, V2
CLIMB: VCL
CRUISE: VC, and as I already told you in the questions that I don't know the other two (3rd maybe VSTD)
LANDG: VFL0, VREF
SINGLE ENGINE: I have no idea

Jet version has different ones e.g. "T/O SPD" and "T/O PWR" -> have to check

@xcvb85
Copy link
Collaborator

xcvb85 commented Feb 12, 2017

I'm not sure if the calculation in Nasal is that big problem since the calculation is done only once per second (you can reduce it even further if you want). I doubt that you will see any difference.

I know that the jet version has a different menu structure. The content of "T/O SPD" is "FLAPS\n12", "V1\n110", "VR\n111", "V2\n124", "VSEC\n154", "MSG" (not sure with VSEC). I don't know the content of "T/O PWR". For this reason I used the menu from the prop version instead. The prop version has the sub menu "T/O TQ" which is currently missing. The content is "TEMP °C\n18", "TEMP °F\n64", "", "L100.0\nR100.0", "", "MSG"

@HHS81
Copy link
Owner Author

HHS81 commented Feb 12, 2017

I'm not sure if the calculation in Nasal is that big problem since the calculation is done only once per second (you can reduce it even further if you want). I doubt that you will see any difference.

yep, but it is easier to maintain since I have interpolated the Vspeeds from various sources. That was my intention behind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants