Basic Information:
Printer Model: Prusa i3MK3S+
MCU / Printerboard: Einsy RAMBo
Host / SBC
klippy.log
Describe your issue:
Hello, I am trying to set up Klipper on Raspberry Pi 5. I installed Klipper via KIAUH.
I am looking for a printer.cfg for Prusa i3MK3S+. I visited the following site but I cannot find the correspoinding printer.cfg. Could you please let me know where it is located?
klipper/config at master · Klipper3d/klipper
Also, is this the required enisy-rambo.cfg?
klipper/config/generic-einsy-rambo.cfg at master · Klipper3d/klipper
Thank you
Hi @printeruser ,
I used this config on my MK3S+.
1 Like
Thanks. What did you do with Step. 2 of Install? Did you just skip it? In the past, I connected a Pi to the i3MK3S+ via a USB cable.
Under what directory are we supposed to execute “Clone config git clone https://github.com/dz0ny/klipper-prusa-mk3s.git ~/printer_data/config/klipper-prusa-mk3s
” mentioned in Step. 4?
For step 2, I connected a Pi to the Einsy with a USB cable.
That will work in any directory on the Pi.
1 Like
FYI, now I’m using an SKR Mini E3 V3 for the extra sensor plugs, better stepper drivers, and 24V fans. Nothing wrong with the Einsy or config, just I needed something a bit different for all the mods I installed.
1 Like
It seems that I might have successfully installed Klipper and flashed the i3MK3S+. Thank you very much.
- Since I have a E3D Revo 6 nozzle, is it better to perform another PID tuning and update the values in the printer.cfg file?
- How do I test if everything is working? Am I correct that if the printer goes crazy, just hit the EMERGENCY STOP on the browser?
- Which Accelerometer do you recommend for Input Shaping?
- I pressed the reset button under the knob on the LCD screen. The fans started spinning but only “Original Prusa i3 Prusa Research…” appears on the screen. No menu from the Klipper firmware is shown. What shall I do?
Thanks for the suggestion about SKR Mini E3 V3. Do you add some kind of probe for automatic bed leveling?
No problem!
- Yes. A PID tune is recommended and you can update the values in your config by using
SAVE_CONFIG
after.
- I’d try to home all axes, PID tune hotend and bed for good measure, then test a bed mesh. If anything goes wrong, use emergency stop
- I recommend the FYSETC PIS.
- When you restart from the printer, you have to go onto Mainsail/Fluidd and hit FIRMWARE_RESTART to start Klipper.
I use the same SuperPINDA that came with my MK3S+.
1 Like
Unless you have any more questions, could you please mark one of my posts as a solution to mark this thread as solved?
Thanks. PID calibration done.
How to do homing down in to X, Y and Z independently? I keyed in G28 X0.0 according to information from a webpage but the extruder moved to the far left. Issuing G28 X0.0 did not cause the extruder to move to the middle but it crashed the left with a loud sound.
Because of that, perhaps I should recalibrate the axes. If I want to do a X, Y and Z calibration likes the Calibration Wizard on the stock Prusa Firmware does, what shall I do?
Is SuperPINDA already functioning with Klipper without me doing anything?
To home XYZ independently, you can use G28 X
, etc.
Klipper doesn’t have auto axis calibration. Instead, follow the below procedure to calibrate X and Y.
If you’re homing X or Y, if it doesn’t move at all (assuming it’s not at the endstop position to begin with), you can increase driver_SGT
(up to 64
) in the corresponding [tmc2130 stepper_]
section.
If it’s crashing into the side when homing X or Y, you can decrease driver_SGT
.
To test your Z probe, run QUERY_ENDSTOPS
with the nozzle at least 1cm above the bed. It should report z:open
.
If you move your Z-axis by hand (physically turning the leadscrews) down so the nozzle just touches the bed, re-run QUERY_ENDSTOPS
, it should report z:TRIGGERED
.
If that works, you should be fine to run G28 Z
(after running G28 X
and G28 Y
). Keep a finger on the emergency stop button just in case.
1 Like
Thank you. I am a bit confused about the Home position. On our i3MK3S+ printer, where is the Home position? Is it the same location once the Klipper firmware took over? The confusion is caused by different positionings.
When I clicked the Blue All button with a house icon on it, the extruder moved to the left end and the build plate moved to the back. Then, the extruder ended up above grid (4, 3) of the steel sheet and stopped. When I did the homing individually, G28 X moved the extruder at the very left (X position of home?) and when I issued G28Y, the build plate moved to the far back (Y position of home is the front end of the build plate?). Executing G28Z after that seems to move the Extruder to the same location in space where the Home All button led to.
z: TRIGGERED showed up when it was close to the steel sheet. I guess the SUPERPINDA serves as the endstop here. Does the i3MK3S+ has endstop for X and Y? I am asking because there is no limit switch on X and Y and after using G28X, the extruder moved to the far left, collided and stopped with a loud sound. However, QUERY_ENDSTOPS gave x:open. Same thing for G28Y.
Thanks for the interesting article.
- Is the origin (0,0, Z), where Z is slightly above the build plate the Home? It seems to be the case by executing G28 X followed by G28 Y which moved the extruder to the far left and then the build plate to the far back (ended up the extruder above 0,0). However, strangely speaking, executing G28 Z did not move the extruder only up or down independently of X and Y but ended up having the extruder moving to somewhere above grid (4,3) on the steel sheet. This seems to be the same as pressing the blue House/Home icon on Mainsail. I am confused.
- How come executing G28 X followed by QUERY_ENDSTOPS still returned x: open, rather than TRIGGERED, respectively? Same thing for the G28 Y.
This is expected behavior and is due to the [safe_z_home]
configuration. This makes sure that every Z home happens near the center of the build plate.
Sensorless endstops (what the MK3S+ uses) don’t work like physical endstops. They would only show “TRIGGERED” for a tiny fraction of a second while homing (aka they would never show as “TRIGGERED”)
1 Like
Thank you very much for the clarifications 
1 Like