Luc Thanks for the explanation. Made the change and going to let it run to see what happens.
Rich On Thursday, March 21, 2019 at 10:57:34 PM UTC-4, [email protected] wrote: > On Thursday, 21 March 2019 23:21:06 UTC-3, rich T wrote: >> >> The issue I'm having now, the program only hops between the first 5 >> frequencies from the hop table for the US frequencies. Even though >> frequencies might not be right, I thought it should hop through all 51 >> frequencies. >> > > The program works as follows for one transmitter: > 1. The program is reading at channel 0 until a message is read. This is > the init phase. > 2a. When no message could be read, a time-out will occur and the program > start again with step 1 (reading channel 0). > 2b. When a message is read from channel 0, the channel is changed to the > next hop frequency (for US this is channel 19). > 3a. When a message is read from channel 19, the channel will hop yo the > next frequency (for US: channel 41). > 3b. When no message could be read, a time-out will occur and the program > will increase the 'missed-counts-in-a-row'. The next channel is selected > (for US: channel 25). > 4a. When a message is read, the 'missed-counts-in-a-row' is reset to zero. > 4b. When no message could be read, and the 'missed-counts-in-a-row' has > value 5 or bigger, the program start all over with the init phase at step 1. > > So in your case, Rich, only with the first frequency a message could be > read. The other 4 hop frequencies were no good and no single message could > be read, so the program started all over with channel 0. > > When you change line 262 in main.go: > if chAlarmCnts[i] > 5 { > into: > if chAlarmCnts[i] > 51 { > > The program will hop through all 51 channels. This could be a nice test to > see which of the 51 frequencies are good and which aren't. > > Luc > > > >
