This was done using prusament PETG using the standard .020 balanced profile and the prusament PETG filament profile. 

Two prints, both looking crappy in the same area, - left rear quarter of the plate. Going to calibrate again, and try again...

I always see oozing.

The nozzle cleaning nearly always fails because of the oozed filament.

The bed leveling is also badly affected by it leading to poor first layers. As well as leaving a grid of dots made of PC which make future bed levelling less accurate as it's so hard to clean off.

It seems off to me that filament is fully loaded during the bed levelling in the first place.

The order seems off.

Nozzle tip should hot and empty during cleaning and levelling.

Then purge and clean at the front edge of the bed

Start Print.

If anyone has any tips, I'd appreciate.

Nach mehreren Jahren relativ problemlosen Druck habe ich neuerding immer verklumpenden Druck in den ersten Schichten, so dass irgendwann der Druckkopf hängen bleibt und die ersten Schichten abreißt. Insbesondere beim Füllen von Flächen passiert das.
Wenn ich extrem langsam Drucke klappt es manchmal, aber beim normalen Druckgeschwindigkeiten gehts immer schief,

Hat jemand ein geschultes Auge und kann anhand des Bildes sagen, woran es liegen könnte ? Welche nächsten Schritte würdet ihr empfehlen ?
Ich bin verzweifelt und kurz davor das Ding abzuschreiben und einen Bambu zu kaufen...

Besten Dank,

Sebastian

Was ich schon gemacht habe:

aktuelleste Firmware 6.4.0 und SlicerSoftware 2.9.5, richtiges Profil mit input Shaper
Standard PLA Druckprofile aus dem Slicer genutzt
xyz ausgerichtet,
Platte mir Isopropanol vor jedem Druck gereinigt.
trockenes PLA Fliament
Düse ausgetauscht gegen neue Original Prusa 0,4mm,
ColdPull mehrfach,
FirstLayerKalibration mehrfach

Another issue are the VFA artifacts, though less of an annoyance than the z-band. The belts are tuned using the built-in stroboscope belt tuner. Though I know this filament makes the vertical artifacts more present due to the shininess.

It's a bit disappointing to see there's no support for the Buddy cameras either standalone or Core One in Prusa Link. It seems like it would be a matter of adding an RTSP feed embedded in the web page the printer serves up (or maybe even a popup link, for starters), and other printer control software like OctoPrint includes support for a multitude of cameras (USB, CSI, etc.), so it seems like a single official camera model would be easier to add on ;)

The main reason I ask is I have my Bambu P1S set up in Developer Mode on old firmware with Orca Slicer, and I can get that printer's built-in feed direct in Orca, but I can't find a way to use Buddy3D with Prusa Slicer unless I connect my printer to Prusa's cloud.

I know the alternative is to pop a camera on a Pi and run OctoPrint or something similar, but have you seen the price of Raspberry Pis lately?

I can't remove supports on the part of the model i have made, the model has its issues and is not great but I'm more focused on removing support on this specific part of the model.

I have tried Paint-on supports with or without clipping of view and i could not reach the part where i need to remove support.

I have also tried adding negative volume cylinder in the middle that did not give me expected results.

I don't need supports there because there is a cylindrical part that i want to insert during printing process.

Here is the part where i don't want support, and at the bottom i provided the file.

Koffing

Apparently, the print didn’t adhese to the plate as well as it seemed. When I got home, I found the printer happily reporting that the print was finished, all 3.5hrs of it, but no print on the bed. Instead, all of the filament was pushed up into the extruder for 3+ hours, somehow without any thermal anomaly errors or anything else.

Is this something that’s even worth trying to repair/replace, or did I just completely trash my printer? Are there any walkthroughs on rebuilding an extruder?

Here is the error report in full:

avrdude-slic3r -v -p atmega2560 -c wiring -P COM7 -b 115200 -D -U flash:w:0:C:\Users\speed\Downloads\__MACOSX\prusa3d_fw_3_14_1_MK3S\._MK3S_MK3S+_FW_3.14.1_MULTILANG.hex:i

avrdude-slic3r: Version 6.3-20160220-prusa3d, compiled on Nov  6 2025 at 10:47:10
                Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
                Copyright (c) 2007-2014 Joerg Wunsch


                Using Port                    : COM7
                Using Programmer              : wiring
                Overriding Baud Rate          : 115200
                AVR Part                      : ATmega2560
                Chip Erase delay              : 9000 us
                PAGEL                         : PD7
                BS2                           : PA0
                RESET disposition             : dedicated
                RETRY pulse                   : SCK
                serial program mode           : yes
                parallel program mode         : yes
                Timeout                       : 200
                StabDelay                     : 100
                CmdexeDelay                   : 25
                SyncLoops                     : 32
                ByteDelay                     : 0
                PollIndex                     : 3
                PollValue                     : 0x53
                Memory Detail                 :

                                         Block Poll               Page                       Polled
                  Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
                  ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
                  eeprom        65    10     8    0 no       4096    8      0  9000  9000 0x00 0x00
                  flash         65    10   256    0 yes    262144  256   1024  4500  4500 0x00 0x00
                  lfuse          0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
                  hfuse          0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
                  efuse          0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
                  lock           0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
                  calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
                  signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

                Programmer Type : Wiring
                Description     : Wiring
                Programmer Model: AVRISP
                Hardware Version: 15
                Firmware Version Master : 2.10
                Vtarget         : 0.0 V
                SCK period      : 0.1 us

avrdude-slic3r: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude-slic3r: Device signature = 0x1e9801 (probably m2560)
avrdude-slic3r: safemode: hfuse reads as D0
avrdude-slic3r: safemode: efuse reads as FD
avrdude-slic3r: reading input file "C:\Users\speed\Downloads\__MACOSX\prusa3d_fw_3_14_1_MK3S\._MK3S_MK3S+_FW_3.14.1_MULTILANG.hex"
avrdude-slic3r: ERROR: No valid record found in Intel Hex file "C:\Users\speed\Downloads\__MACOSX\prusa3d_fw_3_14_1_MK3S\._MK3S_MK3S+_FW_3.14.1_MULTILANG.hex"
avrdude-slic3r: read from file 'C:\Users\speed\Downloads\__MACOSX\prusa3d_fw_3_14_1_MK3S\._MK3S_MK3S+_FW_3.14.1_MULTILANG.hex' failed

avrdude-slic3r: safemode: hfuse reads as D0
avrdude-slic3r: safemode: efuse reads as FD
avrdude-slic3r: safemode: Fuses OK (E:FD, H:D0, L:FF)

avrdude-slic3r done.  Thank you.

It was taking snapshots, then I restarted the camera and now the card is in Read Only mode.

Why does it do this?

Firmware Version 3.1.4

Hardware Version NB.1.0.1

When I add the printer and test the PrusaLink connection (or send jobs to it with PrusaSlicer), I have no issues. But when I click on the 'Physical Printer' tab, I always get "Something went wrong." with a Reload button.

The Linux version of PrusaSlicer shows the printer's PrusaLink page correctly, and visiting the same address in a web browser on the same computer works fine too: