<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN'>
<html>
<head>
<meta http-equiv='Content-Type' content='text/html;charset=us-ascii'>
<style>BODY{font:10pt Tahoma, Verdana, sans-serif;}</style>
</head>
<body>
What I've considred doing is similar, but instead of an absolute distance from your last beacon it'd be distance from your dead-reckoned position based on the last beacon. It'd be particularly useful with clients like Xastir that do dead reckoning - you'd always know that the tracked station isn't further than a certain distance from its displayed position.<br><br>It just happens to take a little more math than I want to squeeze into the OpenTracker. Maybe I'll do it in the Tracker2.<br><br>Scott<br>N1VG<br><blockquote style="border-left: 2px solid rgb(0, 0, 255); padding-left: 5px; margin-left: 5px; margin-right: 0px;"><hr><b>From:</b> Stephen H. Smith [mailto:wa8lmf2@aol.com]<br><b>To:</b> TAPR APRS Mailing List [mailto:aprssig@lists.tapr.org]<br><b>Sent:</b> Wed, 23 May 2007 10:59:44 -0700<br><b>Subject:</b> Re: [aprssig] The new D710 and Smart Beaconing?<br><br><!-- -->Wes Johnston, AI4PX wrote:<br>> I set mine highspeed to 45mph. My line of thinking is that if I'm <br>> travelling at a hi rate of speed, I'm probably on a long straight <br>> stretch of road and can get away with beacons every xx miles. If <br>> below 45mph, I get corner pegging... if parked, the slow rate. If you <br>> set the high speed to an unreasonable unattainable high speed, then <br>> the corner pegging causes transmissions on long slow curves in the <br>> interstates. One such road here in my area has a slow S turn that is <br>> 3/4 mile end to end. It'll cause a transmission entering and exiting <br>> the curves.<br>> <br><br><br>I think it's the corner pegging component of Smart Beaconing that REALLY <br>chokes the APRS channel with excessive transmissions. It might work in <br>the flat midwest where virtually all the major highways and significant <br>secondary roads are dead straight and aligned on the cardinal <br>directions [ Ever looked out the window while flying over western <br>Illinois, Iowa or Nebraska? It looks like flying over graph paper! <br>]. In the west (where roads curve constantly around mountains or <br>switchback their way over mountain passes) , and in suburban <br>subdivisions of carefully artistically curved streets, you wind up <br>transmitting almost continuously. <br><br>I originally had smart beaconing enabled in APRSplus when I first took <br>it mobile in Southern California some years ago. Several weeks later, <br>I happened to see a listing of who made the most transmissions on 144.39 <br>in SoCal and was shocked to see I had the second largest number of <br>transmissions in the area, after a clueless idiot that beacons raw NMEA <br>strings every 60 seconds 24/7. I immediately disabled it. <br><br>I now use what is essentially a modified (and very simple) version of <br>Smart Beaconing. UIview allows you to set the transmit interval based <br>on either a fixed number of minutes (like a D700), or on a specified <br>change in position when above above a certain speed. The position <br>changes are in increments of either 1KM or 1 Mile. This intrinsically <br>has you beaconing less often when crawling in city traffic, and more <br>frequently when you hit the open road at 65+ MPH with no arbitrary <br>thresholds of SLOW-MED-FAST. <br><br>You also set a time interval for beacons when position doesn't change <br>(or changes very slowly) such as when you park and stop changing <br>position (or get gridlocked in a construction zone where your progress <br>is less than 1 or 2 MPH). I have my UIview mobile set to beacon on <br>whichever comes first: a 1 KM change in location --or-- 30 mins elapsed <br>time. <br><br>Compared to the full smartbeaconing described above, this reduced my <br>beaconing over 95%! UIview also allows you to manually force a <br>beacon at anytime by pressing F9. This addresses the issue of a final <br>updated posit when you park before the 30 min stationary interval <br>triggers, and is also useful if you DO want to peg a particularly <br>important corner. <br><br>(You can easily do this with a TinyTrack as well. In addition to the <br>normal smart or dumb timed intervals, connect a push button to the input <br>that would normally be used for Mic-E PTT triggering. You can then force <br>a posit at any time by pushing the button, withot excessive numbers of <br>corner pegs by default.)<br><br><br>BOTTOM LINE: An astonishing number of people seem to have the urge to <br>draw an absolutely perfect track line on other user's maps, via <br>aggressive corner pegging. It is SIMPLY IMPOSSIBLE to do this on a <br>shared 1200 baud channel ! ! !<br><br><br><br><br>--<br><br>Stephen H. Smith wa8lmf (at) aol.com<br>EchoLink Node: 14400 [Think bottom of the 2M band]<br>Home Page: <a href="http://wa8lmf.com" target="_blank">http://wa8lmf.com</a> --OR-- <a href="http://wa8lmf.net" target="_blank">http://wa8lmf.net</a><br><br>NEW! World Digipeater Map<br> <a href="http://wa8lmf.net/APRSmaps" target="_blank">http://wa8lmf.net/APRSmaps</a><br><br>JavAPRS Filter Port 14580 Guide<br> <a href="http://wa8lmf.net/aprs/JAVaprsFilters.htm" target="_blank">http://wa8lmf.net/aprs/JAVaprsFilters.htm</a><br><br>"APRS 101" Explanation of APRS Path Selection & Digipeating<br> <a href="http://wa8lmf.net/DigiPaths" target="_blank">http://wa8lmf.net/DigiPaths</a><br><br>Updated "Rev H" APRS <a href="http://wa8lmf.net/aprs" target="_blank">http://wa8lmf.net/aprs</a><br>Symbols Set for UI-View,<br>UIpoint and APRSplus:<br><br><br><br>_______________________________________________<br>aprssig mailing list<br><a href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a><br><a href="https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig" target="_blank">https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br><!-- --><style>
</style>
</blockquote></body></html>