Direwolf/Pat Winlink/RMS Connection Problem

[Michael LaBlanc]

Pat Users,

I have had a Ham Technician license for many years, but have been away from the hobby with other life priorities.  I now find myself with some quality time to spend getting back into it, but I am challenged to get Winlink to work.

I am working with a very minimal setup!  I have 2 Baofeng Uv-5r radios one of which is hooked up to a Raspberry Pi with a homemade interface board that controls PTT.  I am using the latest Direwolf and Pat Winlink software with packet at 1200 baud. 

I have been using one radio hooked up to the Pi to attempt to interact with the message server and have been listening on the other radio.  I do hear what sounds like 1200 baud modem noises coming both from my radio and my local RMS named K2DLL-10.

Here is a copy/paste of the Pat Winlink log and the Direwolf log.  Pat Winlink seems to say that I can't establish the initial connection with K2DLL-10?  Any suggestions you might have would be greatly appreciated. Is anyone aware of references where I can look up the commands that are being sent back and forth to establish the connection to better understand where things are breaking down? 

Thank you so much for anything you can do to help me out.

Mike

KC2EHR 

Pat Winlink Log
2021/03/21 20:38:49 Starting HTTP service (0.0.0.0:5000)...
2021/03/21 20:39:37 Connecting to K2DLL-10 (ax25)...
2021/03/21 20:40:22 Unable to establish connection to remote: Dial timeout

Direwolf Log
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)

K2DLL-10 audio level = 97(13/8)   [NONE]   _____||__
[0.5] K2DLL-10>KC2EHR:(I cmd, n(s)=0, n(r)=0, p=0, pid=0xf0)[WL2K-5.0-B2FWIHJM$]<0x0d>

K2DLL-10 audio level = 59(11/7)   [NONE]   _____|___
[0.5] K2DLL-10>KC2EHR:(I cmd, n(s)=1, n(r)=0, p=0, pid=0xf0);PQ: 21654520<0x0d>

K2DLL-10 audio level = 104(22/13)   [NONE]   _____||__
[0.5] K2DLL-10>KC2EHR:(I cmd, n(s)=2, n(r)=0, p=0, pid=0xf0)CMS via K2DLL ><0x0d>

K2DLL-10 audio level = 131(13/8)   [NONE]   ____|||__
Audio input level is too high.  Reduce so most stations are around 50.
[0.5] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)

 

 

[Stacey Collier]

Hello, I don't know a whole lot about packet (newly started using it). But, for one your audio level seems really high.

[Michael LaBlanc]

I agree about the audio levels - I have figured out how to stabilize the audio level response from the Remote Message Server, but I am still unable to connect.  The RMS seems to be immediately issuing a DM, which I believe is a connection refused message.  Also, I noticed a message from Direwolf about needing to issue a "kissparms -c 1 -p radio" command, so I did that.  This got rid of the Direwolf message on the next restart, but I am still getting the DM messages from the RMS.  I continue to try different antennas, located in different locations.  Progress, but no success yet...

Pat Winlink Log 3/24/2021

-------------------------

pi@RaspPi4:~ $ sudo kissattach /dev/pts/8 wl2k

AX.25 port wl2k bound to device ax0

pi@RaspPi4:~ $ kissparms -c 1 -p wl2k

kissparms: socket: Operation not permitted

pi@RaspPi4:~ $ sudo kissparms -c 1 -p wl2k

pi@RaspPi4:~ $ pat http

2021/03/24 16:28:41 Starting HTTP service (0.0.0.0:5000)...

2021/03/24 16:29:14 Connecting to K2DLL-10 (ax25)...

2021/03/24 16:29:59 Unable to establish connection to remote: Dial timeout

Direwolf Log 3/24/2021

----------------------

pi@RaspPi4:~ $ sudo direwolf -p

Dire Wolf version 1.6

Includes optional support for:  hamlib cm108-ptt

Reading config file direwolf.conf

Audio device for both receive and transmit: plughw:2,0  (channel 0)

Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.

Ready to accept AGW client application 0 on port 8000 ...

Ready to accept KISS TCP client application 0 on port 8001 ...

Virtual KISS TNC is available on /dev/pts/7

Created symlink /tmp/kisstnc -> /dev/pts/7

Invalid transmit channel 8 from KISS client app.

Are you using AX.25 for Linux?  It might be trying to use a modified

version of KISS which uses the port (channel) field differently than the

original KISS protocol specification.  The solution might be to use

a command like "kissparms -c 1 -p radio" to set CRC none mode.

Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:

sudo /sbin/modprobe -q mkiss crc_force=1

<<< Data frame from KISS client application, port 8, total length = 18

  000:  80 96 64 88 98 98 40 f4 96 86 64 8a 90 a4 61 3f  ..d...@...d...a?

  010:  c9 d9                                            ..

Invalid transmit channel 2 from KISS client app.

Are you using AX.25 for Linux?  It might be trying to use a modified

version of KISS which uses the port (channel) field differently than the

original KISS protocol specification.  The solution might be to use

a command like "kissparms -c 1 -p radio" to set CRC none mode.

Another way of doing this is pre-loading the "kiss" kernel module with CRC disabled:

sudo /sbin/modprobe -q mkiss crc_force=1

<<< Data frame from KISS client application, port 2, total length = 18

  000:  20 96 64 88 98 98 40 f4 96 86 64 8a 90 a4 61 3f   .d...@...d...a?

  010:  24 20                                            $ 

[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)

KC2EHR audio level = 0(0/0)   [NONE]   ||||_____

[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)

K2DLL-10 audio level = 50(20/21)   [NONE]   |||||____

[0.2] K2DLL-10>KC2EHR:(DM res, f=0)

[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)

KC2EHR audio level = 0(0/0)   [NONE]   ||||_____

[0.1] KC2EHR>K2DLL-10:(DISC cmd, p=1)

[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)

KC2EHR audio level = 0(0/0)   [NONE]   ||||_____

[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)

K2DLL-10 audio level = 50(20/21)   [NONE]   ||||||___

[0.2] K2DLL-10>KC2EHR:(DM res, f=0)

[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)

KC2EHR audio level = 10(10/10)   [NONE]   ||||_____

[0.1] KC2EHR>K2DLL-10:(SABM cmd, p=1)

K2DLL-10 audio level = 50(21/21)   [NONE]   |||||____

[0.2] K2DLL-10>KC2EHR:(DM res, f=0)

[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)

KC2EHR audio level = 0(0/0)   [NONE]   |||||____

[0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)

K2DLL-10 audio level = 49(20/21)   [NONE]   |||||____

[0.2] K2DLL-10>KC2EHR:(DM res, f=0)

[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)

KC2EHR audio level = 0(3/3)   [NONE]   |||||____

[0.2] KC2EHR>K2DLL-10:(DISC cmd, p=1)

[Michael LaBlanc]

I have made some progress and now have good audio levels and am getting stable call/response between my home radio setup and the RMS.

However, it seems like my station calls for SAMB, then the RMS returns with the expected RR (ready to receive), but my station ignores this

and sends another SAMB anyway.  Then the RMS sends a DM (Disconnect) command.

Any ideas why my station is not continuing on with the connection steps after the RR command from the RMS?

Thanks in advance for your help.

Mike

KC2EHR

Direwolf Log 3/25/2021

---------------------------------

pi@RaspPi4:~ $ sudo direwolf -p
Dire Wolf version 1.6
Includes optional support for:  hamlib cm108-ptt

Reading config file direwolf.conf
Audio device for both receive and transmit: plughw:2,0  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate / 3.

Note: PTT not configured for channel 0. (Ignore this if using VOX.)

Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...

Virtual KISS TNC is available on /dev/pts/2
Created symlink /tmp/kisstnc -> /dev/pts/2

[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)

KC2EHR audio level = 0(0/0)   [NONE]   _|||_____

[0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)

K2DLL-10 audio level = 55(22/23)   [NONE]   |||||____
[0.2] K2DLL-10>KC2EHR:(RR cmd, n(r)=0, p=1)

[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)

KC2EHR audio level = 2(6/7)   [NONE]   |||||____

[0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)

K2DLL-10 audio level = 55(22/23)   [NONE]   |||||____

[0.2] K2DLL-10>KC2EHR:(DM res, f=0)
[0L] KC2EHR>K2DLL-10:(SABM cmd, p=1)

KC2EHR audio level = 0(0/0)   [NONE]   |||||____
[0.2] KC2EHR>K2DLL-10:(SABM cmd, p=1)

K2DLL-10 audio level = 54(21/23)   [NONE]   ||||||___

[0.2] K2DLL-10>KC2EHR:(DM res, f=0)

[0L] KC2EHR>K2DLL-10:(DISC cmd, p=1)

KC2EHR audio level = 0(1/1)   [NONE]   |||||____

[0.2] KC2EHR>K2DLL-10:(DISC cmd, p=1)

[Jim Weisgram KJ7DMV]

Have you tried more than one gateway?

Sometimes a gateway can be unresponsive or hung up in some way.

>> Jim

--
You received this message because you are subscribed to the Google Groups "pat-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pat-users+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/f80806a5-ad55-4e27-97d4-c644a2b0935dn%40googlegroups.com.

[Mark Avery]

Mike,

Winlink over packet is very timing sensitive. I tried unsuccessfully to use a UV-5R to connect. Part of the problem is the eighth second delay (about 0.125 sec) in transition between transmit and receive modes. (I wasn't aware of that delay at the time.) The radio seems to not respond instantly to PTT. You might be able to adjust the modem timing values to make sure the radio is transmitting before the packet starts, then hope the RMS will delay long enough for your radio to switch back after. We have one in the area I can connect to with a BTECH UV-24X4 (has the same problem), another that I can't. I have a Yaesu FT3D that works just fine with both RMS gateways, one each on VHF and UHF as long as I connect to the external antenna on the roof - the VHF RMS is a bit farther away. The UHF gateway is at the local club and the manager intentionally inserted delays to make it a little more forgiving. That also makes it take quite a bit longer to get the same messages through.

I like trying to work with minimalist systems, and a Yaesu FT3D absolutely does NOT qualify. There are some better radios with faster response time but without the hefty pricetag. If you add a quarter to half second to the delays in the software modem settings, that might help. That's what it took to get any connection at all with the BTECH radio, but it didn't work with the standard high speed/low drag settings the RMS usually uses. Could be worth a try.

73 and good luck!

Mark KE8NHT

[David R. Andersen]

Mark, Mike et. al.

Regarding using a Baofeng UV-5R for packet: a few years ago I wrote up
a description of a PTT circuit that I've had excellent luck with for
Winlink and APRS using that radio. Here's a link to my description:

https://k0rx.com/blog/2017/11/baofeng.html

73,
Dave, K0RX

>--
>You received this message because you are subscribed to the Google Groups "pat-users" group.
>To unsubscribe from this group and stop receiving emails from it, send an email to pat-users+...@googlegroups.com.

>To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/a3fdcf26-9f9c-418c-8fa3-002e4e0def62n%40googlegroups.com.


--
int x=90560580,y=32678;main(){putchar(x);x>>=y&7;y>>=3;return y?main():0;}
Contact info: https://k0rx.com/contact/

Quis custodiet ipsos custodes?

-----BEGIN RANDOM OR NOT?-----

Xlw6cB4j0/cUYCnrpcb8OKZC6zb2+4Q03cLrMKtfuywXYJGuycgTtnR/lBT7gvSJ
ZJ80bhfZPou88qtptZMTK1lxDPLFTOCdbSePvAXl35UEGXGy9nUEIk54W7vtqI0R
UxcLBV8dbEhOyMfX2PIGuvl65vg0AaQd6FJn0MlgmRGKJVrC8kefaNA3qPGhk+Pc
-----END RANDOM OR NOT?-----

[Michael LaBlanc]

Today I successfully connected to my local 1200 baud, packet Remote Message Server about 10 times and was able to both send and receive email messages.

What allowed me to do this was to swap out the Baofeng UV-5R for a 21 year old Kenwood TNC.  I used the exact same antenna, in the exact same spot and left the software configuration for the Pi, Pat Winlink, and Direwolf the same.

I know some folks have been successful with the UV-5R's on packet, but the 2 Baofeng's that I own (purchased from Amazon about 2 years ago) did not seem to be up to the task.

I want to send out a HUGE THANKS to everyone that responded with all your helpful suggestions.  As I am just returning to the Ham Radio hobby after a long absence, it is totally inspiring to find a vibrant community willing to help out a newbie.

Thanks again,

Mike

KC3EHR

[Michael LaBlanc]

CORRECTION -

   I swaped out the Baofeng UV-5R for a 21 year old Kenwood HT

   NOT a TNC

You received this message because you are subscribed to a topic in the Google Groups "pat-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pat-users/V13HKOadb_0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pat-users+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/11931359-3975-4037-a7a1-4b8193eadbe0n%40googlegroups.com.