--- In [email protected], "Lynn W. Deffenbaugh (Mr)" <ldeff...@...> wrote: > > Chris, > > What callsign-SSID are we talking about here? Do you have profile > switching enabled at all? Are you SURE you don't have profile switching > enabled (a very common problem in fast beaconing)? > > If you have a Nuvi 350, did you perchance send in a "--bea" command? I > did that yesterday on my KJ4ERJ-9 and it stuck in the Outbox as > "Sending..." causing beacons every few seconds until I figured it out. > (KJ4ERJ-9 is an OT2m, not an internal T2) > > Lynn (D) - KJ4ERJ - T2-135 as KJ4OVQ-9 OT2m as KJ4ERJ-9 > > Chris wrote: > > I was experimenting with a low speed Smart Beacon Profile on a T2 (with > > integrated 5W VHF transceiver) and encountered an unexpectedly high > > beaconing rate when parked. My settings were as follows: > > > > Slow Speed: 0.0 MPH TX rate: 7193 sec > > High Speed: 4 MPH TX rate: 61 sec > > Turn angle: 15 deg Max TX rate: 3 sec > > > > The shallow turn angle and fast TX rate was set to see if I could reliably > > double beacon on street corners. > > > > The issue arose when parked: Initially, as anticipated, the T2 did not > > beacon, but after 10 minutes sitting, it began beaconing every few seconds > > until I shut it off. After thinking about what could cause this it > > occurred to me that beaconing may be triggered when the uncertainty in > > sequential GPS readings causes the T2 turning algorithm to be satisfied. > > However, since I don't know the details of the turning algorithm I can only > > guess how to avoid this boundary condition. > > > > Can anyone shed some light on this? > > > > > > > > ------------------------------------ > > > > Yahoo! Groups Links > > > > > > > > > > > The call sign is KF7FIR-9. The rapid beaconing event I am referring to began 7/28/2010 at 16:26:39 PDT. I can account for beaconing behavior prior to that time.
I am using a Nuvi 350 in fleet management mode. I looked and noted that I had a --profile listed in my outbox as sending. However, that message is several weeks old at least. I did have speed based profile switching active as follows Profile 1 -> Profile 2 -> 23MPH Profile 2 -> Profile 1 -> 17MPH These settings are high enough so that they shouldn't have been responsible. However, I have disabled Profile switching for the time being.
