Date   

Re: Confirm my understanding of the radio port configuration in direwolf.conf...

Charlie Hein
 

Never Mind - I sorted it out.  That is exactly how it goes.  Left is channel 0 and right is channel 1 in direwolf.conf.  For those running BPQ or linBPQ, the TNC port using the left radio port is Channel A, the TNC Port using the right radio port is Channel B in bpq.cfg - or at least, that is what's up and running on my installation.

Charlie


Confirm my understanding of the radio port configuration in direwolf.conf...

Charlie Hein
 

Hi guys - can I assume that if I'm using Direwolf, "channel 0" is the first radio port, and "channel 1" is the second radio port on the DRAWS board?  Need to set up the second port for 9600 baud, and while I *think* I understand how it's configured it can't hurt to ask.

Charlie


Re: DRAWS to Elecraft KX3

Ruben .
 

Matt,

You will need to set up your Pi as a Hotspot and log in directly to the Pi.

Lots of info and scripts available on the internet. N7NIX may have something, KM4ACK has some nice scripts, haven’t tried it with a DRAWS image.

Ruben
WA2NBL


On Oct 12, 2020, at 2:34 PM, allred13 via groups.io <allred13@...> wrote:

How did you make out on this? 

I'm trying to use my RPI4 with Draws headless with a Android tablet offline for remote ops. I can get it all to work with internet either VNC or remote desktop but that's it. 

Anyone got any successes getting this to work offline without a screen? 

Thanks for the help!
Matt K1MDA 


Re: DRAWS to Elecraft KX3

allred13@...
 

How did you make out on this? 

I'm trying to use my RPI4 with Draws headless with a Android tablet offline for remote ops. I can get it all to work with internet either VNC or remote desktop but that's it. 

Anyone got any successes getting this to work offline without a screen? 

Thanks for the help!
Matt K1MDA 


Re: Fans, Pi4, and the DRAWS case

Ryan Matthew Headley
 

It is an imperfect solution, but I use a heatsink case (solid aluminium--the entire case acts a a heatsink) with a stacking header.  This doesn't really protect the DRAWS board, but you can still anchor it to the Pi if you use longer screws.


Re: OpenRepeater running witH DRAWS hat #udrc

km4cj@...
 

Thanks for the tips.  That is actually where I started.  I did a fresh draws image.  aplay -l showed udrc as a sound device.  Then I ran the OpenRepeater install script.  It installed with no errors.   Then rebooted.   I boots to the raspberry login GUI, and when I login it reverts back to the login GUI.  But OpenRepeater runs a server with an html interface.  So ran that, but udrc was still not available. I assume the OpenRepeater load script overwrote several things.  I am sure one could edit the install script to just load the essentials, but am not proficient in the Linux file system.    I think the DRAWS hat would be a great hardware solution for OpenRepeater and provides a lower cost alternative to some of the other radio interface hats.  

I will continue to experiment and see what I can learn.  
Thanks again for the comments!


Re: #setup showudrc.sh isn't showing #setup

allred13@...
 

Basil,
I am using an FT-857. I just switched my cable to the one that came with the DRAWS and it works now.

Thanks for the help!

Matt
k1mda  


Re: #setup showudrc.sh isn't showing #setup

Basil Gunn
 

Your DRAWS hardware looks fine.
What program are you using to test "RF going out" and which mDin6
connector are you using?

You can easily test your PTT setup with the ptt_ctrl.sh script
ie. to turn PTT on/off for the left connector

ptt_ctrl.sh -l on
ptt_ctrl.sh -l off

Run this to see more options.
ptt_ctrl.sh -?

Look for the red LED next to the mDin6 connector to turn on & off as
well as looking at your radio.

Also your ALSA settings look suspicious, you are not routing any audio
to the DRAWS hat. What radio are you using? Have you set up ALSA
settings for deviation on that radio? Did you follow the 'Getting
Started Guide'?
https://nw-digital-radio.groups.io/g/udrc/wiki/8921

allred13 via groups.io <allred13=mac.com@groups.io> writes:

hello all. Trying to get my draws set up for digital modes. i thought
i had it there but it my watt meter wasnt seeing any RF going out. I
re- imaged from the wiki and was told to post the showUDrc.sh here. I
am not very technical when it comes to Pi's. Youtube is my friend,
usually. Thanks for the help. K1MDA

pi@raspberrypi:~ $ showudrc.sh
==== Sound Card ====
udrc card number line: card 2: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
udrc is sound card #2
==== ALSA Controls for Radio Transmit ====
LO Driver Gain L:[0.00dB] R:[0.00dB]
PCM L:[-20.00dB] R:[-20.00dB]
DAC Playback PT L:[P3] R:[P3]
LO Playback CM [Full Chip]
==== ALSA Controls for Radio Receive ====
ADC Level L:[0.00dB] R:[0.00dB]
IN1 L:[Off] R:[Off]
IN2 L:[Off] R:[Off]


#setup showudrc.sh isn't showing #setup

allred13@...
 

hello all. Trying to get my draws set up for digital modes. i thought i had it there but it my watt meter wasnt seeing any RF going out. I re- imaged from the wiki and was told to post the showUDrc.sh here. I am not very technical when it comes to Pi's. Youtube is my friend, usually. Thanks for the help. K1MDA

pi@raspberrypi:~ $ showudrc.sh
==== Sound Card ====
udrc card number line: card 2: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
udrc is sound card #2
==== ALSA Controls for Radio Transmit ====
LO Driver Gain  L:[0.00dB] R:[0.00dB]
PCM         L:[-20.00dB] R:[-20.00dB]
DAC Playback PT L:[P3] R:[P3]
LO Playback CM [Full Chip]
==== ALSA Controls for Radio Receive ====
ADC Level L:[0.00dB] R:[0.00dB]
IN1 L:[Off] R:[Off]
IN2 L:[Off] R:[Off]
 
==== Pi Ver ====
 
Unknown pi version: b03112
 
Model: Raspberry Pi 4 Model B Rev 1.2
Revision : b03112
Hardware : BCM2711
Revision : b03112
Serial : 10000000d1ced6a9
Model : Raspberry Pi 4 Model B Rev 1.2
 
==== Pi Firmware VideoCore Ver ====
Aug  6 2020 16:22:25 
Copyright (c) 2012 Broadcom
version af3edc2de473197cdfe1ff5a8ff2d34095d5b336 (clean) (release) (start)
 
==== Pi Firmware EEPROM Ver ====
Apr 16 2020 18:11:26
version a5e1b95f320810c69441557c5f5f0a7f2460dfb8 (release)
timestamp 1587057086
 
==== Pi Firmware EEPROM Config ====
BOOT_UART=0
WAKE_ON_GPIO=1
POWER_OFF_ON_HALT=0
 
==== udrc Ver ====
Found a DRAWS
 
     HAT ID EEPROM
Name:        hat
Product:     Digital Radio Amateur Work Station
Product ID:  0x0004
Product ver: 0x0108
UUID:        a0d4f1ee-4d8a-48cb-acd2-5c115c0c34f4
Vendor:      NW Digital Radio
 
==== sys Ver ====
----- image version
2020 08 22 09:30:49 PDT: SD image version: nwdr17
----- /proc/version
Linux version 5.4.51-v7l+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1333 SMP Mon Aug 10 16:51:40 BST 2020
 
