I finally set up a web page, now the dupes are fixed and data is very close to live. Please check out the solar scaling to see if we can tone it down to stay in the graph. Already up to 7160 w/m2 today.
I also have a problem with the extreme conditions reset at 0 hour during startup. It does not reset unless you are live during the 0 hour. Is it possible to have it reset close to the proper time during startup data downloads??
Also check the heading on the 24hr graph. This graph is current, not 7/4/2004.
try a new 10.13x, ready now, to fix the max solar reading problem
as for the midnight reset being missed…i will have to investigate/test that…and see why
what does the time entries in the log file, 72004lg.txt, look like?
If you still have problems, you might have issues with the sensor itself. Does your console show the correct value? and it s the software that is different?
If both are a bit odd, ad that value you quote is very high, then I would say it might be a sensor issue.
there must be calculation of the radiation level bug in wd
a new 10.13x, beta, ready now, will now have the max solar radiation reading go to the max reading that comes in…
so you can see if and when the reading jumps up (and at what point), maybe,…
Looking at the graph it still pegs at 2402 w/m2 and has gotten real sluggish on the one minuet updates. I like it better the way it was and look into the calc or rescaling. Looking at the VP/UV Solar graph it tapers up to 7000+ w/m2 with out any real jumps. It will go between 5000 and 7000 during the day.
Check my link for screen shots.
I found this formula in the online manual for the 2510 console. Is this the one you are using?
Brightness sensor
The brightness is transferred as a 3-digit BCD value (0-999) and a 2-bit factor. (*1, *10, *100, *1000) in lux. This yields a range of values from 0 to 200,000 lux.
L29 Brightn. in lux b3-b0 = 1 (0-9)
H29 Brightn. in lux b7-b4 = 10 (0-9)
L30 Brightn. in lux b3-b0 = 100 (0-9)
H30 Factor b5-b4 = Factor (0=*1; 1=*10; 2=*100; 3=*1000)
b6 = Sunshine flag;
b7 = New flag;
Pyranometer
The irradiation effect is transferred as a 3-digit BCD value (0-999) and a 2-bit factor (*1, *10, *100, *1000) in 1/10 W/m+. This yields a range of values from 0 to 99,900.0 W/m+.
L31 Effect in W/m+ b3-b0 = 1 (0-9)
H31 Effect in W/m+ b7-b4 = 10 (0-9)
L32 Effect in W/m+ b3-b0 = 100 (0-9)
H32 Factor b5-b4 = Factor (0=*1; 1=*10; 2=*100; 3=*1000)
b7 = New flag;
The new flag reveals whether the sensor data has been received again in the time period between the reception of this data record and of the last data record. If this flag is not in place, this means that the value is equal to twice that of the previous data record.
i have used that info
but i must have it calculating wrong
its winter here, so i dont have very high values
but i will have to get the raw values from you to work with that
re the rescaling issue. i changed that back in 10.14b, ready now
re the time/log issue from the data extraction, thanks for the email and the info…i will use that to see what is going wrong
but its sunday night here, and i need a break.
so tomorrow morning i should be able to have a look
I have my sensor up on the roof to get the clearest view of the sun. here are the raw readings for Sunday morning, which it is hear now. Hard to get use to your being almost a day in time ahead of me. The German stations reading look the way I would like to see mine, but there readings are much lower. Full scale of WD the graph is 1500 wm/2.
My raw readings so far for today (Sunday) are: 24, 104, 200, 362, 515, 944, 1479, and 1822. Sunrise was at 6 and it is 9:15 now. I will update you mid day.
Yesterday after the morning startup it varied between 2250 to a high of 7628.
Re data startup extraction issues: It looks like it is skipping the first record also, this puts it 15 minuets behind when live data starts. The day skipping and or 0 hour reset also affect some of the graphs. The solar hours add together and show 48 hours of daylight. Temp/windspeed/rain graph skips days or has used two days of data for the high.
in the solar setup, it will show you what the max reading should be for the time of day and your lat/long
also check that , at the brightest part of the day
It’s noon now and the raw was 24, 104, 200, 362, 515, 944, 1479, 1822, 2089, 4966, 3064, 3201, 3703, 4161, 4609, 5070, 5379, 5676, and 6605.
The graph seems to autochange the values since the cursor reports 6605 for all pegged one and higher on the lower ones. 24 changed to 456.
As far as the real time graph, it shows raw values.
In solar setup it shows 6605 / 100% / and 1199 for max reading. I have the update from max reading ticked. Does this mean the graph should be using 1199 in place of 6605?
ok, 1199 is the max solar radiation you would expect for your location for the time of year
the fact you are getting 7000+means 2 things:
a problem in wd with the data
or a faulty sensor
was does the software that comes with the station show?
The software that comes with the station just reports LUX and hours of daylight using over 20k lux as a reference. I didn’t know it had a Pyranometer until I saw it in the manual above and WD was using the reading. Is anyone else out there reporting high raw readings with the 2510 solar sensor??? Maybe not many being used yet. The formula above looks complex. If you still think it is the sensor I could email the lacrosse tech and see if they even use that reading.
A scale would be great, I could run it at about .18 and get proper results. Looking at the data there are no big jumps. See above it is very consistant and progressive. I could not find any web sites using a 2500 to compair to. If it were a WD error it would be a consistant calculating higher error which someone else should have reported.
Thanks for letting me know the LUX setting entered into the w/m2 calculations. I increased my default of 20,000 to 120,000 and am now getting proper w/m2 readings for my long and lat (1100-1300 w/m2). As you can see from my link starting at noon.
Would it be possible to connect the half scale on graph setup to work with the w/m2 also (just does the % now). This would put my graph down where I would like to have it and still have realistic readings.
Can anyone tell me if your max solar reading at a given long and lat and time is just bright sun. Can it be exceeded on a given day or is it up to. I am trying to figure out how to really zero this in to being real.
hi
the half scale applies to solar %, but the ws2500 is plotting actual wm/2
so i would need to have it so you can have the wm/2 scale as shown as half scale too
OR, set the max lux value 2x higher than you have it now, in the ws2010/ws2500 data setup…
re the sunshine hours not being reset from data from the data extract overnight at midnight, i think i have found the reason…its because it was looking for minute=1, but there is no minute =1 if the data is only every 15 minutes
and the day jumping ahead 1, i have a put a check in for that too
in a new 10.15, uploading now
I think it would be beneficial to everyone to have the half scale do both w/m2 and %. If I double my LUX setting, my w/m2 reading would become half and un-realistic.
This would give everyone the opportunity to keep their solar graph in the lower half or full screen.