Post print behavior

[MSURunner]

Okay, so after playing with many settings in my firmware throughout the process to attempt to match my machine with different upgrades and what not, I am afraid I have some sort of software/firmware glitchyness going on. After a print, I want the printer to stop the heaters, and return home, preferably with a retraction to avoid the little finished blob on the top of the part, but that's not nearly as important. I have tired a couple of different post script endings on the g-code files and none appear to be doing what I want. I've gotten some weird results. The biggest problem is the printer trying to return to the deck after the G28 command. Thoughts?

I have tried:

M104 S0 ;extruder heater off
M140 S0 ;heated bed heater off (if you have it)
G91 ;relative positioning
G92 E0 ;zero the extruded length
G1 E-1 F300 ;retract the filament a bit before lifting the nozzle, to release some of the pressure
G1 Z+0.5 E-5 X-20 Y-20 F{travel_speed} ;move Z up a bit and retract filament even more
G90 ;absolute positioning
G1 X0 Y0 Z400 F{travel_speed} ;move X/Y to min endstops, so the head is out of the way
M84 ;steppers off



M104 S0 ;extruder heater off
M140 S0 ;heated bed heater off (if you have it)
G91 ;relative positioning
G92 E0 ;zero the extruded length
G1 E-1 F300 ;retract the filament a bit before lifting the nozzle, to release some of the pressure
G1 Z+0.5 E-5 X-20 Y-20 F{travel_speed} ;move Z up a bit and retract filament even more
G90 ;absolute positioning
G28 ;return to home
M84 ;steppers off


AND


G92 E0
M107
M104 S0 ; turn off temperature
G28 ; home X axis
M84 ; disable motors

[geneb]

Try this:
M104 S0 ;extruder heater off
M140 S0 ;heated bed heater off (if you have it)
G92 E0 ;zero the extruded length
G1 E-1 F300 ;retract the filament a bit before lifting the nozzle, to release some of the pressure
G28

That should be all you need.

My Slic3r postfix configuration is simply:
M104 S0
M140 S0
M42 P6 S0 ; Turn off PEEK fan
G28

g.

[MSURunner]

Thank you gene, though it's still acting odd. After it returns to home it still starts slowly creeping towards the deck. Thoughts?

[Batteau62]

I had this issue too? I never did figure out what was causing it. My fix, which works, is an extra G28 command. I use Kisslicer, so I just added it to the postfix code. I'm on the latest version of Repetier for Windows. I'm interested to see what you find on this one.

[geneb]

Err. It homes, stops and then starts to slowly head toward the bed?

THat's very, very weird.

g.

[maxman]

Are you sure that the motors are actualy driving the effector down to the bed ?

On my printer when the steppers are disabled, the hot-end does slowly "sag" to the bed because of gravity, Though not usually all the arms move at the same rate. Your printer may just be better set up than mine

[geneb]

Blue Max does this exact thing. No stepper drive and the platform will slowly meander it's way to the bed.

Here's a test - if after a print you can easily move the effector around by hand, there's no power going to the stepper motors.

g.

[MSURunner]

Yeah, it's definitely the steppers moving the platform. It will stay at a height without power connected and there is stepper movement post print (confirmed in resistance and stepper noise). Going to try another slicer to determine if there is something odd in the g-code...

[dsnettleton]

Are you running your prints from SD card or Repetier Host? I know Repetier has a "Park" settings that moves the hotend to a specific position. I believe the default is (0,0,50). With your printer disconnected, just open up Printer Settings (Ctrl+P). Go to the printer tab and make sure the box that says "Go to Park Position after Job/Kill" is unchecked. To my memory, the park speed defaulted to very slow (80mm/s, maybe?). It drove me crazy, so I disabled it almost right away.

[geneb]

The docs do say to disable the park feature.

g.

[MSURunner]

From the SD, though I had unchecked park after print when in Repetier. I was slicing in Cura, trying some KS prints to see if there is any weird difference based upon slicer. I have been trying to introduce a new unit, so it gobbled up my time to devote to the Rostock for a couple days so I'm just getting to it. I guess my thought was in my scrolling through the FM to alter some menu values/adjust the printer I may have accidentally deleted a decimal point somewhere and someone ran across the same thing. You know how those simple typos can get you...

[geneb]

I SAID "LUNCH", NOT "LAUNCH"!!!!!!


g.

[MSURunner]

Exactly, haha, and with as many tweaks as I made, I don't really want to download another and try to sift through my values. I did have something happen yesterday that might be a clue, and I'm going to lazily throw it to you guys rather than sift myself. When I told the machine to "Home All" through the LCD panel, it homed and then started towards the deck. It did it twice throughout the day. I don't know why it did it, as every other time it just homed completely fine. Beginning to think my Rostock's got a sassy personality... I'LL HOME IF I WANNA HOME!

[PurpleDrank]

When I slice with Cura, mine does the same thing. I've used Kisslicer pretty much since I got the machine, and it doesn't do that, but I like Cura's gcode generation better. I'm guessing it could be something to do with the Repetier firmware interaction with Cura files? Anyone running Marlin and slicing with Cura seeing the same thing?

[MSURunner]

Okay, so I don't know what's going on here. Attached are two .g files (not viruses ) that illustrate my frustration. Hanger2.g ends up sending the head back to the deck, yoda.g doesn't. Hanger2 was generated with Cura and yoda with KISSlicer but I'm not sure WHAT the difference is in code. Both end with a G28 aside from some commented out information on the file...

[johnoly99]

MSUrunner,



NOTE ABOUT CURA!!!!


CURA will output the slicing parameters at the end of the Gcode file. Ulitmaker's firmware 'ignores' this post-fixed text, however most others don't. So, at the bottom of your gcode file you'll see a LONG string of text that looks like jibberish, that's the CURA slicing profile. Delete those lines or add a ; to the front of them to comment them out, and your .gcode file won't do the issue you are having anymore. I think there's a way in CURA to disable the output profile when generating the gcode.



Hope that help

[MSURunner]

Hrmmm, well it's commented out in the uploaded G-code file, but perhaps I need to attempt to disable it... I will work on that and hopefully after switching to .83 after talking with Steve we can find an answer to the problem...

[PartDaddy]

It's very long, I would delete it altogether.

[PurpleDrank]

I tried deleting the settings string but it still continued to do the creep. I put an M25 (pause SD Print) at the very end of the end.gcode in and it seems to have fixed the Cura Creep.

Edit: It works most of the time...