WMR88 - No data from outdoor sensor

[Kenneth Edwall]

Hi!

I must say you have done a great job with the weewx software, its easy to set up and use + highly customizable!

Unfortunately I am having some problems getting data from my outdoor sensor(THGN800) that comes with the WMR88 device. I seem to be getting OK data from the wind and rain sensor. 

The values that are not displayed(N/A) are:

- Outside Temp

- Wind Chill

- Heat Index

- Dewpoint

- Humidity

NOTE: I get data on the "Barometer" values, and the outside temp is visible on the display on the WMR88.

Here is the "/var/log/syslog":

ug  9 18:26:20 raspberrypi weewx[2774]: wmrx: Bad USB report received.

Aug  9 18:26:20 raspberrypi weewx[2774]: ***** Connection timed out

Aug  9 18:26:40 raspberrypi weewx[2774]: wmrx: Bad USB report received.

Aug  9 18:26:40 raspberrypi weewx[2774]: ***** Connection timed out

Aug  9 18:27:17 raspberrypi weewx[2774]: wmrx: Bad USB report received.

Aug  9 18:27:17 raspberrypi weewx[2774]: ***** Connection timed out

Aug  9 18:27:37 raspberrypi weewx[2774]: wmrx: Bad USB report received.

Aug  9 18:27:37 raspberrypi weewx[2774]: ***** Connection timed out

Aug  9 18:28:16 raspberrypi weewx[2774]: wmrx: Bad USB report received.

Aug  9 18:28:16 raspberrypi weewx[2774]: ***** Connection timed out

Aug  9 18:28:36 raspberrypi weewx[2774]: wmrx: Bad USB report received.

Aug  9 18:28:36 raspberrypi weewx[2774]: ***** Connection timed out

Aug  9 18:29:16 raspberrypi weewx[2774]: wmrx: Bad USB report received.

Aug  9 18:29:16 raspberrypi weewx[2774]: ***** Connection timed out

Aug  9 18:29:38 raspberrypi weewx[2774]: wmrx: Bad USB report received.

Aug  9 18:29:38 raspberrypi weewx[2774]: ***** Connection timed out

Aug  9 18:30:16 raspberrypi weewx[2774]: wmrx: Bad USB report received.

Aug  9 18:30:16 raspberrypi weewx[2774]: ***** Connection timed out

Aug  9 18:30:36 raspberrypi weewx[2774]: wmrx: Bad USB report received.

Aug  9 18:30:36 raspberrypi weewx[2774]: ***** Connection timed out

Aug  9 18:30:46 raspberrypi weewx[2774]: Archive: added archive record 2013-08-09 18:30:00 UTC (1376073000)

Aug  9 18:30:46 raspberrypi weewx[2774]: reportengine: Running reports for latest time in the database.

Aug  9 18:30:46 raspberrypi weewx[2774]: reportengine: Running report StandardReport

Aug  9 18:30:46 raspberrypi weewx[2774]: reportengine: Found configuration file /etc/weewx/skins/Standard/skin.conf for report StandardReport

Aug  9 18:30:46 raspberrypi weewx[2774]: stats: Schema exists with 16 elements

Aug  9 18:30:47 raspberrypi weewx[2774]: filegenerator: generated 1 'SummaryByMonth' files in 0.51 seconds

Aug  9 18:30:49 raspberrypi weewx[2774]: filegenerator: generated 1 'SummaryByYear' files in 2.65 seconds

Aug  9 18:30:52 raspberrypi weewx[2774]: filegenerator: generated 12 'toDate' files in 2.96 seconds

Aug  9 18:30:56 raspberrypi weewx[2774]: genimages: Generated 11 images in 3.39 seconds

Aug  9 18:30:56 raspberrypi weewx[2774]: reportengine: copied 0 files to /var/www/weewx

Aug  9 18:30:56 raspberrypi weewx[2774]: reportengine: Running report FTP

Aug  9 18:30:56 raspberrypi weewx[2774]: reportengine: Found configuration file /etc/weewx/skins/Ftp/skin.conf for report FTP

Aug  9 18:30:56 raspberrypi weewx[2774]: reportengine: FTP upload not requested. Skipped.

Aug  9 18:30:56 raspberrypi weewx[2774]: reportengine: Running report RSYNC

Aug  9 18:30:56 raspberrypi weewx[2774]: reportengine: Found configuration file /etc/weewx/skins/Rsync/skin.conf for report RSYNC

Aug  9 18:30:56 raspberrypi weewx[2774]: reportengine: rsync upload not requested. Skipped.

Aug  9 18:31:16 raspberrypi weewx[2774]: wmrx: Bad USB report received.

Aug  9 18:31:16 raspberrypi weewx[2774]: ***** Connection timed out

So there may be an USB communication issue, but wouldn't I have issues with all sensors then?

Thanks in advance for any assistance!

Regards,

Kenneth Edwall 

[Kenneth Edwall]

Additional debugs:

Aug  9 22:03:06 raspberrypi weewx[2743]: ***** tuple index out of range

Aug  9 22:03:11 raspberrypi weewx[2743]: wmrx: Bad checksum on buffer of length 19

Aug  9 22:03:26 raspberrypi weewx[2743]: wmrx: Bad USB report received.

Aug  9 22:03:26 raspberrypi weewx[2743]: ***** Connection timed out

Aug  9 22:03:38 raspberrypi weewx[2743]: wmrx: Bad checksum on buffer of length 3

Regards,

Kenneth

[Kenneth Edwall]

Yep, there is definitely something strange with the USB communication. Tried WView and it appears to be working fine(but I did not like the skin so I moved back to Weewx).

Now the scenario is different, I do not get any "Barometer" data but the outside temp data is populated. And I still keep getting errors in the "syslog". Could it be something with the WMR100 driver not being 100% compatible with the WMR88 I have?

Syslog:

Aug 10 09:36:07 raspberrypi weewx[2681]: wmrx: Bad USB report received.

Aug 10 09:36:07 raspberrypi weewx[2681]: ***** Connection timed out

Aug 10 09:36:12 raspberrypi weewx[2681]: wmrx: Exception while calculating checksum.

Aug 10 09:36:12 raspberrypi weewx[2681]: ****  reduce() of empty sequence with no initial value

Aug 10 09:36:12 raspberrypi weewx[2681]: wmrx: Bad checksum on buffer of length 4

Aug 10 09:36:12 raspberrypi weewx[2681]: wmrx: Bad USB report received.

Aug 10 09:36:12 raspberrypi weewx[2681]: ***** tuple index out of range

Aug 10 09:36:17 raspberrypi weewx[2681]: wmrx: Bad checksum on buffer of length 13

Aug 10 09:36:23 raspberrypi weewx[2681]: wmrx: Bad checksum on buffer of length 3

Aug 10 09:36:39 raspberrypi weewx[2681]: wmrx: Bad USB report received.

Aug 10 09:36:39 raspberrypi weewx[2681]: ***** Connection timed out

Aug 10 09:36:59 raspberrypi weewx[2681]: wmrx: Bad USB report received.

Aug 10 09:36:59 raspberrypi weewx[2681]: ***** Connection timed out

Regards,

Kenneth Edwall

[Thomas Keffer]

Hi, Kenneth

Thanks for your kind words.

Unfortunately, I'm on the road right now, so it might be a bit before I get a chance to take a look at this.

-tk
Fat-fingered from my Android phone

--
You received this message because you are subscribed to the Google Groups "Weewx user's group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Per Edström]

Might not be related but I have had some serious problems with a mini-PC that I tried to connect with WMR88. It seems that the USB-port och that specific PC is blocking out the 433MHz-comminucation with some sensors (my guess). I my case the outdoor sensor but my friend had problem with the wind sensor. We have tried a USB-hub in between hoping that is would filter the signal and we have tried multiple ferrite cores bust not improvement. The WMR88 works fine with a laptop or stand-alone but not with this mini-PC. I had plans on taking it to a EMC-lab to verify that there are some issue with the USB-port but instead I got the WMR200 that seems to work a lot better.

When the WMR88 looses sync I get "--" in the display as if the sensor was gone. I have to do a new search for the WMR88 to find the sensor again. Quite annouying..

Have you experienced something similar?

[Kenneth Edwall]

Interesting theory, I did have strange behavior with the weather station(-- in the display from time to time). The thing is that it has been running fine now since last night(hw: rasp pi rev.B) with the WView application. I wonder if the USB driver is the same?

One thing I noticed was that plugging in external power to the WMR88 display seems to have made things more stable when it comes to the "--" behavior

Thanks.

Kenneth

[Thomas Keffer]

Hi, Kenneth

Unfortunately, I am still on the road, so I cannot offer much right now.

It is possible that there are some small WMR88 / WMR100 differences that are accounting for your problems. On the other hand, I think there are some users that are running the WMR88 without any problems (anyone?)

The driver that wview uses is completely different from the weewx driver. It's possible that wview is doing something a little different, accounting for the stability you are getting. Definitely worth looking in to on my part.

-tk

--

You received this message because you are subscribed to the Google Groups "Weewx user's group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

Tom Keffer

kef...@threefools.org
+1 541-386-8891 (h)
+1 541-490-9507 (c)

Skype: tkeffer

[Per Edström]

Hello again!

My theory is that the CPU is at 933MHz on my mini-PC (http://www.lohelectronics.se/ebox-3350mx-p-897.html) and that half that tone, or the 480MHz on USB 2.0, is making life difficult för the 433MHz-sensor communication circuits on the WMR88, thus blocking the sensor out.
Having said that, I connected my WMR88 to the eBox3350 yesterday but I put the sensor just next to the main unit. So far they have maintained contact. Will move the sensors a few meters and see if it fails then. Maybe also try to clock-down the CPU and see if that makes any difference. It's not too busy anyway..

Also when I had the WMR88 as stand-alone there was problems with temporary loss of communication. It was very sensitive on position and line-of-sight to sensors so maybe the radio-design in WMR88 is crap or sensitive to interference from other stuff (e-smog)?

[Christian]

Hi,
I`m running this setup: WMR88, raspi rev. b, wheezy. Had no problems during the installation and the software is running for ten days now. Sometimes the station looses the connection to an sensor, but on my setup it seems to be the distance between sensor an base and the connection gets back soon. Neither the driver nor the raspi itself seems to have a problem.

[Kenneth Edwall]

Im back :) Have been running Wview for a while now and have had no problems what so ever with the communication towards the WMR88 and the sensors. I didn't like the software though(and i like weewx!!), and thats the reason I am back.

Still having the same problem unfortunately, running the latest version. Other people seems to be getting it to work with Weewx and WMR88, not sure what differs for me really?

Anyway I can debug this further on my end(other then debug=1)?

Thanks,

Kenneth