Prusa-Support

Hello, thank you for the additional reports! Just to make sure, were these also solved with the renaming, right? @seb123212 @JazzX Alessandro Pantaleo Prusa Research

Hello, thank you for this update, good to hear it was resolved in all cases so far, but noted these different causes for our devs, hopefully it can be something...

Thank you for reporting this. Something may be taking up too much RAM memory. Am I understanding correctly that you are alternating g-code files running via USB flash drive and...

In the case of the issue https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/2351, this error can be reproduced but quite erratically. In that issue, what seems to increase the chances of the error to show up...

Hello! Thank you for your report, I passed this on to our devs to look into this in more detail and possibly reproduce. Just to make sure, which version of...

Thank you for the info! Alessandro Pantaleo Prusa Research

Thank you for the report. The steps describe how to reproduce the issue quite well. I could easily reproduce it. Our developers will look into this. Michele Moramarco Prusa Research

Thanks for getting in touch about this. It is possible that Prusa Connect is emitting a "ping" signal until the next operation. This doesn't sound concerning I would say, but...

This probably concerns both, MINI firmware and Prusa Link, but in the latter repository, we have a similar (or specular) open issue. https://github.com/prusa3d/Prusa-Link-Web/issues/251 These issues won't necessarily create a conflict...

This is work in progress. Meantime, a workaround could be adding _variables_ like `{timestamp}` to the _output file name format_ in Prusa Slicer, so that filenames will be unique. Alternatively,...