Can I try running MX beside a working 1.9.4 build 1098?

[WxLee]

I'd like to try out MX, but I don't want to mess up my configured and running copy of 1.9.4 build 1098. Is it safe to try MX without worry?

[steve]

As long as you don't try to run them at the same time, you'll be fine. You can actually install MX into the same folder as Cumulus 1, and they will just use the same data, but I wouldn't recommend that to begin with, it's best to install to a copy of your Cumulus 1 installation (or just start MX with no data if you wish), then when you switch between the two they will catch up from when they were closed down using data from the logger.

[WxLee]

OK, I tried copying the extracted content of the Cumulus MX download into a folder I made which is a complete copy of my C/Cumulus folder from which Cumulus currently runs OK. Cumulus is shut down.

I clicked on CumulusMX.exe in the new copy folder and a DOS box opened (Windows 7x64 Home premium) showing several status messages. Here is its content:

Current culture: English (United States)
Serial: 543EE10293A9BFA169442DFE8138DEFA
Cumulus MX v.3.0.0 build 3026
This is pre-release beta software
Today.ini = data\today.ini
Last update=7/28/2015 10:00:00 PM
Connected to station
10:19:29 PM 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
7/28/2015 10:19:29 PM
Type Ctrl-C to terminate
10:19:33 PM Downloading Archive Data
10:19:36 PM Normal running
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'System.Net.Sockets.TcpClient'.
at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
at ?.?(Int32 ?) in C:\Users\steve\Documents\Visual Studio 2015\Projects\Cumul
usMX\CumulusMX\DavisStation.cs:line 740
at ?.?() in C:\Users\steve\Documents\Visual Studio 2015\Projects\CumulusMX\Cu
mulusMX\DavisStation.cs:line 551
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


A security warning window popped up asking me to allow CumulusMX network access, and I allowed it.
Several lines later in the DOS box, everything ground to a halt, and it asked me to post the MXdiags folder here (as shown above). This is the only thing MX Diags contains, in a single text file: I never saw any sign of an instance of Cumulus MX running anywhere.

