Is this the wh-3080 usual error?

[xayide]

My WH-3080 started doing odd thing with solar radiation yesterday. It doesn't lockup but it goes to 13253w/m2. It came to the same value two morning in row. First morning it stayed there for 1,5 hours between 9 and 10:30....today it started at 7:45 and stayed to 11:30.....after that it went down to the normal w/m2 of around 200-400w/m2 following the green curve C MX plotted from max solar.

What could be the cause for this odd behaviour?

[steve]

Well... it may be a bug in MX. What does the console show when this happens?

[xayide]

I will have a look tomorrow when it happens again. This actually started about 4 days after i started using MX. But I see no correlation at all. Although I check tomorrow.

[AllyCat]

Hi,

You should be able to read the log within the Console at any time. Just press the "History" button and then the <down arrow> repeatedly to see earlier times. There's no point in Steve looking for a bug if the Console is wrong!

A value of 13000 w/m2 (say 1600 kLux) is larger than the FO specification and probably of the wirless protocol packets. Actually it seems to be almost exactly 24 bits (3 bytes) of which the FO max spec (400 kLux) normally uses the lower 22 bits.

Also, the UV data seems to be working in steps of ~0.33 unit, but the FO Solar Pod reports only integer values. Are you sure there aren't any "bad" calibration factors set in Cumulus?

Cheers, Alan.

[xayide]

I got to the same conclusion. Since 13253 / 0.0079 is around 16,7 million. Which is a 24 bit value as u say.
I had a look on the console and it says "--" for the time of the error. I also looked in the mxdiags and other logs...this is what I found...
Actually while I had the console in my hand browsing through history it happened again. So I guess this is due to wireless reception of the console maybe? As soon as I put the console back it started working again......

This is in the datalog just when I took it off the shelf to hold it in my hand while browsing history....Maybe I should try to extend the range with an antenna of sorts......

Code: Select all

12/03/15;15:01;9.9;36;-4.5;1.8;4.4;18;0.0;0.0;1036.2;18.3;22.7;28;1.7;9.3;9.9;1.0;402;0.00;0.00;6.1;260;8.2;45;0.0;0.0
12/03/15;15:02;1.6;67;-3.9;1.6;4.4;17;0.0;0.0;1036.5;18.3;22.8;28;1.0;-0.1;1.6;1.0;13253;0.00;0.00;-2.0;258;8.2;180;0.0;0.0
12/03/15;15:03;5.5;55;-2.8;1.7;4.4;10;0.0;0.0;1036.2;18.3;22.3;55;3.1;4.3;5.5;0.7;265;0.00;0.00;2.0;256;8.3;360;0.0;0.0

This is MXDiags just before it started and onto the error:

Code: Select all

2015-03-12 08:22:00.821 Writing today.ini, LastUpdateTime = 12/03/2015 08:22:00 raindaystart = 18.3 rain counter = 18.3
Latest reading: 1D84: 00 1C E3 00 46 05 00 EC 27 0A 11 00 08 3D 00 00
2015-03-12 08:23:00.578 Writing log entry for 12/03/2015 08:23:00
2015-03-12 08:23:00.578 Written log entry for 12/03/2015 08:23:00
2015-03-12 08:23:00.578 Writing today.ini, LastUpdateTime = 12/03/2015 08:23:00 raindaystart = 18.3 rain counter = 18.3
Latest reading: 1D98: 00 1C E3 00 46 05 00 EC 27 0A 11 00 08 3D 00 00
2015-03-12 08:23:32.470 Sensor contact lost; ignoring outdoor data
2015-03-12 08:23:42.490 Sensor contact lost; ignoring outdoor data
2015-03-12 08:23:52.494 Sensor contact lost; ignoring outdoor data
2015-03-12 08:24:00.850 Writing log entry for 12/03/2015 08:24:00
2015-03-12 08:24:00.850 Written log entry for 12/03/2015 08:24:00
2015-03-12 08:24:00.850 Writing today.ini, LastUpdateTime = 12/03/2015 08:24:00 raindaystart = 18.3 rain counter = 18.3

This is the log from data:

Code: Select all

12/03/15;08:14;-0.7;77;-4.2;1.0;1.7;180;0.0;0.0;1037.0;18.3;22.7;28;1.7;-0.7;-0.7;0.3;108;0.00;0.00;-3.9;115;1.6;180;0.0;0.0
12/03/15;08:15;-0.7;77;-4.2;1.0;1.7;180;0.0;0.0;1037.0;18.3;22.7;28;1.7;-0.7;-0.7;0.3;108;0.00;0.00;-3.9;117;1.6;180;0.0;0.0
12/03/15;08:16;-0.7;77;-4.2;1.0;1.7;180;0.0;0.0;1037.0;18.3;22.7;28;1.7;-0.7;-0.7;0.3;108;0.00;0.00;-3.9;119;1.6;180;0.0;0.0
12/03/15;08:17;-0.7;77;-4.2;1.0;1.7;180;0.0;0.0;1037.0;18.3;22.7;28;1.7;-0.7;-0.7;0.3;13253;0.00;0.00;-3.9;121;1.6;180;0.0;0.0
12/03/15;08:18;-0.7;77;-4.2;1.0;1.7;180;0.0;0.0;1037.0;18.3;22.7;28;1.7;-0.7;-0.7;0.3;13253;0.00;0.00;-3.9;123;1.6;180;0.0;0.0
12/03/15;08:19;-0.7;77;-4.2;1.0;1.7;180;0.0;0.0;1037.0;18.3;22.7;28;1.7;-0.7;-0.7;0.3;13253;0.00;0.00;-3.9;125;1.7;180;0.0;0.0
12/03/15;08:20;-0.7;77;-4.2;1.0;1.7;180;0.0;0.0;1036.9;18.3;22.7;28;1.7;-0.7;-0.7;0.3;13253;0.00;0.00;-3.9;127;1.7;180;0.0;0.0
12/03/15;08:21;-0.7;77;-4.2;1.0;1.7;180;0.0;0.0;1036.9;18.3;22.7;28;1.7;-0.7;-0.7;0.3;13253;0.00;0.00;-3.9;129;1.7;180;0.0;0.0

[xayide]

Actually, problem ceased to appear this morning. Seems the 10 inch movement of the console solved it. It is now close up to a wall with the display facing the direction of the transmitter. Odd since the cable-antenna seems to be on the back of the console. Maybe I had it put in a radiowave cancelation spot. At least works now.