Basil, again thanks for the help. I didn't bother to download the last image. I found the problem is fixed by simply using alsamixer and the settings you mention. The ./btest.sh script runs OK

Just downloaded this myself and it took a while so cloned it here: https://tor1.radiowaves.ca/nwdr14.zip This is a Digital Ocean virtual in Toronto, set the limit at 900GB so go nuts. It gave me

Basil, I have a Raspbian Buster RPi 4 running the desired kernel. I want to install whatever is included in the standard DRAWS image over this. I suspect there is no file

Dave, The "DRAWS specific software" are two codec drivers that are in the Linux kernel and an overlay that loads at boot time. The drivers are: snd_soc_tlv320aic32x4_i2c snd_soc_tlv320aic32x4 The

Basil, Please add how to install this on one's own RPi 4 Raspbian image (with proper kernel). Your instructions at "Make your own Raspberry Pi image" seem to end before adding the DRAWS-specific

Before you update your image, please capture any configuration changes you might have made like current alsamixer settings. Run alsa-show.sh & make a copy of result. Note a minimum microSD card size

John, I verified that the following method also works. Copy the following alsa control values from your working image, you can read them by running alsa-show.sh. LO Driver Gain PCM ADC Level Boot

First, beacmin.sh was meant to be a minimum beacon command and doesn't have any arguments. That means it only outputs to the first port (udr0) which will not work on the UDRC II unless you edit the

Thanks. I will give this a try. On a somewhat different topic...I notice in beacmin.sh that in the comments aprs symbols are listed. I do not see sending a symbol implemented in this script. Is this

I used a new image (nwdr14) with a UDRC II and it worked fine. I will release that image today. The only thing I changed from the scripts was to select discriminator out using the alsa commands. You

Basil, responses below. 73, John This is not clear to me. I have tested the RPI3/UDRC-II controller to 2 different Yaesu radios both of which work fine with the beta 10 version. aplay -l **** List

I think that your ALSA audio routing is incorrect. If you route through ALSA IN1 then you are using DISCOUT or discriminator audio. If you route through ALSA IN2 then you are using AFOUT

Hello Everyone, I have updated my case and it is Thing 3897403 https://www.thingiverse.com/thing:3897403. It uses a Raspberry Pi Poe Hat between the Raspberry Pi and the Draws Hat. This brings a

Hi Basil, thanks for the information. I have some additional responses below. 73, NX2I John I am not sure what "released " means; nwdr14.imgf is what I get when I click on "current image" on the NWD

New image is not released yet, so not supported yet. Sounds cool. I can't comment on that unless I see the actual showudrc.sh console output. But please wait until I announce the release. Should be

I am attempting to update my aprs system to the current buster-based image nwdr14.img. the old image was beta 10 I believe. The system uses a UDRC-II HAT. I am looking for a very plain end point; an

I removed pin 6 from both ends of the cable and it didn't seem to help in my case in my ft-891. In fact it was rather a step backwards as I no longer was receiving signals.

I have the same trouble, I have the same radio. I have not tried for several months now. It did work on vhf and aprs with the supplied cables. I live in a trailer and just dont want to take a chance

I have been hunting audio out here with a FT-847. The receive works fine. Should I remove pin 6? Can someone explain why. I am using cables that were supplied with the Draws.

I concur with Mitch. I just downloaded the zipped image and it took 10min 18s at 4.73MB/s I used my Linux workstation. It does depend on how many other connections are in progress. time wget