« previous next »
Pages: [1]   Go Down

Author Topic: Big problem with data update  (Read 4729 times)

0 Members and 1 Guest are viewing this topic.

Offline Guillaume_67370

  • Contributor
  • ***
  • Posts: 123
    • METEO OFFENHEIM
Big problem with data update
« on: February 12, 2014, 04:01:56 PM »
Hello,

I note something very strange.
Please find attached.

last heard 11 seconds (sometimes)

Logged

Offline Beaudog

  • Forecaster
  • *****
  • Posts: 1217
Re: Big problem with data update
« Reply #1 on: February 12, 2014, 04:59:10 PM »
I do not understand the problem. Mine are almost he same.
Logged

Offline Guillaume_67370

  • Contributor
  • ***
  • Posts: 123
    • METEO OFFENHEIM
Re: Big problem with data update
« Reply #2 on: February 13, 2014, 01:55:41 AM »
Quote from: Beaudog on February 12, 2014, 04:59:10 PM
I do not understand the problem. Mine are almost he same.

Normally last heard is always <1 second ...
Logged

Offline ericfynne

  • Contributor
  • ***
  • Posts: 139
Re: Big problem with data update
« Reply #3 on: February 13, 2014, 02:45:00 AM »
I think I would be more concerned that Virtual VP was saying that it hadn't read any data from the console for 49 seconds, and was giving a warning ;)

Eric
Logged

Offline duke666

  • Senior Contributor
  • ****
  • Posts: 187
    • Nightingale Weather
Re: Big problem with data update
« Reply #4 on: February 13, 2014, 09:00:52 AM »
FWIW, my Cumulus connection with VVP, last heard and last sent is always 1 second. However, my Weather Display connection through VVP, last sent is always 1 second but, last heard counts to 60 seconds and then resets. There is no problem with WD as the screen updates in 'real time' as per the Davis console display.

My advice would be to look at the software screen and console simultaneously to ascertain if there really is a problem.

Out of interest, what do you have 'status update speed' set to?
« Last Edit: February 13, 2014, 09:05:09 AM by duke666 »
Logged

Offline Beaudog

  • Forecaster
  • *****
  • Posts: 1217
Re: Big problem with data update
« Reply #5 on: February 13, 2014, 09:26:56 AM »
Mine does the same thing.
WUHU and Cumulus stay at 1 sec but the others run several minutes and then reset.  It is normal.
Logged

Offline Guillaume_67370

  • Contributor
  • ***
  • Posts: 123
    • METEO OFFENHEIM
Re: Big problem with data update
« Reply #6 on: February 13, 2014, 10:28:35 AM »
Quote from: duke666 on February 13, 2014, 09:00:52 AM
FWIW, my Cumulus connection with VVP, last heard and last sent is always 1 second. However, my Weather Display connection through VVP, last sent is always 1 second but, last heard counts to 60 seconds and then resets. There is no problem with WD as the screen updates in 'real time' as per the Davis console display.

My advice would be to look at the software screen and console simultaneously to ascertain if there really is a problem.

Out of interest, what do you have 'status update speed' set to?

it doesn't happend all the time but sometimes you can see the message of my capture "vp console no answer after several retries..."

My status update speed is 1 second.
Logged

Offline Guillaume_67370

  • Contributor
  • ***
  • Posts: 123
    • METEO OFFENHEIM
Re: Big problem with data update
« Reply #7 on: February 13, 2014, 10:34:36 AM »
Quote from: Beaudog on February 13, 2014, 09:26:56 AM
Mine does the same thing.
WUHU and Cumulus stay at 1 sec but the others run several minutes and then reset.  It is normal.

That means it is perhaps normal by me too?? Sometimes i propably don't receive all the datas that the reason why i receive the message "vp console no answer after several retries..."
Logged

Offline duke666

  • Senior Contributor
  • ****
  • Posts: 187
    • Nightingale Weather
Re: Big problem with data update
« Reply #8 on: February 13, 2014, 10:44:03 AM »
Mine has displayed that message since I installed VVP (several years) and I do not believe I have missed anything.

What makes you think this?
Quote
Sometimes i probably don't receive all the datas
Logged

Offline Guillaume_67370

  • Contributor
  • ***
  • Posts: 123
    • METEO OFFENHEIM
Re: Big problem with data update
« Reply #9 on: February 13, 2014, 11:53:47 AM »
Quote from: duke666 on February 13, 2014, 10:44:03 AM
Mine has displayed that message since I installed VVP (several years) and I do not believe I have missed anything.

What makes you think this?
Quote
Sometimes i probably don't receive all the datas

the messages
"vp console no answer after several retries..."
"vp far tto long since last loop=14.250"
Logged

Offline duke666

  • Senior Contributor
  • ****
  • Posts: 187
    • Nightingale Weather
Re: Big problem with data update
« Reply #10 on: February 13, 2014, 12:03:00 PM »
I get those too and I would guess I'm not the only one.....

When you see those messages, do what I suggested earlier to confirm the data actually is (as I suspect) updating perfectly.

Quote
My advice would be to look at the software screen and console simultaneously to ascertain if there really is a problem.

I suggest you try this when it's a bit windy ;)
Logged

Offline Beaudog

  • Forecaster
  • *****
  • Posts: 1217
Re: Big problem with data update
« Reply #11 on: February 13, 2014, 12:21:26 PM »
It says right on the VVP setup page that if you have fast looping enabled that it may affect reception.

I suspect do to packet conflicts.
Logged

Offline duke666

  • Senior Contributor
  • ****
  • Posts: 187
    • Nightingale Weather
Re: Big problem with data update
« Reply #12 on: February 13, 2014, 12:57:14 PM »
I do not have that ticked, yet, still experience the same messages but do not experience any data/comms problems.
Logged

Offline Guillaume_67370

  • Contributor
  • ***
  • Posts: 123
    • METEO OFFENHEIM
Re: Big problem with data update
« Reply #13 on: February 13, 2014, 02:06:44 PM »
Quote from: Beaudog on February 13, 2014, 12:21:26 PM
It says right on the VVP setup page that if you have fast looping enabled that it may affect reception.

I suspect do to packet conflicts.

Where can you find this "fast looping enable" on VVP?
Logged

Offline Guillaume_67370

  • Contributor
  • ***
  • Posts: 123
    • METEO OFFENHEIM
Re: Big problem with data update
« Reply #14 on: February 13, 2014, 02:13:43 PM »
Quote from: duke666 on February 13, 2014, 12:03:00 PM
I get those too and I would guess I'm not the only one.....

When you see those messages, do what I suggested earlier to confirm the data actually is (as I suspect) updating perfectly.

Quote
My advice would be to look at the software screen and console simultaneously to ascertain if there really is a problem.

I suggest you try this when it's a bit windy ;)


I made what you say in Cumulus, Wind datas change every 2 second approximatively sometimes a little bit more.
Logged

Offline duke666

  • Senior Contributor
  • ****
  • Posts: 187
    • Nightingale Weather
Re: Big problem with data update
« Reply #15 on: February 13, 2014, 02:18:01 PM »
Quote
Where can you find this "fast looping enable" on VVP?
Settings-communications, in the top section. If I recall, best left un-checked. If you decide to experiment, monitor your results.

Quote
I made what you say in Cumulus, Wind datas change every 2 second approximatively sometimes a little bit more.

I believe it takes approx 3 seconds to read the Davis DLL so that looks good.

Logged

Offline Guillaume_67370

  • Contributor
  • ***
  • Posts: 123
    • METEO OFFENHEIM
Re: Big problem with data update
« Reply #16 on: February 13, 2014, 02:23:12 PM »
Quote from: duke666 on February 13, 2014, 02:18:01 PM
Quote
Where can you find this "fast looping enable" on VVP?
Settings-communications, in the top section. If I recall, best left un-checked. If you decide to experiment, monitor your results.

Ok by me it's not tick  ;)

Quote
I made what you say in Cumulus, Wind datas change every 2 second approximatively sometimes a little bit more.

I believe it takes approx 3 seconds to read the Davis DLL so that looks good.

Ok that means it's good even if a receive these messages.
Logged

Offline Guillaume_67370

  • Contributor
  • ***
  • Posts: 123
    • METEO OFFENHEIM
Re: Big problem with data update
« Reply #17 on: February 13, 2014, 02:24:17 PM »
Ok by me fast looping isn't tick  ;)
Logged

