Date   

Re: Port 8001

 

Confirmed that all mods except the wifi/hotspot switching work with WLK-Express on both mdin6 ports. The last mod, the wifi/hotspot switch, apparently breaks udr0 but not udr1 with respect to WLK-Express.

This is for posterity and closure on my input to the topic. Mucking around with hostap, dnsmasq and iptables is way above my level of ignorance.


Re: Port 8001

 

As advertised, WLK-Express sends and receives mail through both mdin6 ports when I install a fresh image.

Not sure what I did to break the udr0 port.

Things I modified:

Used Mr. McGrane's wpa_supplicant.conf to initially connect via wifi.

Added private digipeating to udr0 in direwolf.conf, later turned this off and rebooted, port still broken wrt WLK-Express.

Added beaconing using btest.sh and cron.

Added a shutdown mom-switch using dtoverlay.

Added wifi/hotspot switching partly from https://www.raspberrypi.org/documentation/configuration/wireless/access-point.md and partly from https://nw-digital-radio.groups.io/g/main/message/2294 . I had to hybridize these tutorials to get this to work.  Maybe this broke Winlink through port udr0.

Beats me but I'm moving on to paclink unix.


Re: Port 8001

 

Thanks. Exactly what I was after. I suspected something was off. Not asking for a troubleshoot. I’ll try a fresh install if I pursue further.


Re: Port 8001

Basil Gunn
 

I don't have any experience with this setup but I can tell you how it
should work, which doesn't match what you are reporting.

AGWPE defaults to Direwolf port 0 (left connector on the draws card). I
can confirm this with Xastir. I don't know of any way to specify the
second (right connector) with AGWPE. When I google this it appears that
there might be a way to support dual ports with AGWpe but all the sites
are stale & do not load.

Looking at the Direwolf documentation I assume the KISSPORT (KISS over
TCP) works in a similar way, that is it defaults to port 0. From your
configuration and looking at Winlink Express it appears that you can
select the second (right connector) port by specifying Packet TNC Type:
KISS Port 2 rather than Packet TNC Type: KISS AND Serial Port TCP. Make
sure the TCP port used is the same as the one specified in
/etc/direwolf.conf.

I just confirmed by running Winlink Express that I can send & receive
Winlink mail using the left & right mDin6 connectors and configuring
Winlink Express with Packet TNC Type KISS & KISS port 2.

On the linux side the AX.25 ports are configured using the Direwolf
pseudo terminal interface and mkiss to attach to two devices that
produces 2 AX.25 network socket interfaces ax0 & ax1. These correspond
to the left & right connectors.

Short answer I don't know why you are seeing what you are seeing but
Winlink Express can be configured to use the DRAWS left & right
connectors using KISS over TCP.

/Basil



David Lowry <huskyrunnr@msn.com> writes:

Just curious about Winlink Express. I wanted to try that before I dive
into paclink-unix. I set it up using TCP/8001 as described in the
Direwolf User Guide. I can only send and receive email if I use the
Right mini-DIN port on DRAWS and specify "KISS Port 2" in WLK-Express
session setup. Is this expected behavior? Is KISS port 8001 bound to
Right mini-DIN only? If so, where is this done?

If I try Left mini-DIN and choose "KISS" in WLK-Express, I can connect to a gateway but no emails get transferred either direction.

TIA, David


Re: direwolf frame size #ax25 #direwolf

John Spoonhower
 

Basil, and others,
I occasionally see these or similar errors (premature disconnects) at my Winlink RMS, NX2I-10. Other users reported the problem but without a lot of additional information. I have been experimenting with different file sizes as attachments. The problem for me occurs when file sizes are greater than 5K and typically in the 9-12K range. My test setup uses a Winlink Express client (current rev.) on a PC (Win 7) with Direwolf 1.5. The server is a Raspberry Pi3 with a UDRC-II and Direwolf 1.4. The Pi has an earlier version of compass as the OS distribution. Any guidance regarding what/where to look would be appreciated. 
73,
John, NX2I


Port 8001

 

Just curious about Winlink Express. I wanted to try that before I dive into paclink-unix. I set it up using TCP/8001 as described in the Direwolf User Guide. I can only send and receive email if I use the Right mini-DIN port on DRAWS and specify "KISS Port 2" in WLK-Express session setup. Is this expected behavior? Is KISS port 8001 bound to Right mini-DIN only? If so, where is this done?

If I try Left mini-DIN and choose "KISS" in WLK-Express, I can connect to a gateway but no emails get transferred either direction.

TIA, David


Re: YAAC beacons #configuration

Tim Huffaker
 

It’s now fixed.  


DRAWS Video #4

Steve McGrane <temporarilyoffline@...>
 

Its been a while, but now that my radio is back from factory service, I got the kick in the pants I needed to make another video.

This video is all about how to make a bootable backup of your SD card in case mayhem strikes.

Take a look and let me know what you think by clicking like or dislike:


Next up will be a JS8 Video, Stay Tuned!

- Steve, KM9G


Re: gpsd, amixer, sensor, and other issues

Tom Velvin
 

Julie,

 

Thanks for all your testing and hard work.  I’ve been reading your email stream and I’m glad to know you reached the same conclusion I did.  I’m sure you reached a level of frustration before Basil agreed the board might be bad.

 

I’m in Seaside till tomorrow but we should be home by late afternoon.  I can email you when we get home and work out how to get the board so I can send it back to NW Digital.

 

Tom

 

From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On Behalf Of Julie McGrew via Groups.Io
Sent: Friday, June 7, 2019 12:53 PM
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] gpsd, amixer, sensor, and other issues

 

OK .. will do the return as requested.

Thank you Basil and Bryan for the excellent service and support!  :)

73,
julie
ac0wn


Re: gpsd, amixer, sensor, and other issues

Julie McGrew
 

OK .. will do the return as requested.

Thank you Basil and Bryan for the excellent service and support!  :)

73,
julie
ac0wn


Re: gpsd, amixer, sensor, and other issues

 

Have him return it with the GPS Antenna and the SDCARD so I can duplicate it here.

Thanks Julie!
Bryan K7UDR

On Jun 7, 2019, at 12:48 PM, Julie McGrew via Groups.Io <juliemcgrew@...> wrote:

So ... should I have him return the draws card, or do you wish me to do further testing?

Also, if he returns the item do you wish us to include the gps antenna in the return?

Many thanks for all your kind assistance.

73,
julie
ac0wn


Re: gpsd, amixer, sensor, and other issues

Julie McGrew
 

So ... should I have him return the draws card, or do you wish me to do further testing?

Also, if he returns the item do you wish us to include the gps antenna in the return?

Many thanks for all your kind assistance.

73,
julie
ac0wn


Re: gpsd, amixer, sensor, and other issues

 

Results from my reference system:

pi@K7UDR-FHR:~ $ i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         

Isn’t an I2C HW issue. 3 devices respond at the correct addresses.

Bryan K7UDR


Re: gpsd, amixer, sensor, and other issues

Julie McGrew
 

Hi Basil,

pi@K7TMV-draws:~ $ i2cdetect -y 1
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         
pi@K7TMV-draws:~ $ 

73,
julie
ac0wn


Re: gpsd, amixer, sensor, and other issues

Basil Gunn
 

Julie,

Could you please run this command:

i2cdetect -y 1

Should have devices at addresses: 0x18, 0x48 & 0x50
Thanks,
/Basil

Bryan Hoyer <bhhoyer@gmail.com> writes:

Hi Julie,

ADC, CODEC and Serial (GPS) rely on I2C, which is tested in manufacture. I’m with Basil, it sounds defective.

Please return to:

NW Digital Radio
RMA <order number>
245 Highlands Drive
Friday Harbor WA 98250

Thanks,
Bryan K7UDR

On Jun 7, 2019, at 8:47 AM, Basil Gunn <basil@pacabunga.com> wrote:


Hi Julie,

I'm reasonably sure that the draws board you are helping with is
defective. I have an email out to the other NW Digital people to
confirm my suspicion noting these symptoms:

* The rPi is powered via the draws card which is reading 14.12 vdc
* Pin 2 on the gpio is reading 5.047 vdc
* Replaced the rpi unit with a new one - no change.
* Replaced the SDCard with a new 32 GB card with fresh Beta 13 build - twice - no change
* aplay -l enumerates the udrc sound device ok
* amixer gives an error message I have never seen before
* gps, sensors & sound codec appear to be not responding

Thanks for your patience.
/Basil

Julie McGrew via Groups.Io <juliemcgrew=mac.com@groups.io> writes:

Good morning Basil,

The rPi is powered via the draws card which is reading 14.12 vdc
Pin 2 on the gpio is reading 5.047 vdc

pi@K7TMV-draws:~ $ amixer -c udrc get "LO Driver Gain"
amixer: Mixer hw:1 load error: Remote I/O error

Many thanks,
julie
ac0wn



Re: gpsd, amixer, sensor, and other issues

 

Hi Julie,

ADC, CODEC and Serial (GPS) rely on I2C, which is tested in manufacture. I’m with Basil, it sounds defective.

Please return to:

NW Digital Radio
RMA <order number>
245 Highlands Drive
Friday Harbor WA 98250

Thanks,
Bryan K7UDR

On Jun 7, 2019, at 8:47 AM, Basil Gunn <basil@pacabunga.com> wrote:


Hi Julie,

I'm reasonably sure that the draws board you are helping with is
defective. I have an email out to the other NW Digital people to
confirm my suspicion noting these symptoms:

* The rPi is powered via the draws card which is reading 14.12 vdc
* Pin 2 on the gpio is reading 5.047 vdc
* Replaced the rpi unit with a new one - no change.
* Replaced the SDCard with a new 32 GB card with fresh Beta 13 build - twice - no change
* aplay -l enumerates the udrc sound device ok
* amixer gives an error message I have never seen before
* gps, sensors & sound codec appear to be not responding

Thanks for your patience.
/Basil

Julie McGrew via Groups.Io <juliemcgrew=mac.com@groups.io> writes:

Good morning Basil,

The rPi is powered via the draws card which is reading 14.12 vdc
Pin 2 on the gpio is reading 5.047 vdc

pi@K7TMV-draws:~ $ amixer -c udrc get "LO Driver Gain"
amixer: Mixer hw:1 load error: Remote I/O error

Many thanks,
julie
ac0wn


Re: gpsd, amixer, sensor, and other issues

Basil Gunn
 

Hi Julie,

I'm reasonably sure that the draws board you are helping with is
defective. I have an email out to the other NW Digital people to
confirm my suspicion noting these symptoms:

* The rPi is powered via the draws card which is reading 14.12 vdc
* Pin 2 on the gpio is reading 5.047 vdc
* Replaced the rpi unit with a new one - no change.
* Replaced the SDCard with a new 32 GB card with fresh Beta 13 build - twice - no change
* aplay -l enumerates the udrc sound device ok
* amixer gives an error message I have never seen before
* gps, sensors & sound codec appear to be not responding

Thanks for your patience.
/Basil

Julie McGrew via Groups.Io <juliemcgrew=mac.com@groups.io> writes:

Good morning Basil,

The rPi is powered via the draws card which is reading 14.12 vdc
Pin 2 on the gpio is reading 5.047 vdc

pi@K7TMV-draws:~ $ amixer -c udrc get "LO Driver Gain"
amixer: Mixer hw:1 load error: Remote I/O error

Many thanks,
julie
ac0wn


Re: gpsd, amixer, sensor, and other issues

Julie McGrew
 

Good morning Basil,

The rPi is powered via the draws card which is reading 14.12 vdc
Pin 2 on the gpio is reading 5.047 vdc

pi@K7TMV-draws:~ $ amixer -c udrc get "LO Driver Gain"
amixer: Mixer hw:1 load error: Remote I/O error

Many thanks,
julie
ac0wn


Re: gpsd, amixer, sensor, and other issues

Basil Gunn
 

Thanks for the console output.
The driver is loading fine. The software appears to be working but gps,
sensor & audio device are not.

