Open BeppeTemp opened 2 years ago
Hi Beppe,
It looks like Prusa might be slower to initiate, can you try a 60 or 120 second delay to see?
Is the printer on AMC0?
What is AMC0 ?
I tried with 120 seconds but nothing, simply when I press "upload and print" the print turn off after 120 seconds, after that the gcode is uploaded but print not start
What were you doing?
Initial situation: Octoprint server tuned on (indipendente from PSU Control), Printer turned off (controlled from PSU Control, with HomeAssistant Plugin)
How I could see in different issues and posts on octoprint forum, the problem seems is related to an ulterior delay, necessary but not implemented.
In my opinion are necessary two delaies:
What did you expect to happen?
After I press upload and print on Prusa Slicer, Octoprint turn on printer, wait "post delay time" (set to 10) receive the gcode file and start the print.
What happened instead?
After I press upload and print on Prusa Slicer, Octoprint turn on printer, wait "post delay time" (set to 10) receive the gcode file but don't start the print.
Version of OctoPrint-PSUControl: 1.0.6
Operating System running OctoPrint
I installed octoprint on a raspberyy Pi 4 2 Gb with Raspberry Pi Imager (Prebuild Octoprint Image)
Printer model & used firmware incl. version
Prusa MK3S+ firmware version 3.11.0
Link to octoprint.log with octoprnt.plugins.psucontrol set to DEBUG
serial.log octoprint.log