Request to Davis owners with USB loggers

[steve]

I am trying to test some code I have added to MX, but I have noticed an issue with reading data, which also occurs with the released code. I am having to test with just a console and my Windows 10 laptop, and a USB data logger, as that's all I have with me in the motorhome. Back at home, I had a Pi and a TCP/IP logger and didn't experience this issue.

I would like to know whether this is just a problem with my setup here, or something more widespread. So, if you are using MX with a Davis station and a USB logger could you please look in your MXdiags files to see whether or not you get frequent reports of "!!! loop data not received". Please post a reply in this thread stating

(a) whether or not you see these messages frequently
(b) what operating system you are using
(c) if you are using Linux or a Mac, what version of Mono you are using.

I think I have turned off all power saving.

Thanks.

[ConligWX]

Steve

I clear my MXDiags out every now and then and cant say I have seen this issue. checked 5 existing files but none have that report.

Debian 8.6 Jessie, Intel NUC

root@conligwx:~# mono -V
Mono JIT compiler version 4.6.2 (Stable 4.6.2.16/ac9e222 Tue Jan 3 11:48:26 UTC 2017)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
LLVM: supported, not enabled.
GC: sgen

[steve]

Thanks.

Mine seems to have stopped doing it now!

[ConligWX]

Searched about 30 other files from backups. none had that loop error at all.

[mcrossley]

Steve, I have a serial logger so not sure if it applies or this helps. I restarted Cumulus today, but the last log started 20th Dec and there are 20 loop data not received messages in there.

Quite a few occurred directly after setting the console time...

Code: Select all

2016-12-24 03:00:31.351 Setting console time
2016-12-24 03:00:31.461 Wait for ACK...
2016-12-24 03:00:31.470 ACK received
2016-12-24 03:00:31.470 Wait for ACK...
2016-12-24 03:00:31.476 ACK received
2016-12-24 03:00:53.686 !!! loop data not received
2016-12-24 03:00:53.686 Reading reception stats

Others occurred from single instances to a group of 9.

The last occurred like this...

Code: Select all

2017-01-07 22:40:00.782 WU Response: OK: success
2017-01-07 22:41:29.930 !!! loop data not received
2017-01-07 22:41:35.589 !!! No ack received in response to LPS 2 1
2017-01-07 22:41:41.199 !!! No ack received in response to LOOP 50
2017-01-07 22:41:46.809 !!! No ack received in response to LPS 2 1
2017-01-07 22:41:52.420 !!! No ack received in response to LOOP 50
2017-01-07 22:41:58.031 !!! No ack received in response to LPS 2 1
2017-01-07 22:42:03.658 !!! No ack received in response to LOOP 50
2017-01-07 22:42:09.317 !!! No ack received in response to LPS 2 1
2017-01-07 22:42:14.927 !!! No ack received in response to LOOP 50
2017-01-07 22:45:00.372 Writing log entry for 07/01/2017 22:45:00

[steve]

Thanks, Mark- yes, the same would apply to serial loggers. Mine seems to have settled down now, it was doing it on every read cycle previously, after receiving a couple of loop packets, but it has only done it once since I last posted. What I see here is that the first byte of the packet is received (the "L" character) and then it stops.

[steve]

I think the problem is that the console is trying to resync with the ISS, and I don't have one. The resync attempts are apparently interfering with sending LOOP packets.

[mcrossley]

Hmm, my console always has a zero re-sync count?

[steve]

Dunno - but when I start MX, the L in the bottom RH corner of the console changes to R (presumably the requests for data trigger the console to try to get some readings) and the sending of loop packets stops after one or two packets. After a few minutes, the R changes back to L again, and the loop transfers are fine from then on.

[BigOkie]

Is this the same thing I was asking about last month? I noticed that I don't see those messages if I turn debug logging off. I'll re-enable it because I know that I had this problem at least two times a week but it would settle down within 5 to 10 minutes.

EDIT: Nevermind, you don't need it enabled for it to log to the diags. I do have these in the content of my curreny MXDiags files (Pi3 Jessie):

Code: Select all

20170101-001152.txt:2017-01-01 03:43:41.345 !!! loop data not received
20170101-001152.txt:2017-01-01 03:44:02.360 !!! loop data not received
20170101-001152.txt:2017-01-01 03:44:23.475 !!! loop data not received
20170101-001152.txt:2017-01-01 03:44:44.489 !!! loop data not received
20170101-001152.txt:2017-01-01 03:45:05.504 !!! loop data not received
20170101-001152.txt:2017-01-03 09:45:05.984 !!! loop data not received
20170101-001152.txt:2017-01-03 09:45:27.199 !!! loop data not received
20170101-001152.txt:2017-01-03 09:45:48.213 !!! loop data not received
20170101-001152.txt:2017-01-04 23:08:02.029 !!! loop data not received
20170101-001152.txt:2017-01-07 20:01:37.348 !!! loop data not received
20170101-001152.txt:2017-01-08 04:20:44.428 !!! loop data not received
20170101-001152.txt:2017-01-08 04:21:05.443 !!! loop data not received
20170101-001152.txt:2017-01-08 05:52:51.192 !!! loop data not received
20170101-001152.txt:2017-01-08 05:53:12.207 !!! loop data not received
20170101-001152.txt:2017-01-08 07:31:19.094 !!! loop data not received
20170101-001152.txt:2017-01-08 07:31:40.214 !!! loop data not received
20170101-001152.txt:2017-01-08 07:32:01.229 !!! loop data not received
20170101-001152.txt:2017-01-08 07:32:22.342 !!! loop data not received
20170101-001152.txt:2017-01-11 09:25:26.672 !!! loop data not received
20170101-001152.txt:2017-01-11 09:25:47.688 !!! loop data not received
20170101-001152.txt:2017-01-11 09:26:08.704 !!! loop data not received
20170101-001152.txt:2017-01-11 09:26:29.818 !!! loop data not received
20170101-001152.txt:2017-01-11 09:26:50.831 !!! loop data not received
20170101-001152.txt:2017-01-13 13:30:55.050 !!! loop data not received
20170101-001152.txt:2017-01-13 13:31:16.065 !!! loop data not received
20170101-001152.txt:2017-01-13 13:31:37.180 !!! loop data not received
20170101-001152.txt:2017-01-13 13:31:58.193 !!! loop data not received

Code: Select all

root@wxserver:/home/pi/CumulusMX/MXdiags# mono -V
Mono JIT compiler version 4.0.5 (Stable 4.0.5.1/1d8d582 Thu Nov 12 12:22:41 UTC 2015)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
        TLS:           __thread
        SIGSEGV:       normal
        Notifications: epoll
        Architecture:  armel,vfp+hard
        Disabled:      none
        Misc:          softdebug
        LLVM:          supported, not enabled.
        GC:            sgen

[steve]

I had this problem at least two times a week but it would settle down within 5 to 10 minutes.

It seems to happen when the console is busy trying to do something else - specifically in my case (and perhaps yours) trying to (re)connect to the ISS.

[BigOkie]

I had this problem at least two times a week but it would settle down within 5 to 10 minutes.

It seems to happen when the console is busy trying to do something else - specifically in my case (and perhaps yours) trying to (re)connect to the ISS.

