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: !functionalprint@kbin.social or !functionalprint@fedia.io
There are CAD communities available at: !cad@lemmy.world or !freecad@lemmy.ml
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
Be respectful, especially when disagreeing. Everyone should feel welcome here.
No porn (NSFW prints are acceptable but must be marked NSFW)
No Ads / Spamming / Guerrilla Marketing
Do not create links to reddit
If you see an issue please flag it
No guns
No injury gore posts
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 
Moderation policy: Light, mostly invisible
Can you provide any more details on what is not working and what might have changed since things stopped working? There is not a lot of info to go on.
I've been running Klipper on a Raspberry pi with an Ender 3 S1 Pro for about 8 months with virtually zero hiccups, but I'd hardly claim to be an expert.
It work for me since the last year but start buggin this week.
The bltouch les stay red (might turn purple when the boot is done)
I had a similar issue when I initially installed Klipper on my Ender 3 S1 (not the plus). It would not connect unless I fully restarted Octoprint whenever I turned on the printer. The change I needed to make was go into settings in Octoprint (though I assume its similar on other front ends), and add the following settings:
Serial Port: /tmp/printer
Baud Rate: 11520
If that is not the case for you, try to add some more details. Do you have the config file correct?
I'll look for baudrate, but doesn't explain why it's work when I flash the firmware again...