asb

My S5 arrived today. Delivery was quick and packaging was good. When unpacking, the first irritation was that there is no aluminum plate; there is supposed to be a replacement delivery, but without a scheduled arrival date given. Putting everything together is easy, and it actually powers up. But so far that's it… The S5 does not recognize the NFC spool with Ultimaker tough PLA. I could not get it onto my network because the MAC addresses ar not labeld anywhere. The first installation setup does not work as it loops after loading the filament (choices: cancel, or load filament; can not skip or proceed). So it does not work to start right away printing. My first impression is that the S5 is still a bit work in progress, more a pre-production evaluation sample than something you can work with right away.

> You could just add the printer manually by IP. No, I can not because the Ultimaker 3 Extended does not support configurations with a static IP address. This is the official statement by "iGo3D", the German distributor for Ultimaker. I am aware that it is possible to hack the ConnMan configuration with SSH, but - again according to the Ultimaker distributor - this is unsupported and will cause networking issues. Probably quite a bunch of the numerous issues I am encountering with the Ultimaker 3 Extended is caused because I do not run a DHCP server in my network. However, the system requirements for the Ultimaker 3 Extended do not mention that running a DHCP server is required, so it needs to work without. In June, it did with the Cura version from PPA. Also it is the same distributor - iGo3D - who claims that it is not possible to calibrate the Ultimaker 3 Extended so that models with 10x10x10 cm are printed as objects of 10x10x10 cm. I have to deal with this distributor and the claims they made because they supplied the vendor where I bough the Ultimaker 3 Extended. So where exactly does that leves me as an end customer?

Messages when starting the Appimage from the shell: $ ./Cura-3.0.3.AppImage Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 72: non-double matrix element Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 72: non-double matrix element Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 80: saw unknown, expected number Fontconfig warning: "/etc/fonts/conf.d/70-fonts-bpg-georgian.conf", line 12: bad alias Fontconfig warning: "/etc/fonts/conf.d/70-fonts-bpg-georgian.conf", line 21: bad alias Fontconfig warning: "/etc/fonts/conf.d/70-fonts-bpg-georgian.conf", line 30: bad alias QObject::connect: Parentheses expected, signal MainWindow:: QObject::connect: Parentheses expected, signal MainWindow:: QObject::connect: Parentheses expected, signal MainWindow:: QObject::connect: Parentheses expected, signal MainWindow:: file:///tmp/.mount_siJOmj/usr/bin/resources/themes/cura-light/styles.qml:197:17: QML Item: Binding loop detected for property "width" qml: TableViewSelection: index out of range qml: TableViewSelection: index out of range file:///tmp/.mount_siJOmj/usr/bin/plugins/plugins/UM3NetworkPrinting/DiscoverUM3Action.qml:282: TypeError: Cannot read property 'clusterSize' of null qml: TableViewSelection: index out of range file:///tmp/.mount_siJOmj/usr/bin/plugins/plugins/UM3NetworkPrinting/DiscoverUM3Action.qml:282: TypeError: Cannot read property 'clusterSize' of null

