|
Re: [udrc] #draws Aluminum Case
#draws
I’m in the same boat!
toggle quoted messageShow quoted text
On Sep 2, 2019, at 11:54 AM, Chris - KC9AD <c.doutre@...> wrote:
|
|
|
|
Re: [udrc] #draws Aluminum Case
#draws
Chris - KC9AD
If it’s any encouragement, many of run our systems without a case initially. Getting it running is part of the fun. To me, it’s simply magical to attach a keyboard, mouse, and monitor to that tiny system and see it come to life. And Ethernet, and VNC! 73.
Chris Doutre KC9AD
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of okiejim
I also have been waiting for mine for the same reason. My hat is just sitting not in use until I get the case. Sure do hope we get an update soon. And it would be nice to know they know I paid for one along time ago.
|
|
|
|
Re: [udrc] #draws Aluminum Case
#draws
okiejim
I also have been waiting for mine for the same reason. My hat is just sitting not in use until I get the case. Sure do hope we get an update soon. And it would be nice to know they know I paid for one along time ago.
73's kd6vpe
|
|
|
|
Re: [udrc] #draws Aluminum Case
#draws
Tim Huffaker
I really hope I can get the discounted early adopters case I ordered last April. Or it would be nice to know if we will ever get the case. I wanted for its emi shielding and power port. Cases for these boards are limited.
Thank you, Tim KM4ESU
|
|
|
|
Re: no transmit
#wsjt-x
Rob Lapham
Here are the outputs
pi@k6jus:~/n7nix $ piver.sh Pi 3 Model B+ Mfg by Sony UK Has WiFi pi@k6jus:~/n7nix $ udrcver.sh
Found a DRAWS HAT ID EEPROM
Name: hat Product: Digital Radio Amateur Work Station Product ID: 0x0004 Product ver: 0x0106 UUID: 9598845d-e110-49ce-9287-d770da081361 Vendor: NW Digital Radio pi@k6jus:~/n7nix/deviation $ ./measure_deviate.sh -c left
Using tone: 2200 (wave file name: 2200hzsin.wav) for duration 30 & left connector using gpio: 12 Found existing wav file: 2200hzsin.wav If using devcal from Svxlink make sure devcal line has -f2200 Using PTT GPIO 12 with tone of 2200 Hz Playing WAVE '2200hzsin.wav' : Signed 32 bit Little Endian, Rate 48000 Hz, Stereo Hardware PCM card 1 'udrc' device 0 subdevice 0 Its setup is: stream : PLAYBACK access : RW_INTERLEAVED format : S32_LE subformat : STD channels : 2 rate : 48000 exact rate : 48000 (48000/1) msbits : 32 buffer_size : 24000 period_size : 6000 period_time : 125000 tstamp_mode : NONE tstamp_type : MONOTONIC period_step : 1 avail_min : 6000 period_event : 0 start_threshold : 24000 stop_threshold : 24000 silence_threshold: 0 silence_size : 0 boundary : 1572864000 appl_ptr : 0 hw_ptr : 0 ##################################################+| MAX^C pi@k6jus:~/n7nix/deviation $ ./measure_deviate.sh
Using tone: 2200 (wave file name: 2200hzsin.wav) for duration 30 & right connector using gpio: 23 Found existing wav file: 2200hzsin.wav If using devcal from Svxlink make sure devcal line has -f2200 Using PTT GPIO 23 with tone of 2200 Hz Playing WAVE '2200hzsin.wav' : Signed 32 bit Little Endian, Rate 48000 Hz, Stereo Hardware PCM card 1 'udrc' device 0 subdevice 0 Its setup is: stream : PLAYBACK access : RW_INTERLEAVED format : S32_LE subformat : STD channels : 2 rate : 48000 exact rate : 48000 (48000/1) msbits : 32 buffer_size : 24000 period_size : 6000 period_time : 125000 tstamp_mode : NONE tstamp_type : MONOTONIC period_step : 1 avail_min : 6000 period_event : 0 start_threshold : 24000 stop_threshold : 24000 silence_threshold: 0 silence_size : 0 boundary : 1572864000 appl_ptr : 0 hw_ptr : 0 ##################################################+| MAX pi@k6jus:~ $ gpio readall +-----+-----+---------+------+---+---Pi 3B+-+---+------+---------+-----+-----+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM | +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+ | | | 3.3v | | | 1 || 2 | | | 5v | | | | 2 | 8 | SDA.1 | ALT0 | 1 | 3 || 4 | | | 5v | | | | 3 | 9 | SCL.1 | ALT0 | 1 | 5 || 6 | | | 0v | | | | 4 | 7 | GPIO. 7 | ALT0 | 0 | 7 || 8 | 0 | IN | TxD | 15 | 14 | | | | 0v | | | 9 || 10 | 1 | IN | RxD | 16 | 15 | | 17 | 0 | GPIO. 0 | IN | 1 | 11 || 12 | 1 | ALT0 | GPIO. 1 | 1 | 18 | | 27 | 2 | GPIO. 2 | IN | 0 | 13 || 14 | | | 0v | | | | 22 | 3 | GPIO. 3 | IN | 0 | 15 || 16 | 0 | OUT | GPIO. 4 | 4 | 23 | | | | 3.3v | | | 17 || 18 | 0 | IN | GPIO. 5 | 5 | 24 | | 10 | 12 | MOSI | IN | 0 | 19 || 20 | | | 0v | | | | 9 | 13 | MISO | IN | 0 | 21 || 22 | 0 | IN | GPIO. 6 | 6 | 25 | | 11 | 14 | SCLK | IN | 0 | 23 || 24 | 1 | IN | CE0 | 10 | 8 | | | | 0v | | | 25 || 26 | 0 | IN | CE1 | 11 | 7 | | 0 | 30 | SDA.0 | IN | 1 | 27 || 28 | 1 | IN | SCL.0 | 31 | 1 | | 5 | 21 | GPIO.21 | IN | 1 | 29 || 30 | | | 0v | | | | 6 | 22 | GPIO.22 | IN | 1 | 31 || 32 | 0 | OUT | GPIO.26 | 26 | 12 | | 13 | 23 | GPIO.23 | OUT | 1 | 33 || 34 | | | 0v | | | | 19 | 24 | GPIO.24 | ALT0 | 1 | 35 || 36 | 0 | IN | GPIO.27 | 27 | 16 | | 26 | 25 | GPIO.25 | IN | 0 | 37 || 38 | 0 | ALT0 | GPIO.28 | 28 | 20 | | | | 0v | | | 39 || 40 | 0 | ALT0 | GPIO.29 | 29 | 21 | +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+ | BCM | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | BCM | +-----+-----+---------+------+---+---Pi 3B+-+---+------+---------+-----+-----+ Ill have to study a liitle more on gpio pins Thanks Rob k6jus
|
|
|
|
Re: no transmit
#wsjt-x
Rob,
toggle quoted messageShow quoted text
Lets confirm that measure_deviate.sh is working properly. Could you please cut & paste the console output of all the commands below. piver.sh udrcver.sh # Using o-scope check both left & right channels. cd cd n7nix/deviation ./measure_deviate.sh -c left ./measure_deviate.sh -c right # Verify gpio 7 is set to correct mode gpio readall | grep -i "gpio. 7" Thanks, /Basil Rob Lapham <ke6jus@roadrunner.com> writes:
well today I made a din brakeout cable to test the audio to the ft-817 with a o-scope and using
|
|
|
|
Re: no transmit
#wsjt-x
Rob Lapham
well today I made a din brakeout cable to test the audio to the ft-817 with a o-scope and using
./measure_deviate.sh -c left there is no audio on pin 3 or any other pin. I tested with pin 6 connected and disconneted no difference. did the same test with a working sound card and wsjt-x and have a good signal on the o-scope. what am I missing? Is there any other test I can do to the hat. thanks rob k6jus
|
|
|
|
Success!
#beta13
#earlyadopter
#fldigi
#hf
John Amdor III
I am happy to report that after many frustrating evenings puzzling out the setup of my first generation DRAWS hat I made a contact!
PSK31, FLDIGI 4.1.03, Alinco DX70TH, T2FD antenna, homebuilt cable. John K0MXL Council Bluffs IA
|
|
|
|
Re: 1k2 APRS via Satellite successful
K4KDR <scott23192@...>
Sounds great, Basil! We currently have 9600 APRS available with satellite FalconSat-3, so I'll give that a try when there's a favorable pass. With the volume of cubesats being deployed these days, hopefully there will be more with 2-way 9600 capability soon. -Scott ======================
On Sat, Aug 31, 2019 at 1:26 PM Basil Gunn <basil@...> wrote:
|
|
|
|
Re: 1k2 APRS via Satellite successful
Scott,
toggle quoted messageShow quoted text
Great to hear your success!! Motivates me to play with my projects! I have a nice 9600 baud demo with DRAWS using P2P paclink-unix that I'll be showing at Summer Gathering next weekend. [https://lowervalleyassembly.us/tag/summer-gathering/] /Basil K4KDR <scott23192@gmail.com> writes:
Hi everyone. Just wanted to share that I was able to get digipeated
|
|
|
|
Re: no transmit
#wsjt-x
Rob Lapham
thanks Jim but the radio will go into transmit but no power out there is not enough drive to show any power out . it has to
be a audio problem Rob k6jus
|
|
|
|
1k2 APRS via Satellite successful
K4KDR <scott23192@...>
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 VA7SHG/VE7TGZ
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.
toggle quoted messageShow quoted text
Jim ------ 73, Jim VA7SHG - Phone VE7TGZ - Other
|
|
|
|
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,
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: or appended to the overlay line like this: Note here the use of a colon ( 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:
|
|
|
|
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 <scott23192@...>
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:
|
|
|
|
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 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 Move the same SD card to the Pi 3: pi@raspberrypi:~ $ aplay -l 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:
|
|
|
|
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
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.
|
|
|
|
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:
|
|
|
