Simple filament runout sensor with endstop switch
BearcatTD last edited by BearcatTD
I am plugging it into the E1 endstop. So I just extended the stock endstop cable, but I realized that one end is a 3 pin, that connects to the switch, (2 wires, in the outside pins) and the other is a 2 pin that goes to the board. The E1 endstop on the Duet is 2 pins. I am assuming I have to "cheat" to one side of the Duet plug, just not sure which side.
This is the code I'm using:
M591 P2 C"e1_stop" S1 ; filament monitor connected to E1_stop
Hopefully this makes sense! Thanks!
EDIT: I re wired the endstop plugs and matched the signal and ground on both ends. Still nothing. Pretty sure at this point it is the Config.g code.
What firmware version are you using?
I am running 2.04
M591 P2 C"e1_stop" S1
So that syntax is for RRF3.
For RRF2, you'd use
M591 D0 P2 C4 S1; That's Drive 0, simple sensor with low signal, on endstop E1, and enable filament monitoring.
So, assuming I wired the cable correctly and plug it into the board correctly, I just edit config.g file to include M591 D0 P2 C4 S1 and it should be good to go. My last question...LOL, who am I kidding, it won't be my last question, when the switch triggers, i.e., it runs out of filament, what exactly happens? Will it automatically put the machine into pause so the filament can be changed?
My last question...LOL, who am I kidding, it won't be my last question, when the switch triggers, i.e., it runs out of filament, what exactly happens? Will it automatically put the machine into pause so the filament can be changed?
Yes, but only if it happens while printing from SD card.
I'm confused. When I upload a file through the web interface, doesn't it reside on the SD card?
Yes, normally you'd be printing from SD card. The alternative would be using a USB connection to software that is streaming the gcode commands that way.
@Phaedrux Good! The only time I connect via usb is for setting up wifi!
It is working great! Thanks for the help!