Winlink Email Server help

[Peter Sichel]

I'm trying to setup a Winlink Email Server (digip2 + digirig) and connect to it from the Pat Winlink Email Client running on another DigiPi (digipi + IC-705).

The Winlink Email Server is up and connecting to the Winlink system but the Pat Email client fails to connect.  I'm attaching the server syslog and would appreciate any insight on what I'm missing.

I see the digirig reporting the audio level from the radio is too high but don't believe this preventing the connection since it is connecting to the Winlink system.

Is there any published guidance for debugging such problems?

Thanks and 73, Peter K1AV

 

[Peter Sichel]

After more research and testing I can see the problem but have not yet identified the solution.

### The Pat Email Client is sending the connection request:
2024-06-09T19:40:56.540092+01:00 digipi pat[4392]: 2024/06/09 19:40:56 QSY ax25+linux: 145050
2024-06-09T19:40:59.614595+01:00 digipi pat[4392]: 2024/06/09 19:40:59 Connecting to K1AV-10 (ax25+linux)...
2024-06-09T19:40:59.997832+01:00 digipi direwolf.node.sh[4498]: [0L] K1AV>BEACON:K1AV-4 Linux Node http://digipi.org/
2024-06-09T19:41:00.000279+01:00 digipi direwolf.node.sh[4498]: [0L] K1AV>K1AV-10:(SABM cmd, p=1)
2024-06-09T19:41:11.326832+01:00 digipi direwolf.node.sh[4498]: [0L] K1AV>K1AV-10:(SABM cmd, p=1)
2024-06-09T19:41:31.206304+01:00 digipi direwolf.node.sh[4498]: [0L] K1AV>K1AV-10:(SABM cmd, p=1)
2024-06-09T19:41:44.621694+01:00 digipi pat[4392]: 2024/06/09 19:41:44 Unable to establish connection to remote: Dial timeout
2024-06-09T19:41:44.837010+01:00 digipi direwolf.node.sh[4498]: [0L] K1AV>K1AV-10:(DISC cmd, p=1)
2024-06-09T19:41:45.623337+01:00 digipi pat[4392]: 2024/06/09 19:41:45 QSX ax25+linux: 145050.000

### The server is receiving the connection request, connects to the Winlink system and responds it is ready:

2024-06-09T19:41:00.954810+01:00 digipi2 direwolf.winlink.sh[1114]: [0L] K1AV-10>K1AV:(I cmd, n(s)=1, n(r)=0, p=1, pid=0xf0)This is K1AV-10 DigiPi.<0x0a>
2024-06-09T19:41:11.788846+01:00 digipi2 direwolf.winlink.sh[1114]: K1AV audio level = 158(25/26)    ___||____
2024-06-09T19:41:11.789232+01:00 digipi2 direwolf.winlink.sh[1114]: Audio input level is too high.  Reduce so most stations are around 50.
2024-06-09T19:41:11.789495+01:00 digipi2 direwolf.winlink.sh[1114]: [0.3] K1AV>K1AV-10:(SABM cmd, p=1)
2024-06-09T19:41:11.896956+01:00 digipi2 direwolf.winlink.sh[1114]: [0L] K1AV-10>K1AV:(RR cmd, n(r)=0, p=1)

I can hear the response from the Winlink Gateway on the IC-705, but the Pat Email client is not seeing them.

This suggests a couple possibilities:

1. The responses from the Winlink Email Server are failing to decode.  I tried increasing the TXDELAY in direwolf.tnc.conf to 50 thinking the T/R switching on my Yaesu FT-60 + digirig might be too slow.  Is there some other radio setting that likely needs adjustment?

2. Some configuration that routes the AX.25 response to the Pat Email client isn't set properly.

I'd welcome any guidance on how to test each possibility and hopefully correct it.  Is it common for VHF HTs like the FT-60 to have trouble sending responses?  I have an IC-2300H I can also try as the Winlink Gateway radio. 

73, Peter K1AV

[Craig]

Can the pat station receive any packets from anything else?  tune to
APRS, for example, and see if it decodes anything?

From the logs, it looks like the pat station is transmitting, but
doesn't hear anything.

-craig
KM6LYW

[Peter Sichel]

The Pat station (DigiPi + IC-705) works with ARDOP.  Since yesterday I tried the IC-2300 on the Winlink Server side and got the same result so I suspect the Pat station is not receiving AX.25 packets.  My thinking is to examine each link in the connection chain to see where the packets are being dropped, so I want to look at the AX.25 receive packet log if there is such a thing, or the next closest log.

- Peter

K1AV

[Craig]

Based on your logs, the problem seems to be in the direwolf/audio chain.  I don't see
direwolf reporting anything.  Again, I'd tune to 144.390 (in america) for a moment
and see if direwolf decodes anything.

--
You received this message because you are subscribed to the Google Groups "DigiPi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digipi+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/digipi/03c8525a-61eb-4926-996b-c4464ca65ff2n%40googlegroups.com.

[Peter Sichel]

I'm not seeing any APRS traffic or call signs on the mini-display despite hearing it in on the IC-705.

I've used this same DigiPi to make QSOs on FT8 and JS8 Call so I believe the audio connection to the radio via USB is working.

The DigiPi version is 1.8-3 and the IC-705 mode is set to FM-D.  Packets from the Pat client (named "DigiPi") are being received and recognized on the Winlink server (named "DigiPi2").  So it appears to be related to the direwolf audio receive chain with the IC-705.  I can try receiving APRS on DigiPi2 (digirig to Yaesu FT-60) but my area is normally pretty quiet on APRS so I'm not sure the FT-60 will hear much.

[Craig]

okay, great info.

Is there possibly more than one audio device?  direwolf will use the
first one in /proc/asound/cards .  USB audio
typically has priority.   click "PktLog" on the DigiPi home page to see
the direwolf log, the top of it will tell you
audio information  (or "cat /run/direwolf.node.log").   It'd be really
cool if you could transmit an aprs packet
with a spare HT to test.

-craig
KM6LYW

[Peter Sichel]

There are no other audio devices attached to the DigiPi.  Just the Pi Zero W2 and  miniPiTFT.

###Here’s the PktLog from DigiPi(0) IC-705

Connect to IGate server noam.aprs2.net (44.135.208.225) failed.

Now connected to IGate server noam.aprs2.net (44.25.16.4)

Check server status here http://44.25.16.4:14501

[ig] K1AV-2>APDW17:!R9:o+<Iv{&  ! DigiPi http://digipi.org/

[ig] # aprsc 2.1.14-g5e22b37

[ig] # logresp K1AV-2 verified, server T2USANW

### PktLog from DigiPi2, FT-60

Connect to IGate server noam.aprs2.net (44.135.208.225) failed.

Connect to IGate server noam.aprs2.net (199.204.38.35) failed.

Connect to IGate server noam.aprs2.net (173.242.239.99) failed.

Now connected to IGate server noam.aprs2.net (167.114.2.176)

Check server status here http://167.114.2.176:14501

[ig] # aprsc 2.1.14-g5e22b37

[ig] # logresp K1AV-2 verified, server T2CAWEST

[ig] K1AV-2>APDW17:!R9:o+<Iv{&  ! DigiPi http://digipi.org/

————

It’s probably something simple I’m overlooking.  Thanks for your help.

[Peter Sichel]

Finally got back to debugging my DigiPi Winlink Email Server configuration after Field Day and wanted to let you know it's working great.  I'll write some notes to share my experience and post a link here when they're available.

Over the course of a few months I went from knowing very little about Winlink to operating a Winlink Email Server on VHF packet with a couple DigiPi's and 2m FM capable radios I had on hand.  I also used Winlink Express with VARA HF during Field Day to earn 200 bonus points.

Gateway: IC-2300H, KB9VBR J-pole, DigiPi v1.8.3 running Winlink Email Server ($50), DigiRig with cables for Icom radio ($80).

Client used for testing: IC-705 and 2nd DigiPi running Pat Winlink Email Client and Linux Node AX.25.

Total cost excluding radios was under $200.

73, Peter K1AV