Firmware 2.03beta2 available

AlexLin

@dc42 does only apply to G32 or also to G29 mesh calibration?

dc42

@alexlin said in Firmware 2.03beta2 available:

@dc42 does only apply to G32 or also to G29 mesh calibration?

Only to delta auto calibration.

adri84dj

@dc42 said in Firmware 2.03beta2 available:

I've found a bug which might explain the problem, if you don't home the printer between auto calibration and printing. So please try 2.03beta3 when i release it. Meanwhile, homing between auto calibration and printing should work around the bug, assuming that your homing switches have reproducible trigger heights.

In agreement. When beta 3 is available, I try it. Thank you.

dc42

Beta 3 is available now.

adri84dj

@dc42 said in Firmware 2.03beta2 available:

Beta 3 is available now.

In agreement. I'll try it this weekend.
Thank you

adri84dj

@dc42 said in Firmware 2.03beta2 available:

Beta 3 is available now.

Hello,

It is already tested and in beta 3 it works correctly again.

Thanks and best regards

brunofporto

When running G29 now the printer is using the nozzle reference and my z probe is out of the bed area. But when showing the map it thinks it was the probe at the nozzle position.

dc42

@brunofporto said in Firmware 2.03beta2 available:

When running G29 now the printer is using the nozzle reference and my z probe is out of the bed area. But when showing the map it thinks it was the probe at the nozzle position.

The only change should be that if you run G29 within a system macro file (for example, bed.g) then tool offsets will be applied., whereas in firmware 2.02 they are not. But Z probe offsets are always applied by G29. Are you using tool offsets?

brunofporto

@dc42 Not using any tool offsets. The only offset is the z-probe defined at the z-probe configuration line.

Pretty sure it is putting the nozzle exactly where it should be the probe when I send a G29 - needed to change some parameters to make sure the probe is over the bed but the height map shows as the nozzle position is where the probe took the measurement.

brunofporto

@dc42 ps.: just realized that I post at the wrong thread! I am using the beta3!