this post was submitted on 14 Jun 2024
21 points (100.0% liked)

3DPrinting

15661 readers
14 users here now

3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.

The r/functionalprint community is now located at: [email protected] or [email protected]

There are CAD communities available at: [email protected] or [email protected]

Rules

If you need an easy way to host pictures, https://catbox.moe may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is ![](URL)

Moderation policy: Light, mostly invisible

founded 2 years ago
MODERATORS
 

I upgraded to this guy from the neo v2, and he is a beast in comparison. There isn't a premade profile on prusa for it though, so I made one using the neo as a base. Currently have the speed set to 150 mm/s and 1800 mm/s accel but was wondering what kind of speeds y'all are getting while still having consistent quality

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 6 points 5 months ago (4 children)

Have you heard of Klipper? If you're running that it's very easy to set up towers to find your max print speed and acceleration. It's a bit of a rabbit hole so lemme know if you've got any questions

[–] [email protected] 4 points 5 months ago (3 children)

I have most definitely heard of it.

Do I know what it is, how it works, what it does? No.

I know you can run it through a raspberry pi, which is useful because I am already using one for octoprint. If it isn't crazy difficult to setup than I would definitely be willing to try it out!

[–] [email protected] 5 points 5 months ago

I wouldn't say it's "crazy difficult" to set up, but it is definitely a little involved. There will be a ton of documentation on setting it up for an ender printer so that shouldn't be an issue, but it's more work than simply "install it and go".

The way your current set up works, is your pi/ octoprint is sending a file to your printers motherboard, the printers motherboard is processing the file and executing all of the commands. The pi isn't doing any real work besides letting you interact with the printer's motherboard.

In simple terms, the way Klipper works is by replacing the firmware on your printers board with a program that can talk to both Linux and the hardware of your printer (stepper motors, heat cartridges, fans, etc), using the pi to run all of the processing and such, then passing those commands to the printer's board (which is now essentially a zombie that does nothing but what Klipper tells it to do).

Doing the main computation on a strong computer like a pi rather than the weaker CPU on a printer motherboard opens a plethora of options, one of the most popular being something called "input shaping" which is very relevant to your question. What that does is tests the vibration resonance of your printer and modifies stepper commands to counteract them, allowing you to print at significantly higher (read: sometimes 3x or more than stock) speeds without much if any noticeable decrease in quality.

Not only stuff like this, but there are innumerable QOL improvements over Marlin. Object exclusion for when one part out of a multi-part print fails, custom macros for anything you could want your printer to do, graphic bed level mesh.. I honestly don't know how I used my printer for so long without all of these things that seem like no brainers.

Long story short, it'll probably take more than an hour or two to get set up, but as soon as you get it going you'll be wondering why you didn't do it day 1. If you're at all serious about getting the most potential out of your printer, it's an inevitability; the stock firmware is far too limiting in what you can do, and makes any kind of advanced tuning or tinkering either impossible or way harder than it needs to be.

Sorry to dump this wall of text on you! If you decide to give it a go, pick a weekend and hit the forums, shoot me a message if you get stuck on anything and I'll help you best I can!

[–] [email protected] 3 points 5 months ago (1 children)

It took a bit to get used to because the mindset is different but once it’s going it’s great.

I love that I can make config changes easily without having to compile firmware.

If you ever decide to take the plunge feel free to reach out since I did it with my ender 3v2 years ago. Not that it looks anything like the stock anymore.

Looks like somebody else already has the config working for it and a step by step guide for setting it up on your machine

https://artamis.me/projects/klipper_guide/

One thing to note is you don’t have access to the display anymore since the display on the ender 3 is proprietary. You use a web panel (I often use my phone for this with mainsail as my ui of choice)

That being said there are other displays that can work with it but I seldom use my display for anything anymore.

[–] [email protected] 2 points 5 months ago

Holy cow, thanks for the link! I will definitely try it out once I am finished with my next couple of projects.

I already don't use the display because OctoPI though the OctoApp is way more convenient, so no loss there lol

[–] [email protected] 1 points 5 months ago

Yea, I don't think the se runs it out of the box but I've heard an rpi can be used

[–] [email protected] 2 points 5 months ago (1 children)

Need to do one of those speed/acceleration calibrations myself. I've reduced my speed for better quality, but it'd be fun to know my limits

[–] [email protected] 2 points 5 months ago

It's so much fun to know your limits, and really useful when you're prototyping parts.

I like modeling things like little tool holders to fit inside the railings on my printer, so sometimes need to print a couple of them to get the size just right. When doing these tests usually I print 0.6 nozzle, 0.3 layer height at 300m/s and 3000m/s^2 accel. Parts usually don't come out super pretty, but more often than not I end up using the final "test print" rather than reprinting it at more reasonable speeds because I just need it to work, not look nice.

[–] [email protected] 1 points 5 months ago* (last edited 5 months ago)

The SE still runs Marlin, the KE is the Klipper Edition.

[–] [email protected] 1 points 5 months ago

I got the se a couple months ago, unfortunately it doesn't use klipper without modding it with a rpi as far as I know