Ender 6 w/ OctoKlipper

Basic Information:

Printer Model: Ender 6
MCU / Printerboard: SKR Mini E3 V3 & OctoKlipper on RPi4B
klippy.log

Describe your issue:

As the title says I’m trying to configure my Ender 6 to work with Klipper. I’ve followed multiple instructional guides online; How to install Klipper on the SKR Mini E3 V3 – YouMakeTech being the lastest one I tried.

I’m positive the wiring is done properly and that the firmware is built and flashed properly but i cant seem to get Klipper to get beyond standby or any of the buttons under the Klipper tab to become functional.

klippy.log (84.1 KB)

That’s written in your klippy.log

[mcu]
serial = /dev/serial/by-id/“your-mcu-id”

That “your-mcu-id” doesn’t make sense!

You could read the docs of Klipper or Sineos “Knowledge Base” before asking!

Have a look at " Connection Problems to the Printer Board".

Good luck, hcet14

Thanks for the link, I will begin to familiarize myself.

Sorry for old log, I have an updated one here

klippy.log (4.4 KB)

You have an error in your printer.cfg:

[printer]
kinematics = corexy
max_velocity = 500
max_accel = 2000
max_z_velocity = 10
max_z_accel = 100u

This should be:

max_z_accel = 100

and:

I seem to have solved the configuration file issues but now I am stuck with this screen.

Also, is it possible to force update of klippy.log?

image

Edit: New log
klippy.log (25.6 KB)

OctoKlipper?

That’s quite old fashion.

1 Like

I like all the open source plugins and ability to monitor from afar.

But I’m open to suggestions, especially if this might likely be an OctoKlipper issue

Please don’t say that!

Some people like to work with it.
And: On OctoPrint, Klipper was developed.

Ok, I’ll never say it again :face_with_open_eyes_and_hand_over_mouth:

All I wanted to state was: That’s just my opinion!

2 Likes

“I prefer X before Y”

Sounds nicer than:

“Y is bad”

doesn’t it?

1 Like

Are you addressing me? If yes, I don’t get it.

But back to the topic

[quote=“EddyMI3D, post:8, topic:12041”]
And: On OctoPrint, Klipper was developed.

Do you remember

Some of these “big ticket” items include:

The docs need to be upgraded so they recommend Mainsail/Fluidd/etc. instead of OctoPi/OctoPrint. This may also require changes to the install scripts in the main Klipper repo.

Well, it makes sense because:

  • They are specifically developed for Klipper only
  • Integrate Klipper more seamlessly compared to Octoprint
  • Easier to set up. OTOH, only when using KIAUH, otherwise quite impossible for the average Joe / Jane

Which does not make Octoprint any less great, and none of the “modern” solutions come close to customization possibilities that Octoprint is offering.

1 Like

I didn’t say that. koconnor did.

so switch to Mainsail or Fluidd for a sustainable solution?

I would recommend that (just my opinion).

I do not see any immediate benefits of one over the other.
This largely depends on your requirements

  • If you just want a webinterface to click on “print” and jog around a bit then both will fully do
  • If you have special workflows or need special plug-ins then stick to Octoprint
  • If you feel comfortable with Octoprint, then stick to it
  • If you have the needed Linux skills and knowledge, you can run Fluidd, Mainsail and Octoprint in parallel

There is no real right or wrong. Try it and make up your mind.

2 Likes

but

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.