¿ªÔÆÌåÓý

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

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


Re: Next version FLdigi

 

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: flrig 2.0.05.50 development release posted at

 

Hi again.

Re:- flrig 2.0.05.50 development release posted

Built with no errors/warnings on LMDE 5, 64 bit.? (Mint without the Ubuntu Influence.)

There is still a problem with the additional buttons, but this version does eventually return control to the user, but it takes some 10 to 15 seconds to regain control after clicking (or right clicking) on one of those buttons "That actually do something"...

"Empty" buttons, (nothing specified to send to the radio) return control to the user almost instantly.

Ver 2.0.05.05 did not have this issue.

73.

Dave G0WBX.

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


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

 

¿ªÔÆÌåÓý

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


flrig 2.0.05.50 development release posted at

 

¿ªÔÆÌåÓý

Index of /alpha/flrig

See readme.txt for complete list of changes after 2.0.05.

See flrig-2.0.05.50.png for view of changes in dialog(s).? Note that user interface changes has been split into system and color dialogs.? Enable tooltips and hover the mouse over various controls on any of the dialogs for control operation hints.

Please report discrepancies, hidden features, bugs to this forum.

73, David, W1HKJ


Re: #fldigi Exception when closing #fldigi

 

I have just tried a reboot of my machine, hoping I may have had some hangover from the TCP/IP connection to my logger. Started flrig and fldigi ONLY and I get the same error.


Phil.

On 15/05/2024 15:31, Philip Rose, GM3ZZA via groups.io wrote:
I get an exception when I close fldigi.

I have my own logging program that I connect fldigi to (Logbook->Connect to Server). If I close fldigi without disconnecting the logger I get the below exception (I also get it if I do disconnect the logger). It is probably something I need to do when fldigi connects to my logger. I actually seem to get the exception whether or not I connect my logger. The command I use to launch fldigi is:

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




Thread 12 "fldigi" received signal SIGUSR2, User defined signal 2.
[Switching to Thread 0x7f35ee3fe6c0 (LWP 1278591)]
__GI___pthread_sigmask (how=1, newmask=<optimized out>, oldmask=0x0)
at ./nptl/pthread_sigmask.c:43
43 ./nptl/pthread_sigmask.c: No such file or directory.
(gdb) bt
#0 __GI___pthread_sigmask (how=1, newmask=<optimized out>, oldmask=0x0)
at ./nptl/pthread_sigmask.c:43
#1 0x000055e41b369b94 in n3fjp_loop(void*) (args=<optimized out>)
at logbook/n3fjp_logger.cxx:2769
#2 0x00007f35f06a8134 in start_thread (arg=<optimized out>)
at ./nptl/pthread_create.c:442
#3 0x00007f35f07287dc in clone3 ()
at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
(gdb)

The stack notes from fldigi:* Stack trace:
/usr/local/bin/fldigi(+0x3a83f4)[0x560cc47f43f4]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e1a)[0x7faf3c8a8e1a]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e85)[0x7faf3c8a8e85]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa90d8)[0x7faf3c8a90d8]
/lib/x86_64-linux-gnu/libstdc++.so.6(_ZSt20__throw_length_errorPKc+0x40)[0x7faf3c8a01e9]
/usr/local/bin/fldigi(+0x2308cb)[0x560cc467c8cb]
/usr/local/bin/fldigi(+0x23b1c5)[0x560cc46871c5]
/usr/local/bin/fldigi(+0x5612af)[0x560cc49ad2af]
/usr/local/bin/fldigi(+0x4e25e8)[0x560cc492e5e8]
/usr/local/bin/fldigi(+0x4e0383)[0x560cc492c383]
/usr/local/bin/fldigi(+0x4e02c9)[0x560cc492c2c9]
/usr/local/bin/fldigi(+0x596e84)[0x560cc49e2e84]
/usr/local/bin/fldigi(+0x5915a2)[0x560cc49dd5a2]
/usr/local/bin/fldigi(+0x591625)[0x560cc49dd625]
/usr/local/bin/fldigi(+0x5afd29)[0x560cc49fbd29]
/usr/local/bin/fldigi(+0x4df3c9)[0x560cc492b3c9]
/usr/local/bin/fldigi(+0x4df3ed)[0x560cc492b3ed]
/usr/local/bin/fldigi(main+0x1bc4)[0x560cc4555444]
/lib/x86_64-linux-gnu/libc.so.6(+0x2724a)[0x7faf3ca4624a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85)[0x7faf3ca46305]
/usr/local/bin/fldigi(+0x10ef21)[0x560cc455af21]

* Version information:
fldigi 4.2.05.16
Copyright (C) 2007-2010 Dave Freese, Stelios Bounanos, and others.
License GPLv3+: GNU GPL version 3 or later <>following
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

* Build information:
Build information:
built : Fri May 3 15:16:59 BST 2024 by philip@chinook on x86_64-pc-linux-gnu for x86_64-pc-linux-gnu

configure flags:

compiler : gcc version 12.2.0 (Debian 12.2.0-14)

compiler flags : -I$(srcdir) -I$(srcdir)/include -I$(srcdir)/irrxml -I$(srcdir)/libtiniconv -I$(srcdir)/fileselector -I$(srcdir)/xmlrpcpp -I$(srcdir)/mbedtls -pthread -I/usr/local/include -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_THREAD_SAFE -D_REENTRfollowingANT -I/usr/include/opus -I/usr/include/x86_64-linux-gnu -D_REENTRANT -I/usr/local/include -I/usr/include/libusb-1.0 -I/usr/include/libpng16 -pipe -Wall -fexceptions -O2 --param=max-vartrack-size=0 -I$(srcdir)/xmlrpcpp --param=max-vartrack-size=0 -DNDEBUG

linker flags : -lportaudio -lasound -lm -lpthread -L/usr/local/lib -lfltk_images /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so -lfltk -lm -lpthread -lXinerama -lXfixes -lXcursor -L/usr/lib/x86_64-linux-gnu -lpangoxft-1.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lharfbuzz -lfontconfig -lfreetype -lXft -lpangocairo-1.0 -lcairo -lgtk-3 -lgdk-3 -lgio-2.0 -lX11 -lXft -lXrender -lwayland-cursor -lwayland-client -lxkbcommon -ldbus-1 -lfontconfig -ldl -lX11 -lsndfile -lsamplerate -lpulse-simple -lpulse -pthread -L/usr/local/lib -lhamlib -lpng16 -ludev

libraries : FLTK 1.4.0
libsamplerate 0.2.2
libsndfile 1.2.0
PortAudio 19
PulseAudio 16.1
Hamlib 4.6~git

Runtime information:
system : Linux chinook 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64

libraries : libsamplerate-0.2.2 (c) 2002-2008 Erik de Castro Lopo
libsndfile-1.2.0
PortAudio V19.6.0-devel, revision 396fe4b6699ae929d3a685b3ef8a7e97396139a4 1246720
Pulseaudio 16.1.0
Hamlib 4.6~git

* Stack trace:
/usr/local/bin/fldigi(+0x3a83f4)[0x560cc47f43f4]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e1a)[0x7faf3c8a8e1a]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e85)[0x7faf3c8a8e85]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa90d8)[0x7faf3c8a90d8]
/lib/x86_64-linux-gnu/libstdc++.so.6(_ZSt20__throw_length_errorPKc+0x40)[0x7faf3c8a01e9]
/usr/local/bin/fldigi(+0x2308cb)[0x560cc467c8cb]
/usr/local/bin/fldigi(+0x23b1c5)[0x560cc46871c5]
/usr/local/bin/fldigi(+0x5612af)[0x560cc49ad2af]
/usr/local/bin/fldigi(+0x4e25e8)[0x560cc492e5e8]
/usr/local/bin/fldigi(+0x4e0383)[0x560cc492c383]
/usr/local/bin/fldigi(+0x4e02c9)[0x560cc492c2c9]
/usr/local/bin/fldigi(+0x596e84)[0x560cc49e2e84]
/usr/local/bin/fldigi(+0x5915a2)[0x560cc49dd5a2]
/usr/local/bin/fldigi(+0x591625)[0x560cc49dd625]
/usr/local/bin/fldigi(+0x5afd29)[0x560cc49fbd29]
/usr/local/bin/fldigi(+0x4df3c9)[0x560cc492b3c9]
/usr/local/bin/fldigi(+0x4df3ed)[0x560cc492b3ed]
/usr/local/bin/fldigi(main+0x1bc4)[0x560cc4555444]
/lib/x86_64-linux-gnu/libc.so.6(+0x2724a)[0x7faf3ca4624a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85)[0x7faf3ca46305]
/usr/local/bin/fldigi(+0x10ef21)[0x560cc455af21]

