Date   

Re: Winlink RMS installation

John Spoonhower
 

OK Basil,
thanks for help. Just for completeness. I started with a clean compass image download and went thru the apt-get update and upgrade
processes as per the CORE-INSTALL instructions on the web site. All the suggested tests for the Core configuration went OK, excluding the stop/start
issue we have been discussing.
I have subsequently installed and configured the rmsgw. I have a few questions; these may be premature given the problem I have. However with a rebooted system there is some evidence that things are running. If i run mheard I get good news that the system hears the beacon of another Winlink station in the area:
pi@compass-winlinkrms:~/bin $ mheard
Callsign  Port Packets   Last Heard
W3HII-10   udr1      4   Wed May  2 14:21:19

Also, there is output from log file:
pi@compass-winlinkrms:~/bin $ tail -f /var/log/rms.debug
May  2 14:17:01 compass-winlinkrms rmsgw_aci[1237]: NX2I-10 - Linux RMS Gateway ACI 2.4.0 May  2 2018 (EL88xv)
May  2 14:17:01 compass-winlinkrms rmsgw_aci[1237]: Channel: NX2I-10 on udr0 (145030000 Hz, mode 0)
May  2 14:17:01 compass-winlinkrms rmsgw_aci[1237]: /usr/local/bin/rmschanstat ax25 udr0 NX2I-10 reports unavailable
May  2 14:17:01 compass-winlinkrms rmsgw_aci[1237]: Channel: NX2I-10 on udr0 is DOWN -- not updated
May  2 14:17:01 compass-winlinkrms rmsgw_aci[1237]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
May  2 14:17:29 compass-winlinkrms rmsgw_aci[1269]: NX2I-10 - Linux RMS Gateway ACI 2.4.0 May  2 2018 (EL88xv)
May  2 14:17:29 compass-winlinkrms rmsgw_aci[1269]: Channel: NX2I-10 on udr0 (145030000 Hz, mode 0)
May  2 14:17:29 compass-winlinkrms rmsgw_aci[1269]: /usr/local/bin/rmschanstat ax25 udr0 NX2I-10 reports unavailable
May  2 14:17:29 compass-winlinkrms rmsgw_aci[1269]: Channel: NX2I-10 on udr0 is DOWN -- not updated
May  2 14:17:29 compass-winlinkrms rmsgw_aci[1269]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors
Likewise I believe this is good...but I need to ask a few questions. Does the statement that "NX2I-10 on urd0 is DOWN" indicates that I have only
connected to the radio on the 6-pin DIN port of the udrc? 

I have not been able to get the rmsgw_aci command to work; consider:
pi@compass-winlinkrms:~/bin $ sudo -u rmsgw rmsgw_aci
status for interface ax0 unavailable.

i have seen something somewhere on fixing this on the website but I am confused about how to do the fix. BTW, os-release says I am running Jessie:

pi@compass-winlinkrms:~/bin $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

sorry to be asking so many question, but I am learning.
Oh , another question, does the rmsgw announce it's presence in a broadcast over the radio? How does that get setup/configured?
73, John, NX2I
 
 


Re: Winlink RMS installation

Basil Gunn
 

John,
Thanks for providing all the console output I asked for.
The short answer is I don't have an immediate fix but the output you
supplied helps to focus on the problem. The work around, at the moment,
is you have to do a reboot if you stop the ax.25 process.

What I know:
After ax25-stop a subsequent ax25-start does not bring up
the ax.25 ports (ax0, ax1). Since ax25-start works from a system boot I
am looking at:
- some clean-up not happening on a ax25-stop

- some subsequent ax25-start process does not exit with a good status
so it does not complete

- looking at all the files created in /tmp since they would not survive
a reboot but would be around on a ax25-stop/ax25-start

I am not able to replicate what you are seeing on my current test setups
so I will do a fresh install hoping to see your problem.

Will let you know what I find in the next couple of days.

/Basil n7nix


John Spoonhower <jpspoonhower@...> writes:

here's the output prior to an ax25-stop/ax25-start cycle:


Re: Winlink RMS installation

John Spoonhower
 

here's the output prior to an ax25-stop/ax25-start cycle:
pi@compass-winlinkrms:~/bin $ sudo ./ax25-status
== failed & loaded but inactive units==
0 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
 
== direwolf ==
  pid: 561
  ver: Dire Wolf version 1.4
== /proc/sys ==
ax25  core  ipv4  ipv6  netfilter  unix
ax0  ax1
 
== ifconfig ax0 ==
ax0       Link encap:AMPR AX.25  HWaddr NX2I-11
          inet addr:44.24.197.66  Bcast:44.255.255.255  Mask:255.255.255.255
          UP BROADCAST RUNNING  MTU:255  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10
          RX bytes:0 (0.0 B)  TX bytes:20 (20.0 B)
 
 
== status networkd services ==
enabled
● systemd-networkd-wait-online.service - Wait for Network to be Configured
   Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled)
   Active: active (exited) since Wed 2018-05-02 11:45:25 EDT; 1h 6min ago
     Docs: man:systemd-networkd-wait-online.service(8)
  Process: 588 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exited, status=0/SUCCESS)
 Main PID: 588 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/systemd-networkd-wait-online.service
 
May 02 11:45:25 compass-winlinkrms systemd[1]: Started Wait for Network to b....
Hint: Some lines were ellipsized, use -l to show in full.
enabled
● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled)
   Active: active (running) since Wed 2018-05-02 11:45:24 EDT; 1h 6min ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 546 (systemd-network)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-networkd.service
           └─546 /lib/systemd/systemd-networkd
 
May 02 11:45:24 compass-winlinkrms systemd-networkd[546]: lo              : g...
May 02 11:45:24 compass-winlinkrms systemd[1]: Started Network Service.
May 02 11:45:25 compass-winlinkrms systemd-networkd[546]: ax0             : g...
May 02 11:45:25 compass-winlinkrms systemd-networkd[546]: ax1             : g...
Hint: Some lines were ellipsized, use -l to show in full.
 
== status direwolf service ==
enabled
● direwolf.service - Direwolf Daemon
   Loaded: loaded (/etc/systemd/system/direwolf.service; enabled)
   Active: active (running) since Wed 2018-05-02 11:45:24 EDT; 1h 6min ago
  Process: 439 ExecStartPre=/bin/rm -f /tmp/kisstnc (code=exited, status=0/SUCCESS)
 Main PID: 561 (direwolf)
   CGroup: /system.slice/direwolf.service
           └─561 /usr/bin/direwolf -t 0 -c /etc/direwolf.conf -p
 
May 02 11:45:39 compass-winlinkrms direwolf[561]: [ig] # logresp NX2I verifie...
May 02 12:01:20 compass-winlinkrms direwolf[561]: W3HII-10 audio level = 7(3/...
May 02 12:01:20 compass-winlinkrms direwolf[561]: [1.3] W3HII-10>BEACON:Winli...
May 02 12:01:20 compass-winlinkrms direwolf[561]: Unknown APRS Data Type Indi...
May 02 12:21:19 compass-winlinkrms direwolf[561]: W3HII-10 audio level = 7(3/...
May 02 12:21:19 compass-winlinkrms direwolf[561]: [1.3] W3HII-10>BEACON:Winli...
May 02 12:21:19 compass-winlinkrms direwolf[561]: Unknown APRS Data Type Indi...
May 02 12:41:19 compass-winlinkrms direwolf[561]: W3HII-10 audio level = 7(4/...
May 02 12:41:19 compass-winlinkrms direwolf[561]: [1.3] W3HII-10>BEACON:Winli...
May 02 12:41:19 compass-winlinkrms direwolf[561]: Unknown APRS Data Type Indi...
Hint: Some lines were ellipsized, use -l to show in full.
 
== status ax25 service ==
disabled
● ax25dev.service - AX.25 device
   Loaded: loaded (/etc/systemd/system/ax25dev.service; disabled)
   Active: active (exited) since Wed 2018-05-02 11:45:25 EDT; 1h 6min ago
  Process: 729 ExecStartPost=/bin/bash -c /usr/local/sbin/kissparms -p udr0 -f no -l 100 -r 32 -s 200 -t 500 (code=exited, status=0/SUCCESS)
  Process: 631 ExecStart=/bin/bash -c /etc/ax25/ax25-upd (code=exited, status=0/SUCCESS)
 Main PID: 631 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/ax25dev.service
           ├─691 /usr/local/sbin/mkiss /tmp/kisstnc /dev/ptmx /dev/ptmx
           ├─701 /usr/local/sbin/kissattach /dev/pts/1 udr0 44.24.197.66
           └─704 /usr/local/sbin/kissattach /dev/pts/2 udr1 44.24.197.67
 
May 02 11:45:25 compass-winlinkrms bash[631]: using mkiss with UDRC II and p...2
May 02 11:45:25 compass-winlinkrms bash[631]: kissattach return: 0
May 02 11:45:25 compass-winlinkrms bash[631]: Using Device = ax0
May 02 11:45:25 compass-winlinkrms bash[631]: ax25dev-parms finished
May 02 11:45:25 compass-winlinkrms bash[631]: Using Device = ax1
May 02 11:45:25 compass-winlinkrms bash[631]: ax25dev-parms finished
May 02 11:45:25 compass-winlinkrms bash[631]: Port udr0 attached to ax0
May 02 11:45:25 compass-winlinkrms bash[631]: Port udr1 attached to ax1
May 02 11:45:25 compass-winlinkrms bash[631]: ax25-upd script finished
May 02 11:45:25 compass-winlinkrms systemd[1]: Started AX.25 device.
Hint: Some lines were ellipsized, use -l to show in full.
 
== status ax25 path ==
enabled
● ax25dev.path
   Loaded: loaded (/etc/systemd/system/ax25dev.path; enabled)
   Active: active (running) since Wed 2018-05-02 11:45:23 EDT; 1h 6min ago
 
May 02 11:45:23 compass-winlinkrms systemd[1]: Starting ax25dev.path.
May 02 11:45:23 compass-winlinkrms systemd[1]: Started ax25dev.path.
 
== status ax25-mheardd ==
enabled
● ax25-mheardd.service - AX.25 mheard daemon
   Loaded: loaded (/etc/systemd/system/ax25-mheardd.service; enabled)
   Active: active (running) since Wed 2018-05-02 11:45:25 EDT; 1h 6min ago
 Main PID: 733 (mheardd)
   CGroup: /system.slice/ax25-mheardd.service
           └─733 /usr/local/sbin/mheardd -f -n 30
 
May 02 11:45:25 compass-winlinkrms systemd[1]: Started AX.25 mheard daemon.
 
== status ax25d ==
enabled
● ax25d.service - General purpose AX.25 daemon
   Loaded: loaded (/etc/systemd/system/ax25d.service; enabled)
   Active: active (running) since Wed 2018-05-02 11:45:25 EDT; 1h 6min ago
 Main PID: 732 (ax25d)
   CGroup: /system.slice/ax25d.service
           └─732 /usr/local/sbin/ax25d -l
 
May 02 11:45:25 compass-winlinkrms systemd[1]: Started General purpose AX.25....
May 02 11:45:25 compass-winlinkrms ax25d[732]: starting
May 02 11:45:25 compass-winlinkrms ax25d[732]: new config file loaded succes...y
Hint: Some lines were ellipsized, use -l to show in full.
 
== netstat ax25 ==
Active AX.25 sockets
Dest       Source     Device  State        Vr/Vs    Send-Q  Recv-Q
*          NX2I-10    ax1     LISTENING    000/000  0       0
*          NX2I-12    ax0     LISTENING    000/000  0       0
after the stop/start cycle it looks like the following:

pi@compass-winlinkrms:~/bin $ sudo ./ax25-status
== failed & loaded but inactive units==
  UNIT          LOAD   ACTIVE SUB    DESCRIPTION
● ax25d.service loaded failed failed General purpose AX.25 daemon
 
LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
 
1 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
 
== direwolf ==
  pid: 1495
  ver: Dire Wolf version 1.4
== /proc/sys ==
core  ipv4  ipv6  netfilter  unix
ls: cannot access /proc/sys/net/ax25: No such file or directory
 
== ifconfig ax0 ==
ax0: error fetching interface information: Device not found
 
== status networkd services ==
enabled
● systemd-networkd-wait-online.service - Wait for Network to be Configured
   Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled)
   Active: active (exited) since Wed 2018-05-02 11:45:25 EDT; 1h 12min ago
     Docs: man:systemd-networkd-wait-online.service(8)
  Process: 588 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exited, status=0/SUCCESS)
 Main PID: 588 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/systemd-networkd-wait-online.service
 
May 02 11:45:25 compass-winlinkrms systemd[1]: Started Wait for Network to b....
Hint: Some lines were ellipsized, use -l to show in full.
enabled
● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled)
   Active: active (running) since Wed 2018-05-02 11:45:24 EDT; 1h 12min ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 546 (systemd-network)
   Status: "Processing requests..."
   CGroup: /system.slice/systemd-networkd.service
           └─546 /lib/systemd/systemd-networkd
 
May 02 11:45:24 compass-winlinkrms systemd-networkd[546]: lo              : g...
May 02 11:45:24 compass-winlinkrms systemd[1]: Started Network Service.
May 02 11:45:25 compass-winlinkrms systemd-networkd[546]: ax0             : g...
May 02 11:45:25 compass-winlinkrms systemd-networkd[546]: ax1             : g...
Hint: Some lines were ellipsized, use -l to show in full.
 
== status direwolf service ==
enabled
● direwolf.service - Direwolf Daemon
   Loaded: loaded (/etc/systemd/system/direwolf.service; enabled)
   Active: active (running) since Wed 2018-05-02 12:55:43 EDT; 1min 46s ago
  Process: 1470 ExecStop=/bin/rm -f /tmp/kisstnc (code=exited, status=0/SUCCESS)
  Process: 1491 ExecStartPre=/bin/rm -f /tmp/kisstnc (code=exited, status=0/SUCCESS)
 Main PID: 1495 (direwolf)
   CGroup: /system.slice/direwolf.service
           └─1495 /usr/bin/direwolf -t 0 -c /etc/direwolf.conf -p
 
May 02 12:55:43 compass-winlinkrms direwolf[1495]: Channel 0: 1200 baud, AFSK...
May 02 12:55:43 compass-winlinkrms direwolf[1495]: Channel 1: 1200 baud, AFSK...
May 02 12:55:43 compass-winlinkrms direwolf[1495]: Ready to accept AGW client...
May 02 12:55:43 compass-winlinkrms direwolf[1495]: Ready to accept KISS clien...
May 02 12:55:43 compass-winlinkrms direwolf[1495]: Virtual KISS TNC is availa...
May 02 12:55:43 compass-winlinkrms direwolf[1495]: Created symlink /tmp/kisst...
May 02 12:55:48 compass-winlinkrms direwolf[1495]: Now connected to IGate ser...
May 02 12:55:48 compass-winlinkrms direwolf[1495]: Check server status here h...
May 02 12:55:53 compass-winlinkrms direwolf[1495]: [ig] # javAPRSSrvr 4.3.0b33
May 02 12:55:53 compass-winlinkrms direwolf[1495]: [ig] # logresp NX2I verifi...
Hint: Some lines were ellipsized, use -l to show in full.
 
== status ax25 service ==
disabled
● ax25dev.service - AX.25 device
   Loaded: loaded (/etc/systemd/system/ax25dev.service; disabled)
   Active: inactive (dead) since Wed 2018-05-02 12:55:28 EDT; 2min 1s ago
  Process: 1437 ExecStop=/bin/bash -c /etc/ax25/ax25-downd (code=exited, status=0/SUCCESS)
  Process: 729 ExecStartPost=/bin/bash -c /usr/local/sbin/kissparms -p udr0 -f no -l 100 -r 32 -s 200 -t 500 (code=exited, status=0/SUCCESS)
  Process: 631 ExecStart=/bin/bash -c /etc/ax25/ax25-upd (code=exited, status=0/SUCCESS)
 Main PID: 631 (code=exited, status=0/SUCCESS)
 
May 02 11:45:25 compass-winlinkrms bash[631]: ax25-upd script finished
May 02 11:45:25 compass-winlinkrms systemd[1]: Started AX.25 device.
May 02 12:55:25 compass-winlinkrms systemd[1]: Stopping AX.25 device...
May 02 12:55:25 compass-winlinkrms bash[1437]: ax25-downd start
May 02 12:55:25 compass-winlinkrms bash[1437]: ax25d - 732
May 02 12:55:27 compass-winlinkrms bash[1437]: mheardd - 733
May 02 12:55:28 compass-winlinkrms bash[1437]: Netrom daemon not running
May 02 12:55:28 compass-winlinkrms bash[1437]: Detach Ax/Nr/Sp Devices
May 02 12:55:28 compass-winlinkrms bash[1437]: ax25-downd finished
May 02 12:55:28 compass-winlinkrms systemd[1]: Stopped AX.25 device.
 
== status ax25 path ==
enabled
● ax25dev.path
   Loaded: loaded (/etc/systemd/system/ax25dev.path; enabled)
   Active: active (waiting) since Wed 2018-05-02 12:55:43 EDT; 1min 46s ago
 
May 02 12:55:43 compass-winlinkrms systemd[1]: Starting ax25dev.path.
May 02 12:55:43 compass-winlinkrms systemd[1]: Started ax25dev.path.
 
== status ax25-mheardd ==
enabled
● ax25-mheardd.service - AX.25 mheard daemon
   Loaded: loaded (/etc/systemd/system/ax25-mheardd.service; enabled)
   Active: inactive (dead) since Wed 2018-05-02 12:55:27 EDT; 2min 3s ago
  Process: 733 ExecStart=/usr/local/sbin/mheardd -f -n 30 (code=exited, status=0/SUCCESS)
 Main PID: 733 (code=exited, status=0/SUCCESS)
 
May 02 11:45:25 compass-winlinkrms systemd[1]: Started AX.25 mheard daemon.
May 02 12:55:28 compass-winlinkrms systemd[1]: Stopped AX.25 mheard daemon.
May 02 12:57:13 compass-winlinkrms systemd[1]: Dependency failed for AX.25 m....
Hint: Some lines were ellipsized, use -l to show in full.
 
== status ax25d ==
enabled
● ax25d.service - General purpose AX.25 daemon
   Loaded: loaded (/etc/systemd/system/ax25d.service; enabled)
   Active: failed (Result: exit-code) since Wed 2018-05-02 12:57:13 EDT; 16s ago
  Process: 1518 ExecStart=/usr/local/sbin/ax25d -l (code=exited, status=1/FAILURE)
 Main PID: 1518 (code=exited, status=1/FAILURE)
 
May 02 12:57:13 compass-winlinkrms systemd[1]: Started General purpose AX.25....
May 02 12:57:13 compass-winlinkrms ax25d[1518]: ax25d: no AX.25 port data co...d
May 02 12:57:13 compass-winlinkrms systemd[1]: ax25d.service: main process e...E
May 02 12:57:13 compass-winlinkrms systemd[1]: Unit ax25d.service entered fa....
Hint: Some lines were ellipsized, use -l to show in full.
 
== netstat ax25 ==
Active AX.25 sockets
Dest       Source     Device  State        Vr/Vs    Send-Q  Recv-Q
 


Re: Winlink RMS installation

John Spoonhower
 

Hi Basil,
here's the first part:
------------------------
# /usr/local/etc/ax25/axports
#
# The format of this file is:
#portname       callsign        speed   paclen  window  description
udr0        NX2I-11         9600    255     2       Direwolf port
udr1        NX2I-10            9600    255     2       Winlink port

and:

# /usr/local/etc/ax25/ax25d.conf
#
# ax25d Configuration File.
#
# Anyone connecting with the source call of N0CALL will be
# dropped. Everyone else is sent to the default.
#
# To route calls from a specific callsign to a different application,
# add them as desired.
#
# AX.25 Ports begin with a '['.
# Format is [<incoming callsign> VIA <axportname>]
#
# When users connect to <incoming callsign>, they will be processed
# by the section that matches.
#
[NX2I-12 VIA udr0]
NOCALL   * * * * * *  L
default  * * * * * *  - root /usr/sbin/ttylinkd ttylinkd
#
[NX2I-10 VIA udr1]
NOCALL   * * * * * *  L
default  * * * * * *  - rmsgw /usr/local/bin/rmsgw rmsgw -P %d %U

more to follow in another note.
John
 


Re: Winlink RMS installation

Basil Gunn
 

-- Unit ax25d.service has finished starting up.
--
-- The start-up result is done.
May 02 11:39:41 compass-winlinkrms ax25d[1291]: ax25d: no AX.25 port data config
Could you please post the contents of these 2 files:

/etc/ax25/axports
/etc/ax25/ax25d.conf

and the output of ~/bin/ax25-status after the ax25-stop/ax25-start
sequence.

Thanks,

/Basil n7nix


Re: Winlink RMS installation

John Spoonhower
 

Hi Tony,
here's some console output as you request.
John

pi@compass-winlinkrms:~/bin $ sudo ./ax25-start
A dependency job for ax25-mheardd.service failed. See 'journalctl -xn' for details.
pi@compass-winlinkrms:~/bin $ sudo journalctl -xn
-- Logs begin at Wed 2018-05-02 10:17:41 EDT, end at Wed 2018-05-02 11:41:04 EDT
May 02 11:39:41 compass-winlinkrms systemd[1]: Starting General purpose AX.25 da
-- Subject: Unit ax25d.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit ax25d.service has begun starting up.
May 02 11:39:41 compass-winlinkrms systemd[1]: Started General purpose AX.25 dae
-- Subject: Unit ax25d.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit ax25d.service has finished starting up.
--
-- The start-up result is done.
May 02 11:39:41 compass-winlinkrms ax25d[1291]: ax25d: no AX.25 port data config
May 02 11:39:41 compass-winlinkrms sudo[1257]: pam_unix(sudo:session): session c
May 02 11:39:41 compass-winlinkrms systemd[1]: ax25d.service: main process exite
May 02 11:39:41 compass-winlinkrms systemd[1]: Unit ax25d.service entered failed
May 02 11:41:04 compass-winlinkrms sudo[1298]: pi : TTY=pts/3 ; PWD=/home/pi/bin
May 02 11:41:04 compass-winlinkrms sudo[1298]: pam_unix(sudo:session): session o
 


Re: Winlink RMS installation

Tony <w7efs@...>
 

Did the results of executing 'journalctl -xn' indicate that a reboot was needed?

On May 2, 2018 06:22, John Spoonhower <jpspoonhower@...> wrote:
I am following the process outlined by N7NIX in order to build a Winlink RMS with a Raspberry Pi 3 and UDRC-II.
I have completed the CORE-INSTALL scripts and everything seems to run just fine after rebooting.
However, if I "manually" stop running services with ax25-stop, and then restart manually with ax25-start, there is an issue with mheardd.
When I execute:
sudo ./ax25-start, I get back the message:
A dependency job for ax25-mheardd.service failed. See 'journalctl -xn' for details.

This can apparently get fixed with a system reboot.
Any ideas what happening here?

73,
John, NX2I

 


Winlink RMS installation

John Spoonhower
 

I am following the process outlined by N7NIX in order to build a Winlink RMS with a Raspberry Pi 3 and UDRC-II.
I have completed the CORE-INSTALL scripts and everything seems to run just fine after rebooting.
However, if I "manually" stop running services with ax25-stop, and then restart manually with ax25-start, there is an issue with mheardd.
When I execute:
sudo ./ax25-start, I get back the message:
A dependency job for ax25-mheardd.service failed. See 'journalctl -xn' for details.

This can apparently get fixed with a system reboot.
Any ideas what happening here?

73,
John, NX2I

 


Re: 6 pin mini DIN adapter for GM300. Will the radio do 9600?

Richard Hendricks <rickh6155@...>
 

JU551 is for the receive, and does work.  I have the adapter board from Argent and the GM300 receives 9600 baud very well, however, the transmit audio
on the adapter is fed to the MIC AUDIO (pin 2) of the GM300, which will not work.  I've tried injecting into FLAT TX AUDIO (Pin 5) which doesn't work either,
as it distorts the 9600 baud eye pattern.  I've inquired to Argent, and John Cape informed me that I should look at C1 on the board (I requested and got a
schematic from him) as it may be the cause of the distortion, but the eye pattern going into the small amplifier transistor is clean on both sides of the
referenced capacitor.  I just downloaded the schematic for the French version, and see that it does, in fact, directly inject the 9600 baud data signal into
pin 5 without going thru any amplification.  So, I'll do some testing with the Argent Data module and see what I can devise by diverting the 9600-baud
data away from the amplifier transistor and directly into pin 5 of the GM300.

73 - Rick
KE0GB


Re: Digi-Pi

Bernard f6bvp / ai7bg
 

Hi Steve,

Being involved into an EME project with a 10m dish radiotelescope antenna in Paris (France), we are considering using a LimeSDR mini TRX available for 139$ + 10$ shipping.

https://www.crowdsupply.com/lime-micro/limesdr-mini

Device is supported by http://www.sdr-radio.com/Radios/LimeSDR

You may browse the web for "Raspberry & LimeSDR" and will be surprised by the number of projects involved from AMSAT to Ham TV.

73 de Bernard, f6bvp


Le 13/04/2018 à 20:22, Steve McGrane a écrit :

Thanks for the list, I'm checking those out now.  That seems to narrow it down to the FT-891 or the IC-706*.  I have a 706MKII here, and everything seems to work but the speaker output (any radio signal speaker output, status beeps are fine)... so it might work with a data cable and some software.

I haven't found an SDR that will transmit yet...

On Fri, Apr 13, 2018 at 11:29 AM, Bill Vodall <wa7nwp@...> wrote:
> I haven't figured out yet what kind of radio I need


That's a good question and even after all these years that's still the
big problem.   While there are some good'ish radios they are expensive
and which they are is not well defined.

It also depends on what you want to do...   APRS, HF, Higher Speed data...

25 years ago we had the Kantronics D4-10 for 9600 baud to 19200 baud.
It used crystals and was about $1000 is 2018 dollars.

Today we have the Kenwood TH-D710 for $600

Others are around $300.   https://groups.io/g/nwaprs/wiki/Radios-for-Packet

Maybe SDR will be the answer.

73,
Bill, WA7NWP






Re: 2017 SeaPac 7" display?

 

https://www.raspberrypi.org/products/raspberry-pi-touch-display/ If I remember correctly and Newark has a good price.

On Tue, Apr 24, 2018 at 6:37 PM, ynotssor via Groups.Io <ynotssor@...> wrote:
Greetings,

Does someone have a link to information about the 7" displays that were used during the 2017 SeaPac Raspberry Pi forum, please?






--


John D. Hays
Edmonds, WA
K7VE

   


2017 SeaPac 7" display?

ynotssor@...
 

Greetings,

Does someone have a link to information about the 7" displays that were used during the 2017 SeaPac Raspberry Pi forum, please?


Re: UDRC-II Suitability

 

We generally are not bringing inventory to Hamfests due to the hassle of setting up to collect sales tax and then remitting it.

If you would like one, it is best to just order it on the website.  http://nwdigitalradio.com/product/udrc/

On Sun, Apr 15, 2018 at 2:26 PM, <gordo@...> wrote:
Thanks for the info John.  That is most helpful.  Hopefully they will be available for purchase at Dayton/Xenia.
_._,_._,_



John D. Hays
Edmonds, WA
K7VE

   


Re: UDRC-II Suitability

gordo@...
 

Thanks for the info John.  That is most helpful.  Hopefully they will be available for purchase at Dayton/Xenia.


Re: UDRC-II Suitability

 

I have replaced dvrptr boards with UDRC on a couple of repeaters. In my estimation the UDRC works better.  


On Sat, Apr 14, 2018, 14:16 <gordo@...> wrote:
Hello;

I am currently using a DVRPTR v1 board for my public facing D-Star hotspot.  Can the UDRC-II board be used as a suitable replacement for the DVRPTR?  I'm just looking into the possibility of having a backup device in the event my DVRPTR stops working since they are no longer in production.

Thanks for any and all help;
Gord - VA3TWT

Blenheim, Ontario, Canada


UDRC-II Suitability

gordo@...
 

Hello;

I am currently using a DVRPTR v1 board for my public facing D-Star hotspot.  Can the UDRC-II board be used as a suitable replacement for the DVRPTR?  I'm just looking into the possibility of having a backup device in the event my DVRPTR stops working since they are no longer in production.

Thanks for any and all help;
Gord - VA3TWT

Blenheim, Ontario, Canada


Re: Digi-Pi

Chris - KC9AD
 

Oops! Thank you John. I guess I was asleep for that part of the discussion.

 

I guess I could at least mention the website: http://nwdigitalradio.com/

 

73.

 

Chris KC9AD

 

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of John D Hays - K7VE
Sent: Friday, April 13, 2018 11:18 AM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] Digi-Pi

 

 

 

On Fri, Apr 13, 2018 at 9:46 AM, Chris Doutre <c.doutre@sbcglobalnet> wrote:

 The UDRC has two radio port: a mini-DIN-6 connector and a DB-9. 


Just for clarification, the second connector is an HD-15 rather than a DB-9.  The UDRC/UDRC-II has this port specifically to support connection to a Yaesu DR-1X repeater adding D-STAR capabilities to the repeater, however in the UDRC-II it also can be wired for a second radio.

Boards are available.  NW Digital Radio has a new generation board in design that will host 2 mini DIN-6 ports.   Also a variant of the new design will have a low powered, integrated radio (VHF or UHF TBD) and a single mini DIN-6. 

--

 


John D. Hays
Edmonds, WA

K7VE

 

Image removed by sender. Image removed by sender. Image removed by sender. Image removed by sender.

 


Re: Digi-Pi

Steve McGrane <temporarilyoffline@...>
 

Thanks for the list, I'm checking those out now.  That seems to narrow it down to the FT-891 or the IC-706*.  I have a 706MKII here, and everything seems to work but the speaker output (any radio signal speaker output, status beeps are fine)... so it might work with a data cable and some software.

I haven't found an SDR that will transmit yet...

On Fri, Apr 13, 2018 at 11:29 AM, Bill Vodall <wa7nwp@...> wrote:
> I haven't figured out yet what kind of radio I need


That's a good question and even after all these years that's still the
big problem.   While there are some good'ish radios they are expensive
and which they are is not well defined.

It also depends on what you want to do...   APRS, HF, Higher Speed data...

25 years ago we had the Kantronics D4-10 for 9600 baud to 19200 baud.
It used crystals and was about $1000 is 2018 dollars.

Today we have the Kenwood TH-D710 for $600

Others are around $300.   https://groups.io/g/nwaprs/wiki/Radios-for-Packet

Maybe SDR will be the answer.

73,
Bill, WA7NWP





Re: Digi-Pi

 



On Fri, Apr 13, 2018 at 9:46 AM, Chris Doutre <c.doutre@...> wrote:

 The UDRC has two radio port: a mini-DIN-6 connector and a DB-9. 


Just for clarification, the second connector is an HD-15 rather than a DB-9.  The UDRC/UDRC-II has this port specifically to support connection to a Yaesu DR-1X repeater adding D-STAR capabilities to the repeater, however in the UDRC-II it also can be wired for a second radio.

Boards are available.  NW Digital Radio has a new generation board in design that will host 2 mini DIN-6 ports.   Also a variant of the new design will have a low powered, integrated radio (VHF or UHF TBD) and a single mini DIN-6. 
--


John D. Hays
Edmonds, WA
K7VE

   


Re: Digi-Pi

Chris - KC9AD
 

Hi Steve,

 

I am a real Digi-Pi noob, but I, and several of my local ham colleagues are using the Digi-Pi for FSQ mode comms. We use the Fldigi software running under Linux on the Pi. FSQ is a very low speed chat mode, keyboard to keyboard, that we use on VHF FM simplex, 145.580 MHz. To address your specific question, I am using a Kenwood TM-V7 dual band mobile radio; it has a mini-DIN-6 “data” connector on the front panel. Elsewhere, we are using a Yaesu FT-8900R; it has a mini-DIN-6 connector on the back panel. So, the UDRC (aka the modem), is connected to the radio data port using a straight-thru cable with a male mini-DIN-6 on each end. You can order that cable as an option with your UDRC-II. Other radios can use different connectors, like maybe a DB-9, so you might need a different cable. The UDRC has two radio port: a mini-DIN-6 connector and a DB-9. You select the one you want in the Fldigi configuration menu. Once the radio is connected, it is controlled by the software. So, you type a line of text and, when you hit enter, the UDRC turns on the PTT and transmits your message via the radio.

 

I realize that there’s a lot more to it, but hopefully this adds to your understanding. 73.

 

Chris Doutre KC9AD

 

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of Steve McGrane
Sent: Friday, April 13, 2018 9:17 AM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] Digi-Pi

 

Seems like a pretty easy/simple build... but I have zero idea what's actually going on after the build is finished.. 

How do you connect it to your radio?

What is he transmitting/receiving?

A lot of the digital mode videos seem to start after the radio is connected and go over the software.  I haven't figured out yet what kind of radio I need or how to hook up after I have it.

 

On Fri, Apr 13, 2018 at 10:47 AM, Gordon Munck <Gordonmunck@...> wrote:

Thank you, John.  Looks like fun!

Gordon


On Apr 12, 2018, at 10:27 PM, John D Hays - K7VE <john@...> wrote:

By WB7FHC -- Budd Churchward

 

Short Version: https://www.youtube.com/watch?v=65RONF37svw

 


 

--

 


John D. Hays
Edmonds, WA

K7VE

 

Image removed by sender. Image removed by sender. Image removed by sender. Image removed by sender.