Jump to content
Ultimaker Community of 3D Printing Experts

Search the Community

Showing results for tags 'Bug'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type

3D printing forums

  • General
    • Official news
    • Ultimaker.com feedback
  • Ultimaker products
    • Ultimaker 3D printers
    • Ultimaker Software
    • Ultimaker Marketplace
    • Third party products & modifications
  • 3D print Questions
    • Improve your 3D prints
    • Design for Additive Manufacturing
    • Industries
  • Ultimaker Academy e-learning
    • General questions e-learning
    • Courses & learning plans
    • Request a course
  • User Lounge
    • What have you made
    • Coffee corner
    • Buying or selling your Ultimaker
  • Languages
    • Nederlands
    • Deutsch
    • Español
    • Français
    • Italiano
    • Japanese - 日本語
    • Other Languages

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



3D printer

About Me



On The Web

  1. Hi there! I have a problem with my Ultimaker 2+ Connect, the heatbed is not heating up consistently anymore. With the latest version of Cura and all defaults active I created a slice of a model using Ultimaker PLA White as the material. As the gcode flavour Griffin is used (per default), but also when using Marlin or adding bed heating gcode manually, the same problem occurs. I am using a bed temperature of 60 degrees. When I load the UFP file in the printer and start the printing process, I feel the bed and sometimes it heats up, but most of the time it does not and stays at room temperature or only a tiny bit higher. Then the nozzle starts heating and after the nozzle is heated up, the print starts but with a too cold bed. I have taken out the bed completely, unclamped the cables from the mainboard and tested the cables for breakage (using a multimeter) and are well and the soldering is perfect too. The PT100 also shows resistance in the 100 Ohms range, so that is working fine. I reconnected the cables, started the print again and it was still not working. I did a factory reset multiple times, even change material to Generic PLA, always made sure that the material configured in the printer settings matches the UFP config, I reinstalled the latest 1.5 firmware, but still nothing. Only thing I can think of is that the bed heating wires are broken somehow and it does not heatup anymore, or there is a failure on the mainboard, but I am lost. I dont have a 24V/7.5A battery or adapter, so I cant test it manually. Does anyone have any clues for me what I can try out? It is also quite annoying that you cant heatup the bed from the menu or see the temperature. Thanks in advance, before buying a new bed I want to be sure that the bed is broken of course. UPDATE: The bed was heating up again once and it hung in the cooldown phase (the cooldown menu would not go away). That means the heatbed is fine but there must be a problem on the mainboard maybe? This is so annoying, not being to able to diagnose the error and the diagnostic logging does not give any errors. UPDATE 2: After switching the machine off and on again (as it did want to print anymore after the cooldown hung) and starting the print again, the cooldown was again skipped and the machine started printing on a cold bed. Same print file that did heat up the first time. I really dont know what is wrong here. This printer is only 8 months old and I printed very little. I also see the LEDs flickering a bit sometimes, but not turning off, as if there is a power problem or something. I already checked all cables and there is nothing loose. All ideas how to diagnose my problem are very welcome!!! I really hope someone can help me …
  2. For some reason, my Ultimaker 2+ Connect starts to spit out some material before it starts the priming process (the little priming blob). So a strand of about 10 cm (sometimes even 20 cm) comes out and then the printer starts the priming. This is terribly annoying, as I need to manually remove that material before the blob. Is this normal behaviour, or does it have to do with some kind of over-pressure in the nozzle that makes it push out some material? Sometimes it doesn't happen, but most of the time it does unfortunately.
  3. I had this problem shortly after loading up 4.13, and now it is affecting ALL versions of Cura. I can't use any of them, no matter how often I do a clean install the issue is this: If i attempt to do any sort of modification of my settings, the program will not launch next load. i never see the UI, just straight to not-responding when loading the build volume. if i attempt to save the profile? not responding. any subsequent program runs? not responding. deleting the Local and roaming Cura folders helps, but again... not responding after the first run. if i take too long to slice the model? not responding. Right click? not responding. at this point i have clean-installed and set up my printer about a dozen times just trying to get a single file to print. it's a race against time before cura tries to save the profile and necessitates a total reset. i tried going back to 4.12.1 after the issue, but the issue is now following me back through versions. I've also tried running as admin, with no success. it is however more stable, and i can slice something... but it pretty quickly falls back into the same loop of not responding. usually after trying to save my settings i've updated the OS, and both SCF /scannow and the DISM repair commands are coming back clean. i've deleted the local and roaming Cura folders I've even gone so far as to delete all the cura instances out of Program files after uninstalling. it is still happening. i am really at my wits end here because i have no idea what the application might be doing that's causing this crash. edit: now it's any menu item. i can't even click 'file'. cura.log stderr.log
  4. Below is my startcode Yet when slicing my startcode looks like There's a redudant M140, an M105 and an M190 where they shouldn't be. As is visbile in screenshot 1 (i maxed out the manage printers view so everything was visible, evidence of this is the lack of a scrollbar) those 3 startcodes DO NOT exist in my configured startcode. These lines cause additional delay as it waits for the bed to heat up first to full temp before starting to pre-heat the nozzle. I have no idea where this is coming from 4.11.zip
  5. Hi all. New to 3D printing and trying to add Octoprint to Cura. I have followed the steps and added the Octoprint plug in. It states it is added and after shutting Cura and restarting it I go as suggested to the manage printer and select my my printer but there is only option to Update Firmware or Machine settings. No option for Octo print. How can I link it. Many thanks. Mike.
  6. Hello Everyone, I have ultimaker 3 Ext that I have been using since last 4 years for my R&D work. I use it only 3-4 times in a month. So its relatively new machine only. Since last two weeks I am struggling to print an important part.. The moment I print, the printer restarts after about 4-5 sec. The movement is seized immediately.. I have tried to heat the build plate & that works fine .. I have run switching test diagnostics & that runs fine.. However, when I tried to run active levelling it does give the same problem & restarts in about 4-5 secs.. Can anyone please advise some solution ? Thanks you very much
  7. Cura 4.13 Possible bug found: Cura thinks a model has a bottom where none actually exists. Attempting to print a 134mm ring-shaped object (image below)--the ring is open. Brim is enabled under Build Plate Adhesion (BPA). Model imported into Cura as either OBJ and STL. Before slicing, Cura shades area on the virtual build-plate that fills the ring--this is non-representative of actual BPA setting. Additionally, Cura does not display shade area to represent a brim along the outside of the ring (see image below). Instead, Cura shades around the perimeter of the build plate. Why. After slicing, Cura displays the area inside the ring in yellow (as shown in the image below). Yellow represents top/bottom, yet this object has no material where Cura shows yellow. My printer subsequently prints material into this area (along with a brim) that is thicker than a brim but thinner than a raft. Why. What setting might be causing Cura to override the BPA setting and think this model has material where none exists? Or, is this a bug.
  8. I'm working on some parts with both large, low complexity areas and small, detailed areas, so I've been working with the Small Feature Speed setting to help me get the right speeds in both parts of the model. It's been generally working well, but I noticed today as I was previewing a part in the speed view mode, that the part infill is not respecting the small feature speed. In other words, even though the area of infill falls well within the Small Hole Max Size setting I gave it, the infill prints at the normal infill speed and is not reduced by the Small Feature Speed setting. Similarly, the support is entirely unaffected by the Small Feature Speed setting, both in the walls/infill, as well as the interface layers. Since I'm making a big part that is mostly low complexity, I really need to use large nozzles, and that makes it even more important to get the speed down on the tiny features so that it has a chance of printing well. I realize this is an experimental setting, so not fully supported, but I've come to depend on it and I'd love to have it fully functional. Is this exclusion of the infill and support from that setting a deliberate choice or a bug in the experimental setting? Thanks!
  9. Hi I just installed Cura 4.13 and I am trying to slice a mini but the tree supports are being placed through the models legs, I have changed a few support settings around but it doesnt seem to change the issue. please let me know if its a print settings issue or a problem with the slicer. the same model with the same print settings worked before I installed 4.13. I have attached a pic showing the issue. I am using tree supports as they are easier to remove from the model than other supports.
  10. I have been using Cura for over a year and this is the first time I've experienced this type of behavior in the slicer. I could be something I'm doing but it goes away if I print it in a different orientation. I thought it may have something to do with support but it happens even when I turn the support off. The angle starts at layer 119 and adds extra material in the vertical slot. Any Ideas? TWOTSP_Test Piece.3mf TWOTSP_Test Piece.gcode Test Piece.stl
  11. I change out one of the print cores from a BB 0.4 mm to a AA 0.4 and it recognizes it as a BB core. Any ideas on how to solve this problem`?
  12. I like to use "One at a Time" print sequence, when printing multiple objects in the same job. It reduces travel time and avoids "hairs" spanning between parts. There are a few issues. CURA does not automatically figure out where to place objects to avoid the gantry toppling them over. It only works if the objects are less than the gantry height. My usual workaround is to temporarily lie about the gantry height and then manually place the objects to avoid the gantry. This should be a simple thing for CURA to figure out, at least in the case of exactly two parts -- just place one part toward the front and the other part toward the back with a gantry-width amount of space between the parts (which is what I do manually). Likely an RFE here that the printer definition needs to capture the X/Y size of the gantry and/or print-head, not just the gantry Z-height. CURA 4.x blocks the use of "One at a Time" if extruder count is >1. I can't see the reason for this. I used to use "One at a Time" with great success with two extruders in CURA 3.x (caveat being #1 above). This restrictions means I can't print two color parts, nor can I print a bunch of different one-color parts, from two different extruders. I got a new IDEX printer and the two extruders are mounted on the front of the gantry, quite some distance forward. This leads to a preference to print parts at the front of bed first, then at the rear. I don't see a way to specify the print-order for the objects. My workaround is to see what CURA intends to do, then swap the parts if necessary. Any solutions to the above? Bugs / RFE's already documented somewhere?
  13. Hi, I am new to 3D printing. Originally, I was using the Creality Slicer software that came with the Ender 3 Pro that I got, but for some reason it wasn't generating a gcode when I would try to slice something. As a result, I recently downloaded Cura. I have sliced several models and printed them no problem (though I did notice the slicing was a lot slower than the other software - previously slicing took a few seconds, now on Cura its taking a few minutes). This morning I tried to slice a model with the exact same setting as the last thing I printed, and now the slicer isn't moving past `30%. Layer height is 0.2mm and all the other setting looked fine. How can I fix this? Or how can I speed up the slicing process? Ideally I'd like to be back at the few seconds to slice.
  14. Using 4.13, slicing a large object, I get tree supports outside the size of the bed and on top of unprintable areas. I have not seen this in older versions. Bug?
  15. Добрый день при добавлении других принтеров в них можно выбрать материал и затраты на печать при печати. На данной модели представлены различные возможности выбора материала, а также добавление нового в то время как на Tevo Black window нет выбора все заблокированно. Прошу решить проблему скрины пришли. А других моделей принтеров все в порядке. Как решить проблему?
  16. Using Cura 4.12 on my MBP 16" late 2019 model, Line Type Preview is really unusable, due to extraneous vectors blocking my ability to see what it is I'm trying to preview, such as travels and different line types for extruder 1 vs. extruder 2. Is there some setting I can tweak to bias the graphics capability to be more compatible? I already tried "Force layer view compatibility mode" but that is so dumbed down I that I cannot see the extruder 1 vs. extruder 2 lines. 😞 Example:
  17. Cura 4.13 crashes on me. Running on Macbook Pro 13-inch Mid 2014 Mac OS Big Sur 11.16.2 ERROR TRACEBACK: Traceback (most recent call last): File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/site-packages/keyring/backends/macOS/__init__.py", line 49, in get_password File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/site-packages/keyring/backends/macOS/api.py", line 101, in find_generic_password File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/site-packages/keyring/backends/macOS/api.py", line 43, in raise_for_status keyring.backends.macOS.api.SecAuthFailure: (-25293, 'Security Auth Failure: make sure python is signed with codesign util') During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/site-packages/cx_Freeze/initscripts/__startup__.py", line 74, in run File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/site-packages/cx_Freeze/initscripts/Console.py", line 36, in run File "/Users/ultimaker/build/Cura/4.13/build/inst/bin/cura_app.py", line 236, in <module> File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/cura/CuraApplication.py", line 844, in run File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/cura/API/__init__.py", line 54, in initialize File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/cura/API/Account.py", line 118, in initialize File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/cura/OAuth2/AuthorizationService.py", line 282, in loadAuthDataFromPreferences File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/cura/OAuth2/AuthorizationService.py", line 98, in getUserProfile File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/cura/OAuth2/AuthorizationService.py", line 107, in _parseJWT File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/cura/OAuth2/KeyringAttribute.py", line 42, in __get__ File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/site-packages/keyring/core.py", line 55, in get_password File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/site-packages/keyring/backends/macOS/__init__.py", line 55, in get_password keyring.errors.KeyringError: Can't get password from keychain: (-25293, 'Security Auth Failure: make sure python is signed with codesign util') LOGS: Thread 0x000070000dde6000 (most recent call first): File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/UM/Backend/Backend.py", line 165 in _storeStderrToLogThread File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 870 in run File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 932 in _bootstrap_inner File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 890 in _bootstrap Thread 0x000070000cde3000 (most recent call first): File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/UM/Backend/Backend.py", line 153 in _storeOutputToLogThread File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 870 in run File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 932 in _bootstrap_inner File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 890 in _bootstrap Thread 0x000070000b9c8000 (most recent call first): File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 302 in wait File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 433 in acquire File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/UM/JobQueue.py", line 98 in _nextJob File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/UM/JobQueue.py", line 124 in run File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 932 in _bootstrap_inner File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 890 in _bootstrap Thread 0x000070000a9c5000 (most recent call first): File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 302 in wait File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 433 in acquire File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/UM/JobQueue.py", line 98 in _nextJob File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/UM/JobQueue.py", line 124 in run File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 932 in _bootstrap_inner File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 890 in _bootstrap Thread 0x00007000099c2000 (most recent call first): File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 302 in wait File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 433 in acquire File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/UM/JobQueue.py", line 98 in _nextJob File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/UM/JobQueue.py", line 124 in run File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 932 in _bootstrap_inner File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 890 in _bootstrap Thread 0x00007000089bf000 (most recent call first): File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 302 in wait File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 433 in acquire File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/UM/JobQueue.py", line 98 in _nextJob File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/UM/JobQueue.py", line 124 in run File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 932 in _bootstrap_inner File "/Users/ultimaker/build/env/4.13/install/lib/python3.8/threading.py", line 890 in _bootstrap Current thread 0x0000000110c5ee00 (most recent call first): File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/cura/CrashHandler.py", line 398 in _logInfoWidget File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/cura/CrashHandler.py", line 184 in _createDialog File "/Users/ultimaker/build/Cura/4.13/build/inst/lib/python3.8/site-packages/cura/CrashHandler.py", line 88 in __init__ File "/Users/ultimaker/build/Cura/4.13/build/inst/bin/cura_app.py", line 162 in exceptHook 4.13.zip
  18. Please i need some help to understand whats going on. Today my printer started some print jobs that I did not sent to...its even more strange because the stl's sent to her i don't even recognize them...never worked on those print models dont even ever saw then...what's going on?? Some kind of poltergeist?? Many thanks! Primeiro
  19. The program clearly has compatibility issues with AMD graphics cards. I myself have an AMD RX580. Cura slicer crashes every time immediately after launching without any error message. All the drivers on my computer are up to date. All possible solutions to fix the problem have been tried.. I have already made several error reports about this. This has been going on for one full year. I haven't got responded to any error reports. Not from ultimaker or AMD. I think it would be great if you could catch your balls and fix the problem. Thank you.
  20. Multiplicated objects with custom support-blockers do not appear as exact copy - instead all support-blockers are ADDED as extra material, e.g. elevating the base layer in copied object, instead of being an exact copy (check the below picture - left: original, right: multiplied one) Plus: 7.6MB project file loads way too long (like a 700MB one). Anyone experienced such behaviour?
  21. Hi, We've been having this issue with one of our Ultimaker S3 during leveling where the printer senses the nozzle offset to be off. What happens (also seen in the video): -nozzle (clean) of print core 2 touches the glass bed (clean), as normal -Print core 2 gets lifted by the lift switch, as normal -nozzle (clean) of print core 1 slowly lowers to detect de glass bed, as normal -before even touching the build plate the leveling stops with the error "Nozzle offset failed. Please check the nozzle and bed and try again" This error most of the time a print is launched but not everytime. I would say we get the error 2 times every 3 print launch. when it fails we usually simply relaunch the print a couple of times until it it levels correctly. Ultimaker S3 Error.zip
  22. Hello, I have a weird bug occurring when printing with dual extrusion. I will describe the circumstances: I'm printing parts combined out of Ultimaker Nylon (Print Core 1) and Ultimaker TPU 95A (Print Core 2). The parts come out nicely, but when the print is finished, the Nylon always gets stuck in the print core. The core even gets pulled back into the print head. Then the wizard for stuck material appears. When i follow the instructions, print core 1 gets heated up again and clicks back down hard when the Nylon is hot enough. (It seems to be free at this point) I still have to remove the bowden tube and cut the material to finish the wizard. Then it gets unloaded. As if that wasn't enough, after finishing the process, the print bed violently falls down without much resistance from the Z-steppers. Long story short: I think the printers workflow when unloading the material has a bug. After printing the last layer with TPU, print core 1 doesn't heat up again and therefore fails to unload the Nylon properly. I would appreciate some help - maybe i'm doing something wrong. If not, maybe this could be looked over for future bug fixes. Thanks in advance.
  23. Since i upgraded from cura 4.12 to 4.13 i've been experiencing my prints stopping in the middle. No clogs, no jams, no issues with filament passing through. I've researched and saw that it may be the SD card and when i've switched SD card i still get a print that stops midway. When i look at my print information screen the file name disappears. I cannot resume or continue at this point and the only thing i can do is shut my printer off and start over. I'm on a back 2017 monteray 12.1 printer is anycubic chiron just recently purchased (all belts and nozzle housing is tight/taught as it should be, gears are solid feeding extruder) generic black PLA 200c nozzle and 60c bed (had it stop mid print) silk gold PLA by giantarm 200-205c nozzle/ 60-70c bed (stops midprint) i'm at a loss and when researching troubleshoots every one talks about jams and clogged nozzles but i've looked this over multiple times and no issues with extruder or filament coming through. any help is greatly appreciated.
  24. Have been having the same issue where cura 4.12 just gets stuck on slicing. couple days ago i fixed it by completely reinstalling cura, including the files in local and roaming. But now that did not do anything anymore. If i look at the logs it looks like it finishes slicing but my program just keeps showing the same slicing... message. am slicing for an ender 3V2 but it doesnt slice anymore on anything now. the model that might have caused this is attached. its a modified bendy rex. Windows 10, very new hardware(if specifics are needed let me know). cura.log Flexi-Rex-improved-Flexi-Rex-tweaked_1.stl
  25. The mandatory cooldown time forcing the bed to drop below 60C is really quite frustrating when trying to print higher temp materials which require enclosures and higher ambient temperatures. When I'm printing ABS with a 100C build plate I really need to let it warm for like 30-60 minutes to ensure that the ambient temp in the printer is high enough that I don't get warping and layer splitting. If I have a failed print due to something like I just did where the autolevel decided to ram my nozzle very far into the build plate at one spot I basically loose 2hrs of print time as I need to let the thing fully cool down. I then need to let it fully warm up and get the air back to the required 35C ambient before I can tell it my print has been removed and then restart my print. I get this is a safety feature to prevent people from trying to rip prints off a hot glass bed and either damage themselves or the printer but there needs to be an advanced options menu to skip this for these kind of scenarios. The skip cooldown option that comes up doesn't seem to do anything here when it isn't greyed out. I am missing something basic or is there a way to disable or change this safe cooldown temp with a variable or something? At this point I'm basically taking files home from my lab and printing them on my home printer (a Voron 2.4) as it does ABS better than this one. Users at some of our other sites ask me if they should replace their Prusa MK3s with S5s and honestly I'm having a hard time saying yes. At face value this printer will handle these higher temp materials better and hardware wise it's superior but then the limitations int he firmware for stuff like this make it very hard to recommend.
  • Create New...