Page 1 of 2

CMX and <#wdirdata>

Posted: Fri 20 Jan 2017 11:56 am
by mcrossley
Steve,

I just noticed something odd about the wind direction array supplied by MX. Here is a snippet...

Code: Select all

...156,7,169,169,187,195,7,7,160,160,156,156,7,173,173,173,179,7,188,188,183,187,7,7,196,179,171,171,7,159,159,169,173,7,7,171,168,171,171,7,171,171,171,171,7,176,176,175,175,175,172,7,7,169,169,169,169,7,153,153,153,153,7,153,153,150,180,7,7,137,141,149,149,7,146,146,155,171,7,7,172,172,176,176,7,176,183,183,183,7,184,184,159,157,7,7,145,149,149,149,149,149,7,149,149,149,156,7,156,156,157,157,7,7,180,178,178,178,7,164,157,157,157,7,7,171,171,171,171,7,171,167,167,167,7,172,172,172,172,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,7,165,7,7,7,148,113,113,7,101,101,101,101,7,7,101,101,101,101,7,105,105,105,105,7,105,105,105,105,7,7,126,126,126,128,128,128,7,148,148,148,148,7,178,178,178,200,7,7,179,191,214,214,7,195,187,187,194,7,195,195,196,188,188,7,146,161,161,167,7,179,179,178,160,7,7,7,7,7,7,168,7,7,7,7,168,168,7,7,168,168,168,7,7,7,168,168,7,7,7,168,168,168,7,7,7,7,168,7,7,7,7,7,168,168,7,7,7,168,168,168,168,168,168,7,7,168,168,168,7,7,7,168,168,168,7,7,168,168,168,7,7,7,7,168,7,7,7,7,168,168,7,7,168,168,168,7,7,7,7,168,168,168,7,7,7,168,168,168,7,7,7,7,168,7,168,168,168,168,168,7,168,168,168,168,7,168,168,168,168,7,7,7,168,168,168,7,7,7,7,168,7,7,7,7,168,7,7,7,168,168,168,168,168,7,7,168,168,168,7,168,168,168,168,7,7,168,168,168,168,7,168,168,168,168,7,7,168,168,168,168,7,168,168,168,168,7,168,168,168,168,7,7,168,168,168,168,7...
Those "7" direction values are not appearing in console, the CMX display, or the SS Gauges. Maybe something awry with the array creation?

Re: CMX and <#wdirdata>

Posted: Fri 20 Jan 2017 12:00 pm
by mcrossley
They seem "roughly" correspond with "0.0" entries in the wind speed array (but not always), so maybe they should be "0" as well - but I do not have "Use bearing zero when calm" enabled.

Edit: I take that back, the "7" values do correspond to zero wind speed. So two issues..
1. CMX is using 7 instead of zero.
2. It doesn't appear to honouring the "Use bearing zero when calm" setting.

Re: CMX and <#wdirdata>

Posted: Fri 20 Jan 2017 12:24 pm
by mcrossley
Actually, comparing the values in the wind speed array with the values in CMX/console. I think that data is very suspect too!

Re: CMX and <#wdirdata>

Posted: Fri 20 Jan 2017 2:58 pm
by steve
I'll look at the code. Are you using any calibration settings for wind speed and/or direction?

Re: CMX and <#wdirdata>

Posted: Fri 20 Jan 2017 3:49 pm
by mcrossley
No calibration settings for anything.

Re: CMX and <#wdirdata>

Posted: Fri 20 Jan 2017 4:09 pm
by mcrossley
Steve, it may or may not be related, but since I upgraded to 3042 I'm getting the following error in my tag file...

Code: Select all

System.ArgumentOutOfRangeException: Cannot be negative, and should not exceed length of string.
Parameter name: startIndex
  at System.String.IndexOf (System.String value, Int32 startIndex, Int32 count) [0x00000] in <filename unknown>:0 
  at System.String.IndexOf (System.String value, Int32 startIndex) [0x00000] in <filename unknown>:0 
  at CumulusMX.TokenParser.Parse2 () [0x00000] in <filename unknown>:0 
  at CumulusMX.TokenParser.ToString () [0x00000] in <filename unknown>:0 
The diags file has this:

Code: Select all

Web tag error
Exception: i=2031 len=2090
inputText.Length=6745
token=px soli
System.ArgumentOutOfRangeException: Argument is out of range.
Parameter name: index
  at CumulusMX.Cumulus.TokenParserOnToken (System.String strToken, System.String& strReplacement) [0x00000] in <filename unknown>:0 
  at CumulusMX.TokenParser.Parse2 () [0x00000] in <filename unknown>:0 
Any clues?

Re: CMX and <#wdirdata>

Posted: Fri 20 Jan 2017 4:41 pm
by mcrossley
I restarted MX 3042 and so far no more errors - I had two of those web tag errors, the second caused logging interval file (the one with the error) to stop being processed at all, the realtime file was still processed and uploaded OK.

After this latest restart the wind direction and speed arrays also seem to be now working correctly, and obeying the "use zero for calm" setting! :? :groan:

Re: CMX and <#wdirdata>

Posted: Fri 20 Jan 2017 4:47 pm
by richard_newberry
was it behaving correctly on version 3041??

Re: CMX and <#wdirdata>

Posted: Fri 20 Jan 2017 4:55 pm
by steve
Mark, I can't see anything with the winddir and windspd code, it's just translated from the Cumulus 1 code. The values that go in are the same ones that go into the 'Latest' and 'Bearing' values and tags.

That token parsing error is interesting - a few people seem to be seeing similar things. Because I've changed development platforms, it's not easy for me see exactly what changed in 3042, but I don't think the token parsing code has changed for a long time. The only thing I know for certain that I changed in this area was to make the realtimegauges.txt file be processed without it needing to be an extra file. I did that change rather hurriedly, so perhaps I've done something to make it interfere with the 'normal interval' processing when it happens at the same time.

Edit: Yes, I've re-used the same token parser instance, so there's a clash when 'normal' happens at the same time as 'realtime'. I don't think that can explain the first thing you were seeing, though. I'll get a fix out asap.

Re: CMX and <#wdirdata>

Posted: Fri 20 Jan 2017 5:59 pm
by mcrossley
richard_newberry wrote:was it behaving correctly on version 3041??
I don't know. I only spotted it today because I fired up my Instromet page for the first time in a long time - that uses the wind array data to fill in the gaps between my real-time uploads to the web server.

Re: CMX and <#wdirdata>

Posted: Fri 20 Jan 2017 10:46 pm
by mcrossley
B3043 seems to have fixed the web tags issue - thanks Steve.
The wind arrays continue to behave themselves now.

Re: CMX and <#wdirdata>

Posted: Sun 22 Jan 2017 6:45 pm
by mcrossley
Steve, a bit more information about those "7" values for the direction.

They are being generated when the console loses contact with my transmitter.
Or when my relay device was accidentally sending a "wind sensor not connected" radio message periodically :oops: :roll: The cause of all those values in the wind array!

Tonight the console was not receiving any data for a period of time when I reprogrammed by relay. During this time the console went into resync mode and all the values dashed out waiting for a transmitter. MX dislayed zero for all values except the current wind direction which stuck at "7" rather than the expected zero.

Is there something in the protocol handler that isn't right? It is easy for me to reproduce now I know how if you want additional diags.

The Loop and Loop2 packets are supposed to use "0" direction for "no sensor"

Re: CMX and <#wdirdata>

Posted: Sun 22 Jan 2017 6:55 pm
by steve
It makes much more sense that it affects more than jjust the wdirdata web tag as the values in that are the same as used elsewhere. If you have data logging turned on, that will show the raw loop data, so we can see exactly what's in there. I should actually have this myself as I have no ISS within range - I'll have a look at mine and also look at the code.

Re: CMX and <#wdirdata>

Posted: Sun 22 Jan 2017 7:10 pm
by steve
With no ISS, I am getting FF for wind speed and average wind speed, and 7FFF for wind direction. MX detects the wind speeds as out of range and prints this in the diags file:

Ignoring wind speeds. Speed=255 mph, Avg=255 mph.

Because it ignores the wind speed, it also ignores the direction. Presumably on your system the wind speeds are not out of range for some reason, so the data does get processed. As part of applying the offset, it does a 'mod 360' on the direction. 7FFF = 32767 and 32767 MOD 360 is 7, which is where your value is coming from.

Re: CMX and <#wdirdata>

Posted: Sun 22 Jan 2017 7:30 pm
by mcrossley
OK, I switched on data logging and reset the console to receive from a non-existent station.

The MX "Dashboard" display showed "7" on the direction gauge.

Here is a the diag file covering the last bit of valid data, then switching to a non-existent station...

You can see from the last insert into the realtime database, that it is sending a "7" there too.

Code: Select all

2017-01-22 19:20:44.303 Data 37: 4C-4F-4F-14-00-11-09-60-76-A4-02-33-6B-01-00-00-DA-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5A-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-A2-3D
2017-01-22 19:20:46.315 Data 38: 4C-4F-4F-14-00-11-09-60-76-A4-02-33-6B-01-00-00-DA-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5A-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-A2-3D
2017-01-22 19:20:48.413 Data 39: 4C-4F-4F-14-00-11-09-60-76-A4-02-33-6B-01-00-00-FF-7F-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5A-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-C0-09
2017-01-22 19:20:50.426 Data 40: 4C-4F-4F-14-00-11-09-60-76-A4-02-33-6B-01-00-00-FF-7F-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5A-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-C0-09
2017-01-22 19:20:52.688 Data 41: 4C-4F-4F-14-00-11-09-60-76-A4-02-33-6B-01-00-00-DA-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5A-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-A2-3D
2017-01-22 19:20:54.451 Data 42: 4C-4F-4F-14-00-11-09-60-76-A4-02-33-6B-01-00-00-DA-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5A-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-A2-3D
2017-01-22 19:20:56.464 Data 43: 4C-4F-4F-14-00-11-09-60-76-A4-02-33-6B-01-00-00-DA-00-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5A-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-A2-3D
2017-01-22 19:20:58.476 Data 44: 4C-4F-4F-14-00-11-09-60-76-A4-02-33-6B-01-00-00-FF-7F-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-5A-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-C0-09
2017-01-22 19:21:00.605 INSERT IGNORE INTO realtime (LogDateTime,temp,hum,dew,wspeed,wlatest,bearing,rrate,rfall,press,currentwdir,beaufortnumber,windunit,tempunitnodeg,pressunit,rainunit,windrun,presstrendval,rmonth,ryear,rfallY,intemp,inhum,wchill,temptrend,tempTH,TtempTH,tempTL,TtempTL,windTM,TwindTM,wgustTM,TwgustTM,pressTH,TpressTH,pressTL,TpressTL,version,build,wgust,heatindex,humidex,UV,ET,SolarRad,avgbearing,rhour,forecastnumber,isdaylight,SensorContactLost,wdir,cloudbasevalue,cloudbaseunit,apptemp,SunshineHours,CurrentSolarMax,IsSunny,IsSunUp) VALUES ('2017-01-22 19:21:00',2.4,90,0.9,0.0,0.0,7,0.0,0.2,1026.21,'N',0,'mph','C','hPa','mm','61.3',0.33,38.0,38.0,0.2,19.8,51,2.4,'-0.1',3.3,'00:00',-0.5,'03:03',7.0,'08:42',13.0,'08:42',1026.28,'19:04',1023.74,'04:28','3.0.0','3043',0.0,2.4,0.5,0.0,0.15,0,0,0.0,1,'0',0,'N',602,'ft',0.5,0.0,0,'0','0');
2017-01-22 19:21:00.639 MySQL: 1 rows were affected.
2017-01-22 19:21:03.241 !!! loop data not received, bytes received = 0
2017-01-22 19:21:07.349 !!! Not woken
2017-01-22 19:21:07.350 Sending command LPS 2 1 - pass 1
2017-01-22 19:21:07.850 Wait for ACK
2017-01-22 19:21:07.851 Sending command LPS 2 1 - pass 2
2017-01-22 19:21:08.352 Wait for ACK
2017-01-22 19:21:08.352 Sending command LPS 2 1 - pass 3
2017-01-22 19:21:08.853 Wait for ACK
2017-01-22 19:21:08.853 !!! No ack received in response to LPS 2 1
2017-01-22 19:21:12.963 !!! Not woken
2017-01-22 19:21:12.963 Sending command LOOP 50 - pass 1
2017-01-22 19:21:13.464 Wait for ACK
2017-01-22 19:21:13.465 Sending command LOOP 50 - pass 2
2017-01-22 19:21:13.965 Wait for ACK
2017-01-22 19:21:13.966 Sending command LOOP 50 - pass 3
2017-01-22 19:21:14.466 Wait for ACK
2017-01-22 19:21:14.467 !!! No ack received in response to LOOP 50
2017-01-22 19:21:18.575 !!! Not woken
2017-01-22 19:21:18.576 Sending command LPS 2 1 - pass 1
2017-01-22 19:21:19.077 Wait for ACK
2017-01-22 19:21:19.077 Sending command LPS 2 1 - pass 2
2017-01-22 19:21:19.578 Wait for ACK
2017-01-22 19:21:19.579 Sending command LPS 2 1 - pass 3
2017-01-22 19:21:20.079 Wait for ACK
2017-01-22 19:21:20.080 ACK received
2017-01-22 19:21:20.181 Sending command LOOP 50 - pass 1
2017-01-22 19:21:20.682 Wait for ACK
2017-01-22 19:21:20.682 ACK received
2017-01-22 19:21:20.683 Data 1: 4C-4F-4F-14-00-11-09-00-00-A4-02-34-FF-7F-FF-FF-FF-7F-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-00-00-FF-FF-7F-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-C0-41
2017-01-22 19:21:20.684 Ignoring wind speeds. Speed=255 mph, Avg=255 mph.
2017-01-22 19:21:20.685 Data 2: 4C-4F-4F-14-00-11-09-00-00-A4-02-34-FF-7F-FF-FF-FF-7F-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-00-00-FF-FF-7F-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-C0-41
2017-01-22 19:21:20.686 Ignoring wind speeds. Speed=255 mph, Avg=255 mph.
2017-01-22 19:21:25.464 !!! loop data not received, bytes received = 0
2017-01-22 19:21:25.565 Sending command LPS 2 1 - pass 1
2017-01-22 19:21:26.066 Wait for ACK
2017-01-22 19:21:26.067 ACK received
2017-01-22 19:21:26.067 Loop2: 4C-4F-4F-14-01-FF-7F-60-76-A4-02-34-FF-7F-FF-FF-FF-7F-FF-7F-FF-7F-FF-00-FF-FF-FF-7F-FF-7F-FF-00-FF-FF-FF-FF-00-FF-00-FF-00-00-00-FF-FF-7F-00-00-FF-FF-01-00-00-00-00-00-08-00-01-00-02-1D-00-FF-FF-3E-75-5B-75-55-76-FF-01-0D-15-0C-0C-06-12-12-16-04-04-FF-7F-FF-7F-FF-7F-FF-7F-FF-7F-FF-7F-0A-0D-17-56
2017-01-22 19:21:26.068 Ignoring LOOP2 wind speed: 255 mph
2017-01-22 19:21:26.169 Sending command LOOP 50 - pass 1
2017-01-22 19:21:26.670 Wait for ACK
2017-01-22 19:21:26.670 ACK received
2017-01-22 19:21:26.671 Data 1: 4C-4F-4F-14-00-11-09-60-76-A4-02-34-FF-7F-FF-FF-FF-7F-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-00-00-FF-FF-7F-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-9E-E4
2017-01-22 19:21:26.672 Ignoring wind speeds. Speed=255 mph, Avg=255 mph.
2017-01-22 19:21:29.215 OnConnect From : 192.168.1.8:56445
2017-01-22 19:21:29.222 Connected From : 192.168.1.8:56445
2017-01-22 19:21:31.489 !!! loop data not received, bytes received = 0
2017-01-22 19:21:31.590 Sending command LPS 2 1 - pass 1
2017-01-22 19:21:32.091 Wait for ACK
2017-01-22 19:21:32.091 ACK received
2017-01-22 19:21:32.092 Loop2: 4C-4F-4F-14-01-FF-7F-60-76-A4-02-34-FF-7F-FF-FF-FF-7F-FF-7F-FF-7F-FF-00-FF-FF-FF-7F-FF-7F-FF-00-FF-FF-FF-FF-00-FF-00-FF-00-00-00-FF-FF-7F-00-00-FF-FF-01-00-00-00-00-00-08-00-01-00-02-1D-00-FF-FF-3E-75-5B-75-55-76-FF-01-0D-15-0C-0C-06-12-12-16-04-04-FF-7F-FF-7F-FF-7F-FF-7F-FF-7F-FF-7F-0A-0D-17-56
2017-01-22 19:21:32.092 Ignoring LOOP2 wind speed: 255 mph
2017-01-22 19:21:32.193 Sending command LOOP 50 - pass 1
2017-01-22 19:21:32.694 Wait for ACK
2017-01-22 19:21:32.695 ACK received
2017-01-22 19:21:32.696 Data 1: 4C-4F-4F-14-00-11-09-60-76-A4-02-34-FF-7F-FF-FF-FF-7F-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-00-00-FF-FF-7F-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-9E-E4
2017-01-22 19:21:32.697 Ignoring wind speeds. Speed=255 mph, Avg=255 mph.
2017-01-22 19:21:37.451 !!! loop data not received, bytes received = 0
2017-01-22 19:21:37.552 Sending command LPS 2 1 - pass 1
2017-01-22 19:21:38.053 Wait for ACK
2017-01-22 19:21:38.054 ACK received
2017-01-22 19:21:38.054 Loop2: 4C-4F-4F-14-01-FF-7F-60-76-A4-02-34-FF-7F-FF-FF-FF-7F-FF-7F-FF-7F-FF-00-FF-FF-FF-7F-FF-7F-FF-00-FF-FF-FF-FF-00-FF-00-FF-00-00-00-FF-FF-7F-00-00-FF-FF-01-00-00-00-00-00-08-00-01-00-02-1D-00-FF-FF-3E-75-5B-75-55-76-FF-01-0D-15-0C-0C-06-12-12-16-04-04-FF-7F-FF-7F-FF-7F-FF-7F-FF-7F-FF-7F-0A-0D-17-56
2017-01-22 19:21:38.055 Ignoring LOOP2 wind speed: 255 mph
2017-01-22 19:21:38.156 Sending command LOOP 50 - pass 1
2017-01-22 19:21:38.657 Wait for ACK
2017-01-22 19:21:38.657 ACK received
2017-01-22 19:21:38.658 Data 1: 4C-4F-4F-14-00-11-09-60-76-A4-02-34-FF-7F-FF-FF-FF-7F-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-00-00-FF-FF-7F-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-9E-E4
2017-01-22 19:21:38.659 Ignoring wind speeds. Speed=255 mph, Avg=255 mph.
2017-01-22 19:21:38.660 Data 2: 4C-4F-4F-14-00-11-09-60-76-A4-02-34-FF-7F-FF-FF-FF-7F-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-00-00-FF-FF-7F-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-9E-E4
2017-01-22 19:21:38.661 Ignoring wind speeds. Speed=255 mph, Avg=255 mph.
2017-01-22 19:21:40.413 Data 3: 4C-4F-4F-14-00-11-09-60-76-A4-02-34-FF-7F-FF-FF-FF-7F-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-00-00-FF-FF-7F-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-9E-E4
2017-01-22 19:21:40.414 Ignoring wind speeds. Speed=255 mph, Avg=255 mph.

