Maestro pause/resume ends up about 0.5mm above original Z

Phaedrux

I'll take a closer look later today when I'm at my laptop. It's a little hard on a phone.

norbs12

@norbs12 said in Maestro pause/resume ends up about 0.5mm above original Z:
OK thanks.

I should probably mention that I replaced a duet 2 ethernet on this printer with a maestro so I could use the duet 2 ethernet on another printer.

The few things i changed after the move to the maestro was:

Uploaded the Maestro firmware (though the duet 2 one seemed to boot).
Disable sensorless homing and used limit switches for X and Y.
Change thermistor settings to work with maestro.
Ran heater autotune again since nothing was heating with the old PID settings.

I don't think any of that would have any affect on pause/resume but I thought I should mention it.

Phaedrux

What do you have in your resurrect-prologue?

https://duet3d.dozuki.com/Wiki/Setting_up_to_resume_a_print_after_a_power_failure

Note: recent firmware versions write a G92 command containing the coordinates at the time of failure into resurrect.g, just before the call to resurrect-prologue.g. So you may get away without homing axes. But it is still best to home any axes that you can (typically X and Y on a cartesian or CoreXY printer).

So that explains the G92 in resurrect. How are you homing the printer in prologue? Were you using baby stepping on this print before the power loss?

norbs12

@phaedrux

My resurrectprologue.g is empty (well all commented out).

Yes I was using +0.16mm baby stepping, however, this isn't even a power failure. Just a pause and then resume after. There is no need to home anything since the printer is still homed.

I included my resurrect.g because I don't know 100% how the pause/resume process works and thought it might have relevant info since it's generated on pause.

Does the maestro handle pause/resume differently than a duet 2?

Phaedrux

Sorry, I missed that detail that it's just a pause and resume. In that case the whole power loss thing doesn't even come into play at all.

Your pause.g and resume.g look a little different than mine. This is what I have.

; pause.g
; called when a print from SD card is paused
;
; generated by RepRapFirmware Configuration Tool on Wed Feb 07 2018 13:21:45 GMT-0600 (CST)
G10		; retract filament
G91		; relative positioning
G1 Z5		; lift Z by 5mm
G90		; absolute positioning
G1 X0 Y0 F10000	; go to X=0 Y=0

Only real difference here is that I'm using firmware retraction so I use G10 to retract. Otherwise it's the same as yours for all intents and purposes.

; resume.g
; called before a print from SD card is resumed
;
; generated by RepRapFirmware Configuration Tool on Wed Feb 07 2018 13:21:45 GMT-0600 (CST)
G1 R1 Z5 F10000 ; go to 5mm above position of the last print move
G1 R1          ; go back to the last print move
G11		; unretract

And here the difference seems to be the X0 Y0, which I don't have. So maybe give that a try. I can't remember if I changed that or not. There was a bug on resume in one of the last few firmwares that may have caused me to change it. I can't recall.

The G1 R1 documentation doesn't really go into much detail on how it should be used either.

norbs12

@phaedrux I'll give you version a try later today.

Curious are you on a maestro or a duet? I'm only asking because it worked on a duet.

Phaedrux

Duet wifi. I'm not aware of any difference for the maestro in this regard though.

norbs12

@phaedrux said in Maestro pause/resume ends up about 0.5mm above original Z:

So I got it fixed, but unfortunately I kind of a did the shotgun approach and I could not tell you which one thing fixed it.

Swapped to an SD card that came with the duet, copied all configs (from SD card that wasn't working), added a "G29 S1 Pheightmap.csv" into resume.g (again not sure if necessary), downgraded to latest stable firmware (2.02?).

Works like normal now, I'm curious what was causing it but not curious enough to do all those steps 1 by 1 and try a print each time. I do have a old card though, so I could probably replicate the issue if I wanted to.

Anyways I appreciate your time.

Phaedrux

It may be worth updating to the 2.03 beta just to test with everything else as is.

norbs12

@phaedrux
OK, I eventually will. I just need to get some prints done, will tinker more after.