Offline duke666

  • Senior Contributor
  • ****
  • Posts: 187
    • Nightingale Weather
Re: Big problem with data update
« Reply #18 on: February 13, 2014, 02:25:46 PM »
Quote
Ok that means it's good even if a receive these messages.

Agreed :-)
Logged

Offline piconut

  • Juggler Extraordinaire
  • Forecaster
  • *****
  • Posts: 365
    • South Austin Weather
Re: Big problem with data update
« Reply #19 on: February 27, 2014, 11:10:55 AM »
I've got fast looping checked (I'm not sure why, but I set it up a year ago and I think I just followed the directions).    Have you checked your activity log to see if it is an ongoing problem?


Here is what my Virtual VP shows:


« Last Edit: February 27, 2014, 11:13:14 AM by piconut »
Logged
  • Davis Vantage Pro 2 Plus
  • Virtual VP
  • Virtual Weather Station V15.00
  • Cumulus
  • Cumulus MX
  • Image Salsa
  • IP TimeLapse

Offline Guillaume_67370

  • Contributor
  • ***
  • Posts: 123
    • METEO OFFENHEIM
Re: Big problem with data update
« Reply #20 on: February 27, 2014, 12:28:20 PM »
Quote from: piconut on February 27, 2014, 11:10:55 AM
I've got fast looping checked (I'm not sure why, but I set it up a year ago and I think I just followed the directions).    Have you checked your activity log to see if it is an ongoing problem?


Here is what my Virtual VP shows:




That is the activity log it seems to be ok?

