Please read the posts in the Announcements section about the current status of Cumulus development now that I have retired

Please read this post before posting

Latest Cumulus release v1.9.4 (build 1099) - Nov 28 2014
Latest Cumulus MX release - v3.0.0 build 3043 Jan 20 2017. See this post for download

Consistent Daily Connection Exception

Discussion of version 3 of Cumulus, which runs on Windows, Linux, and OS X. All Cumulus MX queries in here, please.
glennpm
Posts: 51
Joined: Sat Dec 17, 2016 1:31 pm
Weather Station: Davis Vantage Vue
Operating System: Windows 10
Location: Wiscasset, Maine USA

Consistent Daily Connection Exception

Postby glennpm » Wed Mar 22, 2017 7:35 pm

For many days I am losing connection at about 2:15PM each afternoon. I use Windows "Task Scheduler" daily which Starts MX at 2:30AM daily. There is no stop time associated with the task. I have also set USB ports to never shut off for my data logger. From today's diag file, March 22:

"2017-03-22 14:14:19.557 !!! loop data not received
2017-03-22 14:14:20.066 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 CumulusMX.DavisStation.SendLoopCommand(TcpClient tcpPort, String commandString) in C:\Users\steve\Documents\Visual Studio 2015\Projects\CumulusMX\CumulusMX\DavisStation.cs:line 766
at CumulusMX.DavisStation.Start() in C:\Users\steve\Documents\Visual Studio 2015\Projects\CumulusMX\CumulusMX\DavisStation.cs:line 575
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()
2017-03-22 14:15:00.330 *** Data input appears to have stopped
2017-03-22 14:16:00.390 *** Data input appears to have stopped
2017-03-22 14:17:00.528 *** Data input appears to have stopped
2017-03-22 14:18:00.582 *** Data input appears to have stopped
2017-03-22 14:19:00.644 *** Data input appears to have stopped
2017-03-22 14:20:00.696 *** Data input appears to have stopped
2017-03-22 14:20:00.697 Writing log entry for 3/22/2017 2:20:00 PM"

and here is diag from yesterday, March 21:

2017-03-21 14:14:27.775 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 CumulusMX.DavisStation.SendLoopCommand(TcpClient tcpPort, String commandString) in C:\Users\steve\Documents\Visual Studio 2015\Projects\CumulusMX\CumulusMX\DavisStation.cs:line 766
at CumulusMX.DavisStation.Start() in C:\Users\steve\Documents\Visual Studio 2015\Projects\CumulusMX\CumulusMX\DavisStation.cs:line 580
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()
2017-03-21 14:16:00.166 *** Data input appears to have stopped

User avatar
steve
Cumulus Author
Posts: 26655
Joined: Mon Jun 02, 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: Consistent Daily Connection Exception

Postby steve » Wed Mar 22, 2017 7:54 pm

Something (possibly the logger itself) is causing the connection to Cumulus to be closed. Do you have the logger uploading to weatherlink.com? If so, you could try turning that off to see if the problem goes away, or experiment with increasing the 'disconnect period' setting.
Steve
-----
Hosting available for Cumulus web sites. See http://sandaysoft.com/forum/viewtopic.php?f=2&t=11876

Please read the posts in the Announcements section about the current status of Cumulus development since I have retired from my day job

glennpm
Posts: 51
Joined: Sat Dec 17, 2016 1:31 pm
Weather Station: Davis Vantage Vue
Operating System: Windows 10
Location: Wiscasset, Maine USA

Re: Consistent Daily Connection Exception

Postby glennpm » Thu Mar 23, 2017 11:33 am

Hi Steve,

No I don't upload to weatherlink.com. I did try changing the "disconnect period" to "5" under the "Station settings". I couldn't find anything in the Wiki that said what the units where for this entry. Are they seconds?

I also noted in my logger from yesterday that just prior to the disconnect, the time was being checked. I'll see what happens this afternoon and report.

thanks

User avatar
steve
Cumulus Author
Posts: 26655
Joined: Mon Jun 02, 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: Consistent Daily Connection Exception

Postby steve » Thu Mar 23, 2017 1:36 pm

Yes, the units are in seconds. If you're not uploading to weatherlink.com, you should leave the setting at zero.

I did wonder whether it was a daily time check which was causing the disconnect - this the console itself doing that, you mean? Does the logger/console have a setting to get the time from the internet? It must be something specific to your system; while a very few people do experience occasional disconnects, I'm not aware of anyone who gets it regularly, as you are doing.
Steve
-----
Hosting available for Cumulus web sites. See http://sandaysoft.com/forum/viewtopic.php?f=2&t=11876

Please read the posts in the Announcements section about the current status of Cumulus development since I have retired from my day job

glennpm
Posts: 51
Joined: Sat Dec 17, 2016 1:31 pm
Weather Station: Davis Vantage Vue
Operating System: Windows 10
Location: Wiscasset, Maine USA

Re: Consistent Daily Connection Exception

Postby glennpm » Thu Mar 23, 2017 1:41 pm

Hi Steve,

I'll set it back to zero then. Yes it is the console time check as best I can tell. Yesterday I couldn't find a way to do anything about it in the Davis Vue setup sequence. I've got more time today so will see what I can find.

thanks!

glennpm
Posts: 51
Joined: Sat Dec 17, 2016 1:31 pm
Weather Station: Davis Vantage Vue
Operating System: Windows 10
Location: Wiscasset, Maine USA

Re: Consistent Daily Connection Exception

Postby glennpm » Thu Mar 23, 2017 7:07 pm

Hi Steve,

Worked fine so far today, past the 2:14 clock time anyway.

The Davis Vue does not update to an internet time clock. It is done manually only. My console was late by only 10 seconds which I reset. I use Meteobridge and there is no setting there for time sync either.

Glenn

User avatar
steve
Cumulus Author
Posts: 26655
Joined: Mon Jun 02, 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: Consistent Daily Connection Exception

Postby steve » Thu Mar 23, 2017 8:00 pm

If it starts happening again, I think the best way to determine what's going on would be to capture a TCP/IP trace at around that time, using something like Wireshark.
Steve
-----
Hosting available for Cumulus web sites. See http://sandaysoft.com/forum/viewtopic.php?f=2&t=11876

Please read the posts in the Announcements section about the current status of Cumulus development since I have retired from my day job

glennpm
Posts: 51
Joined: Sat Dec 17, 2016 1:31 pm
Weather Station: Davis Vantage Vue
Operating System: Windows 10
Location: Wiscasset, Maine USA

Re: Consistent Daily Connection Exception

Postby glennpm » Thu Mar 23, 2017 8:25 pm

Great, I'll do that Steve.

Thanks for your help!

Glenn

glennpm
Posts: 51
Joined: Sat Dec 17, 2016 1:31 pm
Weather Station: Davis Vantage Vue
Operating System: Windows 10
Location: Wiscasset, Maine USA

Re: Consistent Daily Connection Exception

Postby glennpm » Fri Mar 24, 2017 7:14 pm

Well still a problem I'm sorry to say. I installed Wireshark but did not have it running at the time of the disconnect. I'm not sure what to look for within it anyway, i.e. don't know what data to review for the WLAN of my logger device.

I also posted this message on the Meteobridge forum. Note that the logger restarts flowing data but MX does not reset itself to start getting data again once it is flowing.

"Hi,

I have a Davis Vue and receive input to CumulusMX wirelessly. Each day for many days, I lose the connection to CumlusMX. The logger restarts so my Meteobridge shows live data. Would like guidance please on what to look for.

I run Windows 10; computer is always on, no sleep; USB power is continually supplied, noting that I receive data wirelessly

From the CumulusMX diagnostic file for today:

"2017-03-24 14:10:00.423 Writing today.ini, LastUpdateTime = 3/24/2017 2:10:00 PM raindaystart = 4.44 rain counter = 4.44
2017-03-24 14:14:42.756 !!! loop data not received
2017-03-24 14:14:43.411 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 CumulusMX.DavisStation.SendLoopCommand(TcpClient tcpPort, String commandString) in C:\Users\steve\Documents\Visual Studio 2015\Projects\CumulusMX\CumulusMX\DavisStation.cs:line 766
at CumulusMX.DavisStation.Start() in C:\Users\steve\Documents\Visual Studio 2015\Projects\CumulusMX\CumulusMX\DavisStation.cs:line 575
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()"

From Meteobridge:

System

Platform: TL-MR3020 (no USB hub)
RAM: 29364 kB total, 3340 kB free (88% used)
SW Version: Meteobridge 3.2 (Mar 4 2017, build 10970), FW 1.4
Uptime: 16 days, 3 hours, 18 minutes Buffer: 2 items (0%)

Network

MAC: E8:DE:27:64:73:F4
LAN IP: -- WLAN IP: 192.168.1.45 (I fixed this address on my LAN)
LAN Mask: -- WLAN Mask: 255.255.255.0
Gateway: 192.168.1.1 TX Traffic: 232.3 MB
DNS: 192.168.1.1 RX Traffic: 627.2 MB
WAN IP: (hidden for this message) Provider: Time Warner Cable

From logger:

"logger (24.03.2017 14:25:54): child process received timeout signal (14).
logger (24.03.2017 14:25:54): disconnect station 0 (Vantage): exit
logger (24.03.2017 14:25:55): data logger stopped.
logger (24.03.2017 14:25:55): historical data loaded (19 records).
logger (24.03.2017 14:25:55): data logger (version 5.0t, build 10970) started.
logger (24.03.2017 14:25:56): connect station 0 (Vantage via USB serial).
logger (24.03.2017 14:25:56): wakeup sent.
logger (24.03.2017 14:25:56): internal logger activated.
logger (24.03.2017 14:25:56): syncing.
logger (24.03.2017 14:25:59): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (24.03.2017 14:25:59): services paused.
logger (24.03.2017 14:26:06): gettime request sent.
logger (24.03.2017 14:26:06): no Vantage time offset.
logger (24.03.2017 14:26:06): eeprom request sent.
logger (24.03.2017 14:26:06): rain collector size 0.01 inch per tick.
logger (24.03.2017 14:26:06): transmitter 1 active as station type (#0) "ISS".
logger (24.03.2017 14:26:06): firmware version request sent.
logger (24.03.2017 14:26:06): firmware version 3.00
logger (24.03.2017 14:26:06): no reading of Vantage's internal logger.
logger (24.03.2017 14:26:10): sensors are now providing data.
logger (24.03.2017 14:26:10): services started."

User avatar
steve
Cumulus Author
Posts: 26655
Joined: Mon Jun 02, 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: Consistent Daily Connection Exception

Postby steve » Fri Mar 24, 2017 8:07 pm

Have I misunderstood something here? Is Cumulus connected to the Vue via Meteobridge?

I don't know what that "logger" trace is, but is it showing that Meteobridge is losing the connection to the Vue? If Cumulus is indeed connected via Meteobridge, then it follows that Cumulus will also lose the connection. Cumulus currently has no mechanism for reconnecting to the station if the connection is lost, simply because I ran MX for two years 24/7 with an IP logger without ever experiencing a disconnect, so I have never got around to writing any code to handle that.
Steve
-----
Hosting available for Cumulus web sites. See http://sandaysoft.com/forum/viewtopic.php?f=2&t=11876

Please read the posts in the Announcements section about the current status of Cumulus development since I have retired from my day job

glennpm
Posts: 51
Joined: Sat Dec 17, 2016 1:31 pm
Weather Station: Davis Vantage Vue
Operating System: Windows 10
Location: Wiscasset, Maine USA

Re: Consistent Daily Connection Exception

Postby glennpm » Fri Mar 24, 2017 8:11 pm

Hi Steve,

That's correct, "Cumulus is connected to the Vue via Meteobridge". I'll see what response I get from the Meteobridge creator.

Thanks,
Glenn

glennpm
Posts: 51
Joined: Sat Dec 17, 2016 1:31 pm
Weather Station: Davis Vantage Vue
Operating System: Windows 10
Location: Wiscasset, Maine USA

Re: Consistent Daily Connection Exception

Postby glennpm » Tue Mar 28, 2017 12:54 pm

Hi Steve,

Just want to provide an update regarding my connection issue.

I found that my Netgear N150 wireless router's time check was causing the logger to MX connection issue. I was unable to do anything to fix it. I have reverted back to using Cumulus and it has worked fine for me for a few days now. I really liked the MX interface but it is more important to me to consistently record output form my weather station.

Perhaps sometime in the future you may input MX code to with a user adjustable reconnect time ;-)

Glenn

User avatar
steve
Cumulus Author
Posts: 26655
Joined: Mon Jun 02, 2008 6:49 pm
Weather Station: None
Operating System: None
Location: Vienne, France
Contact:

Re: Consistent Daily Connection Exception

Postby steve » Tue Mar 28, 2017 1:01 pm

The Davis DLL that Cumulus 1 uses handles the connection, it presumably automatically reconnects when required. It is something I intend to look at adding to MX, at some point.
Steve
-----
Hosting available for Cumulus web sites. See http://sandaysoft.com/forum/viewtopic.php?f=2&t=11876

Please read the posts in the Announcements section about the current status of Cumulus development since I have retired from my day job

glennpm
Posts: 51
Joined: Sat Dec 17, 2016 1:31 pm
Weather Station: Davis Vantage Vue
Operating System: Windows 10
Location: Wiscasset, Maine USA

Re: Consistent Daily Connection Exception

Postby glennpm » Tue Mar 28, 2017 1:22 pm

Great thanks Steve,

Cumulus 1 has been handling the connection fine for the last few days.

Glenn

jlmr731
Posts: 117
Joined: Sat Aug 27, 2016 12:11 am
Weather Station: Davis vantage pro 2
Operating System: Debian
Location: Youngstown, Ohio
Contact:

Re: Consistent Daily Connection Exception

Postby jlmr731 » Wed Mar 29, 2017 2:44 am

You say its the wireless router causing the problems. Dont know your setup but if your connecting to meteobridge via wireless this may be your problem.
try plugging your meteobridge in along with the connecting computer and see what happens.


Return to “Cumulus MX”

Who is online

Users browsing this forum: No registered users and 2 guests