You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before submitting your issue please make sure to provide the following information
About your environment:
octopi
Octoprint version Version 1.3.11
Hi I currently use the GPIO to handle the power via PSU plugin.
my problem is that i need to execute the following and i can't find a way to do it:
using G4 doesnt work, since it sends it to the printer, printer replies as offline, print job fails.
seems the only way to delay Octoprint at the moment is via plugin, otherwise i would use the
gcode scripts. but there is no !local.delay that i can find.
Here is what i need to achieve to get back to "auto start printing from Cura"
;start power via power on plugin or via GPIO7
M80
;delay octoprint 3 Seconds
Delay S3
;Restart Firmware to reset ADC/Stepper Comms.
FIRMWARE_RESTART
;delay octoprint 7 seconds as it normally takes 6 seconds for the printer to restart
DELAY S7
;Printer Ready
The text was updated successfully, but these errors were encountered:
Before submitting your issue please make sure to provide the following information
About your environment:
Hi I currently use the GPIO to handle the power via PSU plugin.
my problem is that i need to execute the following and i can't find a way to do it:
using G4 doesnt work, since it sends it to the printer, printer replies as offline, print job fails.
seems the only way to delay Octoprint at the moment is via plugin, otherwise i would use the
gcode scripts. but there is no !local.delay that i can find.
Here is what i need to achieve to get back to "auto start printing from Cura"
;start power via power on plugin or via GPIO7
M80
;delay octoprint 3 Seconds
Delay S3
;Restart Firmware to reset ADC/Stepper Comms.
FIRMWARE_RESTART
;delay octoprint 7 seconds as it normally takes 6 seconds for the printer to restart
DELAY S7
;Printer Ready
The text was updated successfully, but these errors were encountered: