Hi Guys,
I thought I will share with you unit that we developed
- 5 colours
- active heating
- rewind of the filament
Hi Guys,
I thought I will share with you unit that we developed
@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?
@T3P3Tony there is no difference - same setup, same hardware. this machine has been running non stop for few years now and suddenly getting these errors without making any changes
@droftarts not sure why are you talking about the SD card - you cannot swap them out since it runs firmware of it - it is Mini5+ board.
since then I have recreated new config file and same gcode files work just fine.
So the issue is internal related to the firmware and not the SD card and/or gcode file.
I have supplied gcode file so that you guys can have a look that there is nothing causing issue in there. I have been logging those issues and there is a warning for every single move
2024-12-18 15:02:37 [warn] 6 points probed, min error -0.165, max error 0.655, mean 0.232, deviation 0.261
Height map saved to file 0:/sys/heightmap.csv
2024-12-18 15:02:49 [warn] HTTP client 192.168.1.141 login succeeded (session key 3163552733)
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:56 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits
2024-12-18 15:02:57 [warn] Error: G1: intermediate position outside machine limits
@Arminas said in PT1000 thermistor configuration:
erature is stable all the time, expect at a
you probably have season changes and thus your PID tuning is out the window.
rerun the tune and you will probably find that it works fine now
@droftarts I think you missed the part where it says: "same file works on the other machine"
tried with multiple files - direct upload, upload from slicer, different STL files - same result
@droftarts said in Error: G1: intermediate position outside machine limits:
The job start sequence appears to be to home all, move the nozzle to Y1 Z3, wait for temperatures, then do a mesh scan of the print area. Does that all work?
yes - it freaks out in the middle of the bed for some of the sections and then continues like nothing happenned and freaks out again later.
as you can imagine there are puddles of plastic where it is freaking out
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