SmartBlug

Has anybody found the fix ? My S5 is stuck at the Ultimaker screen, this is not black but you cannot do anything as there is no menu, just le logo Ultimaker. What is strange is that the printer is working but didn't disply anything and you cannot acknoledge when printing is finished... Power cycle sometimes unlock the situation and allow you to confim... Sounds a bug in the software... I'm running firmware 8.1.1

I removed the folder in /var/log/journal and get back 58Mb 😉 It seems it was logs not properly deleted in the past by the software (probably due to bug in old releases) now, only -rw-r----- 1 root systemd-journal 8388608 Dec 15 07:40 system.journal -rw-r-----+ 1 root systemd-journal 8388608 Dec 15 07:38 user-1000.journal I'll monitor to see if this folder size continue to increase or not...

I deleted some of the logs and get back 100k... /var/log/journal is big, how to safely delete this journal ? size of main folders : 526231 / 215146 /usr 168876 /var 99980 /usr/lib 91755 /var/lib 87435 /usr/share 83935 /var/lib/connman 83910 /var/lib/connman/ethernet_ccbdd300033b_cable 75247 /var/log 74847 /var/log/journal 74844 /var/log/journal/5e702514274833c0ebe690cc5ccc224d 62364 /opt 53676 /lib 50743 /opt/qt 46852 /usr/share/fonts 42043 /opt/qt/lib 39929 /usr/lib/python3 39926 /usr/lib/python3/dist-packages 37227 /usr/share/fonts/opentype 37224 /usr/share/fonts/opentype/noto 27626 /usr/lib/arm-linux-gnueabihf 26975 /lib/modules 26971 /lib/modules/4.14.32-ultimaker-00309-geaace6d4aede 25823 /lib/modules/4.14.32-ultimaker-00309-geaace6d4aede/kernel 23787 /usr/bin 21829 /usr/lib/python3.4 14635 /lib/modules/4.14.32-ultimaker-00309-geaace6d4aede/kernel/drivers 13239 /usr/lib/python3/dist-packages/numpy 12523 /usr/share/i18n 11618 /opt/pyqt 11568 /lib/udev 11428 /opt/pyqt/PyQt5 9486 /usr/share/i18n/locales 8704 /lib/arm-linux-gnueabihf 8289 /usr/share/okuda 8036 /usr/lib/python3/dist-packages/cluster 7911 /usr/lib/python3/dist-packages/cluster/app 7840 /run 7412 /usr/share/griffin 7267 /usr/lib/python3/dist-packages/sqlalchemy 7237 /usr/share/okuda/resources 6606 /usr/lib/python3/dist-packages/cluster/app/static 6440 /run/log/journal/5e702514274833c0ebe690cc5ccc224d 6440 /run/log/journal 6440 /run/log

Yes, of course. I also tried to reset cura settings but same problem.

I cannot use my printer anymore (Extended 3) On the log : ultimakersystem-ccbdd300033b flipflop_wsgi.py[1314]: OSError: [Errno 28] No space left on device: '/var/lib/griffin/cluster/preferences.json.new' If I connect in dev mode : /dev/mmcblk1p2 963584 828416 0 100% / devtmpfs 481308 0 481308 0% /dev tmpfs 515100 0 515100 0% /dev/shm tmpfs 515100 7840 507260 2% /run tmpfs 5120 0 5120 0% /run/lock tmpfs 515100 0 515100 0% /sys/fs/cgroup tmpfs 515100 0 515100 0% /var/lib/apt tmpfs 515100 0 515100 0% /tmp tmpfs 515100 0 515100 0% /var/cache/apt /dev/mmcblk1p3 2775040 26632 2527224 2% /var/spool/cluster Is there a way to clean the file system ? Thanks,

Sure

The answer is 'no' and it's repeatable so the capacitive sensor is probaby HS ;-(

Sorry, I was not clear. It was for a new print I'm printing every day (printer always ON) As usual, I launched next print. As this printer is really reliable, I do not pay attention anymore when I launch a new print... always 100% successfull. After few hours (2 to 3 hours), I looked to the video stream and I was surprised that the cycle was still trying to do bed leveling... and then I discovered it was still trying to do active level, putting message "difference..." and then starting new cycle trying to do active level... I then discovered the problem I reboot, forced active level, tryed manual level and then active level... no way to work again, always almost 1 cm from the head. The cycle is done completely (all differents location on the bed) without touching the head. It's done on both heads and then the message of difference is displayed... Since this date, I changed settings to avoid active level and the printer is working fine with manual level... No idear why this happened...

Hi, I didn't swap print cores. It was working as usual and then, suddenly, all the bed leveling attempts goes wrong (try bed leveling, echec, retry... and so one until I discoverd that my print was still not finished) No blob or filament and it's still printing with manual level. The space before it stops is not just few milimeters, but almost 1cm... much more than what can be compensated with manual adjustments.

I've got a UM3 Extended and suddendly, bed leveling is not working anymore. It end-up with "difference..." message When the active bed leveling start, it stop too far from the head and then start to go up slowly. It stop several milimeters before the glass can touch head (I believe because there is a treshold in the distance). Is there a way to setup the initial trigger higher (when the plate move fast and just before it start to adjust) ? Thanks in advence for your help