@dc42 a 1hr print completed for me too - thanks for the fix. Print quality looks very nice too.
Posts made by Adrian52
-
RE: RepRapFirmware 3.6.0-alpha.4+3 available for testing
-
RE: RepRapFirmware 3.6.0-alpha.4+3 available for testing
@dc42 I didnt check the exact time , but just under 40 min would be about right for me too.
-
RE: RepRapFirmware 3.6.0-alpha.4+3 available for testing
@balajiramani Hi - sorry for the delay
here is my bed.g. I have a 250mm dia round bed; Auto calibration routine for large delta printer M561 ; clear any bed transform ; If the printer hasn't been homed, home it ;if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed G28 ; Probe the bed and do auto calibration G1 X-70 Y-60 Z10 F6000 ; go to just above the first probe point while true if iterations = 5 abort "too many auto calibration attempts" G30 P0 X-70 Y-60 Z-99999 if result != 0 continue G30 P1 X-85 Y0 Z-99999 if result != 0 continue G30 P2 X-50 Y75 Z-99999 if result != 0 continue G30 P3 X0 Y85 Z-99999 if result != 0 continue G30 P4 X50 Y75 Z-99999 if result != 0 continue G30 P5 X85 Y0 Z-99999 if result != 0 continue G30 P6 X75 Y-50 Z-99999 if result != 0 continue G30 P7 X0 Y-85 Z-99999 if result != 0 continue G30 P8 X-40 Y-40 Z-99999 if result != 0 continue G30 P9 X-50 Y0 Z-99999 if result != 0 continue G30 P10 X-40 Y40 Z-99999 if result != 0 continue G30 P11 X0 Y50 Z-99999 if result != 0 continue G30 P12 X40 Y40.00 Z-99999 if result != 0 continue G30 P13 X50 Y0 Z-99999 if result != 0 continue G30 P14 X40 Y-40 Z-99999 if result != 0 continue G30 P15 X-4 Y-2 Z-99999 if result != 0 continue G30 P16 X4 Y-2 Z-99999 if result != 0 continue G30 P17 X0 Y4 Z-99999 S6 if result != 0 continue if move.calibration.final.deviation <= 0.03 break echo "Repeating calibration because deviation is too high (" ^ move.calibration.final.deviation ^ "mm)" ; end loop echo "Auto calibration successful, deviation", move.calibration.final.deviation ^ "mm" G1 X0 Y0 Z150 F5000 ; get the head out of the way M500 G28
-
RE: RepRapFirmware 3.6.0-alpha.4+3 available for testing
@balajiramani I run delta calibration using the smart effector probe without any obvious problem, with residual error usually under 0.02. I normally don't need to use mesh compensation.
-
RE: RepRapFirmware 3.6.0-alpha.4+3 available for testing
@dc42 When trying the new alpha4+3, I get "movement halted step timing error occurred (code 3) Please reset the controller"
Got same error with two different files. Duet2wifi standalone on a linear delta
M122 following error:m122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.6.0-alpha.4+3 (2024-08-28 10:03:28) running on Duet WiFi 1.0 or 1.01 Board ID: 08DAM-999TL-MQ4SD-6J9FD-3SJ6J-K593W Used output buffers: 3 of 26 (24 max) === RTOS === Static ram: 23360 Dynamic ram: 66712 of which 12 recycled Never used RAM 16112, free system stack 112 words Tasks: NETWORK(2,nWait 6,13.1%,222) HEAT(3,nWait 5,0.1%,328) Move(4,invalid,4.8%,266) MAIN(1,running,82.0%,832) IDLE(0,ready,0.0%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:38:48 ago, cause: power up Last software reset at 2024-08-24 14:15, reason: User, Gcodes spinning, available RAM 25120, slot 1 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 36.1, current 38.1, max 39.1 Supply voltage: min 24.1, 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/60/0, gc cycles 0 Events: 0 queued, 0 completed Date/time: 2024-08-28 21:43:15 Slowest loop: 213.94ms; fastest: 0.13ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 9 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 10.1ms, write time 0.0ms, max retries 0 === Move === Segments created 495, maxWait 54217ms, bed comp in use: none, height map offset 0.000, hiccups added 7 (0.25ms), max steps late 0, ebfmin 0.00, ebfmax 0.00 Pos req/act/dcf: 66607.00/66935/-0.71 68379.00/68333/0.81 68571.00/68351/0.46 no step interrupt scheduled 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: === DDARing 0 === Scheduled moves 242824, completed 242785, 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.3 Heater 1 is on, I-accum = 0.4 === 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 17 Code queue 0 is empty === Filament sensors === check 6729139 clear 1019682 Extruder 0: pos 4.41, brightness 27, shutter 117, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === Network === Slowest loop: 21.17ms; fastest: 0.07ms Responder states: HTTP(0) HTTP(1) HTTP(1) 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.1.0 MAC address 5c:cf:7f:2c:24:6b Module reset reason: Turned on by main processor, Vcc 3.38, flash size 4194304, free heap 41984 WiFi IP address 192.168.1.16 Signal strength -46dBm, channel 4, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 5 0 3 3 0 0 0 0 28/08/2024, 21:42:39 Error: Movement halted because a step timing error occurred (code 3). Please reset the controller. 28/08/2024, 21:08:45 M32 "0:/gcodes/OrcaCube_225.gcode" File 0:/gcodes/OrcaCube_225.gcode selected for printing
-
RE: y slope with 3.5.0-rc1, not seen with 3.4.6
@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
-
RE: y slope with 3.5.0-rc1, not seen with 3.4.6
@dc42 thank you very much - looking forward to testing it
-
RE: y slope with 3.5.0-rc1, not seen with 3.4.6
@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
-
RE: y slope with 3.5.0-rc1, not seen with 3.4.6
@balajiramani when I tried the 20x20x20 filled cube with IS disabled there was no debug output (although the y slope is still there).
-
RE: 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 printing
M122:
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
-
RE: y slope with 3.5.0-rc1, not seen with 3.4.6
@dc42 Here is the dbug output
24/03/2024, 10:22:00 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 221, measured min 87% avg 102% max 123% over 1958.4mm 24/03/2024, 10:03:08 Seg length diff -8.66e-7 at 5 S d=8.2207e-4 t=15.8 b=9.4952e+3 c=-3.6525e+8 a=-5.4756e-9 24/03/2024, 10:02:26 Seg length diff 9.13e-7 at 5 S d=8.5831e-4 t=16.5 b=9.5068e+3 c=-3.6552e+8 a=-5.4717e-9 24/03/2024, 10:02:22 Seg length diff 9.13e-7 at 5 S d=8.5831e-4 t=16.5 b=9.5068e+3 c=-3.6552e+8 a=-5.4717e-9 24/03/2024, 10:02:16 Seg length diff 8.82e-7 at 5 S d=8.5831e-4 t=16.5 b=9.5068e+3 c=-3.6553e+8 a=-5.4715e-9 24/03/2024, 10:02:06 Bad interval -676 dr=2, ns=119 DMZ: dir=B steps=119 next=119 rev=52 interval=11626 ssl=120 A=1.3211e+11 B=4.6209e+5 C=-2.3672e+7 dsf=2.7601e+1 tsf=424234.8 hmz0s=6.3767e+4 minusAaPlusBbTimesS=2.7592e+3 dSquaredMinusAsquaredMinusBsquared=4.0683e+9 drev=1.2807e+1 dda: 3 ts=673539940 DDA: start=[13.796242 -8.836784 0.485564] end=[-13.805079 -8.836784 0.400000] s=2.7601e+1 vec=[-0.999995 0.000000 -0.003100] ext=[0.032510 0.032510] a=1.2672e-9 d=1.2673e-9 reqv=7.4666e-5 startv=1.6000e-5 topv=7.4666e-5 endv=1.5992e-5 cks=424233 fp=26876 fl=155f S d=3.4144e-1 t=17361.1 b=-3.7880e+4 c=4.7350e+9 a=4.2239e-10 S d=5.9606e-1 t=17361.1 b=-1.8414e+4 c=1.5783e+9 a=1.2672e-9 S d=9.7800e-1 t=17361.1 b=-3.5775e+4 c=1.5783e+9 a=1.2672e-9 S d=1.2326e+0 t=17361.1 b=-1.5941e+5 c=4.7350e+9 a=4.2239e-10 S d=2.1306e+1 t=285345.9 c=1.3393e+4 S d=1.2326e+0 t=17361.1 b=1.7674e+5 c=-4.7343e+9 a=-4.2245e-10 S d=9.7795e-1 t=17361.1 b=5.3128e+4 c=-1.5781e+9 a=-1.2673e-9 S d=5.9596e-1 t=17361.1 b=3.5767e+4 c=-1.5781e+9 a=-1.2673e-9 S d=3.4131e-1 t=17361.1 b=5.5217e+4 c=-4.7343e+9 a=-4.2245e-10 24/03/2024, 09:58:40 M32 "0:/gcodes/30x20x20cube_filled.gcode" File 0:/gcodes/30x20x20cube_filled.gcode selected for printing
and the M122:
24/03/2024, 10:27:23 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: 16 of 26 (18 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.3%,193) HEAT(3,nWait 5,0.1%,328) Move(4,nWait 5,1.6%,242) MAIN(1,running,84.0%,841) IDLE(0,ready,0.1%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:37:14 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 17.8, current 27.1, max 35.1 Supply voltage: min 24.1, 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-03-24 10:27:19 Cache data hit count 4294967295 Slowest loop: 211.98ms; 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 1.0ms, write time 9.5ms, max retries 0 === Move === DMs created 105, segments created 24, maxWait 487694ms, bed compensation in use: none, height map offset 0.000, max steps late 1, min interval -676, bad calcs 0, ebfmin 0.00, ebfmax 1.00 no step interrupt scheduled Moves shaped first try 2635, on retry 98, too short 2405, wrong shape 2294, maybepossible 2 === DDARing 0 === Scheduled moves 9392, completed 9392, hiccups 1, stepErrors 0, LaErrors 0, Underruns [0, 0, 3], 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 5550781 clear 2098127 Extruder 0: pos -3.49, brightness 12, shutter 102, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === Network === Slowest loop: 206.54ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(1) HTTP(1) 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 39524 WiFi IP address 192.168.1.16 Signal strength -49dBm, channel 13, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 5 3 3 0 0 0 0 24/03/2024, 10:27:15 Finished printing file 0:/gcodes/30x20x20cube_filled.gcode, print time was 0h 28m
-
RE: y slope with 3.5.0-rc1, not seen with 3.4.6
@dc42 This is the debug output printing jig1.gcode with zvd enabled
23/03/2024, 12:19:29 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 23/03/2024, 12:19:28 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 23/03/2024, 12:16:34 M32 "0:/gcodes/jig1_225.gcode" File 0:/gcodes/jig1_225.gcode selected for printing 23/03/2024, 12:14:07 M111 B4096 23/03/2024, 12:12:19 M593 Input shaping 'zvd' at 27.0Hz damping factor 0.00, min. reduction 0.1, impulses 0.250 0.750 with durations (ms) 18.52 18.52
and the M122
23/03/2024, 12:42:28 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 (17 max) === RTOS === Static ram: 23256 Dynamic ram: 76852 of which 12 recycled Never used RAM 7536, free system stack 110 words Tasks: NETWORK(2,nWait 6,14.3%,193) HEAT(3,nWait 5,0.1%,307) Move(4,nWait 5,1.7%,242) MAIN(1,running,83.9%,850) IDLE(0,ready,0.1%,29), total 100.0% Owned mutexes: === Platform === Last reset 00:33:33 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: 0x00 Aux0 errors 0,0,0 MCU temperature: min 17.1, current 27.7, max 33.9 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/24/24, 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-23 12:42:26 Cache data hit count 4294967295 Slowest loop: 210.94ms; 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 3.5ms, write time 0.0ms, max retries 0 === Move === DMs created 105, segments created 29, maxWait 427239ms, 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 1888, on retry 165, too short 2675, wrong shape 6534, maybepossible 136 === DDARing 0 === Scheduled moves 14391, completed 14391, 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 4870041 clear 2112480 Extruder 0: pos 0.83, brightness 25, shutter 133, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === Network === Slowest loop: 205.68ms; 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:24:6b Module reset reason: Turned on by main processor, Vcc 3.38, flash size 2097152, free heap 43036 WiFi IP address 192.168.1.16 Signal strength -53dBm, channel 13, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 23/03/2024, 12:41:24 Finished printing file 0:/gcodes/jig1_225.gcode, print time was 0h 24m 23/03/2024, 12:36:11 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 81% avg 99% max 120% over 1188.1mm
-
RE: y slope with 3.5.0-rc1, not seen with 3.4.6
Just checked printing the same jig1 gcode file with IS disabled, and there is still some slope on the lower part - around 1mm offset at the base, compared with about 2mm with IS on zvd.
-
RE: y slope with 3.5.0-rc1, not seen with 3.4.6
@dc42 Here it is
jig1_225.gcode
I couldn't find the original gcode, so I resliced with the same conditions as the cube. I checked print, and amazingly it came out looking exactly like the blue ones in the early post, going vertical from the U cutout on the y+ face
-
RE: y slope with 3.5.0-rc1, not seen with 3.4.6
@dc42 here is a picture of the effect:
the left cuboid is sloped in the y+ direction (IS on), the right cuboid is vertical. The short sides (x-facing) of the centre cuboid are vertical . The print quality seems fine to me, apart from the lean.
-
RE: y slope with 3.5.0-rc1, not seen with 3.4.6
@dc42 I only used that gcode file - for me, it leans with IS on, but is vertical with IS off. The effect is not that obvious - just less than 1mm over the 20mm height.
-
RE: y slope with 3.5.0-rc1, not seen with 3.4.6
@dc42This is the gcode - it gives the slope with IS on (I used zvd) and no slope with IS "none".
30x20x20cube_filled.gcode -
RE: y slope with 3.5.0-rc1, not seen with 3.4.6
@dc42 No y slope with IS disabled
=== 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: 16 of 26 (26 max) === RTOS === Static ram: 23256 Dynamic ram: 72748 of which 12 recycled Never used RAM 11760, free system stack 120 words Tasks: NETWORK(2,nWait 6,13.9%,193) HEAT(3,nWait 5,0.1%,307) Move(4,nWait 5,0.9%,258) MAIN(1,running,85.2%,836) IDLE(0,ready,0.0%,29), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 01:43:15 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: 0x00 Aux0 errors 0,0,0 MCU temperature: min 27.1, current 28.2, max 34.6 Supply voltage: min 24.1, 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/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-20 19:44:21 Cache data hit count 4294967295 Slowest loop: 221.83ms; 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 3.5ms, write time 0.0ms, max retries 0 === Move === DMs created 105, segments created 24, maxWait 2378135ms, 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 9392, completed 9392, 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 10744745 clear 11675643 Extruder 0: pos -0.80, brightness 17, shutter 91, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === Network === Slowest loop: 212.40ms; fastest: 0.07ms Responder states: HTTP(0) HTTP(1) HTTP(1) 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 36260 WiFi IP address 192.168.1.16 Signal strength -54dBm, channel 13, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 5 0 3 3 0 0 0 0
-
RE: y slope with 3.5.0-rc1, not seen with 3.4.6
@dc42 I am getting a smooth y slope with no hics or step errors printing a 30x20x20 cuboid (filled)
=== 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: 2 of 26 (26 max) === RTOS === Static ram: 23256 Dynamic ram: 72748 of which 12 recycled Never used RAM 11760, free system stack 120 words Tasks: NETWORK(1,ready,14.3%,193) HEAT(3,nWait 5,0.1%,319) Move(4,nWait 5,1.7%,258) MAIN(1,running,84.0%,841) IDLE(0,ready,0.0%,29), total 100.0% Owned mutexes: === Platform === Last reset 00:37:17 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: 0x00 Aux0 errors 0,0,0 MCU temperature: min 20.8, current 27.5, max 34.6 Supply voltage: min 24.1, 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-03-20 18:38:24 Cache data hit count 4294967295 Slowest loop: 226.78ms; 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 1.6ms, write time 4.9ms, max retries 0 === Move === DMs created 105, segments created 24, maxWait 487529ms, bed compensation in use: none, height map offset 0.000, max steps late 1, min interval -676, bad calcs 0, ebfmin 0.00, ebfmax 1.00 no step interrupt scheduled Moves shaped first try 2635, on retry 98, too short 2405, wrong shape 2294, maybepossible 2 === DDARing 0 === Scheduled moves 9392, completed 9392, 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 5549352 clear 2119357 Extruder 0: pos -9.93, brightness 12, shutter 78, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0 === Network === Slowest loop: 207.88ms; fastest: 0.07ms Responder states: HTTP(0) HTTP(1) 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 42972 WiFi IP address 192.168.1.16 Signal strength -57dBm, channel 13, mode 802.11n, reconnections 0 Clock register 00002002 Socket states: 5 0 3 0 0 0 0 0
-
RE: 3.5.0rc1: Input shaping causes layer shifts!?
I have now seen y slope with the latest rc3+4, and have replied to the thread referred to above. My cube was absolutely fine apart from the slope.