What is the problem?
Every Printjob starts with GCODE-Script "After print job completes"
What did you already try to solve it?
I tried to delete script and change gcode but nothing happens. If I start a new job I start with the (old)Script which was intended for the finished job.
Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, octoprint.log, serial.log or output on terminal tab, ...)
Version 1.3.9 / Raspberry Pi 3
Remote in to your Raspberry Pi:
ssh pi@octopi.local # default password is "raspberry"
Then navigate to where OctoPrint stores these scripts:
cd ~/.octoprint/scripts/gcode
Review the various scripts there, for example:
cat afterPrintDone
G92 E1
G1 E-1 F300
G28 X Y Z
M104 S0
M84
cat beforePrintStarted
OCTO801
G91
G28 X0 Y0 Z0
G90
G92 E0
G29
You might even try to edit one if you don't love it:
nano beforePrintStarted
Then restart OctoPrint.
Thank you for the fast reply. I review the scripts "afterPrintDone" and "beforePrintStarted" and I saw exactly the same what I found in the Octoprint-Settings. If I modify the file over ssh I can find the changes in the settings (after restart).
Problem is, that Octoprint always add an old version of "afterPrintDone" to the beginning of the Gcode when I start a Printjob, I never used "beforePrintStarted" and its still empty.
So you're saying that you edit beforePrintStarted in either the GUI or from a command line and you can see the changes in the other place... and then after a restart of OctoPrint... it ignores you and does its own thing by reverting? Here, I would have confirmed that the changes persist after the restart (the text file or Settings dialog agree with my intent) before sending another print job to be the guinea pig. If they don't (meaning that upon a restart OctoPrint has written over my changes) then I would fight that battle to try to determine what's going on.
Can you confirm:
If so, then this sounds like a bug.
And of course, all this needs to be done a second time having rebooted IN SAFE MODE from the System menu. If it now works as expected yet it failed above, then one of your plugins is behaving badly.
Ok I now try the following:
I open beforePrintStarted in ~/octoprint/scripts/gcode with nano over ssh:
--> the file is empty
I open afterPrintDone in ~/octoprint/scripts/gcode with nano over ssh:
I see:
G90 ; use absolute positioning for the XYZ axes
G0 Z180 F3600 ; move to the Z=200mm position on the bed
G0 X140 F3600 ; move to the X=150mm position on the bed
G0 Y140 F3600 ; move to the Y=150mm position on the bed
M81 192.168.0.199 1 ;Schalte Steckdose aus
Now I look in the OctoprintSettings over Webinterface:
--> beforePrintStarted is empty
--> afterPrintDone is the same as what I see over ssh
Now I modify afterPrintDone over ssh and restart octoprint
--> I can see the modification in the settingsTab of WebInterface
Now I open Webinterface and click "open and print"
This is what I see in the Terminal:
I cut Power from printer because he dont know where Z=200 is (there was no homing before)
This Part (copy from Terminal) can I identify as an old Version from "afterPrintDone" :
Send: N3 G0 Z200 F36001
Recv: ok
Send: N4 G0 X150 F36002
Recv: ok
Send: N5 G0 Y150 F3600*2
Recv: ok
Now I start Octoprint in safeMode and start the same printjob. It seems to be ok.
Have you opened the GCode file you're printing? I'm guessing this is actually coming from the slicer, and is in the actual GCode file itself. In that case, you will need to change your slicer settings, because you've got the slicer set up to prepend the GCode in question.
Please note: You've confirmed the GCode you are concerned about doesn't match what is in the settings in the GUI or filesystem, and you've restarted the server, so whatever is in the file is all OctoPrint knows about (unless you're running a non-standard python interpreter setup that is caching something in a VM - highly unlikely), which is what leads me to believe you need to check your slicer settings before continuing.