That's not exactly good news... If you get less than 16 bits of alternating 0 and 1 values, that's still better. Well, the decoder sems to handle the packets themselves when a reception does occur, but I'd rather see it decode every single bit properly, including the preamble. A fixed set of 0xAA or 0x55 values is pretty standard for an FSK preamble, btw. That aside, if the bad preamble were the only problem, we wouldn't complain, would we.
On Sat, Mar 16, 2019 at 10:30 PM <[email protected]> wrote: > On Saturday, 16 March 2019 18:00:21 UTC-3, kobuki wrote: >> >> Bitrate is OK, but the preamble is off, it should be 0xAAAA (alternating >> 1 and 0). >> > > With a preamble of "1010101010101010", no messages were received. Neither > with my set frequencies, nor with the RFM69 frequencies. > > if tf == "EU" { > p.channels = []int{ > // 868072000, 868192000, 868312000, 868432000, 868552000, // original set > that worked > // 868073575, 868192150, 868312125, 868433150, 868553825, // ok > trial-error set > 868078500, 868199000, 868318500, 868438500, 868560000, // best trial-error > set > // 868066711, 868181885, 868297119, 868412292, 868527466, // RFM69 EU > frequencies > } >
