Andy

Take a look at rtl_433 (https://github.com/merbanan/rtl_433). This software 
decodes AcuRite sensors.  No, the 5 N 1 transmits different message types 
that contains the sensor data.  The pressure sensor is located in the 
console. 

time: "2020-06-27 21:29:46"
model: "Acurite-5n1"
subtype: 56
id: 1531
channel: "A"
sequence_num: 1
battery_ok: 1
wind_avg_km_h: 3.483
temperature_F: 73.8
humidity: 94
mic: "CHECKSUM"
mod: "ASK"
freq: 433.931
rssi: -0.132
snr: 13.244
noise: -13.376

time: "2020-06-27 21:31:16"
model: "Acurite-5n1"
subtype: 49
id: 1531
channel: "A"
sequence_num: 1
battery_ok: 1
wind_avg_km_h: 2.656
wind_dir_deg: 180
rain_in: 19.27
mic: "CHECKSUM"
mod: "ASK"
freq: 433.951
rssi: -0.142
snr: 13.246
noise: -13.388





On Saturday, June 27, 2020 at 4:23:33 PM UTC-4, VE4PER / Andy wrote:
>
> I am trying to get SDR Uno &  RSP1A to detect and decode signal between 
> 5 in 1 sensor unit to display unit so I can have a backup diagnostic to 
> verify that data comm link. 
>
> I can see what appears  I suspect to be it, but it looks like 
> cyclical/repetitive  short bursts on the same approx length of xmssn as 
> FT8, but the bursts seem to be occurring on six different discreet UHF 
> freqs in a channel width of about 433.8 MHz to 434.1 MHz. 
>
> Does anyone have any more tech info about this beyond AcuRite's brochure 
> that just says it is in 433 MHz band area? I can feed detected burst 
> audio via VAC to decoders of sorts but need to know what program to use 
> to detect and decode it. 
>
> Does each sensor on the mast unit xmit on it's own? I can maybe grab a 
> short vid clip to show it if that might be of use? 
>
> Thanks for any info. 
>
> 73 & Gud DX 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e5035e0d-8319-45fd-956b-9f322abc56eao%40googlegroups.com.

Reply via email to