1HCL probing problem with ***video***

[HighFreq]

@phaedrux said in 1HCL probing problem with ***video***:

sudo apt dist-upgrade

I updated as reported and it found 4 updated packages, than i run sudo apt dist-upgrade and it did it but didn't update any of the boards (i updated boards yesterday with unstable).
Is it ok?

firmware version 3.4.2 (2022-09-13 15:04:57) is this the correct one?

pi@Duet3:~ $ sudo apt update
Scaricamento di:1 http://archive.raspberrypi.org/debian buster InRelease [32,6 kB]
Scaricamento di:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15,0 kB]
Scaricamento di:3 https://pkg.duet3d.com stable InRelease [2.563 B]
Scaricamento di:4 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13,0 MB]
Scaricamento di:5 http://archive.raspberrypi.org/debian buster/main armhf Packages [392 kB]
Scaricamento di:6 https://pkg.duet3d.com stable/armv7 armhf Packages [22,1 kB]
Recuperati 13,5 MB in 9s (1.501 kB/s)
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
4 pacchetti possono essere aggiornati: eseguire "apt list --upgradable" per vederli.
pi@Duet3:~ $ sudo apt dist-upgrade
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
Calcolo dell'aggiornamento... Fatto
I seguenti pacchetti saranno aggiornati:
bzip2 libbz2-1.0 libmariadb3 mariadb-common
4 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
È necessario scaricare 283 kB di archivi.
Dopo quest'operazione, verranno occupati 1.024 B di spazio su disco.
Continuare? [S/n] s
Scaricamento di:1 http://debian.bio.lmu.de/raspbian/raspbian buster/main armhf bzip2 armhf 1.0.6-9.2~deb10u2 [46,3 kB]
Scaricamento di:2 http://debian.bio.lmu.de/raspbian/raspbian buster/main armhf libbz2-1.0 armhf 1.0.6-9.2~deb10u2 [43,3 kB]
Scaricamento di:3 http://debian.bio.lmu.de/raspbian/raspbian buster/main armhf mariadb-common all 1:10.3.36-0+deb10u1 [33,2 kB]
Scaricamento di:4 http://debian.bio.lmu.de/raspbian/raspbian buster/main armhf libmariadb3 armhf 1:10.3.36-0+deb10u1 [161 kB]
Recuperati 283 kB in 1s (303 kB/s)
Lettura dei changelog... Fatto
(Lettura del database... 103123 file e directory attualmente installati.)
Preparativi per estrarre .../bzip2_1.0.6-9.2~deb10u2_armhf.deb...
Estrazione di bzip2 (1.0.6-9.2~deb10u2) su (1.0.6-9.2~deb10u1)...
Preparativi per estrarre .../libbz2-1.0_1.0.6-9.2~deb10u2_armhf.deb...
Estrazione di libbz2-1.0:armhf (1.0.6-9.2~deb10u2) su (1.0.6-9.2~deb10u1)...
Configurazione di libbz2-1.0:armhf (1.0.6-9.2~deb10u2)...
(Lettura del database... 103123 file e directory attualmente installati.)
Preparativi per estrarre .../mariadb-common_1%3a10.3.36-0+deb10u1_all.deb...
Estrazione di mariadb-common (1:10.3.36-0+deb10u1) su (1:10.3.34-0+deb10u1)...
Preparativi per estrarre .../libmariadb3_1%3a10.3.36-0+deb10u1_armhf.deb...
Estrazione di libmariadb3:armhf (1:10.3.36-0+deb10u1) su (1:10.3.34-0+deb10u1)...
Configurazione di bzip2 (1.0.6-9.2~deb10u2)...
Configurazione di mariadb-common (1:10.3.36-0+deb10u1)...
Configurazione di libmariadb3:armhf (1:10.3.36-0+deb10u1)...
Elaborazione dei trigger per man-db (2.8.5-2)...
Elaborazione dei trigger per libc-bin (2.28-10+rpt2+rpi1+deb10u1)...

[HighFreq]

@Phaedrux

Still having same exact problem.

Requested files:

config.g

; Configuration file for Duet 3 (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Sat Jul 02 2022 11:44:56 GMT+0200 (Ora legale dell’Europa centrale)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Duet 3" ; set printer name

; Wait for expansion boards to star
G4 S1

; Fans
M950 F0 C"!out4+out4.tach" Q25000 ; fan 0 con tach. + pwm freq 25kHz
M106 P0 S0 ; fan al minimo

; Input ports
M950 J5 C"io5.in"
M950 J6 C"io6.in"
M950 J7 C"io7.in"
M950 J8 C"io8.in"

; Output ports
M950 P5 C"io5.out" Q0
M950 P6 C"io6.out" Q0
M950 P7 C"io7.out" Q0
M950 P8 C"io8.out" Q0

; Drives
M569 P1.0 D0 S0 ; asse Z - accensione in Open Loop per evitare caduta durante il tuning
M569 P2.0 D0 S0
M569 P3.0 D0 S0
M569 P4.0 D0 S0
M569 P1 S0 T2:2:0:0 ; asse Y
M569 P0 S0 ; asse X
M569 P10.1 S1 ; extruder motor
;M917 Z0 ;riduzione di corrente a motore fermo per asse
M584 X0 Y1 Z1.0:2.0:3.0:4.0 E10.1 ;mappa driver per ogni asse
M350 Z16 I1 ; configure microstepping with interpolation
M92 X200 Y200 Z320 E224.6 ; set steps per mm
M566 X10000 Y10000 Z60.00 U120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X60000 Y60000 Z5000 U9000 ; set maximum speeds (mm/min)
M201 X1000 Y1000 Z200 U250.00 ; set accelerations (mm/s^2)
M906 Z6000 E2500 ; set motor currents (mA)
M84 S0 ; Disable motor idle current reduction

; Brakes
M569.7 P1.0 C"out1"
M569.7 P2.0 C"out1"
M569.7 P3.0 C"out1"
M569.7 P4.0 C"out1"

; accensione assi
M17 Z E
G4 S2 ; attesa per essere sicuri che la Z sia eccitata

; Z Encoders
M569.1 P1.0 T2 C5 R100 I8000 D0.1 E10.0:30.0; PID asse Z
M569.1 P2.0 T2 C5 R100 I8000 D0.1 E10.0:30.0
M569.1 P3.0 T2 C5 R100 I8000 D0.1 E10.0:30.0
M569.1 P4.0 T2 C5 R100 I8000 D0.1 E10.0:30.0

; Drives
M569 P1.0 D4 S0 ; asse Z - accensione in Closed Loop
M569 P2.0 D4 S0
M569 P3.0 D4 S0
M569 P4.0 D4 S0

; Tuning
;polarity and zeroing asse Z
M569.6 P1.0 V1
M569.6 P2.0 V1
M569.6 P3.0 V1
M569.6 P4.0 V1

; Axis Limits
M208 X0:1000 Y0:1000 Z0:1500

; Endstops
M574 Z1 S1 P"1.io0.in+2.io0.in+3.io0.in+4.io0.in"

; Bed plate Heaters
M308 S0 A"Dietro DX" P"temp0" Y"pt1000" ; configure sensor as thermistor on pin
M308 S1 A"Dietro SX" P"temp1" Y"pt1000"
M308 S2 A"Avanti SX" P"temp2" Y"pt1000"
M308 S3 A"Avanti DX" P"temp3" Y"pt1000"
M950 H1 C"out0" T0 ; create bed heater output and map it to sensor
M950 H2 C"out1" T1
M950 H3 C"out2" T2
M950 H4 C"out8" T3
M307 H1 R0.040 K0.060:0.000 D23.41 E1.35 S1.00 B0 ; PID
M307 H2 R0.040 K0.060:0.000 D23.41 E1.35 S1.00 B0
M307 H3 R0.040 K0.060:0.000 D23.41 E1.35 S1.00 B0
M307 H4 R0.040 K0.060:0.000 D23.41 E1.35 S1.00 B0
M140 P1 H1 ; map heated bed to heater
M140 P2 H2
M140 P3 H3
M140 P4 H4
M143 H1 S120 ; set temperature limit for heater
M143 H2 S120
M143 H3 S120
M143 H4 S120

; Extruder Heaters
M308 S10 A"Top" P"spi.cs2" Y"rtd-max31865" ; configure sensor as thermistor on pin
M308 S11 A"Bottom" P"spi.cs4" Y"rtd-max31865"
M308 S12 A"Nozzle" P"spi.cs1" Y"rtd-max31865"
M950 H10 C"out5" T10 ; create nozzle heater output and map it to sensor
M950 H11 C"out7" T11
M950 H12 C"out6" T12
M307 H10 B0 S1.00 ; disable bang-bang mode for the nozzle heater and set PWM limit
M307 H11 B0 S1.00
M307 H12 B0 S1.00
M143 H10 S300 ; set temperature limit for heater
M143 H11 S300
M143 H12 S300

; Tools
M563 P0 D0 H10:11:12 F0 S"Pulsar" ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C

; Z-Probe
M558 Z P5 K0 C"io1.in" H5 F20:20 T100 ; definizione probe Z
G31 K0 X-3 Y54.5 Z0 ; offset rispetto alla testa
;M557 X15:215 Y15:195 S20 ; define mesh grid

17/9/2022, 08:20:40 m122 b10
Diagnostics for board 10:
Duet EXP3HC rev 1.01 or earlier firmware version 3.4.2 (2022-09-13 15:05:23)
Bootloader ID: SAME5x bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 158932, free system stack 200 words
Tasks: Move(notifyWait,0.0%,160) HEAT(notifyWait,0.0%,88) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,82) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.4%,99) MAIN(running,91.3%,407) IDLE(ready,0.0%,40) AIN(delaying,1.3%,263), total 100.0%
Last reset 00:23:12 ago, cause: power up
Last software reset data not available
Driver 0: pos 0, 80.0 steps/mm,standstill, SG min n/a, mspos 8, reads 18745, writes 0 timeouts 0, steps req 0 done 0
Driver 1: pos 0, 224.6 steps/mm,standstill, SG min n/a, mspos 8, reads 18745, writes 0 timeouts 0, steps req 0 done 0
Driver 2: pos 0, 80.0 steps/mm,standstill, SG min n/a, mspos 8, reads 18745, writes 0 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -4/7, peak Rx sync delay 176, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.1, current 24.1, max 24.1
V12 voltage: min 12.2, current 12.2, max 12.2
MCU temperature: min 25.0C, current 37.6C, max 38.2C
Last sensors broadcast 0x00000000 found 0 5 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 2111, send timeouts 0, received 2348, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

17/9/2022, 08:20:37 m122 b4
Diagnostics for board 4:
Duet EXP1HCL firmware version 3.4.2 (2022-09-13 15:04:57)
Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 52256, free system stack 192 words
Tasks: Move(notifyWait,0.0%,152) HEAT(notifyWait,0.0%,88) CanAsync(notifyWait,0.0%,70) CanRecv(notifyWait,0.0%,79) CanClock(notifyWait,0.0%,70) TMC(notifyWait,41.5%,356) CLSend(notifyWait,0.0%,152) MAIN(running,56.7%,399) IDLE(ready,0.0%,30) AIN(notifyWait,1.7%,265), total 100.0%
Last reset 00:23:10 ago, cause: power up
Last software reset data not available
Closed loop enabled: yes, pre-error threshold: 10.00, error threshold: 30.00, encoder type rotaryQuadrature, reverse polarity: yes, position -1, raw count = 1, tuning mode: 0, tuning error: 0, collecting data: no
Control loop runtime (ms): min=0.004, max=0.037, frequency (Hz): min=10000, max=17045
Driver 0: pos 0, 320.0 steps/mm,ok, SG min 0, mspos 8, reads 51369, writes 45978 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -8/10, peak Rx sync delay 202, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 47.9, current 48.1, max 48.3
V12 voltage: min 12.0, current 12.1, max 12.1
MCU temperature: min 24.4C, current 40.5C, max 40.5C
Last sensors broadcast 0x00000000 found 0 214 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 11167, send timeouts 0, received 12340, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

