OpenDACT 3.1 can compute negative tower offsets, FW interprets them as zero values #16
Description
Hello. Sometimes OpenDACT may produce negative values and try saving them in EEPROM.
Repetier discards these and saves zeroes to EEPROM instead. Yet it seems that OpenDACT thinks printer uses those negative values. In practice this usually leads to nozzle crashing into the bed on the next iteration.
I suggest checking for negative offset values (or, more broadly, negative values being suggested for any parameter) and checking for too big values (like offsets of 2000+ steps).
