
Basil Gunn
It looks like you didn't follow the instructions from the 'Getting Started Guide' here: https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-StartedYou need to follow those instructions specifically: cd cd n7nix/config sudo su ./app_config.sh core This configures AX.25, Direwolf, systemd and a few other things for you. Please read the 'Getting Started Guide' /Basil Craig McVeay <cmcveay@gmail.com> writes:
toggle quoted messageShow quoted text
Basil, Thank you for the quick reply.
*results of AX.25-status* Status for direwolf.service: RUNNING and ENABLED Status for ax25dev.service: RUNNING and ENABLED Status for ax25dev.path: RUNNING and ENABLED Status for ax25-mheardd.service: NOT RUNNING and ENABLED Status for ax25d.service: NOT RUNNING and ENABLED AX.25 device: ax0 not configured AX.25 device: ax1 not configured
It looks like I have to configure the ports so I'll be looking for the instructions on that part. If it helps, I'll be running an Alinco DR-135T on one side and an IC-7200 on the other.
*Here are the results of ifconfig* eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether b8:27:eb:88:93:0f txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.59 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::85c7:f539:b08a:58a6 prefixlen 64 scopeid 0x20<link> ether b8:27:eb:dd:c6:5a txqueuelen 1000 (Ethernet) RX packets 821 bytes 146045 (142.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 445 bytes 83615 (81.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
73, Craig
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Mon, Nov 4, 2019 at 11:19 AM Basil Gunn <basil@pacabunga.com> wrote:
Did you start AX.25? cd cd bin sudo su ./ax25-start
As user pi or whatever your default user name is please post the console output of:
ax25-status and ifconfig
/Basil
Craig McVeay <cmcveay@gmail.com> writes:
Working on getting WINLINK RMS application running on my DRAWS. The image is up and running and I suspect I am nearly there but, I am a noob to Linux so I'm stuck. I went through the setup and configuration from N7NIX and here's where I am now.
Setup: DRAWS HAT on RPi 3B+, 32GB Micro SD running headless. Powered through the HAT, connected to the internet via WiFi.
When I run "tail -f /var/log/rms.debug", I get the following:
Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov 4 08:46:02 n0csmdraws rmsgw_aci[1680]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Nov 4 2019 (DM26sf)
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Nov 4 09:17:02 n0csmdraws rmsgw_aci[3584]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
I've tried two cables on each port with the same results. I'm obviously missing something but I'm not sure what.
Thank you, Craig N0CSM
|
|
Basil, Thank you for the quick reply.
results of AX.25-status Status for direwolf.service: RUNNING and ENABLED Status for ax25dev.service: RUNNING and ENABLED Status for ax25dev.path: RUNNING and ENABLED Status for ax25-mheardd.service: NOT RUNNING and ENABLED Status for ax25d.service: NOT RUNNING and ENABLED AX.25 device: ax0 not configured AX.25 device: ax1 not configured
It looks like I have to configure the ports so I'll be looking for the instructions on that part. If it helps, I'll be running an Alinco DR-135T on one side and an IC-7200 on the other.
Here are the results of ifconfig eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether b8:27:eb:88:93:0f txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.1.59 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::85c7:f539:b08a:58a6 prefixlen 64 scopeid 0x20<link> ether b8:27:eb:dd:c6:5a txqueuelen 1000 (Ethernet) RX packets 821 bytes 146045 (142.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 445 bytes 83615 (81.6 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
73, Craig
toggle quoted messageShow quoted text
On Mon, Nov 4, 2019 at 11:19 AM Basil Gunn < basil@...> wrote:
Did you start AX.25?
cd
cd bin
sudo su
./ax25-start
As user pi or whatever your default user name is please post the console
output of:
ax25-status
and
ifconfig
/Basil
Craig McVeay <cmcveay@...> writes:
> Working on getting WINLINK RMS application running on my DRAWS. The image is up and running and I suspect I am nearly there but, I am a noob to Linux so I'm stuck. I went through the setup and configuration from N7NIX and here's where I am now.
>
> Setup: DRAWS HAT on RPi 3B+, 32GB Micro SD running headless. Powered through the HAT, connected to the internet via WiFi.
>
> When I run "tail -f /var/log/rms.debug", I get the following:
>
> Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
> Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
> Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
> Nov 4 08:46:02 n0csmdraws rmsgw_aci[1680]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
> Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Nov 4 2019 (DM26sf)
> Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0)
> Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable
> Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 is DOWN -- not updated
> Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
> Nov 4 09:17:02 n0csmdraws rmsgw_aci[3584]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
>
> I've tried two cables on each port with the same results. I'm obviously missing something but I'm not sure what.
>
> Thank you,
> Craig
> N0CSM
|
|

Basil Gunn
Did you start AX.25? cd cd bin sudo su ./ax25-start
As user pi or whatever your default user name is please post the console output of:
ax25-status and ifconfig
/Basil
Craig McVeay <cmcveay@gmail.com> writes:
toggle quoted messageShow quoted text
Working on getting WINLINK RMS application running on my DRAWS. The image is up and running and I suspect I am nearly there but, I am a noob to Linux so I'm stuck. I went through the setup and configuration from N7NIX and here's where I am now.
Setup: DRAWS HAT on RPi 3B+, 32GB Micro SD running headless. Powered through the HAT, connected to the internet via WiFi.
When I run "tail -f /var/log/rms.debug", I get the following:
Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel: N0CSM-10 on udr0 is DOWN -- not updated Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors Nov 4 08:46:02 n0csmdraws rmsgw_aci[1680]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1 Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Nov 4 2019 (DM26sf) Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0) Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 is DOWN -- not updated Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors Nov 4 09:17:02 n0csmdraws rmsgw_aci[3584]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
I've tried two cables on each port with the same results. I'm obviously missing something but I'm not sure what.
Thank you, Craig N0CSM
|
|

Basil Gunn
direwolf is a daemon & is controlled by systemd as is the preferred method for controlling daemons that usually start from boot.
The scripts to start/stop/status direwolf & the ax.25 interface are:
cd cd bin sudo su ./ax25-status ./ax25-start ./ax25-stop
You can also look at the direwolf daemon status like this:
systemctl status direwolf
The icon in the RPi menus for direwolf comes from the standard direwolf install and should be deleted.
If you have done a core configuration as described in the 'Getting Started Guide' then the direwolf binary is in directory /usr/local/bin and the configuration file is in /etc ie. /usr/local/bin/direwolf /etc/direwolf.conf
/Basil
Dave Christensen <dkc2030@gmail.com> writes:
toggle quoted messageShow quoted text
I installed NWDR14. I have not spent much time with DRAWS and in fact have no radios hooked up right now (working on that). So this project has been "benchware" for me. I did bring up FLDigi and it looked familiar to my PC version.
When I clicked on Other>Direwolf I get a message "Failed to change to directory "/root" (Permission denied)" I looked at the shortcut properties and see that the working directory is /root. Is this a problem or can it be fixed?
Thanks and 73 Dave - KD7UM
|
|
Working on getting WINLINK RMS application running on my DRAWS. The image is up and running and I suspect I am nearly there but, I am a noob to Linux so I'm stuck. I went through the setup and configuration from N7NIX and here's where I am now.
Setup: DRAWS HAT on RPi 3B+, 32GB Micro SD running headless. Powered through the HAT, connected to the internet via WiFi.
When I run "tail -f /var/log/rms.debug", I get the following:
Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel: N0CSM-10 on udr0 is DOWN -- not updated Nov 4 08:46:01 n0csmdraws rmsgw_aci[1680]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors Nov 4 08:46:02 n0csmdraws rmsgw_aci[1680]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1 Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: N0CSM-10 - Linux RMS Gateway ACI 2.5.1 Nov 4 2019 (DM26sf) Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 (145050000 Hz, mode 0) Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: /usr/local/bin/rmschanstat ax25 udr0 N0CSM-10 reports unavailable Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel: N0CSM-10 on udr0 is DOWN -- not updated Nov 4 09:17:01 n0csmdraws rmsgw_aci[3584]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors Nov 4 09:17:02 n0csmdraws rmsgw_aci[3584]: python script /usr/local/etc/rmsgw/updateversion.py failed, status 1
I've tried two cables on each port with the same results. I'm obviously missing something but I'm not sure what.
Thank you, Craig N0CSM
|
|
I installed NWDR14. I have not spent much time with DRAWS and in fact have no radios hooked up right now (working on that). So this project has been "benchware" for me. I did bring up FLDigi and it looked familiar to my PC version.
When I clicked on Other>Direwolf I get a message "Failed to change to directory "/root" (Permission denied)" I looked at the shortcut properties and see that the working directory is /root. Is this a problem or can it be fixed?
Thanks and 73 Dave - KD7UM
|
|
Re: PlymouthD error when running RMSCHANSTAT
Thanks again Basil!
Im not quite ready to upgrade everything.
Im currently running Stretch, and dont foresee the available time to
install the new version just yet.
But....
You did aim me at the right place for that error.
apt-get purge plymouth*
(I only SSH into this pi, so no need for plymouth)
and a reboot nets :
root@k5ktf-10:~# sudo -u rmsgw rmschanstat ax25 0 K5KTF-10
channel 0 with callsign K5KTF-10 on interface ax0 up
and
sudo -u rmsgw /usr/local/bin/rmsgw_aci
channel 0 with callsign K5KTF-10 on interface ax0 up
and
Nov 3 22:29:29 localhost rmsgw_aci[508]: K5KTF-10 - Linux RMS
Gateway ACI 2.5.0 Dec 10 2018 (EM10bm)
Nov 3 22:29:29 localhost rmsgw_aci[508]: Channel: K5KTF-10 on 0
(145730000 Hz, mode 0)
Nov 3 22:29:40 localhost updatechannel.py[528]: Posting channel
record updates for K5KTF-10...
Nov 3 22:29:41 localhost rmsgw_aci[508]: Channel Stats: 1 read, 1
active, 0 down, 1 updated, 0 errors
Nov 3 22:29:52 localhost updateversion.py[533]: Version update for
K5KTF-10 to version 2.5.0 successful.
Nov 3 22:32:53 localhost rmsgw_aci[568]: K5KTF-10 - Linux RMS
Gateway ACI 2.5.0 Dec 10 2018 (EM10bm)
Nov 3 22:32:53 localhost rmsgw_aci[568]: Channel: K5KTF-10 on 0
(145730000 Hz, mode 0)
Nov 3 22:32:53 localhost rmsgw_aci[568]: Channel Stats: 1 read, 1
active, 0 down, 0 updated, 0 errors
With plymouth* gone, its working now without any complaints.
And it may have been, but throwing those errors falsely?
Dunno, but looks good for now.
Ill remember the upgrades are ready and waiting for when I have some
time.
Thanks again!
Jim
At 10:56 AM 11/3/2019, Basil Gunn wrote:
Hi Jim,
We probably should have been posting our conversations over on the
Linux
RMS Gateway forum on yahoo groups since this has not much to do with
the
udrc. But let's keep going here as I think I know what your problem
is.
The plymouthd daemon is the app which provides the graphical
"splash"
screen when booting. It is the owner of the console device. I always
run
my Linux RMS Gateways headless (without plymouth) so I have never
seen
this error before.
The thing that jumps out at me is that you are not using the latest
version of Linux RMS Gateway. During the last transition of Linux
Debian/Ubuntu from Jessie to Buster there were a lot of changes that
broke the RMS Gateway python scripts ie. ifconfig output changed.
Those
problems have been fixed in the latest 2.5.1 release of Linux RMS
Gateway which lives here:
https://github.com/nwdigitalradio/rmsgw
The other thing that could be wrong are file permissions used by
those
scripts. If you have ever run rmschanstat or rmsgw_aci as a user
other
than rmsgw it creates files that have incompatible owner:group
permissions. Normally the program rmsgw_aci is run from a crontab
owned
by user rmsgw. When testing I recommend running those programs shown
below. rmsgw_aci is a C program that calls the python script
rmschanstat. If rmschanstat fails, rmsgw_aci will also fail.
sudo -u rmsgw rmschanstat ax25 0 K5KTF-10
sudo -u rmsgw rmsgw_aci
Also check the directory & file permissions for /etc/rmsgw/stat.
It
should look similar to the following. Note that user:group is
rmsgw:rmsgw
ls -al /etc/rmsgw/stat
total 8
drwxr-sr-x 2 rmsgw rmsgw 4096 Aug 19 20:25 .
drwxr-sr-x 4 rmsgw rmsgw 4096 Aug 5 16:52 ..
-rw-r--r-- 1 rmsgw rmsgw 0 Nov 3 07:19
.channels.udr0
-rw-r--r-- 1 rmsgw rmsgw 0 Nov 1 13:42
cms.winlink.org
-rw-r--r-- 1 rmsgw rmsgw 0 Nov 3 07:19
.version.N7NIX-10
Those HAMS setting up a Linux RMS Gateway using NW Digital Radio RPi
image won't see the problem you are describing because the latest
version of the gateway has been installed on that image. Of course
that
doesn't help you much since you are using a TNC-Pi which should work
fine after installing the latest Linux RMS Gateway.
Let me know if this fixes your problem.
/Basil n7nix
Jim Kinter Jr. via Groups.Io <jim@...>
writes:
> Thanks Basil.
> Thats what I thought at first (AX not running), but everything I
see
> says it is (as "0", not udrX...its a pi/tnc-pi ).
>
> If I use PAT web GUI on this same system (remotely), I can connect
to
> other local RMS servers just fine, so that tells me the
pi,
> TNC-Pi, network, radio, cabling, AX25, etc are all
OK..
> Right?
> So must be something specific to the RMS config? Or the plymouthd
error?
>
>
> root@k5ktf-10:~# ax25-status
> -bash: ax25-status: command not found
>
> root@k5ktf-10:~# netstat --ax25
> Active AX.25 sockets
> Dest
Source Device
State Vr/Vs
Send-Q Recv-Q
> *
K5KTF-0 ax0
LISTENING 000/000
0 0
> *
K5KTF-10 ax0
LISTENING 000/000
0 0
>
>
> root@k5ktf-10:~# ifconfig
> ax0: flags=67<UP,BROADCAST,RUNNING> mtu 256
> inet
44.128.1.10 netmask 255.0.0.0 broadcast 44.255.255.255
> ax25
K5KTF-10 txqueuelen 10 (AMPR AX.25)
> RX packets
1214 bytes 64695 (63.1 KiB)
> RX errors
0 dropped 0 overruns 0 frame 0
> TX packets
301 bytes 13346 (13.0 KiB)
> TX errors
0 dropped 0 overruns 0 carrier 0 collisions 0
>
> root@k5ktf-10:~# ps -ef |grep ax
> root 410
1 0 Nov01 ? 00:00:13
/usr/bin/axlisten -artc
> root 414
1 0 Nov01 ? 00:00:00
/usr/sbin/ax25d -l
> root 4231 4212 0 07:20
pts/1 00:00:00 grep ax
>
>
> tail /var/log/messages
> Nov 3 06:36:01 localhost rmsgw_aci[4112]: Channel: K5KTF-10 on
0
> (145730000 Hz, mode 0)
> Nov 3 06:36:01 localhost rmsgw_aci[4112]:
/usr/local/bin/rmschanstat
> ax25 0 K5KTF-10 reports unavailable
> Nov 3 06:36:01 localhost rmsgw_aci[4112]: Channel: K5KTF-10 on
0 is
> DOWN -- not updated
> Nov 3 06:36:01 localhost rmsgw_aci[4112]: Channel Stats: 1
read, 1
> active, 1 down, 0 updated, 0 errors
> Nov 3 07:00:11 localhost updatechannel.py[4149]: Posting
channel
> record updates for K5KTF-10...
> Nov 3 07:06:01 localhost rmsgw_aci[4163]: K5KTF-10 - Linux
RMS
> Gateway ACI 2.5.0 Dec 10 2018 (EM10bm)
> Nov 3 07:06:01 localhost rmsgw_aci[4163]: Channel: K5KTF-10 on
0
> (145730000 Hz, mode 0)
> Nov 3 07:06:01 localhost rmsgw_aci[4163]:
/usr/local/bin/rmschanstat
> ax25 0 K5KTF-10 reports unavailable
> Nov 3 07:06:01 localhost rmsgw_aci[4163]: Channel: K5KTF-10 on
0 is
> DOWN -- not updated
> Nov 3 07:06:01 localhost rmsgw_aci[4163]: Channel Stats: 1
read, 1
> active, 1 down, 0 updated, 0 errors
>
> root@k5ktf-10:~# sudo -u rmsgw rmschanstat ax25 0 K5KTF-10
> interface with @sbin/plymouthd unavailable
>
> root@k5ktf-10:~# ps -ef |grep plymouth
> root 130
1 0 07:54 ? 00:00:00
@sbin/plymouthd
> --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
> root 644 597 0
09:24 pts/1 00:00:00 grep plymouth
>
> root@k5ktf-10:~# cat /etc/ax25/axports
> #Port
Call
Baud PacLen Window Description
> 0
K5KTF-10 19200
256 7 Radio -
145.730 MHz
>
> root@k5ktf-10:~# cat /etc/ax25/ax25d.conf
> # /etc/ax25/ax25d.conf
> [K5KTF-10 via 0]
> K5KTF-10 * * * * * * L
> K5KTF * * * * * * L
> default * * * * * * - rmsgw /usr/local/bin/rmsgw
rmsgw -P 0 %U
> # /etc/ax25/ax25d.conf (End)
>
>
> root@k5ktf-10:~# cat /etc/rmsgw/channels.xml
> <?xml version="1.0"
encoding="UTF-8"?>
> <rmschannels xmlns="http://www.namespace.org"
>
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
>
xsi:schemaLocation="
file:///etc/rmsgw/channels.xsd">
> <channel name="0"
type="ax25" active="yes">
>
<basecall>K5KTF</basecall>
>
<callsign>K5KTF-10</callsign>
>
<password>...Im_not_dumb...</password>
>
<gridsquare>EM10bm</gridsquare>
>
<frequency>145730000</frequency>
> <mode>0</mode>
>
<autoonly>0</autoonly>
> <baud>1200</baud>
> <power>50</power>
> <height>10</height>
> <gain>0</gain>
>
<direction>0</direction>
> <hours>24/7</hours>
>
<groupreference>1</groupreference>
>
<servicecode>PUBLIC</servicecode>
> <statuschecker>
> /usr/local/bin/rmschanstat
$type $name $callsign
> </statuschecker>
> </channel>
> </rmschannels>
>
>
> root@k5ktf-10:~# mheard
> Callsign Port Packets Last Heard
> W5TQ-4
0 2 Sun
Nov 3 09:36:00
> KE5RS-10
0 1 Sun
Nov 3 09:35:09
> W5OEM-12
0 1 Sun
Nov 3 09:34:29
>
> For some reason Travis County ARES has W5TQ-4 and W5OEM-12 APRS
units
> at fixed locations beaconing on 145.73...smh
> KE5RS-10 is another RMS stn on freq that I can work via PAT
(system
> it out in workshop, so I cant change freq remotely)
>
> 2019/11/03 09:53:10 Connecting to KE5RS-10 (ax25)...
> 2019/11/03 09:53:11 Connected to KE5RS-10 (AX.25)
> KE5RS -LEAKA- KANode (Since 1996)
> Connected to KE5RS-10 Winlink 2000 RMS
> [WL2K-5.0-B2FWIHJM$]
> ;PQ: 92941613
> CMS via KE5RS >
> >FF
> FQ
> 2019/11/03 09:53:24 Disconnected.
>
>
> What da heck am I missing?
> (good thing my hair grows back fast else I would be bald by
now...)
>
> 73
> Jim
>
>
> At 09:15 AM 11/2/2019, Basil Gunn wrote:
>
>>Jim,
>>
>>An AX.25 interface is most likely not running
>>
>>Look at this document
>>
https://github.com/nwdigitalradio/n7nix/blob/master/rmsgw/README.md#testing-the-rms-gateway
>>
>>run ax25-status to confirm it's not running
>>also run these & look for ax0 or ax1
>>
>>netstat --ax25
>>ifconfig
>>
>>then do this
>>
>>cd
>>cd bin
>>sudo su
>>./ax25-start
>>
>>Also you should always run rmschanstat & rmsgw_aci as
user rmsgw like
>>this:
>>
>>sudo -u rmsgw rmschanstat ax25 udr0 K5KTF-10
>>sudo -u rmsgw rmsgw_aci
>>
>>I now see your gateway k5ktf-10 appearing on the Winlink
RMSChannels
>>page this morning which I didn't see last night so I assume you
are up &
>>running.
>>
>>/Basil
>>
>>Jim Kinter Jr. via Groups.Io <jim@...>
writes:
>>
>> > I received a text from one of our locals that my RMS stn
hangs
>> when he tries to connect to it.
>> >
>> > When I go to the logs, I get
>> > Nov 1 12:06:01 localhost rmsgw_aci[6817]: K5KTF-10 - Linux
RMS
>> Gateway ACI 2.5.0 Dec 10 2018 (EM10bm)
>> > Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel: K5KTF-10
on 0
>> (145730000 Hz, mode 0)
>> > Nov 1 12:06:01 localhost rmsgw_aci[6817]:
>> /usr/local/bin/rmschanstat ax25 0 K5KTF-10 reports
unavailable
>> > Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel: K5KTF-10
on 0
>> is DOWN -- not updated
>> > Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel Stats: 1
read,
>> 1 active, 1 down, 0 updated, 0 errors
>> >
>> > When I Google the errors, I found a post to test with
>> rmschanstat. When I do that, I get
>> >
>> > root@k5ktf-10:/etc/rmsgw# rmschanstat ax25 0 K5KTF-10
>> > interface with @sbin/plymouthd unavailable
>> >
>> > If I look at WL2K web site/map, I (K5KTF-10) show up fine
there.
>> >
>> > I can also use PAT on this Pi to connect to other VHF
stations
>> just fine (without using the -10 suffix going out).
>> >
>> > Im at a loss of where to look.
>> >
>> > Thanks
>> > Jim
>> > K5KTF
>> >
>> >
>>
>>
>>
>
>
73
Jim Kinter, Jr.
K5KTF
Cedar Park TX
Webmaster
www.Broadband-Hamnet.org
www.CTDXCC.org
www.AustinSummerfest.org
Williamson County ARES
#1545
2010/11/15/16/17/18 Board Member/AEC Special Operations
Travis County ARES
Member
ARRL
Field
Instructor/Field Examiner/VE Liaison
W5YI VE #
34031E
NWS Skywarn Spotter
Lone Star Spotter Network Member
-. --- / .... .- -... .-.. .- / -.-. .--
|
|
Re: PlymouthD error when running RMSCHANSTAT

Basil Gunn
Hi Jim, We probably should have been posting our conversations over on the Linux RMS Gateway forum on yahoo groups since this has not much to do with the udrc. But let's keep going here as I think I know what your problem is. The plymouthd daemon is the app which provides the graphical "splash" screen when booting. It is the owner of the console device. I always run my Linux RMS Gateways headless (without plymouth) so I have never seen this error before. The thing that jumps out at me is that you are not using the latest version of Linux RMS Gateway. During the last transition of Linux Debian/Ubuntu from Jessie to Buster there were a lot of changes that broke the RMS Gateway python scripts ie. ifconfig output changed. Those problems have been fixed in the latest 2.5.1 release of Linux RMS Gateway which lives here: https://github.com/nwdigitalradio/rmsgwThe other thing that could be wrong are file permissions used by those scripts. If you have ever run rmschanstat or rmsgw_aci as a user other than rmsgw it creates files that have incompatible owner:group permissions. Normally the program rmsgw_aci is run from a crontab owned by user rmsgw. When testing I recommend running those programs shown below. rmsgw_aci is a C program that calls the python script rmschanstat. If rmschanstat fails, rmsgw_aci will also fail. sudo -u rmsgw rmschanstat ax25 0 K5KTF-10 sudo -u rmsgw rmsgw_aci Also check the directory & file permissions for /etc/rmsgw/stat. It should look similar to the following. Note that user:group is rmsgw:rmsgw ls -al /etc/rmsgw/stat total 8 drwxr-sr-x 2 rmsgw rmsgw 4096 Aug 19 20:25 . drwxr-sr-x 4 rmsgw rmsgw 4096 Aug 5 16:52 .. -rw-r--r-- 1 rmsgw rmsgw 0 Nov 3 07:19 .channels.udr0 -rw-r--r-- 1 rmsgw rmsgw 0 Nov 1 13:42 cms.winlink.org -rw-r--r-- 1 rmsgw rmsgw 0 Nov 3 07:19 .version.N7NIX-10 Those HAMS setting up a Linux RMS Gateway using NW Digital Radio RPi image won't see the problem you are describing because the latest version of the gateway has been installed on that image. Of course that doesn't help you much since you are using a TNC-Pi which should work fine after installing the latest Linux RMS Gateway. Let me know if this fixes your problem. /Basil n7nix Jim Kinter Jr. via Groups.Io <jim=k5ktf.com@groups.io> writes:
toggle quoted messageShow quoted text
Thanks Basil. Thats what I thought at first (AX not running), but everything I see says it is (as "0", not udrX...its a pi/tnc-pi ).
If I use PAT web GUI on this same system (remotely), I can connect to other local RMS servers just fine, so that tells me the pi, TNC-Pi, network, radio, cabling, AX25, etc are all OK.. Right? So must be something specific to the RMS config? Or the plymouthd error?
root@k5ktf-10:~# ax25-status -bash: ax25-status: command not found
root@k5ktf-10:~# netstat --ax25 Active AX.25 sockets Dest Source Device State Vr/Vs Send-Q Recv-Q * K5KTF-0 ax0 LISTENING 000/000 0 0 * K5KTF-10 ax0 LISTENING 000/000 0 0
root@k5ktf-10:~# ifconfig ax0: flags=67<UP,BROADCAST,RUNNING> mtu 256 inet 44.128.1.10 netmask 255.0.0.0 broadcast 44.255.255.255 ax25 K5KTF-10 txqueuelen 10 (AMPR AX.25) RX packets 1214 bytes 64695 (63.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 301 bytes 13346 (13.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@k5ktf-10:~# ps -ef |grep ax root 410 1 0 Nov01 ? 00:00:13 /usr/bin/axlisten -artc root 414 1 0 Nov01 ? 00:00:00 /usr/sbin/ax25d -l root 4231 4212 0 07:20 pts/1 00:00:00 grep ax
tail /var/log/messages Nov 3 06:36:01 localhost rmsgw_aci[4112]: Channel: K5KTF-10 on 0 (145730000 Hz, mode 0) Nov 3 06:36:01 localhost rmsgw_aci[4112]: /usr/local/bin/rmschanstat ax25 0 K5KTF-10 reports unavailable Nov 3 06:36:01 localhost rmsgw_aci[4112]: Channel: K5KTF-10 on 0 is DOWN -- not updated Nov 3 06:36:01 localhost rmsgw_aci[4112]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors Nov 3 07:00:11 localhost updatechannel.py[4149]: Posting channel record updates for K5KTF-10... Nov 3 07:06:01 localhost rmsgw_aci[4163]: K5KTF-10 - Linux RMS Gateway ACI 2.5.0 Dec 10 2018 (EM10bm) Nov 3 07:06:01 localhost rmsgw_aci[4163]: Channel: K5KTF-10 on 0 (145730000 Hz, mode 0) Nov 3 07:06:01 localhost rmsgw_aci[4163]: /usr/local/bin/rmschanstat ax25 0 K5KTF-10 reports unavailable Nov 3 07:06:01 localhost rmsgw_aci[4163]: Channel: K5KTF-10 on 0 is DOWN -- not updated Nov 3 07:06:01 localhost rmsgw_aci[4163]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
root@k5ktf-10:~# sudo -u rmsgw rmschanstat ax25 0 K5KTF-10 interface with @sbin/plymouthd unavailable
root@k5ktf-10:~# ps -ef |grep plymouth root 130 1 0 07:54 ? 00:00:00 @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session root 644 597 0 09:24 pts/1 00:00:00 grep plymouth
root@k5ktf-10:~# cat /etc/ax25/axports #Port Call Baud PacLen Window Description 0 K5KTF-10 19200 256 7 Radio - 145.730 MHz
root@k5ktf-10:~# cat /etc/ax25/ax25d.conf # /etc/ax25/ax25d.conf [K5KTF-10 via 0] K5KTF-10 * * * * * * L K5KTF * * * * * * L default * * * * * * - rmsgw /usr/local/bin/rmsgw rmsgw -P 0 %U # /etc/ax25/ax25d.conf (End)
root@k5ktf-10:~# cat /etc/rmsgw/channels.xml <?xml version="1.0" encoding="UTF-8"?> <rmschannels xmlns="http://www.namespace.org"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="file:///etc/rmsgw/channels.xsd"> <channel name="0" type="ax25" active="yes"> <basecall>K5KTF</basecall> <callsign>K5KTF-10</callsign> <password>...Im_not_dumb...</password> <gridsquare>EM10bm</gridsquare> <frequency>145730000</frequency> <mode>0</mode> <autoonly>0</autoonly> <baud>1200</baud> <power>50</power> <height>10</height> <gain>0</gain> <direction>0</direction> <hours>24/7</hours> <groupreference>1</groupreference> <servicecode>PUBLIC</servicecode> <statuschecker> /usr/local/bin/rmschanstat $type $name $callsign </statuschecker> </channel> </rmschannels>
root@k5ktf-10:~# mheard Callsign Port Packets Last Heard W5TQ-4 0 2 Sun Nov 3 09:36:00 KE5RS-10 0 1 Sun Nov 3 09:35:09 W5OEM-12 0 1 Sun Nov 3 09:34:29
For some reason Travis County ARES has W5TQ-4 and W5OEM-12 APRS units at fixed locations beaconing on 145.73...smh KE5RS-10 is another RMS stn on freq that I can work via PAT (system it out in workshop, so I cant change freq remotely)
2019/11/03 09:53:10 Connecting to KE5RS-10 (ax25)... 2019/11/03 09:53:11 Connected to KE5RS-10 (AX.25) KE5RS -LEAKA- KANode (Since 1996) Connected to KE5RS-10 Winlink 2000 RMS [WL2K-5.0-B2FWIHJM$] ;PQ: 92941613 CMS via KE5RS > >FF FQ 2019/11/03 09:53:24 Disconnected.
What da heck am I missing? (good thing my hair grows back fast else I would be bald by now...)
73 Jim
At 09:15 AM 11/2/2019, Basil Gunn wrote:
Jim,
An AX.25 interface is most likely not running
Look at this document https://github.com/nwdigitalradio/n7nix/blob/master/rmsgw/README.md#testing-the-rms-gateway
run ax25-status to confirm it's not running also run these & look for ax0 or ax1
netstat --ax25 ifconfig
then do this
cd cd bin sudo su ./ax25-start
Also you should always run rmschanstat & rmsgw_aci as user rmsgw like this:
sudo -u rmsgw rmschanstat ax25 udr0 K5KTF-10 sudo -u rmsgw rmsgw_aci
I now see your gateway k5ktf-10 appearing on the Winlink RMSChannels page this morning which I didn't see last night so I assume you are up & running.
/Basil
Jim Kinter Jr. via Groups.Io <jim=k5ktf.com@groups.io> writes:
I received a text from one of our locals that my RMS stn hangs when he tries to connect to it.
When I go to the logs, I get Nov 1 12:06:01 localhost rmsgw_aci[6817]: K5KTF-10 - Linux RMS Gateway ACI 2.5.0 Dec 10 2018 (EM10bm)
Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel: K5KTF-10 on 0 (145730000 Hz, mode 0)
Nov 1 12:06:01 localhost rmsgw_aci[6817]: /usr/local/bin/rmschanstat ax25 0 K5KTF-10 reports unavailable
Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel: K5KTF-10 on 0 is DOWN -- not updated
Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
When I Google the errors, I found a post to test with rmschanstat. When I do that, I get
root@k5ktf-10:/etc/rmsgw# rmschanstat ax25 0 K5KTF-10 interface with @sbin/plymouthd unavailable
If I look at WL2K web site/map, I (K5KTF-10) show up fine there.
I can also use PAT on this Pi to connect to other VHF stations just fine (without using the -10 suffix going out).
Im at a loss of where to look.
Thanks Jim K5KTF
|
|
Re: PlymouthD error when running RMSCHANSTAT
Thanks Basil.
Thats what I thought at first (AX not running), but everything I see says
it is (as "0", not udrX...its a pi/tnc-pi ).
If I use PAT web GUI on this same system (remotely), I can connect to
other local RMS servers just fine, so that tells me the pi,
TNC-Pi, network, radio, cabling, AX25, etc are all OK..
Right?
So must be something specific to the RMS config? Or the plymouthd
error?
root@k5ktf-10:~# ax25-status
-bash: ax25-status: command not found
root@k5ktf-10:~# netstat --ax25
Active AX.25 sockets
Dest Source
Device State
Vr/Vs Send-Q Recv-Q
*
K5KTF-0 ax0
LISTENING 000/000
0 0
*
K5KTF-10 ax0
LISTENING 000/000
0 0
root@k5ktf-10:~# ifconfig
ax0: flags=67<UP,BROADCAST,RUNNING> mtu 256
inet 44.128.1.10 netmask
255.0.0.0 broadcast 44.255.255.255
ax25 K5KTF-10 txqueuelen
10 (AMPR AX.25)
RX packets 1214 bytes
64695 (63.1 KiB)
RX errors 0 dropped
0 overruns 0 frame 0
TX packets 301 bytes
13346 (13.0 KiB)
TX errors 0 dropped 0
overruns 0 carrier 0 collisions 0
root@k5ktf-10:~# ps -ef |grep ax
root 410
1 0 Nov01 ? 00:00:13
/usr/bin/axlisten -artc
root 414
1 0 Nov01 ? 00:00:00
/usr/sbin/ax25d -l
root 4231 4212 0 07:20
pts/1 00:00:00 grep ax
tail /var/log/messages
Nov 3 06:36:01 localhost rmsgw_aci[4112]: Channel: K5KTF-10 on 0
(145730000 Hz, mode 0)
Nov 3 06:36:01 localhost rmsgw_aci[4112]:
/usr/local/bin/rmschanstat ax25 0 K5KTF-10 reports unavailable
Nov 3 06:36:01 localhost rmsgw_aci[4112]: Channel: K5KTF-10
on 0 is DOWN -- not updated
Nov 3 06:36:01 localhost rmsgw_aci[4112]: Channel Stats: 1
read, 1 active, 1 down, 0 updated, 0 errors
Nov 3 07:00:11 localhost updatechannel.py[4149]: Posting channel
record updates for K5KTF-10...
Nov 3 07:06:01 localhost rmsgw_aci[4163]: K5KTF-10 - Linux RMS
Gateway ACI 2.5.0 Dec 10 2018 (EM10bm)
Nov 3 07:06:01 localhost rmsgw_aci[4163]: Channel: K5KTF-10 on 0
(145730000 Hz, mode 0)
Nov 3 07:06:01 localhost rmsgw_aci[4163]:
/usr/local/bin/rmschanstat ax25 0 K5KTF-10 reports unavailable
Nov 3 07:06:01 localhost rmsgw_aci[4163]: Channel: K5KTF-10
on 0 is DOWN -- not updated
Nov 3 07:06:01 localhost rmsgw_aci[4163]: Channel Stats: 1
read, 1 active, 1 down, 0 updated, 0 errors
root@k5ktf-10:~# sudo -u rmsgw rmschanstat ax25 0 K5KTF-10
interface with @sbin/plymouthd unavailable
root@k5ktf-10:~# ps -ef |grep plymouth
root 130
1 0 07:54 ? 00:00:00
@sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid
--attach-to-session
root 644 597 0
09:24 pts/1 00:00:00 grep plymouth
root@k5ktf-10:~# cat /etc/ax25/axports
#Port
Call
Baud PacLen Window Description
0
K5KTF-10 19200
256 7 Radio -
145.730 MHz
root@k5ktf-10:~# cat /etc/ax25/ax25d.conf
# /etc/ax25/ax25d.conf
[K5KTF-10 via 0]
K5KTF-10 * * * * * * L
K5KTF * * * * * * L
default * * * * * * - rmsgw /usr/local/bin/rmsgw rmsgw
-P 0 %U
# /etc/ax25/ax25d.conf (End)
root@k5ktf-10:~# cat /etc/rmsgw/channels.xml
<?xml version="1.0" encoding="UTF-8"?>
<rmschannels xmlns="http://www.namespace.org"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
file:///etc/rmsgw/channels.xsd">
<channel name="0" type="ax25"
active="yes">
<basecall>K5KTF</basecall>
<callsign>K5KTF-10</callsign>
<password>...Im_not_dumb...</password>
<gridsquare>EM10bm</gridsquare>
<frequency>145730000</frequency>
<mode>0</mode>
<autoonly>0</autoonly>
<baud>1200</baud>
<power>50</power>
<height>10</height>
<gain>0</gain>
<direction>0</direction>
<hours>24/7</hours>
<groupreference>1</groupreference>
<servicecode>PUBLIC</servicecode>
<statuschecker>
/usr/local/bin/rmschanstat $type $name
$callsign
</statuschecker>
</channel>
</rmschannels>
root@k5ktf-10:~# mheard
Callsign Port Packets Last Heard
W5TQ-4
0 2 Sun
Nov 3 09:36:00
KE5RS-10 0
1 Sun Nov 3 09:35:09
W5OEM-12 0
1 Sun Nov 3 09:34:29
For some reason Travis County ARES has W5TQ-4 and W5OEM-12 APRS units at
fixed locations beaconing on 145.73...smh
KE5RS-10 is another RMS stn on freq that I can work via PAT (system it
out in workshop, so I cant change freq remotely)
2019/11/03 09:53:10 Connecting to KE5RS-10 (ax25)...
2019/11/03 09:53:11 Connected to KE5RS-10 (AX.25)
KE5RS -LEAKA- KANode (Since 1996)
Connected to KE5RS-10 Winlink 2000 RMS
[WL2K-5.0-B2FWIHJM$]
;PQ: 92941613
CMS via KE5RS >
>FF
FQ
2019/11/03 09:53:24 Disconnected.
What da heck am I missing?
(good thing my hair grows back fast else I would be bald by
now...)
73
Jim
toggle quoted messageShow quoted text
At 09:15 AM 11/2/2019, Basil Gunn wrote:
Jim,
An AX.25 interface is most likely not running
Look at this document
https://github.com/nwdigitalradio/n7nix/blob/master/rmsgw/README.md#testing-the-rms-gateway
run ax25-status to confirm it's not running
also run these & look for ax0 or ax1
netstat --ax25
ifconfig
then do this
cd
cd bin
sudo su
./ax25-start
Also you should always run rmschanstat & rmsgw_aci as user
rmsgw like
this:
sudo -u rmsgw rmschanstat ax25 udr0 K5KTF-10
sudo -u rmsgw rmsgw_aci
I now see your gateway k5ktf-10 appearing on the Winlink RMSChannels
page this morning which I didn't see last night so I assume you are up
&
running.
/Basil
Jim Kinter Jr. via Groups.Io <jim@...>
writes:
> I received a text from one of our locals that my RMS stn hangs when
he tries to connect to it.
>
> When I go to the logs, I get
> Nov 1 12:06:01 localhost rmsgw_aci[6817]: K5KTF-10 - Linux RMS
Gateway ACI 2.5.0 Dec 10 2018 (EM10bm)
> Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel: K5KTF-10 on 0
(145730000 Hz, mode 0)
> Nov 1 12:06:01 localhost rmsgw_aci[6817]: /usr/local/bin/rmschanstat
ax25 0 K5KTF-10 reports unavailable
> Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel: K5KTF-10 on 0 is
DOWN -- not updated
> Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel Stats: 1 read, 1
active, 1 down, 0 updated, 0 errors
>
> When I Google the errors, I found a post to test with rmschanstat.
When I do that, I get
>
> root@k5ktf-10:/etc/rmsgw# rmschanstat ax25 0 K5KTF-10
> interface with @sbin/plymouthd unavailable
>
> If I look at WL2K web site/map, I (K5KTF-10) show up fine
there.
>
> I can also use PAT on this Pi to connect to other VHF stations just
fine (without using the -10 suffix going out).
>
> Im at a loss of where to look.
>
> Thanks
> Jim
> K5KTF
>
>
|
|
Re: Draws Hat with Cooling
#case
Michael WA7SKG <wa7skg@...>
Some hardware stores (typically, NOT Lowes or Home Depot). In our area (PNW), Coastal Farm & Ranch carries down to M2.0. Also look for RC hobby stores. They often carry down to M1.0 for model airplanes, possibly even smaller than that. If you prefer online, try microfasteners.com. Also, Amazon carries a variety of miniature screw assortments. Do a Google search for miniature screws. You might also look for eyeglass/watch screws.
Michael WA7SKG
Ryan W Leathers wrote on 11/3/19 4:41 AM:
toggle quoted messageShow quoted text
Can you suggest a source for these tiny screws? On Fri, Oct 4, 2019, 4:12 PM Frank Ivan via Groups.Io <k0fei=me.com@groups.io <mailto:me.com@groups.io>> wrote: Hello Everyone, I have updated my case and it is Thing 3897403 https://www.thingiverse.com/thing:3897403. It uses a Raspberry Pi Poe Hat between the Raspberry Pi and the Draws Hat. This brings a temperature controlled fan blowing on the Pi's CPU and also is sealed so that hot air can't recirculate back through the fan but must exit through the cooling slots. Again - can be printed for Pi3 or Pi4. Case for Raspberry Pi 3b or Raspberry Pi 4b + NWDR DRAWS hat with GPS port on side. Added PoE Hat as temperature controlled fan - keep Pi cool no matter load SCAD file provided so you can help tune the design STL files for both Raspberry Pi 3b or Raspberry Pi 4b print your choice Has a powerpole power port Nice fit for DRAWS card Rounded corners Machine screws into card spacers hold case together Hardware 4 M2.5 x 8mm hex socket head machine screws (8mm does not include head) 4 M2.5 x 15mm female to female spacers 4 M2.5 x 8mm male to female spacers 4 M2.5 x 25mm hex socket head machine screws 1 Adafruit ADA2223 - 8.5mm header 40 pin stacking header - also available on Amazon 1 4 Pin Extra Tall Header - https://thepihut.com/products/4-pin-extra-tall-header-push-fit-version-poe-hat 1 Official Raspberry Pi Power over Ethernet card - must be official Raspberry Pi PoE hat Available on Amazon - but PiHut is cheaper and you may want to get 4 pin header from PiHut Assembly Clean out screw holes - 7/64 or 3mm bit does it nicely Clean out ports Install Powerpole connector - maybe use a bit of thin double stick tape to hold in place Install DRAWS card in lid. It's a close fit but should not be difficult Push M2.5 x 25mm screws into holes Slide baffles into slots - keep fan power notch on right as you look from back to front of lid Install 8mm spaces on screws coming though Draws card Install 40 pin spacer header into PoE Hat with header pushing into header on PoE Hat Install PoE Hat onto Draws card - you may need to work the hat past the baffles Install 15mm spaces onto screws coming through PoE Hat Plug Pi into Poe Hat - make sure it is aligned with the pins go into correct holes Install base Secure with the 4 M2.5 x 8mm screws Tighten every thing up with allen wrench The PoE Hat will keep a Ri4 down to under 60C under extended load. It easily passes the heating test from the Explaingcomputers YouTube videos testing Raspberry Pi4 B cooling. While the PoE Hat is primarily used as a cooling fat, but a nice side effect is you can power the system from the ethernet port. Note: If you need RFI shielding line the inside of the case with copper foil tape. Enjoy and 73 Frank - K0FEI
|
|
Re: Draws Hat with Cooling
#case
Can you suggest a source for these tiny screws?
toggle quoted messageShow quoted text
On Fri, Oct 4, 2019, 4:12 PM Frank Ivan via Groups.Io <k0fei= me.com@groups.io> wrote: Hello Everyone,
I have updated my case and it is Thing 3897403 https://www.thingiverse.com/thing:3897403. It uses a Raspberry Pi Poe Hat between the Raspberry Pi and the Draws Hat. This brings a temperature controlled fan blowing on the Pi's CPU and also is sealed so that hot air can't recirculate back through the fan but must exit through the cooling slots. Again - can be printed for Pi3 or Pi4.
Case for Raspberry Pi 3b or Raspberry Pi 4b + NWDR DRAWS hat with GPS port on side.
Added PoE Hat as temperature controlled fan - keep Pi cool no matter load
SCAD file provided so you can help tune the design
STL files for both Raspberry Pi 3b or Raspberry Pi 4b print your choice
Has a powerpole power port
Nice fit for DRAWS card
Rounded corners
Machine screws into card spacers hold case together
Hardware
4 M2.5 x 8mm hex socket head machine screws (8mm does not include head)
4 M2.5 x 15mm female to female spacers
4 M2.5 x 8mm male to female spacers
4 M2.5 x 25mm hex socket head machine screws
1 Adafruit ADA2223 - 8.5mm header 40 pin stacking header - also available on Amazon
1 4 Pin Extra Tall Header - https://thepihut.com/products/4-pin-extra-tall-header-push-fit-version-poe-hat
1 Official Raspberry Pi Power over Ethernet card - must be official Raspberry Pi PoE hat
Available on Amazon - but PiHut is cheaper and you may want to get 4 pin header from PiHut
Assembly
Clean out screw holes - 7/64 or 3mm bit does it nicely
Clean out ports
Install Powerpole connector - maybe use a bit of thin double stick tape to hold in place
Install DRAWS card in lid. It's a close fit but should not be difficult
Push M2.5 x 25mm screws into holes
Slide baffles into slots - keep fan power notch on right as you look from back to front of lid
Install 8mm spaces on screws coming though Draws card
Install 40 pin spacer header into PoE Hat with header pushing into header on PoE Hat
Install PoE Hat onto Draws card - you may need to work the hat past the baffles
Install 15mm spaces onto screws coming through PoE Hat
Plug Pi into Poe Hat - make sure it is aligned with the pins go into correct holes
Install base
Secure with the 4 M2.5 x 8mm screws
Tighten every thing up with allen wrench
The PoE Hat will keep a Ri4 down to under 60C under extended load. It easily passes the heating test from the Explaingcomputers YouTube videos testing Raspberry Pi4 B cooling.
While the PoE Hat is primarily used as a cooling fat, but a nice side effect is you can power the system from the ethernet port.
Note: If you need RFI shielding line the inside of the case with copper foil tape.
Enjoy and 73 Frank - K0FEI
|
|

Basil Gunn
Stuart Longland VK4MSL <stuartl@longlandclan.id.au> writes: On 1/10/19 11:03 pm, Mitch Winkle wrote:
I saw something similar when downloading it yesterday. On Win10 it was abysmally slow. With the same connection on Linux it was it's normally speedy self. The reader is left to his own conclusions. I've seen it crawl under Linux too. I test the down load about once a month and have never had a problem (slow download) yet. I have a fiber connection. I think I'd agree with Basil's assessment that "it does depend on how many other connections are in progress". I'm not sure what Internet link services the NWDR server whether it is in a data centre or is on a SOHO Internet link with limited capacity. I use rackspace ( https://www.rackspace.com/). The server lives in San Antonio, TX. Now that standard Raspbian supports the UDRC/DRAWS, I think things should improve since NWDR's servers only have to carry a small handful of packages and not a whopping great big SD card image. If you want a whopping great big SD card image then use the "W3DJS Raspberry Pi Ham Radio Image v2.0". It's 17GB and has a lot stuff. https://groups.io/g/RaspberryPi-4-HamRadio/topic/w3djs_raspberry_pi_ham_radio/39671852?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,39671852 Note that they solved their slow download problem by using bitTorrent. Our image is much smaller @ 2GB. List of NWDR Installed Programs: https://github.com/nwdigitalradio/n7nix/blob/master/docs/IMAGE_README.mdCoding up a boot-strap script which can be run on stock Raspbian images to set everything up would not be a difficult job. I use a (unsupported) script to build and compress the published image. There is even some documentation on how to run it. Search for "how the NWDR images are created" in the markdown files in the docs directory. The script runs for about 5 to 6 hours, IF there are no problems. It usually takes 1 1/2 to 2 days to verify the image. I would rather do other things than spin up boot images so looking forward to seeing your boot-strap script. /Basil
|
|
On 1/10/19 11:03 pm, Mitch Winkle wrote: I saw something similar when downloading it yesterday. On Win10 it was abysmally slow. With the same connection on Linux it was it's normally speedy self. The reader is left to his own conclusions. I've seen it crawl under Linux too. I was at work, so 50Mbps microwave link for Internet. Workstation and border router are both Linux (Gentoo on the workstation, Ubuntu on the border router), an intermediate router runs Cisco IOS (not sure what version). https://nw-digital-radio.groups.io/g/udrc/message/3788I think I'd agree with Basil's assessment that "it does depend on how many other connections are in progress". I'm not sure what Internet link services the NWDR server whether it is in a data centre or is on a SOHO Internet link with limited capacity. Now that standard Raspbian supports the UDRC/DRAWS, I think things should improve since NWDR's servers only have to carry a small handful of packages and not a whopping great big SD card image. Coding up a boot-strap script which can be run on stock Raspbian images to set everything up would not be a difficult job. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
|
|
Re: Draws Hat with Cooling
#case
Very nice. I am trying to power my Pi3/DRAWS today for the first time. This case/fan/PoE solution is really nice. Clifford - KK6QMS
|
|
Re: PlymouthD error when running RMSCHANSTAT

Basil Gunn
Jim, An AX.25 interface is most likely not running Look at this document https://github.com/nwdigitalradio/n7nix/blob/master/rmsgw/README.md#testing-the-rms-gatewayrun ax25-status to confirm it's not running also run these & look for ax0 or ax1 netstat --ax25 ifconfig then do this cd cd bin sudo su ./ax25-start Also you should always run rmschanstat & rmsgw_aci as user rmsgw like this: sudo -u rmsgw rmschanstat ax25 udr0 K5KTF-10 sudo -u rmsgw rmsgw_aci I now see your gateway k5ktf-10 appearing on the Winlink RMSChannels page this morning which I didn't see last night so I assume you are up & running. /Basil Jim Kinter Jr. via Groups.Io <jim=k5ktf.com@groups.io> writes:
toggle quoted messageShow quoted text
I received a text from one of our locals that my RMS stn hangs when he tries to connect to it.
When I go to the logs, I get Nov 1 12:06:01 localhost rmsgw_aci[6817]: K5KTF-10 - Linux RMS Gateway ACI 2.5.0 Dec 10 2018 (EM10bm) Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel: K5KTF-10 on 0 (145730000 Hz, mode 0) Nov 1 12:06:01 localhost rmsgw_aci[6817]: /usr/local/bin/rmschanstat ax25 0 K5KTF-10 reports unavailable Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel: K5KTF-10 on 0 is DOWN -- not updated Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
When I Google the errors, I found a post to test with rmschanstat. When I do that, I get
root@k5ktf-10:/etc/rmsgw# rmschanstat ax25 0 K5KTF-10 interface with @sbin/plymouthd unavailable
If I look at WL2K web site/map, I (K5KTF-10) show up fine there.
I can also use PAT on this Pi to connect to other VHF stations just fine (without using the -10 suffix going out).
Im at a loss of where to look.
Thanks Jim K5KTF
|
|
PlymouthD error when running RMSCHANSTAT
I received a text from one of our locals that my RMS stn hangs when he tries to connect to it.
When I go to the logs, I get Nov 1 12:06:01 localhost rmsgw_aci[6817]: K5KTF-10 - Linux RMS Gateway ACI 2.5.0 Dec 10 2018 (EM10bm) Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel: K5KTF-10 on 0 (145730000 Hz, mode 0) Nov 1 12:06:01 localhost rmsgw_aci[6817]: /usr/local/bin/rmschanstat ax25 0 K5KTF-10 reports unavailable Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel: K5KTF-10 on 0 is DOWN -- not updated Nov 1 12:06:01 localhost rmsgw_aci[6817]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
When I Google the errors, I found a post to test with rmschanstat. When I do that, I get
root@k5ktf-10:/etc/rmsgw# rmschanstat ax25 0 K5KTF-10 interface with @sbin/plymouthd unavailable
If I look at WL2K web site/map, I (K5KTF-10) show up fine there.
I can also use PAT on this Pi to connect to other VHF stations just fine (without using the -10 suffix going out).
Im at a loss of where to look.
Thanks Jim K5KTF
|
|
Re: Hamwan / DRAWS / Fiber / HF / RMS Gateway

Basil Gunn
If you are addressing this post to Alan Bush, I live in the same county as Alan & will be going over to his QTH in the coming weeks to assist in his install. When we do the Linux RMS Gateway install we will note any discrepancies between what we did and what is already in the UDRC/DRAWS Raspberry Pi Getting Started Guide here: https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Getting-StartedI have installed and support 3 active Linux RMS Gateways in our region and am a maintainer of Linux RMS Gateway repository. If you intend to use both channels of the DRAWS hat please describe exactly what your expectations are for the functionality you require. ie. state your requirements including baud rates & frequencies. Also please tell us if you made your own hat-to-radio cable(s) and which radio(s) you intend to use. I recommend you install paclink-unix as well so you can get automated status reports of your RMS Gateway. /Basil n7nix Chris Robinson KF6NFW DMR ID 3153250 <kf6nfw@gmail.com> writes:
toggle quoted messageShow quoted text
Have you made any progress on this project?
I just got my DRAWS board in hand on a pi 3B+, and am about to dig in on this very near identical setup you are attempting. If you have made progress, i would be very interested in what you have accomplished.
|
|
Re: Hamwan / DRAWS / Fiber / HF / RMS Gateway
Have you made any progress on this project?
I just got my DRAWS board in hand on a pi 3B+, and am about to dig in on this very near identical setup you are attempting. If you have made progress, i would be very interested in what you have accomplished.
|
|
Thanks, I had in mind that DRAWS can just handle up to 12 volts. But in this case it makes a lot of hardware installation things a lot easier.
Once again thanks for your help
|
|
The.Pi USB power input is a nominal 5.1 VDC. Typical 'wall wart' USB supplies may have voltage drop who h in turn manifests in inconsistent operation of the Pi. This, and a single station power supply, is why DRAWS™ HAT has the 9-15 VDC power input.
One can use either to power both the Pi and DRAWS ™.
toggle quoted messageShow quoted text
On Mon, Oct 21, 2019, 06:32 Gayland Gump < kg7gcf@...> wrote: I believe you want make sure you use the power input on the DRAWS and not the Pi itself.
On Mon, Oct 21, 2019 at 6:29 AM John D Hays - K7VE < john@...> wrote: That will be just fine. Input voltage range is 9-15 VDC
On Mon, Oct 21, 2019, 06:28 Rico Abagnale < rico@...> wrote: Hi group.
This might be a stupid question. But since I wouldn’t like to grill my D.R.A.W.S. I will post it anyway: I saw a video where somebody presented D.R.A.W.S. In this presentation he recommended to attach a cable with a Powerpole connector to use the Powerpole distributor he uses for all the rig components to power the Raspberry Pi with the D.R.A.W.S. Will this work? My Powerpole terminal delivers constant regulated 13.8 volts for my radios!
73 de Rico, DG5BQ
|
|