Re: Interface documentation for programmers
|
Many HAMs kind of associate the protocol with sound card TNCs (like: AGWpe, UZ7HO, and Direwolf).? Others associate it with (what I will call) an interface combiner (LDSped).
The true is that most APRS clienets that implement the AGW protocol.? It allows for multiple streams over the same TCP interface.
However, as I stated earlier, the standard KISS over TCP/IP has a lot of the same features, and makes interacing easier.? Direwolf has the TCP/IP interface for bidirection communication, as does almost every APRS client.? Why add another protocol, when you probably already have the KISS protocol in any application you would develop for APRS?
On Sunday, September 26, 2021, 07:33:41 PM EDT, Martin Cooper <kd6yam@...> wrote:
AGWPE
Martin, am confused. Isn't AGWPE a separate software package that must be installed? Also is it only available for Microsoft Windows?
The confusion arises because the name is used for two different things. There is the AGWPE software, written by?George Rossopoulos (SV2AGW) for Windows, and comprising a library and a few applications. And then there is the AGWPE API / protocol, as described in the document I linked to.
The name comes from AGW Packet Engine, the AGW?coming from the author's callsign.
There are several server implementations of the AGWPE protocol. The three that I'm aware of are the AGWPE software itself, Direwolf, and ldsped (the name of that last also coming from the author's callsign, plus Packet Engine Daemon). Any of those can be used by client software, such as Xastir and many others, that uses the AGWPE protocol to talk to the server. Hope that helps.
Martin. KD6YAM ?
|
