<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<div>I think there is confusion between the APRS format and the JS8CALL format. If the APRS format was used to send in JS8/FT8 it'll take 30 minutes to send the packet. I'm being facetious but it will take a LONG time... The JS8CALL format is converted somewhere else in the network to the APRS format and then dumped on the APRSIS. I'm guessing after its forwarded to JS8NET?</div><div><br></div><div><br></div><div><br></div><div>-- Joe <br></div><div>KA3NAM</div><div><br></div><div><br></div><div>Date: Apr 23, 2020, 2:01 PM<br></div><div>From: spam8mybrain@yahoo.com<br></div><div>To: aprs@ka3nam.com<br></div><div>Subject: Re: [aprssig] HF APRS igates<br></div><div><br></div><blockquote class="tutanota_quote" style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;"><div>It might be better to use a correctly formatted APRS message, so that other APRS clients would be able to interpret your packets once they are I-gated. Packets starting with @ are position reports with timestamps, and have a specific format of timestamp, latitude, longitude, and APRS symbol code. If you want to identify your position by Maidenhead grid square, either the Status packet format (started with > ) or the obsolete Maidenhead position format (started with [ ) can be used as well.<br></div><div><br></div><div>All the gory details on packet formats are in the APRS Protocol Specification at https://www.tapr.org/pdf/APRS101.pdf<br></div><div><br></div><div>Andrew, KA2DDO<br></div><div>author of YAAC ("Yet Another APRS Client")<br></div><div><br></div><div><br></div><div><br></div><div>-------- Original message --------<br></div><div>From: Joe Bennett via aprssig <aprssig@lists.tapr.org> <br></div><div>Date: 4/23/20 14:39 (GMT-05:00) <br></div><div>To: Aprssig <aprssig@lists.tapr.org> <br></div><div>Subject: Re: [aprssig] HF APRS igates <br></div><div><br></div><div> <br></div><div>Just did a test on 60 meters and got gated by K1TWH. It looks like the igate software is adding the comment that it is coming from 30 meters. Guessing that's something to do with the igate config.<br></div><div><br></div><div>Using: '@APRSIS GRID EM28OV' as the message. It would work best if you inserted your own grid square value. :)<br></div><div><br></div><div><br></div><div><br></div><div>-- Joe <br></div><div>KA3NAM<br></div><div><br></div><div><br></div><div>Apr 22, 2020, 10:53 PM by aprssig@lists.tapr.org:<br></div><blockquote style="border-left: 1px solid #93A3B8; padding-left: 10px; margin-left: 5px;" class="tutanota_quote"><div>Well, at least one station has hit my 60-meters igate!<br></div><div><br></div><div>At 01:59:14 UTC 23 Apr, my igate in central Michigan copied KA3NAM . Apparently, at least one other station is igating on 60 meters. APRS.fi shows KA3NAM was gated by AE4HZ.<br></div><div><br></div><div>Again 60-Meters JS8Call igate is on<br></div><div><br></div><div>60 Meters"US Channel 5" (5.403.5 USB) Set waterfall tone freq to 1400 Hz.<br></div><div><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>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></blockquote><div><br></div> </body>
</html>