Closed craigcabrey closed 1 year ago
I can confirm that the truncating issue happens to both printers.
[craigcabrey@zephyrus Downloads]$ sha1sum Pre-upload.gcode
a20f3181f535207175fa6d7bd3782d6fb813ddce Pre-upload.gcode
[craigcabrey@zephyrus Downloads]$ sha1sum Post-upload.gcode
8403f72e886218f5d784b1e100f53932abce6392 Post-upload.gcode
I take back what I said about scp -- I see the same issue. scp'ing to the home dir goes fine (same hash), but then moving it into the docker volume changes the hash.
I'm not sure if I'm seeing the beginning of hardware failure or something funky with Docker volumes. Either way, it seems like it's not an issue with the software stack.
This is quite a whacky issue I had to narrow down. For additional context, I am using the multiple printer custom compose file. Previously, I was using the standard setup with an Ender 3 S1 without any trouble (I haven't yet confirmed if the S1 instance is also experiencing this).
docker-compose.yaml (from prind 1.8.0):
I uploaded a Calibration cube from PrusaSlicer (but also directly via Fluidd just to be sure) and the hash is different:
It seems like roughly ~4k lines (not sure if there is a pattern here) went missing. I noticed this when my
END_PRINT
macro was nowhere to be found, but the pressure advance gcode I manually scp'd over did.Any ideas welcome! For now, my workaround is to scp gcode over to my Pi but obviously I would much rather upload directly from within PrusaSlicer.