Current update on the forum, March 5th 2026
Hello all;
I wanted to touch base with the community here to give you an update and hopefully have this be a regular type of post, (depending on how busy and active things are here behind the scenes).
Internally;
- A method is being hammered out where forum posts can be forwarded over to our product teams to monitor and track reported issues. It needs to be fine tuned so the same instance is not reported multiple times, and it wont be possible to go back and cover all reported cases. I need to set a starting point and then collect data from that point in time. If I was to go back and collect data from say 6 or more months previously (only as an example), I can easily overwhelm them with reports, and out of those reports, a good percentage of older claims have already been resolved one way or another.
- This same method will be used for submitting unique cases to support for follow up if needed.
- Work on the backend of the forums is still progressing, slowly, but it is progressing and not being pushed off to the side. The forum here is a wee bit on the large size and its a matter of trying to take the current system, finding out what options there are and then porting it over to either a new system or updated system all while trying to keep the current system up and running. It is still being worked on.
Forums in general.
- I will be updating the community guidelines for the forums and have it as a pinned post. No major changes or anything, just updated a bit and posted so people know the expectations of the community and what guidelines there are and reference the new users guide in there as well.
- I would like to get some feedback from the community, as I have seen multiple posts with someone posting a problem, the community answers the question, but there is nothing else after that point (I am talking about several months after the post), if the problem is resolved or not. I was thinking to assume things (and yes, before anyone adds it... I know the saying about assuming things) and mark the post as solved. I could also close it as well if the community thinks thats a good idea or not. Let me know in the comments below.
- A new section was added - "Filament Materials and Techniques" per a community members suggestion. This section is geared more towards filament in general and not specific to a printer type, This is where people can discuss various techniques for different filament types such as pre and post processing, drying, or other topics related to filament in general.
Out side the forums;
We have our official discord server (yes, yet another social media platform to follow) and I am also involved in that and we are working on more community engagement over there as well. Apart of that is working on some scheduled and random "Prusa Community" streams that we are testing in the server to work out some bugs and also since the community can interact more and we can invite people to show off their work.
IF you would like to check it out, the server link is here.
Official Prusa 3D Discord server
Please note, to try and make things a bit easier, its a temporary link, if you don't pick a role and leave the server, you will be removed from it. I thought doing it that way will give people a chance to check things out and then if its not their thing, they can leave and not worry about disconnecting from the server.
That is all I got for you this round. I am not sure when the next update will be, but I would like to try and make this somewhat of a regular thing so I can keep the forum community updated overall.
Thanks for reading.
Shane
Shane (AKA FromPrusa)
RE: Current update on the forum, March 5th 2006
A lot of good stuff -- thank you for the update, Shane.
Regarding admins or moderators marking threads as solved, I don't like that idea at all. Feedback from those who asked for help -- be it a dedicated reply, or at least a click on "like", "best answer" or "solved" -- is the only reward for those who put in their time here to try and help. Please don't make that meaningless by setting everything to "solved" after some timeout.
(Besides, I don't see the point. Well, except that it looks better for Prusa at first glance if all problems around the printers are apparently "solved".)
RE:
- I would like to get some feedback from the community, as I have seen multiple posts with someone posting a problem, the community answers the question, but there is nothing else after that point, if the problem is resolved or not. I was thinking to assume things (and yes, before anyone adds it... I know the saying about assuming things) and mark the post as solved. I could also close it as well if the community thinks thats a good idea or not. Let me know in the comments below.
When a person is asking for help, a lot of the time a good answer is given without it necessarily being the "correct" answer for the OP. So if a thread has 5 good responses, it might be solved for 30 other people reading the post but not for the OP. I can image it being a little frustrating to have your post being marked as "solved" by a moderator when it isn't solved for you. For me as a reader, I don't think a "solved" tag would change my forum-behavior much, since I've learned that almost all threads have good and useful information inside of them, and that not every solution works for everyone.
Something that isn't so common but maybe good to have in mind: When threads continue for ages and change topic compared to the title of the thread. I've seen it a few times on the forum, where a thread title is about some sort of criticism but the latest posts for several days / weeks is about something completely else. This gives the impression that the title of the thread is a very important or common issue, when in reality the forum posters are discussing something different inside.
RE:
- A method is being hammered out where forum posts can be forwarded over to our product teams to monitor and track reported issues. It needs to be fine tuned so the same instance is not reported multiple times, and it wont be possible to go back and cover all reported cases. I need to set a starting point and then collect data from that point in time. If I was to go back and collect data from say 6 or more months previously (only as an example), I can easily overwhelm them with reports, and out of those reports, a good percentage of older claims have already been resolved one way or another.
If it helps, the forum community can compile a list of issues that are older but still unresolved to our knowledge. A few for the Core One, off the top of my head -- let me know if you need links for the respective threads:
- XY stepper motors not grounded, leading to charge buildup and crashes during large prints.
- Heatbed not grounded, leading to ESD issues and crashed when a "charged" user touches the bed.
- Z lead screws with different thread pitches being used, apparently still different pitches in current inventory.
- Nextruder fan shroud can collide with cable cover in the rear left of the print bed.
RE:
let me quickly add something... in regards to the posts and marking them as solved. I edited the post and added "I am talking about several months after the post" (talking about 6-12 months without a response) as I thought I had mentioned that when I was writing it but I didn't. I was just trying to figure out a way to handle posts that appear to be abandoned without an update from the OP. IF the community doesn't want them touched, then I will happily leave them be 🙂
@Jürgen for the Z lead screws, If we are talking about the same post that went on for several pages, that thread was sent to product and support as well as OP was already in touch with support. For the other cases, if you send me a link (either message, or just post them here) I can submit them to the teams as well.
Shane (AKA FromPrusa)
RE:
I think these are the most relevant threads regarding the Core One issues I mentioned:
- XY stepper motors not grounded, leading to charge buildup and crashes during large prints.
Heatbed not grounded, leading to ESD issues and crashed when a "charged" user touches the bed.
https://forum.prusa3d.com/forum/postid/740883/ (long thread which discusses both issues)
https://forum.prusa3d.com/forum/postid/752399/ (root cause of non-grounded motors identified; discussion on mitigation follows)
https://forum.prusa3d.com/forum/postid/783576/ (recent discussion about user discharging into heat bed)
- Z lead screws with different thread pitches being used, apparently still different pitches in current inventory.
https://forum.prusa3d.com/forum/postid/754887/ (original thread; this post is where the root cause was first identified)
https://forum.prusa3d.com/forum/postid/782530/ (recent thread)
- Nextruder fan shroud can collide with cable cover in the rear left of the print bed.
https://forum.prusa3d.com/forum/postid/747519/
RE: Current update on the forum, March 5th 2006
Thanks for the links, I will get them submitted
Shane (AKA FromPrusa)
RE: Current update on the forum, March 5th 2006
in regards to the posts and marking them as solved. I edited the post and added "I am talking about several months after the post"
Perhaps we need a new class of closure and icon: "Presumed solved" and "✓?" - thoughts anyone?
Cheerio,
RE: Current update on the forum, March 5th 2006
Perhaps we need a new class of closure and icon: "Presumed solved" and "✓?" - thoughts anyone?
But what information would such a tag carry? It would not really say anything beyond "This thread is stale; there have not been any updates since X months." But that is easily visible anyway -- old threads sink towards the bottom of the lists, and the date and time are given for every post.
I would suggest addressing this in the community guidelines: Strongly encourage users to provide feedback when an issue has been resolved. That would benefit those who have tried to help (giving them positive feedback) as well as readers who come across the thread later (confirming that the suggested measures were actually successful).
RE: Current update on the forum, March 5th 2006
I think these are the most relevant threads regarding the Core One issues I mentioned:
- XY stepper motors not grounded, leading to charge buildup and crashes during large prints.
Heatbed not grounded, leading to ESD issues and crashed when a "charged" user touches the bed.
https://forum.prusa3d.com/forum/postid/740883/ (long thread which discusses both issues)
https://forum.prusa3d.com/forum/postid/752399/ (root cause of non-grounded motors identified; discussion on mitigation follows)
https://forum.prusa3d.com/forum/postid/783576/ (recent discussion about user discharging into heat bed)
- Z lead screws with different thread pitches being used, apparently still different pitches in current inventory.
https://forum.prusa3d.com/forum/postid/754887/ (original thread; this post is where the root cause was first identified)
https://forum.prusa3d.com/forum/postid/782530/ (recent thread)
- Nextruder fan shroud can collide with cable cover in the rear left of the print bed.
https://forum.prusa3d.com/forum/postid/747519/
I think this one is also relevant, discussing the issue of failure to home the Z axis when nozzle heater is on:
The issue is faulty main wiring harness from the Nextruder to the loveboard.
There are workarounds like disabling the nozzle heater whilst homing the Z axis, but the real fix is to replace the wiring harness.
RE: Current update on the forum, March 5th 2006
For what little it's worth, I'm not a big fan of technology or 3rd parties making decisions on my behalf. If I post a question, it should be up to me to mark it as solved or not, whether I do or not is really my issue alone. I am not a big fan of someone else popping up and saying "yeah, that's the answer" for that thread.
I can get why other people browsing the forums might have issue with no "answer" selected, but at the same time, I would hope they should know when and how to try things even if an answer is not chosen. That's where the like button comes into play.
RE: Current update on the forum, March 5th 2006
I think this one is also relevant, discussing the issue of failure to home the Z axis when nozzle heater is on:
The issue is faulty main wiring harness from the Nextruder to the loveboard.
There are workarounds like disabling the nozzle heater whilst homing the Z axis, but the real fix is to replace the wiring harness.
Right, it's probably an issue that is still affecting units in the field. But regarding communicating things back into the Prusa organisation, it seems that Prusa is aware of the problem. I would hope that the modified wiring harnesses (with twisted-pair wiring I believe) has already been introduced into production of new printers and kits?
Although the reported experience with Prusa support seems a bit hit-or-miss; some people ended up buying new cable harnesses at their own expense. Maybe an additional service bulletin or training is in order?
RE: Current update on the forum, March 5th 2006
- A method is being hammered out where forum posts can be forwarded over to our product teams to monitor and track reported issues. It needs to be fine tuned so the same instance is not reported multiple times, and it wont be possible to go back and cover all reported cases. I need to set a starting point and then collect data from that point in time. If I was to go back and collect data from say 6 or more months previously (only as an example), I can easily overwhelm them with reports, and out of those reports, a good percentage of older claims have already been resolved one way or another.
I am so glad to see the dedicated attention to this community forum! I know this will be a huge benefit for Prusa and for the end users.
A quick thought... When I was running product groups, we used the customer forums to develop empathy with the customer experience for our engineering and product managers. Even if they don't interact directly on the forum, having a regular ritual of scanning the topics on their product lines helps EMs and PMs to quickly develop a qualitative sense of people's pain points and creates a sense of urgency around relieving them. We used to ask that on a monthly basis people prepare to informally report and discuss on their own products, and we would have more formal weekly reviews in the six weeks or so after launching the product.
I want to make a distinction between the VOC type empathy exercise and issue flagging and tracking. With the VOC exercise, the product team reads through the issues themselves and form their own opinion, whereas the escalation path is typically managed by the forum manager. For example, the flagged issues above are clearly problems that need either dev fix or a product workaround and belong on an escalation track. Issues related to users just misunderstanding how to use the product don't get escalation, but are easily surfaced during individual VOC reviews.
This is just my two cents - I'm glad to see Prusa dedicating the resource and time to these forums regardless of the process you wind up using.
Prusa Core One, MK4S w/ MMU3 (formerly MK4 / MMU3, MK3S+/MMU2), 2 Prusa MINI+, Octoprint. ASA, PETG, PVB, (some) PLA.
RE: Current update on the forum, March 5th 2006
I think this one is also relevant, discussing the issue of failure to home the Z axis when nozzle heater is on:
The issue is faulty main wiring harness from the Nextruder to the loveboard.
There are workarounds like disabling the nozzle heater whilst homing the Z axis, but the real fix is to replace the wiring harness.Right, it's probably an issue that is still affecting units in the field. But regarding communicating things back into the Prusa organisation, it seems that Prusa is aware of the problem. I would hope that the modified wiring harnesses (with twisted-pair wiring I believe) has already been introduced into production of new printers and kits?
Although the reported experience with Prusa support seems a bit hit-or-miss; some people ended up buying new cable harnesses at their own expense. Maybe an additional service bulletin or training is in order?
Yeah I'm baffled at people happily paying out of their own pockets to fix what is basically a manufacturing issue.
Whoever I spoke to was clearly aware of the issue, so there was barely even a conversation between us needed, they just agreed to send the part.
I've found the same with the Z motor lead screw issue, some agents seem aware of it while some are not.
I think Prusa should make sure that all their agents are on the same page and aware of these common issues that could still affect the earlier kits/machines...even if the manufacture and supply of these parts has been corrected.
RE: Current update on the forum, March 5th 2006
RE: Current update on the forum, March 5th 2006
Volatile Organic Compounds are typically met with little empathy in these parts, and are either absorbed by active carbon filters or unceremoniously vented out of the room. -- Sorry, couldn't resist... 😊
HA! Victim of my own TLA - should have spelled out VOC (Voice Of the Customer). Definitely don't expose the EMs and PMs to volatile organic compounds 😉
Prusa Core One, MK4S w/ MMU3 (formerly MK4 / MMU3, MK3S+/MMU2), 2 Prusa MINI+, Octoprint. ASA, PETG, PVB, (some) PLA.
RE: Current update on the forum, March 5th 2006
Unless there's some crazy joke thats going way over my head, why does the thread title say 2006 ?
RE: Current update on the forum, March 5th 2006
The internet was a much kinder place back then... That was before social media...
RE: Current update on the forum, March 5th 2026
Unless there's some crazy joke thats going way over my head, why does the thread title say 2006 ?
Because ;
A). I wanted to see how many people would catch it?
B). I wrote it at 2am with no coffee
C). I'm old and fingers confused the 0 and 2 keys?
D). All of the above....
But thanks for catching it, I corrected it 🙂
For the rest of the comments / suggestions and other things, I will have to get back to it after some ZZZZ's
Shane (AKA FromPrusa)