Cura 3.0.3 Appimage can not even discover my Ultimaker 3 Extended printer anyore. Again, new release, things are getting worse. The 2.7.0 Appimage at least saw the printer, when the software managed to pass the splash screen. Excerpt from the last: … 2017-10-23 04:00:34,938 - WARNING - UM.Settings.ContainerStack.addMetaDataEntry [162]: Meta data with key machine was already added. 2017-10-23 04:00:34,939 - DEBUG - UM.Settings.ContainerRegistry.load [228]: Loading data into container registry took 15.746948003768921 seconds 2017-10-23 04:00:35,485 - DEBUG - UM.Controller.setActiveView [84]: Setting active view to SolidView 2017-10-23 04:00:37,902 - DEBUG - UM.Qt.Bindings.Theme.load [163]: Loading theme file: /tmp/.mount_3heCGt/usr/bin/resources/themes/cura-light/theme.json 2017-10-23 04:00:38,073 - DEBUG - UM.Qt.Bindings.Theme.load [231]: Loaded theme /tmp/.mount_3heCGt/usr/bin/resources/themes/cura-light 2017-10-23 04:00:39,007 - DEBUG - UM.Controller.setActiveView [84]: Setting active view to SolidView 2017-10-23 04:00:39,277 - WARNING - UM.Qt.Bindings.Theme.getIcon [109]: No icon tool_icon.svg defined in Theme 2017-10-23 04:00:39,472 - WARNING - UM.Qt.Bindings.Theme.getIcon [109]: No icon tool_icon.svg defined in Theme 2017-10-23 04:00:39,473 - WARNING - UM.Qt.Bindings.Theme.getIcon [109]: No icon tool_icon.svg defined in Theme 2017-10-23 04:00:39,513 - DEBUG - OctoPrintPlugin.DiscoverOctoPrintAction._createAdditionalComponentsView [218]: Creating additional ui components for OctoPrint-connected printers. 2017-10-23 04:00:39,533 - DEBUG - UM3NetworkPrinting.DiscoverUM3Action._createAdditionalComponentsView [138]: Creating additional ui components for UM3. 2017-10-23 04:00:39,637 - DEBUG - UM3NetworkPrinting.DiscoverUM3Action.startDiscovery [38]: Starting printer discovery. 2017-10-23 04:00:39,792 - DEBUG - UM.Mesh.MeshData.approximateConvexHull [392]: approximateConvexHull(target_count=1024) Calculating 3D convex hull took 0.013724803924560547 seconds. 121 input vertices. 121 output vertices. 2017-10-23 04:00:40,417 - DEBUG - UM.Qt.QtRenderer._initialize [172]: Support for Vertex Array Objects: True 2017-10-23 04:00:40,426 - DEBUG - UM.View.GL.OpenGL.__init__ [85]: Initialized OpenGL subsystems. 2017-10-23 04:00:40,427 - DEBUG - UM.View.GL.OpenGL.__init__ [86]: OpenGL Version: 4.5 (Core Profile) Mesa 17.0.7 2017-10-23 04:00:40,428 - DEBUG - UM.View.GL.OpenGL.__init__ [87]: OpenGL Vendor: Intel Open Source Technology Center 2017-10-23 04:00:40,429 - DEBUG - UM.View.GL.OpenGL.__init__ [88]: OpenGL Renderer: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) 2017-10-23 04:00:40,430 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/default.shader]... 2017-10-23 04:00:40,435 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/selection.shader]... 2017-10-23 04:00:40,438 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/default.shader]... 2017-10-23 04:00:40,443 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/composite.shader]... 2017-10-23 04:00:40,452 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/overhang.shader]... 2017-10-23 04:00:40,463 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/striped.shader]... 2017-10-23 04:00:40,479 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/default.shader]... 2017-10-23 04:00:40,484 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/grid.shader]... 2017-10-23 04:00:40,490 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/tmp/.mount_3heCGt/usr/bin/resources/shaders/platform.shader]... 2017-10-23 04:00:48,457 - DEBUG - UM3NetworkPrinting.DiscoverUM3Action.reset [46]: Reset the list of found printers. 2017-10-23 04:00:49,976 - DEBUG - UM3NetworkPrinting.NetworkPrinterOutputDevicePlugin.stop [208]: zeroconf close... 2017-10-23 04:00:55,441 - DEBUG - AutoSave.AutoSave._onTimeout [48]: Autosaving preferences, instances and profiles 2017-10-23 04:00:58,759 - INFO - cura.CuraApplication.closeApplication [377]: Close application 2017-10-23 04:00:58,762 - DEBUG - UM.Qt.QtApplication.windowClosed [300]: Shutting down cura 2017-10-23 04:00:58,766 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [232]: Attempting to kill the engine process 2017-10-23 04:00:58,766 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [238]: Killing engine process 2017-10-23 04:00:58,767 - DEBUG - CuraEngineBackend.CuraEngineBackend._terminate [241]: Engine process is killed. Received return code -15

That is exactly my point - that is all what Cura logs to ~/.local/share/cura/2.7/cura.log. The logfile ends with "DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/cura/resources/shaders/grid.shader]..."

I really can not get these two pieces of information together… you say that "thousands of users are able to connect with Cura using the appimage", but on the other hand you say that "there aren't enough users on Linux for us to be able to invest into getting those packages up and running". Now what is it, "thousends of users" or not enough users on Linux? Logfiles and Shell messages have been posted above. So far, nobody bothered to comment on these chunks of information.

Really? Last time I checked, it worked perfectly for 51000 software packages. And Debian's package manager works fine on my servers for over a decade. Among others, the errors I get from the current Appimage of Cura 2.7.0 are: Does not accept print jobs - Cura reports "Unable to start a new print job, printer is busy. Current printer status is booting", but printer is not booting. Preferences report inconsistently: "Connection: Connected over the network. State: Waiting for a printjob", but print jobs are not accepted because of the error above. Network connectivity is broken - "The connection with the printer was lost. Check your printer to see if it is connected", but printer is online and can be pinged. I'd say this acually has something to to with the Appimage and how it incorrectly reads/interprets status messages. However, the question is how can I print something on this €4500 device?!

