Date   

Re: Not booting

 

I don't have any specific information on RaspAp.  However, people have been advised not to do a general update on Beta-11 with the DRAWS™, though I doubt it would prevent booting.  Will the Pi boot on the image without the DRAWS™ attached?  If not, then it is likely not a DRAWS™ problem.

People have been successful using DRAWS™ with the new Buster Raspbian (see thread on here).  If you make a new image, be sure to backup your current image so you can roll back.


On Sun, Jul 14, 2019 at 3:39 PM Douglas KI7LIK <KI7LIK.AZ@...> wrote:
It seems as if the problem is when i try to update the distribution.   After i do such and do a sudo reboot, it only shuts down and not boot up.

On Sun, Jul 14, 2019, 14:12 Douglas KI7LIK via Groups.Io <KI7LIK.AZ=GMAIL.COM@groups.io> wrote:
I write a new card with draws 11 that i had on my computer.   It booted up normally and went through and checked out with the normal set up in getting started.

I tried to install rasp ap before updating via update and dist-uprade.

I then did the update after not being able to install raspap.  I then did it in proper order and rebooted before setting raspap.  It shut down, but not restart.   I then booted up the pi with a different card and its fine.

What mistakes could i have made and is there a way to correct them?

Thanks for your help,

Douglas
KI7LIK
Granada Estates Neighborhood Watch



--
John D. Hays
Kingston, WA
K7VE

 


Re: Not booting

Douglas
 

It seems as if the problem is when i try to update the distribution.   After i do such and do a sudo reboot, it only shuts down and not boot up.


On Sun, Jul 14, 2019, 14:12 Douglas KI7LIK via Groups.Io <KI7LIK.AZ=GMAIL.COM@groups.io> wrote:
I write a new card with draws 11 that i had on my computer.   It booted up normally and went through and checked out with the normal set up in getting started.

I tried to install rasp ap before updating via update and dist-uprade.

I then did the update after not being able to install raspap.  I then did it in proper order and rebooted before setting raspap.  It shut down, but not restart.   I then booted up the pi with a different card and its fine.

What mistakes could i have made and is there a way to correct them?

Thanks for your help,

Douglas
KI7LIK
Granada Estates Neighborhood Watch


Not booting

Douglas
 

I write a new card with draws 11 that i had on my computer.   It booted up normally and went through and checked out with the normal set up in getting started.

I tried to install rasp ap before updating via update and dist-uprade.

I then did the update after not being able to install raspap.  I then did it in proper order and rebooted before setting raspap.  It shut down, but not restart.   I then booted up the pi with a different card and its fine.

What mistakes could i have made and is there a way to correct them?

Thanks for your help,

Douglas
KI7LIK
Granada Estates Neighborhood Watch


Re: DRAWS to Elecraft KX3

David Wagner 1
 


Initial pi4 Benchmarks

JT Croteau <jt.tobit@...>
 

The boys of Phoronix have been busy testing the new pi 4.

https://www.phoronix.com/vr.php?view=28057


Re: DRAWS on Pi 3b+ with Raspbian Buster #draws

Jon Gross
 

For anyone following along at home, I did get all the hardware working, ax25 configured and dire wolf configured.

I installed pat, and am able to get the LED on the draws to light up when pat is trying to connect over ax25, so as soon as I can build my 6pin din -> wouxun HT cable I can start seeing how it works.

Thanks to everyone for all the assistance.

Goodbye signalink, and hello pi+draws.

-jon, KJ7GDX


Re: DRAWS on Pi 3b+ with Raspbian Buster #draws

Jon Gross
 


Thanks!

What I ended up doing was basically this:

1. vanilla buster install
2. update all the things (apt update ; apt upgrade)
3. add snd-soc-tlv320aic32x4-i2c and ax25 to /etc/modules
4. add dtoverlay=draws,alsaname=udrc and dtparam=audio=on to /boot/config.txt
5. install ax25, gpsd, hamlib, and related dev packages with apt
6. compile/install dire wolf from source

The hardware is working (gps confirmed, radio interface not yet confirmed), and I'm still working on getting the ax25 stuff configured and direwolf wired up correctly, but I think the hardware is functional now, as I'm seeing the sound card and the gps is working great.

Thanks again for your help!

-jon


Re: DRAWS on Pi 3b+ with Raspbian Buster #draws

Jon Gross
 

Aha!  Thank you both.

Instead of running the n7nix code, I've been using it as inspiration, and gotten things to recognize the sound card, thanks to n7nix, Lars and Karl and all the docs that exist in the wiki.

I ended up doing a(nother!) stock buster install, adding the tlv* modules to my /etc/modules, modifying my boot/config.txt, and now it looks like it's on it's way to functionality.

I may add a page to the wiki with my approach in case someone else wants to do it by hand as well.

Thanks all!

-jon KJ7GDX


Re: DRAWS on Pi 3b+ with Raspbian Buster #draws

LA9KOA - Karl
 

Lars is faster than me :)

If someone get a similar problem with RPi4, you should note that there are two variants of the kernel involved.

RPi3 by default boot the -v7+ variant that Lars refers above.
RPi4 use the -v7l+ variant (the difference is the lowercase LIMA)

The name of the modules are the same, but the path to the modules is different. 
When I moved mye SD card with Buster from a RPi3 to a RPi4 it automagically chose the right kernel.

Jon, I hope you get some help from all this. You could run `lsmod` and see if the two modules are loaded:
snd-soc-tlv320aic32x4
snd-soc-tlv320aic32x4-i2c
If the modules show up, you could see if there is any relevant info in `dmesg` that can give a clue why sound (and probably GPS) is still not working.

Good luck!

Karl


Re: DRAWS on Pi 3b+ with Raspbian Buster #draws

la4rha@...
 

Hi Jon,

Your /boot/config.txt seems to be the same as the one on my RPi4, so that looks correct. 

The 2 files Karl refers to that might have been moved to /home/pi/tmp, are 

   /lib/modules/4.19.57-v7+/kernel/sound/soc/codecs/snd-soc-tlv320aic32x4-i2c.ko

   /lib/modules/4.19.57-v7+/kernel/sound/soc/codecs/snd-soc-tlv320aic32x4.ko

Brgds,
LA4RHA, Lars


Re: DRAWS on Pi 3b+ with Raspbian Buster #draws

LA9KOA - Karl
 

Hi, Jon

I actually did a fresh install of Buster on a RPi3b+ while I was waiting for my RPi4 to arrive. So it is possible to run Buster on RPi3.
(RPi4 require Buster to boot, but the setup of Buster should be the same regardless of running on RPi3 or 4. I was able to just move the SD card over to my the RPi4 when it arrived)

The boot config can be a bit tricky. The lines need to be in the right order.
The drivers in Buster are already patched to work with DRAWS. However some of the scripts under n7nix/ are not updated for this, so if run they will move the in-kernel drivers out but not be able to build new drivers.
If this happened to you, you should see two driver files under /home/pi/tmp/ 

All this from memory. I will update with a copy of my boot config and exact name of the drivers when I get home. If noone else beat me to it :)

Best,
Karl LA9KOA


DRAWS on Pi 3b+ with Raspbian Buster #draws

Jon Gross
 

