Cumulus Support

Sorry, I couldn't think of a better subject line!

A couple of issues:

1. When Cumulus updates the time on my VP2 console at 4am it makes the logger miss a record. When I later download the logger contents into Weatherlink, the 4am record is missing. I guess this is because the time drift on my PC is just right that the console never sees an exact 04:00:00 because Cumulus updates it frpm 03:59:59 to 04:00:01 (or something like that). Is there a way of making Cumulus update the console at, say, 04:05:00 - or something?

2. I log at 10 minute intervals on the DVP2 and in Cumulus. If I end Cumulus before a 10 minute boundary and restart it after the next boundary, then when Cumulus downloads from the DVP2 logger a single record is missed.

For example:
at, say, 15:05, I end Cumulus and start it again at 15:15, the 15:10 record is not downloaded and is forever lost.

If I end Cumulus and restart it within a logging interval, say ending at 15:05 and starting at 15:06, then no records are missed.

Has anyone else noticed this?

Adrian Hudson wrote:1. When Cumulus updates the time on my VP2 console at 4am it makes the logger miss a record. When I later download the logger contents into Weatherlink, the 4am record is missing. I guess this is because the time drift on my PC is just right that the console never sees an exact 04:00:00 because Cumulus updates it frpm 03:59:59 to 04:00:01 (or something like that). Is there a way of making Cumulus update the console at, say, 04:05:00 - or something?

I think I would have to make the exact time configurable. As Cumulus has to be running at the time it's not a problem for Cumulus as it doesn't need the logger entry anyway.

2. I log at 10 minute intervals on the DVP2 and in Cumulus. If I end Cumulus before a 10 minute boundary and restart it after the next boundary, then when Cumulus downloads from the DVP2 logger a single record is missed.

Yes, the Davis DLL never supplies the latest entry. I can't remember whether it's specifically down to the DLL or the console.

Its no big deal. I can update the console manually. I'm sure it doesn't matter if its a few seconds adrift from the PC (or does it??)

...and that dll seems rubbish!

Actually, thinking about it (and am guessing here), probably changing the time update to starting at around 30 seconds past the minute would fix it. Perhaps you could put this in the next update, if you remember!

Thanks Steve

Adrian Hudson wrote:Its no big deal. I can update the console manually. I'm sure it doesn't matter if its a few seconds adrift from the PC (or does it??)

I don't think so, no.

...and that dll seems rubbish!

I've just done a test without the DLL, and I can confirm that it is the DLL and not the console. You get all of the entries when you ask for them directly. I regretted using the DLL not long after I started using it, but it's such a lot of code to rewrite to avoid it. But the cross-platform version of Cumulus I'm working on can't use it anyway, so I'm having to rewrite the code for that.

Actually, thinking about it (and am guessing here), probably changing the time update to starting at around 30 seconds past the minute would fix it. Perhaps you could put this in the next update, if you remember!

That might be tricky, but I'll ponder it.