----- /etc/*version: 10.4
 
----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
 
----- lsb_release
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
Release: 10
Codename: buster
 
---- systemd
   Static hostname: raspberrypi
         Icon name: computer
        Machine ID: 27ac1f0c20904cb7a960920e966db545
           Boot ID: a5a3dbe4d1634a44b77a6327d95deb69
  Operating System: Raspbian GNU/Linux 10 (buster)
            Kernel: Linux 5.4.51-v7l+
      Architecture: arm
        sd card id: 035344534c333247800cc74cb400e400
 
---- modules
snd_soc_tlv320aic32x4_i2c    16384  9
snd_soc_tlv320aic32x4    40960  1 snd_soc_tlv320aic32x4_i2c
regmap_i2c             16384  3 ti_ads1015,sc16is7xx,snd_soc_tlv320aic32x4_i2c
snd_soc_core          200704  5 vc4,snd_soc_simple_card_utils,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_soc_simple_card
snd_pcm                98304  6 vc4,snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_bcm2835,snd_soc_core
snd                    73728  14 snd_compress,snd_timer,snd_soc_tlv320aic32x4,snd_bcm2835,snd_soc_core,snd_pcm
 
---- kernel
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name               Version      Architecture Description
+++-==================-============-============-=================================
ii  raspberrypi-kernel 1.20200811-1 armhf        Raspberry Pi bootloader
 
---- Codec drivers
Found: snd-soc-tlv320aic32x4-i2c.ko, OK
Found: snd-soc-tlv320aic32x4.ko, OK
Directory: /proc/device-tree/soc/i2c@7e804000/tlv320aic32x4@18 exists and status is okay
 
---- syslog
 
---- dmesg
 
 
----- Dire Wolf DEVELOPMENT version 1.6 G (Aug 21 2020)
 
==== Filesystem ====
/dev/root        29G  5.0G   24G  18% /
 
==== boot config ====
 
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
 
[all]
#dtoverlay=vc4-fkms-v3d
 
# Flush all overlays, ie. deprecated overlays loaded from eeprom
dtoverlay=
# enable udrc/draws if no eeprom
dtoverlay=draws,alsaname=udrc
force_turbo=1
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
 
---- gpsd
/usr/local/sbin/gpsd
gpsd: 3.21 (revision 3.21)
● gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2020-10-05 13:11:57 EDT; 2min 47s ago
  Process: 610 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
 Main PID: 624 (gpsd)
    Tasks: 3 (limit: 3861)
   CGroup: /system.slice/gpsd.service
           └─624 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
 
Oct 05 13:11:57 raspberrypi systemd[1]: Starting GPS (Global Positioning System) Daemon...
Oct 05 13:11:57 raspberrypi systemd[1]: Started GPS (Global Positioning System) Daemon.
 
---- chrony
crw-rw---- 1 root root    239, 0 Oct  5 13:11 /dev/pps0
crw------- 1 root root    239, 1 Oct  5 13:12 /dev/pps1
crw-rw---- 1 root dialout 510, 0 Oct  5 13:12 /dev/ttySC0
crw-rw---- 1 root dialout 510, 1 Oct  5 13:11 /dev/ttySC1
-- chrony sources
210 Number of sources = 6
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
#? GPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
#? PPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
^* time.cloudflare.com           3   6    37    58   -513us[-5652us] +/-   19ms
^- tock.teljet.net               2   6    37    58    -34ms[  -34ms] +/-   92ms
^- ntp.backplanedns.org          2   6    67    54  +3471us[+3471us] +/-   53ms
^- lithium.constant.com          2   6    37    57  +4515us[+4515us] +/-   69ms
-- chrony tracking
Reference ID    : A29FC801 (time.cloudflare.com)
Stratum         : 4
Ref time (UTC)  : Mon Oct 05 17:13:47 2020
System time     : 0.000000081 seconds fast of NTP time
Last offset     : -0.005138161 seconds
RMS offset      : 0.005138161 seconds
Frequency       : 7.299 ppm fast
Residual freq   : -55.927 ppm
Skew            : 3.731 ppm
Root delay      : 0.036228176 seconds
Root dispersion : 0.007300514 seconds
Update interval : 64.4 seconds
Leap status     : Normal
-- chrony sourcestats
210 Number of sources = 6
Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
==============================================================================
GPS                         0   0     0     +0.000   2000.000     +0ns  4000ms
PPS                         0   0     0     +0.000   2000.000     +0ns  4000ms
time.cloudflare.com         5   3    71    -55.927    596.813  -3227us  2058us
tock.teljet.net             5   3    71   -507.884   1756.256    -59ms   934us
ntp.backplanedns.org        5   5    74    +27.687   1432.000  +6295us  2718us
lithium.constant.com        5   3    71    +39.146    458.491  +6646us  2759us
 
---- sensors
-rw-r--r-- 1 root root 209 Aug 21 12:04 /etc/sensors.d/draws
iio_hwmon-isa-0000
Adapter: ISA adapter
+12V:        +13.24 V  
 +5V:         +5.05 V  
User ADC 1:   +0.00 V  
User ADC 2:   +0.00 V  
 
cpu_thermal-virtual-0
Adapter: Virtual device
temp1:        +54.0°C  
 
rpi_volt-isa-0000
Adapter: ISA adapter
in0:              N/A  
 
 
---- throttle
temp=54.0'C
throttled=0x0
 
---- locale
Locale country codes consistent among WiFi cfg file, iw reg & X11: US
core_config.sh has been run 0 time(s)


Re: OpenRepeater running witH DRAWS hat #udrc

Basil Gunn
 

Please follow Ken's advice on OpenRepeater.

Use aplay -l to determine if your DRAWS device /boot/config.txt entry is
working. To verify your entry you need to see a line similar to the one
below from the aplay command:
card x: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 []

There are some notes here on making a Raspberry Pi OS image enumerate a
DRAWS device:
https://github.com/nwdigitalradio/n7nix/blob/master/docs/DRAWS_CONFIG.md#make-your-own-raspberry-pi-image

and as I mentioned before if you have problems getting this to work just use
the NWDR image with instructions for provisioning your SD card here:
https://nw-digital-radio.groups.io/g/udrc/wiki/8921

Ken Koster <n7ipb@...> writes:

On Sunday, October 4, 2020 4:08:47 PM PDT km4cj@... wrote:
First of all thank you Basil for the quick response. The svxlink.conf file
was there, but empty. I added the sections above, rebooted, but the udrc
port did not show up. I typed the aplay -l command and comes back with "no
soundcards found". So still not able to get the audio device recognized.
The svxlink.conf file may indeed be legitimately empty. OpenRepeater uses it's
own method and from what I understand will ignore what's there.

I would guess that the real problem is the lack of an alsa udrc sound device.
Fix that as Basil suggests in his other email and I suspect the OpenRepeater
web interface will find the udrc and let you select it.

I can't say for sure because I use the stock SVXLink but I'd be surprised if
OpenRepeater can't handle it.

...


Re: OpenRepeater running witH DRAWS hat #udrc

Ken Koster
 

On Sunday, October 4, 2020 4:08:47 PM PDT km4cj@... wrote:

> First of all thank you Basil for the quick response.  The svxlink.conf file

> was there, but empty.  I added the sections above, rebooted, but the udrc

> port did not show up.  I typed the aplay -l command and comes back with "no

> soundcards found".  So still not able to get the audio device recognized.


The svxlink.conf file may indeed be legitimately empty.   OpenRepeater uses it's own method and from what I understand will ignore what's there. 


I would guess that the real problem is the lack of an alsa udrc sound device.  Fix that as Basil suggests in his other email and I suspect the OpenRepeater web interface will find the udrc and let you select it.


I can't say for sure because I use the stock SVXLink but I'd be surprised if OpenRepeater can't handle it.


...


--

Ken - N7IPB

Email: n7ipb@...

JID: n7ipb@...

SvxLink Repeaters: http://pnw220.wetnet.net

PGP Sig: F42B EF90 3CD3 31C7 3056  122E 993A 7B2E 5138 C42A

*Life should not be a journey to the grave with the intention of arriving

safely in a pretty and well preserved body, but rather to skid in broadside,

thoroughly used up, totally worn out, and loudly proclaiming -

"WOW, What a ride!"


Re: OpenRepeater running witH DRAWS hat #udrc

Basil Gunn
 

Steve,

I typed the aplay -l command and comes back with "no soundcards found"
You need to fix this first.

If you have trouble listing any sound card devices then use the NWDR SD
card image and follow the "Getting Started Guide"
https://nw-digital-radio.groups.io/g/udrc/wiki/8921

The svxlink.conf file is quite extensive, that is you would need more
than the two sections I mentioned in my previous post. The config file I
use for Echolink is over 230 lines. If you want to see the contents of
this file go to this repository
https://github.com/nwdigitalradio/echolink

You should be able to find the diff files there as well to see the
changes I made from the original installed file. The fact that there
was nothing in your svxlink.conf file would make me think that the
installation did not complete properly.

km4cj@... writes:

First of all thank you Basil for the quick response. The svxlink.conf
file was there, but empty. I added the sections above, rebooted, but
the udrc port did not show up. I typed the aplay -l command and comes
back with "no soundcards found". So still not able to get the audio
device recognized.


Re: OpenRepeater running witH DRAWS hat #udrc

km4cj@...
 

First of all thank you Basil for the quick response.  The svxlink.conf file was there, but empty.  I added the sections above, rebooted, but the udrc port did not show up.  I typed the aplay -l command and comes back with "no soundcards found".  So still not able to get the audio device recognized.


Re: OpenRepeater running witH DRAWS hat #udrc

Basil Gunn
 

Assuming you are usin SVXLink
In file /etc/svxlink/svxlink.conf

In section [RX1]
[Rx1]
TYPE=Local
AUDIO_DEV=alsa:plughw:CARD=udrc,DEV=0

In section [TX1]
[Tx1]
TYPE=Local
AUDIO_DEV=alsa:plughw:CARD=udrc,DEV=0


km4cj@... writes:

Has any one been successful with getting OpenRepeater to run with the DRAWS hat. The radio control interfaces are fine, PTT and COS via the I/O mapping. The issue is getting OpenRepeater to see the UDRC sound device. I downloaded the latest OpenRepeater image and ran it on the board. I added

dtoverlay=

dtoverlay=draws,alsaname=udrc

force_turbo=1

to the boot/config.txt file.
The Linux Kernal of the Open Repeater build is 4.19.66-v7+

Any suggestions from the group. Thanks in advance
Steve


OpenRepeater running witH DRAWS hat #udrc

km4cj@...
 

Has any one been successful with getting OpenRepeater to run with the DRAWS hat.  The radio control interfaces are fine, PTT and COS via the I/O mapping.  The issue is getting OpenRepeater to see the UDRC sound device.  I downloaded the latest OpenRepeater image and ran it on the board.  I added 


dtoverlay=

dtoverlay=draws,alsaname=udrc

force_turbo=1

 to the boot/config.txt file.
The Linux Kernal of the Open Repeater build is 4.19.66-v7+

Any suggestions from the group.  Thanks in advance
Steve


HamPi 1.1 (September 2020) Released!

 



---------- Forwarded message ---------
From: Dave Slotter, W3DJS <slotter+W3DJS@...>
Date: Sun, Sep 20, 2020 at 10:22 AM
Subject: HamPi 1.1 (September 2020) Released!
To: <Ham-Pi@groups.io>, <RaspberryPi-4-HamRadio@groups.io>
Cc: Atlanta-Hams@groups.io Group Moderators <Atlanta-Hams@groups.io>, <main@athensradioclub.groups.io>, <Cherokee-Hams@groups.io>, GARS@groups.io Group Moderators <GARS@groups.io>, <main@alfordmemorialradioclub.groups.io>, main@NFARL.groups.io <main@nfarl.groups.io>, <BarrowARC@groups.io>, <main@wc4rg.groups.io>, <main@nw-digital-radio.groups.io>


Attention All Hams Using Raspberry Pi For Ham Radio:

I am pleased to announce that HamPi 1.1 is now available for public download!

Please use the attached BitTorrent file to make it easier for everyone to get the image. And after you have completed downloading, please continue to seed for at least a week so other hams can benefit.

If you cannot or will not use BitTorrent, you may download HamPi from SourceForge:


If you run into issues, please post to the forum on https://groups.io/g/Ham-Pi/ first. If you see a bug (defect), please report it on the GitHub issues page at: https://github.com/dslotter/HamPi/issues

UPGRADING: In order to transition smoothly from HamPi 1.0 to HamPi 1.1 and preserve your configuration settings, please follow the instructions in the attached file, "UPGRADING_FROM_PRIOR_VERSION.TXT"

CHANGELOG:

Version 1.1 (September 2020) Release
====================================

Updated WSJT-X
Updated JTDX
Updated GridTracker
Added HamClock by WB0OEW
Added adifmerg command line utility
Added Lopora (QRSS viewer)
Minor fixes with SDRAngel installation
Fixed BlueDV not launching from menu as expected
Fixed FreeDV not launching from menu as expected
Updated DireWolf installation as DW and GPSd are both "moving targets"
Enhanced error message display for D-Rats software update failures
Added exclusion for EMComm / Field users in license
Partially added AMBEserver
Many other applications updated from Internet


Good luck and 73!

HamPi Logo Transparent.png


--


John D. Hays
Director

  


Re: Draws fails to start

Basil Gunn
 

Tim Huffaker <thuffaker@...> writes:

Should this command fail
app_config.sh core.
From the wiki:

cd
cd n7nix/config
# Become root
sudo su
./app_config.sh core

IF you have a command that fails I need to see all the console output
including the command.


Re: Baofeng UV-5R PTT won't turn off?

Andrew Malota
 

Howdy All -
I found some time to follow up on this. I was able to get the radio working correctly.

Another project (https://www.tnc-x.com/Baofeng.htm) provided the answer.
Evidently the resistance between the two PTT pins is too low for the baofeng to see PTT "off" when DRAWS sets PTT "off".
I grabbed a cheap PS/2 extension cable, cut it up, and spliced in a 2.2k resistor on PS/2 pin #2 (this is the sleeve of the skinny TRS connector that goes into the radio.)

So far, so good! I'm able to reliably transmit (and even more importantly, reliably STOP transmitting,) and packets that I send decode just fine.

Thanks
KF5WOR


Re: Draws fails to start

Tim Huffaker
 

Should this command fail 
app_config.sh core. 


Re: Draws fails to start

Tim Huffaker
 

Thank you Basil I must have skipped something along the way.  I did not this it was this simple.