I tried to verify your problem on an RPi 3B+ and a DRAWS 0x0204 and could not. Removed both the dtparam=i2c* statements from /boot/config.txt file and didn't find a problem on either RPi 4B or RPi 3B+

#draws

Brian, Thanks! Nice work! I have a hunch it's because the /boot/config.txt file is biased towards an RPi 4. /Basil Brian Badger <brian@...> writes:

#draws

I fixed the problem by deleting everything from /boot/config.txt except this: dtoverlay= # enable udrc/draws if no eeprom dtoverlay=draws,alsaname=udrc force_turbo=1 # Enable audio (loads snd_bcm2835)

#draws

OK. I will try to replicate your problem with a Pi 3 Model B+ and a 0x0204 DRAWS hat later today. You've posted 3 outputs of aplay -l and 2 had udrc enumerated. It wasn't clear to me which image versi

#draws

This is what my old install says in kern.log during boot up: Oct 11 19:17:32 compass kernel: [ 31.723832] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warne

#draws

I did not "recover" from any script. I flashed the image again, so that you would be satisfied that I am not running the wrong script. The only thing I ran on the fresh image was aplay -l I posted the

#draws

Ok. Thanks. Will Update documentation and remove chk_conflict.sh from image. I am confused as you are seeing udrc enumerated when you run 'aplay -l' Also could you please tell me if my previous instru

#draws

But, to return to the topic at hand, I followed the instructions on your wiki exactly: Start Initial Configuration Boot the newly provisioned microSD card login: pi passwd: digiberry Immediately verif

#draws

Here is the procedure I followed to open a problem report according to your documentation: cat ~/n7nix/PROBLEM_REPORT.md ## Steps to take if you have problems #### Before you run any scripts from a fr

#draws

Right. That's what I did. When the first step "aplay -l" showed no audio devices at all, I started to debug using the documentation on host, which says to use those two scripts. If you are going to re

#draws

CORRECTION: https://nw-digital-radio.groups.io/g/udrc/wiki/8921 Summary of initial config on first boot of a new image: # run aplay -l to make sure the DRAWS codec is enumerated. aplay -l # run the in

#draws

Please provide console output to support this statement. from the showudrc.sh script nwdr20 is what is running: ** The chk_conflict.sh script should NOT be run with the NWDR20 image** This script was

#draws

Fresh DRAWS install from nwdr20.img is not bringing up the audio device, gps or sensors. I reviewed the docs and followed them exactly. DRAWS still comes up with early nwdr release. pi@raspberrypi:~ $

#draws

There seems to be conflicting information on the use of pin 6 for some Yaesu radios. https://nw-digital-radio.groups.io/g/udrc/message/3809 My personal experience trying to get a Yaesu FT-817 radio to

#fldigi #ft857 #wsjtx #draws

Okay, I have been lurking for awhile. I am curious why folks are disabling pin #6 on this yaesu series. ( FT-8XX) I have an 897D. And will be attempting to get my DRAWS going soon. Or as soon as I get

#fldigi #ft857 #wsjtx #draws

Adam, Thanks for the console output. Just a couple of things. Running the initcfg.sh script twice configures your system for packet. Packet uses direwolf which "owns" the codec device. To get HF progr

#fldigi #ft857 #wsjtx #draws

Getting a draws running again with an FT-857D on a 3b+. I used the nwdr19. I have run the init config a couple times, ran the alsa-setft817.sh, broke pin #6. My main problem is no receive audio coming

#fldigi #ft857 #wsjtx #draws

Erwin, in addition to what Basil has said, looking at your config.json file, I see some inconsistencies. I am not sure if they are causing the problems or not, but it is possible. The first is that mo

#upgrade #draws #configuration

Hello Basil, thanks, concerning the rig this was a misunderstanding from my side. So I checked it with your proposal - see below. Thought I found missing arguments - compared to another setting on ano

#upgrade #draws #configuration

Erwin, You only need to setup the ardop systemd service files ONCE and once only. After that the correct systemd files will run from boot and not need touching unless you change radios. First you need

#upgrade #draws #configuration