meteohub.de

Wetterstation: Oregon Scientific WMR300
Meteobridge: TL-MR3020 (ohne USB-Hub)
RAM: 29364 kB insgesamt, 3228 kB frei (89% verwendet)
SW-Version: Meteobridge 3.5 (Jan 8 2018, build 11784), FW 1.4

Seit gestern übermittelt Meteobridge keine Winddaten mehr, weder zu Meteotemplate noch zu den anderen Diensten, auf der Konsole der Station ist alles in Ordnung, die Daten kommen an.

wnetd (09.01.2018 10:27:28): process started.
system (09.01.2018 10:27:28): start of logging process initiated.
logger (09.01.2018 10:27:28): historical data loaded (19 records).
logger (09.01.2018 10:27:28): data logger (version 5.0x, build 11784) started.
logger (09.01.2018 10:27:29): connect station 0 (WMR-300 via USB HID).
logger (09.01.2018 10:27:29): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (09.01.2018 10:27:29): services paused.
logger (09.01.2018 10:27:54): Bad wind0(0) sensor data, "chill x10" (-65513) out of range [-700:1500]
logger (09.01.2018 10:27:56): message above repeats 1 time.
logger (09.01.2018 10:27:56): Bad wind0(0) sensor data, "chill x10" (-65516) out of range [-700:1500]
logger (09.01.2018 10:27:58): message above repeats 1 time.
logger (09.01.2018 10:27:59): Bad wind0(0) sensor data, "chill x10" (-65513) out of range [-700:1500]
logger (09.01.2018 10:28:01): message above repeats 1 time.
logger (09.01.2018 10:28:01): Bad wind0(0) sensor data, "chill x10" (-65507) out of range [-700:1500]
logger (09.01.2018 10:28:03): message above repeats 1 time.
logger (09.01.2018 10:28:04): Bad wind0(0) sensor data, "chill x10" (-65504) out of range [-700:1500]
logger (09.01.2018 10:28:06): message above repeats 1 time.
logger (09.01.2018 10:28:06): Bad wind0(0) sensor data, "chill x10" (-65502) out of range [-700:1500]
logger (09.01.2018 10:28:11): message above repeats 3 times.
logger (09.01.2018 10:28:11): Bad wind0(0) sensor data, "chill x10" (-65507) out of range [-700:1500]
logger (09.01.2018 10:28:13): message above repeats 1 time.
logger (09.01.2018 10:28:14): Bad wind0(0) sensor data, "chill x10" (-65513) out of range [-700:1500]
logger (09.01.2018 10:28:16): message above repeats 1 time.
logger (09.01.2018 10:28:16): Bad wind0(0) sensor data, "chill x10" (-65504) out of range [-700:1500]
logger (09.01.2018 10:28:18): message above repeats 1 time.
logger (09.01.2018 10:28:19): Bad wind0(0) sensor data, "chill x10" (-65499) out of range [-700:1500]
logger (09.01.2018 10:28:21): message above repeats 1 time.
logger (09.01.2018 10:28:21): Bad wind0(0) sensor data, "chill x10" (-65490) out of range [-700:1500]
logger (09.01.2018 10:28:23): message above repeats 1 time.
logger (09.01.2018 10:28:24): Bad wind0(0) sensor data, "chill x10" (-65488) out of range [-700:1500]
logger (09.01.2018 10:28:26): message above repeats 1 time.
logger (09.01.2018 10:28:26): Bad wind0(0) sensor data, "chill x10" (-65490) out of range [-700:1500]
logger (09.01.2018 10:28:31): message above repeats 3 times.
logger (09.01.2018 10:28:31): Bad wind0(0) sensor data, "chill x10" (-65493) out of range [-700:1500]
logger (09.01.2018 10:28:33): message above repeats 1 time.
logger (09.01.2018 10:28:34): Bad wind0(0) sensor data, "chill x10" (-65499) out of range [-700:1500]

Kann ich hier bitte mal remote Zugang bekommen?
URL und Passwort bitte an "info@smartbedded.com"

Vorüberhend sollte das mit einem Fixieren auf Version 3.4 geheilt werden können.
Wir haben am WMR-300 Treiber Ändeurngen durchführen müssen, da er bei anderen WMR-300 Stationen Probleme machte. Scheint irgendwie knifflig zu sein. Daher würde es helfen zu verstehen, warum es jetzt bei dieser Station klemmt. Die andere Station läuft mit dem neuen Treiber wunderbar.

Hello Boris

I can confirm this problem I have exactly identical errors reported when using firmware 3.4 or 3.5 , I am now back on 3.3 and no errors have been reported since changing back to 3.3 since the 23td December.

this is exactly the same error reported "Bad wind0(0) sensor data, "chill x10" (-65516) out of range [-700:1500]"

when this error appeared I compared wind data on the console and the console was displaying wind data speed readings OK and direction was OK.

this is similar issue to what Sinan is trying to explain to you a few weeks ago.

hope it helps ...Brian

Update released last night does hopefully fix it. Please give this a try.

admin wrote: Wed Jan 10, 2018 9:08 am Update released last night does hopefully fix it. Please give this a try.

Ok no problem is that 3.5 reboot get latest ?

Ok all done will let you know how it goes many thanks brian..

ALL SEEMS good so far just one anomaly is the 60 min historical is not recorded so far uptime is 2 hours 30 minutes .

released January 10, 2018

fixes an freshly introduced bug in regard to handling negative wind chill temperatures for WMR-300 station
reduces pointless writing of same sensor values into internal storage every few seconds for wmr300 weather station. Now data in Meteobridge is only updated when sensor data has changed or 50 seconds have passed. By that storage consumption is reduced without compromising on tracking fast sensor data changes.


Boris since this release there is no 60 minute history data for the WMR300 under the live tab .

after first reboot 9 hours later no 60 minute history
rebooted twice and current uptime is 1 hour 23 minutes highlighted in bold below is the dashes alongside 60 min: --

History</b><br>&nbsp;&nbsp;2 min: 8.6°C 47.5°F<br>&nbsp;&nbsp;5 min: 8.6°C 47.5°F<br>10 min: 8.6°C 47.5°F<br>15 min: 8.6°C 47.5°F<br>30 min: 8.6°C 47.5°F<br>60 min: --')">

im only raising this has the template I use requires the 60 minute history value for trends

Brian

Thanks for raising this. I will have a look at it.

admin wrote: Thu Jan 11, 2018 1:01 am Thanks for raising this. I will have a look at it.

awesome Boris

Version 3.5
released January 11, 2018
further improvements on WMR-300 driver

that fixed it many thanks ..Brian

where do you get the latest fimware for the MB ?

it is loaded automatically when you reboot the Meteobridge.

Paul Gee wrote: Thu Jan 11, 2018 11:07 pm where do you get the latest fimware for the MB ?

On re-boot controlled by the Maintenance>Version Control drop down box on the System tab

right, it needs to be set to "newest".