2015-07-28 22:09:59.065 ========================== Cumulus MX starting ==========================
2015-07-28 22:09:59.066 Command line: "C:\Cumulus MX\CumulusMX.exe"
2015-07-28 22:09:59.066 Cumulus MX v.3.0.0 build 3026
2015-07-28 22:09:59.068 Platform: Win32NT
2015-07-28 22:09:59.068 OS version: Microsoft Windows NT 6.1.7601 Service Pack 1
2015-07-28 22:09:59.068 Current culture: English (United States)
2015-07-28 22:09:59.068 Directory separator=\ Decimal separator=. List separator=,
2015-07-28 22:09:59.068 Date separator=/ Time separator=:
2015-07-28 22:09:59.068 Standard time zone name: Eastern Standard Time
2015-07-28 22:09:59.068 Daylight saving time name: Eastern Daylight Time
2015-07-28 22:09:59.068 Daylight saving time? True
2015-07-28 22:09:59.068 7/28/2015 10:09:59 PM
2015-07-28 22:09:59.068 Data path = data\
2015-07-28 22:09:59.073 Creating backup folder backup\20150728220959\
2015-07-28 22:09:59.113 Reading Cumulus.ini file
2015-07-28 22:09:59.119 ASM=10 AST=00:10:00
2015-07-28 22:09:59.121 Cumulus start date: 10/19/2013
2015-07-28 22:09:59.127 Debug logging is disabled
2015-07-28 22:09:59.127 Data logging is disabled
2015-07-28 22:09:59.127 Logging interval = 10
2015-07-28 22:09:59.163 Calculating sunrise and sunset times
2015-07-28 22:09:59.167 Sunrise: 06:20:37
2015-07-28 22:09:59.167 Sunset : 20:51:05
2015-07-28 22:09:59.167 Tomorrow sunrise: 06:21:34
2015-07-28 22:09:59.167 Tomorrow sunset : 20:50:03
2015-07-28 22:09:59.175 Station type: Davis Vantage Pro2
2015-07-28 22:09:59.176 WindUnit=mph RainUnit=in TempUnit=°F PressureUnit=in
2015-07-28 22:09:59.176 YTDRain=0.000 Year=0
2015-07-28 22:09:59.176 RainDayThreshold=-1.000
2015-07-28 22:09:59.176 Offsets and Multipliers:
2015-07-28 22:09:59.176 PO=0.000 TO=0.000 HO=0 WDO=0 ITO=0.000 UVO=0.000
2015-07-28 22:09:59.176 WSM=1.000 WGM=1.000 TM=1.000 TM2=1.000 HM=1.000 RM=1.000 UVM=1.000
2015-07-28 22:09:59.176 Spike removal:
2015-07-28 22:09:59.176 TD=999.000 GD=999.000 WD=999.000 HD=999.000 PD=999.000
2015-07-28 22:09:59.176 MR=999.000 MH=999.000
2015-07-28 22:09:59.176 Cumulus Starting
2015-07-28 22:09:59.176 Opening station
2015-07-28 22:09:59.189 Last update time from today.ini: 7/28/2015 10:00:00 PM
2015-07-28 22:09:59.190 Read today file: Date = 7/28/2015, LastUpdateTime = 7/28/2015 10:00:00 PM, Month = 7
2015-07-28 22:09:59.191 ReadTodayfile: set notraininit false
C:\Cumulus MX\data\alltime.ini
Alltime.ini file read
MonthlyAlltime.ini file read
Month.ini file read
Year.ini file read
2015-07-28 22:09:59.207 Finding raintoday from logfile data\Jul15log.txt
2015-07-28 22:09:59.207 Expecting listsep=, decimal=.
Midnight rain found in the following entry:
28/07/15,00:00,67.3,92,64.9,0.0,0.0,0,0.00,0.00,29.996,16.23,68.7,57,0.0,67.3,67.3,0.0,0,0.000,0.000,72.5,0,0.0,37,0.00,0.00
Setting raintoday from logfile = 0
Calculating rain counter = 16.2299995422363
Midnight rain found = 16.23
Getting rain totals, rain season start = 1
2015-07-28 22:09:59.263 Rainthismonth from dayfile.txt: 3.29
2015-07-28 22:09:59.263 Rainthisyear from dayfile.txt: 19.86
2015-07-28 22:09:59.330 Station type = Davis
2015-07-28 22:09:59.330 LOOP2 enabled
2015-07-28 22:09:59.330 IP address = 192.168.1.207 Port = 22222
2015-07-28 22:09:59.371 Connected OK
2015-07-28 22:09:59.372 Flushing input stream
2015-07-28 22:09:59.572 Reading firmware version
2015-07-28 22:10:01.573 FW version = 3.0

2015-07-28 22:10:01.573 Last update time = 7/28/2015 10:00:00 PM
2015-07-28 22:10:01.574 Reading console time
2015-07-28 22:10:03.574 Received 0x06
2015-07-28 22:10:03.574 ACK received
2015-07-28 22:10:03.574 33-0B-16-1C-07-73-D0-CC
2015-07-28 22:10:03.574 Console clock: 7/28/2015 10:11:51 PM
2015-07-28 22:10:03.574 Start reading archive data
2015-07-28 22:10:03.574 Reading archive data
2015-07-28 22:10:03.574 Loading last N hour data from data logs: 7/28/2015 10:00:00 PM
2015-07-28 22:10:03.617 Loaded 7 entries to last hour data list
2015-07-28 22:10:03.660 Loaded 19 entries to last 3 hour data list
2015-07-28 22:10:03.703 Loaded 107 entries to last 24 hour data list
2015-07-28 22:10:03.783 Loaded 849 entries to recent data list
2015-07-28 22:10:03.791 Loaded 31 entries to daily data list
2015-07-28 22:10:03.799 Get Archive Data
2015-07-28 22:10:03.799 Rollover hour = 0
2015-07-28 22:10:03.799 Last Archive Date: 7/28/2015 10:00:00 PM
2015-07-28 22:10:03.799 Date: 7932
2015-07-28 22:10:03.799 Time: 2200
2015-07-28 22:10:03.813 625 web tags initialised
2015-07-28 22:10:03.906 HTML root path = C:\Cumulus MX\interface
2015-07-28 22:10:03.926 Starting web socket server on port 8002
2015-07-28 22:10:05.799 Received response to DMPAFT, sending date and time
2015-07-28 22:10:05.799 FC-1E-98-08-98-57
2015-07-28 22:10:06.799 Received 0x06
2015-07-28 22:10:06.799 ACK received
2015-07-28 22:10:06.799 Response:00-00-00-00-00-00
2015-07-28 22:10:06.799 Reading data: 0 pages , offset = 0
2015-07-28 22:10:06.799 Get Archive Data
2015-07-28 22:10:06.799 Rollover hour = 0
2015-07-28 22:10:06.799 Last Archive Date: 7/28/2015 10:00:00 PM
2015-07-28 22:10:06.799 Date: 7932
2015-07-28 22:10:06.799 Time: 2200
2015-07-28 22:10:08.799 Received response to DMPAFT, sending date and time
2015-07-28 22:10:08.799 FC-1E-98-08-98-57
2015-07-28 22:10:09.799 Received 0x06
2015-07-28 22:10:09.799 ACK received
2015-07-28 22:10:09.799 Response:00-00-00-00-00-00
2015-07-28 22:10:09.799 Reading data: 0 pages , offset = 0
2015-07-28 22:10:09.799 Updating highs and lows
2015-07-28 22:10:09.801 Start normal reading loop
2015-07-28 22:10:09.804 Start Timers
2015-07-28 22:10:09.804 Starting 1-minute timer
2015-07-28 22:10:09.805 Attempting realtime FTP connect
2015-07-28 22:10:10.987 Starting Realtime timer, interval = 30 seconds
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'System.Net.Sockets.TcpClient'.
at System.Net.Sockets.TcpClient.Connect(String hostname, Int32 port)
at .(Int32 ) in C:\Users\steve\Documents\Visual Studio 2015\Projects\CumulusMX\CumulusMX\DavisStation.cs:line 740
at .() in C:\Users\steve\Documents\Visual Studio 2015\Projects\CumulusMX\CumulusMX\DavisStation.cs:line 551
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

