Unsolved Duet 3 mini5+ nightly restarts 3.5.2

[droftarts]

@Chriss @ProteanReverie Thanks for your continued reports.

@Chriss said in Duet 3 mini5+ nightly restarts:

I think that I will go back to a older version. It is a bit frustrating to loose a print after a print.

That's fair enough. Which is the last version that works correctly for you? I have bumped this thread to @dc42. Unfortunately your Hardfaults are 'imprecise', so there's not much to go on to track down this fault.

To make Hardfault 'precise', send M122 P500 S0 at startup to disable the write buffer. Disabling the write buffer reduces performance, but can help when debugging if the processor resets and the M122 reset data indicates that the cause was an imprecise exception. Disabling the write buffer will usually make the exception precise in future. Which makes it more likely that the cause can be tracked down.

Ian

[Chriss]

@droftarts

I guess that it was the very last RC before 3.5.1 which worked as far as I can tell. What I can do is keeping the printer up for one or two days to disable the write buffer if that helps.

My observation so far is that this problem pops up at least one per 24h. But I have to admit that I do not think that it is related to timing directly. The current print stop after ruffly 4 hours and 115layers. The print before this print finished, hat was a other part so I can not compare it 1:1. But the print before that was the same one and that stopped at ruffly 95% at ruffly 70layers. And the printer did not performed a reset for some hours.

Just to point that out: I did a reset to the board before I started the last print, I had the hope that the board will last long enough to finish the print.

I understand that it is hard for you to find the issue when you can not reproduce it. I can offer two things here:
1: I have a Mini5+ here at my desk, this has nothing connected, just for config development etc. I can flash 3.5.1 to it and upload the current config. Just to verify that it is not a hardware fault.
2: I can hand you over my entire config and you can test with it. We may come up that it is a strange race condition with the config I use. (And you can make some fun out of my poor config, that could be entertaining for you.)

Let me know if you want me to do one of these, I will restart the board now and disable the write buffer in the meantime.

Edit: Or do you think that it is worth to try 3.5.2rc1?

Cheers, Chriss

[droftarts]

@Chriss I think any of those tests are worthwhile, and might narrow down what’s causing it. So yes, please run 3.5.1 a couple more days on your production machine if possible, and on the bench test board, and please zip up your config and macros (or whatever is needed at boot time) tell me the firmware and hardware versions you’re using (let’s stick with 3.5.1 for now, as I don’t think there’s any direct fix in 3.5.2-rc1), and share them with me, and I’ll run the bench test too.

Ian

[Chriss]

@droftarts Good... So I will prepare my bench board than. Is there a way to share the config directly to you? I'm not sure whether I can PM you or not.

[Chriss]

@droftarts

Here a reboot again:

=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.1 (2024-04-19 14:41:25) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: V9NWJ-R296U-D65J0-40KM6-4113Z-HM83B
Used output buffers: 2 of 40 (40 max)
=== RTOS ===
Static ram: 103232
Dynamic ram: 122360 of which 0 recycled
Never used RAM 12968, free system stack 182 words
Tasks: NETWORK(1,ready,15.4%,216) HEAT(3,nWait 6,0.0%,326) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.0%,797) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,1.4%,102) MAIN(1,running,82.2%,665) IDLE(0,ready,0.0%,30) AIN(4,delaying,0.9%,256), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:28:35 ago, cause: software
Last software reset at 2024-06-06 19:14, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 12480, slot 2
Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00489803 BFAR 0x0000001c SP 0x20011ff0 Task NETW Freestk 483 ok
Stack: 2002c5e0 20031f98 200014e8 00000000 2003312d 0002ff99 0002feac 610f0000 0002ff85 00000000 00000000 00000000 20031fa4 00000800 20035c98 2002c5c8 200187fc 2002c41e 200187fc 2001e9f8 0003011f 00000000 00000000 00000000 200120a0 00000014 b5ddcef1
Error status: 0x04
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 1715656, completed 1715654, timed out 0, errs 0
MCU temperature: min 31.5, current 31.9, max 34.4
Supply voltage: min 24.3, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/11, heap memory allocated/used/recyclable 2048/1680/1508, gc cycles 4
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 2, read errors 0, write errors 1, ifcnt 160, reads 24832, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 52, read errors 0, write errors 1, ifcnt 77, reads 24829, writes 16, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 48, read errors 0, write errors 1, ifcnt 76, reads 24829, writes 16, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 87, reads 24835, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 161, reads 24832, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 2, read errors 0, write errors 1, ifcnt 162, reads 24832, writes 13, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 160, reads 24832, writes 13, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2024-06-06 19:43:04
Cache data hit count 3232259166
Slowest loop: 18.31ms; fastest: 0.17ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 6.5ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, 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 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
=== 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
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 15455, received 34346, lost 0, errs 1, boc 0
Longest wait 2ms for reply type 6013, peak Tx sync delay 267, free buffers 26 (min 25), ts 8577/8576/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 11.27ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(2)
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 f0:08:d1:02:e6:75
Module reset reason: Power up, Vcc 3.38, flash size 2097152, free heap 37352
WiFi IP address 192.168.1.69
Signal strength -64dBm, channel 1, mode 802.11n, reconnections 0
Clock register 00002001
Socket states: 0 3 0 0 0 0 0 0

