search

Red-M / Octoprint-Filament-Sensor-ng

GNU General Public License v3.0
11 stars 5 forks source link

Stopped working #3

Open rickyelqasem opened 4 years ago

rickyelqasem commented 4 years ago

It worked a few days ago but stopped. My sensor seems ok since there is a light on it and if you change the option to "normally open" the job wont start to print. But if the filament runs out part way through a job it wont pause.

Archmonger commented 4 years ago

I have the exact same issue. Filament sensor will prevent jobs from starting, but often will not pause once the print has begun. Perhaps the plugin's task is being killed by Octoprint once the print job begins?

Red-M commented 4 years ago

This will depend on how you've got the sensor for normally open/closed and if you've selected the right GPIO pin. I'd suggest setting it to normally open and getting the pin selected correctly, I'd suggest pin GPIO 17 and connecting the other pin to the ground next to it.

image

Archmonger commented 4 years ago

Currently am using board pin 7 and 9 with a normally closed switch. I'll try swapping my wiring to normally open and use 11 instead and let you know the results.

My issue might be a little bit different than OP's since my filament sensor (just a generic microswitch) does sometimes work properly to pause during ongoing prints. It always works properly on preventing prints from starting when filament is not detected.

Out of curiosity, why would using a specific GPIO pin change things. Shouldn't all GPIO pins be effectively equivalent? Additionally, why is normally open suggested?

git-jonathankinney commented 4 years ago

I'd have to agree with the previous posts, however my situation is a brand new install of octopi/octoprint within the last few weeks, on a Raspberry Pi 3B, and this plugin only would stop prints from happening if the filament sensor was triggered, no pupup, no message, just mystery fail won't start. So everything is super fresh/new install, no hacking or custom mods, and it didn't work with normally open with a simple switch. There seems to be a common bug about the GPIO vs Board numbering between plugins, so all my plugins are using Board numbering. I got it to work fine with "Filament Sensor Simplfied", but wanted an email option (via action commands and a g-code snippet), so tried this one, and it didn't work as stated, so I switched to "Filament Sensor Revolutions" and that seems to do exactly as expected, so some coorination between this project and "Filament Sensor Revolutions" might be a good idea.

Red-M commented 4 years ago

Use GPIO pin 17 or 23 in the plugin settings with the other pin wired to either board pin 9 or 14. The plugin wants the GPIO pin number, not the board pin number but I haven't used this plugin in a long time as I've switched to a zesty nimble, haven't mounted a filament sensor to my machine and I don't have the time to do so.

The wiring should be board pins 9 and 11 for using GPIO pin 17 (and setting the pin to 17 in the plugin) or GPIO pin 23 (and setting the pin to 23 in the plugin) and board pin 14. The board pins are the ones in the circles and the GPIO pins are the ones stated on the fly-out section.

bvrielink commented 4 years ago

"Filament Sensor Simplfied",

Also having the same problem with this plugin not working. Used the "Filament Sensor Simplfied" plugin and this one works without problem. Don't know the issue. See that it is enabled in the log file but does not stop the print (when no filament) or reports any problems. Using GPIO pin 17 and pin 1 (3.3 volt). Using ground instead of volt does not work for my sensor btw (Z endstop).