@dc42 Hi, I tested your files and the homing could be done properly.
Just to confirm I reverted to the public rc1 and the problem happens again, using rc1+2 behaves as expected.
Thanks for the help.

@dc42 I will have to wait a bit, unfortunately i destroyed my sbc (forgot that the camera link is not hot-plugable) and am waiting for a new one
As soon as i receive it I'll try the FW.

@dc42 Hi,

You may find all the files here

Thanks for the help,
Pedro Oliveira

@dc42 Thanks for the quick reply, on my eagerness to post I forgot valuable information:

• I'm using a Duet 3 6HC with an SBC
• Open loop steppers

In reality it does look like what you explained every now and then the stepper would make a sound like I had mixed the coils (usually after the 2nd probe location, but also on the 3rd) .

@tom33 I second this finding, today while testing 3.4 rc1 I couldn't get reliable reading while probing.
My setup is as follows:

; Drives
M569 P0.0 S0 D3 H50 V50                            ; physical drive 0.0 goes backwards
M569 P0.1 S0 D3 H50 V50                            ; physical drive 0.1 goes backwards
M569 P0.2 S0 D3 H50 V50                            ; physical drive 0.2 goes backwards
M569 P0.3 S1 D3 H50 V50                            ; physical drive 0.3 goes forwards
M569 P0.4 S1 D3 H50 V50                            ; physical drive 0.4 goes forwards
M569 P0.5 S0 D3 H50 V50                            ; physical drive 0.5 goes backwards
M584 X0.3 Y0.4 Z0.2:0.1:0.0 E0.5                 ; set drive mapping
M350 X16 Y16 Z16 E16 I1                              ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z1600.00 E835                         ; set steps per mm
M566 X400.00 Y400.00 Z6.00 E120.00 P1              ; set maximum instantaneous speed changes (mm/min)
M203 X20800.00 Y20800.00 Z1000.00 E3600.00         ; set maximum speeds (mm/min)
M201 X6000.00 Y6000.00 Z3000.00 E3600.00             ; set accelerations (mm/s^2)
M906 X2000 Y2000 Z1200 E800 I20                              ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; Set idle timeout

and my bed.g:

M561 ; clear any bed transform

G30 P0 X5 Y5 Z-99999      ; probe near a leadscrew
G30 P1 X5 Y20 Z-99999     ; probe near a leadscrew
G30 P2 X20 Y5 Z-99999     ; probe near a leadscrew
G30 P3 X230 Y470 Z-99999  ; probe near a leadscrew
G30 P4 X250 Y470 Z-99999  ; probe near a leadscrew
G30 P5 X250 Y450 Z-99999  ; probe near a leadscrew
G30 P6 X270 Y450 Z-99999  ; probe near a leadscrew
G30 P7 X470 Y20 Z-99999   ; probe near a leadscrew
G30 P8 X470 Y5 Z-99999    ; probe near a leadscrew
G30 P9 X450 Y5 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors

M280 P0 S160              ; clear and reset BL touch
G29 S1                    ; probe the bed and enable compensation

More what i found is that the motor attribution doesn't seem to work properly
while using M584 Z0:0 (and other possible combinations z0:1 or z0:2)
Sometimes I had two motors rotating and some others I had just one, I suspected I had something wrong with the wires but reverting to 3.3 made the printer fully operational without any physical change on the printer.

@dc42 Awsome, it worked like a charm! Thanks for the quick answer on a weekend.

I'm having an issue with the pwm fan setup in a duet 3 - 6hc, when using a 2 wire fan it works as expected but recently I decided to upgrade to pwm fans from noctua. When connecting them the fan will be running at 100% when the pwm in the interface is set to 0% and it will be off when the fan is set to 100% in the web interface.
The intermediate speed will also be decreasing as we increase the fan values in the web frontend.

I'm using the following sw version:

ii  duetcontrolserver                 3.2.2                               armhf        Control server application for Duet 3 series
ii  duetruntime                       3.2.2                               armhf        .NET Core runtime libraries for the Duet software framework
ii  duetsd                            1.1.0                               all          Virtual SD card directory for the Duet software framework
ii  duetsoftwareframework             3.2.2                               armhf        Meta package for the full Duet software framework
ii  duettools                         3.2.2                               armhf        Optional tools (code examples)
ii  duetwebcontrol                    3.2.2                               all          Official web interface for Duet electronics
ii  duetwebserver                     3.2.2                               armhf        Optional web server for Duet 3 series

And the following configuration for the fan:

M950 F1 C"out4" Q500                               ; create fan 1 on pin out4
M106 P1 C"Layer fan" S0 H-1 -L255                  ; set fan 1 value. Thermostatic control is turned off

Does someone have an ideia of what it could be, I suspect the L parameter on M106 but would like to confirm it.

Cheers,
Pedro