Delay after finish printing

Check the ending GCode script in OctoPrint. See what it is up to. Or add some to whichever slicer you use that raises the Z a few mm when done.

 

Hmm, well make sure you check OctoPrint too. Mine sometimes pauses a few seconds there.

 

Sure, might sort it. The delay could be coming from the commands to switch off everything so moving the head away first would get done faster.

 

I believe there is a slight delay between the commands issued in sliced G-Code and switching to code included in OctoPrint's "After print job completes."

 

I would just add a lift to Cura, and leave the OctoPrint alone.

In Cura click on the Printer name, then Manage Printers, then Machine Settings in the dialog, add something like the following at the beginning of End Gcode.

Code:

G91 ; relative positioning
G1 Z10 ; move hotend up 10 mm
G90 ; absolute mode

What this does is move up 10 mm from the last position as soon as the last print or movement command is issued. It will execute this before OctoPrint takes over and executes it's own code. Although @mark tomlinson might disagree (he is a big fan of doing all sorts of stuff in OctoPrint) there are times when you just have to do extra stuff with the slicer.

 

After doing some testing with the Robo web interface and scripts section, there is a noticeable delay in script execution. This can be verified with personal testing. The delay is several seconds. So you will have the nozzle sitting on the top of your model and it may leave a scar or mark while the R2 decides to run the OctoPrint script.

The best remedy is to add code to your slicer to lift the nozzle at the end of the print job. That code will execute as quickly as any other code in your model print, then the delay has no impact.