Duet 3 mini5+ nightly restarts 3.5.2

Chriss

@droftarts I used the same object I always had a problem with and it finished the first time successfully.
I'm not sure how much this will tell us, a lucky punch maybe? Problem solved?
The only problem I see now is the quality:

I'm not sure where this came from. I do not see that on objects which are not as high as this object is. What shall I do now? Bring back the old version and be unable to print objects which this dimension? Or drop the bench board in and go back to the latest stable version and test again to see whether the quality is better than?

Cheers, Chriss

droftarts

@Chriss You'll need to retune Pressure Advance with the 3.6 release. It should work much better!

Ian

Chriss

@droftarts I saw that in the release notes. My PA dial in process came out with very much the same value as it was before.
I will perform the test again with a material I know better, this grey filament (ABS+) is new for me, the temperature may not be ideal for this material too. Maybe to much rush this time.
But I'm confused how the gab at the seams piled up over the layer hight, I never experienced that before.

Phaedrux

@Chriss said in Duet 3 mini5+ nightly restarts 3.5.2:

But I'm confused how the gab at the seams piled up over the layer hight, I never experienced that before.

That is common when there is under extrusion on unretract at layer change.

Chriss

This post is deleted!

Chriss

@Phaedrux

The top line is without any PA. I have the feeling that I do not need any PA at all. Can that be possible with the alpha?

Or I print to slow.

Cheers, Chriss

Chriss

That is the result with no PA at all.

oliof

@Chriss what are your retraction values?

Chriss

@oliof I have to admit that I do not know that anymore at this print. I shift here some profiles in SuSi back and forth. The current print with 5.8mm and 35 and 25mm/s look far better.
I know that 5.8mm are far to much for a direct dive, but I feel a bit helpless so I just tried the Voron 2.4 standard profile and some others.

oliof

@Chriss try 2mm @40mm/sec, if that's not better, give it a quarter to a half millimeter extra unretract.

Chriss

@oliof I do not why but the "avoid crossing perimeter = true" solved it so far with the standard profile. Only the first layer looks a bit strange now:
file:///home/chriss/Downloads/3.6.0-alpha.4/Pics/IMG_0612.JPG
I can not stop thinking that there is something strange ongoing with PA, which is off with my setup at the moment. The top side is overextruded at the touchpoints with the walls. That is more than strange with ABS+ and a EM of 0.88.

Chriss

@droftarts Back to topic..... I tuned a bit and solved my other problem with the missing extrusion. The printer just finished the 2nd 160mm print. So it is a 100% success rate now, I would not put a guarantee on it but it seems to me that the current alpha solved the reboots. But please to not count me on that. I did two prints only and I can not do more of them for now. The prints still look horrible in may ways, I need to tune the printer a bit further before I can do more tests. This thing eats to much filament at the moment.

Cheers, Chriss

Chriss

@droftarts

I'm afraid that I have to move back to the stable FW. I have soo many unexpected behaviours with the alpha since I print with it. I can not stand than anymore. The last pei sheet I sacrificed was to much. I saw steppers tuning into the wrong direction for some mm which ended in a bend gantry etc. Sorry, but I'm out of this testing, for a while now. My printer has to finish some prints and I can live without the hight but not with this strange behaviours I have seen in the last days.

I think that we can come to the conclusion that it is very likely that the next release will fix the reboot problems at least on my end. I'm not fully satisfied with this conclusion but it is how it is for now.

Cheers, Chriss

jay_s_uk

@Chriss have you reported any of these and have you been keeping up with the alpha releases?

Chriss

@jay_s_uk None if them to be honest. I had to switch back to the stable firmware to get some urgent needed parts out of the print bed, therefor was not enough time to take a note on every problem I experienced. And I have to admit that I'm not convinced that all of them where real problems with the firmware and not with my config.

I do not tend not to report a problem if I have not seen it more than once and If I'm not aware of any way to reproduce it. Everybody's time has a value and I try to not send people into the direction of ghost I possible saw.

Let me know if you think that this things may be interesting and I can put my observations into a new threat.

Cheers, Chriss