[Chriss]

@droftarts The bench board is running now some trouble with the upgrade of the wifi module. I can not home the axes, obviously, so I have to check the board manually from time to time and will paste the output of M112 if that board will reboot too.

Cheers, Chriss

[droftarts]

@Chriss you can send G92 X0 Y0 Z0 to set the axes as homed, then visually you’ll know from looking at DWC if it has reset.

Ian

[Chriss]

@droftarts Thanks... you are a walking G-Code dictionary...

Edit: One more comment: The bench board does not have toolboard connected. I will attach one if the problem will not pop up in the next 48 hours.

[Chriss]

@droftarts
The board in the printer seems to be stable now after almost 24h since the last reset. (According to M122). I have the feeling that the problem occurs more often when the printer is printing. I will leave it now how it is and wait for the next reset. Nest test will be a print without filament to get a better understanding whether it happens sooner if the printer is working or not. Let me know if you think that this does not make sense from your point of view.

I can replace the board in the printer with my bench board if we see that the board on the bench is stable. If we agree that this makes sense. And let me know if you want me to parcel the board to you guys.

I have two more printers with a mini5+ in similar setups, one with 2 toolboards, one without one. None of them have 3.5.1, I can update one of them and test with them too if we think that this will bring us forward.

Cheers, Chriss

[Chriss]

Hi @droftarts
Update: Both boards did not reboot after 90 and 80 hours of uptime.
I replaced the SD card od my bench board today to get rid od some strange problems with the the DWC (saving of files failed).

The real printer will get a print job now without any filament to understand whether the printer failed more often when it is printing.

Cheers, Chriss

[droftarts]

@Chriss I've had your config running on mine all weekend with axes homed, and it hasn't skipped a beat either. Can't run a print, it'll break my machine! I'm going to revert to my regular config.g, and with your results, I'm going to assume it doesn't happen when idle.

Ian

[Chriss]

@droftarts

Yes and no Ian, I saw the issue when the printer was not printing over night. And I saw that issue more than than once in 48 hours, all without printing. That is the reason for my confusion that it did not happen in the last 90 hours. And we should not forget that my printer and ProteanReveries printer has a other "board" conencted via CAN but my bench board not.

Anyway, I used SuperSlicer to generate new g-code with an object which is about 155mm high, that should produce the error. The only change is that I lowered the temperatures a lot and have no filament in the extruder. I do not want to waist more plastic.

Let's hope that we see the problem again. The bench board will lay here for some more days with the fresh SD card, so the counter is at 0h for now. I will keep you updated.

Cheers, Chriss

[droftarts]

@Chriss I have a 1LC CAN board on the Mini 5+ I was testing on.

Ian

[Chriss]

@droftarts
It is mega strange, remember that I spoke about the 2nd failed print which made me thinking about going back to a older release? I used this SLT today again and it completed successfully toady. I restarted the print with the same gcode. The uptime of the printer is 126h now.
OK, the bed is off and the hotend is at 80°C, but this should not make any difference. Electrostatic discharge came in my mind but that should not be the problem because I did see the incident when the printer was not moving at all (over night)

I'm a bit helpless to be honest.

@ProteanReverie : Did you see the problem again in the last 5-6 days?

Cheers, Chriss

[Chriss]

@droftarts I'm constantly printing the same since 2-3 days and had no reboot since the last planed reboot. :?
I think that I will do more tests during the weekend, this time with filament. Maybe somehow related to the heaters....

