-
Posts
32 -
Joined
-
Last visited
Content Type
Forums
Events
3D Prints
Posts posted by Andrew_W
-
-
-
I ended up using UltiMaker Polypropylene Natural for my prints.
Images of a section of the part printed to check for function and fit. Wall section is 0.5mm. I had to use a gyroidal support pattern of 80%, and also a support interface for roof and floor. The default zig zag support didn't work where the paths crossed over each other due to the material being so soft that the crossing layer pushed the lower layer out of position.
-
-
We're looking at printing abrasive filaments with both cores on our S5. Is there a lower cost alternative to use seeing as we need two of them?
-
On 2/2/2023 at 7:27 PM, Cuq said:
If you want to supress this issue reduce the value of the : Support Horizontal expansion (0.5 should be enough)
Thanks, this work OK for this part.
-
Simple question I think.
Why is my support blocker not blocking all the support? Is leaving 2 sections of support either side of the hole.
Thanks.
-
3 hours ago, GregValiant said:
Great idea! Just need to untick the connect infill lines to stop the infill on the slope.
-
-
I finally found the problem that was causing the ER65 code. On very very close inspection of the g-code I found that the layer was being duplicated at line 2201 for some reason. This put the print core at the same Z position on the layer it just finished thus not allowing any material to be extruded, and in combination with the flow sensor and the de-coupler on the material station it sensed that there was a problem. Disabling the flow sensor, or not using the material station prevented the layer error from being detected. This is why it always happened at the same spot no matter what bay, extruder or filament I used during testing.
This duplicated layer doesn't show up in preview in CURA. It's only because I have many years experience programing and running CNC machines and back plotting g-code that I found it. The back plot showed the Z not changing is what caught my eye.
I've not been able to reproduce the the code error in CURA 5.1
- 1
- 1
-
On 10/22/2022 at 11:50 PM, Gero said:
After disconnecting from the DF, I wanted to display a connection code again, but the printer jumps directly into the field with "The printer is now connected to the Digital Factory".
Despite resetting the printer's Digital Factory settings several times and resetting it to factory settings, the printer does not display a connection code and immediately thinks it is connected to the DF.
Same here with our S5 also. Was working OK until a few days ago. Cannot print anything.
-
Your attached images look just like the issue we had with too much moisture in our PVA. I put it in an oven over the weekend at 55°C and then store it in a sealed bag with desiccant. No more problems now. Hope this helps.
-
8 minutes ago, MariMakes said:
Hey @Andrew_W,
I tried your new Aborted Gcode, and again am not getting any errors on my Probundle.
I really think it's a hardware issue or material issue.In that case it's better to reach out to our support experts.
You can create a ticket here:
https://support.ultimaker.com/hc/en-us/requests/new?ticket_form_id=360000516360
Thanks so much for trying the G-code 👍. I'll raise a ticket and see what happens.
-
6 minutes ago, Torgeir said:
I'll think @UlrichC-DE give a very good hint here, as the initial speed is 20 mm/sec and from the beginning of second layer it will start printing with 50 mm/sec!
So now it is just another thing to check, the forward cooling fan, -cause this one can be blocked by stringing from the printing process. We have seen this fan completely blocked and partly blocked. So check this fan, sometimes difficult to see..
So if this one is blocked, the printing will go fine for some time, -until it stop printing completely. This is because the filament start softening in the upper part and simply become glued here. This is where we will find lots of grinding in the filament until there is no more to grab on for the feeder.
But if this fan is partial blocked, you may be able to print for a while, but your feeder will struggle "some" with added load.
However, if you need to print fast for some reason, we'll approaching fast "the limit" of feeding with this reduced cooling for the upper fan.
This may also explain why the object is printed well when turned 90 degrees? 😉
Torgeir
Hello @Torgeir, I did check the fan (all clean), the feeder and also did a print core clean.
Thanks.
-
Hello @MariMakes, I tried printing again from the project file I attached above today and like you, have found it prints OK. I also tried reprinting the aborted one again with the same result ER65 in the same place. (Could you try the Aborted G-code file on your S5?)
So I went back and downloaded one of the aborted jobs from my history in the Digital Factory and had a look at the G-code where the print failed. I then compared the G-code to the one that works. This is when I noticed the the failing code has some extra lines in it with M204 commands at the position that it stops extruding?
Does anyone know why this would be?
Thanks.
Good UMS5_Printedholder.gcode Aborted UMS5_Printed_holder.gcode
-
Thanks for the reply @Torgeir. I'll keep all the suggestions in mind if the error returns again, as I still don't understand how it could stop in the exact same place 3 times in a row.
-
Hello @Torgeir, I did look at the support page, but I think the error was a false flag. As I could abort and then restart the print immediately and it wold stop in the exact same spot (about 30min into the print). I tried this 3 times and on the third one I watched very closely, as soon as it moved to position to start the 3rd layer I could see that it stopped extruding and the error came up after about 10sec. And also rotating the project 90° resolved the issue? So I have no idea what caused the problem and how to avoid it in the future? Normally I start the print and go home but this time I was delayed and noticed it had stopped.
I've attached the project file this time (I think).
-
-
-
I started a print on our S5 and at the start of the 3rd layer it stopped with a ER65 after about 30min. Everything look good up to that point. I aborted the print and started again and it stopped at the exact same layer and position. I tried once again with the same result. What is going on?
Attached are the files for the part. Marked in the image is where it stopped each time.
Thanks.
I ended up rotating the part 90° about the Z axis and it printed fine.
UMS5_Printed holder.3mf UMS5_Printed holder.ufp UMS5_Printed holder.gcode
-
-
I've the same question, looking forward to an answer.
- 1
-
-
5 hours ago, PaulKuiper said:
The use of tree support causes a lot of retractions. PVA is protected from to many retractions and after a certain amount of retractions per time period it will not retract anymore (the dark blue travel moves below, the light ones are retracted travel moves). The causes the PVA to ooze on the model while traveling over it. Try to use the default profile (normal support) to see if the problem goes away.
10 hours ago, TimonR said:It looks like you're using 'tree' support, did you also try 'normal' support and does it give you the same error?
Thanks for the reply's, I will try normal support and see how it goes.
-
3mf file attached. The model is trimmed as above the supported area it comes out OK. I have another spool of PVA on order plus some Breakaway to try.
Thanks.
- 1
Printing test file
in Improve your 3D prints
Posted · Edited by Andrew_W
https://www.printables.com/
https://www.thingiverse.com/
https://all3dp.com/1/free-stl-files-3d-printer-models-3d-print-files-stl-download/