I would like to have auto-scaling of temperatures graph - would make tracking lower temps easier.

Perhaps it would be also nice to have dual-scale - left scale for tools (usually higher range), right scale to heatbed/chamber (usualy lower range).

@EducatingSavvas

If state.gpOut[3].pwm==0
	M42 P3 S1
else state.gpOut[3].pwm==1
	M42 P3 S0

condition in else is obsolete, and more "elegant" way is

If state.gpOut[3].pwm != 0
	M42 P3 S0
else
	M42 P3 S1

It would be nice to have recursive delete for non empty directories.

Outstanding idea. I am located in Poland and have a reflow oven, hot air station (IMO more suitable to re-work jobs) and experiance in using it. I would be more than happy to fix some boards.

Probing twice the same point?

G30 P0 X26 Y226 Z-99999 ; probe near an adjusting screw
G30 P1 X26 Y226 Z-99999 ; probe near an adjusting screw

I think that viable solution would be to use NFC tags and a spool holder with reader. With new spool just put a nfc sticker (can be bought easily) and set a filament length when spool used for a first time.

Then each time spool in put on spoolholder read the tag, and update legth when print finished/tool change/ etc

Easy to implement - nfc readers are available with many intercaes, tags can be bought without problems.

Finally G10 support?
I wonder what are the actual changes in this new g code flavor.

https://github.com/prusa3d/PrusaSlicer/releases

Out of pure curiosity, I just checked on my printer (Duet3, standalone, 3.2-b1), and seems to be just fine.

@lui2004

G30 P0 X28.8 Y24 Z-99999 ; hinten rechts
G30 P1 X198.8 Y24 Z-99999 ; hinten links
G30 P2 X198 Y194 Z-99999 ; vorne links
G30 P3 X28.8 Y194 Z-99999 S4 ; vorne rechts and report adjustments needed

You missed P1

@Leav When You define z probe with M558 there are params:

Snnn Tolerance when probing multiple times, default 0.03mm

and

Annn Maximum number of times to probe each point, default 1.

This probes until results are within defined tolerance.

Not sure if this does averaging measurements tho

Commands executed during print.
console.txt

Seems there is some relation with bed heater and tool1:
https://www.youtube.com/watch?v=E9w-VdB8ghc

T1 state "blinks" with the same state as heatbed.
On video it is on stby, but making it active makes T1 blinking in red also.

And after pressing Emergency Stop:

@wilriker There is something strange going on in this firmware...

https://www.youtube.com/watch?v=_dw5heELJEw

@bmarkus108 I have bl touch and no issues on powder coated sheet. Do You use genuine one? Which version. I belive pin heat is bigger that the PEI grains on the sheet, but perhaps this is just on my setup.

@dc42 What about move number? They are not consecutive numbers. Is that OK? Was something executed Out-Of-Order ?

I am checking from time to time M122, and this one is particularly curious result (printing in progress):

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2-beta4.1 running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956L2-G43S8-6J1D6-3SJ6R-KA0YG
Used output buffers: 1 of 40 (26 max)
=== RTOS ===
Static ram: 123292
Dynamic ram: 170684 of which 112 recycled
Never used RAM 98104, free system stack 116 words
Tasks: NETWORK(ready,159) ETHERNET(blocked,103) HEAT(blocked,276) CanReceiv(blocked,947) CanSender(blocked,348) CanClock(blocked,349) TMC(blocked,18) MAIN(running,696) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 03:24:13 ago, cause: software
Last software reset time unknown, reason: User, GCodes spinning, available RAM 98312, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0x00
MCU temperature: min 39.1, current 39.2, max 39.4
Supply voltage: min 27.1, current 27.3, max 27.4, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
Driver 0: position 19983, ok, reads 22817, writes 0 timeouts 0, SG min/max 0/1023
Driver 1: position 28137, ok, reads 22817, writes 0 timeouts 0, SG min/max 0/1023
Driver 2: position 14970, ok, reads 22817, writes 0 timeouts 0, SG min/max 0/168
Driver 3: position 0, standstill, reads 22817, writes 0 timeouts 0, SG min/max not available
Driver 4: position 0, standstill, reads 22817, writes 0 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 22817, writes 0 timeouts 0, SG min/max 0/0
Date/time: 2020-12-14 12:34:38
Slowest loop: 5.90ms; fastest: 0.26ms
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.4ms, write time 0.0ms, max retries 0
=== Move ===
FreeDm 354 (min 344), maxWait 0ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 971089, completed moves 971030, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== 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 = 3 -1 -1 -1
Heater 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X91.461 Y150.354 E0.04368" 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 not empty:
Queued 'M106 S127.5�����������������������������������������������������' for move 971061
Queued 'M106 S76.55�����������������������������������������������������
' for move 971063
2 of 16 codes have been queued.
=== Network ===
Slowest loop: 14.15ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 5 2 2 2 2 2 0 0
=== Filament sensors ===
Extruder 0: pos 190.90, errs: frame 1 parity 0 ovrun 0 pol 0 ovdue 0
Extruder 1: pos 0.00, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0
=== CAN ===
Messages queued 20, send timeouts 44, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 47

@wilriker I am using dark theme 2

I will join this, as I bought second magnet filament monitor, and it barely works. Also I have:

Duet3D rotating magnet filament monitor v3 on pin io7.in, enabled, sensitivity 25.40mm/rev, allow 50% to 150%, check every 12.7mm, version 3, mag 126 agc 128, no calibration data

agc 128 I belive is the limit of this value. I tried to sand down an enclosure a little, but no luck.

@Trideo I am using 4 wire connection with genuine bltouch 3.1 without any issues, just connect grounds together, or just leave black not connected (they are connected on BL Touch board I belive).

Did anyone notice small dot's in corners, when screen saver is active? Are they suppose to be there?

@bearer There are mosfets on heaters and fan outputs, but not on IO ports. Unless... @kuon has OUT4-6 in mind wich are actually fan outputs, and I belive are open drain type on PWM pin, so they do not apply voltage by their own on that pin.

@kuon If You just want to use ordinary PC Noctua fan on 4 pin fan header OUT4-6 it will work.