Cheers, Chriss

[ProteanReverie]

I had not seen any restarts since the last time I reported on June 3rd, until last night. I did briefly power down the board earlier this week to move some things around, so it was not permanent uptime but close. Here is my latest data.

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.1 (2024-04-19 14:41:25) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 65LYX-8Q6KL-K65J0-409N0-NP02Z-ZFK3T
Used output buffers: 1 of 40 (26 max)
=== RTOS ===
Static ram: 103232
Dynamic ram: 119916 of which 24 recycled
Never used RAM 15388, free system stack 143 words
Tasks: NETWORK(1,ready,526.0%,218) HEAT(3,nWait 6,0.4%,372) Move(4,nWait 6,0.1%,355) CanReceiv(6,nWait 1,0.6%,808) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.3%,348) TMC(4,nWait 6,31.4%,102) MAIN(1,running,127.6%,677) IDLE(0,ready,0.3%,30) AIN(4,delaying,33.0%,260), total 719.6%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 09:47:57 ago, cause: software
Last software reset at 2024-06-14 00:45, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 15164, slot 1
Software reset code 0x0063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x00000004 SP 0x20011ff0 Task NETW Freestk 483 ok
Stack: 00000160 00000002 200014e8 0000015f ffffffff 000a07ef 0002ff8e 810f0000 0002ff85 00000000 00000000 00000000 200305e4 00000800 2002c5c8 2002c5c8 00000001 2002c41e 200187fc 2001e9f8 0003011f 00000000 00000000 00000000 200120a0 00000014 00000000
Error status: 0x00
MCU revision 3, ADC conversions started 35277450, completed 35277448, timed out 0, errs 0
MCU temperature: min 38.5, current 40.8, max 41.0
Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/12/12, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 21, reads 21659, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 21, reads 21659, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 21, reads 21658, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 21, reads 21658, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 21, reads 21658, writes 10, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6c
Driver 5: not present
Driver 6: not present
Date/time: 2024-06-14 10:33:11
Cache data hit count 4294967295
Slowest loop: 10.17ms; fastest: 0.16ms
=== Storage ===
Free file entries: 19
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.2ms, write time 2.6ms, max retries 0
=== Move ===
DMs created 83, segments created 0, 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 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 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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
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 0x0000000
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 176386, received 282222, lost 0, errs 1, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 318, free buffers 26 (min 26), ts 176386/176385/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 10.13ms; 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 ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1.0
MAC address e8:68:e7:e1:4e:d0
Module reset reason: Power up, Vcc 3.39, flash size 2097152, free heap 42764
WiFi IP address 10.1.10.46
Signal strength -59dBm, channel 1, mode 802.11n, reconnections 0
Clock register 00002001
Socket states: 0 0 0 0 0 0 0 0

Log file snippet around the time of the issue. Starts at the end of an M122 I ran yesterday morning, ends at the start of the M122 that is part of this post.

2024-06-13 09:41:40 [debug] Socket states:
2024-06-13 09:41:40 [debug]  0
2024-06-13 09:41:40 [debug]  0
2024-06-13 09:41:40 [debug]  0
2024-06-13 09:41:40 [debug]  0
2024-06-13 09:41:40 [debug]  0
2024-06-13 09:41:40 [debug]  0
2024-06-13 09:41:40 [debug]  0
2024-06-13 09:41:40 [debug]  0
2024-06-13 09:41:40 [debug] ok
power up + 00:00:00 [info] Event logging started at level debug
power up + 00:00:00 [info] Running: Duet 3 Mini5plus WiFi: 3.5.1 (2024-04-19 14:41:25)
power up + 00:00:00 [debug] Done!
power up + 00:00:00 [debug] RepRapFirmware for Duet 3 Mini 5+ is up and running.
power up + 00:00:00 [warn] WiFi module started
power up + 00:00:08 [warn] WiFi module is connected to access point SD3D-24, IP address 10.1.10.46
power up + 00:00:08 [warn] HTTP client 10.1.10.9 login succeeded (session key 1488020678)
2024-06-14 00:45:23 [warn] Date and time set at power up + 00:00:08
2024-06-14 10:32:57 [warn] HTTP client 10.1.10.9 disconnected
2024-06-14 10:33:01 [warn] HTTP client 10.1.10.9 login succeeded (session key 4151032817)
2024-06-14 10:33:11 [debug] === Diagnostics ===

