AGW vs. KISS over IP


Rob Giuliano
 

I have mentioned issues with log windows and KISS ports over IP.  Now I was able to try a few things with 2 active channels on 1 sound card that actually interface with APRSIS32, but as 2 ports.  I am confused as to a few things:
1.  Why AGW does not TX on the Right channel, but KISS_IP does?
2.  Logging acts different in AGW than in KISS_IP.
3.  Logging acts differently for KISS_IP if radio is connected to the sound card channel?

Lots of info, but I hope it help find reasons.

Configuration:
I purchased the FePi sound card (stereo output and stereo input board that is a "hat" for the Pi), and the Nexus DR-X (digital radio cross patch).  The Nexus provides 2 "data jacks" that are designed to have access to the left LineIn/LineOut and connect them to different radios.  The Nexus Pi Distro provides drivers and many digital mode applications - including Direwolf. 

With this setup, I run 2 separate instances of Direwolf (separate terminals and configurations).
One uses the left audio channel, the other uses the right.

Observations:
As I was experimenting with this configuration, I noticed that if I connect to them using AGW, the right side does not go into TX.  If I switch to KISS over IP, everything works properly.

I think the TX issue is something in my setup.  HOWEVER, in trying to troubleshoot the issue, I setup 4 ports and enable logging on each:
1.  DW_KISS_Lt             IP  8010
2.  DW_KISS_Rt            IP  8011
3.  DW_AGW_Lt        AGW  8000
4.  DW_AGW_Rt        AGW  8001

If I enable only 1 and 2, clear the log window, and hit <Transmit>
   everything looks normal, both TX as expected.  Neither post anything to the log.
   If I disconnect the radio from the left - Left logs.  (Same with only Left connect to radio - Rt logs)
   If I disconnect both from the radio, Both log.
If I enable only 3 and 4, clear the log window, and hit <Transmit>
   Left TX, but Right No.  Both log.  Entries: L:2 R:3.
   Extra Rt entry:
      Port(DW_AGW_Rt):2020-10-23T03:00:56.711 AGW:Need 892547120 Data, Have 180 / 892547156 Bytes

Only 3:
Port(DW_AGW_Lt):2020-10-23T03:27:51.457 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>@032751h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Lt):2020-10-23T03:27:53.479 AGW:AX.25-rPort[0] KB8RCO>APWW11,WIDE2-2:@032751h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!

Only 4:  No TX!!
   Log:
Port(DW_AGW_Rt):2020-10-23T03:25:08.447 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>@032508h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-23T03:25:22.451 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>@032522h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!

If I enable only 2 and 3, clear the log window, and hit <Transmit>
   Left TX (pause) Right TX. Both log.  Entries: L:2 R:1
If I enable only 1 and 4, clear the log window, and hit <Transmit>
   Left TX, Right No. Both log.  Entries:  L:2 R:4

Example from the AGW log (bold is start of line):
Port(DW_AGW_Rt):2020-10-23T03:13:00.457 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>@031300h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-23T03:13:01.872 Read 90 bytes after 144198 msec (up from 68187) vs 0 Quiet
Port(DW_AGW_Rt):2020-10-23T03:13:01.873 AGW:Need 858797872 Data, Have 630 / 858797908 Bytes
[630]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@030703h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0 C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@030750h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0 C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@030807h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0 C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@030820h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0 C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@030927h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0 C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@031036h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0 C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@031300h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>

Robert Giuliano
KB8RCO


Rob Giuliano
 

Ignore me - messed up right side AGW port.  I Had it swapped with IP.
I knew the data looked strange.

Issue is only logging. KISS IP shows received data, but no TX data when a radio is connected.

Robert Giuliano
KB8RCO



On Thursday, October 22, 2020, 11:52:33 PM EDT, Rob Giuliano via groups.io <kb8rco@...> wrote:


I have mentioned issues with log windows and KISS ports over IP.  Now I was able to try a few things with 2 active channels on 1 sound card that actually interface with APRSIS32, but as 2 ports.  I am confused as to a few things:
1.  Why AGW does not TX on the Right channel, but KISS_IP does?
2.  Logging acts different in AGW than in KISS_IP.
3.  Logging acts differently for KISS_IP if radio is connected to the sound card channel?

Lots of info, but I hope it help find reasons.

Configuration:
I purchased the FePi sound card (stereo output and stereo input board that is a "hat" for the Pi), and the Nexus DR-X (digital radio cross patch).  The Nexus provides 2 "data jacks" that are designed to have access to the left LineIn/LineOut and connect them to different radios.  The Nexus Pi Distro provides drivers and many digital mode applications - including Direwolf. 

With this setup, I run 2 separate instances of Direwolf (separate terminals and configurations).
One uses the left audio channel, the other uses the right.

Observations:
As I was experimenting with this configuration, I noticed that if I connect to them using AGW, the right side does not go into TX.  If I switch to KISS over IP, everything works properly.

I think the TX issue is something in my setup (CONFIRMED!!!)
HOWEVER, in trying to troubleshoot the issue, I setup 4 ports and enable logging on each:
1.  DW_KISS_Lt             IP  8010
2.  DW_KISS_Rt            IP  8011
3.  DW_AGW_Lt        AGW  8000
4.  DW_AGW_Rt        AGW  8001

1.  DW_KISS_Lt             IP  8001
2.  DW_KISS_Rt            IP  8011
3.  DW_AGW_Lt        AGW  8000
4.  DW_AGW_Rt        AGW  8010

If I enable only 1 and 2, clear the log window, and hit <Transmit>
   everything looks normal, both TX as expected.  Neither post anything to the log.
   If I disconnect the radio from the left - Left logs.  (Same with only Left connect to radio - Rt logs)
   If I disconnect both from the radio, Both log.
If I enable only 3 and 4, clear the log window, and hit <Transmit>
   Operates as expected.

Robert Giuliano
KB8RCO


Michael Wright
 

I played around a little with AGW, but DireWolf works for me.

I also want to say thanks for helping all the customers with this product!

Mike K6MFW


Rob Giuliano
 

Just to be clear,  AGW is a sound card TNC application, but includes a specific 'AX.25 style' IP protocol.
I was not using AGW computer application, but running Direwolf and using its AGW protocol between Pi (Direwolf) and PC (APRSIS32).

In direwolf_left.conf the port settings were:
#############################################################
#               VIRTUAL TNC SERVER PROPERTIES               #
#############################################################
# Dire Wolf acts as a virtual TNC and can communicate with
#   client applications by different protocols:
#       - the "AGW TCPIP Socket Interface" - default port 8000
#       - KISS protocol over TCP socket - default port 8001
#       - KISS TNC via pseudo terminal   (-p command line option)
AGWPORT 8000
KISSPORT 8001


In direwolf-right.conf the port settings were:
#############################################################
#               VIRTUAL TNC SERVER PROPERTIES               #
#############################################################
# Dire Wolf acts as a virtual TNC and can communicate with
#   client applications by different protocols:
#       - the "AGW TCPIP Socket Interface" - default port 8000
#       - KISS protocol over TCP socket - default port 8001
#       - KISS TNC via pseudo terminal   (-p command line option)
AGWPORT 8010
KISSPORT 8011


To test the AGW protocol to/from APRSIS32 and more importantly, investigate my concern about the logging,
I created 2 AGW RF port with settings of:
   Type:            AGW     This is the communication protocol between device and APRSIS32.
   IP or DNS:    pi3         hostname for my Pi3 on the local network
   Port:              8000     First port's 'Port' setting to get data from the left side audio
    or  Port:        8010     Second port's 'Port' setting to get data from the right side audio

Then disable those 2 ports and created 2 new using straight KISS over IP
   Type:            IP                          This is the communication protocol between device and APRSIS32.
   IP or DNS:    pi3         hostname for my Pi3 on the local network
   Port:              8001     First port's 'Port' setting to get data from the left side audio
    or  Port:        8011     Second port's 'Port' setting to get data from the right side audio

Most of the sound card TNC emulators offer the option of communicating with the AGW protocol. 

Robert Giuliano
KB8RCO



On Friday, October 23, 2020, 12:20:10 AM EDT, Michael Wright <mfwright@...> wrote:


I played around a little with AGW, but DireWolf works for me.

I also want to say thanks for helping all the customers with this product!

Mike K6MFW