I have two printers powered by DuetWifi. One is a custom made Kossel (delta) and the other is a big core-xy. I've been running 2.02 on both for a long time period, more than a year. I recently updated the delta to 2.05. It worked like a charm. I liked the new web interface so decided after a week or so that I also will update the Core-xy to the same FW package.
After the update the Core-xy would not home the Z-axis correctly. I'm using the Escher IR-sensor and the Z-plane is driven by two separate motors to accomodate leadscrew adjustment. The Z-homing procedure gives an error message that the sensor was not triggered and the Z-plane ends up 3-4 mm away from the nozzle. I didnt't investigate as i were short of time. I just downgraded to 2.03 and the Core-xy was now behaving correct again.
Has the homing G-codes or their parameters behaviour changed in between versions?
Here are the relevant code from config.g that relates to the homing/sensor part:
; Mode and axis travel
M667 S1 ; Select CoreXY mode
M208 X0 Y-10 Z-0.6 S1 ; Set axis minima
M208 X325 Y325 Z380 S0 ; Set axis maxima
; Endstops, Z-probe and bed mesh grid
M574 X1 Y1 S0 ; Set active low endstop switches on X and Y
M574 Z1 S2 ; Set active high Z-probe as endstop Z
M591 D0 P2 C3 S1 ; Filament sensor enable Extruder 0 - E0 endst. input, normal low OK
M558 P1 H2.5 A2 R0.35 S0.02 F140 T8000 ; Set Z probe type to IR sensor, dive height, recov time, tolerance, dive speed, and # of probings/point
G31 P500 X0 Y15 Z2.77 ; Set Z probe trigger value, X/Y offset and trigger height
Best regards /Thom