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

@Phaedrux I have been pining target and had disconnect - ping had no issues at all.

Hi,

has anyone used Duet boards to build a waterjet cutter?

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?