Problem with babystepping V3.01 RC10 and DWC 2.1.5.

3DOeste

I have a problem sin V3 release, it did not happen with 2.05. When I start a print, if I adjust first layer height with baby stepping, lets say 0.1mm closing the gap between bed and extruder, and the print finish or I stop it and start another, the new job takes into account the previously set distance and re apply again, many times making the extruder touch the bed and I need to increase the gap the same amount I decrease it the first time. Im on V3.01 RC10 and DWC 2.1.5. Duet 2 ethernet.

Phaedrux

So you're saying that if you set the baby stepping once during a print it is being applied again on the second print? (EDIT: by this I mean, is it adding it on top of the existing baby stepping?)

If you send M290 with no parameters what does it report the baby stepping as?

RC11 was released today, can you test that as well?

https://github.com/dc42/RepRapFirmware/releases/tag/3.01-RC11

3DOeste

@Phaedrux said in Problem with babystepping V3.01 RC10 and DWC 2.1.5.:

So you're saying that if you set the baby stepping once during a print it is being applied again on the second print?

Thats right. It started since the V3 release. I forgot to mention that every consecutive print re home all the axis. I have a bltouch 2.0 and I get excellent repeatability when homing so I don't think thats the problem.
I'll try RC11 next week and test if there are any changes.

gtj0

It doesn't clear unless you explicitly clear it. It's been that way for a while. It survives homing and any anything else you throw at it except M290 or reset. I mentioned this a few months ago but everyone thought I was crazy.

M290
Baby stepping offsets (mm): X:0.000 Y:0.000 Z:0.000
M114
X:-235.000 Y:-235.000 Z:0.000 E:0.000 E0:0.0 Count -150400 0 0 Machine -235.000 -235.000 0.000 Bed comp 0.000

M290 S1
M290
Baby stepping offsets (mm): X:0.000 Y:0.000 Z:1.000
M114
X:-235.000 Y:-235.000 Z:0.000 E:0.000 E0:0.0 Count -150400 0 1600 Machine -235.000 -235.000 0.000 Bed comp 0.000
G28 Z
M290
Baby stepping offsets (mm): X:0.000 Y:0.000 Z:1.000
M114
X:-235.000 Y:-235.000 Z:0.000 E:0.000 E0:0.0 Count -150400 0 800 Machine -235.000 -235.000 1.000 Bed comp 0.000

Phaedrux

Yes it sticks as it is, but are you saying it's being applied again on top of the first time?

@Phaedrux said in Problem with babystepping V3.01 RC10 and DWC 2.1.5.:

If you send M290 with no parameters what does it report the baby stepping as?

Please answer that.

Phaedrux

@gtj0 said in Problem with babystepping V3.01 RC10 and DWC 2.1.5.:

mentioned this a few months ago but everyone thought I was crazy.

Some people want to make it persist over REBOOTS.

gtj0

@Phaedrux said in Problem with babystepping V3.01 RC10 and DWC 2.1.5.:

Yes it sticks as it is, but are you saying it's being applied again on top of the first time?

@Phaedrux said in Problem with babystepping V3.01 RC10 and DWC 2.1.5.:

If you send M290 with no parameters what does it report the baby stepping as?

Please answer that.

See the last M290 above done after G28 Z.

I'm going to do some actual measurements now.

gtj0

OK, it's not accumulating, at least for me. It's just persisting.

Phaedrux

Personally I have a reset for speed factor, extrusion factor, and baby stepping in my end gcode.

gtj0

@Phaedrux Yeah I remember you mentioning that recently. Maybe the OP just needs to add those as well but if he didn't need them for 2.05 maybe there is a different behavior.