3.4 rc1 1XD Probe problem after update

[x_pedro_x]

@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]

@x_pedro_x @tom33 the significant difference between 3.4rc1 (also 3.4beta7) and earlier releases is that in 3.4rc1, when a motor controlled by a CAN-connected board is stopped because and endstop or Z probe is triggered, the slight overshoot that occurs is corrected after a short delay by reversing the motor movement and sending whatever steps are needed. If you are using closed-loop drivers, perhaps they don't handle this situation very well? If so then reducing the speed of the homing or probing move may help.

[x_pedro_x]

@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) .

[dc42]

@x_pedro_x please post your complete config.g file so that I can reproduce your setup.

[x_pedro_x]

@dc42 Hi,

You may find all the files here

Thanks for the help,
Pedro Oliveira

[tom33]

@dc42 I don't have the problem for the homing just for the probing. And Reduce the acceleration or speed doesn't work for me

[dc42]

@tom33 @x_pedro_x this has now been fixed. Please try the new expansion board firmware at https://www.dropbox.com/sh/2dt7sbqpx6l74np/AADn4-lpcil1iqnWKkiVri3Ia?dl=0.

[x_pedro_x]

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

[Marcossf]

@x_pedro_x @dc42 I think we have the same problem than you, as David said in our post entry. We will test it tomorrow to see if the 3.4RC1+2 solve the issue.

David, do we use all RC1+2 dropbox updated files, or only the one for the 1XD board?

[Marcossf]

@x_pedro_x Hi Pedro, we've tested with the David's 1LC 3.4rc1+2 files and it's working fine.

[tom33]

@dc42 I try this today !

[x_pedro_x]

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