Date   

FT891, FT817, Audio Levels, I/O Fail , and Documentation #draws #ft817 #hfmodes

Julian OH8STN <julian@...>
 

Hello Operators
I've been trying for the better part of four days to get the Yaesu ft-891 and Yaesu ft-817 to work on HF digital modes, correctly with the DRAWS hat. Many of the answers to the questions operators are asking are scattered around the forums in dozens of different threads. This is beyond frustrating! I would suggest building a Wiki specifically for the DRAWS hat called "Getting started". That would solve my first problem which is documentation, and being forced to read through mostly irrelevant threads to find the jewels. 

I've already run the scripts to set the levels. I've disabled ax25 and direwolf. I changed the settings from the 9600 packet port to the data line in mentioned in John and Bryans thread. I've also read through Basils threads about troubleshooting. Most of those are direwolf ax.25relsted threads What I'm left with is a pretty horrific audio I/O problem.
On transmit: When I transmit, I never get a clean signal. When I lower the levels I get some sort of oscillation. There is no sweet spot. it's either too much or too little.
On the receipt side, even with the cables unplugged there's a 30 DB noise level emanating from the DRAWS hat. Signals are barely seen in the waterfall, and decoding is ridiculously poor.
If I plug in my signalink, my miniproSC or even the USB audio interface attached to the wolphilink, it's no problem to get clean audio, and to start decoding stations I could barely see in the waterfall. I've done this with js8 call and fldigi, which both work perfectly with a signalink and zlp miniprosc on the DRAWS image.

I could really use some troubleshooting help.

73
Julian oh8stn 


Re: DRAWS downloadable Image? #setup #compassimage #draws #earlyadopters

Julian OH8STN <julian@...>
 

Hi Art.
were you able to get your ft-891 working properly with an HF radio using an HF digital mode?
73
Julian oh8stn


Re: Draws TX ADC level setting not working for me #draws

Julian OH8STN <julian@...>
 

I am having exactly the same problem with the Yaesu ft-891.
I'm sure the solution is out there, but with all of the answers scattered through dozens of threads it's becoming extremely frustrating.
has there been any testing done on HF radios using HF digital modes? 
73
Julian oh8stn 


Re: It was "fine", then... strange behavior #betaimage #setup #draws

Jack Spitznagel
 

Thanks John, 

I will try that. Keying the rig is not the problem though. I was using flrig with fldigi CAT only and it would go into transmit with no signal. When I checked GPIO 12 in fldigi and enabled CAT contrl, it worked.  Thinking it is the same issue here...

Let you know.


On Dec 22, 2018, at 00:31, John D Hays - K7VE  <john@...> wrote:

I sometimes use flrig to control the radio and wsjtx call flrig to do the CAT PTT.

On Fri, Dec 21, 2018 at 9:25 PM Jack Spitznagel <kd4iz@...> wrote:
Forgot to add that I have not figured out the last little piece of getting
wsjt-x to control the rig with CAT *AND* make DRAWS produce sound; there
does not seem to be a place in wsjt-x to toggle the GPIO pin to get it to do
its magic. No sound, no VOX either... If someone has a clean working set up,
thanks in advance for a useful pointer (yes, I have RTFM and dug through a
bunch of Google-fu - they know nothing about DRAWS and/or make no mention of
using GPIO to key.)

KD4IZ

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Jack Spitznagel
Sent: Friday, December 21, 2018 23:53
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] It was "fine", then... strange behavior #betaimage
#setup #draws

Hi Basil,

I was able to play with settings again today after I finished putting
together the DRAWS/SweetPi console. Spoiler alert - I got back to
function... eventually.) I tried messing with the audio level settings again
- going back and forth between rigs and software. So... please get a beer
(or whatever your favorite libation is) and try to be amused with my
continuing fumbles and the eventual solution.

1. I shut down direwolf, tried your new scripts (in message #2327), and it
did nothing for the lack transmit sound levels for fldigi and wsjt-x, but
also put me back to where the direwolf levels were way too high for the
IC-7000. I reset them to:

PCM             L:[-31.00dB],   R:[-31.00dB]
ADC Level       L:[-2.50dB],    R:[0.00dB]
LO Driver Gain          L:[0.00dB],     R:[11.00dB]
IN1             L:[Off],                R:[Off]
IN1             L:[10kOhm],     R:[10kOhm]

... and direwolf now works again with good transmit audio. So in desperation
I hooked up the FT-817 to repeat the test, but of course had to switch back
to keying with GPIO because I don't have a working CAT control setup just
yet. I had been trying to key the IC-7000 with flrig/C-IV/CAT alone! With
GPIO 12 enabled, the 817 transmitted the very noisy audio! Hmmm. I went back
to the IC-7000 left it keyed by GPIO and it transmitted dirty audio.

So here is a "key" learning: *Keying with flrig C-IV/CAT alone does not
work... the card apparently does not send audio unless a GPIO port is
enabled.* <headsmack>

I don't remember seeing that anywhere in the UDRC/DRAWS discussions. The
fldigi docs were not helpful... implied keying could be done with flrig.
Foo!

So now I am where I can try the deviation/level settings for fldigi/wsjt-x
again... without munging up direwolf.

2. Using fldigi, I adjust PCM levels  up to:
PCM             L:[-21.50dB],   R:[-21.50dB]< the last increment to here
clears the audio!*
ADC Level       L:[-2.50dB],    R:[0.00dB]
LO Driver Gain          L:[2.00dB],     R:[11.00dB]
IN1             L:[Off],                R:[Off]
IN1             L:[10kOhm],     R:[10kOhm]
* this is a familiar #! John put it out with some of his early configs.
Had a nice QSO with KD8MDJ who heard me trying an on air test... looks like
my IMD and S/N ratio are acceptable even though the ALC reading is very
high... I could not see splatter on the pan scope.

3. Now the acid test... did these setting mess up direwolf? Re-enable
ax25/direwolf and...
NO - Problem from Wednesday solved. Put tape on the settings.

So here is the ask:
*I still want to know if there is a way to reduce audio drive so the ALC
reading on the radio drops to near 0 as recommended for digital operations
without the audio getting noisy.*

Is there a way to leave the sound where it is clean? Reducing the LO Drive
Gain or the PCM level immediately puts me back in the high noise plus signal
state. I don't understand the other ADC settings well enough (yet) to make
an educated guess if dialing in some resistance network in the audio output
is possible? Enlightenment please.

Thanks for your help and your patience.

Jack - KD4IZ




--
J Spitznagel
Science River LLC
KD4IZ





--


John D. Hays
Edmonds, WA
K7VE

   


--
J Spitznagel
Science River LLC
KD4IZ


Re: Compatible case, heat sink, and fans?

Patrick - KJ4MUB <ptwaugh@...>
 

When you actual do science and MEASURE something, let us know. :)

Patrick Waugh, M.A., #123263
Probation & Parole Officer II
District 21 Field Office - Branson
(417) 239-3274 Direct
(417) 337-8310 Fax


On Dec 21, 2018, at 09:44, Robert Sears <kf7vop@...> wrote:

Meh... I am a Test Engineer and I do environmental, EMC, HALT, seismic and, all kinds of design qualification testing of electronic products. In fact we would not even be having this conversation if not for my companies products.  Anyway I have been using Raspberry Pi's since they first came out. I have a couple Raspberry Pi's that have been running in a case  24/7 for YEARS without a heatsink or fan, streaming police scanner audio to Broadcastify.

Now maybe if you were taxing the CPU hard it might throttle back due to heat, but how much CPU do you think is needed to run a few ham apps like Fldigi, Direwolf, Xastir? 

In Whatcom county we have been using the UDRC2 on Pi's since they came out and at the most you might see peaks upto %20 CPU utilization in the Raspberry Pi2. Even my Pi that is digitizing and streaming audio only runs at about %10-15 consistently. I don't know what you are doing to see "lower performance in 2 mins flat", but I would say you are doing it wrong.

Honestly like I said before if it makes you feel better by all means stick a heatsink on it. But a fan is another story, all that is going to do is pull dust and contaminants into the case and all over the Pi. The resulting build-up of dust and grime will reduce the heatsinks ability to cool and could make things worse in the long run.  


Re: It was "fine", then... strange behavior #betaimage #setup #draws

 

I sometimes use flrig to control the radio and wsjtx call flrig to do the CAT PTT.

On Fri, Dec 21, 2018 at 9:25 PM Jack Spitznagel <kd4iz@...> wrote:
Forgot to add that I have not figured out the last little piece of getting
wsjt-x to control the rig with CAT *AND* make DRAWS produce sound; there
does not seem to be a place in wsjt-x to toggle the GPIO pin to get it to do
its magic. No sound, no VOX either... If someone has a clean working set up,
thanks in advance for a useful pointer (yes, I have RTFM and dug through a
bunch of Google-fu - they know nothing about DRAWS and/or make no mention of
using GPIO to key.)

KD4IZ

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Jack Spitznagel
Sent: Friday, December 21, 2018 23:53
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] It was "fine", then... strange behavior #betaimage
#setup #draws

Hi Basil,

I was able to play with settings again today after I finished putting
together the DRAWS/SweetPi console. Spoiler alert - I got back to
function... eventually.) I tried messing with the audio level settings again
- going back and forth between rigs and software. So... please get a beer
(or whatever your favorite libation is) and try to be amused with my
continuing fumbles and the eventual solution.

