Posts made by Pyper

@o_lampe
Instead of two gantries, I wonder if this design would work better with two print heads on each side for a total of 4 print heads (this one only has one on each side):
https://www.thingiverse.com/thing:4481112
That way you only have one Z to worry about. You can park each head until needed for 4 filament prints, and still do the duplicate/mirror function with just two heads. The hashPrinter can print four at once, definitely a plus over this!

The 3D Chameleon has a pretty neat feature where it uses the print head to hit a switch on the X axis in the right sequence to switch filaments. Maybe you could do something like that with this quad gantry to switch from using the front print heads to the back.
Just thinking out loud..

@oliof The Jubilee looks like the best option for me, hopefully they have an active support group. I already have a corexy machine I may be able to adapt! Thank you!

@oliof
what other options are there for 4 color printing?
I'd rather have direct drive hotends (no bowden tubes).
I've dabbled with Kraken and 3D chameleon, but I think 4 separate print heads ready to print are the way to go.
Note: do not search for 'hash' on CGTrader.. !

@oliof
awesome, I will check that out!
Thanks!
Edit: That looks very cool, for sure.
I think two gantries would work better though.
One could completely move up Z and be out of the way while the other is being used to print, then vice-versa. With the hash style, all the print heads are at the same height, yes?

I see all the new IDEX printers out there.
Would it be possible to build one with TWO gantry's with two print heads on each? Independent Quad Extruder?

@rjenkinsgb
Lord have mercy I am embarrassed to say the problem was in my config.g file. I think I copy/pasted someone else's BLTouch settings and didn't update them for my own printer. It is working better now! Using this guide to set it up:
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

@rjenkinsgb
Thanks.
Does the probe have to be pressed in that far to send the signal? I assumed it would sense as soon as it touched something (IMMEDIATELY), not several mms of probe movement..

Is there a way to adjust the BLTouch sensitivity?
When I home Z it pushes it so much that my nozzles hit the bed.

@phaedrux
T3P3Tony mentions it here:
https://forum.duet3d.com/topic/25872/not-getting-data-from-filament-sensor/6?_=1641857602417

@phaedrux
Wow, I didn't even know there were different kinds.
I guess just a simple 'filament hasn't broken' type.
I was reading that you can't connect a filament sensor to the Duex5, you have to move your X and Y endstops over to it and use those for the other filament sensors.. correct?

I need to add 4 filament sensors to my Duet 2/Duex5 setup.
Are there some that work better with Duet than others?
Are the cheapies worth dealing with?
https://www.amazon.com/BIQU-Filament-Detection-Accessories-Extruder/dp/B08QJDSZCL?th=1
I just want something simple that works so I can get to printing.
Thanks!

@phaedrux
Can you try the other drivers on the Duex? Change the M584 to match the drivers being used. Is it all Duex drivers or just 8 and 9?

How do I do that? I thought I was supposed to be using drive5 and drive6, no idea why it is on 8 and 9. Not sure if that will make a difference.

Wait- I see what you are saying. In config.g.. I changed it to 5 and 6, will run tests.. Thank you

How do you have the power and ground for the Duex connected?

The same as in the picture of the link you sent, 14G jumper wires from the power in block of the Duet to the power in block of the Duex (checked for polarity)