17:35:10:787 Bug          - TVpCom.BeatNotify: Wake Up Console command timed out, but there is something in the InBuff
17:35:10:788 Warning      - VpConsole: No response after several retries for Wake Up Console
17:35:12:976 Warning      - VpConsole: Far too long since last loop = 8,594, last command= Get Console Diagnostics
17:40:10:579 Warning      - VpConsole: No response after several retries for Get Live Sensor Data
17:40:13:268 Warning      - VpConsole: Far too long since last loop = 8,203, last command= Get Highs/Lows
17:42:06:181 Warning      - VpConsole: Far too long since last loop = 5,609, last command= Get Barometer Data
17:45:10:154 Warning      - VpConsole: No response after several retries for Get Live Sensor Data
17:45:12:240 Warning      - VpConsole: Far too long since last loop = 8,078, last command= Get Console Diagnostics
17:50:10:578 Warning      - VpConsole: No response after several retries for Get Live Sensor Data
17:50:12:514 Warning      - VpConsole: Far too long since last loop = 8,016, last command= Get Highs/Lows
17:55:09:205 Warning      - VpConsole: No response after several retries for Wake Up Console
17:55:12:989 Warning      - VpConsole: Far too long since last loop = 7,703, last command= Get Live Sensor Data
17:56:06:151 Warning      - VpConsole: Far too long since last loop = 5,188, last command= Get Barometer Data
18:05:12:028 Warning      - VpConsole: No response after several retries for Wake Up Console
18:05:12:111 Warning      - VpConsole: Far too long since last loop = 8,125, last command= Get Highs/Lows
18:09:11:967 Warning      - VpConsole: No response after several retries for Wake Up Console
18:09:17:725 Warning      - VpConsole: Far too long since last loop = 14,610, last command= Get Live Sensor Data
18:10:06:550 Warning      - VpConsole: Far too long since last loop = 6,453, last command= Get Live Sensor Data
18:10:18:110 Warning      - VpConsole: No response after several retries for Get Live Sensor Data
18:10:18:222 Warning      - VpConsole: Far too long since last loop = 8,000, last command= Get Console Diagnostics
18:13:13:947 Warning      - VpConsole: No response after several retries for Wake Up Console
18:13:15:806 Warning      - VpConsole: Far too long since last loop = 13,047, last command= Get Live Sensor Data
18:14:06:551 Warning      - VpConsole: Far too long since last loop = 5,641, last command= Get Barometer Data
18:15:12:644 Warning      - VpConsole: No response after several retries for Wake Up Console
18:15:14:109 Warning      - VpConsole: Far too long since last loop = 8,828, last command= Get Console Diagnostics
18:17:11:329 Warning      - VpConsole: No response after several retries for Wake Up Console
18:17:17:680 Warning      - VpConsole: Far too long since last loop = 15,078, last command= Get Live Sensor Data
18:18:07:327 Warning      - VpConsole: Far too long since last loop = 5,454, last command= Get Live Sensor Data
18:19:05:296 Warning      - VpConsole: No response after several retries for Wake Up Console
18:19:08:044 Warning      - VpConsole: Far too long since last loop = 7,515, last command= Get Barometer Data
18:19:48:595 Warning      - VpConsole: Far too long since last loop = 5,125, last command= Get Live Sensor Data
18:20:10:970 Warning      - VpConsole: Far too long since last loop = 10,641, last command= Get Live Sensor Data
18:20:18:329 Warning      - VpConsole: No response after several retries for Wake Up Console
18:20:20:285 Warning      - VpConsole: Far too long since last loop = 8,265, last command= Get Live Sensor Data
18:21:10:030 Warning      - VpConsole: No response after several retries for Wake Up Console
18:21:10:409 Warning      - VpConsole: Far too long since last loop = 8,578, last command= Get Live Sensor Data
18:22:08:501 Warning      - VpConsole: Far too long since last loop = 5,875, last command= Get Live Sensor Data
18:23:10:582 Warning      - VpConsole: No response after several retries for Wake Up Console
18:23:15:967 Warning      - VpConsole: Far too long since last loop = 13,015, last command= Get Live Sensor Data
18:24:11:410 Warning      - VpConsole: No response after several retries for Wake Up Console
18:24:25:264 Warning      - VpConsole: No response after several retries for Get Live Sensor Data
18:24:27:872 Warning      - VpConsole: Far too long since last loop = 26,515, last command= Get Barometer Data
18:24:42:571 Warning      - VpConsole: Far too long since last loop = 5,516, last command= Get Live Sensor Data
18:25:16:966 Warning      - VpConsole: No response after several retries for Get Live Sensor Data
18:25:17:560 Warning      - VpConsole: Far too long since last loop = 17,672, last command= Get Live Sensor Data
18:25:30:175 Bug          - TVpCom.BeatNotify: Get Live Sensor Data command timed out, but there is something in the InBuff
18:25:30:187 Warning      - VpConsole: No response after several retries for Get Live Sensor Data
18:25:30:590 Warning      - VpConsole: Far too long since last loop = 8,844, last command= Get Live Sensor Data
18:25:40:391 Warning      - VpConsole: No response after several retries for Get Live Sensor Data
18:25:40:855 Warning      - VpConsole: Far too long since last loop = 10,266, last command= Get Console Diagnostics
18:25:55:959 Warning      - VpConsole: Far too long since last loop = 6,500, last command= Get Live Sensor Data



