Hemera temperature sensor.
Does this sensor require the expansion board if I have a Duet 3? I also have the Toolboard 1LC and distribution board, which aren't used at the moment. I am using a Hemera.
Otherwise, is there a recommended source for a sensor that actually works with the Duet 3 and an E3D Hemera without another chunk of hardware to mount somewhere?
oliof last edited by
@choblet I am using the Hemera and supplied thermistor with a toolboard. No issues.
it says Genuine Semitec 104GT thermistors used so that'll work as is.
jay_s_uk last edited by
thats just a standard thermistor so works out the box.
The temperature sensor which requires an adapter is a PT100 (for reference)
well played gentlemen!
@oliof, would you mind letting me know what your settings are for the stock thermistor just so I can have a reference in case I am still unable to get it working?
Thanks again for the help. I'll check back later and let you know if I figured anything out.
bearer last edited by bearer
Just click the input fields in the hotend section of the config tool and choose the Semitec 104 GT2 (E3D hotends) and it'll work with any (analouge) input on any Duet.
Resulting Coefficients: R25: 100000 Ω β: 4725 K C: 7.060000e-8
Unfortunately, that was not what I wanted to hear,
took a while to compute.
not all inputs on the duet3 can do analouge in ref: https://duet3d.dozuki.com/Wiki/Duet_3_Mainboard_6HC_Hardware_Overview#Section_IO
@bearer you mention the inputs on the Duet 3 not all having analog inputs...I am plugged into the temp0 (and have tried temp1). I'll obviously start trying other input options, but for my own knowledge, is the thermistor I am using incompatible with the temp inputs?
bearer last edited by bearer
I am plugged into the temp0
temp0-3 are all good; I was thinking about the IO_n.in not all of those can be used for temperatures.
if you have a multimeter, check that you measure about 100k ohm at the plug that goes into the board (when its not plugged in), if you don't then there might be an issue with the wiring.
then post your config and I'm sure one of the eagle eyed people here will spot any config issue
Got some results this morning and thought I'd share; I went through the steps to calibrate the hotend (which I'm pretty sure didn't actually work) and along the way read that I was using H0 for the extruder instead of H1, and once I made that change, boom. Temperature does exactly what it's supposed to, and now I...well, probably not quite ready for a test print, eh? I'll have to see what steps to take next.
I'm including my config file due to my lack of confidence in how I have things set up. There are a few odd, small things I have questions about, one being a warning about the printer name not matching that of the Linux host.
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.3 on Fri Jul 10 2020 07:45:40 GMT-0700 (Pacific Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"3dp" ; set printer name ; Drives M569 P0.0 S0 ; physical drive 0.0 goes backwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S1 ; physical drive 0.2 goes forwards M569 P0.3 S1 ; physical drive 0.3 goes forwards M584 X0.0 Y0.1 Z0.2 E0.3 ; set drive mapping M350 X16 Y16 Z32 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y400.00 Z400.00 E409.00 ; set steps per mm M566 X6000.00 Y6000.00 Z3600.00 E300.00 ; set maximum instantaneous speed changes (mm/min) M203 X12000.00 Y12000.00 Z12000.00 E1200.00 ; set maximum speeds (mm/min) M201 X900.00 Y900.00 Z900.00 E250.00 ; set accelerations (mm/s^2) M906 X850 Y850 Z900 E800 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 X120 Y120 Z300 S0 ; set axis maxima ; Endstops M574 X2 S1 P"!^io0.in" ; configure active-high endstop for high end on X via pin !^io0.in M574 Y1 S1 P"!^io1.in" ; configure active-high endstop for low end on Y via pin !^io1.in M574 Z1 S1 P"!^io2.in" ; configure active-high endstop for low end on Z via pin !^io2.in ; Z-Probe M558 P0 H20 F120 T3000 ; disable Z probe but set dive height, probe speed and travel speed M557 X15:85 Y15:85 S5 ; define mesh grid ; Heaters ;M570 S20 ; Print will be terminated if a heater fault is not reset within 20 minutes. M308 S0 P"temp0" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 0 as thermistor on pin temp0...I think ;M950 H0 C"out1" T0 ; create nozzle heater output on out1 and map it to sensor 0 M950 H1 C"out1" T0 ; try using H1 for the extruder heater. H0 typically bed heater M143 H1 S80 ; Maximum H0 (Extruder) heater temperature (low for testing) ;M307 H1 ; this is the heater tuning. Check output, adjust parameters M307 H1 A340.0 C140.0 D5.5 S1.00 V0.0 B0 ; Default Tool Heater Parameters...? ;Heater 1 model: gain 340.0, time constant 140.0, dead time 5.5, max PWM 1.00, calibration voltage 0.0, mode PID ;Computed PID parameters for setpoint change: P13.4, I0.482, D51.4 ;Computed PID parameters for load change: P13.4, I0.949, D51.4 ; Fans M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency M106 P0 S0 H T45 ; set fan 0 value. Thermostatic control is turned on M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off ; Tools M563 P0 D0 H1 S"Extruder" ; 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 G10 P0 S-273 R-273 ; Set tool 0 operating and standby temperatures(-273 = "off") ; Custom settings are not defined ; Miscellaneous M501 ; load saved parameters from non-volatile memory
ne being a warning about the printer name not matching that of the Linux host.
that just means your M550 name differs from the
/etc/hostnamein rasbpian. Simplest is to run
sudo raspi-configand change the hostname under the network settings.
M106 P0 S0 H T45 ; set fan 0 value. Thermostatic control is turned on
line 55 probably needs
@bearer This was the magic move that got things printing. Thanks for the assistance. I was able to get a few prints out of how it's currently set up before I hit some snags. Still working through those, but I just need to do some more troubleshooting before reaching out again.