Posts made by Aurimas

this is doing my head in
was working find now suddenly it doesn't work any more

01-TCM-03-029 REVB_ABS_6h6m_nozzle_0.6.gcode

3.6.0-beta.2 and just tested its same with 3.5.4

there is nothing obvious in the gcode and it is working on the other machine
@dc42

config.g

; Configuration file for Duet 3 Mini 5+ (firmware version 3)
; executed by the firmware on start-up
G90                                                  ; send absolute coordinates...
M83                                                  ; ...but relative extruder moves
M550 P"Vega2.0"                                      ; set printer name

; Network
M552 S1                                              ; enable network
M586 P0 S1                                           ; enable HTTP
M586 P1 S0                                           ; disable FTP
M586 P2 S0                                           ; disable Telnet

; Drives
M569 P0.0 S1 D3 V40                                        ; physical drive 0.0 goes forwards
M569 P0.1 S0 D3 V40                                        ; physical drive 0.1 goes forwards
M569 P0.2 S1 D3 V40                                        ; physical drive 0.2 goes forwards
M569 P0.3 S1 D3 V40                                        ; physical drive 0.3 goes forwards
M569 P0.4 S0 D3 V40                                        ; physical drive 0.4 goes forwards
M584 X0.0 Y0.1 Z0.4 E0.2                         ; set drive mapping
M350 X16 Y16 Z16 E16 I1                           ; configure microstepping with interpolation
M92 X100.00 Y80.00 Z1920.00 E400.00             ; set steps per mm
M566 X300.00 Y300.00 Z60.00 E120.00           ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z180.00 E1200.00      ; set maximum speeds (mm/min)
M201 X2500.00 Y2500.00 Z20.00 E250.00           ; set accelerations (mm/s^2)
M906 X1200 Y1200 Z900 E650 I30                   ; set motor currents (mA) and motor idle factor in per cent
M84 S90                                              ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                                     ; set axis minima
M208 X320 Y300 Z350 S0                               ; set axis maxima

; Endstops
M574 X1 S1 P"io2.in"                                ; configure active-high endstop for low end on X via pin !io2.in
M574 Y2 S1 P"!io4.in"                                ; configure active-high endstop for low end on Y via pin !io4.in
M574 Z1 S2                                           ; configure Z-probe endstop for low end on Z

; Z-Probe
;M950 S0 C"io3.out" 
M950 S0 C"121.io0.out"                                   ; create servo pin 0 for BLTouch
;M558 P9 C"^io3.in" H5 F120 T6000
M558 P9 C"121.^io0.in" H5 F3000 T8000 S0.25                      ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X-30 Y10 Z4                                ; set Z probe trigger value, offset and trigger height
M557 X20:280 Y20:280 S60                             ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138         ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                                   ; create bed heater output on out0 and map it to sensor 0
M307 H0 B1 S1.00                                     ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0                                              ; map heated bed to heater 0
M143 H0 S160                                         ; set temperature limit for heater 0 to 120C
M308 S1 P"temp1" Y"pt1000" R2200                     ; configure sensor 1 as PT1000 on pin temp1
M950 H1 C"out1" T1                                   ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00                                     ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S350                                         ; set temperature limit for heater 1 to 350C
M308 S2 P"temp2" Y"pt1000" R2200                     ; configure sensor 2 as PT1000 on pin temp2
M950 H2 C"out2" T2                                   ; create nozzle heater output on out2 and map it to sensor 2
M307 H2 B0 S1.00                                     ; disable bang-bang mode for heater  and set PWM limit
M143 H2 S350                                         ; set temperature limit for heater 2 to 350C

; Fans
M950 F0 C"out3" Q500                                 ; create fan 0 on pin out3 and set its frequency
M106 P0 S0 H-1                                       ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out4" Q500                                 ; create fan 1 on pin out4 and set its frequency
M106 P1 S1 H-1                                       ; set fan 1 value. Thermostatic control is turned off
M950 F2 C"out5" Q500                                 ; create fan 2 on pin out5 and set its frequency
M106 P2 S1 H1 T45                                    ; set fan 2 value. Thermostatic control is turned on
M950 F3 C"out6" Q500                                 ; create fan 3 on pin out6 and set its frequency
M106 P3 S1 H2 T45                                    ; set fan 3 value. Thermostatic control is turned on