1. I shut down direwolf, tried your new scripts (in message #2327), and it
did nothing for the lack transmit sound levels for fldigi and wsjt-x, but
also put me back to where the direwolf levels were way too high for the
IC-7000. I reset them to:

PCM             L:[-31.00dB],   R:[-31.00dB]
ADC Level       L:[-2.50dB],    R:[0.00dB]
LO Driver Gain          L:[0.00dB],     R:[11.00dB]
IN1             L:[Off],                R:[Off]
IN1             L:[10kOhm],     R:[10kOhm]

... and direwolf now works again with good transmit audio. So in desperation
I hooked up the FT-817 to repeat the test, but of course had to switch back
to keying with GPIO because I don't have a working CAT control setup just
yet. I had been trying to key the IC-7000 with flrig/C-IV/CAT alone! With
GPIO 12 enabled, the 817 transmitted the very noisy audio! Hmmm. I went back
to the IC-7000 left it keyed by GPIO and it transmitted dirty audio.

So here is a "key" learning: *Keying with flrig C-IV/CAT alone does not
work... the card apparently does not send audio unless a GPIO port is
enabled.* <headsmack>

I don't remember seeing that anywhere in the UDRC/DRAWS discussions. The
fldigi docs were not helpful... implied keying could be done with flrig.
Foo!

So now I am where I can try the deviation/level settings for fldigi/wsjt-x
again... without munging up direwolf.

2. Using fldigi, I adjust PCM levels  up to:
PCM             L:[-21.50dB],   R:[-21.50dB]< the last increment to here
clears the audio!*
ADC Level       L:[-2.50dB],    R:[0.00dB]
LO Driver Gain          L:[2.00dB],     R:[11.00dB]
IN1             L:[Off],                R:[Off]
IN1             L:[10kOhm],     R:[10kOhm]
* this is a familiar #! John put it out with some of his early configs.
Had a nice QSO with KD8MDJ who heard me trying an on air test... looks like
my IMD and S/N ratio are acceptable even though the ALC reading is very
high... I could not see splatter on the pan scope.

3. Now the acid test... did these setting mess up direwolf? Re-enable
ax25/direwolf and...
NO - Problem from Wednesday solved. Put tape on the settings.

So here is the ask:
*I still want to know if there is a way to reduce audio drive so the ALC
reading on the radio drops to near 0 as recommended for digital operations
without the audio getting noisy.*

Is there a way to leave the sound where it is clean? Reducing the LO Drive
Gain or the PCM level immediately puts me back in the high noise plus signal
state. I don't understand the other ADC settings well enough (yet) to make
an educated guess if dialing in some resistance network in the audio output
is possible? Enlightenment please.

Thanks for your help and your patience.

Jack - KD4IZ




--
J Spitznagel
Science River LLC
KD4IZ





--


John D. Hays
Edmonds, WA
K7VE

   


Re: It was "fine", then... strange behavior #betaimage #setup #draws

Jack Spitznagel
 

Forgot to add that I have not figured out the last little piece of getting
wsjt-x to control the rig with CAT *AND* make DRAWS produce sound; there
does not seem to be a place in wsjt-x to toggle the GPIO pin to get it to do
its magic. No sound, no VOX either... If someone has a clean working set up,
thanks in advance for a useful pointer (yes, I have RTFM and dug through a
bunch of Google-fu - they know nothing about DRAWS and/or make no mention of
using GPIO to key.)

KD4IZ

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Jack Spitznagel
Sent: Friday, December 21, 2018 23:53
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] It was "fine", then... strange behavior #betaimage
#setup #draws

Hi Basil,

I was able to play with settings again today after I finished putting
together the DRAWS/SweetPi console. Spoiler alert - I got back to
function... eventually.) I tried messing with the audio level settings again
- going back and forth between rigs and software. So... please get a beer
(or whatever your favorite libation is) and try to be amused with my
continuing fumbles and the eventual solution.

1. I shut down direwolf, tried your new scripts (in message #2327), and it
did nothing for the lack transmit sound levels for fldigi and wsjt-x, but
also put me back to where the direwolf levels were way too high for the
IC-7000. I reset them to:

PCM L:[-31.00dB], R:[-31.00dB]
ADC Level L:[-2.50dB], R:[0.00dB]
LO Driver Gain L:[0.00dB], R:[11.00dB]
IN1 L:[Off], R:[Off]
IN1 L:[10kOhm], R:[10kOhm]

... and direwolf now works again with good transmit audio. So in desperation
I hooked up the FT-817 to repeat the test, but of course had to switch back
to keying with GPIO because I don't have a working CAT control setup just
yet. I had been trying to key the IC-7000 with flrig/C-IV/CAT alone! With
GPIO 12 enabled, the 817 transmitted the very noisy audio! Hmmm. I went back
to the IC-7000 left it keyed by GPIO and it transmitted dirty audio.

So here is a "key" learning: *Keying with flrig C-IV/CAT alone does not
work... the card apparently does not send audio unless a GPIO port is
enabled.* <headsmack>

I don't remember seeing that anywhere in the UDRC/DRAWS discussions. The
fldigi docs were not helpful... implied keying could be done with flrig.
Foo!

So now I am where I can try the deviation/level settings for fldigi/wsjt-x
again... without munging up direwolf.

2. Using fldigi, I adjust PCM levels up to:
PCM L:[-21.50dB], R:[-21.50dB]< the last increment to here
clears the audio!*
ADC Level L:[-2.50dB], R:[0.00dB]
LO Driver Gain L:[2.00dB], R:[11.00dB]
IN1 L:[Off], R:[Off]
IN1 L:[10kOhm], R:[10kOhm]
* this is a familiar #! John put it out with some of his early configs.
Had a nice QSO with KD8MDJ who heard me trying an on air test... looks like
my IMD and S/N ratio are acceptable even though the ALC reading is very
high... I could not see splatter on the pan scope.

3. Now the acid test... did these setting mess up direwolf? Re-enable
ax25/direwolf and...
NO - Problem from Wednesday solved. Put tape on the settings.

So here is the ask:
*I still want to know if there is a way to reduce audio drive so the ALC
reading on the radio drops to near 0 as recommended for digital operations
without the audio getting noisy.*

Is there a way to leave the sound where it is clean? Reducing the LO Drive
Gain or the PCM level immediately puts me back in the high noise plus signal
state. I don't understand the other ADC settings well enough (yet) to make
an educated guess if dialing in some resistance network in the audio output
is possible? Enlightenment please.

Thanks for your help and your patience.

Jack - KD4IZ




--
J Spitznagel
Science River LLC
KD4IZ


Re: It was "fine", then... strange behavior #betaimage #setup #draws

Jack Spitznagel
 

Hi Basil,

I was able to play with settings again today after I finished putting
together the DRAWS/SweetPi console. Spoiler alert - I got back to
function... eventually.) I tried messing with the audio level settings again
- going back and forth between rigs and software. So... please get a beer
(or whatever your favorite libation is) and try to be amused with my
continuing fumbles and the eventual solution.

1. I shut down direwolf, tried your new scripts (in message #2327), and it
did nothing for the lack transmit sound levels for fldigi and wsjt-x, but
also put me back to where the direwolf levels were way too high for the
IC-7000. I reset them to:

PCM L:[-31.00dB], R:[-31.00dB]
ADC Level L:[-2.50dB], R:[0.00dB]
LO Driver Gain L:[0.00dB], R:[11.00dB]
IN1 L:[Off], R:[Off]
IN1 L:[10kOhm], R:[10kOhm]

... and direwolf now works again with good transmit audio. So in desperation
I hooked up the FT-817 to repeat the test, but of course had to switch back
to keying with GPIO because I don’t have a working CAT control setup just
yet. I had been trying to key the IC-7000 with flrig/C-IV/CAT alone! With
GPIO 12 enabled, the 817 transmitted the very noisy audio! Hmmm. I went back
to the IC-7000 left it keyed by GPIO and it transmitted dirty audio.

So here is a "key" learning: *Keying with flrig C-IV/CAT alone does not
work... the card apparently does not send audio unless a GPIO port is
enabled.* <headsmack>

I don't remember seeing that anywhere in the UDRC/DRAWS discussions. The
fldigi docs were not helpful... implied keying could be done with flrig.
Foo!

So now I am where I can try the deviation/level settings for fldigi/wsjt-x
again... without munging up direwolf.

2. Using fldigi, I adjust PCM levels up to:
PCM L:[-21.50dB], R:[-21.50dB]< the last increment to here
clears the audio!*
ADC Level L:[-2.50dB], R:[0.00dB]
LO Driver Gain L:[2.00dB], R:[11.00dB]
IN1 L:[Off], R:[Off]
IN1 L:[10kOhm], R:[10kOhm]
* this is a familiar #! John put it out with some of his early configs.
Had a nice QSO with KD8MDJ who heard me trying an on air test... looks like
my IMD and S/N ratio are acceptable even though the ALC reading is very
high... I could not see splatter on the pan scope.

3. Now the acid test... did these setting mess up direwolf? Re-enable
ax25/direwolf and...
NO - Problem from Wednesday solved. Put tape on the settings.

So here is the ask:
*I still want to know if there is a way to reduce audio drive so the ALC
reading on the radio drops to near 0 as recommended for digital operations
without the audio getting noisy.*

Is there a way to leave the sound where it is clean? Reducing the LO Drive
Gain or the PCM level immediately puts me back in the high noise plus signal
state. I don’t understand the other ADC settings well enough (yet) to make
an educated guess if dialing in some resistance network in the audio output
is possible? Enlightenment please.

Thanks for your help and your patience.

Jack - KD4IZ

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Jack Spitznagel
Sent: Wednesday, December 19, 2018 14:37
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] It was "fine", then... strange behavior #betaimage
#setup #draws

Basil,

Thanks for the quick response.

I understand setting of PCM and LO Driver Gain. If I started with PCM at
zero, I could not turn LO Drive down far enough to prevent the IC-7000 doing
the "protect -self" routine and shut down transmit. Had to turn it way down
from there to have the stupid little beast transmit anything particularly a
noisy but decodable PSK31 sig!

Quick follow up with more info. At those drive levels below, direwolf is
still behaving fine - the audio is loud and clean enough that my D74A and a
creaky old AEA PK232 running as a KISS TNC can both handle it.

It is with fldigi direct to sound that is having the noise and modulation
problems? Confusing for me, but might tell you something. I am not aware of
"transmit power" adjust in fldigi like there is in wsjt-x. It might be
something the program is doing? I have used fldigi a bit, but usually in
"winders 10" prefer other digital programs.

Jack

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Jack Spitznagel
Sent: Wednesday, December 19, 2018 13:52
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] It was "fine", then... strange behavior #betaimage
#setup #draws

Basil,

That test got me part of the way there. DRAWS was apparently overdriving the
audio front end of the IC-7000, hence the flashing TX led. I did not know it
did that! The *showudrc.sh* output is at the end of the email.
Initially *alsa-show.sh* said:
PCM L:[0.00dB], R:[0.00dB]
ADC Level L:[-2.00dB], R:[0.50dB]
LO Driver Gain L:[0.00dB], R:[11.00dB]

Using the *measure_deviate.sh* script, I was able to turn the levels back to
a point that the tone was "fairly" clean. The AGC indication was still very
high with *alsa-show.sh* now saying:
PCM L:[-31.00dB], R:[-31.00dB]
ADC Level L:[-2.00dB], R:[0.50dB]
LO Driver Gain L:[6.00dB], R:[6.00dB]

When I turned PCM back any more than that, the background noise (frying
bacon) being transmitted increased and quickly overwhelmed the tone level.
That was the ALC pumping I was seeing.

Observation: As it is set now, the circuit noise level is extremely high.
Apparently the IC-7000 input is pretty sensitive and/or badly impedance
matched?

Looks like I will need to build some kind of attenuation if the DRAWS board
does not have the ability to dial it in? (I have not gotten that far in the
documentation yet)

Unfortunately, I will have to put off any additional tweaking until Friday.

Jack - KD4IZ

I did not see anything grossly out-of-line in the *showudrc.sh* output
follows:
============================================================================
pi@kd4iz_draws:/bin $ showudrc.sh
==== Sound Card ====
udrc card number line: card 0: udrc [udrc], device 0: Universal Digital
Radio Controller tlv320aic32x4-hifi-0 [] udrc is sound card #0 ==== 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: 78feb572-30c1-420b-8596-f37186c9cb16
Vendor: NW Digital Radio

==== sys Ver ====
----- /proc/version
Linux version 4.14.79-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3
(crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1159 SMP Sun Nov 4 17:50:20
GMT 2018

----- /etc/*version: 9.6

----- /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.6 (stretch)
Release: 9.6
Codename: stretch

---- systemd
Static hostname: kd4iz_draws
Icon name: computer
Machine ID: 2f51e140e908474eaa86ae805f03a6d8
Boot ID: b9e8d2eefb9f401a8884c0d1f9d7c2d3
Operating System: Raspbian GNU/Linux 9 (stretch)
Kernel: Linux 4.14.79-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 6
snd_pcm_dmaengine,tlv320aic32x4,snd_soc_bcm2835_i2s,snd_soc_core

-rw-r--r-- 1 root 6388 Dec 8 19:59
/lib/modules/4.14.79-v7+/updates/dkms/tlv320aic32x4-i2c.ko
-rw-r--r-- 1 root 38156 Dec 8 19:59
/lib/modules/4.14.79-v7+/updates/dkms/tlv320aic32x4.ko
-rw-r--r-- 1 root 6408 Dec 8 19:59
/lib/modules/4.14.79-v7+/updates/dkms/tlv320aic32x4-spi.ko
-rw-r--r-- 1 root 8332 Dec 8 19:59
/lib/modules/4.14.79-v7+/updates/dkms/udrc.ko

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

---- 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 Nov 25 23:31
/var/lib/apt/lists/archive.compasslinux.org_dists_cedar_InRelease
-rw-r--r-- 1 root 17567 Jul 2 22:52
/var/lib/apt/lists/archive.compasslinux.org_dists_cedar_main_binary-amd64_Pa
ckages
-rw-r--r-- 1 root 43315 Nov 25 23:31
/var/lib/apt/lists/archive.compasslinux.org_dists_cedar_main_binary-armhf_Pa
ckages

----- Dire Wolf DEVELOPMENT version 1.6 A (Dec 9 2018)

==== boot config ====
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module #dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
# dtparam=audio=on

force_turbo=1
dtoverlay=
dtoverlay=draws

---- gpsd
● gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; indirect; vendor
preset: en
Active: active (running) since Fri 2018-12-14 20:49:52 EST; 4 days ago
Main PID: 4274 (gpsd)
CGroup: /system.slice/gpsd.service
└─4274 /usr/sbin/gpsd -N -n /dev/ttySC0 /dev/pps0

Dec 14 20:49:52 kd4iz_draws systemd[1]: Started GPS (Global Positioning
System)
lines 1-8/8 (END)
============================================================================
===

-----Original Message-----
From: udrc@nw-digital-radio.groups.io <udrc@nw-digital-radio.groups.io> On
Behalf Of Basil Gunn
Sent: Wednesday, December 19, 2018 12:13
To: udrc@nw-digital-radio.groups.io
Subject: Re: [udrc] It was "fine", then... strange behavior #betaimage
#setup #draws


In general for debugging problems:

Send output of:
~/bin/showudrc.sh
~/n7nix/debug/alsa-show.sh

Use the following instructions for measure_deviate.sh to verify PTT &
transmit paths.
https://github.com/nwdigitalradio/n7nix/tree/master/deviation

Using another radio listen to the tone produced by the measure_deviate.sh
script.

The most common problem, if the tones do not sound right, is the output is
being over driven causing it to clip.

Receive path:
Tune a radio to the APRS 1200 baud freq. 144.390 MHz run the following in a
console:

tail -f /var/log/direwolf/direwolf.log

You should see received packets scrolling by.

Let us know what you find & thanks for testing the DRAWS hat.

/Basil

Jack Spitznagel <@flyingfrawg> writes:

Basil, John, All,

Initially, Beta 5 seemed to work out of the box but I ran into some
DRAWS audio and keying strangeness that is baffling me after 3 tries
at installing from newly flashed microSD cards and following Basil's
latest procedure on GitHub. Hope you can provide insight. Rig is a CAT
controlled IC-7000.

Tested Direwolf with Xastir and YAAC with both RX and TX successfully,
but
noticed the audio was a bit hot - signal here looked normal on the SpecLab
so I left it alone.

Then disabled AX.25/direwolf (script) and configured fldigi and wsjt-x.
Both programs worked in receive but the TX audio to the IC-7000 was very
"hot". Put fldigi in tune then to bring the ALC reading as close to zero as
possible by reducing audio levels with the PCM drive control. As audio level
is reduced - the ALC starts to "pump", as did the power out indication -
unexpectedly, there was a increase of noise on audio and harmonic spikes got
higher as level of signal was reduced. Returned levels to where they had
been and meter indications returned to where they were before. Was able to
have a PSK31 QSO and got no comment about the signal quality.

I re-enabled AX.25/Direwolf using the script. Now both Xastir and YAAC
no
longer would transmit audio. When the rig is keyed, the TX LED on the rig
flashes 3-4 times quickly and there is no modulation of the FM carrier.
Reboot did not change behavior. Going back to non-AX25 mode, now fldigi
would key the radio, but no modulation occurred.

Re-installation of the DRAWS beta 5 from the ground up (x2) did not
help -
none of the programs transmit audio and symptoms are the same.

To be sure rig was OK, I hooked up an old SIgnaLink to a laptop, ran
HRD
and it drove and keyed the rig just fine. So I have to assume that the
problem is software or DRAWS hardware related.

Where should I be looking to fix the audio? The keying?
Settings should not so brittle. Thanks in advance,





--
J Spitznagel
Science River LLC
KD4IZ






--
J Spitznagel
Science River LLC
KD4IZ






--
J Spitznagel
Science River LLC
KD4IZ


Re: Problem getting #wsjtx & #js8call to work #wsjtx #js8call

Basil Gunn
 

It was mentioned to me that your ALSA inputs might be set incorrectly.
I have updated a script & added a new one that should help with that.

- display 5 ALSA controls that are of most interest.
alsa-show.sh

- Set up ALSA controls that should allow the HF programs to work
properly.
setalsa-default.sh

You will still need to set your ALSA controls, PCM & LO Driver Gain for your
deviation depending on which radio you have.

You can get the new scripts by issuing these commands in a console.

cd
cd n7nix
git pull

then:

cd bin
./alsa-show.sh
./setalsa-default.sh

/Basil

Basil Gunn <@basil860> writes:

Hi Bob,

First thank you for testing the DRAWS RPi hat, we appreciate all the
things that people like you are trying out.

If you have a problem it would be much better for you to start a new
thread by using a subject line that describes your problem such as:

Subject: Problem getting #wsjtx & #js8call to work

Perhaps read John's suggestions for using the discussion group here:
https://nw-digital-radio.groups.io/g/udrc/topic/using_the_discussion_topics/28813785

I think your problem is that direwolf is running & you need to stop it
before you start wsjtx & js8call.

cd
cd bin
sudo su
./ax25-disable
reboot

Please read this doc
https://github.com/nwdigitalradio/n7nix/blob/master/DRAWS_CONFIG.md

If you still have problems I will need you to re-enable direwolf so I
can more easily get information about what might be wrong.
Please read this doc
https://github.com/nwdigitalradio/n7nix/blob/master/VERIFY_CONFIG.md

Thanks,
/Basil n7nix


Bob Orrett <boborrett@...> writes:

I need help.

Firstly let me admit that I am a relative newbie to RPi. I have
installed the draws hat and booted up with draws image beta5. Using
the supplied cables or any other cable I have I cannot get anything to
happen with the on board 6 pin audio ports on the draws hat. I have
tried both wsjtx and js8call. I can get both of these programs to work
fine with a digital interface from the usb ports on the RPi.

My radio is a ft817.

It feels like the audio ports need to be activated somehow
but I am unable to find any mention of that in the literature. I have
connected the output to an oscilloscope and see nothing when I try to
transmit. I have tried all the available audio sound card choices in
the settings menu for these programs. I think the correct one is
plughwCARD=udrc,DEV=0. What am I missing? Help. Bob ve3obo


Re: Show us your DRAWS setup photos (reset) #draws #photos

Jack Spitznagel
 

Apologize for doing a subject reset. The original post was lost here. I think it was David [kg5eiu] who originally posted the request but the original does not seem to be in the UDRC subgroup.

 

My original intent was to come up with custom design to 3D print myself. When discussion of the Smarti Pi Touch case came up, I realized that my needs would be met going that way with a little kitbashing. I want something completely integrated, with minimal cabling and power requirements, so the suggested external monitors were not in the cards - just my preference - the unit has to fit in backpack with a radio and a reasonable solar charged battery system that can support 4-5 hours use.

 

Found a discount deal on the case kit with the RPi "official" touch screen, with it ordered the *deep* case back cover and a couple of NTE parts (micro rocker switch and 5mm chassis mount coaxial power socket). I already had the 3" of hook up wire (hobby shelf) and scrounged a spare angled plug assembly with Powerpoles installed from my KX3 kit.  I just happened to have a mini keyboard and the RTS01 USB to ICOM CIV programing adapter. I printed the standoff extenders in black PLA and just did enough finishing to clean out the overhang supports and get them to fit.

 

The back cover needed a couple of strategic cutouts for access to the DIN connectors and the GPS SMA connector. A hole was also drilled for power connector socket. I twisted some hookup wire and the power pigtail fairly tight to get a little stray RF "resistance". Trimmed the pigtail and hookup wire as short as I could get away with. Figured if I had RF noise issues I could put a clip-on ferrite on the power lead. It was not needed. I now have a DRAWS that will be good for my trail kit FT-817 or the KX3 (when I finish the miniDIN 6 adapter). For "QRO" Field Day/POTA/EMCOMM out of the mobile I'll use the IC-7000 shown. If I just have to have a bigger screen, I will investigate using a laptop logged in to the RPi. I have been using the 7" for a while and do not find it a problem.

 Comments welcome. Enjoy:

--
Jack Spitznagel
KD4IZ


Problem getting #wsjtx & #js8call to work #wsjtx #js8call

Basil Gunn
 

Hi Bob,

First thank you for testing the DRAWS RPi hat, we appreciate all the
things that people like you are trying out.

If you have a problem it would be much better for you to start a new
thread by using a subject line that describes your problem such as:

Subject: Problem getting #wsjtx & #js8call to work

Perhaps read John's suggestions for using the discussion group here:
https://nw-digital-radio.groups.io/g/udrc/topic/using_the_discussion_topics/28813785

I think your problem is that direwolf is running & you need to stop it
before you start wsjtx & js8call.

cd
cd bin
sudo su
./ax25-disable
reboot

Please read this doc
https://github.com/nwdigitalradio/n7nix/blob/master/DRAWS_CONFIG.md

If you still have problems I will need you to re-enable direwolf so I
can more easily get information about what might be wrong.
Please read this doc
https://github.com/nwdigitalradio/n7nix/blob/master/VERIFY_CONFIG.md

Thanks,
/Basil n7nix


Bob Orrett <boborrett@...> writes:

I need help.

Firstly let me admit that I am a relative newbie to RPi. I have
installed the draws hat and booted up with draws image beta5. Using
the supplied cables or any other cable I have I cannot get anything to
happen with the on board 6 pin audio ports on the draws hat. I have
tried both wsjtx and js8call. I can get both of these programs to work
fine with a digital interface from the usb ports on the RPi.

My radio is a ft817.

It feels like the audio ports need to be activated somehow
but I am unable to find any mention of that in the literature. I have
connected the output to an oscilloscope and see nothing when I try to
transmit. I have tried all the available audio sound card choices in
the settings menu for these programs. I think the correct one is
plughwCARD=udrc,DEV=0. What am I missing? Help. Bob ve3obo


Re: Compatible case, heat sink, and fans?

Robert Sears
 

Meh... I am a Test Engineer and I do environmental, EMC, HALT, seismic and, all kinds of design qualification testing of electronic products. In fact we would not even be having this conversation if not for my companies products.  Anyway I have been using Raspberry Pi's since they first came out. I have a couple Raspberry Pi's that have been running in a case  24/7 for YEARS without a heatsink or fan, streaming police scanner audio to Broadcastify.

Now maybe if you were taxing the CPU hard it might throttle back due to heat, but how much CPU do you think is needed to run a few ham apps like Fldigi, Direwolf, Xastir? 

In Whatcom county we have been using the UDRC2 on Pi's since they came out and at the most you might see peaks upto %20 CPU utilization in the Raspberry Pi2. Even my Pi that is digitizing and streaming audio only runs at about %10-15 consistently. I don't know what you are doing to see "lower performance in 2 mins flat", but I would say you are doing it wrong.

Honestly like I said before if it makes you feel better by all means stick a heatsink on it. But a fan is another story, all that is going to do is pull dust and contaminants into the case and all over the Pi. The resulting build-up of dust and grime will reduce the heatsinks ability to cool and could make things worse in the long run.  


Re: Brief Introduction and Some Generic Information #ft817 #din6 #audio

Bob Orrett <boborrett@...>
 

I need help.
Firstly let me admit that I am a relative newbie to RPi. I have installed the draws hat and booted up with draws image beta5. Using the supplied cables or any other cable I have I cannot get anything to happen with the on board 6 pin audio ports on the draws hat. I have tried both wsjtx and js8call. I can get both of these programs to work fine with a digital interface from the usb ports on the RPi. My radio is a ft817. It feels like the audio ports need to be activated somehow but I am unable to find any mention of that in the literature. I have connected the output to an oscilloscope and see nothing when I try to transmit. I have tried all the available audio sound card choices in the settings menu for these programs. I think the correct one is plughwCARD=udrc,DEV=0. What am I missing?
Help.
Bob ve3obo


Re: Beta Image Available #betaimage #draws

Joseph Vilardo
 

Basil

I understand now. Couldn't figure out  why the RED PIPE was in the argument ./btest.sh -P [udrc0|udrc1]

Thanks

Joe K3JV

On 12/20/2018 2:01 PM, Basil Gunn wrote:
 [udr0|udr1] is a documentation convention that means choose either udr0
 or udr1 as the argument for port name. ie.
 ./btest.sh -P udr0
 or
 ./btest.sh -P udr1

type
./btest.sh -h
for more information on command line arguments.
/Basil



Joseph Vilardo <jvilardo@...> writes:

John
Not sure if this is the right place to post this question if it is not right please re-direct me

I have loaded beta5 image for the RPi/DRAWS and have been following the instructions from N7NIX ( VERIFY_CONFIG.md ) I cant get the transmit test to run as directed here is what happens
fromroot@drawsjav:/home/pi/n7nix/debug#./btest.sh -P [udr0|udr1]
bash: udr1]: command not found

However I see the port 0 light on the DRAWS and my transmitter fire and can hear a long packet being transmitted on a second radio. Is the console return message ( bash:udr1] :command not found) just telling me I do not have port 1 configured for Direwolf??

Thanks,
Joe K3JV




Re: Beta Image Available #betaimage #draws

Basil Gunn
 

[udr0|udr1] is a documentation convention that means choose either udr0
or udr1 as the argument for port name. ie.
./btest.sh -P udr0
or
./btest.sh -P udr1

type
./btest.sh -h
for more information on command line arguments.
/Basil



Joseph Vilardo <@k3jv> writes:

John
Not sure if this is the right place to post this question if it is not right please re-direct me

I have loaded beta5 image for the RPi/DRAWS and have been following the instructions from N7NIX ( VERIFY_CONFIG.md ) I cant get the transmit test to run as directed here is what happens
fromroot@drawsjav:/home/pi/n7nix/debug#./btest.sh -P [udr0|udr1]
bash: udr1]: command not found

However I see the port 0 light on the DRAWS and my transmitter fire and can hear a long packet being transmitted on a second radio. Is the console return message ( bash:udr1] :command not found) just telling me I do not have port 1 configured for Direwolf??

Thanks,
Joe K3JV


Re: ntpd not installed on beta 5 #ntp #chrony #ntpd

Basil Gunn
 

Hi Bernard,
Thanks for the feedback.

Will be releasing a beta6 image in the next day or so with more updates
including your suggestions:
Prompt for AX.25 IP addresses.
Added chronyc makestep to core_install.sh

Also added iptables default install with drop of 239.255.255.250 on
ax.25 interfaces. This address is an SSDP (Simple Service Discovery
Protocol) udp multicast coming from google chrome to discover chromecast
servers. I am thinking this might solve the panic you are seeing in
rose_route_frame where one of the addresses is a NULL pointer.

/Basil



f6bvp <f6bvp@...> writes:

Hi Basil,

I ran your script verify_time.sh and saw NTP synchronized: no !
Consequently I concluded that my NTP install operation followed by another chrony install introduced some issue.
Thus I apt-get removed chrony and tried to install it again.
However new install failed until I used the following parameter in order to remove ALL chrnoy related files :
*apt-get purge chrony*
before install it again with success.
Then your script showed me that NTP was synchronized.
Many thanks for your help.

Bernard, f6bvp


Re: Beta Image Available #betaimage #draws

Joseph Vilardo
 

John
Not sure if this is the right place to post this question if it is not right please re-direct me

I have loaded beta5 image for the RPi/DRAWS and have been following the instructions from N7NIX ( VERIFY_CONFIG.md ) I cant get the transmit test to run as directed here is what happens
from  root@drawsjav:/home/pi/n7nix/debug# ./btest.sh -P [udr0|udr1]
bash: udr1]: command not found

However I see the port 0 light on the DRAWS and my transmitter fire and can hear a long packet being transmitted on a second radio. Is the console return message ( bash:udr1] :command not found) just telling me I do not have port 1 configured for Direwolf??

Thanks,
Joe K3JV


locked Using the discussion topics #support

 


Hi Everyone.

First of all thank you for your testing, observations, suggestions, and requests for help via the established groups on groups.io


This allows the folks at NW Digital Radio and others to answer once and everyone can benefit.

A few important requests:
  1. Use the right sub-group for you topic (e.g. draws and udrc to https://nw-digital-radio.groups.io/g/udrc and so forth)
  2. Use subject line hashtags, e.g. #fldigi for topics about fldigi. If you use the web interface you can click on hashtags in the subject and see all postings related to that topic, including previous conversations.  Also you can search them in your email.  This helps with organizing information and doing your research on a topic.
  3. Place one and only only one issue per topic, with  a matching hashtag, and create separate topics for each issue so that a thread can be established for a topic/issue.  E.g. don't place an AX.25 and D-STAR issue in the same topic, unless it is specific to an interaction of the two (rare), create a topic for each.
  4. Be thorough in your description, e.g. radio, which port, which application, configuration, etc. Others can't figure out what is going on without sufficient information.
Again, thank you for using NW Digital Radio products and services and your valuable insights.

--


John D. Hays
Director

  


Re: ntpd not installed on beta 5 #ntp #chrony #ntpd

Bernard f6bvp / ai7bg
 

Hi Basil,

I ran your script verify_time.sh and saw NTP synchronized: no !
Consequently I concluded that my NTP install operation followed by another chrony install introduced some issue.
Thus I apt-get removed chrony and tried to install it again.
However new install failed until I used the following parameter in order to remove ALL chrnoy related files :
apt-get purge chrony
before install it again with success.
Then your script showed me that NTP was synchronized.
Many thanks for your help.

Bernard, f6bvp


Re: It was "fine", then... strange behavior #betaimage #setup #draws

Basil Gunn
 

So Basil should
I be following this instruction "Before verifying CORE functionality you
must have run the *app config script*" with the new DRAWS betas or has that
already been done?
On your first boot of the new image you need to follow these
instructions:
https://github.com/nwdigitalradio/n7nix/blob/master/DRAWS_CONFIG.md

You need to run ./app_config.sh core.

It will set your locale, make you change your password & host name &
auto config some other things. If you don't want packet and/or direwolf then
run:

~/bin/ax25-disable
and reboot.

If you run into problems I will ask you to do verification with direwolf
so you will need to load it again:

~/bin/ax25-enable
and reboot

/Basil