Date   
1k2 APRS via Satellite successful

K4KDR
 

Hi everyone.  Just wanted to share that I was able to get digipeated this morning via satellite "AISAT-1" as it passed over the U.S. East Coast.

With an FT-857d connected to the DRAWS & up/down freqs being controlled via CAT from GPredict, Direwolf served as the packet modem.  The "beacon" command that is part of ax25-tools allows you to send payload text of your choice from the Pi.  I just have a number of scripts as clickable icons containing the strings I want as properly formatted APRS "text", "position", & "message" type packets.  

Of course the UISS program on Windows is more capable, but sometimes we have to make compromises or do things differently on the Pi.

Here is a tweet with screen shots:

https://twitter.com/scott23192/status/1167834188822777858

-Scott,  K4KDR

======

Re: no transmit #wsjt-x

Jim Erickson
 

I believe with WSJTX you need to use CAT control to trigger the PTT as WSJTX does not have a GPIO option.  I would test your setup with FLDIGI and see if you can get it to trigger your radio as it has GPIO PTT option.

Jim
------
73,
Jim
VA7SHG - Phone
VE7TGZ - Other

On Aug 30, 2019, at 19:58, Rob Lapham <ke6jus@...> wrote:

well tried it all over with a signal link and the transmitter works then plugged in the hat and not enough audio to drive the radio so it can be the radio
and look like I am dead in the water. I have set the parameters over and over and they say check the same thing. I think this hat is dead and from reading
more problems out there. Shure would be helpful if the instructions were all together for some of us nubs that didn't know what we where getting into.

Rob k6jus

   

Re: no transmit #wsjt-x

Rob Lapham
 

well tried it all over with a signal link and the transmitter works then plugged in the hat and not enough audio to drive the radio so it can be the radio
and look like I am dead in the water. I have set the parameters over and over and they say check the same thing. I think this hat is dead and from reading
more problems out there. Shure would be helpful if the instructions were all together for some of us nubs that didn't know what we where getting into.

Rob k6jus

   

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

Mike Watkins <mike.watkins@...>
 

Hi Frank,


All the people that say you do not need the dtoverlay= line in config.txt probably have new cards with the correct EEPROM.  I have one of the first cards and removing the dtoverlay= line breaks the soundcard.  Putting it back fixes it.  Maybe one of the folks at NW Digital can put in the dtdebug=1 line then boot and see what comes back in sudo vcdbg log msg command.

Is there a version number we should be looking for where the problem exists (or ceases to exist)? Will be very helpful when supporting others. See below, there may be some specific "parameter" conflict, or who knows even a bug in parameter processing, that could have been causing that. All software has bugs.
 
 One other note - the DRAWS lines need to be inserted in the config.txt before the [pi4] and [all] stuff in the config file.

Not quite - as long as the relevant configuration information is after [all] it will be read, regardless of the Pi model number.  But sure, if you included it before the config.txt file format Pi model tag, you can be sure it'll be read. No harm.

Out of curiosity and in an attempt to see what's folklore or not, I've dug into the config.txt documentation out of interest; rather wish I didn't - there's time I won't get back LOL - and discovered a couple things that may not be important but had me curious. Forgive me if I'm covering ground others have already.

Regarding dt_overlay=, from the documentation (https://www.raspberrypi.org/documentation/configuration/device-tree.md) it would appear that dt_overlay= is used to reset "parameters" from conflicting with another overlay that happens to use the same parameter names. 

Since there's only one parameter - alsaname - maybe there's a conflict there but doesn't seem likely... but who knows. Commenting out the on board audio interface removes the other alsa device, and that could be why it's helpful for some cases. I used to think Raspberry Pi's were quite identical until I discovered one of my RPi 3's no longer saw its Wireless adapter despite being configured identically to every other one.

Regarding dt_overlay parameter convention:
Maybe I'm missing something but the line:
dtoverlay=draws,alsaname=urdc

Seems to be mis-formatted, unless commas are happily being interpreted per the documentation (below). A colon between the driver and first parameter appears to be the documented format. Does it matter? Maybe. Not in my case though, both work. Still, it's probably best that the documented approach be used in case that happy accident, if that's what it is, ends one day. 

dtoverlay=draws:alsaname=happytimeurdc

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: happytimeurdc [happytimeurdc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

For the curious, see following.

73
Mike 
VE7WV

If you have an overlay that defines some parameters, they can be specified either on subsequent lines like this:
dtoverlay=lirc-rpi
dtparam=gpio_out_pin=16
dtparam=gpio_in_pin=17
dtparam=gpio_in_pull=down

or appended to the overlay line like this:

dtoverlay=lirc-rpi:gpio_out_pin=16,gpio_in_pin=17,gpio_in_pull=down

Note here the use of a colon (:) to separate the overlay name from its parameters, which is a supported syntax variant.

Overlay parameters are only in scope until the next overlay is loaded. In the event of a parameter with the same name being exported by both the overlay and the base, the parameter in the overlay takes precedence; for clarity, it's recommended that you avoid doing this. To expose the parameter exported by the base DTB instead, end the current overlay scope using:

dtoverlay=

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

Frank Ivan
 

Hi Jonathan,

You are the MAN! You managed to reproduce the problem that NW Digital denies exits and have a work around! 

All the people that say you do not need the dtoverlay= line in config.txt probably have new cards with the correct EEPROM.  I have one of the first cards and removing the dtoverlay= line breaks the soundcard.  Putting it back fixes it.  Maybe one of the folks at NW Digital can put in the dtdebug=1 line then boot and see what comes back in sudo vcdbg log msg command.  Maybe after the Pacific Northwest Summer Gathering there might be either a fix to the driver module or they might send out a way to update the EEPROM on the card.

One other note - the DRAWS lines need to be inserted in the config.txt before the [pi4] and [all] stuff in the config file.

This has been tested on new images for Buster for both Pi3 and Pi4 after doing the sudo apt update and sudo apt upgrade.

I do like the suggestion to comment out the dtparam=audio=on from Mike.

73 and thanks
Frank - K0FEI

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

K4KDR
 

Great write-up, Mike!

Thanks so much for putting that all together in one summary.

FYI, I am still using the "draws_beta13.zip" image from http://nwdig.net/downloads/ on a Pi 3 B+ connected to an FT-857d and everything (audio in/out, CAT rig control, & PTT) works extremely well.  However, your information is great and I will keep it in my notes for whenever I might try the Buster O/S.

-Scott,  K4KDR

=======================


On Fri, Aug 30, 2019 at 12:49 PM Mike Watkins via Groups.Io <mike.watkins=vectorradio.ca@groups.io> wrote:
Hi Jonathan, all. 

I'm puzzled by your "dtoverlay=" observation as that certainly was not required on either my Pi3 or Pi4 running the same Buster image. I wonder if some of the confusion has to do with specifics of the OS you have; what updates it has received. When I first downloaded Buster it was before the DRAWS/udrc device tree files had hit; I had to perform an update before it would work.

As of today (sometime in the last month actually), that's not an issue if one downloads a Buster image from the official source: https://www.raspberrypi.org/downloads/raspbian/

In short, to get DRAWS/udrc recognized, all I did was:

1. Download and burn a new image - I've used both Raspbian Buster "Lite" as well as the full desktop image - same results.
2. While doing the initial setup of the Pi to create an empty ssh file in "boot", I also add to config.txt the famous:
# DRAWS related:
# this adds the udrc driver to the device tree
dtoverlay=draws,alsaname=udrc
# https://www.raspberrypi.org/documentation/configuration/config-txt/overclocking.md
force_turbo=1
 
and, to save having to change ALSA devices when running alsamixer:
# Enable audio (loads snd_bcm2835)
# DRAWS: May as well disable if you don't need this
# dtparam=audio=on

And boot. We're done.
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 []
  Subdevices: 1 / 1
  Subdevice #0: subdevice #0

The "July 10" label on Lite on the download page might not be accurate:
uname -a
Linux raspberrypi 4.19.57-v7l+ #1244 SMP Thu Jul 4 18:48:07 BST 2019 armv7l GNU/Linux

But it indeed is working on a Pi 3 and Pi 4. I'd recommend doing a system update in any case.

sudo apt-get update && sudo apt-get -y dist-upgrade

After reboot, on the Pi 4:
uname -a
Linux raspberrypi 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l GNU/Linux

Move the same SD card to the Pi 3:
pi@raspberrypi:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.19.66+ #1253 Thu Aug 15 11:37:30 BST 2019 armv6l GNU/Linux

This is what we should expect.

For hams new to all this I wrote up a short guide that only goes as far as the above; configuring applications without the support of the myriad of scripts will be daunting for some. I intend to write some follow up guides for the apps I'm using (mostly packet related at this point).


Cheers all
Mike

On Thu, Aug 29, 2019 at 11:58 PM Jonathan Magee <jmagee@...> wrote:
Hi
I just wanted to let the group know that I have made good progress. I started from scratch with a clean buster image and using my Pi3B (to rule out any issues specific to my PI4). With just the out of the box image I added in the lines
dtoverlay=draws,alsaname=udrc
force_turbo=1  
to config.txt and rebooted.

With just those lines the the DRAWS sound card was not detected. I then added in the line dtdebug=1 at the start of config.txt, rebooted and looked at the debug output. I saw that it was trying to load the device tree for HAT but it failed with the error
dterror: can't find symbol 'cprman'
and then it unloaded HAT

I then added in the line 
dtoverlay= 
to the start of my config.txt and rebooted. This time the sound card was detected. I then tried the sd card in my Pi4 and the DRAWS sound card was detected ok.  
I still have to set up the rest of the software but I am now heading in the right direction. 

It looks like the automatic loading of the drive tree based on the data in the DRAWS eeprom was failing and that had a knock on effect that stopped the  line dtovwerlay=draws,alsaname=udrc from working.
I also had a look at the config.txt on the image I am actively using with DRAWS for wsjtx and I notice that it also has the line
dtoverlay= 
in it. 

73 de Jonathan GI7KMC 

On Fri, 30 Aug 2019 at 04:47, John D Hays - K7VE <john@...> wrote:
And make sure the lines are added at the end of /boot/config.txt in that order.


dtoverlay=draws,alsaname=udrc
force_turbo=1


On Thu, Aug 29, 2019 at 7:36 AM Basil Gunn <basil@...> wrote:

Mitch Winkle <ab4mw@...> writes:

> Second that notion. There is a lot of what I consider unwanted fluff
> in this image since I don't care about packet radio. I would really
> like to have a clean image with only the necessary drivers and such and
> then I could install my own programs, and select the HF programs that I
> want to use. So perhaps a "minimal" image that gets the DRAWS
> functioning properly on the RPi??

Use the latest Raspbian image that supports Debian buster and add these
lines in /boot/config.txt

dtoverlay=draws,alsaname=udrc
force_turbo=1

/Basil n7nix





--
John D. Hays
Kingston, WA
K7VE

 


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

Mike Watkins <mike.watkins@...>
 

Hi Jonathan, all. 

I'm puzzled by your "dtoverlay=" observation as that certainly was not required on either my Pi3 or Pi4 running the same Buster image. I wonder if some of the confusion has to do with specifics of the OS you have; what updates it has received. When I first downloaded Buster it was before the DRAWS/udrc device tree files had hit; I had to perform an update before it would work.

As of today (sometime in the last month actually), that's not an issue if one downloads a Buster image from the official source: https://www.raspberrypi.org/downloads/raspbian/

In short, to get DRAWS/udrc recognized, all I did was:

1. Download and burn a new image - I've used both Raspbian Buster "Lite" as well as the full desktop image - same results.
2. While doing the initial setup of the Pi to create an empty ssh file in "boot", I also add to config.txt the famous:
# DRAWS related:
# this adds the udrc driver to the device tree
dtoverlay=draws,alsaname=udrc
# https://www.raspberrypi.org/documentation/configuration/config-txt/overclocking.md
force_turbo=1
 
and, to save having to change ALSA devices when running alsamixer:
# Enable audio (loads snd_bcm2835)
# DRAWS: May as well disable if you don't need this
# dtparam=audio=on

And boot. We're done.
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 []
  Subdevices: 1 / 1
  Subdevice #0: subdevice #0

The "July 10" label on Lite on the download page might not be accurate:
uname -a
Linux raspberrypi 4.19.57-v7l+ #1244 SMP Thu Jul 4 18:48:07 BST 2019 armv7l GNU/Linux

But it indeed is working on a Pi 3 and Pi 4. I'd recommend doing a system update in any case.

sudo apt-get update && sudo apt-get -y dist-upgrade

After reboot, on the Pi 4:
uname -a
Linux raspberrypi 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l GNU/Linux

Move the same SD card to the Pi 3:
pi@raspberrypi:~ $ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.19.66+ #1253 Thu Aug 15 11:37:30 BST 2019 armv6l GNU/Linux

This is what we should expect.

For hams new to all this I wrote up a short guide that only goes as far as the above; configuring applications without the support of the myriad of scripts will be daunting for some. I intend to write some follow up guides for the apps I'm using (mostly packet related at this point).


Cheers all
Mike

On Thu, Aug 29, 2019 at 11:58 PM Jonathan Magee <jmagee@...> wrote:
Hi
I just wanted to let the group know that I have made good progress. I started from scratch with a clean buster image and using my Pi3B (to rule out any issues specific to my PI4). With just the out of the box image I added in the lines
dtoverlay=draws,alsaname=udrc
force_turbo=1  
to config.txt and rebooted.

With just those lines the the DRAWS sound card was not detected. I then added in the line dtdebug=1 at the start of config.txt, rebooted and looked at the debug output. I saw that it was trying to load the device tree for HAT but it failed with the error
dterror: can't find symbol 'cprman'
and then it unloaded HAT

I then added in the line 
dtoverlay= 
to the start of my config.txt and rebooted. This time the sound card was detected. I then tried the sd card in my Pi4 and the DRAWS sound card was detected ok.  
I still have to set up the rest of the software but I am now heading in the right direction. 

It looks like the automatic loading of the drive tree based on the data in the DRAWS eeprom was failing and that had a knock on effect that stopped the  line dtovwerlay=draws,alsaname=udrc from working.
I also had a look at the config.txt on the image I am actively using with DRAWS for wsjtx and I notice that it also has the line
dtoverlay= 
in it. 

73 de Jonathan GI7KMC 

On Fri, 30 Aug 2019 at 04:47, John D Hays - K7VE <john@...> wrote:
And make sure the lines are added at the end of /boot/config.txt in that order.


dtoverlay=draws,alsaname=udrc
force_turbo=1


On Thu, Aug 29, 2019 at 7:36 AM Basil Gunn <basil@...> wrote:

Mitch Winkle <ab4mw@...> writes:

> Second that notion. There is a lot of what I consider unwanted fluff
> in this image since I don't care about packet radio. I would really
> like to have a clean image with only the necessary drivers and such and
> then I could install my own programs, and select the HF programs that I
> want to use. So perhaps a "minimal" image that gets the DRAWS
> functioning properly on the RPi??

Use the latest Raspbian image that supports Debian buster and add these
lines in /boot/config.txt

dtoverlay=draws,alsaname=udrc
force_turbo=1

/Basil n7nix





--
John D. Hays
Kingston, WA
K7VE

 

Re: no transmit #wsjt-x

Fred Meier <fsmeier@...>
 

Rob, you are contributing to the advances of mankind. Think of your purchase as an investment in progress.

I follow this conversation daily. I ordered mine in early Spring- as soon as presales were allowed. I ordered my metal case as soon as that was offered.

The Draws hat arrived in the mail. After postage, duties, taxes and a service fee to the letter carrier this cost nearly $200.00 Canadian at my door.

I have never seen the case.

After following this convoluted thread for months- I think I made the right decision to not open the package. Unfortunately it is much too late to return mine.

You can either be sad about your purchase, or you can go outside and mow the lawn if you have one. Your choice.

Cheers, Fred VE7FMN

 

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of Rob Lapham
Sent: Thursday, August 29, 2019 9:41 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [draws and udrc] no transmit #wsjt-x

 

just did a rest on the radio and still no transmit powers and also don't see how it can be the radio if it works with other soundcards.
just tried the setalsa-ft817.sh command again no joy I have also tried a new memory card and started over I have been at this for
about two months now. I have also tried the draws manager and turned the gain up to max and no transmit.

starting to think I made mistake buying this

rob k6jus



 

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

Jonathan Magee
 

Hi
I just wanted to let the group know that I have made good progress. I started from scratch with a clean buster image and using my Pi3B (to rule out any issues specific to my PI4). With just the out of the box image I added in the lines
dtoverlay=draws,alsaname=udrc
force_turbo=1  
to config.txt and rebooted.

With just those lines the the DRAWS sound card was not detected. I then added in the line dtdebug=1 at the start of config.txt, rebooted and looked at the debug output. I saw that it was trying to load the device tree for HAT but it failed with the error
dterror: can't find symbol 'cprman'
and then it unloaded HAT

I then added in the line 
dtoverlay= 
to the start of my config.txt and rebooted. This time the sound card was detected. I then tried the sd card in my Pi4 and the DRAWS sound card was detected ok.  
I still have to set up the rest of the software but I am now heading in the right direction. 

It looks like the automatic loading of the drive tree based on the data in the DRAWS eeprom was failing and that had a knock on effect that stopped the  line dtovwerlay=draws,alsaname=udrc from working.
I also had a look at the config.txt on the image I am actively using with DRAWS for wsjtx and I notice that it also has the line
dtoverlay= 
in it. 

73 de Jonathan GI7KMC 


On Fri, 30 Aug 2019 at 04:47, John D Hays - K7VE <john@...> wrote:
And make sure the lines are added at the end of /boot/config.txt in that order.


dtoverlay=draws,alsaname=udrc
force_turbo=1


On Thu, Aug 29, 2019 at 7:36 AM Basil Gunn <basil@...> wrote:

Mitch Winkle <ab4mw@...> writes:

> Second that notion. There is a lot of what I consider unwanted fluff
> in this image since I don't care about packet radio. I would really
> like to have a clean image with only the necessary drivers and such and
> then I could install my own programs, and select the HF programs that I
> want to use. So perhaps a "minimal" image that gets the DRAWS
> functioning properly on the RPi??

Use the latest Raspbian image that supports Debian buster and add these
lines in /boot/config.txt

dtoverlay=draws,alsaname=udrc
force_turbo=1

/Basil n7nix





--
John D. Hays
Kingston, WA
K7VE

 

Re: no transmit #wsjt-x

Rob Lapham
 

just did a rest on the radio and still no transmit powers and also don't see how it can be the radio if it works with other soundcards.
just tried the setalsa-ft817.sh command again no joy I have also tried a new memory card and started over I have been at this for
about two months now. I have also tried the draws manager and turned the gain up to max and no transmit.

starting to think I made mistake buying this

rob k6jus



 

Re: no transmit #wsjt-x

 

The FT-817 is probably the most tested for the DRAWS™ HAT.

Are you using the left DIN-6 port and selecting the same in your program?

There is a possibility that one of the flags in the CODEC was set incorrectly, at some point.  Try using n7nix/bin/setalsa-ft817.sh  

Occasionally, we have seen the FT-817 where a parameter is changed from default, sometimes doing a full reset on the radio gets it to a working mode.



On Thu, Aug 29, 2019 at 9:14 AM Rob Lapham <ke6jus@...> wrote:
It’s a ft-817nd



--
John D. Hays
Kingston, WA
K7VE

 

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

 

And make sure the lines are added at the end of /boot/config.txt in that order.


dtoverlay=draws,alsaname=udrc
force_turbo=1


On Thu, Aug 29, 2019 at 7:36 AM Basil Gunn <basil@...> wrote:

Mitch Winkle <ab4mw@...> writes:

> Second that notion. There is a lot of what I consider unwanted fluff
> in this image since I don't care about packet radio. I would really
> like to have a clean image with only the necessary drivers and such and
> then I could install my own programs, and select the HF programs that I
> want to use. So perhaps a "minimal" image that gets the DRAWS
> functioning properly on the RPi??

Use the latest Raspbian image that supports Debian buster and add these
lines in /boot/config.txt

dtoverlay=draws,alsaname=udrc
force_turbo=1

/Basil n7nix





--
John D. Hays
Kingston, WA
K7VE

 

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

Frank Ivan
 

Hi Basil,

Sorry to have wasted your time.

73 - Frank - K0FEI

Re: no transmit #wsjt-x

Rob Lapham
 

yes over and over went home to day and rechecked the radio settings. I would think if the radio work in receive and with a signal link the radio
settings should be right. last night had the drive turned all the way up and would not drive the radio just keys and no power. keep going over the 
settings and instruction's. 
Rob k6jus

Re: Eureka!!!! She works perfectly!!

Michael Narges
 

Thanks for the documentation of the DRAWS Hat! Several questions are answered here.  

Thanks, 

Mike WF8O 

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

Basil Gunn
 

Just adding the lines to /boot/config.txt didn't get the tlv modules
to load and I could not see the sound card. If I put those lines
before the drtparam=audio=-on then aplay -l said there is no sound
card found.
Provide the output of showudrc.sh describing what you did doesn't work
for me.

lsmod | grep -i tlv320*

snd_soc_tlv320aic32x4_i2c 16384 27
snd_soc_tlv320aic32x4 40960 1 snd_soc_tlv320aic32x4_i2c
snd_soc_core 192512 5 vc4,snd_soc_simple_card_utils,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_soc_simple_card
snd_pcm 102400 8 vc4,snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_bcm2835,snd_soc_core
snd 73728 14 snd_compress,snd_timer,snd_soc_tlv320aic32x4,snd_bcm2835,snd_soc_core,snd_pcm

This works with the latest version of Raspbian which uses this Linux
kernel

uname -r
4.19.57-v7l+

If you do not see the udrc driver enumerated:

aplay -l | grep udrc

card 1: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi
tlv320aic32x4-hifi-0 []

then you are not using the latest Raspbian image it's that simple.

Also Beta image 13 works as long as you do NOT do an upgrade.

It would not be to blow it off until after some hamfest more than a
month down the way.
It's 2 weeks a way, thanks for your concern.

/Basil

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

Frank Ivan
 

I'm sorry Jonathan,

You did show the showudrc and it shows some of the modules, and the /boot/config.txt.

If could show all the modules the sudo lsmod and the /etc/modules file that would be interesting.

Thanks - Frank - K0FEI

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

Frank Ivan
 

Hi Basil,

Just adding the lines to /boot/config.txt didn't get the tlv modules to load and I could not see the sound card. If I put those lines before the drtparam=audio=-on then aplay -l said there is no sound card found.

In the Stretch version there is a module udrc loaded.  What does that do and do we still need it?

I am presenting my 3d printed case for the draws hat on a Pi4 at the Tech Connect 285 club the first Saturday in September and would like to tell everyone how great the product is.  We have a lot of SOTA folks (Colorado is SOTA heaven) and the draws hat is one of the smallest interfaces available.  The following Saturday we will be having our annual picnic on a SOTA peak and showing off equipment.

The long and short of it is you have a show stopping problem and it would appear you can not duplicate it.  I am not the only one who is having the problem.  I know what I would do if it were my product.  It would not be to blow it off until after some hamfest more than a month down the way.

Frank - K0FEI
 

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

Frank Ivan
 

Hi Jonathan,

Could you look at a couple of things and tell me what you are seeing.

1. Could you enter sudo lsmod.  That should display a list of kernel modules loaded.
2. Could you cat /boot/config.txt to type out the config.txt file.
3. Could you enter the nx7nix/bin/showudrc.sh.  Its a lot of stuff but it tells pretty much the story.
4. Finally could you cat /etc/modules and get a list of kernel modules that are being loaded.

Thanks
Frank - K0FEI

Re: no transmit #wsjt-x

Basil Gunn
 

Have you read this to set up a "USER" defined digital mode on your
radio?

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

/Basil n7nix