¿ªÔÆÌåÓý

  1. Direwolf
  2. Messages
Expanded Topics Messages Polls
Date
Re: Can serial kiss channel be forced to 0?

 

Hi Graeme,

I finally opted for publishing a small blog post describing the setup.? Feel free to use it or not ;)


--
Geoffrey F4FXL /? KC3FRA
My Direwolf stuff :

Re: decoding winlink packets

 

¿ªÔÆÌåÓý


Hello Bob,

If I can pipe the sound into direwolf can it decode winlink packets?

It depends on what you mean by "Winlink packets".? Traditional Winlink traffic is just 1200bps AFSK connected mode packet traffic and Direwolf can decode that no problem.? That AX.25 traffic decoding will be shown in text command window but it wouldn't be shown in say the MS Windows Winlink application.


145.01 MHz is supposed to have winlink, but I'm only seeing aprs packets decoded.

What specific frequencies are used for Winlink traffic depends on your regional bandplan but the standard Winlink frequency in the US is 145.630.? You can see the most popular frequencies by going to:

?? --> change the radial button to "packet" and then click on "center frequency"


Then I heard something about winlink Wednesdays, so maybe winlink is only on Wednesday? Or might the digipeater be able to send both aprs and winlink packets as needed (on the same day)?

APRS, Winlink, and other applications use AX.25 packet radio as their protocol and all AX.25 digipeaters and nodes can support all of this traffic.? The challenge is hopefully keep different applications on their own unique frequencies to avoid overloading the frequency, etc.? This is what your regional bandplan is trying to do.

--David
KI6ZHD
Re: decoding winlink packets

 

I have several systems where I use Direwolf to decode packet for Winlink.? But note, Winlink uses a publicly available compression method on the text of the message contents, so you will not see plain text for the majority of the Winlink message exchange.? Also Winlink is a connection oriented mode, so any packet digipeater used for Winlink most likely will not work for APRS.? ?The main program used is Winlink Express and is developed for Windows only.? Though there are many folks who brave the waters and force it to work on Linux and Macs via emulators or virtual machines.? I've successfully been able to simultaneously run both VARA FM and DireWolf assigned to the same sound card on my UHF/VHF RMS Gateways.

Packet for Winlink is nearly a deprecated mode, as the majority of users these days are using VARA FM instead? ?I've seen the usage of packet drop from 100% to around 25% of the? UHF/VHF traffic I receive.? A licensed copy of Vara can pass data with nearly 8 time more throughput than Packet for larger messages.? I've regularly sent a 50K photo attachment in a Winlink Session lasting about a minute.? Many software TNC based Winlink gateways that support packet, use UZ7HO SoundModem rather than DireWolf for the packet engine.? ??

Winlink Wednesday is a specific net where participants send a check-in to the Net Control via Winlink tools (see https://winlinkwednesday.net/) on Wednesday of every week.? It was one of the first Winlink Nets and has a large following.? ?If you are interested in learning Winlink operations I recommend the Monthly training exercises that are provided by EmComm-Training.org (https://emcomm-training.org/index.html).? Or, watch the videos provided by WaveTalkers at https://wavetalkers.com/resources/digital/winlink.php they provide detail information on installation and setup of a Winlink Station as well as overviews of the software.

Brian - W7OWO
Re: Can serial kiss channel be forced to 0?

 

¿ªÔÆÌåÓý


Hello Graeme,

Beyond all the soluitions that are being shared, can you explain WHY you need this feature?? I'm curious what you're doing that needs such a "unique" feature.

--David
KI6ZHD


On 06/26/2024 01:03 AM, Graeme Small wrote:

Thanks Geoffrey for your info.? However as I now have my solution working I'll stay with it unless problems arise later, even though it uses a modified kissutil for the extra output, being the serial port.? I found that kissutil and hence my extended version needs either a transmit-from directory or a terminal otherwise it terminates virtually immediately, so I've given it one to keep it happy.? Yes, I'm using the enhanced DW 1.7 KISSPORT to send ch2 to another port with the channel already changed to ch0.

I can easily switch radios to make whichever one I want to be on ch0 so that messages generated by aprsdroid go out over the desired network depending on what rx and tx frequencies the HF radio is set to use if it is switched on. I toggle between split and not split for the HF aprs frequency on the display so that my tbeacon commentcmd script knows which radio I want to be on ch0 and restarts DW with the appropriate config file if not already using it.
The OPi isn't using a BT dongle, instead running another package that handles the BT connection. One of my sons set it up quite a few years ago, including the scripts to restart DW, but I endeavour to make my own desired enhancements.

Graeme VK2HFG


On 26/06/2024 4:21 pm, Geoffrey Merck wrote:

Hi,

I had a similar issue and ended up solving it using a simple "multiplexing" shell script listening on port 8004 for aprsdroid and replicating to port 8001 and 8002 toward direwolf. The other way around it gets packets from port 8001 and 8002 and push them to aprsdroid on port 8004.

If you configure ports like this in Direwolf, it just ignores the tnc port being specified on the kiss frame.

# VHF:
KISSPORT 8001 0
# HF
KISSPORT 8002 2

Additionaly I do not use BT through Direwolf serial. I have another script forwarding port 8004 to Bluetooth.

I do not have my Orange Pi handy right now, I will post the files later.

Here is a rough block diagram of how it works.



--
Geoffrey F4FXL /? KC3FRA
My Direwolf stuff :



decoding winlink packets

Bob
 

If I can pipe the sound into direwolf can it decode winlink packets? 145.01 MHz is supposed to have winlink, but I'm only seeing aprs packets decoded. Then I heard something about winlink Wednesdays, so maybe winlink is only on Wednesday? Or might the digipeater be able to send both aprs and winlink packets as needed (on the same day)?
Re: Can serial kiss channel be forced to 0?

 

¿ªÔÆÌåÓý

Thanks Geoffrey for your info.? However as I now have my solution working I'll stay with it unless problems arise later, even though it uses a modified kissutil for the extra output, being the serial port.? I found that kissutil and hence my extended version needs either a transmit-from directory or a terminal otherwise it terminates virtually immediately, so I've given it one to keep it happy.? Yes, I'm using the enhanced DW 1.7 KISSPORT to send ch2 to another port with the channel already changed to ch0.

I can easily switch radios to make whichever one I want to be on ch0 so that messages generated by aprsdroid go out over the desired network depending on what rx and tx frequencies the HF radio is set to use if it is switched on. I toggle between split and not split for the HF aprs frequency on the display so that my tbeacon commentcmd script knows which radio I want to be on ch0 and restarts DW with the appropriate config file if not already using it.
The OPi isn't using a BT dongle, instead running another package that handles the BT connection. One of my sons set it up quite a few years ago, including the scripts to restart DW, but I endeavour to make my own desired enhancements.

Graeme VK2HFG


On 26/06/2024 4:21 pm, Geoffrey Merck wrote:

Hi,

I had a similar issue and ended up solving it using a simple "multiplexing" shell script listening on port 8004 for aprsdroid and replicating to port 8001 and 8002 toward direwolf. The other way around it gets packets from port 8001 and 8002 and push them to aprsdroid on port 8004.

If you configure ports like this in Direwolf, it just ignores the tnc port being specified on the kiss frame.

# VHF:
KISSPORT 8001 0
# HF
KISSPORT 8002 2

Additionaly I do not use BT through Direwolf serial. I have another script forwarding port 8004 to Bluetooth.

I do not have my Orange Pi handy right now, I will post the files later.

Here is a rough block diagram of how it works.



--
Geoffrey F4FXL /? KC3FRA
My Direwolf stuff :


Re: Can serial kiss channel be forced to 0?

 

Hi,

I had a similar issue and ended up solving it using a simple "multiplexing" shell script listening on port 8004 for aprsdroid and replicating to port 8001 and 8002 toward direwolf. The other way around it gets packets from port 8001 and 8002 and push them to aprsdroid on port 8004.

If you configure ports like this in Direwolf, it just ignores the tnc port being specified on the kiss frame.

# VHF:
KISSPORT 8001 0
# HF
KISSPORT 8002 2

Additionaly I do not use BT through Direwolf serial. I have another script forwarding port 8004 to Bluetooth.

I do not have my Orange Pi handy right now, I will post the files later.

Here is a rough block diagram of how it works.



--
Geoffrey F4FXL /? KC3FRA
My Direwolf stuff :

Re: Can serial kiss channel be forced to 0?

 

The mission has been accomplished. My enhanced kissutil caters for a new command-line parameter -O followed by the output serial port name and minor additional code in conjunction with KISSPORT 8002 2 in the DW configuration, without any need for channel or other data modification. Speed needed to be set using the -s parameter to match that in use by DW.? I didn't provide separate speeds for the optional serial TCP input and serial output but that could easily be provided by a extra command-line parameter, eg -S.
Re: #direwolf #direwolf

[email protected]
 

Thank you so so much David that replied help me so much, i also modified the source code of atest to also save just the decoded frame. I modified the hex dump function in the ax25_pad.c file to also save the frames separately.?
Re: Can serial kiss channel be forced to 0?

 

My latest thought is to create an application based on kissutil source, running continuously to read from tcp port 8001 to which only radio channel 2 data has been sent by using KISSPORT 8001 2 in the DW configuration file. The records will already have the channel changed to 0 so the application can output unmodified KISS records to the serial port.
Re: Can serial kiss channel be forced to 0?

 

¿ªÔÆÌåÓý

Thanks Wojtek for replying and for your program source.? I only fumble my way around Unix and C so I've forwarded your code for comment to one of my sons, a Unix specialist and who initially set-up my tracker. My background is IBM mainframe from nearly 30 years ago so of not much use these days.

I've confirmed that by specifying KISSPORT 8001 2 in my DW 1.7 config and running kissutil using the default 8001 port that ch2 gets changed to ch0 in the generated records. However I would still need to get the records into KISS format and onto the KISS serial port if a 2nd program can indeed write to the port.

Graeme

On 23/06/2024 7:09 pm, Wojtek SP9WPN wrote:

Hi Graeme,

I had similar problem and ended up with dirty workaround, source attached. Maybe you can adapt it to your needs.

Wojtek SP9WPN

Re: Can serial kiss channel be forced to 0?

 

Hi Graeme,

I had similar problem and ended up with dirty workaround, source attached. Maybe you can adapt it to your needs.

Wojtek SP9WPN

kiss_change_channel.c
kiss_change_channel.c

Can serial kiss channel be forced to 0?

 

I'm wanting data from 2 radios running on an Orange Pi to be processed by APRSdroid connected via the serial kiss (BT) facility where APRSdroid ignores other than ch0. Is there a way to achieve this without modifying Direwolf or APRSdroid source?
I currently cause a particular radio to be on ch0 by an automated Direwolf restart using a different configuration file, swapping between VHF and HF depending on whether I'm in a VHF area or not.
Forcing ch0 could be achieved if the channel number in the serial kiss output (kissserial.c) was modified to always set to 0 in the same manner as kissnet.c can now force ch0 for a tnc kiss port, being a simple user modification.? Neither REGEN nor KISSUTIL support R0 as a to-channel.
I acknowledge that data generated by APRSdroid would only be sent to the radio currently on ch0.? No position beacons are created by APRSdroid, but messages could be sent.
My requirement might not be common enough to warrant the addition of a new Direwolf feature such as another parameter on the SERIALKISSPOLL statement to force ch0, unless of course one already exists!
Thanks,
Graeme VK2HFG
Re: #direwolf #direwolf

 

¿ªÔÆÌåÓý


Hi, would anyone know how I would save the frame that is decoded with atest? Currently atest -B 9600 -h only prints out the frames, I was wondering if there is a simple way to save the decoded frames? Thanks!

If you read the man page on "atest", if gives you an example of how to generate a test file and later decode that test file.? Are you looking to save the decoded text like shown below into a file?? If so, you could just use:

?? atest -B 9600 -h test9.wav > test9-wav-decoded.txt


Maybe you're wanting something like saving to a pcap file (readable by tcpdump, wireshark, etc?)

--David
KI6ZHD


?? gen_packets -B 9600 -o test9.wav
?? --
?? Data rate set to 9600 bits / second.
?? Using scrambled baseband signal rather than AFSK.
?? Output file set to test9.wav
?? built in message...
?? --

?? atest -B 9600 -h test9.wav
?? --
?? 44100 samples per second.? 16 bits per sample.? 1 audio channels.
?? 32576 audio bytes in file.? Duration = 0.4 seconds.
?? Fix Bits level = 0
?? Channel 0: 9600 baud, K9NG/G3RUH,? , 44100 sample rate x 3.
?? The ratio of audio samples per sec (44100) to data rate in baud (9600) is 4.6
?? This is on the low side for best performance.? Can you use a higher sample rate?
?? For example, can you use 48000 rather than 44100?

?? DECODED[1] 0:00.091 WB2OSZ-15 audio level = 50(+33/-33)????
?? [0] WB2OSZ-15>TEST:,The quick brown fox jumps over the lazy dog!? 1 of 4
?? ------
?? U frame UI: p/f=0, No layer 3 protocol implemented., length = 69
? ? dest??? TEST??? 0 c/r=1 res=3 last=0
? ? source? WB2OSZ 15 c/r=1 res=3 last=1
? ?? 000:? a8 8a a6 a8 40 40 e0 ae 84 64 9e a6 b4 ff 03 f0? ....@@...d......
? ?? 010:? 2c 54 68 65 20 71 75 69 63 6b 20 62 72 6f 77 6e? ,The quick brown
? ?? 020:? 20 66 6f 78 20 6a 75 6d 70 73 20 6f 76 65 72 20?? fox jumps over
? ?? 030:? 74 68 65 20 6c 61 7a 79 20 64 6f 67 21 20 20 31? the lazy dog!? 1
? ?? 040:? 20 6f 66 20 34??????????????????????????????????? of 4
?? ------

?? DECODED[2] 0:00.183 WB2OSZ-15 audio level = 50(+33/-33)????
?? [0] WB2OSZ-15>TEST:,The quick brown fox jumps over the lazy dog!? 2 of 4
?? ------
?? U frame UI: p/f=0, No layer 3 protocol implemented., length = 69
? ? dest??? TEST??? 0 c/r=1 res=3 last=0
? ? source? WB2OSZ 15 c/r=1 res=3 last=1
? ?? 000:? a8 8a a6 a8 40 40 e0 ae 84 64 9e a6 b4 ff 03 f0? ....@@...d......
? ?? 010:? 2c 54 68 65 20 71 75 69 63 6b 20 62 72 6f 77 6e? ,The quick brown
? ?? 020:? 20 66 6f 78 20 6a 75 6d 70 73 20 6f 76 65 72 20?? fox jumps over
? ?? 030:? 74 68 65 20 6c 61 7a 79 20 64 6f 67 21 20 20 32? the lazy dog!? 2
? ?? 040:? 20 6f 66 20 34??????????????????????????????????? of 4
?? ------

?? DECODED[3] 0:00.275 WB2OSZ-15 audio level = 50(+33/-33)????
?? [0] WB2OSZ-15>TEST:,The quick brown fox jumps over the lazy dog!? 3 of 4
?? ------
?? U frame UI: p/f=0, No layer 3 protocol implemented., length = 69
? ? dest??? TEST??? 0 c/r=1 res=3 last=0
? ? source? WB2OSZ 15 c/r=1 res=3 last=1
? ?? 000:? a8 8a a6 a8 40 40 e0 ae 84 64 9e a6 b4 ff 03 f0? ....@@...d......
? ?? 010:? 2c 54 68 65 20 71 75 69 63 6b 20 62 72 6f 77 6e? ,The quick brown
? ?? 020:? 20 66 6f 78 20 6a 75 6d 70 73 20 6f 76 65 72 20?? fox jumps over
? ?? 030:? 74 68 65 20 6c 61 7a 79 20 64 6f 67 21 20 20 33? the lazy dog!? 3
? ?? 040:? 20 6f 66 20 34??????????????????????????????????? of 4
?? ------

?? DECODED[4] 0:00.368 WB2OSZ-15 audio level = 50(+33/-33)????
?? [0] WB2OSZ-15>TEST:,The quick brown fox jumps over the lazy dog!? 4 of 4
??? ------
?? U frame UI: p/f=0, No layer 3 protocol implemented., length = 69
? ? dest??? TEST??? 0 c/r=1 res=3 last=0
? ? source? WB2OSZ 15 c/r=1 res=3 last=1
? ?? 000:? a8 8a a6 a8 40 40 e0 ae 84 64 9e a6 b4 ff 03 f0? ....@@...d......
? ?? 010:? 2c 54 68 65 20 71 75 69 63 6b 20 62 72 6f 77 6e? ,The quick brown
? ?? 020:? 20 66 6f 78 20 6a 75 6d 70 73 20 6f 76 65 72 20?? fox jumps over
? ?? 030:? 74 68 65 20 6c 61 7a 79 20 64 6f 67 21 20 20 34? the lazy dog!? 4
? ?? 040:? 20 6f 66 20 34??????????????????????????????????? of 4
?? ------


?? 4 from test9.wav
?? 4 packets decoded in 0.010 seconds.? 36.5 x realtime
?? --



--David
KI6ZHD
#direwolf #direwolf

[email protected]
 

Hi, would anyone know how I would save the frame that is decoded with atest? Currently atest -B 9600 -h only prints out the frames, I was wondering if there is a simple way to save the decoded frames? Thanks!
Re: EAS2APRS integration

 



On Sun, Jun 16, 2024 at 12:07?PM David Ranch via <direwolf-groupsio=[email protected]> wrote:

Hello John,


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.

Yes, this is what I want to do. In fact I have been doing precisely this for approximately 2 years now.? My desire is to replace the radio link running on computer A (where direwolf+kisutil+eas2aprs+dsame is currently operating) with a tcp connection to aprx on computer B. I am aware that I could do all this in DW; my assumption was that this would be straightforward. The problem, I think, resides with aprx. I can see errors reported as a result of the simple addition we have tried in aprx.conf to enable the TCP KISS interface. I have inquired in the aprx forum re: how to fix the aprx.conf file, but have not yet received a response.
If I don't figure out soon how to configure aprx correctly to enable the TCP connection. I will abandon the effort.

I'm still missing your goal by making this change.? What are you hoping to have ComputerB+APRX do that ComputerA+Direwolf does not?? Maybe it's just the location of ComputerB is preferred?? Maybe you're hoping that APRX can do some things that Direwolf cannot?

Btw.. you mentioned you reported this issue to the APRX forum.? Looking that up, I see: ? Looking at the detail there, what is your "MYCALL" setting in the eas.conf file that direwolf is using?? Is that where the conflicting callsign is coming from?

David,
the same configuration-related? error occurs when I startup aprx on computer B even it computer A is off. .....
My original assumption (clearly wrong) was that it would be easy to implement the tcp connection that would bring the converted eas packet (converted by DW+dsame+kissutil+eas2aprs.py) to the aprx digi, since the radio attached to computer A is now dead. In the long run it is a goal to have all of this running on a single computer. I am at the point where the effort to perform that task now seems less than trying to get the TCP connection to work.

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.

I don't see why a "split" is warranted. The same TCP port 8001 enabled by DW is used routinely by YAAC and other applications. I don't understand...

As I understand it, you want to receive incoming EAS data on one KISS-TCP connection (from Direwolf), process and re-format that data, and then send it OUT a different KISS-TCP connection for transmission (to APRX).? A single instance of the kissutil program running doesn't support that.? Expanding on this thought, maybe it's possible to have TWO instances of kissutil running using the "-h" parameter and have the second instance try to support the connection to APRX.? I don't think this will work though as kissutil isn't designed to be a KISS-TCP server.. it's intended to be a client.? As I mentioned before, maybe other tools like KISS muxes like might work here but it gets complex very quickly.

--David
KI6ZHD
Re: EAS2APRS integration

 

¿ªÔÆÌåÓý


Hello John,


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.

Yes, this is what I want to do. In fact I have been doing precisely this for approximately 2 years now.? My desire is to replace the radio link running on computer A (where direwolf+kisutil+eas2aprs+dsame is currently operating) with a tcp connection to aprx on computer B. I am aware that I could do all this in DW; my assumption was that this would be straightforward. The problem, I think, resides with aprx. I can see errors reported as a result of the simple addition we have tried in aprx.conf to enable the TCP KISS interface. I have inquired in the aprx forum re: how to fix the aprx.conf file, but have not yet received a response.
If I don't figure out soon how to configure aprx correctly to enable the TCP connection. I will abandon the effort.

I'm still missing your goal by making this change.? What are you hoping to have ComputerB+APRX do that ComputerA+Direwolf does not?? Maybe it's just the location of ComputerB is preferred?? Maybe you're hoping that APRX can do some things that Direwolf cannot?

Btw.. you mentioned you reported this issue to the APRX forum.? Looking that up, I see: ? Looking at the detail there, what is your "MYCALL" setting in the eas.conf file that direwolf is using?? Is that where the conflicting callsign is coming from?



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.

I don't see why a "split" is warranted. The same TCP port 8001 enabled by DW is used routinely by YAAC and other applications. I don't understand...

As I understand it, you want to receive incoming EAS data on one KISS-TCP connection (from Direwolf), process and re-format that data, and then send it OUT a different KISS-TCP connection for transmission (to APRX).? A single instance of the kissutil program running doesn't support that.? Expanding on this thought, maybe it's possible to have TWO instances of kissutil running using the "-h" parameter and have the second instance try to support the connection to APRX.? I don't think this will work though as kissutil isn't designed to be a KISS-TCP server.. it's intended to be a client.? As I mentioned before, maybe other tools like KISS muxes like might work here but it gets complex very quickly.

--David
KI6ZHD
Re: Direwolf CM108 Debug Message on Startup

 

John,

Thanks for acknowleging this report, always gratifying to help spot a bug and air it out!

Love Direwolf and appreciate all you do to make it the outstanding platform that it is.

-Chris
Re: EAS2APRS integration

 

David,
some points of clarification below.
Thanks, John

On Sat, Jun 15, 2024 at 2:59?PM David Ranch via <direwolf-groupsio=[email protected]> wrote:

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.

Yes, this is what I want to do. In fact I have been doing precisely this for approximately 2 years now.? My desire is to replace the radio link running on computer A (where direwolf+kisutil+eas2aprs+dsame is currently operating) with a tcp connection to aprx on computer B. I am aware that I could do all this in DW; my assumption was that this would be straightforward. The problem, I think, resides with aprx. I can see errors reported as a result of the simple addition we have tried in aprx.conf to enable the TCP KISS interface. I have inquired in the aprx forum re: how to fix the aprx.conf file, but have not yet received a response.
If I don't figure out soon how to configure aprx correctly to enable the TCP connection. I will abandon the effort.


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.

I don't see why a "split" is warranted. The same TCP port 8001 enabled by DW is used routinely by YAAC and other applications. I don't understand...



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
Re: Direwolf CM108 Debug Message on Startup

 

Thank you for pointing this out.
It has been fixed and will be in the next release.

73,
John WB2OSZ
861 - 880 of 10462