droftarts

@Chriss Fair enough, and thank you for you help and feedback so far! With so many custom machines running RRF, and the complexity of the firmware, whenever there are major changes it is difficult for us to test all variations of machine. We try to have a mix of machines to test on, but there's always gaps. A big thank you to everyone for taking part in alpha/beta/rc firmware testing, and your feedback.

Ian

ProteanReverie

Wanted to report in that following the changing of the SD cards I mentioned around 7/30/24 my benchtop board has not seen a single restart and currently has over 1000 hours of uptime. The other board which is running in a machine has not seen any issues since my last reported crash in this thread on 8/1/24, which was a crash that happened after the SD cards were changed. That machine has seen various restarts and downtime since then, due to other factors.

ProteanReverie

It would appear that my previous post had exactly the effect I was hoping for - the board that is in a machine crashed shortly after I posted, for the first time in over a month. Machine was idle in between prints when this occurred.

M122:

=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.2 (2024-06-11 17:14:16) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: T69HG-KN6KL-K65J0-409NJ-JYW1Z-RZQJW
Used output buffers: 1 of 40 (36 max)
Error in macro line 17 while starting up: Driver 1.0 does not exist
Driver 1.1 does not exist
Driver 1.3 does not exist
Driver 1.4 does not exist
Driver 1.2 does not exist
=== RTOS ===
Static ram: 103368
Dynamic ram: 122336 of which 0 recycled
Never used RAM 12856, free system stack 202 words
Tasks: NETWORK(1,ready,13.8%,203) HEAT(3,nWait 6,0.0%,350) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.1%,796) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,0.8%,101) MAIN(1,running,84.4%,665) IDLE(0,ready,0.0%,29) AIN(4,delaying,0.9%,259), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:43:24 ago, cause: software
Last software reset at 2024-09-11 12:29, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 12024, slot 2
Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00487803 BFAR 0x0000001c SP 0x20012008 Task NETW Freestk 482 ok
Stack: 2002c658 200317f0 200014e8 00000000 200331a7 0003015d 00030070 610f0000 00030149 00000000 00000000 00000000 200317fc 00000800 20035d08 2002c640 2001882c 2002c496 2001882c 2001ea80 000302e3 00000000 00000000 00000000 200120b8 00000014 4738ebf6
Error status: 0x00
MCU revision 3, ADC conversions started 2604593, completed 2604593, timed out 0, errs 0
MCU temperature: min 38.6, current 39.1, max 44.4
Supply voltage: min 23.8, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/140/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 32, reads 5983, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 32, reads 5983, 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 5983, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 32, reads 5982, 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 5983, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2024-09-11 13:08:49
Cache data hit count 4294967295
Slowest loop: 21.48ms; fastest: 0.16ms
=== Storage ===
Free file entries: 19
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 1.8ms, write time 113.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 0 1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 2 is on, I-accum = 0.0
Heater 4 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
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
=== Filament sensors ===
check 0 clear 24753400
Extruder 0 sensor: no filament
Extruder 1 sensor: no filament
=== CAN ===
Messages queued 23463, received 52125, lost 0, errs 1, boc 0
Longest wait 1ms for reply type 6018, peak Tx sync delay 253, free buffers 26 (min 25), ts 13023/13022/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 118.64ms; 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:b7
Module reset reason: Power up, Vcc 3.40, flash size 2097152, free heap 42764
WiFi IP address 10.1.10.21
Signal strength -57dBm, channel 11, mode 802.11n, reconnections 0
Clock register 00002001
Socket states: 0 0 0 0 0 0 0 0

Log:

2024-09-11 12:15:04 [warn] Finished printing file 0:/gcodes/PLA-2.5Atom-spiral_40base30degree_x_100tall_Cone.gcode, print time was 0h 33m
2024-09-11 12:15:44 [warn] HTTP client 10.1.10.161 login succeeded (session key 359056603)
2024-09-11 12:16:06 [warn] HTTP client 10.1.10.161 login succeeded (session key 3366296215)
2024-09-11 12:16:23 [warn] HTTP client 10.1.10.161 login succeeded (session key 3162514298)
2024-09-11 12:16:35 [warn] HTTP client 10.1.10.161 login succeeded (session key 3095629251)
2024-09-11 12:16:50 [warn] HTTP client 10.1.10.161 login succeeded (session key 3273569751)
2024-09-11 12:17:44 [warn] HTTP client 10.1.10.161 login succeeded (session key 3524598834)
2024-09-11 12:18:17 [warn] HTTP client 10.1.10.161 login succeeded (session key 2236099279)
2024-09-11 12:18:50 [warn] HTTP client 10.1.10.161 login succeeded (session key 2038503451)
2024-09-11 12:19:45 [warn] HTTP client 10.1.10.161 login succeeded (session key 3308195184)
2024-09-11 12:20:35 [warn] HTTP client 10.1.10.161 login succeeded (session key 946720536)
2024-09-11 12:21:28 [warn] HTTP client 10.1.10.161 login succeeded (session key 1138736952)
2024-09-11 12:21:50 [warn] HTTP client 10.1.10.161 login succeeded (session key 3108662693)
2024-09-11 12:22:43 [warn] HTTP client 10.1.10.161 login succeeded (session key 2976044894)
2024-09-11 12:23:05 [warn] HTTP client 10.1.10.161 login succeeded (session key 1080405183)
2024-09-11 12:23:17 [warn] HTTP client 10.1.10.161 login succeeded (session key 1254727083)
2024-09-11 12:23:39 [warn] HTTP client 10.1.10.161 login succeeded (session key 614652800)
2024-09-11 12:24:10 [warn] HTTP client 10.1.10.161 login succeeded (session key 2640235784)
2024-09-11 12:24:57 [warn] HTTP client 10.1.10.161 login succeeded (session key 3181799873)
2024-09-11 12:25:53 [warn] HTTP client 10.1.10.161 login succeeded (session key 1776770804)
2024-09-11 12:26:45 [warn] HTTP client 10.1.10.161 login succeeded (session key 2156320815)
2024-09-11 12:27:18 [warn] HTTP client 10.1.10.161 login succeeded (session key 2647272730)
2024-09-11 12:27:30 [warn] HTTP client 10.1.10.161 login succeeded (session key 1370953698)
2024-09-11 12:27:57 [warn] HTTP client 10.1.10.161 login succeeded (session key 831992087)
2024-09-11 12:28:36 [warn] HTTP client 10.1.10.161 login succeeded (session key 1995411029)
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.2 (2024-06-11 17:14:16)
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:01 [warn] WiFi module started
power up + 00:00:11 [warn] WiFi module is connected to access point SD3D-24, IP address 10.1.10.21
power up + 00:00:14 [warn] HTTP client 10.1.10.9 login succeeded (session key 2317065672)
2024-09-11 12:25:39 [warn] Date and time set at power up + 00:00:14
2024-09-11 12:26:07 [warn] HTTP client 10.1.10.161 login succeeded (session key 2214435877)
2024-09-11 12:27:17 [warn] HTTP client 10.1.10.161 login succeeded (session key 2319523673)
2024-09-11 12:27:17 [warn] HTTP client 10.1.10.161 login succeeded (session key 4186603624)
2024-09-11 12:27:17 [warn] HTTP client 10.1.10.161 attempted login but no more sessions available
2024-09-11 12:27:17 [warn] HTTP client 10.1.10.161 attempted login but no more sessions available
2024-09-11 12:27:17 [warn] HTTP client 10.1.10.161 attempted login but no more sessions available
2024-09-11 13:08:49 [debug] === Diagnostics ===

droftarts

@ProteanReverie Thanks for the report. I think @rechrtb and @dc42 have been tracking down what causes this crash, so will hopefully have a fix soon.

Ian

Chriss

@droftarts said in Duet 3 mini5+ nightly restarts 3.5.2:

@Chriss Fair enough, and thank you for you help and feedback so far!

You are more than welcome, I like to test early versions and give feedback if possible but this alpha was a bit to much for me. There are to many projects at my table at the moment and I have to many printers which do work as they should.