One of our counters stopped transmitting to the gateway. A day later we went out and found that nothing was visibly wrong. As soon as we cycled power to the device, it immediately began transmitting again. Is this a known issue that we should be aware of? Any ideas why this occurred?
Resetting the device is not a major issue, but in doing so, the counted total is reset, and it throws off our software. Is there any way to make the count non-volatile?
What is the firmware version of this device?
The hardware has EEPROM nad if we write too many times, it will wear off the memory.
In future hardware, we are planning to put a FRAM that can store in a non-volatile state.
Firmware version 3. When it stopped communicating the counts were only at ~2,000. On any (3) of our counter modules, if you turn the device off and back on, the counts are lost.
Ok, it was my understanding that eeprom data was available after a power loss.
Counter is changing every 2 minutes or so. Wired to a open collector output on a meter.
Any idea why it needed to be powered down and back on to re-establish communication to the gateway?
Ok thanks. We have the transmission delay set to 10 minutes. So even if the counter stops increasing, we still get transmissions every 10 minutes. In this circumstance however we received no data until we reset it. Another one of the counters has accumulated >12,000 counts and has not had an issue, yet.