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

Feature request - console output filter #1371

Open
krepsy3 opened this issue Aug 2, 2023 · 0 comments
Open

Feature request - console output filter #1371

krepsy3 opened this issue Aug 2, 2023 · 0 comments

Comments

@krepsy3
Copy link

krepsy3 commented Aug 2, 2023

I have a feature request. I only use pronterface, and it gets installed though the Prusa suite installer, so I don't know about other parts of Printrun this could be relevant to. Also, my usage with an original Prusa i3 printer is where this request is coming from. I'll explain the issue I want to resolve by this request in the next paragraph, and give the details in the latter paragraph, if you wanna skip over that.

So, recently, Prusa updated their firmware for i3 MK3/MK2.5 family, and it was also an update for the MMU2/S units. The MMU update was a major overhaul, which makes the unit now constantly communicate with the printer mainboard through echo. So if the MMU is enabled in the printer settings, the Pronterface console is constantly getting spammed with some "echo MMU2 ##CODE##" messages. This reads the console unusable, because the commands you send and their output gets quickly lost in all the echo messages. There isn't really much you can do about it.

The feature I'd like to request is the ability to place a filter on the console output. You'll have a little filters window, where you can add, remove and activate/deactivate filters. Each filter is a regex or something like that. If a message that's to be outputted matches any filter regex, it gets disposed instead of shown.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants