Never heard on the question of the entry fields not clearing when logging the contact.? Any help out there on what setting could be messed up??

--

Karl
K0CIE

Nobody ever got an answer here did they? I had to reinstall mine (FLRig 1.4.7.46) from scratch and almost didn't get it working, I had to change the write time above the Init button to get it to connect, and when it did on FT1000MP it reads some kind of crazy number versus what is on the actual dial of the radio. I changed to FT1000MP-A and it reads correctly. I attempted to update to FLRig 2.0.05 and it quit working all together, no matter what I've tried. So I guess I'm just going to stick with 1.4.7.46 or Hamlib.?

Jack,

Along the same lines....yesterday I installed a second instance of fldigi onto my Windows 10 machine.? I now have one instance (original) working with my TS590SG using Rig CAT XML file and the second instance for my ICOM 9700 using flRIG.? I only want to run one at a time. When I double click on the new second instance, it does not launch right away.? When I double click again, it launches but eventually two versions show up, and one does not close on closing the window.? I kill the task via Windows 10.

?

But, on the second instance, if I right click on the icon (instead of a double click), and then select open, it launches OK, runs OK, and closes OK.

?

Just some data for the heap, LOL.

?

Joe, K1YOW

?

--------------------

From: "Jack Spitznagel (KD4IZ)" <kd4iz@...>
Reply-To: <[email protected]>
To: <[email protected]>
Sent: February 22, 2025 at 10:46 AM EST
Subject: [winfldigi] Potential Bug? fldigi instances not closing out in Windows

Mostly addressed to Dave (W1HKJ) but also looking for others experiences:

?

Scenario:

I am now running current alphas of fldigi and flrig (autostarted) on a gamer Win11 workstation, but have seen this issue? going back several "final" releases and on a Win10 workstation. I use multiple instances of fldigi talking to a single instance of flrig because flrig can do KISS protocol and can control a single rig for multiple instances of fldigi looking at that rigs sound CODEC stream.

?

Before the "frequent commentators" ask, I have had poor luck setting up the other rig control engine because they either did not work at all for my use case or were a mess to configure. I have seen the problem with the other control engines. I will be using flrig.

?

I can start a single instance of fldigi with flrig and they will close out normally most always. The trouble does start after long (days) running the apps.

?

When two or more instances are running with or without flrig, I can almost always shut down the second instances, but the primary instance will shut down (autostarted) flrig but then hang and require one the "messy exit" routines to kill the hung process. This problem happens very often as quickly as 15 minutes or less after the programs are started.

?

Quite a while ago I tried capturing the hang event unsuccessfully - probably because the hang suspended the debug logging writes?

?

@Dave: What is best way to log this event when it happens?

?

@All: have you seen this same scenario when running multiple instances of fldigi either with separate instances of flrig (as in for two different radios) or a single instance of flrig hosting multiple instances of fldigi?

?

Jack Spitznagel

KD4IZ - FM19OO

Parkton, MD

Mostly addressed to Dave (W1HKJ) but also looking for others experiences:

?

Scenario:

I am now running current alphas of fldigi and flrig (autostarted) on a gamer Win11 workstation, but have seen this issue? going back several "final" releases and on a Win10 workstation. I use multiple instances of fldigi talking to a single instance of flrig because flrig can do KISS protocol and can control a single rig for multiple instances of fldigi looking at that rigs sound CODEC stream.

?

Before the "frequent commentators" ask, I have had poor luck setting up the other rig control engine because they either did not work at all for my use case or were a mess to configure. I have seen the problem with the other control engines. I will be using flrig.

?

I can start a single instance of fldigi with flrig and they will close out normally most always. The trouble does start after long (days) running the apps.

?

When two or more instances are running with or without flrig, I can almost always shut down the second instances, but the primary instance will shut down (autostarted) flrig but then hang and require one the "messy exit" routines to kill the hung process. This problem happens very often as quickly as 15 minutes or less after the programs are started.

?

Quite a while ago I tried capturing the hang event unsuccessfully - probably because the hang suspended the debug logging writes?

?

@Dave: What is best way to log this event when it happens?

?

@All: have you seen this same scenario when running multiple instances of fldigi either with separate instances of flrig (as in for two different radios) or a single instance of flrig hosting multiple instances of fldigi?

?

Jack Spitznagel

KD4IZ - FM19OO

Parkton, MD

correction...correction

i copies and pasted wrong info..

here is correct..

jim

?

Hi Jack, yes I did get some ideas and also reread the manual and now my qmx will operate with FT8CN for ultra portable operating. I will let you know if I get it working with fldigi. I want to use it in areas where I can carry the laptop, I would like to use Feldhell and Olivia for some park activations. I wish there was an android app for the other digi modes for going portable.

?

Randy

VE3JO

Thanks for the help, I understand how to do it and have created a second path for my QMX. When I get home this evening I will get it connected and hopefully setup and running.

?

Randy

VE3JO

Hello Randy,

Please refer to my topic 2 below.

Regardless of the OS version, by creating different shortcuts referencing to different data folders, you can configure and run 'independent' instances of a single standard fldigi program installation.

Note the renark about 'TX' though!


Good Luck!


73s Tobias
.-.-.



FLdigi Easy Living - a few practical remarks...


Hello FLdigi Users,


This concise information is for those seeking to restore Basic FLdigi (programs family) Functionality, usually after a program or operating system update, or simply interested in a Portable Installation. Other topics mentioned below include operating multiple FLdigi Instances, FLdigi Configurations and rearranging Macros.


- - - - - -


1. Portable 'thumb drive' Installation, also useful to Restore Basic FLdigi Functionality (from scratch)...


After several updates (especially when skipping a few releases), or even moving FLdigi from one PC (hardware or OS) to another, configuration files may sometimes become incompatible and cause unintended issues. To overcome this and create a truly 'fresh' basic installation, you may wish to try out the 'FL_APPS' folder install feature. For this to work, it doesn't matter where this FL_APPS folder resides, e.g. a path like 'C:\Apps\Radio\FL_APPS' will do, if FLdigi is installed directly therein.

The special 'FL_APPS' folder feature has originally been programmed into FLdigi in order to allow creating a 'portable' FLdigi installation, e.g. on a memory stick. The key for this to work is this special folder name, which by definition triggers FLdigi, if installed into 'FL_APPS', to place all the necessary config files and others as sub-folders therein, contrary to the 'standard' installation, where the 'fldigi.files' with personal user preferences, macros, logs etc. are generally stored in the classic location 'C:\users\<UserName>fldigi.files' and several sub-folders.

A detailed description can be found in the online 'Fldigi Users Manual 4.2.00', in the chapter 'Installing fldigi on a thumb drive'.
This highly recommended Fldigi Users Manual can also be downloaded separately for local use. It has a 'Contents Index' helping to find your way within.


- - - - - -


2. Multiple FLdigi Instances (intended for use with a standard installation)...


There is a versatile feature which may be useful for various reasons, provided FLdigi is already present and (at least partly) operational on your system.

By creating several different shortcuts, you can, quite independently, configure and use multiple different FLdigi instances on your local hard drive, all using the same FLdigi installation (e.g. fldigi.exe etc).

Caution: In case you apply rig control or transmitting of any kind, make sure that only one (1) single FLdigi instance is active in this respect at any given time!

In the above-mentioned FLdigi documentation, you'll also find a chapter 'Operating Multiple Copies', which involves launching FLdigi via a batch file or shortcut link that includes a command line switch, for example:

--home-dir FOLDER --> Set the home folder to full pathname of FOLDER
fldigi will put the file stores fldigi.files, and nbems.files in this folder
The default is: C:\Users\<UserName>\

--config-dir FOLDER --> Look for configuration files in FOLDER
The default is: C:\Users\<UserName>\fldigi.files\


In practical terms, proceed as follows:

- On the desktop or in your windows file manager, perform a mouse 'right-click' (or hit the 'AppsKey', if available).

- Select 'New -> Shortcut'

- In the 'Create Shortcut' dialog, browse or enter/paste the path to your installed FLdigi.exe file, e.g. 'C:\Apps\Radio\FLdigi\fldigi.exe'.

- Behind this path, after a <SPACE>, enter one of the 'command line switches' as given above, e.g.
'C:\Apps\Radio\FLdigi\fldigi.exe --home-dir C:\Apps\Radio\FLdigi\MyConfig'.


All valid command line switches of your current FLdigi installation can be browsed and written into a text file (as a reference) as follows:

fldigi.exe --help >help.txt

If you can't open a command window directly from within the 'FL_APPS' (or your standard FLdigi) folder, simply write the line above into a plain text file, call it 'gethelp.bat', then run this gethelp.bat and, once complete, open the newly written 'help.txt' in the same folder. This file should contain all the available command line options to choose from.


- - - - - -


3. Verify where FLdigi retrieves and stores configurations, data, and macros...


In case of uncertainty or after using any of the options described above, it's a good idea to verify, directly from the Main Menu, where FLdigi has located (and uses) its respective data.

Menu - File - Folders - Fldigi config... => This will open the respective folder, e.g. 'C:\Users\<UserName>\fldigi.files' for a standard installation.

Menu - File - Macros - Open... => This allows loading a Macro definition saved before, e.g. from 'C:\Users\<UserName>\fldigi.files\macros'.


- - - - - -


4. Config Scripts...


On a related note, once you have defined a functional FLdigi configuration and wish to preserve it for future use, save it as follows:

Menu - Config Scripts - Generate => Save it in a suitable location, e.g. 'C:\Users\<UserName>\fldigi.files\scripts\default_script.txt'.

This may be done several times for various different sets of macros, audio devices, or other settings you use, and it may be recalled again from within FLdigi via:

Menu - Config Scripts - Execute => Open an existing script file, e.g. 'C:\Users\<UserName>\fldigi.files\scripts\USB_Audio_script.txt'. It loads instantly without restarting Fldigi.

Note: Config Scripts are a summarized compact data file which contains all your Macros and numerous other Settings, but not all rather specific ones for individual modes etc. If unsure about a specific setting, open the file and search for it. It may also contain actual file paths (e.g. under NBEMS the one for 'flmsg.exe' and, if defined within Macros, these as well). So if you plan moving an installation around and benefit from re-loading a formerly functional Config Script, make sure to review the script file and adapt your paths to match reality. Searching for ':\' should usually take you to the next path in the definitions, if present. Since the UNIX notation may also be used, also check for ":/" to find further file paths.


- - - - - -


5. How to 'easily' Rearrange Macros...


If you wish to move / rearrange your existing Macros, it is easiest to save your current Config Script as shown above, open it in a plain text editor (e.g. Notepad), and quickly make the necessary changes therein.

Note that the Numbering for the Button Sequence per Macro is quite straightforward, just consisting of the Macro Button Row (1...4, top to bottom), and the Macro Button Column (1...8 per row, left to right). Example for the Top Row (1) and the 3rd Macro Button (column 3):

MACRO:1,3,"THOR25"
<MODEM:THOR25>
END:

Then just swap out or alter the respective numbers between the Macros you wish to rearrange. Don't care about the (then illogical) Macro position in the text, only the numbers allocated to each Macro Definition (e.g. MACRO:1,3,...) actually matters for FLdigi. But keep track separately of what you swap to avoid creating double or missing numbers entries!

Practically, to swap the first top 4 with the next top 4 Macros, change (in sequence top - down, which in fact only means changing a total of 8 digits):

1,1 => 1,5 >>>> this shifts the 4 leftmost Macros to the 4 center Buttons.
1,2 => 1,6
1,3 => 1,7
1,4 => 1,8
1,5 => 1,1 <<<< this shifts the 4 Macros from the center Buttons all the way to the left.
1,6 => 1,2
1,7 => 1,3
1,8 => 1,4

If you wish to swap rows, instead alter the 1st figure accordingly, per Macro Definition.

Save the text file as a new Config Script, e.g. 'C:\Users\<UserName>\fldigi.files\scripts\Macros_Rearranged_2025-02-14.txt'.

In FLdigi, open the modified script file via Menu - Config Scripts - Execute.

Check that everything is and works as intended.

Finally, you may then (once) save the modified script file again via Menu - Config Scripts - Generate. This will automatically 'restore order' in the script file (just for future use, this step is functionally not necessary), by auto-sorting the columns and rows along with their respective Macro definition nicely in their 1...N numerical ascending order. In other words, without any effort, your new Macro sequence is now stored as if you had awkwardly re-sorted everything yourself in the process of the file editing described above.



I hope these few simple concepts may help you use and enjoy FLdigi and Ham Radio even more!


73s SWL Tobias
.-.-.

Could some one please explain to me step by step how to create a second instance of fldigi on windows 11. For some reason I am not grasping the concept. I would like to have another setup for my qmx to use portable.

?

Thank you

Randy

VE3JO

I would also like to point out another technicality about the OFDM modes in FLDigi in general. They technically are just multi-carrier modes, not OFDM. OFDM means that the spacing of the carriers is such that the center frequency of each carrier is located at the zero points (nulls) of each adjacent carrier. This produces a spectrum with a flat top. However, in FLDigi, the so-called OFDM modes are such that the zero points (nulls) of each carrier are located at the nulls of the adjacent carriers. So this makes them actually not true OFDM modes. Please fix this. You could get higher data throughput (or at least reduce the bandwidth) if you were to cut the carrier spacing in half, so that they were true OFDM modes where each carrier was located at the null of the adjacent carriers.

Hi Randy,

First of all, the mismatch between the speed factor displayed on the button and the actually used one is what I had described before, saying 'Note that the figure indicated on the button is not always in synch with the chosen mode'. I don't know why this happens, it might be a bug of some sort. That's why I recommended 'So better try it out before actually going on the air'.


The setting should make a very noticeable difference in TX/RX speed, but while the Button only affects transmission, the reception is adapted automatically, based on the Pic header and its suffix: either none, p2, or p4.

I attach a short audio file that you can play back in FLdigi via File - Audio - Playback (select all files (*.*) and then the audio file), after setting fldigi to MFSK64 at 1500 Hz audio. If should decode 3 (greyscale) images in a row:

PM5544_283x227_MFSK64_Pic_Mode_Test_X1+X2+X4_2025-02-16.ogg <- This is the audio file to test the 3 speeds.
PM5544_283x227.png <- the original image (in color), which was sent as greyscale to have a shorter duration.
pic_2025-02-16_175606z_X1.png <- original speed [Note there's no suffix in the Pic header.]
pic_2025-02-16_175654z_X2.png <- double speed. [Please don't ask me why suffix 'p4' is used for double speed...]
pic_2025-02-16_175721z_X4.png <- quadruple speed. [-... and suffix 'p2' in this case, for quadruple speed. I just don't know.]

You see the degrading decoding quality, as the speed increases? Obviously, you could send a larger image with 4 x the area (WxH) in X4 mode during the same time as the original at standard speed, but then, the overall image quality will not be any better, just the size of the image appears visibly bigger. Note that I have quite intentionally heavily compressed this audio file, leading to an unusually small file and rather poor quality. But this way, it kind of behaves like a (stable and reasonably strong) HF path, giving an idea what a receiving station might see in each of the settings.


Your picture (showing very good reception actually!) doesn't look /skewed/ (or \the other way\), which would indicate a sound card speed calibration issue, but your otherwise straight image has partially shifted sideways, let's call it 'sliced'. This usually happens when the PC is busy doing other 'things' (blame it on multitasking or a bit of an overload of other programs drawing much CPU power) and FLdigi (or even your sound card) momentarily doesn't get the continuous CPU support it needs to convert the image without interruption. Any brief pause in the decoded bitstream (although it's analog via the radio, before the ADC conversion within the sound card) will cause an immediate side shift of the remainder of the image, and possibly a tiny lost portion. I have side-shifted back the respective parts in your screenshot and now it looks quite good. You'll find the original (full) decoded image with a date/time stamp in your data folder under fldigi.files \images. Check the location via Menu - File - Folders... - WEFAX images, and it may be called something like 'pic_2025-02-15_205141z.png'. The full path usually is 'C:\Users\<USER NAME>\fldigi.files\images', unless you have chosen a different location.


You can sometimes find a direct root cause for this image 'slicing' behavior, e.g. WSJT-X suddenly starting to decode something (FT8) in the 'background', or a scanner checking for undesirable files, when an e-mail arrives or a website opens, or the like, just to name a few processes that may draw a lot of system resources. If you have or suspect such an issue, try to stop this interfering process and have FLdigi run as the only 'demanding' application, if possible. You may also try to generally increase the FLdigi process priority, e.g. via the Windows Task Manager, Find 'fldigi' in the Applications list, right-click it and choose 'Go to the process'. In the Processes list, right click fldigi.exe, choose 'Define Priority' and set it to 'High' for example. This may (or may not) have a positive effect, provided it's a software decoding issue, rather than the sound card itself. In the Process Manager, in Processes view, you may also try to find other processes that demand a lot of CPU, if you klick the CPU column to have the list sorted accordingly.


On the other hand, if, during image reception, you mouse click around within FLdigi, e.g. changing the frequency offset, or even click onto the RX image preview, this may also cause such image reception disruptions.


I attach a couple of the views mentioned above as examples:


Re_winfldigi_Sending_Pics_2025-02-16_1631_inline0_A)_original_view.png

Re_winfldigi_Sending_Pics_2025-02-16_1631_inline0_B)_straight_view.png

Re_winfldigi_Sending_Pics_2025-02-16_1631_inline0_C)_straight_image.png

Re_winfldigi_Sending_Pics_2025-02-16_1631_inline0_D)_skewed_L.png

Re_winfldigi_Sending_Pics_2025-02-16_1631_inline0_E)_skewed_R.png


If actual skewing occurs, this is caused by a mismatch between the TX and the RX sound card calibration. An absolute reference can be found by calibrating the RX sound card setting using a precise Time Signal, e.g. WWV. It's described in the FLdigi Help file in the chapter 'WWV codec PPM measurement'.

I also attach my 'FLdigi_Soundcard_ppm_Calibration_Recipe_2024-12-10.zip' in case you need it for yourself or someone else sending /skewed/ images.


Hopefully this explains what has happened and what to try to improve the result.


73s from Bavaria

SWL Tobias
.-.-.