[Aleksander Cane]

Hello!

I am experiencing the same problem with my Duet 3 Mini 5+ Wi-Fi board. After weeks of unsuccessful prints, I see on the forum that I am not the only one with the same issue.

I have two printers with Duet 3 Mini 5+ boards, and on Friday I started a two-day print on both printers. The older board completed the print without any problems. The second one, however, reset itself three times, and this morning I restarted it, expecting it to happen again. At least, I hope so, as I can then provide you with some data or log files from the second board.

If you need any information from board 2 or both boards to compare them, please let me know.

Thank you, Alex

[droftarts]

@Aleksander-Cane please post what version of RRF you’re using on both boards. Send M122 and post the response for each board, which will also show the reason for the last restart.

Were they both running the same Gcode? Do they have toolboards or any other non-standard extras? Please post config.g too.

Ian

[Aleksander Cane]

@droftarts

Hi Ian,

I am using the boards for 3D printers in standalone mode and they are not connected to any non-standard boards. Below, I have provided the requested information for both boards.
The machines were not running the same Gcode. However, I have never encountered this problem with Duet Printer 1, while I am continuously experiencing it with Duet Printer 2.
If it can be helpful, several times after the board (Duet Printer 2) restarted, the layer cooling fan remained on, the motors were disabled, and one of the three Z-axis drivers was not working when I requested the Z-axis homing. To restart them, I had to reboot the printer.

If you need any additional information/actions, please let me know.

Duet Printer 1

M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.6 (2023-07-21 14:09:13) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: R5GU7-D296U-D65J0-40KMJ-L903Z-7T0FN
Used output buffers: 1 of 40 (28 max)
=== RTOS ===
Static ram: 103712
Dynamic ram: 110476 of which 36 recycled
Never used RAM 27488, free system stack 192 words
Tasks: NETWORK(notifyWait,57.7%,250) HEAT(notifyWait,0.1%,340) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,941) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.1%,342) TMC(notifyWait,4.8%,115) MAIN(running,33.9%,425) IDLE(ready,0.0%,30) AIN(delaying,3.4%,263), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 07:02:37 ago, cause: software
Last software reset at 2024-06-17 08:06, reason: User, GCodes spinning, available RAM 23240, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 25357202, completed 25357201, timed out 0, errs 0
Step timer max interval 1487
MCU temperature: min 32.5, current 33.2, max 34.7
Supply voltage: min 24.2, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 2, read errors 0, write errors 0, ifcnt 40, reads 44553, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 44, reads 44553, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 44, reads 44553, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 46, reads 44552, writes 0, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6f
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 46, reads 44553, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 37, reads 44553, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 29, reads 44553, writes 0, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2024-06-17 15:08:57
Cache data hit count 4294967295
Slowest loop: 6.44ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
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 ===
Segments left: 0
Movement lock 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0 sensor: no data received
=== CAN ===
Messages queued 205540, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 114189/0/0
Tx timeouts 0,0,114189,0,0,91351 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 100.72ms; fastest: 0.06ms
Responder states: HTTP(0) 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, notready 0, noresp 2
WiFi firmware version 1.26
WiFi MAC address f0:08:d1:03:80:e0
WiFi Vcc 3.44, reset reason Power up
WiFi flash size 2097152, free heap 25208
WiFi IP address 172.16.1.10
WiFi signal strength -40dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

Config.g

; General preferences
G90                                     ; send absolute coordinates...
M83                                     ; ...but relative extruder moves
M550 P"RatRig_1"                         ; set printer name
M669 K1                                 ; CoreXY
G21                                     ; Set Units to Millimeters

; Configurazione della connessione Wi-Fi
M587 S"******" P"******"     ; Salva il nome e la password della rete Wi-Fi
M552 S1                                    ; Abilita la connessione Wi-Fi
M586 P0 S1                              ; enable HTTP
M586 P1 S0                              ; disable FTP
M586 P2 S0                              ; disable Telnet

; Drives
M569 P0.0 S1                            ; physical drive 0.0 goes forwards
M569 P0.1 S1                            ; physical drive 0.1 goes forwards
M569 P0.2 S1                            ; physical drive 0.2 goes forwards
M569 P0.3 S1                            ; physical drive 0.3 goes forwards
M569 P0.4 S1                            ; physical drive 0.4 goes forwards
M569 P0.5 S1                            ; physical drive 0.5 goes forwards
M584 X0.4 Y0.3 Z0.0:0.1:0.2 E0.5        ; set drive mapping
M350 X16 Y16 Z16 E16 I1                 ; configure microstepping with interpolation

