Win7 Pro
A number of different things to report.
1. wind speed average set to 255 when no wind
2. ET reset continuous for 8 hours ongoing
3. possible contention bewtween Cumulus1 and CumulusMX running inthe same machine at the same time time 9separate stations, separate connections).
4. must reconfigure new connection before stopping and changing connection.
5. no selection for UV or Solar?
Have been beta testing MX so far on a VUE (inside - not live VP2 Station) with a USB/serial Logger.
Live data is for a VP2 via USB/serial logger using Cumulus1
Two separate setups running in the same PC.
The VUE has no SOLAR or UV, The VP2 has no UV
1 & 2.
MX b3016 is logging;
Code: Select all
2015-01-29 08:32:24.095 Ignoring wind speeds. Speed=0 mph, Avg=255 mph.
2015-01-29 08:32:26.123 Ignoring wind speeds. Speed=0 mph, Avg=255 mph.
2015-01-29 08:32:28.151 Ignoring wind speeds. Speed=0 mph, Avg=255 mph.
Was also attempting an ET reset at the same intervals (ongoing for over 8 hours) but seems now to have stopped after a restart of CumulusMX
5. There does not seem to be anywhere to tell MX if you have Solar and/or UV or not. The data files were copied over from VP2 so had solar entries.
3.
A long time ago after first getting going with a USB/serial logger (clone) on the VUE, I changed it over to WiFi using a Roving Networks WiFly RN-VX module.
This worked well except every week or so it would stop talking to the VUE.
After discussion with Roving Networks it was decided that the issue was insufficient power/voltage as it can use up to 240mA and requires 3.3V +- 10% and was running off the VUE logger port which supplies 3V - the absolute minimum for the WiFly Module.
The WiFly got put aside and the VUE Console was relocated and run off the USB/Serial logger.
As the recently new VP2 is at the opposite end of the building from the Cumulus PC (has been running off a USB extender over Cat6), I decided to try the IP connection again and so made a separate 3.3V power supply for the WiFly and tested the WiFly Logger in place of the USB/Serial logger. I expected it to be reliable as it is the same setup as before but with a proper power supply. However it will not stay connected for more than a few minutes. It appears to stop talking after the 10 minute data uploads.
Here are two logs of the communication error;
Code: Select all
2015-01-28 15:10:27.766 Done uploading graph data files
System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags 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\Documents\Visual Studio 2013\Projects\CumulusMX\CumulusMX\DavisStation.cs:line 424
at .() in c:\Users\steve\Documents\Visual Studio 2013\Projects\CumulusMX\CumulusMX\DavisStation.cs:line 337
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()
2015-01-28 15:15:00.311 Writing log entry for 28/01/2015 3:15:00 p.m.
2015-01-28 15:15:00.312 Written log entry for 28/01/2015 3:15:00 p.m.
2015-01-28 15:15:00.312 Writing today.ini, LastUpdateTime = 28/01/2015 3:15:00 p.m. raindaystart = 0.4 rain counter = 0.4
Code: Select all
2015-01-28 16:00:29.784 Done uploading graph data files
System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags 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\Documents\Visual Studio 2013\Projects\CumulusMX\CumulusMX\DavisStation.cs:line 424
at .() in c:\Users\steve\Documents\Visual Studio 2013\Projects\CumulusMX\CumulusMX\DavisStation.cs:line 332
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()
2015-01-28 16:05:00.258 Writing log entry for 28/01/2015 4:05:00 p.m.
2015-01-28 16:05:00.259 Written log entry for 28/01/2015 4:05:00 p.m.
2015-01-28 16:05:00.259 Writing today.ini, LastUpdateTime = 28/01/2015 4:05:00 p.m. raindaystart = 0.4 rain counter = 0.4
The PC runs;
Mail server (Surgemail)
Webserver (WAMP)
Cumulus1
CumulusMX
Cumulus1 and MX are both uploading files to both the local web server and to the Public hosted web server at the same time.
The WiFly is also a network device however the Lan load pulses from 0 to <0.01% and has a burst of 0.02% at the 10 minute data uploads.
CPU use is low (mostly around 3% with lifts to perhaps 25% on occasion).
Virus Checker is disabled for all the above applications (there is a special config in the Mail Server)
The logs above show the System.IO.IOException: occurs right after uploading the graph data files.
It also seems that Cumulus1 is losing connection with the VP2 from time to time and auto restarting.
Looking back through the Cumulus1 logs, it seems it restarts randomly up to 1 or 2 times a day but sometimes not for days. I had not noticed this as Cumulus1 restarts and carries on OK. While the log description is different it appears to be a similar issue. It is happening more often now.
So it seems that there is may be some form of contention between Cumulus1 and CumulusMX running simultaneously. As this happens with both 2 USB/Serial loggers (COM3 and COM4), or 1 USB/serial logger (COM3) and one IP logger (on port 2000) it would not appear to be a network issue nor a USB driver issue (different drivers).
I have moved CumulusMX to a different PC and so far the problem has not come up again in 9 hours running so will keep running this way for a time to be sure.
Looking back at the logs and backups it does not seem that this happened until b3016. Did not run b3015 but did not happen with b3014 in MX but there may have been a restart in Cumululus1 but that may not be related.
4.
When making a change (i.e. IP to USB/serial or back again), as the system is not in a first time startup mode, it will not run at all if the connection is not present which means the console webpage won't run so the new connections settings have to be made manually to the .ini file.
Code: Select all
2015-01-28 16:11:49.283 Reading console time
System.InvalidOperationException: The operation is not allowed on non-connected sockets.
at System.Net.Sockets.TcpClient.GetStream()
at .() in c:\Users\steve\Documents\Visual Studio 2013\Projects\CumulusMX\CumulusMX\DavisStation.cs:line 1765
at ..ctor(Cumulus ) in c:\Users\steve\Documents\Visual Studio 2013\Projects\CumulusMX\CumulusMX\DavisStation.cs:line 93
at CumulusMX.Cumulus..ctor(Int32 HTTPport, Int32 WSport) in c:\Users\steve\Documents\Visual Studio 2013\Projects\CumulusMX\CumulusMX\Cumulus.cs:line 895
at .Main(String[] args) in c:\Users\steve\Documents\Visual Studio 2013\Projects\CumulusMX\CumulusMX\Program.cs:line 103
Exiting system due to external CTRL-C, or process kill, or shutdown
System.NullReferenceException: Object reference not set to an instance of an object.
at CumulusMX.exitHandler.( ) in c:\Users\steve\Documents\Visual Studio 2013\Projects\CumulusMX\CumulusMX\Program.cs:line 180