Date   

Re: NWDR18 image release announcement

John Spoonhower
 

and.....it appears that after the update the AX25 daemon is misconfigured.
73, John, NX2I

-------------------------------------------------------------------------------------------------
pi@udrc:~/n7nix/ax25 $ ./ax25-showcfg.sh

 === Display kissparms & ax25dev-parms
port: 0, speed: 1200, slottime: 200, txdelay: 500, txtail: 100, persist: 32, t1 timeout: 3000, t2 timeout: 1000
port: 1, speed: 1200, slottime: 200, txdelay: 500, txtail: 100, persist: 32, t1 timeout: 3000, t2 timeout: 1000

 == kissparms from /etc/ax25/ax25-upd
        $KISSPARMS -p ${PORTNAME_1} -f no -l $TXTAIL -r $PERSIST -s $SLOTTIME -t $TXDELAY
            $KISSPARMS -p ${PORTNAME_1} -f no -l $TXTAIL -r $PERSIST -s $SLOTTIME -t $TXDELAY
            $KISSPARMS -p ${PORTNAME_1} -f no -l $TXTAIL -r $PERSIST -s $SLOTTIME -t $TXDELAY
            $KISSPARMS -p ${PORTNAME_2} -f no -l $TXTAIL -r $PERSIST -s $SLOTTIME -t $TXDELAY
        $KISSPARMS -p ${PORTNAME_1} -f no -l $TXTAIL -r $PERSIST -s $SLOTTIME -t $TXDELAY

 ===== ax.25 config
Found directory: /proc/sys/net/ax25/*
*: cat: '/proc/sys/net/ax25/*/*': No such file or directory


 ==== List All sound card device names (3)
card 0: b1 [bcm2835 HDMI 1]
card 1: Headphones [bcm2835 Headphones]
card 2: udrc [udrc]

 ======= DRAWS
 ===== ALSA Controls for Radio Transmit =====
LO Driver Gain  L:[-6.00dB] R:[-6.00dB]
PCM        L:[5.00dB] R:[5.00dB]
DAC Playback PT L:[P3] R:[P3]
LO Playback CM [Full Chip]

 ===== ALSA Controls for Radio Receive =====
ADC Level L:[0.00dB] R:[0.00dB]
IN1 L:[10 kOhm] R:[10 kOhm]
IN2 L:[10 kOhm] R:[10 kOhm]
CM L:[10 kOhm] R:[10 kOhm]


===== Port baudrate
DireWolf: udr0 speed: 1200, udr1 speed: 1200
AX.25:    udr0 speed: 1200, udr1 speed: 1200

===== axports
axudp N0ONE-8 115200 253 2 Linux (AX25<->UDP)


 ===== ax25d.conf

 ===== wl2k.conf
paclink-unix not configured.


On Wed, Dec 23, 2020 at 7:44 AM John Spoonhower via groups.io <jpspoonhower=gmail.com@groups.io> wrote:
Hi Basil,
BTW running gp_verchk.sh reports the following after an update:
2020 12 23 07:20:49 EST: gp_install.sh: gps install script FINISHED

gpsd version built (3.19) does not match source version (3.21)

2020 12 23 07:20:49 EST: gp_verchk.sh: gpsd program update script FINISHED

pi@udrc:~/n7nix/gps $ ./gp_verchk.sh
gp_verchk.sh: Detected gpsd package.
gpsd: current version: 3.21, installed: 3.19

73, John, NX2I

On Sat, Dec 5, 2020 at 12:52 PM Basil Gunn <basil@...> wrote:

Release image nwdr18 Dec 5, 2020
last image nwdr17 Aug 21, 2020

Latest NWDR RPi image, current_image.img.xz has been updated to
nwdr18.img.xz at this location:
http://images.nwdigitalradio.com/downloads

This is the 4th image release this year. See the ChangeLog
(https://github.com/nwdigitalradio/n7nix/blob/master/ChangeLog) for
more information about what has changed.

To update your current image without using the new image the following
procedure will get you most of the changes. In a console on your
Raspberry Pi type the following:

**Back-up files you would rather not lose first**

sudo apt-get update
sudo apt-get dist-upgrade
cd
cd n7nix
git pull
cd config
./bin_refresh.sh

You can verify & update program versions with these scripts:
./bbs/bbs_verchk.sh
./xastir/xs_verchk.sh
./ax25/ax_verchk.sh
./gps/gp_verchk.sh
./hfprogs/hf_verchk.sh

The hf_verchk.sh script will update to current versions of these HAM
programs. js8call wsjtx fldigi flrig flmsg flamp fllog flxmlrpc

/Basil N7NIX






Re: NWDR18 image release announcement

John Spoonhower
 

Hi Basil,
BTW running gp_verchk.sh reports the following after an update:
2020 12 23 07:20:49 EST: gp_install.sh: gps install script FINISHED

gpsd version built (3.19) does not match source version (3.21)

2020 12 23 07:20:49 EST: gp_verchk.sh: gpsd program update script FINISHED

pi@udrc:~/n7nix/gps $ ./gp_verchk.sh
gp_verchk.sh: Detected gpsd package.
gpsd: current version: 3.21, installed: 3.19

73, John, NX2I


On Sat, Dec 5, 2020 at 12:52 PM Basil Gunn <basil@...> wrote:

Release image nwdr18 Dec 5, 2020
last image nwdr17 Aug 21, 2020

Latest NWDR RPi image, current_image.img.xz has been updated to
nwdr18.img.xz at this location:
http://images.nwdigitalradio.com/downloads

This is the 4th image release this year. See the ChangeLog
(https://github.com/nwdigitalradio/n7nix/blob/master/ChangeLog) for
more information about what has changed.

To update your current image without using the new image the following
procedure will get you most of the changes. In a console on your
Raspberry Pi type the following:

**Back-up files you would rather not lose first**

sudo apt-get update
sudo apt-get dist-upgrade
cd
cd n7nix
git pull
cd config
./bin_refresh.sh

You can verify & update program versions with these scripts:
./bbs/bbs_verchk.sh
./xastir/xs_verchk.sh
./ax25/ax_verchk.sh
./gps/gp_verchk.sh
./hfprogs/hf_verchk.sh

The hf_verchk.sh script will update to current versions of these HAM
programs. js8call wsjtx fldigi flrig flmsg flamp fllog flxmlrpc

/Basil N7NIX






Re: [Ham-Pi] Audio issues

 

Basil, 

Thanks very much.  I decided to start from scratch with a new HamPi image (1.2a) on a new 32GB card, and then followed the guidance you and John gave me.  It looks like I've gotten it pretty much all setup and working (WSJT-X and flidigi/flrig)  although I'm sure there will be more tweaking to do as I add apps/functionality.  

Again, thanks to you and John for the helpful advice.

John
WI6P


Re: [Ham-Pi] Audio issues

Basil Gunn
 

John WI6P,
A couple of things I noticed from your showudrc.sh output.

gps is not installed. Note the gpsd package that is in the Debian repo
does not support the DRAWS gps device very well.

The following script will build & install gpsd from source and configure
chrony. I have never tried this install on an image other than NWDR.

cd
cd n7nix/gps
./gp_install.sh

Also the DRAWS sensors have not been configured. Again I have never
tried this install on an image other than NWDR.

cd
cd n7nix/config
./sensor_update.sh -f

# run this command to confirm
sensors

Also your root file system is 77% full. If you decide to install a HamPI
image again I recommend using an SD card larger than 16GB.

/Basil n7nix


John Lauber <jlauber@ix.netcom.com> writes:

On Sun, Dec 20, 2020 at 06:38 PM, John D Hays - K7VE wrote:


./showudrc.sh
John--here is the output from showurdc.sh--

So what have I missed?

de WI6P
John

pi@draws-wi6p:~ $ cd n7nix/bin
pi@draws-wi6p:~/n7nix/bin $ ./showudrc.sh
==== Sound Card ====
udrc card number line: card 2: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
udrc is sound card #2


Re: [Ham-Pi] Audio issues

 

Yes it did...thanks again.

There is so much to learn....

John


Re: [Ham-Pi] Audio issues

 

No worries. Glad you found it. Did the output of the script help?


On Mon, Dec 21, 2020, 14:08 John Lauber <jlauber@...> wrote:
Problem solved!!  It was an ALSAMIXER setup problem...I now have everything working using the DRAWS hat with the HamPi Image.  Sorry to take up the bandwidth

73 
John
WI6P


Re: [Ham-Pi] Audio issues

 

Problem solved!!  It was an ALSAMIXER setup problem...I now have everything working using the DRAWS hat with the HamPi Image.  Sorry to take up the bandwidth

73 
John
WI6P


Re: [Ham-Pi] Audio issues

 

On Sun, Dec 20, 2020 at 06:38 PM, John D Hays - K7VE wrote:
./showudrc.sh

John--here is the output from showurdc.sh--

So what have I missed?  

de WI6P
John

pi@draws-wi6p:~ $ cd n7nix/bin
pi@draws-wi6p:~/n7nix/bin $ ./showudrc.sh
==== Sound Card ====
udrc card number line: card 2: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
udrc is sound card #2
==== ALSA Controls for Radio Transmit ====
LO Driver Gain  L:[-6.00dB] R:[-6.00dB]
PCM         L:[-24.50dB] R:[-24.50dB]
DAC Playback PT L:[P3] R:[P3]
LO Playback CM [Full Chip]
==== ALSA Controls for Radio Receive ====
ADC Level L:[-0.50dB] R:[-0.50dB]
IN1 L:[Off] R:[Off]
IN2 L:[10 kOhm] R:[Off]
 
==== Pi Ver ====
 Pi 4 Model B, Rev 1.4, 8GB mem, Mfg by Sony UK with WiFi
Hardware : BCM2711
Revision : d03114
Serial : 1000000078df7ff9
Model : Raspberry Pi 4 Model B Rev 1.4
 
==== Pi Firmware VideoCore Ver ====
Nov 30 2020 22:12:08 
Copyright (c) 2012 Broadcom
version ab1181cc0cb6df52bfae3b1d3fef0ce7c325166c (clean) (release) (start)
 
==== Pi Firmware EEPROM Ver ====
Sep  3 2020 13:11:43
version c305221a6d7e532693cc7ff57fddfc8649def167 (release)
timestamp 1599135103
update-time 0
capabilities 0x00000000
 
==== Pi Firmware EEPROM Config ====
[all]
BOOT_UART=0
WAKE_ON_GPIO=1
POWER_OFF_ON_HALT=0
DHCP_TIMEOUT=45000
DHCP_REQ_TIMEOUT=4000
TFTP_FILE_TIMEOUT=30000
TFTP_IP=
TFTP_PREFIX=0
BOOT_ORDER=0x1
SD_BOOT_MAX_RETRIES=3
NET_BOOT_MAX_RETRIES=5
[none]
FREEZE_VERSION=0
 
==== udrc Ver ====
Found a DRAWS
 
     HAT ID EEPROM
Name:        hat
Product:     Digital Radio Amateur Work Station
Product ID:  0x0004
Product ver: 0x0108
UUID:        68f027a3-9427-4a88-9dd2-065fec8e9b6e
Vendor:      NW Digital Radio
 
==== sys Ver ====
----- image version
head: cannot open '/var/log/udr_install.log' for reading: No such file or directory
----- /proc/version
Linux version 5.4.79-v7l+ (dom@buildbot) (gcc version 8.4.0 (Ubuntu/Linaro 8.4.0-3ubuntu1)) #1373 SMP Mon Nov 23 13:27:40 GMT 2020
 
cat: /etc/subversion: Is a directory
----- /etc/*version: 10.6
 
----- /etc/*release
PRETTY_NAME="HamPi 1.2 (December 2020)"
NAME="HamPi"
VERSION_ID="1,2"
VERSION="1.2 (December 2020)"
HOME_URL="http://hampi.radiowaves.ca"
SUPPORT_URL="https://groups.io/g/Ham-Pi"
BUG_REPORT_URL="https://github.com/dslotter/HamPi/issues/"
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
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"
 
----- lsb_release
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
Release: 10
Codename: buster
 
---- systemd
   Static hostname: draws-wi6p
         Icon name: computer
        Machine ID: 4890219a07b34906b35a0d48993814c7
           Boot ID: f6249cdacf584c95ad388896b3227ac8
  Operating System: Raspbian GNU/Linux 10 (buster)
            Kernel: Linux 5.4.79-v7l+
      Architecture: arm
        sd card id: 035344534333324780fa008942014600
 
---- sound modules
snd_soc_tlv320aic32x4_i2c    16384  261
snd_soc_tlv320aic32x4    40960  1 snd_soc_tlv320aic32x4_i2c
regmap_i2c             16384  4 ti_ads1015,sc16is7xx,rtl2832,snd_soc_tlv320aic32x4_i2c
snd_soc_core          200704  5 vc4,snd_soc_simple_card_utils,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_soc_simple_card
snd_pcm                94208  6 vc4,snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_bcm2835,snd_soc_core
snd                    73728  16 snd_compress,snd_timer,snd_soc_tlv320aic32x4,snd_bcm2835,snd_soc_core,snd_pcm
 
---- kernel
||/ Name               Version      Architecture Description
+++-==================-============-============-=====================================
ii  python3-ipykernel  4.9.0-1      all          IPython kernel for Jupyter (Python 3)
ii  raspberrypi-kernel 1.20201201-1 armhf        Raspberry Pi bootloader
 
---- Codec drivers
Found: snd-soc-tlv320aic32x4-i2c.ko, OK
Found: snd-soc-tlv320aic32x4.ko, OK
Directory: /proc/device-tree/soc/i2c@7e804000/tlv320aic32x4@18 exists and status is okay
 
---- syslog
 
---- dmesg
 
 
----- Dire Wolf DEVELOPMENT version 1.7 A (Dec  6 2020)
 
==== Filesystem ====
/dev/root        15G   11G  3.3G  77% /
 
==== boot config ====
disable_overscan=1
dtoverlay=
dtparam=audio=on
[pi4]
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
[all]
dtoverlay=draws,alsaname=udrc
force_turbo=1
 
---- gpsd
/usr/sbin/gpsd
gpsd: 3.21.1~dev (revision release-3.21-695-g2cc76873c)
● gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
 
---- chrony
crw------- 1 root root    239, 0 Dec 21 12:00 /dev/pps0
crw-rw---- 1 root dialout 236, 0 Dec 21 12:00 /dev/ttySC0
crw-rw---- 1 root dialout 236, 1 Dec 21 12:00 /dev/ttySC1
-- chrony sources
210 Number of sources = 4
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
^- 99-104-170-138.lightspee>     2   6   377    59  +1272us[+1584us] +/-   93ms
^* grom.polpo.org                2   6   377    58    -14us[ +299us] +/-   27ms
^+ segfault.boom.net             2   6   377    58  -1575us[-1262us] +/-   54ms
^+ x.ns.gin.ntt.net              2   6   377    58  +1562us[+1562us] +/-   39ms
-- chrony tracking
Reference ID    : 4113B2DB (grom.polpo.org)
Stratum         : 3
Ref time (UTC)  : Mon Dec 21 20:07:56 2020
System time     : 0.000082377 seconds slow of NTP time
Last offset     : +0.000312623 seconds
RMS offset      : 0.000938096 seconds
Frequency       : 8.631 ppm fast
Residual freq   : +0.096 ppm
Skew            : 5.137 ppm
Root delay      : 0.034072276 seconds
Root dispersion : 0.007781397 seconds
Update interval : 64.7 seconds
Leap status     : Normal
-- chrony sourcestats
210 Number of sources = 4
Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
==============================================================================
99-104-170-138.lightspee>  10   5   395     -0.125      8.715  +1827us   775us
grom.polpo.org             10   6   396     +1.526      7.041   +868us   576us
segfault.boom.net          10   5   395     +0.923     14.815  -2926us  1441us
x.ns.gin.ntt.net           10   6   395     -0.809      5.667  +1007us   414us
 
---- sensors
-rw-r--r-- 1 root root 352 Dec  6 14:27 /etc/sensors.d/draws
iio_hwmon-isa-0000
Adapter: ISA adapter
in1:          +2.04 V  
in2:          +2.50 V  
in3:          +0.01 V  
in4:          +0.01 V  
 
cpu_thermal-virtual-0
Adapter: Virtual device
temp1:        +59.9°C  
 
rpi_volt-isa-0000
Adapter: ISA adapter
in0:              N/A  
 
 
---- throttle
temp=58.9'C
throttled=0x0
 
---- locale
Locale country codes consistent among WiFi cfg file, iw reg & X11: US
grep: /var/log/udr_install.log: No such file or directory
core_config.sh has been run  time(s)
pi@draws-wi6p:~/n7nix/bin $ 


Re: [Ham-Pi] Audio issues

 

When you go to the DRAWS™/UDRC support group, you can use some diagnostic tools.

Install them by


Capture diagnostic info on the DRAWS™ install with

cd n7nix/bin
./showudrc.sh

Cut and paste the output/results to your request for help. (Cut and Paste from a terminal or ssh session, don't use screen shots).



On Sun, Dec 20, 2020 at 6:04 PM John D Hays - K7VE via groups.io <john=hays.org@groups.io> wrote:
Take your DRAWS™ support questions to https://nw-digital-radio.groups.io/g/udrc




On Sun, Dec 20, 2020, 15:50 Dave Slotter, W3DJS <slotter@...> wrote:
John Hays... Are you seeing this thread? Can you provide any hints?

73,

On Sat, Dec 19, 2020 at 7:34 PM John Lauber <jlauber@...> wrote:
Still tearing my hair out!  I've tried/checked everything I can think of but to no avail...has anyone been successful in getting the draws hat working on HamPi?  What am I doing wrong?

John 
WI6P


--
- Dave
  W3DJS


--
John D. Hays
Kingston, WA
K7VE

 


Re: [Ham-Pi] Audio issues

 

Take your DRAWS™ support questions to https://nw-digital-radio.groups.io/g/udrc




On Sun, Dec 20, 2020, 15:50 Dave Slotter, W3DJS <slotter@...> wrote:
John Hays... Are you seeing this thread? Can you provide any hints?

73,

On Sat, Dec 19, 2020 at 7:34 PM John Lauber <jlauber@...> wrote:
Still tearing my hair out!  I've tried/checked everything I can think of but to no avail...has anyone been successful in getting the draws hat working on HamPi?  What am I doing wrong?

John 
WI6P


--
- Dave
  W3DJS


Re: New to DRAWS - what order to troubleshoot installation/setup? #draws-manager #ft-817 #ft817 #draws #gps

Basil Gunn
 

Much progress.
Great to hear.

udrcver.sh (in /bin or /n7nx/bin, same result):
Found a DRAWS HAT ID EEPROM
Name: hat
Product: Digital Radio Amateur Work Station
Product ID: 0x0004
Product ver: 0x0108
UUID: 07ca235a-b510-43c0-8ec5-86e5b78e646f
Vendor: NW Digital Radio

You have the current latest version of DRAWS hat.

systemctl status chronyd:
Instead of using systemctl try using this script for a more complete
look at gpsd/chrony status.

cd
cd n7nix/gps
./verify_time.sh

gpsmon now shows data! Yaaay!
I was able to start ax25 and see a direwolf PID.
Good

tail -f /var/log/direwolf/direwolf.log gave:
Indicates you are not receiving any packets.
Assuming you tuned your radio to the APRS 2M frequency 144.390 you
should be seeing plenty of received packets.

Check squelch setting on radio and you may have a SQL/COS problem and
you will have to remove pin 6 from your mDin6 connector.

Read the first part from this link:
https://github.com/nwdigitalradio/n7nix/blob/master/docs/RADIO_APP_NOTES.md

Using ./btest.sh -P udr0 I can get the radio to switch to transmit and
hear the signal on a hand-held (on 144.39), but no raw packet shows on
aprs.fi.I am not too worried about that right now. Enough for one day.
Check deviation config, and distance to a working APRS gateway.

Also AX.25 tends to eat the first 2 transmitted packets after a
reset. It thinks they are TNC control packets. So always send 3 packets
after a power-on or ax25-restart.

*** Running as user: pi ***
Send a message beacon
Sent: /usr/local/sbin/beacon -c W4NKS-11 -d 'APUDR1 via WIDE1-1' -l -s udr0 :W4NKS :20 15:46:38 EST W4NKS mesg_beacon test from host drawspi on port udr0 Seq: 0


Re: New to DRAWS - what order to troubleshoot installation/setup? #draws-manager #ft-817 #ft817 #draws #gps

Microbes
 

Hi Again, Thanks for sticking with me.

Much progress.

New install using "current_image.img"

Yes on battery, tried a new one too.

udrcver.sh (in /bin or /n7nx/bin, same result):

Found a DRAWS HAT ID EEPROM Name: hat Product: Digital Radio Amateur Work Station Product ID: 0x0004 Product ver: 0x0108 UUID: 07ca235a-b510-43c0-8ec5-86e5b78e646f Vendor: NW Digital Radio

systemctl status chronyd:

chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-12-20 15:16:44 EST; 42min ago
Docs: man:chronyd(8)
man:chronyc(1)
man:chrony.conf(5)
Main PID: 611 (chronyd)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/chrony.service
├─611 /usr/sbin/chronyd -F -1
└─623 /usr/sbin/chronyd -F -1

Dec 20 15:16:44 drawspi chronyd[611]: Frequency 6.813 +/- 0.645 ppm read from /var/lib/chrony/chrony.drift
Dec 20 15:16:44 drawspi chronyd[611]: Loaded seccomp filter
Dec 20 15:16:44 drawspi systemd[1]: Started chrony, an NTP client/server.
Dec 20 15:17:17 drawspi chronyd[611]: Selected source 50.205.244.107
Dec 20 15:17:17 drawspi chronyd[611]: System clock wrong by 152.053096 seconds, adjustment started
Dec 20 15:19:49 drawspi chronyd[611]: System clock was stepped by 152.053096 seconds
Dec 20 15:30:38 drawspi chronyd[611]: Selected source 23.157.160.168
Dec 20 15:41:26 drawspi chronyd[611]: Selected source 50.205.244.107
Dec 20 15:44:13 drawspi chronyd[611]: Selected source GPS
Dec 20 15:44:13 drawspi chronyd[611]: Selected source PPS

gpsmon now shows data! Yaaay!


I was able to start ax25 and see a direwolf PID.

tail -f /var/log/direwolf/direwolf.log gave:

Dec 20 15:45:19 drawspi direwolf[1421]: KISS protocol set TXDELAY = 50 (*10mS units = 500 mS), port 1
Dec 20 15:45:19 drawspi direwolf[1421]: KISS protocol set TXtail = 10 (*10mS units = 100 mS), port 1
Dec 20 15:45:19 drawspi direwolf[1421]: KISS protocol set Persistence = 32, port 1
Dec 20 15:45:19 drawspi direwolf[1421]: KISS protocol set SlotTime = 20 (*10mS units = 200 mS), port 1
Dec 20 15:45:19 drawspi direwolf[1421]: KISS protocol set FullDuplex = 0, port 1
Dec 20 15:45:23 drawspi direwolf[1421]: Now connected to IGate server noam.aprs2.net (167.114.2.176)
Dec 20 15:45:23 drawspi direwolf[1421]: Check server status here http://167.114.2.176:14501
Dec 20 15:45:28 drawspi direwolf[1421]: [ig] # aprsc 2.1.5-g8af3cdc
Dec 20 15:45:28 drawspi direwolf[1421]: [ig] # logresp W4NKS verified, server T2CAWEST
Dec 20 15:46:38 drawspi direwolf[1421]: [0L] W4NKS-11>APUDR1,WIDE1-1::W4NKS :20 15:46:38 EST W4NKS mesg_beacon test from host drawspi on port udr0 Seq: 0~


Using ./btest.sh -P udr0 I can get the radio to switch to transmit and hear the signal on a hand-held (on 144.39), but no raw packet shows on aprs.fi.I am not too worried about that right now. Enough for one day.

*** Running as user: pi ***
Send a message beacon
Sent: /usr/local/sbin/beacon -c W4NKS-11 -d 'APUDR1 via WIDE1-1' -l -s udr0 :W4NKS :20 15:46:38 EST W4NKS mesg_beacon test from host drawspi on port udr0 Seq: 0


Thanks again for now.











Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Sunday, December 20, 2020 2:26 PM, Basil Gunn <basil@pacabunga.com> wrote:

I already ran through the "fix" for the new image version, which
states the draws-manager web app is disabled:
https://nw-digital-radio.groups.io/g/udrc/message/5111
That is an old post and is no longer relevant as the DRAWS sensor
overlay has been fixed in the latest Linux kernels since last August.

The following post describes what you need to do to get draws-manager
running with the latest NWDR18 image.

https://nw-digital-radio.groups.io/g/udrc/message/5311

As of now, chrony isn't using the GPS for time (shows #? instead of
#*). I thought that would be set up in the image already.
Chrony has been working with the DRAWS GPS for a long time.
It can sometimes take up to 15 minutes to get a satellite fix.

Do you have a CR1220 battery installed?

I am on separate PC responding, so I abbreviated some of the outputs
to reduce typing.
Learn how to ssh to your RPi and cut & paste into an email or forum post.

systemctl status chronyd returns: active(running), but no indication
of a GPS as a selected source.
What version of DRAWS do you have?
Need the output of: udrcver.sh

gpsmon show data scrolling at bottom, but no
latitude/longitude/speed/altitude values (all zero)
You do NOT have satellite fix yet.

Maybe the chrony not set up to take PPT?
chrony, gpsd and the DRAWS gps ARE setup properly on the NWDR images.


Re: New to DRAWS - what order to troubleshoot installation/setup? #draws-manager #ft-817 #ft817 #draws #gps

Basil Gunn
 

I already ran through the "fix" for the new image version, which
states the draws-manager web app is disabled:
https://nw-digital-radio.groups.io/g/udrc/message/5111
That is an old post and is no longer relevant as the DRAWS sensor
overlay has been fixed in the latest Linux kernels since last August.

The following post describes what you need to do to get draws-manager
running with the latest NWDR18 image.

https://nw-digital-radio.groups.io/g/udrc/message/5311

As of now, chrony isn't using the GPS for time (shows #? instead of
#*). I thought that would be set up in the image already.
Chrony has been working with the DRAWS GPS for a long time.
It can sometimes take up to 15 minutes to get a satellite fix.

Do you have a CR1220 battery installed?

I am on separate PC responding, so I abbreviated some of the outputs
to reduce typing.
Learn how to ssh to your RPi and cut & paste into an email or forum post.

systemctl status chronyd returns: active(running), but no indication
of a GPS as a selected source.
What version of DRAWS do you have?
Need the output of: udrcver.sh

gpsmon show data scrolling at bottom, but no
latitude/longitude/speed/altitude values (all zero)
You do NOT have satellite fix yet.

Maybe the chrony not set up to take PPT?
chrony, gpsd and the DRAWS gps ARE setup properly on the NWDR images.


Re: New to DRAWS - what order to troubleshoot installation/setup? #draws-manager #ft-817 #ft817 #draws #gps

Microbes
 

Thanks Basil.

HF to begin, I am new to digital modes and have worked with Windows and my IC-7300. In reality using on an FT818, but should be the same settings as 817 to start. I figured I can adjust settings for AZ25 once I get going.

I already ran through the "fix" for the new image version, which states the draws-manager web app is disabled:

https://nw-digital-radio.groups.io/g/udrc/message/5111

I see from your post, there are other options to set the ALSA, I used the ft817 script and the values changed; I assume to some that another person used for their rig.

Tuning the FM for VHF/UHF can be done if I get that far. As of now, chrony isn't using the GPS for time (shows #? instead of #*). I thought that would be set up in the image already.

I am on separate PC responding, so I abbreviated some of the outputs to reduce typing.

Following the check GPS link you provided:

To clarify what I meant by it "running"

systemctl status chronyd returns: active(running), but no indication of a GPS as a selected source.

gpsmon show data scrolling at bottom, but no latitude/longitude/speed/altitude values (all zero)

Antenna has a clear view of sky.

cgps show no values in the boxed area, lots of "n/a"

underneath, this refreshes every second:

{"class":"TPV","device"":"/dev/ttySC0","mode":1,"time":"changes-everysecond", "ept":0.005}

running chronyc sourcestats give:

GPS 0 0 0 +0.0000 2000.000 +0ns 4000ms
PPT is same
then several web sources listed.

Maybe the chrony not set up to take PPT?

chronyc tracking shows a web server for the Reference ID


I am going to run through the complete installation again, using the ft817 script.

For "Third Boot" on the walk-through it may be helpful to edit the statement "You must set your ALSA configuration for your particular radio at this time" with instruction on how to do that, which seems to be either with draws-manager, or with alsamixer, or by running a script.

Thanks again for your help. I think if folks have experience setting up Pis to run digital modes without the DRAWS hat, a lot of the tools are already understood.

-S


Re: New to DRAWS - what order to troubleshoot installation/setup? #draws-manager #ft-817 #ft817 #draws #gps

Basil Gunn
 

on the "Third Boot" stage , it states:
"You must set your ALSA configuration for your particular radio at this time" - with no instruction on what that means or how to do it.

I followed a video online and got "alsa-show.sh" to show different values, I assume for the FT817.
You are not providing any information about which HF or VHF/UHF
radio on the FT817 you are using.

Assuming you want packet on your VHF/UHF radio working, like any TNC
or sound card you need to set the FM deviation properly.

There is a section on how to set your deviation here:
https://github.com/nwdigitalradio/n7nix/tree/master/deviation

You can run run draws-manager to help set that up.
Or you can set ALSA settings with the alsamixer program
Or you can run the setalsa-ft817.sh script

https://github.com/nwdigitalradio/n7nix/blob/master/docs/DRAWS_ALSA.md

Need help with: Do need the radio connect with control cable and
powered up during any of the DRAWS set-up?
No but the DRAWS hat needs to be installed. The left mDin6 connector is
direwolf port 0.

I can't figure out if I am supposed to try to get draws_manager to run
or not.
This was brought up in the forums last week:

https://nw-digital-radio.groups.io/g/udrc/topic/can_t_access_draws_manager/76528127?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,76528127

# To install the latest version of draws-manager
cd
cd n7nix
git pull
cd manager
sudo su
./install.sh

I had it running in the past, but can't get it to run now and I read
it is not compatible with current sensor files.
That was fixed about 6 months ago

So, do I need it?
It is a nice tool to use.

Are there ways to change the same values without the web interface
(always fails to connect and went through other troubleshooting posted
here, gave up).
alsamixer
or
just run the script.
setalsa-ft817.sh

Do I need GPS working up-front?
I can run gpsd, and it is listed as active an running, but no
longitude or latitude shows up.
Not sure what you mean. gpsd is already running on the NWDR image.
If you want to verify the gps follow the examples under Check GPS

https://github.com/nwdigitalradio/n7nix/blob/master/docs/VERIFY_CONFIG.md#check-gps

I suspect DRAWS doesn't see the antenna.
It helps to put your antenna close to a window.

Do I focus on getting draws_manager to run or get the gps to report data?

Maybe someone can point me to a step-by-step walk through, but I
haven't found one.
The "Getting Started Guide" found in the wiki is the step-by-step guide
you want to use. There are a number of links in that guide for other
documentation for example under '3. Third boot' there is a link for
verifying your installation.

https://github.com/nwdigitalradio/n7nix/blob/master/docs/VERIFY_CONFIG.md

Be aware that you will probably need different alsa settings for the HF
radio FT817 and the vhf/uhf radio. Search the forum for your radio for
more hints.
https://nw-digital-radio.groups.io/g/udrc/search?q=ft817

If I remember correctly I had to remove pin 6 on the mDin6 connector to
get audio working on the FT-817. This was discussed on the forum here:

https://nw-digital-radio.groups.io/g/udrc/topic/33061161#4083


New to DRAWS - what order to troubleshoot installation/setup? #draws-manager #ft-817 #ft817 #draws #gps

Microbes
 

I bought the DRAWS hat in the summer with the intent of using an FT817 for digital on a pi4 B.

I gave up then after getting gps to work, but never getting radio control.

I recently revisited for the holidays - installed fresh image ( current_image ) and tried again. Following the wiki:

on the "Third Boot" stage , it states:

"You must set your ALSA configuration for your particular radio at this time" - with no instruction on what that means or how to do it.  

I followed a video online and got "alsa-show.sh" to show different values, I assume for the FT817. 

Need help with: 

Do  need the radio connect with control cable and powered up during any of the DRAWS set-up?

I can't figure out if I am supposed to try to get draws_manager to run or not. I had it running in the past, but can't get it to run now and I read it is not compatible with current sensor files.
 So, do I need it? Are there ways to change the same values without the web interface (always fails to connect and went through other troubleshooting posted here, gave up).

Do I need GPS working up-front?  I can run gpsd, and it is listed as active an running, but no longitude or latitude shows up. I suspect DRAWS doesn't see the antenna.

Do I focus on getting draws_manager to run or get the gps to report data?

Maybe someone can point me to a step-by-step walk through, but I haven't found one. 

I appreciate any help. 










Re: Can't access Draws Manager

 

You should turn DRAWS™ Manager off when not in use.   It is basically a configuration application. 

You can use systemctl to turn it on and off. To make it automatically start and stop you can use enable and disable. 

Try

man systemctl



On Fri, Dec 18, 2020, 09:21 Tim Huffaker <thuffaker@...> wrote:
Basil,
I re-imaged with a fresh copy of V18.  Ran this script:
cd
cd n7nix
git pull
cd manager <---- you didn't do this
sudo su
./install.sh
Now I have Draws manager running.  
Do I need to restart Draws manager anytime or does it run all the time?
thank you for your help. 
Tim 
KM4ESU


Re: Can't access Draws Manager

Tim Huffaker
 

Basil,
I re-imaged with a fresh copy of V18.  Ran this script:
cd
cd n7nix
git pull
cd manager <---- you didn't do this
sudo su
./install.sh
Now I have Draws manager running.  
Do I need to restart Draws manager anytime or does it run all the time?
thank you for your help. 
Tim 
KM4ESU


Re: Can't access Draws Manager (slightly off topic)

Daniel VE3NI
 

Basil,

Thanks for the explanation.

Daniel

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Basil Gunn
Sent: Friday, December 18, 2020 2:01 AM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] Can't access Draws Manager (slightly off
topic)


sudo apt-get update
sudo apt-get dist-upgrade
cd
cd n7nix
git pull
cd config
./bin_refresh.sh
This is exactly right. This will get almost all of the contents of the
latest image. I try to keep everything updated via scripts. If you are using
some of the HF programs you should also do:

cd
cd n7nix/hfprogs
./hf_verchk.sh

# To do the actual update add a -u
./hf_verchk.sh -u

# For the NWDR18 image at this time everything is current.

cd hfprogs/
./hf_verchk.sh

js8call: current version: 2.2.0, installed: 2.2.0
wsjtx: current version: 2.2.2, installed: 2.2.2
Library: libflxmlrpc IS loaded.
flxmlrpc: current version: 0.1.4, installed: 0.1.4
fldigi: current version: 4.1.17, installed: 4.1.17
flrig: current version: 1.3.53, installed: 1.3.53
flmsg: current version: 4.0.17, installed: 4.0.17
flamp: current version: 2.2.05, installed: 2.2.05
fllog: current version: 1.2.6, installed: 1.2.6

Everything that makes sense to get from the Debian/Raspberry Pi OS
repositories I do. For most of the HAM programs I try to use their own
repositories since they are generally not maintained in the Debian repo any
way.

My image started out as NWDR16

I have been using the commands below after each release announcement.

sudo apt-get update
sudo apt-get dist-upgrade
cd
cd n7nix
git pull
cd config
./bin_refresh.sh

After running these commands I am running the equivalent of the NWDR
released software?

Just want to be sure that I am doing it right.

Thanks,
Daniel VE3NI


-----Original Message-----
From: udrc@nw-digital-radio.groups.io
<udrc@nw-digital-radio.groups.io> On Behalf Of Basil Gunn
Sent: Thursday, December 17, 2020 7:18 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] Can't access Draws Manager


I won't discourage someone from installing the latest version of some
tool but a lot of time has gone into making sure that what is on the
image actually works. I don't have time to support anything other than
what is on the image. Perhaps someone else on the forum can help.

To be clear many/most of the HAM apps on the image are the latest
version and there are scripts on the image to keep them that way.
I used to use the latest version of nodejs, been down that road and
currently don't want or need to do that.

You should confirm that your image started out as NWDR18:

head -n1 /var/log/udr_install.log

2020 12 04 13:45:55 PST: SD image version: nwdr18

Also:

aplay -l
showudrc.sh

Did you follow the getting started guide?
https://nw-digital-radio.groups.io/g/udrc/wiki/8921


Re: Can't access Draws Manager (slightly off topic)

Basil Gunn
 

sudo apt-get update
sudo apt-get dist-upgrade
cd
cd n7nix
git pull
cd config
./bin_refresh.sh
This is exactly right. This will get almost all of the contents of the
latest image. I try to keep everything updated via scripts. If you are
using some of the HF programs you should also do:

cd
cd n7nix/hfprogs
./hf_verchk.sh

# To do the actual update add a -u
./hf_verchk.sh -u

# For the NWDR18 image at this time everything is current.

cd hfprogs/
./hf_verchk.sh

js8call: current version: 2.2.0, installed: 2.2.0
wsjtx: current version: 2.2.2, installed: 2.2.2
Library: libflxmlrpc IS loaded.
flxmlrpc: current version: 0.1.4, installed: 0.1.4
fldigi: current version: 4.1.17, installed: 4.1.17
flrig: current version: 1.3.53, installed: 1.3.53
flmsg: current version: 4.0.17, installed: 4.0.17
flamp: current version: 2.2.05, installed: 2.2.05
fllog: current version: 1.2.6, installed: 1.2.6

Everything that makes sense to get from the Debian/Raspberry Pi OS
repositories I do. For most of the HAM programs I try to use their own
repositories since they are generally not maintained in the Debian repo
any way.

My image started out as NWDR16

I have been using the commands below after each release announcement.

sudo apt-get update
sudo apt-get dist-upgrade
cd
cd n7nix
git pull
cd config
./bin_refresh.sh

After running these commands I am running the equivalent of the NWDR
released software?

Just want to be sure that I am doing it right.

Thanks,
Daniel VE3NI


-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Basil Gunn
Sent: Thursday, December 17, 2020 7:18 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] Can't access Draws Manager


I won't discourage someone from installing the latest version of some tool
but a lot of time has gone into making sure that what is on the image
actually works. I don't have time to support anything other than what is on
the image. Perhaps someone else on the forum can help.

To be clear many/most of the HAM apps on the image are the latest version
and there are scripts on the image to keep them that way.
I used to use the latest version of nodejs, been down that road and
currently don't want or need to do that.

You should confirm that your image started out as NWDR18:

head -n1 /var/log/udr_install.log

2020 12 04 13:45:55 PST: SD image version: nwdr18

Also:

aplay -l
showudrc.sh

Did you follow the getting started guide?
https://nw-digital-radio.groups.io/g/udrc/wiki/8921

681 - 700 of 5981