-
Notifications
You must be signed in to change notification settings - Fork 995
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow bulge detector without encoder in filament detector #783
Allow bulge detector without encoder in filament detector #783
Conversation
Allows the module to be instantiated if the bulge detector exists but the encoder does not. Inhibits attachment to events for the encoder if the encoder doesn’t exist.
As far as i can see this will do nothing more than the switch module would do. If the bulge detector fires it will issue a suspend regardless of whether it is printing. This is because you completely by passed the code that checks if there were any extruder movements, which is what stops this module from false alarming when not printing. The bulge detector was not protected from this because it was unlikely to trigger when not printing, unlike the encoder check, it also was added to provide a button to do a manual suspend when needed. |
I'm happy to go back and refactor this but let me explain my underlying assumptions because I think this is still valid code.
Do I need to remove the changes I've made and implement it as suggested or are the current changes also valid? I see a digital filament sensor as complementary to this change and will implement it but need to know whether I have to revert back to stock and start over or start from where I am. |
your current changes are fine, however as I said they do exactly what switch would do, except the addition of being able to activate/deactivate the detection. If that is all you need to do then leave it as it is and I'll merge it. |
That's all the functionality I need but I'm happy to make it better. Let me take a stab at adding digital_detector_pin and the associated code this evening. |
This shouldn't affect my solution as the system I use monitors both extruders with a single pin but I don't see how the filament detector works with multiple extruders. It seems that we can monitor only one encoder but the get_emove() is effective for the active tool (right?). Multiple instances of this module won't work because it has no way of determining which instance it should be handling it. Is the intention to eventually add a second extruder to this monitor (then how would we handle n?) or is there a way to modify this to be able to determine it should be monitoring? |
OK, I did my modifications tonight and it doesn't trigger like it should. Can we merge this code and I'll see about making the suggested improvements in another pull request? |
Allow bulge detector without encoder in filament detector
Hello everyone! Does anybody know how to apply filament monitor to dual extruders on smoothieware? E.t. if first extruder working - then checked first filament monitor, and if worked secont extruder - then checked second filament monitor. |
Allows the module to be instantiated if the bulge detector exists but
the encoder does not. Inhibits attachment to events for the encoder if
the encoder doesn’t exist.
I was able to test this with the bulge detector and it works as expected. I am not able to test the encoder functionality but that functionality should be completely untouched by this pull request.