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

IBUS receiver does not work in BF 4.5.0 RC 3 (on my OMNIBUSF4SD FC) #13504

Open
wterreb opened this issue Apr 6, 2024 · 3 comments
Open

IBUS receiver does not work in BF 4.5.0 RC 3 (on my OMNIBUSF4SD FC) #13504

wterreb opened this issue Apr 6, 2024 · 3 comments
Labels
Template: Bug Set by auto_close_issue.

Comments

@wterreb
Copy link

wterreb commented Apr 6, 2024

Describe the bug

IBUS receiver on my OMNIBUSF4SD works perfectly in BF 4.4.3
But after I upgrade to 4.5.0 RC3 it does not work anymore.
If I go back to 4.4.3 again then it works again. Problem seem to only occur on 4.5.0 (I tried with RC2 and RC3)

To Reproduce

Upgrade OMNIBUSF4SD to BF 4.5.0 RC3 and choose IBUS as the radio protocol.

Expected behavior

After upgrade, IBUS receiver should continue to be detected and work

Support ID

00f2b709-6ece-48cc-9420-eec874dacae1

Flight controller

OMNIBUSF4SD

Other components

FlySky2A IBUS receiver

How are the different components wired up (including port information)

Receiver connected to Ibus input

Add any other context about the problem that you think might be relevant here

No

@wterreb wterreb added the Template: Bug Set by auto_close_issue. label Apr 6, 2024
@wterreb wterreb changed the title OMNIBUSF4SD does not work with IBUS in BF 4.3.5 RC 3 OMNIBUSF4SD does not work with IBUS in BF 4.5.0 RC 3 Apr 6, 2024
@wterreb wterreb changed the title OMNIBUSF4SD does not work with IBUS in BF 4.5.0 RC 3 IBUS receiver does not work in BF 4.5.0 RC 3 (on my OMNIBUSF4SD FC) Apr 6, 2024
Copy link

github-actions bot commented May 6, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week.

@github-actions github-actions bot added the Inactive Automatically detected and labeled, will be closed after another week of inactivity. label May 6, 2024
@blckmn
Copy link
Member

blckmn commented May 12, 2024

@SteveCEvans can this be in maintenance also please.

@SteveCEvans
Copy link
Member

I don't have any IBUS kit. This is a classic case for a git bisect to find the commit that fixed it. Do any of the devs use this?

@github-actions github-actions bot removed the Inactive Automatically detected and labeled, will be closed after another week of inactivity. label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Template: Bug Set by auto_close_issue.
Projects
None yet
Development

No branches or pull requests

3 participants