Voron Trident build

Details

Why a Voron Trident:

  • It’s an enclosed printer to promote healthy geekroom air quality through the use of an enclosure and an air filter.
  • It’s CoreXY and Klipper and therefore has a lot of opportunities for cleaner prints because of better motion control. At the same time, it doesn’t have quite as much somewhat-questionable complexity as the V2.4 printer.
  • I feel like the Ender 3v2’s bed was a bit too small, so getting something bigger was always on my mind. At the same time, a 350mm printer is just too big.
  • There are multiple options for multi-material printing, either the ERCF v2/Tradrack, a IDEX mod, or the Dakash toolchanger.
  • It’s open source and community supported but you can still get a kit to assemble, which is cheaper than the fully-supported-closed-source expensive quality printer but better off than the sketchy printer that’s basically community supported except someone still claims ownership over the design and nominally acts like it’s something other than community supported.
  • I took apart the Ender 3v2’s hotend, a Slice Engineering Mosquito, because it was a bit bent and I’m not entirely sure where the actual problem is but the tiny little M1.4 screws that hold it together aren’t threading very well and I’ve kinda made up my mind that I should replace the Ender so I might as well work on the new hotness.

Parts List

QtyPart #DescriptionManufacturer
1Voron Trident Pro kitVoron Trident R1 Pro kit with Dragon Standard Flow hotendFormbot3D
1Voron Trident Functional Parts, Plutonic Purple, Self Sourced, Dragon hotendcPIF printed functional parts for a 300mm tridentFabreeko
1Voron Trident Complete Parts Add-On, Plutonic Purple, Self Sourced, Dragon hotendcPIF printed complete add-on to the functional partsFabreeko
1Magnet sheetMagnet sheet with high-temp glueFabreeko
1Edge to edge bed heaterEdge to edge bed heater with better adhesiveFabreeko
2CFM-6020V-237-280Fan Tubeaxial 24VDC Square - 60mm L x 60mm H omniCOOL™ Magnetic Sleeve 19.0 CFM (0.532m³/min) 2 Wire LeadsCUI Devices
2BFB0405HHA-AFan Blower 5VDC Square - 40mm L x 40mm H Ball 3.0 CFM (0.084m³/min) 2 Wire LeadsDelta Electronics
1BFB0405HHA-AFan Tubeaxial 5VDC Square - 30mm L x 30mm H Sleeve 4.3 CFM (0.120m³/min) 3 Wire LeadsDelta Electronics
1B071JT3ZHCAluminium Heat Dissipation Heatsink Cooling Fin for Solid State Relayuxcell
1CM4-HEATSINKDedicated Aluminum Heatsink for Raspberry Pi Compute Module 4 CM4Waveshare
1USB-HUB-4UIndustrial Grade USB HUB, Extending 4x USB 2.0 PortsWaveshare
17840K72Slit Corrugated Sleeving, 3/8" ID, Black, 5ftMcMaster Carr
1Beacon Rev HBeacon Rev H, normal, 6ft cableBeacon
1Mellow FLY SHT36 Max V3Mellow Fly SHT36 Max V3 with MAX31865 and LDC1612 chipsMellow
1Dragon AceTriangle Lab Dragon Ace PT1000 hotendTriangle-Lab
2#10 18-22AWG spade terminalRed 10 Stud Spade Terminal Connector Crimp 18-22 AWGMolex

Build Log

Step 7: Voron Print Farm

This update covers many months of using the printer, working on things, etc. Including a giant burst of printing to get everything together for the Maker Faire and also some periods where the printer sat idle and not-quite-functional because I had to go to funerals and things.

General improvements

  • Instead of using one of the fancy tools, I just used the builtin SHAPER_CALIBRATE. I’ll probably obsess over it more when I’ve got it closer to the final configuration. But it’s kinda obvious that the Tap makes things jiggly. My old Ender was accelerating at 500 mm/s2 and I’ve got it accelerating at 4000 mm/s2. 4k accels is enough to give it that freaky fast-printing feeling.
  • With a 0.4mm nozzle and PETG, I’m mostly limited by the 60mm/s speed limit for PETG and/or layer time. If I switch to a 0.6mm nozzle and PETG, I’m volumetric flow rate limited. I have some CHT nozzles and I haven’t seen how much I can squirt down those yet.
  • I used the slip in brackets to make it easier to insert the deck plate. I ended up removing the provided supports in the back because they were just getting in the way. I ended up needing to jiggle things a bit to get it all to slide in perfectly. But I do have the deck plate closed, which is good because one problem with the inverted electronics is that you can drop a bolt into the works and zap stuff.
  • I put a Waveshare CM4 heatsink on and that definitely helped the Pi’s temperatures.
  • I re-printed the Y Endstop relocation mod in Plutonic Purple ABS now that I’ve got that spool open.
  • I’m going to use, at least for starters, the Voron 2.2/Annex panel clips on the side and top panels.

Tap to Beacon

Ryan: “I have a 9 point mesh. How many points does your ABL have?” “Yes.”

After finding out that allegedly the Tap sensor is going to limit my speeds and finding out about Beacon adding a contact mode, I’d planned all along to get a Beacon.

I figured that the right way to do this is to get the Beacon probe going first, then switch over to a new toolhead as a second step.

So I started yoinking the tap. I printed the non-official Annex Beacon carriage. I tried some of the magical solutions for redoing the belt without having to re-tension the whole works. One of them was awkward. The other one cracked, although I’d screwed up printing it so I’ll try that one again. Finally I just gave up on being fancy took advantage of having fairly good relative pitch to re-tension the works because after all it doesn’t take me that long.

I’m not sure exactly what’s wrong, but the X-limit switch for the Annex mount is something like ~1-2mm too far. I was just checking, powered-down, and it was kinda obvious. I ended up taping a piece of filament on the XY joint to make it a bit thicker. Kinda confused as to what’s going on there…

The sensor looks to be 0,28 from the nozzle.

I also had to fight with the prind docker image and the Beacon installer. It turned out that the best way to get it going was to replicate the installer shell script as a child docker container.

I also had to print a DIN rail bracket for the Waveshare USB-HUB-4U hub that I got because apparently the USB on the Manta is slightly iffy according to the Beacon folks.

Overall, it feels like an improvement. For several reasons:

First, while I still haven’t actually sat down and plotted the graphs from the data and used that to hunt down screws to tighten, the difference in what SHAPER_CALIBRATE suggests is dramatic. So, clearly, the tap sensor jiggling really is hurting the performance, that’s not just random allegations. I went from 4k accels to a conservative 8k accels.

Also, and this is probably a bit my fault for being potentially a bit lackadasical in my Tap construction, but the overall accuracy is a lot higher. But I guess this still counts as an advantage - the Tap is a very neat design with some careful compromises and design thinking but you have to assemble it. The Beacon (or Cartographer or other such sensor) is a largely solid-state device that is fabbed and all you need to do is screw it on. So I upped the required tolerances of bed leveling because it tends to be right on the nose.

Finally, the Contact workflow is better than I’d thought. With Tap, you need to keep the nozzle de-schmutzed before every print, understanding that’s actually really hard with PETG because it really wants to booger out the nozzle. Contact can still work in a mode where it does a touch sensor every print. However, there’s also a BEACON_AUTO_CALIBRATE command that I can run which will calibrate the probe with the touch mode and then save that model. So instead of having to do the touch sensor every print, I can use the touch sensor only when I change the bed or the nozzle.

I don’t need to figure out the overall offset for tap the way I did with tap, but I did discover that I need to adjust the z offset up 0.1-0.15 if I’m using a wider nozzle.

Thus, I definitely don’t want to use the brass nozzle brush because it might short the self-test contacts on the bottom of the Beacon and also scrape the coating off of my coated nozzles. I decided against the Bambu nozzle silicone thingies because they seem to be quite short lived. I’ve got some high temperature silicone that’s suitable for making a nozzle brush out of and I guess I still want to mount it, but it’s a lot less important versus just manually scrubbing the nozzles still. So that’s still an open question.

Either way, I have some Slice Engineering Vandium nozzles and they are 0.1mm or so off from the “standard” and so I’d always have to mess around with the Ender 3v2 whereas I can just tell Beacon to auto-calibrate and everything’s fine.

New toolhead, first try

A conversation a while ago on the Voron discord indicated that the VZ-Hextrudort Low with the non-twisty gears was the best TPU-focused extruder. And then I also decided that I wanted to have relatively simple wiring for the toolhead, so I got the Mellow-Fly SHT36 V2.0 toolboard because the NH36 seems like a bit of a disaster.

I was thinking about either the Xol or the Dragon Burner. The big thing is that the Dragon Burner fits on my Zero whereas a Xol will not, so this way I’ve got identical toolheads. Also, the Dragon Burner has a slot for a thermistor that sits against the heatsink.

