Hi there, a new P1S user in need of troubleshooting.
I have trouble printing this model: Fidget Gears - Print in Place
The printer stops the print and signals the print is finished just when it should start printing overhangs for the top part. This has repeated 3 times already. The picture below shows the last failed print after taking it off the build plate:
The source file contains 3 parts, I tried printing with or without merging them to one assembly, both with the same result.
Filament is Devil Design PLA, I have done few other prints successfully.
Print settings are as per recommendation: 0.16 Optimal @BBL X1C, wall loops = 3, sparse infill density = 0, outer wall speed = 100 mm/s. I tried both options for print infill first already.
Printer firmware is 01.06.00.00. I’m using Bambu Studio 1.9.3.50.
I have checked the sliced model and can’t see any issues, I have exported the gcode and inspected it in a viewer, also can’t see errors in the top part. Maybe somebody can give me further hints?
Edit: fix a typing error, originally I wrote wall loops = 0.
The original print & most of the makes look just like yours.
I’m going to say this is your problem.
Studio sends an error with these settings.
These settings don’t make much sense?
Have you tried printing it with standard settings?
2 Likes
Sorry, that was a typing error on my part, wall loops = 3.
In my print there’s a missing top horizontal part that should join the hubs of two gears.
OK, I thought that was a separate part that snapped on afterwards.
Try turning on Detect thin Walls.
I printed this part in ABS with stock settings and 3 walls.
1 Like
I had a clog today, not sure what was the reason, but the extruder gear ground the filament and couldn’t move it either forwards or backwards. After disconnecting the PTFE tube I was able to cut the filament, feed it manually and get the extruder to working.
Since then I was able to print the part.
I tried to reproduce the print failure multiple times trying to find the setting but was not able to. So even though my problem is now solved, I don’t think I’ve found the culprit.
Thanks @JonRaymond and @lion7718 for your help!
2 Likes
