v2.0 consistently increasing probe heights

[dc42]

@oarjjj gave you verified that all the boards are now running 3.6.0-beta.1 ?

[oarjjj]

@dc42 Yes.

FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.6.0-beta.1 ELECTRONICS: Duet 3 MB6HC v1.0 or earlier FIRMWARE_DATE: 2024-09-24 10:07:51
Duet EXP1HCL rev 1.0a or earlier firmware version 3.6.0-beta.1 (2024-09-24 08:50:54)
Duet EXP1HCL rev 1.0a or earlier firmware version 3.6.0-beta.1 (2024-09-24 08:50:54)
Duet EXP1HCL rev 1.0a or earlier firmware version 3.6.0-beta.1 (2024-09-24 08:50:54)
Duet EXP1HCL rev 1.0a or earlier firmware version 3.6.0-beta.1 (2024-09-24 08:50:54)

[oarjjj]

I wonder if there's something wrong on the CAN bus causing unexpected latency? I didn't use a premade cable.

[oarjjj]

@dc42 said in v2.0 consistently increasing probe heights:

@oarjjj gave you verified that all the boards are now running 3.6.0-beta.1 ?

Any other ideas?

[oarjjj]

@dc42 I updated to the beta 2 firmware. The increasing values appear to be more consistent now. Almost exactly .010 over each probe. I've tried connecting the smart effector to the IO pins on the expansion boards. Also re-did the configuration from scratch using the RRF config tool.

[oarjjj]

@dc42 Interesting when running the board in standalone mode the offset decreases from 0.010 to 0.005. Appears to be a hardware problem. Can we do an RMA?

G32 bed probe heights: 0.096 0.101 0.106 0.111 0.121 0.121 0.131 0.136 0.141 0.146 0.151 0.156 0.161 0.166 0.171 0.176 0.181 0.186 0.191 0.196, mean 0.147, deviation from mean 0.030
G32 bed probe heights: 0.201 0.206 0.211 0.216 0.221 0.226 0.236 0.241 0.241 0.246 0.251 0.261 0.261 0.271 0.271 0.281 0.286 0.291 0.296 0.301, mean 0.250, deviation from mean 0.030
G32 bed probe heights: 0.306 0.316 0.316 0.326 0.331 0.331 0.341 0.346 0.351 0.356 0.361 0.366 0.371 0.376 0.376 0.381 0.391 0.396 0.401 0.406, mean 0.357, deviation from mean 0.029
G32 bed probe heights: 0.406 0.416 0.421 0.426 0.431 0.436 0.441 0.446 0.451 0.456 0.461 0.466 0.471 0.476 0.481 0.486 0.491 0.496 0.501 0.506, mean 0.458, deviation from mean 0.029
G32 bed probe heights: 0.511 0.516 0.521 0.526 0.531 0.536 0.541 0.546 0.551 0.556 0.561 0.566 0.571 0.576 0.581 0.586 0.591 0.596 0.601 0.606, mean 0.558, deviation from mean 0.029
G32 bed probe heights: 0.616 0.616 0.621 0.631 0.631 0.641 0.646 0.646 0.656 0.661 0.666 0.671 0.676 0.681 0.686 0.691 0.696 0.701 0.706 0.711, mean 0.662, deviation from mean 0.030
G32 bed probe heights: 0.711 0.721 0.726 0.731 0.736 0.741 0.746 0.751 0.756 0.761 0.771 0.771 0.781 0.786 0.791 0.796 0.801 0.806 0.811 0.816, mean 0.765, deviation from mean 0.031
G32 bed probe heights: 0.826 0.831 0.836 0.841 0.846 0.846 0.856 0.861 0.866 0.871 0.876 0.881 0.886 0.891 0.896 0.901 0.906 0.911 0.911 0.921, mean 0.873, deviation from mean 0.029
G32 bed probe heights: 0.931 0.936 0.941 0.946 0.951 0.956 0.961 0.966 0.971 0.976 0.981 0.986 0.991 0.996 1.001 1.006 1.011 1.016 1.016 1.026, mean 0.978, deviation from mean 0.028

[oarjjj]

Here is my configtool.json

[oarjjj]

I also tried turning off segmentation with M669 and the hotend hit the bed so hard it wrecked my E3D Revo 6.

[shaunppl]

This post is deleted!

[shaunppl]

@oarjjj said in v2.0 consistently increasing probe heights:

I am starting to think it may be an issue with the E3d Lite6, possibly its spring is compressing? I'm not sure.

There should be no compression available on the E3D lite 6 with a Revo nozzle as the compression spring is there to hold the nozzle heat-break assembly tight against the thread of the body after hand tightening it, so when in constant use it does not come undone and also to allow the heater element a degree of heat expansion.
The only case i have ever had with a loose nozzle was with a customer who had not tightened it it up fully and they kept getting a very inconsistent filament laydown and jagged edges as it would oscillate as it was moving. I am running 3 Delta printers all Anycubic Predators converted to linear rails and all using version 3.5 on Mini + 5 boards and all the motors directly from the motherboard with the Hemera sx extruders without any expansions as I have never needed them nor have i ever any issues to warrant using expansion board as I get extremely good prints.