Re: Config check now not acting right
#earlyadopter
#beta13
K4SPB
Also ran these checks:
pi@SpoobyDRAWS:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 7/7
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
pi@SpoobyDRAWS:~ $ chk_conflict.sh
Check udrc driver conflict for Kernel release: 4.14.98-v7+
=== Loaded module check
=== Sound card check
udrc driver not loaded.
pi@SpoobyDRAWS:~ $ chk_bootcfg.sh
Verify IF dtoverlay= is set properly
dtoverlay currently set to: dtoverlay=draws,alsaname=udrc
dtoverlay for DRAWS OK
Verify IF dtparam=audio is set properly
Last line in /boot/config.txt OK
|
|
Config check now not acting right
#earlyadopter
#beta13
K4SPB
I started with a fresh write of beta 13 the other day that I configured and then check without issue. Only think I've done since is update and upgrade which ran into a kernel upgrade issue I've seen repeatedly and ran KM4ACK's auto hotspot script. Now outputs of sndcard.sh, alsa-show.sh, and gpsmon are all giving negative information.
My most recent config checks: followed by the outputs of gpsmon and cgps pi@SpoobyDRAWS:~ $ cd ~/n7nix/bin
pi@SpoobyDRAWS:~/n7nix/bin $ ./piver.sh
Pi 3 Model B+ Mfg by Sony UK
Has WiFi
pi@SpoobyDRAWS:~/n7nix/bin $ ./udrcver.sh
Found a DRAWS
HAT ID EEPROM
Name: hat
Product: Digital Radio Amateur Work Station
Product ID: 0x0004
Product ver: 0x0405
UUID: 3036072f-20a8-441c-9901-4e8abec0fab4
Vendor: NW Digital Radio
pi@SpoobyDRAWS:~/n7nix/bin $ cd
pi@SpoobyDRAWS:~ $ cd ~/bin
pi@SpoobyDRAWS:~/bin $ ./sndcard.sh
No udrc sound card found.
pi@SpoobyDRAWS:~/bin $ ls
alsa-show.sh crontab.txt pluweb-sysd.sh setalsa-tmv71a.sh
ap-start.sh dstar-stop.sh prog_refresh.sh setalsa-udrc-alinco.sh
ap-status.sh gatewaylist.sh radiopwr.sh setalsa-udrc-din6.sh
ap-stop.sh hwtest.sh rmslist.sh set-time.sh
ax25-start iptable-check.sh rmsverlist.sh showudrc.sh
ax25-status iptable-flush.sh setalsa-default.sh sndcard.sh
ax25-stop iptable-up.sh setalsa-dr1x.sh sysver.sh
chk_bootcfg.sh manager-sysd.sh setalsa-ft817.sh udrcver.sh
chk_conflict.sh mgr-stop.sh setalsa-ic7000.sh
chk_perm.sh piver.sh setalsa-not-dr1x.sh
pi@SpoobyDRAWS:~/bin $ alsa-show.sh
===== ALSA Controls for Radio Transmit =====
Invalid card number.
Invalid card number.
Invalid card number.
LO Driver Gain L: R:
Invalid card number.
Invalid card number.
Invalid card number.
PCM L: R:
Invalid card number.
===== ALSA Controls for Radio Receive =====
Invalid card number.
Invalid card number.
Invalid card number.
ADC Level L: R:
Invalid card number.
Invalid card number.
Invalid card number.
Invalid card number.
Invalid card number.
Invalid card number.
Invalid card number.
Invalid card number.
Invalid card number.
Invalid card number.
Invalid card number.
Invalid card number.
IN1 L:[] R:[]
IN2 L:[] R:[]
CM L:[] R:[]
pi@SpoobyDRAWS:~/bin $ cd
pi@SpoobyDRAWS:~ $ gpsmon
pi@SpoobyDRAWS:~ $ cgps
cgps: caught signal 2
pi@SpoobyDRAWS:~ $ sudo nano /etc/default/gpsd
pi@SpoobyDRAWS:~ $ sudo systemctl enable gpsd && sudo systemctl restart gpsd
Synchronizing state of gpsd.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable gpsd
pi@SpoobyDRAWS:~ $
pi@SpoobyDRAWS:~ $
pi@SpoobyDRAWS:~ $ sudo systemctl status gpsd
● gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: ena
Active: active (running) since Fri 2019-07-12 11:31:02 UTC; 26s ago
Process: 2246 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (
Main PID: 2247 (gpsd)
CGroup: /system.slice/gpsd.service
└─2247 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
Jul 12 11:31:02 SpoobyDRAWS systemd[1]: Starting GPS (Global Positioning System)
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: device open of /dev/tty
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: read-only device open o
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: initial GPS device /dev/ttyS
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: device open of /dev/pps
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: read-only device open o
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: initial GPS device /dev/pps0
Jul 12 11:31:02 SpoobyDRAWS systemd[1]: Started GPS (Global Positioning System)
lines 1-16/16 (END)
● gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled
Active: active (running) since Fri 2019-07-12 11:31:02 UTC; 26s ago
Process: 2246 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code
Main PID: 2247 (gpsd)
CGroup: /system.slice/gpsd.service
└─2247 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
Jul 12 11:31:02 SpoobyDRAWS systemd[1]: Starting GPS (Global Positioning System) Dae
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: device open of /dev/ttySC0
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: read-only device open of /d
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: initial GPS device /dev/ttySC0 o
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: device open of /dev/pps0 fa
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: read-only device open of /d
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: initial GPS device /dev/pps0 ope
Jul 12 11:31:02 SpoobyDRAWS systemd[1]: Started GPS (Global Positioning System) Daem
~
~
~
~
~
~
~
lines 1-16/16 (END)
● gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-07-12 11:31:02 UTC; 26s ago
Process: 2246 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exi
Main PID: 2247 (gpsd)
CGroup: /system.slice/gpsd.service
└─2247 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
Jul 12 11:31:02 SpoobyDRAWS systemd[1]: Starting GPS (Global Positioning System) Daemon.
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: device open of /dev/ttySC0 fail
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: read-only device open of /dev/t
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: initial GPS device /dev/ttySC0 open
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: device open of /dev/pps0 failed
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: read-only device open of /dev/p
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: initial GPS device /dev/pps0 open fa
Jul 12 11:31:02 SpoobyDRAWS systemd[1]: Started GPS (Global Positioning System) Daemon.
~
~
~
~
~
~
~
pi@SpoobyDRAWS:~ $ gpsmon
pi@SpoobyDRAWS:~ $ sudo systemctl status gpsd
● gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-07-12 11:31:02 UTC; 5min ago
Process: 2246 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
Main PID: 2247 (gpsd)
CGroup: /system.slice/gpsd.service
└─2247 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: initial GPS device /dev/pps0 open failed
Jul 12 11:31:02 SpoobyDRAWS systemd[1]: Started GPS (Global Positioning System) Daemon.
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: device open of /dev/ttySC0 failed: No such file or directory - re
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: read-only device open of /dev/ttySC0 failed: No such file or dire
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: /dev/ttySC0: device activation failed.
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: /dev/ttySC0: activation failed, freeing device
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: device open of /dev/pps0 failed: No such file or directory - retr
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: read-only device open of /dev/pps0 failed: No such file or direct
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: /dev/pps0: device activation failed.
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: /dev/pps0: activation failed, freeing device
...skipping...
● gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-07-12 11:31:02 UTC; 5min ago
Process: 2246 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
Main PID: 2247 (gpsd)
CGroup: /system.slice/gpsd.service
└─2247 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
Jul 12 11:31:02 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: initial GPS device /dev/pps0 open failed
Jul 12 11:31:02 SpoobyDRAWS systemd[1]: Started GPS (Global Positioning System) Daemon.
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: device open of /dev/ttySC0 failed: No such file or directory - re
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: read-only device open of /dev/ttySC0 failed: No such file or dire
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: /dev/ttySC0: device activation failed.
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: /dev/ttySC0: activation failed, freeing device
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: device open of /dev/pps0 failed: No such file or directory - retr
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: SER: read-only device open of /dev/pps0 failed: No such file or direct
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: /dev/pps0: device activation failed.
Jul 12 11:32:30 SpoobyDRAWS gpsd[2247]: gpsd:ERROR: /dev/pps0: activation failed, freeing device
~
~
~
~
~
lines 1-18/18 (END)
pi@SpoobyDRAWS:~ $ gpsmon
pi@SpoobyDRAWS:~ $ cgps
cgps: caught signal 2
pi@SpoobyDRAWS:~ $ sudo systemctl restart gpsd
pi@SpoobyDRAWS:~ $ sudo systemctl status gpsd
● gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-07-12 11:37:54 UTC; 5s ago
Process: 2988 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
Main PID: 2989 (gpsd)
CGroup: /system.slice/gpsd.service
└─2989 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
Jul 12 11:37:54 SpoobyDRAWS systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jul 12 11:37:54 SpoobyDRAWS systemd[1]: Started GPS (Global Positioning System) Daemon.
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: SER: device open of /dev/ttySC0 failed: No such file or directory - re
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: SER: read-only device open of /dev/ttySC0 failed: No such file or dire
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: initial GPS device /dev/ttySC0 open failed
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: SER: device open of /dev/pps0 failed: No such file or directory - retr
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: SER: read-only device open of /dev/pps0 failed: No such file or direct
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: initial GPS device /dev/pps0 open failed
pi@SpoobyDRAWS:~ $ sudo systemctl status gpsd
● gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-07-12 11:37:54 UTC; 21s ago
Process: 2988 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
Main PID: 2989 (gpsd)
CGroup: /system.slice/gpsd.service
└─2989 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
Jul 12 11:37:54 SpoobyDRAWS systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jul 12 11:37:54 SpoobyDRAWS systemd[1]: Started GPS (Global Positioning System) Daemon.
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: SER: device open of /dev/ttySC0 failed: No such file or directory - re
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: SER: read-only device open of /dev/ttySC0 failed: No such file or dire
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: initial GPS device /dev/ttySC0 open failed
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: SER: device open of /dev/pps0 failed: No such file or directory - retr
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: SER: read-only device open of /dev/pps0 failed: No such file or direct
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: initial GPS device /dev/pps0 open failed
pi@SpoobyDRAWS:~ $ sudo systemctl status gpsd
● gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-07-12 11:37:54 UTC; 1min 5s ago
Process: 2988 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
Main PID: 2989 (gpsd)
CGroup: /system.slice/gpsd.service
└─2989 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
Jul 12 11:37:54 SpoobyDRAWS systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jul 12 11:37:54 SpoobyDRAWS systemd[1]: Started GPS (Global Positioning System) Daemon.
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: SER: device open of /dev/ttySC0 failed: No such file or directory - re
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: SER: read-only device open of /dev/ttySC0 failed: No such file or dire
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: initial GPS device /dev/ttySC0 open failed
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: SER: device open of /dev/pps0 failed: No such file or directory - retr
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: SER: read-only device open of /dev/pps0 failed: No such file or direct
Jul 12 11:37:54 SpoobyDRAWS gpsd[2989]: gpsd:ERROR: initial GPS device /dev/pps0 open failed
gpsmon: tcp://localhost:2947 JSON slave driver>
(86) {"class":"VERSION","release":"3.18.1","rev":"3.18.1","proto_major":3,"proto_minor":13}
(32) {"class":"DEVICES","devices":[]}
(122) {"class":"WATCH","enable":true,"json":false,"nmea":false,"raw":2,"scaled":false,"timing":false,"split24":false,"pps"
:true}
cgps:
┌───────────────────────────────────────────┐┌──────────────────Seen 0/Used 0┐
│ Time: n/a ││ PRN Elev Azim SNR Use │
│ Latitude: n/a ││ │
│ Longitude: n/a ││ │
│ Altitude: n/a ││ │
│ Speed: n/a ││ │
│ Heading: n/a ││ │
│ Climb: n/a ││ │
│ Status: NO FIX (0 secs) ││ │
│ Long Err (XDOP, EPX): n/a , n/a ││ │
│ Lat Err (YDOP, EPY): n/a , n/a ││ │
│ Alt Err (VDOP, EPV): n/a , n/a ││ │
│ 2D Err (HDOP, CEP): n/a , n/a ││ │
│ 3D Err (PDOP, SEP): n/a , n/a ││ │
│ Time Err (TDOP): n/a ││ │
│ Geo Err (GDOP): n/a ││ │
│ ECEF X, VX: n/a n/a ││ │
│ ECEF Y, VY: n/a n/a ││ │
│ ECEF Z, VZ: n/a n/a ││ │
│ Speed Err (EPS): n/a ││ │
│ Head Err (EPD): n/a ││ │
│ Time offset: n/a ││ │
│ Grid Square: n/a ││ │
└───────────────────────────────────────────┘└─────────────────────────────────┘
{"class":"VERSION","release":"3.18.1","rev":"3.18.1","proto_major":3,"proto_minor":13}
{"class":"DEVICES","devices":[]}
{"class":"WATCH","enable":true,"json":true,"nmea":false,"raw":0,"scaled":false,"timing":false,"split24":false,"pps":false}
I'm relatively inexperienced with RPi although I've been running linux for a couple years I don't any deep technical background. All help is appreciated.
Thanks, K4SPB
|
|
Re: X11 forwarding
Paul Johnson
Linux = open source = choices (;
toggle quoted messageShow quoted text
On Wed, 2019-07-17 at 11:30 -0700, John D Hays - K7VE wrote:
I find the built in VNC to be pretty efficient and better than X11
|
|
Re: X11 forwarding
I find the built in VNC to be pretty efficient and better than X11
On Wed, Jul 17, 2019 at 11:26 AM Paul Johnson <ve7dhm@...> wrote: Just an info note. I found fldigi GUI response very poor to almost --
John D. Hays Kingston, WA K7VE
|
|
X11 forwarding
Paul Johnson
Just an info note. I found fldigi GUI response very poor to almost
a "locked up" response when I was running it remotely via a ssh connection. I changed the encryption algorithm on my command line login and now get a real time response from the GUI. This was with a Pi 3B+ with DRAWS hat over a wireless connection. ssh -XC -c aes128-ctr user@IPaddress Paul VE7DHM
|
|
Re: DRAWS on Pi 3b+ with Raspbian Buster
#draws
Frank Ivan
Hi Jon,
toggle quoted messageShow quoted text
Can you tell me where you got the snd-soc-tlv320aic32x4-i2c.ko file and do you also need UDRC and snd-soc-tlv320aic32x4.ko? Is there a ax25.ko? Where do you put those files in /lib/modules? Did you need to do a insmod command? Thanks Frank - K0FEI
|
|
Re: Echolink install on Raspi3 and UDRC II with Direwolf from n7nix
Hi Wim,
I would be interested to know what repeater you connected and if all went well to simultaneously use svxlink/echolink and direwolf/aprs on an RPi with Draws. Did you install and configure svxlink/echolink independently of the Draws software or are there any interdependencies? Thanks and 73 sa0bxi
|
|
Re: prog_refresh.sh error?
Thanks Edd & Jim for verifying the changes I made. I appreciate your
toggle quoted messageShow quoted text
support. /Basil n7nix Jim Erickson <jim@va7shg.ca> writes:
I didn’t save the output, but mine successfully detected that gpsd was
|
|
Re: prog_refresh.sh error?
Edward Seeliger
Basil, after the update above, I ran prog_refresh.sh again and it updates as it should without the previous errors.
It also updated XASTIR to a new version. It shows the correct GPSD version is installed. Thanks for your help and all the (prompt) support you provide here for all of us! Edd - KD5M
|
|
Re: prog_refresh.sh error?
Jim Erickson
I didn’t save the output, but mine successfully detected that gpsd was a different version, downloaded the new version (3.19), compiled it and installed it in place. That appears to have fixed the same problem I was having Basil.
toggle quoted messageShow quoted text
73 Jim
|
|
Re: prog_refresh.sh error?
Edward Seeliger
Here is the console output after git pull:
pi@KD5MDRAWS:~/n7nix/gps $ ./gp_verchk.sh gp_verchk.sh: Detected gpsd package. gpsd: current version: 3.19, installed: 3.19 pi@KD5MDRAWS:~/n7nix/gps $ ./gp_verchk.sh -u gp_verchk.sh: Detected gpsd package. gpsd: Running current version 3.19 pi@KD5MDRAWS:~/n7nix/gps $ sudo systemctl restart gpsd pi@KD5MDRAWS:~/n7nix/gps $ ./gp_verchk.sh gp_verchk.sh: Detected gpsd package. gpsd: current version: 3.19, installed: 3.19 pi@KD5MDRAWS:~/n7nix/gps $ Edd - KD5M
|
|
Re: prog_refresh.sh error?
Edd,
toggle quoted messageShow quoted text
I made changes to both gp_verchk.sh & gp_install.sh to correct problem parsing version string. Could you please execute the following console commands & send me the console output. cd cd n7nix/gps git pull ./gp_verchk.sh ./gp_verchk.sh -u sudo systemctl restart gpsd ./gp_verchk.sh Thanks, /Basil n7nix Edward Seeliger <eseeliger@earthlink.net> writes:
For the past week or more, if I run the prog_refresh.sh script, it chooses to build GPSD (again) and ends with the following:
|
|
prog_refresh.sh error?
Edward Seeliger
For the past week or more, if I run the prog_refresh.sh script, it chooses to build GPSD (again) and ends with the following:
Setup default gpsd file Setup default chrony.conf file Synchronizing state of gpsd.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable gpsd Failed to reload daemon: Method call timed out Failed to reload daemon: Method call timed out Synchronizing state of chrony.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable chrony tee: /var/log/udr_install.log: Permission denied 2019 07 16 08:26:42 CDT: gp_install.sh: gps install script FINISHED Debug: Testing 3.19.tar, ver: 3.19 gpsd version built (3.19) does not match source version (3.19.tar) It also requires me to enter my password 12-14 times near the end as it attempts to update Is chrony.conf and enable GPSD It otherwise appears to run as it should - this AM it built the new WSJTX version. Is this an error that needs to be fixed or do I need to change/correct something on my device? Thanks for your time and help. Edd - KD5M
|
|
JT Croteau <jt.tobit@...>
Thanks for the confirmation Jim and John. I think I will get the 3B+ as I run completely off of solar power and the 3B+ will use less power than the 4. 73 N1ESE
On Tue, Jul 16, 2019, 11:17 John D Hays - K7VE <john@...> wrote:
|
|
DRAWS™ is decoding FT8 and other signals just fine on the Raspberry Pi 3 (B/B+) without even challenging CPU utilization. If other groups are reporting problems, it may have more to do with the hardware they are using. DRAWS™ is a purpose built system for amateur radio applications.
On Tue, Jul 16, 2019 at 9:04 AM JT Croteau <jt.tobit@...> wrote: Does the Pi 3B+ decode FT8 properly or should I wait on the Pi 4 for the faster CPU? I'm getting mixed reports from other Raspberry groups. --
John D. Hays Kingston, WA K7VE
|
|
Jim Erickson
They all work fine on my Pi 3B+. I also just did a ./prog_refresh.sh this morning and got the latest WSJT-X 2.1 installed. Haven’t tried decoding FT-8 with the latest version, but has worked fine for me for previous versions.
toggle quoted messageShow quoted text
73 VA7SHG/VE7TGZ
|
|
JT Croteau <jt.tobit@...>
Does the Pi 3B+ decode FT8 properly or should I wait on the Pi 4 for the faster CPU? I'm getting mixed reports from other Raspberry groups.
I already have a DRAWS and just waiting to see how the Pi 4 testing continues. Thanks N1ESE
|
|
Re: Not booting
Douglas
Thank you. I tried on a pi without the hat and it did not boot. Does draws 11 have the same isdue with updating? KI7LIK Granada Estates Neighborhood Watch
On Sun, Jul 14, 2019, 17:33 John D Hays - K7VE <john@...> wrote:
|
|
Re: DRAWS on Pi 3b+ with Raspbian Buster
#draws
To all using an HT with DRAWS:
Clamp on Ferrite Beads are recommended on both ends of the Cable to prevent RFI from interfering with the Pi. 73 Bryan K7UDR
|
|
Re: Yaesu DR-2X with UDRC
I tried when the DR-2X first came out with no success and have not heard of anyone having success with it. You would need direct access to the discriminator, modulator, and PTT with no interference from firmware.
On Sun, Jul 14, 2019, 19:31 Nathan Dykstra <ngjdykstra@...> wrote: This is an old thread, but is UDRC operation with the DR-2X still impossible?
|
|