Cumulus Support

For the first time since owning it, my Pro2 console time didn't move forward. I had to manually do it this morning. I checked the timezone, that's set to Greenwich. Daylight savings is turned on and set to auto. I cannot work out why it didn't change?

It's not a huge problem. But, I wondered if anyone else has encountered this before?

We had our DST a couple weeks ago and like all years in the past, VP2, Vue and Cumulus consoles changed automatically, as did Cumulus and Weatherlink data files. My consoles are both plugged in to power and have batteries.

Paul

PaulMy wrote:We had our DST a couple weeks ago and like all years in the past, VP2, Vue and Cumulus consoles changed automatically, as did Cumulus and Weatherlink data files. My consoles are both plugged in to power and have batteries.

Paul

My VUE console moved forward too, and like you, both have batteries and are plugged in. I just can't understand why it didn't move forward, very strange.

I've just noticed that the console isn't keeping very good time either. I set it precisely to the PC time this morning, and the console clock would show a minute change at exactly the same time as the PC. Right now, it is 4 seconds out of sync.

Have you switched off the Cumulus time sync feature? That should set your console to match your computer time once a day.

mcrossley wrote:Have you switched off the Cumulus time sync feature? That should set your console to match your computer time once a day.

Hi Mark

That's checked. I didn't know Cumulus can control the console clock. Obviously, that hasn't been working for me. I presume clocks go forward and back at 2am?! I adjusted the console clock around 7am this morning, so five hours passed without it moving forward or synchronising.

By default it sets the console time at 04:00. Both my consoles changed over automatically, one connected to CMX the other standalone.

I've come back to this as I have noticed my console time is out of sync with my computer/CMX time again. I have the option checked in CMX to sync it, but it doesn't seem to make any difference. The console is ahead by 3 seconds and it'll keep increasing over the coming months. I have to manually set the the console time to the PC time when I see that it's happened.
No idea why it won't sync..

There should be some logging in the diags file when/if it tries to set the time, near the beginning of the file (i.e. just after startup) and then again just after 0400. May show something useful.

Hi Mapantz,

I highly doubt this would cause your issue, however noticed you are still running "Davis Console Firmware Version:3.15"
Current version is 3.80
Kind regards,

Hi there

Sorry for the late reply. Been out enjoying this heatwave.
That's in my diags. I manually synced the console clock on Friday, but it's back to around 1.5 seconds ahead of my PC clock.

I don't remember having this issue when I first got my console. The clock didn't go forward at the end of March, as I mentioned in the start of this thread. I have never touched the console in the 30 months it has been on the wall. I only checked to see if daylight saving was turned on, which it was.

re firmware Tony; I may update it later, although I don't like doing in in case there's a failure.

But later in the diags file there should be something about setting the console clock and reading it.

steve wrote:But later in the diags file there should be something about setting the console clock and reading it.

Out of a 5 day log file, this is the only instance:

It's apparently not attempting to set the station clock (otherwise there would be messages locked about it immediately before those lines, just after it prints the "Last update time = " message). I'm afraid I have no idea why that would be, if you had the setting selected at the time of that startup. You don't have another instance of the SyncDavisClock setting in the cumulus.ini file?

I'm back in here again lol

This seems to be an ongoing problem.

My Davis console failed to move forward. The console has daylight savings switched on. Cumulus MX has 'synchronise station clock' enabled (checked .ini file)
In fact, the time never ever sync's and so the time's end up out of kilter by 2 or 3 seconds and I have to manually sync the console.

I closed Cumulus MX and reopened it and my Davis console then synchronised. It surely has to be a bug? Bearing in mind, Cumulus MX is now on a new system, so it had this issue on my main PC and now my new mini server

If you turn on debug and data logging MX should show the time being set and read back.

It works ok with both my consoles, is anybody else having this problem?

Note, from memory I think the console time can only be set to the nearest minute, so a few seconds drift isn't significant.