<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>You are correct. It is a compressed position and not Mic-E. I'm guessing from your earlier comments that it is not being sent or received properly when using that format... I'll leave it in "plain text" mode for now..<br></div><div> <br></div><div><br></div><div><br></div><div>-- Joe <br></div><div>KA3NAM</div><div><br></div><div><br></div><div>May 8, 2020, 9:50 PM by aprssig@lists.tapr.org:<br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>On 5/8/2020 10:20 PM, Joe Bennett wrote:<br></div><blockquote><div>Not sure about the Mic-E issue. It is a valid Mic-E frame on 2 meters. I suspect it is something with how FLDIGI is handling the frame.<br></div></blockquote><div><br></div><div>The latest packet as received here:<br></div><div><br></div><div> A3NAM-12>APX210,ECHO:=3854.24N/09446.04Wx<br></div><div><br></div><div><br></div><div><br></div><div>There are actually THREE formats for position reports:<br></div><div><br></div><div>- Plain test human-readable lat/long values in "APRS format" with the symbol control codes interspersed.<br></div><div><br></div><div>- APRS compressed format that encodes both lat and long in the payload as "ASCII gibberish" (actually two 4-bit hex representations of decimal digits per byte, that get displayed as an ASCII symbol with the same byte value.<br></div><div><br></div><div>- Mic-E format Mic-E replaces the destination address (In your case "APX210") with a bunch of seemingly-random alpha-numeric "ASCII gibberish" that encodes the latitude. The packet payload only contains the longitude, also in "ASCII gibberish", for the absolutely shortest possible transmission.<br></div><div><br></div><div><br></div><div><br></div><div>If you think your application is sending Mic-E, it is apparently incorrectly labeling "APRS compressed formt" as "Mic-E". ALL the transmissions from youi that I monitored tonight have "APK210" in the destination address field. Not one had the kind of ASCII gibberish here that would be a Mic-E format posit.<br></div><div><br></div><div><br></div><div><br></div><div> I'll have to look further into the WIDE2-2 path. Looks like Xastir is<br></div><blockquote><div>defaulting to WIDE2-2 even when I leave the path(s) blank. I changed it to ECHO for the time being.<br></div><div><br></div><div>I heard you once this evening via packet. No other digital stations heard here otherwise. Few folks running phone on the channel...<br></div></blockquote><div><br></div><div>I heard them, and some CW activity. MFSK16 is so robust that it plowed right through them with no difficulty! The CW was especially dramatic on my waterfall display. The MFSK transmissions were occupying a span from about 1575 to 1825 HZ, with the CW at 1500 Hz at the same time -- no problems with either.<br></div><div><br></div><div>____________________________________________________________<br></div><div>Stephen H. Smith wa8lmf (at) aol.com<br></div><div>Skype: WA8LMF<br></div><div>EchoLink: Node # 14400 [Think bottom of the 2-meter band]<br></div><div>Home Page: http://wa8lmf.net<br></div><div><br></div><div>----- NEW! 60-Meter APRS! HF NVIS APRS Igate Now Operating ------<br></div><div> <http://wa8lmf.ddns.net:14447/><br></div><div><br></div><div><br></div><div><br></div><div>Live Off-The-Air APRS Activity Maps<br></div><div> <http://wa8lmf.net/map><br></div><div><br></div><div>Long-Range APRS on 30 Meters HF<br></div><div> <http://wa8lmf.net/aprs/HF_APRS_Notes.htm><br></div><div><br></div><div><br></div><div><br></div><div>_______________________________________________<br></div><div>aprssig mailing list<br></div><div>aprssig@lists.tapr.org<br></div><div>http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org<br></div></blockquote><div><br></div> </body>
</html>