Runout filament sensor - microswitch
-
Hello everyone,
I'm having a problem with a runout filament sensor. I'm using a Trianglelab.
I use M591 and I connect it to E0 endstop:M591 D0 P2 C3 S1
I don't specify anything in M574 for E0 endstop.
The problem is, that also if the filament is present (reported by M591 D0), the printing job is paused as there isn't filament.
After pause, if I check with M591 D0, it says filament present.
Another info, I'm running 2.05.1 firmware on duet 2 wifi.What could be the problem?
-
@bigsub said in Runout filament sensor - microswitch:
The problem is, that also if the filament is present (reported by M591 D0), the printing job is paused as there isn't filament.
Is it paused immediately, or after some time?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@bigsub Your command looks correct for an active low TriangleLabs filament runout sensor.
I'd suspect poor wiring or interference is giving you false triggering. Because the Duet is expecting 0V when filament is present and the switch is triggered, any voltage that is being picked up makes it look like the switch has been released, and there's no filament present. Check the wiring for bad contacts, loose and/or poorly crimped crimps, or the wires running close to other high current wires, eg stepper motor wires. It's also possible that the filament bumping over a particularly sensitive microswitch switch is generating enough movement to create a false reading occasionally.
Ian
Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : TronXY X5S with Duet 3 MB6HC and Roto toolboard
-
@dc42 said in Runout filament sensor - microswitch:
@bigsub said in Runout filament sensor - microswitch:
The problem is, that also if the filament is present (reported by M591 D0), the printing job is paused as there isn't filament.
Is it paused immediately, or after some time?
It's paused after some instructions printed.
-
@droftarts said in Runout filament sensor - microswitch:
@bigsub Your command looks correct for an active low TriangleLabs filament runout sensor.
I'd suspect poor wiring or interference is giving you false triggering. Because the Duet is expecting 0V when filament is present and the switch is triggered, any voltage that is being picked up makes it look like the switch has been released, and there's no filament present. Check the wiring for bad contacts, loose and/or poorly crimped crimps, or the wires running close to other high current wires, eg stepper motor wires. It's also possible that the filament bumping over a particularly sensitive microswitch switch is generating enough movement to create a false reading occasionally.
Ian
Ok many thanks, I'll check.
-
Did you get it resolved? I am having the same issue. I have checked the wiring switched sensors and connecting cables but it always gives me the runout on E0 no matter of which sensor and or cable is being used.
-
I've been working with these sensors on my Duet2 Wifi - thought I'd share my experience. I thought it was just going to be a simple microswitch connection with a common, NC, NO - but when I started checking continuity on the leads in different states it was clear that it's not that simple.
I saw a review on Amazon that talked about connecting to a RASPI board with three leads - ground (black), voltage(red), and signal(blue).
I tried that first on the Duet board going into E1 endstop. There are LEDs in the sensor - green when filament is present, flashing red when not. The LED on the Duet board was changing state - low (LED ON) with filament present and high (LED OFF) with no filament.
Added M591 D0 P2 C4 S1 to my config.g.
Initially it looked great. Printer started printing and paused with filament out notification when I pulled the filament. At that point, however, I was unable to restart the print. I put filament back in the switch and pressed RESUME - the print head moved over the part and then reported NO FILAMENT again - pausing the print. The end stop LED on the board was still turning on and off without filament, but M591 D0 reported no filament regardless of the state of the switch or LED on the board.
The Red and Blue leads on the switch act like a direct NC connection, so I wired those to the E1 end stop ground and signal - just the outer connections. Changed the P2 to P1 in the config file and all is working fine. I lost the blinky lights in the sensor, but that's minor. A little mystified as to why the LED on the board was switching states with the original setup, but M591 would not report the changing state after the initial filament out warning.
-
@zemlin said in Runout filament sensor - microswitch:
I've been working with these sensors on my Duet2 Wifi - thought I'd share my experience. I thought it was just going to be a simple microswitch connection with a common, NC, NO - but when I started checking continuity on the leads in different states it was clear that it's not that simple.
I saw a review on Amazon that talked about connecting to a RASPI board with three leads - ground (black), voltage(red), and signal(blue).
I tried that first on the Duet board going into E1 endstop. There are LEDs in the sensor - green when filament is present, flashing red when not. The LED on the Duet board was changing state - low (LED ON) with filament present and high (LED OFF) with no filament.
Added M591 D0 P2 C4 S1 to my config.g.
Initially it looked great. Printer started printing and paused with filament out notification when I pulled the filament. At that point, however, I was unable to restart the print. I put filament back in the switch and pressed RESUME - the print head moved over the part and then reported NO FILAMENT again - pausing the print. The end stop LED on the board was still turning on and off without filament, but M591 D0 reported no filament regardless of the state of the switch or LED on the board.
The Red and Blue leads on the switch act like a direct NC connection, so I wired those to the E1 end stop ground and signal - just the outer connections. Changed the P2 to P1 in the config file and all is working fine. I lost the blinky lights in the sensor, but that's minor. A little mystified as to why the LED on the board was switching states with the original setup, but M591 would not report the changing state after the initial filament out warning.
After about 5 hours spent at this I came across this post. Thank you so much for spending the time to comment. This solved my problem.
Thanks again. -
@EricE555 said in Runout filament sensor - microswitch:
After about 5 hours spent at this I came across this post. Thank you so much for spending the time to comment. This solved my problem.
I have two of those units and at first they did not work for me.
It seemed like everything was ok. The LED on the unit tracked the presence or absence of filament.
The LED on the Duet seemed to track the state of the LED on the unit.
I finally hooked up an oscilloscope and found out the signal levels from the unit were not valid logic off and on states.
The levels were adequate to make the Duet LED look like it was turning on and off but it actually was never fully on.
I took the units apart and found that to pull the output low there was a 4.7K ohm resistor from the output to ground.
That was too much resistance to pull down the Duet input to a logic low.
I changed out the resistor to a 680 ohm and everything was fine.
Frederick
-
So glad I found this post after struggling with this sensor.
I ended up sistering a 1.5k resistor across the existing 4.5k SMD resistor for a combined resistance of 1.1k. The sensor now works correctly with all LED indicators also still functioning.
This is the Gcode command I used for RepRap 3.2
M591 P2 C"e0stop" S1 D0 ;Filament is out when switch is Low, Extruder 0
