actual_sol0_radiation_rel tag missing on some MH systems

[wvdkuil]

In some systems runnig the Meteohub software the actual_sol0_radiation_rel value is missing.
Same systems (Alix) same ISS (VP2+ all) same location (my backyard).

I found this because one of the users for the Leuven-Template is complaining that his sol% is always zero and my website displays a nice % during the day.

I have two alix meteohub's listening to the same ISS, one using an envoy/WLIP, the other one a console/usb logger.
When using the ip-address with the :5558 port the output displayed is different as actual_sol0_radiation_rel is missing from 1 of the two meteohubs.
The meteohub with '4.9v b7019' displays that tag, the version '4.9W ??' and '4.9z b7082' does not. And all other sol0_radiation tags are there on both meteohub:5558 outputs.

Here a write-up of all parameters and the results

Code: Select all

Meteohub station-Leuven  listening to an ISS using Envoy/WLIP port 22222

$ws['wsVersion']			= '4.9z b7082';

$ws['solarAct']				= '[actual_sol0_radiation_wqm:0]';
$ws['solarAct']				= '176.0';

$ws['solActPerc']			= '[actual_sol0_radiation_rel:0]';
$ws['solActPerc']			= '0';

checking all data via ip-address : 5558
======================================
actual_th15_cloudheight_ft 6680
actual_uv0_index 1.1
actual_sol0_radiation_wqm 197.0
actual_sol0_evapotranspiration_inch 0.070
actual_sol0_evapotranspiration_mm 1.78

There are 32 sol0_radiation measurements in the 5558 output including 1 actual_sol0_radiation_rel 
=====
Meteohub station-Wilsele using an VP2 console and an usb logger

$ws['wsVersion']			= '4.9v b7019';

$ws['solarAct']				= '[actual_sol0_radiation_wqm:0]';
$ws['solarAct']				= '176.0';

$ws['solActPerc']			= '[actual_sol0_radiation_rel:0]';
$ws['solActPerc']			= '19';


checking all data via ip-address : 5558
======================================
actual_th15_cloudheight_ft 6680
actual_uv0_index 0.8
actual_sol0_radiation_wqm 149.0
actual_sol0_radiation_rel 21
actual_sol0_evapotranspiration_inch 0.067
actual_sol0_evapotranspiration_mm 1.70

The   actual_sol0_radiation_rel   is not displayed, nowhere in the output.
There are 31 sol0_radiation measurements in the 5558 output but none sol0_radiation_rel

I hope someone has a clue,

Wim

[YJB]

Hi Wim,

Most likely you have an issue in one of the following files on MH:

clientraw.conf
clientrawdaily.conf
clientrawextra.conf
clientrawhour.conf

since you are using actual_* I guess it is /home/meteohub/clientraw.conf.

Keep in mind that the entire file is a single line; you can edit it manually, but keep a copy to be safe. Also, a MH update will "revert" a manual change.

Probably best to post the "wrong"values" so that Boris can fix this manually. On the other hand it could be as simple as a mistake on the ""WD Live" and "Meteoware Live" Support" page where the "solar" field is not configured correctly (this is where the clientraw.conf gets build from).

Ysbrand

[wvdkuil]

Hi Wim,

Most likely you have an issue in one of the following files on MH:

clientraw.conf
clientrawdaily.conf
clientrawextra.conf
clientrawhour.conf

since you are using actual_* I guess it is /home/meteohub/clientraw.conf.

Keep in mind that the entire file is a single line; you can edit it manually, but keep a copy to be safe. Also, a MH update will "revert" a manual change.

Probably best to post the "wrong"values" so that Boris can fix this manually. On the other hand it could be as simple as a mistake on the ""WD Live" and "Meteoware Live" Support" page where the "solar" field is not configured correctly (this is where the clientraw.conf gets build from).

Ysbrand

Hello Ysbrand,
I see no differences on the "WD Live" and "Meteoware Live" Support page, only the one has dutch as a native language, the other one english.

The other files you are referring to are way above my head. Never heard of them. Search the pdf-manual, no clue.
The tags I am using for my users are as I understood normal tags as described in the manuals and the sol% tag is available at least since since 2008. Why is it available one time and not another?

Question: What files should I post so Boris can look into them
Question:Where do i find those clientraw???.conf files

Wim

[YJB]

Hi Wim,

The files are on meteohub located in /home/meteohub. You will need to use root access to get to these files.

I guess that Boris would like to see the clientraw.conf from a "goog" setup and also a copy of one that doesn't work as expected.

If this is way above your head, I guess that the only option left is to ask Boris to log in remotely and have a look himself.

Ysbrand

[wvdkuil]

Hi Wim,

The files are on meteohub located in /home/meteohub. You will need to use root access to get to these files.