* Version information:
fldigi 4.2.05.16
Copyright (C) 2007-2010 Dave Freese, Stelios Bounanos, and others.
License GPLv3+: GNU GPL version 3 or later <>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

* Build information:
Build information:
built : Fri May 3 15:16:59 BST 2024 by philip@chinook on x86_64-pc-linux-gnu for x86_64-pc-linux-gnu

configure flags:

compiler : gcc version 12.2.0 (Debian 12.2.0-14)

compiler flags : -I$(srcdir) -I$(srcdir)/include -I$(srcdir)/irrxml -I$(srcdir)/libtiniconv -I$(srcdir)/fileselector -I$(srcdir)/xmlrpcpp -I$(srcdir)/mbedtls -pthread -I/usr/local/include -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_THREAD_SAFE -D_REENTRANT -I/usr/include/opus -I/usr/include/x86_64-linux-gnu -D_REENTRANT -I/usr/local/include -I/usr/include/libusb-1.0 -I/usr/include/libpng16 -pipe -Wall -fexceptions -O2 --param=max-vartrack-size=0 -I$(srcdir)/xmlrpcpp --param=max-vartrack-size=0 -DNDEBUG

linker flags : -lportaudio -lasound -lm -lpthread -L/usr/local/lib -lfltk_images /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so -lfltk -lm -lpthread -lXinerama -lXfixes -lXcursor -L/usr/lib/x86_64-linux-gnu -lpangoxft-1.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lharfbuzz -lfontconfig -lfreetype -lXft -lpangocairo-1.0 -lcairo -lgtk-3 -lgdk-3 -lgio-2.0 -lX11 -lXft -lXrender -lwayland-cursor -lwayland-client -lxkbcommon -ldbus-1 -lfontconfig -ldl -lX11 -lsndfile -lsamplerate -lpulse-simple -lpulse -pthread -L/usr/local/lib -lhamlib -lpng16 -ludev

libraries : FLTK 1.4.0
libsamplerate 0.2.2
libsndfile 1.2.0
PortAudio 19
PulseAudio 16.1
Hamlib 4.6~git

Runtime information:
system : Linux chinook 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64

libraries : libsamplerate-0.2.2 (c) 2002-2008 Erik de Castro Lopo
libsndfile-1.2.0
PortAudio V19.6.0-devel, revision 396fe4b6699ae929d3a685b3ef8a7e97396139a4 1246720
Pulseaudio 16.1.0
Hamlib 4.6~git





#fldigi Exception when closing #fldigi

 

I get an exception when I close fldigi.

I have my own logging program that I connect fldigi to (Logbook->Connect to Server). If I close fldigi without disconnecting the logger I get the below exception (I also get it if I do disconnect the logger). It is probably something I need to do when fldigi connects to my logger. I actually seem to get the exception whether or not I connect my logger. The command I use to launch fldigi is:

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




Thread 12 "fldigi" received signal SIGUSR2, User defined signal 2.
[Switching to Thread 0x7f35ee3fe6c0 (LWP 1278591)]
__GI___pthread_sigmask (how=1, newmask=<optimized out>, oldmask=0x0)
at ./nptl/pthread_sigmask.c:43
43 ./nptl/pthread_sigmask.c: No such file or directory.
(gdb) bt
#0 __GI___pthread_sigmask (how=1, newmask=<optimized out>, oldmask=0x0)
at ./nptl/pthread_sigmask.c:43
#1 0x000055e41b369b94 in n3fjp_loop(void*) (args=<optimized out>)
at logbook/n3fjp_logger.cxx:2769
#2 0x00007f35f06a8134 in start_thread (arg=<optimized out>)
at ./nptl/pthread_create.c:442
#3 0x00007f35f07287dc in clone3 ()
at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
(gdb)

The stack notes from fldigi:* Stack trace:
/usr/local/bin/fldigi(+0x3a83f4)[0x560cc47f43f4]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e1a)[0x7faf3c8a8e1a]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e85)[0x7faf3c8a8e85]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa90d8)[0x7faf3c8a90d8]
/lib/x86_64-linux-gnu/libstdc++.so.6(_ZSt20__throw_length_errorPKc+0x40)[0x7faf3c8a01e9]
/usr/local/bin/fldigi(+0x2308cb)[0x560cc467c8cb]
/usr/local/bin/fldigi(+0x23b1c5)[0x560cc46871c5]
/usr/local/bin/fldigi(+0x5612af)[0x560cc49ad2af]
/usr/local/bin/fldigi(+0x4e25e8)[0x560cc492e5e8]
/usr/local/bin/fldigi(+0x4e0383)[0x560cc492c383]
/usr/local/bin/fldigi(+0x4e02c9)[0x560cc492c2c9]
/usr/local/bin/fldigi(+0x596e84)[0x560cc49e2e84]
/usr/local/bin/fldigi(+0x5915a2)[0x560cc49dd5a2]
/usr/local/bin/fldigi(+0x591625)[0x560cc49dd625]
/usr/local/bin/fldigi(+0x5afd29)[0x560cc49fbd29]
/usr/local/bin/fldigi(+0x4df3c9)[0x560cc492b3c9]
/usr/local/bin/fldigi(+0x4df3ed)[0x560cc492b3ed]
/usr/local/bin/fldigi(main+0x1bc4)[0x560cc4555444]
/lib/x86_64-linux-gnu/libc.so.6(+0x2724a)[0x7faf3ca4624a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85)[0x7faf3ca46305]
/usr/local/bin/fldigi(+0x10ef21)[0x560cc455af21]

* Version information:
fldigi 4.2.05.16
Copyright (C) 2007-2010 Dave Freese, Stelios Bounanos, and others.
License GPLv3+: GNU GPL version 3 or later <>following
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

* Build information:
Build information:
built : Fri May 3 15:16:59 BST 2024 by philip@chinook on x86_64-pc-linux-gnu for x86_64-pc-linux-gnu

configure flags:

compiler : gcc version 12.2.0 (Debian 12.2.0-14)

compiler flags : -I$(srcdir) -I$(srcdir)/include -I$(srcdir)/irrxml -I$(srcdir)/libtiniconv -I$(srcdir)/fileselector -I$(srcdir)/xmlrpcpp -I$(srcdir)/mbedtls -pthread -I/usr/local/include -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_THREAD_SAFE -D_REENTRfollowingANT -I/usr/include/opus -I/usr/include/x86_64-linux-gnu -D_REENTRANT -I/usr/local/include -I/usr/include/libusb-1.0 -I/usr/include/libpng16 -pipe -Wall -fexceptions -O2 --param=max-vartrack-size=0 -I$(srcdir)/xmlrpcpp --param=max-vartrack-size=0 -DNDEBUG

linker flags : -lportaudio -lasound -lm -lpthread -L/usr/local/lib -lfltk_images /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so -lfltk -lm -lpthread -lXinerama -lXfixes -lXcursor -L/usr/lib/x86_64-linux-gnu -lpangoxft-1.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lharfbuzz -lfontconfig -lfreetype -lXft -lpangocairo-1.0 -lcairo -lgtk-3 -lgdk-3 -lgio-2.0 -lX11 -lXft -lXrender -lwayland-cursor -lwayland-client -lxkbcommon -ldbus-1 -lfontconfig -ldl -lX11 -lsndfile -lsamplerate -lpulse-simple -lpulse -pthread -L/usr/local/lib -lhamlib -lpng16 -ludev

libraries : FLTK 1.4.0
libsamplerate 0.2.2
libsndfile 1.2.0
PortAudio 19
PulseAudio 16.1
Hamlib 4.6~git

Runtime information:
system : Linux chinook 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64

libraries : libsamplerate-0.2.2 (c) 2002-2008 Erik de Castro Lopo
libsndfile-1.2.0
PortAudio V19.6.0-devel, revision 396fe4b6699ae929d3a685b3ef8a7e97396139a4 1246720
Pulseaudio 16.1.0
Hamlib 4.6~git

* Stack trace:
/usr/local/bin/fldigi(+0x3a83f4)[0x560cc47f43f4]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e1a)[0x7faf3c8a8e1a]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa8e85)[0x7faf3c8a8e85]
/lib/x86_64-linux-gnu/libstdc++.so.6(+0xa90d8)[0x7faf3c8a90d8]
/lib/x86_64-linux-gnu/libstdc++.so.6(_ZSt20__throw_length_errorPKc+0x40)[0x7faf3c8a01e9]
/usr/local/bin/fldigi(+0x2308cb)[0x560cc467c8cb]
/usr/local/bin/fldigi(+0x23b1c5)[0x560cc46871c5]
/usr/local/bin/fldigi(+0x5612af)[0x560cc49ad2af]
/usr/local/bin/fldigi(+0x4e25e8)[0x560cc492e5e8]
/usr/local/bin/fldigi(+0x4e0383)[0x560cc492c383]
/usr/local/bin/fldigi(+0x4e02c9)[0x560cc492c2c9]
/usr/local/bin/fldigi(+0x596e84)[0x560cc49e2e84]
/usr/local/bin/fldigi(+0x5915a2)[0x560cc49dd5a2]
/usr/local/bin/fldigi(+0x591625)[0x560cc49dd625]
/usr/local/bin/fldigi(+0x5afd29)[0x560cc49fbd29]
/usr/local/bin/fldigi(+0x4df3c9)[0x560cc492b3c9]
/usr/local/bin/fldigi(+0x4df3ed)[0x560cc492b3ed]
/usr/local/bin/fldigi(main+0x1bc4)[0x560cc4555444]
/lib/x86_64-linux-gnu/libc.so.6(+0x2724a)[0x7faf3ca4624a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85)[0x7faf3ca46305]
/usr/local/bin/fldigi(+0x10ef21)[0x560cc455af21]

* Version information:
fldigi 4.2.05.16
Copyright (C) 2007-2010 Dave Freese, Stelios Bounanos, and others.
License GPLv3+: GNU GPL version 3 or later <>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

* Build information:
Build information:
built : Fri May 3 15:16:59 BST 2024 by philip@chinook on x86_64-pc-linux-gnu for x86_64-pc-linux-gnu

configure flags:

compiler : gcc version 12.2.0 (Debian 12.2.0-14)

compiler flags : -I$(srcdir) -I$(srcdir)/include -I$(srcdir)/irrxml -I$(srcdir)/libtiniconv -I$(srcdir)/fileselector -I$(srcdir)/xmlrpcpp -I$(srcdir)/mbedtls -pthread -I/usr/local/include -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_THREAD_SAFE -D_REENTRANT -I/usr/include/opus -I/usr/include/x86_64-linux-gnu -D_REENTRANT -I/usr/local/include -I/usr/include/libusb-1.0 -I/usr/include/libpng16 -pipe -Wall -fexceptions -O2 --param=max-vartrack-size=0 -I$(srcdir)/xmlrpcpp --param=max-vartrack-size=0 -DNDEBUG

linker flags : -lportaudio -lasound -lm -lpthread -L/usr/local/lib -lfltk_images /usr/lib/x86_64-linux-gnu/libjpeg.so /usr/lib/x86_64-linux-gnu/libpng.so /usr/lib/x86_64-linux-gnu/libz.so -lfltk -lm -lpthread -lXinerama -lXfixes -lXcursor -L/usr/lib/x86_64-linux-gnu -lpangoxft-1.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 -lharfbuzz -lfontconfig -lfreetype -lXft -lpangocairo-1.0 -lcairo -lgtk-3 -lgdk-3 -lgio-2.0 -lX11 -lXft -lXrender -lwayland-cursor -lwayland-client -lxkbcommon -ldbus-1 -lfontconfig -ldl -lX11 -lsndfile -lsamplerate -lpulse-simple -lpulse -pthread -L/usr/local/lib -lhamlib -lpng16 -ludev

libraries : FLTK 1.4.0
libsamplerate 0.2.2
libsndfile 1.2.0
PortAudio 19
PulseAudio 16.1
Hamlib 4.6~git

Runtime information:
system : Linux chinook 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64

libraries : libsamplerate-0.2.2 (c) 2002-2008 Erik de Castro Lopo
libsndfile-1.2.0
PortAudio V19.6.0-devel, revision 396fe4b6699ae929d3a685b3ef8a7e97396139a4 1246720
Pulseaudio 16.1.0
Hamlib 4.6~git