M92 X80.00 Y80.00 Z800.00               ; set steps per mm
M906 X1600 Y1600 Z1600 I30              ; set motor currents (mA) and motor idle factor in per cent -- safe for Duet 3 mini 5+
M84 S30                                 ; Set idle timeout

; M566 X400.00 Y400.00 Z6.00 E120.00 P1          ; set maximum instantaneous speed changes (mm/min)
; M203 X10800.00 Y10800.00 Z1000.00 E5000.00     ; set maximum speeds (mm/min)
; M201 X3000.00 Y3000.00 Z100.00 E3600.00        ; set accelerations (mm/s^2)

M566 X800.00 Y800.00 Z12.00 E240.00 P1          ; set maximum instantaneous speed changes (mm/min)
M203 X24000.00 Y24000.00 Z3000.00 E15000.00     ; set maximum speeds (mm/min)
M201 X9000.00 Y9000.00 Z300.00 E6000.00        ; set accelerations (mm/s^2)

; Axis Limits
M208 X0 Y0 Z0 S1                               ; set axis minima
M208 X475 Y500 Z500 S0                         ; set axis maxima

; Endstops
M574 X1 S1 P"io3.in"                           ; configure active high endstops
M574 Y2 S1 P"io1.in"                           ; configure active high endstops

M671 X-4.5:150:304.5 Y-4.52:305:-4.52 S5       ; define positions of Z leadscrews or bed levelling screws
M557 X20:280 Y20:280 P5                        ; define 5x5 mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Bed"    ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 Q11                                 ; create bed heater output on out5 and map it to sensor 0, lower switching frequency to 11Hz
M307 H0 B0 S3.00                                       ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                                ; map heated bed to heater 0
M143 H0 S110                                           ; set temperature limit for heater 0 to 110C



;; Run Bed PID Tune!! Below is an example for a 300x300 bed
;; M307 H0 A303.1 C356.7 D1.4 S1.00 V24.0 B0

; Fans
;M950 F0 C"out4" Q500                   ; create fan 0 on pin out4 and set its frequency
;M106 P0 C"Layer Fan" S0 H-1            ; set fan 0 name and value. Thermostatic control is turned off

; 4-wire PWM fan and tacho
M950 F0 C"!out4+out4.tach"              ; Definisce la ventola 3 con controllo PWM su io4.out e tachimetro su io4.in
M106 P0 C"Layer Fan" S0              ; set fan 1 name and value. Thermostatic control turned on for Hotend

M950 F1 C"out3" Q500                   ; create fan 1 on pin out3 and set its frequency
M106 P1 C"Hotend Fan" S0 H1 T45        ; set fan 1 name and value. Thermostatic control turned on for Hotend

M950 F2 C"out6" Q500                   ; create fan 2 on pin out5 and set its frequency
M106 P2 C"Electronics Fan" S1 H-1         ; set fan 2 name and value. Thermostatic control turned off


; Tools
M563 P0 D0 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

M950 H1 C"out1" T1         ; create nozzle heater output on out2 and map it to sensor 1
M307 H1 B0 S1.00           ; disable bang-bang mode for heater and set PWM limit
M143 H1 S300               ; set the maximum temperature in C for heater

; EVA 2 / BMG / E3D V6

M92 E400         ; set extruder steps per mm, 0.9 angle/step (LGX BONDTECH)
M906 E600         ; set extruder motor current (mA) and idle factor in per cent

M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.060000e-8 A"Hotend"  

;; Run Heater PID Tune!! 
M307 H1 R2.796 K1.398:0.000 D8.59 E1.35 S1.00 B0 V24.2

M570 H1 P30 T30 ; Imposta un tempo di tolleranza di 30 secondi (P30) e un tempo di monitoraggio di 30 minuti (T30) per Heater 1

; Z-Probe
;; Inductive Probe
; M558 P5 C"!io3.in" H5 F400 T5000       ; set Z probe type to unmodulated and the dive height + speeds
; G31 P500 X-30 Y-15 Z0.20               ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed

;; BLTouch
 M950 S0 C"io2.out"                     ; Create a servo pin on io2
 M558 P9 C"io2.in" H5 F240 T10800 A5    ; set Z probe type to unmodulated and the dive height + speeds
 G31 P25 X-28.00 Y-13.00 Z3.8           ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed

; Select default tool
T0

; Pressure Advance
 M572 D0 S0.08

; Panel Due 7i
 M575 P1 B57600 S1                      ; Avvia communicazione seriale

; Sensore fillamento
;M591 D0.5 P7 C"io5.in" S1 F30:200      ; Dichiara pulse generating sensore di filamento
M591 D0.5 P7 L6.5 E20 C"io5.in" S0 R1:99999   ;   

[Aleksander Cane]

@droftarts

Duet Printer 2

M122

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.0 (2022-03-15 18:59:15) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: D3XWJ-AN6KL-K65J0-409NL-JPW1Z-ZGHMG
Used output buffers: 9 of 40 (40 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 110780 of which 24 recycled
Never used RAM 23336, free system stack 118 words
Tasks: NETWORK(ready,96.3%,202) HEAT(notifyWait,0.2%,338) Move(notifyWait,15.6%,267) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,356) CanClock(delaying,0.1%,337) TMC(notifyWait,9.3%,71) MAIN(running,120.7%,428) IDLE(ready,0.1%,29) AIN(delaying,6.3%,264), total 248.6%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 07:25:59 ago, cause: power up
Last software reset at 2024-06-16 10:56, reason: User, GCodes spinning, available RAM 27008, slot 0
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 26760958, completed 26760958, timed out 0, errs 0
Step timer max interval 912
MCU temperature: min 34.2, current 39.5, max 41.2
Supply voltage: min 23.6, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/26/0, gc cycles 0
Events: 1 queued, 1 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 7577, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 7576, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 7576, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 7575, writes 11, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x6a
Driver 4: ok, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 7577, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 5: ok, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 7576, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 7578, writes 9, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2024-06-17 15:21:50
Cache data hit count 4294967295
Slowest loop: 60.25ms; fastest: 0.09ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 2.1ms, write time 7.8ms, max retries 0
=== Move ===
DMs created 83, segments created 43, maxWait 1393453ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 662178, completed 662138, hiccups 0, stepErrors 0, LaErrors 0, Underruns [136, 0, 0], CDDA state 3
=== AuxDDARing ===
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.0
Heater 1 is on, I-accum = 0.7
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X362.183 Y193.699 E1554.25171" 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
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0: pos 80.86, errs: frame 33 parity 0 ovrun 0 pol 0 ovdue 0
=== CAN ===
Messages queued 240831, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 133796/0/0
Tx timeouts 0,0,133795,0,0,107034 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 71.89ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address e8:68:e7:e1:50:99
WiFi Vcc 3.38, reset reason Power up
WiFi flash size 2097152, free heap 25592
WiFi IP address 172.16.1.11
WiFi signal strength -49dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

config.g

; General preferences
G90                                     ; send absolute coordinates...
M83                                     ; ...but relative extruder moves
M550 P"RatRig_2"                         ; set printer name
M669 K1                                 ; CoreXY
G21                                     ; Set Units to Millimeters

; Configurazione della connessione Wi-Fi
M587 S"*****" P"******"     ; Salva il nome e la password della rete Wi-Fi
M552 S1                                 ; Abilita la connessione Wi-Fi
M586 P0 S1                              ; enable HTTP
M586 P1 S0                              ; enable FTP
M586 P2 S0                              ; enable Telnet

; Drives
M569 P0.0 S0                            ; physical drive 0.0 goes forwards
M569 P0.1 S0                            ; physical drive 0.1 goes forwards
M569 P0.2 S0                            ; physical drive 0.2 goes forwards
M569 P0.3 S1                            ; physical drive 0.3 goes forwards
M569 P0.4 S1                            ; physical drive 0.4 goes forwards
M569 P0.5 S1                            ; physical drive 0.5 goes forwards
M584 X0.4 Y0.3 Z0.0:0.1:0.2 E0.5        ; set drive mapping
M350 X16 Y16 Z16 E16 I1                 ; configure microstepping with interpolation

M92 X80.00 Y80.00 Z800.00               ; set steps per mm
M906 X1600 Y1600 Z1600 I30              ; set motor currents (mA) and motor idle factor in per cent -- safe for Duet 3 mini 5+
M84 S30                                 ; Set idle timeout

