Cumulus Support

The only explanation I can offer is that either the clock on your Pi is not actually correct, or there is an issue with the console where it is not displaying the time that has been set. MX is clearly setting the console clock to the same time as the Pi, reading it back confirms that.

I found something very interesting. Normally this console is plugged into a wall power supply but also has batteries installed. When I was running v1.9.4 I had it on a shelf near my Win2003 Server that was running Cumulus. When I started with the RPi and MX, I moved it over to a desk so I could have the RPi plugged into a monitor and the console connected. When I moved the console, I unplugged the power and it seemed to be running fine so I left it on battery power. It's been running that way for a couple of days with no apparent problems.

Since this clock problem was peculiar, I plugged the power supply back into the console and restarted MX. When I did, the console clock display updated correctly! So, I went ahead and unplugged the wall power supply putting it back on battery power. As soon as I did this, the clock display lost 24 minutes. I plugged the power supply back in, restarted MX, and the clock was back to normal.

What is even stranger is my custom Davis Stats web page using the <#battery> webtag shows 4.70v when plugged into the power supply and 4.68v on battery. I wonder if Davis is really reporting a valid console battery level since this appears to be some kind of a power issue?

Perhaps this is a problem with fw 3.15 - I'm using 3.12 and I don't have these issues.

Or possibly a hardware issue. Is you console newer or several years old? I had one console that I bought back in 2011. At the beginning of this year, I had several problems with communications drops between my console and the ISS and issues with something (console or ISS) inventing rain. I went round and round with Davis Tech Support and ended up replacing the ISS transmitter and the console main board.

None of that actually seemed to solve the problems 100% so I bought a new console. The console was new enough that my old USB datalogger wouldn't work with it and I had to exchange my old datalogger for a new one from Davis. The new console was better but didn't fix the comm lockups 100% either. Now that I have two consoles though, it's obvious that the datalogger is the source of the comm problem because my datalogging console will lose comms while the other one is receiving fine - but that is a topic for another post.

I'm wondering if there is something different in the hardware of the newer consoles or dataloggers.

My console is from 2006.