[aprssig] AEA PK12 and UIView
Jan T. Pharo la2bba at jpharo.netThu Dec 28 14:23:40 UTC 2006
- Previous message: [aprssig] AEA PK12 and UIView
- Next message: [aprssig] power poles (oh noooo)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Roger Grady <k9opo-1 at sbcglobal.net>, Thu, 28 Dec 2006 09:11:43 -0500: >At 01:12 AM 12/28/2006, Daron J. Wilson wrote: > >>I picked up a PK-12 TNC and it seemed fine on packet, so I hoped to use it >>for my UIView APRS Igate. I ve tried a couple of the UIView config files, >>looks like there are a couple commands not recognized that I have to >>adjust, but the biggest problem is what I get out of the TNC. Here is a >>screen capture from a straight terminal program. It appears to display >>the correct path information when I hear the station directly, but when it >>is digipeated, I get a string of digipeater callsigns in there. >> >>NEWPRT*>WIDE2-2>APN390 <UI>: >>@232402z4445.37NS12402.98W_000/000g000t040r000p000P000b10292.WxDG >> >>PATSY>NEWPRT>NEWPRT*>APN382 <UI>: >>$ULTW0000000001760245283E001897FF000103A70169015E00000000 > >This is standard TNC-2 compatible behavior, and also for the PK-12. It's >controlled by the MRpt command, which defaults to ON. Setting it to OFF >will display only the originating and destination stations. > Also, if PK12 will accept the Host mode KISS command from UI-View, you don't need to care what the TNC can do; UI-View will control it. -- 73 de Jan, LA2BBA Hvaler, Norway
- Previous message: [aprssig] AEA PK12 and UIView
- Next message: [aprssig] power poles (oh noooo)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
