Jump to content
Ultimaker Community of 3D Printing Experts
asb

Cura 2.1 broken dependencies on Ubuntu 16.04 LTS

Recommended Posts

Cura 2.1 does not start on Ubuntu 16.04 LTS.

Ubuntu version:

 

$ lsb_release -aNo LSB modules are available.Distributor ID: UbuntuDescription: Ubuntu 16.04 LTSRelease: 16.04Codename: xenial

 

OpenGL version:

 

$ glxinfo | grep OpenGLOpenGL vendor string: Intel Open Source Technology CenterOpenGL renderer string: Mesa DRI Intel® HD Graphics 530 (Skylake GT2) OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.2.0OpenGL core profile shading language version string: 3.30OpenGL core profile context flags: (none)OpenGL core profile profile mask: core profileOpenGL core profile extensions:OpenGL version string: 3.0 Mesa 11.2.0OpenGL shading language version string: 1.30OpenGL context flags: (none)OpenGL extensions:OpenGL ES profile version string: OpenGL ES 3.1 Mesa 11.2.0OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10OpenGL ES profile extensions:

 

That matches the system requirements as given here.

According to the FAQ I added the PPA as mentioned in https://ultimaker.com/en/resources/21362-cura-2-1-linux-not-working and tried a "reset" according to this description.

When Cura is started, a splash screen shows up for a fraction of a second. Nothing else happens.

From shell, starting Cura looks like this:

 

$ cura2016-06-21 16:11:18,545 - INFO - Loaded plugin ConsoleLogger2016-06-21 16:11:18,550 - INFO - Loaded plugin CuraEngineBackend2016-06-21 16:11:18,551 - WARNING - Plugin ConsoleLogger was already loaded2016-06-21 16:11:18,552 - INFO - Loaded plugin FileLogger2016-06-21 16:11:18,555 - INFO - Loaded plugin LocalFileOutputDevice2016-06-21 16:11:18,557 - INFO - Loaded plugin STLWriter2016-06-21 16:11:18,561 - INFO - Loaded plugin 3MFWriter2016-06-21 16:11:18,563 - INFO - Loaded plugin OBJReader2016-06-21 16:11:18,565 - INFO - Loaded plugin OBJWriter2016-06-21 16:11:18,567 - INFO - Loaded plugin STLReader2016-06-21 16:11:18,570 - INFO - Loaded plugin SelectionTool2016-06-21 16:11:18,574 - INFO - Loaded plugin MirrorTool2016-06-21 16:11:18,579 - INFO - Loaded plugin TranslateTool2016-06-21 16:11:18,584 - INFO - Loaded plugin RotateTool2016-06-21 16:11:18,587 - INFO - Loaded plugin CameraTool2016-06-21 16:11:18,591 - INFO - Loaded plugin ScaleTool2016-06-21 16:11:18,593 - INFO - Loaded plugin WireframeView2016-06-21 16:11:18,595 - INFO - Loaded plugin SimpleView2016-06-21 16:11:18,597 - INFO - Loaded plugin CuraProfileReader2016-06-21 16:11:18,599 - INFO - Loaded plugin ChangeLogPlugin2016-06-21 16:11:18,599 - WARNING - Plugin CuraEngineBackend was already loaded2016-06-21 16:11:18,601 - INFO - Loaded plugin AutoSave2016-06-21 16:11:18,604 - INFO - Loaded plugin RemovableDriveOutputDevice2016-06-21 16:11:18,608 - INFO - Loaded plugin ImageReader2016-06-21 16:11:18,611 - INFO - Loaded plugin 3MFReader2016-06-21 16:11:18,613 - INFO - Loaded plugin LegacyProfileReader2016-06-21 16:11:18,615 - INFO - Loaded plugin CuraProfileWriter2016-06-21 16:11:18,631 - INFO - Loaded plugin SliceInfoPlugin2016-06-21 16:11:18,634 - INFO - Loaded plugin XRayView2016-06-21 16:11:18,636 - INFO - Loaded plugin SolidView2016-06-21 16:11:18,639 - INFO - Loaded plugin GCodeWriter2016-06-21 16:11:18,642 - INFO - Loaded plugin PerObjectSettingsTool2016-06-21 16:11:18,649 - INFO - Loaded plugin USBPrinting2016-06-21 16:11:18,653 - INFO - Loaded plugin GCodeProfileReader2016-06-21 16:11:18,656 - INFO - Loaded plugin LayerView2016-06-21 16:11:18,656 - INFO - Command line arguments: {'disable-textures': False, 'external-backend': False, 'debug-mode': False, 'file': []}2016-06-21 16:11:18,777 - DEBUG - Attempting to kill the engine process2016-06-21 16:11:18,893 - DEBUG - Attempting to kill the engine process2016-06-21 16:11:18,894 - DEBUG - Setting active view to SolidView2016-06-21 16:11:18,929 - INFO - Started engine process: /usr/bin/CuraEngineQQmlApplicationEngine failed to load componentfile:///usr/share/cura/resources/qml/Cura.qml:660 Type FileDialog unavailableqrc:/QtQuick/Dialogs/DefaultFileDialog.qml:44 module "Qt.labs.folderlistmodel" is not installedqrc:/QtQuick/Dialogs/DefaultFileDialog.qml:45 module "Qt.labs.settings" is not installedqrc:/QtQuick/Dialogs/DefaultFileDialog.qml:44 module "Qt.labs.folderlistmodel" is not installedqrc:/QtQuick/Dialogs/DefaultFileDialog.qml:45 module "Qt.labs.settings" is not installed2016-06-21 16:11:19,101 - DEBUG - Backend connected on port 496762016-06-21 16:11:29,047 - DEBUG - Autosaving preferences, instances and profiles2016-06-21 16:11:29,048 - WARNING - No active machine found when trying to save setting visibility

 

The Cura package is broken as it does not resolve the required dependencies.

You can install the missing dependencies manually by issuing:

 

$ sudo aptitude install qml-module-qt-labs-folderlistmodel$ sudo aptitude install qml-module-qt-labs-settings

 

However, even after resolving this, the software does nothing. It starts a GUI that allows to drag & drop an object, but it doesn't do anything else:

cura-21.png.a0268c5c83287e1e46d864cbe326fe78.png

There is no progress indicator, and the output doesn't change for hours.

cura-21.png.a0268c5c83287e1e46d864cbe326fe78.png

Edited by Guest

Share this post


Link to post
Share on other sites

Part of this is also Ubuntu maintainers being freakishly horrible at maintaining packages. For some unknown reason they decided to drop python 3.4 (and switch over to 3.5). This won't cause issues for their system, but if we suddenly start working with 3.5, we also need to do that on other systems, which causes issues there.

You can just use the ppa made by thopiekar. That should work as intended.

Share this post


Link to post
Share on other sites
You can just use the ppa made by thopiekar. That should work as intended.

 

No, it does not. As mentioned above, this PPA is exactly what I am using. Manually installing the dependencies qml-module-qt-labs-folderlistmodel and qml-module-qt-labs-settings allows Cura only to load beyond the Splash screen.

IT DOES NOT DO ANYTHING besides showing a GUI with menus. It does NOT allow to save GCode. The printer firmware can NOT be updated. Loading STL files > 10 MB causes Cura to crash instantly, leaving zombies in system memory.

Cura 2.1.2-0 for Linux is neither production ready, nor beta. It's pre-alpha software.

Edited by Guest

Share this post


Link to post
Share on other sites
Cura 2.1.2-0 for Linux is neither production ready, nor beta. It's pre-alpha software.

Wow - big words!!!

Please tell me how I managed to work with 2.1.2 for nearly a month now on Ubuntu 16.04 using topiekars PPA ...

Have you ever read the link I gave you above?!?

Did you try to install the dependencies mentioned in this link:

 

sudo apt install qml-module-qtquick-dialogs qml-module-qtquick-controls

 

?

Have you ever made an update for this PPA?

Edited by Guest

Share this post


Link to post
Share on other sites
Have you ever read the link I gave you above?!?

 

Yes.

 

Have you ever read the link I gave you above?!?

Did you try to install the dependencies mentioned in this link:

 

sudo apt install qml-module-qtquick-dialogs qml-module-qtquick-controls

 

?

 

I already mentioned in my initial post that these missing dependencies have to be installed manually. So yes, of course. Without manually installing these packages, Cura does not even start a GUI.

 

$ sudo aptitude install qml-module-qtquick-dialogs qml-module-qtquick-controls»qml-module-qtquick-dialogs« ist bereits in der angeforderten Version (5.5.1-1ubuntu1) installiert.»qml-module-qtquick-controls« ist bereits in der angeforderten Version (5.5.1-1ubuntu1) installiert.»qml-module-qtquick-dialogs« ist bereits in der angeforderten Version (5.5.1-1ubuntu1) installiert.»qml-module-qtquick-controls« ist bereits in der angeforderten Version (5.5.1-1ubuntu1) installiert.Es werden keine Pakete installiert, aktualisiert oder entfernt.

 

 

Have you ever made an update for this PPA?

 

I can not update the PPA, only the maintainer can do this.

Yes, I'm running

$ sudo aptitude update ; sudo aptitude safe-upgrade ; sudo aptitude dist-upgrade
on a daily basis. Result:

cura-2120.thumb.png.518231d38af5a314c3d564d1e49cedb3.png

cura-2120.thumb.png.518231d38af5a314c3d564d1e49cedb3.png

Edited by Guest

Share this post


Link to post
Share on other sites

Great to see my PPA is useful for you :)

The problem with the missing dependencies has been solved. You can mark these packages as "automatically installed" by "apt-mark auto ", so they will be removed in case they won't be needed in the far future. (Just in case..)

@asb I can confirm it works great here, BUT it might be possible that your old settings are playing on your nerves. So I recommend to remove ~/.config/cura/* and ~/.local/cura/*.

If there are important changes you've done to your profile(s) make sure you export them before removing these directories. Removing them will do a "factory reset".

Share this post


Link to post
Share on other sites

@thopiekar: Yes, your PPA is definitely useful as having to manually download software packages and taking care of manually updating them is quite bizarre in the Debian/Ubuntu world. Making use of the "cura-engine" package that is in Ubuntu/Debian archives for years, but was never used by the pre-packaged archives provided for download is another plus.

The issues I'm continuing to encounter with Ultimaker and the Cura software are not caused by your PPA. The missing dependencies were a minor glitch. A major glitch is in the Cura software itself which doesn't give error messages (e.g. when it can not start), which seems not to write an error log, and especially which does not give useable status updates if it does something or silently died hours or days ago (yes, some larger objects take days to process, and some never finish). This was the case for previous release and has not been fixed yet. These are general issues with Cura.

Another major issue is in the UM hardware itself. It's just plain stupid that an updated firmware can not be read from the SD card. This would allow to avoid to work around USB issues as those mentioned above (lsusb lists the UM as Arduino Mega, as far as I remember, so a connection is there, Cura "just" can not send the updated firmware to the printer). This is a general issue with the UM hardware. It's bad hardware design.

I believe that I am encountering a special issue on top of the general issues mentioned above. Cura always had major problems to deal with STL files >100 MB. There appear to be undocumented limitations about the file size and/or complexity of the object.

To work around these assumed file size/object complexity limitations which I can not quantify resonably, I created a most simple object. As mentioned above, it is 684 Bytes small. This file can not be processed with Cura 15.04.6 either. If anyone is willing to verify this: Please create a object with a size of 222 x 222 x 1 mm. Without raft and without brim this should fit into the build space of the UM2+ which is specified to 223 x 223 x 205 mm. None of the current cura versions allow me to generate GCode from this file. Previous versions of Cura allowed to write GCode for objects like this, but then the UM2+ would throw an error and abort printing.

If I click on "Maximize" in 15.04.6, Cura scales the object down to 212.8 x 212.8 x 1.0 mm, but still does not allow to write Gcode. Only if I manually decrese the object further to smoething like 200 x 200 x 0.9 mm, I can write GCode with Cura 15.04.6. I can not check this with the PPA as I have disabled it yesterday (I just need to get that thing working again).

Edited by Guest

Share this post


Link to post
Share on other sites

@thopiekar: Yes, your PPA is definitely useful as having to manually download software packages and taking care of manually updating them is quite bizarre in the Debian/Ubuntu world. Making use of the "cura-engine" package that is in Ubuntu/Debian archives for years, but was never used by the pre-packaged archives provided for download is another plus.

Thanks!

The issues I'm continuing to encounter with Ultimaker and the Cura software are not caused by your PPA. The missing dependencies were a minor glitch. A major glitch is in the Cura software itself which doesn't give error messages (e.g. when it can not start), which seems not to write an error log, and especially which does not give useable status updates if it does something or silently died hours or days ago (yes, some larger objects take days to process, and some never finish). This was the case for previous release and has not been fixed yet. These are general issues with Cura.

You'll need to run cura from the console. Just type in "cura" or check the logs at ~/.local/share/cura.

Another major issue is in the UM hardware itself. It's just plain stupid that an updated firmware can not be read from the SD card. This would allow to avoid to work around USB issues as those mentioned above (lsusb lists the UM as Arduino Mega, as far as I remember, so a connection is there, Cura "just" can not send  the updated firmware to the printer). This is a general issue with the UM hardware. It's bad hardware design.

Well, I wouldn't call the hardware "bad". It is absolutely able to do the job(!). Unfortunately Cura is just not able to flash the board. There could be different reasons:

1. There is a bug in Cura.

2. You don't have permissions to flash your Ultimaker! (and sadly Cura doesn't tell something about this). Make sure your user account is member of the "dialout" group. (It is also possible that I made other changes here in order to flash my Arduinos.)

I believe that I am encountering a special issue on top of the general issues mentioned above. Cura always had major problems to deal with STL files >100 MB. There appear to be undocumented limitations about the file size and/or complexity of the object.

Please add a issue report on this at GitHub plus your model. I've got here one from an different site, which is >200MB, and I use that file often as the "worst case", when testing new Cura features.

To work around these assumed file size/object complexity limitations which I can not quantify resonably, I created a most simple object. As mentioned above, it is 684 Bytes small. This file can not be processed with Cura 15.04.6 either. If anyone is willing to verify this: Please create a object with a size of 222 x 222 x 1 mm. Without raft and without brim this should fit into the build space of the UM2+ which is specified to 223 x 223 x 205 mm. None of the current cura versions allow me to generate GCode from this file. Previous versions of Cura allowed to write GCode for objects like this, but then the UM2+ would throw an error and abort printing.

Again, report this on GitHub + append your model + add your error message.

If I click on "Maximize" in 15.04.6, Cura scales the object down to 212.8 x 212.8 x 1.0 mm, but still does not allow to write Gcode. Only if I manually decrese the object further to smoething like 200 x 200 x 0.9 mm, I can write GCode with Cura 15.04.6. I can not check this with the PPA as I have disabled it yesterday (I just need to get that thing working again).

No problem. This is also something I worry about: If you are unlucky your are mixing new with old configurations by upgrading and downgrading again. You will need to make a full cleanup to make sure that there are no new settings that might confuse the "old" Cura.

Remove ~/.config/cura and ~/.local/share/cura for this (there might be other locations for the old Cura).

Share this post


Link to post
Share on other sites

OK, uninstalled and purged Cura 15.04.6, deleted ~/.config/cura and ~/.local/share/cura, re-activated the PPA, now back on Cura 2.1.2-0.

Updating the firmware:

2016-06-27 02:14:51,259 - INFO - Updating firmware of /dev/ttyACM0 using /usr/share/cura/resources/firmware/MarlinUltimaker2plus.hex
2016-06-27 02:14:52,400 - ERROR - Unable to connect with serial. Could not update firmware

The user running Cura is member of the "dialout" group.

With UM2+ switched on and connected via USB:

$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 009: ID 2341:0010 Arduino SA Mega 2560 (CDC ACM)

Build space issue: Disabled brim, raft, skirt, and support material. Setting skirt to "0". Scaling the object with "Maximize" results in dimensions 195.0 x 195.0 x 0.9 mm.

In the base plate, Cura steals 28 x 28 mm. That is not a rounding error!

Why can I not use the specified build space of 223 x 223 x 205 mm???

Edited by Guest

Share this post


Link to post
Share on other sites

PS: There is also a PPA built from "master" with nightly builds. If you like you can check out  whether your problems will be fixed in the future 2.2 release.

https://launchpad.net/~thopiekar/+archive/ubuntu/cura-master

But keep in mind: Don't report any issues using these packages to the Ultimaker support. This is still work-in-progress.

If you want to use 2.1 again after using this PPA. Remove all cura packages, remove all local settings again, deactivate the "master" PPA and reinstall 2.1 from the "stable" PPA.

Edited by Guest

Share this post


Link to post
Share on other sites

That's strange. Please copy from the log some more lines. It is possible that there are other messages related to this problem. Thanks!

 

Excerpted from ~/.local/share/cura/cura.log:

 

2016-06-27 02:13:00,580 - INFO - Started engine process: /usr/bin/CuraEngine2016-06-27 02:13:00,602 - DEBUG - Backend connected on port 496742016-06-27 02:13:31,571 - DEBUG - Autosaving preferences, instances and profiles2016-06-27 02:14:40,302 - DEBUG - Attempting to connect to /dev/ttyACM02016-06-27 02:14:40,302 - INFO - Could not establish connection on /dev/ttyACM0: 'Failed to open serial port'. Device is not arduino based.2016-06-27 02:14:40,303 - DEBUG - Attempting to connect to printer with serial /dev/ttyACM0 on baud rate 1152002016-06-27 02:14:40,303 - DEBUG - Attempting to connect to printer with serial /dev/ttyACM0 on baud rate 2500002016-06-27 02:14:40,304 - DEBUG - Attempting to connect to printer with serial /dev/ttyACM0 on baud rate 2304002016-06-27 02:14:40,305 - DEBUG - Attempting to connect to printer with serial /dev/ttyACM0 on baud rate 576002016-06-27 02:14:40,306 - DEBUG - Attempting to connect to printer with serial /dev/ttyACM0 on baud rate 384002016-06-27 02:14:40,306 - DEBUG - Attempting to connect to printer with serial /dev/ttyACM0 on baud rate 192002016-06-27 02:14:40,307 - DEBUG - Attempting to connect to printer with serial /dev/ttyACM0 on baud rate 96002016-06-27 02:14:40,307 - ERROR - Baud rate detection for /dev/ttyACM0 failed2016-06-27 02:14:40,308 - DEBUG - Closing the printer connection.2016-06-27 02:14:40,308 - WARNING - Printer connection state was not changed2016-06-27 02:14:40,309 - WARNING - Printer connection state was not changed2016-06-27 02:14:51,259 - INFO - Updating firmware of /dev/ttyACM0 using /usr/share/cura/resources/firmware/MarlinUltimaker2plus.hex2016-06-27 02:14:52,400 - ERROR - Unable to connect with serial. Could not update firmware2016-06-27 02:21:20,880 - DEBUG - Setting value of adhesion_type to skirt on profile Current settings2016-06-27 02:21:22,868 - DEBUG - Backend quit with return code 0. Resetting process and socket.2016-06-27 02:21:22,885 - INFO - Started engine process: /usr/bin/CuraEngine2016-06-27 02:21:22,890 - DEBUG - Backend connected on port 496742016-06-27 02:21:29,459 - DEBUG - Backend quit with return code 0. Resetting process and socket.2016-06-27 02:21:29,477 - INFO - Started engine process: /usr/bin/CuraEngine2016-06-27 02:21:29,480 - DEBUG - Backend connected on port 496742016-06-27 02:21:31,563 - DEBUG - Autosaving preferences, instances and profiles

 

Edited by Guest

Share this post


Link to post
Share on other sites

/dev/ttyACM* simply does not exist. After skimming through http://forum.arduino.cc/index.php?topic=129647.0, I'm not sure it can be safely assumed that /dev/ttyACM* is even supposed to exist on current systems (with USB 3).

However:

 

$ dmesg | grep tty[    0.000000] console [tty0] enabled[    0.634660] 00:01: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A[    0.782114] tty ttyS16: hash matches[    3.184724] systemd[1]: Created slice system-getty.slice.[121415.704315] cdc_acm 1-5.1:1.0: ttyACM0: USB ACM device

 

And  about cdc_acm:

 

$ dmesg | grep cdc[121415.704315] cdc_acm 1-5.1:1.0: ttyACM0: USB ACM device[121415.704526] usbcore: registered new interface driver cdc_acm[121415.704527] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters[160133.203760]  cdc_acm nvram msr input_leds joydev bnep binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nls_iso8859_1 eeepc_wmi intel_rapl asus_wmi x86_pkg_temp_thermal intel_powerclamp sparse_keymap snd_hda_intel coretemp snd_hda_codec snd_hda_core snd_hwdep kvm snd_pcm irqbypass crct10dif_pclmul crc32_pclmul aesni_intel snd_seq_midi snd_seq_midi_event snd_rawmidi aes_x86_64 lrw gf128mul snd_seq glue_helper ablk_helper cryptd snd_seq_device snd_timer snd serio_raw soundcore mei_me shpchp mei hci_uart btbcm btqca btintel bluetooth intel_lpss_acpi 8250_fintek mac_hid intel_lpss acpi_als kfifo_buf acpi_pad industrialio parport_pc ppdev lp parport autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1[184959.464695]  cdc_acm nvram msr input_leds joydev bnep binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nls_iso8859_1 eeepc_wmi intel_rapl asus_wmi x86_pkg_temp_thermal intel_powerclamp sparse_keymap snd_hda_intel coretemp snd_hda_codec snd_hda_core snd_hwdep kvm snd_pcm irqbypass crct10dif_pclmul crc32_pclmul aesni_intel snd_seq_midi snd_seq_midi_event snd_rawmidi aes_x86_64 lrw gf128mul snd_seq glue_helper ablk_helper cryptd snd_seq_device snd_timer snd serio_raw soundcore mei_me shpchp mei hci_uart btbcm btqca btintel bluetooth intel_lpss_acpi 8250_fintek mac_hid intel_lpss acpi_als kfifo_buf acpi_pad industrialio parport_pc ppdev lp parport autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1[194699.064711]  cdc_acm nvram msr input_leds joydev bnep binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic nls_iso8859_1 eeepc_wmi intel_rapl asus_wmi x86_pkg_temp_thermal intel_powerclamp sparse_keymap snd_hda_intel coretemp snd_hda_codec snd_hda_core snd_hwdep kvm snd_pcm irqbypass crct10dif_pclmul crc32_pclmul aesni_intel snd_seq_midi snd_seq_midi_event snd_rawmidi aes_x86_64 lrw gf128mul snd_seq glue_helper ablk_helper cryptd snd_seq_device snd_timer snd serio_raw soundcore mei_me shpchp mei hci_uart btbcm btqca btintel bluetooth intel_lpss_acpi 8250_fintek mac_hid intel_lpss acpi_als kfifo_buf acpi_pad industrialio parport_pc ppdev lp parport autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1

 

cdc_acm is an "USB Abstract Control Model driver for USB modems and ISDN adapters". More information is to be found in Linux/drivers/usb/class/cdc-acm.c. Though, kernel drivers are out of my league.

The huge issue here is still the build volume mismatch with the UM2+ specs.

Edited by Guest

Share this post


Link to post
Share on other sites

Cura 2.1.2-0 for Linux is neither production ready, nor beta. It's pre-alpha software.

 

Or how -every- developer that we have right now develops Cura on Linux ;)

 

Why can I not use the specified build space of 223 x 223 x 205 mm???

 

Because that's a known issue with the scale to max. We have a pretty naive way of doing it, which in most cases doesn't give you a perfect max size.

Edited by Guest

Share this post


Link to post
Share on other sites
Because that's a known issue with the scale to max. We have a pretty naive way of doing it, which in most cases doesn't give you a perfect max size.

 

Thank you for commenting on this. I was not aware that it is a "known issue" that the specified build space can not be used and/or that the "Maximize" feature does not maximize the dimensions of the object.

Actually I can not find any documentation what the "real" build space would be or how to calculate how much of the specified build space can not be used to print objects. If I can only use 195.0 x 195.0 mm of the base plate, I got the wrong printer. I paid for a device with an useable build space of 223 x 223 mm on the base plate. A deviation of 28 x 28 mm from the specs is not "naive", but misleading or even fradulent, if these deviation was known and the specification has not been updated.

The actually useable build space is probably even smaller than 195.0 x 195.0 mm on the base plate, if support material, raft, or brim has to be printed. I haven't found documentation on how to calculate this precisely either, but I guess the effective size of objects printable with the Ultimaker is less than 190 x 190 mm on the base plate.

To avoid any misunderstandings, I'll try to rephrase: The build space of the UM2+ is specified to 223 x 223 x 205 mm, but this build space can not be used to print an object. It is impossible to print an object with a size of 222 x 222 x 1 mm (without raft and without brim). Do I understand this correctly?

If I misunderstood the statment: How do I print my 222 x 222 x 1 mm test file on the UM2+?

Edited by Guest

Share this post


Link to post
Share on other sites

I paid for a device with an useable build space of 223 x 223 mm on the base plate. A deviation of 28 x 28 mm from the specs is not "naive", but misleading or even fradulent, if these deviation was known and the specification has not been updated.

 

I find it rather interesting how you manage to convert "An automatic feature does not give the best possible result, so you need to do it by hand" into "This is fraud"

The machine can print it. The software doesn't help you do it automatically yet. I think you are overreacting a bit here.

 

The actually useable build space is probably even smaller than 195.0 x 195.0 mm on the base plate, if support material, raft, or brim has to be printed. I haven't found documentation on how to calculate this precisely either, but I guess the effective size of objects printable with the Ultimaker is less than 190 x 190 mm on the base plate.

 

Because what is build space? Is it what you actually use? or is it where the printer can lay down fillament. There is no clear definition.

 

If I misunderstood the statment: How do I print my 222 x 222 x 1 mm test file on the UM2+?

 

You use the scale tool.

Share this post


Link to post
Share on other sites

There should be no problem using a USB v3 port. "dmesg" even says that your printer's board was found and ttyACM0 was created!

Which desktop are you using? I had a similar problem in the past and I guess something might left during an upgrade that the service "modemmanager" is catching your printer and locks the connection.

See: http://stackoverflow.com/a/33855995/6333993

But I would prefer to use "sudo systemctl disable modemmanager" to disable the service and reboot. Uninstalling modemmanager is also possible, but some "meta-packages" might depend on it.

Finally: If "dmesg" says there is ttyACM0 there should be ttyACM0. Maybe in use or not accessible during any restrictions (which need to be disabled), but it really should be there.

  • Like 1

Share this post


Link to post
Share on other sites
Which desktop are you using? I had a similar problem in the past and I guess something might left during an upgrade that the service "modemmanager" is catching your printer and locks the connection. […] But I would prefer to use "sudo systemctl disable modemmanager" to disable the service and reboot. Uninstalling modemmanager is also possible, but some "meta-packages" might depend on it.

 

I'm using Ubuntu Mate; the modemmanger package is a dependency of ubuntu-mate-core and ubuntu-mate-desktop, so removing modemmanger woud render the system unusable.

Don't know about systemctl (or is it sysctl?), invoking these commands results in an error:

 

$ sudo systemctl disable modemmanager[…]Failed to execute operation: No such file or directory$ sudo sysctl disable modemmanagersysctl: der Aufruf von stat für /proc/sys/disable ist nicht möglich: Datei oder Verzeichnis nicht gefundensysctl: der Aufruf von stat für /proc/sys/modemmanager ist nicht möglich: Datei oder Verzeichnis nicht gefunden

 

I will try to find out if modemmanger can be disabled.

@naliath: "The machine can print it. The software doesn't help you do it automatically yet. I think you are overreacting a bit here."

No, I don't think that I am overreacting at all as there is no way to make the UM2+ print an object with the given dimensions of 222 x 222 x 1 mm. Cura just does not render Gcode for it. Clicking on "Maximize" gives the largest dimension that allow to generate Gcode. And those are 2.8 cm less than specified.

I paid for a device that can print object with ~22x22 cm at least. ~18x18 or 19x19 cm are not enough for the objects I need to print.

Edited by Guest

Share this post


Link to post
Share on other sites

That's not true. If you remove these packages APT could (!) probably decided to remove one of your preferred applications. Meta-packages are only depending on others and they are empty. Sometimes they come with some settings which are used to add some branding, but this is the maximum they do. In my case I don't use any kubuntu* meta-packages and everything works well ;)

However, to be sure we don't break anything I would prefer to disable the service.

Ah, I thought it is only containing lowercase letters, but it should be:

 

sudo systemctl disable ModemManager.service

 

Systemd is managing all services on your computer (at least since the last 2 Ubuntu releases). Now it is default and should have been replaced Upstart.

Edited by Guest

Share this post


Link to post
Share on other sites

 

$ sudo systemctl disable ModemManager.serviceRemoved symlink /etc/systemd/system/multi-user.target.wants/ModemManager.service.Removed symlink /etc/systemd/system/dbus-org.freedesktop.ModemManager1.service.

 

Rebooting…

 

2016-06-29 23:43:24,484 - DEBUG - Attempting to connect to printer with serial dev/ttyACM0 on baud rate 2500002016-06-29 23:43:26,002 - INFO - Printer connection listen thread started for /dev/ttyACM02016-06-29 23:43:26,003 - INFO - Established printer connection on port /dev/ttyACM02016-06-29 23:43:28,980 - DEBUG - Autosaving preferences, instances and profiles2016-06-29 23:43:38,260 - INFO - Updating firmware of /dev/ttyACM0 using /usr/share/cura/resources/firmware/MarlinUltimaker2plus.hex2016-06-29 23:43:38,261 - DEBUG - Closing the printer connection.2016-06-29 23:43:40,065 - INFO - Printer connection listen thread stopped for /dev/ttyACM0Flashing 127530 bytesWriting flashVerifying 127530 bytesCompleted2016-06-29 23:43:59,169 - DEBUG - Attempting to connect to /dev/ttyACM02016-06-29 23:43:59,788 - DEBUG - Attempting to connect to printer with serial /dev/ttyACM0  on baud rate 1152002016-06-29 23:44:07,440 - DEBUG - Attempting to connect to printer with serial /dev/ttyACM0  on baud rate 2500002016-06-29 23:44:08,958 - INFO - Printer connection listen thread started for /dev/ttyACM02016-06-29 23:44:08,958 - INFO - Established printer connection on port /dev/ttyACM0

 

Now running a firmware v2.1. This issue is fixed. Thank you!

However, still less than 90% of the build space can be used to print an object.

Edited by Guest

Share this post


Link to post
Share on other sites

 

Clicking on "Maximize" gives the largest dimension that allow to generate Gcode.

 

Look, I'm going to say this one more time. Clicking maximize won't give you the max printable size

 

Am I talking to a wall? If you enter larger dimensions than by clicking on "Maximize", Cura won't generate Gcode.

You can waste days to find out which version of Cura supports which fraction of the build space. E.g. with Cura 15.04.4, the object needed to be smaller than 229 x 207 x 205 before it refuses to generate Gcode.

With Cura 2.1.2-0, I can scale an object to 215.7 x 194.9 x 193.1 mm (94.2% of an object filling the whole specified build space).

I haven't tried to print these scaled down objects. It's possible that the UM2+ would throw the "Tried printing out of printing area" error even if Cura could generate the Gcode.

DSC02359.thumb.JPG.fdc47dde049a4973e78787a7deba6e27.JPG

I really don't care is this is a problem of marketing, or the UM2+ hardware, or of a certain Cura version. I just need to use about 220 x 220 x 200 mm, which fits into the specified build space of 223 x 223 x 205 mm.

If I pay for a device with a build space of 223 x 223 x 205 mm, I want to be able to use this. I do not have to teach myself to debug obscure JSON files. This is an (expensive) ready-to-use device for end users, not a (cheap) toy for do-it-yourselfers.

DSC02359.thumb.JPG.fdc47dde049a4973e78787a7deba6e27.JPG

Edited by Guest

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Announcements

  • Our picks

    • Architect Design Contest | Vehicles.
      We're open for entries! - Design and submit your 3D designs of architectural entourage - vehicles - for a chance to win a large filament pack. Presenting an idea, an architectural design or something as big as an urban project isn't easy. A scaled model can really help to get your idea across.
        • Like
      • 24 replies
    • What The DfAM?
      I'm Steve Cox, an experienced engineer familiar with 3D printing. I wanted to share some DfAM guidelines with this community to help and make stronger parts.
      I'm also an Autodesk Certified Instructor for Fusion 360, so many of the images in ...
        • Thanks
        • Like
      • 23 replies
×

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!