09-02-2021, 06:21 PM
If we introduced an issue in a recent firmware we'll need some help to narrow it down since we've never seen this happen in development or testing. It is probably not coincidence that these 3 reports all came in a weeks time. Meaning, we possibly introduced a new issue with the firmware that fixed a different patch saving issue.
It would be most helpful if we could get the contents of MRCC's preset files when the error happens. It requires removing the left side end-cap with a 2.5mm hex key, take out the microSD card, plug it into a computer and make a zip file of the entire directory structure.
If we see an error in the file it will likely be an easy fix. It could be something as simple as a certain combination of settings creates some bad data.
It would be most helpful if we could get the contents of MRCC's preset files when the error happens. It requires removing the left side end-cap with a 2.5mm hex key, take out the microSD card, plug it into a computer and make a zip file of the entire directory structure.
If we see an error in the file it will likely be an easy fix. It could be something as simple as a certain combination of settings creates some bad data.