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

Approach speed #65

Open
Marci353 opened this issue Jul 8, 2023 · 5 comments
Open

Approach speed #65

Marci353 opened this issue Jul 8, 2023 · 5 comments

Comments

@Marci353
Copy link

Marci353 commented Jul 8, 2023

Hi,

I wrote a few days ago a post with an issue at .org, I found another one, I post it here.

So whatever I do, I get the warning with the "approach speed", see picture below. Vref is setted always, in general 40/xxx.

I fly Zibo.
1

@Clamb94
Copy link
Owner

Clamb94 commented Jul 8, 2023

Hi, thanks for the report. I'll check it next weekend

@Marci353
Copy link
Author

Marci353 commented Jul 8, 2023

Hi Axel,

thank you for you reply.

Additionally, I copy here my post from the .org, with another issue.

"Hi Axel,

what a fantastic plugin! Thank you!

But I have the same problem as [@jonesm35205]. I checked all the datarefs, my speedbrake is armed, but the report still seeing this different. What can cause this?

I fly Zibo, speedbrake by axis."

2
3

@Marci353
Copy link
Author

Marci353 commented Jul 9, 2023

I think I solved the approach speed issue.

I changed the "and" to "or" in the string:

($laminar/B738/FMS/vref - 3) <= $sim/cockpit2/gauges/indicators/airspeed_kts_pilot or ($laminar/B738/FMS/vref + 20) >= $sim/cockpit2/gauges/indicators/airspeed_kts_pilot

@Marci353
Copy link
Author

Marci353 commented Jul 9, 2023

I think I solved the speedbrake issue too, but will test it again and again.

I deleted the minus from < 0.1 (originally it was < -0.1, which is not possible since the min value is 0, maybe it was a typo)

UPDATE:

it is not enough. For some reason the plugin monitors the speedbrake AFTER touchdown, when it will have a value more than 0.1 due to rollout and decceleration because of the groundspoilers. The "till" is set to #TD-3000ms, so I dont know why the plugin doesnt stop monitoring the speedbrake 3 sec before toucdown...

@Marci353
Copy link
Author

So, I am sure that there is a problem with #TD-3000ms. The "FMC/Flap disagree" also appears (not always, but often), even if the position is correct.

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

No branches or pull requests

2 participants