Recent Posts

Pages: [1] 2 3 ... 10
1
LOOP(2) might miss values but the archive record (DMP/DMPAFT in the serial protocol docs) has them, like additional temp and humidity sensor data.

Um, yes but aren't we talking about a whole bunch of different things here and I think they're in danger of getting mixed up. Current conditions uploads may typically be uploaded eg every minute, if not more often, whereas new archive records will be generated with 5 or 10 minutes as a commonly-used interval. This needs a much longer post to really nail down.
2
Quote
I find that difficult to believe - there's a lot of readings in LOOP that are missing in LOOP2 like many of the supplementary sensor readings. I always imagined that Cumulus (or maybe CMX) polls for LOOP and LOOP2. But I've never had cause to look into it in detail.
Far from my understanding how it all works but from what I have read Cumulus1 uses the Davis DLL and some of LOOP1.  But LOOP2 use was introduced with CumulusMX.

Quote
With auto pause cooperating won't be a problem any more. It works perfectly good. Much better I was suspecting.
Looking forward to trying that with CumulusMX.

Paul
3
LOOP(2) might miss values but the archive record (DMP/DMPAFT in the serial protocol docs) has them, like additional temp and humidity sensor data.
4
Watch the walkthrough video?

https://www.youtube.com/watch?v=gEWsAeQB0R8

The speaker would make a good hypnotist but there's plenty of detail there.
5
PaulMy noted that the still most used Cumulus version, never uses LOOP (LOOP2 more precisely) data.

I find that difficult to believe - there's a lot of readings in LOOP that are missing in LOOP2 like many of the supplementary sensor readings. While there is some overlap, LOOP2 is more of a supplement to LOOP - LOOP2 includes several extra values but also omits several (has to really, since they're both 99-byte packets). I always imagined that Cumulus (or maybe CMX) polls for LOOP and LOOP2. But I've never had cause to look into it in detail.
6
First, from what you wrote it seemed like the RE you've done showed that WL only queries the logger for archive data when it's time to upload. Contacting the logger only before upload can mean only one thing: reading an archive record. Did I misinterpret that?

I said that the only software where I can verify if archive records are used is WeeWx since the source code is available. WeeWx uploads archive records at the frequency you set - in older versions it had to match the logger interval, but in more recent versions it's not required - IIRC it repeats the last record. This might answer one of your questions.

PaulMy noted that the still most used Cumulus version, never uses LOOP (LOOP2 more precisely) data.

I don't know anything about the WL software, I've never used it. WU, PWS, Awekas, WOW etc. expect a record in the format defined by their own API. They have no means to check how they're generated, and most likely they don't care; but they support existing proven methods, which mostly mean supporting some existing software.
7
Some changes may have been made through the ongoing development of CumulusMX so the extent of LOOP2 use may have changed.
I have tested WiFiLogger with CumulusMX a few weeks ago and the only issue was the communication issue due to more than one program trying to get access.

Cumulus1 does not use LOOP2. 

LOOP2 has dew point and wind gust, that why WFL needs software 1.90+. There is no reason to use old console software. Many peoples are thinking that console update will make it GREEN DOT sensitivite. It won't be. You can only earn more data on it.

With auto pause cooperating won't be a problem any more. It works perfectly good. Much better I was suspecting.
8
It's worth noting that before upload you can only query archive or hilo data, not real-time loop data, since that needs to be accumulated for the duration of the archive interval (OK, technically you can query LOOP data but makes little sense here). Isn't there a bit of mix up?

I just don't know, what to say.
1. WU, PWS, Awekas, WOW etc. don't expect arch. records. They expect current data with time of reading. So WFL is sending max 4s old data. I can change that to 1s if you like. We can say that arch. records are not allowed, because arch. rec. are statistical data and those services makes own statistic.
2. Show me the proof that any of those programs are sending arch. records, when uploads are the same like current loop readings and uploaded data sent is not even a bit similar to the arch. records
3. With 30 min arch. interval. WFL should transmit every 1min same old archive data?
4. There can be only an option to synchronized uploads with arch. records interval and then option to use those statistical data instead of current data readings. This is an option which most programs don't use, but I agree that is very ok to use it.
9
Quote
TBH I'd assumed that with most software the default was to use only LOOP data, with archive being reserved for catch-up scenarios. But not looked into it in great detail.

From the original CumulusMX announcement
Quote
A note to Davis owners:
I am experimenting with the use of the LOOP2 packet. The current code uses this for two purposes. First, it uses the 'peak 10-minute gust' value, to avoid the problem where a gust might be missed (although hopefully this will not be such an issue with Cumulus MX as it does not use the Davis DLL), and secondly it uses the 'absolute pressure' value to make calculation of 'altimeter pressure' easier and more accurate. This is mainly used if you upload to CWOP.

The LOOP2 packet is supported on the VP2 with firmware version 1.90 or later, and on the Vue. If you have a Vantage Pro (i.e. the original 'VP1'), or a VP2 with pre-1.90 firmware, or if you are using Virtual VP, none of these support the LOOP2 packet. In these cases, you should edit cumulus.ini and add a line to the [Station] section:

UseDavisLoop2=0
Some changes may have been made through the ongoing development of CumulusMX so the extent of LOOP2 use may have changed.
I have tested WiFiLogger with CumulusMX a few weeks ago and the only issue was the communication issue due to more than one program trying to get access.

Cumulus1 does not use LOOP2. 

Paul
10
Quote
Quote
Do you think that WeatherLink or Cumulus is sending archive records to WU, PWS, WOW Awekas etc.?
I don't think Cumulus is sending archive records to those sites, however Cumulus has settings to "Catch Up" to send to PWS, WB, WU and WOW from the time of Cumulus shut down and a restart.
Paul
I forgot to say, and you likely already knew this,  that the Catch up data is then at the logger interval.  It is highly recommended that the logger and Cumulus data are set at the same interval otherwise issues can arise.
Paul
Pages: [1] 2 3 ... 10
anything