There's nothing saying you would need to use a smart phone's cellular data connection in the regular course of action. There are detailed programs entirely devoid of data connections for their operation. Medical programs that have vast databases of information and images. Dictionary.com is great and easily accessible example. The installed app size is nearly 200 megs and must be updated over a wi-fi or wired connection. However, it has the entirety of Dictionary.com contained inside it.<div>
<br></div><div>A iOS or Android platform program could be written that would take advantage of every implementation of APRS purely over a TNC or direct audio link to a amateur RF device. Of course, implementing an APRS-IS tie-in is free, but it isn't necessary for maps, image traffic or messaging.</div>
<div><br></div><div>This could cut a walkabout solution down to two "boxes", radio and smart phone, and one wire connection. Or put all the features of a base APRS station onto a tablet securely mounted in a vehicle.<br>
<br><div class="gmail_quote">On Tue, May 24, 2011 at 2:32 PM, Stephen H. Smith <span dir="ltr"><<a href="mailto:wa8lmf2@aol.com">wa8lmf2@aol.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 5/24/2011 9:37 AM, Julian, G4ILO wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I understand and agree with you Gregg but as a user of Lynn KJ4ERJ's<br>
APRSISCE in Windows Mobile and also an owner of several APRS RF<br>
devices I find myself in something of a dilemma. Do I use APRS over<br>
cellular and get all these improved features or do I stick true to the<br>
spirit of the hobby, use the radio and accept the limitations of the<br>
radio devices and the bandwidth?<br>
</blockquote>
<br></div>
The smart phone types seem to also forget that cellular "wireless" depends on VAST amounts of infrastructure - you must be within 5 miles or so of a cell site, for all these neat gadgets with their fractional-watt transmitters linked to low-performing hidden antennas to work. (It seems to be impossible now to get a cell phone with an actual exposed whip antenna or external antenna connector. )<br>
<br>
Our clunky old low-bit-rate narrowband radios transmit 10s of watts (or more) into real antennas, results in vastly more robust long-distance communications.<br>
<br>
<br>
I recently attended a seminar on conventional land mobile radio vs broadband "4G" LTE for public safety comms. An interesting take on the differences I had never heard brought up before was contrasting the energy density per Hz of bandwidth (which ultimately determines the SNR at the receiver and data throughput achievable). 35 watts in a 20 KHz bandwidth for FM LMR vs a one-third-watt smeared out across 10 megahertz.for LTE. The implication was that for comparable coverage area for the user in a large metro police dept or county sheriff's dept, you would require 10-20 times (!) the number of base station sites for LTE broadband; i.e. they would basically be building another cellular network.<div class="im">
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
APRS over cellular is as much ham<br>
radio as Echolink on a computer (or cellphone) and I think many of us<br>
would be quite scathing of someone who claimed he made a ham radio<br>
contact because he called someone up on Echolink.<br>
<br>
</blockquote>
<br></div>
A lot of people seem to forget that the original intent of EchoLink was to interconnect RADIOs in different regions together over the Internet.<br>
<br>
Several years ago, I saw a posting somwhere reporting that the author of EchoLink now regretted implementing the local-user-in front-of-PC-mike-&-speaker mode of EchoLink rather than keeping it strictly a radio-to-radio setup like IRLP. Providing the local user mode reduced EchoLink to being essentially a hams-only version of Skype or Google Voice.<br>
<br>
-------------------------------------------------------------------------------<br>
<br>
--<br>
<br>
Stephen H. Smith wa8lmf (at) <a href="http://aol.com" target="_blank">aol.com</a><br>
EchoLink Node: WA8LMF or 14400 [Think bottom of the 2M band]<br>
Skype: WA8LMF<br>
Home Page: <a href="http://wa8lmf.net" target="_blank">http://wa8lmf.net</a><br>
<br>
===== Vista & Win7 Install Issues for UI-View and Precision Mapping =====<br>
<a href="http://wa8lmf.net/aprs/UIview_Notes.htm#VistaWin7" target="_blank">http://wa8lmf.net/aprs/UIview_Notes.htm#VistaWin7</a><br>
<br>
*** HF APRS over PSK63 ***<br>
<a href="http://wa8lmf.net/APRS_PSK63/index.htm" target="_blank">http://wa8lmf.net/APRS_PSK63/index.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><div><div></div><div class="h5"><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a><br>
<a href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig" target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br>
</div></div></blockquote></div><br></div>