I'm having some issues with the included cable, it's fairly short and stiff, I'll try and order the XT30+2 connector and crimp a cable myself.
If duet would decide to make a "simple" direct drive toolboard using the same connectors as the duet5 mini, using the same stepper driver, I would certainly buy that.
thx
@dc42 No I didn't have an addon. I have swapped the board with a new one and it's working again, I noticed a very thin piece of copper on the board, 3mm long, almost invisible to the naked eye, a piece of very fine copper wiring, could have been caught on my sleeve and fallen on the board in the wrong place or something.
thx for your help
Hi,
Thx, I ordered another board, I'll swap it and see if it works again.
I ordered it from 123-3d , I think I have this board 3 weeks now.
I had tried with an older firmware to see if it would help, M98 returns Warning: Heater 2 predicted maximum temperature at full power is 268°C if I remove the neopixel lines.
; Configuration file for RepRapFirmware on Duet 3 Mini 5+ Ethernet
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.5.0-rc.4+1 on Thu Apr 25 2024 22:03:22 GMT+0200 (Midden-Europese zomertijd)
; General
G90 ; absolute coordinates
M83 ; relative extruder moves
M550 P"Brenda" ; set hostname
; Accessories
M918 P2 E-4 F2000000 ; Fysetc 12864mini
M950 E1 C"io3.out" T1 U3 ; create a RGB Neopixel LED strip with 3 LEDs on the Duet 3 Mini 5+ 12864_EXP1 header
M150 E1 R0 U0 B255 P255 S1 F1 ; display led blue
M150 E1 R255 U0 B0 P255 S1 F1 ; left encoder led red
M150 E1 R0 U255 B0 P255 S1 F0 ; right encoder led green
; Network
;M551 P"Brenda" ; set machine password
M552 P0.0.0.0 S1 ; configure Ethernet adapter
M586 P0 S1 ; configure HTTP
; Wait a moment for the CAN expansion boards to become available
G4 S2
; Accelerometers
M955 P121.0 I20 ; configure accelerometer on board #121
; Smart Drivers
M569 P0.0 S0 D2 ; driver 0.0 goes forwards (X axis), reverse !
M569 P0.1 S0 D2 ; driver 0.1 goes forwards (Y axis)
M569 P0.2 S0 D2 ; driver 0.2 goes forwards (Z axis)
M569 P0.3 S0 D2 ; driver 0.3 goes forwards (Z axis)
M569 P121.0 S1 D2 ; driver 121.0 goes forwards (extruder 0)
; Motor Idle Current Reduction
M906 I30 ; set motor current idle factor
M84 S30 ; set motor current idle timeout
; Axes
M584 X0.0 Y0.1 Z0.2:0.3 ; set axis mapping
M350 X32 Y32 Z16 I1 ; configure microstepping with interpolation
M906 X1800 Y1800 Z1800 ; set axis driver currents
M92 X160 Y160 Z2133 ; configure steps per mm
M208 X0:200 Y0:200 Z0:200 ; set minimum and maximum axis limits
M566 X900 Y900 Z12 ; set maximum instantaneous speed changes (mm/min)
M203 X12000 Y12000 Z600 ; set maximum speeds (mm/min)
M201 X3000 Y3000 Z100 ; set accelerations (mm/s^2)
; Extruders
M584 E121.0 ; set extruder mapping
M350 E16 I1 ; configure microstepping with interpolation
M906 E1000 ; set extruder driver currents
M92 E415 ; configure steps per mm
M566 E120 ; set maximum instantaneous speed changes (mm/min)
M203 E3600 ; set maximum speeds (mm/min)
M201 E250 ; set accelerations (mm/s^2)
; Kinematics
M669 K0 ; configure Cartesian kinematics
; Endstops
M574 X1 P"io0.in" S1 ; configure X axis endstop
M574 Y1 P"io1.in" S1 ; configure Y axis endstop
M574 Z1 P"io2.in" S1 ; configure Z axis endstop
; Sensors
M308 S0 P"temp0" Y"thermistor" A"Heated Bed" T100000 B3950 ; configure sensor #0
M308 S1 P"121.temp0" Y"pt1000" A"Nozzle" ; configure sensor #1
M308 S2 P"temp1" Y"thermistor" A"Chamber" T100000 B3950 ; configure sensor #2
; Heaters
M950 H0 C"out0" T0 ; create heater #0
M143 H0 P0 T0 C0 S110 A0 ; configure heater monitor #0 for heater #0
M307 H0 R0.305 K0.281:0.000 D1.86 E1.35 S1.00 B0 ; BED
M950 H1 C"121.out0" T1 ; create heater #1
M143 H1 P0 T1 C0 S285 A0 ; configure heater monitor #0 for heater #1
M307 H1 R2.43 D5.5 E1.35 K0.56 B0 ; configure model of heater #1
M950 H2 C"io4.out" T2 ; create heater #2
M143 H2 P0 T2 C0 S70 A0 ; configure heater monitor #0 for heater #2
;M307 H2 R0 D0 E0 K0 B1 ; configure model of heater #2
; M307 H2 A100 C10000 D2000 B1 S1.0
M307 H2 R0.1 D300 K0.03 B1; <- werkt ietswat
M570 H2 P144000 T70 ; 144000, hiermee zou het 40 uur moeten duren eer hij een fout geeft
; Heated beds
M140 P0 H0 ; configure heated bed #0
; Heated chambers
M141 P0 H2 ; configure heated chamber #0
; Fans
M950 F0 C"121.out2" ; create fan #0
M106 P0 C"Hotend Fan" S0 B0.1 H1 T45 ; configure fan #0
; Tools
M563 P0 S"Extruder" D0 H1 F0 ; create tool #0
M568 P0 R0 S0 ; set initial tool #0 active and standby temperatures to 0C
; neopixel hotend, turn on as well
M950 E0 C"121.led" T2 Q3000000
M150 E0 W255 B255 U255 R255 P255 S8
; Miscellaneous
T0 ; select first tool
"Manual" motor movement without homing is also impossible after M564 S0 H0
I'm setting up my printer with duet, I made some decent test prints 2 days ago but today the printer won't home at all, no movement, nothing.
The extruder does work, this one is connected to a roto toolboard.
When asking for the status with M122 I get a lot of Driver: not present lines, I don't know if this is normal
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.1 (2024-04-19 14:41:25) running on Duet 3 Mini5plus Ethernet (standalone mode)
Board ID: UPT9X-Z396U-D65J0-40KMA-L603Z-75NHD
Used output buffers: 1 of 40 (18 max)
=== RTOS ===
Static ram: 103232
Dynamic ram: 119804 of which 12 recycled
Never used RAM 15512, free system stack 190 words
Tasks: NETWORK(1,ready,21.6%,171) ETHERNET(5,nWait 7,0.5%,566) HEAT(3,nWait 6,0.0%,359) 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%,353) TMC(4,nWait 6,0.3%,111) MAIN(1,running,75.9%,647) IDLE(0,ready,0.9%,30) AIN(4,delaying,0.8%,260), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:37 ago, cause: power up
Last software reset at 2024-05-04 09:37, reason: User, Gcodes spinning, available RAM 15440, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00487000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 37325, completed 37325, timed out 0, errs 0
MCU temperature: min 24.4, current 25.4, max 25.7
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/1, heap memory allocated/used/recyclable 2048/8/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: not present
Driver 1: not present
Driver 2: not present
Driver 3: not present
Driver 4: not present
Driver 5: not present
Driver 6: not present
Date/time: 2024-05-04 09:40:16
Cache data hit count 67224291
Slowest loop: 51.23ms; fastest: 0.16ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.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 2 -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 343, received 733, lost 0, errs 0, boc 0
Longest wait 1ms for reply type 6034, peak Tx sync delay 3, free buffers 26 (min 25), ts 187/186/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 27.35ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 2 of 8
= Ethernet =
Interface state: active
Error counts: 0 0 0 0 0 0
Socket states: 5 5 2 2 2 0 0 0
@T3P3Tony thx, this seems to work even when set to 40 hours, thx
@EasyTarget I would also be willing to do some translations if I can get the printer working with duet
Hi,
For my chamber heater I'm using 2 large power resistors, these are aluminium plates of 20x10cm each, I've chosen the resistance so they can't run too hot, each resistor is 15 ohm, the two combined generate 76 watt heat. It's not much but it's enough and they don't get so hot that I risk burns, issues with cabling etc.
My printer lives outside, shielded from the rain but not the cold...
It's not possible to tune the heater, in Marlin I had THERMAL_PROTECTION_CHAMBER commented out and it worked well, sometimes the heater doesn't reach the set temperature but this doesn't really matter.
I'm puzzled how to do this in reprapfirmware, it have not found how to disable the faults.
It's ok that the firmware checks if the heater gets too hot, but I would like to get rid of any heating too slowly errors.
I've now resorted to mounting the thermistor on the heating element and not in the air, this seems to work with the tuning but this isn't really the temperature I want to control.
thx
Hi,
When upgrading to the latest firmware duet web control was in dutch.
-The translation isn't great, Console becomes "troosten", which is more like when someone is sad and needs to be comforted, jobs is translated to the equivalent of lanes (Banen).
-Also weird, the dutch language in the setting is called "Engels" which is dutch for english, I had to set it to English instead of Engels to get dutch, which should be called Nederlands
thx
@jay_s_uk Thx, I ordered the roto tool board
Hi,
I have bought the 1.3 toolboard but I'm not such a big fan on the connectors, I find them a bit small, I also don't need that many connections.
I'm considering the roto toolboard, this uses more standard e3d connectors.
On the product page it says:
Up to 1A peak current, micro-step interpolation from any setting to x256, stall detection (Note further thermal testing may allow higher extruder current for Extruders other than the Revo Roto which should not exceed 600mA current)
Does this mean I can connect an extruder motor with a higher current ? if I run into issues where the board would become to hot do I get a warning, does it shut down ?
Or does it make more sense to just use a stepper driver from the main board and run an additional cable in this case ?
I'm using a chamber, it can get up to 50 degrees in the summer, I guess if the stepper driver isn't used the board will not get very hot.
The Roto toolboard uses a XT30 2+2 connector, is such a cable included when you buy it ?
Does anyone know if more expansion boards are coming ? Does anyone other than duet make expainsion board that aren't clones ?
thx
@alankilian
I tried buying the duet one last year but was unable to find it at that time.
It uses some special parts if I'm not mistaken, for my design
you need 4 flanged bearings, 2 X-seal rubbers, a couple of washers, a magnet and a hal effect sensor, on my board the sensor is connected directly to the board and works as on/off switch, I think this is possible on a duet board as well.
Hi,
I've been working on a rotating filament sensor (with a magnet + hal effect sensor).
I've gotten to the point where it seems to be working well and reliable (3 weeks now, on a printer running marlin).
I'm using rubber X-seals to ensure good contact with the filament without adding too much resistance.
Do any of you think it's an interesting device to have ?
It detects both when the filament spool is empty and when the print head is clogged.
I do "a lot" of 3d printing and these 2 cases seem to account for +90% of my failed prints (I often print flame resistant abs and this can clog at times)
I've made a small video, https://youtu.be/DCe-7jBzin0
I posted this on the reprap forum last week but there was zero response 
thx
Bram
@blacksheep99
Hi,
I'm selling my duet board, duet ethernet + paneldue + pt100 + duex
Used for 100 (printing) hours, I was hoping to get 200 euros for everything (cost me 420 euro new)
The documentation does suggest this but:
-When printing on some surfaces that are less flat I find that delta calibration can cause skewed prints, maybe because it's difficult to tell the difference between a bed that is mounted at an angle and a tufnol plate that is somewhat warped.
I do delta calibration on a clean flat aluminium plate, then if I need to print on something other than that plate, I switch plates and do mesh compensation.
-With my printer delta calibration requires the head to be in the halfway position, this requires manual intervention
You think this causes me to have these issues ?
I managed a couple of prints without further adjustments, after 3 prints I needed to adjust the head -0.9mm with babystepping, homing again did not help here.
Resetting did help somewhat, but I'm now on +0.2mm with babystepping.
I did M500 before rebooting hoping that the config would be saved, I did not do delta calibration after reboot.
My bad, I was using the smartphone and pressed the y-50 button by accident, a nice scratch info the new aluminium plate.
Shouldn't duet stop at the height of the offset when the head is active actually, or at least ask for confirmation before going to 0 ?
I guess not using the buttons X,Y,Z on the web interface solves that, maybe a head1-z=0 macro button instead
Yes, I get that, but if I print the first layer with head1, and I see it needs to be lower, and I change the value, will duet, while printing, see that Z is no longer correct and adust while printing in this case.
I thought there was an issue (read it on the forum somewhere that the nozzle only moves when the next Gcode run that includes a Z height) that prevented this.
Or can you confirm that this does work, using these command while printing the head/nozzle does lower "immediately" ?
This would mean
G31 P500 X-12.5 Y-17.5 Z0
and for head 1:
G10 P0 X-4.32 Y-4.5 Z-2.45
This does have the downside of being able to crash the head into the bed as I've just found out (should have used an old bed to try this), but it does make more sense.
Does this solve the issue of adjusting while printing, should I be able to use this command to lower the nozzle while printing the first layer and then pasting to commands in the config file.
@luke-slaboratory
thx for your info
No I have:
G31 P500 X-12.5 Y-17.5 Z-2.07
to set the probe trigger height
and then
G10 P0 X-4.32 Y-4.5 Z0
G10 P1 X4.32 Y4.5 Z-0.2
A command like G10 P0 X-4.32 Y-4.5 Z10 does not really have the effect of the head going up.
You have G10 Z commands where the head does move while you send the command ? I was under the impression this was not possible.
I have been able to get good repeatable results, but setting the height for 2 heads this way takes too long when dealing with filament that clogs easily
I'm really looking for a way like the G10 command that actually moves the head up and down so I all have to do is check with the G10 command what the correct height is and then copy past that into the config.
It would also make adjusting while printing and applying that adjustment later easier.
Not, adjusting with babystepping, applying that different to the config file, rebooting, checking, make another small adjustment.
This would save me so much time.
thx
It couldn't hurt to ask I guess.
I don't really have specific issues I think.
I have observed that I need to double babystepping when starting my second print, I don't home between prints, I would like to know if this is a known bug/issue or an issue on my end.
I would prefer to not use babystepping at all, and set the head offset directly.
However, setting the Z offset of the head/tool does not actually alters the height of the head directly ? This is still the case ?
Both these issues seem to have the end result that setting the correct Z height for a dual head printer is a lot of work, this means I end up spending more time tuning the printer than printing.
I would like to know if there is a better way, it's not so much that I can't get it to work , it's more that these settings will only be good until the next clog and that clog could cost me hours in setting the correct height again.
Some (all) of this is off course user error.
So, is it possible to just avoid babystepping and have something similar that is saved between prints and reboots and allows me to set the Z height of head 1 & head 2 using an up or down button and/or with the offset command so the head moves to the new position and also remembers that this z-offset needs to be applied from now on until I change it again.
I have included an image of the printer, it's really a very simple kossel based design with dual extrusion.
both heads are on a rotating part bringing either head 1 or head 2 down.
probing can be done by putting an M6 bolt between the mechanism so both heads are placed "symetrical", the endstop is a simple microswitch on the bottom of the part cooler/blower.
Switching itself is a simple on/off that switched a valve fills one of the both ends of the pneumatic cylinder.
It works well fairly well actually but still needs some work for it to work well in +50 degrees celcius.