I decided to get some fancy Delta fans. Xol recommends the BFB0405HHA-A 4010 blower and the ASB02505SHA-AY6B 2510 axial fan. I got the same blower but ended up getting the ASB0305HA-DF00 fan that seemed to be fairly close.

  • The cable that came with the SHT36 is too short for my printer but thankfully I’m able to re-use the cable that came with the printer.
  • The packaging for Katapult assumes that it’s running alongside Klipper. I spent some more time and decided to see if I really really needed to use it or if I can just use the standard Klipper interfaces for things.
  • After I’d gotten into it, I realized that the SHT36 V2 toolhead only supports a PT100 sensor, not a PT1000. I want the SHT36 V3 with the PT1000 instead, so I’ll get back to working on this later.

Chassis grounding

This came up on the Voron discord one evening after work.

I’m not really sure if this is worth obsessing over. I have never seen someone ask “Hey, I get a spark when I touch my Voron, what’s up?” and generally the times that 3D printers in general have done something dangerous, it’s been that they caught on fire.

On the other hand, there’s been a lot of complaints about glitchy toolboard designs. LDO had to recall the NH36 boards. Triangle Labs ships theirs with a bodge wire to connect the stepper chassis to the neutral wire.

In an ideal world of properly made electronics, all of the pieces of the chassis are bonded and connected to safety “earth” ground, which goes to the safety “earth” ground lug in your electronics plug, which is connected to the actual earth via a code-compliant mechanism, generally a grounding post and potentially a bonding strap to the neutral lug coming in.

It’s important to note that while the electrical potential between the neutral ground and the safety “earth” ground should be zero, they are not the same. The neutral ground has the return current flowing to complete the circuit. The safety “earth” ground is there to dissipate spurious currents like ESD or noise. If you look at the block diagram for your PSU there’s an isolation transformer that is required by most electrical codes.

The construction guide specifically has you connect the safety “earth” ground to the frame and the build plate via ring terminals. I added a toothed locknut to the frame’s ground connection to make sure that it scratched away any powdercoating.

Most Vorons are anodized or coated with a presumably not conductive material to make them have a stylish color. At least for my Formbot frame, this happens after the frame has been cut and tapped. This is a problem because it means that when you bolt a frame together, it may not be grounded properly.

Several of us did a quick test. If I probe two points on the coating, I do not get connectivity. However, if I probe the left and right side linear rails, I do see connectivity. So, in spite of everything being powder coated, there’s apparently at least some grounding happening?

Now, allegedly there’s a bit of a problem with static electricity building up as filament moves through the bowden tube which may be responsible for signal glitchies and fried boards. From what I understand the conductive chassis of the stepper motor is meant to go the protective earth (green/yellow striped), not the neutral ground. This mostly makes sense — you don’t want any static electricity spikes on the V- line. That’ll glitch your toolboard.

It would also make sense to spray some conductive spray on parts of the toolboard and maybe have it enclosed, to further prevent EMI glitchies.

Either way, I’ve got some ring terminals on the way so I think I’m just going to add an earthing wire to the stepper motor’s body.

Broken endstop, PUG umbilical, and then minor tweaks to the StealthBurner

The metal thing on the endstop broke, so I found a suitable spare switch but I screwed that up while heat-shrinking the tubing onto the leads, so then I switched to the Creality Limit Switch version of the endstop. And then after I’d gotten that working, the metal thing broke again.

It might have been getting hooked on some of the wires?

I wasn’t entirely a fan of the supplied corrugated tubing nor the glands, so I decided to use the PUG system. After measuring the size of the combination USB+CAN cable, I realized that the 3/8” Slit Corrugated Sleeving that I had gotten for my Ender’s umbilical was about the right size. I used the CW2 mounting umbilical arm on one side and the A drive mount on the other. The endstop relocate conflicts with the PUG mount, so I just bodged with a long screw.

Also, since I really wanted to print some PET-GT and HTPET+ and the StealthBurner’s a bit marginal, I decided to just upgrade the fan to a Vindr from West3D so that I’d at least have a pretty potent fan to cool the hotend and that wouldn’t represent me spending a lot of money on a toolhead I am just going to replace shortly.

There’s not enough room for JST-XH connectors in the StealthBurner’s face so I had to use a Molex connector. And for whatever reason, Molex connectors are always a giant pain in the butt, although I will probably get a different crimper tool and try again at some point. But, with the tool and connectors I’ve got, I managed to get at a passable crimp on the fan’s wires. It’s a 3 wire fan so I ended up making a 2 pin connector that goes to the normal fan port with the black and red wires and then put the yellow tach wire into the 4 pin port so I could just use the sensor.

Assuming the tach doesn’t lie, the Vindr fan is 9300-9600 RPM, which is close enough to the advertized 10k RPM, is at least annoying louder than the prior fan, and seems to be OK with me printing PET-GF so I’m guessing it’s a reasonable improvement over whatever the fan was that I got in the Formbot kit.

Anyway, I lowkey hate sensorless homing, but I switched things over. I’m kinda frustrated because I would have maybe had a working printer earlier if I’d just switched earlier. I want to switch back, mostly because I want the better accuracy from the switch so I can eventually do things like frame temperature compensation and speed tests using the endstop as reference. The annoying part is that you need to follow the special Beacon override section while also following the Voron guide.

The main area I got tripped up is that it’s really hard to get the jumpers for the DIAG pins inserted properly.

A print farm

printing

After some frustrations with the endstop and everything, I got both the Zero and the Trident printing at the same time so I could wrap up a printing project. While both printers are noticeably faster than my Ender 3v2, the real dramatic improvement in print speeds is if I can get them both going at the same time.

New toolhead, second try

I dono, the StealthBurner feels like it’s a lot of overly fancy design and poor ergonomics.

Which I guess I can’t quite critique because … part of why the Voron is a thing is design and aesthetics.

But there’s little things like.. if I’m supposed to adjust the gear meshing, why is the gear in the most awkward position possible to determine if it’s meshing right?

Anyway, the most annoying failure I’ve had so far is that the idler gear popped out of the tensioning arm, which was an annoying failure mode because things would kinda work, but not right. This required a lot of monkeying around. Eventually the heatbreak got clogged with HTPET+. Ugh. Thankfully, it happened after the SHT36 V3 arrived.

Some folks on the Voron discord were talking up the Dragon Ace as a standard-height higher-flow well-behaved printhead, so I had picked up one.

Thus, the configuration is a DragonBurner with a Mellow SHT36 V3 controller board, a Dragon Ace hot-end without the MZE, and the VZ-Hextrudort Low extruder, where I’ve got a tach on the hotend cooling fan to detect a fan failure, plus a thermistor against the heatsink to detect an impending heatbreak clog (or provide a second way to detect a hotend fan failure).

  • Still not bothering to use Katapult.
  • In order to use two thermistors without running extra wires, I have a PT1000 running into the MAX31865 which frees the regular thermistor port up to run the heatsink thermistor.
  • I had seen some people post variations on the DragonBurner mount for the extruder but the standard one was fine?
  • I ended up using 2 x M3x16mm to secure the extruder mount to the hotend mount and it looks like the PTFE tube needs to protrude from the hotend mount 13mm.
  • To run two fans off of one connector, I ended up checking out NASA’s workmanship standard and decided that if NASA considered it OK to do an inline branch using a solder sleeve for a space shuttle, I’ll use it for my 3D printer.
  • The Dragon Ace comes with Molex Micro-Fit 3.0 connectors for the power and the PT1000. I made up a little jumper bit for the screw terminals and ended up snipping the PT1000’s Molex off and directly replacing it with a JST-SH, which was a bit of a leap of faith but it turns out that the wires were 26 gauge and therefore would crimp.
  • It’s really annoying to crimp JST-SH connectors by hand. I can do it, but it’s annoying.
  • Also, JST-SH connectors need to be 24 gauge or smaller wire, which meant I had to source some extra wires.
  • I’m keeping the “endstop” pins empty and running the tach for the fan into the “Probe Servo” connector where the Z stop would be.
  • I ended up needing to change the config to use a pull-up because the Delta fan has an open-collector output (Most of the time you want to use the ^ to engage a pullup) as well as set the tachometer_poll_interval to 0.0011 because the default wasn’t fast enough for a 10500 RPM fan.
  • There is no PCB holder that has the PUG umbilical. I was poking around designing one but the version I’ve got doesn’t quite work and it holds the umbilical too high. I might just go back to zipties.
  • I have never been able to make any of the quick and easy solutions for holding the belt in place while I swap things work. Ugh. At least I’ve got a musical ear from tuning guitars.

The “Alternative Voron Mounts” section is a bit under-documented.

  • I printed the MGN12H mount with the PCB mount holes, which means that the PCB isn’t mounting to the two spacers but to the lugs on top. You want to insert two square nuts into the slots on the side, that’s where the DIN557 size is right, not the thinner kind. And then there’s a pair of heat-sets that go into the lugs and a pair of heat-sets that go into the bottom where the carriage base connects. Except that one of the heat-sets came loose.
  • I printed the carriage base short version with the X-stop switch mount. That seems to use a M3x8mm screw?
  • I also printed the probe mount for the Beacon which needs a pair of heat-set inserts for the Beacon side and a pair of heat-set inserts that go in the back.
  • There’s also two heat-sets that need to be added to the cowl (I printed the cat cowl because of course) to reinforce the whole works from the bottom.
  • The design calls for a M3x12mm screw to secure the toolhead to the carriage.
  • I slammed the Beacon mount all of the way up. It probably doesn’t matter too much but I figure this is less likely to end up wrong?
  • I’d somehow assumed that the temperature sensor against the heatsink was meant to be a cartridge styled sensor, but the one I put in there had a broken wire right away and another cartridge sensor just straight up failed to fit, so I guess I’ll put a bead sensor in instead.

dragon burner

ASA-GF is … not great?

ASA tends to be less temperamental, albeit more expensive, than ABS.

I’d wanted to print a full Nevermore Micro for the Zero and it warped. So I decided for my next spool of black ASA filament to get some a spool of Siraya Tech FibreHeat ASA-GF to see if that would make my life easier?

As it turned out, it didn’t do any better of a job on the Nevermore Micro. Plus, some of the Voron parts I printed with it just didn’t work because while the fiber reinforcement is increasing the structural strength in the XY plane, it hurts the strength in the Z axis. Plus it feels “itchy” like all fiberglass things. Plus I kept getting filament breaks.

So, while my ABS-GF parts that Formbot printed my Zero with seem to be holding up, it looks GF doesn’t bring any real useful advantages?

Klippain Shake&Tune is great, albeit really annoying to set up in Docker.

After a few dismantlings of the gantry, I noticed that the accelerometer tests were looking super-sketch.

I’d avoided using Shake&Tune specifically because it requires effort to set up. On the other hand, it’s really handy.

What I want is to have declarative and repeatable releases such that I don’t get surprise broken by dependency updates and so that if the SD card gets corrupted on my Pi, I can wipe it and just run Ansible on the fresh node.

Shake&Tune is in a git repo that you clone and link into your Klipper install and it comes with some excellent documentation including images, but I couldn’t come up with a good way to git clone just what I needed without dealing with GitHub timeouts, but at least they ship releases.

So, here’s what my docker file looks like:

FROM mkuf/klipper:v0.12.0-286-g81de9a86

USER root
RUN apt-get update && apt-get install -y git python3-can libopenblas-dev libatlas-base-dev wget
RUN mkdir -p /opt/beacon_klipper && chown -R klipper:klipper /opt/beacon_klipper
RUN mkdir -p /opt/klippain_shaketune && chown -R klipper:klipper /opt/klippain_shaketune

# Install Beacon
USER klipper
RUN git clone https://github.com/beacon3d/beacon_klipper.git
WORKDIR /opt/beacon_klipper 
RUN ls -al
RUN git checkout 730836d40f1bf02b6f1bf08649dcaacca9aee900
WORKDIR /opt/
RUN echo ${HOME}/klipper
RUN /opt/venv/bin/pip install -r /opt/beacon_klipper/requirements.txt
RUN ln -s "/opt/beacon_klipper/beacon.py" "/opt/klipper/klippy/extras/beacon.py"

