<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
               xmlns:atom="http://www.w3.org/2005/Atom"
               xmlns:dc="http://purl.org/dc/elements/1.1/"
               xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
               xmlns:admin="http://webns.net/mvcb/"
               xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
               xmlns:content="http://purl.org/rss/1.0/modules/content/">
            <channel>
                <title>
                	                    	Prusa3D Forum - Recent Topics                                    </title>
                <link>https://forum.prusa3d.com/forum/</link>
                <description>Prusa3D Forum Discussion Board</description>
                <language>en-US</language>
                <lastBuildDate>Wed, 29 Apr 2026 04:32:24 +0000</lastBuildDate>
                <generator>wpForo</generator>
                <ttl>60</ttl>
                					                    <item>
                        <title>Why so difficult to push filament through side sensor?</title>
                        <link>https://forum.prusa3d.com/forum/prusa-core-one-assembly-and-first-prints-troubleshooting/why-so-difficult-to-push-filament-through-side-sensor/</link>
                        <pubDate>Wed, 29 Apr 2026 02:41:02 +0000</pubDate>
                        <description><![CDATA[I&#039;m not sure if I&#039;ve done something wrong, but ever since I assembled my Core One+, it has been very difficult to push filament through the side sensor.  It feels like something is blocking ...]]></description>
                        <content:encoded><![CDATA[<p>I'm not sure if I've done something wrong, but ever since I assembled my Core One+, it has been very difficult to push filament through the side sensor.  It feels like something is blocking the path and I can hear a click each time I try to jam the filament in but it stops, as if it's pressing into something that moves and is blocking its path.</p><p>I moved the switch that is supposed to make it easier to push filament through, but it makes no difference.  (There does appear to be less resistance after I have pushed the filament through, but it does not make it any easier to get the filament to pass through initially.)</p><p>Cutting the filament to a sharp point sometimes helps, but not always.  Rotating the filament as I'm pushing it through sometimes helps.  Wiggling the base of the PTFE tube as it enters the sensor sometimes helps.</p><p>It just seems to me like there's something misaligned inside that prevents the filament from being pushed through, no matter how hard you press (enough to bend the filament and put a crease in it, and it still won't go through).</p><p>Is this normal, or is it a sign that I have not quite assembled the side filament sensor properly?</p>]]></content:encoded>
                        <category domain="https://forum.prusa3d.com/forum/"></category>                        <dc:creator>Malvineous</dc:creator>
                        <guid isPermaLink="true">https://forum.prusa3d.com/forum/prusa-core-one-assembly-and-first-prints-troubleshooting/why-so-difficult-to-push-filament-through-side-sensor/</guid>
                    </item>
                                        <item>
                        <title>Less Grid Boxes on the Bed on Mini Prusa vs MK4 in Prusa Slicer 2.9.4</title>
                        <link>https://forum.prusa3d.com/forum/general-discussion-announcements-and-releases/less-grid-boxes-on-the-bed-on-mini-prusa-vs-mk4-in-prusa-slicer-2-9-4/</link>
                        <pubDate>Tue, 28 Apr 2026 20:36:19 +0000</pubDate>
                        <description><![CDATA[I&#039;ve used the MK4 and there are many grid boxes within the 12 larger boxes on the bed viewing in the Prusa Slicer 2.9.4There&#039;s only 16 large boxes in the viewer in that same Prusa Slicer 2.9...]]></description>
                        <content:encoded><![CDATA[<p>I've used the MK4 and there are many grid boxes within the 12 larger boxes on the bed viewing in the Prusa Slicer 2.9.4</p><p>There's only 16 large boxes in the viewer in that same Prusa Slicer 2.9.4</p><p>Are you only given those 16 larger squares when the mini-Prusa is  the chosen printer?</p><p>reddit and Googled results suggest making all the sorts of settings  changes but before I do that maybe it's just a matter that the mini-Prusa has such a small bed all the other squares within those 16 boxes are not needed for the mini-Prusa?</p><p>Thank you for your insights and help.</p><p> </p><p> </p><p> </p>]]></content:encoded>
                        <category domain="https://forum.prusa3d.com/forum/"></category>                        <dc:creator>eager</dc:creator>
                        <guid isPermaLink="true">https://forum.prusa3d.com/forum/general-discussion-announcements-and-releases/less-grid-boxes-on-the-bed-on-mini-prusa-vs-mk4-in-prusa-slicer-2-9-4/</guid>
                    </item>
                                        <item>
                        <title>Axis test</title>
                        <link>https://forum.prusa3d.com/forum/english-forum-original-prusa-i3-mk3-5s-hardware-firmware-and-software-help/axis-test/</link>
                        <pubDate>Tue, 28 Apr 2026 15:43:05 +0000</pubDate>
                        <description><![CDATA[On my initial test of mk3.5S after updating the printer, i am failing my X,Y axis test. I do not see any interference in the full travel of either axis, what can be the problem. I also notic...]]></description>
                        <content:encoded><![CDATA[<p>On my initial test of mk3.5S after updating the printer, i am failing my X,Y axis test. I do not see any interference in the full travel of either axis, what can be the problem. I also noticed that during my Z axis test, the print head did not go all the way to the print plate. After topping out, the print head would only travel down about 65% of the distance towards the print bed or stopping with about 35% remaining travel. I am not sure what this means as it did pass the Z axis test.</p>]]></content:encoded>
                        <category domain="https://forum.prusa3d.com/forum/"></category>                        <dc:creator>Martha Rykala</dc:creator>
                        <guid isPermaLink="true">https://forum.prusa3d.com/forum/english-forum-original-prusa-i3-mk3-5s-hardware-firmware-and-software-help/axis-test/</guid>
                    </item>
                                        <item>
                        <title>Printer is asking for unloading and changing filament randomly during printing</title>
                        <link>https://forum.prusa3d.com/forum/original-prusa-i3-mk3s-mk3-hardware-firmware-and-software-help/printer-is-asking-for-unloading-and-changing-filament-randomly-during-printing/</link>
                        <pubDate>Tue, 28 Apr 2026 13:53:10 +0000</pubDate>
                        <description><![CDATA[Hi, since yesterday my MK3S+ is randomly stopping, goes to the front left and asks to press the button to unload the filament like a filament /color change was triggered, although there is n...]]></description>
                        <content:encoded><![CDATA[<p>Hi, since yesterday my MK3S+ is randomly stopping, goes to the front left and asks to press the button to unload the filament like a filament /color change was triggered, although there is nothing in the gcode. I checked the sensor readout but this seems to be normal, also rebooting the printer didn't solve the issue. Anybody an  idea what could cause /trigger this behavior? </p>]]></content:encoded>
                        <category domain="https://forum.prusa3d.com/forum/"></category>                        <dc:creator>Ulf</dc:creator>
                        <guid isPermaLink="true">https://forum.prusa3d.com/forum/original-prusa-i3-mk3s-mk3-hardware-firmware-and-software-help/printer-is-asking-for-unloading-and-changing-filament-randomly-during-printing/</guid>
                    </item>
                                        <item>
                        <title>Prusa goes Subscription</title>
                        <link>https://forum.prusa3d.com/forum/english-forum-general-discussion-announcements-and-releases/prusa-goes-subscription/</link>
                        <pubDate>Tue, 28 Apr 2026 13:48:17 +0000</pubDate>
                        <description><![CDATA[Who would have thought... Last year I cancelled my order for a Bambu printer when they announced the new lock-down mechanism in their firmware, restricting access to the printer from 3rd par...]]></description>
                        <content:encoded><![CDATA[<p>Who would have thought... Last year I cancelled my order for a Bambu printer when they announced the new lock-down mechanism in their firmware, restricting access to the printer from 3rd party tools. I thought I saw the writing on the wall that this was just the first step to making some services and functionality billable via a subscription model.</p><p><strong>And now Prusa, of all companies, is the first consumer 3D printing vendor to offer subscriptions if you want more storage space or better video streaming?? </strong><strong>https://subscription.prusa3d.com/</strong></p><p>This sounds like a great way to generate rather limited income but alienate a lot of longstanding users. How does this align with your "you buy it, you own it, no strings attached" marketing message? Yes, I get it, users still own their printers and basic functionality remains free (for now). But can we talk about "mixed messages" for a moment?</p>]]></content:encoded>
                        <category domain="https://forum.prusa3d.com/forum/"></category>                        <dc:creator>Jürgen</dc:creator>
                        <guid isPermaLink="true">https://forum.prusa3d.com/forum/english-forum-general-discussion-announcements-and-releases/prusa-goes-subscription/</guid>
                    </item>
                                        <item>
                        <title>Better quality?</title>
                        <link>https://forum.prusa3d.com/forum/general-discussion-announcements-and-releases/better-quality/</link>
                        <pubDate>Tue, 28 Apr 2026 13:33:39 +0000</pubDate>
                        <description><![CDATA[What should  do to get better layers and first layer?IMG_0602]]></description>
                        <content:encoded><![CDATA[<p>What should  do to get better layers and first layer?</p><p><a href="https://storage.googleapis.com/prusa3d-content-prod-14e8-wordpress-forum-prod/2026/04/e1a67057-image-scaled.jpg"><img class="alignnone size-medium wp-image-186114" src="https://storage.googleapis.com/prusa3d-content-prod-14e8-wordpress-forum-prod/2026/04/e1a67057-image-600x500.jpg" alt="" width="600" height="500" /></a><a href="https://storage.googleapis.com/prusa3d-content-prod-14e8-wordpress-forum-prod/2026/01/531711f4-img_0602.mov">IMG_0602</a> <a href="https://storage.googleapis.com/prusa3d-content-prod-14e8-wordpress-forum-prod/2026/04/4550844d-image-scaled.jpg"><img class="alignnone size-medium wp-image-186115" src="https://storage.googleapis.com/prusa3d-content-prod-14e8-wordpress-forum-prod/2026/04/4550844d-image-600x500.jpg" alt="" width="600" height="500" /></a><a href="https://storage.googleapis.com/prusa3d-content-prod-14e8-wordpress-forum-prod/2026/04/77287779-image-scaled.jpg"><img class="alignnone size-medium wp-image-186116" src="https://storage.googleapis.com/prusa3d-content-prod-14e8-wordpress-forum-prod/2026/04/77287779-image-600x500.jpg" alt="" width="600" height="500" /></a></p>]]></content:encoded>
                        <category domain="https://forum.prusa3d.com/forum/"></category>                        <dc:creator>Jullicca</dc:creator>
                        <guid isPermaLink="true">https://forum.prusa3d.com/forum/general-discussion-announcements-and-releases/better-quality/</guid>
                    </item>
                                        <item>
                        <title>Eigenständiges Öffnen und Schließen des Ventilationsgrills funktioniert nicht?</title>
                        <link>https://forum.prusa3d.com/forum/original-prusa-core-one-hilfe-zur-hardware-firmware-und-software/eigenstandiges-offnen-und-schliesen-des-ventilationsgrills-funktioniert-nicht/</link>
                        <pubDate>Tue, 28 Apr 2026 13:27:19 +0000</pubDate>
                        <description><![CDATA[Moin,vielleicht stelle ich mich ja etwas blöd an, aber ich hatte es so verstanden, dass mit der Einführung des Core One + auch für den normalen Core One die automatische Öffnung und Schließu...]]></description>
                        <content:encoded><![CDATA[<p>Moin,</p><p>vielleicht stelle ich mich ja etwas blöd an, aber ich hatte es so verstanden, dass mit der Einführung des Core One + auch für den normalen Core One die automatische Öffnung und Schließung des oberen Ventilationsgrills eingeführt wurden.</p><p>Das Update hatte ich vor langer Zeit gemacht und seitdem auch schon wieder öfters gedruckt. Der Drucker befindet sich somit auf dem neuesten Stand.</p><p>Leider kann ich es jedoch nicht beobachten, dass er selbstständig den Ventilationsgrill öffnet und schließt. Habe ich dahingehend etwas falsch verstanden oder muss man noch irgendwo was aktivieren? Ich habe die Einstellung durchsucht und konnte weder im Slicer noch am Drucker selbst nichts finden.</p><p>Für Ideen, was ich noch machen könnte, wäre ich sehr dankbar.</p><p>Vielen Dank für Eure Bemühungen!</p>]]></content:encoded>
                        <category domain="https://forum.prusa3d.com/forum/"></category>                        <dc:creator>Keno</dc:creator>
                        <guid isPermaLink="true">https://forum.prusa3d.com/forum/original-prusa-core-one-hilfe-zur-hardware-firmware-und-software/eigenstandiges-offnen-und-schliesen-des-ventilationsgrills-funktioniert-nicht/</guid>
                    </item>
                                        <item>
                        <title>PETG problems - finally solved. Pressure Advance M572 values in filament custom GCode need updating for Obxidian nozzles...</title>
                        <link>https://forum.prusa3d.com/forum/original-prusa-xl-tool-changer-hardware-firmware-and-software-help/petg-problems-finally-solved-pressure-advance-m572-values-in-filament-custom-gcode-need-updating-for-obxidian-nozzles/</link>
                        <pubDate>Tue, 28 Apr 2026 12:31:18 +0000</pubDate>
                        <description><![CDATA[I feel as though I have reached the end of a particularly frustrating tunnel, and I have found that the light is not actually a train.I have an XL 5-tool, currently with two 0.4mm Obxidian 5...]]></description>
                        <content:encoded><![CDATA[<p>I feel as though I have reached the end of a particularly frustrating tunnel, and I have found that the light is not actually a train.</p><p>I have an XL 5-tool, currently with two 0.4mm Obxidian 500 high-flow nozzles, two 0.4mm Obxidian high-flow nozzles, and a 0.6mm Obxidian high-flow nozzle. I have a general preference for printing with PETG, and I'm hoping to play with the UltraGlow and PC-CF filaments as well.</p><p>I had been having significant problems with all varieties of PETG filament buildup around nozzles, that buildup causing printhead crashes with prints, buildup dropping onto prints and creating a raft of weird problems both structural and aesthetic, problems with gaps in layers where filament extrusion wasn't "gripping" to the underlying and adjacent print layers, and a significant amount of time and effort and filament reels being wasted in pursuit of "good enough".</p><p>I had tried all of the advice, from manipulation of the temperature of extrusion, significantly lowering the feedrate of filament, significantly lowering the printhead speeds, changing the fill types to avoid crossing, varying the extrusion percentage, lots of playing with retraction and wipe and Z-move settings. Nothing was giving me similar results to what I had been getting when I first assembled the printer, and everything was having similar problems. Reverting firmware didn't help either.</p><p>As it turns out, one of the few configuration items I did not play with was the "Pressure Advance" parameter, that is in the M572 GCode setting.</p><p>Following the suggestions here: <a href="https://www.printables.com/model/641490-prusa-slicer-pressure-advance-test" target="_blank" rel="noopener">https://www.printables.com/model/641490-prusa-slicer-pressure-advance-test</a> I set up the test print with a range of parameter from 0.01 through 0.30 in a couple of prints. For my setup, the HF500 nozzles were looking best with M572 values in the 0.08 to 0.09 range, and looking noticeably poor in the 0.05-0.06 range, and from 0.12 upwards. This was using dried Prusament PETG in the SignalWhite flavour.</p><p>Checking the "Custom GCode" for the filament profile, I had seen that in the code there, if the nozzle was advertised as 0.04mm, that the value for Pressure Advance was being set at 0.53.</p><p>Setting that value in the custom code section to 0.09, and running a print through one of the normal slightly-modified print profiles that I had previously been having lots of trouble with, I ended up with a print that completed without blobs, that had a consistent surface finish, and that had a nozzle that was free of filament. I was really surprised at the difference this made..</p><p>Changing the parameter for other PETG filaments that had poor results previously, allowed similar high standards of completed test prints. </p><p>I effectively have a printer that (assuming no bed adhesion issues, but that is another story!) is pretty much guaranteed to give me a print output that is what is expected, and without the problems that were present.</p><p> </p><p>I am _happy_ now.</p>]]></content:encoded>
                        <category domain="https://forum.prusa3d.com/forum/"></category>                        <dc:creator>CathalFerris</dc:creator>
                        <guid isPermaLink="true">https://forum.prusa3d.com/forum/original-prusa-xl-tool-changer-hardware-firmware-and-software-help/petg-problems-finally-solved-pressure-advance-m572-values-in-filament-custom-gcode-need-updating-for-obxidian-nozzles/</guid>
                    </item>
                                                </channel>
        </rss>
        