Date   

moderated Re: TAPR 30M WSPR-PI kit instructions #raspberrypi #wsjtx

w4oa@arrl.net <w4oa@...>
 

Thanks for the response Robin, but the documentation you linked to is for the current offered assembled only unit. The prior product was a kit, and I have the kit, so I need the kit assembly instructions. 

I may can figure it out, I have been able to trace the resistors to the current unit schematic. However, the filter components will be a bit of work, which I would like to avoid if possible.

Mitch W4OA
Opelika, AL


moderated Re: TAPR 30M WSPR-PI kit instructions #raspberrypi #wsjtx

G8DQX
 

Mitch,

you could try https://tapr.org/wspr-on-20-30-and-40-meters/#comment-7849, which offers a document https://web.tapr.org/pdf/WSPR-WIthout-Tears-30m-and-40m.pdf. I suspect that the necessary image card is the one at the bottom of https://tapr.org/product/wspr-without-tears-30-or-40m/.

HTH, 73, Stay Safe,

Robin, G8DQX

PS: It was all well hidden!


On 18/11/2020 17:59, w4oa@... wrote:

I recently acquired the kit version of the TAPR 30M WSPR-PI kit. A card came with the kit to go to the TAPR website for building instructions. Unfortunately, TAPR has retired the kit (new version is not a kit, already built). TAPR has a new web site and the instructions for this old kit is not there. Does anyone have the instructions that they can email to me? The new version is not a kit, it is already built.

Tnx
Mitch W4OA
Opelika, AL
_._,_._,_


moderated flrig memories question

d_ziolkowski
 

Hello-

For the flrig memories, is there a way to filter by TAGS?

Or sort by Frequency?

Nothing at all found re memories in help docs that I could find.

Thanks

Dan KC2STA


moderated TAPR 30M WSPR-PI kit instructions #raspberrypi #wsjtx

w4oa@arrl.net <w4oa@...>
 

I recently acquired the kit version of the TAPR 30M WSPR-PI kit. A card came with the kit to go to the TAPR website for building instructions. Unfortunately, TAPR has retired the kit (new version is not a kit, already built). TAPR has a new web site and the instructions for this old kit is not there. Does anyone have the instructions that they can email to me? The new version is not a kit, it is already built.

Tnx
Mitch W4OA
Opelika, AL


moderated Re: fldigi 4.1.16.02 posted at

Brian Morrison ,G8SEZ
 

On Wed, 2020-11-18 at 10:50 -0600, Dave, W1HKJ wrote:

   Contestia / Olivia
     * Added mode CONTESTIA 16/250 with RsID 275
     * Added macro code to allow any valid Contestia or
       Olivia BW/TONES combination to be set via macro tags:
Good to see the Olivia love, one of my favourite modes.

--

Brian


moderated Re: Kenwood TH-D72 and Allstar

Victor Zarich
 

My TH-D72 is my favorite radio for use with my AllStar nodes. It is very easy to transmit DTMF codes with and It works great. It is my go to radio when it comes to anything requiring DTMF tones. I also just like the way it sounds and feels in my hand.

On Nov 18, 2020, at 7:29 AM, Danny K5CG via groups.io <k5cg@...> wrote:


Allstar is Linux so it is related but this isn't the best group to get that answer.

In any case, yes it does work. Allstar is dependent on the accuracy of the DTMF tone frequencies and mine works flawlessly. However, my older TH-G71A does not work well enough.


From: "Dave Holcomb / K9DBA" <kilo9deltabravoalpha@...>
To: linuxham@groups.io
Sent: Tuesday, November 17, 2020 3:22:19 PM
Subject: [linuxham] Kenwood TH-D72 and Allstar


Hello,

Does the TH-D72 work with allstar just as well as it works with echolink?


moderated fldigi 4.1.16.02 posted at

Dave, W1HKJ
 

http://www.w1hkj.com/alpha/fldigi/

Wed Nov 18 10:12:00 2020 -0500 - Versopm 4.1.16.02

  Contestia / Olivia
    * Added mode CONTESTIA 16/250 with RsID 275
    * Added macro code to allow any valid Contestia or
      Olivia BW/TONES combination to be set via macro tags:
      . <MODEM:CONTESTIA:BW:TONES>
      . <MODEM:OLIVIA:BW:TONES>
      . where BW in set {125, 250, 500, 1000, 2000}
           TONES in set {2, 4, 8, 16, 32, 64, 256}

  Greek translation
    * Update to Greek po file

73, David, W1HKJ


moderated Re: Enhancement Request

Dave, W1HKJ
 

Patrick, F6CTE, (RsID principal) and I discussed your request.  The pool of available RsID codes is small and diminishing.  No RsID will be assigned at this time, unless a very strong case can be made for adding these two modes.  The recent addition of Contestia 16/250 was justified by that modes use as a call up frequency for a large and active emergency communications net.  Contestia 16/250 exhibits similar resiliency and s/n characteristics as Olivia 16/250.  These two modes share the same MFSK modem code. The principal difference is that the reduced (caps only) character set of Contestia makes that mode almost twice as fast as Olivia for every TONES/BANDWIDTH selection.  Contestia is recommended for casual QSO's.

I have modified the macro language to make it more convenient to select odd combinations of BW / TONES for both Contestia and Olivia

73, David, W1HKJ

On 11/17/20 2:48 PM, Raul M0ZZM wrote:

Hi Everyone,

Would it be possible to add Olivia 16/250 and 32/500 to the list of Fldigi modes so that the user can select them without the need of using custom options? And would it be possible to also have the RSID codes for these two modes?

I found that 16/250 in particular is incredibly resilient and able to reliably decode at -12dB, it would be great to have them ready and with an RSID code attached.

Thank you for your commitment to Fldigi and for your support.


moderated Re: Enhancement Request

Raul M0ZZM
 

On Tue, Nov 17, 2020 at 09:28 PM, Chris E., KC2RGW wrote:
Hah, I knew I recognized your call from somewhere Raul.
Hi Chris,

I also operate on 30m, feel free to say hello if you see me.


moderated Re: Kenwood TH-D72 and Allstar

Danny K5CG
 

Allstar is Linux so it is related but this isn't the best group to get that answer.

In any case, yes it does work. Allstar is dependent on the accuracy of the DTMF tone frequencies and mine works flawlessly. However, my older TH-G71A does not work well enough.


From: "Dave Holcomb / K9DBA" <kilo9deltabravoalpha@...>
To: linuxham@groups.io
Sent: Tuesday, November 17, 2020 3:22:19 PM
Subject: [linuxham] Kenwood TH-D72 and Allstar


Hello,

Does the TH-D72 work with allstar just as well as it works with echolink?


moderated Re: Kenwood TH-D72 and Allstar

Dave, GØWBX
 

Sent to the wrong group ?

Dave G0WBX

--
Created on and sent from a Unix like PC running and using free and open source software:


moderated Re: Anybody else running TQSL?

Paul Bramscher , KD0KZE
 

I got the escalation message also. Looks like 2.5.7 is in the works
according to the directory listing there on SourceForge. I'm willing to
use 2.5.5 and wait for a new point release. Good to know it appears
that they're on top it.

73, KD0KZE / Paul

On 11/17/2020 10:47 AM, Harry Bloomberg, W3YJ wrote:
Thanks!  In the meantime I received an email from ARRL acknowledging my
ticket and letting me know they've escalated the issue.  I do not know
Rick, is he a TQSL developer, or just a highly skilled programmer who
was able to figure this out?

73,
Harry W3YJ

On Tue, Nov 17, 2020 at 9:51 AM Joseph Counsil, KØOG
<counsil@... <mailto:counsil@...>> wrote:

Good news!  Rick Murphy (K1MU) posted an update at Sourceforge to
fix the crash.  I built and test it on my Linux Mint 20 Xfce system,
and it works fine - uploads log entries with no problem now.

You can download the latest from Sourceforge:
  https://sourceforge.net/p/trustedqsl/tqsl/ci/master/tree/
<https://sourceforge.net/p/trustedqsl/tqsl/ci/master/tree/>

73,
-Joe-
K0OG


