@norder Thank you for your reply. I apologize for my delayed response.

I did clean everything up, gave it a few drops of thin or very thin oil where needed and made sure everything moved freely and easily.

Thank you for the suggestion on the print bed. I looked at them when you posted and may just go that direction.

I like what you've done with your M558 probe code with adding multiple times to probe each spot, the tolerance and then probe recovery time. Here's what mine is currently set for. This is the one generated by the config wizard:

M558 P1 C"zprobe.in" H5 F120 T6000

I have not had a chance to add in some of the things you've identified yet - my wife is finally better from c19 so hopefully soon. I am wondering if those settings - slowing down, multi probe and time delay - will make a difference in the readings I am getting ( see post above ). Hopefully I can make this changes tomorrow and give it a test! Will post my results.

@ccs86 Interesting. Gotcha. Figured you were asking based on the 'padding' around the graphic of the map.

What browser are you using?

@ccs86 Please try either rolling your mouse wheel, left click and dragging or right click and dragging.

@norder Thank you for your reply. I apologize for my delayed response.

I did clean everything up, gave it a few drops of thin or very thin oil where needed and made sure everything moved freely and easily.

Thank you for the suggestion on the print bed. I looked at them when you posted and may just go that direction.

I like what you've done with your M558 probe code with adding multiple times to probe each spot, the tolerance and then probe recovery time. Here's what mine is currently set for. This is the one generated by the config wizard:

M558 P1 C"zprobe.in" H5 F120 T6000

I have not had a chance to add in some of the things you've identified yet - my wife is finally better from c19 so hopefully soon. I am wondering if those settings - slowing down, multi probe and time delay - will make a difference in the readings I am getting ( see post above ). Hopefully I can make this changes tomorrow and give it a test! Will post my results.

@phaedrux Sorry for the delayed reply. Looks like you are correct. Different measurements at different locations and they are not the same. Close but not identical.

Ok. So I ran through measuring nozzle heights and then IR trigger heights five times. In brief, I heated up my printer to 205 & 60C bed, ran G28 then G32 twice and then started measuring and recording.

Took center measurement first and then went out 100mm and measured. First the IR reading ( G30 S1 from about Z15 = "IR Trigger" height ) and then manually down to the same piece of paper every time ( "off bed" ). I was curious so I used excel to do the math from the IR Trigger point to the measured spot difference. Did the same for the off bed measurement. The last column, "difference from measured" is IR difference minus off bed difference. Not sure if helpful but I was looking for a trend indicator.

Side notes. IR trigger height has changed vs my original post - new nozzle and adjusted. On the first G32, the print head only moves out 90mm and begins to measure. Its configured for 115mm. Every G32 after that, until a reset/power off/etc, moves 115mm. I also know that the effector does NOT move in a flat plane until the G32 command is run. Its movement is high in the middle and about 10mm low at the outside edge of the print bed. I don't know if both these are normal or not.

@phaedrux I will take a look tonight. I print on glass and under that I have a piece of black construction paper (with bulls eye rings for alignment). One of the things I've tried is lights out with the enclosure closed up. When running a mesh leveling, I believe that I've have seen a difference with lights on vs off.

I did check the Z height (not IR sensor) last night and found a difference when I measured after homing and at temp and that, plus a G32 command. Difference wasn't much, maybe 1.2mm?? Didn't record that change/difference. I'm going to adjust my overall starting height a little more tonight...

Side note- I measured 115mm from bed center and that is where the effector lands in the bottom picture above. So in the first run, its landing short, maybe 20mm... will measure that also.

Thank you phaedrux and oliof for replying.

@oliof That's a good thought but I've checked everything and this only seems to occur the first G32 after a power on or recovery from a machine stop/reset. Once its been run, it makes that system 'adjustment' and throws the parameters off. Likewise, in the first image above, running G32 repeatedly gets very close, consistent results -after- that first run.

First time poster, Duet2 user since early 2017?? Pleased with the thoroughness of Duet products and the support it has! Thank you to all in advance (and sorry for the long post!)

Delta - Kossel XL with IR Probe running Duet2 wifi. Did not use the printer for a while and just got back into it. Updated all the firmware recently and basically re-wrote all the config files. Had a problem before with bed leveling and I'm trying to work that out (turns out my glass print bed is slightly curled).

In the process of nailing that down, I came across an error that appears when running G32. At first I didn't realize what I was seeing... first run (G28 first) and then I'd get a higher reading and if I hit G32 again, (G28) and then get a much smaller reading. Trying again, the reading changes slightly, see image.

Now the crazy part. The very first run, the print head is closer to the center or maybe I should say a little further from the print bed edge. Bed is 280mm with configuration specifying 250mm usable. These print head/bed images are with me calling out 115mm radius, no offset for the IR probe. This appears to be about the correct distance from center.

When I hit G32 again, the print head goes right to the edge. These pictures (above and below) are two of the 3 runs listed above. This is #2 or #3. The bed.g file homes (G28) every time before it runs the points specified. The X and Y coordinates displayed in the DWC are the same in both runs, X = 0.0 and Y = 115.0 but clearly they are positioned differently physically.

I have tried this with bed and hot end at temp, cold, from a power off, IR sensor offsets used, no offset, etc. This is repeatable. Clearly after the first run, the printer/Duet2 board makes an adjustment for or maybe "to" Z0 and the the G32 runs after that, uses this new measurement.

Now, the original config.g file had the rod length shorter than actual length by about 6mm (I have the correct, measured length in there now) and I did need to replace the IR sensor a few years ago because I broke the original. How? When manually setting Z height, my readings have always been too low and I was trying to get them where the published numbers say. Example = IR Probe triggered height "should be" somewhere between 1.0 to 2.0mm and mine consistently measures at 0.33 to 0.4mm. From the top Home switch down to a paper shim on the glass is very repeatable. (Edit: saying that, I will try this before and after a G32 to see if there's a difference).

So I am probably overlooking something in the configuration - Homed Height, arm length - something - and any help would be greatly appreciated! Thank you for reading this!