-
-
Notifications
You must be signed in to change notification settings - Fork 466
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
Input PIN for Filament Runout Sensor? #577
Comments
the sensor feature is to send sensor info only (Temperature, humitidy, voltage, etc..) no action on sensor just forward collected info I am not sure about the benefit of ESP3D on filament sensor - printer FW already have such feature - so why ask ESP3D to monitor a pin that Printer FW could monitor directly ? as action(s) to react from pin state change can differe from one user to another and need to do specific code I was more thinking on using interpreter for this but need to think more : #378 |
As I stated above, to send me a Notification to my mobile phone that the filament has run out. |
so your idea is to hook on existing pin check the pin state and according state send a notification like M600 do ? |
do you realize that the feature is already in Marlin https://github.com/MarlinFirmware/Marlin/blob/2.0.x/Marlin/Configuration.h#L1182 |
Check the PIN state and send Notification to mobile, yes, NOT to the printer so no need for M600. The microswitch will already be plugged into the mainboard, stopping the printer as per Marlin firmware. The ESP3D will merely notify as per Notifications setting in the Interface (Email, Pushover, Telegram, Line) to inform of Filament Runout and that the printer has stopped and awaiting urgent attention. |
so just change the GCODE to As it should support several commands should become
|
Ah! Thank you. That's one way around it I guess. |
I am guessing you use Marlin - but other FW should have a similar way |
Correct. Ender 3 V2 with Creality 4.2.7 and latest Marlin from AU site. |
So I guess issue can be closed ? |
Going back to this again if I may? Sorry. Hope you can help further. OK, so my question is - How do I set up any further notifications I want?
Where does that go exactly? And how does it work? |
in your end code of cura just add
|
Yes, I understood that, thank you. |
this is done by Marlin as mentioned above https://github.com/MarlinFirmware/Marlin/blob/2.0.x/Marlin/Configuration.h#L1182 |
Ah, gotcha! Thanks. |
I can now confirm that I have successfully compiled my own firmware. Several times in fact! lol |
the ESP3DLib references in Marlin are for ESP3DLib a library for Marlin, it is used on ESP32 as main board , not for external ESP board like you do - so uncomment them may just make the compilation failed if target is not an ESp32 board depending of Marlin version you use - some sanity check block compilation if settings are wrongly enabled |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Forgive me if this is already implemented or planned for the future but I was unable to find any info.
In the config files (either versions 2.1.1 or 3.0) particularly version 3.0, I notice there are several possible/future functions commented out, especially one for a SENSOR. Is this able to be used for a Filament Runout Sensor?
If so, which PIN is used? If not, could it please be considered for inclusion as a Mod?
I was looking at this idea - https://www.instructables.com/IoT-Enabled-Smart-Filament-Runout-Switch/ - but it seems sill to use yet another Arduino when I could run a wire to ESP3D. I don't use Blynk nor do I want to but my thinking is that ESP3D could send me an alert when the Filament Runout Sense PIN goes HIGH (Or LOW, whichever)
I'm thinking of making my own Filament Runout Sensor such as the diagram below and it would be quite easy to run a single wire from the center arm of the micro switch to an INPUT PIN on ESP3D.
Your help and advice would be most appreciated if this is already possible.
Thanks.
The text was updated successfully, but these errors were encountered: