Its a 24v 220w creality bed.
Yes tested and voltage present. I cant see any damage other than the smell of something popped.
New board it is. Luckily i have a duet 3 to hand.
How do you think the mosfet failed ? Everything is crimped with a good few years of experience behind it and some pretty bouji crimpers. The board is only a year old . Its pretty suss with no route to a warrantied repair service
I have a cartesian machine running off a duet 2. No issue to date. I was printing some tpu with the bed at 55 degrees and the printer stopped printing a couple of minutes into the print .
Now each time i switch the printer back on the temperature climbs even if the bed temp is set to 0 degree.
Ive checked the wiring all seems ok and had not been touched or amended but i do smell some of that classic POP smell.
The 15amp blade seems all good.
What do you thing is going on ?
Thank you kindly. Works a treat on the X axis. Will give the adjustments positions a go also.
Ive added a G29 into the bed file after the probing as if it were a macro when I G32, Is this ok ? Prints are coming off nicely and bed seems very level after adjust from the mesh.
I only ask as I’ve never seen a Z adjust notification in commands.
Hello,
I have a cartesian bed slinger with a 310x320 bed. The z motors are independent and I’ve been wanting to implement G32 before i G29 so that the gantry is level before mesh bed levelling .
Ive whacked the leadscrew positions in (m671) and set the probing points in the bed file with g30 commands.
I was wondering where is best for me to probe. At the middle of the bed each side of the x gantry or probe at the adjustment screws in each corner
If the latter is the case, the probe cant reach the left side screws. What should i do in this instance
Regards
Iwan
Oh no bobbins.
Ill retrace my steps. I wouldn't say im 100% pcb literate but enough to say its likely goosed.
The printer still homes and is responsive via DWC. I’ll run a dry gcode and see its behaviour, report back
Would Duet recycle the board if i sent it back ?
Compared with another duet 2 wifi I have, L6 and L5 are blacked out and it expelled a waft of “component pop” in the air when switched on.
The Bl touch no longer lights up and is unresponsive, previously the Bltouch would probe test on start up.
Multi meter has confirmed that these have blown. Currently looking at schem to see what else has been affected.
I think its a goner.
No amendments have been made to the wiring over the past 24hrs. Sheathed the bltouch cable with some paracord and recrimped is all. Red to 5v, yellow heater 3, black / brown to ground, white in. The bltouch is a 3.0 and my understanding is that the duet 2 is 5v tolerant.
This is my 3rd duet on one of my printers and I know the pin out pretty well… I’d be surprised if I had “F upped”
Ive never had an issue with a film resistor blowing like this out of the blue but im absolutely bemused to how this has happened and the gradual degradation ive seen over the past few days
Is it worth sending it over for inspection?
@t3p3tony
Unfortunatley it became unresponsive shortly after. Ive attached a pic of the board below and it looks like L5&L6 has burnt out. Could you confirm ?
Wow. It was an inteference issue. Shielded the bltoch cable and now works fine
Thanks for your time
Oddly the same issues persist with the last known working config.
Will clean the probe and test out with another set of Bl touch wiring.
The wiring from bltouch follows the sam path as all the other wiring from my Hemera. Ive heard of interference issues but never had this issue in the past. But will isolate to make sure.
self test on start up works correctly
Side by side in notepad++ I cant see any differences but the pid values and the printer name.
Is there anything board side i should check for ?
@t3p3tony said in RFF 3.3 and unresponsive BLTOUCH:
M98 P"0:/sys/config.g"
Ye no other errors reported. This event is replied
M98 P0:/sys/config.g
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Yes it was the only parameters which were changed. Im really scratching my head on this one. Been through this list and reconfigured the probe following this
https://duet3d.dozuki.com/Wiki/BLTouch_Troubleshooting
https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_Software_setup_RepRapFirmware_Num_3
Will have a look at an old config
Hello
I recently made some amendments via the wizard to my config. (pid values) but had I've had issues with my BLtouch since. The initial self test on start up works perfectly fine however the pin does not self deploy when homed. M401 / M402 also do not take affect.
Im assuming its not an issue with wiring as the self test functions on start up and it functioned perfectly fine before uploading the pid updates. Signals fine
I've also tested with another Genuine BLTOUCH
Please find my homez/ deploy/retract/ configs below
Thank you
; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.3 on Thu Oct 07 2021 17:04:34 GMT+0100 (British Summer Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G90 ; absolute positioning
G1 X-51 Y14 F6000 ; go to first probe point
G30 ; home Z by probing the bed
; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F100 ; lift Z relative to current position
;G90 ; absolute positioning
; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.3.3 on Thu Oct 07 2021 17:04:34 GMT+0100 (British Summer Time)
M280 P0 S10 ; deploy BLTouch
; retractprobe.g
; called to retract a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.3.3 on Thu Oct 07 2021 17:04:34 GMT+0100 (British Summer Time)
M280 P0 S90 ; retract BLTouch
; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.3 on Thu Oct 07 2021 17:04:34 GMT+0100 (British Summer Time)
; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"My Printer" ; 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 S0 ; physical drive 0 goes backwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X160.00 Y160.00 Z1600.00 E409.00 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E900 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 X310 Y320 Z400 S0 ; set axis maxima
; Endstops
M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z
; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X66 Y1 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 B0 S1.00 ; disable 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 B4725 C7.06e-8 ; 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
; 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 T45 ; set fan 1 value. Thermostatic control is turned on
; Tools
M563 P0 S"HEMERA" 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
; Custom settings are not defined
@dc42 All sorted. Amazing platform. Amazing support.
@dc42 Hey
This is what I thought. The heater cartridge is on e0heat and the sensor is on e0temp. The heater parameters are also set to Semitic 104 gt.
The error I’m receiving is - temperature reading fault on heater 1: unknown temperature sensor channel
Will post up the config shortly
I’ve attached a pic of the board 
Am I being a total idiot ?
Hello
Just set up my duet and everything is working like a dream thanks to the great documentation provided. My last hurdle is the hot end temp read.
I’m running a hemera with a Semtec104. The hot end is connected to e0heat and the sensor is connected to e0temp. This is also reflected in the firmware. However my temps are at 2000c
Rereading the sensor documentation I clocked the use of the daughter boards. I’m now unsure wether this is required in order to use the Semtec sensor
I’ve ordered a p100 sensor and breakout board regardless as I intend to print at higher temps but could somebody shed light on wether a DB is required for the semtec heater or am I overlooking another detail.
Yet to pid tune as the reading was so far off
Appreciate your time