[BUG] M412 doesn't show the Host Action Command variable value

[Ari-SSO]

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

Trying to make the filament sensor work, I realized that there was no easy way to know the current value of the H parameter, because the M412 command that sets it, does not report its status, but it does with the rest of the parameters. Checking the source code I realized that it never reports that value.

If you run M412 without parameters, only the S and D parameters are shown (D is reported depending on whether the filament runout distance is activated, this is OK).

Example:
M412 S1 H1 D25
M412
Filament runout ON
Filament runout distance (mm): 25 (if FILAMENT_RUNOUT_DISTANCE_MM is defined)

I already sent a PR with the name "M412 now shows host action command value", it is my first time that I collaborate in this, please if something is wrong with the PR, the source code, or whatever, I ask you to let them know, so I avoid future mistakes.

New output:
M412 S1 H1 D25
M412
Filament runout ON
Host action command ON
Filament runout distance (mm): 25 (if FILAMENT_RUNOUT_DISTANCE_MM is defined)

Thanks!!!

Bug Timeline

No response

Expected behavior

M412
Filament runout ON (OFF if S=0)
Host action command ON (OFF H=0)
Filament runout distance (mm): 25 (if D=25 and FILAMENT_RUNOUT_DISTANCE_MM is defined, if not defined this line is not displayed)

Actual behavior

M412
Filament runout ON _(OFF if S=0)_
Filament runout distance (mm): 25 _(if FILAMENT_RUNOUT_DISTANCE_MM is defined)_

Steps to Reproduce

Run:

1. M412 H0 (or H1)
2. M412

Version of Marlin Firmware

2.0.8.2, 2.0.9, bugfix 2.0.x

Printer model

Generic Delta

Electronics

SKR 1.3, TMC2209, BTT TFT25 v3.0, Dual Nozzle Extruder, 1 sensor filament attached to the first extruder and connected to SKR 1.3.

Add-ons

No response

Your Slicer

Cura

Host Software

Repetier Host

Additional information & file uploads

No response

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.