; Tools
M563 P0 S"Left Extruder" D0 H1 F0                    ; define tool 1
G10 P0 X0 Y0 Z0                                      ; set tool 1 axis offsets
G10 P0 R0 S0                                         ; set initial tool 1 active and standby temperatures to 0C
;

; Custom settings are not defined

; Miscellaneous
M575 P1 S0 B57600                                    ; enable support for PanelDue
M501                                                 ; load saved parameters from non-volatile memory
;
T0                                                   ; select first tool

hi all,

any ideas how to tune bed while heated chamber is on?
tuning separately doesn't really work since the bed is slow to warm up on its own and would not reach 150C
chamber needs to be 120-150C
also fairly slow to heat up.
when both are heating up it faults out few times
after resetting the faults and it has heated up the temperatures overshoot big time.
big time as in 10-20C and the PID is out of the water and cannot control the temperature properly

@dc42
got this error
Error: Movement halted because a step timing error occurred (code 3). Please reset the controller.

here is M122

=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.6.0-alpha.4+3 (2024-08-28 10:03:49) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 44BBP-1N6KL-K65J0-409N2-1BW1Z-RD9N1
Used output buffers: 3 of 40 (40 max)
=== RTOS ===
Static ram: 92328
Dynamic ram: 91792 of which 12 recycled
Never used RAM 37808, free system stack 121 words
Tasks: NETWORK(2,nWait 7,11.6%,183) HEAT(3,nWait 6,0.0%,325) Move(4,invalid,0.1%,247) TMC(4,nWait 6,0.9%,65) CanReceiv(6,nWait 1,0.1%,771) CanSender(5,nWait 7,0.0%,327) CanClock(7,delaying,0.0%,348) MAIN(1,running,86.4%,639) IDLE(0,ready,0.1%,29) AIN(4,delaying,0.8%,255), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 19:56:34 ago, cause: software
Last software reset at 2024-08-03 12:45, reason: HardFault imprec, Gcodes spinning, available RAM 12036, slot 0
Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00000400 ICSR 0x00489803 BFAR 0xe000ed38 SP 0x200120a0 Task NETW Freestk 544 ok
Stack: 00000000 000aff28 200014ec 2000dfe0 ffffffff 0009e9c7 00012156 210f0000 00012179 2000dfe0 00000000 000afea8 00000083 e000e000 2001e880 a5a5a5a5 000121ed 200355f8 00000000 563bc5f2 00031c25 2001e880 2001ce00 00000001 200355f8 00000000 00033dd7
Error status: 0x04
Aux0 errors 0,0,0
MCU temperature: min 22.3, current 30.3, max 31.2
Supply voltage: min 24.3, current 24.4, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/4, heap memory allocated/used/recyclable 2048/420/316, gc cycles 0
Events: 0 queued, 0 completed
Date/time: 2024-09-03 09:16:25
Slowest loop: 246.24ms; fastest: 0.09ms
=== Storage ===
Free file entries: 18
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 12.1ms, write time 94.0ms, max retries 0
=== Move ===
Segments created 667, maxWait 66447882ms, bed comp in use: mesh, height map offset 0.000, hiccups added 0 (0.00/278.36ms), max steps late 1, ebfmin 0.00, ebfmax 0.00
Pos req/act/dcf: 34659.00/34449/0.28 -5056.00/-4998/-0.90 15480.00/15286/0.68
no step interrupt scheduled
Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 33, reads 42543, writes 20, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 33, reads 42543, writes 20, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 37, reads 42540, writes 22, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 37, reads 42540, writes 22, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 25, reads 42551, writes 12, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
=== DDARing 0 ===
Scheduled moves 113330, completed 113290, LaErrors 0, Underruns [0, 0, 0]
=== DDARing 1 ===
Scheduled moves 0, completed 0, LaErrors 0, Underruns [0, 0, 0]
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.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) 3
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
SBC is idle in state(s) 0
Daemon is doing "M106 P5 S0.1" 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 1, axes/extruders owned 0x0000807
Queue 0 has 'M106 P5 S0.1' for move 113291
Queue 0 has 'M106 P5 S0.1' for move 113293
Queue 0 has 'M106 P5 S0.1' for move 113299
Queue 0 has 'M106 P5 S0.1' for move 113300
Queue 0 has 'M106 P5 S0.1' for move 113303
Queue 0 has 'M106 P5 S0.1' for move 113308
Queue 0 has 'M106 P5 S0.1' for move 113309
Queue 0 has 'M106 P5 S0.1' for move 113311
Queue 0 has 'M106 P5 S0.1' for move 113312
Queue 0 has 'M106 P5 S0.1' for move 113314
Queue 0 has 'M106 P5 S0.1' for move 113317
Queue 0 has 'M106 P5 S0.1' for move 113325
Queue 0 has 'M106 P5 S0.1' for move 113328
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 755848, received 2872555, lost 0, ignored 0, errs 0, boc 0
Longest wait 5ms for reply type 4014, peak Tx sync delay 282, free buffers 26 (min 25), ts 358975/358974/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 223.95ms; fastest: 0.00ms
Responder states: MQTT(0) HTTP(0) HTTP(1) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 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 c4:5b:be:ce:9c:81
Module reset reason: Power up, Vcc 3.36, flash size 2097152, free heap 36344
WiFi IP address 192.168.1.131
Signal strength -52dBm, channel 6, mode 802.11n, reconnections 0
Clock register 00002001
Socket states: 5 0 3 0 0 0 0 0