I guess that Boris would like to see the clientraw.conf from a "goog" setup and also a copy of one that doesn't work as expected.

If this is way above your head, I guess that the only option left is to ask Boris to log in remotely and have a look himself.

Ysbrand

Thanks,
The two one-line files are not identical.
I posted them here, a zip with the two files.

Wim

[wvdkuil]

I checked every setting on all Meteohub tags. Made them identical if possible. Language (both Dutch now), Sensors, Data Export, WD/MW live all the same settings on both Meteohubs. I did not update the version v to z as this station uploads my "production" data and I do not want to lose the actual_sol0_radiation_rel % for my site.

EDIT:
I started a third Meteohub on a raspberry with version z.
Works like a charm. The actual_sol0_radiation_rel is there and displayed. In Wd-Live, in all-tags and in 5558.
So it is not a z version problem
==============

I can not see any setting more to set or check. The actual_sol0_radiation_rel tag is still missing from one meteohub in all output.
I attached the two outputs of :5558 as a text file.
There are some remarks:
1. The sequence of the tags in the output differs. So in one file it is th1 then th10, other file th10 is always at another place.
2. The number of lines in the file are not the same. The one missing the sol tag is missing others also.
Wim

[wvdkuil]

Hi Wim,

Most likely you have an issue in one of the following files on MH:

clientraw.conf
clientrawdaily.conf
clientrawextra.conf
clientrawhour.conf

since you are using actual_* I guess it is /home/meteohub/clientraw.conf.

Keep in mind that the entire file is a single line; you can edit it manually, but keep a copy to be safe. Also, a MH update will "revert" a manual change.

Probably best to post the "wrong"values" so that Boris can fix this manually. On the other hand it could be as simple as a mistake on the ""WD Live" and "Meteoware Live" Support" page where the "solar" field is not configured correctly (this is where the clientraw.conf gets build from).

Ysbrand

Hello Ysbrand,
I compared the two files and the tag is the same and on the same place in both conf files.
[actual_date0_min_local:-] 0 [actual_sol0_radiation_rel:-] [actual_date0_day_local:-]
The output on the built in WD-live display is different. One system displays the correct value, the other one a minus sign as is specified in the .conf file.

So also in generating the clientraw.txt the [actual_sol0_radiation_rel:-] tag is NOT processed and gets the default value from Meteohub in one system while the other system works correct.

One important difference between the output for this conf and all other output:
The clientraw.conf generated output gets the - for the tag value.
In the :5558 output the complete line with the tagname is missing, as is in the all-sensors files.

You pointed me to the template file (*.conf) for the clientraw files. Is there a template/conf file also for the all-sensors.txt and all-sensors.xml?

Thanks, Wim

[admin]

In order to print out that tag Meteohub needs
1) A solar sensor (Vantage) detected and getting recent data from it
2) Station longitude and Latitude set, as this determines maximum possible radiation which is needed to compute a relative percentage.

[wvdkuil]

In order to print out that tag Meteohub needs
1) A solar sensor (Vantage) detected and getting recent data from it
2) Station longitude and Latitude set, as this determines maximum possible radiation which is needed to compute a relative percentage.

And off course these are set and identical to the settings of the same alix which reports this value. The ntp server and those settings are identical also.
The sensors are already in the first screenshot. Wilsele has the tag, Leuven has not. both have a solar sensor and both report the solar w/m2.
The only difference on the settings page is that Wilsele is uploading to Meteoplug. Leuven not. But the raspberry is not either. And the rapsberry one reports the actual_sol0_radiation_rel tag correctly.

All three Meteohubs listen to the same ISS with UV and solar sensor. The values on the sensor page are the same (522 W/qm), the last signal time differs (24 sec / 34 sec) but that is for all sensors and is normal.

Wim

[wvdkuil]

I put the following screenshots on-line
http://www.weerstation-leuven.be/sol-rel/lat-lon.jpg
The latitude and longitude are the same
I even checked for spaces or unprintable characters

http://www.weerstation-leuven.be/sol-rel/sensors.jpg
Sensors are identical anbd reporting correct data

http://www.weerstation-leuven.be/sol-rel/wdlive.jpg
The wdlive display shows the - for the missing tag.

Wim

[wvdkuil]

Ok, I think I found something.

I removed the WLIP ip and port address from the weatherstation defenition and "piggy-backed" the Leuven Meteohub to the Wilsele Meteohub by chosing TCP/IP meteohub and the correct ip address, without changing anything in sensors ar any other setting.

After a few seconds the data from the other Meteohub was coming in, AND immidiatly the solar data on the WD-Live page appeared. Also the port 5558 is showing the tag and its value.

Maybe it has something to do with receiving data from the Envoy/WLIP?
Although it is reporting the exact same solar values, something else must be different.

I will try to find a spare console to feed the Leuven Meteohub.

EDIT: A spare console will take some time.
But the Meteostick works OK and displays the correct value for solar% in WDLive and the :5558 output.
EDIT 18:06 It is foorball time Belgium is playing. the wife loves football so I have time to check things out.
Replaced the envoy with a console. After removing the meteostick weatherstation and adding the WLIP again, the WD Live and the :5558 display correct: actual_sol0_radiation_rel 38

Found anotherweatherstation with Envoy/WLIP and a functioning solar sensor.
And that in combination with Meteohub also has no actual_sol0_radiation_rel tag.

So for one reason or another
An Envoy + WLIP+ solar ==> Meteohub: results in a missing actual_sol0_radiation_rel tag.

Switching the Envoy for a console but keeping the rest results in the availabillity of the tag and the correct value for that tag.

I checked the Envoy/WLIP with WeatherLink also,here is the log part of the wlip in an envoy, the firmware is 1.90

Code: Select all

logger (17.06.2014 17:24:01): data logger (version 4.9z, build 7082) started.
logger (17.06.2014 17:24:02): connect station 0 (Vantage via TCP/IP).
logger (17.06.2014 17:24:02): connect station 1 (System Data via Plug-in).
logger (17.06.2014 17:24:02): station 0 (Vantage), wakeup sent.
logger (17.06.2014 17:24:02): station 0 (Vantage), internal logger activated.
logger (17.06.2014 17:24:02): station 0 (Vantage), syncing.
logger (17.06.2014 17:24:12): station 0 (Vantage), gettime request sent.
logger (17.06.2014 17:24:13): station 0 (Vantage), time offset of Vantage: -1 minutes
logger (17.06.2014 17:24:13): station 0 (Vantage), eeprom request sent.
logger (17.06.2014 17:24:14): station 0 (Vantage), rain collector size 0.2 mm per tick.
logger (17.06.2014 17:24:14): station 0 (Vantage), transmitter 1 active as station type (#0) "ISS".
logger (17.06.2014 17:24:14): station 0 (Vantage), transmitter 2 active as station type (#1) "Temperature Only" mapped to "t1".
logger (17.06.2014 17:24:14): station 0 (Vantage), transmitter 3 active as station type (#8) "Soil/Leaf".
logger (17.06.2014 17:24:14): station 0 (Vantage), firmware version request sent.
logger (17.06.2014 17:24:14): station 0 (Vantage), firmware version 1.90
logger (17.06.2014 17:24:14): station 0 (Vantage), no reading of Vantage's internal logger as data gap is less than 10 minutes: 32 secs

The firmaware for the console is 1.82, here the complete log listing:

Code: Select all

logger (17.06.2014 18:03:33): data logger (version 4.9z, build 7082) started.
logger (17.06.2014 18:03:33): connect station 0 (Vantage via TCP/IP).
logger (17.06.2014 18:03:33): connect station 1 (System Data via Plug-in).
logger (17.06.2014 18:03:34): station 0 (Vantage), wakeup sent.
logger (17.06.2014 18:03:35): station 0 (Vantage), internal logger activated.
logger (17.06.2014 18:03:35): station 0 (Vantage), syncing.
logger (17.06.2014 18:03:45): station 0 (Vantage), gettime request sent.
logger (17.06.2014 18:03:46): station 0 (Vantage), time offset of Vantage: -111 minutes
logger (17.06.2014 18:03:46): station 0 (Vantage), eeprom request sent.
logger (17.06.2014 18:03:47): station 0 (Vantage), rain collector size 0.2 mm per tick.
logger (17.06.2014 18:03:47): station 0 (Vantage), transmitter 1 active as station type (#0) "ISS".
logger (17.06.2014 18:03:47): station 0 (Vantage), transmitter 2 active as station type (#1) "Temperature Only" mapped to "t1".
logger (17.06.2014 18:03:47): station 0 (Vantage), transmitter 3 active as station type (#8) "Soil/Leaf".
logger (17.06.2014 18:03:47): station 0 (Vantage), firmware version request sent.
logger (17.06.2014 18:03:47): station 0 (Vantage), firmware version 1.82
logger (17.06.2014 18:03:47): station 0 (Vantage), no reading of Vantage's internal logger as data gap is less than 10 minutes: 65 secs

I will drive to the location with the other Envoy/WLIP tomorrow to check the logs there.

Wim

[admin]

Checked the code and found a bug, that depends on order of sensor ID definition. Will be fixed with next update.

[wvdkuil]

Checked the code and found a bug, that depends on order of sensor ID definition. Will be fixed with next update.

THANKS,

Wim