17/9/2022, 08:20:35 m122 b3
Diagnostics for board 3:
Duet EXP1HCL firmware version 3.4.2 (2022-09-13 15:04:57)
Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 52256, free system stack 192 words
Tasks: Move(notifyWait,0.0%,152) HEAT(notifyWait,0.0%,88) CanAsync(notifyWait,0.0%,70) CanRecv(notifyWait,0.0%,79) CanClock(notifyWait,0.0%,70) TMC(notifyWait,41.6%,356) CLSend(notifyWait,0.0%,152) MAIN(running,56.6%,417) IDLE(ready,0.0%,30) AIN(notifyWait,1.7%,265), total 100.0%
Last reset 00:23:07 ago, cause: power up
Last software reset data not available
Closed loop enabled: yes, pre-error threshold: 10.00, error threshold: 30.00, encoder type rotaryQuadrature, reverse polarity: yes, position -1, raw count = 1, tuning mode: 0, tuning error: 0, collecting data: no
Control loop runtime (ms): min=0.004, max=0.036, frequency (Hz): min=10000, max=17045
Driver 0: pos 0, 320.0 steps/mm,ok, SG min 0, mspos 8, reads 39943, writes 58559 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -9/8, peak Rx sync delay 202, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 47.7, current 47.9, max 48.1
V12 voltage: min 12.0, current 12.0, max 12.0
MCU temperature: min 26.1C, current 39.6C, max 39.8C
Last sensors broadcast 0x00000000 found 0 69 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 11146, send timeouts 0, received 12315, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

17/9/2022, 08:20:33 m122 b2
Diagnostics for board 2:
Duet EXP1HCL firmware version 3.4.2 (2022-09-13 15:04:57)
Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 52256, free system stack 182 words
Tasks: Move(notifyWait,0.0%,152) HEAT(notifyWait,0.0%,88) CanAsync(notifyWait,0.0%,70) CanRecv(notifyWait,0.0%,79) CanClock(notifyWait,0.0%,72) TMC(notifyWait,41.6%,360) CLSend(notifyWait,0.0%,152) MAIN(running,56.7%,399) IDLE(ready,0.0%,30) AIN(notifyWait,1.7%,265), total 100.0%
Last reset 00:23:06 ago, cause: power up
Last software reset data not available
Closed loop enabled: yes, pre-error threshold: 10.00, error threshold: 30.00, encoder type rotaryQuadrature, reverse polarity: yes, position -1, raw count = 65535, tuning mode: 0, tuning error: 0, collecting data: no
Control loop runtime (ms): min=0.004, max=0.017, frequency (Hz): min=10417, max=17045
Driver 0: pos 0, 320.0 steps/mm,ok, SG min 0, mspos 8, reads 28411, writes 58431 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -6/6, peak Rx sync delay 201, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 48.0, current 48.1, max 48.4
V12 voltage: min 12.1, current 12.1, max 12.1
MCU temperature: min 24.9C, current 39.7C, max 39.7C
Last sensors broadcast 0x00000000 found 0 46 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 11132, send timeouts 0, received 12300, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

