[3.5.0.beta.4] Clicking Z-Screws after upgrade from RRF 3.4.6

MaxGyver

After upgrading from RRF 3.4.6 to 3.5.0.beta.4, I noticed a clicking sound coming from all four of my Z-leadscrews when printing with mesh compensation enabled. The clicking is caused by the lead screw motors that make a small but abrupt movement when changing direction. When placing a finger on one of the leadscrews it feels like something is clicking into place before the motor starts turning in the opposite direction.

In addition to the clicking, the mesh compensation does not work properly. I have the impression that the Z-Axis motors are loosing steps. Downgrading to RRF 3.4.6 solves the issue.

Although the printer is quite noisy, the clicking can be heard in this video.

T3P3Tony

@MaxGyver I know there were changes to M201 and M203 (adding of M201.1 and M203.1 defaults) however that should not have impacted mesh compensation moves. From your description is sounds like the jerk values are super high, but that would impact other Z moves so probably not that.

Did you capture a M122 before downgrading? i would be interesting to see if any hiccups were reported.

MaxGyver

@T3P3Tony

I am not using M201.1 and 203.1 yet.

I have a Duet 3 MB6HC+ 1HCL for X and Y.
I will revert to stable and post the diagnostics tomorrow.

Here is my systems diagnostic for 3.5.0.beta.4:

=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.5.0-beta.4 (2023-06-08 23:41:30) running on Duet 3 MB6HC v1.0 or earlier (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J1F2-3SN6N-1U0LG
Used output buffers: 1 of 40 (18 max)
=== RTOS ===
Static ram: 155012
Dynamic ram: 87716 of which 0 recycled
Never used RAM 99688, free system stack 136 words
Tasks: SBC(2,ready,2.7%,406) HEAT(3,nWait,0.0%,323) Move(4,nWait,1.4%,214) CanReceiv(6,nWait,0.0%,796) CanSender(5,nWait,0.0%,328) CanClock(7,delaying,0.0%,344) TMC(4,nWait,8.2%,59) MAIN(2,running,87.4%,135) IDLE(0,ready,0.1%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:44:39 ago, cause: software
Last software reset at 2023-08-21 18:56, reason: User, FilamentSensors spinning, available RAM 99896, slot 1
Software reset code 0x600d HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
MCU temperature: min 41.7, current 43.3, max 43.6
Supply voltage: min 0.5, current 23.9, max 24.2, under voltage events: 1, over voltage events: 0, power good: yes
12V rail voltage: min 0.2, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 99/10, heap memory allocated/used/recyclable 2048/708/332, gc cycles 0
Events: 3 queued, 3 completed
Driver 0: ok, SG min 0, mspos 193, reads 17515, writes 38 timeouts 0
Driver 1: ok, SG min 0, mspos 95, reads 17515, writes 38 timeouts 0
Driver 2: ok, SG min 0, mspos 207, reads 17515, writes 38 timeouts 0
Driver 3: ok, SG min 0, mspos 433, reads 17515, writes 38 timeouts 0
Driver 4: ok, SG min 0, mspos 703, reads 17523, writes 30 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 17532, writes 22 timeouts 0
Date/time: 2023-08-21 19:41:01
Slowest loop: 95.51ms; fastest: 0.05ms
=== Storage ===
Free file entries: 20
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 30, maxWait 492336ms, bed compensation in use: mesh, height map offset 0.000, ebfmin -1.00, ebfmax 1.00
next step interrupt due in 195 ticks, disabled
=== DDARing 0 ===
Scheduled moves 32182, completed 32147, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], CDDA state 3
=== DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.2
Heater 1 is on, I-accum = 0.2
=== GCodes ===
Movement locks held by null, null
HTTP* is doing "M122" in state(s) 0
Telnet is idle in state(s) 0
File* is idle in state(s) 3
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
File2* is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 7, axes/extruders owned 0x80000007
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 99409, received 64255, lost 0, boc 0
Longest wait 56ms for reply type 6041, peak Tx sync delay 57490, free buffers 50 (min 17), ts 13399/13382/0
Tx timeouts 0,0,16,0,0,0 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 34295/34295
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x25ce8
Buffer RX/TX: 3168/4040-0, open files: 0
=== Duet Control Server ===
Duet Control Server version 3.5.0-beta.4 (2023-06-09 10:49:49)
File /opt/dsf/sd/gcodes/Luftungsgitter_V6_zum verschrauben_ASA_15h48m.gcode is selected, processing
File:
Buffered code: G1 X202.949 Y72.635 Z.5
Buffered code: G1 Z.2
Buffered code: G1 E.3 F4800
Buffered code: G1 F3600
Buffered code: G1 X202.78 Y72.436 E.00093
Buffered code: G1 X202.61 Y72.238 E.00178
Buffered code: G1 X202.318 Y71.919 E.00437
Buffered code: G1 X202.025 Y71.6 E.00573
Buffered code: G1 X201.733 Y71.28 E.00709
Buffered code: G2 X199.885 Y69.464 I-26.928 J25.554 E.05301
Buffered code: G1 X199.579 Y69.194 E.00642
Buffered code: G1 X199.274 Y68.924 E.00476
Buffered code: G1 X198.969 Y68.654 E.00311
Buffered code: G1 E-.21 F4800
Buffered code: G1 F19200
Buffered code: G1 X199.274 Y68.924 E-.0855
Buffered code: G1 E-.0045 F4800
Buffered code: G1 X193.625 Y69.848 Z.5 F18000
Buffered code: G1 X16.909 Y98.745 Z.5
Buffered code: G1 Z.2
Buffered codes: 896 bytes total
Code buffer space: 3168
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 1
Full transfers per second: 159.64, max time between full transfers: 879.0ms, max pin wait times: 86.6ms/36.6ms
Codes per second: 583.23
Maximum length of RX/TX data transfers: 4496/3044

T3P3Tony

@MaxGyver thanks. That's not showing the specific issues i was wondering about but @dc42 my have ideas about how to isolate what it could be.

MaxGyver

@T3P3Tony
@dc42

After formatting the SD-Card and flashing RRF 3.5.0-rc1. I have had no problems with clicking Z-Screws. I would consider this issue solved.

T3P3Tony

@MaxGyver thanks!