Hi,

is there a way to overcome this without pulling SD card out on the slave board?
I am trying to update miniplus firmware on a board that has can address 4

Error: M997: In-application programming binary "0:/firmware/Duet3_CANiap32_Mini5plus.bin" not found on board 4

@o_lampe said in AuruMMS - multi colour/material unit running on Duet:

Hope to see more of your machine in the future.

Reply

The cutter is independent - on the extruder in this case similar to Bambu/Voron setups.
Also have designed actuator activated cutter that can sit just above the extruder

Hi Guys,

I thought I will share with you unit that we developed

• 5 colours
• active heating
• rewind of the filament

https://youtu.be/X2Cqmb0qTWI

@oliof said in weird issue with fans:

Main difference between your IDEX and mine is that you have a chamber fan and an electronics fan(? seems to be disabled in the config); so it's not a perfect match but the best I can do.

thank you for trying

@oliof said in weird issue with fans:

PS: Please dont be mistaken, toolchanging and IDEX can be intricate, and I debugged an intractable issue this morning where the U axis unhomed when switching out of tfree2 ... it happened during homing calls, but not for X. So I changed to manually defining the parking position.

the isssue is that the actual speed is not the same as the actual speed - this is reported by firmware itself. have a look once again in the image I provided

@oliof the fans work on individual extruders - no problem at all, ie when T0 and T1 is used.
it is an issue when T2 and T3 is used.
it can be seen that it is an issue when you look at the requested and actual speeds - they do not match.

@Phaedrux said in weird issue with fans:

I understand the reluctance to upgrade but if it's already something that's been fixed or not present in a a current version. We try to ask if the problem exists in the latest release so that it can be more easily fixed in the next release.

I have upgraded other machines and had nothing but problems - constant software restart.
The same on multiple machines and as far as I know no issues have been rectified.
and it is really dissapointing that topics with simple questions about configuration get lots of support, but when it comes to real firmware issues everyone just stays quiet and provides no feedback.

Doesn't really inspire to use Duet going forward. Does it?
it is not the first serious issue I am having and so far I have not received appropriate support even though I have installed multiple boards into our printers that we build.
It sounds really good when we tell customer "Please downgrade to old version of the firmware because new one has bugs and causes system issues and we get no proper support on resolving the issues"
doesn't that sound great?

My issues so far:

• constant issue with magnetic rotating filament sensor - either too little movement or sensor error. IMPOSSIBLE to use
• constant reboots of the boards for software reasons from RC4 - Impossible to use
• no this issue with requested speed >0 and actual speed ZERO

@dc42 @droftarts anyone?

@droftarts said in weird issue with fans:

M106 to set the fan

neither of the fans is running when P2 or P3 is selected until the pause.
see the image of the state of the fan

both fans are in the same state - requested >0 and actual is 0

