CumulusMX Help

[txweather]

Steve,

Looks like that got me further.

On the logs I now see:

Code: Select all

2016-01-04 09:28:34.050 Loaded archive record for Page=30 Record=3 Timestamp=12/27/2015 12:30:00 AM
2016-01-04 09:28:34.051 Ignoring old archive data
2016-01-04 09:28:34.051 150archive entries processed
2016-01-04 09:28:34.052 Loaded archive record for Page=30 Record=4 Timestamp=12/27/2015 12:35:00 AM
2016-01-04 09:28:34.052 Ignoring old archive data
2016-01-04 09:28:34.053 151archive entries processed

and now the web interface values are set to -- -- instead of 0.

Also, Here is a screen shoot of the logger unable to grab data (Note: Red on the min means is unable to grab data) as CumulusMX is connected.
This does not happen when I use Cumulus.



I am running a test to see if its holding the logger while it downloads the archives and releases it when its done.

Will report back.

[steve]

Yes, the logger has now sent it the entire contents, so it will take a little time to process that and discard it (as its old data) and then it should switch to reading live data.

[txweather]

Yes, the logger has now sent it the entire contents, so it will take a little time to process that and discard it (as its old data) and then it should switch to reading live data.

Well.... All working now.

For those Meteohub users out there that would like to do this...
As pointed by Steve:

On Cumulus.ini make sure you set DavisIPResponseTime=5000 (The intervals are in milliseconds and you can set it to your liking's... The lower the faster but you want it at least grater than 1000) as new entry under [Station ]

Note: While CumulusMX is downloading the archive data, it will hold your logger hostage and during this period meteohub wont be able to access the sensors.
Once the download of the archive records is done it will release the logger and meteohub will resume its operations. Unlike Cumulus, CumulusMX wont show any data untill its done processing all archives.
This will apply for the Windows and Linux version of CumulusMX.

Thank you all for the help and support!

[steve]

While CumulusMX is downloading the archive data, it will hold your logger hostage and during this period meteohub wont be able to access the sensors.
Once the download of the archive records is done it will release the logger and meteohub will resume its operations.

It's not really a question of it "holding" or "releasing" the logger, as there is no such concept. Cumulus connects when it starts up, and disconnects when it closes down.

I have no idea how Meteohub operates the "pass through" facility (but presumably it performs the various operations on behalf of the connected software, and then relays the results back), but because of the way the Davis logger works, it simply isn't possible for something to read live data while the logger is in the middle of sending archive data, the two operations would clash.

[txweather]

While CumulusMX is downloading the archive data, it will hold your logger hostage and during this period meteohub wont be able to access the sensors.
Once the download of the archive records is done it will release the logger and meteohub will resume its operations.

It's not really a question of it "holding" or "releasing" the logger, as there is no such concept. Cumulus connects when it starts up, and disconnects when it closes down.

I have no idea how Meteohub operates the "pass through" facility (but presumably it performs the various operations on behalf of the connected software, and then relays the results back), but because of the way the Davis logger works, it simply isn't possible for something to read live data while the logger is in the middle of sending archive data, the two operations would clash.

Thank you for the clarification!