Re: Connecting APRSIS32 to APRX or DIXPRS


Rob Giuliano
 

Thanks for the clarification.  I was actually thinking that APRX 'listened' and when APRSIS32 tried to connect, it would do so.  But as usual, you are correct.  Neither does. 

You can connect from APRX to APRSIS32 through as the APRSIS32 local-server.
  I have never looked at whether APRX can have more than 1 APRS-IS server configuration.
  I tried it.  I didn't get an error, but it appears it only connects to the first instance.

The other WRT54 application I was using at the time was 'ldsped' by ON7LDS
It is somewhere between AGW and APRX in that it includes AGW ports for remote connections to TNCs. I think it was a little more difficult to get setup, but that must have been what I used.
I think I read there was a version for the Pi.  I am not sure if it is still in development, but the page was still active.

Robert Giuliano
KB8RCO



On Friday, February 19, 2021, 1:22:29 PM EST, Lynn Deffenbaugh <kj4erj@...> wrote:


APRSISCE/32 does not accept incoming connections from TNCs or other external devices.  APRSISCE/32 expects the device to be listening for an incoming connection that APRSISCE/32 will initiate.

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


On 2/19/2021 12:19 PM, Rob Giuliano via groups.io wrote:
The last time I used APRX was with my WRT54, so it is a bit rusty.

First, you want Simply(KISS) in APRSIS32 because you will not need any <OpenCmd> or <ClosseCmd> commands for this port configuration.
  The other ports (KISS and radio specific) have defined information that is sent to properly initialize the TNC.

Your interface is trying to connect to itself (localhost).
I am pretty sure you want that interface to connect to APRSIS32.

# This port tries to connect to your APRSIS32 application - assumed on another computer.
# I am not sure what APRX will do if that application (port) is not open.  I assume wait for it.
<interface>
      tcp-device   {APRSIS32 IP} 8100    KISS
      callsign     iw2ejh-14
      tx-ok true
</interface>

# This port connects to your TNC2 - assumed already functioning.
<interface>
      serial-device {device settings per APRX manual}
      callsign     iw2ejh-1        {for referencing below, use your current settings}
      {All your related settings for the TNC2 ??}
</interface>

# Send all received packets from TNC2 to APRSIS32
<digipeater>
      transmitter iw2ejh-1
      <source>
            source iw2ejh-14
      </source>
</digipeater>

# Send all received packets (according to the port configuration) from APRSIS32 to TNC2
<digipeater>
      transmitter iw2ejh-14
      <source>
            source iw2ejh-1
      </source>
</digipeater>

I am pretty sure that was how I had it working on my WRT54.  I tried to find copies of my old aprx.conf files from back then, but I am sure they are long gone.

Join APRSISCE@groups.io to automatically receive all group messages.