How are you powering the RPi/Draws board?
I am assuming you are using the RPi 5V USB connector.
Could you measure the voltage on the 5V supply.

Also could you cut & paste the output to this command:

amixer -c udrc get "LO Driver Gain"

Thanks,
/Basil


Julie McGrew via Groups.Io <juliemcgrew=mac.com@groups.io> writes:

hmmm ... It appears reply by email is slow ... I'll answer here and apologize to all if there is a dup of this message.

Thank you for the quick response!

pi@K7TMV-draws:~ $ 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 ALSA [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: udrc [udrc], device 0: Universal Digital Radio Controller tlv320aic32x4-hifi-0 []
Subdevices: 0/1
Subdevice #0: subdevice #0
pi@K7TMV-draws:~ $

pi@K7TMV-draws:~ $ showudrc.sh
==== Sound Card ====
udrc card number line: card 1: udrc [udrc], device 0: Universal Digital Radio Controller tlv320aic32x4-hifi-0 []
udrc is sound card #1
==== ALSA Controls for Radio Tansmit ====
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
LO Driver Gain L: R:
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
PCM L: R:
amixer: Mixer hw:1 load error: Remote I/O error
==== ALSA Controls for Radio Receive ====
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
ADC Level L: R:
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
amixer: Mixer hw:1 load error: Remote I/O error
IN1 L:[] R:[]
IN2 L:[] R:[]
==== Pi Ver ====
Pi 3 Model B+ Mfg by Sony UK
Has WiFi
==== udrc Ver ====
Found a DRAWS

HAT ID EEPROM
Name: hat
Product: Digital Radio Amateur Work Station
Product ID: 0x0004
Product ver: 0x0204
UUID: 3c64ff9f-0cdd-403e-bdac-821b040e8693
Vendor: NW Digital Radio

==== sys Ver ====
----- image version
2019 05 07 12:46:37 PDT: SD image version: beta13
----- /proc/version
Linux version 4.14.98-v7+ (dom@dom-XPS-13-9370) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1200 SMP Tue Feb 12 20:27:48 GMT 2019

----- /etc/*version: 9.9

----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
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 9.9 (stretch)
Release: 9.9
Codename: stretch

---- systemd
Static hostname: K7TMV-draws
Icon name: computer
Machine ID: 2f51e140e908474eaa86ae805f03a6d8
Boot ID: 0ed5a4bbb1e640178dd8793f69b624f2
Operating System: Raspbian GNU/Linux 9 (stretch)
Kernel: Linux 4.14.98-v7+
Architecture: arm

---- modules
tlv320aic32x4_i2c 16384 1
tlv320aic32x4 32768 1 tlv320aic32x4_i2c
udrc 16384 2
snd_soc_core 188416 3 tlv320aic32x4,snd_soc_bcm2835_i2s,udrc
snd_pcm 98304 7 snd_pcm_dmaengine,tlv320aic32x4,snd_soc_bcm2835_i2s,snd_bcm2835,snd_soc_core

-rw-r--r-- 1 root 6388 Apr 16 12:42 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4-i2c.ko
-rw-r--r-- 1 root 39084 Apr 16 12:42 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4.ko
-rw-r--r-- 1 root 6408 Apr 16 12:42 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4-spi.ko
-rw-r--r-- 1 root 8332 Apr 16 12:42 /lib/modules/4.14.98-v7+/updates/dkms/udrc.ko

---- kernel
||/ Name Version Architecture Description
+++-==================-============-============-=================================
ii raspberrypi-kernel 1.20190401-1 armhf Raspberry Pi bootloader
ii udrc-dkms 1.0.5 armhf DKMS source for the UDRC driver

Directory: /proc/device-tree/soc/i2c@7e804000/tlv320aic32x4@18 exists and status is okay

---- syslog

---- dmesg
[ 3.289751] udrc: loading out-of-tree module taints kernel.
[ 3.290477] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
[ 3.290491] snd-udrc soc:sound: snd_soc_register_card() failed: -517
[ 3.398819] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
[ 3.398825] snd-udrc soc:sound: snd_soc_register_card() failed: -517
[ 3.411000] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
[ 3.411011] snd-udrc soc:sound: snd_soc_register_card() failed: -517
[ 3.457739] snd-udrc soc:sound: tlv320aic32x4-hifi <-> 3f203000.i2s mapping ok

---- compass
Compass preference file not found: /etc/apt/preferences.d/compass
---- compass apt sources list file
deb [arch=armhf,amd64] http://archive.compasslinux.org/ cedar main
---- compass package files
-rw-r--r-- 1 root 2201 Dec 31 10:44 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_InRelease
-rw-r--r-- 1 root 17567 Jul 2 2018 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_main_binary-amd64_Packages
-rw-r--r-- 1 root 43316 Dec 31 10:44 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_main_binary-armhf_Packages

----- Dire Wolf DEVELOPMENT version 1.6 B (Feb 27 2019)

==== Filesystem ====
/dev/root 30G 4.9G 24G 18% /

==== boot config ====
# 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

force_turbo=1
dtoverlay=
dtoverlay=draws,alsaname=udrc
# Enable audio (loads snd_bcm2835)
dtparam=audio=on

---- gpsd
/usr/local/sbin/gpsd
gpsd: 3.18.1 (revision 3.18.1)
● gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2019-06-06 08:52:16 PDT; 7h ago
Main PID: 576 (gpsd)
CGroup: /system.slice/gpsd.service
└─576 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0

Jun 06 08:52:16 K7TMV-draws systemd[1]: Starting GPS (Global Positioning System) Daemon...
Jun 06 08:52:16 K7TMV-draws systemd[1]: Started GPS (Global Positioning System) Daemon.

---- chrony
crw------- 1 root root 243, 0 Jun 6 08:52 /dev/pps0
crw-rw---- 1 root dialout 242, 0 Jun 6 08:52 /dev/ttySC0
crw-rw---- 1 root dialout 242, 1 Jun 6 08:52 /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
^* 96-8-121-205-host.colocr> 3 10 377 509 +848us[ +916us] +/- 23ms
^+ server.nanoslim.org 3 10 377 334 -2205us[-2205us] +/- 29ms
^+ jitter.tickadj.net 2 10 377 85 +998us[ +998us] +/- 47ms
^- eterna.binary.net 2 10 377 332 +669us[ +669us] +/- 75ms
-- chrony tracking
Reference ID : 600879CD (96-8-121-205-host.colocrossing.com)
Stratum : 4
Ref time (UTC) : Thu Jun 06 23:36:54 2019
System time : 0.000421532 seconds fast of NTP time
Last offset : +0.000067734 seconds
RMS offset : 0.000240083 seconds
Frequency : 0.727 ppm slow
Residual freq : +0.002 ppm
Skew : 0.014 ppm
Root delay : 0.025503 seconds
Root dispersion : 0.008533 seconds
Update interval : 1031.6 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
96-8-121-205-host.colocr> 44 19 460m +0.000 0.017 +1767us 296us
server.nanoslim.org 51 23 466m -0.006 0.014 -2658us 264us
jitter.tickadj.net 6 5 85m +0.111 0.322 +822us 168us
eterna.binary.net 13 9 207m +0.067 0.053 +1311us 146us

---- sensors
-rw-r--r-- 1 root root 171 Nov 11 2018 /etc/sensors.d/draws
ads1015-i2c-1-48
Adapter: bcm2835 I2C adapter
User ADC Differential: N/A
+12V: N/A
User ADC 1: N/A
User ADC 2: N/A

---- locale
Locale country codes consistent among WiFi cfg file, iw reg & X11: US
core_config.sh has been run 1 time(s)
pi@K7TMV-draws:~ $

Many thanks for your assistance, Basil. :)

73,
julie
ac0wn


Re: YAAC beacons #configuration

Tim Huffaker
 

Now with YAAC I can transmit on one draws port and receive on the other port. I’m not sure how to make both work on one port. 
Tim KM4ESU 

1781 - 1800 of 5335