开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: Next version FLdigi

 

开云体育

I am sorry Vladimir, but the macro parser does not include conditional execution.? That is an interesting idea.

David

On 5/24/24 11:55, Vladimir, RW6AVK wrote:

Hi David!

How can I implement a macros, for example?
IF <MODEM:FELDHELL> THEN <EQSL>?
Is it possible to process a condition in a macro?

TNX



Re: #flrig #icom7300 Restoring data incorrectly #flrig #icom7300

 

On Fri, 24 May 2024 08:35:27 -0700
"Philip Rose, GM3ZZA via groups.io" <gm3zza@...>
wrote:

flrig version 2.0.05.45
Maybe 2.0.05.51 will be different?

--

Brian G8SEZ


Re: Next version FLdigi

 

Hi David!

How can I implement a macros, for example?
IF <MODEM:FELDHELL> THEN <EQSL>?
Is it possible to process a condition in a macro?

TNX


Re: #flrig #icom7300 Restoring data incorrectly #flrig #icom7300

Cliff, AE5ZA
 

开云体育

Phil,

Try unchecking the individual boxes for parameters on the Restore config page. Those items are the ones that are restored when you quit flrig.

73,
Cliff, AE5ZA



On May 24, 2024, at 10:39, Philip Rose, GM3ZZA via <gm3zza@...> wrote:

What I've also noticed is that when I close flrig it changes the rig to the state before it was started, which is not what I want. For example I was tuned to 10 MHz it change to 24 MHz

Phil.







Re: #flrig #icom7300 Restoring data incorrectly #flrig #icom7300

 

What I've also noticed is that when I close flrig it changes the rig to the state before it was started, which is not what I want. For example I was tuned to 10 MHz it change to 24 MHz

Phil.


#flrig #icom7300 Restoring data incorrectly #flrig #icom7300

 

I have been having a lot of inconvenience with the filter settings changing even though I change them back.

I have got a fairly repeatable situation now that changes FIL1 CW from 400~1600 to 350~1550 when I start Flrig.

What I see in the trace file is (first commands being sent across:

15:17:39.136 : getID()
15:17:39.136 : WriteBuffer: FE FE 94 E0 19 00 FD
15:17:39.138 : ReadBuffer [2.100000 msec]:
15:17:39.139 : ReadBuffer [0.005000 msec]: FE FE E0 94 19 00 94 FD
15:17:39.139 : set_pbt_outer()
15:17:39.139 : WriteBuffer: FE FE 94 E0 14 08 01 89 FD
15:17:39.141 : ReadBuffer [2.127000 msec]: FE FE E0 94 FB FD
15:17:39.142 : S: FE FE 94 E0 14 08 01 89 FD R: FE FE E0 94 FB FD
15:17:39.142 : set_pbt_inner()
15:17:39.142 : WriteBuffer: FE FE 94 E0 14 07 01 89 FD
15:17:39.144 : ReadBuffer [2.122000 msec]:
15:17:39.145 : ReadBuffer [0.004000 msec]: FE FE E0 94 FB FD
15:17:39.145 : S: FE FE 94 E0 14 07 01 89 FD R: FE FE E0 94 FB FD

I have the box "Use xcvr data" checked so I do not expect to see any values being updated. The above case was one that didn't change my setting: in the case where the setting was changed the values sent to the IC-7300 were 0179 rather than 0189.

flrig version 2.0.05.45


73 Phil GM3ZZA


Re: FLRIG - Is it possible to lock down the USB port?

 

开云体育

Hi Gary / team,

Glad you are working with MacOS - MacLogger does check for the right ports (and will keep them constant, as long as you do not reboot).? I use a MacMini (with Arm Silicon) as well as a iMac - my advice is, leave the MacMini on 24/7.

My use case is to have FLRig manage rig control (and I have 3 HF rigs - so 3 configs) - I use RumLog, and the JS8Call interface i believe is the same as JT8.? In the Logs, I manually set the output levels.? Frankly, it's not that critical, but nice for future?reference (and I use Gridtracker to pump the contact data over to CloudLog and other on-line logs (Clublog, HRD, QRZ, and LOTW).

Sadly, macOS does not have 'udev rules' - which I use (on linux) to interrogate the attached devices, create symbolic links, and bind to predictable ports.? On my other OS's, I just FLrig for rig control as well - and scripts to assign the correct audio devices to each rig.

Fun stuff - 73's - share what you develop!



Glenn
WA6BJQ



From: [email protected] <[email protected]> on behalf of Gary WA4YMZ via groups.io <wa4ymz@...>
Sent: Monday, May 20, 2024 4:18 PM
To: [email protected] <[email protected]>
Subject: Re: [linuxham] FLRIG - Is it possible to lock down the USB port?
?

Hi, Glenn.

?

I’m running Sonoma 14.5.

?

That’s a shame that I can’t assign a specific port for FLRIG or, rather, that what the Mac Mini sees changes from one to the other.? Still, it is a small thing and easily corrected in moments.

?

My next challenge will be setting up logging.? I’ve installed MacLoggerDX but am not using it for rig control, simply as a logger.? The problem I’m having with that is MLDX is receiving the information from both FLDIGI and JS8CALL but logging 0W instead of the 40W I’m using.? I suppose I could just use MLDX for rig control but from what I’ve seen that is problematic when also using digital modes.

?

Oh, well, I’ve just recently begun my transition to Mac OS and the Mac Mini as my daily driver so hopefully, in time, I’ll get this all figured out.

?

Thanks for the reply.

?

73,

Gary

?

From: [email protected] <[email protected]> on behalf of Glenn Jensen, WA6BJQ via groups.io <WA6BJQ@...>
Date: Monday, May 20, 2024 at 12:30
?PM
To: [email protected] <[email protected]>
Subject: Re: [linuxham] FLRIG - Is it possible to lock down the USB port?

Hi Gary....

Are you using macOS (the cu.SLAB seems to suggest that)... macOS does not 'wire' a USB port to? a specific port (on reboot).??

I use 'em all - and normally, I use Linux and have routines to assign to specific ports based on the ID from the serial connection from the rig.

Either way - the Mac rocks on rig control / logging - the FL series is great, and you can throw in RumLog, CloudLog, GridTracker, WSJT-x/JTD-x, et.al.

73's,

?

?

?

Glenn

WA6BJQ

?

?


From:[email protected] <[email protected]> on behalf of Gary WA4YMZ via groups.io <wa4ymz@...>
Sent:?Sunday, May 19, 2024 10:50 AM
To:[email protected] <[email protected]>
Subject:?[linuxham] FLRIG - Is it possible to lock down the USB port?

?

Since mmoving over from Windows and a computer with a "real" serial port, I have noticed that sometimes FLRIG fails to init because it is looking for the incorrect port.? For example, sometimes it is set to /dev/cu.SLAB_USBtoUART and I have to change it to /dev/cu.SLAB_USBtoUART2 and other times, if it is already set to /dev/cu.SLAB_USBtoUART2, I have to set it to /dev/cu.SLAB_USBtoUART.? In both situations, after I make the update and click Init everything works great.

Radio is FTdx10 connected to computer via USB cable
(another USB cable is providing Port Audio to a SignaLink USB)
Computer is M1 Mac-mini running Sonoma 14.5
FLRIG is rev 2.0.05.45
FLDIGI is rev 4.2.05.15

I have another question about logging in FLDIGI, but I'll save that for another day.? Baby steps and all that. :-)

Thanks!

Gary
WA4YMZ FM05pp


flamp 2.2.12.01 development version posted at

 

开云体育

Index of /alpha/flamp

??? RELAY/OUTPUT FORMAT/GUARD LOCK
???? * Remove misplaced '{}' on Relay repeat loops
???? * Simplified some code
???? * Remove exit() code on non fatal code execution.
???? * Remove header modem condition flags for replay files.
???? * Transfer to FLDIGI a few leading '\n' to separated noise data from FLAMP data
?????? (Cosmetic, FLDIGI receive panel).

73, David,? W1HKJ
for Robert, KK5VD


Re: FLRIG - Is it possible to lock down the USB port?

 

开云体育

Hi, Glenn.

?

I’m running Sonoma 14.5.

?

That’s a shame that I can’t assign a specific port for FLRIG or, rather, that what the Mac Mini sees changes from one to the other.? Still, it is a small thing and easily corrected in moments.

?

My next challenge will be setting up logging.? I’ve installed MacLoggerDX but am not using it for rig control, simply as a logger.? The problem I’m having with that is MLDX is receiving the information from both FLDIGI and JS8CALL but logging 0W instead of the 40W I’m using.? I suppose I could just use MLDX for rig control but from what I’ve seen that is problematic when also using digital modes.

?

Oh, well, I’ve just recently begun my transition to Mac OS and the Mac Mini as my daily driver so hopefully, in time, I’ll get this all figured out.

?

Thanks for the reply.

?

73,

Gary

?

From: [email protected] <[email protected]> on behalf of Glenn Jensen, WA6BJQ via groups.io <WA6BJQ@...>
Date: Monday, May 20, 2024 at 12:30
?PM
To: [email protected] <[email protected]>
Subject: Re: [linuxham] FLRIG - Is it possible to lock down the USB port?

Hi Gary....

Are you using macOS (the cu.SLAB seems to suggest that)... macOS does not 'wire' a USB port to? a specific port (on reboot).??

I use 'em all - and normally, I use Linux and have routines to assign to specific ports based on the ID from the serial connection from the rig.

Either way - the Mac rocks on rig control / logging - the FL series is great, and you can throw in RumLog, CloudLog, GridTracker, WSJT-x/JTD-x, et.al.

73's,

?

?

?

Glenn

WA6BJQ

?

?


From:[email protected] <[email protected]> on behalf of Gary WA4YMZ via groups.io <wa4ymz@...>
Sent:?Sunday, May 19, 2024 10:50 AM
To:[email protected] <[email protected]>
Subject:?[linuxham] FLRIG - Is it possible to lock down the USB port?

?

Since mmoving over from Windows and a computer with a "real" serial port, I have noticed that sometimes FLRIG fails to init because it is looking for the incorrect port.? For example, sometimes it is set to /dev/cu.SLAB_USBtoUART and I have to change it to /dev/cu.SLAB_USBtoUART2 and other times, if it is already set to /dev/cu.SLAB_USBtoUART2, I have to set it to /dev/cu.SLAB_USBtoUART.? In both situations, after I make the update and click Init everything works great.

Radio is FTdx10 connected to computer via USB cable
(another USB cable is providing Port Audio to a SignaLink USB)
Computer is M1 Mac-mini running Sonoma 14.5
FLRIG is rev 2.0.05.45
FLDIGI is rev 4.2.05.15

I have another question about logging in FLDIGI, but I'll save that for another day.? Baby steps and all that. :-)

Thanks!

Gary
WA4YMZ FM05pp


correction to flrig posting

 

开云体育

change fldigi.files to flrig.files

David


flrig 2.0.05.51 development test release posted at

 

开云体育

Index of /alpha/flrig



See readme.txt for changes.?

This version allows you to more fully change and manage the user interface style and colors.



This is an example of a dark scheme.? UI schemes are saved in separate <NAMED>.UI.prefs files which can be saved, restored, and shared between flrig instances.? This dark scheme is defined in the file "darkscheme.UI.prefs" which you can download.

Before trying you should
  • start flrig
  • select Config/UI/Save prefs to save your current color scheme.? Either use 'default' or name it to indicate it's characteristics.
  • save the downloaded file, darkscheme.UI.prefs to the fldigi files folder (on Windows it is the folder flrig.files in you home folder)
  • select Config/UI/Load prefs and select the darkscheme file.

I've tested this by transferring the darkscheme.UI.prefs file to a Windows, and a MacOS computer from the original Linux test computer.

73, David, W1HKJ



CTY-3417 Country Files - 20 May 2024

 

The Country (CTY) Files were updated on 20 May 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 May 2024 (CTY-3417)
VER20240520, Version entity is Qatar, A7

Added/changed Entities/Prefixes/Callsigns:

* 9M1Z is East Malaysia, 9M6
* G6ICR is Isle of Man, GD
* GB9DAT is Scotland, GM
* HK4X/HK0 is Colombia, HK
* W5LFA is Guam, KH2
* KJ7ZCW is Hawaii, KH6
* K8K is American Samoa, KH8
* AK6GS is Alaska, KL
* KJ4PMZ is Puerto Rico, KP4
* LU1DSO/D, LU1DUA/D, LU1HAK/H, LU1HC/H, LU1HRA/H, LU1HYW/H, LU3DXG/D,
LU3HAT/H, LU3IG/I, LU8EMD/D, LW2DMD/D, LW6DGI/D and LW6DNF/D are all Argentina, LU
* LU1WP/W, LU1XOP/V, LU3VAL/V, LU5YBJ/Y, LU7VFM/V and LU7VRC/V are all Argentina, LU in ITU zone 16
* PD0ARI/MILL is Netherlands, PA
* R119MS, RM0F/6 and UE39MS are all European Russia, UA
* R2BW/9 is Asiatic Russia, UA9 in CQ zone 18, ITU zone 32

Removed Entities/Prefixes/Callsigns:

* AT42I in Antarctica, CE9
* TO5LA in Mayotte, FH
* TO7O in Martinique, FM
* TX5XG in Austral Islands, FO/a
* TO8AN in St. Martin, FS
* GB0SSB in Scotland, GM
* GB2WAA in Wales, GW
* K4RFT, KA9FRH and NH2JE in United States, K
* KF6PHC and N3GWR in Hawaii, KH6
* K5GEC, KE6FNQ, KJ7IXG and KJ7OLX in Alaska, KL
* LU1EQF/D in Argentina, LU
* R2014RK, R2014SE, R9HAF/6 and RI0SP in European Russia, UA
* R75SHK, R9CS/P, RV3DSA/0 and RW6MD/0 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 - Is it possible to lock down the USB port?

 

开云体育

Hi Gary....

Are you using macOS (the cu.SLAB seems to suggest that)... macOS does not 'wire' a USB port to? a specific port (on reboot).??

I use 'em all - and normally, I use Linux and have routines to assign to specific ports based on the ID from the serial connection from the rig.

Either way - the Mac rocks on rig control / logging - the FL series is great, and you can throw in RumLog, CloudLog, GridTracker, WSJT-x/JTD-x, et.al.

73's,



Glenn
WA6BJQ



From:[email protected] <[email protected]> on behalf of Gary WA4YMZ via groups.io <wa4ymz@...>
Sent:?Sunday, May 19, 2024 10:50 AM
To:[email protected] <[email protected]>
Subject:?[linuxham] FLRIG - Is it possible to lock down the USB port?
?
Since mmoving over from Windows and a computer with a "real" serial port, I have noticed that sometimes FLRIG fails to init because it is looking for the incorrect port.? For example, sometimes it is set to /dev/cu.SLAB_USBtoUART and I have to change it to /dev/cu.SLAB_USBtoUART2 and other times, if it is already set to /dev/cu.SLAB_USBtoUART2, I have to set it to /dev/cu.SLAB_USBtoUART.? In both situations, after I make the update and click Init everything works great.

Radio is FTdx10 connected to computer via USB cable
(another USB cable is providing Port Audio to a SignaLink USB)
Computer is M1 Mac-mini running Sonoma 14.5
FLRIG is rev 2.0.05.45
FLDIGI is rev 4.2.05.15

I have another question about logging in FLDIGI, but I'll save that for another day.? Baby steps and all that. :-)

Thanks!

Gary
WA4YMZ FM05pp


FLRIG - Is it possible to lock down the USB port?

 

Since mmoving over from Windows and a computer with a "real" serial port, I have noticed that sometimes FLRIG fails to init because it is looking for the incorrect port.? For example, sometimes it is set to /dev/cu.SLAB_USBtoUART and I have to change it to /dev/cu.SLAB_USBtoUART2 and other times, if it is already set to /dev/cu.SLAB_USBtoUART2, I have to set it to /dev/cu.SLAB_USBtoUART.? In both situations, after I make the update and click Init everything works great.

Radio is FTdx10 connected to computer via USB cable
(another USB cable is providing Port Audio to a SignaLink USB)
Computer is M1 Mac-mini running Sonoma 14.5
FLRIG is rev 2.0.05.45
FLDIGI is rev 4.2.05.15

I have another question about logging in FLDIGI, but I'll save that for another day.? Baby steps and all that. :-)

Thanks!

Gary
WA4YMZ FM05pp


flrig color configuration

 

开云体育

I am working on the color / scheme selection dialogs for flrig.? The result will no doubt pass the Abe Lincoln test, "You can please some of the people..."

This dark scheme will be possible with the changes:



73, David, W1HKJ


Re: [winfldigi] Fldigi "not working" with QMX - two issues solved

Cliff, AE5ZA
 

开云体育

Bob,

Interesting suggestions. I've been using a QDX for some time and it does pretty much all the modes it should do with little config changes. Rise/Fall - 80/60, Min. Samples 180, TX Shift - 0.

Tried your suggestions on the QMX and no go. The Audio processing was changed in item #12 in QMX Firmware update 007. From then on it was broken except for a few modes like Thor as Dave indicated by his testing. The new 018 firmware didn't change anything for digital modes including unable to use TxID without it killing TX after the ID.

73,
Cliff, AE5ZA



On May 16, 2024, at 12:00, Bob Cameron, VK2YQA via <bob3bob3@...> wrote:

Hi Dave, more to help with your testing rather than the L-R issue.

The TX "failure" for such MFSK audio as Olivia/Contestia/Thor/MFSK/Domino/IKFP/FSQ/RSID is "fixed" by reducing the QDX (and I assume QMX) minimum samples from the 480 default to something like 120-180. I also reduce the rise/fall times (2/40) to stop the raise cosine PTT inhibit, otherwise the TX chops on and off. FM picture sub modes are generally not pretty with random like line shifts.

Minimum samples at 120 is however not low enough for Thor 56 or faster/wider. I have a series of command buttons on flrig to change this and the audio level as needed.

The TX audio still sounds a little ragged, but I have had some successful Olivia 8/250 QSO's VK>EU. One day I'll do some SDR s/n threshold testing to see of there is any decode degradation.

Cheers Bob VK2YQA


On 16/5/24 23:38, Dave, W1HKJ wrote:


MODE
TX
COMMENTS
TUNE
yes

CW
no
single dit hears and then silence
CONTESTIA 8-250
no
starting tone and then silence; CONTESTIA uses shaped tones <HK9LwHSLF0nBY0XS.png>
DOMINO-EX
partial

HELL
partial
only FSK 245/105/80; received raster not distinct
MFSK
no
tx ends after first tone
MT63
no
amplitude/phase modulation
OFDM
no
amplitude/phase modulation
OLIVIA
no
tx ends after first tone
PSK, QPSK, 8PSK,PSKR
no
amplitude/phase modulation
RTTY
yes

THOR
partial
Micro, 4, 5, 8, 11 & 16;? higher baud rates the QMX does not follow the transition
THROB
no
amplitude/frequency modulation
?



Re: [winfldigi] Fldigi "not working" with QMX - two issues solved

 

开云体育

Hi Dave, more to help with your testing rather than the L-R issue.

The TX "failure" for such MFSK audio as Olivia/Contestia/Thor/MFSK/Domino/IKFP/FSQ/RSID is "fixed" by reducing the QDX (and I assume QMX) minimum samples from the 480 default to something like 120-180. I also reduce the rise/fall times (2/40) to stop the raise cosine PTT inhibit, otherwise the TX chops on and off. FM picture sub modes are generally not pretty with random like line shifts.

Minimum samples at 120 is however not low enough for Thor 56 or faster/wider. I have a series of command buttons on flrig to change this and the audio level as needed.

The TX audio still sounds a little ragged, but I have had some successful Olivia 8/250 QSO's VK>EU. One day I'll do some SDR s/n threshold testing to see of there is any decode degradation.

Cheers Bob VK2YQA


On 16/5/24 23:38, Dave, W1HKJ wrote:



MODE
TX
COMMENTS
TUNE
yes

CW
no
single dit hears and then silence
CONTESTIA 8-250
no
starting tone and then silence; CONTESTIA uses shaped tones
DOMINO-EX
partial

HELL
partial
only FSK 245/105/80; received raster not distinct
MFSK
no
tx ends after first tone
MT63
no
amplitude/phase modulation
OFDM
no
amplitude/phase modulation
OLIVIA
no
tx ends after first tone
PSK, QPSK, 8PSK,PSKR
no
amplitude/phase modulation
RTTY
yes

THOR
partial
Micro, 4, 5, 8, 11 & 16;? higher baud rates the QMX does not follow the transition
THROB
no
amplitude/frequency modulation
?


Re: [winfldigi] Fldigi "not working" with QMX - two issues solved

 

开云体育

Well, that is bad news.? Installed 1.00.018 and just started to test when the QMX went up in smoke.? Literally !! Stinks !!? I now have one available for parts.? Anyone want one for the price of the postage?

David

On 5/16/24 11:09, Dave wrote:

Board revision V1, firmware 1.00.017.

I will update the firmware and retest.

David

On 5/16/24 10:11, ok4rm wrote:
Hi, David,
thank you for the very interesting observations. As for the left channel: Cliff, AE5ZA, mentioned that "it worked" until firmware 1.0.0.7. Which version do you have? And which board revision? Mine is V2 and started at FW version 1.0.0.14 IIRC, now I have 1.0.0.18. This issue with the right channel seems to be common to different transceivers (for me: Digirig Mobile + TS-480) and maybe, then, I have something wrong in the Windows audio setup and it just prevents any output on the left channel. I'll have to check that (if I only knew how :) ). OTOH, there seem to be many other QMX users who complain that their tcvr generates zero output on RTTY with fldigi.?

As for the CW generated as audio in QMX digi mode, I have the same experience: when VOX is ON, it transmits more or less normal CW. When I switch VOX OFF, switch to transmit using CAT command, as soon as the first audio element is finished, it switches to RX mode and does not transmit any more. This seems to be a bug, I already reported to Hans.

As for the levels, yes, I use 0 dB output level everywhere. My issue was indeed due to the right channel "not included" in fldigi.

73! Jindra

On Thu, May 16, 2024 at 03:38 PM, Dave wrote:
Good morning Jindra,

After receiving your email solutions I put my QMX on line and retested.? My findings are not the same as yours.

Issue #1: my QMX expects to receive the audio on the LEFT channel and not the RIGHT channel.



The audio drive to the QMX must be of sufficient amplitude for the QMX to detect the audio frequency.? Set the OS audio output to provide maximum drive and then set this control to 0 dB:



Testing the QMX into a dummy load and listening and decoding on an FT-710 with flrig/fldigi; the various digital modes behave thuslyL

MODE TX COMMENTS
TUNE yes ?
CW no single dit hears and then silence
CONTESTIA 8-250 no starting tone and then silence; CONTESTIA uses shaped tones
DOMINO-EX partial ?
HELL partial only FSK 245/105/80; received raster not distinct
MFSK no tx ends after first tone
MT63 no amplitude/phase modulation
OFDM no amplitude/phase modulation
OLIVIA no tx ends after first tone
PSK, QPSK, 8PSK,PSKR no amplitude/phase modulation
RTTY yes ?
THOR partial Micro, 4, 5, 8, 11 & 16;? higher baud rates the QMX does not follow the transition
THROB no amplitude/frequency modulation
?
Any attempt at transmiting a leading RsID signal results in a loss of transmission immediately after the RsID signal.

Issue #2:? use flrig with fldigi


The "RF" control is simply a gain control for the QMX transceiver.? It provides a very wide range of input signal amplification.? I usually set mine between 80 and 90 depending on the band and antenna in use.

73, David

On 5/16/24 02:37, ok4rm wrote:
Issue #1: QMX is in TX mode, but there is no output despite fldigi generating signal

SOLUTION:? "The only right channel is the right channel" (not mentioned in QMX Operation manual, though). BTW I had the same problem with TS-480 & Digirig mobile, in general this applies to any interface (USB or other) which uses only the right channel for AFSK input into the transceiver. Unlike other programs which show options like "Mono" or "L+R" when setting up soundcard (JTDX, JS8Call, VARA etc.), fldigi is not so straightforward.



Issue #2: QMX receives signal (and it can be heard in headphones), but there is no waterfall in fldigi no matter what threshold settings for the waterfall you choose. Signal level indicator in fldigi shows noise level at about -100 dB and incoming signal in peaks does not exceed minimum level needed for detection, for instance does not exceed -80 dB. This issue is very confusing due to the fact that other digi programs (such as JS8Call, which I used to test this) seem to find this signal level satisfactory, detect signals and show usual waterfall picture.

IMMEDIATE SOLUTION: on QMX open menu, Audio/AGC settings/AGC = OFF. Or, you can tweak your AGC settings until you achieve at least -50 dB audio level supplied to fldigi input.

LONG TERM SOLUTION:
?Variant 1: modify fldigi to automatically adjust for the level needed for detection (a kind of digital AGC or digital amplification, to amplify the signal to move the peak level e.g. to -20 dB for weak audio signal)
?Variant 2: modify QMX firmware to adjust output level presented to the audio interface just in the USB path (such as? shift left a couple of bits) so that the peak level is never less than, let's say, -60 dB.
(both variants would be welcome, but either one should suffice).

Yes, I know it is not good manner to tell software developers how they should do their work, I apologize! Just wanted to decrease level of frustration among the users of both fldigi and QMX :)

--
73 de Jindra OK4RM, OM0RM



Re: Next version FLdigi

 

开云体育

Would be simple to export the fldigi NOTES field as COMMENT field.? Or external program could perform the field renaming.

David

On 5/16/24 10:06, Vladimir, RW6AVK wrote:

Good day David.

Colleagues asked to add the <COMMENT> tag () to the ability to send via UDP. I'm not sure this will be done. It's just a wish.

TNX


Re: Next version FLdigi

 

开云体育

NOTES is an available field for export



// These ADIF fields are not in the fldigi QSO database
/*
??????? {COMMENT,????? 256,?? "COMMENT",????? NULL},??????????????? // comment field for QSO
??????? {ADDRESS,????? 256,?? "ADDRESS",????? NULL},??????????????? // contacted stations mailing ad
dress
??????? {PFX,????????? 20,??? "PFX",????????? NULL},??????????????? // WPA prefix
??????? {PROP_MODE,??? 100,?? "PROP_MODE",??? NULL},??????????????? // propogation mode
??????? {QSL_MSG,????? 256,?? "QSL_MSG",????? NULL},??????????????? // personal message to appear on
?qsl card
??????? {QSL_RCVD,???? 4,???? "QSL_RCVD",???? NULL},??????????????? // QSL received status
??????? {QSL_SENT,???? 4,???? "QSL_SENT",???? NULL},??????????????? // QSL sent status
??????? {QSL_VIA,????? 20,??? "QSL_VIA",????? NULL},??????????????? // QSL via this person
??????? {RX_PWR,?????? 8,???? "RX_PWR",?????? NULL},??????????????? // power of other station in watts
??????? {SAT_MODE,???? 20,??? "SAT_MODE",???? NULL},??????????????? // satellite mode
??????? {SAT_NAME,???? 20,??? "SAT_NAME",???? NULL},??????????????? // satellite name
};

David

On 5/16/24 10:06, Vladimir, RW6AVK wrote:

Good day David.

Colleagues asked to add the <COMMENT> tag () to the ability to send via UDP. I'm not sure this will be done. It's just a wish.

TNX