Hi Graeme,

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

Wojtek SP9WPN

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 :

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 :

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 :

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 :