Luc The approach sounds like a good way to proceed. Currently running option -tr 3 and receiving the same results. Do you think we should move this to weewx-development group?
Rich On Wednesday, March 13, 2019 at 7:10:21 PM UTC-4, Luc Heijst wrote: > Hi Rich, > > We need another approach. As I said before, the frequencies of RFM69 > didn’t work for my EU transmitter either. > Note: the lowest and highest frequencies in the RFM69 table were not > modified by me, so that can’t be a cause here. > > I plan to write a testprogram as follows. > 1. Start with a frequency in the lower US band. > 2. Start the init proces to see if any messages can be read. When you > configure both of your sensors with parameter -tr 7 this process may take > less time. > 3a. When a message is read succesful; continue right away. This frequency > is (more or less) good. > 3b. When a timeout occurred; this frequency is no good. Also continue. > 4. Increase the frequency with a certain amount. The amount must be small > enough not to miss any good frequencies. > 5a. When the increased frequency is bigger than the max frequency (at the > end of the US band), we are ready to analyse the logging. > 5b. If not, continue with step 2. > > The logfile will show a list with evenly spreaded frequencies and for each > frequency a true or false message received. > With this info we create our first new hopping list. The program will show > for each received message a frequency error for that channel. > With the frequency error data we can fine-tune each channel frequency. > > Note: On my test site the rtldavis program will function normaly with > maximum frequency errors of + and - 10,000 Hz. > > What do you think? > > Luc > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