I have followed the notes here (https://docs.google.com/document/d/1Wq-jNLXYuREIOcr0OVu1FxPNhDFGuCOu6dX5OQ2BVxA/edit#).  I'm on my second go-round with a fresh image.

I can't seem to get the drivers to load properly.

Curious if anyone out there running buster on a 3b+ gotten the sound card to work?

Output of "showudrc.sh":

pi@raspberrypi:~ $ sudo n7nix/bin/showudrc.sh
==== Sound Card ====
No udrc sound card found.
==== 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: 0x0106
UUID:        999d4843-b4d4-44cf-b488-3015da0573cf
Vendor:      NW Digital Radio
 
==== sys Ver ====
----- image version
2019 07 11 20:42:56 PDT: image_install.sh: image install script START
----- /proc/version
Linux version 4.19.57-v7+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1244 SMP Thu Jul 4 18:45:25 BST 2019
 
----- /etc/*version: 10.0
 
----- /etc/*release
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: raspberrypi
         Icon name: computer
        Machine ID: b487ea14459143c1b7d198356e08876f
           Boot ID: e3682e09b4284de3a39f151c0a37ae38
  Operating System: Raspbian GNU/Linux 10 (buster)
            Kernel: Linux 4.19.57-v7+
      Architecture: arm
 
---- modules
 
Command 'apt-get install udrc-dkms' failed or was not run.
 
---- kernel
dpkg-query: no packages found matching udrc-dkms
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name               Version      Architecture Description
+++-==================-============-============-=================================
ii  raspberrypi-kernel 1.20190709-1 armhf        Raspberry Pi bootloader
 
Directory: /proc/device-tree/soc/i2c@7e804000/tlv320aic32x4@18 exists and status is okay
 
---- syslog
 
---- dmesg
 
---- compass
Compass preference file not found: /etc/apt/preferences.d/compass
Compass apt sources list file not found: /etc/apt/sources.list.d/compass.list
---- compass package files
ls: cannot access '/var/lib/apt/lists/archive.compasslinux.org_*': No such file or directory
 
----- Dire Wolf version 1.5
 
==== Filesystem ====
/dev/root        59G  2.2G   54G   4% /
 
==== boot config ====
 
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
 
[all]
#dtoverlay=vc4-fkms-v3d
 
# enable udrc/draws if no eeprom
dtoverlay=draws,alsaname=udrc
force_turbo=1
 
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
 
---- gpsd
/usr/local/sbin/gpsd
gpsd: 3.19 (revision 3.19)
● gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-07-11 21:57:38 PDT; 4min 26s ago
  Process: 523 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
 Main PID: 524 (gpsd)
    Tasks: 1 (limit: 2200)
   Memory: 1.0M
   CGroup: /system.slice/gpsd.service
           └─524 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
 
Jul 11 21:57:38 raspberrypi systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jul 11 21:57:38 raspberrypi systemd[1]: Started GPS (Global Positioning System) Daemon.
 
---- chrony
crw------- 1 root root    241, 0 Jul 11 21:57 /dev/pps0
crw-rw---- 1 root dialout 239, 0 Jul 11 21:57 /dev/ttySC0
crw-rw---- 1 root dialout 239, 1 Jul 11 21:57 /dev/ttySC1
-- chrony sources
210 Number of sources = 6
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
#? GPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
#? PPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
^+ triangle.kansas.net           3   6   177    57    -66us[ +664us] +/-   83ms
^- you.dontlike.us               3   6   177    57  -4799us[-4069us] +/-  110ms
^- 0.time.dbsinet.com            2   6   177   117   -620us[ +111us] +/-   84ms
^* tesla.selinc.com              2   6   177    56  +2716ns[ +733us] +/-   38ms
-- chrony tracking
Reference ID    : 4A75D602 (tesla.selinc.com)
Stratum         : 3
Ref time (UTC)  : Fri Jul 12 05:01:07 2019
System time     : 0.000000026 seconds slow of NTP time
Last offset     : +0.000730021 seconds
RMS offset      : 0.002060165 seconds
Frequency       : 2.778 ppm fast
Residual freq   : -0.583 ppm
Skew            : 0.666 ppm
Root delay      : 0.013313225 seconds
Root dispersion : 0.029869111 seconds
Update interval : 64.1 seconds
Leap status     : Normal
-- chrony sourcestats
210 Number of sources = 6
Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
==============================================================================
GPS                         0   0     0     +0.000   2000.000     +0ns  4000ms
PPS                         0   0     0     +0.000   2000.000     +0ns  4000ms
triangle.kansas.net         7   3   200     -0.583      5.207    -90us   156us
you.dontlike.us             7   3   201     +0.986     10.467  -4630us   323us
0.time.dbsinet.com          6   4   136     -0.902      2.373   -726us    34us
tesla.selinc.com            7   7   201     -0.583      8.417  -7639ns   265us
 
---- sensors
-rw-r--r-- 1 root root 171 Jul 11 21:58 /etc/sensors.d/draws
rpi_volt-isa-0000
Adapter: ISA adapter
in0:              N/A
 
ads1015-i2c-1-48
Adapter: bcm2835 I2C adapter
+12V:         +0.00 V
in5:          +2.50 V
User ADC 1:   +0.00 V
User ADC 2:   +0.00 V
 


btest.sh version (circa 14apr2019) hard coded lat and lon directions #beta

vk2psf@...
 

file n7nix/debug/btest.sh

hardcoded N and W
current 
beacon_msg="!${lat}N/${lon}W-$timestamp, from $(hostname) on port $AX25PORT Seq: $seqnum"

recommended 
beacon_msg="!${lat}${latdir}/${lon}${londir}-$timestamp, from $(hostname) on port $AX25PORT Seq: $seqnum"

the heavy lifting for this has already been performed in the function     get_lat_lon_nmeasentence

.../alex VK2PSF


[New post] DRAWS™ Update! What about the Pi 4?

 



k7udr posted: "The DRAWS HATs are in stock but the announcement of the Pi 4 has changed the landscape. We have Pi 4s on order, and a few of our customers have DRAWS working on the Pi 4 now (see our support group for details). This proves out the conne"

New post on NW Digital Radio

DRAWS Update! What about the Pi 4?

by k7udr

The DRAWS HATs are in stock but the announcement of the Pi 4 has changed the landscape.

We have Pi 4s on order, and a few of our customers have DRAWS working on the Pi 4 now (see our support group for details). This proves out the connectivity, but 3 issues remain; power consumption, thermal requirements and mechanical design of the case.

Once we have Pi 4s on the bench, we will analyze these issues and make adjustments accordingly. The goal is to modify the case so it will work with either the Pi 3 or 4.

In the meantime we have suspended ordering of turn-key units. Kits will ship with the case backordered.

k7udr | July 8, 2019 at 6:00 pm | Categories: DRAWS | URL: https://wp.me/p2mAAP-1JP

--
John D. Hays
Kingston, WA
K7VE

 


Re: No WSJT-X transmission with FT-891 #ft-891 #draws #ft-8 #wsjtx

Tim Sperry
 

Matt,
You may want to reset the radio.
I have done that in the past when problems arise.
I use the included menu settings after I reset the radio.
I am using the left audio channel.
Have you checked the draws manager and make sure AF (pin5) for your channel.
Also make sure Direwolf is not running 
cd
cd bin
sudo su
./ax25-stop

Tim / AG6RS


Re: Failure activating AX25, need help to fix #draws #direwolf #a25

David Nussdorfer <davesworld06@...>
 

I had a PIJuice hat between the Draws Hat and the rPi 3b.  showudrc.sh text showed that I was missing the UDRC radio.  I placed the Draws Hat onto another rPi without the PIJuice hat, and the UDRC radio showed by rerunning the script.

I can confirm that using a PIJuice hat between the rPi and the Draws hat does not work.  Something on the I2C bus must be interfering with the UDRC?

Next step: redo the SD card to a fresh rebuild and try loading the software again.  Why? There are errors that must have occured during the initial setup on the missing UDRC were not captured.

David Nussdorfer


Re: No WSJT-X transmission with FT-891 #ft-891 #draws #ft-8 #wsjtx

Matt N7ROO
 

Thanks all for your suggestions.

I've made sure that my "DATA IN SELECT" (setting 08-09) is set to "REAR" rather than "MIC", and confirmed this by whistling into my mic while transmitting. No transmission / power output was observed with on my radio meter or PSKreporter. I've confirmed that my settings were accurate as far as I can tell, and have mimicked other FT-891 users. I've included some screenshots of this below. I've also adjusted the power output on the side of the WSJT-X screen with no observable difference in outcome.

image.png

image.png


image.png

Cheers,
Matt  - N7ROO


On Sun, Jul 7, 2019 at 5:52 AM Richard Waller via Groups.Io <rewaller=verizon.net@groups.io> wrote:
Have you looked at the output settings in draws manager and tried to adjust those? Have you confirmed that the audio settings are correct for transmit in the wsjt-x program? Lastly, have you adjusted the power output slider on the right side of the wsjt-x screen? Rick Ka4ohm.


On Jul 6, 2019, at 10:05 PM, Matt N7ROO <n7roo@...> wrote:

Hello,

I've been trying to set up my DRAWS and FT-891 to use FT8 via WSJT-X. I've been following the videos and settings from Julian and Steve, and can receive messages ok, however whenever I transmit the radio lights up but the power output meter never changes. Almost as if there is no data aside from the PTT notification being send from the DRAWS unit. 

If anyone has some insight on what may be causing this please let me know. Happy to run any commands / dump console outputs if it will help.

73
Matt N7ROO


Re: Using the DRAWS hat with a Raspberry Pi 4 #yaac #replacecompass #draws #install #js8call

 

You never know until it is tested, but with Anna's driver for sound and serial in the kernel it should just move forward.

On Mon, Jul 8, 2019 at 7:50 AM LA9KOA - Karl <oyoygard@...> wrote:


In other news Debian Buster was released this weekend. This is now the new "stable" release. 
How will this affect the DRAWS ecosystem? 

Best,
Karl


--
John D. Hays
Kingston, WA
K7VE

 


Re: Using the DRAWS hat with a Raspberry Pi 4 #yaac #replacecompass #draws #install #js8call

LA9KOA - Karl
 

FYI: While you are waiting for your RPi4 to arrive, you still prepare a SDcard with Raspbian Buster (the new version needed for RPi4) on an older RPi.
I followed LA4RHA, Lars' guide (and hopefully helped a tiny bit) on a RPi3b+
Today my shiny new RPi4 arrived. I moved the DRAWS hat and SDcard over to the new RPi4 and was up and running before I could even find the right input on my TV to watch the first boot !

- I got an new IP by DHCP since the hardware MAC address change on the new unit. Other than that, everything seem to be working. Now I have to do some testing on the air. Think I'll start with my FT-817 and JS8call on 40m. :)

In other news Debian Buster was released this weekend. This is now the new "stable" release. 
How will this affect the DRAWS ecosystem? 

Best,
Karl


Re: Failure activating AX25, need help to fix #draws #direwolf #a25

Basil Gunn
 

David Nussdorfer <davesworld06@...> writes:

The instructions do not call for a play -l until configuring the sound
card. The instructions link you posted is the one I used twice to
configure the Draws Hat on a rPi 3b.

I ran the ax25-start, then ax25-status and ax25-status -d per the
instructions on a fresh install and got the errors in my first
post. Both attempts were connected to a FT-857d, using my wireless
connection found by the ifconfig command.

I used the image labeled draws-beta13.img, and received my Draws Hat
on July 6th. On another rPi with a Signalink USB (without the Hat), I
had no problems setting up Direwolf.
No new information from you to comment on.
I'm guessing the tlv320aic driver is not loading for some reason.
The output of showudrc.sh would confirm that.

Unfortunately this is my last post for a week or so.
/Basil