Re: Interface documentation for programmers
|
At the top of this conversation, you said:
"Although I see a lot of good in the AGW protocol, it does add an extra layer."
The point of my previous message was that there is an extra layer involved when using KISS that hadn't been mentioned. As you said yourself?below, you decoded packets received from Direwolf using KISS. What you got from KISS itself was just a blob of data; you had to implement some other specification to understand / interpret those blobs before you could do something meaningful with them. It is KISS plus that extra layer that is the parallel to AGWPE,?not KISS by itself.
I haven't claimed that there is anything you can do with AGWPE that you can't do with KISS plus that extra layer, or vice versa, nor have I claimed that one is better than the other. To each, his or her own. But let's understand that KISS by itself is just a blob transport, and there's more involved.
Martin. KD6YAM
So, with respect to the Direwolf interface, what in the AGW protocol is so much different? So far, there has been nothing I have done with the Direwolf AGW that I haven't done with Direwolf's KISS over TCP/IP. ?>>> On Sun, Sep 26, 2021 at 07:13 PM, John wrote: > I would
like to be able to write a program on a Raspberry Pi that receives APRS
packets from direwolf,
> makes some decisions based upon those packets,
and then has direwoldf transmit other packets
> under program control. I
also want to use hamlib to do such things as set frequency etc.
Using
KISS over TCP/IP, I have received packets from Direwolf, decoded those
packets, acted on those packets, and sent packets back to Direwolf for transmitting.? I have even help others use decoded KISS packets from Direwolf to aim satellite antennas at a balloon.
On Sun, Sep 26, 2021 at 22:14, Martin Cooper KISS by itself just provides an envelope and encoding for arbitrary data, and says nothing about what kind of data is inside that envelope. Encoding and decoding the data contained in a KISS packet is by agreement between client and server on what the packets contain. Without a higher level protocol / API that defines the contents, KISS has no concept?of, for example, enabling monitoring or opening a connection. So while KISS will help you get data back and forth, you still need something else on top of it. Even if there's a commonly understood agreement on the format of the contents, that's not part of KISS itself, but another layer. KISS plus that other layer may be equivalent to AGWPE, but not KISS by itself.
Martin. KD6YAM
<snip>
|
