ook-decoder icon indicating copy to clipboard operation
ook-decoder copied to clipboard

Not getting data

Open slothbag opened this issue 10 years ago • 4 comments

Hi, thanks for writing this app, was just what I was looking for.

I have an rtlsdr sitting alongside the WH1080 weather station receiver, running ookd it detects 1 sometimes 2 bursts of about 28 bytes every 15 seconds thereabouts.

wh1080 (software) is receiving those bursts but says it cannot decode because the highs & lows are outside a normal tolerance.

Any idea whats happening?

slothbag avatar Mar 01 '14 14:03 slothbag

I'm glad you are finding ook-dump potentially useful, lets see if we can make it actually useful.

The description sounds like either a different protocol than what I've seen from a WH1080, or a bunch of noise bits somehow stuck to the packet. I see an 11 byte message every time.

First, can you run ook-dump, which runs just like wh1080, capture a few minutes of output, and add it to this issue?

Second, take the batteries out of your weather station and run the programs to listen. It is possible you are listening to an unrelated device.

Third, add to this issue as much model number information from your weather station as you can find. Especially look for somewhere in the fine print of the FCC marking where it might say which frequency it is using. It might be broadcasting other than where you are looking.

jimstudt avatar Mar 01 '14 18:03 jimstudt

Upon closer inspection it would appear I have the WH1081 weather station. Not sure if the RF protocol is the same..

I believe the 10 second blips are from my current cost energy monitor also using 433mhz, i confirmed this by watching the LED update and the blips through the rtlsdr.

Looks like the WH1081 is transmitting every 45-60 seconds.

Will get a ook_dump output later tonight.

Thanks for the help.

slothbag avatar Mar 02 '14 02:03 slothbag

So it looks like ookd is only ever sending 1 burst, sometimes 2 over the multicast. The 28 bytes per message is the multicast packet bytes (presumably the size of the burst struct).

The 1 burst is outside of the default mins/maxs set in wh1080.c, so it never tries to decode it, but as it is only 1 burst, it only has 1 bit (if i understand correctly) which means its useless anyway.

So not sure why ookd is not detecting the signal and multicasting it. I am trying to figure out how to analyze the signal in a waveform viewer and maybe share it online somewhere if seeing it would help decode it.

http://192.210.200.104/wh1081.wav

slothbag avatar Mar 02 '14 11:03 slothbag

ookdump output:

Received 28 bytes
0000016.275204s ###   1 pulses
num high   low      freq
  1 54648uS   8004uS   20.797kHz
Received 28 bytes
0000064.276124s ###   1 pulses
num high   low      freq
  1 54624uS   8004uS   19.781kHz

I was playing around with the riseThreshold and dropThreshold in ookd.c, if I make them 1.4 & 1.2 respectively I get a lot more bursts being detected and sent to wh1080, but still not decoding anything.

slothbag avatar Mar 06 '14 12:03 slothbag