# Install shaketune
WORKDIR /opt/klippain_shaketune
RUN wget https://github.com/Frix-x/klippain-shaketune/archive/refs/tags/v5.0.0.tar.gz
RUN tar -xvzf v5.0.0.tar.gz
RUN ls -al && mv /opt/klippain_shaketune/klippain-shaketune-5.0.0/* /opt/klippain_shaketune/
RUN /opt/venv/bin/pip install -r /opt/klippain_shaketune/requirements.txt
RUN ln -frsn /opt/klippain_shaketune/shaketune /opt/klipper/klippy/extras/shaketune
WORKDIR /opt/ 

Overall, I like prind, even though I’ve abused it to replace the Docker Compose with Ansible. I have a bias because I do infra for work. The problem is that kiauh works pretty well and it’s only real flaws are those inherent with running inside of mutable infrastructure so it’s a hard sell.

Now, imagine if there was integration with Klipper modules and macros against Mainsail and Fluidd and OctoPrint such that I don’t have to SSH copy my graphs over.

The PF Makes belt tension meter

In the process of building out the Voron, I’d stripped one of the screws on the Y gantry and that axis was a bit off, so I took the opportunity to get a fancy set of West3D’s Berserker MGN9H-1R-350 rails to replace the stock.

I also got the West3D fully assembled PF Makes belt tension meter. I’d been kinda fighting the stock status of it and finally it was in stock when I needed other things from West3D so that I’d get a pre-assembled one that was already configured properly.

I kinda wish I’d had one earlier because it takes a lot of the drama out of the belt tuning process, even though I have good enough ears to tune a guitar properly. I think I had the belts too tight when I built it the first time.

The Dragon Ace so far

I managed to clog the heatbreak, while changing filament. Not sure if this was user error, I probably retracted the filament while the hotend wasn’t hot enough and got it stuck towards the top.

Overall, the design of the Dragon Ace isn’t bad? You get a beefy stubby slot to remove the top part of the heatsink and then you can unbolt the heatbreak. It runs afowl of the Slice Engineering Mosquito patents apparently, or is at least close enough that you have to order it from TriangleLab directly instead of being able to get it on AliExpress. On the other hand, it’s way better than the Mosquito design which has you unscrewing a very long M1.4 screw that faces the build plate so it’s got a high probability of being gunked up.

Apparently the heatblock can be destroyed by tightening the nozzle too hard. And apparently the ceramic heater isn’t all that great. Either way, the specced power for the heater is too much for the V0’s power supply.

Either way, the fill rate is refreshingly high and much better matched for the overall speed of the Trident than a standard flow hot-end.

The SHTv3

Let’s review the options for toolboards, yet again:

  • LDO makes the NH36, which sounded great but the first rev was a disaster and, overall, I haven’t been actually super-impressed with the LDO stuff I’ve procured so far.
  • BTT makes the EBB36 which requires a bunch of messy wiring because it assumes 24v fans.
  • Fystec released the H36 combo board that looks like it’s, in some ways, better than the NH36. On the other hand, there’s one bad review and they pulled the listing from aliexpress so I’m assuming that their first release is going … as well as LDO’s.
  • Mellow makes the Fly SHT36.
  • Luke’s Labs is beta testing the Jupiter toolboard that looks kinda close to overkill
  • I could always not use a CAN or USB toolboard?

Toolheads are somewhat cursed, clearly, otherwise there would be a slate of entirely reasonable boards out there. I definitely feel like CAN bus is somewhat overkill for the printer’s electrical environment and USB is arguably a bit less temperamental. But the thing is, the board is going to get hot from a closed chamber, there’s a giant EMI interference generator right there, there’s a lot of power going through the board, and clearly there’s also static discharge from the filament rubbing against stuff.

Anyways, the Fly SHT36 V3 could be pretty good or at least good enough, however, mine has a broken screw terminal that likes to come loose, plus the LIS2DW seems to be broken, which I’d initially thought was because there was some resistors on the SPI lines before I’d realized that the LIS2DW and MAX31865 share a bus.

Other glichies

  • Some of the Z axis screws came out. It looks like I should probably back out all of the M3 screws connecting to the linear rails and add thread-lock, although I might have more disassembly and re-assembly to go.
  • I noticed that a chip came out of the edge of the A drive so I need to replace that.
  • Bad cPIF part: Some of the hinges were printed wrong. It’s a print-in-place hinge and the two pieces were separated.
  • I thought the idlers needed speedy replacement but the clicking was from the Z axis and they were bending because the tension was too high. I should still replace them.
  • There’s no way to set the nozzle size at runtime for a Klipper printer, which means that I have to disable some of the safety features because I use a lot of different nozzle sizes.

Next up to work on

  • Speed test, further tuning
  • Mount the nozzle brush
  • Figure out the nozzle purge situation. It’s less important to use pellet-style purge with a giant bed as compared to the Zero but I’m realizing that I really like not having purge stripes all over the place.
  • Mount the panels. I printed out some of the Voron 2.2/Annex clips that I’m probably going to use for most of the panels I’d want to remove. The Coroplast sheets for the back seem to be more like 3.5mm instead of 3mm.
  • One of the screws on the right side of the gantry is accidentally a M3 T-nut and so I need to dismantle that a bit to get an M5 T-nut in there. Ugh.
  • Refactor the macros
  • reacted for opsec reasons
  • Nevermore air filter
  • Mount the display. I think I’m going to just put in a simple display instead of the supplied fancy display.
  • Bed fans
  • LEDs for the Dragon Burner.
  • also redacted for opsec reasons
  • Chamber temperature sensor
  • Filament sensor
  • Serial number
  • Replace the idlers and AB motor mounts, potentially try cleedlers, one of the geared cleedlers designs, or maybe the CNC idlers and motor mounts.

Conclusion

tl;dr:

  • I’d feel worse about spending time doing printer mechanic things instead of useful printed things if it wasn’t for some recent Bambu asshattery.
  • For the open-source / open-architecture side of the fence, we need to accept that some of the things that Bambu has done in terms of making printers friendlier should be copied over and included into the standard. The tension meter takes a lot out of the belt process. Shake&Tune is really great and things like it should be more tightly wound into the Klipper ecosystem.
  • Beacon with contact is really really good. I’ve been procrastinating on getting some sort of nozzle cleaning solution setup because I only touch-probe when things have changed.
  • Toolheads and hotend clogs are frustrating.
  • A good belt tension meter ought to be part of any build.
  • It would overall be nice to have a Large-Voron styled mount that comes in two pieces instead of an adapted Small-Voron styled mount for the DragonBurner.
  • The Voron Trident at 300mm bed size invites the design of interesting large things and a Dragon standard flow is not enough, which is not a surprise really. I’m not sure if I’m going to exceed the capacity of the Dragon Ace for practical projects, although I need to see how much I can bump the speed up.

In order to flip the printer upside down to install the new Y rails, I took it downstairs to the living room to have more room to work with. I then decided that I should probably print out a bunch of wiring organizers before I put it back so I don’t need to pull it out a few more times.

Step 6: A CAN do attitude

Manta M8P plus CM4 cooling

What I really want to do is mount a fan to directly cool the stepper drivers and a second fan to directly cool the Raspberry Pi.

So I found one mod that mounts a 40mm fan on the CM4 module and a second mod that mounts a 5015 blower fan in a air duct for the steppers. However, when I put the models together, I don’t think I can use both of them at the same time.

This might be a design project. Not right away.

Systemd yak shaving intensifies

I have this vague uncomfortable feeling that the instructions in the standard CANBus guide are slightly wrong, but I gave up on worrying.

From my reading, it sounds like I would want to skip the ifupdown section because I’m definitely using a fairly modern version of linux on the Pi and it’s definitely using systemd-networkd instead of ifupdown… but for some reason I actually do have to follow both sections of the documentation and that feels a bit weird.

On the other hand, I can’t really find much documentation on using the CANBus inside of systemd anywhere and I gave up messing around and just did both sides and the whole thing works and this is really just silly and while I try not to pile onto the systemd drama situation I’m still somewhat blaming systemd.

I complained to a friend about this and she sent me a “Yak Intensifies” animated GIF.

CAN bus setup

  • I decided to not bother with setting up katapult.
  • Formbot helpfully provided a CANbus cable that had the required connectors and was heat-shrinked… and I had to cut off the heat-shrink cable and some of the insulation to stretch to make all of the connections.
  • The CAN bus cable didn’t come with any sort of fork terminals for the two wires, so I bent them into a J shape to get it going and then got a proper spade terminal to crimp on the wires with my next DigiKey order.
  • Oddly, nowhere in the manual is the meaning of the LEDs on the BTT SB2209 board specified. One of them is the power LED, one of them is the status LED. The Esoterical guide shows you setting that to on at startup if you take the Klipper Config route… which didn’t make sense at first.
  • I accidentally put firmware to have the CANbus hanging off of PB12/PB13 instead of PD12/PD13. Oops! After I got that fixed, things seem to be working.
  • The wiring diagram doesn’t show that you need to put a jumper for the terminator resistor on the motherboard side nor does it show that you need to put a jumper for the terminator resistor on the toolboard side and two more jumpers to set the voltages.
  • There’s two cable-wrap-y thingies. One bag which is nylon-coated seems to be the “Cable Sheath 150mm” from the BOM, which means that it’s probably meant to be cut up and used to cover the other cables. The other bag is AD11.6 corrugated pipe, and that looks to be the umbilical part.
  • The PG7 gland is just perfectly slightly too small to fit a JST connector without being de-pinned. Yay.
  • Wrong cPIF part: I got three versions of the part for the umbilical bridge for the StealthBurner toolhead from my cPIF provider. I got the version for the 2 screw cable chain, the version for the 3 screw cable chain, and then the version for the EBB SB2209 CAN RP2040 board. However, what I need is the Formbot-provided umbilical bridge for the PG7 gland. If I’d thought this through, I might have gone straight to the PUG system.
  • The prind container is installing the can libraries at every startup, which is I guess how Klipper wants to work? I try not to think too much about this because I don’t want to arrive to either the regular Klipper or DangerKlipper communities with a pile of patches. There’s a fairly specific yet also battle-tested way that we tend to default to in the infrastructure engineering world and Klipper doesn’t comply and it bothers me.

X and Y endstops

  • The Y Endstop relocation mod was a bit confusing. Basically, there’s some stuff that’s intended to screw into the gantry that you don’t need. So you unscrew the XY Joint Cable Bridge part, either the 2 or 3 hole version, that you installed during the X axis section and then also the Y axis Y Endstop Bumper part you did during the Y axis section. The XY Joint Cable Bridge is where the bumper for the relocation mod goes and then you unscrew the front two screws from the motor mount and put the switch there.
  • The X endstop just triggers against the XY joint without a special bumper?

Lead up to first print.

  • Formbot ships a filament sensor for you but it won’t actually work, apparently. The pullup for GPIO22 doesn’t work, so either you need to wire up your own pull-up resistor or you need to switch it around… yeah, just leaving that out.
  • The Tap manual klipper config section sucks because it doesn’t actually tell you about the virtual z endstop and the klipper manual doesn’t really cover this very well either.
  • The way the stock wiring is designed, you are wiring a PT1000 through the 4-pin connector, so you want to be configuring the MAX31865. So the toolboard config looks something like this:
# This file contains common pin mappings for the BIGTREETECH EBBCan
# Canbus board. To use this config, the firmware should be compiled for the
# RP2040 with "USB" or "CAN bus (on gpio4/gpio5)".
# The "EBB Can" micro-controller will be used to control the components on the nozzle.

# See docs/Config_Reference.md for a description of parameters.

[mcu EBBCan]
#serial: /dev/serial/by-id/usb-Klipper_Klipper_firmware_12345-if00
canbus_uuid: xxxxxxxxxxxx
# Change the canbus_uuid to somethng

[temperature_sensor EBB_NTC]
sensor_type: Generic 3950
sensor_pin: EBBCan:gpio28

[temperature_sensor EBB_mcu_temp]
sensor_type: temperature_mcu
sensor_mcu: EBBCan
min_temp: 0
max_temp: 85

[adxl345]
cs_pin: EBBCan:gpio1
spi_software_sclk_pin: EBBCan:gpio2
spi_software_mosi_pin: EBBCan:gpio0
spi_software_miso_pin: EBBCan:gpio3
axes_map: z,-y,x

[resonance_tester]
probe_points: 100, 100, 20
accel_chip: adxl345

[extruder]
step_pin: EBBCan:gpio18
dir_pin: EBBCan:gpio19
enable_pin: !EBBCan:gpio17
microsteps: 16
rotation_distance: 22.6789511
gear_ratio: 50:10
nozzle_diameter: 0.400
filament_diameter: 1.750
heater_pin: EBBCan:gpio7
sensor_type: MAX31865
sensor_pin: EBBCan:gpio9
spi_software_sclk_pin: EBBCan:gpio10
spi_software_mosi_pin: EBBCan:gpio8
spi_software_miso_pin: EBBCan:gpio11
rtd_nominal_r: 1000
rtd_reference_r: 4300
rtd_num_of_wires: 2
control: pid
pid_Kp: 22.518
pid_Ki: 1.532
pid_Kd: 82.753
min_temp: 0
max_temp: 350

[tmc2209 extruder]
uart_pin: EBBCan:gpio20
run_current: 0.2
stealthchop_threshold: 999999

[fan]
pin: EBBCan:gpio13
max_power: 1.0
kick_start_time: 0.5 # Depending on your fan, you may need to increase this value if your fan will not start
off_below: 0.13
cycle_time: 0.010

[heater_fan hotend_fan]
pin: EBBCan:gpio14
heater: extruder
heater_temp: 50.0

[neopixel hotend_rgb]
pin: EBBCan:gpio16
chain_count: 3
initial_RED: 0.3
initial_GREEN: 0.0
initial_BLUE: 0.9
initial_WHITE: 0.0
color_order: GRBW

[probe]
pin: ^EBBCan:gpio22
x_offset: 0.0
y_offset: 0.0
z_offset: -1.600 # You need to tune this
speed: 15
lift_speed: 7.0
samples: 4
samples_result: median
sample_retract_dist: 2
samples_tolerance: 0.01
samples_tolerance_retries: 10
activate_gcode:
    {% set PROBE_TEMP = 150 %}
    {% set MAX_TEMP = PROBE_TEMP + 5 %}
    {% set ACTUAL_TEMP = printer.extruder.temperature %}
    {% set TARGET_TEMP = printer.extruder.target %}

    {% if TARGET_TEMP > PROBE_TEMP %}
        { action_respond_info('Extruder temperature target of %.1fC is too high, lowering to %.1fC' % (TARGET_TEMP, PROBE_TEMP)) }
        M109 S{ PROBE_TEMP }
    {% else %}
        # Temperature target is already low enough, but nozzle may still be too hot.
        {% if ACTUAL_TEMP > MAX_TEMP %}
            { action_respond_info('Extruder temperature %.1fC is still too high, waiting until below %.1fC' % (ACTUAL_TEMP, MAX_TEMP)) }
            TEMPERATURE_WAIT SENSOR=extruder MAXIMUM={ MAX_TEMP }
        {% endif %}
    {% endif %}

(Note: I initially had set the rtd_nominal_r to 100 and rtd_reference_r to 470, which would be the correct values for a PT100. As far as I can tell from the MAX31865 datasheet, it’s actually setting the ratio between RRTD and RREF on the device, where the base resistance (which is the differentiator between PT100 and PT1000 sensors) is set via the DIP switches, thus 100/470 = 1000/4700. I didn’t seem to notice much of a difference when I tested but other people had different results.)

  • I realized that the most recent time I’d wrapped the belt, I’d accidentally not gotten them around the front idler wheels, so I had to fix that and tighten everything up. The belts on the Zero were, for whatever reason, infinitely easier to deal with.
  • Finally, I can go back into the Tap and Stealthburner and EBB SB2209 manuals and finally put the thing together!
  • The Formbot PDF instructions that explain how to use their hinge system doesn’t mention that you should probably trim the piece of AD11.6 conduit they gave you. Presumably it’s meant to work on the 350mm x 350mm bed. They also fail to mention that you need to de-pin the CAN connector. I’m not overly happy with AD11.6 conduit. I’m probably going to redo the umbilical.
  • I decided to use the Lever Connector Mount using Side Fan Supports to wire up the two side-fans because I don’t think I have any cases where I would want just one of the pair of side fans running and it simplifies the wiring overall.
  • I also printed some pieces from the Modular Cable Management Clip set. It would be really cool if I could print a long version of the clip to completely hide the cables but if I scale the Z-height of the clips, I end up with a very very rigid clip.
  • I managed to put the hotend cooling fan in backwards. Oops. Generally the label faces inwards, although I’m betting there are some fans floating around that have the label on the wrong side because that’s just how things are.
  • Again, the Tap manual is not really useful here. If you go through the startup guide you can mostly follow the first part. When you get into the Bed Locating section, you can ignore the Z-endstop section (because there isn’t one). You can define the zero point as usual. You can ignore the Z Endstop Pin Location section. You do want to run the Probe Accuracy check. You want to run that a bunch because for whatever reason the accuracy gets better after it’s probed a few hundred times. You want to do the PID tune as normal. And you want to do the whole Bed Level process as normal. The Z offset adjust is silly because you want to do PROBE_CALIBRATE instead of a Z_ENDSTOP_CALIBRATE because there is no Z endstop.
  • I backed off the tap required accuracy.
  • Also there’s some Y loss from the Tap sensor. In my case, I’m losing maybe 5mm off the back of the bed.

First prints

I used the default SuperSlicer 2.4.x profile for a Voron 1 because I figured it wouldn’t stress the machine but would otherwise be mostly working. I loaded up the cube… and there was a tangle in the drybox partway through the cube. Oops!

  • I copied most of the calibration settings over from the Zero because they both have the same hotend.
  • Also I had to mess with the z side position_min setting to give it enough upward travel to avoid the “No trigger on z after full movement” error message.
  • I ended up wasting some time to get things migrated to a version of the better print_start macro.

Finally, I started making prints. I decided to print a compliant cable clip because that’s an actual useful item but also relatively good to understand if the printer’s OK. After two of those, I printed the Gridfinity bin that I was frustrated about because I wanted it but it was too big to fit on the Zero’s bed.

printing

So far the tally is that my Voron Trident has printed zero calibration cubes and zero benchies.

Labor Day sale

My long-term plan has always been to run either a Dragon Burner or XOL toolhead to replace the StealthBurner and also to replace the Tap with a Beacon probe.

Coincidentally there’s a 20% off sale on the Beacon site.

Next up to work on

  • Motion compensation measurement and adjustment, making it print faster and cleaner.
  • Bed meshing. I was kinda thinking of using the KAMP plugin but Klipper has native meshing at this point and that’s one less thing to install.
  • Mount the Pi’s heatsink
  • Mount the nozzle brush
  • Figure out the nozzle purge situation. It’s less important to use pellet-style purge with a giant bed as compared to the Zero but I’m realizing that I really like not having purge stripes all over the place. Because of the Tap sensor I can’t put the pellet bin in the usual place.
  • Mount the panels. I printed out some of the Voron 2.2/Annex clips that I’m probably going to use for most of the panels I’d want to remove. The Coroplast sheets for the back seem to be more like 3.5mm instead of 3mm.
  • One of the screws on the right side of the gantry is accidentally a M3 T-nut and so I need to dismantle that a bit to get an M5 T-nut in there. Ugh.
  • Refactor the macros
  • Nevermore air filter
  • Bed fans
  • Dragon Burner or XOL and Beacon
  • Filament sensor
  • Serial number

Conclusion

working printer

The Trident is sitting where my Ender 3v2 used to sit. It’s not finished but it’s usable. And, like my Zero, the first prints actually look pretty darn good.

It’s a bit of a relief to be solidly in the “using it” side of the fence? There’s other things going on as well that have distracted me from building the printer but at the same time, there’s a bunch of half-finished projects that I can wrap up now.

Step 5: Toolhead and final integration prep

The eventual Dragon Burner upgrade

While purchasing things I keep thinking that maybe I should just get the much-hyped Nitehawk 36 and just go straight to DragonBurner.

But my LDO Sherpa was a pain in the butt that left me asking “Wait, isn’t LDO supposed to be the people who don’t send you weird semi-working shit with no manual?” So I decided that I’d wait a bit and see what happened.

This seems to be a good call. The NH36 seems to be a bit of a disaster in terms of early failures.

Not sure. I kinda wanted to be able to run 5v fans. The BTT EBB36 toolboard doesn’t make that easy; I’d have to run extra wires and stuff. There’s a Mellow toolboard that does, but the documentation’s lacking and I guess people had some reliability problems. Or I can wait till the NH36 situation is fixed?

ClockWork 2

The Formbot gear set is a little odd. I thought I was missing parts? It turns out that it’s just differently designed. Instead of the needle bearings on the inside of the BMG idler set, there’s two tiny little bearings that go on the shaft to hold the idler gear in place and the red main gear is an integrated assembly. This is the gears you get:

gears

  • “Tighten until the plastic bends and cracks. Back up 2 turns, discard parts, reprint and try again” is probably a little too jovial.
  • Overall, this went fairly fast, probably because it’s mostly like the Zero’s MiniSB.

Tool Cartridge

  • Missing part: You need a M2.5 × 8mm screw (I think - the mount is 5mm tall so 3mm into the DragonBurner sounds about right?) to mount the Dragon SF into the tool cartridge, but you don’t get one in the default kit package nor do you get one in the separate package that contains the Dragon.
  • The measurement is nice (11mm) but a jig would still be better.

StealthBurner

  • I hate it when it’s the “flair” features of the printer that get fiddly when building. In this case, the logo LED took a lot of effort to get it all snapped down right.
  • This is the classic manual-flipping problem. I’ve gotta interweave between the Trident manual, the StealthBurner manual, the Tap manual, and then the EBB SB2209 CAN manual.

I’m skipping out on actually installing the StealthBurner and TAP until I’m ready to start the bringup process. When I was building the zero, I started with the power supply hooked up and verified that it was behaving and then added electronics a piece at a time and I’ll probably do that this time as well.

Wiring prep

  • I thought that two of the brackets I’d placed were in a safe position, but it looks like they’ve got to go. Not sure how rigid the frame is at the moment.
  • I’m doing the inverted electronics mod, so I had to spend a lot of time figuring out what direction some of the brackets were there to go.
  • Some folks on the Voron discord were mentioning that the SSR’s tended to get a little hot in 110v countries for much the same reason why electric kettles suck. I’d done some random looking around for heatsink solutions and decided to try a cheap uxcell fin heatsink for SSR’s hoping that the height was such that it would fit inside of the inverted electronics bay with the SSR on top and that the ears did what I thought they were doing. And it fits! What’s not entirely evident from the description is that there’s a pair of ears that slide over a DIN Rail, so I looked forward to where the SSR was supposed to be and put it on that DIN rail and then installed it using the inverted electronics brackets and I’ll probably add a DIN clip to either side just to keep it from jiggling.

Electronics

This is where the Formbot config starts to differ:

  • Instead of the wago 221-415 lever nuts for neutral, live, and protective earth, there’s the 3-to-6 board.
  • Instead of the separate pi and controller, there’s a Manta M8P board.
  • Similarly, there’s no 5v PSU.
  • The X end-stop is wired through the toolhead board and so you mount the bumper to the stepper motor and then the switch gets screwed into the Tap, I think?
  • The Y end-stop is wired up to where it usually is, I think?
  • This has no cable chains other than the Z axis.

As far as assembly…

  • For first power-up, I had Crafty Sorceress as the designated safety person in case I screwed up somehow and zapped myself.
  • There are no M3×10 FHCS screws for the filtered inlet; I used M3×12 FHCS screws instead.
  • The electronics bay arrangement was a bit dicey and I had to yank everything out and start over. The instructions say “Note: the DIN rails should be parallel to bed extrusions. or else, the wires may be not long enough.” and I’m not sure what that means. After the re-arrangement, everything seems to fit.
  • The Fabreeko edge-to-edge heater bed’s thermistor cable wasn’t quite long enough. There’s an extension cable meant for the nevermore config the way they are doing it, which I’m not going to do, so I am using that instead.
  • The diagram indicates that there’s one screw holding the side-skirts on, but there’s two, presumably because I’ve got the 300mm version.
  • I am replacing the provided stock 60mm fans with CFM-6020V-237-280 fans.
  • I printed the Y Endstop relocation mod to replace the endstop pod.

Provisioning with Ansible

For the most part, I’m able to re-play all of the same provisioning bits from the Zero, with a few of the steps forked such that the Zero files get put on the Zero’s pi and the Trident’s files get put on the Trident’s pi.

There was a good template for getting started with the Zero but there’s not one for the Trident. I ended up wasting a bunch of time because I’d screwed up some of the pin mappings. For a short period of time I thought I had a bad board.

Conclusion

It’s powered up and starting to work out…

closer to ready

What’s left, I think, before I can start trying to print a cube:

  • Set up CAN interface.
  • Provision the toolboard
  • X and Y endstops
  • Tighten the belt to spec
  • Install the tap + stealthburner

Step 4: Frame and bed

Getting tired of not having a large printer, actually.

Also, I have a bunch of other stuff going on.

Tap

Okay, so two problems here… First, the manual is from Tap R6 and then there’s an errata file explaining what the differences are. Second, part of why you are urged to build a stock-configuration Voron is to avoid flipping around in the different manuals except that if a Voron comes with a default Tap, you can’t build it as a stock-configuration Voron, so flipping between the different manuals is a requirement.

Oh yeah, and I’m not sure if, were I to be a core Voron designer, I’d make Tap the default. Things are enough in flux these days.

Either way, I feel like if someone wanted to make a lasting improvement to the Voron infrastructure, making it amazingly easy to do documentation updates while retaining the existing positive qualities of Voron docs is probably a huge thing. What I get is the R6 manual with R8 errata and no clear directions for how to build a new printer with Tap and what I want is an R8 manual and enough hints in the Trident/V2.4 and Tap manuals such that I can assemble things.

  • When I first got my PIF parts kit, I was worried that I wasn’t going to get the parts for Tap but after looking through the parts, I realized that they were there, in an unlabeled bag, so all is well and the system works. Unfortunately the two magnet holders are a little bit roughly printed.
  • On pg 28, the Tap manual blandly assures you that “We could say that there is only one way they fit, but we don’t want to underestimate you” and … sure … but how is it supposed to fit? I think what it meant to say was so that you can see the heatsets through the side.
  • The rail comes cut to the correct length already but you still need the spacer piece, which they also provide.

X Axis

  • It would be really nice to remind the user on pg 99 which extrusion is used for the X axis instead of a bunch of pages later because I was getting all of my bits together.
  • I had a bit of a struggle because I was inserting the wrong bolt into the wrong hole and I had to go back and look carefully at the images.

Belts

Folks usually say that the full-sized Vorons have easy to work with belts compared to the Zero… This did not turn out to be the case. I have spent a lot less time on the Zero’s belts than this.

  • Okay so now the part where I get to flip between manuals. On pg 29 of the Tap manual, there’s some M3x6 BHCS screws that the instructions suggest I thread through the center part but it doesn’t tell me where. I’m assuming those are going into the carriage on the X rail.
  • My cPIF provider printed the tap center part in black not the accent color. I guess I get no love from my cPIF provider. (That was a pun)
  • Now I get to flip into the R8 errata file and realize that the tap center needs to be taken off the X-rail again so I can put the belt covers. The illustration there is quite unclear because I thought there was only one belt-cover, not two. Either way, now that the center is installed with the new belt covers, we’re in a situation where I can actually thread the belts.
  • The Formbot Trident kit comes with two separate belts instead of one giant belt, although I ended up feeding one side through and using that to gauge the belt length anyway and then trimming both belts. This turned into a disaster. I thought I’d fed it through properly and left a reasonable length. I used a low-squish belt clamp to try and keep the two belts aligned while I tried very carefully to get exactly the same number of teeth. And then when I tried to lace it up the gantry wouldn’t be trammed right, which generally means that there’s the wrong number of teeth and it definitely felt like the first time through I might not have actually fed it properly. So I tried a few times and then gave up and ordered a fresh belt.
  • The second time, I tried a different approach. I printed a bunch of back-to-back belt aligner clips and used them to split the entire length of the belts into two identical pieces and then fed the whole length through, which seems to have done the trick.

Bed

  • As before, I’m streamlining the Fabreeko magnet bed that’s stronger and stickier as well as the Fabreeko bed heater that’s sticker and covers more of the plate. The only downside is that this Fabreeko magnet sheet is precisely sized to the build plate with no excess, which made the process a bit nerve-wracking. But, same technique as the Zero.
  • I found the blind joint alignment nut to be quite handy for keeping the bed extrusions from getting all floppy. If I could go back, I’d suggest people print a plate of them at the start and use them in all of the blind joints.
  • It looks like there’s no Z-endstop because the Tap replaces that. There’s no parts for making one regardless.
  • I realized that I’d probably want to put in the frame thermistor corner in before I got much father, so I printed and added that one.
  • Formbot provided a Bakelite insulator to replace the M4 thumb nuts that are usually used. I’m not sure how well they compare to the Ultem spacers that some people have been using but I’m imagining that they are far better insulators than a chunk of metal.

The Fabreeko Honeybadger Bed

The Formbot bed has the thermal fuse wired into the wire bundle. Apparently this isn’t super-great because this means if the thermal fuse pops (which it will, eventually) it’ll be annoying to replace it.

The Fabreeko Honeybadger bed doesn’t have the thermal fuse wired in. Furthermore, it’s got a funky wiring scheme that lets them ship a single bed that can either work in 110v or 220v mode. The 110 wiring diagram looks like this:

Bed wiring

I ended up making a parametric Wago 221 mount based on an existing OpenSCAD generator from Thingiverse. If you leave it at the default settings it’s almost exactly the same geometry generated.

wago bed mounts

Conclusion

bed and motion mostly done

We’re finally at the “it looks like a printer” portion of the build.

Step 3: Y and Z axes, and some side-quests

I ended up on a few side-quests while doing this.

See, I want the inverted electronics mod. The key part of the mod is, of course, the brackets that flip the DIN rails upside down. But also you have modified Z stepper motor mounts that don’t grip the panel anymore. Except those are going to get hot and so they really needed to be printed out of ASA, so that provided the final push for me to get my Zero printing high-temperature materials which led off on a few more side quests.

Then I had to switch gears to wrap up a project that a nice lady has been waiting on me to finish.

And then I had the soldering iron out and decided to just read forward in the manual and put in a bunch of heat-set inserts before I continued, such that I wouldn’t need to pause my assembly process to add any more heat-sets.

Y Axis

The frame is pretty flexy. I spent a bunch of time squaring the frame at the start but even though I got things fairly tight, everything worked itself loose and so pretty much everything has fallen out of square, just from moving it around to get the right working angle.

As I’d written previously, you can get a HCJ5 screw joint that will make the blind joints keyed. There’s also the keyed Mismui corner cubes.

I got some aftermarket 2020 nuts and it turns out they are also pretty annoying. I got one batch of M5 nuts will actually pop in mostly OK, but the M3 nuts from the same manufacturer won’t and the M5 and M3 nuts that I got also won’t. All of the nuts, including the out-of-spec ones that came with the printer, work perfectly well if you put them in pre-assembly.

Getting enough actual drop-in nuts from Misumi USA adds up fast, BTW.

Furthermore, I thought I had a reasonable rule to sort out the extrusions but it turns out that I was wrong.

I was thinking that it felt weird to not have a laundry list of things to preload ahead of time, given that I built a Zero first, but I think the easiest road forward is to just treat it as a Zero and preload a bunch of nuts.

While I was disassembling it, I realized that the orientation of the T-nuts that they show in the manual is important. If you orient them as the manual suggests it tends to result in the screw holes being exactly where you think they ought to be, which is helpful.

I’m also adding some right-angle 2020 extrusion reinforcements and corner brackets for 2020 extrusions to some corners where it looks like I can get away with it.

So I squared the whole thing all over again. With the added bracing, now I can rotate it to get the right angle without worrying about things going out of square. I’ll see how it works out and remove them later on if they get in the way.

Z Axis

  • In order to do the inverted electronics mod, I’ve gotta slipstream in the modified stepper mounts.
  • Missed 4x M5 T-nuts in my pre-loading binge but thankfully the M5 nuts I got are actually fairly happy being jammed in there.
  • While assembling the three Z joints, it just says to put an M5 nut in there, except that it’s going to just fall out if I do that. I read forwards and it looks like eventually an M5x16 bolt goes through there, so I’ll add that now so that the nut doesn’t go flying.
  • Also missed some nuts on the skirt. What I ended up needing to do is thread a bolt into the nut and kinda yank it around.

I wanted to get to the end of the Z axis section. It was a bit tricky getting to the end of the chapter but I guess it was either defeat or the feet.

Conclusion

Y and Z axis done

  • There’s several large projects that are blocked on account of not having a full-sized printer, so I really really want this done.
  • The frame is really flexy with the thing partially assembled even with some braces added.
  • At this point, with the feet on, I can now look and think and decide just how badly I want a 300mm Z axis or if I should stick to the 250mm.

Step 2: Stopping at the Y axis

An accidental clee day

I noticed that, because of Clee Day on the Voron Discord, West3D had a deal on titanium backers and a kinematics mount. So I was planning on getting steel backers and the kinematics mount later, but I guess we’ll have those on the way now.

Siboor Trident R1 vs Formbot Trident Pro

This came out after I’d ordered my Formbot Trident. It’s interesting! I look forward to people’s build logs.

Neither printer is going to have a taller Z-axis, you need LDO or MagicPhoenix CBT Pro to get that.

Using Cartographer instead of TAP is interesting. I wonder if there’s going to be a usable mode for some sort of Z-tap mode on the Cartographer in the same way as the Beacon has to make nozzle change and different print surface thickness a problem of the past.

The CNC components are interesting. The plus side is that they won’t break and they let you reach Forbidden temperatures. On the other hand, a lot of folks have spent a lot of time explaining why they don’t really improve your in any useful fashion, although the AWD mod is designed for CNC instead of printed parts… so maybe that’ll be better?

This one has the Manta v2.0 instead of the v1.1 on my Formbot. I think there was like 1 or 2 things that annoyed me about the 1.1 that made me want the 2.0 but I am presently forgetting.

I am glad that everybody’s putting in filters these days, although overall I am more a fan of the overkill StealthMax than the included Fume Pack or the smaller Nevermore Micro.

And, dono, I was probably going to do the Monolith Gantry at some point for mine, the sheet cooler was a thought, etc. The only thing that feels supremely wild is the beefy motors that may or may not make a useful difference to speed or print quality but definitely might score you drinks at the super-secret Voron cabal meetings.

My big concern about most of these kits is that we don’t have an organized fashion for kit-makers to communicate how they have deviated from stock, nor is the manual well-constructed to make it easy for deviated printers. The problem is that if Siboor doesn’t provide adequate support and self-help resources for their modded printers, it’s going to end up being an unfair drag on the Voron community. And this is really the same concern I have with the printer I actually purchased, it’s just that the Siboor one goes farther off.

Obviously, most people build a Voron only because they are prepared to actually go all of the way and, furthermore, an unmodded Voron is kind of a sad Voron. Also, if we’re looking at the kits people tend to get, there’s presumably a lot of Siboor kits out there.

Ugh wrists

So I’m pretty sure I strained a tendon in my right wrist while I was building the zero. SO I looked at the Project Farm and Torque Test videos and decided that the Skil Twist 2.0 looked the most reasonable for something to reduce the wrist-stress. I already have a set of reasonably good Makita metric drill bits and accessories but I did pick up some Ball-End Hex bits and a flexible shaft from McMaster Carr.

The problem is that blind joints need to fit inside of the blind joint hole and these won’t, so it’s not useful for the frame itself. Otherwise, it’s nice and most other things don’t use a wrench hole.

Linear Rail prep

I couldn’t print a bathtub for the rails so I ended up using a 2.5 gallon ziploc bag, which was kind of a mess because the bag leaked. But the rail lubing was a lot easier the second time around.

Component prep

Pg 13 on the manual and the BOM generator both suck and there is already a bug report. For my 300mm bed size build, I was able to spot the A extrusions (there’s 9 of them) and then the B extrusions (there’s 4 of them, with the particular set of holes). The C and F extrusions are the same length, the difference is that the C extrusion is tapped and the F is not. Then you end up with a pile of short extrusions. For the 300mm bed size, the H is the shortest, the G is only 2mm longer, the D is a bit longer, F is longer, then the rest. If you are building the even larger 350mm bed size Trident, the same sorting order should apply.

Ideally the kit-maker should just label the darn things. However, the BOM generator should show the letters of the extrusions and the manual should contain a better phrased of what I just wrote. I got the sorting order wrong, so I’m not sure what the right way is to sort this out.

Frame

Misumi makes an HCJ5 screw joint for 2020 extrusions that contains an BHCS M5 screw but has this little metal bit that makes the alignment process just a bit easier. Presumably a kit-maker could make some cut-rate version of this part and bundle this as a real pro feature. Or, I dono, you can always just buy a bunch of them, at $1.93 each for I think 21 of them?

The frame was a fairly quick assembly, it’s just that it’s a lot bigger than a Zero, so I ended up needing to get it to it’s designated spot on the shelf. And I used my 1-2-3 blocks and clamps to square all of the joints up. Basically, 1-2-3 blocks are supposed to be very square and if you get a pair or a set of four, they should be square in exactly the same way and dimensioned exactly the same. You could also use an engineer’s square but the nice part about 1-2-3 blocks is that they are heavy chonky things that are easy to clamp to and presumably more square than a cheap cast 90 degree clamp.

I ended up using a set of calipers to measure things to get the two middle A extrusions at the right height because using the extrusion as a reference only works with the 250mm version and I don’t quite trust the printed spacers.

Oh, and a note about my shelving unit: I designed it to replace an IKEA wire shelving unit that used to live there and it turns out that a shelving unit a smidgen bigger than 24 in × 24 in was about the right size, so I built it out of 2020 extrusion because that way it’s sturdy yet flexible. I assumed that I’d eventually replace my Ender 3v2 with something bigger, so I ended up looking at the size for a 300mm × 300mm × 300mm Voron 2.4 or a Jubilee printer or maybe just a CR-10, took the largest dimension of any of the three of them and used that to make a reference cube for the shelving design. So it was no surprise that it fits, but it’s good that it really does.

So, yes, I’ve got a 2020-extrusion based printer sitting in a 2020-based shelving unit.

Frame on a shelf

A/B Drive and Idler

  • The included shims on the Trident kit are a lot less variable than the Zero’s. I still decided to use the shims I got from McMaster-Carr.
  • Also, I wanted to start the printer on an auspicious day in my spouse’s faith but wasn’t ready to actually order the kit, so I got some F695 bearings and some hammerhead M3 nuts. I’m using the F695’s I got on the auspicious day for the set of bearings on the idlers.
  • The cPIF parts in bags with labels make it a lot easier to find stuff than the intricately packed foam sheets.

A and B drive and idlers

Y Axis: blocked by bad nuts

I was going to stop at the A/B Drive and Idler step, but I noticed the next step needed the roll-in nuts and I might as well see how well they fit… and yep, both the M3 and M5 roll-in nuts are the bad batch.

Bad nuts

This is a bit easier for me to critique because I’ve got some genuine Misumi roll-in nuts, which I use to mount things on the shelving unit. You can see one of my Mismui nuts to the left side of the picture, with the supplied nuts on the right side. And the supplied nuts, they work as pre-assembly nuts if you want to do your Trident build the way you’d build a Zero with all of the nuts pre-loaded or you can kinda maybe sometimes crunch it down such that it acts as it’s supposed to, except not very well. Because the Mismui nuts work, it’s clear that someone just didn’t quite make it to the right tolerance.

So I decided that this was enough for this weekend and sent a message to the support address instead of fighting with it. I’m just savoring the irony that I got a bag of hammerhead nuts instead of a bag of roll-in spring nuts.

Conclusion

Considering that I did the Zero first now a Trident, everything feels absurdly giant! And it feels weird to not have a laundry list of things to preload ahead of time, it feels like I’m screwing up.

Step 1: Prep work

I figured it was time to order my Trident because my Zero was starting to print reasonable and clean prints, except that I was in the middle of some projects that required a larger print bed. Remembering that the Zero took a while to show up, I put in the order and kinda forgot that I was getting it from the US warehouse and maybe I should keep a closer eye on the delivery date.

Thus, it was a few days into the week where I was not supposed to do lifting or housework.

Which meant that my spouse comes upstairs and tells me that she got the giant heavy box inside but if I wanted to get it upstairs, it could wait until I was better. And how big is this printer going to be anyways?

Which meant that this conversation happened:

300x300 millimeters right?

The problem wasn’t that I was being difficult or trying to re-enact the meme, it’s just that I realized that I had hit the second frame of the meme and I couldn’t respond because I could see the meme in my mind’s eye.

Kit selection

There are three popular expansions of CBT. The first is Cognitive Behavioral Therapy, a well-regarded drug-free treatment methodology for conditions such as depression. The second is the one people often find when they search for the first and regret. The third is the MagicPhoenix CBT kits, where CBT means CanBus + Tap.

I was planning on getting a CBT kit but they are out of stock and if I look around the official Voron discord’s channel for them, it sounds like they have gone eerily silent. I’m not sold on the Tap, the CanBus seems like an upgrade, and the full 300mm Z axis would be really really nice.

The LDO kit has the full 300mm but it’s pricier and out-of-stock as well. There were some noises that there’s a new Trident on the way out but it sounds like it’s not a new Trident version, it’s just that LDO is making their kit fancier.

Thus, it looks like I might as well use the Formbot kit, and when I was ready to get the kit, the new “Pro” version arrived which has CanBus and Tap and some other bits and pieces… but not the 300mm Z-axis. Given that I kinda want to DOOMCUBE it, I can actually fix this down the road either by getting a set of the LDO steppers or by switching to a belted Z or deciding that 250mm on the Z axis is just fine.

The Voron discord is fairly negative about the high-flow Dragon but the standard-flow Dragon sounds fine. Mostly, I’m not printing speed-benchies here; what I want is good print quality but fast, where I can always add a CHT nozzle if I need more performance, so I’m leery about an overly high-flow hot-end. It feels most reasonable to have two identical hot-ends, at which point I can figure out what my performance limits look like and then upgrade then.

The Doom Tri

There’s the Trident-EZBake otherwise known as the “DOOMCUBE Trident”. Basically, replacing some of the 2020 extrusions with 4020 or 4040 extrusions. It’s a bit of a choose-your-own-adventure but the advantage of the is that you can insulate the printer better.

Presumably, at some point in the future, I’ll start in on a project where I do this, and at that point I’ll also address Z-height if I want.

Filter options

It feels like the goal is to be able to switch airflow setups and take advantage of having more room than a Zero. Obviously there needs to be some experimentation. But ABS likes a hot chamber and also it puts out a lot of VOCs so you want a configuration where there’s minimum outflow, basically just what is necessary to create negative pressure and/or prevent it from overheating. And then PLA wants a room-temperature chamber and it would be nice to have the airflow out be enough such that I don’t need to open the doors and lid. Which, obviously, might not actually be possible.

I figure a VOC sensor inside of the printer chassis is a requirement over time.

Some options for the Trident:

  • Nevermore Micro - The V6 version is much improved over past revs, doesn’t require you to sing “CUT MY FAN INTO PIECES / THIS IS MY LAST RESORT” while building one. I have the mechanical bits for a Nevermore Micro in the box with the printer.
  • THE FILTER - Positioned so as to better act as a bed fan than the Nevermore filters.
  • Nevermore Mini - Adds a HEPA filter and more filter medium, better positioned so as to circulate air within the chamber.
  • StealthMax - This one is interesting because of the exhaust slider and overall largeness.
  • Voron HEPA exhaust filter
  • BentoBox V2

The StealthMax is the most interesting because presumably with the exhaust slider, it’s most of the way there. Versus using an internal filter that’s just recirculating and then an external filtered exhaust that can be throttled and/or closed off.

Klipper + Docker + Ansible

My end-goal here is to apply a single Ansible role to both a Trident and a Zero such that both printers look and act alike and have the same klipper macros.

Given the Formbot kit just moved to a Manta, this also means I need a Pi compute module.

Other mods and odds

I suspect the Trident is going to end up with fewer added mods streamlined in than the Zero, especially because there’s not the same thing with preloading nuts.

Looking at the fans and where they are used, it looks like I might stick with the electronics compartment fans sized the same, just the quieter versions thereof, instead of doing a larger-scale skirt mod.

On the Voron discord the Trident Inverted Electronics mod was suggested as one of the few mods that you would want to do to a stock printer.

I probably want the Xol toolhead or maybe the DragonBurner on account of either one being lighter and with better cooling and there was discussion there that suggests that the best extruder for flexibles is the Vz-Hextrudort-Low but with the straight gears instead of the angled gears.

I kinda want to replace the Tap sensor with a Beacon now that it can work as both a radar sensor and a touch probe. At some point.

The Kinematic bed and the Monolithic Gantry sound like some other improvements.

I’ve already got a lot of the spare bits (screwdrivers, bearings, et al) and required tools.

Comparing the Formbot Trident printables folder against the stock

For a while, Formbot helpfully gave you a giant zip file containing “their” printable set. They applied their own organizational scheme which I guess might be helpful in some cases, but it’s also a bit of a hassle.

When I looked in, I found the files to be a mish-mash of stuff. There are files missing, where I’m not sure if that means that I don’t need them (for example, because it’s CANBus + Tap) or because somebody forgot, because the Formbot discord already contains examples of people finding missing files. And then there are some files that seem to match prior versions of the repo. So it feels like a mess. And Formbot took it down and promise to put up a GitHub repo shortly.

Paraphrasing what I wrote on their discord, the things you want to know are:

  • What mechanical deviations from stock to expect - for example, the 3 to 6 board, the wiring’s a bit different, etc. This is already generally there in the ordering page, but it’s nice to have as an independent reference.
  • What parts we shouldn’t print, either because they aren’t necessary or because they are replaced by one of the custom files.
  • When given a choice between multiple parts (e.g. 2 hole or 3 hole chain link) which one to pick.
  • Links to the required mods, where appropriate (this is in the PDF already, at least for the Trident).
  • Presumably what git hash on the upstream the kit is built around (e.g. if they do a point release for the Trident files on git down the road, we know what the stable long-term reference is)
  • A changelog of changes to kits sold under the same name (e.g. if the Trident Pro changes things, that would be a good call-out, but if you call it the Trident Super because it’s got some new fancy feature, that’s an obvious difference)

It’s obviously easier to store these on a git repo, especially if there’s multiple versions or bugfixes.

I can definitely appreciate that for the mods you might still want to package those because Printables is not really a git-style repository where you can provide a git hash.

I’d also suggest that it’s probably better to not fork the repo to create a customized repo unless you are intending to actually fork the printer.

cPIF

When I asked on the Formbot discord what to tell PIF providers, it was suggested that I explain what version of the kit I had. So I added that to the “special instructions” on the Formbot and crossed my fingers.

I think I got what I needed out of the commercial PIF program. I’ll find out as I go. Thankfully all of the important parts are designed to be printed on a V0, which I presently have.

It comes in bags with labels on the bags indicating what’s in the bag by filename, plus a mysterious unlabeled bag that’s all of the extra bits that I need. I was worried that I wasn’t getting the complete parts kit for a while before I compared the STL files against the parts in the unlabeled bag and realized that’s where the special Tap parts and everything lived.

I think the packing method is actually fine as compared to the way the Formbot printed parts kit for the zero came in a foam box, outside of shipping constraints, because I ended up sorting the Formbot parts for the zero into bags anyway.

Formbot Roll-in nuts

Apparently some folks have been having problems with the roll-in nuts provided with the kit. I will see what happens there.

It’s time to start

One of my tasks was to get the Ender 3v2 mostly back together and get all of my little spare parts and stuff specific to that printer bagged up for whoever I offload the printer to.

Empty shelf ready for a Trident to arrive

Posted:

Updated: