Cumulus Support

Currently, I'm running on a Windows 8.1 machine. Been running VVP along with VWS, VPLive, Weatherlink without any major issues.

Tried to start testing MX since VWS is having issues with WUnderground. I'm running it as Admin. Command window shows downloading data and "Normal running". But in the webpage, all I get for data is all zeros.

To test out my connection, I was able to install the older 1.9.4 without any major issues. It is getting data. I started on the Saratoga templates. Got "most" of that up and running. But I'd prefer to use MX since that's the way things are heading.

Anyone ever see this issue with "all zeros"? I even shut down Weatherlink since I don't need that running. Started with a whole new blank MX download and install. Still getting the same thing. I have VWS on port 5511, MX now on 5512, VPLive on 5513. And Cumulus1 on 5514.

One other "odd" thing I notice in VVP. It shows last connect times. Cumulus MX never shows up as actually connected.

Here is the latest of my diag files. I see a bunch of LOOP errors at the end. I'm guessing this is related.

VVP appears not to be responding a lot of the time. I notice that you haven't disabled LOOP2 as in the instructions - VVP doesn't support it.

Have you set VP2SleepInterval in Cumulus 1?

steve wrote:VVP appears not to be responding a lot of the time. I notice that you haven't disabled LOOP2 as in the instructions - VVP doesn't support it.

Have you set VP2SleepInterval in Cumulus 1?

I don't see where the LOOP2 settings is in MX. Where is that at?

No, I haven't adjusted any Station settings in Cumulus 1 either. Just set the IP and port and it worked.

92merc wrote:I don't see where the LOOP2 settings is in MX. Where is that at?

You set it by editing Cumulus.ini, as described in the instructions.

No, I haven't adjusted any Station settings in Cumulus 1 either. Just set the IP and port and it worked.

You need to set VP2SleepInterval to 1100 in Cumulus.ini, as described in the instructions in the readme.txt.

OK, I googled it and added DavisIPResponseTime=2000 and UseDavisLoop2=0 to the CumulusMX ini file.

I also added VP2SleepInterval = 1100 to the Cumulus1 ini file. Restarted Cumulus1. No change noticed. But that's probably a good thing. You probably helped me avoid an issue later.

Still no change in CumulusMX though. Still all zero's. VVP still doesn't show any linking on that port.

I gave my PC a reboot just to see if that helps. Now MX just comes to the "Ctrl-C" prompt. It doesn't get to the downloading data or Normal running spots.

What I think has improved though is VVP is showing communications. 1 second or less appears like my other software.

Here is the last diags.

It was still downloading archive data, VVP sent the entire contents of the logger, so you probably don't have the Cumulus logger interval set to the same interval as your station - http://wiki.sandaysoft.com/a/FAQ#Cumulu ... t_start_up

I verified I had both the console and MX settings to log at 10 minutes.

I had VPLive doing the time sync. I turned that off and enabled it in MX.

Still hanging at the Cntrl-C window. No Normal Running again.

It is still downloading logger entries. It will take quite a while to download the entire contents. Your station logger is apparently set to 15 minute intervals:

2017-02-22 14:43:18.056 Loaded archive record for Page=17 Record=0 Timestamp=2/12/2017 10:00:00 PM
2017-02-22 14:43:18.056 Ignoring old archive data
2017-02-22 14:43:18.056 85 archive entries processed
2017-02-22 14:43:18.056 Loaded archive record for Page=17 Record=1 Timestamp=2/12/2017 10:15:00 PM
2017-02-22 14:43:18.056 Ignoring old archive data
2017-02-22 14:43:18.056 86 archive entries processed
2017-02-22 14:43:18.056 Loaded archive record for Page=17 Record=2 Timestamp=2/12/2017 10:30:00 PM
2017-02-22 14:43:18.056 Ignoring old archive data
2017-02-22 14:43:18.056 87 archive entries processed
2017-02-22 14:43:18.056 Loaded archive record for Page=17 Record=3 Timestamp=2/12/2017 10:45:00 PM
2017-02-22 14:43:18.056 Ignoring old archive data
2017-02-22 14:43:18.056 88 archive entries processed
2017-02-22 14:43:18.056 Loaded archive record for Page=17 Record=4 Timestamp=2/12/2017 11:00:00 PM

If you start MX at either :00 :15 :30 or :45 past the hour, that might persuade VVP not to send the entire contents of the logger. But you will need to have the logger intervals set to the same value to avoid the same thing happening again.

It was at 15, I changed it to 10 to match what MX had already. I totally shut down VPLive since its reason in life was to do the clock. I reconfigured Weatherlink to use that port so I can run VWS, MX, WL, and Cumulus1 at the same time.

For testing, I shut all of my programs down and reconfigured MX to use the COM1 port. If fired up instantly and my console showed the correct data. NOT all zero's. So it has to be VVP interfering somehow. I switched it back to IP again. Still hanging again at Ctrl-C again.

Ok maybe I don't have it right. I looked at the logs again. Still showing 15 minutes.

That 15 minutes in the MX log files, is that the setting the logger is using, or the setting MX is using?

This is the setting Cumulus is using:

2017-02-22 14:42:19.831 Logging interval = 10

Those archive entries that are being downloaded are at 15 minute intervals, so that is apparently the interval the logger is using (but I have no idea how VVP affects this, perhaps it has those entries already downloaded from the console).

The ini file in MX had DataLogInterval=3. I changed that to 15.

Console fires up now. Showing Normal Running. But data still stuck at zero.

92merc wrote:The ini file in MX had DataLogInterval=3. I changed that to 15.

That's not how that setting works, 15 is not a valid value. The way to change the interval is via the user interface.

Console fires up now. Showing Normal Running. But data still stuck at zero.

Have a look at the diags file and see what that shows.