jseriff

Hi, I have an Ultimaker S5 that has not been used heavily for the last 2 years, and I'm looking to sell it as well as all of the accessories and 2.85mm filament i have. Details: * Ultimaker S5 * Builtak Build Plate + PEI flex steel sheet * 5 ultimaker print cores (0.25, 0.4x2, 0.8, 0.4BB) * 3D Solex print core with various nozzles * 10+ rolls of 2.85mm filament in various materials/colors - both ultimaker and 3rd party brands The only known issue with the printer is that the onboard wifi is unreliable - it works well either hardwired or with an ethernet -> wifi adapter. I have the original box and packaging, but i'd strongly prefer a local buyer for pickup/delivery. Looking to move it - willing to entertain any reasonable offers

Unfortunately, I am on 5.7.2, and continue to see the issue. I have not seem any changes in the issue in the last 12 months, and I generally upgrade to the latest firmware within a few weeks of its release.

I have this same issue on an S5. The logs fill up with ~85MB over several days, filling the device entirely. At that point, the S5 shows as being on the network, but is basically inoperable. There are three ways I've found to get the printer back into an operable state: 1) Factory Reset 2) Cura Connect Reset 3) SSH into the printer, and clean the log files directory, then reboot the printer (via the CLI) Once one of those three steps is taken, the printer will be operable again for between 2 and 10 days, at which point the cycle repeats. The root cause appears to be network connectivity issues - the printer appears to have network connectivity issues when under load (the laptop next to the printer does not exhibit any connectivity issues, and the printer is showing full signal). I see excessive avahi logs, as well as the printer's software having trouble getting firmware version information, or hitting its own API, causing it to log large python stack traces. Long term, it would be great to get a more stable network connection, as this has other issues (Cura will frequently not be able to show the status of the print, despite the printer thinking it has a network connection - this will come and go as a print is operating). Short term, monitoring the size of the log directory and removing old files, or modifying the rotation settings would be a great help.