3.4.0 beta 4 issue?
-
@jens55 I had a similar occurrence on my currently-decomissioned V-Core Pro but ignored it.
-
@oliof, hmmm , well, everything does work so I suppose I could ignore it ....
I tried to remove sections of the homez.g to locate the error but was unable to do so. I am concerned that something else might jump out and bite me in the behind -
It looks like this command causes the error message:
M290 R0 S0
I have zero clue why resetting baby stepping would cause an 'insufficient axis homed' error message.
Could someone explain to me why this is happening? -
@jens55 is that linked to the change about not allowing babystepping when an axis isn't homed?
-
@jay_s_uk, that could very well be .... but then how do you home z? If there is any baby step offset, doesn't that screw up the homed z=0 position ?
-
I suppose I could home, reset baby steps and then home again but that seems screwy
-
@jens55 you know, I just recently read about M290 and confess we've never used it to reset babysteps - and never had an issue. I'm having a hard time understanding the need for it. It was our perception that rehoming reset everything..
-
@jay_s_uk , just tested your theory and sure enough, if I move the M290 past the first z probing, there is no issue.
-
@oozebot said in 3.4.0 beta 4 issue?:
@jens55 you know, I just recently read about M290 and confess we've never used it to reset babysteps - and never had an issue. I'm having a hard time understanding the need for it. It was our perception that rehoming reset everything..
I am 100% with you on that. I used pre-made routines for my Jubilee which is why the command is there and assumed I had always done it incorrectly but didn't really understand why it was required.
Maybe somebody could comment? @dc42
-
@jens55
As you know I have the same issues.
The documents state...In RepRapFirmware 1.19 and earlier, the babystepping offset is reset to zero when the printer is homed or the bed is probed. In RepRapFirmware 1.21 and later, homing and bed probing don't reset babystepping, but you can reset it explicitly using M290 R0 S0.
Which is why I implicitly cleared baby steps when homing.
EDIT
The change log says M290 is no longer allowed on unhomed axes.
As soon as you call homez, it becomes unhomed.
My guess is that the new code to disallow M290 doesn't check if it's just clearing rather than setting baby steps. -
@owend said in 3.4.0 beta 4 issue?:
My guess is that the new code to disallow M290 doesn't check if it's just clearing rather than setting baby steps.
My thought as well, an oversight I am sure (I hope)
-
@jens55 in the next beta RRF will allow M290 with R0 parameter even if axes have not been homed; however for unhomed axes, no movement will be made.
-
@dc42, Thanks !
-