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

NMEA decoding baudrate is wrong #221

Closed
hpsaturn opened this issue Oct 9, 2024 · 2 comments
Closed

NMEA decoding baudrate is wrong #221

hpsaturn opened this issue Oct 9, 2024 · 2 comments
Assignees
Labels
⬇️ low-priority Low Priority bug Something isn't working

Comments

@hpsaturn
Copy link
Collaborator

hpsaturn commented Oct 9, 2024

Overview

Sometimes, after performing manual reboots via the CLI, attempting to request the outnmea command results in bad characters, indicating that the baud rate may be incorrect. Additionally, you may notice that the main clock in the status bar displays an incorrect time of 00:00:00. If you perform one more reboot, the problem disappears. I believe this issue has been present in past versions, possibly in the master version, as the clock issue and the inability to synchronize GPS sometimes.

@hpsaturn hpsaturn added the bug Something isn't working label Oct 9, 2024
@jgauchia
Copy link
Owner

Maybe it's a problem when autobaud is selected.
I'll check it.

@jgauchia jgauchia self-assigned this Oct 10, 2024
@jgauchia jgauchia added the ⬇️ low-priority Low Priority label Oct 10, 2024
@jgauchia
Copy link
Owner

Unified in issue #236

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⬇️ low-priority Low Priority bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants