<div dir="ltr"><div>Right, so what I have gathered is not to bother with UHF at the moment, stick with 2m and use another transmitter. <br><br></div><div>Thanks all for the help, <br><br></div><div>PS: Sorry if I caused any problems with my question. <br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 28, 2016 at 12:28 PM, Scott Miller <span dir="ltr"><<a href="mailto:scott@opentrac.org" target="_blank">scott@opentrac.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Sending the entire NMEA string is a waste of bandwidth and leads to
greater packet loss because of the long packets. Base91 will give
you plenty of resolution, and the !DAO! extension gives you an extra
digit with the standard lat/lon format. Please don't put new
systems on the air using raw NMEA - that was a kludge for things
like the KPC-3 from more than 15 years ago.<br>
<br>
Scott<br>
N1VG<div><div class="h5"><br>
<br>
<div>On 9/28/2016 4:00 AM, Andrew Rich
wrote:<br>
</div>
<blockquote type="cite">
<div>Cody</div>
<div><br>
</div>
<div>I found you better accuracy out of
APRS by sending just the full nmea string </div>
<div><br>
</div>
<div><br>
<br>
<div>Andrew</div>
<div><br>
</div>
<div>-----------------------------</div>
Sent from my iPhone
<div>Andrew Rich</div>
<div>e <a href="mailto:vk4tec@tech-software.net" target="_blank">vk4tec@tech-software.net</a></div>
<div>w <a href="http://www.tech-software.net" target="_blank">www.tech-software.net</a></div>
<div>m 0419 738 223</div>
</div>
<div><br>
On 28 Sep 2016, at 10:57, crvickru <<a href="mailto:crvickru@lakeheadu.ca" target="_blank">crvickru@lakeheadu.ca</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div><br>
</div>
<div>Thank you all for your suggestions from what I gather
from the discussion it is impracticable to use this module.
All of your comments and suggestions have been helpfully. I
am reading more about aprs and it's capabilities what an
amazing system. </div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style="font-size:85%;color:#575757" dir="auto">Sent
from my Samsung Galaxy smartphone.</div>
</div>
<div><br>
</div>
<div style="font-size:100%;color:#000000">
<div>-------- Original message --------</div>
<div>From: Mark Cheavens <<a href="mailto:mcheavens@usa.net" target="_blank">mcheavens@usa.net</a>>
</div>
<div>Date: 2016-09-27 8:32 PM (GMT-05:00) </div>
<div>To: <a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a> </div>
<div>Subject: Re: [aprssig] UHF APRS </div>
<div><br>
</div>
</div>
defamation?<br>
Or did he deform you....<br>
<br>
Only since this is a "technical" group.<br>
<br>
Mark<br>
KC5EVE<br>
On 9/27/2016 6:03 PM, <a href="mailto:steve@dimse.com" target="_blank">steve@dimse.com</a> wrote:<br>
>> On Sep 27, 2016, at 6:42 PM, Andrew Rich <<a href="mailto:vk4tec@tech-software.net" target="_blank">vk4tec@tech-software.net</a>>
wrote:<br>
>><br>
>> Cyber bully<br>
>><br>
> Well, Andrew, we've covered this before. It isn't
bullying, it is sarcasm, because my other attempts to make you
act like a responsible member of the community, including
hundreds of answers to your questions over more than thirteen
years, have failed. If you don't want to hear any more, all
you have to do is to use the SIG the way the other hundreds of
people here do - don't report things that are not novel to
APRS, don't ask questions a simple google response can answer,
and if you answer questions make sure your response actually
addresses the question being asked and is not simply a way for
you to tell us all about something you have done or want to
do.<br>
><br>
>> Public deformation<br>
>><br>
> That requires a something I've said to be untrue, what
would that be?<br>
><br>
> Steve K4HG<br>
><br>
> ______________________________<wbr>_________________<br>
> aprssig mailing list<br>
> <a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a><br>
> <a href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/<wbr>listinfo/aprssig</a><br>
<br>
<br>
______________________________<wbr>_________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a><br>
<a href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/<wbr>listinfo/aprssig</a><br>
</div>
</blockquote>
<blockquote type="cite">
<div><span>______________________________<wbr>_________________</span><br>
<span>aprssig mailing list</span><br>
<span><a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a></span><br>
<span><a href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/<wbr>listinfo/aprssig</a></span><br>
</div>
</blockquote>
<br>
<fieldset></fieldset>
<br>
<pre>______________________________<wbr>_________________
aprssig mailing list
<a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a>
<a href="http://www.tapr.org/mailman/listinfo/aprssig" target="_blank">http://www.tapr.org/mailman/<wbr>listinfo/aprssig</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>______________________________<wbr>_________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br>
<a href="http://www.tapr.org/mailman/listinfo/aprssig" rel="noreferrer" target="_blank">http://www.tapr.org/mailman/<wbr>listinfo/aprssig</a><br>
<br></blockquote></div><br></div>