Every time my trident has an issue I curse the box turtle and assume it’s the failure.
It’s nearly always something else.
This time I got a tiny piece of filament stuck in the toolhead extruder gears in an invisible spot.
…But I definitely spent a day blaming the box turtle for failing to load filament.
Well the #BoxTurtle is working, but I’m not out of the woods yet.
After calibration I got through 7 layers of this 12 layer print and 20+ automated filament swaps before getting a clog somewhere in the toolhead during a filament swap that I wasn’t able to easily clear.
The BT macros detected it and paused the print to give me a shot at recovery but it wasn’t possible without tearing down the toolhead.
(It’s just as slow and wasteful as I expected it to be)
My #BoxTurtle filament changer is fully built and flashed and has passed all the basic functionality checks.
Tuning all the parameters for loading and unloading filament is up next. We’ll see how fiddly that is.
Well. Somehow the filament sensor I installed on my Xol-metrix has worn out before I even configured it. The ball no longer triggers for some reason.
I had gone in to set it up so I can get moving again on the box turtle but I guess I’m going to try ramming with the buffer instead.
I don’t like how fiddly Xol-metrix is to assemble and would probably print up an anthead or a4t before reprinting it.
Nothing like trying to print clear filament to prove that your nozzle isn’t really purged…
I can’t even recall printing blue or teal filament on this machine and I would certainly prefer that my #BoxTurtle status LEDs were shining through a neutral colored diffuser.
Sold my Bambu P1S, down to my Vorons now.
Much better this way. I didn’t like Bambu the company much even before buying the printer and never liked the printer much once I had it.
Time to get back to building my #BoxTurtle for the trident and figuring out how to delete the Bambu network plugin out of my OrcaSlicer config.