Date   
Re: Just starting out #draws

Ryan Matthew Headley
 

This is the image you should use if you need and X server:

https://downloads.raspberrypi.org/raspbian_latest

If you can get by without a desktop, this install is a little over half the size of the above version with the X server.

https://downloads.raspberrypi.org/raspbian_lite_latest

Either way, make sure that you make the changes to /boot/config.txt to enable to DRAWS hat.

When you go to configure your specific software packages, the DRAWS board shows up as the ALSA device 'UDRC.'

Re: Just starting out #draws

Paul Noa
 

Ryan,

Thanks for that advice, I was hoping there would be a minimal configuration as well, so this sounds good.

To clarify, so there is no need to download the latest image from NWDR/support, correct?

Could you be more specific on the Raspian with Desktop? I already have an image with a Debian blend, the option not in NOOBS but from RPI.org.

Thanks fro your support in advance,

Paul

Re: Just starting out #draws

Ryan Matthew Headley
 

If your only application will be as you describe, I would suggest foregoing the DRAWS image.

Download Raspbian with Desktop (NOT the one with 'recommeded software'); install gpsd, direwolf, and FoxtrotGPS; and you are good to go without a lot of complication.

Be sure to make the changes in /boot/config.txt to enable the DRAWS hat described at the bottom of the 'Getting Started' page.

This may not be what you are looking for, but this is what I would do with for such a straightforward single application.

#draws #audio #ax25 #draws #audio #ax25

Ryan Matthew Headley
 

Apologies ahead of time if I am rehashing anything already extant on the boards.  I have attempted to search for solutions, but have not been able to find anything.

I received my DRAWS hat yesterday, loaded the DRAWS image, and followed the configuration steps listed on the boards.  Most things worked exactly as indicated. 

Using the scripts indicated in 'Getting Started,' I configured AX25 and got ALSA working, but with a few curiosities.  Mysteriously, the default configuration sets AX25 to use the right connector.  (That one took a few minutes to figure out).  ALSA audio was is curious as well. 

In testing to set levels, I set up an Alinco 135 connected to the DRAWS, and a Yaesu FT-991A for monitoring--both on 144.390Mhz.  I had to set the output gain to +15db before it was even audible--and +29db is decodable, but still well below the other AX25 signals I was receiving from elsewhere.  I switched the radios with virtually the same result.  I cannot imagine that this is normal. 

I am probably going to set up my own imagine later today for further testing.

Any thoughts?

Re: Stream Audio Using VNC Command Line to Local Network #audio

Paul Noa
 

Basil,
I am reaching out for a little direction getting started with my Draws (Hat Only) install on RPi 3 B+ as I see you are very active and obviously much more knowledgeable than myself in this area.

The more I  read the more unsure I become as where to start. This is where I have started :
Could you be so kind as to direct me to the best most reliable version of Buster w/NWDR code for the Draws hat if this is not the best place to start?

Thanks in advance for your support,

Paul

Paul 


On Sat, 16 Nov 2019 at 11:05, Basil Gunn <basil@...> wrote:

Where in the command that you gave is the syntax for the USB device you
are using? dsnoop:1 ?

If I use cvlc --longhelp it lists alsa audio devices so I'm guessing you
would replace dsnoop:1 with dsnoop:CARD=udrc

cvlc --longhelp | grep -i alsa-audio-device
VLC media player 3.0.7 Vetinari (revision 3.0.7-0-g86cee31099)
      --alsa-audio-device {null,default:CARD=ALSA,sysdefault:CARD=ALSA,dmix:CARD=ALSA,DEV=0,dmix:CARD=ALSA,DEV=1,dsnoop:CARD=ALSA,DEV=0,dsnoop:CARD=ALSA,DEV=1,hw:CARD=ALSA,DEV=0,hw:CARD=ALSA,DEV=1,plughw:CARD=ALSA,DEV=0,plughw:CARD=ALSA,DEV=1,default:CARD=udrc,sysdefault:CARD=udrc,dmix:CARD=udrc,DEV=0,dsnoop:CARD=udrc,DEV=0,hw:CARD=udrc,DEV=0,plughw:CARD=udrc,DEV=0,default}

