GW1000 issue

[LindaFNM]

I had an issue with my Pi and GW1000, this is copied from the terminal, is it something I'm doing please?
Also, when using CreateMissing, I'm not getting sunshine hours, my rollover time is midnight.
Thank you.

Failed to discover any GW1000 devices
Failed to discover any GW1000 devices
Failed to discover any GW1000 devices
Failed to discover any GW1000 devices
Failed to discover any GW1000 devices
Failed to discover any GW1000 devices
Failed to discover any GW1000 devices
Ctrl+C pressed

Cumulus terminating
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'System.Net.Sockets.TcpClient'.
at System.Net.Sockets.TcpClient.GetStream () [0x00019] in <9c6e2cb7ddd8473fa420642ddcf7ce48>:0
at CumulusMX.GW1000Station.Start () [0x0015c] in <dd52e756d74a413c919fc7e1d298e7d3>:0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00014] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00071] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x0002b] in <533173d24dae460899d2b10975534bb0>:0
at System.Threading.ThreadHelper.ThreadStart () [0x00008] in <533173d24dae460899d2b10975534bb0>:0
**** An error has occurred - please zip up the MXdiags folder and post it in the forum ****
Press Enter to terminate

here's a chunk from the log file
021-04-17 17:00:00.348 Sunrise: 06:07:47
2021-04-17 17:00:00.348 Sunset : 20:05:21
2021-04-17 17:00:00.349 Tomorrow sunrise: 06:05:45
2021-04-17 17:00:00.349 Tomorrow sunset : 20:06:57
2021-04-17 17:00:00.350 *** Data input appears to have stopped
2021-04-17 17:00:04.952 DoCommand(CMD_GW1000_LIVEDATA): No response received
2021-04-17 17:00:04.952 GetLiveData: Invalid response
2021-04-17 17:00:13.946 ERROR: No data received from the GW1000 for 30 seconds
2021-04-17 17:00:13.946 Running GW-1000 auto-discovery...
2021-04-17 17:00:15.957 DoCommand(CMD_GW1000_LIVEDATA): No response received
2021-04-17 17:00:15.958 GetLiveData: Invalid response
2021-04-17 17:00:26.963 DoCommand(CMD_GW1000_LIVEDATA): No response received
2021-04-17 17:00:26.963 GetLiveData: Invalid response
2021-04-17 17:00:37.969 DoCommand(CMD_GW1000_LIVEDATA): No response received
2021-04-17 17:00:37.969 GetLiveData: Invalid response
2021-04-17 17:00:43.946 ERROR: No data received from the GW1000 for 30 seconds
2021-04-17 17:00:43.946 Running GW-1000 auto-discovery...
2021-04-17 17:00:48.974 DoCommand(CMD_GW1000_LIVEDATA): No response received
2021-04-17 17:00:48.975 GetLiveData: Invalid response
2021-04-17 17:00:59.981 DoCommand(CMD_GW1000_LIVEDATA): No response received
2021-04-17 17:00:59.981 GetLiveData: Invalid response
2021-04-17 17:01:00.346 *** Data input appears to have stopped
2021-04-17 17:01:10.986 DoCommand(CMD_GW1000_LIVEDATA): No response received
2021-04-17 17:01:10.986 GetLiveData: Invalid response
2021-04-17 17:01:13.946 ERROR: No data received from the GW1000 for 30 seconds
2021-04-17 17:01:13.946 Running GW-1000 auto-discovery...
2021-04-17 17:01:21.991 DoCommand(CMD_GW1000_LIVEDATA): No response received
2021-04-17 17:01:21.991 GetLiveData: Invalid response
2021-04-17 17:01:32.996 DoCommand(CMD_GW1000_LIVEDATA): No response received
2021-04-17 17:01:32.996 GetLiveData: Invalid response
2021-04-17 17:01:43.946 ERROR: No data received from the GW1000 for 30 seconds
2021-04-17 17:01:43.946 Running GW-1000 auto-discovery...
2021-04-17 17:01:44.002 DoCommand(CMD_GW1000_LIVEDATA): No response received
2021-04-17 17:01:44.003 GetLiveData: Invalid response
2021-04-17 17:01:55.008 DoCommand(CMD_GW1000_LIVEDATA): No response received
2021-04-17 17:01:55.009 GetLiveData: Invalid response
2021-04-17 17:02:00.376 *** Data input appears to have stopped
2021-04-17 17:02:06.015 DoCommand(CMD_GW1000_LIVEDATA): No response received
2021-04-17 17:02:06.017 GetLiveData: Invalid response

[KarlS]

If you are running an older version of CumulusMX and your GW1000 firmware is 1.6.6, please upgrade to the latest build. Your GW1000 problem will likely be solved.

[LindaFNM]

Sorry, I should have said, I’m running Build 3122, GW firmware is indeed v1.6.6. I was under the impression that the firmware updates were automatic and pushed by Ecowitt. Thanks for the heads up, I’ll Google if there’s any way I can update the GW myself.

[uktricky]

Sorry, I should have said, I’m running Build 3122, GW firmware is indeed v1.6.6. I was under the impression that the firmware updates were automatic and pushed by Ecowitt. Thanks for the heads up, I’ll Google if there’s any way I can update the GW myself.

I use WS View from Phone to push Firmware updates to the GW1000

[LindaFNM]

Thank you for posting, usually, the app asks if you want to upgrade but it isn’t doing it this time either on my iPad or phone. I’ve just emailed Ecowitt just in case, I’m a bit reluctant to stop everything and mess around as I had a horrible job trying to connect my GW1000 for some reason last time!

[mcrossley]

From your log snippet is seems there is no network connectivity between Cumulus and your GW1000.

Regarding the missing sunshine hours. Do you use a midnight or 9am day rollover?
Are the sunshine hours logged in your monthly log files? - you can use the monthly file viewer/editor to check the Sun Hours column is incrementing.

[LindaFNM]

Mark, thank you for replying. I’m to a loss to know what to do about this, I’ve been uploading to Ecowitt.net now to avoid issues with the GW not being properly on line, not sure if this is down to my inexperience or an issue. The GW is now on a separate lead and not connected direct to the USB charger to see if this helps but doesn’t seem to have. I’m awaiting a response from Ecowitt to see why the firmware may not be updating.

I’m on a midnight rollover and the sunshine hours are perfect on the normal logging, it’s just the create missing. I lost 4 days in the middle of April which I’m trying to recreate after messing up my Raspberry Pi. It doesn’t really matter that much so please don’t worry.

[mcrossley]

Can you post your April log file please, and I'll take a look to see if I can spot any issues with it...

[LindaFNM]

I had the same thing happen again at 21.20 last night. I’m at a loss. Uploads continue to Ecowitt and I understand that programs work differently, but I’m also running WD on the Pi which doesn’t seem to be affected either? I discovered there was no logging last night and restarted, which happens without any issues. Am I correct in thinking that v3122 cured the problems? Sorry!

[mcrossley]

Please switch on both debug and data logging. Then post the MXdiags log file once you have an issue.

B3122 did address some issues, but another has come to light recently that seems to occur occasionally if two programs are accessing the GW1000 at the same time. A fix for that will be in the next release.

[LindaFNM]

Mark, thank you. I have the logs etc from last night, plus the terminal scripts. I’ll get them off the Pi this evening and post them. Very much appreciate your time. Linda

[LindaFNM]

Mark, my apologies as this is somewhat late........... Please find attached zip of the terminal window plus the end of the log file when CumulusMX shut down. Thank you.

[mcrossley]

Thanks, a fix for the crash will be in the next release.

[LindaFNM]

Mark, thank you very much.