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

[Master] Tuning tab hangs using F405 controllers #2085

Open
Jetrell opened this issue May 19, 2024 · 3 comments
Open

[Master] Tuning tab hangs using F405 controllers #2085

Jetrell opened this issue May 19, 2024 · 3 comments

Comments

@Jetrell
Copy link

Jetrell commented May 19, 2024

When using the configurator master build to date.
And using the master firmware post 2719472 . I can not get any F405 controller I have tested, to access the Tuning tab. It just hangs indefinitely.

But after speaking with @breadoven who said he had not had this issue. But also referenced he was using an F722.
I then proceeded to try the above builds with one of my F722 controllers.. And after a slight delay, the Tuning tab loaded.
So it appears to have a greater affect on the F405 controllers.

For reference. I tested.
Mamba F405
Matek F405
Speedybee F405

Windows 64 OS

But I'm not saying its totally caused by the above mentioned PR.. It just happens to have made an addition to the Tuning tab.
I also notice the Advance Tuning tab occasionally doesn't loading. And the Alignment tab will exit to the landing page.

While If I use the latest master firmware. And use my last NW.js builds of 8.0, everything works as expected with all FC's.
I'm sorry I can't be anymore specific.

@breadoven
Copy link
Collaborator

I tried this with an F411 and an old Omnibus F4 Pro (F405 I believe) and the Tuning tab works OK for both. That's with the latest Configurator master and fairly recent INAV master (2 weeks old perhaps).

Don't see why #9471 would affect the Tuning tab though. I'm not aware any of the changes are used for that tab at the moment.

@Jetrell
Copy link
Author

Jetrell commented May 19, 2024

@breadoven I'm not totally sure of what the go is either. But these are the results I get.

And why I can use one of the last nw.js versions of the configurator on all the firmware's of have tried with success.
While the previously mentioned results are what I see with electron.

I tested everything I could think of before opening this issue report. Because I was second guessing myself, when not hearing of issues from anyone else. But I don't know what else it could be ?

@breadoven
Copy link
Collaborator

Do you run Configurator in development mode so you can get error info from the console ? May not show anything though if it just hangs.

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