8:23:24:305 Verbose      - VpConsole: Sending Wake Up Console
18:23:24:413 Verbose      - VpConsole: Received Wake Up Console response
18:23:24:419 Verbose      - VpConsole: Sending Get Live Sensor Data
18:23:24:554 Verbose      - VpConsole: Received Get Live Sensor Data response
18:23:24:564 Info         - VpConsole: Received Loop packet 4   (2,047 seconds since last packet)
18:23:24:769 Info         - Cumulus: Received Get Live Sensor Data
18:23:24:778 Info         - Cumulus: Sent response for Get Live Sensor Data
18:23:24:784 Verbose      - Serving Get Live Sensor Data from cache
18:23:24:789 Info         - Cumulus: Sending LOOP 1 of 1
18:23:25:173 Verbose      - WsWin: Received Wake Up Console
18:23:25:182 Verbose      - WsWin: Sent response for Wake Up Console
18:23:25:382 Verbose      - WsWin: Received Wake Up Console
18:23:25:388 Verbose      - WsWin: Sent response for Wake Up Console
18:23:25:401 Info         - WsWin: Received Get Live Sensor Data
18:23:25:407 Info         - WsWin: Sent response for Get Live Sensor Data
18:23:25:415 Verbose      - Serving Get Live Sensor Data from cache
18:23:25:515 Info         - WsWin: Sending LOOP 1 of 1
18:23:25:529 Verbose      - Cumulus: Received Wake Up Console
18:23:25:535 Verbose      - Cumulus: Sent response for Wake Up Console
18:23:26:396 Info         - Cumulus: Received Get Live Sensor Data
18:23:26:402 Info         - Cumulus: Sent response for Get Live Sensor Data
18:23:26:411 Verbose      - Serving Get Live Sensor Data from cache
18:23:26:416 Info         - Cumulus: Sending LOOP 1 of 1
18:23:26:428 Verbose      - VpConsole: Inserting Loop at start of queue
18:23:26:434 Verbose      - VpConsole: Sending Wake Up Console
18:23:26:799 Verbose      - VpConsole: Retry #1 for Wake Up Console
18:23:27:069 Verbose      - Cumulus: Received Wake Up Console
18:23:27:078 Verbose      - Cumulus: Sent response for Wake Up Console
18:23:27:118 Verbose      - VpConsole: Retry #2 for Wake Up Console
18:23:27:137 Verbose      - VpConsole: Received Wake Up Console response
18:23:27:145 Verbose      - VpConsole: Sending Get Live Sensor Data
18:23:27:235 Verbose      - VpConsole: Received Get Live Sensor Data response
18:23:27:389 Info         - VpConsole: Received Loop packet 5   (2,812 seconds since last packet)
18:23:27:398 Info         - VpConsole: Too long since last loop = 2,812, last command= Get Live Sensor Data
18:23:27:681 Verbose      - WsWin: Received Wake Up Console
18:23:27:687 Verbose      - WsWin: Sent response for Wake Up Console
18:23:27:725 Info         - WsWin: Received Get Console Diagnostics
18:23:27:731 Verbose      - VpConsole: Queueing Wake Up Console
18:23:27:737 Verbose      - VpConsole: Queueing Get Console Diagnostics
18:23:27:753 Verbose      - VpConsole: Sending Wake Up Console
18:23:27:838 Info         - Cumulus: Received Get Live Sensor Data
18:23:27:879 Info         - Cumulus: Sent response for Get Live Sensor Data
18:23:27:885 Verbose      - Serving Get Live Sensor Data from cache
18:23:27:922 Info         - Cumulus: Sending LOOP 1 of 1
18:23:27:982 Verbose      - VpConsole: Received Wake Up Console response
18:23:27:988 Info         - VpConsole: Sending Get Console Diagnostics
18:23:28:046 Info         - VpConsole: Received Get Console Diagnostics response
18:23:28:052 Info         - WsWin: Sent response for Get Console Diagnostics
18:23:28:098 Verbose      - WsWin: Received Wake Up Console
18:23:28:104 Verbose      - WsWin: Sent response for Wake Up Console
18:23:28:152 Info         - WsWin: Received Get Live Sensor Data
18:23:28:162 Info         - WsWin: Sent response for Get Live Sensor Data
18:23:28:167 Verbose      - Serving Get Live Sensor Data from cache
18:23:28:176 Info         - WsWin: Sending LOOP 1 of 1
18:23:28:293 Verbose      - Cumulus: Received Wake Up Console
18:23:28:300 Verbose      - Cumulus: Sent response for Wake Up Console
18:23:28:470 Verbose      - VpConsole: Inserting Loop at start of queue
18:23:28:478 Verbose      - VpConsole: WakeUp send not needed (console already awake)
18:23:28:501 Verbose      - VpConsole: Sending Get Live Sensor Data
18:23:28:645 Verbose      - VpConsole: Received Get Live Sensor Data response
18:23:28:654 Info         - VpConsole: Received Loop packet 1   (1,266 seconds since last packet)
18:23:29:011 Info         - Cumulus: Received Get Live Sensor Data
18:23:29:018 Info         - Cumulus: Sent response for Get Live Sensor Data
18:23:29:026 Verbose      - Serving Get Live Sensor Data from cache
18:23:29:032 Info         - Cumulus: Sending LOOP 1 of 1
18:23:29:421 Verbose      - Cumulus: Received Wake Up Console
18:23:29:428 Verbose      - Cumulus: Sent response for Wake Up Console
18:23:30:127 Info         - Cumulus: Received Get Live Sensor Data
18:23:30:133 Info         - Cumulus: Sent response for Get Live Sensor Data
18:23:30:139 Verbose      - Serving Get Live Sensor Data from cache
18:23:30:196 Info         - Cumulus: Sending LOOP 1 of 1
18:23:30:228 Verbose      - WsWin: Received Wake Up Console
18:23:30:235 Verbose      - WsWin: Sent response for Wake Up Console
18:23:30:309 Info         - WsWin: Received Get Live Sensor Data
18:23:30:317 Info         - WsWin: Sent response for Get Live Sensor Data
18:23:30:326 Verbose      - Serving Get Live Sensor Data from cache
18:23:30:331 Info         - WsWin: Sending LOOP 1 of 1
18:23:30:570 Verbose      - VpConsole: Inserting Loop at start of queue
18:23:30:578 Verbose      - VpConsole: Sending Wake Up Console
18:23:30:668 Verbose      - VpConsole: Received Wake Up Console response
18:23:30:676 Verbose      - VpConsole: Sending Get Live Sensor Data
18:23:30:716 Verbose      - Cumulus: Received Wake Up Console
18:23:30:722 Verbose      - Cumulus: Sent response for Wake Up Console
18:23:30:831 Verbose      - VpConsole: Received Get Live Sensor Data response
18:23:30:837 Info         - VpConsole: Received Loop packet 2   (2,187 seconds since last packet)
18:23:31:379 Info         - Cumulus: Received Get Live Sensor Data
18:23:31:385 Info         - Cumulus: Sent response for Get Live Sensor Data
18:23:31:394 Verbose      - Serving Get Live Sensor Data from cache
18:23:31:400 Info         - Cumulus: Sending LOOP 1 of 1
18:23:31:758 Verbose      - Cumulus: Received Wake Up Console
18:23:31:764 Verbose      - Cumulus: Sent response for Wake Up Console
18:23:32:431 Info         - Cumulus: Received Get Live Sensor Data
18:23:32:437 Info         - Cumulus: Sent response for Get Live Sensor Data
18:23:32:446 Verbose      - Serving Get Live Sensor Data from cache
18:23:32:452 Info         - Cumulus: Sending LOOP 1 of 1
18:23:32:627 Verbose      - VpConsole: Inserting Loop at start of queue
18:23:32:633 Verbose      - VpConsole: Sending Wake Up Console
18:23:32:697 Verbose      - WsWin: Received Wake Up Console
18:23:32:703 Verbose      - WsWin: Sent response for Wake Up Console
18:23:32:711 Info         - WsWin: Received Get Live Sensor Data
18:23:32:717 Info         - WsWin: Sent response for Get Live Sensor Data
18:23:32:726 Verbose      - Serving Get Live Sensor Data from cache
18:23:32:732 Info         - WsWin: Sending LOOP 1 of 1
18:23:32:841 Verbose      - Cumulus: Received Wake Up Console
18:23:32:847 Verbose      - Cumulus: Sent response for Wake Up Console
18:23:32:853 Verbose      - VpConsole: Retry #1 for Wake Up Console
18:23:32:908 Verbose      - VpConsole: Received Wake Up Console response
18:23:32:913 Verbose      - VpConsole: Sending Get Live Sensor Data
18:23:33:203 Verbose      - VpConsole: Received Get Live Sensor Data response
18:23:33:211 Info         - VpConsole: Received Loop packet 3   (2,375 seconds since last packet)
18:23:33:559 Info         - Cumulus: Received Get Live Sensor Data
18:23:33:565 Info         - Cumulus: Sent response for Get Live Sensor Data
18:23:33:571 Verbose      - Serving Get Live Sensor Data from cache
18:23:33:580 Info         - Cumulus: Sending LOOP 1 of 1
18:23:33:950 Verbose      - Cumulus: Received Wake Up Console
18:23:33:957 Verbose      - Cumulus: Sent response for Wake Up Console
18:23:34:566 Info         - Cumulus: Received Get Live Sensor Data
18:23:34:574 Info         - Cumulus: Sent response for Get Live Sensor Data
18:23:34:580 Verbose      - Serving Get Live Sensor Data from cache
18:23:34:586 Info         - Cumulus: Sending LOOP 1 of 1
18:23:34:709 Verbose      - VpConsole: Inserting Loop at start of queue
18:23:34:715 Verbose      - VpConsole: Sending Wake Up Console
18:23:34:819 Verbose      - VpConsole: Received Wake Up Console response
18:23:34:829 Verbose      - VpConsole: Sending Get Live Sensor Data
18:23:34:966 Verbose      - Cumulus: Received Wake Up Console
18:23:34:974 Verbose      - Cumulus: Sent response for Wake Up Console
18:23:35:018 Verbose      - VpConsole: Received Get Live Sensor Data response
18:23:35:028 Info         - VpConsole: Received Loop packet 4   (1,813 seconds since last packet)
18:23:35:156 Verbose      - WsWin: Received Wake Up Console
18:23:35:162 Verbose      - WsWin: Sent response for Wake Up Console
18:23:35:209 Info         - WsWin: Received Get Live Sensor Data
18:23:35:215 Info         - WsWin: Sent response for Get Live Sensor Data
18:23:35:224 Verbose      - Serving Get Live Sensor Data from cache
18:23:35:230 Info         - WsWin: Sending LOOP 1 of 1
18:23:35:580 Info         - Cumulus: Received Get Live Sensor Data
18:23:35:586 Info         - Cumulus: Sent response for Get Live Sensor Data
18:23:35:596 Verbose      - Serving Get Live Sensor Data from cache
18:23:35:602 Info         - Cumulus: Sending LOOP 1 of 1
18:23:35:970 Verbose      - VpConsole: Queueing Wake Up Console
18:23:35:979 Verbose      - VpConsole: Queueing Get Archive Buffer
18:23:36:020 Verbose      - Cumulus: Received Wake Up Console
18:23:36:029 Verbose      - Cumulus: Sent response for Wake Up Console
18:23:36:036 Verbose      - VpConsole: Sending Wake Up Console
18:23:36:139 Verbose      - VpConsole: Received Wake Up Console response
18:23:36:145 Info         - VpConsole: Sending Get Archive Buffer
18:23:36:640 Verbose      - Serving Get Live Sensor Data from cache
18:23:36:736 Verbose      - VpConsole: Inserting Loop at start of queue
18:23:36:743 Verbose      - VpConsole: WakeUp send not needed (console already awake)
18:23:36:748 Verbose      - VpConsole: Sending Get Live Sensor Data
18:23:36:928 Verbose      - VpConsole: Received Get Live Sensor Data response
Logged

