0scar

My printer uses 2.85 mm to share filament with the UM3E. I'll look if the diameter of the filament is accidentally set to something different than 2.85. Thanks for pointing to this possibility! edit: Indeed, the filament diameter has somehow accidentally changed... Many thanks for pointing to the correct direction!

No, there is one UM3E stored in the cloud, but that printer is at a different site, furthermore it wasn't even added to this instance of Cura as I wasn't logged in. In a last resort I've removed all appdata and installed versions of Cura and started fresh with a new 4.7 install. The market place has no added plugins (as it should), after adding ColorFabb and Eastman, they simply don't show up in the materials list. Strange thing is that it used to work in 4.6, I even added a set of my own material profiles, but I noticed prior to updating to 4.7 that the materials where suddenly m

Materials I added myself or downloaded from the marketplace (e.g. Eastman Amphora or ColorFabb) do not show up in Cura 4.7. Anybody experienced similar problems or knows how to fix it?

I have installed the 4.4 Beta. I'm able to re-establish the connection with the printer and can print again. Thanks for your help! Note that 4.3.0 did work for our other department on their UM3E and UM5S, but somehow not on our identical UMS3.

No problem to test it out, PM me for a pre public release (if necessary). Another department at work have a 3E and an S5, so I can ask them to also test if possible (I believe they are still on 4.2).

My Cura 4.3.0 keeps crashing on me just after the GUI has loaded (my apologies to the Cura development team for reporting so much crashes...). Removing all the files from local and roaming gets me further, I get into selecting a printer and see that it fails there. If I select the printer from the network (Ultimaker 3 Extended) the program crashes, but when I select the same printer from the list, Cura continues. Have not tried to print anything as I lost all material profiles. Anyone experiencing the same issue? How to proceed further to connect the network printer? Th

That is definitely an answer! And a great reference for those who seek the same. I guess this should all be done in a post processing script of your own.

I'm aware of the availability of keywords that can be used in G-code that are parsed by Ultimaker Cura on compiling the G-code file. I'm missing a good reference how you can do some basic arithmetic to parse a formula to a value rather than an in-place substitution. E.g. in Slic3r you can use some complex arithmetic and conditional statements to define custom values. In defining a certain speed (in mm/min) based on a travel speed (in mm/sec) in end or start G-code one might to use something like: G1 X0 F{speed_travel}*60*0.75 How would you implem

I learned that CPE is a co-polyester like PETG. I use PETG a lot (colorFabb 2.2 kg spools) and have had similar issues. I print PETG at 235 - 240 degC and no fan. This gives fairly good results, but not as nice as NGEN or PLA. You could try and print a custom temperature tower and see which temperature/speed/cooling/etc. options give you the best result.

There are post processing scripts available to pause at height or tweak at Z. The first could easily be used to change filament. You'll find the scripts under main menu item "Extensions" -> "Post Processing" -> "Modify G-Code" and then add the script of your choice.

Yay, I took me a while but I got it running after a lot of fiddling with the Cura profiles in the roaming\cura folder! Windows updates, graph driver update, etc. Bottleneck where the printer profiles...

Just installed Cura 3.2 BETA on an i5 with a GTX970 and again as version 3.1 it won't run on my machine... Please guys, make it work! I want to try those nice new features. P.S. Where is the signup for Beta testers, my machine is a killer for you! Running 3.2 will throw me this:

Hi, I have 4 banks of which 2 are filled with 8 GB memory modules, maybe I also qualify for these kind of software/hardware issues. I have no urge to pull modules, I'd rather wait for a new working version or stay on an older one for now. This should be something the devs could try on the test machines. Version 3.2 looks promising with nice features, I'd love to try those.

Dat probleem is al lang bekend. Bij de eerste versie van de moederborden was het probleem voornamelijk de stekker op het bord, die is in de latere versie (die je nu koopt; al vanaf dec. 2016) vervangen door schroef connectoren. Je moet echter wel zelf even c-clamps of vorken op goede kabels krimpen! De stekker op het heat bed moet wel direct worden vervangen door het liefst nieuwe draden (AWG 14) te solderen aan de achterkant van de connector, de draden voor thermistor kunnen wel blijven zitten. Wil je het demontabel maken stop er dan een XT60 connector tussen en een strain releave

Strange thing is I only can not run v3.1, but all other versions below that one run fine. Indeed very strange, and IMHO, there is no attention given to the people complaining. There is no problem as long as you ignore it. I hope v3.2 works, will try that tonight.