@phaedrux
M122:

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DJM-9178L-L2MS8-6JKF0-3SN6Q-TTFYR
Used output buffers: 3 of 24 (15 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 75348 of which 44 recycled
Never used RAM 13228, free system stack 191 words
Tasks: NETWORK(ready,180) HEAT(blocked,314) DUEX(blocked,31) MAIN(running,449) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:36 ago, cause: power up
Last software reset at 2021-06-19 18:43, reason: User, GCodes spinning, available RAM 14616, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 24.5, current 29.9, max 30.3
Supply voltage: min 24.1, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0, standstill, SG min/max not available
Driver 6: position 0, standstill, SG min/max not available
Driver 7: position 0, standstill, SG min/max not available
Driver 8: position 0, standstill, SG min/max not available
Driver 9: position 0, standstill, SG min/max not available
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-06-21 15:55:38
Cache data hit count 116318905
Slowest loop: 6.51ms; fastest: 0.21ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.9ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.95ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(1) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.25
WiFi MAC address (hidden)
WiFi Vcc 3.32, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24792
WiFi IP address (hidden)
WiFi signal strength -73dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 4 2 0 0 0 0 0 0
=== DueX ===
Read count 1, 0.62 reads/min

M98 P"config.g"

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled

config.g

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue Jun 15 2021 20:08:38 GMT-0500 (Central Daylight Time)

; General preferences
G90                                                             ; send absolute coordinates...
M83                                                             ; ...but relative extruder moves
M550 P"TronXY X5SE-500 Pro"                                     ; set printer name
M669 K1                                                         ; select CoreXY mode

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

; Drives
M569 P0 S1                                                      ; physical drive 0 goes forwards
M569 P1 S1                                                      ; physical drive 1 goes forwards
M569 P2 S0                                                      ; physical drive 2 goes backwards
M569 P3 S1                                                      ; physical drive 3 goes forwards
M569 P4 S1                                                      ; physical drive 4 goes forwards
M569 P8 S1                                                      ; physical drive 8 goes forwards
M569 P9 S1                                                      ; physical drive 9 goes forwards
M584 X0 Y1 Z2 E3:4:8:9                                          ; set drive mapping
M350 X16 Y16 Z16 E16:16:16:16 I1                                ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E420.00:420.00:420.00:420.00          ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00:120.00:120.00:120.00        ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00:1200.00:1200.00:1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00:250.00:250.00:250.00        ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800:800:800:800 I30                        ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                                         ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                                                ; set axis minima
M208 X500 Y500 Z600 S0                                          ; set axis maxima

; Endstops
M574 X1 S1 P"xstop"                                             ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop"                                             ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2                                                      ; configure Z-probe endstop for low end on Z

; Z-Probe
M558 P1 C"zprobe.in" H5 F120 T6000                              ; set Z probe type to unmodulated and the dive height + speeds
G31 P500 X0 Y0 Z2.5                                             ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20                                        ; define mesh grid

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138                  ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                                           ; create bed heater output on bedheat 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"e0temp" Y"thermistor" T100000 B4138                   ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1                                            ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00                                                ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                                    ; set temperature limit for heater 1 to 280C
M308 S2 P"e1temp" Y"thermistor" T100000 B4138                   ; configure sensor 2 as thermistor on pin e1temp
M950 H2 C"e1heat" T2                                            ; create nozzle heater output on e1heat and map it to sensor 2
M307 H2 B0 S1.00                                                ; disable bang-bang mode for heater  and set PWM limit
M143 H2 S280                                                    ; set temperature limit for heater 2 to 280C
M308 S3 P"duex.e2temp" Y"thermistor" T100000 B4138              ; configure sensor 3 as thermistor on pin duex.e2temp
M950 H3 C"duex.e2heat" T3                                       ; create nozzle heater output on duex.e2heat and map it to sensor 3
M307 H3 B0 S1.00                                                ; disable bang-bang mode for heater  and set PWM limit
M143 H3 S280                                                    ; set temperature limit for heater 3 to 280C
M308 S4 P"duex.e3temp" Y"thermistor" T100000 B4138              ; configure sensor 4 as thermistor on pin duex.e3temp
M950 H4 C"duex.e3heat" T4                                       ; create nozzle heater output on duex.e3heat and map it to sensor 4
M307 H4 B0 S1.00                                                ; disable bang-bang mode for heater  and set PWM limit
M143 H4 S280                                                    ; set temperature limit for heater 4 to 280C

; Fans
M950 F0 C"fan0" Q500                                            ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1                                                  ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500                                            ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1:2:3:4 T45                                         ; set fan 1 value. Thermostatic control is turned on

; Tools
M563 P0 S"Nozzle 1 (front left)" D0 H1 F0                       ; define tool 0
G10 P0 X0 Y0 Z0                                                 ; set tool 0 axis offsets
G10 P0 R0 S0                                                    ; set initial tool 0 active and standby temperatures to 0C
M563 P1 S"Nozzle 2 (front right)" D1 H2 F0                      ; define tool 1
G10 P1 X18 Y0 Z0                                                ; set tool 1 axis offsets
G10 P1 R0 S0                                                    ; set initial tool 1 active and standby temperatures to 0C
M563 P2 S"Nozzle 3 (back left)" D2 H3 F0                        ; define tool 2
G10 P2 X0 Y18 Z0                                                ; set tool 2 axis offsets
G10 P2 R0 S0                                                    ; set initial tool 2 active and standby temperatures to 0C
M563 P3 S"Nozzle 4 (back right)" D3 H4 F0                       ; define tool 3
G10 P3 X18 Y18 Z0                                               ; set tool 3 axis offsets
G10 P3 R0 S0                                                    ; set initial tool 3 active and standby temperatures to 0C

; Custom settings are not defined

; Miscellaneous
M575 P1 S1 B57600                                               ; enable support for PanelDue

I purchased the Duex5 from Filastruder on April 1st of this year (no foolin'!)

I notice on the bottom of the Duet2wifi the pinouts for motors are 1B1A2A2B, but the pinouts on the bottom of the duex5 are A+A-B+B-.. Two different pinouts?

I have two extra extruder motors on a Duex5 on drive 5 and 6.
When I try to run the test to see if they are working from this link:
https://duet3d.dozuki.com/Wiki/Test_axes_or_motors_individually
by using this code

M563 P2 D2
T2
G1 E10 F60

or

M563 P3 D3
T3
G1 E10 F60

I always get this error:

Warning: motor phase A may be disconnected reported by driver(s)8
or
Warning: motor phase B may be disconnected reported by driver(s)9

and nothing happens.

If I plug the same extruder motor back into E0 on the Duet2wifi and run the same test, it extrudes and tests properly.

Are the pinouts the same for each board?

@cthulhulabs
woah, that is definitely heavy duty..!
I can crimp the 4 pin that goes to the Duet board, what about the 6 pin that goes into the stepper motor..?

Does anyone have a source for heavy duty stepper motor wires, like 20AWG? Most I find are 22AWG

@droftarts
That makes sense, thank you!

Do you have to manually update config.g to add another extruder and hot end heater?
I followed the directions here but nothing changed:
https://betrue3d.dk/duet-wifi-adding-a-second-extruder/

@jens55
I was using 1.2A, but have lowered it to 800ma which seems to have helped.
I was just surprised these jumper wires melted, they are indeed dainty. I'll get some better cables! Sorry about all the confusion

@jens55
Would this be a better option? it says it is 14g
https://usa.banggood.com/1M-4pin-Stepper-Motor-Cable-XH2_54-Male-Compatible-For-3D-Printer-p-1118480.html