Why the heaters are indicated by the letter "E" in the "Cooling fans" interface? Indeed, in all other places in the interface and in the associated G-code commands, the heaters are designated by the letter "H"...
Is there any logical mnemonic for this?

@fcwilt said in Why are heaters marked with the letter "E"?:

Do they normally have an associated cooling fan?

I do not know. I have a printer without a thermal camera; I just gave an example that the heater is not always an extruder.
Thermal chamber fan - it is possible that it is necessary. Hot air rises, and the temperature must be equalized throughout the chamber, so I think the air will have to be mixed, especially in printers with a large working volume. I have seen printer designs with a heat chamber and a fan embedded in the top panel.

@patrickwjoyce , try starting your macros (homex.g, homey.g, homez.g) with command
M400 S1 ; wait until motion stops, do not release any axes or extruders

@dc42 , After installing the new MB6HC binary from the link you provided, the problem was completely resolved. THANK YOU SO MUCH!

@chrishamm , Many Thanks!

@chrishamm , Thank you! Here is a link to my config file and Gcode file

The process of printing the part is carried out absolutely normally, the process is completed without any errors.

After upgrading from version 3.5.2 to version 3.5.3, the file simulation process runs infinitely. My configuration after upgrade:

As usual, I start the simulation process for a part that was previously successfully simulated in version 3.5.2:

After a while, a pop-up window about the end of the simulation process with information about the results is shown at the bottom of the screen.
After a while or by clicking the mouse, the window is hidden - up to this point, everything works correctly.
But after that:

1. The screen says that the simulation is 100% complete
2. The "Pause Simulation" button is still displayed, which should only be displayed during the simulation process.
3. The "Slicer" counter continues to count down, its value continues to decrease.
4. The "Current Layer Time" counter continues to count, its value continues to increase.
5. The "Job Duration" counter continues to count, its value continues to increase.
   

If you go to the "Jobs" section at this time, you cannot start the simulation of another part by right-clicking.

@Falcounet , thank you very much for your quick response! Please tell me what changes should be made to DSF config and how this can be done? Maybe there is a link to the description?
Is it possible to give the plugin the necessary rights by changing the manifest of the ExecOnMcode plugin before installing it in the DWC interface (https://github.com/Duet3D/DuetSoftwareFramework/blob/master/PLUGINS.md#list-of-permissions, "SuperUser" )?
P.S. I have extensive experience in IT, but practically no experience with *nix systems...

@jay_s_uk , many thanks! I didn't know about this possibility.
I tried it and it worked!

Re: ExecOnMcode
Hello!
I'm using Duet3HC + SBC Raspberry Pi3
I deployed the Duet3-Lite image (v.3.4.6 from 09/06/2023, taken from https://github.com/Duet3D/DuetPi) to MicroSD, configured the network, and restored the configuration files of my printer.
Then I installed the ExecOnMcode plugin (ExecOnMcode-0.5.zip) in DWC exactly according to the instructions https://plugins.duet3d.com/plugins/DSF_ExecOnMcode_Plugin.html,
including creating the file /etc/sudoers.d/010_dsf-nopasswd and writing dsf ALL=(ALL) NOPASSWD: ALL in it

Restarted Duet3HC+SBC
Launched the ExecOnMcode plugin in DWC
I edited the M1201 command and specified 'sudo reboot' in it

In the console DWC I executed commands M1200 and M1201 sequentially.
Raspberry did not restart.

The lines appeared in the log:
Duet3 kernel: audit: type=1400 audit(1701354925.815:8):apparmor="DENIED" operation="capable" profile="/opt/dsf/plugins/ExecOnMcode/" pid=820 comm="sudo" capability=7 capname="setuid"
Duet3 kernel: audit: type=1400 audit(1701354925.815:9): apparmor="DENIED" operation="capable" profile="/opt/dsf/plugins/ExecOnMcode/" pid=820 comm="sudo" capability=6 capname="setgid"

What should I do to be able to use the plugin to run "sudo reboot" and "sudo poweroff" with M-Code commands?

P.S. IMHO, it would be useful for many users if you added one more example to the two existing example commands that appear after installing the plugin: a command using sudo. For example, "sudo reboot".

@engikeneer said in PSU dedicated temperature control channel?:

I think it defaults to 100% (I've never specified the x parameter before) but can't hurt to define it like that

Many thanks! I think even such a configuration will be enough for most applications.
In any case, it is much (MUCH!) better than what is offered by the manufacturer in PSU industrial standards!

@engikeneer , THANKS A LOT! How do you think it is necessary to use the "X" parameter in the M106 command? For example,
M106 P3 L0.40 X1.00 T40:65 B1.0