[PaulMy]

Steve will have to respond to the error message.

I never saw any sign of an instance of Cumulus MX running anywhere.

The information in the DOS box is actually CumulusMX running and giving the ongoing status. To see a user interface/console like you may have noticed in other posts is to open a browser and enter the IP address for CumulusMX running

Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)

which will be similar to something like http://192.168.0.xx:8998 and there you will see all the console information, setting tabs, etc. (substitute your actual IP address for 192.168.0.xx which you should be able to get by logging into your router setup). You will then also be able to get to that interface/console from any other computer on your home network by entering that IP address in a browser window.

Enjoy,
Paul

[steve]

This is a bug in the 'periodic disconnect' code - no-one must have tried to use it previously. I can reproduce it myself now that I have a WLIP to play with. For now, you will have to disable it by setting it to zero. If you can't access the settings interface because of the crash, edit Cumulus.ini while MX is stopped and change the VP2PeriodicDisconnectInterval value to zero.

[WxLee]

Steve will have to respond to the error message.

I never saw any sign of an instance of Cumulus MX running anywhere.

The information in the DOS box is actually CumulusMX running and giving the ongoing status. To see a user interface/console like you may have noticed in other posts is to open a browser and enter the IP address for CumulusMX running

Cumulus running at: http://*:8998/
(Replace * with any IP address on this machine, or localhost)

which will be similar to something like http://192.168.0.xx:8998 and there you will see all the console information, setting tabs, etc. (substitute your actual IP address for 192.168.0.xx which you should be able to get by logging into your router setup). You will then also be able to get to that interface/console from any other computer on your home network by entering that IP address in a browser window.

Enjoy,
Paul

Thanks! I guess I was sort of expecting the process of Cumulus MX to open its own browser window. I didn't remember having read that a browser should be opened and pointed to CumulusMX. But now that you pointed it out I do recall having seen that somewhere. Aging brain cells here.

[WxLee]

This is a bug in the 'periodic disconnect' code - no-one must have tried to use it previously. I can reproduce it myself now that I have a WLIP to play with. For now, you will have to disable it by setting it to zero. If you can't access the settings interface because of the crash, edit Cumulus.ini while MX is stopped and change the VP2PeriodicDisconnectInterval value to zero.

Aha. Actually, I began to wonder about that after I posted the above. But it is essential to my usage of the weather station to have the periodic disconnect feature operational, because Weather Underground, if your data stream goes offline to them, locks you out and takes its sweet time ever hooking you back up, sometimes for more than 24 hours. I like having the combination of my own weather data and a local forecast based upon it on my smartphone, which I get from Weather Underground.