So having weird issue with fan.
It is IDEX setup as per the config file attached
when using single extruder the fans turn on on and off as supposed.
when it is using Tool 2 or tool 3 the fans do not turn on as supposed to.
Requested speed reports as supposed to, but actual sits at 0
if paused/resumed - fans come on

Firmware version is 3.5.0 RC3. I know that it is not the latest, but not keen to upgrade to latest due to all issues I have been having

; Configuration file for Duet 3 Mini 5+ (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat May 08 2021 10:30:29 GMT+1000 (Australian Eastern Standard Time)

; General preferences
G90                                                  ; send absolute coordinates...
M83                                                  ; ...but relative extruder moves
M550 P"Vega300-IDEX"                                      ; set printer name
G4 S1   ;wait for expansion boards to start
; Network
;M551 P"Vega"                                         ; set password
M552 S1                                              ; enable network
M586 P0 S1                                           ; enable HTTP
M586 P1 S0                                           ; disable FTP
M586 P2 S0                                           ; disable Telnet
M575 P1 S1 B57600
M584 X0.2 Y0.3 Z0.0:0.1 U0.4 E121.0:20.0                         ; set drive mapping
M669 K1 X1:1:0:0 Y-1:1:0:0 U0:0:0:1 Z0:0:1:0                                       ; select CoreXY mode

; Drives
M569 P0.0 S0 D3 V40                                         ; physical drive 0.0 goes forwards
M569 P0.1 S0 D3 V40                                        ; physical drive 0.1 goes forwards
M569 P0.2 S1 ;D3 V40                                      ; physical drive 0.2 goes forwards
M569 P0.3 S1 ;D3 V40                                       ; physical drive 0.3 goes forwards
M569 P0.4 S0 ;D3 V40                                       ; physical drive 0.4 goes forwards
M569 P121.0 S0 D3 V40
M569 P20.0 S0 D3 V40

M350 X16 Y16 Z16 U16 T1 E16:16 I1                           ; configure microstepping with interpolation
M671 X-125:465 Y170:170 S14
M92 X80.00 Y80.00 Z2400.00 U80.00 E400.0:400.0             ; set steps per mm
M566 X1200.00 Y1200.00 Z20.00 U1200 E3200.00:3200.00           ; set maximum instantaneous speed changes (mm/min)
M203 X15000.00 Y15000.00 Z280.00 U15000.00 E10200.00:10200.00      ; set maximum speeds (mm/min)
M201 X5000.00 Y5000.00 Z25.00 U5000.00 E1550.00:1550.00           ; set accelerations (mm/s^2)
M906 X1600 Y1600 Z850 U1200 E600:600 I30                   ; set motor currents (mA) and motor idle factor in per cent
M84 S90                                              ; Set idle timeout

; Axis Limits
M208 X-65 Y0 U0 Z-1 S1                                     ; set axis minima
M208 X325 Y340 U390 Z420 S0                               ; set axis maxima


; Endstops
M574 X1 S1 P"!io3.in"                               ; configure switch-type (e.g. microswitch) endstop for low end on X via pin
M574 Y1 S1 P"!io4.in"
M574 U2 S1 P"!io2.in"
M574 Z1 S2                                           ; configure Z-probe endstop for low end on Z

; Z-Probe
M950 S0 C"121.io0.out"                                   ; create servo pin 0 for BLTouch
M558 P9 C"121.^io0.in" H5 F2200 T3000 S0.25                     ; set Z probe type to bltouch and the dive height + speeds
G31 P300 X-30 Y5 Z2.5                               ; set Z probe trigger value, offset and trigger height Increase Z number if the nozzle is too far
M557 X50:330 Y25:280 S200

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138         ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0                                   ; create bed heater output on out0 and map it to sensor 0
M307 H0 B1 S1.00                                     ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0                                              ; map heated bed to heater 0
M143 H0 S120                                         ; set temperature limit for heater 0 to 120C

M308 S1 P"121.temp0" Y"pt1000" R2200               ; configure sensor 1 as PT1000 on pin 121.temp0
M950 H1 C"121.out0" T1                             ; create nozzle heater output on 121.out0 and map it to sensor 1
M307 H1 B0 S1.00                                   ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S350

M308 S2 P"20.temp0" Y"pt1000" R2200              ; configure sensor 2 as PT1000 on pin 121.io0.in
M950 H2 C"20.out0" T2                             ; create nozzle heater output on 122.out0 and map it to sensor 2
M307 H2 B0 S1.00                                   ; disable bang-bang mode for heater  and set PWM limit
M143 H2 S350                                       ; set temperature limit for heater 2 to 350C

M308 S4 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin temp2
;M950 H4 C"out5" T4                           ; create chamber heater output on out2 and map it to sensor 4
;M307 H4 B1 S1.00                             ; enable bang-bang mode for the chamber heater and set PWM limit
M141 H4                                      ; map chamber to heater 2
;M143 H4 S70                                 ; set temperature limit for heater 2 to 280C

; Fans

M950 F3 C"20.out1" Q500                           ; create fan 1 on pin 121.out2 and set its frequency
M106 P3 S0                                   ; set fan 1 value. Thermostatic control is turned on

M950 F1 C"121.out1" Q500                           ; create fan 3 on pin 122.out2 and set its frequency
M106 P1 S0                    ;                set fan 3 value. Thermostatic control is turned on

M950 F5 C"out5" Q500                         ; create fan 1 on pin out3 and set its frequency
;M106 P5 S1 H4 T55                            ; set fan 1 value. Thermostatic control is turned on

M950 F4 C"20.out2" Q500
M106 P4 T45 H2

M950 F6 C"121.out2" Q500
M106 P6 T45 H1

M950 P12 C"out1"
M42 P12 S1 ;turn the light on

M950 F10 C"out6" Q500                                 ; create fan 2 on pin out5 and set its frequency
M106 P10 S1                                    ; set fan 2 value. Thermostatic control is turned on

; Tools
M563 P0 S"Left Extruder" D0 H1 F1                   ; define tool 1
M568 P0 S0 R0 A0

M563 P1 S"Right extruder" D1 H2 X3 F3                   ; define tool 2
M568 P0 S0 R0 A0

; ''' Create a tool that prints 2 copies of the object using both carriages'''
M563 P2 S"Copy 200x340" D0:1 H1:2 X0:3 F1:3 L0; tool 2 uses both extruders, hot end heaters and fans, and maps X to both X and U
G10 P2 X30 Y0 U-165 S0 R0 ; set tool offsets and temperatures
M567 P2 E1:1 ; set mix ratio 100% on both extruders

;''' Create a tool that prints 2 copies of the object using both carriages'''
M563 P3 S"Mirror 180x340" D0:1 H1:2 X0:3 F1:3 L0; tool 2 uses both extruders, hot end heaters and fans, and maps X to both X and U
G10 P3 X50 Y0 U-370 S0 R0 ; set tool offsets and temperatures
M567 P3 E1:1 ; set mix ratio 100% on both extruders

; Custom settings are not defined
M591 D0 P3 C"121.io1.in" S1 R10:150 L24.8 E15.0 ; Duet3D rotating magnet sensor for extruder drive 0 is connected to E0 endstop input, enabled, sensitivity 24.8mm.rev, 70% to 130% tolerance, 3mm detection lengt

M591 D1 P3 C"20.io1.in" S1 R10:150 L24.8 E15.0 ; Duet3D rotating magnet sensor for extruder drive 0 is connected to E0 endstop input, enabled, sensitivity 24.8mm.rev, 70% to 130% tolerance, 3mm detection length

; Miscellaneous
M575 P1 S0 B57600                                    ; enable support for PanelDue
M501                                                 ; load saved parameters from non-volatile memory

T0
                                                  ; select first tool

M307 H0 R0.21 K0.586:0.000 D3.70 E1.35 S1.00 B1

15-45s intervals 1LC looses connection with Mini - console reports that the toolboard stop sending status
eventually the board restarts
downgraded to 3.4.6 don't have the same issue

@droftarts The wires are 100mm long
why would it run sometimes for hours and hours on the same printer and then throw an error every 15min?

@droftarts

straight after the error no data received this time

M591 D0
Duet3D rotating magnet filament monitor v4 on pin 121.io1.in, enabled, sensitivity 24.80mm/rev, allow 50% to 150%, check printing moves every 5.0mm, version 4, mag 132 agc 61, measured sensitivity 25.79mm/rev, min 95% max 105% over 113023.8mm

	M122 B121
Diagnostics for board 121:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.6 (2023-07-21 14:17:33)
Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10)
All averaging filters OK
Never used RAM 2108, free system stack 17 words
Tasks: Move(notifyWait,0.0%,99) HEAT(notifyWait,0.4%,75) CanAsync(notifyWait,0.0%,61) CanRecv(notifyWait,0.0%,74) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,3.0%,57) MAIN(running,91.7%,351) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0%
Last reset 07:43:21 ago, cause: software
Last software reset data not available
Driver 0: pos 100779577, 400.0 steps/mm,standstill, SG min 2, read errors 0, write errors 0, ifcnt 55, reads 22960, writes 0, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
Moves scheduled 713681, completed 713681, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -1/9, peak Rx sync delay 193, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 23.8, current 24.2, max 24.3
MCU temperature: min 55.0C, current 78.5C, max 81.7C
Last sensors broadcast 0x00000002 found 1 6 ticks ago, 0 ordering errs, loop time 1
CAN messages queued 975, send timeouts 0, received 605, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 0, other errors 0
=== Filament sensors ===
Interrupt 4 to 9us, poll 8 to 1184us
Driver 0: pos 13916.25, errs: frame 236 parity 0 ovrun 0 pol 0 ovdue 0

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: UFKKT-RN6KL-K65J0-409N8-28W1Z-RSKK2
Used output buffers: 1 of 40 (40 max)
=== RTOS ===
Static ram: 103712
Dynamic ram: 112888 of which 304 recycled
Never used RAM 20896, free system stack 112 words
Tasks: NETWORK(notifyWait,2.6%,201) HEAT(notifyWait,0.1%,338) Move(notifyWait,15.2%,235) CanReceiv(notifyWait,0.5%,771) CanSender(notifyWait,0.4%,324) CanClock(delaying,0.0%,349) TMC(notifyWait,7.8%,72) MAIN(running,58.6%,425) IDLE(ready,9.5%,30) AIN(delaying,5.3%,263), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 07:43:06 ago, cause: software
Last software reset details not available
Error status: 0x04
Aux0 errors 0,0,1964
MCU revision 3, ADC conversions started 27789048, completed 27789048, timed out 0, errs 0
Step timer max interval 1487
MCU temperature: min 23.0, current 32.0, max 33.1
Supply voltage: min 21.7, current 23.7, 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/84/8, gc cycles 0
Events: 6 queued, 6 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 48, reads 31646, writes 2, timeouts 2, DMA errors 0, CC errors 0, failedOp 0x71
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 48, reads 31647, writes 2, timeouts 1, DMA errors 0, CC errors 0, failedOp 0x71
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 40, reads 31649, writes 2, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 40, reads 31649, writes 2, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 40, reads 31648, writes 2, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 48, reads 31648, writes 2, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 48, reads 31649, writes 2, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2024-05-13 16:45:03
Cache data hit count 4294967295
Slowest loop: 229.31ms; fastest: 0.07ms
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 11.2ms, write time 4.7ms, max retries 0
=== Move ===
DMs created 83, segments created 44, maxWait 2882877ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 723642, completed 723642, hiccups 0, stepErrors 0, LaErrors 0, Underruns [1, 0, 6], 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 4 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.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 assembling a command in state(s) 0 0, running macro
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0: no data received
Extruder 1: no data received
=== CAN ===
Messages queued 963536, received 1137912, lost 0, boc 0
Longest wait 5ms for reply type 6024, peak Tx sync delay 498, free buffers 18 (min 16), ts 138736/138736/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 203.94ms; fastest: 0.06ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 4 of 8
= WiFi =
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notready 0, noresp 6
WiFi firmware version 1.26
WiFi MAC address e8:68:e7:e1:50:c5
WiFi Vcc 3.43, reset reason Power up
WiFi flash size 2097152, free heap 24712
WiFi IP address 192.168.1.87
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