/Basil

Anthony Sutera <tsutera@...> writes:

> I am using my Draws Hat mainly for WSJT-X. I have a quick question: I
> would like to stream audio to my local network. On my other setups
> (Raspberry Pi3) using a signal link USB audio card, I succesfully use
> this command:

cvlc -vvv alsa://dsnoop:1 --sout '#transcode{acodec=mp3,ab=64,channels=1}:standard{access=http,dst=192.168.165.126/out.mp3}'

> to stream audio out to my local network. Can someone let me know the
> correct audio device to list in the command line using the Draws Hat
> sound card? Thank you! Tony Sutera KF7VLT



Just starting out #draws

Paul Noa
 

I just received my new draws unit (Hat Only).

I am using Pi 3B+.  I have reviewed as much online documentation I can find but not sure which is the latest, did not expect a beta version on the support page...

I am not sure if I have installed the proper/best version of software and would like not to go to far down the wrong path if possible.

My application is simple and limited to one goal: track multiple assets using FoxtrotGPS with DireWolf using a single radio.

Any help getting me started sorting all of the options would be greatly appreciated. perhaps simply a confirmation the support page downloads are the latest and most reliable.

Paul

Re: PAT with DRAWS on VHF

Dave Christensen
 

Thank you again for your time.  with your explanation I now understand the relationship of axports, mkiss, and the PAT config.  I did run the config script you provided 
----------------------------------------------------------------------------------
This is my edited PAT ax25 section now using the correct port name:

},
  "listen": [],
  "hamlib_rigs": {},
  "ax25": {
    "port": "udr0",
    "beacon": {
      "every": 3600,
      "message": "Winlink P2P",
      "destination": "IDENT"
    },
    "rig": ""
  },
------------------------------------------------------------
And my axports with the line I added removed referencing wl2k

It looks like this now:
# /usr/local/etc/ax25/axports
#
# The format of this file is:
#portname       callsign        speed   paclen  window  description
udr0        KD7UM-6         9600    255     2       Direwolf port
udr1        KD7UM-10            9600    255     2       Winlink port
---------------------------------------------------------------------------------------------
Now I am trying to find the whole paclink-unix installation instructions, MUTT interface, piardop, etc.  I know it is out there, I just haven't found it since you referenced adding piardop to the distribution 9 going forward with your work on Packlink-UNIX.

Another day....  TNX

Re: PAT with DRAWS on VHF

Basil Gunn
 

The packet configuration for a DRAWS hat enables both mDin6 connectors
as ports udr0 & udr1. If you follow the documentation & use the
configuration scripts these ports are started at boot time using systemd
unit files that use mkiss (instead of kissattach) for multi KISS attach
so that both ports are active & available.

Since you had to edit the axports file I'm guessing you did not use the
configuration script that is supplied in the n7nix directory on the
DRAWS image.

Very pleased that you have PAT working with your DRAWS hat.
/Basil


Dave Christensen <dkc2030@...> writes:

Basil, et.al

All the tests you mentioned above were all working normally from the image installation. Thank you again for detailing these, I have save this post for future checkouts.

To make a really long story short here is what fixed PAT running on the NW image:
1. Added a line to the /etc/ax25/axports file in the format: wl2k KD7UM 1200 255 7 Winlink
2. Did a sudo kissattach /tmp/kisstnc wl2k

It all worked. Now two things for me to do: create a script when starting PAT to do the kissattach and then the pat http command.

This help came from Scott:
"I believe this is the video that I used to get setup for PAT over ax25:

https://www.youtube.com/watch?v=o8OBF47UkeI&t=509s

-Scott, K4KDR"

