polygonfuture

No more problems with heat creep since flipping the fan. Calling this solved.

Thanks Enimga_M4. Reached out to local North American support (Thanks Erin at FBRC8.com!) Turns out I had the fan backwards. Two weeks ago had a print flood the printhead and lost an AA core. When reassembling looks like I flipped it by mistake. Air is now blowing onto the printhead vs away from. Will test but this should fix my problem.

Hi all, I've got a UM3 and recently changed to a new print core (AA) after having one fail to a print flooding the head. I'm getting heat creep on two different PLA spools in the nozzle which causes the filament to expand in size slightly causing it to seize and fail to extrude. This in turn causes the extruders to detect a flow issue and pause print. (I have S5 feeders with flow sensors and modified configs on my UM3) After print pauses I pull the bowden at the print head, snip off the expanded portion, reinsert bowden and it continues to print for a while. Eventually it will happen again and I repeat the process. My retraction settings are pretty low at 3.5 mm - 4mm/s. Retraction speed is 40mm/s. Previously my settings were 4.5mm/s for retraction length and 25mm/s for speed. Anyone have any suggestions on what could be the culprit? Cura settings pasted below:

I do not think this is correct. The gear on the extruder motor does not come into contact with any abrasive material. Only the feeder gears within the extruder housing themselves come into contact with abrasive filament. If you upgrade your feeders to S5 you are good.

Anyone?

Bump

Ok not sure what was going on, but I just upgraded to 5.3.0 cura and now its working. Pretty odd, it didnt matter what profile I used it would crash. Solved now.

Hey All, Getting an error when trying to slice in cura all of a sudden. Every time I go to slice I get this issue. Cura gave me an error about bad profiles. I removed those profiles but still getting the crash when sending a print over network. Slicing works fine. Printing does not. Anyone have some thoughts or suggestions? Windows 10, using RTX 3070 laptop. Cura 5.2.1. Error Traceback: Traceback (most recent call last): File "cura\CuraApplication.py", line 1127, in event return super().event(event) File "UM\Qt\QtApplication.py", line 502, in event event._function_event.call() File "UM\Event.py", line 218, in call self._function(*self._args, **self._kwargs) File "cura\Utils\Threading.py", line 34, in _handle_call ico.result = func(*args, **kwargs) File "C:\Program Files\Ultimaker Cura 5.2.1\share\cura\plugins\UFPWriter\UFPWriter.py", line 88, in write json.dump(self._getSliceMetadata(), setting_textio, separators=(", ", ": "), indent=4) File "json\__init__.py", line 179, in dump File "json\encoder.py", line 431, in _iterencode File "json\encoder.py", line 405, in _iterencode_dict File "json\encoder.py", line 405, in _iterencode_dict File "json\encoder.py", line 405, in _iterencode_dict File "json\encoder.py", line 438, in _iterencode File "json\encoder.py", line 179, in default TypeError: Object of type SettingFunction is not JSON serializable Logs Thread 0x0000ab7c (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 600 in wait File "cura\Utils\Threading.py", line 39 in _call_on_qt_thread_wrapper File "C:\Program Files\Ultimaker Cura 5.2.1\share\cura\plugins\UM3NetworkPrinting\src\Network\SendMaterialJob.py", line 112 in _sendMaterials File "C:\Program Files\Ultimaker Cura 5.2.1\share\cura\plugins\UM3NetworkPrinting\src\Network\SendMaterialJob.py", line 68 in _sendMissingMaterials File "threading.py", line 946 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x00002898 (most recent call first): File "C:\Program Files\Ultimaker Cura 5.2.1\share\cura\plugins\USBPrinting\USBPrinterOutputDeviceManager.py", line 88 in _updateThread File "threading.py", line 946 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x00007fec (most recent call first): File "threading.py", line 324 in wait File "zeroconf\__init__.py", line 2534 in wait File "zeroconf\__init__.py", line 1715 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x0000378c (most recent call first): File "threading.py", line 324 in wait File "threading.py", line 600 in wait File "C:\Program Files\Ultimaker Cura 5.2.1\share\cura\plugins\UM3NetworkPrinting\src\Network\ZeroConfClient.py", line 81 in _handleOnServiceChangedRequests File "threading.py", line 946 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x000044c8 (most recent call first): File "zeroconf\__init__.py", line 1369 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x00008bd8 (most recent call first): File "C:\Program Files\Ultimaker Cura 5.2.1\share\cura\plugins\RemovableDriveOutputDevice\RemovableDrivePlugin.py", line 61 in _updateThread File "threading.py", line 946 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x00005258 (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 460 in acquire File "UM\JobQueue.py", line 98 in _nextJob File "UM\JobQueue.py", line 124 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x00009aa0 (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 460 in acquire File "UM\JobQueue.py", line 98 in _nextJob File "UM\JobQueue.py", line 124 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x00000e90 (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 460 in acquire File "UM\JobQueue.py", line 98 in _nextJob File "UM\JobQueue.py", line 124 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x0000444c (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 460 in acquire File "UM\JobQueue.py", line 98 in _nextJob File "UM\JobQueue.py", line 124 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x000077d4 (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 460 in acquire File "UM\JobQueue.py", line 98 in _nextJob File "UM\JobQueue.py", line 124 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x0000a1b8 (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 600 in wait File "cura\Utils\Threading.py", line 39 in _call_on_qt_thread_wrapper File "UM\FileHandler\WriteFileJob.py", line 76 in run File "UM\JobQueue.py", line 133 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x00007f80 (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 460 in acquire File "UM\JobQueue.py", line 98 in _nextJob File "UM\JobQueue.py", line 124 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x00006c54 (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 460 in acquire File "UM\JobQueue.py", line 98 in _nextJob File "UM\JobQueue.py", line 124 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x00007b98 (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 460 in acquire File "UM\JobQueue.py", line 98 in _nextJob File "UM\JobQueue.py", line 124 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x00002868 (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 460 in acquire File "UM\JobQueue.py", line 98 in _nextJob File "UM\JobQueue.py", line 124 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x00009c78 (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 460 in acquire File "UM\JobQueue.py", line 98 in _nextJob File "UM\JobQueue.py", line 124 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x00004644 (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 460 in acquire File "UM\JobQueue.py", line 98 in _nextJob File "UM\JobQueue.py", line 124 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x00006188 (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 460 in acquire File "UM\JobQueue.py", line 98 in _nextJob File "UM\JobQueue.py", line 124 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x0000adcc (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 460 in acquire File "UM\JobQueue.py", line 98 in _nextJob File "UM\JobQueue.py", line 124 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x0000641c (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 460 in acquire File "UM\JobQueue.py", line 98 in _nextJob File "UM\JobQueue.py", line 124 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Thread 0x0000aca4 (most recent call first): File "threading.py", line 320 in wait File "threading.py", line 460 in acquire File "UM\JobQueue.py", line 98 in _nextJob File "UM\JobQueue.py", line 124 in run File "threading.py", line 1009 in _bootstrap_inner File "threading.py", line 966 in _bootstrap Current thread 0x00004694 (most recent call first): File "cura\CrashHandler.py", line 397 in _logInfoWidget File "cura\CrashHandler.py", line 182 in _createDialog File "cura\CrashHandler.py", line 86 in __init__ File "cura_app.py", line 165 in exceptHook File "UM\Qt\QtApplication.py", line 416 in exec File "cura\CuraApplication.py", line 897 in run File "cura_app.py", line 239 in <module>

Hi all, TLDR: Got an upgraded UM3 with S5 feeders. -Will CC print cores work out of the box? -Will it function natively as any other print core or are there specific workflows I should be aware of with this setup? Long Version: So some of you may remember about two years ago CarlosK and I put together a document posted here for upgrading UM3 feeders to S5 feeders to get the S5 flow sensors. Those feeders have been doing great for the past two years. Now they've been run-tested and have the benefit of abrasion resistance, I am finally getting around to upgrading to a CC print core for my modified UM3. I want to print NylonG and NylonX materials from matter hackers and just purchased a 0.6 CC nozzle for my UM3. What can I expect the workflow of CC print cores on UM3?

Thanks for the info CarloK. I'll add this info into the doc for future as well. @3dprntz Turns out I made a mistake on Feeder revision. Based on CarloK's latest post, the part numbers I provided are for R1 feeders as R2 are not currently supported with UM3 5.3.0 firmware (but will be added in future firmware update). @CarloK What are the downsides of R1 feeder? The issue is that the R1 feeders can create cracks in PVA filament? Just asking so I know what to watch for in the future.

UPDATE Nov 23, 2021: @3dprintz Based on CarloK's post on November 17th, I am using R1 feeder versions purchased from Erin's outfit at FBRC8 (I'm based in North America). For now R1 is only supported for UM3 firmware 5.3.0. R2 should be supported in future updates but no official deadline has been set for this change.

Hey everyone. @Enigma_M4 @fbrc8-erin @3dprintz I've successfully upgraded to S5 feeders on my UM3 with instructions from CarloK. I've put together a detailed write-up for making the upgrades. The doc is still a WIP and I'll be adding more photos, but thought this would be nice if anyone is adventurous. I've been testing it for two weeks a now and so far so good! It gives abrasion resistant feeders and flow sensor. Also the S5 feeder is just way nicer to change filament using the new lever system. The spring lever system of the stock UM3 is so poor in comparison. NOTE: This document is still a WIP. There may be typos or small mistakes. Please do this mod at your own discretion! Its very simple but it does require one small modification to the ultimaker case, so it may void warranty if that matters to you. More photos will be added in the coming days. Also if you spot any errors in the doc let me know. https://docs.google.com/document/d/1xS30mssCCnmrijWDpg-YsJSjPGnsYNUsdmtQHAISqxY/edit?usp=sharing I can also make a new post if everyone feels that this is worthwhile.

@CarloK Please share with us a guide for you mod for the S5 feeder on the UM3. So many of us I think are wanting this feature. Totally capable to do whatever edits need to be done in firmware / software or any configs.

I've got a super annoying bug where the monitor window doesnt expand wide enough to see the delete print job menu.

This is beautiful! I am looking for a filtration system now that the latest study on 3D printing VOCs is out. The fumes from ABS and PLA are indeed nasty stuff! Stay safe everyone. Raul, if you sell this please let us know. If you offer kits would love to know as well! Cheers, Jonathan

I have this exact same problem. I replaced my short bearing, tightened, realigned etc and all the same problems. My replacement Y bearing also felt like it was scratchy as well. This could be because the Y bearing is so shorter, it is prone to deflection. I was never able to figure out exactly what was causing it. It's been going on for a while. Any other info I'd love to hear as well.

I've noticed the inverse problem on my printer. If autoleveling is not set to always, It tries to print at or below glass plate level, so it never extrudes and just scrapes on the glass. Manual leveling doesnt fix the problem either. Putting it back to always makes it work properly.

Did you try contacting fbrc8.com? They are U.S. based part supplier. If they dont have it or can't get it, no one can. They ship super fast. Last ditch effort would be to try McMaster-Carr, Fastenal, or Grainger. Can determine the thread size with a thread checker or calipers, and then measure the shoulder length, thread length, etc to get the exact screw you need.

Ok Ultimaker Community. It appears I may have found a bug with UM3 5.2.8 firmware! If turn active leveling frequency less than "always", the machine appears to fail to remember the offsets, and print at the wrong z height. The moment I turn active leveling frequency back to always, it prints at the proper z offset from the glass plate. Not on "always", the printer prints at the absolute 0 Z cordinate as the glass plate, therefore it can never extrude. Can anyone else replicate this?

Ok, so scratch that. Both cores are scraping the glass and not printing. What the heck. I dont understand.

Hi all, I am having a problem with my UM3. Today I replaced my short belts and the short bearing the print head. After reassembly, I loaded my AA 0.4 print core into slot 1, and BB 0.4 print core into slot 2. After printing a simple cube using PLA test from core AA, I went to print something that used the BB core with PVA. After doing the prime blob, the BB print core began to "print", but it appeared to only be scraping off the glue stick off of the glass. When the bed retracts, some PVA extrudes out. I have ran active leveling, and finally manual leveling and each time I keep getting the same result for my PVA adhesion layer. I have ran diagnostics on my level sensor, and UM3 is saying it is functioning ok. I have also tried to clear the print head using PLA filament and the cleaning routine. Any one have any ideas why this is happening? What could be causing this?

Hi all, I am looking to purchase a used Ultimaker 3 or 3 Extended located in the U.S. Preferably in Los Angeles or California, but I'll take what I can get. Only request is that machine works well and has no issues. I'm an artist and creative director and its time to finally invest in my own machine. If anyone has one for sale in the U.S. please let me know. Cheers, Jonathan www.polygonfuture.com mail@polygonfuture.com