Re: Fldigi ver4.2.06 and 4.2.06.21
Hi Dave
AFC is not relevant to all modes. Back in the 4.2.06.alpha evolutions I mentioned to the forum that it wasn't working, but was indicating "on" with the multicarrier PSKR modems. RSID action
By
Bob Cameron, VK2YQA
·
#54243
·
|
Fldigi ver4.2.06 and 4.2.06.21
Hi.
Running on LMDE 6 all up-to-date, on a 4 core Intel platform with 8G of RAM.
Fldigi 4.2.06.21 (alpha) has a buggy AFC feature.
It's been flaky since I first tried it, but intermittently the
By
Dave, G?WBX
·
#54242
·
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
Hi Chris,
I am glad it is working better. I know we are getting into the weeds a little, but looking at your command lines shown here, it seems that you have a space character between the double dash
By
Dave, KZ1O
·
#54241
·
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
PROGRESS!!
First of all, thanks to everyone who chimed in on this. This is my first linuxham post and your responses made me feel really welcome.
Second, I am now on the air with FLAMP. Here's an
By
Chris Doutre - KC9AD
·
#54240
·
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
Thanks. I just gave that a try, with a few variations, and they all seemed to work the same way.
The FLAMP command is accepted, FLAMP starts, displays “NOT CONNECTED” (with the correct window
By
Chris Doutre - KC9AD
·
#54239
·
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
Give it a try without those parentheses. They might be falsely interpreted by the shell.
To be sure, make it flamp-right or something shorter, no spaces or special characters. (If it doesn't help,
By
Dave, KZ1O
·
#54238
·
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
I tried another test:
Start FLDigi, leave it running,
Start FLMsg, leave it running,
Run netstat -an | grep -e 7362 -e 7363
Results:
tcp 0 0 0.0.0.0:7363 0.0.0.0:*
By
Chris Doutre - KC9AD
·
#54237
·
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
David, thanks for getting back so soon. My responses are below.
tcp ? ? ? ?0 ? ? ?0 0.0.0.0:7363 ? ? ? ? ? ?0.0.0.0:* ? ? ? ? ? ? ? LISTEN
Yes, I start FLDigi first, then FLMsg,
By
Chris Doutre - KC9AD
·
#54236
·
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
Hello Chris,
Is Fldigi running when you run Flamp? It's required.
That's not a shell script.. that's just a GUI menu definition for Flamp meant to be used by the LXDE desktop manager
By
David Ranch, KI6ZHD
·
#54235
·
|
Re: New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
Correction: It should say:
Here is the FLDigi desktop script:
Sorry about that.
Chris KC9AD
By
Chris Doutre - KC9AD
·
#54234
·
|
New #NexusDR-X Linux software build from scratch; #fldigi will start; #flamp will not.
#NexusDR-X
#fldigi
#flamp
Hello All,
I'm a brand new member of linuxham. I'm a Linux "user", not really an admin of any kind.
I have been running the FLDigi suite under Linux on a Raspberry Pi for several years. I was using
By
Chris Doutre - KC9AD
·
#54233
·
|
Re: #flrig Switching from CW to FT8 leaves filter width at 500 Hz
#flrig
I was thinking about this. Why are we setting bandwidth for a rig like IC7300?
The algorithm appears to set the bandwidth as follows:
Have we seen this mode? Set the bandwidth to last time;
Else set
By
Philip Rose, GM3ZZA
·
#54232
·
|
Re: #flrig Switching from CW to FT8 leaves filter width at 500 Hz
#flrig
All I can see is that the mode_bwA is getting corrupted when I change the CW bandwidth. The CW, CW-R, LSB, LSB-D, USB and USB-D values are all getting set to 9 (500 Hz). I set a breakpoint on
By
Philip Rose, GM3ZZA
·
#54231
·
|
Re: #flrig Switching from CW to FT8 leaves filter width at 500 Hz
#flrig
After some prompting by Mike Black in another forum, I have the following results.
The problem only occurs if I have transmitted in CW mode, AND the CW filter bandwidth was not its default value. I
By
Philip Rose, GM3ZZA
·
#54230
·
|
Re: Next version FLdigi
Good day David.
*Sending QSO via API to external log*
Once I forgot to turn off sending QSO via API to an external log. And on the host this resource was deleted due to some circumstances or the
By
Vladimir, RW6AVK
·
#54229
·
|
CTY-3507 Country Files - 07 March 2025
The Country (CTY) Files were updated on 07 March 2025:
https://www.country-files.com/cty-3507-07-march-2025/
For installation instructions, start at:
https://www.country-files.com/
Hover
By
Jim Reisert AD1C
·
#54228
·
|
#flrig Switching from CW to FT8 leaves filter width at 500 Hz
#flrig
This is a problem that has been bugging me for sometime. I finally decided to look into it.
I am running an IC-7300 and connecting to it with flrig. Most times I change my operating from CW to FT8
By
Philip Rose, GM3ZZA
·
#54227
·
|
Re: AndFlmsg V1.6.0.7 posted on Bitbucket
Thankyou for doing the android APK ...
By
Michael Durkin, KC7NOA
·
#54226
·
|
CTY-3506 Country Files - 28 February 2025
The Country (CTY) Files were updated on 28 February 2025:
https://www.country-files.com/cty-3506-28-february-2025/
For installation instructions, start at:
By
Jim Reisert AD1C
·
#54225
·
|
Is there a limit on notifications?
Running FLDIGI version 4.1.18 on a Raspberry Pi 4.
I seem to be limited to 21 custom text search notifications before they begin glitching and changing form into "My callsign de CALL"
By
Drew, KG7YSX
·
#54224
·
|