Page 1 of 2
WD-live and VP2 bugs ** solved **
Posted: Wed Jul 30, 2008 10:46 am
by wfpost
Yesterday I switched from the Oregon WMR-100 to a VP2.
Worked flawless, but a few things are not working in connection with WDL:
No value for
Cloudbase
Wrong values for
Dew point
UV-I
Solar (shows the W/m² value in %)
Any chance to fix this with the next update?
Cheers,
___
Screenshots (click to enlarge!)

Re:WD-live and VP2 bugs
Posted: Wed Jul 30, 2008 6:38 pm
by wfpost
UV_I comes up with the date around 3PM until midnight :huh:
Until than it shows values, but they have nothing to do with what the sensors reporting.

Re:WD-live and VP2 bugs
Posted: Wed Jul 30, 2008 7:25 pm
by admin
Cloudbase should be ok with 2.6b. Please press "save" on the "WD-Live" page of Meteohub, to generate a modified template for generation of the data. After that the changes compared to the previous version will be applied. To give some detail on how this works...
a) Meteohub generates template files for the 4 clientraw files based on the sensors selected on the "WD-live page" by pressing "save". These templates are named "/public/graphs/clientraw*.out"
b) Meteohub then takes these templates and replaces the variables by the current values by the built-in hmtl-template replace mechanism. This is controlled by the settings on the "graph upload" page, where a schedule for each type of clientraw file can be defined
c) resulting "clientraw*.txt" files are then uploaded the usual way.
If this also fixes UV-I indexes and dew-point I cannot say for sure. Please report on that.
Solar is just available in Wqm. Any idea how to compute percent values from that?
Re:WD-live and VP2 bugs
Posted: Wed Jul 30, 2008 7:50 pm
by skyewright
admin wrote:a) Meteohub generates template files for the 4 clientraw files based on the sensors selected on the "WD-live page" by pressing "save". These templates are named "/public/graphs/clientraw*.out"
Does that perhaps only happen if the CRON job is set up?
I have 2.6b.
I have pressed Save on the WDL page (more than once).
I don't have the clientraw CRON job set.
There are no clientraw*.out templates in "/public/graphs/".
Re:WD-live and VP2 bugs
Posted: Wed Jul 30, 2008 8:06 pm
by admin
ah, I mixed up with the coming update 2.6c ;-)
Errata:
a) "clientraw*.conf" files are at "/home/meteohub/" so you need ssh access to inspect these. However, shouldn't be necessary any time, but I wanted to let you know if you might try debugging yourself.
b) schedules for the generation of the four wd-live files will be part of the next update.
Re:WD-live and VP2 bugs
Posted: Wed Jul 30, 2008 8:53 pm
by wfpost
admin wrote:Cloudbase should be ok with 2.6b. Please press "save" on the "WD-Live" page of Meteohub, to generate a modified template for generation of the data. After that the changes compared to the previous version will be applied.
I tried that before, but it didn´t solve the issue.
Even if I remove the UV-I from WD-live settings page, press save and then look at what shows up at the applet, it now still shows only current date. If I reset WD-Live with UV-I enabled nothing changes, neither UV-I nor cloudbase working.
I attach the files you mentioned from /home/meteohub [file name=clientraw.zip size=5207]
http://www.meteohub.de/joomla/images/fb ... entraw.zip[/file]
Re:WD-live and VP2 bugs
Posted: Wed Jul 30, 2008 9:58 pm
by skyewright
admin wrote:b) schedules for the generation of the four wd-live files will be part of the next update.
Sounds excellent. Thank you. I look forward to trying that. :)
Re:WD-live and VP2 bugs
Posted: Wed Jul 30, 2008 11:06 pm
by wfpost
admin wrote:
Solar is just available in Wqm. Any idea how to compute percent values from that?
My problem is this.
It doesn´t matter what option for the solar scale I set with the wdlconfig tag. It always shows W/m² in percentage. The values are correct, but the unit % doesn´t fit.
So, if using Option 1 from below, applet shows
NaNW/m² (and no value)
<instSolar>
<x>150</x>
<y>262</y>
<show>1</show>
<size>100</size>
<url></url>
<title></title>
<options>1</options>
</instSolar>
---
Same effect for Option 5, which I want to use:
applet displays:
NaNW/m² (and no value)
<instSolar>
<x>150</x>
<y>262</y>
<show>1</show>
<size>100</size>
<url></url>
<title></title>
<options>5</options>
</instSolar>
WDL manual>>
___
Description Solar Bar
Tag <instSolar>
Instrument options None
Notes Enter 0 – 9 in the <options>
tag for the following
combination of bar styles and
values:
For options 0 – 4 the Solar bar
will be displayed in percent
along with -
0. Percent.
1. W/m2 value.
2. Percent and W/m2 value
3. Percent and W/m2 value and
sunshine hours
4. As above but different order
For options 5 – 8 the Solar bar
will be displayed in W/m2
along with -
5. W/m2.
6. Percent value.
7. W/m2 and Percent value
8. Percent and W/m2 value and
sunshine hours
9. As above but different order
Re:WD-live and VP2 bugs
Posted: Thu Jul 31, 2008 1:08 am
by wfpost
Boris, I found out what´s the reason for it:
In the clientraw.txt the forecast parameter is written erroneously without underlines between the words.
The sensor variable is:
actual_thb0_fc_text Mostly_clear_with_little_temperature_change.
But parsed into clientraw.txt is this
Mostly clear with little temperature change.
With the spaces after every word that is interpreted as a new value. So every correct entry position is moved on because of this.
If I enter the underlines manually into the clientraw.txt all values are correctly displayed:
Mostly_clear_with_little_ temperature_change.
I guess, the reason I´m using an American VP2 cabled version isn´t a problem. Otherwise any meteohub/US Version user would have the same trouble.
Re:WD-live and VP2 bugs
Posted: Thu Jul 31, 2008 5:31 pm
by wfpost
In
clientraw.conf I replaced [actual_thb0_fc_text:_]
with
[actual_thb0_fc_wdlive:_] to virtually block creating the wrong fc_text entry which because of the missing underlines leads to every word with the forecast text identified as value and changing the given order.
Now UV-I, Solar and Dew Point show up correctly on WDL >>
So, what needs to be fixed, is this:
[actual_thb0_fc_text:_] must write the forecast text with underlines and no spaces between the words into clientraw.txt

