Jump to content
Ultimaker Community of 3D Printing Experts

Search the Community

Showing results for tags 'Question'.

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


3D printer


About Me


Country


Industry


On The Web

  1. Good day, Yesterday I tried having installed both aforementioned cores on UMS5. However, print settings displayed were for AA25mm. Hence the question: Can I have both cores installed and have a choice which one to use? For instance, I wanted to have a quick print/draft, AA25 was installed in slot 1. I figured, instead of unloading the material, removing AA25mm, installing AA40mm core and loading material back in, I'd just install AA40mm into slot 2 and "mark" that for the print! But no, settings for printing were for AA25mm. Please advice!
  2. I just got a new Ender 3 V2. I am trying to do a filament change mid print in Cura. For some reason, after I go through adding the script and re-slicing, nothing gets added to the generated GCODE. If I do the same thing with the "pause at height" script, it gets added properly but it only pauses for a few seconds and then resumes the print before I get a change to change the filament. I can open up the gcode in a text editor and see the added changes. I don't understand why trying to add the "filament change' script doesn't show any gcode changes at all?
  3. The Kodak Portrait comes with a custom version of an old version of Cura. I'm on a Mac, and that app stopped working on my first OS update. The makers of the printer have no plan that I see to update their version, so I'm basically orphaned now. I'm hoping someone here has had some experience getting current versions of Cura working for it. Their support tried to have me set Cura up with their parameters. It did not work.
  4. hi i wondered if anyone could tell me which file contains the code which points cura to machine_instances with the following path C:\Users\USERNAME\AppData\Roaming\Creality Slicer\4.8\machine_instances thanks
  5. Has anybody used any kind of alternative, textured build plate with an Ultimaker printer (like the “Double-sided Textured PEI Powder-coated Spring Steel Sheet” from Prusa)? Not sure if there is something like this for the Ultimakers… The glass plate is fine for most print jobs, but sometimes a slightly textured surface looks better. Thanks for any feedback, -pl
  6. Just updated from windows 7 to 10 on my desktop so I could use cura 4.12 and have never used the market place in the past, but thought I would try it and it wouldn't sync my account when I go to account updates in cura. I tried this on my laptop just to see and it works there but not on my desktop. I have uninstalled all the previous curas and uninstalled/reinstalled 4.12 but nothing changes. Thanks Greg
  7. Unable to use CURA, please help... AttributeError: 'nonetype' object has no attribute 'close' ============================================================================ 屬性錯誤:“nonetype”對像沒有屬性“關閉” 線程 0x00003aec(最近一次調用): 文件“C:\Program Files\Ultimaker Cura 4.11.0\plugins\USBPrinting\USBPrinterOutputDeviceManager.py”,_updateThread 文件“threading.py”中的第 79行,運行 文件“ threading”中的第 870 行 .py”,_bootstrap_inner 文件中的第 932 行 “threading.py”,_bootstrap 中的第 890 行 線程 0x00001860(最近一次調用優先): 文件“threading.py”,等待文件“zeroconf\__init__.py”中的第 306 行,等待 文件“zeroconf\__init__.py”中的第 2534 行,運行 文件“threading.py”中的第 1715 行。 py”,_bootstrap_inner 文件中的第 932 行 “threading.py”,_bootstrap 中的第 890 行 線程 0x00003b8c(最近一次調用優先): 文件“threading.py”,等待文件“threading.py”中的第 306 行,等待 文件“C:\Program Files\Ultimaker Cura 4.11.0\plugins\UM3NetworkPrinting\src中的第 558 行\Network\ZeroConfClient.py”,_handleOnServiceChangedRequests 文件“threading.py”中的第 81 行,運行文件“threading.py”中的第 870 行,_bootstrap_inner 文件“threading.py”中的第 932 行,_bootstrap 中的第 890 行 線程 0x00001b38(最近一次調用優先): 文件“zeroconf\__init__.py”,運行 文件“threading.py”中的第 1369 行,_bootstrap_inner 文件“threading.py”中的第 932 行,_bootstrap 中的第 890 行 線程 0x00000a8c(最近一次調用優先): 文件“C:\Program Files\Ultimaker Cura 4.11.0\plugins\RemovableDriveOutputDevice\RemovableDrivePlugin.py”,_updateThread 文件“threading.py”中的第 61行,運行 文件“ threading”中的第 870 行 .py”,_bootstrap_inner 文件中的第 932 行 “threading.py”,_bootstrap 中的第 890 行 線程 0x00003880(最近一次調用優先): 文件“C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Backend\ Backend.py”,_storeStderrToLogThread 文件“threading.py”中的第 165 行,運行文件“threading.py”中的第 870 行,_bootstrap_inner 文件“threading.py”中的第 932 行,_bootstrap 中的第 890 行 Thread 0x00003c60 (most recent call first): File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Backend\Backend.py", line 153 in _storeOutputToLogThread File "threading.py", line 870 in run File "threading.py", line 932 in _bootstrap_inner File "threading.py", line 890 in _bootstrap Thread 0x00003ad0 (most recent call first): File "threading.py", line 302 in wait File "threading.py", line 433 in acquire File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 98 in _nextJob File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 124 in run File "threading.py", line 932 in _bootstrap_inner File "threading.py", line 890 in _bootstrap Thread 0x00002ca0 (most recent call first): File "threading.py", line 302 in wait File "threading.py", line 433 in acquire File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 98 in _nextJob File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 124 in run File "threading.py", line 932 in _bootstrap_inner File "threading.py", line 890 in _bootstrap Thread 0x000005d8 (most recent call first): File "threading.py", line 302 in wait File "threading.py", line 433 in acquire File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 98 in _nextJob File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 124 in run File "threading.py", line 932 in _bootstrap_inner File "threading.py", line 890 in _bootstrap Thread 0x00003fd8 (most recent call first): File "threading.py", line 302 in wait File "threading.py", line 433 in acquire File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 98 in _nextJob File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 124 in run File "threading.py", line 932 in _bootstrap_inner File "threading.py", line 890 in _bootstrap Thread 0x0000353c (most recent call first): File "threading.py", line 302 in wait File "threading.py", line 433 in acquire File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 98 in _nextJob File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 124 in run File "threading.py", line 932 in _bootstrap_inner File "threading.py", line 890 in _bootstrap Thread 0x000033d8 (most recent call first): File "threading.py", line 302 in wait File "threading.py", line 433 in acquire File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 98 in _nextJob File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 124 in run File "threading.py", line 932 in _bootstrap_inner File "threading.py", line 890 in _bootstrap Thread 0x00002ae0 (most recent call first): File "threading.py", line 302 in wait File "threading.py", line 433 in acquire File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 98 in _nextJob File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 124 in run File "threading.py", line 932 in _bootstrap_inner File "threading.py", line 890 in _bootstrap Thread 0x00003594 (most recent call first): File "threading.py", line 302 in wait File "threading.py", line 433 in acquire File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 98 in _nextJob File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\JobQueue.py", line 124 in run File "threading.py", line 932 in _bootstrap_inner File "threading.py", line 890 in _bootstrap Current thread 0x00002c70 (most recent call first): File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 396 in _logInfoWidget File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 182 in _createDialog File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 86 in __init__ File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\bin\cura_app.py", line 159 in exceptHook File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Math\Polygon.py", line 249 in getConvexHull File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Math\Polygon.py", line 283 in getMinkowskiHull File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\BuildVolume.py", line 924 in _computeDisallowedAreasStatic File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\BuildVolume.py", line 771 in _updateDisallowedAreas File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\BuildVolume.py", line 649 in _onStackChangeTimerFinished File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 452 in _show File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Event.py", line 218 in call File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Qt\QtApplication.py", line 479 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CuraApplication.py", line 1090 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 452 in _show File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Event.py", line 218 in call File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Qt\QtApplication.py", line 479 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CuraApplication.py", line 1090 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 452 in _show File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Event.py", line 218 in call File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Qt\QtApplication.py", line 479 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CuraApplication.py", line 1090 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 452 in _show File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Event.py", line 218 in call File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Qt\QtApplication.py", line 479 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CuraApplication.py", line 1090 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 452 in _show File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Event.py", line 218 in call File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Qt\QtApplication.py", line 479 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CuraApplication.py", line 1090 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 452 in _show File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Event.py", line 218 in call File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Qt\QtApplication.py", line 479 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CuraApplication.py", line 1090 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 452 in _show File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Event.py", line 218 in call File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Qt\QtApplication.py", line 479 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CuraApplication.py", line 1090 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 452 in _show File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Event.py", line 218 in call File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Qt\QtApplication.py", line 479 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CuraApplication.py", line 1090 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 452 in _show File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Event.py", line 218 in call File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Qt\QtApplication.py", line 479 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CuraApplication.py", line 1090 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 452 in _show File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Event.py", line 218 in call File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Qt\QtApplication.py", line 479 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CuraApplication.py", line 1090 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 452 in _show File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Event.py", line 218 in call File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Qt\QtApplication.py", line 479 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CuraApplication.py", line 1090 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 452 in _show File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Event.py", line 218 in call File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Qt\QtApplication.py", line 479 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CuraApplication.py", line 1090 in event File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CrashHandler.py", line 452 in _show File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Event.py", line 218 in call File "C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Qt\QtApplication.py", line 479 in event 文件“C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CuraApplication.py”,事件 文件中的第 1090 行“ C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\UM\Qt\QtApplication.py",exec_File 中的第 393 行 " C:\Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\lib\python3.8\site-packages\cura\CuraApplication.py”,運行 文件中的第 867 行“C: \Users\ultimaker\AppData\Local\Temp\cura-build-4.11-exe\build\inst\bin\cura_app.py”,<module> 文件“Console.py”中的第 233 行,運行 文件“__startup__ ”中的第 36 行.py”,運行中的第 74 行
  8. Hey there, I m wondering if anyone knows what s going on with my printer. Firstly I got my new laptop a few days ago and I download Cura. Before that on the old one it was ok, but now I have a problem. Actually the problem I think it has to do with the slicer cause i had the same problem when i firstly download it on the old one, i fix it but i dont remember how (lol). The problem is that when i transfer the doc from the slicer to my creality CR 6 SE it s trying to go to the bottom left corner and print. It s like it has no limits and it keep going, the gears lose rotations and its cracking until i stop it. If anyone knows what the problem is, please share with me your knowledge 🙂
  9. Hi I recently downloaded a cura project 3mf file from a guy here and now my ender 3 is ignoring the G0... Z___ commands in gcode, it just plows and plows on the first layer and never moves up. If I send a command thru terminal like G0 Z1, then it moves up and stays that way. Well point of a gcode file is to have those commands processed one by one. What is wrong with ";MESH:NONMESH G0 F240 X136.959 Y150.071 Z0.28"? Well thats from my gcode and it even works from terminal so why ignored the gcode? I guess it's more of a marlin question. Sorry DEFAULT04x012_N0113.gcode
  10. Well, over the past few weeks cura 4.12 has started to underextrude - well made gcode files that did so. I finally took a single layer to a caliper and measured. My lines are set at 0.4mm, same as the nozzle, and yet only 2.5 lines are within 1.6mm with much empty space. There should be 4 lines. I don't see an option for space between lines, there's line width and thats it. If it means anything I have a bunch of custom line directions [45,135,15,105,75,165]. I don't think it's the printer because i tried an old gcode I sliced last year, it printed fine with lines approximated. So with the lines overspaced, none of my prints are finishing. I can compensate with flow to like 150%, but then I get artifacts from overextrusion! Please help.
  11. I'm thinking it's time to replace the desiccant in my material manager. It doesn't seem to be maintaining the 40% humidity level it is supposed to. I have a 5 lb jar of color changing desiccant beads that I could use. Are there any instructions for doing this? I seem to remember something not being shielded that I could zap myself on. I think my warrantee was out around September so I won't be endangering anything regarding that..
  12. How to set Cura to print with a 0.15mm nozzle? The minimum nozzle in the program is 0.25mm.
  13. Hi friends. I am wondering where I do change the end position for the bed? It is currently parkng the printer head all the way in the front of the bed lower left side. I want the bed to move forward so that the printer head parks itself at the upper left corner instead. But is there a way to change this? If so, where? Have looked at all settings but cannot find it or i missed it, there are so many settings, but so far start and end position have I not seen anywhere. How to solve this?
  14. Is anybody familiar with the Olimex Board that sits inside the S5, first version. We have a faulty USB port, and it's not the cable. Olimex.com has several versions listed for the A20 board. But wich one is the correct one? A20-OLinuXino-LIME2 A20-OLinuXino-LIME2-e16Gs16M A20-OLinuXIno-LIME2-n8G A20-OLinuXino-LIME2-s16M T2-OLinuXino-LIME2-e8Gs16M-IND T2-OLinuXino-LIME2-IND T2-OLinuXino-LIME2-s16M-IND
  15. when starting a print with the UM2+ from cold the machine doesn't start the print process but restarts the whole system. the bug occurs only with new gcodes; an old gcode, from about 4 weeks ago, works with no problem. When I start with the old gcode, abort after a few minutes heating and start the new gcode it works fine, so this is a workaround. I just updated the firmware thethe bug persists. does anyone have a solution to this bug? all the best 🙂
  16. 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.
  17. I really wish there was a way to use something like the Ultimaker Android app to rewrite a bad or missing RFIDs. I got new material and every single spool has a blank RFID. I don't know if it's just getting reset in the mail or they never got written in the factory but now I am taking RFIDs off empty spools to make them print. This is becoming more common and is now pretty much a regular occurance. Now is it the FBI scanning all my mail because they hate my politics or is it just my bad luck, dunno. The best solution is to give the app the ability to rewrite the missing or reset RFID. Right now I am using an old ABS Black RFID on my new blue spools and the amount left is just a question mark. Worse is since I only have one ABS RFID I can't have it switch automatically to the next spool.
  18. Hello, I have a question I’m printing a Text and a Figure on a Wall Hanging Plaque I sculpted in ZBrush. It’s Watertight and all the Text Letters and Figure start on the same layer. Is there any Setting, Script or Model Creation Technique that I can set the text and figure to start printing at the same layer after a completely smooth flat layer has completed? Cura 4.12.1 slices my model so the infill continues from the bottom for both the text and figure making the surface not as smooth as it could be if the text and figure started printing after a flat layer. Photos attached. Any suggestions would be appreciated. Thanks Paul
  19. The attached .STL is just a test piece that is part of a much bigger print. The protrusion is very small. The whole piece is only 6 mm tall, with an arc radius of 1.5 mm. I can print the test piece vertically and it comes out perfect. However, it needs to print horizontally as part of the bigger object. I determined that it needs to print with the smallest layer height possible with supports, but no matter what I do with the supports, it never comes out with a useful print. Are there things I can do with supports to make this work, or am I just asking the impossible? Using a Prusa i3-MK3. P4.stl
  20. Hello everyone, is there an easy way to mount the filament spools to the side of the Ultimaker S5? We do not have enough space in depth to mount the spools behind the S5. Our preferred solution would be to mount them sideways, without loosing the NFC functionalities. Best regards Igor
  21. I'm using a Creality Ender 5 Plus with Cura 4.12.1 I'm new at 3D printers and Cura. I've been printing directly from a SD card and don't have a network connection to my printer. Do I need to have my printer connected via my network to get the Start Simulation menu choice to show up?
  22. Cura has been giving me some trouble and I'm sure it's an easy fix but I just can't seem to find my issue on past discussions. That or I'm just not sure what to call this issue since I'm pretty new to 3D printing but anyways, here is my issue: Cura is slicing my first layer into 3 different sections and then begins the second layer on top of that first layer and some of it gets printed in air which results in poor bed adhesion and a failed print. Does anyone know how fix this issue ? Any help is appreciated. Also, I've debated whether it is my bed-leveling but the skirt prints well.
  23. Hi everyone, The print head in my ultimaker S5 flooded a few weeks ago. After finally getting all of the plastic out and turning the printer on, I kept on getting a max temp error for print core 1. I took out the print core, cleaned the sensors, and put it back in - but now my printer won’t even recognize that there’s a print core in there (just says “no print core”). When I took it out, I noticed there were some scratches on the sensors (after the head flooded, it took some wiggling to get the core out - I’m guessing they got scratched then). Any recommendations on what to do? Thanks for the help!
  24. And I'm wondering why? I used 3DLac and was printing ABS with default Cura settings. (On my new 2+Connect, btw 😀) Didn't find any shivers of glass on the prints, or otherwise. So what the h*ll happened?
  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...