Re: [winfldigi] FLDIGI keeps deleting my log

 

On Mon, May 13, 2024 at 01:53 PM, Dave, W1HKJ wrote:
Can someone else please verify.
Good day David.

I've been using the version?fldigi 4.2.05.17?since day one. There were no problems with log. Worked actively from 1 to 10?May, sending via UDP. After Alpha?.17 was not updated - I'm waiting for the release. (Windows-7 x86)


Re: [winfldigi] flrig: User Interface settings issues - Tested on 2.0.05.49

 

¿ªÔÆÌåÓý

Tim,

I find your haughty attitude disengaging.? Let me be a little frank with you.
  • github is not the primary repository for flrig.? Neither is it for fldigi.
  • Source Forge is the primary repository.
  • flrig is fully open source and you are free to correct deficiencies, both bugs and cosmetic.? return the code changes to the developer(s) for merger with other submissions.
  • most users are concerned with functionality and are willing to abide with some user interface inconveniences.
  • the primary flrig developer was marginally available for all of the years 2022 and 2023 as he was primary caregiver to a dying spouse.? 2024 has been a catch up year for more critical code items.
  • thank you for reporting the discrepancies.

73, David, W1HKJ



On 5/13/24 20:19, Tim wrote:

Hello!

I have tested and confirmed the following outstanding UI issues with flrig 2.0.5.49. ?See details of each issue at the end.

== Reset/Cancel loses your original settings: ?Unchanged. ?Cancel does *not* undo the reset.

== Tab Clr does not reset: ?Unchanged. ?Reset does *not* reset Tab Clr

== Automatically-changing foreground text color: ?Unchanged. ?Changing System/Bgnd2 changes foreground colors for *unrelated* elements!

== Configuration tree navigator hard-coded black: ?Unchanged. ?Still hard-coded to black.

== UI does not update dynamically: ?Unchanged, both meter and Configure dialog boxes.

Tim
AD8JL


Details of issues:

== Reset/Cancel loses your original settings
If you enter the Configure/UI/User Interface dialog box, press Reset and then press Cancel, you will NOT get back the settings you had before you click Reset! They seem to be permanently lost. This is annoying to say the least!

== Tab Clr does not reset
When you click on Reset, the Tab Clr setting is not changed back to the default. Only pressing the Tab Clr button resets the color.

== Automatically-changing foreground text color
When you change System/Bgnd2, almost all foreground colors are automatically changed too. What's frustrating is that the foreground text that's changed is NOT the text used for that background!

For example: after a UI reset: change System/Bgnd2 to medium blue. Most if not all of the text now changes to white. The problem is, only a little bit of text is actually on top of Bgnd2. Most are on Bgnd, and now you have white text on light-grey background! And this seems to change multiple foreground colors: at least both Freq Color and System/Fgnd. Oddly, if you click on those buttons, the setting there is still set at full-black. If I go into those settings and simply click OK, I get black again. But if I go into System/Bgnd2 and simply click OK, I get the white back again!

This inconsistency and widespread random change is enough to drive you mad. :) None of this really seems to make any sense. First of all, if we have a control for changing the color, why does the code try to 'do us a favor' and change it behind our back? Sure, if you set the foreground color to the background color you can't read anything. I get that. But if you're going to change foreground colors based on background colors, you should do it only with that actual background color. Right now, change a single, lesser-used background color and your foreground color changes practically software-wide, even though there's at least four differ background color settings!

== Configuration tree navigator hard-coded black
It seems that the tree navigator foreground text color in the Configuration box does not change no matter what. It doesn't change to white based on background color as described above. It uses System/Bgnd2, yet it does not follow System/Fgnd, either. In fact, I can't make it change at all. Seeing as I'm trying to make a dark UI (where the background is dark and the foreground is light), this is a big difficulty.

== UI does not update dynamically
There are several features that do not change their UI settings dynamically. In the main window, most everything reflects UI changes immediately. However, the frequency and meter do not dynamically. In the Configuration box, most things do not change dynamically when UI settings are made. For example, after a UI reset: Open the Configuration box. Open the UI box. Change the System/bgnd to pink. The main window and the UI window immediately reflect this change. The Configuration box does not. Change System/bgnd2 to blue. Again, both the UI and main windows reflect this change. The Configuration box does not. Now, simply click on the title bar of the Configuration window. The left navigator will change at that point (without the text turning white :) ), but the rest of the window will not. You have to either select something else in the Navigator area or close and reopen the window to get it to redraw.

Thank you for your time and attention. I believe that these are the same issues as already covered in the above GitHub link: nothing has changed from my previous writeup. The GitHub link above includes screenshots, which were also previously included in emails to this list. I don't expect you to use the GitHub issue list if you don't want to ¨C I don't expect you to do anything? you don't want to! ? ¨C but I will put this information there as well for future users. It's way? easier for people to find GH resources than old e-mail threads. However, I will continue to work with the project in an e-mail-first manner.

Tim
AD8JL


flrig 2.0.05.49 development version posted at

 

¿ªÔÆÌåÓý

Index of /alpha/flrig

Refer to readme.txt for changes.

73, David, W1HKJ


Re: [winfldigi] FLDIGI keeps deleting my log

 

¿ªÔÆÌåÓý

I've completed my testing of fldigi 4.2.05.21 and cannot duplicate the reported problem.? The fldigi logbook data file, default:? <fldigi data folder>/logs/logbook.adif *, remains intact whether adding, modifying, or deleting logbook records.

Can someone else please verify.? Thank you.

latest development release is at

* <fldigi data folder>
? on Windows: USER_HOME_FOLDER\fldigi.files
? on Linux & MacOS: USER_HOME_FOLDER/.fldigi

73, David, W1HKJ


On 5/13/24 08:03, Dave, W1HKJ wrote:

Thank you for the report.? The UDP log export introduced this bug to the code.? I will look into this immediately.

In the meantime, cease from using the latest fldigi development test version and vall back to version 2.0.5



David

On 5/12/24 22:41, Dave Garber wrote:
is it deleting your Writelog log, or Fldigi log??? ?is the path correct on your Fldigi files paths, or did you install in a different folder.

it almost sounds like a path issue. good luck finding it.? ?good reason to backup files before updating? ( maybe you have a backup?)


Dave Garber
VE3WEJ / VE3IE


On Sun, May 12, 2024 at 10:59?PM Jim ZL2BMH via <zl2bmh=[email protected]> wrote:
I too are having the same problem as the gentleman using cable TV.

We don't have cable here yet, but since downloading the latest version of
FLdigi it wipes out me complete log.? I am using Winlog32.

Regards to all.
Jim.

Amateur Radio Station: ZL2BMH







Re: [winfldigi] FLDIGI keeps deleting my log

 

¿ªÔÆÌåÓý

Thank you for the report.? The UDP log export introduced this bug to the code.? I will look into this immediately.

In the meantime, cease from using the latest fldigi development test version and vall back to version 2.0.5



David

On 5/12/24 22:41, Dave Garber wrote:

is it deleting your Writelog log, or Fldigi log??? ?is the path correct on your Fldigi files paths, or did you install in a different folder.

it almost sounds like a path issue. good luck finding it.? ?good reason to backup files before updating? ( maybe you have a backup?)


Dave Garber
VE3WEJ / VE3IE


On Sun, May 12, 2024 at 10:59?PM Jim ZL2BMH via <zl2bmh=[email protected]> wrote:
I too are having the same problem as the gentleman using cable TV.

We don't have cable here yet, but since downloading the latest version of
FLdigi it wipes out me complete log.? I am using Winlog32.

Regards to all.
Jim.

Amateur Radio Station: ZL2BMH






CTY-3416 Country Files - 13 May 2024

 

The Country (CTY) Files were updated on 13 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:

13 May 2024 (CTY-3416)
VER20240513, Version entity is Central Kiribati, T31

Added/changed Entities/Prefixes/Callsigns:

* B7CRA and B9CRA are both China, BY
* TO972JO is Martinique, FM
* GB0AEL is Northern Ireland, GI
* GB0BOA, GB5RB and MM0PLX/P are all Scotland, GM
* GB0MFB, GB1SDB and GB8SOS are all Wales, GW
* K1LB and N5YJZ are both United States, K in CQ zone 3, ITU zone 6
* KD2DMR, NY9P and WA9FBO are all United States, K in CQ zone 4, ITU zone 7
* KC4YDJ, KI5UXR, KM4IYW, KO4BVP, KO4UMQ, N5VJX, W5BAM, WA2DLN and WB2UBW
are all United States, K in CQ zone 4, ITU zone 8
* AA8WZ, K8OSF, K9DY, K9JHR, KB8NXH, KQ6KC, N9FZ and WA6VZN are all United States, K in CQ zone 5, ITU zone 8
* KC5LAF, KO4V and W7CWT are all Hawaii, KH6
* AC9IZ, K1LH, KG5COH and KH6RF are all Alaska, KL
* LU2DT/D, LU3EU/D, LU4EV/D, LU5JAH/F, LU5JSB/H, LU7EPT/D, LU7VB/O,
LU9DNV/D, LU9JDZ/H and LW3DJC/D are all Argentina, LU
* RA9ULL/6, RJ9I/6, UA4FMQ/P and UE79MA are all European Russia, UA
* R9XD/9 is Asiatic Russia, UA9 in ITU zone 20
* UA1O/0 is Asiatic Russia, UA9 in CQ zone 19, ITU zone 23
* RL5G/0 is Asiatic Russia, UA9 in CQ zone 19, ITU zone 34
* VK8DNT/4 is Australia, VK in ITU zone 55
* VK2HJ/9 is Norfolk Island, VK9N

Removed Entities/Prefixes/Callsigns:

* EA1RCI/P in Spain, EA
* TO3Z in Guadeloupe, FG
* GB0SPD, GB1PAT and GB9SPD in Northern Ireland, GI
* GB8FT in Scotland, GM
* AB4GG, AD4FL, AI1K, K0FE, K0PLC, K2AMF, K4KSV, K4TNN, K4YO, K5PSN,
K6ACV, K8MCN, K8WV, K9KA, K9TWW, KA8VZB, KB4ZFA, KF4TCV, KI4ZRH, KJ4EBE,
KO4SKK, N0FIR, N0TR, N2CCG, N7GVV, N7NG, N8JOE, N9JNQ, NY9H, W4YPW, W5EPL,
W8HMK, WA4CAX, WB4KUU, WB9WKT, WE4BY, WO0M, WP2C, WR8AA and WX7F in United States, K
* KD0VQY and KX4ES in Hawaii, KH6
* AG6PI, KF0EXR, KF7PFN, KI6ZYO, KK6BVH and KK6CAU in Alaska, KL
* LU2EE/D, LU7DZV/D and LW6DNF/D in Argentina, LU
* PI9TP/J in Netherlands, PA
* R24BLIN, R8FF/1, RC9HC/1, RT9K/6 and UA8K/1 in European Russia, UA
* R0QAW/9, R2023BA, R4DB/8 and R4FBJ/0/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 2.0.05.48 development test version posted

 

Built and working on LMDE 5 64 bit with a real TS-870s as the target.

Seems OK, but there is (like 2.0.05.05) a momentary assertion of the DTR line as the serial port is opened.
(I may have omitted to report that, but 2.0.05.05 has been working OK for me for some time now.)

I have protection against that (using the radio's TX-Disable feature) but it could key an unprotected radio momentarily if a simple hardware PTT is used, driven from DTR.? (RTS is needed for flow control, and the hardware PTT is "Needed" so the rig will accept TX Audio from the rear accessory port.)

However, it crashes and deadlocks the UI when using the companion "Extra Buttons" dialogue, needing a "Kill" from Htop to end.
The buttons stay "stuck in" and the entire Flrig UI is frozen.? No excess CPU usage that I can see in that state.

The .05 alpha was not a problem.


The same happens with the FT736r, also needing Htop to Kill it.


Testing .48 alpha with the PCR1000, and all seems well.? Not got an antenna on it at present, but all the controls seem to work, making changes to the background noise as expected.

I do not (yet) have any of the extra buttons configured with that RX, so nothing happens when they are pressed.? They also do NOT cause the UI deadlock, so maybe some clash of threads with the other rigs with the serial I/O routines?


If you require any specific testing, just give me chapter and verse instructions, and I'll do the tests for you.


73, and thanks for your time and effort etc.

Dave G0WBX.




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


Re: #flrig flrig not working with my FT-890 FTDI Programming Cable #flrig

 

I tried the new test release flrig-2.0.05.48.

It still works like my previous post. I guess it is still like the last patches you sent.
I know you have been busy with fldigi lately.