Quote
Roxy
Did you do a M502 followed by a M500 ?
Good call, its quite possible that there are values stored in EEPROM that are not compatible with the current build.
IF so its pulling the values on boot but then cant store them back with the E500 causing the CRC errors.
M502 to ensure all default 1.1.5 values are loaded from configuration.h first then clear current stored values by M500 to push in known good values that work with 1.1.5
I am sure Clif knows to do a full re calibration after this, I am putting in this last bit of info for other readers that may come across this post in the future.