AGW (logs TX) vs. KISS over IP (TX not in log)


Rob Giuliano
 

Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


Lynn Deffenbaugh
 

Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


Rob Giuliano
 

So not logging the TX on teh IP port is by design?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 4:56:37 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


Lynn Deffenbaugh
 

Possibly not by design, but probably by accident.  One of these days I need to revisit the port logging to make it more consistent.

In the meantime, sometimes the Transmit log can help, at least to determine if it is internal, -IS, RF, or both.  Not sure if you can tell from it which actual RF ports it was transmitted over.

Are you sure it actually transmitted or tried to transmit over the KISS over TCP/IP port?

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 5:25 PM, Rob Giuliano via groups.io wrote:
So not logging the TX on teh IP port is by design?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 4:56:37 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


Rob Giuliano
 

Yes, it transmits when the RF port is KISS over IP.
I have transmited on the KISS over IP port alone and heasr the packet back from a local DIGI.
I enabled all 3 ports to show that it was the only one that doesn't place the TX information in the log.
Normally, I never use both protocols to the same device. 

This started when I was having trouble with a KISS over IP port, but the logs didn't show I was transmitting.
That TNC was not "near by" the APRSIS32 instance, so I tried going back and forth between rooms.


Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 5:32:19 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Possibly not by design, but probably by accident.  One of these days I need to revisit the port logging to make it more consistent.

In the meantime, sometimes the Transmit log can help, at least to determine if it is internal, -IS, RF, or both.  Not sure if you can tell from it which actual RF ports it was transmitted over.

Are you sure it actually transmitted or tried to transmit over the KISS over TCP/IP port?

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 5:25 PM, Rob Giuliano via groups.io wrote:
So not logging the TX on teh IP port is by design?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 4:56:37 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


Lynn Deffenbaugh
 

If you still have the KISS over IP port configured, check for the latest development version (2020/10/27 18:38) and see if an enabled trace log shows Sent packets.  I'm not sure I put it in the right place, but hopefully I did!

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 5:38 PM, Rob Giuliano via groups.io wrote:
Yes, it transmits when the RF port is KISS over IP.
I have transmited on the KISS over IP port alone and heasr the packet back from a local DIGI.
I enabled all 3 ports to show that it was the only one that doesn't place the TX information in the log.
Normally, I never use both protocols to the same device. 

This started when I was having trouble with a KISS over IP port, but the logs didn't show I was transmitting.
That TNC was not "near by" the APRSIS32 instance, so I tried going back and forth between rooms.


Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 5:32:19 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Possibly not by design, but probably by accident.  One of these days I need to revisit the port logging to make it more consistent.

In the meantime, sometimes the Transmit log can help, at least to determine if it is internal, -IS, RF, or both.  Not sure if you can tell from it which actual RF ports it was transmitted over.

Are you sure it actually transmitted or tried to transmit over the KISS over TCP/IP port?

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 5:25 PM, Rob Giuliano via groups.io wrote:
So not logging the TX on teh IP port is by design?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 4:56:37 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


Rob Giuliano
 

Yep.
Logging the TX now on the KISS over IP port and AGW port.
Seeing both the TX and RX from a local DIGI.

I know that with 2 channels on an AGW port APRSIS32 can only TX on the first channel.
  With my Nexus setup, I can run 2 instances of the AGW app (Direwolf or UZ7OH) and have 2 ports.

I assume the same limitation exists for KISS over IP?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 6:44:02 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


If you still have the KISS over IP port configured, check for the latest development version (2020/10/27 18:38) and see if an enabled trace log shows Sent packets.  I'm not sure I put it in the right place, but hopefully I did!

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 5:38 PM, Rob Giuliano via groups.io wrote:
Yes, it transmits when the RF port is KISS over IP.
I have transmited on the KISS over IP port alone and heasr the packet back from a local DIGI.
I enabled all 3 ports to show that it was the only one that doesn't place the TX information in the log.
Normally, I never use both protocols to the same device. 

This started when I was having trouble with a KISS over IP port, but the logs didn't show I was transmitting.
That TNC was not "near by" the APRSIS32 instance, so I tried going back and forth between rooms.


Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 5:32:19 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Possibly not by design, but probably by accident.  One of these days I need to revisit the port logging to make it more consistent.

In the meantime, sometimes the Transmit log can help, at least to determine if it is internal, -IS, RF, or both.  Not sure if you can tell from it which actual RF ports it was transmitted over.

Are you sure it actually transmitted or tried to transmit over the KISS over TCP/IP port?

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 5:25 PM, Rob Giuliano via groups.io wrote:
So not logging the TX on teh IP port is by design?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 4:56:37 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


Lynn Deffenbaugh
 

If multiple channels come over a single port connection as is typical with the AGW protocol, then yes, APRSIS32 only supports transmitting on the "first" channel.

If the sound card TNC supplies different ports for each channel, as I believe I saw in your DireWolf configuration, then a KISS over IP connection will be able to transmit on each individually configured port in APRSIS32.  At least, I think it should work that way!  I have never configured a multi-port DireWolf to test it.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 10:53 PM, Rob Giuliano via groups.io wrote:
Yep.
Logging the TX now on the KISS over IP port and AGW port.
Seeing both the TX and RX from a local DIGI.

I know that with 2 channels on an AGW port APRSIS32 can only TX on the first channel.
  With my Nexus setup, I can run 2 instances of the AGW app (Direwolf or UZ7OH) and have 2 ports.

I assume the same limitation exists for KISS over IP?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 6:44:02 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


If you still have the KISS over IP port configured, check for the latest development version (2020/10/27 18:38) and see if an enabled trace log shows Sent packets.  I'm not sure I put it in the right place, but hopefully I did!

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 5:38 PM, Rob Giuliano via groups.io wrote:
Yes, it transmits when the RF port is KISS over IP.
I have transmited on the KISS over IP port alone and heasr the packet back from a local DIGI.
I enabled all 3 ports to show that it was the only one that doesn't place the TX information in the log.
Normally, I never use both protocols to the same device. 

This started when I was having trouble with a KISS over IP port, but the logs didn't show I was transmitting.
That TNC was not "near by" the APRSIS32 instance, so I tried going back and forth between rooms.


Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 5:32:19 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Possibly not by design, but probably by accident.  One of these days I need to revisit the port logging to make it more consistent.

In the meantime, sometimes the Transmit log can help, at least to determine if it is internal, -IS, RF, or both.  Not sure if you can tell from it which actual RF ports it was transmitted over.

Are you sure it actually transmitted or tried to transmit over the KISS over TCP/IP port?

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 5:25 PM, Rob Giuliano via groups.io wrote:
So not logging the TX on teh IP port is by design?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 4:56:37 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


Rob Giuliano
 

Idon't want to make this too confusing, but a single instance of Direwolf does not allow 2 separate ports.

However the Nexus DR-X implementation on the Raspberry Pi allows for separating the 2 audio channels (left & right) which allows 2 instances of Direwolf to run and become separate RF connections on APRSIS32.

I sure wish Direwolf offered the AGW and KISS over IP ports on a per port basis.
It is kind of like you DIGI, outside the port settings so applies to all.

Robert Giuliano
KB8RCO



On Wednesday, October 28, 2020, 10:08:43 AM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


If multiple channels come over a single port connection as is typical with the AGW protocol, then yes, APRSIS32 only supports transmitting on the "first" channel.

If the sound card TNC supplies different ports for each channel, as I believe I saw in your DireWolf configuration, then a KISS over IP connection will be able to transmit on each individually configured port in APRSIS32.  At least, I think it should work that way!  I have never configured a multi-port DireWolf to test it.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 10:53 PM, Rob Giuliano via groups.io wrote:
Yep.
Logging the TX now on the KISS over IP port and AGW port.
Seeing both the TX and RX from a local DIGI.

I know that with 2 channels on an AGW port APRSIS32 can only TX on the first channel.
  With my Nexus setup, I can run 2 instances of the AGW app (Direwolf or UZ7OH) and have 2 ports.

I assume the same limitation exists for KISS over IP?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 6:44:02 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


If you still have the KISS over IP port configured, check for the latest development version (2020/10/27 18:38) and see if an enabled trace log shows Sent packets.  I'm not sure I put it in the right place, but hopefully I did!

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 5:38 PM, Rob Giuliano via groups.io wrote:
Yes, it transmits when the RF port is KISS over IP.
I have transmited on the KISS over IP port alone and heasr the packet back from a local DIGI.
I enabled all 3 ports to show that it was the only one that doesn't place the TX information in the log.
Normally, I never use both protocols to the same device. 

This started when I was having trouble with a KISS over IP port, but the logs didn't show I was transmitting.
That TNC was not "near by" the APRSIS32 instance, so I tried going back and forth between rooms.


Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 5:32:19 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Possibly not by design, but probably by accident.  One of these days I need to revisit the port logging to make it more consistent.

In the meantime, sometimes the Transmit log can help, at least to determine if it is internal, -IS, RF, or both.  Not sure if you can tell from it which actual RF ports it was transmitted over.

Are you sure it actually transmitted or tried to transmit over the KISS over TCP/IP port?

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 5:25 PM, Rob Giuliano via groups.io wrote:
So not logging the TX on teh IP port is by design?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 4:56:37 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO