Welcome to the Cumulus Support forum.

Latest Cumulus MX V4 release 4.4.2 (build 4085) - 12 March 2025

Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024

Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)

Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki

If you are posting a new Topic about an error or if you need help PLEASE read this first viewtopic.php?p=164080#p164080

Lots of LOOP errors

From Cumulus MX version 3 build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since, and has recently released Cumulus MX version 4. He has made the code available on GitHub. It is Mark's hope that others will join in this development, but at the very least he welcomes your ideas for future developments (see Cumulus MX Development suggestions).

Moderator: mcrossley

Post Reply
User avatar
weernoordbergum
Posts: 23
Joined: Sat 24 Dec 2022 10:43 pm
Weather Station: Ecowitt WS90
Operating System: Raspberry Pi 4B

Lots of LOOP errors

Post by weernoordbergum »

I seem to get a lot of LOOP errors
Anyone explain how these errors occur and why?
CumulusMX is running fine
And a lot of missed packets it seems
Schermafbeelding 2024-12-19 133325.png
2024-12-19 13:26:08 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:26:02 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:25:56 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:25:50 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:25:45 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:25:38 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:25:31 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:25:25 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:25:18 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:25:10 - LOOP: 40 - Expected data not received, expected 99 bytes, got 1
2024-12-19 13:23:51 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:23:46 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:23:39 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:23:33 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:23:27 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:23:21 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:23:15 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:23:07 - LOOP: 5 - Expected data not received, expected 99 bytes, got 1
2024-12-19 13:22:59 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:22:59 - InitTCP: Error - Unable to write data to the transport connection: Broken pipe.
2024-12-19 13:22:54 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:22:48 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:22:42 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:22:36 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:22:30 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:22:24 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:22:18 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:22:12 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:22:04 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:21:58 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:21:52 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:21:46 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:21:40 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:21:33 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:21:27 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:19:45 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:18:02 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Unable to write data to the transport connection: Connection reset by peer.
2024-12-19 13:18:01 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:17:54 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:17:48 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:17:42 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:17:36 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:17:30 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:15:48 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:15:42 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:15:35 - SendLoopCommand: Error sending LOOP command [LPS 2 1]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:15:28 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:15:08 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
2024-12-19 13:14:59 - LOOP: 42 - Expected data not received, expected 99 bytes, got 1
2024-12-19 13:13:37 - SendLoopCommand: Error sending LOOP command [LOOP 50]: Cannot access a disposed object. Object name: 'System.Net.Sockets.NetworkStream'.
You do not have the required permissions to view the files attached to this post.
Top
User avatar
mcrossley
Posts: 14384
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2/WLL
Operating System: Bullseye Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:
Contact mcrossley

Re: Lots of LOOP errors

Post by mcrossley »

What sort of logger are you using?
Top
User avatar
weernoordbergum
Posts: 23
Joined: Sat 24 Dec 2022 10:43 pm
Weather Station: Ecowitt WS90
Operating System: Raspberry Pi 4B

Re: Lots of LOOP errors

Post by weernoordbergum »

I'm using a meteobridge nano sd

Sometimes in the meteobridge log it states second request denied
I changed the response time in the Cumulus MX Davis connection settings
My nano sd logger stalled sometimes but that is now much better
I think Cumulus MX was the culprit of the data stalling of my primary station which is a Davis VP 2
Top
User avatar
mcrossley
Posts: 14384
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2/WLL
Operating System: Bullseye Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:
Contact mcrossley

Re: Lots of LOOP errors

Post by mcrossley »

The meteobridge devices are not great on the network side. I have had to add a lot of extra code into Cumulus to try and cope with their fobiles. The old Davis IP loggers just worked!
Top
User avatar
weernoordbergum
Posts: 23
Joined: Sat 24 Dec 2022 10:43 pm
Weather Station: Ecowitt WS90
Operating System: Raspberry Pi 4B

Re: Lots of LOOP errors

Post by weernoordbergum »

I have the following times set on the Davis advanced option page
TCP/ip init wait time 150ms
TCP/ip response delay time 120ms

Is there a recommended setting for these times?

For now I'll leave them as they are, Cumulus MX is working fine and the wind updates every 2 seconds on the dashboard
Top
User avatar
mcrossley
Posts: 14384
Joined: Thu 07 Jan 2010 9:44 pm
Weather Station: Davis VP2/WLL
Operating System: Bullseye Lite rPi
Location: Wilmslow, Cheshire, UK
Contact:
Contact mcrossley

Re: Lots of LOOP errors

Post by mcrossley »

They should be fine. The problem is that meteobridges just abort the connection at their end, they do not close down the connection nicely so MX still thinks it is active and tries to use it. You get the error message and MX reconnects and continues.
Top
User avatar
weernoordbergum
Posts: 23
Joined: Sat 24 Dec 2022 10:43 pm
Weather Station: Ecowitt WS90
Operating System: Raspberry Pi 4B

Re: Lots of LOOP errors

Post by weernoordbergum »

Thanks for the help
Top
Post Reply

Return to “Cumulus MX version 4”