Pylon: Make CAN baud rate configurable and not always stuck at 500#2127
Merged
dalathegreat merged 1 commit intomainfrom Mar 12, 2026
Merged
Pylon: Make CAN baud rate configurable and not always stuck at 500#2127dalathegreat merged 1 commit intomainfrom
dalathegreat merged 1 commit intomainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
This PR fixes a bug where the UI would show CAN baud rate always set to 250, even though it changed under the hood
Why
We fix this bug, since it confuses users easily
How
Instead of glitchy dropdown, we let user manually enter baud rate. This makes it easier to maintain longterm
Tip
You can help test this PR with this guide