If you get the bug fixed, please post mention of it here or let me know some other way. Until then I'll have to continue using the original Cumulus version in its present configuration.

Thanks!

[WxLee]

OK, curiosity got the best of me I decided it won't hurt to shut down the periodic disconnect for "a little while" to get a quick look at Cumulus MX. It looks very NICE!

But, it isn't getting real time data for some reason, like temp is 0 when it should be in the 70s at the moment.

I made a duplicate of my installed Cumulus folder on the C drive, renamed it CumulusMX, and am running the CumulusMX.exe from there. What would I need to do to get the data into CumulsMX? Is it because I renamed the folder?

Edit - I tried saving my Cumulus folder, and then renaming the CumulusMX folder to just Cumulus, but running the CumulusMX.exe from there instead. Still no live data. But I CAN see chart data that is correct for today. I get the feeling I probably need to change some kind of access login or something, but it has been so long since I initially set up Cumulus last summer that I don't remember all the details. Can you point me in the right direction? Looking back through the log file I wrote when I set up Cumulus to feed off my Weatherlink IP on my Vantage Vue, it appears that in order for the Weatherlink IP to be able to send data to the internet, the VP2PeriodicDisconnectInterval is REQUIRED? I had to set that to get things working initially, and have both the Weatherlink website AND Cumulus running concurrently So is there no way for me to see live data in CumuusMX until the bug would be fixed?

Edit 2 - I decided to experiment. I shut down Cumulus, and edited its cumulus.ini to set the VP2PeriodicDisconnectInterval=0. Running Cumulus.exe, it is HUNG on the "Downloading Data" step. So for me, even to run the older version of Cumulus, I MUST have VP2PeriodicDisconnectInterval set to at least =2.

[steve]

The periodic disconnect is intended to allow the WLIP to do its once-a-minute upload to weatherlink.com. The design of the WLIP is such that it can only handle one connection at a time, so if it is connected to Cumulus, it cannot connect to weatherlink.com. Similarly, if it is connected to weatherlink.com, it will not connect to Cumulus. But the setting should not affect the ability of Cumulus to connect to the WLIP, so I don't really understand why it is apparently having that effect. But for whatever reason, it does look like you will have to wait until I release a build with the fix.

[WxLee]

The periodic disconnect is intended to allow the WLIP to do its once-a-minute upload to weatherlink.com. The design of the WLIP is such that it can only handle one connection at a time, so if it is connected to Cumulus, it cannot connect to weatherlink.com. Similarly, if it is connected to weatherlink.com, it will not connect to Cumulus. But the setting should not affect the ability of Cumulus to connect to the WLIP, so I don't really understand why it is apparently having that effect. But for whatever reason, it does look like you will have to wait until I release a build with the fix.

OK, thanks!

[WxLee]

Hi Steve,

I noticed in your latest MX beta mention of this periodic disconnect on Davis systems still being troublesome in a Windows environment. But I don't see the issue listed in your FAQ page where you have all the previous issues crossed off that you have fixed, as well as current issues not yet fixed.

Just wondering if you are making any progress on this?

Have a great day!

WxLee

[steve]

It's listed on the issues page as 'should be fixed in 3029' and listed as a fix in the announcement for 3029. Is it still causing problems?

[WxLee]

I have not tried it since the last time we spoke, waiting for a fix. Sorry I had not seen it where you mentioned it. I'll give it another try and let you know if it still gives me problems.

Thanks!

WxLee

[WxLee]

It seems to be running OK now, in that I no longer get the error message int he command line window. And I can see "some" data being displayed on the interface's different views. But it appears to be recorded data from the past, and not current data. The "Today" view is mostly zeros. I am probably missing a step because it has been some time since I initially read your setup instructions for MX. Is there a way to force an update in MX, or is there something I need to do to get MX grabbing the data from my Vantage Vue? Cumulus 1 was working OK, with no data interruptions before I tried MX. When I look at the MX settings, it appears they all carried over from the Cumulus 1 settings. So I am not sure what to try next.

Could there be any issue running MX on Waterfox 40.0.02? (64 bit Firefox version)

[steve]

If you zip up the MX diags folder and attach it, I'll take a look. Make sure you have debug logging turned on in Cumulus.ini (I may also need data logging also turned on later). Is it actually logging data to the September log file? Are the times on the dashboard screen updating? Are any errors shown in the browser F12 developer console?