#Help deciding switch from ERCF to BT

1 messages · Page 1 of 1 (latest)

quasi thunder
#

I built the ERCF/ERCT about 6 mos ago anf it works great when it works but about every 10 to 20 hours of printing an issue usually shows up, mostly dirty encoder. I also hate the buffers, to load my system I have to get on a step ladder. I currently use Happy Hare with Happy Hare Klipper Screen. The ERCF is feed through Canbus board. Their is good videos on HH (Silverback) tunning but I am having trouble finding much info on setup for the BT. I am a GOOD builder but an average software installer. HH website says HH can run BT. So my question is how painful will the switch from ERFC/HH to BT/AFC be, do I uninstall HH, HH Screen and start from scratch? I know this is a work in progress I am trying to decide live with what works most of the time and wait awhile longer for the BT project. Advice appreciated.

viral haven
#

So, a question is, what macros are you using for purging and stuff in HH?

#

If you’re using a toolhead cutter, the swap is as easy as copying locations for macros to start at and setting positions for poop/kick if you want to use them

#

There is currently no support for Blobifier (afaik)

#

Otherwise, if you build as the instructions and documentation say outline, the configs are pre-written basically

#

Only things to adjust are Bowden lengths really, and there’s some automated stuff for that already, so it’s just a matter of running those tools once and setting values

quasi thunder
#

Thanks. Yes I use blobifier. I may buy the kit build and wait for the project to mature before I set it up. I like HH and the HH screen. Thanks for your answer.

viral haven
#

There is a Klipperscreen integration coming. Also, afaik, there’s nothing stopping someone from using a macro to do the blobifier stuff in AFC, it’s just not natively supported.

bright otter
# quasi thunder Thanks. Yes I use blobifier. I may buy the kit build and wait for the project to...

I liked the HH screen and integration too. But later realized it was just because it helped me pinpoint where the error was occurring or where my filament was in the system. The integration of the AFC is becoming so seamless that most of the time I forget it is there. I set up a multi-color print, hit print, and walk away. Lol. And this is on an early Beta build unit. Just finishing up a 2nd full release version now. All self sourced though. A kit should be alot easier to jump into new.

quasi thunder
#

Thanks

viral haven
#

I have 3 serialized units from 2nd generation beta parts to full release parts. I’ve had some issues with my physical bits caused by print tuning as far as I can tell, but I can hit print and walk away without worry of a print failing

quasi thunder
bright otter
#

I currently use the poop, kick, and wipe integrated into AFC. I do not use purge blocks.

quasi thunder
bright otter
#

Yeah. HH went bye bye.

I’m sure the enclosure is being worked on now.

quasi thunder
viral haven
#

I’m on a 350 2.4r2 with the turtles on it

#

Atm, I’m just kinda kicking them into the corner and cleaning the printer out once in a while

#

I can get a video of a full change on it when I get home in a couple of hours

quasi thunder
bright otter
quasi thunder
#

I think I can add macro to my tool change g code in orca to make blobifier work. Ordered the LDO kit today.

viral haven
#

You don't need to do it in Orca

#

You can configure the macro on the printer and call it with AFC during a change

#

There's no default macro for it in AFC is all

quasi thunder
#

Ya I will get it built then kill the rabbit I am sure a may yell for help.

bright otter
viral haven
#

If you need any assistance with the turtle build or getting AFC configured, feel free to ping @ teaching turtles. That's what we're here for

quasi thunder
#

👌

#

Will do. I usually have no issues will the building. It is the configuration that’s an issue sometimes.

quasi thunder
#

Is there an uninstaller for HH and HH Screen?

bright otter
quasi thunder
#

Not heard of DangerKlipper