03-01-2015, 13:44
Hi,
Your Nano or it's eeprom is not likely bad, only values saved to eeprom might be not valid. WeatherDuino saves measurement to eeprom every now and then and reads them when necessary. Eeprom keeps it's values when Nano is not powered. For new Nano's I have seen eeprom filled with random values and it's wise to clear eeprom before using Nano for real application. There was a good instructions by uncle_bob how to clear whole eeprom memory. I assume that your problems were related to wrong TX board initial eeprom values, which were later on distributed to RX units and Cumulus. They both remember wrong values and should be cleared accordingly. RX/TX codes could not have "erase_eeprom()" enabled all the time, since that would destroy their "long time memory".
Your Nano or it's eeprom is not likely bad, only values saved to eeprom might be not valid. WeatherDuino saves measurement to eeprom every now and then and reads them when necessary. Eeprom keeps it's values when Nano is not powered. For new Nano's I have seen eeprom filled with random values and it's wise to clear eeprom before using Nano for real application. There was a good instructions by uncle_bob how to clear whole eeprom memory. I assume that your problems were related to wrong TX board initial eeprom values, which were later on distributed to RX units and Cumulus. They both remember wrong values and should be cleared accordingly. RX/TX codes could not have "erase_eeprom()" enabled all the time, since that would destroy their "long time memory".