Cumulus Support

It appears that Cumulus was/is not the only software experiencing problems with the firmware upgrade! - WXforum

It is equally as bad news for those of us that run multiple weather software utilizing the only software capable of allowing this - VVP

But if I understand that correctly, it's 3.12 which the other software is having problems with, whereas with Cumulus, 3.0 caused the problem, and 3.12 appears to have fixed it.

steve wrote:But if I understand that correctly, it's 3.12 which the other software is having problems with, whereas with Cumulus, 3.0 caused the problem, and 3.12 appears to have fixed it.

I wonder what firmware version they were running before upgrading to 3.12? If they were at 1.x then they may be experiencing the same issues that 3.0 caused for Cumulus. If they were actually running 3.0, then Davis have caused a world of problems by not doing sufficient beta testing or communicating with users.

Also, the information on the Davis site for 3.12 only states:
"Fixed a bug in 3.00 that did not allow the ET alarm to be cleared."
NOTHING about the communications issue.

This reply is from someone running VVP, WeatherLink and Cumulus and reports no problems whatsoever.
http://www.wxforum.net/index.php?topic= ... #msg177655

The only issue I've seen is with VVP and VWS. I don't have VWS. If anyone here does then looks like they should tread carefully.

I too had no problem with v3.12 running Cumulus, WeatherLink and VPLive through VVP.

My issue was WUHU and VWS would not communicate correctly using a VVP virtual port, but would work just fine using a standalone COM port connection to the console.

I rolled back the firmware to 1.90 and they both resumed functioning with VVP ports.

The issue seems to be something in the two programs themselves at fault rather than in the firmware itself. Three of five worked perfectly, two did not.

I am not using VirtualVP, but here are my results after searching for a solution to the slow updates I was seeing...

Cumulus - v1.9.4 b1066
Davis f/w - v3.12
Serial data logger

I was seeing (from the status bar) that Cumulus was reading the station mostly every 5 seconds or so, with some longer periods up to 10 seconds.

I discovered the VPSleepInterval setting, and had set that to zero, the result was the same, lots of missed wind readings.

I then discovered this thread and set VPSleepInterval=1, now it is updating between 1 and 3 seconds - I guess an average of 2.5? The CPU usage is low, and the disconnects irrelevant to me as I am not using VVP.

I'm guessing that setting VPSleepInterval=0 causes Cumulus to use it's internal delay timer?

mcrossley wrote:I'm guessing that setting VPSleepInterval=0 causes Cumulus to use it's internal delay timer?

Yes, in the more recent versions which are aware of firmware 3.xx. If it's zero, it implements a sleep interval of 1500ms, as otherwise the reads were coming back immediately (as they do with VVP) and causing excessive reads and high CPU.

You've set it to to 1ms, i.e. negligible. From what you've seen, the reads aren't coming back immediately, so no sleep interval is required. I wonder whether this is a change between version 3.00 and 3.12?

Steve,

I have VPSleepInterval=1100. Is that what you would recommend?

Not sure if it's linked but uploads to my website are taking around 1m 30s which seems excessive. They used to take less than a minute. Could the new firmware update be responsible? I have a cabled connection via a homeplug to my router.

RayProudfoot wrote:I have VPSleepInterval=1100. Is that what you would recommend?

You're using VVP, so the firmware versions aren't relevant in this case. 1100 ms is the value that people using VVP found worked OK some time ago. Anything around the 1000 to 1500 ms mark should work OK.

Not sure if it's linked but uploads to my website are taking around 1m 30s which seems excessive. They used to take less than a minute. Could the new firmware update be responsible? I have a cabled connection via a homeplug to my router.

Not related. FTP is inherently inefficient and the Cumulus FTP runs in a background thread. I don't know why it's taking longer than previously, unless it's because there are more files now than there used to be.

Thanks Steve. I'll leave things alone.

steve wrote:I wonder whether this is a change between version 3.00 and 3.12?

I decided it was time I installed firmware 3.12. And it does appear that it's reverted to the pre-3.00 behaviour in not sending the first LOOP response immediately, so no VP2SleepInterval needs setting in Cumulus. So I've changed the code just to look for 3.00.

steve wrote:I decided it was time I installed firmware 3.12. And it does appear that it's reverted to the pre-3.00 behaviour in not sending the first LOOP response immediately, so no VP2SleepInterval needs setting in Cumulus.

Is that only for non-VVP users?

RayProudfoot wrote:Is that only for non-VVP users?

Yes - VVP always returns the first LOOP packet immediately, so VVP users need to keep VP2SleepInterval=1100 in cumulus.ini regardless of what firmware their console has.

steve wrote:

RayProudfoot wrote:Is that only for non-VVP users?

Yes - VVP always returns the first LOOP packet immediately, so VVP users need to keep VP2SleepInterval=1100 in cumulus.ini regardless of what firmware their console has.

Thanks for the confirmation Steve.

Hello everybody,

I noticed the problem. Please see below :
05/04/2014 10:09:00 : Data input appears to have stopped - check your station and connections
05/04/2014 10:42:00 : Data input appears to have stopped - check your station and connections
06/04/2014 16:51:00 : Data input appears to have stopped - check your station and connections
06/04/2014 19:25:00 : Data input appears to have stopped - check your station and connections
07/04/2014 18:08:00 : Data input appears to have stopped - check your station and connections
07/04/2014 18:44:00 : Data input appears to have stopped - check your station and connections
07/04/2014 19:00:01 : Data input appears to have stopped - check your station and connections
07/04/2014 19:02:00 : Data input appears to have stopped - check your station and connections
07/04/2014 19:03:00 : Data input appears to have stopped - check your station and connections
07/04/2014 22:51:00 : Data input appears to have stopped - check your station and connections
07/04/2014 22:53:00 : Data input appears to have stopped - check your station and connections
08/04/2014 12:02:00 : Data input appears to have stopped - check your station and connections
08/04/2014 17:11:00 : Data input appears to have stopped - check your station and connections

I'm using Cumulus and Wswin with Virtual Vp.
What will i have to do?

Thanks a lot for your help