3.4.0 beta 4 issue?
-
Never noticed this before so it might be related to something completely different than the firmware upgrade but when I run a 'Home all', I now get a G28 Error:insufficient axes homed error but the homing does complete with all 4 axis showing homed when it finishes.
Running the homing on each individual axis, I get the error when Z is homed.
This is my homez.g; Home Z Axis
if !move.axes[3].homed
M291 R"Cannot Home Z" P"U axis must be homed before Z to prevent damage to tool. Press OK to home U or Cancel to abort" S3
M98 P"homeu.g"; RRF3 does not permit Z homing without x&y being homed first. Popup window for convenience.
if !move.axes[0].homed || !move.axes[1].homed
M291 R"Cannot Home Z" P"X&Y Axes must be homed before Z for probing. Press OK to home X&Y or Cancel to abort" S3
M98 P"homey.g"
M98 P"homex.g"if state.currentTool != -1
M84 U
M291 R"Cannot Home Z" P"Tool must be deselected before homing. U has been unlocked, please manually dock tool and press OK to continue or Cancel to abort" S3
M98 P"homeu.g"M290 R0 S0 ; Reset baby stepping
M561 ; Disable any Mesh Bed CompensationG91 ; Relative mode
G1 H2 Z5 F5000 ; Lower the bed
G90 ; back to absolute positioningG90 G1 X150 Y130 F10000 ; Move to the center of the bed -20mm to not probe on
; top of the mandal rose bed magnet skrew headM558 F500 ; Set the probing speed
G30 ; Probe
M558 F50 ; Set a slower probing speed
G30 ; Prob
G32 ; Run 3-point bed calibration defined in bed.g
G29 S1 ; Enable Mesh Bed CompensationHere is my bed.g file that is called
M290 R0 S0 ; Reset baby stepping
M561 ; Disable any Mesh Bed Compensation
G30 P0 X152.5 Y5 Z-99999 ; probe near back leadscrew
G30 P1 X295 Y295 Z-99999 ; probe near front left leadscrew
G30 P2 X5 Y295 Z-99999 S3 ; probe near front right leadscrew and calibrate 3 motors
G29 S1 ; Enable Mesh Bed CompensationBTW, this is for a Jubilee printer
-
Anybody ?
-
@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 !
-