...

2017-01-22 19:22:00.325 Ignoring wind speeds. Speed=255 mph, Avg=255 mph.
2017-01-22 19:22:00.326 Data 3: 4C-4F-4F-14-00-11-09-00-00-A7-02-34-FF-7F-FF-FF-FF-7F-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-FF-00-00-FF-FF-7F-00-00-FF-FF-01-00-A3-00-A3-00-08-00-19-00-19-00-FF-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-2B-03-06-09-26-03-61-06-0A-0D-36-F0
2017-01-22 19:22:00.327 Ignoring wind speeds. Speed=255 mph, Avg=255 mph.
2017-01-22 19:22:00.662 INSERT IGNORE INTO realtime (LogDateTime,temp,hum,dew,wspeed,wlatest,bearing,rrate,rfall,press,currentwdir,beaufortnumber,windunit,tempunitnodeg,pressunit,rainunit,windrun,presstrendval,rmonth,ryear,rfallY,intemp,inhum,wchill,temptrend,tempTH,TtempTH,tempTL,TtempTL,windTM,TwindTM,wgustTM,TwgustTM,pressTH,TpressTH,pressTL,TpressTL,version,build,wgust,heatindex,humidex,UV,ET,SolarRad,avgbearing,rhour,forecastnumber,isdaylight,SensorContactLost,wdir,cloudbasevalue,cloudbaseunit,apptemp,SunshineHours,CurrentSolarMax,IsSunny,IsSunUp) VALUES ('2017-01-22 19:22:00',2.4,90,0.9,0.0,0.0,7,0.0,0.2,1026.21,'N',0,'mph','C','hPa','mm','61.3',0.33,38.0,38.0,0.2,19.9,52,2.4,'-0.1',3.3,'00:00',-0.5,'03:03',7.0,'08:42',13.0,'08:42',1026.28,'19:04',1023.74,'04:28','3.0.0','3043',0.0,2.4,0.5,0.0,0.15,0,0,0.0,1,'0',0,'N',602,'ft',0.5,0.0,0,'0','0');