Filament monitoring while printing via USB

chrishamm

@benecito See https://github.com/Duet3D/RepRapFirmware/issues/862

jaysuk created this issue in Duet3D/RepRapFirmware

closed [FeatureRequest]: M591 filament monitoring option for USB control #862

benecito

@chrishamm @jay_s_uk thanks for the suggestion! Just wanted to try it out, but did not even get that far as it's status stays at "ok" even if there is no more filament in the sensor and the print is paused on a sd print.
Also is there a limitation not documented if the filament monitor is connected to a CAN board (duet 3 mini slave)
I get information back when sending M591 but no calibration values and the print does not pause. It works when it's connected to the mainboard.

jay_s_uk

@benecito the filament monitor has to be on the same board as the extruder driver.
there are some temporary limitations in place https://docs.duet3d.com/en/User_manual/RepRapFirmware/CAN_limitations

benecito

@jay_s_uk I know about those and the extruder driver was always on the same board as the filament monitor

jay_s_uk

@benecito looks like there are a few things that aren't reported in the OM for filament sensors, especially when over CAN-FD. https://github.com/Duet3D/RepRapFirmware/issues?q=is%3Aissue+is%3Aopen+filament

benecito

@jay_s_uk @chrishamm To be honest I don't care so much if it's reported in the OM or not. The proposed "workaround" at https://github.com/Duet3D/RepRapFirmware/issues/862 does not work if the status is always "ok". Rearranging the extruders and the filament monitors to the mainboard could be done, but is not the preferred option.

Is there another parameter than sensors.filamentMonitors[0].status that might help to achieve the idea of using deamon.g

jaysuk created this issue in Duet3D/RepRapFirmware

closed [FeatureRequest]: M591 filament monitoring option for USB control #862

jay_s_uk

@benecito no, thats the point of my response, sensors.filamentMonitors[0].status is from the object model...
there isn't another way to query something

benecito

@jay_s_uk all right - so the conclusion is, that we can't use any filament monitor as of now?

jay_s_uk

@benecito you can use them on the mainboard but it looks as though the reporting over CAN-FD needs work. but hopefully someone like @dc42 can chime in

benecito

@jay_s_uk But that's my point - even when connected to the mainboard sensors.filamentMonitors[0].status will stay at "ok" when I run out of filament

jay_s_uk

@benecito that may be a bug then. what firmware version are you running?

benecito

@jay_s_uk 3.5.0 beta 3

timoschuett

Hi, are there any updates on how to enable filament monitoring while printing via usb? Is there a new enable mode which needs to be used?
Thanks, Timo

jay_s_uk

@timoschuett you use S2 in M591 https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m591-configure-filament-sensing
only supported in 3.5RC1 and newer

T3P3Tony

@timoschuett see the M591 documentation:
https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m591-configure-filament-sensing

The S2 parameter.

benecito

@timoschuett please be aware it does not really work yet.

jay_s_uk

@benecito have you reported any problems with it that you're having?

benecito

@jay_s_uk we're in contact and diagnosing the issue yes

timoschuett

Thank you guys! I must been blind while reading the wiki earlier, have not found anything about it. Now i`ve found it
@benecito what exactly "does not really work yet" ?

dc42

@timoschuett we have one user (only one AFAIK) who has an intermittent issue with a filament monitor connected to a Duet 3 Mini. Apart from that, I believe all the outstanding issues have been addressed in the 3.5.0-rc.1+ firmware builds, which are available at https://www.dropbox.com/scl/fo/tjznycpk7bv7sj71p0ssl/h?rlkey=096p4nvgmigyrb20jj8olg3wu&dl=0.