17/9/2022, 08:20:31 m122 b1
Diagnostics for board 1:
Duet EXP1HCL firmware version 3.4.2 (2022-09-13 15:04:57)
Bootloader ID: SAME5x bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 52256, free system stack 178 words
Tasks: Move(notifyWait,0.0%,152) HEAT(notifyWait,0.0%,88) CanAsync(notifyWait,0.0%,70) CanRecv(notifyWait,0.0%,79) CanClock(notifyWait,0.0%,70) TMC(notifyWait,41.9%,356) CLSend(notifyWait,0.0%,152) MAIN(running,56.4%,407) IDLE(ready,0.0%,30) AIN(notifyWait,1.7%,265), total 100.0%
Last reset 00:23:03 ago, cause: power up
Last software reset data not available
Closed loop enabled: yes, pre-error threshold: 10.00, error threshold: 30.00, encoder type rotaryQuadrature, reverse polarity: yes, position -1, raw count = 1, tuning mode: 0, tuning error: 0, collecting data: no
Control loop runtime (ms): min=0.009, max=0.036, frequency (Hz): min=10000, max=15625
Driver 0: pos 0, 320.0 steps/mm,ok, SG min n/a, mspos 8, reads 0, writes 60327 timeouts 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -6/13, peak Rx sync delay 200, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 47.9, current 47.9, max 48.0
V12 voltage: min 12.0, current 12.1, max 12.1
MCU temperature: min 26.9C, current 41.4C, max 41.6C
Last sensors broadcast 0x00000000 found 0 8 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 7634, send timeouts 0, received 8558, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

