Discourse works well. I think it's important to add that theming is important regardless of the solution selected. Beyond just good looks, it can really help with ease of use as well.

Really glad to hear this is being considered.

This might be a bit off the wall, but since the majority of the posts here seem to be questions / users seeking help, would a stack exchange-esque option make sense? Then the OP could select an answer that solved their issue, people could up vote helpful comments, and have sub-threads built in to responses instead of intertwining with the rest of the conversation. I think this really makes the information and effort put into a thread more future proof and easy to mine for future users/searchers.

@dc42:

Is it a Duet WiFi or Duet Ethernet?

Sorry David, I didn't see you had replied. It is a Duet Wifi. I'm running 1.20 (2017-12-23).

I can also confirm it is not the new ironing setting that's causing any issues. This has happened on all three of my prints since I posted, two of which don't have ironing on. The machine is basically frozen while this occurs, I have to do an emergency stop (the normal M0 stop does nothing) and wait for it to boot back up before moving my print head away from my print.

It's definitely hitting the end code - I see the extruder retract but after that, it hangs. The next line in my end code is

G1 Z+5 E-5 X-20 Y-20 F9000 ;move Z up a bit and retract filament even more

Any ideas?

Thanks again.

Hi dc42, I expect this will happen again, anything I can do to capture more information on the problem? I should have run an m122, now that I think about it.

So, this is odd and scary. I've just completed my 6th or 7th print with the Duet, using the same slicer (Cura) and same start/end gcode.

I just wrapped up a 9h print and I was monitoring the printer because it was getting close to done. I watched the print head move to a corner of the print and just stop. It sat there for a few seconds while I fumbled with the bed and pulled it out of the way. It had started melting a hole into the print, but thankfully it doesn't impact it much.

I took a screen shot of the web interface next.

I highlighted a few things.

• The Duet was reporting 95.6% completion.

• Both heaters had beed turned off.

• The total layers was reporting 21. It was actually 154, with a last, 155th layer for ironing, which had been completed. (Cura counts ironing as a layer apparently)

• The filament usage was WAY off. Or it was accurate and the expected usage was way off.

About 4 minutes after I took the screen shot, the printer homed X and Y, and raised the Z by 5mm as the end G-Code tells it to.

This happened once before, though I didn't see it happened and was scratching my head about it. I printed a small calibration cube and came back to see it stuck to the hot end, off the print bed by about 5mm with the X and Y homed.

My gut is telling me ironing has something to do with this, but all of my prints have been ironed on the top layer for a week or so now.

Here's my end GCode from Cura, I think it's clear this was hit because the heaters were off. Not sure where it went wrong.

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

Not sure I can help with the problem, but for me at least, I can't see your picture.

Hmm. I think I've somehow worked through this. It looks like my steps/mm micro-stepping commands were off by quite a bit. I've adjusted those and it looks like things are working out now, although I'm sure it's not dialed in just yet.

I think removing the errant G92 commands helped as well. I'm not certain why the configurator put them in.

Fortunately I've discovered several more issues after trying to print again, so at least I won't be bored tonight!

Thanks for the help dc42.

Ok, then it sounds like I don't need that command since the homing switch is hit below the bed surface. This happens because the glass surface doesn't extend to the XYZ home corner, plus the nozzle compresses the bed spring a little when homing Z. Not Ideal, but I can't print my Z-Limit adjuster until the printer prints again.

That being the case, if the switch is hit ~5mm below the bed surface, shouldn't the ~5mm mesh grid compensation account for that?

It looks like I have a G92 Z2.5. If my understanding is correct, this would tell the printer that the current Z position is actually 2.5mm, not 0mm. When adjusting for the mesh it would only lift up by about 2.5mm instead of 5mm, correct? That would seem like it could be part of my issue if that's the case.

I commented the G92out of the homez.g and homeall.g, and re-ran the mesh compensation just to be safe. It's still digging into the bed however.

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool on Sun Feb 18 2018 21:28:00 GMT-1000 (HST)
G91               ; relative positioning
;G1 Z5 F6000       ; lift Z relative to current position
G1 S1 Z-185 F1800 ; move Z down until the switch triggers
G92 Z2.5          ; set Z position to trigger height

; Uncomment the following lines to lift Z after probing
G91              ; relative positioning
G1 Z5 F100       ; lift Z relative to current position
G90              ; absolute positioning

Awesome! Did you find specs for the 7i online or did you measure it up yourself?

Hi dc42,

Yeah, I agree, they need to be smaller than that. However I'm not able to adjust the Z endstop any higher without being higher than the bed can go, due to some damage to the printer. The first thing I plan to print is an adjustable Z-limit: https://www.thingiverse.com/thing:1008176. But for now, this is what I'm stuck with. Can the mesh compensation not handle a 5mm offset? the maximum difference between heights is only .9mm, admittedly still too much, but seems like it's well within operating capacity.

All three axes are homed. My Z is set to 120, and my acceleration is set to 100. These are actually a bit lower than they were on the Melzi board previously I believe.

Again, I was able to print one test damn near perfectly. But the mesh just isn't loading any more, or is loading inconsistently and I'm getting a string of bad luck.