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.

Sign up for GitHub

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

Jump to bottom

FCU_SPD_SET event not working as expected #9881

Closed
paulalexandrow opened this issue Mar 1, 2025 · 1 comment · Fixed by #9884
Closed

FCU_SPD_SET event not working as expected #9881

paulalexandrow opened this issue Mar 1, 2025 · 1 comment · Fixed by #9884
Labels
A32NX Related to the A32NX aircraft Bug Something isn't working

Comments

@paulalexandrow
Copy link

Simulator Version

2020

Aircraft Version

Development

Build info

{
    "built": "2025-02-28T00:20:51+00:00",
    "ref": "refs/heads/master",
    "sha": "5aa9fbd1391e94d460f265c1731b8c4b772ae47f",
    "actor": "BravoMike99",
    "event_name": "manual",
    "pretty_release_name": "master:5aa9fbd1",
    "version": "a32nx-v0.13.0-dev.5aa9fbd"
}

Describe the bug

FCU_SPD_SET (see a320-events.md) does not work as expected.

Expected behavior

Call the FCU_SPD_SET event when in selected Mach mode and instantly get the new value selected on the FCU. This did work at some point and is currently still working in Speed mode.

Steps to reproduce

  1. Get airborne.
  2. Select (pull) Speed on the FCU.
  3. Call for example Event 78 (>K:A32NX.FCU_SPD_SET)

The selected speed will always be .99 unless a value < 1 is selected. In the latter case the selected speed will always be 0.10 (so min and max selectable values). Possibly some erroneous rounding or casting going on?

References (optional)

No response

Additional info (optional)

No response

Discord Username (optional)

No response
@paulalexandrow paulalexandrow added A32NX Related to the A32NX aircraft Bug Something isn't working labels Mar 1, 2025
@lukecologne
Copy link
Member

Oh, yes, you're correct. Simconnect doesn't support floating point parameters passed to K events, so we'll have to use the mach number multiplied by 100 (this is how the sim's own event does it too). Thanks for the report, totally overlooked that!

@lukecologne lukecologne mentioned this issue Mar 1, 2025
Merged
paulalexandrow added a commit to paulalexandrow/a32nx-webremote that referenced this issue Mar 1, 2025
@paulalexandrow
Modified for recent changes in FBW A32NX
398d2ba 
- Using new variables for barometric settings
  - Removed QFE functionality
  - Improved accuracy of inHg display
- Using new variables for EFIS ND controls
- Using new variables for FD, LS, APPR, LOC and EXPED buttons
  - FD buttons are now separated between CM1 and CM2
- Fixed ECAM STS button behavior
- Using new variables for navaid selectors
- Fixed VS/FPA display for dashes
- Added a workaround for proper altitude selection in sub-1000 steps
- A few under-the-hood improvements
- Known issue: Mach selection does not work (see flybywiresim/aircraft#9881)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A32NX Related to the A32NX aircraft Bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(a32nx/fcu): use mach * 100 for selected mach set event lukecologne/a32nx
2 participants
@paulalexandrow @lukecologne