Burn the Filament Sensor - it is the devil!! 😈
I kind of get the feeling the feeling the Filament Sensor is a big reason the XL gets a bad rep. I even found a thread now where someone reports he thought the toolchanger is broken, but no it was the Filament sensor.. I always had problems with the nextruder not (n)extruding, which is the one thing it should be reaallllyy good at.. well it was the FILAMENT SENSOOORR.. and guess what sucks at loading new filament?? the FilAmEnt SenSoRR!
Okayy.. but you know what is really amazing and ground breaking.. for sure it isn't the fluuhping PH1L4M3N7 53N50r!!!!
Â
Okay I will stop the comedy here.. but for real can we not engineer a better filament sensor for the XL? What would even happen if I just get rid of it - the hotend would still register there is not filament loaded right? I mean it has its own FILAMENT SENSOOORR that works..
RE: Burn the Filament Sensor - it is the devil!! 😈
I don't own an XL (sadly), but from this post I gather that the filament sensor might, in some rare cases, be slightly annoying.
RE: Burn the Filament Sensor - it is the devil!! 😈
I was actually hoping OP would tell me what kind of issues the sensors are causing. I don't have any issues with mine.
RE: Burn the Filament Sensor - it is the devil!! 😈
OK, then make a knot in your filament, wait a few minutes, then reconsider your post. Or try flexibles 🤡Â
The sensor produces way too much drag. Also it measures only if filament is present, not its motion. It will not detect nozzle clogs, filament break or tangles. It's clearly an afterthought because they thought they can do everything with the load cell. I'm super happy with my printer, but losing prints because of shitty spooling is ridiculous. My 180USD china printer does this better.
RE: Burn the Filament Sensor - it is the devil!! 😈
I get it you have had issues. That really sucks for such an expensive machine. Though in all fairness I doubt that everyone has had the same issues as you. I am not saying no one has by any means . I myself have had zero issues with the filament sensor regardless of material (mind you i have only used pla, silk, petg, flexibles.) Only 1 bad print and I know the issue was mine. A long narrow/tall print diagonal in a rather cold basement (Edmonton) that was 9.5 hours long. With no mouse ears either, yes you guessed it, it curled up on the ends. Mind you I have only a few hundred hours on my print though have used all 5 heads and multi-material prints as well with no issues. I hope you get your issue(s) resolved!
RE:
I have no issues. My sensors work. Their capabilities are a different matter, they simply cannot detect blockage. Someone asked what the issues were and I gave a quick explanation to OPs rant.
If they can get the load cell working as intended it will be quickly forgotten.
RE: Burn the Filament Sensor - it is the devil!! 😈
My understanding was that the filament sensor was simply a presence detector. The nozzle assembly with pressure sensor is supposed to detect a clogged nozzle. I also believe that hasn't been implemented yet, though. One of those features on the board. Maybe someone can correct me?
Also, I've printed in TPU without any issues right out of the box. Maybe I'm lucky?
RE: Burn the Filament Sensor - it is the devil!! 😈
Fair enough my interpretation of your issue was off a bit. One of the issues with text type messages as there is not voice inflections. Hope you get it sorted!
RE: Burn the Filament Sensor - it is the devil!! 😈
I'm not sure if you're lucky...could be a different reason: Afaik the design files have not been released yet, so we don't know if the part in question was silently changed in the newer printers. All it would take is making the holes that hold the springs a tiny bit longer. My spring pressure doesn't feel terribly strong, but probably still too much for soft TPU.
The weight cell does nothing except bed probing currently. I had a few tangles already (not the printers fault), and it keeps printing with no filament and skipping extruder (which by the way could be detected by the driver if I'm not mistaken, but that is also not being done).