M591 D0 S0 not reporting data to console

Macgyver

Good Day all I am trying to configure a clog sensor, (wheel with optical sensor)

As the filament is moved through the sensor the red light is pulsing on and off, the light on the mainboard (e0stop) is also pulsing so I am ruling out wiring at this point

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.2 (2024-06-11 17:13:43) running on Duet WiFi 1.02 or later + DueX5v0.11
Board ID: 0JD2M-9F8TA-GJ4TJ-6JKFD-3S86J-1RVL6

=== Filament sensors ===
check 3133587 clear 336281503
Extruder 0 sensor: ok

Config.g file
; Primary hotend Clog detector__________________________________________________
M591 D0 P7 C"e0stop" S1 L3.14 E10 R10:300 ; Clog Detector E0 [Add-On]

Using just the above configuration whenever I try to print I get the following message

9/26/2024, 2:25:15 PM Printing paused at X373.9 Y183.9 Z1.0 U675.0
9/26/2024, 2:25:07 PM No filament or possible clog on E0 - Paused
Resume state saved

Next I tried to enable reporting on the clog sensor
M591 D0 S0

Console is just showing no data,
I moved the sensor over to e1stop and updated config just to eliminate a bad port on the board, Same results.

Does anyone have any suggestions to be able to see the data being captured by the clog sensor?

dc42

@Macgyver the S0 parameter disables the filament monitor. If you send just M591 D0 then it should report the current status to the console.

Macgyver

@dc42 HI DC

thanks for your reply, I apologize I put the incorrect command in the description,

That is the command I was running and not the M591 D0 S0

The command I did run was the M591 D0

Macgyver

@dc42 Let me ask a question, does this command report continuesly back to the console or only report once per entry? I realize now it is returning a response once per entry of the M591 command. I seem to remember it would give the results back every time there was a pulse in a previous firmware rev?

Was this ever the case or am I not remembering something correctly?

dc42

@Macgyver it's only ever returned one reply. However, you can view the state of the filament monitor in the Object Model Browser within DWC.