--- In [email protected], "Keith VE7GDH" <ve7...@...> wrote: > > Chris KF7FIR wrote... > > > I am interested in double beaconing on corners because only > > ~40% of my beacons are received in my area. If I double beacon, > > I can increase the probability that one beacon is heard to ~75%, > > while the probability that both beacons are heard is only ~15%. > > If I can increase the probability of corner pegging I can increase > > the length of time between ordinary beacons. > > Sorry if someone has already suggested this, but I'm way behind on > catching up with my email right now. > > I'm not sure if the cause of what you were seeing is because of > what the GPS is outputting or because of algorithms in the T2. > > How about trying some semi-SmartBeaconing? You could set the > fast and slow speeds both to e.g. 10 mph with both set for a 3 minute > beacon rate. You are presumably running low power while on foot, and > if you use a reasonable path, and keeping in mind that you won't always > be heard, you wouldn't be creating too much QRM. Then use your slightly > more aggressive settings for corner pegging. > > I believe some airborne APRS users have used the technique, but not > always with otherwise optimal (path) settings. On a plane, profile switching > would really shine to change the paths e.g. > 5000' and < 3000' on the way > back down, with those figures adjusted depending on the kind of terrain > where they are flying. > > 73 es cul - Keith VE7GDH > -- > "I may be lost, but I know exactly where I am!" > Keith,
Thanks for your input. The workaround turns out to be easy. All I have to do is put in a small non-zero value for the Slow Beacon Threshold Speed. Apparently the T2 doesn't like 0 MPH even when the Slow Beacon Rate is set adequately large (e.g. 7200 sec). However, someone who unsuspectingly puts in 0 MPH is going to be blasting their neighborhood with rapid beaconing so I think this glitch is worth a look to confirm, and fix if possible. Chris KF7FIR
