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

Pause at TOD doesn't trigger when thrust is not in managed mod #8261

Closed
hargn opened this issue Oct 22, 2023 · 8 comments · Fixed by #9517
Closed

Pause at TOD doesn't trigger when thrust is not in managed mod #8261

hargn opened this issue Oct 22, 2023 · 8 comments · Fixed by #9517
Labels
Bug Something isn't working

Comments

@hargn
Copy link

hargn commented Oct 22, 2023

Aircraft Version

Development

Build info

{
    "built": "2023-10-20T23:27:31+00:00",
    "ref": "refs/heads/master",
    "sha": "581edbca8c25bad8562274fef1370bbcbf9545c8",
    "actor": "Gurgel100",
    "event_name": "manual",
    "pretty_release_name": "master:581edbca",
    "version": "v0.11.0-dev.581edbc"
}

Describe the bug

This is an issue i've encountered on the HW A339 here : headwindsim/aircraft#77

As i believe it's related to the FBW systems and EFB, i post it here in order it can be solved.

Two times in different flights the aircraft didn't respect the Pause at TOD :
I've found it still flying at cruise level after to have overpass the last flightplan waypoint in the last heading it had the time it reached it.

After some tests, i've figured that the Pause at TOD doesn't trigger when the Speed Selector has not be enforced in managed mod.

Expected behavior

When the aircraft reach the point on flightplan, the distance it has been set in the EFB from the TOD point and the AP is on, the aircraft should pause the simulation, whatever the state of knobs on the FCU.

Pause at TOD should trigger if the autothrust is in managed mod or in selected mod.

Steps to reproduce

  1. Take the aircraft in cruise level, far away the TOD, with the AP on, and the autothrust in
  2. Setup in the EFB the Pause at TOD feature, at a random distance (at it seems to don't matter)
  3. Disconnect the AP : Pause is triggered.
  4. Click OK and reconnect the AP
  5. Disconnect the AP : Pause don't trigger
  6. Reconnect the AP and push the Speed Selector knob to enforce the managed speed
  7. Disconnect the AP : Pause trigger as it should

References (optional)

No response

Additional info (optional)

No response

Discord Username (optional)

alwiswennerstroem

@hargn hargn added the Bug Something isn't working label Oct 22, 2023
@Revyn112
Copy link
Contributor

@hargn can you test this behaviour in the a32nx aswell?

@hargn
Copy link
Author

hargn commented Oct 22, 2023

Yes i'll test, but not today : i'm on a OMDB-WSSS flight with the HW A339 on which i've performed my tests.

@Maximilian-Reuter
Copy link
Member

Just to clarify, by Autothrust Knob you mean the Speed Selector ? Ie. Managed and Selected Speed ?
image
this one ?

@hargn
Copy link
Author

hargn commented Oct 22, 2023

Yes, you have to push it even if the aircraft is in managed mode in order to activate the Pause at TOD, after it has been triggered once.
The best, i think, would be to have the pause at tod working whatever the aircraft is in managed or selected thrust.

@tracernz
Copy link
Member

@2hwk Do you remember why it only pauses when speed is managed? It explicitly checks that in the code.

@hargn
Copy link
Author

hargn commented Oct 30, 2023

Hi, i did some tests this weekend and the FBW 32NX has the same behavior than i've described.

@hargn
Copy link
Author

hargn commented Nov 17, 2023

So i did some tests and i've reproduced the issue on the FBW32NX.
It seems that the problem where you have to push the thrust knob to enforce the managed mod was due to a timeout (10s if i remember the code).

So i can make a PR where i can:

  1. Remove the condition on the managed mod, in order to have the break at ToDwhatever the speed mode engaged (managed or selected)
  2. Remove the timeout, or reduce it

Another thing i would also change, is the maximum of 50NM for the distance from ToDthe pause should be triggered.
In SLC (Self Loading Cargo) i use, you've to advert the crew minimum 10min before the ToD, and 50NM is too late.

@2hwk
Copy link
Member

2hwk commented Dec 16, 2023

@2hwk Do you remember why it only pauses when speed is managed? It explicitly checks that in the code.

I believe it's part of the check that automatically pauses the sim if AP has been disengaged before TOD. It's supposed to detect that the AP has been automatically deactivated due to a sudden deviation caused by weather or other factors and immediately pause the sim then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants