Bad Calibration Data can be accepted as valid, causing no output volume
Closed this issue · 1 comments
danngreen commented
Need to look into how this could happen, but on one unit, upgrading from v0.13.0 to v0.13.3 causes the outputs to be silent. Re-calibrating fixes it. I presume some bad values were in flash, and were validated as OK on startup.
danngreen commented
Branch calibration_data_range tests the validate() function and it seems to be working OK.
Unfortunately the old bad calibration values are lost/overwritten so this might be hard to reproduce...