@kaj
I'd choose the DM542 driver, it superseeds the TB6600 and isn't much more expensive.
The TMC drivers are very quiet, but their configuration (either jumpers or UART/SPI) can be difficult.

Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

@dc42 said in Duet2 wifi + Duex5 board thermistor issue:

version

yeah, I saw the beta version, I just went with the latest stable release. I'll have to remember that for when I upgrade.

@gixxerfast said in BL Touch not working:

Which version of RRF are you using, ver 2? I can't see that you've mentioned it.

EDIT: OK, so you're using RRF 3.3

Then I think you should config the BLTouch differently:

Have you read this bit, "Software setup (RepRapFirmware 3)" for the https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe

Either I'm a sloppy reader or I can't see that you have the M950

AS in this example:
2. Create a GPIO/Servo pin index using your chosen control pin, for example:

M950 S0 C"io7.out" ; Duet 3 MB6HC
M950 S0 C"io3.out" ; Duet 3 Mini 5+
M950 S0 C"exp.heater3" ; Duet 2 WiFi/Ethernet
M950 S0 C"duex.pwm1" ; Duet 2 WiFi/Ethernet + DueX2/5
M950 S0 C"!exp.heater6" ; Duet 2 WiFi/Ethernet + BoB
M950 S0 C"zprobe.mod" ; Duet 2 Maestro

Thank you, that did the trick! I must have overseen that section and used outdated sources. There are so many out there, you don't see the wood for the trees.

Also my deployprobe.g and retractprobe.g files referenced P7 rather than P0 as was mentioned in one of the guides. But these files reference the probe input rather than the heater, so P0 is the correct setting.

These are the correct settings and corresponding files:

config.g

; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Clayster" ; set printer name M302 P1 ; enable cold extrusion for clay printing ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; X1 M569 P1 S1 ; Y (reversed) M569 P2 S0 ; Z1 M569 P3 S1 ; E0 (Extruder, reversed) M569 P4 S1 ; E1 (Ram, reversed) M569 P5 S0 ; Z2 M569 P6 S0 ; Z3 M569 P7 S0 ; X2 M569 P8 S0 ; Z4 M569 P9 S0 ; n/a M584 X0:7 Y1 Z2:5:6:8 E3:4 ; remap motors M350 X16 Y16 Z16 E8:16 I1 ; configure microstepping with interpolation M92 X100.00 Y100.00 Z1600.00 E1000.00:1000.00 ; set steps per mm M566 X500.00 Y500.00 Z20.00 E1000.00:500.00 ; set maximum instantaneous speed changes (mm/min) M203 X5000.00 Y5000.00 Z600.00 E6000.00:400.00 ; set maximum speeds (mm/min) M201 X150.00 Y200.00 Z500.00 E1000.00:500.00 ; set accelerations (mm/s^2) M906 X1200 Y1200 Z500 E2000:2000 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; set idle timeout ; Axis Limits M208 X0:390 Y0:365 Z0:350 S1 ; 390mm x 365mm x 350mm ; Bed leveling geometry & leveling M671 X470:470:-70:-70 Y400:-40:400:-40 S20 ; position leadscrews (S = adjust max.) ; Endstops M574 X1 S1 P"xstop+e0stop" ; configure active-low endstop for 2 X-motors M574 Y1 S1 P"ystop" ; configure active-low endstop for low end on Y via pin ystop ; Filament sensor for Ram M591 P1 C"e1stop" S1 D1 ; extruder (Ram) endstop ; Z-Probe (capacitive sensor) ;M558 P5 C"^!zprobe.in" I1 ; default travel (5mm) ;G31 P1000 X0 Y0 Z0.475 ; Z = offset (greater value = closer to bed) ; Miscellaneous M575 P1 S1 B57600 ; enable support for PanelDue ; Tool 1 (Ram 80mm) M563 P1 D0:1 S"80mm" ; enable tool 1 and extruder E0 (D0) & E1 (D1) M567 P1 E1.00:0.03200 ; mixing ratio (77% more volume) G10 P1 S0 R0 X0 Y0 ; axis offsets for extruder G10 P1 R0 S0 ; set extruders active and standby temperature to 0 Celsius ; Tool 2 ("Pause") M563 P2 D1 S"Pause" ; retract ram motor when ram endstop is triggered ; Enable moving of axes before homing M564 H0 S1 ; S0 = move beyond axis limits, H0 = move without homing ; BL Touch M950 S0 C"duex.pwm5" ; assign heater 7 on the Duex5 to BL touch M558 P9 C"^zprobe.in" H5 F500 T6000 ; P = Z probe type 9, H = dive height, F = speed G31 P25 X0 Y-36 Z0.0 ; Z probe trigger value, offset in relation to nozzle

deployprobe.g

M280 P0 S10

retractprobe.g

M280 P0 S90

Thank you for your help! You made my day!

@honeycris said in Blew a fuse! replacing 7.5A fuse for 10A (Duex5)?:

Got it. And that is because the SSR is controlled by the board but the power from the PSU doesn't run through the board, rather it runs through the SSR?

Correct.

@honeycris said in Blew a fuse! replacing 7.5A fuse for 10A (Duex5)?:

Sorry for the basic questions. I am learning...

We all start at zero. 😉

@dc42 said in Servo on a Duet 2 Wifi + Duex5:

280 P0 S100

Ok, sorry to come back to this post so late but I had other issues and I could not test further...

Now I managed to free other 3 heater ports on the Duex, so I got rid of the buck converter as I could connect all 4 servos to 4 pwm ports on the Duet.
Nothing works anymore.

I tried also this configuration but nothing... The only visible thing that happens when I invoke a M42 or M280 command is that the corresponding heater led lights up (and remains up). So, it could be that the ports do not deliver the 5v? Before, using only the signal pin they worked with an external 5v supply...

can you please share your config? this can help me too

@JDigglyWiggly I did it out of sympathy for a dad with 3 kids under 10.

I found the error, i got the firmware from a friend and he used a Chamber heater that is allways on. I turned it off and everything is fine now

It seems I have not read the docs as good as I thought. The L Parameter of the M106-Command fixes my problem. This is the minimum Power for this fan.

M950 F1 C"duex.fan8+^duex.pb6" M106 P1 C"HeatSinkFan" S0 H1 T45 L255

I found this out when investigating the fan status by running M106 P1. It only turned with 50% power.

I solved the Problem 😄

You have to PullUp the Pin than it will work.

Depending on the current needed you can use both options and still draw the power from the external 12v supply.

Both the fan and heater output is switched on the low side, so you can wire the LED+ to your 12V supply and the LED- to the - of either the fan or heater output and have it work just the same.

A inline fuse is always a good idea when you're circumventing the Duets fuse, other than that LEDd don't require any safety precautions.

I solved it, didnt read enough... The Duex5 inverts the signal depending on how you name the pin in firmware...
The spam bot wont let me change the first post anymore I guess

"Sometimes a pin has multiple names.

Example:

"exp.heater3"
"exp.8"
"duex.e2_heat"
"duex.pwm1"
These four all refer to the heater3 pin, either on the expansion connector (where it is pin #8 of 50) or on the heater output terminal block of a DueX2 or DueX5. However, there is a difference. The DueX boards buffer and invert the signal. Therefore, when you use one of the forms prefixed with duex the firmware knows it has to invert the signal, but it doesn't invert it if you use one of the other forms. In contrast, when you referred to logical pin 3 in previous versions of RRF, the firmware always inverted the signal - so if you were driving a servo or BLTouch from this pin you would have needed to use the I1 parameter in your M280 command."

It's already mentioned at https://duet3d.dozuki.com/Wiki/Duex_wiring_diagrams#Section_Warnings_and_Cautions.

Thanks for the quick response. I made a couple of test leads and measured a good 3.3V between the 3.3V, TWD, and gnd. However when I measured TWC, twice, it registered only 136mV. The Duex5 has been swapped and although much longer than the provided ribbon cable, I had an old 50 pin SCSI cable which I tried with the same negative result. So I assume that would point to a problem with the Duet-wifi card.
Thanks

@bearer Thanks for the info.
Added and moved a jumper, powered on and nothing went bang or started smoking.
Just need to wire my LEDs now and test again.

Thanks again.
Paul.

It's a typo, it should say E2-E6 heaters, not E2-E7.

@flux said in Connect servo motor to Duet2Wifi with Duex5:

i can use a servo OR a heater, but don't booth a same time on a same channel?

Correct.

@dc42

it fixed the issue with RC4