You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've developed a device to ensure that filament is constantly flowing into the machine properly. If the filament stops flowing for any reason (i.e. empty, clogged, jammed) the print will go into a pause allowing the user to fix the filament issue and then continue the print.
The change that is needed is to use a GPIO as a digital input that is pulled high. When my device alarms, it pulls that line low (to about .5V). Also a 5V and 0V connection are required, but those are not related to firmware.
I'm a EE and have designed this device to protect the GPIO on the motherboard against shorting to a rail.
I'd love it if marlin could support this device. I think it would save a lot of potential failed prints.
I made a filament monitor using OctoPrint that does not require any firmware modification and offers a number of advanced features (like telling you how much filament is actually left). https://github.com/MarcusWolschon/UltimateFilamentSensor/
I've developed a device to ensure that filament is constantly flowing into the machine properly. If the filament stops flowing for any reason (i.e. empty, clogged, jammed) the print will go into a pause allowing the user to fix the filament issue and then continue the print.
The change that is needed is to use a GPIO as a digital input that is pulled high. When my device alarms, it pulls that line low (to about .5V). Also a 5V and 0V connection are required, but those are not related to firmware.
I'm a EE and have designed this device to protect the GPIO on the motherboard against shorting to a rail.
I'd love it if marlin could support this device. I think it would save a lot of potential failed prints.
Here's the device:
https://sites.google.com/site/tunelldev/home/filamentmonitor
https://www.youmagine.com/designs/filament-monitor
The text was updated successfully, but these errors were encountered: