开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. Linuxham
  2. Messages
Expanded Topics Messages Polls
Date
updated K4.xml rigcat control definition file

 

开云体育

posted at

and at

Corrects bandwidth selections.

Thank you Mike, W9MDB.

73, David, W1HKJ

Re: fldigi 4.2.04.14 developers version posted at

 

Hi David

Sorry, forget to said my work on MS Window 10.

Yip
VR2VRC?
Re: Next version FLdigi

 

开云体育

Hi.

Fldigi ver4.2.05 successfully built and running here on LMDE 5 64 bit, all OK.

I still see, that I can't see the rx IMD figures for PSK modes other than PSK31.



For all the higher PSK modes (PSK61 and faster) it shows a "Phase" figure in %.
I.e.

(Yes, it's not a PSK63 signal under the cursor, I know that.)


Is this a "Feature" or a "Bug"?? (If "Feature", why?)

I've asked this before when a previous release came out, but never seen an answer.
(If it was sent, It got likely got lost in the noise of other stuff...)


73.

Dave G0WBX.




-- 
Sent from a Micro$oft free zone:
Re: fldigi 4.2.04.14 developers version posted at

 

开云体育

Repeating what Joel Black just told y'all.

Open the MacOS Finder

Press and hold the Cmd key
Press and hold the Shift key
Press the period '.' key

Your Finder window should now show hidden files and folders.? One of which should be named ".fldigi", that is DOT FLDIGI.

Double click on that folder and the Finder will display the hidden folders contents.

This book available on Amazon has great reviews:



David, W1HKJ


On 4/24/24 08:38, VR2VRC via groups.io wrote:

On Wed, Apr 17, 2024 at 01:42 AM, Dave, W1HKJ wrote:
where the path of folder??

VR2VRC

Re: fldigi 4.2.04.14 developers version posted at

 

On Wed, Apr 17, 2024 at 01:42 AM, Dave, W1HKJ wrote:
where the path of folder??

VR2VRC
Re: FLDIGI won't open on M1 Mac

 

开云体育

If you execute the following: CMD+SHIFT+. (hold them all down at the same time) you will display hidden files on a Mac. That is CMD+SHIFT+[period] in case that “.” is ambiguous. You can issue the same command to re-hide files and folders if you like.

Getting familiar with the CLI will save you a lot of issues but I understand the apprehension. When learning DOS 30-odd years ago and going through the commands in alphabetical order, I came to “format” (I don’t know how I got past “fdisk") I typed in “format C:” When asked if I was sure, I said hell yeah I’m sure and hit “Y” and [return].

I’ve not been apprehensive of breaking things since. ;) That was on the *only* computer in the house at the time and contained all my dad’s Quicken information. Thankfully, he had a backup.

Joel - W4JBB

On Apr 24, 2024, at 7:53?AM, N5WDX via groups.io <rlongwell@...> wrote:

Thanks for the suggestion, David. I've done a few very minor things in Terminal, but I'm not real experienced at all. I tried just entering what you did, but couldn't get past the second line. I don't know how to search for hidden files.

Re: FLDIGI won't open on M1 Mac

N5WDX
 

Thanks for the suggestion, David. I've done a few very minor things in Terminal, but I'm not real experienced at all. I tried just entering what you did, but couldn't get past the second line. I don't know how to search for hidden files.
Re: FLDIGI won't open on M1 Mac

N5WDX
 

Yes, I've tried them both. Neither will open. Interestingly, FLAMP and FLMSG will both open, but not FLDIGI.
Re: FLDIGI won't open on M1 Mac

 

开云体育

The VN dmg is built on a Mac mini / M2 / 14.4.1, and then tested on a Mac mini / i7 / 14.4.1.? It should run OK on an M1 based machine.

Open a terminal window:

$ cd
$ ls -a
look for hidden folder .fldigi? (dot fldigi)

if found:

$ cd .fldigi

and then delete these two files "fldigi_def.xml" "fldigi.prefs"

then

$ cd /Applications

$ ls fldigi*

if found:

$ cd fldigi*app
$ cd Contents
$ cd MacOS

$ ls

you should a a single file "fldigi", execute it from the command line

$ ./fldigi

Does the applcation start ?? If yes, proceed to configure fldigi being sure to select "file only" for the soundcard if you do not have a transceiver connected to the computer.

Report back please.

David

On 4/24/24 06:39, N5WDX via groups.io wrote:

I've been trying for days to get FLDIGI to work on my M1 Mac running Sonoma 14.4.1. But when I try to open it, it closes immediately. Does anyone have a solution? Thanks!

FLDIGI won't open on M1 Mac

N5WDX
 

I've been trying for days to get FLDIGI to work on my M1 Mac running Sonoma 14.4.1. But when I try to open it, it closes immediately. Does anyone have a solution? Thanks!
Next version FLdigi

 

GD.
I really like FLdigi.
Tell me, is it possible to add to the Settings?menu item “send QSO via the UDP (or TCP)? protocol to an external IP?server”, as is done, for example, in WSJT-X.

Picture0003.jpg

fldigi 4.2.05

 

开云体育

posted to Source Forge, and


Index of /files/fldigi

On line help also updated to this version.

Refer to the readme.txt file for a chronological list of changes since 4.2.04.

73, David, W1HKJ
Re: #flrig flrig not working with my FT-890 FTDI Programming Cable #flrig

 

I ran FLRIG from the terminal. It initially followed the rig's tuning, but when I tuned the rig to exactly 14.200.00, it disagreed. This is repeatable At 14.200.00. It doesn't do that at frequencies above or below that.
Grig doesn't do that.
Starting FLRIG with the rig set to 14.200.00 causes the rig not found pop-up. The init button does the same. I can change the frequency slightly to fix this.
---
Using VFO A, the rig was tuned to 14.200.00 and FLRIG displayed 14200.02
The terminal displayed
Info: 0D 15 AA E2 00 00 02 04 05 09 0A CB 48 00 00 01 04 85
?? A: 14200020, AM
?? B: 7074000, CW
Flag Bytes??? 80 00 00 08 50
? Split:????? OFF? Active vfo: B? PTT:??????? OFF

failed to read VFO status bytes (18)
failed to read VFO status bytes (18) ...repeating...
---

The yellow light in the PTT button lights when the rig is transmitting.

* Read/Set VFO A
I can set the frequency from FLRIG or the rig (except as noted above)

* Read/Set VFO B
When I click vfoB, FLRIG displays the vfoB frequency from the rig. FLRIG display follows the rig's VFO, but I cannot change the rig's frequency by changing vfoB on FLRIG. FLRIG just reverts back to the rig's frequency.
vfoB does not have the problem with 14.200.00 that vfoA has.

* Read/Set VFO A/B active
The FLRIG highlight follows the VFO A/B setting from the rig.
The rig switches to the VFO that FLRIG requests.

* Read/Set Split
The yellow light in FLRIG's Split button does not change when split mode is changed from the rig.
The rig and the split button light agree when set from FLRIG.

* Read Smeter
S meter follows the rig's meter relative to the signal, however FLRIG reads lower.

* Read power out
On the FLRIG 100 watt scale, with 100 watts on the rig, FLRIG showed 55 watts and changes with power output.
The FT-890 needs 50 watt and 150 watt scales.

The modulation mode menu puts the rig into the correct mode, but the menu changes to read something else:
LSB reads LSB
USB reads CW
CW reads AM
CW-N reads AM
AM reads FM
AM-N reads FM
FM reads LSB
FM-N reads LSB

Sometimes when FLRIG is started or quit, changes the rig to a frequency and mode other than it was set to.
It seems to eventually leave the frequency unchanged when I keep setting it back to the desired frequency.
Maybe mode problem could be from the mode menu issue.
CTY-3414 Country Files - 20 April 2024

 

The Country (CTY) Files were updated on 20 April 2024:



For installation instructions, start at:



Hover your mouse over the word Contest in the menu, then select the
software you are using.

To install the file, follow the link to your software at the top of the page.

If you are interested in a bigger CTY.DAT for everyday logging, you can get
it here:



Note that the release notes (and Version Entity) for this larger file are
different than what is shown below. There is a separate link to them.

As a reminder, there is an RSS feed of the latest country file announcements:



Here are the release notes:

20 April 2024 (CTY-3414)
VER20240420, Version entity is Kyrgyzstan, EX

Added/changed Entities/Prefixes/Callsigns:

* 3D2CCC is Conway Reef, 3D2/c
* TO2FY is French Guiana, FY
* GB8DDY is Northern Ireland, GI
* GB1FT, GB6DD and GB8VED are all Scotland, GM
* GB0ILB is Wales, GW
* IT9PQJ/0 is Italy, I
* IQ0SS/P is Sardinia, IS
* K1GJQ, K3EYJ, N4CUC, N5DIM, NO5O, W0MOT, W5BMO, W9PDC, W9SSS, WA0RMW,
WA1NHZ and WE4BY are all United States, K in CQ zone 3, ITU zone 6
* K7AER is United States, K in CQ zone 3, ITU zone 7
* K7SWS and N6IGA are both United States, K in CQ zone 4, ITU zone 6
* K7MOE, K8VH, K9TWW, KB9TYC, KC9CSQ, KC9LBO, KD2CFD, KE7RTB, KF7ZYV,
KJ4EBE, KN4SLP, N6TCO, N7TBU, N9JNQ, N9ZW, NA7XX, ND9M, W2HK, W2RPC, W6EHY,
W6NJB, WB9WKT and WJ9H are all United States, K in CQ zone 4, ITU zone 7
* AA4QM, AD5IT, K0BBQ, K4HHA, K4IDT, K4JW, K4TEP, KA0S, KB4IY, KD4BWM,
KD5UVV, KD5YBE, KG5EG, KI4ZRH, KI5HVD, KI5VNB, KJ4DVR, KJ5AZV, KJ6XC, KK4EM,
KK4VPT, KK4XA, KN4JGH, KO4IDC, KO4TNK, KO4TUP, KO4UFD, KQ4AHO, KQ4AZN,
KQ4IMY, N0KWA, N0XMD, N0XOH, N1RIP, N2CCG, N2GSB, N4BCD, N4EJW, N4RRW,
N6XBP, W0CGC, W1WWA, W4JGD, W4PGM, W4YEM, W5LNX, W5OBM, W5SPH, WA4III,
WB4KUU, WM4U, WV4E and WX7AA are all United States, K in CQ zone 4, ITU zone 8
* AJ6TE, K5NT, K5YDR, K8II, K9KA, KA8VZB, KB0NVR, KE8TEH, KM6UH, KU8V,
KW5DRE, N0TR, NA5Y, NQ8C, W0GZR, W0RMX, W5MPB, W6ALG, W6GOK, W8ANT, W8DOF,
W8QI, W9JJ, W9MGB, W9NWY, WB7RAV, WB8WUP, WG9X, WJ0J, WN8KXY and WO0M
are all United States, K in CQ zone 5, ITU zone 8
* K6KOA is Hawaii, KH6
* AG7XM and KE5APD are both Alaska, KL
* KD2RCT is Puerto Rico, KP4
* LU1EQF/D and LW2EDM/D are both Argentina, LU
* LU1XA/XA is Argentina, LU in ITU zone 16
* 5P0WARD/D, 5P0WARD/E, 5P0WARD/H, 5P0WARD/I, 5P0WARD/U, 5P0WARD/W,
5P0WARD/X and 5P0WARD/Z are all Denmark, OZ
* R1961AG, R1961GP, R1994YU, R1996VK, R2014NC, R80SEV, R9KC/6, R9XD/6,
RN2F/1, RW6MD/1 and UA0QNI/3 are all European Russia, UA
* R4WAN/P, UA9SY/4 and UG4I/P are all European Russia, UA in ITU zone 30
* RI0POL is European Russia, UA in CQ zone 40
* UA9AR/P is Asiatic Russia, UA9
* R2ET/9 is Asiatic Russia, UA9 in CQ zone 18, ITU zone 31
* R3DFE/9/P and RA1WS/0 are both Asiatic Russia, UA9 in CQ zone 18, ITU zone 32
* VI60ATZ is Australia, VK

Removed Entities/Prefixes/Callsigns:

* 4UNR in Vienna Intl Ctr, *4U1V
* 3D2CR in Conway Reef, 3D2/c
* VP8CP in Antarctica, CE9
* TO4A in Martinique, FM
* TX0QRP in French Polynesia, FO
* GB0DS in Wales, GW
* AG1RL, AL4B, KD9ATF, KL4J, KN0A, KY0W, N1IPB, NK9I, WB2UBW and WB5NHL
in United States, K
* KC8UHF in Hawaii, KH6
* AC5D and N7DKL in Alaska, KL
* LU1HAK/H, LU2AJG/K, LU5EFG/D, LU5YBJ/V, LU6HL/H, LU7HCH/H, LU9EKQ/D,
LW5DHG/D, LW5DIT/D and LW9EUE/D in Argentina, LU
* 4UNR in Austria, OE
* R35AFC, R35AFQ and R35DRA in European Russia, UA
* R35AFA, R35AFZ and RX9WT/P in Asiatic Russia, UA9

Though I am subscribed to this reflector so that I can make these
announcements, I do not see most messages posted to it. If you have
any comments or corrections to the country file, please contact me
directly.

73 - Jim AD1C

--
Jim Reisert AD1C, <jjreisert at alum.mit.edu>,

Re: flrig development version posted

 

开云体育

I was just about to settle down and look at a problem I was having with filter width displays on IC-705. Then this came in, so I recompiled flrig with the latest alpha.

The problems I had have gone away. I can adjust the filter widths in flrig and see the values change in flrig and fldigi. Also the waterfall on fldigi changes in the same way.

Thanks Phil.?

From: [email protected] <[email protected]> on behalf of Dave, W1HKJ <w1hkj@...>
Sent: 20 April 2024 3:55 PM
To: ham-software@... <ham-software@...>; ham-mac <ham-mac@...>; winfldigi <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>
Subject: [linuxham] flrig development version posted
?
at

See readme.txt for list of changes.

73, David, W1HKJ
flrig development version posted

 

开云体育

at

See readme.txt for list of changes.

73, David, W1HKJ
Re: #flrig flrig not working with my FT-890 FTDI Programming Cable #flrig

 

开云体育

Steve,

Substitute the attached two files for the ones of the same name in the flrig source tree.? Rebuild and then run from a command line terminal.

Test: Read/Set VFO A
????? Read/Set VFO B
????? Read/Set VFO A/B active
????? Read/Set Split
????? Read Smeter
????? Read power out

73, David

FT890.h
FT890.h
FT890.cxx
FT890.cxx

Re: #sound Connecting multiple rigs. #sound #fldigi

 

开云体育

Thanks Bob,

Spend a couple of hours this afternoon doing some investigations.

As far as I can tell, there is no discernible difference between the two pairs of Audio Codecs. The only difference I can see is due to the position on the USB sub-system. If I want a bomb-proof PnP solution I would need to find the USB port that the serial port connects to in each case and then assume that the Audio Codec connected on that port is the one associated rig - fair enough I think. So I'll keep the two rigs plugged in and connected to power, though not necessarily switched on (keeps the USB active).

I am using flrig to connect my apps to the serial ports (and provide all the data for remote working).

I ended up creating the following aliases:

alias ic7300='flrig --config-dir ~/.ic7300 &'
alias ic705='flrig --config-dir ~/.ic705 &'
alias wsjtx7300='wsjtx -c IC7300 &'
alias wsjtx705='wsjtx -c IC705 &'
alias fldigi705='PULSE_SINK=alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo PULSE_SOURCE=alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo /usr/local/bin/fldigi --config-dir ~/.ic705 &'
alias fldigi7300='PULSE_SINK=alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo.2 PULSE_SOURCE=alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo.2 /usr/local/bin/fldigi --config-dir ~/.ic7300 &'

Note the way the two codecs are enumerated. I've done a reasonable amount of robustness testing and I've not seen unwanted interaction between the two fldigi aliases.

I think I have a solution that works for what I want to do. Now I need to automate launching the modem apps from within my logger. Thanks for all your help. It's helped me a lot to get my head round this.


73 Phil GM3ZZA


On 17/04/2024 21:40, Bob Cameron, VK2YQA wrote:

Hi Phil

Enumeration depends on the polling order of the PC and whether the rig(s) are on at the time. If both rigs are on every time you reset the PC's USB bus and the plugs remain in the same sockets they will get the same "number" "order". In most cases then cycling a single rig's power off/on will bring back the same "number", but it kind of depends on how it dies. Sometimes you'll get an entirely new "number".

I hope I made that clear hihi. I think being aware of the reason is important.

If one wanted full automation and perfect response every time the next step IMO would be to interrogate each of the USB serial ports created using the CI-V. ie to differentiate between Icom rig models. Then use that info to name the relevant hardware. My USB serial port on the Icom is /dev/icom9100a for example, but I do that through udev, not manual naming.

I'd suggest though that it is simpler to just leave both rigs on, or hot unplug/plug them in the same order if things get messed up. That will also enumerate the same audio/codec port number. Additionally I'd suggest only adjust pavucontrol as a last resort.

At some stage with both rigs connected issue the terminal command "pactl list" to verify the sound port names I have used below.

The fldigi start commands (which can be entered in a terminal window) might then be;

PULSE_SINK=alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo PULSE_SOURCE=alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo /usr/local/bin/fldigi --home-dir /home/<user>/.fldigi.ic705

and

PULSE_SINK=alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-01.analog-stereo PULSE_SOURCE=alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-01.analog-stereo /usr/local/bin/fldigi --home-dir /home/<user>/.fldigi.ic7300

Somewhere before there you might also need to create a device link for the serial ports so that fldigi "sees" a name like /dev/ic7300a and /dev/ic705a. Not a problem though if both rigs always powered and plugged in at the same ports.

Sorry its getting kind of complex, but happy to elaborate or take off list.

Cheers Bob VK2YQA


On 18/4/24 04:48, Philip Rose, GM3ZZA via groups.io wrote:

Thanks Bob,

The two icoms get enumerated ok, but the enumeration changed after a reboot. Probably as a result of adding the IC705 after the previous reboot. It seems to be stable since.

The two FLdigi instances identify themselves to pulseaudio as the same.

It's the understanding how to enscript this that I lack.

Phil GM3ZZA
Re: #sound Connecting multiple rigs. #sound #fldigi

 

开云体育

Hi Phil

Enumeration depends on the polling order of the PC and whether the rig(s) are on at the time. If both rigs are on every time you reset the PC's USB bus and the plugs remain in the same sockets they will get the same "number" "order". In most cases then cycling a single rig's power off/on will bring back the same "number", but it kind of depends on how it dies. Sometimes you'll get an entirely new "number".

I hope I made that clear hihi. I think being aware of the reason is important.

If one wanted full automation and perfect response every time the next step IMO would be to interrogate each of the USB serial ports created using the CI-V. ie to differentiate between Icom rig models. Then use that info to name the relevant hardware. My USB serial port on the Icom is /dev/icom9100a for example, but I do that through udev, not manual naming.

I'd suggest though that it is simpler to just leave both rigs on, or hot unplug/plug them in the same order if things get messed up. That will also enumerate the same audio/codec port number. Additionally I'd suggest only adjust pavucontrol as a last resort.

At some stage with both rigs connected issue the terminal command "pactl list" to verify the sound port names I have used below.

The fldigi start commands (which can be entered in a terminal window) might then be;

PULSE_SINK=alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo PULSE_SOURCE=alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo /usr/local/bin/fldigi --home-dir /home/<user>/.fldigi.ic705

and

PULSE_SINK=alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-01.analog-stereo PULSE_SOURCE=alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-01.analog-stereo /usr/local/bin/fldigi --home-dir /home/<user>/.fldigi.ic7300

Somewhere before there you might also need to create a device link for the serial ports so that fldigi "sees" a name like /dev/ic7300a and /dev/ic705a. Not a problem though if both rigs always powered and plugged in at the same ports.

Sorry its getting kind of complex, but happy to elaborate or take off list.

Cheers Bob VK2YQA


On 18/4/24 04:48, Philip Rose, GM3ZZA via groups.io wrote:

Thanks Bob,

The two icoms get enumerated ok, but the enumeration changed after a reboot. Probably as a result of adding the IC705 after the previous reboot. It seems to be stable since.

The two FLdigi instances identify themselves to pulseaudio as the same.

It's the understanding how to enscript this that I lack.

Phil GM3ZZA
Re: #sound Connecting multiple rigs. #sound #fldigi

 

Thanks Bob,

The two icoms get enumerated ok, but the enumeration changed after a reboot. Probably as a result of adding the IC705 after the previous reboot. It seems to be stable since.

The two FLdigi instances identify themselves to pulseaudio as the same.

It's the understanding how to enscript this that I lack.

Phil GM3ZZA



On 17 April 2024, at 17:25, "Bob Cameron, VK2YQA" <bob3bob3@...> wrote:


Hi Phil

Some info for your situation - I use a pulseaudio environment startup to distinguish between between an Icom and QDX. (The Exec command in a desktop file) eg

/bin/sh -c "PULSE_PROP_APPLICATION_NAME=FLDIG PULSE_SINK=alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo PULSE_SOURCE=alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo /usr/local/bin/fldigi"

/bin/sh -c "PULSE_PROP_APPLICATION_NAME=FLQDX PULSE_SINK=alsa_output.usb-QRP_Labs_QDX_Transceiver-02.analog-stereo PULSE_SOURCE=alsa_input.usb-QRP_Labs_QDX_Transceiver-02.analog-stereo /usr/local/bin/fldigiqdx --home-dir /home/bcameron/.fldigi.qdx"

One would assume that for two Icom radios with the same codec hardware would be numbered CODEC-00 and CODEC-01. The above then removes the need to use pactl or pavucontrol to link app<>port

Pulseaudio is suppose to remember each applications volume etc settings based on (I think) an application name provided by the application itself. I haven't delved into why but that doesn't seem to happen with fldigi. I don't think the PULSE_PROP_APPLICATION_NAME=FLDIG works either.

load-module module-device-manager probably has to be done in /etc/pulse/system.pa or the equivalent user location

Cheers Bob VK2YQA


On 18/4/24 00:21, Philip Rose, GM3ZZA via wrote:
Making some progress. I'm now in the maze of twisty little passages all alike.

I reverted to selecting PortAudio->pulse in fl;digi.

I found where I can connect a specific instance of fldigi to the specific audio codecs. Obvious really. Under the playback and recording tabs of pavucontrol, I can attach each app to a different code. Two problems:

1. The two apps are both called "ALSA  plug-in [fldigi]" and the two codecs are called "PCM2901 Audio Codec Analog Stereo". 
2. When I make the connections they don't survive restarting fldigi.

Yesterday I managed to rename the codecs (at least for displaying in pavucontrol). The names had reverted today. But just typing: 
pactl load-module module-device-manager 
in the terminal caused the names to reappear. Just need to be able to identify which instance of fldigi is which. But as I will usually only be using one at a time, it's no longer a big deal.

1701 - 1720 of 54087