DuetWifi 1.01 Updated to 1.24 - No Z Axis after update

[Phaedrux]

M558 will need F for feed rate during probe moves. H for dive height to probe from, T for travel speed between probe points. P for the probe type. X Y and Z are deprecated and can be removed. The g31 seems ok. Except the trigger height for z would indicate that the nozzle is touching the bed when it triggers.

Is the probe attached to the print head or fixed to the frame?

[dirtybirdnj]

@phaedrux

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

Additionally when it does run G30 it does one probe and then rises and dives again moving in x+y+z. In doing so it pushes up past the end-stops making bad noises even though it's already homed the x and y axes.

It seems like it's doing something after the probing, but none of the actions defined in any of the home_.g match what it's doing. What exactly happens when G30 runs and is it dictated by any of these files? Running G29 also causes the machine to push beyond its axes after x and y homing as well.

Here's the latest version of my config:

; Communication and general
M111 S1                            	; Debug off
M550 OldYeller				; Machine name and Netbios name (can be anything you like)
M551 Preprap                        	; Machine password (used for FTP)
;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED 	; MAC Address
;*** Wifi Networking
M552 S1					; Enable WiFi. Disabled for setup and testing. Enable once set up on your network.
 
M555 P2                           	; Set output to look like Marlin
M575 P1 B57600 S1			; Comms parameters for PanelDue
 
G21                                 	; Work in millimetres
G90                                	; Send absolute coordinates...
M83                                 	; ...but relative extruder moves
 
; Axis and motor configuration
M569 P0 S0                          ; Drive 0 (x motor) goes reverse
M569 P1 S0                          ; Drive 1 (y motor) goes reverse
M569 P2 S0                          ; Drive 2 (z motor) goes reverse
M569 P3 S0                          ; Drive 3 (ext motor) goes reverse
;M569 P4 S1                         ; Drive 4 goes forwards
 
M350 X16 Y16 Z16 E16 I1             ; set 16x microstepping with interpolation
M574 X1 Y1 Z0 S1		    ; set homing switch configuration (x and y switches, at low end, active high)
M906 X800 Y800 Z800 E800            ; Set motor currents (mA)
M201 X1000 Y1000 Z1000 E100         ; Accelerations (mm/s^2)
M203 X3000 Y3000 Z3000 E600         ; Maximum speeds (mm/min)
M566 X1000 Y1000 Z1000 E50          ; Maximum jerk speeds mm/minute
M208 X200 Y200 Z240                 ; set axis max and high homing switch positions (adjust to suit your machine)
M208 X-0 Y0 Z0 S1                   ; set axis min and low homing switch positions (adjust to make X=0 and Y=0 the edges of the bed)
M92 X80 Y80 Z400 E95                ; set axis steps/mm
G21                                 ; Work in millimetres
G90                                 ; Send absolute coordinates...
M83                                 ; ...but relative extruder moves
 
; Thermistors
M305 P0 T100000 B3950 R4700 H30 L0	; Put your own H and/or L values here to set the bed thermistor ADC correction
M305 P1 T100000 B3974 R4700 H30 L0	; Put your own H and/or L values here to set the first nozzle thermistor ADC correction
M305 P2 T100000 B3974 R4700 H30 L0	; Put your own H and/or L values here to set the second nozzle thermistor ADC correction
M570 S180				; Hot end may be a little slow to heat up so allow it 180 seconds
 
; Fans
;M106 P1 H-1 				; disable thermostatic mode for fan 1
 
; Tool definitions
M563 P0 D0 H1 F0:1                      ; Define tool 0 - Heater 1, Fan 0 (extruder) and Fan 1 (bed fan)
G10 P0 S0 R0                        	; Set tool 0 operating and standby temperatures
M92 E663:663                       	; Set extruder steps per mm
 
; Z probe and compensation definition
;*** If you have a switch instead of an IR probe, change P1 to P4 in the following M558 command
M558 P5 X0 Y0 Z1 F100 T5000 H2	        ; Z probe is an inductive probe and is used for homing
G31 P1000 Z2			        ; Set the zprobe height and threshold (put your own values here)
 
;*** If you are using axis compensation, put the figures in the following command
;M556 S78 X0 Y0 Z0                   	; Axis compensation here
M208 S1 Z-0			        ; set minimum Z
;
T0					; select first hot end
 
 
;Enable pronterface?
M555 P2
 
;Enable Z-Axis because of dumb firmware
;M564 H0

[dirtybirdnj]

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

I just occured to me now that it looks like you have a duet wifi but are running 1.24? I think you're eligible to upgrade further to 2.03 if you wished.

This was one part of the update that was super confusing, I wasn't sure if the Duet2 and the DuetWifi I have are directly compatible with the firmware offered.

The file I sent during firmware writing using BOSSA was Duet2CombinedFirmware.bin from what appears to be the latest release.

https://github.com/dc42/RepRapFirmware/releases/tag/2.03

[Phaedrux]

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

G31 P1000 Z2

Your G31 needs to define the X and Y offset between the probe and the nozzle.

[Phaedrux]

What does the settings page say you have installed for firmwares?

[dirtybirdnj]

@phaedrux

First off thank you so much for your help with this!

Your G31 needs to define the X and Y offset between the probe and the nozzle.

!!!! wow lol seems like a critical thing to be missing... measuring this now and figuring out the distance

[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.