@jay_s_uk said in Bed PID tuning cycle adjustment:

Currently, tuning a bed can take forever and still fail at the end of it.
Can the number of tuning cycles be specified to reduce the time required?
The new algorithm is great for tools and look ahead regarding fan usage but is too complicated for beds with the old method being more than adequate.
Can the phase messages also be adjusted to remove reference to fans when tuning a bed?

I fully agree +1
It anoys me since > v3.2. that such a basic feature works now that bad.
For the tool/hotend it works great, no question, but for the bed heater maximal bad at least with insulation.

Has anyone successfully running the Reppanel at a Duet3?
I experienced the following problem. The display doesn't start (applying 24V to the Duet) when connected to the 5V supplied by the Duet - in my case just the connector IO_0.
When I reset the Lolin32 afterwards with it's reset button it works immediately like expected. When I plug/unplug the connector IO_0 it starts as well.
I can reproduce this with a spare Duet3 just supplying 24V and Reppanel connected.

It must have something to to with the rising 5V voltage of the Duet and the power on reset of the Lolin. The board just doesn't reset properly at boot-up.
I fixed it by applying 10uF to extend the time constant of the R-C combination for boot-up reset. Former 10k+1uF->0.01s, now 10k+10uF->0.1s.
Now it starts like it should...

Now my question - is there already a software reset at start-up or could an additional software reset be implemented?

@Phaedrux
Thank you!
Of course I understand the intention in that case and it makes sense....

@Phaedrux said in Tool Fan selector in Duet Web Control:

If it doesn't that could be a feature request.

This is the thing what I wanted to confirm from the both guys before me

@Phaedrux
Doesn't work, already tried... it hides only at the status page...

M563 P0 S"Extruder" D0 H1 F0:1 ; define tool 0

Ok, thanks for the hint this is indeed wrong.

What I don't understand is why I have two sliders at the dashboard then?
So typically TOOL FAN and F0 or the custom name for F0.
I want only one to be visible in that case then TOOL FAN as there is only one tool.

And this was also the question from the thread opener:

They both do the same thing but I can't remove either of them and still have a working fan

I can confirm this. It becomes visible (TOOL FAN) at the Dashboard when you switch the heater to active.
RepRapFirmware for Duet 3 MB6HC 3.2
Duet Web Control 3.2.0

; Tools
M563 P0 S"Extruder" D0 H1 F0:1               ; 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

; Fans
M950 F0 C"out9" Q200                         ; create fan 0 (print cooling fan) on pin out9 and set its frequency
M106 P0 C"Part Cooling" S0 H-1               ; set fan 0 custom name and value. Thermostatic control (H-1) is turned off

M950 F1 C"out7" Q500                         ; create fan 1 (hot end fan) on pin out7 and set its frequency
M106 P1 S1.0 H1 T45         		     ; set fan 1 name and value. Thermostatic control (H1) is turned on

Can anyone confirm that this is needed/works also for the Duet 3 with the MKS PWC?

Ok, got it... will delete or move it.

I found out whats the reason of getting it when I Home Y.

• If nothing else is wired besides the Y-Axis you will get all the time this warning. So i assumed it must be Y related even showing Z.
• If you don't know that a Y movement results also in a short Z move/lift you end up with not understanding whats going on...
• In my case even a Duet Maestro connected before at this build stage without warning.

-> Hooked up also a Z Motor and the warning is gone.

@bearer
I posted that here as maybe something is wrong with the number indication at the warning where DC42 assumed the thread opener is talking about Z - I assume he never talked about z axis...

With your explanation it makes even more no sense with the warning.

I will delete or shift the post if it is a big problem.