Hi,
I have a Davis Vue and recieve 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."
child process received timeout signal; everyday **solved**
Moderator: Mattk
Re: child process received timeout signal; everyday about 2:
Hi,
I've traced my problem to my wireless router's time check/adjustment. I was unable to get CumulusMX to remain connected consistently throughout a day.
I've reverted back to using Cumulus and occasionally Weatherlink. There is no issue with Meteobridge in this regard.
I've traced my problem to my wireless router's time check/adjustment. I was unable to get CumulusMX to remain connected consistently throughout a day.
I've reverted back to using Cumulus and occasionally Weatherlink. There is no issue with Meteobridge in this regard.