@koz

The other thing is. With #PrusaSlicer in the printer's custom #Gcode where you set the start, end,layer-change, etc. Gcode. You can access variables such as temperature and layers, etc.

You, however, can't access variables like acceleration limits and use those values to emit them to your Macros when you run #Klipper.

So I need to look at a print, think a bit. Set limits in Klipper, transfer said limits to #PrusaSlicer, generate gcode, and then print.

#OrcaSlicer actually will honor your request to print slower or faster, but there is something wrong with its flow rate.

If you slice an object and switch to the flow-rate view. The color codes clearly show that it exceeds your set max. However , in speed-view, you can see that the speed is correct. And in #Mainsail during printing and can actively see how it changes the acceleration limits as it prints overhangs, perimiters, and briges.

As you can see, I am between 2 slicers here

@3dprinting #3dprinting

@linux_mclinuxface

I often do half prints like this for tests. This, however, resulted in my #Klipper and #Mainsail history to show more than 80% canceled jobs.

@3dprinting #3dprinting

I just tried #OrcaSlicer for the first time, I've just not had time to test it until now.

Because it was based on #PrusaSlicer, #SuperSlicer, and #Slic3r, I hoped that I could just import my PrusaSlicer config, but could not because it expected a .json file and PrusaSlicer outputs a .ini, but I might have done this incorrectly.

So I configure a "Generic Klipper setup" and copied the values by hand by comparing settings with my PrusaSlicer setup and a bit of experience and intuition.

My first resulting print, a custim part by me compared to the PrusaSlicer, was worlds apart. The finish was greatly improved with bridges requiring no supports, however it did print a bit slower, 28 minutes instead of 18 minutes, but this might still just be speed settings.

I like the UI, although I am more used to PrusaSlicer, and I especially love that I can access #Mainsail and #Klipper from within the app.

@3dprinting #3dprinting

So an update broke the camera in #Mainsail.

Good news: I got it working again

Bad news: I don’t know how/why

successbaby.jpg

So I am living in bed, but I can't see my print. So #Mainsail is open on my big screen en my series on my small screen. Because my printer is to the right and I can't see it.

Counting layer lines helps me to fall asleep.

@3dprinting #3dprinting

@geekandi

I thought that you might know and have some advice.

When I was running #Marlin, I used a z-offset of about 0.2mm to 0.24mm depending on my nozzle size.

Now with #Klipper:

1. I run HOME
2. PROBE
3. PROBE_CALIBRATE
4. Then I do the normal paper test. TESTZ Z=-.1 until I get it.
5. ACCEPT
6. SAVE_CONFIG

I get this: "probe: z_offset: -0.101" as my result.

When I print however I get the screenshot provided. The z-offset is shown as 0. My first layers are correct and my offset is correct, but it shows 0 here. Is this the "SET_GCODE_OFFSET" in #Mainsail? Is it normal to have it as 0 and just have the prove offset set?

I think so, I am using a load cell, so my nozzle is my probe. So I think it is correct that my probe offset is and z-offset is the same?

@3dprinting #3dprinting

After enjoying #Octoprint for the last 7 months and upgrading to #Klipper and #Mainsail, one of my other greatest hinders of moving to Klipper was the loss of #OctoEverywhere

Byt, they recently announced native and full support for Klipper. So, I just decided to upgrade from the free tier and support them.

I can now control and monitor my 3D printer from anywhere, and I just love it! They are definitely one of the best projects out there, and I highly recommend them.

Their #AI webcam monitoring Gadget is also amazing. It has only detected one fail, no misses. I only had one so far. But my print dislodged from the printer bed, and it immediately stopped my print. I had no false positives at all, and it probably has monitored about 20 hours of printing.

I feel a lot safer and more confident with it and so happy I am now supporting them!

They have a 14-day free trial for anyone who wants to try it!

https://octoeverywhere.com/

@3dprinting #3dprinting

@andypiper

Will check it out thanks, haven't heard of it before

@3dprinting #3dprinting #Klipper #OctoEverywhere #Mainsail #VPN

So, finally. My transition was successful. Took me one full day because it was my first time, and I had a complex system.

But I just love how smooth and fast the #UI of #Mainsail is and that I am not scared that I won't be able to access my printer in a pinch.

The #Klipper macros are really cool, and I already have 1000s of ideas and already implemented a bunch.

Then, the new #UI is also modern and sleek, where #Octoprint was outfated and slow. It broke my heart to say it, but it wasn't me. It was you, #Octoprint.

@3dprinting #3dprinting

I installed #KlipperScreen, although I currently don't have a screen.

I did this because I am planning on working in the wiring in the near future, so if I can prepare for a touch screen, it would be nice.

However, once again, I can overestimate enough how fast #Mainsail is. Not only on my desktop but also on my phone.

I have now uninstalled all mobile #Octoprint apps on my phone, and I am just using the app directly in my browser, and it is faster than most #Octoprint apps.

