Using TH-D72 with ax25, no ack on connection attempt
103 views
Skip to first unread message
VE7PPE
Apr 12, 2021, 6:40:09 PM4/12/21
to pat-users
I am attempting to get a TH-D72 to access one of our local Winlink packet repeaters. Been at this for days, with no solid results.
Using Debian Bullseye on an AMD64 SBC and am quite conversant with unix-like systems. TH-D72 is plugged into the SBC via Kenwood USB cable.
udev provides the serial tty as /dev/ttyTHD72. When this is viewed in Minicom, show Rx from repeater.
Wrote script to manually setup & break-down ax25 to more systemically test my parameter changes. Includes notes on my /etc/ax25axports & /etc/default/ax25 config.
----------------------------------------------------------------
#!/usr/bin/env bash
# sets up THD72 ax25 for packet
# kill all old kissattach setups
sudo killall kissattach
# /etc/ax25/axports
# name callsign speed paclen window description
# thd72 VE7PPE-7 9600 128 2 Winlink
# /etc/default/ax25
# DEV=/dev/ttyTHD72
# HBAUD=1200
# transmits, but no ack from RMS; squelch @3, open squelch won't transmit
#./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72
#./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72 -s
# transmits, but no ack from RMS; squelch @3, open squelch won't transmit
#./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72 --baudrate 1200 -s
# won't tx; ?? shifts TH-D72 to packet96
#./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72 --baudrate 9600 -s
# HBAUD=9600
# tx, but no ack from RMS
#./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72
# tx, but no ack from RMS; squelch @3, open squelch won't transmit
#./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72 -s
# tx, but no ack from RMS; squelch @3, open squelch won't transmit
./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72 --baudrate 1200 -s
# tx, but no ack from RMS; squelch @3, open squelch won't transmit
#./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72 --baudrate 9600 -s
sudo kissattach /dev/ttyTHD72 thd72
# tried duplex half & full, still no ack
sudo kissparms -p thd72 -t 300 -l 10 -s 12 -r 80 -f n
-----------------------------------------------------------------------------------------
Tried calling tmd setup script in ax25 & directly in the script. Been all through the tmd script & has # SERIAL_SPEED B9600 as default. Tried w/o calling tmd script.
HBAUD ==> tried both 1200 & 9600 in ax25, same results, though docs seem to suggest that ax25 HBAUD should be the serial speed to TNC, not TNC air/rf speed. Though tmd script authour sets it at 1200 in /etc/default/ax25 [https://feeding.cloud.geek.nz/posts/using-kenwood-th-d72a-with-pat-linux-ax25/]
baud ==> 1200 passed into tmd script
Tx and Rx lights flash
Using axlisten -crap --> pat connect ax25://thd72/VE7SEP-10
thd72: fm VE7PPE to VE7YDA-10 ctl SABM+
thd72: fm VE7PPE to VE7YDA-10 ctl SABM+
thd72: fm VE7PPE to VE7YDA-10 ctl SABM+
then a disconnect
thd72: fm VE7PPE to VE7YDA-10 ctl DISC+
after disconnect happens, continues to Rx from the repeater various announcements - example:
VE7RYF-10, CRD Radio Network Post Office Local Hubbing of message and VE7RYF-6 K-Net N
ode @ 1500Ft
No ack from the server. Telnet from Pat works.
This repeater is ~2-3km away. Also tried 2 other winlink repeaters a bit further away. Using an externally hung j-pole to the TH-D72.
Got to be something simple I have over-looked. Any ideas or suggestions of where to tweak/look next to get this working?
Using Debian Bullseye on an AMD64 SBC and am quite conversant with unix-like systems. TH-D72 is plugged into the SBC via Kenwood USB cable.
udev provides the serial tty as /dev/ttyTHD72. When this is viewed in Minicom, show Rx from repeater.
Wrote script to manually setup & break-down ax25 to more systemically test my parameter changes. Includes notes on my /etc/ax25axports & /etc/default/ax25 config.
----------------------------------------------------------------
#!/usr/bin/env bash
# sets up THD72 ax25 for packet
# kill all old kissattach setups
sudo killall kissattach
# tmd710 script to initialize Kiss TNC on radio is included in /etc/default/ax25
# SERIAL_SPEED B9600
# commented out in /etc/default/ax25 until working
# used here for debugging, otherwise systemctl enable starts kissattach on boot# /etc/ax25/axports
# name callsign speed paclen window description
# thd72 VE7PPE-7 9600 128 2 Winlink
# /etc/default/ax25
# DEV=/dev/ttyTHD72
# HBAUD=1200
# transmits, but no ack from RMS; squelch @3, open squelch won't transmit
#./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72
#./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72 -s
# transmits, but no ack from RMS; squelch @3, open squelch won't transmit
#./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72 --baudrate 1200 -s
# won't tx; ?? shifts TH-D72 to packet96
#./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72 --baudrate 9600 -s
# HBAUD=9600
# tx, but no ack from RMS
#./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72
# tx, but no ack from RMS; squelch @3, open squelch won't transmit
#./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72 -s
# tx, but no ack from RMS; squelch @3, open squelch won't transmit
./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72 --baudrate 1200 -s
# tx, but no ack from RMS; squelch @3, open squelch won't transmit
#./tmd710_tncsetup/tmd710_tncsetup --band 0 --serialport /dev/ttyTHD72 --baudrate 9600 -s
sudo kissattach /dev/ttyTHD72 thd72
# tried duplex half & full, still no ack
sudo kissparms -p thd72 -t 300 -l 10 -s 12 -r 80 -f n
-----------------------------------------------------------------------------------------
Tried calling tmd setup script in ax25 & directly in the script. Been all through the tmd script & has # SERIAL_SPEED B9600 as default. Tried w/o calling tmd script.
Used 1200 & 9600 baud in various combinations between the axports, ax25 and tmd script usage.
This should be working, and most correct config?
axports ==> 9600HBAUD ==> tried both 1200 & 9600 in ax25, same results, though docs seem to suggest that ax25 HBAUD should be the serial speed to TNC, not TNC air/rf speed. Though tmd script authour sets it at 1200 in /etc/default/ax25 [https://feeding.cloud.geek.nz/posts/using-kenwood-th-d72a-with-pat-linux-ax25/]
baud ==> 1200 passed into tmd script
Tx and Rx lights flash
Using axlisten -crap --> pat connect ax25://thd72/VE7SEP-10
thd72: fm VE7PPE to VE7YDA-10 ctl SABM+
thd72: fm VE7PPE to VE7YDA-10 ctl SABM+
thd72: fm VE7PPE to VE7YDA-10 ctl SABM+
then a disconnect
thd72: fm VE7PPE to VE7YDA-10 ctl DISC+
after disconnect happens, continues to Rx from the repeater various announcements - example:
VE7RYF-10, CRD Radio Network Post Office Local Hubbing of message and VE7RYF-6 K-Net N
ode @ 1500Ft
No ack from the server. Telnet from Pat works.
This repeater is ~2-3km away. Also tried 2 other winlink repeaters a bit further away. Using an externally hung j-pole to the TH-D72.
Got to be something simple I have over-looked. Any ideas or suggestions of where to tweak/look next to get this working?
Thanks,
Peter
Dr. Torsten Harenberg
Apr 13, 2021, 2:59:59 AM4/13/21
to VE7PPE, pat-users
Hi Peter,
to see if the problem is on the HF or on the Linux/AX.25 side, I would
suggest to try the following:
can you connect to your repeater just using the terminal (completely
without Pat and the Linux AX.25)? Is no: something is still wrong with
the AX.25 setting within the TH-D72's TNC. It's been a while since I
used this kind of setup (packet radio is pretty much dead in Europe),
but I remember that TXdelay etc. needed some tweaking.
What also puzzles me a bit is your axlisten output:
pat connect ax25://thd72/VE7SEP-10
> thd72: fm VE7PPE to VE7YDA-10 ctl SABM+
> thd72: fm VE7PPE to VE7YDA-10 ctl SABM+
> thd72: fm VE7PPE to VE7YDA-10 ctl SABM+
> then a disconnect
> thd72: fm VE7PPE to VE7YDA-10 ctl DISC+
You are trying to VE7SEP-10 but actually on the AX.25 level, a
connection to VE7YDA-10 is trying to be established...?!?!
And last but lot least: did you actually set the TH-D72's TNC into kiss
mode?
If I remember corretly, it needs a
KISS ON
RESTART
to do that.
Hope that helps to narrow down the problem.
73s
Torsten DL1THM
Am 13.04.21 um 00:40 schrieb VE7PPE:
> --
> 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
> <mailto:pat-users+...@googlegroups.com>.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/pat-users/13e2ffa8-658a-4421-aac6-5df3c08b08b3n%40googlegroups.com
> <https://groups.google.com/d/msgid/pat-users/13e2ffa8-658a-4421-aac6-5df3c08b08b3n%40googlegroups.com?utm_medium=email&utm_source=footer>.
to see if the problem is on the HF or on the Linux/AX.25 side, I would
suggest to try the following:
can you connect to your repeater just using the terminal (completely
without Pat and the Linux AX.25)? Is no: something is still wrong with
the AX.25 setting within the TH-D72's TNC. It's been a while since I
used this kind of setup (packet radio is pretty much dead in Europe),
but I remember that TXdelay etc. needed some tweaking.
What also puzzles me a bit is your axlisten output:
pat connect ax25://thd72/VE7SEP-10
> thd72: fm VE7PPE to VE7YDA-10 ctl SABM+
> thd72: fm VE7PPE to VE7YDA-10 ctl SABM+
> thd72: fm VE7PPE to VE7YDA-10 ctl SABM+
> then a disconnect
> thd72: fm VE7PPE to VE7YDA-10 ctl DISC+
connection to VE7YDA-10 is trying to be established...?!?!
And last but lot least: did you actually set the TH-D72's TNC into kiss
mode?
If I remember corretly, it needs a
KISS ON
RESTART
to do that.
Hope that helps to narrow down the problem.
73s
Torsten DL1THM
Am 13.04.21 um 00:40 schrieb VE7PPE:
> 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
> <mailto:pat-users+...@googlegroups.com>.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/pat-users/13e2ffa8-658a-4421-aac6-5df3c08b08b3n%40googlegroups.com
> <https://groups.google.com/d/msgid/pat-users/13e2ffa8-658a-4421-aac6-5df3c08b08b3n%40googlegroups.com?utm_medium=email&utm_source=footer>.
VE7PPE
Apr 14, 2021, 1:02:16 PM4/14/21
to pat-users
Thanks Torsten,
RE axlisten: should have read "pat connect ax25://thd72/VE7YDA-10 " I had tried VE7VIC, VE7SEP, VE7YDA and VE7BWA.
Connecting to packet node with only TNC and Minicom:
-------------------------------------------------------------
bbRAM loaded with defaults
Kenwood Radio Modem
AX.25 Level 2 Version 2.0
Release 16/Nov/2010 2Chip Version 1.00
Checksum $7772
cmd:DA 210414091106
cmd:MY VE7PPE-7
MYCALL was NOCALL
Kenwood Radio Modem
AX.25 Level 2 Version 2.0
Release 16/Nov/2010 2Chip Version 1.00
Checksum $7772
cmd:DA 210414091106
cmd:MY VE7PPE-7
MYCALL was NOCALL
cmd:kiss
KISS OFF
cmd:c ve7sep-10
cmd:*** CONNECTED to VE7SEP-10
KISS OFF
cmd:c ve7sep-10
cmd:*** CONNECTED to VE7SEP-10
cmd:kiss
KISS OFF
cmd:kiss on
KISS was OFF
cmd:c ve7sep-10
cmd:*** CONNECTED to VE7SEP-10
KISS OFF
cmd:kiss on
KISS was OFF
cmd:c ve7sep-10
cmd:*** CONNECTED to VE7SEP-10
Fred Hillhouse Jr
May 12, 2022, 1:18:34 PM5/12/22
to pat-users
Greetings VE7PPE,
I have an interest in using my D72 for Pat. After searching for D72 and Pat I ended up here. I am new to Pat (and Winlink).
I am a bit confused. I can't tell if you were successful or not.
Is this what you ended up with?
pat connect ax25://thd72/VE7YDA-10
I have a local node K1EHZ-10 (7 km distance). If you were correct, then this may work? Of course this assumes I have whatever other layers there are correct.
pat connect ax25://thd72/K1EHZ-10
pat connect ax25://thd72/K1EHZ-10
Reply all
Reply to author
Forward
0 new messages