Are these the Frequencies? 902.381925, 902.884575, 903.385425, 903.888075, 904.389375, 904.890675 905.391975, 905.894625, 906.395925, 906.898125, 907.399425, 907.901175 908.402925, 908.904675, 909.406875, 909.909075, 910.409925, 910.912125 911.413875, 911.915175, 912.417375, 912.919125, 913.420425, 913.922625 914.424375, 914.926575, 915.427875, 915.929175, 916.431825, 916.933575 917.434425, 917.935725, 918.438375, 918.940125, 919.441425, 919.943625 920.445375, 920.947125, 921.448425, 921.949725, 922.451925, 922.953225 923.456325, 923.957175, 924.458925, 924.960225, 925.462425, 925.964625 926.466375, 926.967675, 927.469875
On Monday, March 18, 2019 at 8:09:02 AM UTC-4, kobuki wrote: > Yes, you summed up correctly. All things point to the fact the Golang code > is at fault somewhere. > > On Mon, Mar 18, 2019 at 1:05 PM Greg Troxel <[email protected] <javascript:>> > wrote: > >> nls <[email protected] <javascript:>> writes: >> >> > As mentioned earlier, the frequencies were sniffed in original VP2 >> consoles >> > (you can find the posts about that in wxforum threads). They're the GFSK >> > center frequencies, no IF. The "RFM69 frequencies" just mean the ones >> > programmed into the firmware of small Arduino clone based receivers >> using >> > an RFM69 transceiver module. Also noted that with a simple SDR receiver >> the >> > packets are appearing at the expected frequency. It's possibly a simple >> > overlook with handling frequencies or frequency correction in the SDR >> > demodulator code. I think any help or ideas come handy. >> >> If I follow then, the RFM69 list matches both the VP2 console sniffing >> and the Arduino RFM69 code, and those arduino projects are known to >> work. And the RFM69 frequencies have been confirmed with SDR code not >> involving rtldavis. So it is clear that there is a bug in the rtldavis >> code and of course somebody needs to find it. Is that right? >> >> I will have a look. >> >>
