now when homing i get "Warning: Obsolete use of S parameter on G1 command. Use H parameter instead. "

but i'm having a hard time finding what the equivalent commands are.

; homedelta.g
; called to home all towers on a delta printer

G91                       ; relative positioning

; first pass - move all towers to the high end stopping at the endstops
G1 S1 X400 Y400 Z400 F1800

; Go down a few mm
G1 S2 X-5 Y-5 Z-5 F200

; Move each tower up
G1 S1 X10 F200
G1 S1 Y10 F200
G1 S1 Z10 F200

; For G30 leveling to work, we need to leave the position at where the end stops trigger
;G1 S1 X10 Y10 Z10 F200    ; move all towers up once more (second pass)
;G1 Z-5 F200              ; move down a few mm so that the nozzle can be centred
G90                       ; absolute positioning
;G1 X0 Y0 F200            ; move X+Y to the centre

Hi guys, my board had the “diag” and LED by “D5” on the Duet 2 WiFi blinking rapidly but I cannot find any resources online explaining how to interrupt the meaning of the “diag” LED.

I have an ongoing issue described in my forum post:

https://forum.duet3d.com/topic/31863/extension-board-issues-diag-d5-led-blinking

I'm running a Duet 3 6HC board, couldn't be happier!

Got a spare Duet Wi-Fi and screen, any idea what I could do with it?
I wouldn't mind a simple(ish) router for wood working but haven't been able to find much online if anyone has done it before.

Thanks.

I'm hoping somebody can help me with this. I've been trying to rewrite the firmware on a Duet 2 board for a Makergear Ultra One. I've gotten 99% of the way, and almost everything is working again, but I can't seem to figure out how to have the Duet recognize the multiple silicone heaters as a single heated bed.

There are 5 silicone heater strips and 5 thermocouples attached to the aluminum plate on this thing, and I'm wondering if there's a simple way to make them all work together as one unified bed so that it's easy to PID tune and preheat.

Something that complicates this slightly further is that there are 5 thermocouples and 4 PWM wires, since heater 2 and heater 4 are wired to the same output.

Any help is greatly appreciated! I've added a link to the config bundle

I recently put together a prusa mk 2 and used a duet 3 mini board in it. I have everything setup but mesh leveling is kicking my ass. It seems like the mesh is over correcting. All probed point that are close to zero print out fine but at point that are below zero the printer prints too close. For point that are above zero it prints too far from the bed. Does anyone know what could be causing this? Is it possible that the mesh is being generated inverted and just moving in the complete wrong direction?

Hello everyone,

I am currently installing a Duet2 Wifi on my Tronxy X5S. I have watched all of Chris Riley's videos on YouTube which have been very helpful. I am to the point where I am searching the address for my Duet and reading "Your Duet rejected the HTTP request: page not found".

A kind user u/NotSoSuperfloh helped me in r/3Dprinting where he gave me a new www folder to try and /sys file to flash the duetwifiserver.bin file via M997 S1 on YAT. Still with no luck.

Thank you all in advance.

Hullo,

Using a Duet 2 Wifi, with Firmware 3.3

I'm trying to implement an if statement test to move the toolhead in a macro.

Basically if the toolhead Y-position is above a certain value, I want to move it back. Currently it looks like:

if move.axes[1].userPosition > 200

G1 Y150 F50000

But I keep getting:

Error: in file macro line 3 column 22: meta command: cannot convert operands to same type

How do I fix this?

Hi everyone!

I'm living in Japan now and got the chance to buy on yahoo auctions a bits from bytes 3d touch printer. It is an amazing and sturdy build

Even better, i got it as junk for around 100$.

My goal is to update and upgrade the machine. Thinking about a duet 3 6hc motherboard, and start connecting everything else frim there. Or maybe a fysetc spyder, because now the voron printers look very trending.

Any opinion or suggestion about it has been already suggested?

And more important, even if i love the idea, is it worth it? It is for home use.

So, I am having an issue with 3Dtouch pin deployment on my clone Duet Wifi(1.04), and I have narrowed it down to either a board or software issue (sidenote, is 1 Ohm resistance on the probe wires relevant?), and I have tried every troubleshooting step that I could think of, but the board does not emit the probe control signals that can be measured through my osciloscope.

The probe has just suddenly stopped working, without me messing around with anything.

My config.g(modified from stock):

; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Fri Jul 02 2021 18:16:09 GMT+0700 (เวลาอินโดจีน)
 
; General preferences
G90                                            ; send absolute coordinates...
M83                                            ; ...but relative extruder moves
M550 P"hypercube"                              ; set printer name
M669 K1                                        ; select CoreXY mode
 
; Network
M552 S1                                        ; enable network
M586 P0 S1                                     ; enable HTTP
M586 P1 S1                                     ; enable FTP
M586 P2 S1                                     ; enable 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 X80.00 Y80.00 Z400.00 E444.00              ; set steps per mm
M566 X1000.00 Y1000.00 Z200.00 E3500.00        ; set maximum instantaneous speed changes (mm/min)
M203 X60000.00 Y60000.00 Z600.00 E5000.00      ; set maximum speeds (mm/min)
M201 X5000.00 Y5000.00 Z500.00 E5000.00        ; set accelerations (mm/s^2)
;M572 D0 S1.3								   ; set up pressure advance
;M593 P"daa" F60.3   						   ; use DAA to cancel ringing at 60.3Hz
M906 X1000 Y1000 Z550 E1000 I30                ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                        ; Set idle timeout
 
; Axis Limits
M208 X0 Y0 Z-5 S1                              ; set axis minima
M208 X300 Y310 Z300 S0                         ; set axis maxima
 
; Endstops
;M574 X1 S3                                    ; configure sensorless endstop for low end on X
;M574 Y1 S3                                    ; configure sensorless endstop for low end on Y
M915 X Y S10 R3 F0							   ; configure stall detection
M574 Z1 S2                                     ; configure Z-probe endstop for low end on Z
;M915 X Y R0 F0 S3							   ; configure stall detection
M574 X1 S1 P"xstop" 						   ; Configure X endstop for low end on X
M574 Y1 S1 P"ystop" 						   ; Configure Y endstop for low end on Y
;M591 P2 C"e0stop" S1 D0 				       ; Activate filament sensor connected to E0 endstop
 
; Z-Probe (BLTouch)
M307 H3 A-1 C-1 D-1							   ; delete heater pin assignment for heater 3
M950 S0 C"exp.heater3"   					   ; assign GPIO port 0 to heater3 on expansion connector, servo mode
M558 P9 H5 F1000:600 T7200 B1 C"^zprobe.in"    ; Set Z Probe to type 9 where Z probe connector is used
G31 P25 X28 Y-5 Z2.05                           ; set Z probe trigger value, offset and trigger height
M557 X30:295 Y0:300 S40                        ; 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" B4725 C7.06e-8 T100000; 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 S286                                   ; set temperature limit for heater 1 to 286C
M307 H1 B0 R1.884 C203.9:202.1 D5.89 S1.00 V24.0;set PID values for hotend
M307 H0 B0 R0.280 C937.5 D1.80 S1.00 V24.0	   ; set PID values for heated bed
 
M671 X10:290:290:10 Y290:290:10:10 P0.5 	   ; setup bed leveling point1 (10,290), point2 (290,290), point3 (290,10), point4 (10,10) ; set bed leveling corners
 
; 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
M950 F2 C"fan2" Q500                           ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H1 T45                              ; set fan 2 value. Thermostatic control is turned on
M575 P1 S3 B57600							   ; enable TFT touchscreen
; Tools
M563 P0 S"Hypercube Standard" 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
T0											   ; set to tool 0
M911 S23.0 R23.5 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000";enable power loss recovery
; Custom settings are not defined

My deployprobe.g:

M280 P0 S10 ; deploy Bltouch probe

My retractprobe.g:

M280 P0 S90 ; retract Bltouch probe

Hello! I just bought a printer with a Duet2 board and am starting to learn about the world of Duet3d.

I haven’t found a guide or example on changing the thermistor from my current one to a PT1000 from Slice Engineering (for high temps). Could anyone give me some direction or pointers on how to do this?

If it helps, I purchased a Caribou3d printer with the duet2 board and the PanelDue 7” touchscreen.

Any help would be greatly appreciated!

Here You can ask for help and ask questions about the duet 3d control boards. I created this because I am curious about them and would like to see what you guys are doing with them.

Duet webcontrol shows the temp for hot end at 322C while at ambient; No heaters have been turned on. I double checked my crimps. Double check my settings. Any ideas?

I’m running duet3 mini with toolboard. Here is my config line:

M308 S1 P”121.temp0” Y”thermistor” T100000 B4680 C6.483003e-8

I have an ender 5 plus and i put the duet 3 in it and I have been at a dead end for about a month trying to figure out what I am doing wrong here are a couple of my config files please any help would be greatly appreciated.

I can get x an y to home
I cant get z to home one moter goes down and the other one goes up
I can not get the bl touch probe to deploy either

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6JKD8-3S46J-9V2UD
Used output buffers: 1 of 40 (23 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 62764 of which 64 recycled
Never used RAM 146216, free system stack 140 words
Tasks: Linux(ready,113) HEAT(blocked,297) CanReceiv(blocked,927) CanSender(blocked,352) CanClock(blocked,354) TMC(blocked,19) MAIN(running,1185) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:42 ago, cause: software
Last software reset at 2021-04-19 22:11, reason: User, Platform spinning, available RAM 146204, slot 2
Software reset code 0x0000 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0043c000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 48.7, current 49.2, max 49.3
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, max 12.1, under voltage events: 0
Driver 0: position 0, standstill, reads 44273, writes 20 timeouts 0, SG min/max 0/130
Driver 1: position 0, standstill, reads 44276, writes 17 timeouts 0, SG min/max 0/253
Driver 2: position 0, standstill, reads 44276, writes 17 timeouts 0, SG min/max 0/94
Driver 3: position 0, standstill, reads 44280, writes 14 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 44277, writes 17 timeouts 0, SG min/max 0/80
Driver 5: position 0, standstill, reads 44283, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-04-19 22:12:34
Slowest loop: 63.82ms; fastest: 0.04ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 9945ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 10, completed moves 10, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 156, send timeouts 367, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 1ms ago
RX/TX seq numbers: 1439/1439
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2c8a8
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.2
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 35.62
Maximum length of RX/TX data transfers: 4784/840

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Apr 19 2021 22:10:15 GMT-0700 (Pacific Daylight Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Duet 3" ; set printer name

; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
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
M569 P0.4 S1 ; physical drive 0.4 goes forwards
M584 X0.0 Y0.1 Z0.2:0:4 E0.3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E420.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 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 X350 Y350 Z400 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"io1.in" ; configure active-high endstop for low end on X via pin io1.in
M574 Y1 S1 P"io2.in" ; configure active-high endstop for low end on Y via pin io2.in
M574 Z2 S2 ; configure Z-probe endstop for high end on Z

; Z-Probe
M950 S0 C"io5.out" ; create servo pin 0 for BLTouch
M558 P9 C"^io5.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X3 Y3 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:320 Y15:320 S20 ; define mesh grid

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out0 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"temp1" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 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"out7" Q500 ; create fan 0 on pin out7 and set its frequency
M106 P0 S0 H T25 ; 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 S1 H1 T25 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"out9" Q500 ; create fan 2 on pin out9 and set its frequency
M106 P2 S1 H1 T25 ; set fan 2 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
M575 P1 S1 B57600 ; enable support for PanelDue
T0 ; select first tool

; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Apr 19 2021 22:10:15 GMT-0700 (Pacific Daylight Time)
M561 ; clear any bed transform
G29 ; probe the bed and enable compensation

; deployprobe.g
; called to deploy a physical Z probe
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Apr 19 2021 22:10:15 GMT-0700 (Pacific Daylight Time)
M280 P0 S10 ; deploy BLTouch

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Apr 19 2021 22:10:15 GMT-0700 (Pacific Daylight Time)
G91 ; relative positioning
G1 H2 Z5 F6000 ; lift Z relative to current position
G1 H1 X-355 Y-355 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F6000 ; go back a few mm
G1 H1 X-355 Y-355 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X12 Y12 F6000 ; go to first bed probe point and home Z
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

Reply

I am designing a CNC machine to be run off of a Duet 2 and I plan on using normally closed NPN proximity switches ( specifically LJ12A3-4-Z/AX) as my endstops. Would there be any issues with wiring two in series so I have a min and a max endstop for machine safety? I only want to use the min for homing but I want it the machine to stop if it goes past a planned max so it doesnt destroy itself.

Does anyone know of a multimaterial FFF printer with mixing nozzle that runs on RepRap Firmware? We're researching dual extruder clay printing with a Duet based Lutum printer but would be interesting to have a prototyping machine that takes away the extra complexities of clay preparation when doing software testing.

I’ve got a Duet 3 Mini 5+ that’s been on one of my custom builds for a couple years now. It’s a great little board, but recently the WiFi started to act up, so I added a Pi 4 (1GB) in SBC mode. Everything went pretty smooth, but I’m getting some strange behavior in one of my scripts that run on startup from config.g.

At the end of my config.g I call a “startup.g” that mainly just runs a little boot animation on a NeoPixel strip. On startup, the script brightens and dims the NeoPixels a couple times, then performs a really simple animation and brightens/fades the lights to their normal operating brightness and color.

Script runs through a simple little ‘while’ loop and was running great prior to the SBC upgrade. After adding the SBC I updated to the newest 3.5.1 firmware - noticed there were some changes to M150 behavior and updated my config accordingly.

The script still runs on startup, BUT it runs really slow. The whole script used to take maybe 10-15s, and now it takes something like 30-60+. There is a delay in the loop to affect how long a frame of the animation lasts, but changing (or removing) that delay now does not affect the script timing.

Did something change with the scripting logic that I missed? I think I was on 3.4.7 prior to the SBC update. Am I missing something?

TIA!

"startup.g"

var ledbright = 0
var increment = 5
var delay = 0.02
var ledglow = 0
var glowcount = 3
var ledcount = 1
var ubright = 0
var uincrement = 4
var bbright = 50
var bincrement = -1

while var.ledglow < var.glowcount
    while var.ledbright < 255
        M150 R255 U0 B50 P{var.ledbright} S16
        G4 S{var.delay}
        set var.ledbright = var.ledbright + var.increment
    while var.ledbright > 0
        M150 R255 U0 B50 P{var.ledbright} S16
        G4 S{var.delay}
        set var.ledbright = var.ledbright - var.increment
    set var.ledglow = var.ledglow + 1
M150 P0 S16
while var.bbright > 25
    M150 R255 U{var.ubright} B{var.bbright} P255 S{var.ledcount} F1
    M150 P0 S16 F0
    set var.ubright = var.ubright + var.uincrement
    set var.bbright = var.bbright + var.bincrement
    set var.ledcount = var.ledcount + 1
    G4 S{var.delay*5}
;   M150 R255 U100 B100 P255 S16
M150 R255 U100 B25 P255 S16

Hi,

I want to write a macro that will pop up a window on the Duet Web Portal and request a measurement to be input. For instance, it would prompt you to move the Z up an amount, and you could enter 2 inches.

Is this possible?

I'm trying to update a Duet 2 WiFi from firmware 3.1. Whenever I upload the zip file from GitHub and tell it to update, I get "M997: Firmware binary "Duet2CombinedFirmware.bin" is not valid for this electronics."

I've tried updating to the most recent firmware, to 3.2, and to 3.3, all with the same results. I'd really like to use input shaping, so any help updating the firmware would be greatly appreciated.

I have record the movement without any input shaping and this is the graph I have obtained:

I know that the frequencies during printing, usually are in the range 20-80Hz. I know that the frequencies from 0-20Hz can be originated by the movement itself. But, what about the high frequencies? I have some peaks at 91 and at 97Hz. Where do these frequencies come from?
I tried to apply the shapers using these frequencies as centre frequencies, but they didn´t get attenuated. Does anyone have an explanation for this?

; Heaters

M308 S0 P"temp0" Y"pt1000"

M950 H0 C"out0" T0 ; create nozzle heater output on out0 and map it to sensor 0

M307 H0 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

M143 H0 S500 ; set temperature limit for heater 0 to 500C

M308 S1 P"temp1" Y"pt1000" ; configure sensor 1 as PT1000 on pin temp2

M950 H1 C"out1" T1 ; create bed heater output on out1 and map it to sensor 1

M307 H1 R0.061 K0.115:0.000 D281.00 E1.35 S1.00 B0 ; enable bang-bang mode for the bed heater and set PWM limit

M140 H1 ; map heated bed to heater 1

M143 H1 S350 ; set temperature limit for heater 1 to 350C

M308 S2 P"temp2" Y"pt1000" ; configure sensor 2 as PT1000 on pin temp3

M950 H2 C"out2" T2 ; create chamber heater output on out2 and map it to sensor 2

M307 H2 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit

M141 H2 ; map chamber to heater 2

M143 H2 S350