-
-
Notifications
You must be signed in to change notification settings - Fork 150
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
Black Box Website not showing logs #811
Labels
Comments
Please try https://master.dev.blackbox.betaflight.com/ |
Thanks, this works On Jan 30, 2025, at 2:26 AM, Mark Haslinghuis ***@***.***> wrote:
Please try https://master.dev.blackbox.betaflight.com/
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
@blckmn , can the web-app be put in sync with master again please? |
If this was to me, I deleted that log ages ago and have been using the have just been using the linked black box configurator since. Some of my traces look strange though , should I send a log? On Feb 5, 2025, at 9:24 AM, Vladimir Demidov ***@***.***> wrote:
Share broken log please.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
@Weeperr , please use Betaflight Discord for support: https://discord.betaflight.com/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
For the past couple days whenever I load I blackbox log onto blackbox.betaflight.com, it doesn't show any data, just the wave form at the bottom of the screen. I've tried two different quads to make sure that they're not the problem. I had been uploading logs daily for the previous couple weeks with no issues.
To Reproduce
load a black box log onto the website
Expected behavior
data should appear after log is loaded
Betaflight Blackbox Explorer version
the website version
Add any other context about the problem that you think might be relevant here
No response
The text was updated successfully, but these errors were encountered: