Jump to content

Ultimaker 3 Firmware update: 5.2.17

SandervG

By SandervG
in Firmware

 Share

Recommended Posts

gr5

gr5 2,024

Posted
Posted · Ultimaker 3 Firmware update: 5.2.17

I suspect the flash memory on your UM3 is getting old.  You can get a new olimex board but first I'd try the standard unbricking procedure which involves a uSD card.  Contact your reseller for the pdf instructions on how to unbrick your UM3/UM3ext.

 

If the uSD card method doesn't work I have much more details on how to watch your Olimex Linux board boot up so you can see EXACTLY where the error lies.  Then you can repair the problem with linux commands.  Everything is explained in great detail here.  I wrote it for the S5 but the UM3 has the same Olimex board with the same issues:

http://gr5.org/unbricking/

 

    • Link to post
    Share on other sites
    • Replies 50
    • Created
    • Last Reply

    Top Posters In This Topic

    Popular Days

    Top Posters In This Topic

    Popular Days

    Popular Posts

    CarloK
    CarloK

    @V3DPrinting You are right. My printer is modified and I tend to forget it's an unofficial feature.   @Enigma_M4 Yes, it's possible and works great on my UM3 but not officially and require

    SandervG
    SandervG

    We’re happy to announce that we’re releasing a firmware update to the popular Ultimaker 3 and Ultimaker 3 Extended. Firmware 5.2.17 will contain: material profiles for the new Ultimaker PETG

    CarloK
    CarloK

    And there are a whole lot of other changes that didn't make it into the official release notes because those are not applicable to most users. A small list: - copied firmware installation ro

    Posted Images

    CarloK

    CarloK 196

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    I discovered what the weird lines are, it is an error message, but the graphical image was created for the display of an S5 printer and fails in this weird way on the UM3.

     

    In 5.2.17 the update routines were replaced by a newer version backported from the S-line printers. The error screen was not converted to the UM3 screen, we'll fix this in a next release (coming very soon).

    One of the new features is that we now check for the printer that you install the software on is allowed to run this software. That's why higher up in this thread someone got the screen with lines when installing v6.2.2 for the S5 on his UM3.

    Nothing breaks, after power cycling the printer you will still be on your previous firmware version. We are looking into why some UM3 Extended owners experience these problems.

     

    • Like 2
    Link to post
    Share on other sites
    TheoM

    TheoM 1

    Posted
    Posted (edited) · Ultimaker 3 Firmware update: 5.2.17
    8 hours ago, CarloK said:

    @TheoM Thanks for the extra info that the lines remain for more than 10 minutes. This is an indication the update process has stopped.
    I can't reproduce the error here, so I depend on info from users like you to narrow down the problem cause.
    So far, we got 3 other users reporting this problem. All on a UM3 Extended. Is your machine a normal UM3 or the Extended version?

     

    I am using a UM3, standard height. 

     

    I have attempted 2x times. I can shut the machine off (manual power switch) and the machine will turn back on in working order, but with older firmware. 

    Edited by TheoM
    • Link to post
    Share on other sites
    CarloK

    CarloK 196

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    @TheoM Thanks for the info that you experience this problem with the standard UM3 model.

     

    This means the problem was reported on both normal size UM3 and Extended UM3 printers. Weird and frustrating is that we can't reproduce the problem on our testing printers which makes it difficult to fix this problem.

    • Like 1
    Link to post
    Share on other sites
    CarloK

    CarloK 196

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    Good news: a hotfix release for the UM3 is under test and we expect to release this in a about a week.

     

    V5.2.18 will fix 2 bugs:

    • Fixed missing Chinese font. Selecting the Chinese language resulted in mostly empty screens.
    • Fixed update failing while showing vertical lines. This was caused by a new firmware compatibility check failing. The check is not required for the UM3 and removed.

    When you want to participate in beta testing, then send me a private message through this forum (click my avatar and select 'message' in top of the screen).

    • Like 1
    Link to post
    Share on other sites
    Ivan881

    Ivan881 0

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    Hi,

     

    during the firmware update 5.2.17 my Ultimaker 3 got stuck with 1 minute remaining for over 3 hours. After reading the message of this thread i switched it off but it did non power up again. what can i do? (it is still in the 2 year warranty)

     

    Thanks in advance

    • Link to post
    Share on other sites
    gr5

    gr5 2,024

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    Start by turning it back on and leaving it for 15 minutes.  And if it doesn't recover turn it off and on one more time.  If that still doesn't work contact your reseller.

    • Link to post
    Share on other sites
    CarloK

    CarloK 196

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    @Ivan881 I agree with @gr5. Retry a few times and if it still fails to boot, then contact your reseller. This will help us to get statistics on the types and numbers of problems.
    Your reseller most likely will help you to follow the recovery procedure. This incorporates opening the bottom cover and installing a mini SD card with recovery software. This procedure is also described here on the forum.

    • Link to post
    Share on other sites
    CarloK

    CarloK 196

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    The v5.2.18 hotfix is available for download. For changes, see my post 4 messages up in this thread.

    • Link to post
    Share on other sites
    V3DPrinting

    V3DPrinting 11

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    @CarloK v5.2.17 works fine regarding the dual extrusion.

    But it seems that some parameters were copied from another printer : in um3.json the Bowden tube length is 700 mm. As a consequence, the filament loading / unloading procedures are not accurate.

    If I remember well in the old FW it was 760 mm.

    • Link to post
    Share on other sites
    CarloK

    CarloK 196

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    @V3DPrinting The um3.json wasn't touched in the recent updates and this value in particular hasn't changed since April 2016. Then it was reduced from 750mm to 700mm, so your memory is not totally wrong.

     

    The S-line recently got the feature to use the flow-sensor in the loading procedure. I'll add this to my wish list to back-port to the UM3. No promises however about if and when.

    • Like 1
    Link to post
    Share on other sites
    V3DPrinting

    V3DPrinting 11

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    @CarloK Thanks again for the reply.

    UM3 stock doesn't have a flow sensor, so back port won't work. Nor do mine as I have Bondtech extruders on my two UM3E.

    • Link to post
    Share on other sites
    Enigma_M4

    Enigma_M4 96

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17
    14 hours ago, CarloK said:

    The S-line recently got the feature to use the flow-sensor in the loading procedure. I'll add this to my wish list to back-port to the UM3. No promises however about if and when.

    Does this mean the flow sensor would be supported by the UM3 if installed? So could I just buy complete S5-feeders and change the UM3 ones with them?

    Kind regards

    • Link to post
    Share on other sites
    CarloK

    CarloK 196

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17
    On 9/5/2021 at 11:07 AM, V3DPrinting said:

    @CarloK Thanks again for the reply.

    UM3 stock doesn't have a flow sensor, so back port won't work. Nor do mine as I have Bondtech extruders on my two UM3E.

    @V3DPrinting You are right. My printer is modified and I tend to forget it's an unofficial feature.

     

    22 hours ago, Enigma_M4 said:

    Does this mean the flow sensor would be supported by the UM3 if installed? So could I just buy complete S5-feeders and change the UM3 ones with them?

    Kind regards

    @Enigma_M4 Yes, it's possible and works great on my UM3 but not officially and requires a small change to the printer's software configuration. You could even experiment with 1 feeder first before spending the money on the 2nd feeder.
    When desired I can create a new topic explaining this in more detail.

    • Like 2
    • Thanks 2
    Link to post
    Share on other sites
    Enigma_M4

    Enigma_M4 96

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    @CarloK That' great news, thanks a lot.

    25 minutes ago, CarloK said:

    When desired I can create a new topic explaining this in more detail.

    That would be great. Being able to use the UM3 with flow sensors would be a great benefit 🙂.

    Regards

    • Link to post
    Share on other sites
    gr5

    gr5 2,024

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    @CarloK - I think I know some other people who would be interested in this.  Assume we know linux - how to ssh to the machine, locate and edit files.  But not what edits to make.  Also where would the sensor plug in?

    • Link to post
    Share on other sites
    JohnInOttawa

    JohnInOttawa 103

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    Good afternoon everyone!

    One quick request - would like to hear from anyone who has applied the new firmware to UM3 or 3X with Bondtech feeders.  Is the modification process for the new steps the same?

     

    Thanks in advance!

    John

    • Link to post
    Share on other sites
    Smithy

    Smithy 1,135

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    Hi John,

    I don't have Bondtech feeders on the UM3, but as far as I know there were only some minor bug fixes, so the process should be still the same.

    • Thanks 1
    Link to post
    Share on other sites
    V3DPrinting

    V3DPrinting 11

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17
    2 hours ago, JohnInOttawa said:

    Good afternoon everyone!

    One quick request - would like to hear from anyone who has applied the new firmware to UM3 or 3X with Bondtech feeders.  Is the modification process for the new steps the same?

     

    Thanks in advance!

    John

    @JohnInOttawa I have two UM3X with Bondtech extruders. Yes the tweak is the same as for the previous FW. You need to edit the um3.json and another file but I don't remember it. I refer always to the Bondtech documentation

    It works very well

    • Like 1
    • Thanks 1
    Link to post
    Share on other sites
    sisu

    sisu 0

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    Hello,

     

    We are trying to update the firmware on our Ultimaker 3 Extended and have not been able to. We tried 5.2.17 (first) and 5.2.18 (when it came out). Both will run the update sequence, but then hang at the "waiting two minutes" screen. I have tried multiple times over the span of a month to update it, including downloading the 5.2.18 update to a flash drive (same outcome). Not urgent, but it would be nice to get it updated at some point. We have been running the printer with the 5.2.16 without problems in between attempts to update.

     

    Not sure if this is the portion of the log that would be helpful. Maybe the 5th line from the bottom is a clue? (maybe that's just normal)

     

    Thanks!

      

    Sep 10 22:06:51 ultimakersystem-ccbdd3002925 python3[216]: 2021-09-10 22:06:51,947 INFO     systemUpdate    Starting download of: http://software.ultimaker.com/releases/firmware/9511/stable/um-update.swu?current_version=5.2.16.20200331
Sep 10 22:06:51 ultimakersystem-ccbdd3002925 python3[216]: 2021-09-10 22:06:51,966 INFO     systemUpdate    Comparing firmware 'stable' old version '5.2.16.20200331' with new version '5.2.18.20210820' with result: False
Sep 10 22:06:52 ultimakersystem-ccbdd3002925 python3[216]: 2021-09-10 22:06:52,170 INFO     systemUpdate    Starting download of: http://software.ultimaker.com/releases/firmware/9511/stable/um-update.swu?current_version=5.2.16.20200331
Sep 10 22:06:53 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host 10.1.1.200.
Sep 10 22:06:53 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host 10.1.1.65.
Sep 10 22:06:57 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host fe80::bead:28ff:fe45:825.
Sep 10 22:06:57 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host 10.1.1.25.
Sep 10 22:06:58 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host fe80::fa4d:fcff:fe08:31eb.
Sep 10 22:06:58 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host 10.1.1.38.
Sep 10 22:06:58 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host 10.1.1.38.
Sep 10 22:06:58 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host fe80::fa4d:fcff:fe08:31eb.
Sep 10 22:07:03 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host fe80::bead:28ff:fe45:825.
Sep 10 22:07:03 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host 10.1.1.25.
Sep 10 22:07:03 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host fe80::fa4d:fcff:fe08:31eb.
Sep 10 22:07:03 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host 10.1.1.38.
Sep 10 22:07:25 ultimakersystem-ccbdd3002925 python3[216]: 2021-09-10 22:07:25,496 INFO     systemUpdate    Signature verification done
Sep 10 22:07:25 ultimakersystem-ccbdd3002925 python3[216]: 2021-09-10 22:07:25,498 INFO     systemUpdate    Storing current version 5.2.16.20200331 to file
Sep 10 22:07:25 ultimakersystem-ccbdd3002925 python3[216]: 2021-09-10 22:07:25,500 INFO     registryFile    Saving preferences to /var/lib/griffin/system_update_notification.json
Sep 10 22:07:25 ultimakersystem-ccbdd3002925 python3[216]: 2021-09-10 22:07:25,517 INFO     systemUpdate    Performing pre-update procedure.
Sep 10 22:07:25 ultimakersystem-ccbdd3002925 sudo[1822]: ultimaker : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/pre_update.sh /tmp/um-update.swu
Sep 10 22:07:25 ultimakersystem-ccbdd3002925 sudo[1822]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 10 22:07:25 ultimakersystem-ccbdd3002925 kernel: squashfs: SQUASHFS error: Xattrs in filesystem, these will be ignored
Sep 10 22:07:25 ultimakersystem-ccbdd3002925 kernel: squashfs: SQUASHFS error: unable to read xattr id index table
Sep 10 22:07:25 ultimakersystem-ccbdd3002925 jedi-display[1147]: attachOnUsbNewStorage: mounted tmp-um\x2dupdate_root_mnt.5J2seU.mount
Sep 10 22:07:26 ultimakersystem-ccbdd3002925 kernel: EXT4-fs (mmcblk1p1): mounted filesystem with ordered data mode. Opts: (null)
Sep 10 22:07:26 ultimakersystem-ccbdd3002925 jedi-display[1147]: attachOnUsbNewStorage: mounted tmp-update_file_dest_dir.FAi49y.mount
Sep 10 22:07:26 ultimakersystem-ccbdd3002925 jedi-display[1147]: attachOnUsbRemoved: unmounted tmp-update_file_dest_dir.FAi49y.mount
Sep 10 22:07:26 ultimakersystem-ccbdd3002925 jedi-display[1147]: attachOnUsbNewStorage: mounted tmp-update_file_dest_dir.FAi49y.mount
Sep 10 22:07:26 ultimakersystem-ccbdd3002925 jedi-display[1147]: attachOnUsbRemoved: unmounted tmp-update_file_dest_dir.FAi49y.mount
Sep 10 22:07:26 ultimakersystem-ccbdd3002925 jedi-display[1147]: attachOnUsbNewStorage: mounted tmp-update_file_dest_dir.FAi49y.mount
Sep 10 22:07:27 ultimakersystem-ccbdd3002925 jedi-display[1147]: attachOnUsbRemoved: unmounted tmp-update_file_dest_dir.FAi49y.mount
Sep 10 22:07:28 ultimakersystem-ccbdd3002925 jedi-display[1147]: attachOnUsbRemoved: unmounted tmp-um\x2dupdate_root_mnt.5J2seU.mount
Sep 10 22:07:28 ultimakersystem-ccbdd3002925 sudo[1822]: pam_unix(sudo:session): session closed for user root
Sep 10 22:07:28 ultimakersystem-ccbdd3002925 python3[216]: 2021-09-10 22:07:28,380 INFO     systemUpdate    Pre-update done, rebooting printer to perform the firmware update.
Sep 10 22:07:28 ultimakersystem-ccbdd3002925 python3[216]: 2021-09-10 22:07:28,385 INFO     systemService   Reboot starting
Sep 10 22:07:28 ultimakersystem-ccbdd3002925 python3[216]: 2021-09-10 22:07:28,389 INFO     registryFile    Saving preferences to /var/lib/griffin/system_preferences.json
Sep 10 22:07:30 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host 10.1.1.179.
Sep 10 22:07:30 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host 10.1.1.179.
Sep 10 22:07:33 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host 10.1.1.12.
Sep 10 22:07:35 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host 10.1.1.12.
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Invalid response packet from host 10.1.1.135.
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 sudo[1866]: ultimaker : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl reboot
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 sudo[1866]: pam_unix(sudo:session): session opened for user root by (uid=0)
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Starting Synchronise Hardware Clock to System Clock...
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Unmounting /var/spool/cluster...
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopping mjpg-streamer, Webcam streaming for all on /dev/video0...
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopping WPA supplicant...
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Target running the griffin services.
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target Target running the griffin services.
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Multi-User System.
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target Multi-User System.
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Login Prompts.
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target Login Prompts.
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Getty on tty1...
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Serial Getty on ttyS0...
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Login Service...
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Charon File Metadata service...
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Startup service which populates /dev/gpio...
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopping A high performance web server and a reverse proxy server...
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Embedded service that connects to the Ultimaker cloud platform (Stardust)....
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Ultimaker 3 Display Human Machine Interface service on /dev/fb0...
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Hermes notification service...
Sep 10 22:07:37 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Print cluster server...
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 flipflop_wsgi.py[1150]: INF - registryFile:123 - Saving preferences to /var/lib/griffin/cluster/analytics_state.json
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 flipflop_wsgi.py[1148]: INF - registryFile:123 - Saving preferences to /var/lib/griffin/hermes_preferences.json
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 flipflop_wsgi.py[1148]: INF - registryFile:123 - Saving preferences to /var/lib/griffin/hermes_subscriptions.json
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 flipflop_wsgi.py[1150]: INF - registryFile:123 - Saving preferences to /var/lib/griffin/cluster/preferences.json
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Login Service.
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 systemd[1]: Stopped WPA supplicant.
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Getty on tty1.
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Serial Getty on ttyS0.
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Charon File Metadata service.
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Embedded service that connects to the Ultimaker cloud platform (Stardust)..
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 systemd[1]: Stopped mjpg-streamer, Webcam streaming for all on /dev/video0.
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Ultimaker 3 Display Human Machine Interface service on /dev/fb0.
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 systemd[1]: Unmounted /var/spool/cluster.
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Startup service which populates /dev/gpio.
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 systemd[1]: Stopped A high performance web server and a reverse proxy server.
Sep 10 22:07:38 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Hermes notification service.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopping system-griffin.hmi.slice.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Removed slice system-griffin.hmi.slice.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Griffin beep service...
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopping system-mjpg\x2dstreamer.slice.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Removed slice system-mjpg\x2dstreamer.slice.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopping system-serial\x2dgetty.slice.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Removed slice system-serial\x2dgetty.slice.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopping system-getty.slice.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Removed slice system-getty.slice.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Permit User Sessions...
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Griffin beep service.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Permit User Sessions.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Remote File Systems.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target Remote File Systems.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Remote File Systems (Pre).
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target Remote File Systems (Pre).
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopping /etc/rc.local Compatibility...
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 connmand[241]: Terminating
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped /etc/rc.local Compatibility.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Network.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target Network.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Connection service...
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Withdrawing address record for 10.1.1.52 on eth0.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.1.1.52.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Interface eth0.IPv4 no longer relevant for mDNS.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 connmand[241]: Time request for server 10.1.1.1 failed (101/Network is unreachable)
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 connmand[241]: Time request for server 10.1.1.1 failed (101/Network is unreachable)
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Withdrawing address record for fe80::cebd:d3ff:fe00:2925 on eth0.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::cebd:d3ff:fe00:2925.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Interface eth0.IPv6 no longer relevant for mDNS.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 connmand[241]: Remove interface eth0 [ ethernet ]
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 connmand[241]: Remove interface wlan0 [ wifi ]
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 hwclock[1872]: hwclock from util-linux 2.25.2
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 hwclock[1872]: Using the /dev interface to the clock.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 hwclock[1872]: Last drift adjustment done at 1631311536 seconds after 1969
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 hwclock[1872]: Last calibration done at 1631311536 seconds after 1969
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 hwclock[1872]: Hardware clock is on UTC time
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 hwclock[1872]: Assuming hardware clock is kept in UTC time.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 hwclock[1872]: Waiting for clock tick...
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 hwclock[1872]: ...got clock tick
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 hwclock[1872]: Time read from Hardware Clock: 2021/09/10 22:07:38
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 hwclock[1872]: Hw clock time : 2021/09/10 22:07:38 = 1631311658 seconds since 1969
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 hwclock[1872]: 1631311659.500000 is close enough to 1631311659.500000 (0.000000 < 0.001000)
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 hwclock[1872]: Set RTC to 1631311659 (1631311659 + 0; refsystime = 1631311659.000000)
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 hwclock[1872]: Setting Hardware Clock to 22:07:39 = 1631311659 seconds since 1969
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 hwclock[1872]: ioctl(RTC_SET_TIME) was successful.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 hwclock[1872]: Not adjusting drift factor because it has been less than a day since the last calibration.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Started Synchronise Hardware Clock to System Clock.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 connmand[241]: eth0 {remove} index 2
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 connmand[241]: wlan0 {remove} index 3
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 connmand[241]: Exit
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 dbus[220]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.13" (uid=1000 pid=517 comm="/usr/bin/python3 /usr/share/griffin/main.py griffi") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.3" (uid=0 pid=241 comm="/usr/sbin/connmand -n -o ")
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 python3[517]: 2021-09-10 22:07:39,547 INFO     connmanAgent    NetworkAgent Release
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Disconnected from D-Bus, exiting.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 avahi-daemon[375]: Got SIGTERM, quitting.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 avahi-daemon[375]: avahi-daemon 0.6.31 exiting.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 sudo[1866]: pam_unix(sudo:session): session closed for user root
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Connection service.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopping D-Bus System Message Bus...
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: griffin.camera.service: main process exited, code=exited, status=1/FAILURE
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Griffin camera service.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Unit griffin.camera.service entered failed state.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: griffin.initialize_database.service: main process exited, code=exited, status=1/FAILURE
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Initializer for Griffin History database. This sets up the tables to prevent a race condition between its dependents.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Unit griffin.initialize_database.service entered failed state.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: griffin.system.service: main process exited, code=exited, status=1/FAILURE
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: griffin.network.service: main process exited, code=exited, status=1/FAILURE
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Griffin network service.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Unit griffin.network.service entered failed state.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped D-Bus System Message Bus.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: griffin.job_history.service: main process exited, code=exited, status=1/FAILURE
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Griffin PrintJob History service.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Unit griffin.job_history.service entered failed state.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: griffin.event_history.service: main process exited, code=exited, status=1/FAILURE
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Griffin Event History service.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Unit griffin.event_history.service entered failed state.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: griffin.material.service: main process exited, code=exited, status=1/FAILURE
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Griffin Material service.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Unit griffin.material.service entered failed state.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: griffin.printer.service: main process exited, code=exited, status=1/FAILURE
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Griffin printer service.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Unit griffin.printer.service entered failed state.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: griffin.led.service: main process exited, code=exited, status=1/FAILURE
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Griffin led service.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Unit griffin.led.service entered failed state.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: griffin.nfc.service: main process exited, code=exited, status=1/FAILURE
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Griffin nfc service.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Unit griffin.nfc.service entered failed state.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: griffin.message.service: main process exited, code=exited, status=1/FAILURE
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Griffin message service.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Unit griffin.message.service entered failed state.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: griffin.interface.avahi.service: main process exited, code=exited, status=1/FAILURE
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Griffin Avahi zeroconf service.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Unit griffin.interface.avahi.service entered failed state.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: griffin.interface.http.service: main process exited, code=exited, status=1/FAILURE
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Griffin HTTP service.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Unit griffin.interface.http.service entered failed state.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Print cluster server.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Griffin system service.
Sep 10 22:07:39 ultimakersystem-ccbdd3002925 systemd[1]: Unit griffin.system.service entered failed state.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Basic System.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target Basic System.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Slices.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target Slices.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping User and Session Slice.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Removed slice User and Session Slice.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Paths.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target Paths.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Forward Password Requests to Wall Directory Watch.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Dispatch Password Requests to Console Directory Watch.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Timers.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target Timers.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Daily Cleanup of Temporary Directories.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Sockets.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target Sockets.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping hermes.interface.http.socket.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Closed hermes.interface.http.socket.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Avahi mDNS/DNS-SD Stack Activation Socket.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping the http fastcgi link to nginx.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Closed the http fastcgi link to nginx.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping linking griffin.interface.http service to nginx via fastcgi over a unix socket.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Closed linking griffin.interface.http service to nginx via fastcgi over a unix socket.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping D-Bus System Message Bus Socket.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Closed D-Bus System Message Bus Socket.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping System Initialization.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target System Initialization.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Load/Save Screen Backlight Brightness of backlight:ssd1307fb0...
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Encrypted Volumes.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target Encrypted Volumes.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Load/Save Random Seed...
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Apply Kernel Variables...
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Apply Kernel Variables.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Load Kernel Modules...
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Load Kernel Modules.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Swap.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target Swap.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:ssd1307fb0.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Load/Save Random Seed.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Create Volatile Files and Directories...
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Create Volatile Files and Directories.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Local File Systems.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target Local File Systems.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Unmounting /media/usb0...
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Unmounting /var/cache/apt...
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Unmounting /var/lib/apt...
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Unmounting /tmp...
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Stopping system-systemd\x2dbacklight.slice.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Removed slice system-systemd\x2dbacklight.slice.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Unmounted /var/cache/apt.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Unmounted /var/lib/apt.
Sep 10 22:07:40 ultimakersystem-ccbdd3002925 systemd[1]: Unmounted /tmp.
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Unmounted /media/usb0.
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Starting Unmount All Filesystems.
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Reached target Unmount All Filesystems.
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Local File Systems (Pre).
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Stopped target Local File Systems (Pre).
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Create Static Device Nodes in /dev...
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Create Static Device Nodes in /dev.
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Stopping Remount Root and Kernel File Systems...
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Stopped Remount Root and Kernel File Systems.
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Starting Shutdown.
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Reached target Shutdown.
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Starting Final Step.
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Reached target Final Step.
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Starting Reboot...
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Shutting down.
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd[1]: Failed to set timeout to 120s: Invalid argument
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 kernel: watchdog: watchdog0: watchdog did not stop!
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 kernel: systemd-shutdow: 41 output lines suppressed due to ratelimiting
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Sep 10 22:07:41 ultimakersystem-ccbdd3002925 systemd-journal[123]: Journal stopped

     

    • Link to post
    Share on other sites
    ColoRich

    ColoRich 1

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17
    On 9/8/2021 at 2:04 PM, gr5 said:

    @CarloK - I think I know some other people who would be interested in this.  Assume we know linux - how to ssh to the machine, locate and edit files.  But not what edits to make.  Also where would the sensor plug in?


    @gr5  I’m only assuming here, but my UM3 has existing connectors located behind each of the feeders [supposedly] for this exact purpose, but it was never brought to fruition.

    • Link to post
    Share on other sites
    gr5

    gr5 2,024

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    If you aren't using Digital Factory then I'm not sure there is any reason to update the firmware.

     

    If you have a strong need of some feature then I recommend getting the Olimiex-serial-F cable.  You can take the cover off the bottom of the printer and hook up that cable.  Make sure you can get a login prompt and if that's working then start the update process.  You will get a stream of information from the update process which outputs lots of great, informative details about which step it is on and when it fails it then tries to fall back onto the existing version.

     

    Save the log and post it.  Or just read it.

     

    Is it possible you just don't wait long enough?  There is a step in one of the upgrades (lost track which one) where it updates all the material files to the a new internal format and this step can take quite a while - maybe 30 minutes?  Not sure.  Something like that.

     

    Another option is to try the "unbricking procedure" aka "system restore".  It involves putting the latest version on a uSD card and putting that into the computer under your printer.

     

    But if you don't need any particular feature, I would just not worry about it.

    • Link to post
    Share on other sites
    CarloK

    CarloK 196

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    @sisu v5.2.16 works great, so there is no immediate reason to upgrade. Most important changes are improvements to the Digital Factory and some bug fixes in Active Leveling.

    As you noticed, the warning in the 5-th last line of your log is weird. It does ring a bell, but 5.2.16 is more than 2 years ago and I can't find the change in our code base. I suspect a problem with the update-bootloader program in your printer.
    You can also install the 5.2.18 version using the recovery method by inserting a micro-sd in the bottom of the printer.
    Check this guide for more info:

     

    • Link to post
    Share on other sites
    sisu

    sisu 0

    Posted
    Posted (edited) · Ultimaker 3 Firmware update: 5.2.17

    We have left the printer on for several hours during the update with no luck. I could try that again; I may have only tried that with the .17 firmware.

    I read that the .17/.18 firmware update includes support for PETG profiles. That could be of interest to us in the future, but this is not urgent.

     

    Thanks everyone for your help. 

     

     

     

     

     

    Edited by sisu
    • Link to post
    Share on other sites
    ddrsarah

    ddrsarah 0

    Posted
    Posted · Ultimaker 3 Firmware update: 5.2.17

    Just adding I've had nothing but problems with the latest firmware version on my UM3E. I have a UM3 thats running just fine.

     

    * Active leveling constantly can't be performed 

    * Can't even turn off active leveling because the manual leveling values don't store correctly

    * Prints stopping mid-print, the timer still remains but the print head is frozen 

     

    I've been fighting with my UM3E for weeks now and I'm ready to throw it into the sun. Wholly disappointed in the lifespan of this printer. 

    • 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
     Share
    Followers 10
    Go to topic listing

    • Our picks

      • UltiMaker Cura 5.3 stable released

        UltiMaker Cura 5.3 stable released

        ArunC posted a topic in UltiMaker Cura,

        In this stable release, Cura 5.3 achieves yet another huge leap forward in 3D printing thanks to material interlocking! As well as introducing an expanded recommended print settings menu and lots of print quality improvements. Not to mention, a whole bunch of new printer profiles for non-UltiMaker printers!
          • Thanks
          • Like
        • 56 replies
        MariMakes

        Picked By

        MariMakes,
      • Here it is. The new UltiMaker S7

        Here it is. The new UltiMaker S7

        MariMakes posted a topic in Official news,

        The UltiMaker S7 is built on the success of the UltiMaker S5 and its design decisions were heavily based on feedback from customers.
         
         
        So what’s new?
        The obvious change is the S7’s height. It now includes an integrated Air Manager. This filters the exhaust air of every print and also improves build temperature stability. To further enclose the build chamber the S7 only has one magnetically latched door.
         
        The build stack has also been completely redesigned. A PEI-coated flexible steel build plate makes a big difference to productivity. Not only do you not need tools to pop a printed part off. But we also don’t recommend using or adhesion structures for UltiMaker materials (except PC, because...it’s PC). Along with that, 4 pins and 25 magnets make it easy to replace the flex plate perfectly – even with one hand.
         
        The re-engineered print head has an inductive sensor which reduces noise when probing the build plate. This effectively makes it much harder to not achieve a perfect first layer, improving overall print success. We also reversed the front fan direction (fewer plastic hairs, less maintenance), made the print core door magnets stronger, and add a sensor that helps avoid flooding.
         

         
        The UltiMaker S7 also includes quality of life improvements:
        Reliable bed tilt compensation (no more thumbscrews) 2.4 and 5 GHz Wi-Fi A 1080p camera (mounted higher for a better view) Compatibility with 280+ Marketplace materials Compatibility with S5 project files (no reslicing needed) And a whole lot more  
        Curious to see the S7 in action?
        We’re hosting a free tech demo on February 7.
        It will be live and you can ask any questions to our CTO, Miguel Calvo.
        Register here for the Webinar
          • Like
        • 18 replies
        MariMakes

        Picked By

        MariMakes,
      • UltiMaker Cura Alpha 🎄 Tree Support Spotlight 🎄

        Cura Alpha With New Tree Support 🎄

        MariMakes posted a topic in UltiMaker Cura,

        Are you a fan of tree support, but dislike the removal process and the amount of filament it uses? Then we would like to invite you to try this special release of UltiMaker Cura. Brought to you by our special community contributor @thomasrahm
         
        We generated a special version of Cura 5.2 called 5.3.0 Alpha + Xmas. The only changes we introduced compared to UltiMaker Cura 5.2.1 are those which are needed for the new supports. So keep in mind, this is not a sneak peek for Cura 5.3 (there are some really cool new features coming up) but a spotlight release highlighting this new version of tree supports.  
          • Like
        • 29 replies
        MariMakes

        Picked By

        MariMakes,
      View All
    ×
    ×
    • Create New...