Welcome to the Cumulus Support forum.

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

Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 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

LOOP: xx - Expected data not received, expected 99 bytes, got 0

From build 3044 the development baton passed to Mark Crossley. Mark has been responsible for all the Builds since. 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
BigOkie
Posts: 272
Joined: Tue 28 May 2013 1:06 am
Weather Station: Davis VP2 Plus
Operating System: Raspian Buster (RPi 3b)
Location: Tulsa, OK

Re: LOOP: xx - Expected data not received, expected 99 bytes, got 0

Post by BigOkie »

I get these errors too from time to time but they never last more than a minute or two. I have a wireless 6253 with the solar suite and have had it now since Jun 2013. Example from today:

Code: Select all

2024-01-28 10:19:43 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:19:42 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:19:38 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:19:37 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:19:33 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:19:32 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:19:28 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:19:27 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:19:23 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:19:22 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:19:17 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:19:16 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:19:12 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:19:11 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:19:07 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:19:06 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:19:02 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:19:01 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:18:57 - LOOP: 3 - Timed out waiting for LOOP data
2024-01-28 10:18:56 - LOOP: 3 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:18:52 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:18:51 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:18:46 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:18:45 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:18:41 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:18:40 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:18:36 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:18:35 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:18:31 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:18:30 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:18:26 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:18:25 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:18:20 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:18:19 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:18:15 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:18:14 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:18:10 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:18:09 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:18:05 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:18:04 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:18:00 - LOOP: 3 - Timed out waiting for LOOP data
2024-01-28 10:17:59 - LOOP: 3 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:17:54 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:17:53 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:17:49 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:17:48 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-01-28 10:17:44 - LOOP: 2 - Timed out waiting for LOOP data
2024-01-28 10:17:43 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
Is it possible that this can happen (specifically with the wireless stations) when the station is in a run of not receiving packets? I do know that my stats are pretty good (98 to 99.5 percent reception is common; usually the reception gets worse the colder it is and it's not real bad today).
Top
lgeitner
Posts: 19
Joined: Wed 11 Aug 2021 1:40 pm
Weather Station: Davis VP2 6163
Operating System: Linux

Re: LOOP: xx - Expected data not received, expected 99 bytes, got 0

Post by lgeitner »

I wondered myself if perhaps the consoles were receiving bad packets of data from the transmitter. However, I have checked the percentage of good packets from both of my consoles and they are almost always 100%.

My transmitter is not that far from my consoles approximately 15 meters (~50 feet).

Now that you mention it, we were in a cold spell for a few weeks temperatures around 0-20 F (~-10 to -20C). That was around the time I was noticing all the errors. In the last couple of days we have had near record high temperatures for my location 50-60 F (10-15C). I have noticed that there has not been nearly as many errors in the past couple of days from either of my 2 raspberry pi 5's.

I am going to pay attention in the future if the errors occur more frequently when the weather is colder.

Thank You for bringing that to my attention!
Lancee
Top
BigOkie
Posts: 272
Joined: Tue 28 May 2013 1:06 am
Weather Station: Davis VP2 Plus
Operating System: Raspian Buster (RPi 3b)
Location: Tulsa, OK

Re: LOOP: xx - Expected data not received, expected 99 bytes, got 0

Post by BigOkie »

lgeitner wrote: ↑Sun 28 Jan 2024 8:26 pm I wondered myself if perhaps the consoles were receiving bad packets of data from the transmitter. However, I have checked the percentage of good packets from both of my consoles and they are almost always 100%.

My transmitter is not that far from my consoles approximately 15 meters (~50 feet).

Now that you mention it, we were in a cold spell for a few weeks temperatures around 0-20 F (~-10 to -20C). That was around the time I was noticing all the errors. In the last couple of days we have had near record high temperatures for my location 50-60 F (10-15C). I have noticed that there has not been nearly as many errors in the past couple of days from either of my 2 raspberry pi 5's.

I am going to pay attention in the future if the errors occur more frequently when the weather is colder.

Thank You for bringing that to my attention!
Lancee
Did you say your Davis was cabled and not a wireless (like mine)? I would think the cabled versions would not have a lot of packet errors given that it's cabled. Although faulty cable or environmental conditions I'm sure could cause them. I just figured these errors were part of the routine not getting a valid LOOP/LOOP2 packet during the time when the console loses sync with the transmitter. This is my current day's (from midnight) reception stats.
status.png
You do not have the required permissions to view the files attached to this post.
Top
lgeitner
Posts: 19
Joined: Wed 11 Aug 2021 1:40 pm
Weather Station: Davis VP2 6163
Operating System: Linux

Re: LOOP: xx - Expected data not received, expected 99 bytes, got 0

Post by lgeitner »

My davis transmitter is wireless. However, I have my davis consoles connected to my raspberry pi 5's with a meteo-pi that uses an rj11 telephone cable to connect the meteo-pi hat on the raspberry pi 5 to the data logger in the back of the davis console.
Top
lgeitner
Posts: 19
Joined: Wed 11 Aug 2021 1:40 pm
Weather Station: Davis VP2 6163
Operating System: Linux

Re: LOOP: xx - Expected data not received, expected 99 bytes, got 0

Post by lgeitner »

I installed the 2 new cables that are shielded and contain twisted pair in them from digi-key. I am still receiving the same errors.

I should note the temperature this morning was very cold around 20F (-7C) around 5 AM ET or so. It does seem that I receive a lot more of these errors when the weather is colder outside. I did notice there were a number of bad packets between my transmitter and my console as well.

Someone did previously mention they receive a number of similar errors the colder the weather is.

This is something I probably going to have to live with!

Lance

2024-02-07 06:37:16 - LOOP: 15 - Timed out waiting for LOOP data
2024-02-07 06:37:15 - LOOP: 15 - Expected data not received, expected 99 bytes, got 0
2024-02-07 06:37:09 - LOOP: 12 - Expected data not received, expected 99 bytes, got 0
2024-02-07 06:36:46 - LOOP: 9 - Timed out waiting for LOOP data
2024-02-07 06:36:45 - LOOP: 9 - Expected data not received, expected 99 bytes, got 0
2024-02-07 06:36:28 - LOOP: 47 - Timed out waiting for LOOP data
2024-02-07 06:36:27 - LOOP: 47 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:27:12 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:27:11 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:27:06 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:27:05 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:27:01 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:26:59 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:26:55 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:26:54 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:26:50 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:26:49 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:26:45 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:26:44 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:26:40 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:26:39 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:26:35 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:26:34 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:26:29 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:26:28 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:26:24 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:26:23 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:26:19 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:26:18 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:26:14 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:26:13 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:26:09 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:26:08 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:26:04 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:26:03 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:25:58 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:25:57 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:25:53 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:25:52 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:25:48 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:25:47 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:25:43 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:25:42 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:25:38 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:25:37 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:25:33 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:25:32 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:25:28 - LOOP: 2 - Timed out waiting for LOOP data
2024-02-07 04:25:27 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 04:25:22 - LOOP: 2 - Timed out waiting for LOOP data
Top
User avatar
PaulMy
Posts: 3852
Joined: Sun 28 Sep 2008 11:54 pm
Weather Station: Davis VP2 Plus 24-Hour FARS
Operating System: Windows8 and Windows10
Location: Komoka, ON Canada
Contact:
Contact PaulMy

Re: LOOP: xx - Expected data not received, expected 99 bytes, got 0

Post by PaulMy »

Hi,
Like you, I get those errors periodically on my VP2 ISS with Vue console and WiFiLogger to CMX

Code: Select all

2024-02-07 20:06:58 - Realtime[206]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 20:02:58 - Realtime[194]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 20:02:42 - LOOP: 9 - Expected data not received, expected 99 bytes, got 0
2024-02-07 20:02:18 - Realtime[192]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 20:00:58 - Realtime[188]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 20:00:18 - Realtime[186]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:59:38 - Realtime[184]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:58:58 - Realtime[182]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:58:18 - Realtime[180]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:57:38 - Realtime[178]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:56:58 - Realtime[176]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:56:18 - Realtime[174]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:55:38 - Realtime[172]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:54:38 - Realtime[169]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:53:58 - Realtime[167]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:51:58 - Realtime[161]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:50:59 - FTP[157]: Upload of public_html/cumulusmx/realmore.txt failed
2024-02-07 19:50:29 - FTP[156]: Upload of public_html/cumulusmx/realtimetags.php failed
2024-02-07 19:50:22 - FTP[155]: Upload of public_html/komokaweather-ca2/realtime.txt failed
2024-02-07 19:49:17 - Realtime[153]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:48:17 - RealtimeReconnect: Realtime ftp connection failed to connect after reinitialisation
2024-02-07 19:48:17 - RealtimeFTPLogin: Error connecting ftp - Object reference not set to an instance of an object.
2024-02-07 19:46:57 - Realtime[146]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:46:20 - FTP[142]: Upload of public_html/cumulusmx/realtimegauges.txt failed
2024-02-07 19:45:57 - Realtime[143]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:45:17 - Realtime[141]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:44:37 - Realtime[139]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:39:57 - Realtime[125]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:39:47 - FTP[123]: Upload of public_html/cumulusmx/realtimegauges.txt failed
2024-02-07 19:38:57 - Realtime[122]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:36:57 - Realtime[116]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:35:37 - Realtime[112]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 19:22:42 - LOOP: 9 - Expected data not received, expected 99 bytes, got 0
2024-02-07 19:21:02 - LOOP: 12 - Expected data not received, expected 99 bytes, got 0
2024-02-07 19:03:53 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 19:03:48 - LOOP: Timed out waiting for LOOP data
2024-02-07 19:03:45 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 19:03:40 - LOOP: Timed out waiting for LOOP data
2024-02-07 19:03:38 - LOOP: 5 - Expected data not received, expected 99 bytes, got 0
2024-02-07 19:03:31 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-02-07 19:02:39 - LOOP: 8 - Expected data not received, expected 99 bytes, got 0
2024-02-07 18:56:51 - LOOP: 14 - Expected data not received, expected 99 bytes, got 0
2024-02-07 18:35:15 - AWEKAS: Exception = A task was canceled.
2024-02-07 18:24:41 - LOOP: 9 - Expected data not received, expected 99 bytes, got 0
2024-02-07 18:20:15 - AWEKAS: Exception = A task was canceled.
2024-02-07 18:00:53 - WakeVP: *** Console Not woken
2024-02-07 17:25:15 - AWEKAS: Exception = A task was canceled.
2024-02-07 17:16:34 - Realtime[207]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 17:15:34 - Realtime[204]: Warning, a previous cycle is still processing local files. Skipping this interval.
2024-02-07 17:11:00 - *** Data input appears to have stopped
I haven't monitored but can't say it is temperature impacted. In my case WiFiLogger is doing many other uploads, and I have my Disconnect period at 20. It is intermittent and doesn't appear to affect live data other than during the Disconnect period.

I don't get those errors in my WLL to CMX and that comes from the same ISS.

Enjoy,
Paul
VP2+
C1 www.komokaweather.com/komokaweather-ca
MX https://komokaweather.com/cumulusmx/index.htm /index.html /index.php
MX https://komokaweather.com/cumulusmxwll/index.htm /index.html /index.php
MX https:// komokaweather.com/cumulusmx4/index.htm
Image
Top
picca
Posts: 22
Joined: Mon 02 Jan 2012 4:35 pm
Weather Station: Davis VP2
Operating System: Debian 11
Location: Valdisotto - Italy
Contact:
Contact picca

Re: LOOP: xx - Expected data not received, expected 99 bytes, got 0

Post by picca »

Hi, same problem for me with v. 4 beta.

Unfortunately with the beta version of CumulusMX 4 I started having this "error" in the log. No problem with v.3.
At the moment is sporadic (something like 3/4 times a day for a total of about 10 alerts/day).

Davis VP2 WL usb to Raspberry.

2024-03-27 22:29:11 - LOOP: 2 - Timed out waiting for LOOP data
2024-03-27 22:29:10 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-03-27 22:29:06 - LOOP: 38 - Timed out waiting for LOOP data
2024-03-27 22:29:05 - LOOP: 38 - Expected data not received, expected 99 bytes, got 0
Top
User avatar
mcrossley
Posts: 12774
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: LOOP: xx - Expected data not received, expected 99 bytes, got 0

Post by mcrossley »

picca wrote: ↑Wed 27 Mar 2024 11:56 pm Hi, same problem for me with v. 4 beta.

Unfortunately with the beta version of CumulusMX 4 I started having this "error" in the log. No problem with v.3.
At the moment is sporadic (something like 3/4 times a day for a total of about 10 alerts/day).

Davis VP2 WL usb to Raspberry.

2024-03-27 22:29:11 - LOOP: 2 - Timed out waiting for LOOP data
2024-03-27 22:29:10 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-03-27 22:29:06 - LOOP: 38 - Timed out waiting for LOOP data
2024-03-27 22:29:05 - LOOP: 38 - Expected data not received, expected 99 bytes, got 0
That looks pretty normal to me, those sorts of errors have always occurred. The VP2 console sometimes does not process serial commands whilst it is busy doing something else.
Top
User avatar
Dador
Posts: 202
Joined: Thu 24 Nov 2011 2:22 pm
Weather Station: Davis VP2 Plus & Ecowitt
Operating System: Windows 10
Location: Rybnik, Poland
Contact:
Contact Dador

Re: LOOP: xx - Expected data not received, expected 99 bytes, got 0

Post by Dador »

mcrossley wrote: ↑Thu 28 Mar 2024 10:57 am
picca wrote: ↑Wed 27 Mar 2024 11:56 pm Hi, same problem for me with v. 4 beta.

Unfortunately with the beta version of CumulusMX 4 I started having this "error" in the log. No problem with v.3.
At the moment is sporadic (something like 3/4 times a day for a total of about 10 alerts/day).

Davis VP2 WL usb to Raspberry.

2024-03-27 22:29:11 - LOOP: 2 - Timed out waiting for LOOP data
2024-03-27 22:29:10 - LOOP: 2 - Expected data not received, expected 99 bytes, got 0
2024-03-27 22:29:06 - LOOP: 38 - Timed out waiting for LOOP data
2024-03-27 22:29:05 - LOOP: 38 - Expected data not received, expected 99 bytes, got 0
That looks pretty normal to me, those sorts of errors have always occurred. The VP2 console sometimes does not process serial commands whilst it is busy doing something else.
Since the ability to preview current errors became available in CMX, I see the same ones almost every day. They are not worth attention if they occur sporadically. I also think this is a normal situation.
Top
Post Reply

Return to “Cumulus MX Current (releases since b3043)”