-
Notifications
You must be signed in to change notification settings - Fork 6
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
VIRTUAL printer broken after installing MeatPack plugin #29
Comments
What these numbers refer to? Issues somewhere but where?
and
|
I'm confused about why you want to have MeatPack enabled when using a Virtual printer? It won't work, and doesn't really serve a purpose in that use case. It needs to hook into and override the serial port creation so it can interface directly with the printer and send it the compressed data. There is no callback or event hook for OctoPrint which allows outgoing serial data to be arbitrarily changed before it goes to the printer. At least with the performance and granularity required here. -- Those numbers refer to issues on the original OctoPrint repo. The serial code is mostly copied from what is already used internally. |
Wanted to implement meat pack in virtual printer (virtual printer is used for testing things in octoprint without real hardware). Thanks for pointers. |
Doing so would require implementing the associated unpacking/decompression code on the virtual-printer side. I do know that Prusa's MK404 printer emulator w/ the MeatPack PR applied to the firmware image works with OctoPrint + MP. In fact, this is how they tested the PR before approving it. |
MeatPack overrides serial port opening (could it not do that?) which causes Virtual Printer (available by default in any OctoPrint installation) to be broken:
The text was updated successfully, but these errors were encountered: