[aprssig] ARISS igated location anomaly/discrepancy

[Cap Pennell]

Apparently W0JW-6 “satgate” is using UISS software from ON6MU, 

http://users.belgacom.net/hamradio/uiss.htm

 

Hope this helps.

73, Cap KE6AFE

 

From: aprssig [mailto:aprssig-bounces at tapr.org] On Behalf Of Nagi Punyamurthula via aprssig
Sent: Thursday, July 2, 2015 9:05 PM
To: Pete Loveall AE5PL Lists; TAPR APRS Mailing List
Subject: Re: [aprssig] ARISS igated location anomaly/discrepancy

 

This issue still remains.  

The following screen shots are from the pass thru a few minutes ago here in the Minnesota area

 



 



 

 

-----Original Message-----
From: aprssig [mailto:aprssig-bounces at tapr.org] On Behalf Of Pete Loveall AE5PL Lists via aprssig
Sent: Wednesday, July 01, 2015 6:25 AM
To: TAPR APRS Mailing List
Subject: Re: [aprssig] ARISS igated location anomaly/discrepancy

 

Unfortunately, the software used by W0JW-6 is doing Mic-E translation at the IGate which was deprecated over a decade ago because of just this issue (and because everyone was creating different translated packet formats which removed any traceability).  Also, it is likely they are using a TNC in command mode, not in KISS mode.  The software or TNC is stripping the 0x1c character as white space before doing the translation and that is what is causing the issue.  The last packet seen from W0JW-6 this morning had a TOCALL of APEG02  Maybe that will help identify the software improperly translating Mic-E packets instead of passing them transparently to APRS-IS.

 

73,

 

Pete Loveall AE5PL

pete at ae5pl dot net

 

> -----Original Message-----

> From: Paul Bramscher via aprssig

> Sent: Tuesday, June 30, 2015 8:23 PM

> 

> Most likely an encoding issue at the gating level.  What we see in 

> rendered HTML on the web site doesn't necessarily mean that the 

> underlying encoding methodology was sound.  On aprs.fi, for example, 

> you can look at "raw" packets.

> 

> I see the same operator (W0JW, on 6/27), who very briefly gave me a 

> "No Sym Yet" also.  I hit BCON once more, out of curiosity on this 

> pass, and WA8LMF digipeated me correctly.  WA8LMF has a reliable 

> setup, and is one of our better bets for being heard from our QTH in the St.

> Paul/Minneapolis area.  Here you can see how WA8LMF passed a "<0x1c>"

> character (if e-mail doesn't mess this up), whereas W0JW did not:

> 

> 2015-06-27 17:15:39 EDT: KD0KZE>TUPX8Y,RS0ISS*,qAR,W0JW-6:'yaHl

> -/]Greetings via ISS from Circle Pines MN=

> 2015-06-27 17:18:44 EDT: KD0KZE>TUPX8Y,RS0ISS*,qAR,WA8LMF-SG:'yaHl

> <0x1c>-/]Greetings via ISS from Circle Pines MN=

_______________________________________________

aprssig mailing list

 <mailto:aprssig at tapr.org> aprssig at tapr.org

 <http://www.tapr.org/mailman/listinfo/aprssig> http://www.tapr.org/mailman/listinfo/aprssig

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20150702/8142f686/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 29871 bytes
Desc: not available
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20150702/8142f686/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 19207 bytes
Desc: not available
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20150702/8142f686/attachment-0001.png>