Config for Prusa Mk2.5S (Bear frame, Bear Extruder & TMC2209 drivers)?

Hi everybody, I have a Prusa Mk2.5S with:

  1. Bear frame v2.1

  2. Bear Extruder and X-Axis

  3. TMC2209 drivers on X & Y Axes via https://github.com/toto99303/Prusa-MK2-Ext.-Driver-Board (StealthChop2 mode… they don’t require any firmware changes in Prusa’s stock FW, so hopefully they should just work).

I’m planning on switching the V6 to a Revo Six in the next few days. I’m new to Klipper, but no stranger to 3D printing, coding etc… just never heard of Klipper until yesterday.

It uses the original 12V MiniRAMBo board… it’s the TMC2209 external driver board that I’m concerned about.

I suspect that this might be difficult to configure… does anybody happen to have a similar setup and would be willing to share their config?

Hi @MikeRatcliffe ,

Which board does your MK2.5S have? If it’s an Einsy RAMBo, you could start with this config, adjusting the axis limits to match the size of your machine.

For the TMC2209 drivers, I’m not sure how that board you linked works, but I would recommend switching to something like an SKR Pico or SKR Mini E3 V3 since those have built in TMC2209 drivers and are much more straightforward to setup with Klipper.

For the Revo Six hotend, really all you’d need to change is the thermistor type and re-run a PID tune (but since you’re Klipperizing anyway, you’ll have to do a PID autotune anyway).

As far as I can tell the external drivers will be invisible to klipper. There is no support for UART on the RAMBo so the driver modes are irrelevant to Klipper.

I concur with this. A 32 bit board with 5 drivers (so you can enable Z tilt) would be a worthwhile upgrade.

So I think I am best:

  1. Get the Revo setup working with the stock firmware (it will need to be tested).
  2. Migrate to Klipper with my current board. The TMC2209 drivers piggyback the stock ones, so the pins should be the same… in theory. If I can get it to work, I can make the config available to the community.
  3. Migrate to the SKR Mini E3 V3… I can’t argue with that one ‘cos it makes a heckuvalotta sense.

Fun times :wink:

OR Migrate to klipper with the current hotend. Debug and test.
Install new hotend.

Depending on what thermistor Marlin is configured for you may have to rebuild the firmware to change to the Revo. Changing thermal sensors in klipper is MUCH easier.

IIRC with my MK3S+, I didn’t have to recompile Marlin for the Revo. The Revo Six should be a drop in replacement for the v6.

I can confirm that. I’ve done the change some time ago with the original Prusa-Marlin and there was no need to changing the thermistor.