This is possible as I do average between 3 and 20 reconnects a day (usually it's closer to 20 the colder it is out). Wish I could catch the console in a resync (I know what to look for, just wish I had time to stare down the console LOL).

[kocher]

Greetings to all, Saludos a todos

Steve, I've never had that error message.

Davis station and a USB logger
CumulusMX build 3041
Windows 7 Professional
Davis Vantage Pro 2 Station

[jlmr731]

I just looked through about 10 log files and it is about 35 meg in total going back to the end of December.
2 or 3 files didnt have it at all and the rest had just a few and 1 file had a few multiple's in a row shown here

Code: Select all

2017-01-06 07:11:00.079 Writing log entry for 1/6/2017 7:11:00 AM
2017-01-06 07:11:00.080 Written log entry for 1/6/2017 7:11:00 AM
2017-01-06 07:11:00.080 Writing today.ini, LastUpdateTime = 1/6/2017 7:11:00 AM raindaystart = 0.32 rain counter = 0.32
2017-01-06 07:11:00.081 INSERT IGNORE INTO Monthly (LogDateTime,Temp,Humidity,Dewpoint,Windspeed,Windgust,Windbearing,RainRate,TodayRainSoFar,Pressure,Raincounter,InsideTemp,InsideHumidity,LatestWindGust,WindChill,HeatIndex,UVindex,SolarRad,Evapotrans,AnnualEvapTran,ApparentTemp,MaxSolarRad,HrsSunShine,CurrWindBearing,RG11rain,RainSinceMidnight,WindbearingSym,CurrWindBearingSym) Values('17-01-06 07:11',5.3,88,2.5,0.0,1.0,270,0.00,0.00,30.126,0.32,66.7,40,0.0,5.3,5.3,0.0,0,0.000,0.000,-0.9,0,0.0,261,0.00,0.00,'W','W')
2017-01-06 07:11:00.081 MySQL: 1 rows were affected.
2017-01-06 07:11:28.912 !!! loop data not received
2017-01-06 07:11:50.726 !!! loop data not received
2017-01-06 07:12:00.075 Writing log entry for 1/6/2017 7:12:00 AM
2017-01-06 07:12:00.075 Written log entry for 1/6/2017 7:12:00 AM
2017-01-06 07:12:00.076 Writing today.ini, LastUpdateTime = 1/6/2017 7:12:00 AM raindaystart = 0.32 rain counter = 0.32
2017-01-06 07:12:00.076 INSERT IGNORE INTO Monthly (LogDateTime,Temp,Humidity,Dewpoint,Windspeed,Windgust,Windbearing,RainRate,TodayRainSoFar,Pressure,Raincounter,InsideTemp,InsideHumidity,LatestWindGust,WindChill,HeatIndex,UVindex,SolarRad,Evapotrans,AnnualEvapTran,ApparentTemp,MaxSolarRad,HrsSunShine,CurrWindBearing,RG11rain,RainSinceMidnight,WindbearingSym,CurrWindBearingSym) Values('17-01-06 07:12',5.3,88,2.5,0.0,1.0,270,0.00,0.00,30.126,0.32,66.7,40,0.0,5.3,5.3,0.0,0,0.000,0.000,-0.9,0,0.0,261,0.00,0.00,'W','W')
2017-01-06 07:12:00.082 MySQL: 1 rows were affected.
2017-01-06 07:12:12.547 !!! loop data not received
2017-01-06 07:12:34.358 !!! loop data not received
2017-01-06 07:13:00.081 Writing log entry for 1/6/2017 7:13:00 AM
2017-01-06 07:13:00.081 Written log entry for 1/6/2017 7:13:00 AM
2017-01-06 07:13:00.082 Writing today.ini, LastUpdateTime = 1/6/2017 7:13:00 AM raindaystart = 0.32 rain counter = 0.32
2017-01-06 07:13:00.082 INSERT IGNORE INTO Monthly

On the other files it pretty much appears the same as above but only 1 instance and not the double like above.

Using davis vp2 with a meteobridge
MX running under linux connecting via tcp port to meteobridge

mono -V
Mono JIT compiler version 4.2.1 (Debian 4.2.1.102+dfsg2-7ubuntu4)

[Weerhaas]

Good morning.

I see it a few times last 10 days.

Using Windows 10 Home 32 bit
Vantage 2 Pro Plus

Using Cumulus and Cumulus MX.
Virtual VP 1.2.5
http://www.weerhaas.nl