leliep

Sorry guys, after trying out the Beta again and loading an .stl file it turns out that the font distortion is still there, please see attached image. It seems to be somehow random, some characters are ok, some others are not. Sometimes cura starts with fine characters and you have to load a print file or change to "Monitor" before the distortions start. (Sorry for the confusion) Just did a quick check and it looks like the fonts are coming out perfectly. Thanks for fixing this!

Just did a quick check and it looks like the fonts are coming out perfectly. Thanks for fixing this!

I had the same kind of problem after I didn‘t use my UM3 for several days (disconnected from mains power). The prints did not attach to the glass plate any more. It turned out that the leveling had gone somehow. After manually initiating the automatic leveling process everything was fine again.

Thanks for your suggestions; tried both, but none helps.

Up to now it hasn't reappeared, but previously it already took some time to repeat. So right now I'm printing like mad, hoping that it will have gone. (But - as I know from other projects - those things do not just disappear, they only hide. Until you can find the real reason, which I did not. Yet.) ...still counting... no problem till now.

Please see my previous reply; I just added a screenshot.

Same for me.

Up to now it hasn't reappeared, but previously it already took some time to repeat. So right now I'm printing like mad, hoping that it will have gone. (But - as I know from other projects - those things do not just disappear, they only hide. Until you can find the real reason, which I did not. Yet.)

Further testing leads to the conclusion that the (original Apple A1433 EMC2590) Thunderbold Gigabit Ethernet Adapter is crashing Cura 2.7 on my MacBook pro with MacOS 10.12.6 (no problems with Cura 2.6): when I connect to the network via my Thunderbold Gigabit Ethernet adapter, Cura crashes after several (about 6) seconds, producing a formidable stack dump. This behavior ist reproducible on intent. Using the network via WiFi or via an USB-Ethernet Adapter is working w/o any problem.

Could it have something to do with the Cura printer access? I was able to start Cura 2.7 from another fresh account on my MacOS based MacBook and prepare a print without any problem, not yet connected a printer. As soon as I then tried to connect Cura to my UM3 (via ethernet, local network with 192.168.10.x) address, Cura crashed immediately. Was able to reproduce this several times. I have a cura stderr.log from this event, can send it to whom it concerns... (too long to post here)

Yes, I disconnected and reseated the cable, but it looked absolutely ok, will try now whether the problem is still there... For further reference I took some pictures to show the proper place to push to disconnect the plug ;-)

Which materials did you use? PLA and Nylon? I used PLA for both parts of the housing; the mounting arm and (temporary) base are Nylon. Eventually it will be attached to a wooden post in the garden. Maybe to make the case weather proof, it needs to get a paint cover, but that's something I have not made (yet).

Could you also share your cura.log file? The only one that I have is one from the night before, please see: http://elb-v2-prod-615036279.eu-west-1.elb.amazonaws.com/en/community/50967-announcing-cura-27?page=1&sort=#reply-188213 Right now Cura can be started without a problem, so the problem ist sometimes there and sometimes not. Strange. Seems the problem has nothing to do with the CA trust, because right now it works despite the CA error msg on the console: Last login: Fri Sep 1 11:56:36 on ttys008 PL-MBPro-1257:~ peterlelie$ /Applications/Cura\ 2.app/Contents/MacOS/cura ; exit; qt.network.ssl: Error receiving trust for a CA certificate QObject::connect: Parentheses expected, signal MainWindow:: QObject::connect: Parentheses expected, signal MainWindow:: QObject::connect: Parentheses expected, signal MainWindow:: QObject::connect: Parentheses expected, signal MainWindow:: qml: TableViewSelection: index out of range qml: TableViewSelection: index out of range

Air quality sensor housing, for details see https://www.thingiverse.com/thing:2499253

Today I was able to start Cura 2.7 once and send a job to my UM3. When the print was finished, Cura had crashed. When I try to start it again, it always crashes now. When I open the Cura package and start MacOS/cura, I get the following message in the terminal window: Last login: Fri Sep 1 00:01:19 on ttys006 PL-MBPro:~ peterlelie$ /Applications/Cura\ 2.app/Contents/MacOS/cura ; exit; qt.network.ssl: Error receiving trust for a CA certificate Segmentation fault: 11 logout Saving session... ...copying shared history... ...saving history...truncating history files... ...completed. Deleting expired sessions...none found. [Prozess beendet]

Thanks for making it available, but on my MacBook with MacOS Sierra 10.12.6 it always crashes during startup. This behavior was already with the beta version and it persists after reboot. Right now I am working with Cura 2.6.x, but would like to change to 2.7 Thanks again, -pl 2017-08-30 23:46:45,580 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin ConsoleLogger 2017-08-30 23:46:45,588 - INFO - CuraEngineBackend.CuraEngineBackend.__init__ [64]: Found CuraEngine at: /Applications/Cura 2.app/Contents/MacOS/CuraEngine 2017-08-30 23:46:45,590 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin CuraEngineBackend 2017-08-30 23:46:45,593 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin CuraProfileReader 2017-08-30 23:46:45,597 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin CuraProfileWriter 2017-08-30 23:46:45,600 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin OBJReader 2017-08-30 23:46:45,604 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin OBJWriter 2017-08-30 23:46:45,611 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin STLReader 2017-08-30 23:46:45,614 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin STLWriter 2017-08-30 23:46:45,618 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin FileLogger 2017-08-30 23:46:45,622 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin GCodeProfileReader 2017-08-30 23:46:45,627 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin GCodeReader 2017-08-30 23:46:45,631 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin GCodeWriter 2017-08-30 23:46:45,635 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin ImageReader 2017-08-30 23:46:45,642 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin LayerView 2017-08-30 23:46:45,646 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin LegacyProfileReader 2017-08-30 23:46:45,652 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin LocalFileOutputDevice 2017-08-30 23:46:45,657 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin MachineSettingsAction 2017-08-30 23:46:45,693 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin OctoPrintPlugin 2017-08-30 23:46:45,699 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin PerObjectSettingsTool 2017-08-30 23:46:45,704 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin PluginBrowser 2017-08-30 23:46:45,710 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin PostProcessingPlugin 2017-08-30 23:46:45,727 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin RemovableDriveOutputDevice 2017-08-30 23:46:45,763 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin SliceInfoPlugin 2017-08-30 23:46:45,769 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin SolidView 2017-08-30 23:46:45,774 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin CameraTool 2017-08-30 23:46:45,781 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin MirrorTool 2017-08-30 23:46:45,788 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin RotateTool 2017-08-30 23:46:45,795 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin ScaleTool 2017-08-30 23:46:45,802 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin SelectionTool 2017-08-30 23:46:45,810 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin TranslateTool 2017-08-30 23:46:45,818 - INFO - UM.PluginRegistry.loadPlugin [231]: Loaded plugin UltimakerMachineActions Fatal Python error: Segmentation fault Thread 0x0000700005411000 (most recent call first): File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/zeroconf.py", line 1853 in send File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/zeroconf.py", line 1164 in run File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x0000700004f0e000 (most recent call first): File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 297 in wait File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/zeroconf.py", line 1569 in wait File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/zeroconf.py", line 1017 in run File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x0000700004a0b000 (most recent call first): File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/zeroconf.py", line 984 in handle_read File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/zeroconf.py", line 951 in run File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x0000700004508000 (most recent call first): File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/subprocess.py", line 1059 in communicate File "/Applications/Cura 2.app/Contents/MacOS/plugins/plugins/RemovableDriveOutputDevice/OSXRemovableDrivePlugin.py", line 19 in checkRemovableDrives File "/Applications/Cura 2.app/Contents/MacOS/plugins/plugins/RemovableDriveOutputDevice/RemovableDrivePlugin.py", line 56 in _updateThread File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 862 in run File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x0000700004005000 (most recent call first): File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 297 in wait File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/zeroconf.py", line 1569 in wait File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/zeroconf.py", line 1153 in run File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x0000700003b02000 (most recent call first): File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 297 in wait File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/zeroconf.py", line 1569 in wait File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/zeroconf.py", line 1017 in run File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x00007000035ff000 (most recent call first): File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/zeroconf.py", line 984 in handle_read File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/zeroconf.py", line 951 in run File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x0000700003079000 (most recent call first): File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 297 in wait File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/zeroconf.py", line 1569 in wait File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/zeroconf.py", line 1017 in run File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x0000700002b76000 (most recent call first): File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/zeroconf.py", line 946 in run File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/threading.py", line 882 in _bootstrap Current thread 0x00007fffe458e3c0 (most recent call first): File "/Applications/Cura 2.app/Contents/MacOS/plugins/plugins/UM3NetworkPrinting/NetworkPrinterOutputDevicePlugin.py", line 110 in checkManualPrinter File "/Applications/Cura 2.app/Contents/MacOS/plugins/plugins/UM3NetworkPrinting/NetworkPrinterOutputDevicePlugin.py", line 93 in addManualPrinter File "/Applications/Cura 2.app/Contents/MacOS/plugins/plugins/UM3NetworkPrinting/NetworkPrinterOutputDevicePlugin.py", line 74 in startDiscovery File "/Applications/Cura 2.app/Contents/MacOS/plugins/plugins/UM3NetworkPrinting/NetworkPrinterOutputDevicePlugin.py", line 56 in start File "/Users/ultimaker/build/2.7/build/inst/lib/python3.5/site-packages/UM/OutputDevice/OutputDeviceManager.py", line 183 in addOutputDevicePlugin File "/Users/ultimaker/build/2.7/build/inst/lib/python3.5/site-packages/UM/PluginRegistry.py", line 243 in _addPluginObject File "/Users/ultimaker/build/2.7/build/inst/lib/python3.5/site-packages/UM/PluginRegistry.py", line 227 in loadPlugin File "/Users/ultimaker/build/2.7/build/inst/lib/python3.5/site-packages/UM/PluginRegistry.py", line 257 in loadPlugins File "/Users/ultimaker/build/2.7/build/inst/lib/python3.5/site-packages/cura/CuraApplication.py", line 512 in _loadPlugins File "/Users/ultimaker/build/2.7/build/inst/lib/python3.5/site-packages/UM/Qt/QtApplication.py", line 110 in __init__ File "/Users/ultimaker/build/2.7/build/inst/lib/python3.5/site-packages/cura/CuraApplication.py", line 205 in __init__ File "/Users/ultimaker/build/2.7/build/inst/lib/python3.5/site-packages/UM/Application.py", line 316 in getInstance File "/Users/ultimaker/build/2.7/build/inst/bin/cura_app.py", line 72 in File "", line 634 in _load_backward_compatible File "", line 664 in _load_unlocked File "", line 958 in _find_and_load_unlocked File "", line 969 in _find_and_load File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/cx_Freeze/initscripts/Console.py", line 21 in File "", line 634 in _load_backward_compatible File "", line 664 in _load_unlocked File "", line 958 in _find_and_load_unlocked File "", line 969 in _find_and_load File "/Users/ultimaker/build/env/2.7/inst/lib/python3.5/site-packages/cx_Freeze/initscripts/__startup__.py", line 12 in File "", line 634 in _load_backward_compatible File "", line 664 in _load_unlocked File "", line 958 in _find_and_load_unlocked File "", line 969 in _find_and_load

Important note at the beginning “Do not disassemble the printer unless you have been instructed to do so.” not disagreeing with that, but if the first thing out of a resellers mouth is "just send it back" then that;s not ok with this error... then again, perhaps I just like to live on the wild side Nono. I agree with you personally. I would have disassemble the heck out of it because that how I am. But warranty and stuff for um3 is different. So I prefer to be safe than sorry when the printer isn’t mine Also we know there’s no magic unicorns inside and except the damage by ESD, the rest it’s pretty much like any printer. But also, well, is a 3K machine after all. agreed, but he bought at Conrad who is NOT an official reseller. and if the first thing out of their mouths is "just send it back" I'd worry about what I would get returned to me. I'd contact either an official reseller, or play with it myself before I would send it back. Well, the printer kit contained a screwdriver which fits the screws we're talking about. I take that as a sign from above... ;-) Btw, if I had known the support issue with Conrad previously, then I would have chosen another reseller. I really hesitate to ship the printer to them, because I fear that it might not get better by being sent across the country. Thank you for the reference to the fabric8-document, it looks helpful and after opening the cable cover to get a peek into it, I'm pretty confident that checking the cable will do no harm. This is not the first box that I'm opening in my life.

Arrgggg, I just talked to a technician from Conrad who told me to return the printer to them for repair or exchange. :-/

Thanks guys, I will try that. In some certain order ;-) Cheers & groetjes, -pl

Thanks for your suggestion; I am pretty sure that they are placed correctly, but will verify once more and test again.

It did it again After the first problem occurred I was able to print several parts with both extruders without of any problem, but today the above error occured again. After completing the last night's print job with (only) extruder 2, my UM2 this morning sat there again with the same error message like 6 days ago. There is a communication error with the print head. Go to ultimaker.com/ER18 -devMode- internal message follows: Error I2C_HEAD_COMM_ERROR I suppose in the cooldown phase after completion of printing the UM3 tried to communicate with the temperature sensor in extruder 1 (unused in the preceding job) without success, which led to the error. Sending the request http:///api/v1/system gave this result: {"country": "DE", "firmware": "3.7.7.20170627", "guid": "01d2b23d-6a83-41a0-a3e8-dcf0fde26d85", "hardware": {"revision": 0, "typeid": 9066}, "hostname": "ultimakersystem-ccbdd3001d93", "language": "", "log": ["Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,882 INFO procedure Message: 'ABORT' for procedure 'PrintProcedure(key='PRINT')'", "Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,883 INFO procedure Abort message received for procedure PrintProcedure(key='PRINT')", "Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,886 INFO procedure Pass abort to RUN_POST_PRINT", "Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,887 INFO procedureStep Aborting step: OtherProcedureStep(key='RUN_POST_PRINT')", "Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,888 INFO procedure Message: 'ABORT' for procedure 'PostPrintProcedure(key='POST_PRINT')'", "Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,889 INFO procedure Abort message ignored for procedure PostPrintProcedure(key='POST_PRINT')", "Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,893 INFO printerStateProperty State change: printing -> error", "Aug 28 05:49:06 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:06,916 INFO procedure PostPrintProcedure(key='POST_PRINT') is going to be aborted", "Aug 28 05:49:07 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:07,977 INFO procedure PostPrintProcedure(key='POST_PRINT') transitioning from HomeHeadStep(key='HOME_HEAD') --> QueueRawGCodeWaitStep(key='RESET_OFFSET_0')", "Aug 28 05:49:07 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:07,979 INFO printerService Procedure next step: POST_PRINT: RESET_OFFSET_0", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,157 INFO procedure PostPrintProcedure(key='POST_PRINT') transitioning from QueueRawGCodeWaitStep(key='RESET_OFFSET_0') --> ResetPropertyToDefaultStep(key='RESET_TUNE_OFFSET_TEMPERATURE_0')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,159 INFO printerService Procedure next step: POST_PRINT: RESET_TUNE_OFFSET_TEMPERATURE_0", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,162 INFO procedure PostPrintProcedure(key='POST_PRINT') transitioning from ResetPropertyToDefaultStep(key='RESET_TUNE_OFFSET_TEMPERATURE_0') --> QueueRawGCodeWaitStep(key='RESET_OFFSET_1')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,165 INFO printerService Procedure next step: POST_PRINT: RESET_OFFSET_1", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,276 INFO procedure PostPrintProcedure(key='POST_PRINT') transitioning from QueueRawGCodeWaitStep(key='RESET_OFFSET_1') --> ResetPropertyToDefaultStep(key='RESET_TUNE_OFFSET_TEMPERATURE_1')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,280 INFO printerService Procedure next step: POST_PRINT: RESET_TUNE_OFFSET_TEMPERATURE_1", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,285 INFO procedure PostPrintProcedure(key='POST_PRINT') transitioning from ResetPropertyToDefaultStep(key='RESET_TUNE_OFFSET_TEMPERATURE_1') --> WaitForQueueToBeEmptyStep(key='WAITING')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,287 INFO printerService Procedure next step: POST_PRINT: WAITING", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,292 INFO procedure PostPrintProcedure(key='POST_PRINT') transitioning from WaitForQueueToBeEmptyStep(key='WAITING') --> OtherProcedureStep(key='SWITCH_TO_HOTEND')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,294 INFO printerService Procedure next step: POST_PRINT: SWITCH_TO_HOTEND", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,297 INFO switchActiveHotendProcedure Target hotend = 1", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,304 INFO printerService Procedure start: SWITCH_ACTIVE_HOTEND: WAIT", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,313 INFO printerService Procedure next step: SWITCH_ACTIVE_HOTEND: WAIT", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,322 INFO procedure SwitchActiveHotendProcedure(key='SWITCH_ACTIVE_HOTEND') transitioning from WaitForQueueToBeEmptyStep(key='WAIT') --> SwitchActiveHotendStep(key='SWITCH_ACTIVE_HOTEND')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,328 INFO printerService Procedure next step: SWITCH_ACTIVE_HOTEND: SWITCH_ACTIVE_HOTEND", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,335 INFO procedure SwitchActiveHotendProcedure(key='SWITCH_ACTIVE_HOTEND') transitioning from SwitchActiveHotendStep(key='SWITCH_ACTIVE_HOTEND') --> None", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,339 INFO printerService Procedure finished: SWITCH_ACTIVE_HOTEND", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,344 INFO procedure PostPrintProcedure(key='POST_PRINT') transitioning from OtherProcedureStep(key='SWITCH_TO_HOTEND') --> HomeHeadStep(key='HOME_HEAD')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,347 INFO printerService Procedure next step: POST_PRINT: HOME_HEAD", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,725 INFO procedure PostPrintProcedure(key='POST_PRINT') transitioning from HomeHeadStep(key='HOME_HEAD') --> WaitForQueueToBeEmptyStep(key='WAITING')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,727 INFO printerService Procedure next step: POST_PRINT: WAITING", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,732 INFO procedure PostPrintProcedure(key='POST_PRINT') transitioning from WaitForQueueToBeEmptyStep(key='WAITING') --> PowerDownSteppersStep(key='POWER_DOWN_STEPPERS')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,734 INFO printerService Procedure next step: POST_PRINT: POWER_DOWN_STEPPERS", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,879 INFO procedure PostPrintProcedure(key='POST_PRINT') transitioning from PowerDownSteppersStep(key='POWER_DOWN_STEPPERS') --> WaitForQueueToBeEmptyStep(key='WAITING')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,881 INFO printerService Procedure next step: POST_PRINT: WAITING", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,885 INFO procedure PostPrintProcedure(key='POST_PRINT') transitioning from WaitForQueueToBeEmptyStep(key='WAITING') --> None", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,890 INFO printerService Procedure finished: POST_PRINT", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,892 INFO procedureStep Step to Aborted state: RUN_POST_PRINT", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,901 WARNING procedure PrintProcedure(key='PRINT') is aborted and overruling outcome OutcomeBase.Aborted from OtherProcedureStep(key='RUN_POST_PRINT')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,906 INFO procedure PrintProcedure(key='PRINT') transitioning from OtherProcedureStep(key='RUN_POST_PRINT') --> WaitMessageStep(key='WAIT_FOR_CLEANUP')", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,913 INFO printJobStateProperty New print job state: post_print -> wait_cleanup", "Aug 28 05:49:08 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:08,921 INFO printerService Procedure next step: PRINT: WAIT_FOR_CLEANUP", "Aug 28 05:49:09 ultimakersystem-ccbdd3001d93 python3.4[369]: 2017-08-28 05:49:09,887 INFO registryFile Saving preferences to /var/lib/griffin/printer_hotend_1_preferences.json", "Aug 28 05:54:10 ultimakersystem-ccbdd3001d93 connmand[196]: ntp: time slew -0.007819 s", "Aug 28 06:01:39 ultimakersystem-ccbdd3001d93 python3.4[182]: 2017-08-28 06:01:39,596 INFO systemUpdate Comparing firmware 'stable' old version '3.7.7.20170627' with new version '3.7.7.20170627' with result: True", "Aug 28 06:11:14 ultimakersystem-ccbdd3001d93 connmand[196]: ntp: time slew -0.008152 s", "Aug 28 06:28:19 ultimakersystem-ccbdd3001d93 connmand[196]: ntp: time slew -0.008002 s", "Aug 28 06:40:19 ultimakersystem-ccbdd3001d93 mjpg-streamer[257]: MJPG-streamer [257]: serving client: 192.168.10.135", "Aug 28 06:42:21 ultimakersystem-ccbdd3001d93 mjpg-streamer[257]: MJPG-streamer [257]: serving client: 192.168.10.135", "Aug 28 06:45:23 ultimakersystem-ccbdd3001d93 connmand[196]: ntp: time slew -0.008102 s"], "memory": {"total": 1057030144, "used": 176541696}, "name": "ultimaker", "platform": "Linux-4.2.0-rc7-opinicus-00002-g1e30dbd-armv7l-with-debian-8.1", "type": "3D printer", "variant": "Ultimaker 3"} Issuing http:///api/v1/printer/diagnostics/temperature_flow/10 results in this: [["Time", "temperature0", "target0", "heater0", "flow_sensor0", "flow_steps0", "temperature1", "target1", "heater1", "flow_sensor1", "flow_steps1", "bed_temperature", "bed_target", "bed_heater", "active_hotend_or_state"], [430249.375, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 24.0, 0.0, 0.0, 16.0], [430249.46875, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 23.799999237060547, 0.0, 0.0, 16.0], [430249.59375, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 24.299999237060547, 0.0, 0.0, 16.0], [430249.6875, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 24.0, 0.0, 0.0, 16.0], [430249.8125, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 24.100000381469727, 0.0, 0.0, 16.0], [430249.90625, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 24.0, 0.0, 0.0, 16.0], [430250.03125, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 23.700000762939453, 0.0, 0.0, 16.0], [430250.125, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 24.299999237060547, 0.0, 0.0, 16.0], [430250.25, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 23.799999237060547, 0.0, 0.0, 16.0], [430250.34375, 280.5, 0.0, 0.0, 0.0, 0.0, 280.5, 0.0, 0.0, 0.0, 0.0, 24.0, 0.0, 0.0, 16.0]] And finally the result from http:///api/v1/printer/heads/0 is this: {"acceleration": 3000.0, "extruders": [{"active_material": {"GUID": "506c9f0d-e3aa-4bd4-b2d2-23e2425b1aa9", "guid": "506c9f0d-e3aa-4bd4-b2d2-23e2425b1aa9", "length_remaining": -1.0}, "feeder": {"acceleration": 3000.0, "jerk": 5.0, "max_speed": 45.0}, "hotend": {"id": "AA 0.4", "offset": {"state": "valid", "x": 0.0, "y": 0.0, "z": 0.0}, "serial": "d1fac2170000", "statistics": {"last_material_guid": "506c9f0d-e3aa-4bd4-b2d2-23e2425b1aa9", "material_extruded": 468080, "max_temperature_exposed": 280, "time_spent_hot": 2069820}, "temperature": {"current": 280.5, "target": 0.0}}}, {"active_material": {"GUID": "506c9f0d-e3aa-4bd4-b2d2-23e2425b1aa9", "guid": "506c9f0d-e3aa-4bd4-b2d2-23e2425b1aa9", "length_remaining": -1.0}, "feeder": {"acceleration": 3000.0, "jerk": 5.0, "max_speed": 45.0}, "hotend": {"id": "AA 0.4", "offset": {"state": "valid", "x": -0.07317073170731714, "y": 0.07317073170731714, "z": 1.4191436945413525}, "serial": "ae3fc2170000", "statistics": {"last_material_guid": "506c9f0d-e3aa-4bd4-b2d2-23e2425b1aa9", "material_extruded": 120620, "max_temperature_exposed": 280, "time_spent_hot": 806220}, "temperature": {"current": 280.5, "target": 0.0}}}], "fan": 0.0, "jerk": {"x": 20.0, "y": 20.0, "z": 0.4}, "max_speed": {"x": 300.0, "y": 300.0, "z": 40.0}, "position": {"x": 0.0, "y": 0.0, "z": 0.0}} Thanks for any hints or recommendations (Ultimaker, are you listening?).

After several weeks without any major problem my UM3 last night stopped with an error, while printing with with a 0.8 nozzle and displayed the following error message: PrintCore in head slot 1 is taking too long to warm up. -devMode- internal message follows: Waiting for hotend temperature is taking too long After turning off the device and clearing up the mess I restarted the print process. After printing part of the first layer, it stopped with the following error message: There is a communication error with the print head. Go to ultimaker.com/ER18. -devMode- internal message follows: Error I2C_HEAD_COMM_ERROR I replaced the print core with an aa0.4 type and after restarting the print I got the previous error again after a short time of printing. I restarted the print on extruder 2 and it went without a problem. Maybe the cable to the print heads is defective? After 7 weeks of use? The information at ultimaker.com/ER18 is not helpful in this case. Anybody else seen this problem? What can I do next? Thanks, -pl