Re:WD-live and VP2 bugs
Posted: Thu Jul 31, 2008 6:21 pm
by wfpost
admin wrote:
Solar is just available in Wqm. Any idea how to compute percent values from that?
Solar Radiation is summed up in the so-called
Solar constant
"It is measured by satellite to be roughly 1366 watts per square meter (W/m²)"
That value isn´t used for transfering Solar Radiation given in W/m² into percent.
From all I read this formula is
1000W/m² = 100%
I would be more interesting, if you could implement the algorithm allowing to calculate the Sun hours from the Solar Radiation and send this value to WDL, because the tooltip for Solar in WDL is only showing Sun hours. So without that numbers available for WDL its graph stays with zeros only :(
What do you think about it, Boris? Too much work to implement?
Would it be helpful, if a put together "the maths" for that?
Cheers,
Re:WD-live and VP2 bugs
Posted: Thu Jul 31, 2008 8:57 pm
by admin
Underscore bug will be solved with next update. The html-template variables will be enables to take text as-is, without switching these into spaces. This can be done by adding a "&" and the end of the variable name. Here: [actual_thb0_fc_text&]
Will be part of 2.6c.
Re:WD-live and VP2 bugs
Posted: Thu Jul 31, 2008 9:00 pm
by admin
if have found some math for computing maximal solar radiation based on latitude, and day of the year... I will give this a try in one of the next updates.
todo list is growing ;-)
Re:WD-live and VP2 bugs
Posted: Sat Aug 02, 2008 10:43 am
by admin
Solar radiation in percent is implemented in 2.6d
Re:WD-live and VP2 bugs
Posted: Sat Aug 02, 2008 7:51 pm
by skyewright
admin wrote:a) Meteohub generates template files for the 4 clientraw files based on the sensors selected on the "WD-live page" by pressing "save". These templates are named "/public/graphs/clientraw*.out"
Now using 2.6e.
I have set up a CRON job for upload on clientraw.txt (but with a different upload name) and that is resulting in a file on the server. :)
but still no clientraw*.out templates in "/public/graphs/"...
(though I think I briefly saw a zero byte clientraw.out there)