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

    Reboots/resets randomly - RRF 3.5.0-b4

    Scheduled Pinned Locked Moved
    Beta Firmware
    12
    112
    6.4k
    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.
    • dc42undefined
      dc42 administrators @Exerqtor
      last edited by

      @Exerqtor PS - please run M122 P500 S1 after reset (you can put this in config.g temporarily). This will reduce performance somewhat, but will provide more accurate reset data in the M122 report.

      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

      Exerqtorundefined 1 Reply Last reply Reply Quote 0
      • Exerqtorundefined
        Exerqtor @dc42
        last edited by

        @dc42 said in Extruder stops extruding (again) & reboots randomly - RRF 3.5b3+:

        @Exerqtor please post a few more M122 reports for the main board after this issue happens. There does appear to be some commonality but I haven't identified the exact issue yet.

        The crash happens in the WiFi module interface code. Do you have just a single PC running DWC as wifi client, or are there multiple clients?

        Ok, good to see it's something happening that's traceable!

        Uhm DWC is mainly running on one pc/unit at a time. Either i'm at the office while printing, then I use the PC to check in on the printer. If i'm not in the office i use my phone (the pc might or might not be on/in hibernation). So for sake of argument lets say two units at a time?

        Are you able to run RRF 3.4.5 to see whether the resets happen with that version?

        I've deployed to many 3.5 dependant scripts at this point to make that swap tbh 😮‍💨

        @dc42 said in Extruder stops extruding (again) & reboots randomly - RRF 3.5b3+:

        @Exerqtor PS - please run M122 P500 S1 after reset (you can put this in config.g temporarily). This will reduce performance somewhat, but will provide more accurate reset data in the M122 report.

        Ok, i added it as the last line in config.g and rebooted the machine before going to bed yesterday, so i'll check after work and report back.

        Exerqtorundefined 1 Reply Last reply Reply Quote 0
        • Exerqtorundefined
          Exerqtor @Exerqtor
          last edited by Exerqtor

          @dc42

          The printer haven't restartet (yet), but i just tried another print (one object) and it stopped extruding again!
          Now it stopped on more or less the first print line on the first layer, and started agian in the second layer (then i canceled the print).

          M122's from when it's not extruding:

          M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.3+ (2023-05-09 10:59:17) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: FAP55-Q967A-G65J0-401GL-0S02Z-RF9TL
