Klipper

114 readers

1 users here now

A community for discussion of the Klipper firmware for 3d printers.

Here are some Klipper links to get you started:

Klipper

Klipper3d - The Klipper documentation.
Config Reference - This document is a reference for options available in the Klipper config file.
G-code Commands - This document describes the commands that Klipper supports.
Status Reference - This document is a reference of printer status information available in Klipper macros, display fields, and via the API Server.
Command Templates - This document provides information on implementing G-Code command sequences in gcode_macro (and similar) config sections.

Companion software

Moonraker Config Reference - This document describes Moonraker's full configuration.
Mainsail Docs - Documentation for Mainsail Web UI
Fluidd Docs - Documentation for FluiddWeb UI
KlipperScreen Docs - KlipperScreen is a touchscreen GUI that interfaces with Klipper via Moonraker.

Klipper Discord

founded 1 year ago

MODERATORS

Rootiest

Klipper vs Octoprint (self.klipper)

submitted 1 year ago by nosnahc to c/klipper

2 comments fedilink hide all child comments

Hi, Actually I use octoprint + marlin and think about changing to Klipper. I understand that with Klipper, main calculs are made in the Raspberry PI. But what about Cura? Isnt' Cura who lead the gcode and then the printer movements? Thank by advance.

you are viewing a single comment's thread
view the rest of the comments

[–] Rootiest 2 points 1 year ago* (last edited 1 year ago) (1 children)

You got a lot of good comments on your other post so I won't reinvent the wheel.

But the biggest thing is:

On Klipper virtually all of the computation is done on the Linux Host side. The MCU (printer control board) simply acts as a bridge to pass those low-level signals on to the various components.

On Marlin with OctoPrint, the MCU is still doing all the thinking. OctoPrint is simply streaming clear text gcode lines to the MCU and the MCU must compute the low-level commands necessary to manage the movement and all the components like fans/etc.

Some of the benefits to this are:

you can easily use multiple MCUs on one printer
you do not need to reflash the MCU virtually ever, certainly not for basic config changes
we can use the pins/sensors on the pi
more advanced features like macros and Jinja are possible because they are executed on a modern Linux CPU.
etc

[–] nosnahc 2 points 1 year ago

Yeah, I've lot of good responses in my other post. But if someone has the same question as me, he can read a good answer here too! Thanks