1. udrc@nw-digital-radio.groups.io
   Date   
ARDOP or software similar to WinLink (HF mail) #winlink

wa9pyh@...
 

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
Re: Undulating transmit audio in HF programs #draws

Mitch Winkle
 
Edited

Over the air testing revealed that what I was seeing here is mirrored over 200 miles away, so it is not likely a local RFI issue on RX here.

Then, I hooked up an external high quality sound card via USB and an external radio interface which keys PTT by USB serial.  Clean audio out using FLDIGI.  Clean reception locally, and clean reception verified by the remote station.

Definitely an audio hardware issue or an audio config issue.
Re: [udrc] UDRC-II squelch on the Yaesu FT-897D → Resolved, DRAWS does *not* require this

Stuart Longland VK4MSL
 

On 20/8/19 9:35 pm, Stuart Longland VK4MSL wrote:
Do I need a pull-up on the SQL lines like I did for the UDRC-II in order
to have normal audio on the FT-857D/897D?
Well, I tried it at first with my FT-897D, got no audio, then tried
switching to an Icom IC-706MkIIG… still no joy.

I was using arecord/aplay and netcat for testing.

I have a Pi 3 with a UDRC-II board as well, which I had previously used
with the Icom set for packet radio, so *knew* it worked. This is a
completely separate computer, so I shut down the Pi I had the DRAWS on,
put it to one side, and plugged the UDRC-II equipped Pi, plugging it
into the same radio and power supply with the same cables.

Bingo… I had audio, badly distorted, but some tweaks in alsamixer, and I
had Triple M Brisbane's calling of the football coming through clear via
the UDRC-II. I swapped back to the other Pi with the DRAWS…

Comparing the mixer settings, the UDRC-II had the ADC Fine Gain Adjust
(ADCFGA) turned off, whereas the DRAWS had them turned on. Soon as I
turned those off, I got audio.

Swapping back to the FT-897D, it worked there too. No removal of SQL
pins or pull-ups necessary, I had audio from both the set directly, and
audio from my netbook. I didn't try watching the SQL pin to see if I
could detect squelch… that'll be another day.

So executive summary:
- There is no pull-up or modification necessary with the FT-897D, it
worked out-of-the-box with the supplied cables as-is.
- Initially I had no audio at all, this was due to ADCFGA being turned
on, audio came through when this was turned off.
--
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
...it's backed up on a tape somewhere.
Re: Undulating transmit audio in HF programs #draws

Mitch Winkle
 

  • Describe your problem and answer these questions:  as in prev message
  • Did you make your own cables? No, using cables provided with the DRAWS
  • Which mDin6 connector are you using?
    • Looking at the front of the connector left or right - LEFT
  • What program & program version are you running that gives the symptoms you described? FLDIGI 4.1.03 and JS8Call 1.01
  • What is the make & model number of your radio? Yaesu FT-450D
  • Include the console output of:
    • Complete console output of install by running script program before first configuration script -- Not possible obviously
    • Console output of showudrc.sh script 
      ==== 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 ====
LO Driver Gain  L:[-6.00dB]	R:[-6.00dB]
PCM	        L:[-21.50dB]	R:[-21.50dB]
DAC Playback PT	L:[PTM_P3]	R:[PTM_P3]
LO Playback CM	[Full Chip CM]
==== ALSA Controls for Radio Receive ====
ADC Level	L:[0.00dB]	R:[0.00dB]
IN1		L:[Off]		R:[Off]
IN2		L:[10 kOhm]	R:[Off]
==== 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: 0x0106
UUID:        a736ef4d-9221-4377-a880-245c4a8ac271
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
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 9.9 (stretch)
Release:	9.9
Codename:	stretch

---- systemd
   Static hostname: nnx3xa
         Icon name: computer
        Machine ID: 2f51e140e908474eaa86ae805f03a6d8
           Boot ID: 2ff7ca062c1c47949920c643a851afd2
  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  3
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 15:42 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4-i2c.ko
-rw-r--r-- 1 root 39084 Apr 16 15:42 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4.ko
-rw-r--r-- 1 root  6408 Apr 16 15:42 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4-spi.ko
-rw-r--r-- 1 root  8332 Apr 16 15: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
Aug 22 09:07:43 nnx3xa npm[476]: /usr/bin/amixer -c udrc sset 'IN2_L to Left Mixer Positive Resistor' '10 kOhm'
Aug 22 09:07:43 nnx3xa npm[476]: /usr/bin/amixer -c udrc sset 'IN1_L to Left Mixer Positive Resistor' 'Off'
Aug 22 09:07:43 nnx3xa npm[476]: /usr/bin/amixer -c udrc sset 'IN2_R to Right Mixer Positive Resistor' 'Off'
Aug 22 09:07:43 nnx3xa npm[476]: /usr/bin/amixer -c udrc sset 'IN1_R to Right Mixer Positive Resistor' 'Off'
Aug 22 09:07:44 nnx3xa npm[476]: /usr/bin/amixer -c udrc sset 'CM_R to Right Mixer Negative Resistor' '10 kOhm'
Aug 22 09:07:44 nnx3xa npm[476]: /usr/bin/amixer -c udrc sset 'CM_L to Left Mixer Negative Resistor' '10 kOhm'
Aug 22 09:07:44 nnx3xa npm[476]: /usr/bin/amixer -c udrc sset 'LO DAC' 'on,off'
Aug 22 09:07:44 nnx3xa npm[476]: /usr/bin/amixer -c udrc sset 'LOL Output Mixer L_DAC' 'on'
Aug 22 09:07:44 nnx3xa npm[476]: /usr/bin/amixer -c udrc sset 'LOR Output Mixer R_DAC' 'off'
Aug 22 09:08:00 nnx3xa npm[476]: /usr/bin/amixer -c udrc sset 'PCM' '84,77'
Aug 22 11:32:41 nnx3xa npm[5736]: /usr/bin/amixer -c udrc sset 'ADC Level' '36,24'
Aug 22 11:32:57 nnx3xa npm[5736]: /usr/bin/amixer -c udrc sset 'ADC Level' '29,24'
Aug 22 11:33:00 nnx3xa npm[5736]: /usr/bin/amixer -c udrc sset 'ADC Level' '24,24'
Aug 22 12:13:09 nnx3xa kernel: [    3.492157] udrc: loading out-of-tree module taints kernel.
Aug 22 12:13:09 nnx3xa kernel: [    3.492658] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 12:13:09 nnx3xa kernel: [    3.492666] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 12:13:09 nnx3xa kernel: [    3.720959] snd-udrc soc:sound: tlv320aic32x4-hifi <-> 3f203000.i2s mapping ok
Aug 22 12:53:19 nnx3xa kernel: [    3.475252] udrc: loading out-of-tree module taints kernel.
Aug 22 12:53:19 nnx3xa kernel: [    3.475791] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 12:53:19 nnx3xa kernel: [    3.475800] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 12:53:19 nnx3xa kernel: [    3.577013] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 12:53:19 nnx3xa kernel: [    3.577026] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 12:53:19 nnx3xa kernel: [    3.583771] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 12:53:19 nnx3xa kernel: [    3.583781] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 12:53:19 nnx3xa kernel: [    3.751659] snd-udrc soc:sound: tlv320aic32x4-hifi <-> 3f203000.i2s mapping ok
Aug 22 12:57:00 nnx3xa kernel: [    3.501006] udrc: loading out-of-tree module taints kernel.
Aug 22 12:57:00 nnx3xa kernel: [    3.501667] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 12:57:00 nnx3xa kernel: [    3.501679] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 12:57:00 nnx3xa kernel: [    3.577872] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 12:57:00 nnx3xa kernel: [    3.577884] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 12:57:00 nnx3xa kernel: [    3.584094] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 12:57:00 nnx3xa kernel: [    3.584101] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 12:57:00 nnx3xa kernel: [    3.630979] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 12:57:00 nnx3xa kernel: [    3.630990] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 12:57:00 nnx3xa kernel: [    3.731574] snd-udrc soc:sound: tlv320aic32x4-hifi <-> 3f203000.i2s mapping ok
Aug 22 14:41:56 nnx3xa kernel: [    3.474401] udrc: loading out-of-tree module taints kernel.
Aug 22 14:41:56 nnx3xa kernel: [    3.475023] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 14:41:56 nnx3xa kernel: [    3.475037] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 14:41:56 nnx3xa kernel: [    3.526005] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 14:41:56 nnx3xa kernel: [    3.526011] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 14:41:56 nnx3xa kernel: [    3.526164] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 14:41:56 nnx3xa kernel: [    3.526169] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 14:41:56 nnx3xa kernel: [    3.564341] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 14:41:56 nnx3xa kernel: [    3.564354] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 14:41:56 nnx3xa kernel: [    3.578165] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 14:41:56 nnx3xa kernel: [    3.578172] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 14:41:56 nnx3xa kernel: [    3.661365] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 14:41:56 nnx3xa kernel: [    3.661381] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 14:41:56 nnx3xa kernel: [    3.693406] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 14:41:56 nnx3xa kernel: [    3.693422] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 14:41:56 nnx3xa kernel: [    3.699740] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 14:41:56 nnx3xa kernel: [    3.699753] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 14:41:56 nnx3xa kernel: [    3.792692] snd-udrc soc:sound: tlv320aic32x4-hifi <-> 3f203000.i2s mapping ok
Aug 22 15:27:42 nnx3xa npm[485]: /usr/bin/amixer -c udrc sset 'PCM' '84,84'
Aug 22 15:27:55 nnx3xa npm[485]: /usr/bin/amixer -c udrc sset 'LO Driver Gain' '0,6'
Aug 22 15:28:15 nnx3xa npm[485]: /usr/bin/amixer -c udrc sset 'LO Driver Gain' '0,0'
Aug 22 16:01:55 nnx3xa kernel: [    3.417679] udrc: loading out-of-tree module taints kernel.
Aug 22 16:01:55 nnx3xa kernel: [    3.418183] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 16:01:55 nnx3xa kernel: [    3.418192] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 16:01:55 nnx3xa kernel: [    3.437041] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 16:01:55 nnx3xa kernel: [    3.437056] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 16:01:55 nnx3xa kernel: [    3.490992] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 16:01:55 nnx3xa kernel: [    3.491000] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 16:01:55 nnx3xa kernel: [    3.494978] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 16:01:55 nnx3xa kernel: [    3.494990] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 16:01:55 nnx3xa kernel: [    3.569672] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 16:01:55 nnx3xa kernel: [    3.569686] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 16:01:55 nnx3xa kernel: [    3.577078] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
Aug 22 16:01:55 nnx3xa kernel: [    3.577088] snd-udrc soc:sound: snd_soc_register_card() failed: -517
Aug 22 16:01:55 nnx3xa kernel: [    3.720785] snd-udrc soc:sound: tlv320aic32x4-hifi <-> 3f203000.i2s mapping ok

---- dmesg
[    3.417679] udrc: loading out-of-tree module taints kernel.
[    3.418183] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
[    3.418192] snd-udrc soc:sound: snd_soc_register_card() failed: -517
[    3.437041] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
[    3.437056] snd-udrc soc:sound: snd_soc_register_card() failed: -517
[    3.490992] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
[    3.491000] snd-udrc soc:sound: snd_soc_register_card() failed: -517
[    3.494978] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
[    3.494990] snd-udrc soc:sound: snd_soc_register_card() failed: -517
[    3.569672] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
[    3.569686] snd-udrc soc:sound: snd_soc_register_card() failed: -517
[    3.577078] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
[    3.577088] snd-udrc soc:sound: snd_soc_register_card() failed: -517
[    3.720785] 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  2018 /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  2018 /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        29G  5.7G   22G  21% /

==== 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-08-22 16:08:33 EDT; 1h 7min ago
  Process: 2287 ExecStart=/usr/local/sbin/gpsd $GPSD_OPTIONS $OPTIONS $DEVICES (code=exited, status=0/SUCCESS)
 Main PID: 2288 (gpsd)
   CGroup: /system.slice/gpsd.service
           └─2288 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0

Aug 22 16:08:33 nnx3xa systemd[1]: Starting GPS (Global Positioning System) Daemon...
Aug 22 16:08:33 nnx3xa systemd[1]: Started GPS (Global Positioning System) Daemon.

---- chrony
crw-rw---- 1 root root    243, 0 Aug 22 16:01 /dev/pps0
crw------- 1 root root    243, 1 Aug 22 16:08 /dev/pps1
crw-rw---- 1 root dialout 242, 0 Aug 22 16:08 /dev/ttySC0
crw-rw---- 1 root dialout 242, 1 Aug 22 16:01 /dev/ttySC1
-- chrony sources
210 Number of sources = 6
MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
#x GPS                           0   3   377     7   -193ms[ -193ms] +/-  102ms
#* PPS                           0   3   377     9   -228ns[ -272ns] +/- 1033ns
^- darwin.kenyonralph.com        2   9   367    57    -10ms[  -10ms] +/-  106ms
^- 2600:3c00::f03c:91ff:fe5>     2   9   377   449    -17ms[  -17ms] +/-  118ms
^- ntp3.junkemailfilter.com      2   9   377   186  +9922us[+9920us] +/-  122ms
^- time-d.bbnx.net               2   9   377   389    -11ms[  -11ms] +/-   68ms
-- chrony tracking
Reference ID    : 50505300 (PPS)
Stratum         : 1
Ref time (UTC)  : Thu Aug 22 21:15:47 2019
System time     : 0.000000034 seconds fast of NTP time
Last offset     : -0.000000045 seconds
RMS offset      : 0.000000257 seconds
Frequency       : 1.987 ppm fast
Residual freq   : -0.000 ppm
Skew            : 0.007 ppm
Root delay      : 0.000000 seconds
Root dispersion : 0.000010 seconds
Update interval : 8.0 seconds
Leap status     : Normal
-- chrony sourcestats
210 Number of sources = 6
Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
==============================================================================
GPS                         6   3    40    -53.388    886.198   -197ms  3892us
PPS                        33  19   255     -0.000      0.007     -0ns   882ns
darwin.kenyonralph.com     26  12   50m     -0.056      5.193    -13ms  5281us
2600:3c00::f03c:91ff:fe5>  25  14   57m     -0.165      1.245  -9091us  1571us
ntp3.junkemailfilter.com   28  15   68m     +3.281      4.329    +12ms  5432us
time-d.bbnx.net            29  14   66m     +0.232      1.511   +120us  2267us

---- 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:  +0.00 V
+12V:                  +12.33 V
User ADC 1:             +0.00 V
User ADC 2:             +0.00 V

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

Undulating transmit audio in HF programs #draws

Mitch Winkle
 
Edited

DRAWS image Beta13

I am getting output audio which undulates when using either FLDIGI or JS8Call (or even when just using the TUNE button in FLDIGI).

Has anyone run across this?

My draws-manager has the other radio port OFF and I have set TX audio levels based on the mW p-p value of my radio (60).

Receive audio on the Left radio port is great and decodes like a champ. 

Receive audio when enabling and using the Right radio port is a very very low level.  It's so low FLDIGI will not show a waterfall with the lower limit set to -20 in the program.  the same audio levels were used on the Right port as the left port.
Re: no PTT with FT857D, DRAWS HAT and 6 pin miniDIN cable

John D Hays - K7VE
 

I am not where I can look right now, but seem to recall WSJT (FT8) does not implement GPIO PTT, so you have to use CAT through hamlib or VOX.  Fldigi has a setting for GPIO PTT on a tab beyond the CAT setup.
Re: no PTT with FT857D, DRAWS HAT and 6 pin miniDIN cable

Bryan Hoyer
 

Does the RED Led light?

On Aug 22, 2019, at 8:05 AM, wa9pyh@... wrote:

I am using DRAWS software version "DRAWS_BETA13" from May 7, 2019.  I connected to DRAWS MANAGER and set the receive & transmit levels there.  I am using a single 6 pin miniDIN cable plugged into the left connector and have both transmit & receive audio working properly.  But I have no PTT.  If I push the mic button on the rig I can transmit the tones.  I am using the DIG mode on the rig.  I have tried every menu selection combination in the config menus for FT8 and FLDIGI and still no PTT.  Any help or suggestions are welcome!

no PTT with FT857D, DRAWS HAT and 6 pin miniDIN cable

wa9pyh@...
 

I am using DRAWS software version "DRAWS_BETA13" from May 7, 2019.  I connected to DRAWS MANAGER and set the receive & transmit levels there.  I am using a single 6 pin miniDIN cable plugged into the left connector and have both transmit & receive audio working properly.  But I have no PTT.  If I push the mic button on the rig I can transmit the tones.  I am using the DIG mode on the rig.  I have tried every menu selection combination in the config menus for FT8 and FLDIGI and still no PTT.  Any help or suggestions are welcome!
Re: [udrc] UDRC-II squelch on the Yaesu FT-897D → Does DRAWS require this?

Stuart Longland VK4MSL
 

On 21/8/19 9:07 am, Bryan Hoyer wrote:
Squelch in the Radio is for analog modes so we don’t annoy the humans. The SW Modem isn’t annoyed so I turn squelch off in the radio.
The software I plan to use requires the SQL signal to key up PTT in a
VoIP application. As stated in my original email:

With the Pi acting as a WiFi access point, I should be able to use a
Mumble VoIP server to allow my mobile phone to connect and act as a
"cross-band repeater".

Thus when operating a check-point (like I was for the Yarraman to
Wulkuraka bike ride¹ last year), instead of being tethered to the
bicycle, I can plug my headset into my phone instead and still have
80m-70cm all-mode capability.
In short, I'll be doing FM and SSB voice via the DRAWS board.

I'll have a look at the schematic and see if I can do the 5V pull-up mod
on the DRAWS and see how that goes.
--
Stuart Longland (aka Redhatter, VK4MSL)

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

Alan Bush
 

It works. Just as you said it would. And I had a ton of fun getting it there.

Thanks,

Alan . KJ7BFC
Re: Draws/udrc2

W2TLJ <tjoneson@...>
 

Was working normally for months then audio out stopped including echo. Alsamixer settings appear normal.


On Wed, Aug 21, 2019, 19:36 Bryan Hoyer <bhhoyer@...> wrote:
No, because it doesn’t have the IO Configuration and connector.

What failed?

Bryan

On Aug 21, 2019, at 4:34 PM, W2TLJ <tjoneson@...> wrote:

I guess the question I should have asked was can a DRAWS be used to replace a failed UDRC2 on a DR1X

On Tue, Aug 20, 2019, 09:36 John D Hays - K7VE <john@...> wrote:
No.

On Tue, Aug 20, 2019, 01:44 W2TLJ <tjoneson@...> wrote:
Is #DRAWS a drop in replacement for the UDRC2 used with a DR1X?

Tom Joneson w2tlj
Re: Draws/udrc2

Bryan Hoyer
 

No, because it doesn’t have the IO Configuration and connector.

What failed?

Bryan

On Aug 21, 2019, at 4:34 PM, W2TLJ <tjoneson@...> wrote:

I guess the question I should have asked was can a DRAWS be used to replace a failed UDRC2 on a DR1X

On Tue, Aug 20, 2019, 09:36 John D Hays - K7VE <john@...> wrote:
No.

On Tue, Aug 20, 2019, 01:44 W2TLJ <tjoneson@...> wrote:
Is #DRAWS a drop in replacement for the UDRC2 used with a DR1X?

Tom Joneson w2tlj
Re: Draws/udrc2

W2TLJ <tjoneson@...>
 

I guess the question I should have asked was can a DRAWS be used to replace a failed UDRC2 on a DR1X


On Tue, Aug 20, 2019, 09:36 John D Hays - K7VE <john@...> wrote:
No.

On Tue, Aug 20, 2019, 01:44 W2TLJ <tjoneson@...> wrote:
Is #DRAWS a drop in replacement for the UDRC2 used with a DR1X?

Tom Joneson w2tlj
Re: #draws Not Booting #draws

Allen Lee <alee@...>
 

The DRAWS should supply voltage to the pi if your supplying 12v to the DRAWS unit input power. Dont power Pi separately


On 8/21/2019 9:58 AM, Bryan Hoyer wrote:
Make sure it’s on the header correctly and check the 5V Pin on the Pi Header

On Aug 21, 2019, at 5:15 AM, stuartliss@... wrote:

I connected the Draws to my 12v battery box and nothing happens.  It boots normally, when I supply power to the Pi.

Are there troubleshooting instructions?

Thanks,

Stuart, K2YYY
Re: #draws Not Booting #draws

Bryan Hoyer
 

Make sure it’s on the header correctly and check the 5V Pin on the Pi Header

On Aug 21, 2019, at 5:15 AM, stuartliss@... wrote:

