RESOLVED: Z probe issues after recalibration

[H0bb3z]

I'm a bit of a noobie at 3D printing, but I just completed a RMax v3.2 kit. All wiring looks like all is working, bed heating works, individual stepper control works as advertised. I ran the First Probe macro and it appeared to complete just fine, but as I was attempting to finish the calibration (the paper trick), I'm starting to see issues with the Z axis stepper.

As I recalibrate, I'm consistently getting "Warning: Z probe readings not consistent" and then "Error: Z probe was not triggered during probe move" - this results in an "Error: Compensation or calibration cancelled due to probing errors"

I've reset things to default and rerun the First Probe again. Now it appears to hit the Y axis upright when running a bed calibration. I've been looking at some of the common errors in the forum posts and I've checked belt tightness, connections, etc. but I'm still having the Z probe issue.

Edit: the X axis stepper appears to be impacted when the Y upright is hit -- the bearing housing gets stuck lower on the axis after impact, so that when the printing head centers again, it is offset a bit due to the X axis being lower than the other axes. At the end, all axes home correctly though.

Any insight where I might focus my efforts here?

RESOLUTION: I opened a support ticket to see if they could give me some options and they suggested the reset include deletion of two key files in the /sys folder: config-override.g and heightmap.csv. Do this after selecting "Load Factory Defaults" on the General tab of the Duet Wifi Settings. (NOTE: you can delete the files in the System Editor tab by selecting them, then right-clicking and choosing delete).

After I did this, then reran the First Probe macro, it corrected the issue. Also, I didn't know that if you run any probes after bed mapping, it effectively cancels out the bed mapping.

[rootboy]

Good to hear! I noticed that if I didn't home my printer between calibration attempts, it would do the same thing. Something to keep in mind.

[jadedsecurity]

Having the same issue.. Checked belts, wiring etc.. It keeps hitting Y axis no matter what I do.

[geneb]

Have you contacted support?

g.

[Jmorovich]

I am having the same issue. Had to replace duet board when it failed. Afterwards, the printer prints large and then trying to calibrate it has made it do all sorts of goofy things, including ramming against the Y and X pillars. Also the center seems offset.

[dc42]

I am having the same issue. Had to replace duet board when it failed. Afterwards, the printer prints large and then trying to calibrate it has made it do all sorts of goofy things, including ramming against the Y and X pillars. Also the center seems offset.

That's almost certainly due to incorrect files on the SD card. Maybe your new Duet had the factory default files on it instead of the ones customised for your R3.2 or Artemis.

[Jmorovich]

I am having the same issue. Had to replace duet board when it failed. Afterwards, the printer prints large and then trying to calibrate it has made it do all sorts of goofy things, including ramming against the Y and X pillars. Also the center seems offset.

That's almost certainly due to incorrect files on the SD card. Maybe your new Duet had the factory default files on it instead of the ones customised for your R3.2 or Artemis.

Did the firmware upgrade with the files downloaded from seemecnc

[metzb1]

I'm having similar issues with my V3 upgraded to V3.2. My first calibration went fine but now, several days later, I get bed crashes and failed calibrations. It seems to have gotten worse over time, and after a hot end disassembly to fix a jamming problem. The blue light indicating a probe trigger is no longer lighting up at all and all bed touches crash. I've been through firmware reloads, messing around with Z height and all kinds of other trial/error to no avail. I finally checked to be sure and I do indeed have 3.3V for the probe at the whip connector where it connects to the hot end. I contacted support this afternoon.

[bryan]

I'm having similar issues with my V3 upgraded to V3.2. My first calibration went fine but now, several days later, I get bed crashes and failed calibrations. It seems to have gotten worse over time, and after a hot end disassembly to fix a jamming problem. The blue light indicating a probe trigger is no longer lighting up at all and all bed touches crash. I've been through firmware reloads, messing around with Z height and all kinds of other trial/error to no avail. I finally checked to be sure and I do indeed have 3.3V for the probe at the whip connector where it connects to the hot end. I contacted support this afternoon.

metzb1, did you get this issue resolved? My blue probe trigger LED recently stopped lighting up.

[geneb]

You should probably contact support regarding that issue.

g.

[bryan]

I sent them an email, thanks.

[bryan]

I found the problem with mine: in the 10-pin Molex connector on the hotend PCB, the black 26 AWG wire broke where it goes into the crimped connector, and the orange one was hanging on by one strand. The kit assembly instructions show a zip tie strain relief holding the harness loop to the PCB between the connectors; my RTP machine was missing that zip tie.