Cumulus Support

I believe I've read all the download and Setup requirements for Mx.
That said I am unable to get it started. See the attached jpeg.
I created a separate Cumulus-Mx folder and also copied all from the regular Cumulus folder. Then I extracted the contents of the Mx Zip into the Cumulus-Mx folder. I did note that the CumulusMX.exe listing did not have a pictured Icon fwiw.

CumulusMX.exe is set to run as Admin and later I also checked the box to run compat with Win7 just to see if that helped as I am using Win7-pro 64 bit .

This is a home computer and I am admin on everything anyway.

Obviously my regular Cumulus is not running while I am trying Mx.

help please

One (or more) of your settings in Cumulus.ini has somehow been set to an invalid value - zero - and MX does not currently handle this. The setting is likely one of the 'interval' settings for internet services, e.g. Wunderground etc. It does not matter whether you actually use the particular. Open Cumulus.ini in a text editor and look at the sections for Wunderground, Awekas etc, and make sure that none of the 'interval' settings are zero - change them to '1' or something else if so.

Perfect .... there were 8 to 10 Interval=0 ... Twitter for example.

Running now; have GUI up; My Weather-Underground is updating

thanks help

BTW, is it normal that WU does some activity every second?

016-12-22 13:33:43.995 WU Response: OK: OK
2016-12-22 13:33:43.995 Uploading WU archive #39
2016-12-22 13:33:44.100 WU Response: OK: OK
2016-12-22 13:33:44.100 Uploading WU archive #40
2016-12-22 13:33:44.205 WU Response: OK: OK
2016-12-22 13:33:44.205 Uploading WU archive #41
2016-12-22 13:33:44.308 WU Response: OK: OK
2016-12-22 13:33:44.309 Uploading WU archive #42
2016-12-22 13:33:44.414 WU Response: OK: OK
2016-12-22 13:33:44.414 End of WU archive upload
2016-12-22 13:34:06.787 Object reference not set to an instance of an object.
2016-12-22 13:36:01.212 WU Response: OK: success

2016-12-22 13:39:00.453 WU Response: OK: success

2016-12-22 13:40:00.066 Writing log entry for 22-Dec-16 13:40:00
2016-12-22 13:40:00.067 Written log entry for 22-Dec-16 13:40:00
2016-12-22 13:40:00.068 Writing today.ini, LastUpdateTime = 22-Dec-16 13:40:00 raindaystart = 35.4900016784668 rain counter = 35.49
2016-12-22 13:42:00.835 WU Response: OK: success

It's doing catch-up with the archive entries from the station logger, when it starts up. It just sends them as fast as WU will accept them. Cumulus 1 is exactly the same.

seen this numerous times today.

------------------------------------------------------------Current culture: English (United States)
Serial: 89E7152BB7309EEEBF08846574567069
Cumulus MX v.3.0.0 build 3041
Today.ini = data\today.ini
Last update=2016-12-22T18:10:00
Connected to station
18:12:51 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
22-Dec-16 18:12:51
Type Ctrl-C to terminate
18:12:55 Downloading Archive Data
18:12:58 Normal running
System.IO.IOException: Unable to write data to the transport connection: An esta
blished connection was aborted by the software in your host machine. ---> System
.Net.Sockets.SocketException: An established connection was aborted by the softw
are in your host machine
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, So
cketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32
size)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32
size)
at ?.?(TcpClient ?, String ?) in C:\Users\steve\RiderProjects\CumulusMX\Cumul
usMX\DavisStation.cs:line 673
at ?.?() in C:\Users\steve\RiderProjects\CumulusMX\CumulusMX\DavisStation.cs:
line 563
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionCo
ntext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, C
ontextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, C
ontextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
**** An error has occurred - please zip up the MXdiags folder and post it in the
forum ****
Press Enter to terminate
----------------------------------------------------------------------------------------------------------------------

hopefully the zip file doesn't contain secure info ?

The station (or something between Cumulus and the station) is closing the connection. MX is just reporting it. It's possible that a future version might try to recover the connection. Whether that would actually achieve anything useful would depend on the cause of the problem with the connection to the station.