moderated Re: fldigi 4.1.16 Pulse Audio configuration issue #raspberrypi #pi3

Cliff, AE5ZA
 

Great news, Dan. Thanks for letting us know it’s all working finally. Now enjoy!

73,
Cliff, AE5ZA

On Nov 17, 2020, at 22:21, Dan, N1UKJ <uspt@...> wrote:

yea Cliff - AE5ZA  !

in my message: https://groups.io/g/linuxham/message/43366

my question was : "maybe there is an XML file that i can edit to remove the offend entry.
is anyone aware of such a XML file ??? "
you did It !
in your message reply: https://groups.io/g/linuxham/message/43369

your answer was : "open the fldigi_def.xml file. Do a search for <PULSESERVER>"

thank you, thank you, thank you, thank you, thank you !
here is what the  offending line looks like on my system, that i have been looking for in the fldigi_def.xml file.
<!-- type: std::string; default: &quot;&quot;
PulseAudio server string -->
<PULSESERVER>raspberrypi</PULSESERVER>

the result is that in Fldigi-4.1.16   Configure>Soundcard>Devices > [ ] PulseAudio  ---->Server string: [            ]

the "Server srting:"      textbox is empty, as it should be !
NOW when i put a check into the " [ ] PulseAudio"   checkbox, the program no longer generates a pop-up
Error window message i was getting as stated in my original posting message:

https://groups.io/g/linuxham/message/43353

as a side note i made a similar mistake a year ago and was never able to resolve it on groups.io
guess that just says i'm not ageing gracefully or can't remember sh_t.
i'm thankful to those who endured this very long drawn out posting
but remember,  i have been dealing with this same issue for a year.

 i am exceeding grateful that there is a community like linuxham@groups.io 
and the special effort of support that i found here.
i just knew it could be fix but the final credit has to go to :
Cliff - AE5ZA  !

dan - N1UKJ


moderated Re: fldigi 4.1.16 Pulse Audio configuration issue #raspberrypi #pi3

dan n1ukj
 

i just want to make it clear to anyone who has encountered this problem that the offending line in:
fldigi_def.xml
on my RaspberryPi 3 B+ using OS buster 10 was:

<PULSESERVER>raspberrypi</PULSESERVER>



when the line is corrected it should look like:

<PULSESERVER></PULSESERVER>



NOTE:
when restarting Fldigi  the file  fldigi_def.xml   was not read so,

i reboot the RaspberryPi  to ensure the file fldigi_def.xml
was read by the FlDigi program.



moderated Re: fldigi 4.1.16 Pulse Audio configuration issue #raspberrypi #pi3

dan n1ukj
 

yea Cliff - AE5ZA  !

in my message: https://groups.io/g/linuxham/message/43366

my question was : "maybe there is an XML file that i can edit to remove the offend entry.
is anyone aware of such a XML file ??? "
you did It !
in your message reply: https://groups.io/g/linuxham/message/43369

your answer was : "open the fldigi_def.xml file. Do a search for <PULSESERVER>"

thank you, thank you, thank you, thank you, thank you !
here is what the  offending line looks like on my system, that i have been looking for in the fldigi_def.xml file.
<!-- type: std::string; default: &quot;&quot;
PulseAudio server string -->
<PULSESERVER>raspberrypi</PULSESERVER>

the result is that in Fldigi-4.1.16   Configure>Soundcard>Devices > [ ] PulseAudio  ---->Server string: [            ]

the "Server srting:"      textbox is empty, as it should be !
NOW when i put a check into the " [ ] PulseAudio"   checkbox, the program no longer generates a pop-up
Error window message i was getting as stated in my original posting message:

https://groups.io/g/linuxham/message/43353

as a side note i made a similar mistake a year ago and was never able to resolve it on groups.io
guess that just says i'm not ageing gracefully or can't remember sh_t.
i'm thankful to those who endured this very long drawn out posting
but remember,  i have been dealing with this same issue for a year.

 i am exceeding grateful that there is a community like linuxham@groups.io 
and the special effort of support that i found here.
i just knew it could be fix but the final credit has to go to :
Cliff - AE5ZA  !

dan - N1UKJ


moderated Re: fldigi 4.1.16 Pulse Audio configuration issue #raspberrypi #pi3

Dave - N9QNZ <dave@...>
 

As for #2, alsamixer shows mono stereo is output.  The incorrect "label" can be fixed by commenting out the mono section of /usr/share/pulseaudio/alsa-mixer/profile-sets/default.conf

Assuming this is what you are referring to, this is an old and well known "issue".


On Tue, Nov 17, 2020 at 6:31 PM G8DQX <list@...> wrote:

Dave,

a good question. PulseAudio has not been part of Pi OS (née Raspbian) since Raspbian Stretch. It was introduced to support Bluetooth audio, but was dropped in Stretch, and is absent from Buster. My observations in Buster, when PulseAudio is installed, are (on Pi 4B hardware) that:

1) Bluetooth audio is not supported when PulseAudio is active (it is under ALSA)

2) audio from the 3.5mm socket is reduced to mono (under ALSA, the audio is stereo, of pretty high quality)

The reasons for this behaviour are not directly known. The behaviour is consistent with the dropping of PulseAudio, which is otherwise generally easier to use than raw ALSA.

HTH, 73, Stay Safe,

Robin, G8DQX

From the release notes (https://downloads.raspberrypi.org/raspios_armhf/release_notes.txt):

2017-08-16:
  * Based on Raspbian Stretch (Debian version 9)
  * Version 60 of Chromium browser included
  * Version 3.0.1 of Sonic Pi included
  * Version 6.1.1 of RealVNC included
  * Version 0.17.4 of NodeRED included
  * Bluetooth audio routed via ALSA rather than Pulseaudio


On 17/11/2020 18:53, Dave - N9QNZ wrote:
In what ways is pulseaudio "broken"?

On Tue, Nov 17, 2020 at 9:45 AM G8DQX <list@...> wrote:
Dan,

had you specifically installed PulseAudio? On Buster it is not installed
by default. If you do install PulseAudio, then it is broken in several
respects. Pi OS Buster expects you to use ALSA, which, as far as my
informal tests go, fully supports built-in audio & audio peripherals.

73, Stay Safe,

Robin, G8DQX


moderated Re: fldigi 4.1.16 Pulse Audio configuration issue #raspberrypi #pi3

Cliff, AE5ZA
 

Robin,

I don’t know who installs PulseAudio for fldigi, but it’s there when fldigi is built and works fine for me on a Pi3 and Pi4. It even starts without being told to. All I do is build fldigi and install Pavcontrol and it’s there. Just did it yesterday with the latest Buster.

73,
Cliff, AE5ZA

On Nov 17, 2020, at 17:31, G8DQX <list@...> wrote:

Dave,

a good question. PulseAudio has not been part of Pi OS (née Raspbian) since Raspbian Stretch. It was introduced to support Bluetooth audio, but was dropped in Stretch, and is absent from Buster. My observations in Buster, when PulseAudio is installed, are (on Pi 4B hardware) that:

1) Bluetooth audio is not supported when PulseAudio is active (it is under ALSA)

2) audio from the 3.5mm socket is reduced to mono (under ALSA, the audio is stereo, of pretty high quality)

The reasons for this behaviour are not directly known. The behaviour is consistent with the dropping of PulseAudio, which is otherwise generally easier to use than raw ALSA.

HTH, 73, Stay Safe,

Robin, G8DQX

From the release notes (https://downloads.raspberrypi.org/raspios_armhf/release_notes.txt):


2017-08-16:
  * Based on Raspbian Stretch (Debian version 9)
  * Version 60 of Chromium browser included
  * Version 3.0.1 of Sonic Pi included
  * Version 6.1.1 of RealVNC included
  * Version 0.17.4 of NodeRED included
  * Bluetooth audio routed via ALSA rather than Pulseaudio



On 17/11/2020 18:53, Dave - N9QNZ wrote:
In what ways is pulseaudio "broken"?

On Tue, Nov 17, 2020 at 9:45 AM G8DQX <list@...> wrote:
Dan,

had you specifically installed PulseAudio? On Buster it is not installed
by default. If you do install PulseAudio, then it is broken in several
respects. Pi OS Buster expects you to use ALSA, which, as far as my
informal tests go, fully supports built-in audio & audio peripherals.

73, Stay Safe,

Robin, G8DQX


moderated Re: fldigi 4.1.16 Pulse Audio configuration issue #raspberrypi #pi3

Ken Cox, WA8OMR
 

I had issues with Pulse Audio Output volume setting changing on it's own running flrig and fldigi 4.1.15. Went back to using alsa and no more problems. Also 4.1.16 works well on pi 4b.


moderated Re: fldigi 4.1.16 Pulse Audio configuration issue #raspberrypi #pi3

G8DQX
 

Dave,

a good question. PulseAudio has not been part of Pi OS (née Raspbian) since Raspbian Stretch. It was introduced to support Bluetooth audio, but was dropped in Stretch, and is absent from Buster. My observations in Buster, when PulseAudio is installed, are (on Pi 4B hardware) that:

1) Bluetooth audio is not supported when PulseAudio is active (it is under ALSA)

2) audio from the 3.5mm socket is reduced to mono (under ALSA, the audio is stereo, of pretty high quality)

The reasons for this behaviour are not directly known. The behaviour is consistent with the dropping of PulseAudio, which is otherwise generally easier to use than raw ALSA.

HTH, 73, Stay Safe,

Robin, G8DQX

From the release notes (https://downloads.raspberrypi.org/raspios_armhf/release_notes.txt):

2017-08-16:
  * Based on Raspbian Stretch (Debian version 9)
  * Version 60 of Chromium browser included
  * Version 3.0.1 of Sonic Pi included
  * Version 6.1.1 of RealVNC included
  * Version 0.17.4 of NodeRED included
  * Bluetooth audio routed via ALSA rather than Pulseaudio


On 17/11/2020 18:53, Dave - N9QNZ wrote:
In what ways is pulseaudio "broken"?

On Tue, Nov 17, 2020 at 9:45 AM G8DQX <list@...> wrote:
Dan,

had you specifically installed PulseAudio? On Buster it is not installed
by default. If you do install PulseAudio, then it is broken in several
respects. Pi OS Buster expects you to use ALSA, which, as far as my
informal tests go, fully supports built-in audio & audio peripherals.

73, Stay Safe,

Robin, G8DQX


Re: fldigi 4.1.15 posted

Dave Slotter, W3DJS
 

Sent direct email with attachment.

On Tue, Nov 17, 2020 at 6:06 PM Randy Greig, VE3YRG <ve3yrg@...> wrote:
Yes please.

Randy
VE3YRG



On Sun, Nov 15, 2020 at 5:45 PM Dave Slotter, W3DJS <slotter@...> wrote:
I have a script which installs/updates the entire Fldigi suite on Linux. Let me know if you want it.

73,

On Sun, Nov 15, 2020 at 5:03 PM Dan, N1UKJ <uspt@...> wrote:
i have tried to get the following FLDIGI versions working without success for a week;
4.12.1, 4.15.1, and most recently 4.16.1

all have generated error messages in the 'make install' phase.

1) this is on a new OS-Buster 10 image install on RaspberryP1 3 ( CLEAN / FRESH install )
2) ran 'sudo apt update'
3) ran 'sudo apt upgrade
4) followed these instructions: https://sourceforge.net/p/fldigi/wiki/debian_howto/

current error reported during ' make install '
CXX      wwv/fldigi-wwv.o
  CXXLD    fldigi
/usr/bin/ld: dialogs/fldigi-confdialog.o: file not recognized: file truncated
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:3130: fldigi] Error 1
make[3]: Leaving directory '/home/pi/Downloads/fldigi-4.1.16/src'
make[2]: *** [Makefile:8559: all-recursive] Error 1
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.16/src'
make[1]: *** [Makefile:2008: all] Error 2
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.16/src'
make: *** [Makefile:469: all-recursive] Error 1
pi@raspberrypi:~/Downloads/fldigi-4.1.16 $

thanks, dan


--
- Dave
  W3DJS


--
- Dave
  W3DJS

6101 - 6120 of 49455