Unfortunately, in this process, I did lose my smartwatch app that #OctoApp provided. Which I 100% still recommened btw. The developer is such a decent guy, and he helped me a lot . His app and watch app are the next level of top quality! Probably one of my most difficult losses of this process.

@3dprinting #3dprinting

I installed #Crowsnest without knowing much about it, knly that it is for webcam streaming. I wanted to use a webvmcam and install it.

But I found that #Klipper and #Mainsail webcams are so much simpler than #Octoprint, and it just worked. The FPS and quality are better, and it isn't as overexposed and blurry. All this without touching my webcam at all or changing anything.

@3dprinting #3dprinting

I chose #Raspbian OS lite to get a fresh, fast, and clean #RadpberryPi. It was not only recommended, but I wanted to use #KIAUH ratger than using #MainsailOS.

This gave me more storage space, and I also knew what was already installed.

This also solved one of my problems when I used #Klipper with #Octoprint and #OctoKlipper.

I had a "mcu error," which I never could get a solution for. I had to restart my printer and Klipper repeatedly until they finally would connect.

This was solved by following the #Mainsail and #KIAUH docs and installing the Raspberry Pi MCU firmware.

These problems are now solved.

And damn, is this blazing fast.

Although I did clean my fan and heatsink and decided to #overclock my Raspberry Pi, the UI is so responsive I can live without my printer screen.

@3dprinting #3dprinting

Although I enjoyed my #Klipper transition. I stayed with #Octoprint, which was actually the final straw.

Although I could live without my printer's display, the lag and sluggish and slow #UI of Octoprint just pushed me over the limit. I felt as if I couldn't react to my printer anymore.

So with a heavy heart, I removed my SD card, wiped it and installed a clean version of #Raspbian OS Lite, and used #KIAUH to install #Klipper, #Mainsail, #KlipperScreen, #Crowsnest, #Moonraker and #Octoeverywhere

@3dprinting #3dprinting

@geekandi

Coming into the #Klipper space, I heard about #Mainsail and #Fluid being the best alternatives to #Octoprint. And then you get #Moonraker as well.

Currently, I just want to preasure advance and inputshaping setup andbget a few printsbgoing, then I will look into how I am going to convert all separate devices, sensors, and actuators to #MQTT

@RobeeShepherd

@3dprinting #3dprinting

@geekandi

I saw #KAIUH during my research about #Klipper and was wondering about it.

I just need to break the dependence of my enclosure with the #Octoprint plugins, and then I'll probably get #Mainsail. I have been meaning to move everything to #MQTT.

@RobeeShepherd

@3dprinting #3dprinting

@stooovie

I doubled the slicing resolution and halved the minimum maximum path length to prove a point. That printers can be overwhelmed at normal speeds of 60 mm/s with excessive G1 movements.

Default settings in #PrusaSlicer can do this to a #benchy with some cheaper 8-bit boards or over slower serial connections using something like #Octoprint

Not only does #Klipper have its own methods of being faster, but #Mainsail and #Fluidd have less oerhead than #Octoprint. So, just the serial communication can be more efficient due to this.

I am busy with my own personal investigation into #Octoprint to see how I can speed it up because I need it and don't have the time to rewrite my entiee enclosure to work without my plugins. So Mainsail isn't an option.

I actually installed #Klipper and #Octoklipper literally like 6 hours ago. I am still busy with mt config because I had some unrelated issues.

@3dprinting #3dprinting

@fabbaloo

"What’s more interesting is that the K1 series is equipped with substantial networking, cloud connectivity, and remote control features. It seems that Creality has implemented some form of farm management system where an array of K1s could be running production jobs."

This could be great! Maybe #Creality now feels as if their printers are on par with #Prusa, after the #MK3 outperformed the #Ender3 in #PrintFarm usage.

The #Ender3 just wasn't reliable enough, and if it was used, it had to be heavily modded.

But a new age of print farms has grown with the release of the #Bambulab #X1C. Someone could have a small print farm for their products without any #3dprinting skill and juet plug-and-play their printers.

Creating a commercial print-and-play solution is a great step.

It will be interesting to see if this is a fork of #Octofarm, a multi-printer #Klipper and #Mainsail setup, or something brand new. #Prusa already have their own solutions.

@3dprinting #3dprinting

Today, we released #Mainsail v2.5.1 with some important bug fixes and added Czech translation.

Here you can find the release: https://github.com/mainsail-crew/mainsail/releases/tag/v2.5.1

#Klipper #3dprinting

The amazing #Octoprint plugin #OctoEverywhere now has full #Klipper support! This is really amazing for Klipper and the Octoprint community using it instead of #Fluidd and #Mainsail. Until now, Octoprint was manly the good choice for the plugin support, but this will allow for all the great remote #Marlin features with Klipper!

https://octoeverywhere.com/klipper?source=launch_email_learn_more

Octoprint on #Mastodon
@octoprint

@3dprinting #3dprinting

Love to see the new #klipper (G-Code flavor) Support and Fileupload to #mainsail / #fluidd (technical its #moonraker ) function in the new #prusaslicer alpha release! 😍

#3dprinting