Appimages are generally crap because they introduce harmful redundundancy to a perfectly fine operating system, are not integrated into Debian's elaborate mechanisms for sane file & package management and updating, they waste disk space and bandwidth, pose an inherent security risk through through outdated software duplicates that will never be updated as an Appimage is not handled by package management, and Appimages are neither integrated into the operating system nor the UI. It is just software engineering at it's worst. Also, the Appimage provided by Ultimaker is horribly slow, which makes using features like the layer view impossible. And worst of all, it simply does not work most of the time. To verify these claims I downloaded the current "Cura-2.7.0.AppImage" which has an idiotic size of 107.4 megabytes. After making it executable, it sometimes startes beyond the splash screen; usually it just silently dies. If it manages to go beyond the splash screen, it reproducably fails to communicate with the printer like so: Status message: "Unable to start a new print job, printer is busy. Current printer status is booting" This is complete nonsense. In this case, the printer was neither busy nor booting. It was started 30 minutes ago. That's what Cura reported after claiming to be unable to start a new print job: "Connection: Connected over the network. State: Waiting for a printjob". So the Cura Appimage is not even consistent how to interpret the status messages. Next try. Rebooted the printer, waited for about ten minutes, restarted Cura. Now Cura reports: "The connection with the printer was lost. Check your printer to see if it is connected." That's why I say that the Appimage is crap and why I do not want to start trying to debug the Appimage. It already fails on the most basic level - consistently, over the past months. Sorry, compiling and debugging a faulty software is beyond what I am willing to do. I have paid EUR 4,500 to obtain a productive solution for 3d printing, not a development kit for playing. Now back to Thopiekar's PPA version which at least justifies debugging attempts. Here is the output when starting the debinized Cura 2.7.0 from the shell: […] Thread 0x00007fb7f4db2700 (most recent call first): File "/usr/lib/python3.5/threading.py", line 293 in wait File "/usr/lib/python3.5/threading.py", line 424 in acquire File "/usr/lib/python3/dist-packages/UM/JobQueue.py", line 86 in _nextJob File "/usr/lib/python3/dist-packages/UM/JobQueue.py", line 116 in run File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x00007fb7f55b3700 (most recent call first): File "/usr/lib/python3.5/threading.py", line 293 in wait File "/usr/lib/python3.5/threading.py", line 424 in acquire File "/usr/lib/python3/dist-packages/UM/JobQueue.py", line 86 in _nextJob File "/usr/lib/python3/dist-packages/UM/JobQueue.py", line 116 in run File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x00007fb7f5db4700 (most recent call first): File "/usr/lib/python3/dist-packages/UM/Backend/Backend.py", line 156 in _storeStderrToLogThread File "/usr/lib/python3.5/threading.py", line 862 in run File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x00007fb7f65b5700 (most recent call first): File "/usr/lib/python3/dist-packages/UM/Backend/Backend.py", line 148 in _storeOutputToLogThread File "/usr/lib/python3.5/threading.py", line 862 in run File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x00007fb7f75b7700 (most recent call first): File "/usr/lib/cura/plugins/USBPrinting/USBPrinterOutputDeviceManager.py", line 88 in _updateThread File "/usr/lib/python3.5/threading.py", line 862 in run File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x00007fb810ad7700 (most recent call first): File "/usr/lib/cura/plugins/RemovableDriveOutputDevice/RemovableDrivePlugin.py", line 58 in _updateThread File "/usr/lib/python3.5/threading.py", line 862 in run File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x00007fb8112d8700 (most recent call first): File "/usr/lib/python3.5/threading.py", line 297 in wait File "/usr/lib/python3/dist-packages/zeroconf.py", line 1569 in wait File "/usr/lib/python3/dist-packages/zeroconf.py", line 1153 in run File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x00007fb811ad9700 (most recent call first): File "/usr/lib/python3.5/threading.py", line 297 in wait File "/usr/lib/python3/dist-packages/zeroconf.py", line 1569 in wait File "/usr/lib/python3/dist-packages/zeroconf.py", line 1017 in run File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap Thread 0x00007fb8122da700 (most recent call first): File "/usr/lib/python3/dist-packages/zeroconf.py", line 946 in run File "/usr/lib/python3.5/threading.py", line 914 in _bootstrap_inner File "/usr/lib/python3.5/threading.py", line 882 in _bootstrap Current thread 0x00007fb8577a0700 (most recent call first): File "/usr/lib/python3/dist-packages/UM/Qt/ListModel.py", line 63 in setItems File "/usr/lib/python3/dist-packages/cura/Settings/ExtrudersModel.py", line 224 in __updateExtruders File "/usr/lib/python3/dist-packages/cura/CuraApplication.py", line 682 in run File "/usr/bin/cura", line 73 in Speicherzugriffsfehler (Speicherabzug geschrieben) The last message means: "Memory access error (memory dumped)". As the current Appimage, the current PPA is not operational.

@ smartavionics: The "Appimage" has never worked, not even remotely. It always failed to do anything but to waste a lot of bandwidth for downloading. There is an older thread from a few months ago about it: https://ultimaker.com/en/community/50064-um3-extended-either-no-network-or-not-slicing-which-cura-version-works Thopiekar's PPA is usually magnitudes better, e.g. it actually creates a logfile; and it - so far - mostly worked, except for some "glitches" like losing network connectivity after a couple of hours or sometimes not being able to find a WLAN'd Ultimaker on the network, or (recently) the dead slicer. The "only" problem with the PPA is that it keeps being a moving target; even if there are no updates, different glitches occur erratically. But it basically used to work. The Appimage does not. And as far as I can tell, that faulty slicer is not new, either, it was inherited from Cura 1.x where this has been a major issue for years, long before there even was a PPA. The issue with the current Cura 2.7.0 is that it (again) does not migrate settings from Cura 2.6.x and crashes after the splash screen, when asking to select a printer. What the logfile records is just gibberish to me, at least I do not see a fatal error being logged that would explain why the software dies during startup.

This crap still does not work.

The PPA is supposed to be supported by Ultimaker as the programmer is an intern. As I mentioned elsewhere, the existence of this repository was the only reason to buy an UM 3 Extended.

Schade, daß im letzten Vierteljahr nicht an diesen Problemen gearbeitet wurde, die seit mittlerweile über neun Monaten bekannt sind. Cura 2.7.0 läßt sich gar nicht erst starten…

@smartavionics: The last time I could successfully use Cura was in June 2017. Version 2.6.4 from PPA did not slice anything, but did not crash. It just would not generate something that could be printed. The 2.7.0 "upgrade" was rolled out a few days ago. This version crashes when starting the software (splash screen loads, then it tries to "connect to networked printer", then it crashes). It's just ridiculous, a €4,500 device that can not be used for over four months because of faulty software and a buggy networking stack.

Hi, today I "upgraded" to Cura 2.7.0 from PPA (Ubuntu 17.04). The software immediately crashes when starting. Last recorded messages from logfile: 2017-10-11 00:54:42,498 - DEBUG - UM3NetworkPrinting.NetworkPrinterOutputDevicePlugin._onServiceChanged [210]: Bonjour service added: ultimakersystem-ccbdd30030ac._ultimaker._tcp.local. 2017-10-11 00:54:49,665 - DEBUG - UM.Settings.ContainerRegistry.load [214]: Loading data into container registry took 7.361455917358398 seconds 2017-10-11 00:54:49,666 - WARNING - cura.Settings.CuraContainerRegistry._fixupExtruders [405]: Could not find machine Ultimaker 3 Extended for extruder ultimaker3_extended_extruder_left #2 2017-10-11 00:54:49,666 - WARNING - cura.Settings.CuraContainerRegistry._fixupExtruders [405]: Could not find machine Ultimaker 3 Extended for extruder ultimaker3_extended_extruder_right #2 2017-10-11 00:54:49,667 - DEBUG - UM.Backend.Backend._logSocketState [178]: Socket state changed to Connected 2017-10-11 00:54:49,668 - DEBUG - UM.Backend.Backend._onSocketStateChanged [168]: Backend connected on port 49674 2017-10-11 00:54:49,670 - DEBUG - UM.Controller.setActiveView [84]: Setting active view to SolidView 2017-10-11 00:54:50,062 - DEBUG - UM.Qt.Bindings.Theme.load [165]: Loading theme file: /usr/share/cura/resources/themes/cura/theme.json 2017-10-11 00:54:50,117 - DEBUG - UM.Qt.Bindings.Theme.load [232]: Loaded theme /usr/share/cura/resources/themes/cura 2017-10-11 00:54:50,193 - WARNING - cura.Settings.ContainerManager.getContainerMetaDataEntry [184]: Could not get metadata of container because it was not found. 2017-10-11 00:54:50,524 - WARNING - UM.Preferences.getValue [81]: Tried to get the value of non-existing setting info/automatic_update_check. 2017-10-11 00:54:50,549 - DEBUG - UM3NetworkPrinting.DiscoverUM3Action._createAdditionalComponentsView [138]: Creating additional ui components for UM3. 2017-10-11 00:54:50,569 - DEBUG - UM3NetworkPrinting.DiscoverUM3Action.startDiscovery [38]: Starting printer discovery. 2017-10-11 00:54:50,747 - DEBUG - UM.Qt.QtRenderer._initialize [172]: Support for Vertex Array Objects: True 2017-10-11 00:54:50,751 - DEBUG - UM.View.GL.OpenGL.__init__ [85]: Initialized OpenGL subsystems. 2017-10-11 00:54:50,751 - DEBUG - UM.View.GL.OpenGL.__init__ [86]: OpenGL Version: 4.5 (Core Profile) Mesa 17.0.7 2017-10-11 00:54:50,751 - DEBUG - UM.View.GL.OpenGL.__init__ [87]: OpenGL Vendor: Intel Open Source Technology Center 2017-10-11 00:54:50,751 - DEBUG - UM.View.GL.OpenGL.__init__ [88]: OpenGL Renderer: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) 2017-10-11 00:54:50,751 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/uranium/resources/shaders/default.shader]... 2017-10-11 00:54:50,756 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/uranium/resources/shaders/selection.shader]... 2017-10-11 00:54:50,759 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/uranium/resources/shaders/default.shader]... 2017-10-11 00:54:50,761 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/uranium/resources/shaders/composite.shader]... 2017-10-11 00:54:50,769 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/cura/resources/shaders/overhang.shader]... 2017-10-11 00:54:50,778 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/cura/resources/shaders/striped.shader]... 2017-10-11 00:54:50,788 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/uranium/resources/shaders/platform.shader]... 2017-10-11 00:54:54,103 - INFO - cura.Settings.GlobalStack.addExtruder [81]: Extruder[ultimaker3_extended_extruder_left #3] added to [ultimaker 3 Extended] at position [0] 2017-10-11 00:54:54,133 - INFO - cura.Settings.GlobalStack.addExtruder [81]: Extruder[ultimaker3_extended_extruder_right #3] added to [ultimaker 3 Extended] at position [1] 2017-10-11 00:54:54,788 - DEBUG - UM3NetworkPrinting.DiscoverUM3Action.reset [46]: Reset the list of found printers. 2017-10-11 00:54:54,833 - DEBUG - UM.Mesh.MeshData.approximateConvexHull [392]: approximateConvexHull(target_count=1024) Calculating 3D convex hull took 0.018415212631225586 seconds. 121 input vertices. 121 output vertices. 2017-10-11 00:54:54,842 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/uranium/resources/shaders/default.shader]... 2017-10-11 00:54:54,845 - DEBUG - UM.View.GL.ShaderProgram.load [55]: Loading shader file [/usr/share/cura/resources/shaders/grid.shader]... Any suggestions? Thanks!

Bei mir ist der aktuelle Status folgendermaßen: "Ultimaker 3"-App funktioniert überhaupt nicht - keine Verbindung zum Ultimaker; Verbindung über Ethernet und Switch - funktioniert mit APIPA-Adresse manchmal und teilweise; Verbindung über WLAN - funktioniert mit APIPA-Adresse manchmal und teilweise. Etwas besser wird es, wenn man dem UM3 eine statische IP-Adresse beigbracht hat. Dann findet ihn die UM3-App, und Firmware-Updates über Cura und Ethernet sind auch möglich, manchmal jedenfalls. "Manchmal" bedeutet, daß ich oft genau einen Druckjob über Cura und das Netzwerk an den UM3 schicken kann. Der wird dann auch brav zuende gebracht - nur kann der UM3 nicht korrekt mit Cura kommunizieren. Typische Fehlermeldung: "Unable to start a new print job, printer is busy. Current printer status is printing". Das stimmt nicht, der Druck wurde gerade erfolgreich beendet, die Statusabfrage ist also kaputt. Dann muß ich Cura neu starten und manchmal geht es dann wieder. Manchmal aber auch nicht. Es ist hit & miss. Um den UM3 in ein WLAN zu bekommen, brauchst du idealerweise einen DHCP-Server, der ihm eine IP-Adresse aus dem Adresspool zuweist. Hast du keinen DHCP-Server, bekommst du eine APIPA-Adresse, die zu funktionalen Einschränkungen führt (z.B. keine Firmware-Updates möglich). Um das zu umgehen, musst du dich per SSH auf dem Ultimaker einloggen und dort mit der "ConnMan"-Software eine statische Netzwerk-Konfiguration durchführen. Außerdem zu beachten ist, daß Ethernet und Wireless im UM3 zwei unterschiedliche Schnittstellen sind, die nicht parallel betrieben werden können. Also entweder Ethernet oder Wireless. Beide Netzwerkschnittstellen haben unterschiedliche MAC-Adressen; wenn du also in deinem WLAN auf MAC-Adressen filterst, mußt du die Adresse der Wireless-Schnittstelle freischalten. Welche Netzwerkschnittstelle aktiv ist, stellst du über das Display des UM3 ein. Falls du mit "ConnMan" die Netzerkkonfiguration einstellen möchtest, muß du das für beide Schnittstellen separat machen. Ist das so, wie es bei einem Consumer-Gerät mit fürstlichem Preisschild sein sollte? Sicherlich nicht. Es besteht aber die Hoffnung, daß die zahlreichen "Kinderkrankheiten" der Netzwerk-Funktionalität beseitigt werden. Und ich bete, daß das noch im UM3 und nicht erst im UM4 passiert…

Der Netzwerk-Teil des UM3 ist, freundlich gesagt, noch ziemlich unausgereift. Es werden unzählige Annahmen über die erwartete Umgebung gemacht, die aber natürlich nirgendwo dokumentiert sind. Bei der Ethernet-Schnittstelle wird beispielsweise einfach davon ausgegegangen, daß IP-Adressen und Konfigurationsinformationen über DHCP vergeben werden. Daß man dem Gerät vielleicht manuell eine statische IP-Adresse geben möchte ist einfach nicht vorgesehen. Technisch möglich ist es schon, nur ist weder dokumentiert, daß der UM3 einen DHCP-Server erwartet, noch daß man die statische IP-Adresse über SSH und "ConnMan" konfigurieren könnte. Bei der WLAN-Schnittstelle ist es dasselbe; man muß raten, was das Ding gerne haben möchte, um sich wohlzufühlen. Genau wie bei dir funktioniert bei mir die WLAN-Konfiguration weder über ein Notebook noch über ein Smartphone so wie beschrieben. In der Dokumentation steht: "A pop-up will appear on the display of your computer", wenn man sich mit dem UM-Hotspt verbunden hat. Das mag auch sein, daß es irgendwo auf der Welt einen Computer gibt, bei dem das der Fall ist (vielleicht war das Windows 98 so?), nur allgemeingültig ist es sicherlich nicht. Bei Linux geht kein Fenster auf, wenn man sich mit einem Hotspot verbindet. Man ruft also einen Webbrowser auf, wenn der UM3 seinen Hotspot aufgemacht und man sich in diesen eingeklinkt hat. Der UM3 biegt dann die Internet-Adresse ultimaker.com auf seine interne Konfigurationsroutine um und man bekommt WLAN-Netzwerke in der Umgebung aufgelistet. Meins war nicht dabei, obwohl der AP direkt neben dem UM3 steht. Also SSID und Passphrase manuell eingeben, der UM3 verbindet sich dann mit deinem WLAN. Bei einem Smartphone - in meinem Falle Android 7.0 - behauptet die (manuelle) WLAN-Konfiguration dann irgendwann: "Ultimaker connection process complete". Nur weiß weder die "Ultimaker 3"-App (Version 1.0.1), noch Cura auf dem Desktop von ihrem Glück. Nun ist die App noch ziemlich neu, und vielleicht ist sie noch buggy; und die Statusabfragen in Cura funktionieren mit Ethernet ja auch nicht zuverlässig. Also wo sitzt der Fehler, in der App, in Cura, in der UM-Firmware oder vor dem Computer? Es ist leider nur schwer herauszubekommen, weil so wenig klar dokumentiert ist.

In case you have not found it yet: At least an Ultimaker 3 will reject to print the Gcode if settings for support material or brim point to extruder 1 (default setting).

I tried the Cura setting for “Shell - Horizontal Expansion”. For a 0.4 mm nozzle size and a layer height of 0.2 mm ("Fast" profile) I guesstimated an offset of -0.2 mm. With this compensation, the InMoov parts now come just right out of the printer; I do not even have to sand them down anymore. Now I just have to grind down all the parts I already have printed in the past weeks, *sigh*. Thanks for pointing me to the "Hoizontal Expansion" setting!

Hi, thanks for your reply. Sorry, I have no idea what "the final siE" or "a rule of three" is. If my UM3+ prints with an offset of approximately 0.3 mm on the X and Y axis, can I just enter "-0.3 mm" in the "Horizontal Expansion" setting to get accurately sized prints? I really do not understand why this problem even happens with such an expensive device like the UM3. InMoov is designed to be printed even on cheap 3D printers, and nobody else seems to have to do these hacks, except for very few people with totally uncalibrated DIY 3D printer kits…

Hi, I am trying to get dimensionally accurate printouts with my factory-fresh UM3. During set-up, I went through the usual calibration procedures - build plate levelling with the "calibration card", and running the "Z and XY offset calibration" with the supplied "XY calibration sheet". My prints look visually good. Print bed adhesion is excellent. I thought everything would be fine. But then I noticed that my UM had severe issues reproducing technical models accurately. This affects dozends of pre-designed models from the InMoov project like RollBackLeftV1.stl RollBackRightV1.stl RollFrontLeftV1.stl RollFrontRightV1.stl These parts need to be interlocked after printing, but they do not fit. The models should be perfeclty fine as they have been printed and built dozends of times in the past years. Some sanding and deburring is required, obviously, but I would have to grind down almost half a millimeter of material to make these parts fit. Gael (the InMoov designer) recommends to calibrate the printer. To do so I downloaded a "STEP Calibration Piece (X, Y and Z axis)" from Thingiverse (https://www.thingiverse.com/thing:195604) The calibration object is 100mm on X and Y axis and 50mm on the Z-Axis. Measured with calipers, my test piece is 100,38 × 100,33 × 50,16 mm, so there actually is an offset. The instructions say: "You can then calibrate your STEPS using this formula: X,Y-Axis: 100 / [measured length in mm] [current STEPS] Z-Axis: X,Y-Axis: 50 / [measured height in mm] [current STEPS]" Where do I find the "current STEPS" value, and where do I enter the corrected values? Thanks!

Hi, some of you might be aware that smoothing PLA with Acetone is possible. I'm doing this for a while with a PLA filament from "ICE" in color "wondrous white". First some sanding, then brushing a couple of layers with acetone. It looks like this: This is a detail: I belive this works because PLA is just a category for polylactides, not a precisely defined substance. Or the PLA filaments available on the market could be blends that include a portion of different materials like ABS. However, not all PLA filaments respond do acetone equally. I just tried this with the original Ultimaker PLA in color "silver". Before: Detail: …and after applying one coat of acetone: Detail: In this case, it's an unintentional, but somehow cool effect for this small model of the InMoov 3D printed robot. It makes him look nicely worn-out. So, smoothing PLA with acetone is possible - but only in some cases. Manufacturers, please disclose the composition of your filaments! Now I am very cusrious how other PLA filament brands respond to acetone. Next time I will try "REC" and "German RepRap Premium Filament", both PLA and in color white. Maybe it will give me rainbow colors

Hi, for some unknown reason, the printer yesterday asked me for authorization when trying to access it with Cura. It has only done this once before - when I switched to developer mode and accessed it through SSH. After allowing myself access to the printer on the UM display, I got a (stable) Ethernet connection and a webcam stream. Today I had to put the printer in a different room without Ethernet, so I don't know if it will remember the access grants. I will report back. I'd suggest to take a look at how Cura triggers this authorization request. It is definitely erratic as I tried to access it numerous times before without getting the authorization question on the UM display. However, I now do know the Ultimaker 3 Extended in combination with Cura 2.6.1 (PPA) can connect via Ethernet and a static IP address. I have seen it with my own eyes, at least once in two weeks ;-) Btw, another suggestion would be to seriously consider to give Thopiekar some support or even hire him as a freelancer to offer an official repository. At least for me, Thopiekar's repository was the decisive reason to buy another Ultimaker. Otherwise I would have chosen an Atom 2.5 EX, an Lulzbot TAZ 3 or an RepRap X350. Though, with auto print bed levelling and PLA I'm currently getting nice prints, so so far no buyer's remorse. asb

Cura writes a logfile? Cool… (searching…) Is it ~/.local/share/cura/cura.log? This is what it says regarding networking. 192.168.178.200 is the static IP address I configured with ConnMan. If the UM is on, I can ping this address. 2017-06-27 18:41:39,172 - DEBUG - UM3NetworkPrinting.NetworkPrinterOutputDevice._onFinished [940]: A reply from http://192.168.178.200/api/v1/auth/verify did not have status code. 2017-06-27 18:41:39,172 - DEBUG - UM3NetworkPrinting.NetworkPrinterOutputDevice._onFinished [940]: A reply from http://192.168.178.200/api/v1/printer did not have status code. 2017-06-27 18:41:39,172 - DEBUG - UM3NetworkPrinting.NetworkPrinterOutputDevice._onFinished [940]: A reply from http://192.168.178.200/api/v1/print_job did not have status code. 2017-06-27 18:41:41,212 - DEBUG - UM3NetworkPrinting.NetworkPrinterOutputDevice._onFinished [940]: A reply from http://192.168.178.200/api/v1/auth/verify did not have status code. 2017-06-27 18:41:41,213 - DEBUG - UM3NetworkPrinting.NetworkPrinterOutputDevice._onFinished [940]: A reply from http://192.168.178.200/api/v1/printer did not have status code. 2017-06-27 18:41:41,213 - DEBUG - UM3NetworkPrinting.NetworkPrinterOutputDevice._onFinished [940]: A reply from http://192.168.178.200/api/v1/print_job did not have status code. 2017-06-27 18:41:43,175 - DEBUG - UM3NetworkPrinting.NetworkPrinterOutputDevice._onFinished [940]: A reply from http://192.168.178.200/api/v1/auth/verify did not have status code. 2017-06-27 18:41:43,175 - DEBUG - UM3NetworkPrinting.NetworkPrinterOutputDevice._onFinished [940]: A reply from http://192.168.178.200/api/v1/printer did not have status code. 2017-06-27 18:41:43,175 - DEBUG - UM3NetworkPrinting.NetworkPrinterOutputDevice._onFinished [940]: A reply from http://192.168.178.200/api/v1/print_job did not have status code. 2017-06-27 18:41:45,171 - DEBUG - UM3NetworkPrinting.NetworkPrinterOutputDevice._update [457]: We did not receive a response for 10.1 seconds, so it seems the printer is no longer accessible. 2017-06-27 18:41:45,172 - WARNING - UM.OutputDevice.OutputDeviceManager.removeOutputDevice [125]: Could not find output device with id ultimakersystem-ccbdd3000d1b._ultimaker._tcp.local. to remove Thanks, asb

Thopiekar's stable PPA has now Cura 2.6.1. Did an update. Printer is connected to the switch: Printer is visible in Cura: Printing via Ethernet results in various errors: Simply no luck :(

Hi, I got a UM3 Extended last Friday; the installed firmware was dated (3.4.16.20161104). Downloaded more recent firmware from ultimaker.com website and updated the firmware from USB stick to the current 3.6.3.20170406. Updating appears to have worked, at least there were no error messages. Next, connected the UM to a switch via Ethernet, found out that UM can has no UI to set up networking and gets a bogus "link local" APIPA address (segment 169.254.0.0); switched into "developer mode" and accessed UM via SSH; configured a static IP address, netmask and gateway from the proper segment (192.168.0.0) with "ConnMan"; left "developer mode" and rebooted. Now I can ping the UM. It even remembers the IP address after rebooting. However, getting Cura to communicate with the UM turned out to be not impossible. I'm running Cura 2.5.0 stable (PPA) from https://launchpad.net/~thopiekar/+archive/ubuntu/cura on Ubuntu 17.04 "Zesty" with Mate desktop. Cura sees the printer and displays even it's IP address, but can not connect to the printer. No webcam image, nothing. But it can slice a file and write Gcode onto an USB stick. Purged Thopiekar's stable PPA and "updated" to Cura 2.5.99 master (PPA) from https://launchpad.net/~thopiekar/+archive/ubuntu/cura-master. Now Cura can sometimes connect to the printer, at least for a few seconds; it displays the UM's IP address and, if connecting to the printer succeeds, it even shows a webcam image. However, when loading an object, Cura (claims to) start slicing, but shows no progress. It can not slice even the smallest files. Turned off automatic slicing in Cura's preferences, then it says: "Ready to slice" and there is a "Pepare" button. Clicking on "Prepare" starts to slice, but nothing happens - no progress, no finished Gcode. Purged the master PPA as well, downloaded an "AppImage" from ultimaker.com. That cura version says it's Cura 2.6.0, but it behaves like 2.5 from Thopiekar's stable PPA: No networking, but it slices. So now I have a 3D printer for 4,500 Euros and I need to choose if I either want networking or slicing. These are not great options, considering the price range of this supposedly "ready to run" 3D printer. So I chose slicing and went ahead with the the factory default profiles embedded in Cura; let Cura write the Gcode to an USB stick, put the US stick into the UM and kindly asked it to print. Then the UM started throwing errror messages like: "Material expected to be used by PrintCore in head slot 1, but no material loaded. Please load material". That error message was misleading since PLA filament was loaded onto both extruders/PrintCores. So I chose "Ignore". Then UM started active levelling, reported "Heating build plate … Printing" - but only very little or no filament at all came out of the nozzle. Let's call it a severe case over under extrusion (with the factory default profiles). Aborted the print job, restarted it. Now active levelling failed with the error message: "Difference between detected height of both PrintCores exceeds realistic". Next I tried manual levelling and checked the "manual levelling" setting in the printer menu, but with the next print, the UM started auto-levelling nonetheless. Tried that repeatedly, sometimes auto-levelling works, sometimes it fails. It's totally erratic. After wasting a lot of time with this UM3 Extended I have two questions: 1) The UM3 Extended is on the market for over half a year. Is it supposed to behave like this, or do I need to consider the possibility of a hardware defect? 2) What is the recommended Cura version to run on Linux together with an UM3 Extended at the moment? Having to choose between either networking or slicing is not very reasonable. Is it possible to get Cura 2.5.99-master to slice an object file, or is that functionality currently broken? Or is it possible to get Cura 2.5.0-stable to connect to the UM via Ethernet? Thanks, asb