Hello all,
I have a peculiar problem. When octolapse is enabled, I can't upload *.bgcode to octoprint, either through prusa slicer or dragging and dropping. In both cases the upload seems to work, but after uploading Prusa slicer gets a 502 error and the drag and drop tries to start over. After that, in both cases the octoprint service just crashes and I have to restart it through ssh.
In both cases, simple *.gcode works.
I am not familiar enough with octoprint to know what I need to send, so please bear with me.
Here is the relevant information:
Raspberry pi 4B
Prusa Mk4S
Octoprint version: 1.10.3
Octolapse version: 0.4.5
Bgcode plugin version: 0.2
Just disable the option "Supports binary G-code" on the printer tab in PrusaSlicer, see screenshot.
The existence of the bcode format imho is only a crutch to overcome the bandwidth limitation on the networking hardware (ESP boards) for PrusaLink/PrusaConnect. If you are using a Raspberry Pi or other more capable network hardware to connect your printer, you don't need it.
That's what I'm doing atm. The problem is that the gcodes are huge compared to their bgcode counterparts, and ideally I'd like to keep using it. Also, as far as I can understand it, it's still a bug.
I think it's more .bgcode crashes Octolapse.
Octolapse looks for layer changes but can't find them because of the binary code and so it runs into nirvana and takes OctoPrint with it.
to give you perspective, it doesn't matter, because if you are using my plugin to support bgcode in the first place, the file is extracted into the full gcode size anyway, it's just stored with the same bgcode extension, but it's not. it's actually the plain text gcode file post conversion.
