Date   
Re: GPS not working #gps #gpsd

Mike - KB0FX
 

Chris,

Glad to hear everything is working for you now! As you have found, sometimes it is simpler to just start over with a fresh image on the Raspberry Pi. 

73

Mike - KB0FX

On Fri, Jan 18, 2019 at 10:27 AM oe8bck <christof.bodner@...> wrote:
Hi,

Well, I finally decided to do a fresh install of the BETA7 with the external 12V-supply. The reason was the 3rd line in Mikes log, because there it's stated that there is a sound chip.

So I transfered the image to the SD-card and after following the "Getitng Started" instructions, I checked the status via bin/showudrc.sh. And now there is stated that the audio card is found!
And gpsd is working, too!

Thanks a lot for all the support I got.

Lessons Learned: If you are using Raspberry Pi 3, you have to supply the system via the external 12V supply, otherwise you get strange behaviour!

73 de Christof

Re: GPS not working #gps #gpsd

oe8bck
 

Hi,

Well, I finally decided to do a fresh install of the BETA7 with the external 12V-supply. The reason was the 3rd line in Mikes log, because there it's stated that there is a sound chip.

So I transfered the image to the SD-card and after following the "Getitng Started" instructions, I checked the status via bin/showudrc.sh. And now there is stated that the audio card is found!
And gpsd is working, too!

Thanks a lot for all the support I got.

Lessons Learned: If you are using Raspberry Pi 3, you have to supply the system via the external 12V supply, otherwise you get strange behaviour!

73 de Christof

Re: GPS not working #gps #gpsd

Mike - KB0FX
 

Chris,

Below is the output from my showudrc.sh. Since you were having problems with providing enough power to your DRAWS Pi-Hat it may be simpler for you to just flash the current  SD RAM with the Beta 7 version of Compass and then run the app_config.sh to build the core system. 

73

Mike - KB0FX

cd
cd n7nix/config
sudo su
./app_config.sh core


root@KB0FX_DRAWS:/home/pi/bin# ./showudrc.sh
==== Sound Card ====
udrc card number line: card 0: udrc [udrc], device 0: Universal Digital Radio Controller tlv320aic32x4-hifi-0 []
udrc is sound card #0
==== ALSA Controls for Radio Tansmit ====
LO Driver Gain  L:[24.00dB] R:[24.00dB]
PCM         L:[0.00dB] R:[0.00dB]
DAC Playback PT L:[PTM_P3] R:[PTM_P3]
LO Playback CM [Full Chip CM]
==== ALSA Controls for Radio Receive ====
ADC Level L:[0.00dB] R:[5.50dB]
IN1 L:[Off] R:[Off]
IN2 L:[10 kOhm] R:[10 kOhm]
==== Pi Ver ====
 Pi 3 Model B+ Mfg by Sony UK
 Has WiFi
==== udrc Ver ====
Found a DRAWS

     HAT ID EEPROM
Name:        hat
Product:     Digital Radio Amateur Work Station
Product ID:  0x0004
Product ver: 0x0204
UUID:        46e7be5d-e71d-4558-a1ca-da83e874200d
Vendor:      NW Digital Radio

==== sys Ver ====
----- image version
2019 01 05 17:06:50 PST: SD image version: beta7
----- /proc/version
Linux version 4.14.79-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1159 SMP Sun Nov 4 17:50:20 GMT 2018

----- /etc/*version: 9.6

----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=raspbian
ID_LIKE=debian

----- lsb_release
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 9.6 (stretch)
Release: 9.6
Codename: stretch

---- systemd
   Static hostname: KB0FX_DRAWS
         Icon name: computer
        Machine ID: 2f51e140e908474eaa86ae805f03a6d8
           Boot ID: 32ff8e594ea8445a97d761b27577faa5
  Operating System: Raspbian GNU/Linux 9 (stretch)
            Kernel: Linux 4.14.79-v7+
      Architecture: arm

---- modules
tlv320aic32x4_i2c      16384  1
tlv320aic32x4          32768  1 tlv320aic32x4_i2c
udrc                   16384  3
snd_soc_core          188416  3 tlv320aic32x4,snd_soc_bcm2835_i2s,udrc
snd_pcm                98304  6 snd_pcm_dmaengine,tlv320aic32x4,snd_soc_bcm2835_i2s,snd_soc_core

-rw-r--r-- 1 root  6388 Dec 14 21:56 /lib/modules/4.14.79-v7+/updates/dkms/tlv320aic32x4-i2c.ko
-rw-r--r-- 1 root 39084 Dec 14 21:56 /lib/modules/4.14.79-v7+/updates/dkms/tlv320aic32x4.ko
-rw-r--r-- 1 root  6408 Dec 14 21:56 /lib/modules/4.14.79-v7+/updates/dkms/tlv320aic32x4-spi.ko
-rw-r--r-- 1 root  8332 Dec 14 21:56 /lib/modules/4.14.79-v7+/updates/dkms/udrc.ko

---- kernel
||/ Name               Version      Architecture Description
+++-==================-============-============-=================================
ii  raspberrypi-kernel 1.20181112-1 armhf        Raspberry Pi bootloader
ii  udrc-dkms          1.0.5        armhf        DKMS source for the UDRC driver

---- compass
Compass preference file not found: /etc/apt/preferences.d/compass
---- compass apt sources list file
deb [arch=armhf,amd64] http://archive.compasslinux.org/ cedar main
---- compass package files
-rw-r--r-- 1 root  2201 Dec 31 12:44 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_InRelease
-rw-r--r-- 1 root 17567 Jul  2  2018 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_main_binary-amd64_Packages
-rw-r--r-- 1 root 43316 Dec 31 12:44 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_main_binary-armhf_Packages

----- Dire Wolf DEVELOPMENT version 1.6 A (Dec  9 2018)

==== boot config ====
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
# dtparam=audio=on

force_turbo=1
dtoverlay=
dtoverlay=draws
# dtparam=audio=on


---- gpsd
● gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-01-17 08:17:04 CST; 22h ago
  Process: 539 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, statu
 Main PID: 542 (gpsd)
   CGroup: /system.slice/gpsd.service
           └─542 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0

Jan 17 08:17:04 KB0FX_DRAWS systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jan 17 08:17:04 KB0FX_DRAWS systemd[1]: Started GPS (Global Positioning System) Daemon.
lines 1-10/10 (END)


On Fri, Jan 18, 2019 at 3:44 AM oe8bck <christof.bodner@...> wrote:
Hi again,

I removed the comment from line #2 from the bottom, see attached showudrc.sh output.

Hat is mounted and I thoink properly, but GPSD is still not working properly:
---
pi@draws:~ $ ps xa|grep gps
  454 ?        S<s    0:00 /usr/local/sbin/gpsd -n /dev/ttyAMA0 /dev/pps0
 1288 pts/0    S+     0:00 grep --color=auto gps
pi@draws:~ $ ls -.l /dev/pps0
ls: invalid option -- '.'
Try 'ls --help' for more information.
ls -al /dev/ttySC* /dev/pps*
ls: cannot access '/dev/ttySC*': No such file or directory
ls: cannot access '/dev/pps*': No such file or directory
---

73 de Ch.

Re: GPS not working #gps #gpsd

oe8bck
 
Edited

BTW:
I found in the kernel log that there are voltage drops in the supply, so I changed the supply of the RasPi to the external +12V with a 10A supply. Now there are no messages in the kernel log files any more about too low voltage. But GPSD is still not working.

73 de Christof

Re: GPS not working #gps #gpsd

oe8bck
 

Well, again, I posted too early...

hciattach is running on AMA0, but now there is a /dev/ttyS0 as mentioned in the link, but where is the GPS acutally connected? It's obviously not ttyS0:
---
pi@draws:~ $ sudo /usr/local/sbin/gpsd  -D 3 -n -N /dev/ttyS0
gpsd:INFO: launching (Version 3.18.1)
gpsd:INFO: listening on port gpsd
gpsd:INFO: stashing device /dev/ttyS0 at slot 0
gpsd:INFO: SER: opening GPS data source type 2 at '/dev/ttyS0'
gpsd:INFO: SER: speed 9600, 8N1
gpsd:INFO: SER: speed 9600, 8O1
gpsd:INFO: SER: speed 9600, 8N1
gpsd:INFO: SER: speed 9600, 8N1
gpsd:INFO: SER: speed 9600, 8N1
gpsd:INFO: gpsd_activate(2): activated GPS (fd 5)
gpsd:INFO: KPPS:/dev/ttyS0 RFC2783 path:/dev/pps0, fd is 6
gpsd:INFO: KPPS:/dev/ttyS0 pps_caps 0x1133
gpsd:INFO: KPPS:/dev/ttyS0 have PPS_CANWAIT
gpsd:INFO: KPPS:/dev/ttyS0 kernel PPS will be used
gpsd:INFO: PPS:/dev/ttyS0 ntpshm_link_activate: 1
gpsd:INFO: device /dev/ttyS0 activated
gpsd:INFO: KPPS:/dev/ttyS0 kernel PPS timeout Interrupted system call
gpsd:INFO: KPPS:/dev/ttyS0 kernel PPS timeout Interrupted system call
gpsd:INFO: KPPS:/dev/ttyS0 kernel PPS timeout Interrupted system call
gpsd:INFO: running with effective group ID 20
gpsd:INFO: running with effective user ID 65534
gpsd:INFO: startup at 2019-01-18T11:07:59.000Z (1547809679)
gpsd:INFO: KPPS:/dev/ttyS0 kernel PPS timeout Connection timed out
gpsd:INFO: KPPS:/dev/ttyS0 kernel PPS timeout Connection timed out
gpsd:INFO: KPPS:/dev/ttyS0 kernel PPS timeout Connection timed out
gpsd:INFO: KPPS:/dev/ttyS0 kernel PPS timeout Connection timed out
gpsd:INFO: KPPS:/dev/ttyS0 kernel PPS timeout Connection timed out
---

Re: GPS not working #gps #gpsd

oe8bck
 

Sorry for this many posts, but currently I am searching for a solution...

I found this explanation of the /dev/ttyAMA0/Bluetooth behaviour of RasPi 3B (which I have running)
https://raspberrypi.stackexchange.com/questions/45570/how-do-i-make-serial-work-on-the-raspberry-pi3-pi3b-pizerow
---
pi@draws:/boot $ grep Revision /proc/cpuinfo
Revision        : a02082
---

But I did not manage to prevent hciattach to be started, so I am still looking for ideas/hints...

73 de Christof

Re: GPS not working #gps #gpsd

oe8bck
 

Hi again,

I was wondering wh gpsd cannot open /dev/ttyAMA0, which process is blocking it.
---
pi@draws:~/n7nix/gps $ sudo lsof  /dev/ttyAMA0
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
      Output information may be incomplete.
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
hciattach 539 root    3u   CHR 204,64      0t0 1733 /dev/ttyAMA0
---

So hciattach is running, which is I think Bluetooth. So I disabled the Bluetooth by adding
dtoverlay=pi3-disable-bt-overlay
to /boot/config.txt and rebooted. But this way, hciattach is still running and blocking ttyAMA0

Do you think I am in thinking in the right direction?

73 de Ch.

Re: GPS not working #gps #gpsd

oe8bck
 

Hi John,

Thanks for the information. I have a 2.5A supply on the USB line and I double-checled the connection of the hat. I am looking forward that Basil can help me to find a hint for where I shall look at more in detail.

73 de Christof

Re: GPS not working #gps #gpsd

oe8bck
 

Hi again,

I removed the comment from line #2 from the bottom, see attached showudrc.sh output.

Hat is mounted and I thoink properly, but GPSD is still not working properly:
---
pi@draws:~ $ ps xa|grep gps
  454 ?        S<s    0:00 /usr/local/sbin/gpsd -n /dev/ttyAMA0 /dev/pps0
 1288 pts/0    S+     0:00 grep --color=auto gps
pi@draws:~ $ ls -.l /dev/pps0
ls: invalid option -- '.'
Try 'ls --help' for more information.
ls -al /dev/ttySC* /dev/pps*
ls: cannot access '/dev/ttySC*': No such file or directory
ls: cannot access '/dev/pps*': No such file or directory
---

73 de Ch.

Re: GPS not working #gps #gpsd

Basil Gunn
 

Jeff,

The results from the showudrc.sh script indicate that it is either not
seated properly on the 40pin RPi header ie. not pushed down far enough
or off by 1 row OR your DRAWS hat has been damaged or is defective.

I made the changes that you made to your /boot/config.txt file by
putting these entries as the last 2 lines & my DRAWS worked as expected:

enable_uart=0
dtparam=audio=on

You could try eliminating these 2 lines which is the default
configuration and rebooting but I don't think that is your problem.

/Basil


Jeff Marden via Groups.Io <jmardensdl=netscape.net@groups.io> writes:

Hello Basil:

Here is what shows on the console upon run of showudrc.sh:

aplay: device_list:270: no soundcards found...
No LSB modules are available.
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

Attached is the output from the showudrc.sh run on my Beta 7 DRAWS setup.

Comments and questions welcome.

Thanks,

Re: GPS not working #gps #gpsd

Jeff Marden
 

Hello Basil:

Here is what shows on the console upon run of showudrc.sh:

aplay: device_list:270: no soundcards found...
No LSB modules are available.
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

Attached is the output from the showudrc.sh run on my Beta 7 DRAWS setup.

Comments and questions welcome.

Thanks,
--
Jeff Marden
N1JCM

Re: DRAWS Shout Out - Great Solution #earlyadopters #beta7

N9UMJ
 

echoing Mike's comments..NWD Keep up the great work

On Thu, Jan 17, 2019 at 8:14 AM Mike - KB0FX <mweilb@...> wrote:
Ladies and Gentlemen of NW Digital Radio,

I just want to the thank you for introducing the DRAWS Pi-Hat! I have greatly enjoyed working with the card and the beta software! Your tireless support is greatly appreciated!

73

Mike - KB0FX

DRAWS Shout Out - Great Solution #earlyadopters #beta7

Mike - KB0FX
 

Ladies and Gentlemen of NW Digital Radio,

I just want to the thank you for introducing the DRAWS Pi-Hat! I have greatly enjoyed working with the card and the beta software! Your tireless support is greatly appreciated!

73

Mike - KB0FX

Re: GPS not working #gps #gpsd

Basil Gunn
 

With the load of Beta7 I appear to have the same problem as described
by Christof. Same messages from Showudrc ( no sound card found, and
errors), and my /boot/config.txt does not have the "dtoverlay="
commented-out. Beta6 works OK without sound card issues.
Send me the output of the showudrc.sh command.
/Basil

Re: GPS not working #gps #gpsd

Jeff Marden
 

Hello Basil:

With the load of Beta7 I appear to have the same problem as described by Christof. Same messages from Showudrc ( no sound card found, and errors), and my /boot/config.txt does not have the "dtoverlay=" commented-out. Beta6 works OK without sound card issues.

Any other thoughts (Perhaps wait for Christof's results)?

Thanks,
--
Jeff Marden
N1JCM

Re: GPS not working #gps #gpsd

Basil Gunn
 

From your showudrc.sh console output you have a comment character in
front of 'dtoverlay=' in the second line from the bottom of
/boot/config.txt.

You need to have 'dtoverlay=' before 'dtoverlay=draws'
Please remove the comment character and reboot the RPi.

/Basil n7nix

oe8bck <christof.bodner@...> writes:

Hi Basil!

Thanks or your quick response!
---
pi@draws:~/bin $ ./showudrc.sh >../showudrc
No LSB modules are available.
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
---
See attachement for the output of showudrc.sh

---
pi@draws:~/bin $ ls -al /dev/ttySC* /dev/pps*
ls: cannot access '/dev/ttySC*': No such file or directory
ls: cannot access '/dev/pps*': No such file or directory
---

Yes, I did the first steps, but not all of them as I do not have a radio attached, yet.

Obvisously, the HAT is not recognized, do I need the 12V supply?

Re: GPS not working #gps #gpsd

 

Hi Christof,

The 12VDC connection is not required, but highly recommended.  What are you using for the 5VDC power supply (it should be at least 2.5 A).

My quick look at your showudrc output didn't see anything that jumped out at me, but I will let Basil respond after he takes a look.   

Of course, do the usual verification that the DRAWS HAT is properly seated.  

On Wed, Jan 16, 2019 at 10:13 AM oe8bck <christof.bodner@...> wrote:
Hi Basil!

Thanks or your quick response!
---
pi@draws:~/bin $ ./showudrc.sh >../showudrc
No LSB modules are available.
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
---
See attachement for the output of showudrc.sh

---
pi@draws:~/bin $ ls -al /dev/ttySC* /dev/pps*
ls: cannot access '/dev/ttySC*': No such file or directory
ls: cannot access '/dev/pps*': No such file or directory
---

Yes, I did the first steps, but not all of them as I do not have a radio attached, yet.

Obvisously, the HAT is not recognized, do I need the 12V supply?

73 de Christof



--


John D. Hays
Edmonds, WA
K7VE

   

Re: GPS not working #gps #gpsd

oe8bck
 

Hi Basil!

Thanks or your quick response!
---
pi@draws:~/bin $ ./showudrc.sh >../showudrc
No LSB modules are available.
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
---
See attachement for the output of showudrc.sh

---
pi@draws:~/bin $ ls -al /dev/ttySC* /dev/pps*
ls: cannot access '/dev/ttySC*': No such file or directory
ls: cannot access '/dev/pps*': No such file or directory
---

Yes, I did the first steps, but not all of them as I do not have a radio attached, yet.

Obvisously, the HAT is not recognized, do I need the 12V supply?

73 de Christof

Re: GPIO Pass through #draws

Ed Bloom, KD9FRQ
 

Thank you.
 
Then I will build an HF set and UHF/VHF set.
 
Ed Bloom
ewbloom@...
Sent from Webmail access
 
 

-----Original Message-----
From: John D Hays - K7VE <john@...>
To: udrc <udrc@nw-digital-radio.groups.io>
Sent: Tue, Jan 15, 2019 1:46 pm
Subject: Re: [udrc] GPIO Pass through #draws

Ed,

There is no current plan for stacked DRAWS boards.

Many of the GPIO pins are dedicated and not available for stacked cards.  However, the DRAWS provides 2 four wire ports (Mini Din-6) and 4 USB ports (plus the 8 pin GPIO brought off the board to the exterior of a case) which allows for a wide variety of configurations. 

Within direwolf, you can configure the 2 radio ports to provide independent 1200 baud and 9600 baud connections.  As we get better support for virtual audio ports, more applications can use these two ports independently as well as running multiple packet modem data rates on a single port.

Because of the Raspberry Pi networking capabilities, building up larger arrays of applications are possible over Ethernet/WiFi/... using multiple Pi + DRAWS.


On Tue, Jan 15, 2019 at 11:25 AM Ed Bloom, KD9FRQ <ewbloom@...> wrote:
Are there plans to have the DRAWS use pass-through GPIO pins so two units can be stacked?  This would allow 1200 & 9600 packet as well as WinMor and ARDOP to all run from one control point.

Just wondering as I am starting work though getting my station active using DRAWS instead of a PC or PI-TNC.
_._,_



--


John D. Hays
Director

  

Re: GPIO Pass through #draws

 

Ed,

There is no current plan for stacked DRAWS boards.

Many of the GPIO pins are dedicated and not available for stacked cards.  However, the DRAWS provides 2 four wire ports (Mini Din-6) and 4 USB ports (plus the 8 pin GPIO brought off the board to the exterior of a case) which allows for a wide variety of configurations. 

Within direwolf, you can configure the 2 radio ports to provide independent 1200 baud and 9600 baud connections.  As we get better support for virtual audio ports, more applications can use these two ports independently as well as running multiple packet modem data rates on a single port.

Because of the Raspberry Pi networking capabilities, building up larger arrays of applications are possible over Ethernet/WiFi/... using multiple Pi + DRAWS.


On Tue, Jan 15, 2019 at 11:25 AM Ed Bloom, KD9FRQ <ewbloom@...> wrote:
Are there plans to have the DRAWS use pass-through GPIO pins so two units can be stacked?  This would allow 1200 & 9600 packet as well as WinMor and ARDOP to all run from one control point.

Just wondering as I am starting work though getting my station active using DRAWS instead of a PC or PI-TNC.
_._,_



--


John D. Hays
Director