Having said all this, and given my Newbie status, I am going to
investigate patlink-unix knowing now that this is the supported
product.

Again, thank you and all the moderators and contributors for your
time.

Re: PAT with DRAWS on VHF

Dave Christensen
 

Scott, et. al

To make a really long story short here is what fixed PAT running on the NW image:
1.  Added a line to the /etc/ax25/axports file in the format:  wl2k KD7UM 1200 255 7 Winlink
2.  Did a sudo kissattach /tmp/kisstnc wl2k

It all worked.  Now two things for me to do:  create a script when starting PAT to do the kissattach and then the pat http command.
 

Having said all this, and given my Newbie status, I am going to investigate patlink-unix knowing now that this is the supported product.

Again, thank you and all the moderators and contributors for your time.

Re: PAT with DRAWS on VHF

Dave Christensen
 

Basil, et.al

All the tests you mentioned above were all working normally from the image installation.  Thank you again for detailing these, I have save this post for future checkouts.

To make a really long story short here is what fixed PAT running on the NW image:
1.  Added a line to the /etc/ax25/axports file in the format:  wl2k KD7UM 1200 255 7 Winlink
2.  Did a sudo kissattach /tmp/kisstnc wl2k

It all worked.  Now two things for me to do:  create a script when starting PAT to do the kissattach and then the pat http command.

This help came from Scott:
"I believe this is the video that I used to get setup for PAT over ax25:
 
 
-Scott,  K4KDR"

Having said all this, and given my Newbie status, I am going to investigate patlink-unix knowing now that this is the supported product.

Again, thank you and all the moderators and contributors for your time.

 

Re: PAT with DRAWS on VHF

Basil Gunn
 

I can not find the PAT CONFIGURE setup for ax25 VHF ports.
Because I don't support PAT. I support paclink-unix.

I had ax25
started and when I attempted a packet connection the error message
said that a ax25 port was not found.
Without showing me (cutting & pasting into post or email) the console
output of the error message I can't really comment.

Verify that ax.25 is running properly by running:
ax25-status
and
ax25-status -d

It would be helpful if you could post the console outputs of the above
commands as well.

Read this:
https://github.com/nwdigitalradio/n7nix/blob/master/docs/VERIFY_CONFIG.md#testing-ax25

What do I need to change in the
config.json file to create a VHF port on PAT? There are lots of videos
and post for ARDOP configuration but these won't help.

Re: PAT with DRAWS on VHF

K4KDR
 

Hi Dave!

I believe this is the video that I used to get setup for PAT over ax25:


-Scott,  K4KDR

========================


On Sat, Nov 16, 2019 at 12:47 PM Dave Christensen <dkc2030@...> wrote:
I can not find the PAT CONFIGURE setup for ax25 VHF ports.  I had ax25 started and when I attempted a packet connection the error message said that a ax25 port was not found.  What do I need to change in the config.json file to create a VHF port on PAT?  There are lots of videos and post for ARDOP configuration but these won't help.

Thanks in advance...

Dave - KD7UM

PAT with DRAWS on VHF

Dave Christensen
 

I can not find the PAT CONFIGURE setup for ax25 VHF ports.  I had ax25 started and when I attempted a packet connection the error message said that a ax25 port was not found.  What do I need to change in the config.json file to create a VHF port on PAT?  There are lots of videos and post for ARDOP configuration but these won't help.

Thanks in advance...

Dave - KD7UM

Re: Stream Audio Using VNC Command Line to Local Network #audio

Basil Gunn
 

Where in the command that you gave is the syntax for the USB device you
are using? dsnoop:1 ?

If I use cvlc --longhelp it lists alsa audio devices so I'm guessing you
would replace dsnoop:1 with dsnoop:CARD=udrc

cvlc --longhelp | grep -i alsa-audio-device
VLC media player 3.0.7 Vetinari (revision 3.0.7-0-g86cee31099)
--alsa-audio-device {null,default:CARD=ALSA,sysdefault:CARD=ALSA,dmix:CARD=ALSA,DEV=0,dmix:CARD=ALSA,DEV=1,dsnoop:CARD=ALSA,DEV=0,dsnoop:CARD=ALSA,DEV=1,hw:CARD=ALSA,DEV=0,hw:CARD=ALSA,DEV=1,plughw:CARD=ALSA,DEV=0,plughw:CARD=ALSA,DEV=1,default:CARD=udrc,sysdefault:CARD=udrc,dmix:CARD=udrc,DEV=0,dsnoop:CARD=udrc,DEV=0,hw:CARD=udrc,DEV=0,plughw:CARD=udrc,DEV=0,default}

/Basil

Anthony Sutera <tsutera@...> writes:

I am using my Draws Hat mainly for WSJT-X. I have a quick question: I
would like to stream audio to my local network. On my other setups
(Raspberry Pi3) using a signal link USB audio card, I succesfully use
this command:
cvlc -vvv alsa://dsnoop:1 --sout '#transcode{acodec=mp3,ab=64,channels=1}:standard{access=http,dst=192.168.165.126/out.mp3}'

to stream audio out to my local network. Can someone let me know the
correct audio device to list in the command line using the Draws Hat
sound card? Thank you! Tony Sutera KF7VLT

Boot-strap [was Re: [draws and udrc] Download Issues]

Stuart Longland VK4MSL
 

On 3/11/19 3:57 pm, Basil Gunn wrote:
Now that standard Raspbian supports the UDRC/DRAWS, I think things
should improve since NWDR's servers only have to carry a small handful
of packages and not a whopping great big SD card image.
If you want a whopping great big SD card image then use the "W3DJS
Raspberry Pi Ham Radio Image v2.0". It's 17GB and has a lot stuff.
https://groups.io/g/RaspberryPi-4-HamRadio/topic/w3djs_raspberry_pi_ham_radio/39671852?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,39671852
Note that they solved their slow download problem by using bitTorrent.

Our image is much smaller @ 2GB. List of NWDR Installed Programs:
https://github.com/nwdigitalradio/n7nix/blob/master/docs/IMAGE_README.md
Heh, I guess it's all relative. :-)

I'm used to a minimal image that basically just gets the machine booted
with all the hardware usable.

I suppose in UDRC/DRAWS terms, that'd be the necessary drivers loaded
and some scripts configured that at least set sane mixer levels. To
that, you add whatever packet or digital mode software, desktop
environments, etc.

Raspbian Lite weighs in at around 2GB uncompressed. Images I've made¹
for TS-7670 industrial computers (basically the result of `debootstrap`)
would basically install about 200-300MB worth of data on the root fs.

I recognise the standard NWDR image is basically aiming to be a complete
radio station out-of-the-box, so somewhat different rationale there.

Coding up a boot-strap script which can be run on stock Raspbian images
to set everything up would not be a difficult job.
I use a (unsupported) script to build and compress the published image. There is even
some documentation on how to run it. Search for "how the NWDR images are
created" in the markdown files in the docs directory.

The script runs for about 5 to 6 hours, IF there are no problems. It
usually takes 1 1/2 to 2 days to verify the image. I would rather do
other things than spin up boot images so looking forward to seeing your
boot-strap script.
Right, one thing I've observed is the Raspberry Pi 3, as powerful as it
is, isn't famous for its ability as a compiler work horse, mine at least
gripes about temperature. Also power supply fluctuations if I use the
standard Raspberry Pi PSU; the one on the UDRC is much better. However,
this doesn't get around other constraints on the Pi.

So my thinking on this is to split the problem up:

1. make a set of scripts that will generate a build environment that
will run on a conventional x86-64 Linux host and produce Debian packages
that will be installable on the Raspberry Pi

2. build each of the packages to be installed on a Pi+UDRC/DRAWS as a
separate Debian package and arrange these into an APT repository

