Jump to content

All Activity

This stream auto-updates     

  1. Past hour
  2. Today
  3. Had my UM3 for 6 weeks or so, and it was fine until leveling went wrong about 2 weeks ago, and once it went wrong, it went all the way. - I had autolevel set to always, - After the firmware patch my print success started feeling inconsistent, - I'd added UHU to a print where the most important layer had to be printed on the bed and raft/brim messed with it, - Adhesion had gotten worse and UM3 provides a painful, slow, experimentation cycle, so I'd flipped the bed over unaware that the two sides are different, - A large build of Colorfabb nGen had slipped and covered the printheads in ngen residue, forcing me to open the print head to get the cores out, - After reassembly not even my unaffected print cores (bb .4 and aa .25) could level, - Printing the X/Y calibration was impossible because the head was either too close or was dragging drips/strands/the print into the print and turning to mush, - The manual leveling process is an awful user experience. You should grandmother it (get family members of staff to come in and attempt to correctly manually level a printer: I challenge you), how much "some resistance" is turns out to be absolutely criticial, - During the fight between manual and autolevel I think I over loosed some of the screws, - The turn around time on making leveling adjustments to finding out whether you are within +/-0.05mm of correct extrusion is INSANE, - It took me about 5 attempts after the buildtak addition to piece together what was going on. a) I thought I'd turned off auto-leveling but it was back on - maybe I had done that thing where pressing the wheel counts as turning the wheel too, b) I was feeling for "resistance" as in a sense that the card was being dragged at rather than aiming for the barest hint that the card wasn't utterly free to move, c) The card isn't perfectly flat, and its hard to get it to be flat, d) auto-levelling can't handle buildtak, and it definitely can't handle flex plate, e) in my case, the calibration card was too thin, a 0.35mm piece of card that came with the shipping of something worked a lot better, What I don't get is why this problem isn't generally solved in 3d printing using a simple obstruction sensor? Hang an emitter and a receiver from the same axis the print core is from until you sense the bed interrupting the bottom of the receiver? The sensors/emitters can probably be bought off the shelf and you just send the output to the extant board, with the mounting parts, probably sell for $50-150, and voila customers have a way to obtain factory-fresh perfect auto leveling in a single pass. Or for $250-$350 you could put strips along the sides of the bed up by the home position: in a single scan you can do both leveling and obstruction checking -- you can confirm that nothing is in the way of the current layer and, at the end of the layer, after moving the head, that the print hasn't failed to adhere. You could even check for droop, etc, by checking that end-of-layer occlusion matches expectations...
  4. Hello. I increased by 205% on the z axis. And at the time of printing, the impression is always defective as I show in the image. How can I solve this problem??
  5. Then it was exactly the problem I was talking about. When you model something in Fusion you get often a new body instead of joining the existing one. It is not a problem, but you should be aware of it and that the export function only exports one body (you can also not select more than one). So when you have more than body in Fusion, you should combine it before sending it to Cura. You find the combine function in the Modify menu in Fusion.
  6. That's a problem, but the other is that the FW obviously does not take into account which material is loaded - it makes no sense to advance ABS and nylon 6 mm and print at a fixed temperature of 190 degrees (Core 1) or 220 degrees (Core 2) - that does not go through the nozzle ...! Deadline only because much too cold. It was not an Ultimaker material now, but I loaded it with the load command and specified the material type there - so I suspect that's the problem in general. The way I see it, you have to calibrate PLA each time - whether you have it there or not ... If only the question were what I have to state it for - just to load? I can do that manually too ... with regards, Digibike
  7. The problem with the XY calibration is that it's not un-/retracting. Cura's default setting is to do exactly this. So that's why the filament is too far away from the nozzle. Anyway, the XY calibration is actually a gcode that is stored in the firmware. It assumes the scenario that the printcore is ready to be used. So what Ultimaker needs to do (or you if you know how to hack your printer) is to add the instruction for the printer in this gcode to do the un-/retraction. That should be it if I'm not wrong.
  8. Well said. Shame on you Ultimaker!!! Your leaving us all hang out to dry 😞
  9. I tried running x_pack's posts through Google translate, but there was no option to convert from selfishandentitledgibberish.
  10. Thank you so much! It was very helpful! Best regards
  11. They are M3 screws (3mm - standard thread). With "socket cap" screw heads (although any head type should work). You can indeed measure the length and get similar ones (threading will probably run the length but that's fine).
  12. First, im a brand new user here and for some reason, the product category for software is greyed out so i had to choose 3d printer for the category Ok, here is my question. I am using cura 4.0 and i have set up my printer, made my first part, and all went well. I have now started to mess with the print settings such as temp, speeds, and other basic settings. I save the file as a gcode file. I transfer to SD card, i print it and during the print, i forget how long it will take to print and i want to look at some of the other settings so i can write them down. I open the gcode file in cura4.0 and it loads the 3d image, but says i cant view the settings i had for it. How does one view the original print settings and see how long it will take to print? thanks
  13. Major stringing is occurring with all U3 prints on Cura. Tried various settings to no avail. Any ideas?
  14. Just to clarify myself; the showed code without G92, was before I re-installed Cura. I will test it again and show the results.
  15. But there needs to be *another* G92 when it goes from extruder at 4 meters back to zero meters - well into the file. You had E4158 and then suddenly it goes back to E0.04 There needs to be another G92 E0 between those. Otherwise it will retract the 4.158 meters of filament just as you described.
  16. Oh I just saw that there is Cura 4.0, thank you very much, I will try with the new one and update if the problems still occur
  17. Nope, it's all standard. What I've just done, was do a clean install of Cura 4. Now I can see the G92 codes that are needed, are indeed there. I also noticed that saving a file after slicing is done in seconds, where before it was minutes. So I guess that somewhere in the upgrade from 3.6.0 to 4.0.0, something went wrong. And despite having this in my start G-code: G1 Z15.0 F{travel_speed} ;move the platform down 15mm G92 E0 ;zero the extruded length G1 F200 E3 ;extrude 3mm of feed stock G92 E0 ;zero the extruded length again G1 F{travel_speed} M117 Printing... The generated code was this: G1 X0 Y0 Z15 ;zero the extruded length G1 F200 E3 ;zero the extruded length again G1 E0 M117 Printing... And I didn't notice that G92 was missing. I would say your answer pointed right to the problem, and re-installing solved it. Thanks a lot!
  18. I'm also experiencing it, but i'm not sure if I had this behaviour before the update or not. My UM3 is pretty new (received it mid of March 2019) and as the firmware was updated almost immediatly, I don't really know if it's specific to the new firmware or CURA 4. Anyway, i'm also experiencing this blob being carried out by the nozzle, especially for the PVA on printcore 2. Even when not rolling it's little ball, the nozzle gets full of plastic and the outside of it is soon carbonize, also this does not at first glance adversly impact the prints (when the blob doed not get stuck in the middle of the print, but now i'm quite trained to quicky pick it up in the first minutes of the print.) For sure the issues i'm having with the new firmware + cura 4 are : - XY calibration not working (I've been reading about the ugly manual push fix...) - automatic levelling not working, when activated, the nozzle almost scratch the glass and there is no extrusion possible. I've been factory resetting the UM3 but same behaviours... I've seen the instruction to rollback to 4.3.3 but I don't want to open the machine... I really hope that Ultimaker will solve this mess quickly, it's been out for more than a month now. ETA / progress bar updates (you know those smart UI/UX widgets that keeps users to wait patiently in front of their computers during long task runs) for the next "hotfix" would really be welcome... regards
  19. Has anyone experienced the blob extrusion issue? Since the update? Goes to print the Blob, after a short extrude Z moves down, extrudes some more. Z raises into print head, Print head moves to start of print position dragging some/if not all of the blob with it. Initially i wiped the nozzle to remove the blob. At the time i was just happy my printer was alive after updating🤦‍♂️ Is there any update from UM on when the fixes will be released? how long has it been now? The reason this isnt even bigger for UM is that not everyone has upgraded. (my work 5+ machines, some of my mates 3+ machines etc to name people i know) But when those users start to update the small trickle of issues will get bigger and bigger. (look how many UM users have just signed up with 1 post to complain!) Like many other people on here I'm really disappointed. I would expect this from a cheap Chinese manufacture but not from UM. I feel like I've fallen for the marketing (as per usual). Really not impressed and wont be recommending forward.
  20. Interesting. The 5.2 thread issues never end. Mine is slightly different to yours in the video. mine goes to extrude the blob, Then the Bed drops for more extrusion. -Great. However when its finished... the z goes UP to the print core, and forces the blob into the nozel then drags the blob across the plate, Being covered in plastic it then goes to start printing and every print is ruined. Not going to be so eager to update my firmware in future thats for sure!
  21. Je pense que tu peux éditer le GCODE avant d'envoyer l'impression pour retirer la ligne de calibration.
  22. Est-ce que tu es sûr de bien être en unité métriques ?
  23. Okay so the problem is in the gcode, not the printer. Something is quite wrong there. Marlin runs on an arduino which is VERY limited and there are many efficiency improvements that can be a problem. One of them is that the extruder position is stored in a floating point number that only has so many significant digits so every few meters, cura resets the extruder back to zero, but should have also included a G92 command to let Marlin know. As in: G92 E0 I can see the extruder was up to 4.1 meters so it makes sense that it would go back to zero around this point but the "G92 E0" is missing. Do you have a plugin that removes all G92 commands maybe? Or did you do some kind of hand edit and remove all G92 commands?
  24. i have this same problem recently. did you find a solution?
  25. Is there a reason you are still using 3.6? Would suggest retrying with 4.0 and see whether it still occurs. Personally, I doubt that you will still get support for 3.6. Even if someone finds a bug in this release, there will be never an updated version of it, e.g. version 3.6.1. It is normally not intended by Ultimaker to release bugfixes for older versions.
  26. I found out another thing, when I examined the gcode again. I know for that the last time the extruder reversed, the Z position was at 28. At that height, I saw that I have a blank line in my code, and nowhere else (except for the header). In the same block, the extruder value drops from 4158 to 0.04. Is this an error, or not? Here is the piece of code: ;LAYER:278 ;MESH:MotorConnector5.stl G0 X117.716 Y134.017 Z28 ;TYPE:WALL-INNER G1 F2400 X117.535 Y133.977 E4155.08934 G1 X115.269 Y133.493 E4155.11703 G1 X115.269 Y75.746 E4155.83718 G1 X117.816 Y75.746 E4155.86645 G1 X117.716 Y133.831 E4156.59087 G1 X117.716 Y133.832 E4156.59088 G1 X117.816 Y134.021 E4156.59229 G0 F7200 X117.916 Y134.206 G1 F2400 X117.916 Y134.207 E4156.59231 G1 X118.038 Y134.294 E4156.59461 G1 X117.857 Y134.254 E4156.59603 G1 X115.069 Y133.734 E4156.63139 G1 X114.969 Y75.545 E4157.35828 G1 X118.016 Y75.445 E4157.39503 G1 X117.916 Y134.206 E4158.12787 G0 F7200 X118.106 Y134.566 ;TYPE:WALL-OUTER G1 F1200 X114.819 Y133.934 E0.04174 G1 X114.719 Y75.294 E0.77424 G1 X118.266 Y75.194 E0.81724 G1 X118.166 Y134.518 E1.55708 G1 X118.166 Y134.519 E1.55709 G1 X118.288 Y134.607 E1.55941 G1 X118.106 Y134.566 E1.56083 G0 F7200 X117.911 Y134.523 G0 X117.962 Y134.3 G0 X117.777 Y134.032
  1. Load more activity
  • 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!