y slope with 3.5.0-rc1, not seen with 3.4.6
-
@dc42 I also checked a 20x20x20 plain filled cube, as this has a more pronounced y slope than the 30x20x20 cube.
debug:24/03/2024, 10:58:02 Finished printing file 0:/gcodes/20x20x20cube_filled.gcode, print time was 0h 24m 24/03/2024, 10:52:49 Duet3D laser filament monitor v2 on pin (connlcd.encb,connlcd.3), enabled when SD printing, allow 1% to 300%, check all extruding moves every 10.0mm, cal. factor 0.450, quality 219, measured min 86% avg 98% max 116% over 1430.4mm 24/03/2024, 10:52:11 Seg length diff -8.60e-7 at 5 S d=8.5258e-4 t=16.4 b=9.4745e+3 c=-3.6557e+8 a=-5.4710e-9 24/03/2024, 10:51:46 Seg length diff 8.93e-7 at 5 S d=8.5449e-4 t=16.5 b=9.4796e+3 c=-3.6584e+8 a=-5.4669e-9 24/03/2024, 10:51:43 Seg length diff 9.40e-7 at 5 S d=8.5258e-4 t=16.5 b=9.4796e+3 c=-3.6586e+8 a=-5.4666e-9 24/03/2024, 10:51:18 Seg length diff 8.71e-7 at 5 S d=8.0872e-4 t=16.9 b=1.6875e+4 c=-7.0312e+8 a=-2.8444e-9 24/03/2024, 10:36:17 Seg length diff 9.52e-7 at 5 S d=9.0218e-4 t=17.3 b=9.6610e+3 c=-3.7000e+8 a=-5.4053e-9 24/03/2024, 10:36:16 Seg length diff -9.28e-7 at 5 S d=8.8501e-4 t=16.9 b=9.6607e+3 c=-3.7000e+8 a=-5.4055e-9 24/03/2024, 10:33:21 M32 "0:/gcodes/20x20x20cube_filled.gcode" File 0:/gcodes/20x20x20cube_filled.gcode selected for printingM122:
24/03/2024, 11:02:48 M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.3+ (2024-03-18 09:34:21) running on Duet WiFi 1.0 or 1.01 Board ID: 08DAM-999TL-MQ4SD-6J9FD-3SJ6J-K593W Used output buffers: 3 of 26 (26 max) === RTOS === Static ram: 23256 Dynamic ram: 76852 of which 12 recycled Never used RAM 7656, free system stack 68 words Tasks: NETWORK(2,nWait 6,14.2%,193) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,1.5%,242) MAIN(1,running,84.2%,841) IDLE(0,ready,0.0%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 01:12:41 ago, cause: power up Last software reset at 2024-03-05 21:23, reason: User, Gcodes spinning, available RAM 11272, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x08 Aux0 errors 0,0,0 MCU temperature: min 26.5, current 28.1, max 35.3 Supply voltage: min 24.1, current 24.4, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/64/64, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0 Driver 1: standstill, SG min 0 Driver 2: standstill, SG min 0 Driver 3: standstill, SG min 0 Driver 4: standstill, SG min 0 Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2024-03-24 11:02:46 Cache data hit count 4294967295 Slowest loop: 211.56ms; fastest: 0.14ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 8.2ms, write time 0.0ms, max retries 0 === Move === DMs created 105, segments created 24, maxWait 645579ms, bed compensation in use: none, height map offset 0.000, max steps late 1, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 1.00 no step interrupt scheduled Moves shaped first try 2392, on retry 6, too short 1623, wrong shape 2362, maybepossible 3 === DDARing 0 === Scheduled moves 8376, completed 8376, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 4], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === 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) 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Q0 segments left 0 Code queue 0 is empty === Filament sensors === check 10345540 clear 4725652 Extruder 0: pos 7.10, brightness 15, shutter 91, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === Network === Slowest loop: 203.61ms; 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.1beta6 MAC address 5c:cf:7f:2c:24:6b Module reset reason: Turned on by main processor, Vcc 3.38, flash size 2097152, free heap 42348 WiFi IP address 192.168.1.16 Signal strength -52dBm, channel 13, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
@dc42 Here is the output of M122 before the print. This print had IS turned on. I will submit another result after turning off IS.
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.3+mms (2024-03-13 13:10:20) running on Duet WiFi 1.0 or 1.01 Board ID: 08DAM-999TL-MQ4SD-6JTDL-3SS6N-968BX Used output buffers: 2 of 26 (26 max) === RTOS === Static ram: 23256 Dynamic ram: 77488 of which 0 recycled Never used RAM 8320, free system stack 114 words Tasks: NETWORK(1,ready,30.6%,193) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,0.0%,258) MAIN(1,running,60.1%,714) IDLE(0,ready,9.2%,29), total 100.0% Owned mutexes: === Platform === Last reset 00:13:31 ago, cause: software Last software reset at 2024-03-20 18:21, reason: StuckInSpinLoop, Gcodes spinning, available RAM 8552, slot 0 Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200025b4 Task MAIN Freestk 929 ok Stack: 0042c6eb 0045747c 61030000 3ef8490a 40a00400 4232877a 80000000 c33a2cf8 00000000 20000c98 00000001 00000001 00000028 20004c64 40090000 0042c96d 00000000 00000001 000c8f49 0042d0fb 00000000 447b221d 00000001 03ba77ff 004575b5 00000000 00000000 Error status: 0x04 Aux0 errors 0,0,0 MCU temperature: min 41.1, current 41.5, max 43.1 Supply voltage: min 24.1, current 24.3, 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/1212/1176, gc cycles 1 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2024-03-26 18:50:33 Cache data hit count 4294967295 Slowest loop: 51.48ms; fastest: 0.18ms 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 51.1ms, write time 2.7ms, max retries 0 === Move === DMs created 83, segments created 51, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 13465, completed 13465, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.1 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) 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 Daemon is idle in state(s) 0 0, running macro Autopause is idle in state(s) 0 Q0 segments left 0 Code queue 0 is empty === Network === Slowest loop: 21.11ms; 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.1beta6 MAC address 5c:cf:7f:2c:25:00 Module reset reason: Turned on by main processor, Vcc 3.40, flash size 2097152, free heap 43088 WiFi IP address 192.168.1.61 Signal strength -36dBm, channel 6, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0Here is the output after I cancelled the print.
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.3+mms (2024-03-13 13:10:20) running on Duet WiFi 1.0 or 1.01 Board ID: 08DAM-999TL-MQ4SD-6JTDL-3SS6N-968BX Used output buffers: 7 of 26 (26 max) === RTOS === Static ram: 23256 Dynamic ram: 77488 of which 0 recycled Never used RAM 8232, free system stack 114 words Tasks: NETWORK(2,nWait 6,29.8%,193) HEAT(3,nWait 5,0.1%,319) Move(4,nWait 5,1.4%,258) MAIN(1,running,60.9%,714) IDLE(0,ready,7.8%,29), total 100.0% Owned mutexes: === Platform === Last reset 00:23:40 ago, cause: software Last software reset at 2024-03-20 18:21, reason: StuckInSpinLoop, Gcodes spinning, available RAM 8552, slot 0 Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200025b4 Task MAIN Freestk 929 ok Stack: 0042c6eb 0045747c 61030000 3ef8490a 40a00400 4232877a 80000000 c33a2cf8 00000000 20000c98 00000001 00000001 00000028 20004c64 40090000 0042c96d 00000000 00000001 000c8f49 0042d0fb 00000000 447b221d 00000001 03ba77ff 004575b5 00000000 00000000 Error status: 0x04 Aux0 errors 0,0,0 MCU temperature: min 39.2, current 42.7, max 43.4 Supply voltage: min 23.4, current 24.3, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/620/584, gc cycles 3 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0 Driver 1: standstill, SG min 0 Driver 2: standstill, SG min 0 Driver 3: standstill, SG min 0 Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2024-03-26 19:00:42 Cache data hit count 4294967295 Slowest loop: 311.49ms; fastest: 0.09ms 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 50.1ms, write time 10.5ms, max retries 0 === Move === DMs created 84, segments created 51, maxWait 534671ms, bed compensation in use: none, height map offset 0.000, max steps late 1, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 1.00 no step interrupt scheduled Moves shaped first try 244, on retry 11, too short 236, wrong shape 11146, maybepossible 64 === DDARing 0 === Scheduled moves 13421, completed 13421, hiccups 0, stepErrors 0, LaErrors 0, Underruns [16, 0, 20], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.1 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) 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 Daemon is idle in state(s) 0 0, running macro Autopause is idle in state(s) 0 Q0 segments left 0 Code queue 0 is empty === Network === Slowest loop: 210.54ms; 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.1beta6 MAC address 5c:cf:7f:2c:25:00 Module reset reason: Turned on by main processor, Vcc 3.40, flash size 2097152, free heap 42812 WiFi IP address 192.168.1.61 Signal strength -50dBm, channel 6, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
BTW, I had run
M111 B4096before starting the print, but I did not get any debugging output. -
@balajiramani when I tried the 20x20x20 filled cube with IS disabled there was no debug output (although the y slope is still there).
-
Here is the output of
M122with IS off.M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.3+mms (2024-03-13 13:10:20) running on Duet WiFi 1.0 or 1.01 Board ID: 08DAM-999TL-MQ4SD-6JTDL-3SS6N-968BX Used output buffers: 3 of 26 (26 max) === RTOS === Static ram: 23256 Dynamic ram: 77488 of which 208 recycled Never used RAM 8024, free system stack 114 words Tasks: NETWORK(1,ready,30.2%,193) HEAT(3,nWait 5,0.1%,319) Move(4,nWait 5,1.0%,258) MAIN(1,running,60.4%,714) IDLE(0,ready,8.3%,29), total 100.0% Owned mutexes: === Platform === Last reset 00:37:42 ago, cause: software Last software reset at 2024-03-20 18:21, reason: StuckInSpinLoop, Gcodes spinning, available RAM 8552, slot 0 Software reset code 0x4083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f80f BFAR 0xe000ed38 SP 0x200025b4 Task MAIN Freestk 929 ok Stack: 0042c6eb 0045747c 61030000 3ef8490a 40a00400 4232877a 80000000 c33a2cf8 00000000 20000c98 00000001 00000001 00000028 20004c64 40090000 0042c96d 00000000 00000001 000c8f49 0042d0fb 00000000 447b221d 00000001 03ba77ff 004575b5 00000000 00000000 Error status: 0x04 Aux0 errors 0,0,0 MCU temperature: min 39.7, current 42.9, max 43.7 Supply voltage: min 23.4, current 24.3, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/1796/1760, gc cycles 4 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0 Driver 1: standstill, SG min 0 Driver 2: standstill, SG min 0 Driver 3: standstill, SG min 0 Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2024-03-26 19:14:44 Cache data hit count 4294967295 Slowest loop: 238.35ms; fastest: 0.09ms 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 53.1ms, write time 5.6ms, max retries 1 === Move === DMs created 84, segments created 51, maxWait 639154ms, bed compensation in use: none, height map offset 0.000, max steps late 1, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 1.00 no step interrupt scheduled Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0 === DDARing 0 === Scheduled moves 13388, completed 13388, hiccups 0, stepErrors 0, LaErrors 0, Underruns [21, 0, 46], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.1 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) 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 Daemon is idle in state(s) 0 0, running macro Autopause is idle in state(s) 0 Q0 segments left 0 Code queue 0 is empty === Network === Slowest loop: 211.70ms; 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.1beta6 MAC address 5c:cf:7f:2c:25:00 Module reset reason: Turned on by main processor, Vcc 3.40, flash size 2097152, free heap 43088 WiFi IP address 192.168.1.61 Signal strength -45dBm, channel 6, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
@Adrian52 I too have the same experience, where IS does not seem to matter.
-
@Adrian52 is your config.g file still the same as the one you posted on 23 Oct 2023 here https://forum.duet3d.com/post/325846 ?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Probably not exactly - this is my current config.g
; Communication and general M111 S0 ; Debug off M550 PKosselXL ; Machine name and Netbios name (can be anything you like) M551 Preprap ; Machine password (used for FTP) ;*** If you have more than one Duet on your network, they must all have different MAC addresses, so change the last digits ;M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address ;*** Wifi Networking M552 S1 ; Enable WiFi. Disabled for setup and testing. Enable once set up on your network. M555 P0 ; Set output to look like Reprap M575 P1 B57600 S1 ; Comms parameters for PanelDue G21 ; Work in millimetres G90 ; Send absolute coordinates... M83 ; ...but relative extruder moves ; Axis and motor configuration M584 X0 Y1 Z2 E3:4 ;explicitly assign drives M569 P0 S0 ; Drive 0 goes backwards - changed to backwards for robodigg clamps M569 P1 S0 ; Drive 1 goes backwards - " M569 P2 S0 ; Drive 2 goes backwards - " M569 P3 S0 ; Drive 3 goes backwards - changed for orbiter 1.5 M569 P4 S0 ; Drive 4 goes backwards - orbiter 2.0 M84 S120 ;set idle timeout to 120sec ;M574 X2 Y2 Z2 S1 ; set endstop configuration (all endstops at high end, active high) M574 X2 S1 P"xstop" M574 Y2 S1 P"ystop" M574 Z2 S1 P"zstop" ;*** The homed height is deliberately set too high in the following - you will adjust it during calibration M665 L360.25 R173.990 H297.084 B120.0 X0.538 Y0.525 Z0.000 M666 X1.493 Y-1.213 Z-0.280 A-1.03 B-0.66 ; put your endstop adjustments here, or let auto calibration find them M579 X1.005 Y1.012 Z1.00 ;correct x y z scaling M350 X16 Y16 Z16 I1 ; Set 16x microstepping with interpolation M350 E16:16 I1 ; Set exruder to 16x with interpolation M92 X200 Y200 Z200 ; Set axis steps/mm M906 X1400 Y1400 Z1400 I0.6 ; Set motor currents (mA) and increase idle current to 60% M906 E850:850 I10 ;current for orbiter M201 X5000 Y5000 Z5000 E5000:5000 ; Accelerations (mm/s^2) M203 X20000 Y20000 Z20000 E7200:7200 ; Maximum speeds (mm/min) M566 X900 Y900 Z900 E300 P1 ; Maximum instant speed changes mm/minute, switch on 2.03 jerk policy ; Thermistors and heaters M308 S0 P"bedtemp" A"Bed temp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B0 S1.00 ; disable bang-bang mode for the nozzle heater and set PWM limit M140 H0 ;bed heater is heater 0 M143 H0 S125 M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.060000e-8 A"Extruder temp" ; configure sensor 1 as thermister via e0temp M308 S2 P"e1temp" Y"thermistor" T100000 B4725 C7.060000e-8 A"Cold end temp" ; configure sensor 2 as thermister via e1temp ;M308 S1 P"spi.cs1" Y"rtdmax31865" A"Extruder temp" ; configure sensor 1 as thermocouple via CS pin spi.cs1 ;M308 S2 P"spi.cs2" Y"rtdmax31865" A"Test temp" ; configure sensor 2 M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M950 P2 C"e1heat" ; create output to switch lights M307 H1 B0 S1.00 ; disable bang-bang mode for the nozzle heater and set PWM limit M143 H1 S300 ; set temperature limit for heater 1 to 295C M570 H1 S60 ;cancel print 60min after extruder temp fault ; ****Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q2500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"!Fan2+^exp.pb6" Q25000 M106 P2 S0 H-1 C"Extra cool" ; Tools M563 P0 D0:1 H1 F0 ; 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 ; Tool definitions ;M563 P0 D0 H1 F0:2 ; Define tool 0 with fan 0, fan 2 linked ;M563 P0 D0 H1 F0 ; tool 0 with fan 0 only G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures M567 P0 E1.00:1.00 ; set mix ratio M309 p0 S0.006 ; set heater feed forward for tool 0 ;*** If you have a single-nozzle build, comment the next 2 lines ;M563 P1 D1 H2 ; Define tool 1 ;G10 P1 S0 R0 ; Set tool 1 operating and standby temperatures ;M92 E458 ; Set extruder steps per mm M92 E667:667 ; Set extruder steps per mm orbiter M572 D0:1 S0.032 ;pressure advance extruder 0 and 1 ;M572 D1 S0.02 ; pressure advance extruder 1 M207 S2.1 R0.0 F7200 Z0.05 ; firmware retraction setting ; Z probe and compensation definition M558 P8 C"zprobe.in+zprobe.mod" R0.4 F1000 H5 A2 S-1 ;Z probe smart effector M672 S105:20:235 ;set z probe sensitivity ;G31 P100 X0 Y0 Z-0.10 ;probe offset for old smart effector G31 P100 X0 Y0 Z-0.08 ;probe offset for new smart effector 0.27 for petg 0.18 for pla try 0.1 for direct drive ;laser filament monitor settings M591 D0 P5 C"connlcd.encb" R01:300 E10 L0.45 S1 A1 ;version for reprap3 ;M955 P0 C"spi.cs3+spi.cs4" I64 S5000 R10 ;accelerometer configuration ;*** If you are using axis compensation, put the figures in the following command M556 S100 X0.05 Y0 Z0 ; Axis compensation here M593 P"zvd" F27 L0.10 S0 ; Damp ringing at 27Hz M376 H0 ;taper mesh over 10mm M501 ;use override-config.g parameters M208 S1 Z-0.2 ; set minimum Z M912 P0 S-2 ;calibration mcu temperature reading G28 ;Home axes M42 P2 S1 ;lights on ;G29 S1 ;load height map and activate mesh compensation ;M290 S-0.1 ;current baby steps ; T0 ; select first hot end -
@Adrian52 thanks. Using that config.g and starting from your filled cube job file, I have produced a small test case that loses a step on the Z motor and identified the conditions that cause it. I expect to have a fix for it on Friday.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 thank you very much - looking forward to testing it
-
@Adrian52 it turns out that there is more than one cause of this issue. I found and fixed the first one, now I am working on the second.
-
@Adrian52 @balajiramani please try the new firmware at https://www.dropbox.com/scl/fo/6afk7iewlw1ycldb8dc4u/h?rlkey=21rm8jcz6aqy3gh523wkmxro7&dl=0. The main board binaries there report version 3.5.0-rc.3+8 and the expansion board binaries are 3.5.0-rc.3+6.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 the filled cube looks fine - thank you very much.
here is the m122, in case of interest. No hics or step errors05/04/2024, 17:32:04 m122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.3+8 (2024-04-05 15:37:41) running on Duet WiFi 1.0 or 1.01 Board ID: 08DAM-999TL-MQ4SD-6J9FD-3SJ6J-K593W Used output buffers: 3 of 26 (26 max) === RTOS === Static ram: 23256 Dynamic ram: 72916 of which 12 recycled Never used RAM 12032, free system stack 114 words Tasks: NETWORK(2,nWait 6,14.0%,193) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,1.2%,258) MAIN(1,running,84.7%,850) IDLE(0,ready,0.0%,29), total 100.0% Owned mutexes: === Platform === Last reset 00:43:32 ago, cause: software Last software reset at 2024-03-05 21:23, reason: User, Gcodes spinning, available RAM 11272, slot 1 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU temperature: min 27.3, current 28.5, max 35.2 Supply voltage: min 24.0, current 24.4, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/32/32, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0 Driver 1: standstill, SG min 0 Driver 2: standstill, SG min 0 Driver 3: standstill, SG min 0 Driver 4: standstill, SG min 0 Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2024-04-05 17:32:01 Cache data hit count 4294967295 Slowest loop: 213.37ms; fastest: 0.11ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 1.0ms, write time 0.0ms, max retries 0 === Move === DMs created 100, segments created 24, maxWait 672741ms, bed compensation in use: none, height map offset 0.000, max steps late 1, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 1.00 no step interrupt scheduled Moves shaped first try 2394, on retry 6, too short 1623, wrong shape 2362, maybepossible 3 === DDARing 0 === Scheduled moves 8376, completed 8376, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 4], CDDA state -1 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 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) 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Q0 segments left 0 Code queue 0 is empty === Filament sensors === check 4755950 clear 4423949 Extruder 0: pos 10.19, brightness 27, shutter 134, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === Network === Slowest loop: 206.77ms; 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.1beta6 MAC address 5c:cf:7f:2c:24:6b Module reset reason: Turned on by main processor, Vcc 3.38, flash size 2097152, free heap 42348 WiFi IP address 192.168.1.16 Signal strength -50dBm, channel 13, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
@dc42 I tried it now and it works fine. Thank you for getting dow to the root of the issue fixing it!
-
BTW, one thing that I noticed with the new firmware is that there seems to be random pauses while printing. Here is a video that shows that. The pause is between 11 and 13 seconds into the video.
Here is the output of M122 taken after one such pause:
M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.0-rc.3+8 (2024-04-05 15:37:41) running on Duet WiFi 1.0 or 1.01 Board ID: 08DAM-999TL-MQ4SD-6JTDL-3SS6N-968BX Used output buffers: 2 of 26 (23 max) === RTOS === Static ram: 23256 Dynamic ram: 73416 of which 20 recycled Never used RAM 12324, free system stack 110 words Tasks: NETWORK(1,ready,33.2%,220) HEAT(3,nWait 5,0.1%,313) Move(4,nWait 5,3.5%,258) MAIN(1,running,55.0%,745) IDLE(0,ready,8.3%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:31:47 ago, cause: power up Last software reset at 2024-04-07 11:33, reason: User, Gcodes spinning, available RAM 14388, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 MCU temperature: min 34.7, current 47.5, max 49.1 Supply voltage: min 23.4, current 24.2, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/4, heap memory allocated/used/recyclable 2048/1212/1088, gc cycles 1 Events: 0 queued, 0 completed Driver 0: ok, SG min 0 Driver 1: ok, SG min 0 Driver 2: ok, SG min 0 Driver 3: phase B may be disconnected, SG min 0 Driver 4: standstill, SG min n/a Driver 5: Driver 6: Driver 7: Driver 8: Driver 9: Driver 10: Driver 11: Date/time: 2024-04-07 16:00:29 Cache data hit count 4294967295 Slowest loop: 233.94ms; fastest: 0.13ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 7 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 53.6ms, write time 15.3ms, max retries 1 === Move === DMs created 83, segments created 53, maxWait 490265ms, bed compensation in use: none, height map offset 0.000, max steps late 1, min interval -24898, bad calcs 0, ebfmin 0.00, ebfmax 1.00 next step interrupt due in 64 ticks, disabled Moves shaped first try 826, on retry 580, too short 4644, wrong shape 93438, maybepossible 1202 === DDARing 0 === Scheduled moves 118046, completed 118006, hiccups 48, stepErrors 0, LaErrors 0, Underruns [116, 3, 184], CDDA state 3 === Heat === Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.1 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 doing "G1 X-21.782 Y13.17 E.00871" 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 Daemon is idle in state(s) 0 0, running macro Autopause is idle in state(s) 0 Q0 segments left 1 Code queue 0 is empty === Network === Slowest loop: 131.97ms; fastest: 0.00ms 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.1beta6 MAC address 5c:cf:7f:2c:25:00 Module reset reason: Turned on by main processor, Vcc 3.40, flash size 2097152, free heap 43088 WiFi IP address 192.168.1.61 Signal strength -45dBm, channel 6, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
@balajiramani maybe open another thread for that issue.
-
@balajiramani as @oliof says please create a new thread for that issue.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
-
undefined droftarts has marked this topic as solved
-
@dc42 any chance this is not just 3.5.0 and delta related?
We've one printer (Cartesian / IDEX) that's somewhat randomly (but mostly) also producing leaning prints.
For a long time we thought it is ClosedLoop or Hardware related, but running normal steppers etc. now.
Happens both with 3.4.6 and 3.5.1 and always in X-direction.Kind of sure it's not hardware related by know, but somewhat special setup by now due to all the tests we did.
Let me know if you need any information, or want me to move it to a new thread. Or maybe it's the same error not jet fixed for a different kinematic?
-
@benecito said in y slope with 3.5.0-rc1, not seen with 3.4.6:
want me to move it to a new thread.
probably would be a good idea to start a new thread. include as much info as you can.
