Cumulus Support

Hi,

Lately, and I haven't been yet able to determine when or why, MX is taking a very long time to start. I just stopped it and restarted and it took over ten minutes. It is also reading a massive amount of archive material and reading through the list and then starting again before MX gets to "Normal running"

"Current culture: English (United States)
Serial: F70778FCFC72385C62406EBB1DEE7E3B
Cumulus MX v.3.0.0 build 3042
Today.ini = data\today.ini
Last update=2017-03-08T07:10:00
Connected to station
7:24:04 AM Downloading Archive Data
Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)
Starting web socket server on port 8002
3/8/2017 7:24:04 AM
Type Ctrl-C to terminate
7:29:51 AM Downloading Archive Data
7:35:38 AM Normal running"

The associated diag is attached.

Thanks

Forgot to mention that this is a Davis Vantage Vue station.

Have you looked at the FAQ and confirmed that this one doesn't apply in your case? http://wiki.sandaysoft.com/a/FAQ#Cumulu ... t_start_up

Hi Steve,

Thanks for the reply.

I already have these settings:

- Synchronize station clock
Keep station clock in line with computer clock (Davis/Instrument only)

- I also have the station and MX log intervals set to the same 10 minutes value.

I did notice this in the Wiki though:

"Cumulus takes a long time to download the data from my Davis station at start up
....
Note that this situation [long time] can also occur if you close Cumulus and then start it up again very soon afterwards, for similar reasons. There is nothing that Cumulus can do about this, it is an issue with the logger (or Virtual VP, which behaves in the same way)."

I do restart MX every day at 1:00AM and this morning when I did the test, I stopped it, ran WeatherLink and then restarted MX. Interesting though was that Weatherlink was also downloading the entire archive which it normally does not do either.

Thanks

I also just manually verified that my computer and Davis console are set at exactly the same time.

It could be that your logger has stopped logging. All of the entries MX downloaded were for Timestamp=1/1/1900 12:00:00 AM (which is probably equivalent to all 'empty' fields). It may be worthwhile running Weatherlink and resetting the archive interval.

Okay I stopped MX, changed Weatherlink to 30 minutes, saved it, changed back to 10 minute, saved it and restarted MX. I only have five archive records now but the time is still wrong.

I also restarted my data logger with no change. At a loss regarding this time stamp error of "Timestamp=1/1/1900 12:00:00 AM"

Glenn

All I can suggest is that your logger is faulty. You could try the following test: Stop MX for half an hour and then start it again. See if any valid logger entries are received (perhaps along with the invalid ones).

Is Weatherlink downloading any entries with valid timestamps?

Okay, I'll stop MX and check Weatherlink out in the meantime.

Thanks Steve

Okay, Weatherlink had issues too. I unplugged and removed the batteries from my Vantage Vue console, waited about 30 seconds and hooked up power and batteries again. Looks like its fine now although I did lose data from Feb 18th until today. MX started right up too.

2017-03-08 11:40:59.475 Console clock: 3/8/2017 11:40:58 AM
2017-03-08 11:40:59.475 Start reading archive data
2017-03-08 11:40:59.476 Reading archive data
2017-03-08 11:40:59.476 Loading last N hour data from data logs: 3/8/2017 11:30:00 AM
2017-03-08 11:40:59.520 Loaded 4 entries to last hour data list
2017-03-08 11:40:59.558 Loaded 15 entries to last 3 hour data list
2017-03-08 11:40:59.598 Loaded 66 entries to graph data list
2017-03-08 11:40:59.708 Loaded 983 entries to recent data list
2017-03-08 11:40:59.730 Loaded 31 entries to daily data list
2017-03-08 11:40:59.745 Get Archive Data
2017-03-08 11:40:59.746 Rollover hour = 0
2017-03-08 11:40:59.746 Last Archive Date: 3/8/2017 11:30:00 AM
2017-03-08 11:40:59.746 Date: 8808
2017-03-08 11:40:59.746 Time: 1130
2017-03-08 11:40:59.775 629 web tags initialised
2017-03-08 11:40:59.790 HTML root path = C:\CumulusMX\interface
2017-03-08 11:40:59.839 Starting web socket server on port 8002
2017-03-08 11:41:01.748 Received response to DMPAFT, sending date and time
2017-03-08 11:41:01.748 68-22-6A-04-90-D2
2017-03-08 11:41:02.749 Received 0x06
2017-03-08 11:41:02.749 ACK received
2017-03-08 11:41:02.749 Response:00-00-00-00-00-00
2017-03-08 11:41:02.749 Reading data: 0 pages , offset = 0
2017-03-08 11:41:02.749 Get Archive Data
2017-03-08 11:41:02.750 Rollover hour = 0
2017-03-08 11:41:02.750 Last Archive Date: 3/8/2017 11:30:00 AM

Thanks for your help Steve!

Make sure you set the logging interval to 10 minutes again, if you haven't already. And after doing that, try the test of leaving MX for half an hour again, to make sure it really is logging now.

Okay Steve,

Still looks good:

"017-03-08 14:05:07.618 Loaded archive record for Page=0 Record=4 Timestamp=3/8/2017 1:50:00 PM
2017-03-08 14:05:07.618 Processing archive record for 3/8/2017 1:50:00 PM
2017-03-08 14:05:07.618 Page=0 Record=4 Timestamp=3/8/2017 1:50:00 PM
2017-03-08 14:05:07.618 Writing log entry for 3/8/2017 1:50:00 PM
2017-03-08 14:05:07.622 Written log entry for 3/8/2017 1:50:00 PM
2017-03-08 14:05:07.623 Writing today.ini, LastUpdateTime = 3/8/2017 1:50:00 PM raindaystart = 4.1 rain counter = 4.34
2017-03-08 14:05:07.627 Log file entry written
2017-03-08 14:05:07.628 5 archive entries processed
2017-03-08 14:05:07.628 Reading archive page 1
2017-03-08 14:05:07.628 Waiting for response
2017-03-08 14:05:08.629 Loaded archive record for Page=1 Record=0 Timestamp=3/8/2017 2:00:00 PM
2017-03-08 14:05:08.629 Processing archive record for 3/8/2017 2:00:00 PM
2017-03-08 14:05:08.634 Page=1 Record=0 Timestamp=3/8/2017 2:00:00 PM
2017-03-08 14:05:08.634 Writing log entry for 3/8/2017 2:00:00 PM
2017-03-08 14:05:08.638 Written log entry for 3/8/2017 2:00:00 PM
2017-03-08 14:05:08.639 Writing today.ini, LastUpdateTime = 3/8/2017 2:00:00 PM raindaystart = 4.1 rain counter = 4.34"

Still looking okay to me. Latest diag after about one hour shutdown is attached.

Yes, looks fine now.

Thanks Steve