Skip to content

Suggestions to improve serial port error logging #102

@nightswimmer

Description

@nightswimmer

I am currently testing some custom USB harp hubs and having some issues with noise on the USB data lines that cause a lot harp messages being discarded sometimes. While doing these tests I usually have several boards connected all of them spamming data. We can see the failed messages showing up on the bonsai console window.

When doing these types of tests, there are some changes that could simplify the process:

  • Printing also the COM port associated to the error. Currently when we do get errors, we have no idea where they come from looking at the log. We need to count the messages per seconds and check if the count is within the expected values. And even like this, this is not so easy to detect if the errors are very sporadic.
  • Having a way to clear the console. I found myself doing tests where there were barely any errors happening, so I knew while the console was empty there had been no errors. Then when I did get errors, I would shut down bonsai and open it again, just to get the console empty again. This might be a very specific situation, I don't know if there are any other good use cases for this. But having a clear console button, or maybe alternatively an option to clear the console automatically when pressing play would be interesting.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions