[aprssig] HF APRS igates

[Joe Bennett]

Looks like it. Found this text in the JS8CALL documentation. JS8NET handles it. As long as you have the box checked:

@JS8NET and @APRSIS

Available are two “special” groups for spotting. When spotting stations receive messages to these @JS8NET and @APRSIS groups, the messages are posted to the JS8NET spotting server for processing. This allows for specialized functionality to be built to handle these messages. These groups are non-standard, so you cannot add them to your groups list for standard group processing. However, you can send messages to these groups directly (type it into your TX message box, save it to your saved messages, etc). 



The @APRSIS group is an experimental feature allowing APRS messages to be spotted to the APRS-IS gateway. Two message commands are available, GRID for spotting your callsign at a specific location and CMD for sending a raw APRS packet. 



For example, any station receiving my message:



KN4CRD: @APRSIS GRID FN04TV53



Will submit that spot to JS8NET and spot my callsign at that location to the APRS network. You would then be able to query that spot in an APRS client, like https://aprs.fi



To send a raw frame (say a direct APRS message to SMSGTE), we’d send:



KN4CRD: @APRSIS CMD :SMSGTE   :@5551212 TEST



Everything after the CMD frame is forwarded in an APRS packet, like: 



KN4CRD <https://aprs.fi/?c=raw&limit=&call=KN4CRD>>APZJS8,qAS,KN4CRD::SMSGTE   :@5551212 TEST



Every once in a while it pays to RTFM.. :)



-- Joe 
KA3NAM

Apr 23, 2020, 5:01 PM by aprssig at lists.tapr.org:

> On 4/23/2020 4:02 PM, Joe Bennett via aprssig wrote:
>
>> 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?
>>
>
>
> The earlier version 1.1.1 of of the JS8CALL application treated the APRS-IS as an alternative "spotting network" to the usual FT8/JS8 spots.  It provided a set of fields with the usual APRS-IS login info, right in the application (File, Settings, then the "Reporting").
>  The APRS fields asked for were:
> APRS-IS server name, server port name (defaulted to the customary 14580), and APRS-IS passcode.   Apparently the app was computing the APRS-IS passcode based on the callsign initially entered during setup by itself -- I certainly never entered it myself.
>
> Apparently, the JS8 app translated to APRS format internally before linking to the APRS-IS.
>
> In the current 2.1.1 version, the "APRS-centric" dialog has completely disappeared, with no warning.  I have no idea what is happening now.  Has the JS8 Internet "spot-reporting" infrastructure now taken on the task of reformatting and forwardinmg to the APRS-IS??
>
> __________________________________________________________
>
> Stephen H. Smith    wa8lmf (at) aol.com
> Skype:        WA8LMF
> EchoLink:  Node #  14400  [Think bottom of the 2-meter band]
> Home Page:          http://wa8lmf.net
>
> -----   NEW!    60-Meter APRS!   HF NVIS APRS Igate Now Operating  ------
>  <http://wa8lmf.ddns.net:14447/>
>
>
>
> Live Off-The-Air APRS Activity Maps
>  <http://wa8lmf.net/map>
>
> Long-Range APRS on 30 Meters HF
>  <http://wa8lmf.net/aprs/HF_APRS_Notes.htm>
>
>
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20200424/cec56e3d/attachment.html>