Date   

UDRC/DRAWS audio driver? #audio #draws #udrc-ii #documentation

Art - KC7SDA
 

I've been looking around the site and I see mention of a udrc-dkms (I'm assuming thats the audio driver file for the udrc)

my question is there a repository somewhere that I could add to, say, raspbian and install the udrc driver with apt-get and run the scripts to install the board?

I've looked through the scripts and I thought there was a fix for when a distro-update broke the driver but I can't find it.

73
Art


Re: no transmit #wsjt-x

Rob Lapham
 

I was not upset about your responses I did every thing you said it was the lack of response from the office, and I think maybe
they should offer to test some of the unit people cant get the unit to work, but that is up to them. I am sending it back
maybe they will test it not that they will ever let me know.  on to other projects

73 k6jus 
 


Re: no transmit #wsjt-x

Ed Bloom, KD9FRQ
 

Please send the DRAWS to me, if you don't want to send it back to NWDR.

I'll give it a go since they did issue you the refund.

Ed, KD9FRQ

On 9/5/2019 7:56 PM, Rob Lapham wrote:
still no return contact from them. Its like when you have a problem with there card they forget you.
ill take it to pay pal Monday before its to late
Rob k6jus


Re: no transmit #wsjt-x

 

I think, if you go back and review, you will see that you have had quite a few responses over the last several days, trying to help you diagnose the problem.  Bryan processed the promised refund today. 

73

On Thu, Sep 5, 2019 at 5:56 PM Rob Lapham <ke6jus@...> wrote:
still no return contact from them. Its like when you have a problem with there card they forget you.
ill take it to pay pal Monday before its to late
Rob k6jus
_.
--
John D. Hays
Kingston, WA
K7VE

 


Re: no transmit #wsjt-x

 

Refund Issued

Thanks,
Bryan K7UDR


Re: Buster Image with DRAWS software

Frank Ivan
 

Hi Brian,

It reports 0x0204.

udrcver.sh shows:
Found a DRAWS

          HAT ID EEPROM
Name: hat
Product: Digital Radio Amateur Work Station
Product ID: 0x0004
Product ver: 0x0204
UUID: 2420cda1-931d-478c-80e5-d770f3346adb
Vendor: NW Digital Radio

Thanks - Frank - K0FEI


Re: no transmit #wsjt-x

Rob Lapham
 

still no return contact from them. Its like when you have a problem with there card they forget you.
ill take it to pay pal Monday before its to late
Rob k6jus


Re: Buster Image with DRAWS software

 

To see what version of DRAWS you have:

$ cat /proc/device-tree/hat/product_ver
0xAAFF

AA is Assembly Revision
FF is Fab Rev

Currently Shipping 0x0106

Bryan K7UDR

On Sep 5, 2019, at 3:03 PM, Frank Ivan via Groups.Io <k0fei@...> wrote:

Hi Edd,

Just glad its working.

I must have a really really early card.

Hey - its a hobby and if you are not having fun then you are doing it wrong :-)

73 - Frank - K0FEI


Re: Buster Image with DRAWS software

Frank Ivan
 

Hi Edd,

Just glad its working.

I must have a really really early card.

Hey - its a hobby and if you are not having fun then you are doing it wrong :-)

73 - Frank - K0FEI


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

Frank Ivan
 

Thanks Ed,

I can't wait for an aarch64 system.  I think it will really allow the Pi4 to show what its made of - especially with 2 or 4 gig.

73 - Frank - K0FEI


Re: No audio detected (FLDIGI) #fldigi #audio #cat #configuration #cw

Basil Gunn
 

Michael,
There are two possible choices for radio receive data with ALSA settings
for each.

There is not a lot of description on the ACC port for your radio so I'm
going to assume AF_OUT is your 1200/300 baud receive pin & DATA is your
9600 baud receive pin and AF_IN is your transmit data pin. There is a
good chance that I have this wrong so a little empirical testing
will serve you well.

On the DRAWS side make sure that you are selecting IN2 with alsamixer to
use AF_OUT.
Run alsashow.sh to verify.

Read this for more information on interfacing & controls.
https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%E2%84%A2-Audio-CODEC-Analog-Routing%2C-Digital-Interfacing-and-Controls

From the above document.

The DRAWS™ board wires all of the "L" pins to the left DIN-6 connector
and all the "R" pins to the right DIN-6 connector. The IN1 pins are
wired to the "9600 baud" or "discriminator" pin on the DIN-6, and the
IN2 pins are wired to the "1200 baud" or "audio" pin on the DIN-6.
Please note that IN3 is not used or connected anywhere on the DRAWS™.

Depending on which DRAWS mDin6 connector you are connected to you can
control your PTT pin on your ACC port.
Left connector port 0, GPIO 12
Right connector port 1, GPIO 23

There are some notes for setting up FLdigi using older NW Digital hats
here:
https://nw-digital-radio.groups.io/g/udrc/wiki/UDRC%E2%84%A2-and-fldigi-Setup-Page


Hope that helps.

/Basil n7nix

Michael Sharp via Groups.Io <nexxusix=yahoo.com@groups.io> writes:

Hello,
I am attempting to connect a Xiegu G90 to the DRAWS Hat. I am using a custom made cable from Ham Made Parts. Using my oscilloscope, I can definitely confirm that there is audio coming from the G90 through the custom cable. The cable will connect directly from the ACC port of the G90 to the DRAWS Hat Right Channel.

I am using the latest DRAWS image for Raspberry Pi 3, and I would like to use the DRAWS Hat with FLDIGI so I can send and receive CW.The problem I am having is that I don’t see any audio coming through to FLDIGI. Also, I am a bit overwhelmed with all of the configuration options in the Audio Mixer that the DRAWS Hat offers. Which inputs or outputs do I enable? Do I need to set the attenuators? How does the DRAWS Hat show up as a CAT control?

There certainly seems to be a lot of flexibility in this card to say the least. I’m sure that the problem is a configuration problem, possibly even needing Permissions or Group Access (?) from the Raspberry Pi OS.

Any help appreciated... Thanks in advance!

73,
-Michael


Re: No audio detected (FLDIGI) #fldigi #audio #cat #configuration #cw

 

DRAWS™ Manager has links to many application support groups.

For fldigi audio adjustment, check this page http://www.w1hkj.com/FldigiHelp/audio_adjust_page.html

On Thu, Sep 5, 2019 at 11:58 AM John D Hays - K7VE via Groups.Io <john=hays.org@groups.io> wrote:
Hi Michael,

If you are not familiar with all of the workings of CODEC chip, it is best not to use alsamixer or similar tools to configure settings.  The DRAWS™ Manager is designed to control the selection of ports and levels.  Use one of the setalsa scripts in the n7nix tools to reset the CODEC into a basic configuration, then use use DRAWS™ Manager to set up for your radio.

Application configuration assistance is best handled through the application support groups, though other users of fldigi on this forum may lend advice.  

On Thu, Sep 5, 2019 at 11:36 AM Michael Sharp via Groups.Io <nexxusix=yahoo.com@groups.io> wrote:
Hello,
I am attempting to connect a Xiegu G90 to the DRAWS Hat. I am using a custom made cable from Ham Made Parts. Using my oscilloscope, I can definitely confirm that there is audio coming from the G90 through the custom cable. The cable will connect directly from the ACC port of the G90 to the DRAWS Hat Right Channel.

I am using the latest DRAWS image for Raspberry Pi 3, and I would like to use the DRAWS Hat with FLDIGI so I can send and receive CW. The problem I am having is that I don’t see any audio coming through to FLDIGI. Also, I am a bit overwhelmed with all of the configuration options in the Audio Mixer that the DRAWS Hat offers. Which inputs or outputs do I enable? Do I need to set the attenuators? How does the DRAWS Hat show up as a CAT control?

There certainly seems to be a lot of flexibility in this card to say the least. I’m sure that the problem is a configuration problem, possibly even needing Permissions or Group Access (?) from the Raspberry Pi OS.

Any help appreciated... Thanks in advance!

73,
-Michael



--
John D. Hays
Kingston, WA
K7VE

 



--
John D. Hays
Kingston, WA
K7VE

 


NW Digital Radio availability September 6-8th

 

The NW Digital Radio team will be attending the Digital Summer Gathering this weekend.  Email service at the camp is very limited.  Requests for support, either technical or sales, will likely not be reviewed until Monday, so please be patient if looking for assistance.

This is a great annual event in the Seattle area.  If you happen to be in the area, drop by and meet the team.



John D. Hays
Director

  


Re: No audio detected (FLDIGI) #fldigi #audio #cat #configuration #cw

 
Edited

Hi Michael,

If you are not familiar with all of the workings of CODEC chip, it is best not to use alsamixer or similar tools to configure settings.  The DRAWS™ Manager is designed to control the selection of ports and levels.  Use one of the setalsa scripts in the n7nix tools to reset the CODEC into a basic configuration, then use DRAWS™ Manager to set up for your radio.

Application configuration assistance is best handled through the application support groups, though other users of fldigi on this forum may lend advice.  

On Thu, Sep 5, 2019 at 11:36 AM Michael Sharp via Groups.Io <nexxusix=yahoo.com@groups.io> wrote:
Hello,
I am attempting to connect a Xiegu G90 to the DRAWS Hat. I am using a custom made cable from Ham Made Parts. Using my oscilloscope, I can definitely confirm that there is audio coming from the G90 through the custom cable. The cable will connect directly from the ACC port of the G90 to the DRAWS Hat Right Channel.

I am using the latest DRAWS image for Raspberry Pi 3, and I would like to use the DRAWS Hat with FLDIGI so I can send and receive CW. The problem I am having is that I don’t see any audio coming through to FLDIGI. Also, I am a bit overwhelmed with all of the configuration options in the Audio Mixer that the DRAWS Hat offers. Which inputs or outputs do I enable? Do I need to set the attenuators? How does the DRAWS Hat show up as a CAT control?

There certainly seems to be a lot of flexibility in this card to say the least. I’m sure that the problem is a configuration problem, possibly even needing Permissions or Group Access (?) from the Raspberry Pi OS.

Any help appreciated... Thanks in advance!

73,
-Michael

 

 


 
--
John D. Hays
Kingston, WA
K7VE
 
 
 


No audio detected (FLDIGI) #fldigi #audio #cat #configuration #cw

Michael Sharp
 

Hello,
I am attempting to connect a Xiegu G90 to the DRAWS Hat. I am using a custom made cable from Ham Made Parts. Using my oscilloscope, I can definitely confirm that there is audio coming from the G90 through the custom cable. The cable will connect directly from the ACC port of the G90 to the DRAWS Hat Right Channel.

I am using the latest DRAWS image for Raspberry Pi 3, and I would like to use the DRAWS Hat with FLDIGI so I can send and receive CW. The problem I am having is that I don’t see any audio coming through to FLDIGI. Also, I am a bit overwhelmed with all of the configuration options in the Audio Mixer that the DRAWS Hat offers. Which inputs or outputs do I enable? Do I need to set the attenuators? How does the DRAWS Hat show up as a CAT control?

There certainly seems to be a lot of flexibility in this card to say the least. I’m sure that the problem is a configuration problem, possibly even needing Permissions or Group Access (?) from the Raspberry Pi OS.

Any help appreciated... Thanks in advance!

73,
-Michael


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

Edouard Lafargue
 


  The one big 'no-no' in this case, is to run 'raspi-update', which will move you to a bleeding edge testing kernel that really breaks a lot of drivers - it is not even an armhf kernel anymore, but aarch64 which is quite exciting by itself - . It's difficult to go back afterwards. I discovered this early on when installing Buster and trying raspi-update, and reverting to the standard kernel lead to various errors.

   As a conclusion: do not 'raspi-update' :)

Ed


On Thu, Sep 5, 2019 at 7:54 AM Frank Ivan via Groups.Io <k0fei=me.com@groups.io> wrote:
Hi Edouard,

Where did you get kernel 4.19.69-v8+?  The best I can do this morning - Sept 5 is 4.19.66-v71+ with sudo apt upgrade and 4.19.69-v71+ with sudo rpi-update on a Pi4. Both of them have the  tlv  modules.

In other words - what should I not do that might break things?

Thanks
73 Frank K0FEI



Re: Buster Image with DRAWS software

Edward Seeliger
 

Good morning Frank.
I no longer have your image - I overwrote it with a clean Raspbian Buster image and then used John Hayes (k7VE) instructions and Basil Gunn's (N7NIX) scripts to build a working DRAWS Buster image that is fully expanded, shows the UDRC sound device, and runs GPSD / GPSMON / CGPS as well as Xastir, YACC, WSJTX, FLDIGI, and Direwolf.
My DRAWS card has the GPS port on the side sitting above the RPi 3B+ power port.
I do not have an RPI 4.
Edd - KD5M


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

Frank Ivan
 

Hi Edouard,

Where did you get kernel 4.19.69-v8+?  The best I can do this morning - Sept 5 is 4.19.66-v71+ with sudo apt upgrade and 4.19.69-v71+ with sudo rpi-update on a Pi4. Both of them have the  tlv  modules.

In other words - what should I not do that might break things?

Thanks
73 Frank K0FEI



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

Edouard Lafargue
 

One thing I have noticed about those discussions whether udrc/draws works or not on various Pis: the necessary codecs for the DRAWS/UDRC seem to be hit or miss in the latest kernel module distributions on Raspbian:
 
root@raspberrypi:/lib/modules# find . -name "*tlv*"
./4.19.66+/kernel/sound/soc/codecs/snd-soc-tlv320aic32x4-i2c.ko
./4.19.66+/kernel/sound/soc/codecs/snd-soc-tlv320aic32x4.ko
./4.19.66-v7+/kernel/sound/soc/codecs/snd-soc-tlv320aic32x4-i2c.ko
./4.19.66-v7+/kernel/sound/soc/codecs/snd-soc-tlv320aic32x4.ko
./4.19.69+/kernel/sound/soc/codecs/snd-soc-tlv320aic32x4-i2c.ko
./4.19.69+/kernel/sound/soc/codecs/snd-soc-tlv320aic32x4.ko
./4.19.66-v7l+/kernel/sound/soc/codecs/snd-soc-tlv320aic32x4-i2c.ko
./4.19.66-v7l+/kernel/sound/soc/codecs/snd-soc-tlv320aic32x4.ko
root@raspberrypi:/lib/modules#
 
   For instance, the modules are missing from 4.19.69-v8+ which is the current latest RPi kernel as of Sept 4th.
 
  -> If you type 'uname -a' and your kernel version does not match one of the versions that contain the right modules, you'll be out of luck. My impression is that this might be one of the reasons why some people get the DRAWS working right away, and some just can't get it to load: it all depends on when you did your latest kernel update through "apt-get upgrade"


Re: no transmit #wsjt-x

Rob Lapham
 

I meant pin 1 for audio