Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    y slope with 3.5.0-rc1, not seen with 3.4.6

    Scheduled Pinned Locked Moved Solved
    Beta Firmware
    10
    92
    4.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Adrian52undefined
      Adrian52 @dc42
      last edited by

      @dc42This is the gcode - it gives the slope with IS on (I used zvd) and no slope with IS "none".
      30x20x20cube_filled.gcode

      dc42undefined 2 Replies Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators @Adrian52
        last edited by

        @Adrian52 thanks. My delta also has 200 steps/mm so I'll try it on that.

        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

        1 Reply Last reply Reply Quote 0
        • dc42undefined
          dc42 administrators @Adrian52
          last edited by dc42

          @Adrian52 I increased the max speeds and acceleration on my delta to the values in your config.g and set the input shaping to be the same. The print came out OK.

          2024-03-22 14.59.40.jpg

          If you send me the GCode file for the other print that had a lean, I'll try that one.

          PS - I've just noticed an anomaly in the 'min interval' value in your M122 report after the print that leaned. That may be relevant to this issue. I will investigate it.

          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

          Adrian52undefined 2 Replies Last reply Reply Quote 0
          • Adrian52undefined
            Adrian52 @dc42
            last edited by

            @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.

            dc42undefined 1 Reply Last reply Reply Quote 0
            • dc42undefined
              dc42 administrators @Adrian52
              last edited by

              @Adrian52 i meant the one in this post https://forum.duet3d.com/post/325473.

              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

              Adrian52undefined 1 Reply Last reply Reply Quote 0
              • Adrian52undefined
                Adrian52 @dc42
                last edited by

                @dc42 here is a picture of the effect:
                alt text

                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.

                1 Reply Last reply Reply Quote 0
                • Adrian52undefined
                  Adrian52 @dc42
                  last edited by

                  @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
                  alt text

                  1 Reply Last reply Reply Quote 0
                  • Adrian52undefined
                    Adrian52
                    last edited by

                    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.

                    dc42undefined 1 Reply Last reply Reply Quote 0
                    • dc42undefined
                      dc42 administrators @Adrian52
                      last edited by

                      @Adrian52 please re-run some of those prints that give you a slope, but before the print run this command:

                      M112 B4096

                      This will likely result in debug output on the DWC console during the print. Please post that output here. If you don't see any debug output, please take a M122 report when the print finishes, or when you are sure it is leaning if you don't want t complete the print.

                      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

                      gloomyandyundefined Adrian52undefined 2 Replies Last reply Reply Quote 0
                      • gloomyandyundefined
                        gloomyandy @dc42
                        last edited by

                        @dc42 Did you mean M111 B4096 rather than M112 B4096?

                        1 Reply Last reply Reply Quote 0
                        • Adrian52undefined
                          Adrian52 @dc42
                          last edited by

                          @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
                          dc42undefined 1 Reply Last reply Reply Quote 0
                          • dc42undefined
                            dc42 administrators @Adrian52
                            last edited by

                            @Adrian52 thanks. Please do the same test with the filled cube print.

                            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

                            Adrian52undefined 2 Replies Last reply Reply Quote 0
                            • Adrian52undefined
                              Adrian52 @dc42
                              last edited by

                              @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
                              1 Reply Last reply Reply Quote 0
                              • Adrian52undefined
                                Adrian52 @dc42
                                last edited by

                                @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
                                1 Reply Last reply Reply Quote 0
                                • balajiramaniundefined
                                  balajiramani @dc42
                                  last edited by

                                  @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 0

                                  Here 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
                                  1 Reply Last reply Reply Quote 0
                                  • balajiramaniundefined
                                    balajiramani
                                    last edited by

                                    BTW, I had run M111 B4096 before starting the print, but I did not get any debugging output.

                                    Adrian52undefined 1 Reply Last reply Reply Quote 0
                                    • Adrian52undefined
                                      Adrian52 @balajiramani
                                      last edited by

                                      @balajiramani when I tried the 20x20x20 filled cube with IS disabled there was no debug output (although the y slope is still there).

                                      balajiramaniundefined dc42undefined 2 Replies Last reply Reply Quote 0
                                      • balajiramaniundefined
                                        balajiramani
                                        last edited by

                                        Here is the output of M122 with 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
                                        1 Reply Last reply Reply Quote 0
                                        • balajiramaniundefined
                                          balajiramani @Adrian52
                                          last edited by

                                          @Adrian52 I too have the same experience, where IS does not seem to matter.

                                          1 Reply Last reply Reply Quote 0
                                          • dc42undefined
                                            dc42 administrators @Adrian52
                                            last edited by

                                            @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

                                            Adrian52undefined 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Unless otherwise noted, all forum content is licensed under CC-BY-SA