this post was submitted on 06 Sep 2023
26 points (100.0% liked)

3DPrinting

14795 readers
55 users here now

3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.

The r/functionalprint community is now located at: [email protected] or [email protected]

There are CAD communities available at: [email protected] or [email protected]

Rules

If you need an easy way to host pictures, https://catbox.moe may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is ![](URL)

Moderation policy: Light, mostly invisible

founded 1 year ago
MODERATORS
 

As title says. I got myself a filament runout sensor, wired it, designed and printed a holder for it and now I am experiencing some issues. I hope someone here can help me.

At first, the sensor is doing its job and seems to be working as it should. Printing is possible, but only with extra steps I would like to avoid. I use this sensor:

Creality Offiziell Filament Runout Sensor Kit Ender 3 Filament Erkennung Modul Detektor Gerät Original Pausen Erkennungs Monitor für Ender 3Pro, Ender 3 V2 mit 32 Bit V4.2.2/V4.2.7 Motherboard https://amzn.eu/d/3aR6o2e

I am using it on my standard Voxelab Aquila running Alex firmware. Slicing in Astroprint and managing over Octoprint on a raspberry pi.

The problem: The runout sensor sends a false positive right after starting a print. It draws the first line on the printbeds side and then stops telling me the filament ran out. It then proceeds to unload the filament and asks me to change it. I then re-insert the „new“ filament, it extrudes a load and then prints just fine.

So as you have possibly guessed right, I want it to print right away, just stopping the print, if there really is some jamming or no more filament left. Does someone know if I have to adjust the start commands or something like that? It seems to be a software problem.

Thanks in advance for any help!

Update: I gave up on this project and sent the sensor back. I couldn’t get it to work even after modifications to the firmware. Too bad…

you are viewing a single comment's thread
view the rest of the comments
[–] corodius 1 points 9 months ago (1 children)

it sounds like you need to invert the runout sensor detection, as it is triggering immediately.

[–] Gorroth 1 points 9 months ago

I already tried that, didn’t work. I increased the runout distance and sent some M412 commands to configure everything before a test print. It then seemed to work, but when I cut the Filament to simulate a runout it didn’t work. Sending the sensor back if I can’t get it to run this weekend