Filament monitoring while printing via USB
-
@dc42 another option would be to implement Marlin's Host Action Commands as part of setting a Duet board to Marlin compatibility mode. Maybe that's more generally useful?
-
@oliof is this still needed if the host reads the outputs of the board?
The board just needs to output a certain message in the console and the host needs to react to this event as for example repetier-server can.I would be totally happy with an S2 option for M591. This should resolve many problems.
If there is a quick and dirty workaround for this, please tell me
-
undefined Phaedrux moved this topic from Filament Monitor
-
@timoschuett The host reading output from the board is exactly what happens with host action prompts, just in a documented, known, and supported way that is already done by other firmware. Hence I suggested using that instead of inventing another scheme which would require adoption by other systems.
-
undefined jay_s_uk referenced this topic
-
Any update on when it will / might be available?
-
-
@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. -
@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 -
@jay_s_uk I know about those and the extruder driver was always on the same board as the filament monitor
-
@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
-
@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
-
@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 -
@jay_s_uk all right - so the conclusion is, that we can't use any filament monitor as of now?
-
-
@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
-
@benecito that may be a bug then. what firmware version are you running?
-
@jay_s_uk 3.5.0 beta 3
-
undefined Phaedrux moved this topic from Firmware wishlist
-
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 -
@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 -
@timoschuett see the M591 documentation:
https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m591-configure-filament-sensingThe S2 parameter.
-
@timoschuett please be aware it does not really work yet.
