All Activity

Mijn zoon (13) heeft waarschijnlijk abusievelijk een verkeerde firmware update gedaan. Volgens hem stond het hele LCD scherm vol met U4 meldingen. Connectie via USB niet mogelijk. LCD is blauw (zie foto). Fan draait wel (hard als voeding aan staat, zacht als USB is aangesloten). Verder helemaal niets. Is er een oplossing voor dit probleem? Met vriendelijke groet, Sabri

"... the nozzle hit the object while passing from ..." I am not a fan of using "Z-Hops" but for some models it is unavoidable. There are several causes of the nozzle hitting a print. The two most popular are: Depending on the Infill Pattern, the infill can develop high points that are above the layer height. Enabling "Connect Infill Lines" can help with this. Feather edges develop and warp upwards (like when closing large horizontal holes). Enabling "Z-hop on Retraction" can help a lot. I usually set it to 0.50mm.

Ok I just realized I used the stock TPU setting accidentally instead of your tweaks. I'm shocked that it even melted enough to do anything at 210 degrees. I'll print one with your settings.

My dryer gets to about 110F, which does seem cold to me. I didn't unspool any filament and I left it in for 8 hours.

Hey All, I've come across this issue where cura tries to start the walls mid air when it could easily start from where there is already material (yellow circle) as you can see in the picture i enable bridging but that doesn't keep it from starting mid air, I can't use support as I'm printing with PETG. Is there any existing settings I could try to make it start from one of the fins of the impeller? (yellow circle) if not this would be an awesome feature for the next update 🙂

Could be done with a postprocessing Script, or a script .

The suggestion has been made to delete the log files in %appdata%\cura. I have attached the log files from the successful execution of v5.3.1 (please note that stdout.log is empty, and so this app refused to attach it?). I then deleted them, and installed v5.7.0, which, not unexpectedly wouldn't start. However, it *also did NOT create* any new log files while attempting to start. So, deleting the log files in %appdata%\cura did not fix the problem, and in fact v5.7.0 doesn't even get as far as creating a log file. Perhaps the "debugging" was left on, and the offending call is to a logger? stderr v5.3.1.log

i have been searching for this too. Maybe one solution would be to design a boss on the surface you want to fill from, have the boss att the top when printing and pause/stop the print at the last layer before the boss

Installing up to version 5.3.1 works fine. Including installing it to a custom location, in my case the D drive. I'm installing it onto an Alfawise Z83 tiny PC, that lives in the garage with the 3D printer. I access it by remote desktop. The PC only has 32GB of internal storage, barely enough for Windows 10 Home (WinPE version), since Windows is a disk hog, so I have installed a 128GB SSD via an internal USB port, HDD D:\, and put all my applications on D:. If you try to install v5.4 and up you get the attached error message: Error message from 5.4 and above.pdf This message results from a call to a non-existent handle in the QTWidgets DLL, distributed with the version. If version 5.3.1 is installed, it can be started correctly. If v>5.4.0 is installed *on top of* v5.3.1 (same directory), version 5.3.1 won't start, and throws the same error message. Installing on top of another installation isn't kosher, but it is an interesting experiment showing that the QTwidgets DLL is the problem. It should be noted that I had v5.7.0 running on this PC. This PC has been used this way since v4.5, or so, and I just added the new versions as they came out. When I added the 128GB SSD, I damaged the OS image, and had to replace it. Since then I have been unable to reproduce the functioning installation. Nevertheless, v5.3.1 installs and runs *every time*, v>5.4.0 never runs after installation. My installation of Windows 10 Home is completely up to date, so this isn't a Windows staleness issue (polemics aside). I don't have Python installed on this machine, but the error is the call to a non-existent handle in the QTwidgets DLL, not Python. There is clearly a problem with a call to a non-existent handle in the QTwidgets DLL distributed with versions >5.4.0.

Merci Alain_D de m'avoir aussi conseillé 🙂

👍

Bonsoir GregValiant, Merci pour votre réponse. J'ai imprimé 2 objets, et les impressions se sont très bien passées, jusqu'à 100 %. J'en ai tenté une 3ème mais au 3/4 de l'impression, la buse a tapé dans l'objet en passant de la tour d'amorçage vers l'objet. Du coup, mon objet s'est décollé. Le problème d'arrêt de la température à 98% de l'impression est donc apparemment résolu et cela grâce à vous. Depuis 5 mois que j'ai cette imprimante, personne n'avait su me donner LA bonne solution. Je croise les doigts pour que les prochaines impressions n'apportent plus ce problème ! Un ENORME merci à vous 🤩 Je saurai à qui m'adresser en cas d'éventuels futurs problèmes ☺️😉

