Order Tray | Contact Us | Home | SIG Lists

[aprssig] Q: Verify Path for SmartPhones

Lynn W. Deffenbaugh (Mr) ldeffenb at homeside.to
Sat Jan 14 02:48:36 UTC 2012

You are correct and while you're at it, remind him that APRS-IS is cAsE 

Refer him to http://www.aprs-is.net/Connecting.aspx in particular the 
last paragraph which includes:

> Packets originating from the client should only have TCPIP* in the 
> path, nothing more or less (AE5PL-TS>APRS,TCPIP*:my packet). 

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 1/13/2012 2:19 PM, Steve Noskowicz wrote:
> I don't have a smart phone, so I only pay half attention to those discussions. One of the am drive-time group got a message and I think the sender needs some advice...
> Based on what I (think I try to) inderstand, smart phones shouldn't have an RF path, right?  Seems to make no sense.  They should only have TCPIP, right?
> I wanna' give MXT the correct advice, and it looks like time to update my Beginner guide to include some smart phone points.
> E.G.
> Correct:
> KA9MGS>APDU65,TCPIP*,qAC,T2LAX:=4154.94N/08747.38W$260/000 /A=000630 U2APRS
> Incorrect:
> N9MXT-12>APRNOW,WIDE1-1,WIDE2-1,qAS,n9mxt-12:/131528z4210.94N/08819.40WM>Viewing on my iPad!
> ...???...

More information about the aprssig mailing list