Okay

reading through the notes I found what the issue was.

"On Cartesian and CoreXY printers, normal G0 and G1 moves are no longer allowed before the corresponding axes have been homed. In particular, if your homex.g, homey.g and homeall.g files raise Z a little at the start and lower it at the end, you will need to add the S2 parameter to those G1 Z moves. Otherwise the G1 Z move will be refused unless Z has already been homed and the homing macro will be terminated."

I had to add the S2 to the end of my first G1 command in the homex.g file along with the other home files

; homex.g
; called to home the X axis

G91 ;Set to Relative Positioning
G1 Z5 F1000 S2 ; Lift Z relative to current position
G90 ;Back to absolute positioning
G1 X-225 F1800 S1 ; Move quickly to X axis endstop and stop there (first pass)
G91 ;Set to Relative Positioning
G1 X5 F6000 ; Go back a few mm
G90 ;Back to absolute positioning
G1 X-225 F360 S1 ; Move slowly to X axis endstop once more (second pass)
G91 ;Set to Relative Positioning
G1 Z-5 F1000 ; Lower Z again
G90 ;Back to absolute positioning

Hopefully somebody else upgrading finds this useful.

Okay

reading through the notes I found what the issue was.

"On Cartesian and CoreXY printers, normal G0 and G1 moves are no longer allowed before the corresponding axes have been homed. In particular, if your homex.g, homey.g and homeall.g files raise Z a little at the start and lower it at the end, you will need to add the S2 parameter to those G1 Z moves. Otherwise the G1 Z move will be refused unless Z has already been homed and the homing macro will be terminated."

I had to add the S2 to the end of my first G1 command in the homex.g file along with the other home files

; homex.g
; called to home the X axis

G91 ;Set to Relative Positioning
G1 Z5 F1000 S2 ; Lift Z relative to current position
G90 ;Back to absolute positioning
G1 X-225 F1800 S1 ; Move quickly to X axis endstop and stop there (first pass)
G91 ;Set to Relative Positioning
G1 X5 F6000 ; Go back a few mm
G90 ;Back to absolute positioning
G1 X-225 F360 S1 ; Move slowly to X axis endstop once more (second pass)
G91 ;Set to Relative Positioning
G1 Z-5 F1000 ; Lower Z again
G90 ;Back to absolute positioning

Hopefully somebody else upgrading finds this useful.

Hey everyone.

I finally got around to upgrading to 2.05 today.
The upgrade was successful. However I am getting the following error when trying to home any of my axis.

I assume I missed something that was changed between firmwares. I'm going through the change notes now.
I have also attached my config.g and homex.g files
config.g
homex.g

Thanks for any help.

ok so I can update to version 2.05 straight from 1.18.1?
so this is the order I update in?

1 Duet2CombinedFirmware
2 DuetWiFiServer
3 DuetWebControl

and do these steps?

1 The contents of DuetWebControl-SD-2.04.zip, extracted into the /www folder.
2 Duet2CombinedFirmware.bin, copied into /sys and renamed to exactly Duet2CombinedFirmware.bin
3 DuetWiFiServer.bin, copied into /sys and renamed to exactly DuetWiFiServer.bin.

Doing the upgrade

Send M997 S0:1 to upgrade both Duet2CombinedFirmware and DuetWiFiServer firmwares together.
or do I send M997 S0:1:2 to update all at the same time?

Then

Upload the new DuetWebControl.bin file to the /sys folder on the on-board SD card, either through the General tab on the Settings page of DuetWebControl or by moving the SD card to a PC.
Send M997 S2 to install it (if you uploaded it through DuetWebControl then it will offer to do this for you).

thanks

Hey everyone I've been running my duet wifi on my printer now for a couple years on 1.18.1 with no real problems.
Just wondering if its worth it to upgrade to a newer version? The only real issues I've had is some ajax disconnect errors every so often. I've read through the upgrade procedures a few times but its still a little confusing.
What version should I upgrade to if decide to?

Thanks

Thanks!! Makes a lot more sense now.

@dc42:

To use that S3D starting script, the grid needs to be defined using M577 first.

Did you mean M557? M577 is Wait until endstop is triggered

As you can see in my bed file I posted above I do use M557 command to define the grid.
Do you mean I need the M557 command in my starting script?

so the G32 command just calls the bed.g file to run which has the G29 command in it right?

I have recently switched over to the Duet WiFi and I'm having an issue with the G29 command not always running when I start a print.
The auto compensation works every time with no issues from the Duet WiFi Web interface.
I always run it before each print as seen below in my Simplify3D starting script.
The problem is sometimes it runs and sometimes it doesn't. I never change my starting script.
My firmware version is 1.18.1

zprobe settings

[[language]]
M558 P4 X0 Y0 Z1 H2 I1 F120 T6000 					
G31 P1000 X0 Y53 Z6.631 		

bed.g file

[[language]]
M561				       ;Clear any bed transform
G28				               ;Home all axes
G90 				               ; Back to absolute positioning
M557 X10:210 Y0:210 S40      ;Define mesh grid 
G29 S0				      ;Probe the bed and save height map to file
M374 				     ; Save calibration data. Default is sys/heightmap.csv

Simplify3D starting Script

[[language]]
G21 ;metric values 
G90 ;absolute positioning 
M107 ;start with the fan off 
G28 ;home all 
G29 ;run bed compensation
G0 X5 Y5 F5000 ;move to x5 y5
G1 Z0.4
G92 E0 ;zero the extruded length
G1 X40 E25 F500 ;extrude 25mm filament in a 40mm line
G92 E0 ;zero the extruded length 
G1 E-1 F500 ;retract a little
G1 X80 F4000 ;quick wipe

Thanks for the help. I have everything working now!
just as a reference below are my zprobe and bed.g configs

Z-Probe

[[language]]
M558 P4 X0 Y0 Z1 H2 I1 F120 T6000 
G31 P1000 X0 Y53 Z6.582

bed.g file

[[language]]
M561				
G28				
G90 	
M557 X10:210 Y0:210 S40
G29 S0				
M374 

I think i found my problem. Let me know if I'm right.

When setting up the grid with M557 I should subtract the z probe y offset (53) from my current numbers.
I believe it should look like this: M557 X10:210 Y0:157 S40