Jump to content


Popular Content

Showing content with the highest reputation since 10/22/2019 in all areas

  1. 3 points
    I can say something about that! The visual intents change the following settings: speed_infill = 50 wall_thickness = =wall_line_width * 3 top_bottom_thickness = =wall_thickness It's not a whole lot, but they were added last. I expect the visual intents to get more changes in the next releases. The engineering profiles do a whole lot more: infill_line_width = =line_width jerk_print = 30 jerk_infill = =jerk_print jerk_topbottom = =jerk_print jerk_wall = =jerk_print jerk_wall_0 = =jerk_wall jerk_wall_x = =jerk_wall jerk_layer_0 = 5 line_width = =machine_nozzle_size speed_print = 30 speed_infill = =speed_print speed_layer_0 = 20 speed_topbottom = =speed_print speed_wall = =speed_print speed_wall_0 = =speed_wall speed_wall_x = =speed_wall top_bottom_thickness = =wall_thickness wall_line_width_x = =line_width wall_thickness = =line_width * 3 xy_offset = =- layer_height * 0.2 Note that these intent changes sit on top of the existing profiles (so they override settings if both of them define it)
  2. 2 points
    Thanks for the references to the metal gears. I've seen those but would like to avoid a metal-plastic interface, generally the plastic goes quickly (depending on the finish of the metal gear). However, this might be the ticket to get the UM printer going for a while if gluing does not hold. LocTite makes some epoxy for glueing Delrin, it needs heated curing. Might need to give that a try.
  3. 2 points
    sqrt3 is a bit of a strange name: Whereas sqrt is short for square root, sqrt3 is actually the cube root. Square root of a value is the inverse function of square of a value: sqrt(value * value) = value. Cube root of a value is the inverse function of the cube of a value: sqrt3(value * value * value) = value. Here's a calculator: https://www.calculatorsoup.com/calculators/algebra/cuberoots.php
  4. 1 point
    Hallo Hendrik, Ich würde dir empfehlen eine Rolle UM PVA zu kaufen und damit deine Tests zu machen. Filament von anderen Herstellern kann funktionieren, kann auch gut sein, muss aber nicht. Mit dem UM PVA wissen wir, dass es klappt, daher teste einmal mit einer UM Spule, damit du anderes ausschließen kannst. Wenn das klappt, können wir uns dann immer noch an das andere Material herantasten. Da wollte einer auf Nummer sicher gehen 🙂 Die Düsen vom UM Core gibt es nicht zu kaufen auch nicht von anderen Herstellern. Die handelsüblichen Düsen passen am UM Printcore alle nicht.
  5. 1 point
    I don't have this material, but my experience with PET is just the opposite. On my UM2-printers, I achieve the best bonding and best fill rate (=least amount of unwanted voids inbetween extruded sausages) at very low speeds, thin layers, and low temperatures. Typically 20...30mm/s; 0.06...0.1mm layer height; 210...215°C nozzle temp; and no fan (!). Due to this slow speed the material has plenty of time to melt and bond with the previous layer. Due to the thin layer, the heat from the nozzle is transferred well onto the previous layer. And due to the low temperature, even 5...10°C below the recommended minium, the material does not decompose too much in the nozzle, even though it is sitting there for a longer time. When these models break, the fracture goes diagonally through all layers, as if there are no layers. Absolutely no delamination-effects, which indicates a good bonding. See the photos: the fracture lines start at the bottom center, and then radiate outwards in a star-pattern, regardless of layers. This is clearly visible under a microscope, but hard to photograph. Layers are very lightly visible too, running vertically in these photos. This model is ca. 6mm x 4mm cross section. It might be worth trying this too? The main disadvantage is of course that it goes very slow...
  6. 1 point
    alles UM Teile,habe ich evtl. blöd geschrieben, ich hatte einen Kaputten 0,25 Heizblock dann habe ich die Platine und die Düse in einen 0,4er Heiblock gebaut da war die Düse kaputt:D das Problem habe ich auch ja, wenn ich kein Breakaway brauche dann zieh das am Feeder dann paar cm einfach zurück
  7. 1 point
    I'm glad you asked! We're getting that ready and will roll it out as soon as possible! @Tomhe ❤️ so, stay tuned!
  8. 1 point
    Oh dear.. 😅 Yes, the plugins (all CAD ones) are incompatible now. I was recently very busy with something else (as Terri knows). So since the other thing was more important for the moment and the plugins are still non-profit software. I focused on the other thing. Anyway, as soon as I find the time (and I really promise to do!) I'll review the plugins whether they are affected by the API change and fix eventual bugs. Additionally, there are other things to do related to the plugins. So yes, the to-do list is growing every day. .. I'm never getting bored..
  9. 1 point
    @hartparr - We have an internal ticket to fix this issue. Thank you for reporting it and providing the model where you see it happening! For Cura internal devs: CURA-6989
  10. 1 point
    I just installed new Versrion on a Apple Mac, and now I can not start CURA. Mac OS shows a Error Message, translated like "MAC OS is not able to check file for Virus". Update 21.11.2019 I am very sorry, my mistake. It was a MAC OS Problem, not a Cura 4.4 Problem. Cura 4.4 is now running on my MAC OS.
  11. 1 point
    Can you also share your config folder, please? You can PM it to me. It will be faster this way for us to find out the cause of your crash. Your config folder can be found in the Help menu > Show Configuration folder > go one folder back and zip the whole Cura folder. This way, we can check if there was a problem with upgrade.
  12. 1 point
    Is there a way to create subfolders for profiles? This would be VERY useful as I print in a range of materials and with different infill settings regularly and end up with a ton of different profiles, which are difficult to name and manage effectively!
  13. 1 point
    Heres my Cathulhu model. Came out great considering it was full of intersecting geometry. I realised that if i have unassigned polygroups on an object and bring them into MAX then it creates seperate elements within the object that arent joined geometrically to the model yet still a part of it. Cura doesnt like this. At all. I keep forgetting to reassign my elements after editing them! Oh well. it works and thats all that counts! Well done cura! Ill post more pics as it complete it. Its a bit impossible to see whats going on at the moment. The wings are using my classic bespoke support because cura cant create good support for thin tall vertical objects and anything vertical that starts with a sharp spike, like the bottom of a dragon wing claw or fingers pointing down. Eitherway not hard to remedy bespokely. maual support is 0.4 -0.6mm thick for those interested. Now for the clean up, filling, acetoning, sanding, spraying, and painting!
  14. 1 point
    Das heisst im deutschen Cura auch Combing-Modus. Ich empfehle diesen hier bei Nicht in Außenhaut setzen. Wenn du den auf Aus setzt, hast du eine Retract Party. Diese Linien auf der obersten Schicht könntest du mit "Einziehen bei Fahrt zur nächsten Schicht" eventuell loswerden.
  15. 1 point
    It's rare, but I've seen a pinched front fan cable (the black and white one) cause electrical interference with the active leveling. To test this unplug your front fan and run active leveling and see if it works. (Note: don't run your print this way; running prints without your front fan can make the filament swell in your Print Cores.)
  16. 1 point
    Jupp, Du hast recht, hab ich tatsächlich übersehen das dünne Ding 🙂
  17. 1 point
    If you loosen 2 screws at opposite diagonals then you can rotate them totally freely.
  18. 1 point
    Its for a Lego Car for a centerlock Its printed in Pla with Breakaway on UM S5
  19. 1 point
    If it is stuck in the Bowden tube and you are not able to get it out as Reiner described, you can also try to completely remove the Bowden with the filament and hold it under warm water. PLA gets soft at 60°C so your chances are higher that you will get it out.
  20. 1 point
    @mrtinfy Yes. There is an issue...but it is not as simple as you think. Many of us run Cura on systems that have the newer redistributables with no problem. My Surface Book v2 runs it fine in its laptop configuration that uses the NVidia GPU in the keyboard. But it will not launch properly when in tablet mode where it uses the integrated Intel GPU. I have given this info to the team both here in the forums and on the Github issues section, but I don’t pester the team asking, “Is it done yet?” One of the truly frustrating things in software development is to have bugs that a small group of customers see, but that you cannot reproduce on the computers you have available for testing. Letting other users know what worked for you, as you did in your initial posts about this issue, is good because it gave others who have the problem a possible workaround. It also let others add to that, for example my comments about needing to reinstall the later redistributables one Cura was installed so as to not break other programs. This is collaborative troubleshooting. And these points of information may provide clues to the development team.
  21. 1 point
    I am not "from the team", but I think it is the shear number of profiles that need to be made and tested to support more printer, printcore, material, quality and intent profiles.
  22. 1 point
    Glad to hear it works and thanks for the feedback. 👍
  23. 1 point
    The delivered one are: c:\Program Files\Ultimaker Cura 4.3\resources\definitions\
  24. 1 point
    To extend or setup everything else, you should take a look in the printer definition files. Additionally the build plate you see in Cura is just a picture, so even if you extend your build volume, the picture remains as is. But as far as I know the grayed areas are build dynamically depending on the printer definition. I am on a Mac and the printer definition files are within the application package. You can copy the UM2+ profile from there and place it into the user configuration folder (definitions). Otherwise you would loose your profile after a Cura update. You have to search for the folder in Windows. The folder is called definitions and the file you want to copy is named ultimaker2_plus.def.json
  25. 1 point
    https://ultimakernasupport.zendesk.com/hc/en-us/articles/115004324223-Printhead-Parts-Ultimaker-2-#Print Head Block
  26. 1 point
    Yes, this seems like a very good idea, I hadn't thought of that: less friction, and far less complexity, especially when changing filament. You just need to make sure that the external tubing is long and flexible enough to be pulled up to the feeder automatically when the filament moves.
  27. 1 point
    Yeah, it won't allow you to do just the holes though, sorry buddy.
  28. 1 point
    Note that you probably logged in as ultimaker/ultimaker but you can also log in as root/ultimaker and get access to all the python files there. But I think you found what you are looking for. I'm pretty sure those the the correct values. I don't know why those are defaults when travel moves have a jerk of 50! And accel travel can go to 5000mm/s/s. It seems like you would get more accuracy with maximum jerk and accel. But you get less ringing with lower jerk and accel (ringing is visible and ugly but vanishingly small compared to other sources of dimensional errors). So I suppose it's a tradeoff - higher accuracy versus more beautiful. There are quite a few differences between the nicest looking profiles and the most dimensionally accurate profiles. Have you seen the new profiles in the beta cura? Anyway, bulging corners are caused when the printer slows down for the corners yet the pressure is still high. The simplest way to fix this is to lower the print speed down to around the jerk speed although 30mm/sec should be slow enough. Other ways are to crank up the jerk and accel. It also makes a lot of sense to cut the corners in the CAD model (and other modifications like make all vertical holes 0.4 to 0.5 larger in diameter than desired). Just bring in the corners to compensate for what the printer does. If you think it's bad for FFF printing you should see what it's like - all the crazy changes you have to do - to create an injection mold. If you want 90 degree corners the CAD model actually has to be <90 or >90 (I forget which). I assume most European and USA mechanical engineers don't deal with this as the CAD modifications tend to be done in Asia. But for FFF printing it's done usually in-house and you have to do these tweaks.
  29. 1 point
    This is day 2 of "Inside the Ultimaker 3", Remote access. - Other days: Day 1 - GCode Day 3 - Remote access (part 2) - A new day, a new piece of information. Yesterday we took a quick look at the changes in gcode files. Which is the core of pretty much any 3D print. Today, we will look at the remote access trough the network. The remote API is designed to allow control of the machine trough the network. It is what Cura uses to control and monitor the machine remotely. - Even if you are not a software engineer, there is added value for you here. So do not stop reading yet! The technology behind the API The API is a REST interface using JSON. That could be 3 new words for you right there. Don't worry. API: Application Programming Interface. Simply meaning it's an thing designed so that applications can talk to eachter. Does not mean we cannot use it as an user. But the end goal is for other applications. REST: Representational State Transfer. Just a fansy way of saying that every "request" you do to the printer is "stateless". Also, just a standardized way of doing things. The really cool part here is that is done trough HTTP. JSON: Javascript Object Notation. A standadized way to represent data. This makes it easier for applications to understand each other. Nothing to worry here, it is quite easy to read by humans. HTTP: Hyper Text Transfer Protocol. For those that missed it, I introduced this term in the REST term. If you are now like "I have seen this before, but where?" that is most likely true. Http is the way your browser talks to a webserver. So, in a nutshell. Our remote access on the printer is actually just a website acting in a standarized way so applications (like Cura) can understand it. Example time! You most likely don't have your fansy Ultimaker 3 yet. But I do. Now, first things you need to do is connect your printer to a network. As it's not really possible to access something remotely without access. So setup that WiFi or just plug in a cable. - Next you need your IP address. You can find it in the {SYSTEM}->{Network}->{Connection status} menu. It is those 4 numbers with dots in between. For this example, I'll be using, as that is my printer. - Now, you don't need any tool. As you already have the tool for basic viewing of data. You are looking at it. It is your browser. You have this fancy location bar at the top of your browser. And if we enter there, we will see the result: "" That is your firmware version. Could not be simpler. Just so you know, the firmware version is build out of [major].[minor].[revision].[date], every version we use, even internally for testing, gets a new number for tracebility. - I picked a simple example for a reason, so we could look into this at a bit more detail first. The address you entered. Or URL as it is called in fancy computer terms is made up out of these parts: http://: This means we are using http. Part of REST remember? The IP address we looked up on the printer. /api/v1: This means we are accessing our API, and the first version of it. If we ever need to make incompattible changes, we will have a v2 here and keep the v1 for a long as we can. /system: We are accessing the "system" part. System contains things that are not really 3d printer specific. Any device could have these properties. /firmware: We are requesting the "firmware" part of system. Which is defined are returning the firmware version. Having that made clear, in the system we have the following parts: - Returns the linux version that we are running on, who cares right? - Returns the hostname of the printer. This is not user configurable and will remain the same unless electronics are replaced. So you can use this to uniquely identify the printer. - This is the user configurable name. You are asked to configure this during the WiFi setup. - As explained, the current firmware version. - The amount of memory in use by the system. - The amount of memory available in total. - The system keeps a log of many state changes, this API accesses that log. More on it later. - The configured language, we are preparing for providing the printer in your native language as well. But we decided not to delay the release for this. So this is always empty right now. - 2 letter country code, if configured. This is done during the WiFi setup. WiFi hardware needs to be configured for your region to make sure the proper WiFi channels are used. If you don't use WiFi this is most likely empty. - However, if you want all of these in a single go. You can just request: Which will respond with: {"country": "", "firmware": "", "hostname": "ultimakersystem-ccbdd3000229", "language": "en", "log": ["...", "..."], "memory": {"total": 1057030144, "used": 125394944}, "name": "Ultimaker-000229", "platform": "Linux-4.2.0-rc7-opinicus-00001-g63c264e-armv7l-with-debian-8.1"} Note that I cut out the log data, the rest is a JSON response. It looks a bit hard to read, but computers have no problem in reading it. There are however, tools to format it in a more readable way: { "country": "", "firmware": "", "hostname": "ultimakersystem-ccbdd3000229", "language": "en", "log": [ "...", "..." ], "memory": { "total": 1057030144, "used": 125394944 }, "name": "Ultimaker-000229", "platform": "Linux-4.2.0-rc7-opinicus-00001-g63c264e-armv7l-with-debian-8.1"} There is currently on the printer that uses /api/v1/system/log to view the latest log data in a more readable format. It was quickly put together and I'm sure we will expand to a better web interface for the printer in the future. But, it is a 3D printer! Yes yes. It is a 3D printer. So we want 3D printer data. And we have that. There are 2 basic important start points: The first contains a lot of information about the printer itself. And all of those things can be accessed in the same way as the system part. The second contains information about the currently running print job. If no job is running, you will get a "not found" error. For the technical people, this includes status code 404. /api/v1/printer Let us look at the /api/v1/printer first. This as the following sub parts: /api/v1/printer/led - Part to access the printer casing leds. /api/v1/printer/heads - Part to access the printer head (more on this one later) /api/v1/printer/bed - Part to access information of the printer bed, limited to current and target temperature. /api/v1/printer/status - Best thing to look at first. Basic status of the printer. This could be "idle", "printing", "error", "maintenance" or "booting". Will explain in a bit. /api/v1/printer/beep - Nothing to read from here. Can be written to to make the printer beep. /api/v1/printer/diagnostics - Different diagnostic functions. Retreiving this part does not do anything, but it has sub parts that are not collected in the /api/v1/printer that can be used for in depth diagnostic functions. We WILL go over this for sure. /api/v1/printer/network - Contains the WiFi and Ethernet information. Mostly usefull to see if it is cable of WiFi connected. But the WiFi setup process uses this to connect to a network and to see which networks are available. /api/v1/printer/status The main status of the printer, can be: idle: Printer is doing nothing and ready for action. printing: Printer is actively printing something, or still needs to be emptied, print_job needs to be retreived for details. error: Something is wrong with the printer, and requires action at the printer itself to be corrected. maintenance: Someone is actively doing things with the printer, for example changing materials or PrintCores. booting: Printer is still starting up. This only lasts for a few seconds. /api/v1/printer/heads The printer has a single head. However, the API is prepared for possible futures, so it accounts for multiple heads already. Do not take this as a reason to think we are developing multi head printers. It just good engineering practice to have this in place when it costs almost no effort. - So, the actual part that we need to access for print head information is: Software engineers are mighty annoying, as we start counting at 0. So the first head is identified by 0. The first hotend is identified by 0 and the second one with 1. - In here we have some basic settings like acceleration values, maximum speeds, the current position and linked extruders with their hotends. Feel free to explore. As you are all in love with the current hotend temperature, I will show you that one: For the first and second extruder. But, by sheer magic, we also know what type of PrintCore you have in the machine, which can be seen from: In my case, it returns "AA 0.4" There is the fan entry: Which contains the print cooling fan speed in 0% to 100% (not 0 to 255 as you see in GCode). The head cooling fan state is not accessible, but directly linked to the hotend temperatures. Small note of warning There is However, this breaks with the rest of the API and will be removed. Use the lower case instead. /api/v1/printer/diagnostics Currently, the only intressing part here is: The last number can be changed up to 20000, but that might take a while to load. The printer takes about 10 samples per second. The result of this is: [["Time", "temperature0", "target0", "heater0", "flow_sensor0", "flow_steps0", "temperature1", "target1", "heater1", "flow_sensor1", "flow_steps1", "bed_temperature", "bed_target", "bed_heater"],[62868.34765625, 23.100000381469727, 0.0, 0.0, 0.0, 0.0, 23.0, 0.0, 0.0, 0.0, 0.0, 18.299999237060547, 0.0, 0.0],[62868.453125, 23.100000381469727, 0.0, 0.0, 0.0, 0.0, 23.0, 0.0, 0.0, 0.0, 0.0, 18.700000762939453, 0.0, 0.0],[62868.5625, 23.100000381469727, 0.0, 0.0, 0.0, 0.0, 23.0, 0.0, 0.0, 0.0, 0.0, 18.399999618530273, 0.0, 0.0],[62868.671875, 23.100000381469727, 0.0, 0.0, 0.0, 0.0, 23.0, 0.0, 0.0, 0.0, 0.0, 18.399999618530273, 0.0, 0.0],[62868.78125, 23.100000381469727, 0.0, 0.0, 0.0, 0.0, 23.0, 0.0, 0.0, 0.0, 0.0, 18.399999618530273, 0.0, 0.0],[62868.890625, 23.100000381469727, 0.0, 0.0, 0.0, 0.0, 23.0, 0.0, 0.0, 0.0, 0.0, 18.5, 0.0, 0.0],[62869.00390625, 23.100000381469727, 0.0, 0.0, 0.0, 0.0, 23.0, 0.0, 0.0, 0.0, 0.0, 18.299999237060547, 0.0, 0.0],[62869.11328125, 23.100000381469727, 0.0, 0.0, 0.0, 0.0, 23.0, 0.0, 0.0, 0.0, 0.0, 18.700000762939453, 0.0, 0.0],[62869.22265625, 23.100000381469727, 0.0, 0.0, 0.0, 0.0, 23.0, 0.0, 0.0, 0.0, 0.0, 18.5, 0.0, 0.0],[62869.328125, 23.100000381469727, 0.0, 0.0, 0.0, 0.0, 23.0, 0.0, 0.0, 0.0, 0.0, 18.0, 0.0, 0.0]] It is a history of temperature data for both hotends, and the bed. There is the current temperature, the target temperature and the amount of heating output. There is also something in there called "flow", but that returns 0 for you. Sorry. Now, this data is a bit hard to parse. But lucky for you, if you want to save this data you can do so very easy, by adding ?csv=1 behind it. Note that this is the only API part that supports this download. However, like this you can store it for later viewing, or do all kinds of crazy math and graphing with it, as microsoft-excel or libreoffice-calc can both import this file with relative ease. - There is currently on the printer that uses this data to plot a real-time temperature graph. It is not an official feature of the printer and something we used during development. But it is damn cool. I'm a 100% sure will will expand this diagnostics part later with more data collection. So stay tuned for firmware updates. /api/v1/print_job That's the part that returns the currently active print job. Or it returns: {"message": "Not found"} If there is no print job running. It does not return a whole lot of information, but I think it is the most important information that you can have about the printer. So I will go over it in great detail. A result when a job is running looks like: { "name": "Most awesome PVA print ever done.gcode", "progress": 0, "state": "pre_print", "time_elapsed": 0, "time_total": 0} Initially, the most important entry to look at is the "state", this is different from the printer status. And can have the following values: printing: Print is currently busy. Most common state. pausing: Print was busy and the printer is in the process of going to the paused state. This usually does not last long. paused: Print is paused and thus will not finish without used interaction. resuming: Print is resuming after a pause. Could be heating up the hotend again so this can take a while. pre_print: Preparing to print. This is the state before any gcode is run. Active leveling is done during this state as well as heating up the bed/hotends. post_print: Print is finished, cooling down things and homing the head. This state lasts a while because of how the hotends are properly released from filament. (user can skip part of this at the machine) wait_cleanup: Print is fully finished, everything is cooled down. But the print still needs to be removed from the printer. This waits for a conformation of the user at the printer itself. The progress value is from 0.0 to 1.0 for 0% to 100%, the time values are in seconds. Note that the time_total will be updated during a print as the estimate on when the print is finished will be adjusted during printing. Printing estimates from Cura are usually within the 5% error range. And due to some extra time markers we added the estimate is generally less then 1% off after 2 layers of printing. - If you only care about a single value, you can request just that, just like all the other parts of the API. Documentation I've uploaded our work-in-progress documentation files at: http://software.ultimaker.com/jedi/api/2016.10.20/, these can be viewed with http://editor.swagger.io/. Note that there could be errors and mistakes in this documentation. Wrapping it up This is day 2. I think this is a information overload for quite some people already. I also have actual work to do. Tomorrow I will go into the details of using the API to actually change things. That will be a lot more technical then today. Expect code. Also, I don't know how many days I will fill on remote access. As there is a lot to cover. Stay tuned. - - Disclaimer: Any information presented here could be wrong. I did my best to proof read everything, but it could conflict with official statements and the actual behavior of the printer.
  30. 1 point
    The update to here also broke bed leveling and thus printing with support material at all. This is an UM3. Just as described initially in this post. As a lot of UM3-appliances got this problem suddenly by firmware update: is there some hope to get this repaired in the near future or is there still no clue to solve this?
  31. 1 point
    The answer depends what printer you have. UM3/S3/S5. If you have a UM3 then I recommend you disable automatic leveling and do a careful manual level. However I suspect this is an S5. Something is going wrong with the autoleveling I think. The second head is too close or too high off the glass (you can verify by pushing up or down on the glass while it prints with the second head and filament should stick nicely). Autolevel failures are usually caused by spring issues. You basically need the spring in the cores to be stronger than the spring in the bed. This is a simplification but often one needs to make the core springs stronger or the bed springs weaker. You can weaken the bed springs by moving the bed up a bit so the 3 springs are compressed less. Try 10 rotations of each of the 3 levelling knobs, then redo manual level. You can test the cores by putting the nozzle on a postage scale and pushing down until you first start to see a tiny bit of movement. This should happen at 1.0 kg (or higher). Less than 1kg force needed means the core may have vertical calibration issues. Which model printer do you have?
  32. 1 point
  33. 1 point
    See, thats the problem, can't even recalling ever heard 'tredje roten ur' 😄 Men alltid kul att läsa lite svenska... I guess I'm out of my league here, but is that (sqrt3 (0,6/1,45)) the actual formula. I'm mostly thinking of of that 'sqrt3' thingie. Or is this solvable with just multiplying and/or dividing? *I guess I don't make a lot of sense due to my ignorance. I looked at my calculator and found that sqrt3 function and managed to get the result you gave me so hopefully I can remember this. Thank you Anders!
  34. 1 point
    It is printed on an UM2+ with a front window to reduce warping problems. I did not try to print it with a raft until now... I may give that a try. You got the cross section well, the design modification seems tu be a good idea too!
  35. 1 point
    It could be that the plastic contains an electric charge because plexiglass can be staticly charged. but it is highly unlikley because the nozzle itself is probably grounded via the heater cartridge and thus removes any charge from the print plastic. Also the printer is sensitive to static charges (ESD) and this could damage the electronics, so it makes sense that the printers are propperly grounded. If you suffer from any charge you could fix this by 'grounding' the filament and so remove any charge present. But I highly doubt that PLA of some sort could hold an static charge, because it is plastic, non concuctive and there is not much chance for the plasic atoms to become charged. I have never heard of this and (as an electrical engineer) I think that it is never going to hapen because there is nowhere for electrons to build a charge inside a printer plastic part. It just doesn't make any sense, but it is nice to wonder abount these kind of topics, good food for tought.
  36. 1 point
    So I’ve had my UM3 for a few weeks now and love it but have had a few clogs using the PVA material in the BB 0.4 print core. This became exceptionally annoying when printing something like Gyro the Dodo which takes days. One thing I noticed when the core clogs is that the PVA turns from a more translucent white color to a more opaque yellow and sometimes even brown color, clogging the nozzle and turning the PVA into an almost sandy grit. So I decided to look into the chemical properties of PVA and to my surprise I found that partially hydrolysed (reacted with water from the air) PVA will begin pyrolysis (chemical decomposition from high temperatures) at temperatures above 200 C and the UM3 default setting print temperature for PVA is 215 C. Since it would be a hassle to try to constantly keep the PVA dry even during printing I simply lowered the print temperature and have had pretty good luck with 205 C print temperature. There doesn’t seem to be any indication of under extrusion and the filament flows better and creates cleaner lines. According to the TDS for UM PVA filament it actually has a melting temperature of just 163 C but I think extrusion issues may result from temperatures lower than 195 C especially with higher print speeds.
  37. 1 point
    I have created a PR (https://github.com/Ultimaker/Cura/pull/6580) to bring back this feature. We'll see if the Cura devs review and merge it for the 4.4 release.
  38. 1 point
    Bon, ça c'est mon levier de vitesse en Ninjaflex semi flex 3mm en cour d'impression sur UM2 avec QR feederBondtech... Non seulement ça n'a pas été trop dur à imprimer, Mais en plus la pièce est en place dans une décapotable en zone tropicale depuis 1 an et demi et 8000 km...et ça ne bouge pas... (Pour ceux qui ont Facebook)
  39. 1 point
    Nous avons pu faire des tests, donc je viens donner la réponse à ma question. Le PLA, le PETG et l'ABS ont tous les 3 fait l'affaire. ils n'ont pas bougé et ont résisté les dizaines de minute de l'expérience.
  40. 1 point
    Hello @SandervG, The UMS3 was the printer I've been waiting for, but came a bit late as I purchased an UM3 a few months ago. The one feature missing on the UM3 is the filament flow sensor, and this has cost me already quite some filament on long (2 day +) prints, with the filament jamming and as a result of that being ground away without the printer knowing it has stopped feeding plastic. After some research on the forums I found that there was a project for the UM2+ with a filament flow sensor working quite nice. I also read that the initial intend was to include a filament flow sensor in the UM3 but is was scrapped during development because the results were not reliable enough. Now, a few years later both the S5 and S3 have a working filament flow sensor and I figure that the code and reliability are now up to Ultimaker’s standards So this got me wondering, since the intent was to include the sensor in the UM3, there is space for the sensor wheel, the PCB and the wiring. So does the UM3 firmware and main board have the possibility for the implementation of a filament flow sensor, and what would be necessary to do so, or is it possible to pause the print externally with a third party sensor, or just a rotary encoder (for example via an I/O input). Also now that the sensors are implemented in both the S5 and S3, the firmware for this sensor should be pretty optimized by now, but the firmware for the S5 is not yet open source (I might be wrong? couldn't find it on github), so implementing this in the UM3 firmware shouldn’t be that difficult. The only issue would be the signing of the firmware before uploading. Since I have a background in electrical engineering and writing firmware/software, implementing a filament flow sensor in the UM3 looks like a fun thing to do and I guess that there are plenty of people who would love to tinker with a flow sensor in their Ultimaker. So when/where can I find the firmware for the filament flow sensor and would it be possible to (co-)develop this into a product? With kind regards, Theodor
  41. 1 point
    Took me forever to do this. And it is still rougher than I would have liked. 3D concept rendering: Finished piece:
  42. 1 point
    Right clic on the model and select multiply You can have a number of duplication in this operation
  43. 1 point
    Problem was that dilithium was very difficult with legislation, being an accidental space-time warp risk. So we removed that feature last second.
  44. 1 point
    Doesn't seem available right now but I found it here on YouMagine: https://www.youmagine.com/designs/gyro-the-dodo-ultimaker-special
  45. 1 point
  46. 1 point
    My experience is the same. Last night my printer jammed completely. See out of focus pic: Had to take the whole thing apart. After cleaning out the feeder and the printcore I tried again but kept jamming. Increased tension all the way and still jammed. Then I realised how soft the filament felt and realised it must be from moisture, lots of rain and misty days lately. Will try dry it out on a heating pad as suggested and the dry box seems like a good idea going forward. This is my first time using PVA so did not realise it was going to be this susceptible to moisture but it makes total sense. Don't forget to bring your tension back to default (the middle) before you start another print!
  47. 1 point
    Tu fermes CURA Dans "C:\Program Files\Cura 2.7\resources\variants" tu as les fichiers correspondant aux buses. Tu cherches le fichier "ultimaker2_0.25.inst.cfg" qui correspond à une buse de 0.25 sur une UM2 (le fichier est différent pour une UM2+) Tu en fais une copie que tu renommes en "ultimaker2_0.15.inst.cfg" Tu édites le fichier pour le faire correspondre à ça : ******************************************* [general] name = 0.15 mm version = 2 definition = ultimaker2 [metadata] author = Ultimaker type = variant setting_version = 2 [values] machine_nozzle_size = 0.15 machine_nozzle_tip_outer_diameter = 0.6 ******************************************* je ne suis pas certain de la valeur suivante : machine_nozzle_tip_outer_diameter = 0.6 C'est à tester. Tu lances CURA et tu pourras choisir une buse de 0.15 dans "Nozzle". Avec ce fichier, CURA calcul automatiquement ses paramètres...
  48. 1 point

    Version 1.0


    Erik's 3MF Hairy Lion Print. Printed With Colorfabb which i found needs the standby temp reduced a bit.
  49. 1 point
    Kin, It's all about the indents. If they are not perfectly aligned, the Python interpreter just tosses out the whole script. The last return at the bottom of you script is not perfectly indented from the def execute subroutine declaration. If NotePad++ has an 'Untabify' function (remove tabs and replace with spaces), use that after aligning the 'return' statement. Otherwise, might I suggest Kimodo Edit from ActiveState. It's free, easy to use and understands a lot of different programming languages (including Python). And it has a function under the 'Code' menu to 'Untabify Region' (which basically removed tabs and replaces with spaces all the lines you have highlighted). That's is how I got you script to load and show up in Cura. Hope this helps.
  50. 1 point
    Even on interior layers, combing as implemented in Cura is a bad idea, as it doesn't perform retraction, and that can result in the head oozing as it moves, especially as each time the head crosses a line of infill it can tend to pull our some plastic. You can also get some long moves (e.g., all the way around the curve of a 'C' shaped object when moving from one side of the opening to the other). This can result in the head being empty when it starts printing the perimeter again, with resultant under-extrusion effects. While the 'not crossing boundaries' effect is a good thing, in principle, the 'not retracting' is a bad thing. For that reason, I never ever enable combing on the UM2.
This leaderboard is set to Amsterdam/GMT+01:00
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!