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

Investigate Booster serial port usage with TeraTerm and Putty #234

Closed
ryan-summers opened this issue Oct 10, 2022 · 3 comments · Fixed by #236
Closed

Investigate Booster serial port usage with TeraTerm and Putty #234

ryan-summers opened this issue Oct 10, 2022 · 3 comments · Fixed by #236
Assignees

Comments

@ryan-summers
Copy link
Member

We have had a number of reports that users struggle to get Booster's serial port to function when communicating with Putty or TeraTerm. Users report that no output is shown and can't communicate with the device, but other descriptions of device functionality seem to indicate that Booster is otherwise operating normally (e.g. fan startup self test is heard, LEDs show disabled channels).

@ryan-summers ryan-summers self-assigned this Oct 10, 2022
@ryan-summers
Copy link
Member Author

It appears that this is the result of Putty not sending a \n when the user presses Enter. Instead, Putty sends just <CR>. In putty, the only way to insert a is using Ctrl+J.

Interestingly, even enabling "Implicit LF on CR" does not appear to resolve the issue. The user is required to press Ctrl+J to submit a command with the current design.

@jordens
Copy link
Member

jordens commented Oct 10, 2022

Speculating: maybe the latter is because then cmd<CR><LF> is not recognized the way cmd<LF> would be.

@ryan-summers
Copy link
Member Author

ryan-summers commented Oct 10, 2022

Currently, firmware just looks for the b'\n' character, which is a single LF. If there's a prepended , that should still cause it to parse the command and would still work.

With the local echo, it can be seen in the Putty display that no newline is created (so no is sent by Putty and echo'd back). I think we should just accept either or as the termination character.

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

Successfully merging a pull request may close this issue.

2 participants