17/9/2022, 08:22:54 m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6XD version 3.4.2 (2022-09-13 15:19:26) running on Duet 3 MB6XD v1.0 or later (SBC mode)
Board ID: 08DLM-956DA-M24S4-7J1D4-3SJ6N-KBJYU
Used output buffers: 1 of 40 (15 max)
=== RTOS ===
Static ram: 151256
Dynamic ram: 67192 of which 0 recycled
Never used RAM 132224, free system stack 200 words
Tasks: SBC(ready,0.6%,487) HEAT(notifyWait,0.1%,374) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,773) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,352) MAIN(running,99.2%,1082) IDLE(ready,0.1%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:25:26 ago, cause: power up
Last software reset at 2022-09-16 19:31, reason: User, GCodes spinning, available RAM 132224, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 18633
MCU temperature: min 35.9, current 40.0, max 40.3
Supply voltage: min 23.8, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok
Driver 1: ok
Driver 2: ok
Driver 3: ok
Driver 4: ok
Driver 5: ok
Date/time: 2022-09-17 08:22:53
Slowest loop: 1000.36ms; fastest: 0.03ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 1 2 3 4 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger* is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 10681, received 47428, lost 0, boc 0
Longest wait 4ms for reply type 6024, peak Tx sync delay 398, free buffers 50 (min 49), ts 5902/5902/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 33773/33773
SPI underruns 0, overruns 0
State: 5, disconnects: 1, timeouts: 1 total, 1 by SBC, IAP RAM available 0x2b738
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.2
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 37.25, max time between full transfers: 53.3ms, max pin wait times: 44.8ms/1.2ms
Codes per second: 0.01
Maximum length of RX/TX data transfers: 3795/64

I get the following error too:

Event notification
Driver 1.0 error: failed to maintain position

[HighFreq]

@Phaedrux do you have any news by any chance? We are basicly unable to go forward with the printer because of the problem we are encountering in probing with 1HCL.

[dc42]

@highfreq are all four Z motors doing the same?

[HighFreq]

@dc42 Yes the entire gantry jumps up on all 4 corners.

[dc42]

@highfreq I've tried to reproduce this on a bench system with a single Z motor, but I don't see that issue. The behaviour is the same in open and closed loop mode. The only issues I saw were:

1. The maximum motor speed is lower in closed loop mode than in open loop mode. With microstepping set to x16 and Z steps/mm set to 4000, the maximum speed in closed loop mode is about 200 mm/min. That's equivalent to 133kHz step rate. This isn't unexpected, because the PID loop runs at between 9740 and 17045 Hz, and the maximum the motor can be commanded in one PID cycle is one full step.

2. If I run some tests in closed loop mode, change to open loop mode to run more tests, and then change back to closed loop mode, the motor no longer moves. Re-running my tuning macro makes it work again.

To set up for testing I do this

• Set up the motor in closed loop node and run basic tuning
• Send G92 X0 Y0 to pretend that X and Y are homed (because I am running on a bench system)
• Configure a Z probe with dive height set to H0.1

The test I run is:

• Send G1 Z20 F200 G30. After it completed the G1 move and starts the probing move, press the Z probe switch.

PS - if I create a homez.g file containing just a G30 command, then when I press Home Z in DWC it also works correctly.

What command are you running to provoke the error?

[HighFreq]

@dc42 i do G92 x0 y0 to home x and y than i run G30 and press the z probe switch than it jumps.
I don't send any G1 i just send a G30 while the switch is 30mm above a carton box and wait for the switch to hit the box.

I have a dive height of 5mm, could it be the problem? Should i try 0.1mm? To be honest i didn't understand what dive height really is.

[dc42]

@highfreq I only reduced the dive height so that the motor moves back up less when the probe triggers, so that I can more easily see how far the motor shaft rotates.

I am running a slightly different version of MB6XD firmware from the standard one. I don't think it should make any difference, but I suggest you try it anyway. Here is is. To install it, upload it via DWC. After installation, M115 should return:

FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.4.2+ ELECTRONICS: Duet 3 MB6HC v1.02 or later FIRMWARE_DATE: 2022-09-16 15:25:37

Duet3Firmware_MB6XD.bin

[dc42]

@highfreq I am trying to reproduce your configuration more accurately.

• When you run the G30 command, is the Z axis showing as being homed already, or not?
• What is in your homez.g file?

[HighFreq]

@dc42 thank you for your help, i am out of office now, will test everything tomorrow and will send you files.

[dc42]

@highfreq tomorrow is a public holiday in UK because of the Queen's funeral; however I may be online some of the time.

[HighFreq]

@dc42 I am trying updating firmware from web interface, it says i am running sbc and update only if adviced from developers i click yes but m115 command always shows old version.

Is there another way to update if running trough raspberry?

[HighFreq]

The video shows only one of the z axis during a G30 command, please turn on audio with phases description.

https://share.icloud.com/photos/06cU8ELrfs-zCSDhG1GmE0kaw

We are really at a loss now, we do not know where to look, if we configure our X axis as Z (it uses a different motor driver) probing works as expected with first touch than back than second touch than back. Using 1HCL it never works, not in open nor in closed loop. It is probably a configuration problem on our side but we do not know where to look.

One other thing, if we issue a G1 Z20 F200 G30 , he G30 is ignored, machine only execute the G1, if we issue two G1 commands on same line it executes them.

[HighFreq]

@dc42 I think we understood where the problem is. Between first and second touch of the probe the axis goes back to whee the G30 started.
As i understand after first touch should go back by the amount set in the dive, instead it goes back more or less where the g30 started, so if i start a g30 200mm above bed, when it touches the bed the first time it goes back to 200mm above and it starts the second touch.

Basicly i think there is a bug on how it handles backup between first ad second touch when in closed loop.

In open loop it works it seems but between first and second touch it emits a beeping sound, maybe it would go back like in closed loop but being in open it skips steps and looks like it works?

[JoergS5]

This post is deleted!

[HighFreq]

@joergs5 would you mind let the thread follow what the real problem is and not a simple answer i gave to the developer that used that commands in his tests?

[JoergS5]

This post is deleted!

[HighFreq]

@dc42 can you give us any help please? we are pretty much at a loss.

thanks.

[HighFreq]

@dc42 the problem we have looks very much like

https://forum.duet3d.com/topic/27248/3-4-rc1-1xd-probe-problem-after-update

Is there any chance you reintroduced the bug in following releases?

[HighFreq]

@dc42 we tested the firmware in the thread i mentioned but it does exactly the same. It keeps jumping back after first touch.

We have been trying pretty much everything in the last days, a sign of life on your side would e nice

As it is now is unusable, i am wondering if it is us or simply nobody uses multi z axis on 1HCL yet.