custom gcode in slic3r

[tmccafferty]

At the end of my print, one ofthe things that I want the extruder to do is move up 20mm from where it is and go to x0. I am using the following code:
M104 S0 ; turn off estruder heater
M140 S0 ; turn off bed heater
G91 ; set to relative positioning
G0 Z20 ; move Z axis up 20 mm
G90 ; set to absolute positioning
G28 X0 ; home X axis
G0 Y200 ; move table forward

everything works except the line to move the z up 20 mm
I can type the commands in the command line and they work.

Any ideas on what's going on?

[TLHarrell]

Is it somehow set to disallow rapid movements at that time in the code? Would you need to add code for movement speed?

[tmccafferty]

I just tried it with a G1 instead of the G0 and it worked.

[TLHarrell]

Nice. It's been a while since I had to do Gcode by hand, so I'm a bit rusty on the finer details. Good to see you got it sorted.

[Digitalmagic]

If you have to print again, it is good to have a similar script, keeping extruder & bed heating.

After a print, I rapidly quit the host software, unplug/plug the USB, and switch heating again.

[tmccafferty]

I put the code to turn the heaters off as a default in case I've left it printing on its own. If I'm going to print again immediately I just select the "set" button on Pronterface for the two heaters and press on.

[tmccafferty]

Ugh, I just thought it was working (or id did once). Even with G1 and a federate, it doesn't work.

Any ideas?

[rocketwiz]

I had the same issue. Turns out there wasn't enough current delivered by the z driver. Normal moves were fine but G0 and G1 commands seemed too much. You can try turning up your pot bit by bit while manually sending a G0 command.

[tmccafferty]

When I enter a g0 or g1 command from the console, it moves fine. The commands don't work though when embedded in the script.

[flurin]

Try with the code M400 (Finish all buffered moves).