3. create a script which adds the aforementioned APT repository, asks
some questions of the user as to what their intended use case is, then
installs package sets which achieve those aims.
https://wiki.debian.org/tasksel might be a way to achieve this. This
script can also do some last-minute set-up, but should not need to do
any heavy compilation.

Step (1) I've more-or-less already managed. Docker make available
standard Debian images for ARMv7 platforms, and under Linux, one can
combine QEMU user emulation and binfmt-misc to allow execution of ARMHF
binaries on an x86-64 host.

You need a statically linked version of `qemu-arm`; on Debian
derivatives, `apt-get install -y qemu-user-static` will have you sorted.
The other puzzle piece is `binfmt-support`; which can be installed with
`apt-get install -y binfmt-support`.

On my Gentoo host, I was able to get `qemu-arm` by compiling the
app-emulation/qemu package with USE=static and QEMU_USER_TARGETS=arm.
(Actually, I think I might've either nicked Debian's binary or built it
myself. I can't remember now. I have a binary in /opt/qemu/usr/bin.)

`binfmt-support` was found here:
https://github.com/qemu/qemu/blob/master/scripts/qemu-binfmt-conf.sh

The attached script was then able to create a Docker environment for
building the Raspberry Pi packages:

$ DEBIAN_MAIN_MIRROR=http://mirror.internode.on.net/pub/debian \
QEMU_BIN=/opt/qemu-static/usr/bin/qemu-arm-static \
sh mkbuildenv.sh

That'll create a docker image (nwdr/draws-buildimg) which we can use to
compile what we need. For example, building direwolf:

$ mkdir /tmp/work
$ docker run -v /tmp/work:/tmp/work --rm -ti nwdr/draws-buildimg bash
root@c7f1747ae8eb:/# cd /tmp/work
root@c7f1747ae8eb:/tmp/work# apt-get build-dep -y direwolf
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
dh-systemd libbluetooth3 libdbus-1-3 libgps-dev libgps23 pkg-config

root@c7f1747ae8eb:/tmp/work# apt-get source -y direwolf
Reading package lists... Done

root@c7f1747ae8eb:/tmp/work# ls
direwolf-1.4+dfsg direwolf_1.4+dfsg-1.debian.tar.xz
direwolf_1.4+dfsg-1.dsc direwolf_1.4+dfsg.orig.tar.gz
root@c7f1747ae8eb:/tmp/work# wget -O direwolf_1.5.orig.tar.gz
https://github.com/wb2osz/direwolf/archive/1.5.tar.gz
--2019-11-15 10:43:18--
https://github.com/wb2osz/direwolf/archive/1.5.tar.gz
Resolving github.com (github.com)... 13.236.229.21
Connecting to github.com (github.com)|13.236.229.21|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/wb2osz/direwolf/tar.gz/1.5 [following]
--2019-11-15 10:43:19--
https://codeload.github.com/wb2osz/direwolf/tar.gz/1.5
Resolving codeload.github.com (codeload.github.com)... 52.63.100.255
Connecting to codeload.github.com
(codeload.github.com)|52.63.100.255|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: 'direwolf_1.5.orig.tar.gz'

2019-11-15 10:43:33 (1.29 MB/s) - 'direwolf_1.5.orig.tar.gz' saved
[17996557]

root@c7f1747ae8eb:/tmp/work# tar -xzvf direwolf_1.5.orig.tar.gz
direwolf-1.5/
direwolf-1.5/.gitattributes

direwolf-1.5/xmit.h
root@c7f1747ae8eb:/tmp/work# cp -a direwolf-1.4+dfsg/debian direwolf-1.5
root@c7f1747ae8eb:/tmp/work# cd direwolf-1.5
root@c7f1747ae8eb:/tmp/work/direwolf-1.5# rm -fr debian/patches
-- at this point I should update debian/changelog too ! --
root@c7f1747ae8eb:/tmp/work/direwolf-1.5# dpkg-buildpackage -us -uc -b
dpkg-buildpackage: info: source package direwolf
dpkg-buildpackage: info: source version 1.4+dfsg-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Iain R. Learmonth
<irl@...>
dpkg-buildpackage: info: host architecture armhf
dpkg-source --before-build .
debian/rules clean
dh clean --with=systemd
debian/rules override_dh_auto_clean
make[1]: Entering directory '/tmp/work/direwolf-1.5'
make -f Makefile.linux clean
make[2]: Entering directory '/tmp/work/direwolf-1.5'
rm -f direwolf decode_aprs text2tt tt2text ll2utm utm2ll aclients atest
log2gpx gen_packets ttcalc kissutil cm108 gen_fff tune.h
fsk_fast_filter.h *.o *.a direwolf.desktop
make[2]: Leaving directory '/tmp/work/direwolf-1.5'

make[1]: Leaving directory '/tmp/work/direwolf-1.5'
dh_systemd_start
dh_perl
dh_link
dh_strip_nondeterminism
dh_compress
debian/rules override_dh_fixperms-arch
make[1]: Entering directory '/tmp/work/direwolf-1.5'
dh_fixperms
chmod 644 debian/direwolf/usr/share/direwolf/dw-icon.png
make[1]: Leaving directory '/tmp/work/direwolf-1.5'
dh_missing
dh_strip
dh_makeshlibs
dh_shlibdeps
dh_installdeb
dh_gencontrol
dh_md5sums
dh_builddeb
dpkg-deb: building package 'direwolf-dbgsym' in
'../direwolf-dbgsym_1.4+dfsg-1_armhf.deb'.
dpkg-deb: building package 'direwolf' in '../direwolf_1.4+dfsg-1_armhf.deb'.
dpkg-genbuildinfo --build=binary
dpkg-genchanges --build=binary >../direwolf_1.4+dfsg-1_armhf.changes
dpkg-genchanges: info: binary-only upload (no source code included)
dpkg-source --after-build .
dpkg-source: info: unapplying fix_documentation_path.patch
dpkg-buildpackage: info: binary-only upload (no source included)
root@c7f1747ae8eb:/tmp/work/direwolf-1.5# chown -R 1000:1000 /tmp/work
root@c7f1747ae8eb:/tmp/work/direwolf-1.5# exit
$ ls -l /tmp/work/
total 19828
drwxr-xr-x 10 stuartl stuartl 8192 Nov 15 20:41 direwolf-1.4+dfsg/
-rw-r--r-- 1 stuartl stuartl 4570 Nov 15 21:03
direwolf_1.4+dfsg-1_armhf.buildinfo
-rw-r--r-- 1 stuartl stuartl 2143 Nov 15 21:04
direwolf_1.4+dfsg-1_armhf.changes
-rw-r--r-- 1 stuartl stuartl 336804 Nov 15 21:03
direwolf_1.4+dfsg-1_armhf.deb
-rw-r--r-- 1 stuartl stuartl 8732 Sep 15 2017
direwolf_1.4+dfsg-1.debian.tar.xz
-rw-r--r-- 1 stuartl stuartl 1743 Sep 15 2017 direwolf_1.4+dfsg-1.dsc
-rw-r--r-- 1 stuartl stuartl 801382 Sep 15 2017
direwolf_1.4+dfsg.orig.tar.gz
drwxrwxr-x 9 stuartl stuartl 8192 Nov 15 21:04 direwolf-1.5/
-rw-r--r-- 1 stuartl stuartl 17996557 Nov 15 20:43 direwolf_1.5.orig.tar.gz
-rw-r--r-- 1 stuartl stuartl 1108088 Nov 15 21:03
direwolf-dbgsym_1.4+dfsg-1_armhf.deb

The test cases took a little while but the nice thing about this is you
can have several packages building in parallel on a modern system.

There's a few rough edges, but I think that could be worked around to
build the packages more-or-less autonomously… maybe via some CI system
like Jenkins, Atlassian Bamboo or similar… and the resulting binaries
uploaded to a repository.

That would reduce the amount of work needed at the actual boot-strap end
quite a bit.

Regards,
--
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
...it's backed up on a tape somewhere.

1. https://bne.vrt.com.au/technologicsys/ -- this is armel rather than
armhf, but the same principles apply

Stream Audio Using VNC Command Line to Local Network #audio

Anthony Sutera
 

I am using my Draws Hat mainly for WSJT-X.  I have a quick question: I would like to stream audio to my local network.  On my other setups (Raspberry Pi3) using a signal link USB audio card, I succesfully use this command: cvlc -vvv alsa://dsnoop:1 --sout '#transcode{acodec=mp3,ab=64,channels=1}:standard{access=http,dst=192.168.165.126/out.mp3}' to stream audio out to my local network.  Can someone let me know the correct audio device to list in the command line using the Draws Hat sound card?  Thank you! Tony Sutera KF7VLT
 

Re: NWDR14 image release announcement #beta #support

Basil Gunn
 

One thing maybe to note would be the inclusion of
a note that the default editor for the V14 image is JED.
Did not know that. Usually the first time you edit one of the system
files like a crontab entry you get presented with a menu of all the
editor choices.

I have never
seen this editor before (Newbie status) and could not save the image
when I was installing PAT. I changed it with the sudo
update-alternatives --config editor command to nano and then I was
back in familiar territory, although knowing it is JED I can deal with
that also now.
I don't mess with any default system settings like default editor. This
setting would be the same as a vanilla Raspbian image.

What I want to get to is one DRAWS port for VHF packet and the second
for HF apps (understanding that ax25 will have to be stopped to switch
between them (I think).
You will not have to stop AX.25 as long as you only bind to one of the
ports. See split-channels README.md here:
https://github.com/nwdigitalradio/split-channels

I will probably order a second draws for a "Go
Kit" when the cases get into the distribution channel. This one will
be a Pi4 based system. I wish I could help more but my skills in this
area only allow to comment how I can break things..

Thanks again to the team. I have known John Hayes for over 30 years
and he is a good friend.

Re: NWDR14 image release announcement #beta #support

Dave Christensen
 

Thanks for the reply Basil.  I am a real Newbie to DRAWS and Linux but I muddled through the install until I went to setup ARDOP from the web and then later discovered there was a script to do that.  So I am starting over again to do it using the supplied scripts.  Under the getting started web page = "https://nw-digital-radio.groups.io/g/udrc/wiki/DRAWS%3A-Image-getting-started"  there are 5 steps listed and the first three steps have similar and different instructions for creating the SD card and running the configure scripts.  I suspect this is from improving the images since January.  Being a IT person I understand that the Docs come last but I think they should be updated for the current images as they improve and simplify things.  One thing maybe to note would be the inclusion of a note that the default editor for the V14 image is JED.  I have never seen this editor before (Newbie status) and could not save the image when I was installing PAT.  I changed it with the sudo update-alternatives --config editor command to nano and then I was back in familiar territory, although knowing it is JED I can deal with that also now.

What I want to get to is one DRAWS port for VHF packet and the second for HF apps (understanding that ax25 will have to be stopped to switch between them (I think).  I will probably order a second draws for a "Go Kit" when the cases get into the distribution channel.  This one will be a Pi4 based system.  I wish I could help more but my skills in this area only allow to comment how I can break things..

Thanks again to the team.  I have known John Hayes for over 30 years and he is a good friend.

Moderation?

August Johnson
 
Edited

I see that I'm now subject to moderation on my posts. Why is this? Is it because I'm again asking where my early adopter aluminum case is?

August KG7BZ

Re: Kenwood 707, 2m #draws

Douglas
 

Thank you.  draws manager is setup and I put the settings in for the 500 mv setting for the kenwood tm 707.  I am still having the issue with input device and rig control errors.