Offline piconut

  • Juggler Extraordinaire
  • Forecaster
  • *****
  • Posts: 365
    • South Austin Weather
Re: Big problem with data update
« Reply #21 on: February 27, 2014, 01:12:39 PM »
Yes, that looks similar to mine.  So is Cumulus updating correctly?
Logged
  • Davis Vantage Pro 2 Plus
  • Virtual VP
  • Virtual Weather Station V15.00
  • Cumulus
  • Cumulus MX
  • Image Salsa
  • IP TimeLapse

Offline Guillaume_67370

  • Contributor
  • ***
  • Posts: 123
    • METEO OFFENHEIM
Re: Big problem with data update
« Reply #22 on: February 27, 2014, 02:53:01 PM »
Quote from: piconut on February 27, 2014, 01:12:39 PM
Yes, that looks similar to mine.  So is Cumulus updating correctly?

I think because i always have a look when i go on my computer and last heard is <1 second but for WsWin it is <1 second then <2 seconds
Perhaps it was some bugs...?
Logged

Offline piconut

  • Juggler Extraordinaire
  • Forecaster
  • *****
  • Posts: 365
    • South Austin Weather
Re: Big problem with data update
« Reply #23 on: February 27, 2014, 05:29:36 PM »
Quote from: Guillaume_67370 on February 27, 2014, 02:53:01 PM
I think because i always have a look when i go on my computer and last heard is <1 second but for WsWin it is <1 second then <2 seconds
Perhaps it was some bugs...?


...or gremlins...
Logged
  • Davis Vantage Pro 2 Plus
  • Virtual VP
  • Virtual Weather Station V15.00
  • Cumulus
  • Cumulus MX
  • Image Salsa
  • IP TimeLapse
Pages: [1]   Go Up
« previous next »