sj3fk3

Can you also tell us, is it Ultimaker material (with NFC) or is it? 3rd party? and what firmware version is the printer running on? I agree with @carbon that changing bays might be the best option for now. Or does that not help?

--> https://github.com/Ultimaker/UltimakerMarlin

I think it's almost just as frustrating for us as it is for you. We really care about our product, all the engineers working on our printers do. Everybody in the S-Line firmware team is an active user also for instance, so we all use the printers daily, not only to test but also to create things for ourselves. That's the problem! It's like hunting a ghost, we don't see it.. Logs don't show us any information that we can use.. We even had several printers dedicated to testing wifi only (24/7) but don't see any reproducible issues. You mentioned 5.8Ghz wifi in the other post. While the chipset in some S5's is capable of doing 5Ghz, we don't actually support it. I know that having a so called mixed network (2.4Ghz and 5.8Ghz networks with the same SSID) can cause connection issues. In those cases it's better to append _5G to the 5.8Ghz network. (Many wifi Access Points recommend this by default).

Hold on! I did not say that. Not even close! I said: "of course ethernet is going to be more reliable than wifi". I did not say you could not connect you printer with wifi. You even quote me saying that we connect hundreds of printers over wifi. And we use ordinary office wifi like any other office and it works. I also have printers at home and they also 100% connect to wifi. I also have devices that have difficulty connecting to wifi (mostly homebrew ESP32 devices). I do not however have devices that have difficulty connecting over ethernet, because it's more reliable or less prone to interference. We have been looking into it, we still are looking into it. We have uptil now not found anything technically wrong with the wifi setup that could explain any of the symptoms that are been described by some customers. Maybe we have to look more into the connection between Cura / Digital Factory and the printer. Maybe it's not wifi but something else, or maybe it's 2 completely different issues, but they look the same. Because the WifI on the UM2 and UM3 is completely different from the WiFi on the S3 / S5. Different chipset, different drivers, different OS even.

If not defined by a material profile, the default value is: the material should stay in "parked" for 2 hours. Sounds like you might have an issue in your material profile. Is it generic? Or is it a selfmade one? What material is used? Do you have a spool of Ultimaker material and could you see how it works with say Ultimaker PLA?

What we want to do is show the 5 or 6 most used materials in the first list then you can click "show the rest" where you can dive deep and select an other. The idea is that in 80% of the time one only uses up to 5-6 materials. Yes, if you turn on the firewall you can only print via DF or USB (of course). Personally I prefer printing via cloud. It might sound strange, but it's faster for me? To sync materials you currently do need to disable the firewall, we are working on a alternative way of updating materials, but that will take some time.

There was a bug in 6.1.0 that was triggered in about 1 in 100 cases. (Technically the upgrade worked and if you had dev-mode on it was easily fixed). This bug is fixed in 6.1.1 and it should be safe to upgrade. Currently there are 500+ S5's already on 6.1.1. with out any issue.

Does this problem persist? If so, could you please contact support about it? Do you remember where the printhead was before you started the upgrade?

It is one of the reasons why we are changing our release schedule. We are going to work with a Stable and Latest channel. People who want latest and greatest can just stay on latest (about 8 releases per year) and always get updates. People who want more stability can choose "Stable". We will only release about 3 times a year to Stable and only with features that are already (previously) released to Latest. We are indeed spending more and more time on this issue. We do not only extensively test all releases with many different configurations (both hardware and firmware), but we are also looking at making the whole process more robust. On top of that, we are also looking at ways to have easier fail-modes where you can recover when something went wrong. Thanks for your very constructive feedback! I hope, I was able to answer some of your questions. We are working very hard on improving upgrading and although I'm not sure if a USB key is the way I will look into this.

Hmm, that is not the case, you can still use local network (directly print from Cura to your printer) with 6.1.1 I sure hope you have discovered this by now 🙂

The release notes did not clearly state this?

WiFi will always (also in 2021) be less reliable than ethernet. That has nothing to do with 10+ yr old ideas but with 100+ yr old physics. There will always be more interference on the 2.4Ghz band (try wifi near a microwave) and 5Ghz (not supported by the printers btw) only works well when you are really near to the AP. Ethernet with UTP has near to none interference (unless your cable is more than 100m). The UM3 and S5 have different wifi chipsets as far as I know. Like I stated before, there a literally hundreds of UM printers that work well with wifi, but we always recommend using ethernet just because it's more reliable (obviously), that does not mean wifi will not work at all. If you have issues, I would suggest to contact support about it.

If you can reproduce this (make it happen again) we would like to see the logfiles. Could you then file a report with support? Because it should work the same as in 5.8.2.

Yes, and the firewall is not enabled by default.

With dev-mode activated ssh is on. I've used it myself on 5.8.x and now on 6.x

It could be that your wifi chip on that specific machine has issues? We literally have hundreds of S5's connected with wifi. Wifi is not as stable as ethernet of course, but it should work in most cases. What version of firmware are you using btw?

Do you mean 5.8.1? Or was it really 5.1.8?

Glad that you have found the issue!

If it's still on this screen for more than 20 minutes, try to reboot it. Upgrading specially with a Material Station can sometimes take longer because it might also upgrade the firmware of the material station. What was the version you upgraded from?

Firmware 6.1 is released as of a couple of minutes ago, see also https://support.ultimaker.com/hc/en-us/articles/360012055979 where you can find an alternative way of network provisioning (including fixed IP).

Printer / DF (Digital Factory) indeed don't care about the type of connection being ethernet or wifi, but it must have access to the "cloud" in order for DF to work (and this should work with the firewall turned on). If you want direct local network access to the printer (e.a. direct from cura to the printer or use the API on the printer) the firewall needs to be off.

Please DON'T try to downgrade it! It is not possible, we clearly state this with the release notes! 6.x is based on a different OS version, downgrading will most likely brick your printer! Wait for 6.1 to be released it will be here *really* soon, try upgrading it will also give some new possibilities to (network) provision your printer.

I'm 100% sure it is not the firmware. We did not change anything network related between 5.7 and 5.8.2. When connected to ethernet are you still able to ping the ip of the printer? If not maybe there is something wrong with the cable or the connector or the switch-port.

I could look into making it a variable within some kind of advanced user-setting menu.

Could you also unload all materiaal from the printer into the Material station and then reboot the printer? See if everything starts to work normally again. I would be very interested to see if that solves your issues.