开云体育

Hello John,

just another possibility to consider. eas2aprs.py specifies channel 0 as the output for the aprs packet constructed from reading the eas input created by the sdr.

Stepping back a moment, I re-read your original email and I think I was confused.? Are you wanting to do what this following this doc proposes or are you trying to do something different?

??


I ask because your original email specifically wanted to use APRX and I had assumed you wanted it to connect to the remote Direwolf KISS-TCP interface.? That won't be enough to convert the EAS message into an APRS packet.? The above URL talks about the other needed glue including kiss-util (comes with Direwolf), eas2aprs.py (different Git project), and dsame.py (different Git project).? The secret sauce in this one document's approach is the kiss-util command which silently DEFAULTS to connecting to a KISS-TCP port on *locahost* of the current machine but also creates a software "shared memory" connector which the eas2aprs.py + dsame programs do all the protocol translation.

So.. understanding all that... why are you wanting to use APRX to support your project goal?? Best I can tell, Direwolf should be able to do all of this w/o APRX but I have a concern with your design.? You specifically want to receive KISS-TCP packets from Computer-A but you want to *transmit* them from Computer-B.? I don't think that the kissutil program can support that split RX vs. TX KISS-TCP role.? Your original email stated:

?? "For the time being, I wish to maintain the 2 computer setup; EAS reception and processing on computer A, with aprs digipeating and internet gating on computer B. There are a number of reasons for the 2 computer setup; unless I am advised that this is not possible, I would to continue with that plan"


I believe there are other KISS-TCP "mux" programs out there that could be considered to see if you could split the KISS packet traffic but I think it will greatly complicate the setup.

Does the TCP port receive output when DW has no output for a receive-only device?

Yes.. direwolf will always allow remote KISS-TCP connections as long as it's configured to do so.? The actual traffic that comes/goes through that port is secondary.?

Is there a way in direwolf config to construct a second device that receives input from eas2aprs.py and produces output on the TCP port?

eas2aprs.py interacts with direwolf only via the kissutil program.?

--David
KI6ZHD