Post by jimustanguitar on May 7, 2015 1:05:00 GMT -5
Hey guys!
I've been using OctoPrint for a while now, and it's not very happy with me trying to print the same part twice in a row. The blue print button doesn't kick the printer into gear, and I have to restart the program and reconnect to get things to work again.
Has anybody else seen this? OctoPrint glitch, or Repetier firmware timeout?
I usually hit the x/y home button and z home button before starting another print. I have found that sometimes Octoprint seems unresponse for no apparent reason, and it will queue up my commands until the logjam clears, and then it executes all the commands in the order I gave them just fine. Moral of the story, try issuing a move command through Octoprint before starting another print.
How does Repetier factor into this? I assume you are uploading gcode to Octoprint and then printing that from the Octoprint interface.
How does Repetier factor into this? I assume you are uploading gcode to Octoprint and then printing that from the Octoprint interface.
It's the firmware that I have on the Rambo board. I haven't dug into it to look for a culprit, but thought it might be possible that there's an idle timeout built into the code...
I'll try sending some manual commands to "wake it up" before I try printing next time.