duet2, firmware 3 --> bed and 1 heater on TEVO little monster
-
Hi, why can't I find my bed and heater after Firmware 3 for Duet2? I used https://configtool.reprapfirmware.org/Start
Can you help me? Thank you
; Drives
M569 P0 S1 ; physical drive 0 goes forwards
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 X80.00 Y80.00 Z80.00 E837.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z1200.00 E1200.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z18000.00 E1200.00 ; set maximum speeds (mm/min)
M201 X1000.00 Y1000.00 Z1000.00 E1000.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 Z0 S1 ; set minimum Z; 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 S1 P"zstop" ; configure active-high endstop for low end on Z via pin zstopM950 H3 C"nil" ; Disable heaters h3-h7 to free up pins
M950 H4 C"nil"
M950 H5 C"nil"
M950 H6 C"nil"
M950 H7 C"nil"; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H6 F200 T2000 ; set Z probe type to bltouch and the dive height + speeds
M557 R150 S20; 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
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M307 H0 B0 S1.00 ; disable bang-bang mode for the nozzle heater and set PWM limit
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
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M307 H1 B0 S1.00 ; disable bang-bang mode for the nozzle heater and set PWM limit; 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 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
; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power lossM501
-
@RafB This is a stock output from the RRF config tool to compare:
; 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 M143 H0 S120 ; set temperature limit for heater 0 to 120C 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 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 M143 H1 S280 ; set temperature limit for heater 1 to 280C M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; 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 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 0CBut mainly you need
M140 H0and to uncomment your Tools section.Ian
-
@droftarts said in duet2, firmware 3 --> bed and 1 heater on TEVO little monster:
But mainly you need M140 H0 and to uncomment your Tools section.
IanThank you
I've tried to add M140 but still got nothing. See the screenshotI don't understand where this is coming from and how to find my mistake.
Thank you for any help.
-
@RafB prior to RRF3, H0 was by default, the bed heater. Since RRF 3, it is not and you have to explicitly define it using M140 H0. Are you sure that you put that command in your config.g and saved it? BTW that's H zero not the letter "O".
-
Thank you for your help.
Droftarts, I forgot to uncomment the tools, it works...I have a new problem that I don't understand at the moment.
After a home, I get this message
-
Post your homing files.
-
Hi,
; homedelta.g
; called to home all towers on a delta printer
;
; generated by RepRapFirmware Configuration Tool v2.1.5 on Thu Jan 09 2020 14:51:14 GMT+0100 (CET)
G91 ; relative positioning
;*** Slow homing has been configured. Change F180 to F1800 below when your configuration is working
G1 H1 X705 Y705 Z705 F1800 ; move all towers to the high end stopping at the endstops (first pass)
G1 H2 X-5 Y-5 Z-5 F1800 ; go down a few mm
;*** Slow homing has been configured. Change F180 to F360 below when your configuration is working
G1 H1 X10 Y10 Z10 F360 ; move all towers up once more (second pass)
;G1 Z-10 F6000 ; move down a few mm so that the nozzle can be centred
G90 ; absolute positioning
;G1 X0 Y0 F6000 ; move X+Y to the centre -
How are you homing when that message happens? From the DWC? Sending G28 in a gcode file?
Can you evoke it again by sending those lines from homedelta manually in the console?
-
@Phaedrux said in duet2, firmware 3 --> bed and 1 heater on TEVO little monster:
How are you homing when that message happens? From the DWC? Sending G28 in a gcode file?
Can you evoke it again by sending those lines from homedelta manually in the console?Hey, guys,
I'm doing a G28 and then I want to put my head down, that's when the message comes.
When I send a gcode file with G28, it works perfectly.
-
@RafB said in duet2, firmware 3 --> bed and 1 heater on TEVO little monster:
I'm doing a G28 and then I want to put my head down, that's when the message comes.
What do you mean by "I want to put my head down,"?
If you press the homeall button in the DWC does it work without error?
-
@Phaedrux said in duet2, firmware 3 --> bed and 1 heater on TEVO little monster:
What do you mean by "I want to put my head down,"?
If you press the homeall button in the DWC does it work without error?Okay, I just figured it out and everything seems to be working fine.
I was trying to shoot my hothead but I pressed +0.5mm and when I pressed -0.5mm I got the same message.
On the other hand if I do Home(G28) and I press -0.5mm my hothead goes down correctly.Sorry, rookie mistake...
-
Glad you figured it out.
-
@Phaedrux said in duet2, firmware 3 --> bed and 1 heater on TEVO little monster:
Glad you figured it out.
I wanted to run a print but I still have to put G31 Zx.xx (0.88mm).
I don't understand the difference between Firmware 2 and 3.Can you advise me on this point here? J'ajoute simplement la ligne à Z-probe?
G31 Z0.88Actuel z-probe
; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H6 F200 T2000 ; set Z probe type to bltouch and the dive height + speeds
M557 R150 S20 -
There is no example in the firmware3 wiki. Complicated for a beginner like me
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_G31
-
@RafB Refer to the main gcode dictionary: https://duet3d.dozuki.com/Wiki/Gcode#Section_G31_Set_or_Report_Current_Probe_status
Put it in your config.g. eg
; Z-Probe M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch M558 P9 C"^zprobe.in" H6 F200 T2000 ; set Z probe type to bltouch and the dive height + speeds G31 P500 X0 Y0 Z0.88 ; set Z probe trigger value, offset and trigger height M557 R150 S20This is where you put your probe XY offset, too. You can use the RRF config tool to produce example code: https://configtool.reprapfirmware.org/
Ian
-
@droftarts Thanks a lot!
I would like to know if it is possible to change the shrinkage values during printing?
-
@RafB You can use https://duet3d.dozuki.com/Wiki/Gcode#Section_M579_Scale_Cartesian_axes for scaling. However, I don't know the effect of doing this during a print.
Ian
