It finally came back after rebooting a couple times. This seems to happen every time it does a firmware update. Next time I'll run it from the USB to rule out any network issues.
Is the upgrade process to 7.0 on the S5 running 5.8.2 reliable and robust?
I've had the machine almost a year and I've held off on the firmware upgrades due to reports here and elsewhere of users 'bricking' machines when attempting such an upgrade.
When I upgraded to the latest Cura, it generates a front panel version warning when I submit print jobs and one of the team replied in another thread that I need to upgrade the firmware to resolve that.
I just want to be sure I'm not going down a black hole that will take a service call to recover from.
Thanks.
The S-line printers have 2 release channels: Stable and Latest
As the naming suggests, Stable is for the environments where users give more priority to stability than to newest features. This channel receives about 3 updates per year, mostly bug fixes. Current release is v6.2.3
'Latest' is also a well tested release, but here new features are introduced that still have to prove themselves in the wild. This channel receives about 10 updates per year, a combination of bug fixes and new features. Current release is v7.0.0
Release notes: https://support.ultimaker.com/hc/en-us/articles/360012055979-Ultimaker-S-line-firmware-release-notes
Thanks.
I just downloaded both the Latest and Stable and I'll probably try it with the Stable release, at least at first.
Since the upgrade from 5.8.x to 6.5.x appears to be a true 'trap door' situation, I want to be 100% sure of it before I try it.
I feel more comfortable doing it locally from a memory stick than to risk a network disruption during the process.
Updating from 5.8 to 6.x is indeed a one-way update. Since changes will be made to the internal drive structure it isn't easy to do a downgrade. Installing an old firmware is always possible using the SD-card based recovery procedure, but not recommended on the early S5 models because you have to open the casing and hazardous voltages are inside.
Use whatever update procedure makes you feel more comfortable. A network interruption is not going to create a problem during the update process; first the whole new image is downloaded and verified before real installation starts.
It just finished and a test print (a 20mm calibration cube) is now printing.
It took less clock time than I expected. The only thing I noticed is that it appeared to wait at the '2 minutes to finish' point slightly longer than two minutes.
- 3 weeks later...
@jsw as far as I know the long wait at the end of the print was fixed in 7.0.0.
Though we're also waiting for the buildplate to cool down and if you use a material station for the material to deprime and park above the printhead.
@CarloK ahh, yeah that is just an approximate guess.
Installed new fermware on my S5 locked on splash screen for 10 minutes or more...
Turned S5 off then on S5 does not boot to Ready to Print, screen just shows Ultimaker
What next?
my printer is down!
need it now
22 hours ago, RogueWave said:Installed new fermware on my S5 locked on splash screen for 10 minutes or more...
Turned S5 off then on S5 does not boot to Ready to Print, screen just shows Ultimaker
What next?
my printer is down!
need it now
TURNING THE S5 OFF then ON severaal times fixed the hang up...works fine
For other people - leave the printer on for at least 3 minutes as sometimes it can take almost that long. If it has done nothing for more than 15 minutes there isn't much point to let it keep going and better to power cycle.
There is an unbricking procedure but it is difficult and can take half a day if you haven't done it before. And requires special tools for the S5 to remove the bottom (easier I think on S3 and UM2+C). And the unbricking requires a uSD card.
- 2 weeks later...
My S5 was turned off for one day and tryed to power it up but failed after 10 minutes. cycling on/off booted up normally within couple of minutes ......certain a bug to find
Hi,
ive got a strange situation.
I updated and my S5 is working fine.
Now after a couple days, i found this with my setup :
S5 latest udpate, wifi connected
Computer Linux latest CURA 4.11.0
If i start the software first at my computer, and then my S5 it wont boot after the ULTIMAKER name showing up in the display.
If i first boot my S5 and after the complete checkup and boot and start my software, its working without troubles.
I could reproduce this now already a couple of times, anybody else too ??
- 1 month later...
I noticed a little bug in the firmware, I’m on the latest 7.0.2.
When clicking "Skip cooldown" in the …-menu after a print finished, it skips, but the menu itself doesn’t disappear. The buttons are gone but there’s the black box, that was the menu before, still on the screen. It disappears when I tap the screen. I shot a quick video:
- 6 months later...
After upgrading to Firmware 7.0.4 the ethernet as well as wifi stopped working. I have a new S3 (2022) and the ethernet connection was perfectly fine until I upgraded to the firmware.
Now, when I click the switch next to the ethernet setting on the S3 screen, it shows a wait icon for about 30 seconds and then goes back to the off-switch icon. The lights on the network switch doesn't even blink once. I tried turning on/off the S3. I unplugged the network cable from the S3 and connected it to my laptop and the internet/network connection is perfectly fine.
On the wifi side, when I start wifi setup on the S3 network settings, it creates a hotspot, but it is nowhere to be found on my computer, on my phone or on my tablet's wifi lists. I tried to enter the wifi hotspot name manually in the network setting of my computer but it cannot find it.
There is a forum post from 2020 with a similar problem and they resolved it by trying different network ports, which doesn't make any sense in my case since the same network connection works on any other device but the S3. But, to rule out any possibilities I even tried that; I tested 5 different cables and ports, which work with other devices but none of them works with S3.
One odd situation is the release notes screen under maintenance > diagnostics > check release notes shows "Release notes '/tmp/release_notes.md' not found".
I would appreciate any suggestions?
I would try downgrading the firmware. You can put the older firmware on a USB flash drive and install the version that was working for you. Maybe do a factory reset afterwards. Actually that reminds me - in maintenance there is some kind of reset. Maybe "network reset" or "digital factory reset" or something like that - it resets all network related things and fixes all manner of networking issues.
Does the S3 have developer mode? I think that was taken away in a firmware release. But if it does - and you seem unusually good at networking stuff - then I'd have you ssh into the machine (root/ultimaker) and run connman which is the utility to control both ethernet and wifi. You can google connman commands on the internet. Note: 2 "n"s in connman.
@Smithy or @Dim3nsioneer might have ideas as they know this stuff better than me.
Also check the wifi antenna connection maybe?
-
1
Dim3nsioneer 557
16 minutes ago, gr5 said:"digital factory reset" or something like that - it resets all network related things and fixes all manner of networking issues
That is certainly worth trying first. If that doesn't help, a factory reset (reset all printer settings) might be necessary.
7.0.4 is the current firmware of the 'latest' channel. If you switch to the 'stable' channel, you will get 7.0.3. That change might also be something to consider.
Thank you for the blazing fast response, gr5 and Dim3nsioneer. I just did a "reset all printer settings" and during the initial setup it asked me to setup wifi and this time the hotspot showed up on my laptop and I was able to setup the wifi.
Ethernet option is still not working, but I am able to use the printer through wifi.
Unless I encounter another issue I won't downgrade, but that is a great idea.
PS. I wasn't able to ssh into S3 since the network on s3 seems to be completely off; the ethernet connection of s3 shows "down" on my network switch software. I assume the S3 ethernet setting is to turn it on/off.
sshd is disabled unless you go into "developer" mode. It's a setting in the menus but... I think they maybe removed that feature on the S3. It's still on the S5 and it *might* be on the S3 - I can't keep track. Maybe it's only the UM2+C where they removed developer mode. Once it's in that mode it also shows the ip address right at the top of the dispaly (for all screens I think). Only then is it worth trying to ssh. An alternative to getting into connman is you can buy a USB to Serial cable - I like the olimex-cable-f. You can connect that inside the base of the S3 near or on the computer (I'm not sure exactly where on the S3 - I know the S5 and UM3 better). Then you have console access. You can watch it boot and then you can log into root from there and access connman.
It's entirely possible that your ethernet died - something happened to the chip that does ethernet. But since it seems to have happened with an upgrade I'm guessing it's firmware related.
- Dustin unpinned this topic
Recommended Posts
wfin73 1
How long should this update take? My S3 has been on the splash screen for a couple hours now.
Link to post
Share on other sites
ccr90 2
@wfin73 the update shouldn't take that long to finish.
Normally it is not advised to switch off the printer during a firmware upgrade. If has been going on for that long it is safe to assume it has run into an issue.
Please try re-starting your printer and you may find out that the upgrade has been finished correctly.
Link to post
Share on other sites