I'm not afraid of the cow. (I'm far enough away!!)

Look @Slashee_the_Cow!!! I didn't say it!

I see the issue you are talking about above. Very strange. I tried your 3mf file in cura 5.4.0 and it sliced fine. I noticed 2 things: 1) Layers 158, 174, 250 were fine 2) Only top/bottom layers should be yellow and for me only top/bottom layers were yellow. But you show yellow layers in the screenshots above! For me the layers were "infill" which is orange. So something is very strange with your version of cura. I think this may be a known bug. Anyway I strongly recommend you install and use Cura 5.4.0. It's okay to have multiple versions of cura installed at the same time.

Ich möchte nach dem Druck das die X Achse auf -20 fährt. Habe schon etliches ausprobiert aber beim beenden des Drucks fährt ganz nach links, und dann auf die Position 0 Wie kann ich das ändern. Mein Momentaner G-Code G91 ;RelativMode G1 Z3 E-2 ;Fast-Einzug und anheben G90 ;AbsoluteMode G28 X0 F2400 ;ganz nach links G91 ;RelativMode G1 E-35 F100 ;Slow-Einzug G90 ;AbsoluteMode M104 S0 ;Hotend auf Null M140 S0 ;Bed auf Null G1 Y220 F2400 ;Bed nach vorne fahren G1 X-20 F2400 ;Bed nach links fahren M84 ;Motoren abschalten

Yes sorry, As it is not anymore compatible I've removed it from the Marketplace.

Hi @Cuq Cause of this message? "The given author does not exist."

You can try (I'd start trying at 0.1mm because I like nice round numbers) but I can't make any promises, it's sort of up to the printer at that point.

Hello community, I have a problem when slicing a part with an 83% lines infill. In some random layers and positions in the component, errors in the infill can already be seen after slicing in Cura 5.5.0, which are also visible when printing with the Ultimaker S5. The extruder does not move parallel to the previous line, but at an angle. Also, instead of a U at the end of a path, it makes an 8. This is perhaps easier to see in the following pictures. I have already tried to change some settings. However, the problem also occurs with other infill densities (80-90%), as well as with other components. Even a different positioning on the printer bed does not solve the problem. As the print is intended for CT imaging, these printing errors can be seen in the printed component. I would be pleased to receive ideas on how this can be prevented or subsequently corrected. In the attached file, the error occurs in layers 158, 174 and 250, for example. Many thanks and best regards! UMS5_Kegel_Druckfehler.3mf UMS5_Kegel_Druckfehler.ufp

I added a compatible Ultimaker S3/S5/S7 profile for PrusaSlicer On the PrusaSlicer profile settingsrepo: https://github.com/prusa3d/PrusaSlicer-settings/tree/master/live/Ultimaker Implementation details: https://ansonliu.com/2024/04/ultimaker-s3-s5-s7-prusaslicer-profile/

Please see: Moonraker Connection - Ultimaker Cura Marketplace you add that plug-in to Cura, and connect it to the IP address of your Sonic Pad. Then, you can upload, or upload AND print right out of Cura itself. Very handy, and that's what I am using!!! Good Luck! --Mark

Starting with Cura 5.0 the "QT Controls" dialog boxes, settings boxes, buttons, etc. that Cura uses went to a different QT version. That Qidiprint plugin looks like it hasn't been updated in 4 years so the settings it tries to add aren't working and that causes an error. If you want to print via a network you would probably need to research whether OctoPrint is an option. There is a Cura plugin but it also requires it's own hardware (usually a Raspberry PI board).

The seam is a function of FDM printing. There will be a point on the outer wall where the nozzle starts to extrude it. The Nozzle travels around extruding the outer wall, and then ends right where it started. Those starts and ends are what makes the seam visible. There is an Inner-Wall seam, a Support seam, an Infill Seam, a Prime Tower seam, and a Support Interface seam. Even an "Ooze Shield" would have a seam. Only the Outer Wall seam is displayed because it's the only one visible on a finished print. The preview would get kind of cluttered if they were all shown.

Dont know why, other can see it.. hmmm anyway, I followed advice from monroe7 and used a solder iron to melt the mess little-by-little until it was gone. turns out the only thing the plastic was adhered to was the silicon membrane so it only took 15 minutes or so to clear it. Now I gotta remember how to put a new membrane in it 🙂