DuetWifi 1.01 Updated to 1.24 - No Z Axis after update

Phaedrux

Looks like you're all up to date.

This may help with getting the probe setup: https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe#Section_Static_test_of_the_Z_probe

nophead

Seems like a bug if missing or incorrect probe offsets can cause the X and Y axes to crash. Once they are homed shouldn't they be limited to their defined range regardless of what G-code is executed?

Phaedrux

Did adding the X and Y parameters to G31 fix it?

dc42

@nophead said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

Seems like a bug if missing or incorrect probe offsets can cause the X and Y axes to crash. Once they are homed shouldn't they be limited to their defined range regardless of what G-code is executed?

The probe offsets default to zero; so leaving them out won't cause a crash.

dc42

@dirtybirdnj said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

M558 is definiltey responding to the extra settings, but I still have to run M564 H0 to home the z-axis.

Do you mean you always need to run M564 H0 to home the Z axis; or only if you try to home the Z axis before X and Y have been homed?

When homing Z with a Z probe, the firmware won't let you do it if X and Y have not been homed first; otherwise it would probe at unknown XY coordinates.

Did you add the S2 parameter to the following command in homez.g as @Phaedrux said?

G1 Z1 F200 ; raise head 1mm to ensure it is above the Z probe trigger height

dirtybirdnj

@dc42

Do you mean you always need to run M564 H0 to home the Z axis; or only if you try to home the Z axis before X and Y have been homed?

Yes, this is exactly the case. Please see the screenshot above, I posted a log from the g-code console to document this.

Did you add the S2 parameter to the following command in homez.g as @Phaedrux said?

I did and the S2 allows for upward movement before the probe, but it still refuses to execute the G30 that does Z-probing unless I run M564 H0 first.

Phaedrux

Can you try deleting the deployprobe.g and retractprobe.g files?

dirtybirdnj

@phaedrux

Can you try deleting the deployprobe.g and retractprobe.g files?

THIS WORKED The "random movements" issue has been solved! I didn't delete the files I just commented out their contents, but I'll prob remove them soon for good measure.

Still need to run M564 H0 before z-axis is unlocked, but I feel way more confidant about doing some test prints now that the machine is homing correctly and behaving as expected again.

Phaedrux

@dirtybirdnj said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

Still need to run M564 H0 before z-axis is unlocked

Repost your homing files. There is a G1 move in there somewhere that needs S2.

Phaedrux

@dirtybirdnj said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

I just commented out their contents

What did they contain?

dirtybirdnj

@phaedrux said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

@dirtybirdnj said in DuetWifi 1.01 Updated to 1.24 - No Z Axis after update:

I just commented out their contents

What did they contain?

I copied the contents of the files over to a scratch pad before I commented them out, here they are. I don't recall setting these up so it seems like something that was on the SD card that the previous firmware didn't run / care about? Not sure... either way I am elated that I had two successful prints tonight!

// deployprobe.g
; Probe deployment routine for Mini Kossel
M564 S0					; don't apply limits
G1 X25 Y93 Z40 F10000	; put probe arm next to belt
G1 X-5 F500				; move probe arm across belt
G1 X12 F1000			; move probe back
G1 X0 Y0 F10000			; move to somewhere sensible
M564 S1					; apply limits again


//retractprobe.g
; Probe retraction routine for Mini Kossel
M564 S0					; don't apply limits
G1 Z40 F10000			; raise head
G1 X-59 Y66 Z35			; move over the post
G1 Z7 F500				; push probe down on post
G1 Z35 F10000			; raise head again
G1 X0 Y0				; move to somewhere sensible
M564 S1					; apply limits again

After taking a look at these I can clearly see it's setting M564 S1 at the end of each which is prob what was causing the "axes not homed" errors! I commented out the M654 H0 in my config.g and it homes the Z with no problem now. These files also account for the "random" x+y movements that were happening with the homing process as well... mysteries solved and case closed.

This thread can be marked solved! Thanks again to @dc42 @Phaedrux for your help!

Phaedrux

Glad it's all working now.