; M566 X400.00 Y400.00 Z6.00 E120.00 P1          ; set maximum instantaneous speed changes (mm/min)
; M203 X10800.00 Y10800.00 Z1000.00 E5000.00     ; set maximum speeds (mm/min)
; M201 X3000.00 Y3000.00 Z100.00 E3600.00        ; set accelerations (mm/s^2)

M566 X800.00 Y800.00 Z12.00 E240.00 P1          ; set maximum instantaneous speed changes (mm/min)
M203 X24000.00 Y24000.00 Z3000.00 E15000.00     ; set maximum speeds (mm/min)
M201 X9000.00 Y9000.00 Z300.00 E6000.00        ; set accelerations (mm/s^2)


; Axis Limits
M208 X0 Y0 Z0 S1                               ; set axis minima
M208 X500 Y500 Z500 S0                         ; set axis maxima

; Endstops
M574 X1 S1 P"io3.in"                           ; configure active high endstops
M574 Y2 S1 P"io1.in"                           ; configure active high endstops

M671 X-4.5:150:304.5 Y-4.52:305:-4.52 S5       ; define positions of Z leadscrews or bed levelling screws
M557 X20:280 Y20:280 P5                        ; define 5x5 mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Bed"    ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 Q11                                 ; create bed heater output on out5 and map it to sensor 0, lower switching frequency to 11Hz
M307 H0 B0 S3.00                                       ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                                ; map heated bed to heater 0
M143 H0 S110                                           ; set temperature limit for heater 0 to 110C



;; Run Bed PID Tune!! Below is an example for a 300x300 bed
;; M307 H0 A303.1 C356.7 D1.4 S1.00 V24.0 B0

; Fans
;M950 F0 C"out4" Q500                   ; create fan 0 on pin out4 and set its frequency
;M106 P0 C"Layer Fan" S0 H-1            ; set fan 0 name and value. Thermostatic control is turned off

; 4-wire PWM fan and tacho
M950 F0 C"!out4+out4.tach"              ; Definisce la ventola 3 con controllo PWM su io4.out e tachimetro su io4.in
M106 P0 C"Layer Fan" S0              ; set fan 1 name and value. Thermostatic control turned on for Hotend



M950 F1 C"out3" Q500                   ; create fan 1 on pin out3 and set its frequency
M106 P1 C"Hotend Fan" S0 H1 T45        ; set fan 1 name and value. Thermostatic control turned on for Hotend

M950 F2 C"out5" Q500                   ; create fan 2 on pin out5 and set its frequency
M106 P2 C"Electronics Fan" S1 H-1         ; set fan 2 name and value. Thermostatic control turned off


; Tools
M563 P0 D0 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

M950 H1 C"out1" T1         ; create nozzle heater output on out2 and map it to sensor 1
M307 H1 B0 S1.00           ; disable bang-bang mode for heater and set PWM limit
M143 H1 S300               ; set the maximum temperature in C for heater

; EVA 2 / BMG / E3D V6

M92 E400         ; set extruder steps per mm, 0.9 angle/step (LGX BONDTECH)
M906 E600         ; set extruder motor current (mA) and idle factor in per cent

M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.060000e-8 A"Hotend"  

;; Run Heater PID Tune!! 
;; M307 H1 A751.5 C196.6 D4.7 S1.00 V23.9 B0

; Z-Probe
;; Inductive Probe
; M558 P5 C"!io3.in" H5 F400 T5000       ; set Z probe type to unmodulated and the dive height + speeds
; G31 P500 X-30 Y-15 Z0.20               ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed

;; BLTouch
 M950 S0 C"io2.out"                     ; Create a servo pin on io2
 M558 P9 C"io2.in" H5 F240 T10800 A5    ; set Z probe type to unmodulated and the dive height + speeds
 G31 P25 X-28.00 Y-13.00 Z3.5           ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed

; Select default tool
T0

; Pressure Advance
 M572 D0 S0.10

; Panel Due 7i
 M575 P1 B57600 S1                       ; Avvia communicazione seriale

; Sensore fillamento
M591 D0.5 P3 C"io5.in" R0:99999  S0; E22.0; filament monitor connected to E0_stop
M591 D0.5 ; display filament sensor parameters for extruder drive 0