Maybe slicer related? - g28 and g29 work from console, not from print.



  • So I'm about 90% certain that this is a slicing problem.

    If I'm in the web interface and send a g28, everything is perfect. Goes right to the front left corner drops until Z triggers. If I follow that up with a g29, it proceeds to probe the entire bed, no issues there.

    Now, if I pull up simplify3d and slice a model (In this case a 20x20mm cube, it homes X and Y and starts dropping the Z without moving first to the tool offset of x45,y15 so it attempts to drop into empty space.

    So I attempted to see if the g29 would happen after that point by artificially triggering the Z probe (Holding a metal ruler under it flat against the bed but sticking out enough to trigger the probe) the probe stops at that level, rolls over to the first probe point, then throws a "Error: Z probe was not triggered during probing move" and attempts to just shoot over and start printing willy nilly.

    This has to be a slicer issue right? I mean sending the codes manually in sequence acts exactly like it's supposed to.

    This happens both in Slic3r and Simplify3d.



  • slic3r has start g codes, gotta make sure G29 is in there after G28. In slic3r, it's under printer, custom g code.

    Not all printers have auto leveling so by default, it doesn't include it in start g code.

    You can also enter G29 S1 to make it load your saved height map without probing again, this would come after the G28 as well



  • @3dprinting:

    slic3r has start g codes, gotta make sure G29 is in there after G28. In slic3r, it's under printer, custom g code.

    Not all printers have auto leveling so by default, it doesn't include it in start g code.

    You can also enter G29 S1 to make it load your saved height map without probing again, this would come after the G28 as well

    Yeah in both Slic3r and S3d I have this as the start code -

    G28; Home all axes
    G29; Start ABL
    G92 Z0; ABL offset in mm (This isn't set yet)

    But when a print starts the g28 homes x and y and then goes straight down without the tool offset. It's completely weird.



  • can you program the z offset in config.g? That's what I do. I've never used the g92 zo. or is that because you have multiple tools? that also wouldn't make sense, because if they were at different z heights, one would crash while using the other.



  • @3dprinting:

    can you program the z offset in config.g? That's what I do. I've never used the g92 zo. or is that because you have multiple tools? that also wouldn't make sense, because if they were at different z heights, one would crash while using the other.

    Well I was using that for first layer adjustment. Just fast. But that happens after the g28, which is the command that is failing to play out correctly when attempting to print, and starting the snowball so to speak.


  • administrators

    You should not be sending G92 Z0 after G29.


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.