[Print requiring build space of ~22x22x20 cm]

So let's summarize three months after posting this request:

 

• Ultimaker is advertising misleading specs about the Ultimaker 2+, probably also for the Ultimaker 2+ Extended and older Ultimaker models. As well distributors as vendors are misinformed and thusly communicate more misleading information regarding the build space.
  
• There is no workable solution to print objects with approximately 22 x 22 x 20 cm or bigger with any Ultimaker device.
  
• So far, no service provider has made an offer to print the objects in question.
  

 

This is devastating.

[Print requiring build space of ~22x22x20 cm]

For this sort of model, in real size, I would rather recommend using a powder or sintering-based printer (such as Onshape's nylon printers). Some of our surgeons use nylon sintered models for replicating human bones and parts of skulls, and they look fine. … You need to carefully study specs and use the right tool for the right job. Preferably before buying anything.

That is an interesting idea. I am starting to understand that all Ultimaker printers are totally unfit for what I need. Studying specs does not help, as - it was mentioned multiple times before - Ultimaker does not state truthful specs. The actually useable build space is much smaller than advertised, and in the past about nine months it has been impossible to figure out the really useable build volume. According to a German distributor, the real build volume of the Ultimaker 2+ Extended is not 223 x 223 x 305 mm, but about 203 x 203  x 285 mm with skirt. However, from what I can tell it's even smaller than that because another half centimeter or so is shaved off for the clamps and whatever else (UM can position the nozzle on all axes, and they do know exactly where the clamps are located, so I don't understand what their problem is). It's very easy to falsify the specs with a flat object with ~223 x 223 x 1 mm on the base plate. Anyway, it's just impossible to work with vague specs like that, and that 's why I am looking for a printing service now.

The actual file(s) I need to print are not a skull. The skull is just a testing object intended for a inner structure. The objects I need to print are life-sized heads. The current STL files are around 200 MB. From top of the head to chin, the head needs to be scaled up to >22 cm to be life-sized.

What I could accomplish with the UM2+ a couple of months ago (with the old Cura version which does not work in current Linux distributions anymore) was to cut about 2 cm off from the top of the head in Blender and make a test print with the head sculpt upright, scaled to the max. height of 20.5 cm, then added the top of the head back manually in clay. Then sanded the surface, and smoothed the PLA with Acetone (yes, that does not only work for ABS). It's a shitty workflow as you need to cast the assembled draft object, then pour it and have a sculptor go manually over it again, then cast again and start making the actual mold form. In theory, a non-FDM printer could output the mold form directly. But that kind of tech is just not affordable yet, as far as I know.

Another approach would be to cut the head into two/four pieces, print them separately and glue them together, but I couldn't figure out how to do this properly in Blender. The original model was created in ZBrush, so it's definitely not a low-poly mesh which would allow easy splitting around the vertices. The other disadvantages would be similar to the approach I described above.

Sintered nylon could be very nice for the inner structures as they'd not require so much post-processing.

However, the total workflow to create the draft object is supposed to save time & money; if too much post-processing is required - like sanding, and adding parts back manually in clay, it's much easier to sculpt the head the traditional way and forget about 3D printing.

[Print requiring build space of ~22x22x20 cm]

Mine says BETA, both on splash screen and in the "about" section …

Well… nope, mine does not:

[Print requiring build space of ~22x22x20 cm]

As already a mentioned a few times in other topics, there is an issue with the beta and importing existing profiles from 2.1. …

My Cura version is not labeled as a "beta version". The splash screen says "Cura 2.3.0-0", not "Cura 2.3.0-0 beta".

I was instructed to install Cura 2.3 because Cura 2.1 does not work either. The official instructions for this are here: https://ultimaker.com/en/resources/21362-cura-2-1-linux-not-working . This page says:

 

Unfortunately the latest Linux Ubuntu build stopped including Python 3.4 in their systems. Cura 2.1.x runs on this version of Python and is therefore not running properly. This is an extreme inconvenience since all python 3.4 and lower applications now stopped working properly on these systems. The resolution. To fix this issue you will need to install a Personal Package Archive. How to get this archive working properly is found here …

 

You can fix this by clearing your setting folders and restarting Cura.

This would be this instruction page: https://ultimaker.com/en/resources/20499-reset-cura-2-1 . This page says:

 

Linux … Make sure Cura is closed. … Navigate to: $USER/.local/share/cura …

Delete the entire 'cura' folder.

On my system, no $USER/.local/share/cura folder exists.

So no, I can not modify any settings about "num lines" in Cura.

[Print requiring build space of ~22x22x20 cm]

Anyway, software is totally broken (Cura 2.3.0-0). NO values can be changed, and "Print Support Structure" can neither be turned on or off. And software does not generate any GCode, not even for small objects.

[Print requiring build space of ~22x22x20 cm]

You have a non-zero bed adhesion size. Try changing the bed adhesion (most notably the num lines / width settings)

The settings for "Build Plate Adhesion" can not be zero. I can change the type, e.g. from Brim to Raft, but 8 mm is the smallest possible setting.

Cura just refuses to process the object. Error message given:

"Nothing to slice because none of the models fit the build volume."

WTF!

[Print requiring build space of ~22x22x20 cm]

Anyone able to explain this?

Thanks!

[Print requiring build space of ~22x22x20 cm]

Ultimaker has been lying about the printable volume since the Ultimaker 2 was announced.

 

Yes, they are not telling the truth, and they also make their resellers to give false specs to customers. Multiple vendors have promised me explicitely that "build space" means that I can use the area for printing.

This is misleading and obviously intended to gain a competitive advantage over other manufacturers who state truthful facts about the build space.

However, I still need a solution to print the objects I want to print, and neither Cura nor the UM2+ allow this.

[Print requiring build space of ~22x22x20 cm]

Did you try to turn of brim and skirt?

 

For the object that need to be printed, some support structures are required.

Regarding the build space: Yes, I have used several test objects with 223 x 223 x 1 mm, 222 x 222 x 1 mm and the like when I tried to figure out the real build space. The useable space of the UM2+ is nowhere near the specs. I wasted months with this crap.

To print the object, the UM2+ would probably require modifications of the firmware or whatever, or it might work with an UM2+ Extended, I don't know. Since nobody is willing to tell me the "real" specs of the UM2+ Extended, I'm not going to buy one for "testing" purposes. That's why I'm looking for a service provider. I don't care about the brand of the printer, I just want a useable result.

Greetings, asb

[Print requiring build space of ~22x22x20 cm]

Hi,

I need to print an object which requires a build space of roughly 22x21x18 cm.

I bought an UM2+ for that because I was deceived to believe that this device has an useable build space of 223 x 223 x 205 mm. It has not.

So I need someone who has either a hardware-fixed, or a hardware-hacked Ultimaker, or another 3D printer which actually allows to print an object with ~22x21x18 cm (or slightly bigger).

Preferred filament is white ABS, but PLA should work as well. Nozzle size 0.4 mm. Ideally, the service provider is in the EU area.

Thanks, asb

[Cura 2.1 broken dependencies on Ubuntu 16.04 LTS]

 

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.

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.

[Cura 2.1 broken dependencies on Ubuntu 16.04 LTS]

 

$ 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.

[Cura 2.1 broken dependencies on Ubuntu 16.04 LTS]

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.

[Cura 2.1 broken dependencies on Ubuntu 16.04 LTS]

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+?

[Cura 2.1 broken dependencies on Ubuntu 16.04 LTS]

/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.

[Cura 2.1 broken dependencies on Ubuntu 16.04 LTS]

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

 

[Cura 2.1 broken dependencies on Ubuntu 16.04 LTS]

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???

[Cura 2.1 broken dependencies on Ubuntu 16.04 LTS]

@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).

[Cura 2.1 broken dependencies on Ubuntu 16.04 LTS]

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 2.1 broken dependencies on Ubuntu 16.04 LTS]

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.

[Cura 2.1 broken dependencies on Ubuntu 16.04 LTS]

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:

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

[Bugs in Cura 15.04.5 / Linux]

Yea, Cura is too stupid to calculate max print size. Let Cura scale the object with the "Maximize" button. Result:

ERROR: Tried printing out of printing area.

Try to reduce number of lines in the "Expert settings". Cura allows a minimum of "1".

Turn object on the build plate sideways 90° and hit "Maximize" again. Result:

ERROR: Tried printing out of printing area.

Now scale down manually. Objects just can not be 21,5 cm long, neither in X, Y, or Y axis.

ERROR: Tried printing out of printing area.

Wasted half a day trying to guess what the real build volume of the UM2+ might be.

Again, no success and lots of filament trashed for nothing.

And what exactly does this piece of junk consider "printing area"? Where it stopped with this error is pretty much in the middle of the print bed!

[Bugs in Cura 15.04.5 / Linux]

Actually, it's a lot worse. The UM2+ seems to not have a useable build volume of 223 × 223 × 205 mm, as specifications suggest. My object is 179 x 220 x 203 mm and the UM2+ just exited with an error message when trying to print a radically simplified object that Cura could process:

ERROR: Tried printing out of printing area.

Cura does not warn that the 179 x 220 x 203 mm object can not be printed in the 223 × 223 × 205 mm build space. I am not printing with brim. And even if I did, why doesn't take Cura care of these calculations? It knows which printer I'm using and it should be able to do some math.

Second try. Scaled the object down even more. Now it's 177 x 217 x 200 mm. Guess what? The UM2+ stopped again with the error message:

ERROR: Tried printing out of printing area.

Third try. Scaled the object down even more. Now it's 176 x 216 x 199 mm. And of course, the UM2+ stopped again with the error message:

ERROR: Tried printing out of printing area.

Last try. Scaled the object down to 175 x 215 x 198 mm. The longest side with 21,5 cm is the smallest size I can use. And of course, the UM2+ stopped again with the error message:

ERROR: Tried printing out of printing area.

Why the heck can I not print a low poly object with 175 x 215 x 198 mm in 223 × 223 × 205 mm build space?

At least in it's endless failures and notorious unrelyability the UM2+ one can rely on the UM2+.

This is beyond annoying :-(

[Bugs in Cura 15.04.5 / Linux]

Can't confirm this, just processed a part with 6,8 MB, 68446 vertices, 136879 faces without problems or noticable time consumption. If it didn't work for you, there must be an other reason than the file size ...

Operation to repeat: Make model in Blender, scale and verify in Netfabb, largest side ~220 mm, export to STL. Load STL into Cura. Processing in Cura will take about ten minutes, every time I change a parameter like infill or print speed. Then rotate the object to fit into the build space. Then cura will stop recalculating the estimated time & filament consumption and it will be impossible to write Gcode.

Another annoyance in Cura is that it doesn't check if the object fits into the build volume. 220 mm exceed the build volume of UM2+ (specs: 223 × 223 × 205 mm) when the longest side is upside. Cura will just not proces such a modelwithout telling anything.

[Bugs in Cura 15.04.5 / Linux]

…whatever the "new one" might be.

However, Cura 15.04.5 / Linux can not even process STL files STL files with a relatively moderate size of ~5 MB, ~50000 vertices, ~100000 faces (from Blender), and that sucks big time :-(