mech-thkoeln

For online update: I made the online update twice - but the Firmware still thinks there is a newer version online. Seems to be a bug. Just abort the following update.

The issue is solved with the help of Ultimaker support. After factory reset and another firmware update it works now. However, the printer would now like to upgrade endlessly as it thinks the firmware 5.3 in the online repository is newer as the installed firmware 5.3.0. Thanks for help!

Thanks. It was the initial firmware from 2018. However, it printed as it should. I raised an issue at ultimaker. I will post the solution -if any- for others...

Dear all, i had to upgrade my UM3 to the newest firmware (um-update-5.3.0.20211003.swu). Now it is impossible to connect to a wifi. Before the upgrade wifi worked flawlessly. I start wifi setup, connect to the UM3 hotspot and enter the network credentials. After this the UM3 states "Waiting for network..." forever. In the network settings it switches always back to wired network after setup. Any idea? Thanks for input.

Thanks for the reply, I tested all combinations above. Only the "xcb" option works for Opensuse Leap 15.5 / Gnome Desktop. All other options end up with: Could not find the Qt platform plugin The error seems independent of the QT_QPA_PLATFORM... option. If i do not use the QT_QPA_PLATFORM... option cura starts and the issue with crashing by clicking the file button remains.

UltiMaker Cura 5.4 crashes on Opensuse Leap 15.5 I got the package run and resolved libstdc++ dependencies with: QT_QPA_PLATFORM=xcb LD_PRELOAD=/usr/lib64/libstdc++.so.6 ./UltiMaker-Cura-5.4.0-linux.AppImage Cura comes up and shows the changes window. If i try to load a file it crashes: (UltiMaker-Cura:10473): Gtk-WARNING **: 11:44:10.929: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. ** Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Adwaita/16x16/status/image-missing.png: Format der Bilddatei unbekannt (gdk-pixbuf-error-quark, 3) Bail out! Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Adwaita/16x16/status/image-missing.png: Format der Bilddatei unbekannt (gdk-pixbuf-error-quark, 3) /tmp/.mount_UltiMa1BHwLu/AppRun: Zeile 25: 10473 Abgebrochen (Speicherabzug geschrieben) $scriptdir/UltiMaker-Cura "$@" /usr/share/icons/Adwaita/16x16/status/image-missing.png is a generic png and exists. Cura 5.3.1 is running fine...

Tanks for the replies. The residue is not the problem. The heads are cleaned prior to every print. I guess in the new firmware the limits for compensation were tightened in order to gain some speed. The old strategy was more robust.

Dear Robin, if i tighten the screws nearly completely, the procedure works again. Thanks. However, i would wish that the programming of active levelling is more robust. It seems that you do not check at the start of the procedure if the plate is nearly in contact with the plate. Or why not use the z-height of manual levelling as starting point. If i use -for example- the "BuildTak FlexPlate" on this UM3 the start distance is again too tight and active levelling fails again. Thanks for help.

Dear all, we are running several UM3 and UM2+ at out laboratory. Today i decided to update the firmware on one of the UM3 printers. After the firmware update, the active levelling fails always with the message: 'difference between detected height of both printcores exceeds realistic value' -> I tried to level the print bed several times manually: No change. After manual levelling he tries always another active levelling procedure which naturally fails. -> I tried to lower the height of the print bed by turning the screws: No change -> I tried both the stable and the experimental versions of the firmware. The levelling starts nearly in contact with the plate. During active levelling the z-stepper keeps running until the stepping fail with a "click". Thus, the printcores are pushed upwards until the x-y-rods are bend. Any idea?