I connected the Draws to my 12v battery box and nothing happens.  It boots normally, when I supply power to the Pi.

Are there troubleshooting instructions?

Thanks,

Stuart, K2YYY
#draws Not Booting #draws

Stuart, K2YYY
 

I connected the Draws to my 12v battery box and nothing happens.  It boots normally, when I supply power to the Pi.

Are there troubleshooting instructions?

Thanks,

Stuart, K2YYY
Re: [udrc] UDRC-II squelch on the Yaesu FT-897D → Does DRAWS require this?

Bryan Hoyer
 

Squelch in the Radio is for analog modes so we don’t annoy the humans. The SW Modem isn’t annoyed so I turn squelch off in the radio.

On Aug 20, 2019, at 1:46 PM, Stuart Longland VK4MSL <stuartl@longlandclan.id.au> wrote:

On 20/8/19 11:27 pm, Bryan Hoyer wrote:
Removing the SQL Pin seems like the best way to deal with the Yaesu Radios
How do I read the state of the SQL pin if it's open-circuit?

--
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
...it's backed up on a tape somewhere.
Re: [udrc] UDRC-II squelch on the Yaesu FT-897D → Does DRAWS require this?

Stuart Longland VK4MSL
 

On 20/8/19 11:27 pm, Bryan Hoyer wrote:
Removing the SQL Pin seems like the best way to deal with the Yaesu Radios
How do I read the state of the SQL pin if it's open-circuit?

--
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
...it's backed up on a tape somewhere.
Re: Draws/udrc2

John D Hays - K7VE
 

No.


On Tue, Aug 20, 2019, 01:44 W2TLJ <tjoneson@...> wrote:
Is #DRAWS a drop in replacement for the UDRC2 used with a DR1X?

Tom Joneson w2tlj
Re: [udrc] UDRC-II squelch on the Yaesu FT-897D → Does DRAWS require this?

Bryan Hoyer
 

Removing the SQL Pin seems like the best way to deal with the Yaesu Radios

Bryan

On Aug 20, 2019, at 4:35 AM, Stuart Longland VK4MSL <stuartl@longlandclan.id.au> wrote:

On 15/11/16 12:33 am, Bryan Hoyer wrote:
The Active Low SQL pin drives a 4.7kOhm resistor to the base of a transistor.

Some radios may require a pull-up resistor to any convenient voltage 3-12V. I’d go with a 4.7k to 3.3V up to 10k at 12V.
Hi all,

The DRAWS board arrived yesterday evening, and today I picked up a new
Raspberry Pi 3 to connect it… so far things seem to be working but I'm
yet to hook up a radio.

Now, with the predecessor board (which has seen some use as a packet
radio station), I had to make a small modification to get audio on the
FT-897/857…

https://stuartl.longlandclan.id.au/blog/2016/11/20/getting-the-udrc-ii-to-play-nice-with-the-yaesu-ft-897d/

I've also used this same board with an Yaesu FTM-350AR and a Icom 706 MkIIG.

For the DRAWS, I intend to use it on my bicycle, which runs a FT-857D.
The plan is I'll set up two transceivers: a Wouxun KG-UVD1P I have
laying around set on 145.175MHz for APRS; and use the other port going
to the data jack on the FT-857D. I'll use the DRAWS auxiliary port to
control the CAT interface.

With the Pi acting as a WiFi access point, I should be able to use a
Mumble VoIP server to allow my mobile phone to connect and act as a
"cross-band repeater".

Thus when operating a check-point (like I was for the Yarraman to
Wulkuraka bike ride¹ last year), instead of being tethered to the
bicycle, I can plug my headset into my phone instead and still have
80m-70cm all-mode capability.

For this to work, I still want to be able to use my radio normally, so
basically be able to plug the headset into the microphone/speaker jacks
on the set, and use it like I do now -- as Queensland road rules
preclude me from using a mobile phone whilst in transit *for any reason*
(unless I want an AU$1000 fine for my troubles).

Do I need a pull-up on the SQL lines like I did for the UDRC-II in order
to have normal audio on the FT-857D/897D?

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

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

1. https://www.brisbanewicen.org.au/2018/08/04/y2w/
1541 - 1560 of 5335  
More
Home Messages Hashtags Wiki About Features Pricing Updates Terms Help Twitter