@dc42 Thank you! This is what I needed. I come from the Ultibot days when they gave us a Simplify3D conifugration than ran a G28 every print. I'll give this all a go, I was having all sorts of issue but after microstepping back 0.9mm each print has been perfect so I'll let you know soon.

Did a lot of work upgrading from 1.16, replaced duet wifi 2, re-wrired (and checked my crimps) and checked everything w my multi-meter, installed new PETG tube inside e3d, installed new themistor, replaced my PEI bed, so I wanted to be sure everything was good now that I know more this go around.

@achrn Ahh yes my bad G29 and G32, sorry was at work but I think my intent was there. The fact that a calibration was running after should have been a hint.

Messing with G92 Z0 at all, screws with subsequent G29 and G32 calls.

@achrn I do have a small trigger height in my G31 Z-0.6. On my delta (and i assume others [sorry meant G32 but still regardless G29 still does hotend movemet] - delta calibration does at a homeall.g then uses the an algorithm to to compensate for the the calibration of the bed. The 3 arms come down and touch the bed at several points activating the FSR sensors, allowing it to calibrate. G92 however also moves the printer head, it does a bed calibration mesh grid in the call defined by 357. Are you talking about a cartesian printer? How else is your hot end not moving on a delta machine?

G31 X0 Y0 Z-.6 P500 		
M558 P5 C"!e0stop" H5 I1 F75    ; Set zprobe, p4 is now p5 w 3.x

I think you're process works for me too, i just have to micro step up .9-1.0 mm whether or not I just boot it up and start or calibrate then print. Appreciate it btw!

@dc42 My slicer is set up to home then run a G92 calibration before printing so that may be it, although if I understand correctly the calibration should reset the home, but not sure exactly how it relates to the G30 call i have to make or the height map gives warnings. I'll give it a shot and appreciate the help!

@achrn what I'm saying is if I follow that documentation, paper just barely catching g92 z0 then the subsequent calibrations are away too low (G92 = detached printer head from hitting the bed). Don't setup G92 Z0 and it calibrates great. I'll see if checking my probe offset would help but its an FSR setup using the JohnSL board so I don't see that applying here.

If I set G92 z0 i can G30 S-1 until the cows come home, if I do anything the requires a homing then the z value is incorrect. For instance it'd be nice to configure my printer, run the G30, G92 and save with M500 so it's good for next time. But the delta requires you to home before moving the print head, so my Z would be messed up.

Just not to note, this was all fine in 1.6, I just ran through all the updates at once and now we're on 3.2 so not sure where/if when that changed.

Turn printer on >> Home all >> G30 (allow z probe to set z=0) >> G32 >> G92 (M557 is defined in config at 100mm radius every 10 mm) >> M500 (save all the configuration)

Now I have to raise the print via micro-stepping from 0.7-1.0 mm and the prints work fine.

My z probe is configured using JohnSL board and is working fine;

M558 P5 C"!e0stop" H5 I1 F75    ; Set zprobe, p4 is now p5 w 3.x

Changing the G31 Z value is useless, I currently have it set to -0.6 but I can make it 2.0 and it doesn't effect any calibration or print issues the way I am doing configuration. Other than this last issue have a D300VS running great on 3.2 firmware. I suppose this works, it just bothers me the homing height is never right, am I doing something wrong or is the firmware just wonky with delta's and 3.x?

Values saved from M500

M665 L360.310:360.310:360.310 R210.773 H438.588 B140.0 X-0.415 Y-0.448 Z0.000
M666 X2.633 Y-2.306 Z-0.326 A0.00 B0.00

@alankilian manual process to to tun a command that allows it below z, set to it to right where it holds a paper and set G92 Z0, then you can get offset with G30 S-1. Like I said it never works for me, just leave it at zero. I believe but not positive after homing if you run G30 it'll set the homed height, and then when you create the mesh map it doesn't complain. I can do that, just the manual process doesn't work for me.

I keep printing a PITA object so if it fails again here I'll move to some benchy type stuff.

It feels like a dome issue of some kind, as some of the first layer print better (thicker but all too low and thin) than others, but the rods and everything are matched from before. No hardware swaps. The flat bed and height map just confuse me, as well as it being fine before. Post those other details soon!

@alankilian Fixed that for ya, but lemme see how this print goes and then print something normal like a calibration cube for you. The G30, G92, etc are so good its weird it's so low. I'll post soon, sorry and thank you!

@alankilian thanks for the help!!

D300VS.js

I have another print going, and i guess i tossed the other cubes i printed so i'll do that tonight and post back here. I'm sorry about the format, just download and change to xml or ffl, this forum won't accept those file typess. Thanks again!

Also advice welcome, starting to get frustrated. Should I scrap this delta and just go with an Ender3 or something. I'm equipped to handle most things, but this has me puzzled; steppers aren't slipping, they're 0.9 degree motors, the JohnSL FSR sensors are kind of a pain in butt at times, but seem accurate enough. I don't get it... suggestions PLEASE. I'd be willing to upgrade the extruder but that doesn't explain the loss in the print quality I experienced just by going through firmware steps. Delta's just a bad idea with not enough support, I don't know.