I recently run into the Issue that i couldn't upload print files though Prusa Connect because the Cloud Space was full.

Then I noticed that there where a decent amount of files saved, that wehre blocking the space.

Shouldn't those files be deleted after a successful download to the Printer?

Best Regards

Updated firmware. Downgraded firmware. Upgraded firmware. Printed mods. Removed mods. Enclosure. No enclosure. Glue, no glue, stock settings, tweaked settings, firmware errors, parking issues, dropped support for my 5000 dollar printer. Clog after clog, multiple nozzles, large, small, stock. HF, not HF, hardened and not hardened. 

Support for the XL: Zero

"Flagship status" claim: Completely superseded. 

Today, it clogged while I was at work on an 8 hour print. I came home, fixed it. Thirty minutes later, I had a giant PC blob of death, ruining the hotend, the print, and finally, my relationship with Prusa. 2016-2026. I'm done. This printer sucks. Mine hasn't worked reliably since 2023, and in 2026 (eons of time, per many people on this forum), it still doesn't work. 

I owned ten MK3S/+. I brought one to Antarctica. They were great. I strongly support Prusa's open source ethos. I cannot condone the lack of support for this printer. 

The abandonment of the platform was the first straw. The realization that, yet again, I cannot get my 5k printer to work after following all troubleshooting, after a decade of successful printing on Prusa's platforms, was in fact the final straw. If yours works, good - I am very glad for you and hope you get many more great prints out of it. Mine doesn't. 

So Prusa announces the new 400° HT hotend  in October, puts it up in the store but doesn't make it available for purchase. Obviously this would need to include a firmware upgrade and most likely a fan-shroud redesign but was this to just check off a box saying: "Hey, the Core One can do 400° now so get your PPS-CF on"? Wondering if the tested this in-house and melted the nextruder or something. 

I'm also assuming that this won't work with standard brass nozzles and will need to use exclusively the 500° Obxidian nozzles. 

Now here's the thing, if I print and the bed heats up to this temp, it's perfectly fine. Even after hours of printing. The manual heat up method throws the error within a minute. 

I print with ABS and I like setting the bed temp so that the chamber has time to soak up the heat since my enclosure is passively heated. It's not the end of the world that this issue is happening, but I was curious if anyone else has started experiencing this issue after upgrading the firmware.

The full setup is a Mk4, with 6.5.3 firmware, and an MMU3. 

   I’m reaching out to the community for help regarding my Prusa Core One L. I have been working with Prusa Support for about 2 months now, but despite numerous attempts and tests, we haven't been able to find a definitive solution to the following issues:

1. Persistent Ghosting/Ringing: Highly visible on complex geometries and test models. It remains consistent regardless of software calibrations or mechanical adjustments.
2. Asymmetric "Clicking/Rattling" Noise: Originating from the rear-left motor block. The noise occurs during Front-Rear, Left-Right, and diagonal movements (Front/Left - Rear/Right). It is reproducible even when moving the print head manually with motors off. I’ve also noticed that the clicking volume increases as belt tension increases.

Printer Specs:

• Model: Core One L
• Firmware: 6.5.3 (issue also present on 6.5.2)
• Filaments used: Buddy 3D PLA Black and other PLA filaments (prusa and no prusa).

Steps taken so far (under support guidance):

• Software Calibration: Multiple Input Shaper and Phase Stepping calibrations performed.
• Belt Tension: Checked and set within nominal range (92 Hz Upper / 88 Hz Lower).
• Axis Maintenance: Cleaned and lubricated Y-axis rods with Prusa lubricant.
• Pulley Troubleshooting: Swapped the motor pulleys between X and Y motors. This makes the clicking disappear temporarily (for about 48h of printing), but then it systematically returns. Grub screws are correctly tightened on the flat part of the motor shaft.
• X-axis Guide Rail: Loosened the screws, pressed the rail down, and retightened them from the outside toward the center as suggested by support.
• Slicer Profiles: Tested both "Speed" and "Structural" profiles and change speed and acceleration; ghosting remains evident, especially on faster profiles.

Video evidence and documentation:

I have compiled several videos and test files that clearly show the noise and the print defects:

• Complete Analysis (Photos, Videos and G-codes): Analysis Archive
• Click sound video (google photo link): Click video
• Ghosting Test with Buddy 3D PLA Black - HF nozzle 0.4 - 0.25 lyaer height - speed profile

Has anyone else encountered similar issues with a Core One L? The fact that the noise returns shortly after reseating the pulleys makes me wonder if there's a defect in the motor itself or an internal bearing in the left block.

Any advice or insight would be greatly appreciated. Thanks!