Used output buffers: 4 of 40 (40 max)
=== RTOS ===
Static ram: 101720
Dynamic ram: 130896 of which 228 recycled
Never used RAM 4860, free system stack 134 words
Tasks: NETWORK(ready,224.7%,179) HEAT(nWait,0.7%,327) Move(nWait,0.4%,270) CanReceiv(nWait,1.2%,772) CanSender(nWait,0.0%,327) CanClock(delaying,0.2%,341) TMC(nWait,30.8%,74) MAIN(running,62.8%,335) IDLE(ready,10.7%,29) AIN(delaying,21.2%,266), total 352.6%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 16:32:12 ago, cause: software
Last software reset at 2023-06-01 00:47, reason: User, Gcodes spinning, available RAM 13792, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 59533190, completed 59533190, timed out 0, errs 0
MCU temperature: min 33.9, current 45.6, max 46.0
Supply voltage: min 23.1, current 23.5, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 198/33, heap memory allocated/used/recyclable 2048/1260/772, gc cycles 2264
Events: 0 queued, 0 completed
Driver 0: ok, SG min 0, read errors 0, write errors 1, ifcnt 39, reads 38057, writes 51, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min 0, read errors 0, write errors 1, ifcnt 39, reads 38056, writes 51, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 167, reads 38078, writes 29, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 168, reads 38078, writes 29, timeouts 0, DMA errors 0, CC errors 0
Driver 4: ok, SG min 0, read errors 0, write errors 1, ifcnt 167, reads 38079, writes 29, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 65, reads 38098, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 65, reads 38097, writes 10, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2023-06-01 17:19:31
Cache data hit count 4294967295
Slowest loop: 239.37ms; fastest: 0.08ms
=== Storage ===
Free file entries: 16
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 9.0ms, write time 62.2ms, max retries 0
=== Move ===
DMs created 83, segments created 29, maxWait 58897889ms, bed compensation in use: mesh, comp offset 0.000
next step interrupt due in 45 ticks, enabled
=== DDARing 0 ===
Scheduled moves 364, completed 358, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X181.195 Y162.316 E1.347" 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
SBC is idle in state(s) 0
Daemon is doing "G4 S1                                                                        " in state(s) 0 0, running macro
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is doing "M0" in state(s) 0, sync state 1
Queue2 is idle in state(s) 0
Q0 segments left 1, axes/extruders owned 0x0000807
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 538684, received 1190889, lost 0, boc 0
Longest wait 3ms for reply type 6053, peak Tx sync delay 275, free buffers 18 (min 14), ts 297665/297664/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 216.97ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
= WiFi =
Network state is active
Module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
Firmware version 2.1beta4
MAC address bc:ff:4d:e6:b1:62
Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 43000
WiFi IP address 192.168.10.50
Signal strength -50dBm, channel 1, mode 802.11n, reconnections 0
Clock register 00002001
Socket states: 0 0 0 0 0 0 0 0

          M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.5.0-beta.3+ (2023-05-09 13:40:30)
Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 4232, free system stack 38 words
Tasks: Move(nWait,0.1%,93) HEAT(nWait,13.2%,57) CanAsync(nWait,0.0%,53) CanRecv(nWait,0.3%,74) CanClock(nWait,0.5%,67) ACCEL(nWait,0.0%,53) TMC(nWait,80.4%,57) MAIN(running,128.9%,346) IDLE(ready,0.0%,27) AIN(delaying,128.5%,142), total 351.9%
Last reset 16:32:19 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 568.8 steps/mm,standstill, SG min 0, read errors 0, write errors 1, ifcnt 67, reads 15903, writes 15, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 229311
Moves scheduled 2515, completed 2515, in progress 0, hiccups 133, step errors 0, maxPrep 1012, maxOverdue 4036, maxInc 2308, mcErrs 0, gcmErrs 0
Peak sync jitter -4/9, peak Rx sync delay 245, resyncs 0/0, no timer interrupt scheduled
VIN voltage: min 23.3, current 24.4, max 24.7
MCU temperature: min 40.7C, current 68.1C, max 69.8C
Last sensors broadcast 0x00000012 found 2 202 ticks ago, 0 ordering errs, loop time 1
CAN messages queued 1191020, send timeouts 0, received 538754, lost 0, free buffers 37, min 36, error reg 110000
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 513, adv 35873/74646
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0

          Debug log (with the M122 info scrubbed:

          2023-06-01 17:17:13 [warn] Started printing file 0:/gcodes/print_job_0.16mm_ABS_0.4n_1h23m.gcode
2023-06-01 17:17:13 [debug] File 0:/gcodes/print_job_0.16mm_ABS_0.4n_1h23m.gcode selected for printing
2023-06-01 17:17:16 [info] M291: - [no title] - Print started, preheating.
2023-06-01 17:17:17 [info] G10 P0 S150 R150                                                               
2023-06-01 17:17:17 [debug] T:140.5 /150.0 T0:140.5 /150.0 B:110.2 /110.0
2023-06-01 17:17:18 [debug] T:139.9 /150.0 T0:139.9 /150.0 B:110.2 /110.0
2023-06-01 17:17:19 [debug] T:140.8 /150.0 T0:140.8 /150.0 B:110.2 /110.0
2023-06-01 17:17:20 [debug] T:143.6 /150.0 T0:143.6 /150.0 B:110.1 /110.0
2023-06-01 17:17:21 [debug] T:147.3 /150.0 T0:147.3 /150.0 B:110.1 /110.0
2023-06-01 17:17:23 [warn] HTTP client 192.168.10.100 login succeeded (session key 0)
2023-06-01 17:17:27 [warn] HTTP client 192.168.10.226 login succeeded (session key 0)
2023-06-01 17:17:36 [info] G10 P0 S150.0
2023-06-01 17:17:36 [info] G10 P0 S150.0
2023-06-01 17:17:36 [info] M291: - [no title] - Pre-print mesh probing enabled, probing new bed mesh!
2023-06-01 17:17:36 [debug] Default grid: X10.0:340.0, Y10.0:340.0, Number of points: X12 Y12, 144 points
2023-06-01 17:17:36 [debug] Adaptive grid: X160.918:189.082, Y147.261:202.739, Number of points: X3 Y3, 9 points
2023-06-01 17:17:38 [info] G10 P0 S150.0
2023-06-01 17:17:38 [debug] Z probe trigger height set to -1.361 mm
2023-06-01 17:17:39 [info] M291: - Mesh Probing - Probing now! Please wait...
2023-06-01 17:17:51 [info] G10 P0 S150.0
2023-06-01 17:17:52 [warn] 9 points probed, min error -0.017, max error 0.005, mean -0.007, deviation 0.006
Height map saved to file 0:/sys/heightmap.csv
2023-06-01 17:17:52 [debug] 9 points probed, min error -0.017, max error 0.005, mean -0.007, deviation 0.006
Height map saved to file 0:/sys/heightmap.csv
2023-06-01 17:17:52 [debug] Height map saved to file 0:/sys/adaptive_heightmap.csv
2023-06-01 17:17:54 [info] M291: - Mesh Probing - Done
2023-06-01 17:17:54 [info] G10 P0 S150.0
2023-06-01 17:17:55 [info] G10 P{global.initial_extruder} R{global.hotend_temp} S{global.hotend_temp}     
2023-06-01 17:17:55 [debug] T:150.4 /255.0 T0:150.4 /255.0 B:110.0 /110.0
2023-06-01 17:17:56 [debug] T:150.5 /255.0 T0:150.5 /255.0 B:110.0 /110.0
2023-06-01 17:17:57 [debug] T:152.6 /255.0 T0:152.6 /255.0 B:110.0 /110.0
2023-06-01 17:17:58 [debug] T:156.5 /255.0 T0:156.5 /255.0 B:110.0 /110.0
2023-06-01 17:17:59 [debug] T:161.4 /255.0 T0:161.4 /255.0 B:110.0 /110.0
2023-06-01 17:18:00 [debug] T:167.0 /255.0 T0:167.0 /255.0 B:110.0 /110.0
2023-06-01 17:18:01 [debug] T:172.5 /255.0 T0:172.5 /255.0 B:110.0 /110.0
2023-06-01 17:18:02 [debug] T:178.2 /255.0 T0:178.2 /255.0 B:110.0 /110.0
2023-06-01 17:18:03 [debug] T:183.6 /255.0 T0:183.6 /255.0 B:110.0 /110.0
2023-06-01 17:18:04 [debug] T:189.0 /255.0 T0:189.0 /255.0 B:110.0 /110.0
2023-06-01 17:18:05 [debug] T:194.0 /255.0 T0:194.0 /255.0 B:110.0 /110.0
2023-06-01 17:18:06 [debug] T:199.3 /255.0 T0:199.3 /255.0 B:110.0 /110.0
2023-06-01 17:18:07 [debug] T:204.5 /255.0 T0:204.5 /255.0 B:110.0 /110.0
2023-06-01 17:18:08 [debug] T:209.7 /255.0 T0:209.7 /255.0 B:110.0 /110.0
2023-06-01 17:18:09 [debug] T:214.3 /255.0 T0:214.3 /255.0 B:110.0 /110.0
2023-06-01 17:18:10 [debug] T:219.3 /255.0 T0:219.3 /255.0 B:110.0 /110.0
2023-06-01 17:18:11 [debug] T:224.1 /255.0 T0:224.1 /255.0 B:110.0 /110.0
2023-06-01 17:18:12 [debug] T:228.9 /255.0 T0:228.9 /255.0 B:110.0 /110.0
2023-06-01 17:18:13 [debug] T:233.7 /255.0 T0:233.7 /255.0 B:110.0 /110.0
2023-06-01 17:18:14 [debug] T:238.0 /255.0 T0:238.0 /255.0 B:110.0 /110.0
2023-06-01 17:18:15 [debug] T:242.3 /255.0 T0:242.3 /255.0 B:110.0 /110.0
2023-06-01 17:18:16 [debug] T:246.4 /255.0 T0:246.4 /255.0 B:110.0 /110.0
2023-06-01 17:18:17 [debug] T:249.8 /255.0 T0:249.8 /255.0 B:110.0 /110.0
2023-06-01 17:18:18 [debug] T:252.4 /255.0 T0:252.4 /255.0 B:110.0 /110.0
2023-06-01 17:18:19 [info] M291: - [no title] - Purge location, X min: 135.918; Y min: 137.261; Purge move speed: 4.802495; Prepurge speed: 4.158004
2023-06-01 17:18:30 [debug] ABS filament loaded & config applied
2023-06-01 17:18:30 [debug] ABS filament loaded & config applied
2023-06-01 17:18:30 [debug] Maximum printing acceleration 5000.0, maximum travel acceleration 7000.0 mm/sec^2
2023-06-01 17:22:42 [warn] Resume state saved
2023-06-01 17:22:46 [warn] Printing paused at X179.6 Y161.4 Z1.4
2023-06-01 17:22:46 [debug] Printing paused at X179.6 Y161.4 Z1.4
2023-06-01 17:22:57 [debug] Done printing file
2023-06-01 17:22:57 [debug] Done printing file
2023-06-01 17:22:57 [warn] Cancelled printing file 0:/gcodes/print_job_0.16mm_ABS_0.4n_1h23m.gcode, print time was 0h 5m
2023-06-01 17:23:03 [info] G10 P0 R0 S0                                                                   
2023-06-01 17:23:03 [debug] ABS filament unloaded & pressure advance disabled
2023-06-01 17:23:03 [debug] ABS filament unloaded & pressure advance disabled
          dc42undefined 1 Reply Last reply Reply Quote 0
          • dc42undefined
            dc42 administrators @Exerqtor
            last edited by

            @Exerqtor the issue with extrusion on tool boards stopping (actually reversing) is a known issue in 3.5beta3.

            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

            Exerqtorundefined 1 Reply Last reply Reply Quote 0
            • Exerqtorundefined
              Exerqtor @dc42
              last edited by

              @dc42 said in Extruder stops extruding (again) & reboots randomly - RRF 3.5b3+:

              @Exerqtor the issue with extrusion on tool boards stopping (actually reversing) is a known issue in 3.5beta3.

              Yeah i knew it was in 3.5b3, but i thought the patch in b3+ sorted it out 😬

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

                @Exerqtor OK, I didn't spot that you were running the patched version. There are still some extrusion issues on tool boards in that version.

                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

                Exerqtorundefined 1 Reply Last reply Reply Quote 0
                • Exerqtorundefined
                  Exerqtor @dc42
                  last edited by

                  @dc42 said in Extruder stops extruding (again) & reboots randomly - RRF 3.5b3+:

                  @Exerqtor OK, I didn't spot that you were running the patched version. There are still some extrusion issues on tool boards in that version.

                  Ok, if you have any newer binaries thats supposed to fix said issues i would be more than happy to try them if we put it like that 😆

                  1 Reply Last reply Reply Quote 0
                  • Exerqtorundefined
                    Exerqtor @dc42
                    last edited by

                    @dc42 said in Extruder stops extruding (again) & reboots randomly - RRF 3.5b3+:

                    @Exerqtor PS - please run M122 P500 S1 after reset (you can put this in config.g temporarily). This will reduce performance somewhat, but will provide more accurate reset data in the M122 report.

                    Ok so i checked in on the debuglog now and the printer apparently restarted a couple times last evening (just been standing there collecting dust).

                    2023-06-02 20:55:23 [warn] HTTP client 192.168.10.100 disconnected
power up + 00:00:03 [info] Event logging started at level debug
power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-beta.3+ (2023-05-09 10:59:17)
power up + 00:00:03 [debug] Done!
power up + 00:00:03 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running.
power up + 00:00:04 [warn] WiFi module started
power up + 00:00:07 [warn] WiFi module is connected to access point RV32-IOT2G, IP address 192.168.10.50
power up + 00:00:08 [warn] HTTP client 192.168.10.100 login succeeded (session key 0)
2023-06-02 21:19:35 [warn] Date and time set at power up + 00:00:08
power up + 00:00:03 [info] Event logging started at level debug
power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-beta.3+ (2023-05-09 10:59:17)
power up + 00:00:03 [debug] Done!
power up + 00:00:03 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running.
power up + 00:00:04 [warn] WiFi module started
power up + 00:00:07 [warn] WiFi module is connected to access point RV32-IOT2G, IP address 192.168.10.50
power up + 00:00:08 [warn] HTTP client 192.168.10.100 login succeeded (session key 0)
2023-06-02 21:24:36 [warn] Date and time set at power up + 00:00:08
power up + 00:00:03 [info] Event logging started at level debug
power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-beta.3+ (2023-05-09 10:59:17)
power up + 00:00:03 [debug] Done!
power up + 00:00:03 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running.
power up + 00:00:04 [warn] WiFi module started
power up + 00:00:07 [warn] WiFi module is connected to access point RV32-IOT2G, IP address 192.168.10.50
power up + 00:00:08 [warn] HTTP client 192.168.10.100 login succeeded (session key 0)
2023-06-03 05:24:05 [warn] Date and time set at power up + 00:00:08

                    Here is the M122:

                    M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.3+ (2023-05-09 10:59:17) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: FAP55-Q967A-G65J0-401GL-0S02Z-RF9TL
Used output buffers: 15 of 40 (30 max)
=== RTOS ===
Static ram: 101720
Dynamic ram: 123664 of which 0 recycled
Never used RAM 13816, free system stack 184 words
Tasks: NETWORK(nWait,155.6%,219) HEAT(nWait,0.2%,329) Move(nWait,0.0%,358) CanReceiv(nWait,0.4%,772) CanSender(nWait,0.0%,336) CanClock(delaying,0.1%,341) TMC(nWait,9.8%,108) MAIN(running,107.8%,444) IDLE(ready,3.3%,29) AIN(delaying,6.8%,266), total 284.1%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 07:13:36 ago, cause: software
Last software reset at 2023-06-03 05:23, reason: HardFault imprec, Gcodes spinning, available RAM 13792, slot 1
Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00000400 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x20011b98 Task NETW Freestk 482 ok
Stack: 2002be78 00000000 200014e8 0000019f ffffffff 0002f6d1 00034064 810f0000 0002f6bd 00000000 00000000 00000000 20031a6c 00000800 20035760 2002be60 20018250 2002bd05 20018250 2001e438 0002f857 00000000 00000000 00000000 20011c48 00000014 b5dd9f97
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 26016866, completed 26016866, timed out 0, errs 0
MCU temperature: min 33.5, current 36.3, max 37.6
Supply voltage: min 23.7, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/28, heap memory allocated/used/recyclable 2048/468/84, gc cycles 974
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 2, read errors 0, write errors 1, ifcnt 83, reads 5830, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 2, read errors 0, write errors 1, ifcnt 83, reads 5830, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 211, reads 5830, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 2, read errors 0, write errors 1, ifcnt 212, reads 5830, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 211, reads 5831, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 98, reads 5832, writes 10, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6f
Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 98, reads 5833, writes 10, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2023-06-03 12:37:44
Cache data hit count 4294967295
Slowest loop: 22.63ms; fastest: 0.12ms
=== Storage ===
Free file entries: 18
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 4.2ms, write time 2.1ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
no step interrupt scheduled
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, 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
SBC is idle in state(s) 0
Daemon is doing "G4 S1                                                                        " in state(s) 0 0, running macro
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000803
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 234159, received 520381, lost 0, boc 0
Longest wait 3ms for reply type 6053, peak Tx sync delay 275, free buffers 18 (min 17), ts 130084/130083/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 19.72ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Network state is active
Module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
Firmware version 2.1beta4
MAC address bc:ff:4d:e6:b1:62
Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 43000
WiFi IP address 192.168.10.50
Signal strength -54dBm, channel 1, mode 802.11n, reconnections 0
Clock register 00002001
Socket states: 0 0 0 0 0 0 0 0
                    dc42undefined 1 Reply Last reply Reply Quote 0
                    • dc42undefined
                      dc42 administrators @Exerqtor
                      last edited by

                      @Exerqtor thanks. I made a mistake: the command needed in config.g is M122 P500 S0 not S1. Please make that change and send me the next M122 main board report after that. You can check that the setting is correct by sending M122 P500 without the S parameter - it should report "Write buffer is disabled".

                      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

                      Exerqtorundefined 2 Replies Last reply Reply Quote 0
                      • Exerqtorundefined
                        Exerqtor @dc42
                        last edited by

                        @dc42
                        Aha, cool changed it to S0 now and checked, now it's disabled ✌

                        1 Reply Last reply Reply Quote 0
                        • Exerqtorundefined
                          Exerqtor @dc42
                          last edited by

                          @dc42
                          NOW i think "we" got it!

                          2023-06-03 13:59:24 [debug] Write buffer is disabled
power up + 00:00:03 [info] Event logging started at level debug
power up + 00:00:03 [info] Running: Duet 3 Mini5plus WiFi: 3.5.0-beta.3+ (2023-05-09 10:59:17)
power up + 00:00:03 [debug] Done!
power up + 00:00:03 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running.
power up + 00:00:04 [warn] WiFi module started
power up + 00:00:07 [warn] WiFi module is connected to access point RV32-IOT2G, IP address 192.168.10.50
power up + 00:00:07 [warn] HTTP client 192.168.10.100 login succeeded (session key 0)
2023-06-03 15:52:38 [warn] Date and time set at power up + 00:00:07

                          M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-beta.3+ (2023-05-09 10:59:17) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: FAP55-Q967A-G65J0-401GL-0S02Z-RF9TL
Used output buffers: 13 of 40 (28 max)
=== RTOS ===
Static ram: 101720
Dynamic ram: 123664 of which 0 recycled
Never used RAM 13816, free system stack 184 words
Tasks: NETWORK(nWait,68.6%,217) HEAT(nWait,0.1%,327) Move(nWait,0.0%,358) CanReceiv(nWait,0.2%,772) CanSender(nWait,0.0%,336) CanClock(delaying,0.0%,341) TMC(delaying,4.4%,108) MAIN(running,22.0%,444) IDLE(ready,1.5%,29) AIN(delaying,3.1%,266), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 02:09:59 ago, cause: software
Last software reset at 2023-06-03 15:52, reason: HardFault bfarValid precise, Platform spinning, available RAM 13816, slot 2
Software reset code 0x4060 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x0000001c SP 0x20011b98 Task NETW Freestk 482 ok
Stack: 2002be78 20030218 200014e8 00000000 20032c37 0002f6d1 0002f5e4 610f0000 0002f6bd 00000000 00000000 00000000 20030224 00000800 20035760 2002be60 20018250 2002bd05 20018250 2001e438 0002f857 00000000 00000000 00000000 20011c48 00000014 b5dd9f97
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 7800185, completed 7800184, timed out 0, errs 0
MCU temperature: min 35.7, current 36.9, max 40.4
Supply voltage: min 23.7, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/28, heap memory allocated/used/recyclable 2048/1876/1492, gc cycles 291
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 2, read errors 0, write errors 1, ifcnt 97, reads 53695, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 2, read errors 0, write errors 1, ifcnt 97, reads 53695, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 225, reads 53695, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 2, read errors 0, write errors 1, ifcnt 226, reads 53695, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 225, reads 53695, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 109, reads 53698, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 109, reads 53698, writes 10, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2023-06-03 18:02:30
Cache data hit count 4294967295
Slowest loop: 21.27ms; fastest: 0.12ms
=== Storage ===
Free file entries: 18
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 4.2ms, write time 2.1ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
no step interrupt scheduled
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Movement locks held by null, 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0 0, running macro
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000803
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 70207, received 156041, lost 0, boc 0
Longest wait 3ms for reply type 6053, peak Tx sync delay 275, free buffers 18 (min 17), ts 39000/38999/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 20.23ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Network state is active
Module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
Firmware version 2.1beta4
MAC address bc:ff:4d:e6:b1:62
Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 42288
WiFi IP address 192.168.10.50
Signal strength -50dBm, channel 1, mode 802.11n, reconnections 0
Clock register 00002001
Socket states: 0 0 0 0 0 0 0 0
                          dc42undefined 1 Reply Last reply Reply Quote 0
                          • dc42undefined
                            dc42 administrators @Exerqtor
                            last edited by

                            @Exerqtor thanks again. Please try the Mini5+ RRF file at https://www.dropbox.com/sh/in0t2j68ic66oa8/AADv_6WzRy07H6MhBOrkDt23a?dl=0. Leave the M122 command in config.g, and post the main board M122 main board if it resets again.

                            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

                            Exerqtorundefined 1 Reply Last reply Reply Quote 0
                            • Exerqtorundefined
                              Exerqtor @dc42
                              last edited by

                              @dc42
                              Will do, just installed the new binaries. This is just meant to remedy the restart issue right? Not the reversing extruder?

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

                                @Exerqtor this may not remedy the resetting issue, but should remedy any extrusion issues.

                                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

                                Exerqtorundefined 1 Reply Last reply Reply Quote 0
                                • Exerqtorundefined
                                  Exerqtor @dc42
                                  last edited by

                                  @dc42
                                  Oh thats promising 😁

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

                                    @Exerqtor I just remembered you are using a tool board, so I've now put the latest tool board firmware build in the same place.

                                    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

                                    Exerqtorundefined 1 Reply Last reply Reply Quote 1
                                    • Exerqtorundefined
                                      Exerqtor @dc42
                                      last edited by

                                      @dc42
                                      Happy to say i'm able to melt some plastic for the first time in almost two weeks now with that new build! 🙂

                                      Looks like it fixed the extrusion issues!

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

                                        @Exerqtor thanks, let me know ASAP if you get another main board reboot (and provide the M122 report) because I didn't really get to the bottom of that one.

                                        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

                                        Exerqtorundefined 2 Replies Last reply Reply Quote 0
                                        • Exerqtorundefined
                                          Exerqtor @dc42
                                          last edited by Exerqtor

                                          @dc42

                                          Yeah I will shout out as soon as I see a reset in the debuglog!

                                          Not any extrusion issues, but the print finishes off without completing the print for some reason. It's got status : "Cancelling" with 100% progress. And the printer is somewhat locked up in that state until i manually press Cancel in the status tab of DWC or PD (even though it's ran stop.g.

                                          This is the last part of the print that just "finished":

                                          G1 X176.576 Y189.748 E.00789
G1 X176.726 Y190.157 E.01028
G1 X176.791 Y190.611 E.01082
G1 X176.764 Y190.87 E.00614
G1 X176.969 Y191.069 F12000
; stop printing object print_job.stl id:0 copy 0
G10 ; retract

;TYPE:Custom
set global.line_type = "Custom"
; Filament-specific end G-code START
;
; Filament specific end G-code: END
; End G-code: START
M0
; End G-code: END
M73 P100 R0
; filament used [mm] = 2401.91
; filament used [cm3] = 5.78
; filament used [g] = 6.01
; filament cost = 1.68
; total filament used [g] = 6.01
; total filament cost = 1.68
; estimated printing time (normal mode) = 1h 23m 7s
; estimated first layer printing time (normal mode) = 2m 51s

; prusaslicer_config = begin
; autoemit_temperature_commands = 0
; avoid_crossing_curled_overhangs = 0
; avoid_crossing_perimeters = 0
; avoid_crossing_perimeters_max_detour = 0

                                          And the debuglog:

                                          2023-06-04 21:42:51 [debug] Done printing file
2023-06-04 21:42:51 [warn] Finished printing file 0:/gcodes/print_job_0.16mm_ABS_0.4n_1h23m.gcode, print time was 1h 12m
2023-06-04 21:42:56 [info] G10 P0 R0 S0                                                                   
2023-06-04 21:42:56 [debug] ABS filament unloaded & pressure advance disabled
2023-06-04 21:42:56 [debug] ABS filament unloaded & pressure advance disabled
                                          jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                                          • jay_s_ukundefined
                                            jay_s_uk @Exerqtor
                                            last edited by

                                            @Exerqtor that appears to be if M0 is used at all then a print gets stuck. Try having stop.g but not using M0 to call it

                                            Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

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