|
Re: Using the DRAWS hat with a Raspberry Pi 4
#yaac
#replacecompass
#draws
#install
#js8call
Frank Ivan
Hi John,
If you would like to take this offline - my email address (at least the one in QRZ) is k0fei@.... Frank
|
|
|
|
Re: Using the DRAWS hat with a Raspberry Pi 4
#yaac
#replacecompass
#draws
#install
#js8call
Frank Ivan
Hi John,
I followed your steps exactly,. The second post was some additional info to show that I could read the EEPROM and thus the hardware was working. I think there is a problem that the drivers are not being loaded. Is there a log file for the image_install script? Is there anything else I can send to you? Thanks Frank - K0FEI
|
|
|
|
Re: Using the DRAWS hat with a Raspberry Pi 4
#yaac
#replacecompass
#draws
#install
#js8call
Frank, Between your two emails, I am not sure of your current state. Did you follow the steps I outlined earlier? You should be seeing the card.
On Tue, Aug 27, 2019 at 1:40 PM Frank Ivan via Groups.Io <k0fei=me.com@groups.io> wrote: Hi John, --
John D. Hays Kingston, WA K7VE
|
|
|
|
Re: Using the DRAWS hat with a Raspberry Pi 4
#yaac
#replacecompass
#draws
#install
#js8call
Frank Ivan
Hi John,
One thing more - I do see the hat ./udrcver.sh 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
|
|
|
|
Video - Pat Winlink on DRAWS
Here's a video if you are interested in setting up Pat Winlink for HF email on the DRAWS hat.
https://youtu.be/LnJQv6rDpss 73, KM4ACK Find me on YouTube
|
|
|
|
Re: Using the DRAWS hat with a Raspberry Pi 4
#yaac
#replacecompass
#draws
#install
#js8call
Frank Ivan
Hi John,
My results were not successful. I am using a Pi 4 - 2gb memory with the Buster downloaded today. I did not turn on anything except to connect to wifi. After the install I did enable ssh. uname -a Linux raspberrypi 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l GNU/Linux No udrc sound card found. aplay -l **** List of PLAYBACK Hardware Devices **** card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA] Subdevices: 7/7 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 Subdevice #4: subdevice #4 Subdevice #5: subdevice #5 Subdevice #6: subdevice #6 card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 IEC958/HDMI [bcm2835 IEC958/HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: ALSA [bcm2835 ALSA], device 2: bcm2835 IEC958/HDMI1 [bcm2835 IEC958/HDMI1] Subdevices: 1/1
Subdevice #0: subdevice #0 sudo lsmod Module Size Used by rfcomm 49152 4 bnep 20480 2 hci_uart 40960 1 btbcm 16384 1 hci_uart serdev 20480 1 hci_uart bluetooth 389120 29 hci_uart,bnep,btbcm,rfcomm ecdh_generic 28672 1 bluetooth fuse 110592 3 8021q 32768 0 garp 16384 1 8021q stp 16384 1 garp llc 16384 2 garp,stp joydev 20480 0 evdev 24576 11 brcmfmac 311296 0 brcmutil 16384 1 brcmfmac sha256_generic 20480 0 cfg80211 614400 1 brcmfmac bcm2835_v4l2 45056 0 rfkill 28672 6 bluetooth,cfg80211 bcm2835_codec 36864 0 snd_bcm2835 24576 2 v4l2_mem2mem 24576 1 bcm2835_codec videobuf2_dma_contig 20480 1 bcm2835_codec snd_pcm 102400 1 snd_bcm2835 bcm2835_mmal_vchiq 32768 2 bcm2835_codec,bcm2835_v4l2 v4l2_common 16384 1 bcm2835_v4l2 videobuf2_vmalloc 16384 1 bcm2835_v4l2 videobuf2_memops 16384 2 videobuf2_dma_contig,videobuf2_vmalloc videobuf2_v4l2 24576 3 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem videobuf2_common 45056 4 bcm2835_codec,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2 snd_timer 32768 1 snd_pcm raspberrypi_hwmon 16384 0 videodev 200704 6 bcm2835_codec,v4l2_common,videobuf2_common,bcm2835_v4l2,v4l2_mem2mem,videobuf2_v4l2 hwmon 16384 1 raspberrypi_hwmon snd 73728 7 snd_timer,snd_bcm2835,snd_pcm media 36864 2 videodev,v4l2_mem2mem vc_sm_cma 36864 1 bcm2835_mmal_vchiq rpivid_mem 16384 0 uio_pdrv_genirq 16384 0 uio 20480 1 uio_pdrv_genirq fixed 16384 0 ax25 69632 0 i2c_dev 20480 0 ip_tables 24576 0 x_tables 32768 1 ip_tables ipv6 450560 30 cat /boot/config.txt # For more options and information see # http://rpf.io/configtxt # Some settings may impact device functionality. See link above for details
# uncomment if you get no picture on HDMI for a default "safe" mode #hdmi_safe=1
# uncomment this if your display has a black border of unused pixels visible # and your display can output without overscan #disable_overscan=1
# uncomment the following to adjust overscan. Use positive numbers if console # goes off screen, and negative if there is too much border #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16
# uncomment to force a console size. By default it will be display's size minus # overscan. #framebuffer_width=1280 #framebuffer_height=720
# uncomment if hdmi display is not detected and composite is being output #hdmi_force_hotplug=1
# uncomment to force a specific HDMI mode (this will force VGA) #hdmi_group=1 #hdmi_mode=1
# uncomment to force a HDMI mode rather than DVI. This can make audio work in # DMT (computer monitor) modes #hdmi_drive=2
# uncomment to increase signal to HDMI, if you have interference, blanking, or # no display #config_hdmi_boost=4
# uncomment for composite PAL #sdtv_mode=2
#uncomment to overclock the arm. 700 MHz is the default. #arm_freq=800
# Uncomment some or all of these to enable the optional hardware interfaces #dtparam=i2c_arm=on #dtparam=i2s=on #dtparam=spi=on
# Uncomment this to enable the lirc-rpi module #dtoverlay=lirc-rpi
# Additional overlays and parameters are documented /boot/overlays/README
# Enable audio (loads snd_bcm2835) dtparam=audio=on
[pi4] # Enable DRM VC4 V3D driver on top of the dispmanx display stack dtoverlay=vc4-fkms-v3d max_framebuffers=2
[all] #dtoverlay=vc4-fkms-v3d
# enable udrc/draws if no eeprom dtoverlay=draws,alsaname=udrc force_turbo=1
|
|
|
|
Re: ARDOP or software similar to WinLink (HF mail)
#winlink
|
|
|
|
Re: Using the DRAWS hat with a Raspberry Pi 4
#yaac
#replacecompass
#draws
#install
#js8call
Mike Watkins <mike.watkins@...>
On your Pi3/4 running Buster, please report the result from: uname -a
On Mon., Aug. 26, 2019, 13:07 Frank Ivan via Groups.Io, <k0fei=me.com@groups.io> wrote: Hi John and all,
|
|
|
|
Re: Using the DRAWS hat with a Raspberry Pi 4
#yaac
#replacecompass
#draws
#install
#js8call
I did this just yesterday (from memory - not at system right now) Download and burn Buster onto SD Card Let it boot up and update/upgrade sudo reboot sudo apt install git build-essential cd cd n7nix/config sudo ./image_install.sh sudo apt install --fix-broken sudo reboot After boot try aplay -l Use n7nix scripts to install/config applications. DRAWS™ Manager is at https://github.com/nwdigitalradio/draws-manager
On Mon, Aug 26, 2019 at 1:07 PM Frank Ivan via Groups.Io <k0fei=me.com@groups.io> wrote: Hi John and all, --
John D. Hays Kingston, WA K7VE
|
|
|
|
Re: Using the DRAWS hat with a Raspberry Pi 4
#yaac
#replacecompass
#draws
#install
#js8call
Frank Ivan
Hi John and all,
I have tried everything listed above on both a Pi3 and Pi4. I can not see the sound card or the gps or even the sensor data. Can someone do a new step by step or better still a video. Maybe just a description of the kernel modules, dkms system, what is the udrc module used for and where to get it. I am interested making a portable SOTA station running FT8 and JS8CALL maybe using flrig for rig control. Not to put too sharp of a point on it, but Buster and Pi4 have been out just short of two months. Downloading the stretch Compass gives you something that can not be updated. Is there any projection when drivers for Buster and Pi 4 will be available or even a downloadable image. As for the Pi 4 heat problem, just use the PoE HAT between the pi and DRAWS and put a small heat sink on the cpu. It will not go above 58 C on a fully loaded system. 73 - Frank - K0FEI
|
|
|
|
Re: Undulating transmit audio in HF programs
#draws
Hi Mitch, I’ll check it out
toggle quoted messageShow quoted text
Send it to: NW Digital Radio RMA<ordernumber> 150 Cessna Ave Roche Harbor WA 98250 Thanks, Bryan K7UDR
|
|
|
|
Re: Undulating transmit audio in HF programs
#draws
Mitch Winkle
If no-one has any input I will package up my DRAWS for a return. It's a might expensive GPS hat at this point.
|
|
|
|
Copper PCB RFI Top for DRAWS Case
K4KDR
If anyone selects the excellent Pi/DRAWS case from C4Labs:
https://www.c4labs.com/product/nwdrpi-2-for-raspberry-pi-3b-3b-2b-b-and-drawstm-digital-radio-amateur-workstation-version-2-hat/
... and would like to add a top to help guard against RFI (as demonstrated on YouTube by KM4ACK: https://www.youtube.com/watch?v=QZqh_Rc1s9s&t=7s), I just wanted to share that in addition to aluminum, a spare piece of copper PCB material can be fabricated into a decent top.
73!
-Scott, K4KDR ====== ======
|
|
|
|
Re: no transmit
#wsjt-x
Rob,
toggle quoted messageShow quoted text
Verify that transmit is working with the simplest program possible. Use the measure_deviate.sh script to output a tone on a specific channel. Assuming you are using the mDin6 connector closest to the gps SMA connector. If you tune a second radio to the same frequency as the first you should hear a tone. cd cd n7nix/deviation ./measure_deviate.sh -c left To see the command line parameter options: ./measure_deviate.sh -h Also send the console output of showudrc.sh /Basil Rob Lapham <ke6jus@roadrunner.com> writes:
I've been trying to get my Raspberry Pi 3 working with my DRAWS hat but I think either my connection is messed up or my audio setup / levels wrong.
|
|
|
|
no transmit
#wsjt-x
Rob Lapham
I've been trying to get my Raspberry Pi 3 working with my DRAWS hat but I think either my connection is messed up or my audio setup / levels wrong.
I think Im doing something wrong I have used the draws manager and no transmit ## Symptoms - receive work - Nothing on ALC meter when I tune with WSJT-X ## Hardware - Yaesu FT-817 - Raspberry Pi 3 - DRAWS hat ## Settings - 24 Dig Disp: 0Hz - 25 Dig Mic: 61 - 26 Dig Mode: User-U - 27 Dig Shift: 0Hz - 38 Op Filter: Off - AGC: Fast - Noise Blanker: Off ## Connections -with and without Pin 6 removed from the Data cable - Data cable in Left (facing the connectors) jack - USB Serial CAT cable - into antenna or dummy load ## WSJT-X Setup - CAT control set up and working - Input: plughw:CARD=udrc,DEV=0 in left - Output: plughw:CARD=udrc,DEV=0 in left I've tried Left, Right, and other udrc input devices to no success) ## ALSA Setup I ran the setup-ft817.sh script to set my levels: ===== ALSA Controls for Radio Transmit ===== LO Driver Gain L:[-6.00dB] R:[-6.00dB] PCM L:[-16.50dB] R:[-16.50dB] DAC Playback PT L:[PTM_P3] R:[PTM_P3] LO Playback CM [Full Chip CM] ===== ALSA Controls for Radio Receive =====
ADC Level L:[-2.00dB] R:[-2.00dB] IN1 L:[Off] R:[Off] IN2 L:[10 kOhm] R:[Off] CM L:[10 kOhm] R:[10 kOhm] Thanks, Rob k6jus
|
|
|
|
Re: ARDOP or software similar to WinLink (HF mail)
#winlink
I have ARDOP setup and running with Pat on the DRAWS hat using beta 13. I've made a video tutorial, but need to edit before posting. It will release on my YouTube channel Tuesday Aug 27 at 1600 central.
73, KM4ACK Find me on YouTube
|
|
|
|
Re: ARDOP or software similar to WinLink (HF mail)
#winlink
I'm writing an ARDOP transport for paclink-unix that runs on the RPi.
toggle quoted messageShow quoted text
I use ardopc RPi (piardopc) from here: http://www.cantab.net/users/john.wiseman/Downloads/Beta/ I test that with ARIM from here: http://www.whitemesa.net/arim/arim.html#inst Currently for winlink using ARDOP on an RPi you can use PAT or LinBPQ http://www.cantab.net/users/john.wiseman/Documents/LinBPQ_WinlinkClient.html /Basil n7nix K4KDR <scott23192@gmail.com> writes:
I've only had my DRAWS board for a day, but did have success running the
|
|
|
|
Re: ARDOP or software similar to WinLink (HF mail)
#winlink
Mitch Winkle
I think there is also a build shell script in Beta13 for ARDOP, but I have not used it.
|
|
|
|
Re: ARDOP or software similar to WinLink (HF mail)
#winlink
I'm not sure if it's included, but there is an open source implementation of ARDOP that can be compiled to run natively on the Pi. Check here: http://www.cantab.net/users/john.wiseman/Documents/ARDOPC.html
toggle quoted messageShow quoted text
Matthew N8OHU
On August 23, 2019 8:03:43 PM EDT, wa9pyh@... wrote: Is anyone using the DRAWS Pi HAT for HF email that would be similar to ARDOP (part of WinLink) or WinMor (also part of WinLink) that both run under Windows? I'm using an FT857D, a Pi 3B+, a DRAWS board, a 6 pin miniDIN cable(xmt & rcv audio) and a CT62 CAT cable. The Pi is using the beta_13 image.. This setup runs JS8CALL, FLDIGI and WSJT_X properly. I would like to add HF mail using the DRAWS board. 73 --
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
|
|
|
Re: ARDOP or software similar to WinLink (HF mail)
#winlink
K4KDR
I've only had my DRAWS board for a day, but did have success running the PAT Winlink client (thanks to the YouTube videos by KM4ACK) over 2m ax25 packet. I will get around to testing the HF modes but just haven't gotten there yet. The PAT software is at: ... and by coincidence, I'm also running the FT857d & a Pi3B+. Works great! -Scott, K4KDR ==================
On Fri, Aug 23, 2019 at 8:03 PM <wa9pyh@...> wrote: Is anyone using the DRAWS Pi HAT for HF email that would be similar to ARDOP (part of WinLink) or WinMor (also part of WinLink) that both run under Windows? I'm using an FT857D, a Pi 3B+, a DRAWS board, a 6 pin miniDIN cable(xmt & rcv audio) and a CT62 CAT cable. The Pi is using the beta_13 image.. This setup runs JS8CALL, FLDIGI and WSJT_X properly. I would like to add HF mail using the DRAWS board. 73
|
|
|
