@NeoDue I too, previously had layer shifts. With the newer firmware, there are no layer shifts and it works great!

Thank you, @dc42!!

@o_lampe I think how @dc42 interacts with the community and listens to each one of us, is what makes the whole Duet ecosystem amazing!

While the endstop values are high, I don't think it is related to that. @dc42 what do you think?

Thanks,
Balaji

@balajiramani I tried the 3.5rc1+ firmware and the slope is no longer there.

So, after removing daemon.g, there are no pauses. Sorry for the false alarm.

@DonStauffer I too am having a similar problem with bed levelling. Printing with 3.6.0-alpha2+3 works fine and the input shaping is absolutely awesome! BTW, the printer I have is a delta.

The input shaping is so good that I am able to increase the accleration and jerk, without any artefacts. I was also able to drop the pressure advance value. I went from 0.21 to 0.14.

@dc42 Thank you! Verified that this version workes, irrespective of what the starting point for the bed calibration is.

@dc42 Thank you for the update. I will wait for the next release.

@dc42 were you able to take a look at this? I built the latest dev release and I still the same issue.

@droftarts The hissing sound is from the fans. The noise that I am referring to can be heard at 7 and 19 seconds in the video. It is from the delta tower motors. I am using a Duet Wifi 2 board. Input shaping is turned on. Here is the config.g file. Here is the output of M122 when the issue arises:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-beta.2 (2024-11-12 08:12:30) running on Duet WiFi 1.0 or 1.01
Board ID: 08DAM-999TL-MQ4SD-6JTDL-3SS6N-968BX
Used output buffers: 3 of 26 (19 max)
=== RTOS ===
Static ram: 23536
Dynamic ram: 67308 of which 12 recycled
Never used RAM 9316, free system stack 122 words
Tasks: NETWORK(1,ready,23.3%,195) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,7.4%,264) MAIN(1,running,69.2%,742) IDLE(0,ready,0.0%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:08:48 ago, cause: software
Last software reset at 2024-12-08 19:04, reason: User, Gcodes spinning, available RAM 12172, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 35.8, current 36.0, max 36.5
Supply voltage: min 23.6, current 24.2, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/1140/1072, gc cycles 1
Events: 0 queued, 0 completed
Date/time: 2024-12-11 20:25:22
Slowest loop: 16.23ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.9ms, write time 0.0ms, max retries 0
=== Move ===
Segments created 746, maxWait 45ms, bed comp in use: none, height map offset 0.000, hiccups added 65/0 (0.00ms), max steps late 0, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 67028.00/66704/0.74 63402.00/63796/-0.93 68665.00/68591/-0.77
next step interrupt due in 68 ticks, disabled
Driver 0: stalled, SG min 0
Driver 1: ok, SG min 0
Driver 2: ok, SG min 0
Driver 3: ok, SG min 0
Driver 4: standstill, SG min n/a
Driver 5: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
=== DDARing 0 ===
Scheduled moves 3130, completed 3091, LaErrors 0, Underruns [0, 0, 0]
=== Heat ===
Bed heaters 0 -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
HTTP is idle 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 22.00ms; fastest: 0.07ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.2.0
MAC address 5c:cf:7f:2c:25:00
Module reset reason: Turned on by main processor, Vcc 3.40, flash size 4194304, free heap 40844
WiFi IP address 192.168.1.61
Signal strength -46dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

I updated to 3.6.0-beta.2 and I noticed that there were some strange motor noise during printing. I also noticed that there were some layer shifts some times. I am attaching a video that shows the noise. I later lowered the acceleration for both X and Y from 4000 to 1000 and the noise went away. I went back to 3.6.0-beta.1 and noticed that there were no issues and the printer is able to handle the acceleration value of 4000.

The printer I have is a delta (not sure if this is something specific to a delta).

Here is the gcode that triggered the issue

22-334StringStar2L2N4open_0.2mm_PLA_BigDelta_12m.gcode

Here is the video that shows the motor noise - https://photos.app.goo.gl/dX5uqjCsf5SBth4Y9

@dc42 Yes, it is a Duet 2 Wifi board.

@dc42 I uploaded the 3.6.0-beta2+4 build an changed the height from 50mm to 10mm to as it would be easier to see if the problem occurs. When pausing, the effector moves in a straight line, but when resuming, it moves in a 'U' shape. I am attaching a video that shows that.

PXL_20241205_050140998.TS.mp4

@dc42 any update on this?

@dc42 were you able to look into this issue?

I paused a print and tried to resume it and the effector moved in a "U" shaped move when resuming the print. Due to this, the nozzle crashed into the printed part and messed up. This is on a delta printer.

I am attaching config.g, pause.g and resume.g.

Thanks,
Balaji

@dc42 Understand. Let me know if I can help in any way.