Firmware 2.03beta2 available

Martin1454

@chas2706 said in Firmware 2.03beta2 available:

@martin1454
In your config.g remove M667 S1 and replace it with M669 K1. That will sort it!

Still mirrored

whosrdaddy

@chas2706 : from which firmware did you upgrade may I ask?
If coming from an older firmware (pre 1.19), the Y motors will need reverse direction. (you can do that in firmware)

Martin1454

@whosrdaddy said in Firmware 2.03beta2 available:

@chas2706 : from which firmware did you upgrade may I ask?
If coming from an older firmware (pre 1.19), the Y motors will need reverse direction. (you can do that in firmware)

If it is me you are reffering to - 2.0 or what it was called late december

EDIT: found out how the new 669 worked - had 2 put X-1.0:-1.0

whosrdaddy

@martin1454 : Yeah wrong person
Glad you worked it out.
Weird, I also have a CoreXY but I did not have to change anything...

dc42

From the upgrade notes for 2.03beta1:

If you have a CoreXY or other Core architecture printer, and you were using any axis factor parameters in your M667 command in config.g, those parameters are no longer supported. You will need to use M669 matrix parameters instead.

@Martin1454 was using a X-1 parameter in his M667 command. Swapping the X and Y motors over and adjusting the directions in M569 would have worked too.

adri84dj

Hi. So far, I've been with firmware 2.02 RC3 in my Kossel.

When I calibrated the bed with G32 with calibration factor 8, after two passes, I had some 0.05mm measurements, the difference between each measured point, and the first layer was very good

I have updated to the latest version, 2.03 beta 2, and when doing the G32 calibration several times, I get disparate measurements between the measured points of up to 0.2mm. Now the first layers are uneven in different parts of the bed.

Have I missed something? Has anything changed in this latest firmware?

Thanks and best regards

dc42

There has been no intentional change in this area. There might have been an unintentional change because the code that handles endstop corrections has changed. Can you revert to 2.02 and check whether the new firmware really is to blame?

adri84dj

@dc42

Okay. I go back to 2.02 and try it later.

Thank you

adri84dj

@dc42 said in Firmware 2.03beta2 available:

There has been no intentional change in this area. There might have been an unintentional change because the code that handles endstop corrections has changed. Can you revert to 2.02 and check whether the new firmware really is to blame?

Hello,

With the 2.02 final it works correctly again, as in 2.02 RC3.

At least in my case there is something weird about 2.03 Beta 2.

dc42

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.

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!