Hi everyone, a week ago my printer (heavily modified Neptune 3) started randomly shutting down in the middle of prints. I come back to a print with the "Klipper reports: SHUTDOWN / Lost communication with MCU 'mcu'" error message.

The printer has been "under construction" for the last couple of weeks, but it has been in varying states of "working" for most of the time - working well enough for me to print the parts I needed to get it back to "fully operational". During this time, the printer never shut down like it is now.

Only once I started making little cosmetic changes did the problem present itself. I was running a known-good print, and I got the above error twice (first time after ~2 hours, second time after ~1 hour) before I got a successful print off of it. This was last week.

After this successful print, I continued other prints with no issues. After a day or two with no problems, an hour long print threw the error at me four consecutive times between 10-45 minutes into the

Ok guys, I'm breaking down and posting here to see if anyone has any ideas. I'm greatful for any advice.

I have an upgraded flsun SR. I recently lost my computer (psu issue, waiting for replacement) and I took this opportunity to switch from Cura to Orcaslicer.

Over-all I'm very happy, and getting some good speeds, but I just cannot remove stringing no matter what I try:

• Retraction from 0-7mm. After about 3mm, no further effect
• Retraction speed from 30mm/s-50mm/s. No noticable effect
• Travel speed and acceleration both high (up to 350mm/s and 6000 accel. No effect
• Temp from 205-215 with no effect
• Dried filament and different colours, no effect
• Wipe on retract on and off, up to 2mm wipe distance and 100% retraction. No effect
• Messed with scarf seams on and off, no effect
• No effect from layer heights

My setup:

• Printer - FLSun SR running klipper with a speede pad
• Filament - Esun PLA+
• Upgrades - Deported fans, OMG v2 extruder, volcano hotend and high flow cht no

Hi guys. Please check my previous post for any background questions, I don't have it in me to go over everything again.

Long story short, I was having issues with clogging that were being caused by my hotend not reaching the reported temp. After a few days of troubleshooting and diagnosing the motherboard and Klipper settings, I gave up and decided the motherboard was faulty (even though I could not perform any tests to determine in) and bought an SKR mini. I got that all set up, and the printer has been working flawlessly since then.

Until now.

Same exact problem; one print goes perfectly fine, next print, failing to extrude by the 4th layer. I removed the clog, restarted the print, now can't even extrude the priming line. Fearing the worst, I disassemble the hotend, try hand feeding filament, and once again I am unable to push more than a few centimeters through before it gets clogged up. A probe thermometer reads ~160C while Klipper reports 200C.

What could possibly be happen

OK guys, I finally found what the issue is, or at least kind of where it's coming from.

As some of you (and myself) suspected, my hot end is not reaching the reported temperature. I previously blamed the low readings on my IR thermometer on not being able to point the laser directly at the hotend, but it seems it was reporting accurate readings (around 95C when klipper reports 200C).

Now, here's where things get a little weird. At this point, I've used multiple thermistors, but swapped in a new one anyways. My board also has a pin for a second extruder thermistor, so I plugged it in to that one and changed the pin in my printer.cfg. No change.

I tried switching the bed and hot end thermistors on the board and in printer.cfg, no change.

I changed the thermistor "sensor type" from "EPCOS 100K B57560G104F" (same as the bed) to "Generic 3950", no change.

I found an article about tuning your pullup_resistance value. My cfg file did not have this value specified, so I added a line and

First I'd like to say thanks to everyone for looking at these posts and trying to help, and sorry to anyone who may be annoyed. Trust me, I'm not happy either.

I'm jumping back and forth between making this write up and recreating the clog by hand feeding filament into the hotend. This test was already performed earlier today and I got the same clog as I have been, so the extruder can be removed from the list of possible culprits. Anyways, here's the steps I'm following:

1. Verify temperatures are within acceptable range

This is my temp chart upon starting the printer. I used a thermal laser to test both nozzle and bed and they were within the range of accuracy of the laser. The laser is not accurate enough to get a good reading on the heat block; however, a few drops of water on the heat block boils within seconds when the temp is set to 100C, whereas at 90C it does nothing, so the nozzle is a

Hi everyone, I'm having constant clogging issues with my printer that sprung up out of nowhere. I'm running out of things to test.

The printer had been running several prints a day for several days when I decided to change nozzles for one print. Ever since then (~2 weeks ago) i have not completed a single print, due to clogging. I have tried:

Replacing the PTFE tubing in my hotend.

Replacing the nozzle. (I've used a handful of nozzles, all with the same results)

Trying different filament.

Replacing the hot end with an all metal hot end, trying three different heat breaks from two manufacturers.

Removing the printer from its enclosure to ensure proper cooling.

Adjusting extrusion tensioner.

All the other basic obvious stuff like making sure there's no blockages anywhere (whole hot end and nozzles have been soaked in acetone, torched, brushed etc).

The printer will seem to work fine for a little while before either slowly failing to extrude until it completely jams, or it c

Hi guys, I've dove into the klipper scene with my Neptune 3 and am having a really odd issue.

When I first got klipper/ Fluidd set up, I tried loading the interface in my browser (Chrome) and got an all white screen. At first I thought it just failed to connect, or the process wasn't running, but then noticed the tab was named "Fluidd". I spent an hour or two reinstalling things over and over before I decided to try a different browser (Edge). It loaded up just fine. I pulled it up in Firefox and spent a while configuring it. I had to reinstall the Pi's OS a few times, but each time Fluidd came up in Firefox without issue but failed to load in chrome.

Now, suddenly, it is failing to load in Firefox, but continues to load in Edge. Below is a screenshot from my PC with all three browsers with the same address typed into the bar, with only Edge loading for some reason... Does anyone have any clue what could be causing this? It also loads on the Chrome app on my phone.

![](https://lemm

I am somewhat new to 3d printing and i am playing around with different filaments and print plates on my cheap ender3 v3 se.

Right now I am observing a weird adhesion-issue i have not seen before: The copper-silk filament has trouble sticking to the printplate, but only in some places of the plate.

My guess it's either some dirt/oil on the printplate. Or maybe the silk-pla has bad adhesion.

What do you think?

This printplate is this (but glued over the original printplate): https://www.amazon.de/dp/B0CL5FYHBR

The filament is this: https://www.amazon.de/dp/B09CPBRQXS

some clarification for the video: all corners of the first layer should have been rectangular. Instead some corner lost adhesion and become roundish. Here is the view from the slicer: https://imgur.com/rwA0fQW

cross-posted from: https://lemmy.ml/post/5711722

We are getting closer to the next major release. This version will have many breaking changes, so we are listing them here for app and client developers to adjust their projects.

As we prepare for the release of Lemmy 0.19.0, we'd like to provide any app or client developers ample time to upgrade their apps, as well as discover any problems, before we do the release. This will be at least 4 weeks from now (but likely longer).

Server admins can also upgrade to the latest release candidates for testing. Be aware that they are still unstable and shouldn't be used in production. As with any upgrade it is important to have working backups in place.

It should be possible for clients to support both Lemmy 0.18 and 0.19 without major workarounds. If backwards compatibility is causing you trouble, comment below and we will help to find a solution.

To test, you can point your app to the following test instance runnin

cross-posted from: https://lemmy.ml/post/5711722

We are getting closer to the next major release. This version will have many breaking changes, so we are listing them here for app and client developers to adjust their projects.

As we prepare for the release of Lemmy 0.19.0, we'd like to provide any app or client developers ample time to upgrade their apps, as well as discover any problems, before we do the release. This will be at least 4 weeks from now (but likely longer).

Server admins can also upgrade to the latest release candidates for testing. Be aware that they are still unstable and shouldn't be used in production. As with any upgrade it is important to have working backups in place.

It should be possible for clients to support both Lemmy 0.18 and 0.19 without major workarounds. If backwards compatibility is causing you trouble, comment below and we will help to find a solution.

To test, you can point your app to the following test instance runnin

cross-posted from: https://lemmy.ml/post/5711722

We are getting closer to the next major release. This version will have many breaking changes, so we are listing them here for app and client developers to adjust their projects.

As we prepare for the release of Lemmy 0.19.0, we'd like to provide any app or client developers ample time to upgrade their apps, as well as discover any problems, before we do the release. This will be at least 4 weeks from now (but likely longer).

Server admins can also upgrade to the latest release candidates for testing. Be aware that they are still unstable and shouldn't be used in production. As with any upgrade it is important to have working backups in place.

It should be possible for clients to support both Lemmy 0.18 and 0.19 without major workarounds. If backwards compatibility is causing you trouble, comment below and we will help to find a solution.

To test, you can point your app to the following test instance runnin

We are getting closer to the next major release. This version will have many breaking changes, so we are listing them here for app and client developers to adjust their projects.

As we prepare for the release of Lemmy 0.19.0, we'd like to provide any app or client developers ample time to upgrade their apps, as well as discover any problems, before we do the release. This will be at least 4 weeks from now (but likely longer).

Server admins can also upgrade to the latest release candidates for testing. Be aware that they are still unstable and shouldn't be used in production. As with any upgrade it is important to have working backups in place.

It should be possible for clients to support both Lemmy 0.18 and 0.19 without major workarounds. If backwards compatibility is causing you trouble, comment below and we will help to find a solution.

To test, you can point your app to the following test instance running a release candidate of 0.19.0: https://voyager.lemmy.ml

A diff

• Debian 12
• AirPods Pro (2nd generation)

I have audio in KDE, but not in Gnome, so I'm convinced there's something about the DE.

In Gnome's output configuration I see these options:

• High Fidelity Playback (A2DP Sink)
• High Fidelity Playback (A2DP Sink, codec SBC-XQ)
• High Fidelity Playback (A2DP Sink, codec SBC)
• Handsfree head unit

I can't select the first option (defaults to whatever I had selected before). BUT, if I have a video playing and switch between the options I get audio for ~0.1 seconds.

The Handsfree head unit options has sound, but very poor quality.

In KDE I just have the "High Fidelity Playback (A2DP Sink)" option.

If I had to take a guess, then "High Fidelity Playback (A2DP Sink)" should work in Gnome, but it's not selecting for some reason.

c/jailbreak Community Megathread / Updated June 2023

Guides

• iOS Modding Guide / Start - Finish
• Getting Started
• Common Terminology
• Blocking Updates
• Troubleshooting
• Blocking Jailbreak Detection

Repos

• Recommended Repos
• Repo Updates

Modded .ipa Repos

*Check c/Sideloaded for more info on sideloading .ipa files.

Themes‎

• How to theme your device
• Themes
• Icons

Jailbreaking News

(only use the following as a resource for information, never trust any outside sources for downlo