@gloomyandy

yes - I believe it was on.
even though after all these restarts I might have lost the track
here is another crash report

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: PA279-4N6KL-K65J0-409N0-4Z02Z-HWYBD
Used output buffers: 20 of 40 (36 max)
=== RTOS ===
Static ram: 103232
Dynamic ram: 122532 of which 12 recycled
Never used RAM 15640, free system stack 182 words
Tasks: NETWORK(2,nWait 7,14.4%,208) HEAT(3,nWait 6,0.0%,326) Move(4,nWait 6,0.0%,310) CanReceiv(6,nWait 1,0.1%,772) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,348) TMC(4,nWait 6,1.4%,102) MAIN(1,running,83.1%,651) IDLE(0,ready,0.0%,30) AIN(4,delaying,0.9%,260), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 39:07:39 ago, cause: software
Last software reset at 2024-05-11 16:34, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 11100, slot 1
Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x0047d803 BFAR 0x0000001c SP 0x20011ff0 Task NETW Freestk 483 ok
Stack: 2002c610 20030848 200014e8 00000000 2003322f 0002ff99 0002feac 610f0000 0002ff85 00000000 00000000 00000000 20030854 00000800 2002c5f8 2002c5f8 00000002 2002c41e 200187fc 2001e9f8 0003011f 00000000 00000000 00000000 200120a0 00000014 46b8173e
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 140859060, completed 140859060, timed out 0, errs 0
MCU temperature: min 22.9, current 23.1, max 23.5
Supply voltage: min 23.9, current 24.0, max 24.1, 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 81, reads 62161, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 106, read errors 0, write errors 0, ifcnt 81, reads 62161, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 45, reads 62161, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 64, read errors 0, write errors 0, ifcnt 83, reads 62161, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 66, read errors 0, write errors 0, ifcnt 84, reads 62161, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 56, read errors 0, write errors 0, ifcnt 84, reads 62161, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 68, read errors 0, write errors 0, ifcnt 83, reads 62161, writes 0, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2024-05-13 07:41:49
Cache data hit count 4294967295
Slowest loop: 32.79ms; fastest: 0.16ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.7ms, 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 1, completed 1, 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 4 -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
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 6162, received 27379, lost 0, errs 0, boc 0
Longest wait 6ms for reply type 6024, peak Tx sync delay 261, free buffers 26 (min 25), ts 3419/3419/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 20.35ms; fastest: 0.06ms
Responder states: MQTT(0) HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 2.1beta6
MAC address e8:68:e7:e1:4e:a5
Module reset reason: Power up, Vcc 3.41, flash size 2097152, free heap 33128
WiFi IP address 192.168.1.110
Signal strength -56dBm, channel 2, mode 802.11n, reconnections 0
Clock register 00002001
Socket states: 0 0 3 0 0 0 0 0

@droftarts that is the biggest problem - all versions are now playing up. this all started after I went to 3.5.1 and rolling back to older versions make no difference.
Until then all machines worked non stop didn't have a single issue.
I ran Rc3 and RC4 before upgrade to 3.5.1
after upgrade to 3.5.1 started getting issues with constant restarts.
rolled back to RC4 - same issues
rolled back to RC3 - still having issues and even RC2 is not helping.
All RC versions prior to this worked just fine.
now it appears that one of the machines MCU is being overloaded - the load goes to 1930% as you can see per log.
this hapenned multiples times. in this case movement is only 150mm/s
dropping the speed to 60mm/s helps to reduce the load, but the movement is still jittery and not acceptble.
this never been an issue prior to the update.
this is why I am asking if the installation of the firmware does clean install and should I try to downgrade via USB cable.
I have 3 machines that are no behaving any more. it is really upsetting when the printer crashes on a print that was going on for nearly 80 hours and had only 6 hours to go. not to mention kilograms of plastic wasted

@dc42 @gloomyandy @Phaedrux

guys got a question - does rolling back firmware completelly reinstalls it? I am having issues with 3 machines that worked find on RC2-RC4, but since I have installed 3.5.1 all of them have issues - reboots, overloads and so on. none of the machines work reliablly anymore.

@droftarts thanks, but I am not sure how it solves my issue
1LC is mounted in the front of the LGX extruder with filament sensor on top of it.
saying that I had issues with simple switch type filament sensor as well.