Hello.

I'm new to flrig/fldigi, so this is probably something obvious but wasn't able to track it down.

fldigi 4.2.06 (also tried 4.2.06.05) on macbook pro m3 (macos sequoia), connected fo flrig 2.0.05. flrig drives FT-710.

As soon as I start fldigi it starts fighting with my changes to frequency and band made on the radio or via flrig xmlrpc API.

Like I'm changing frequency with radio knob and frequency gets reverted. Same for bands - changing band on radio and it gets switched back to previous. Same for frequency changes made with flrig API - these also get "reverted". If I keep changing frequency, despite reverts, eventually I'm able to get wanted frequency.

When I exit fldigi problem stops happening.

AFC is off for testing, RxID is off.

What else I should turn off?

I would like to be able to see frequency in fldigi (so polling should stay), change freq from fldigi by mouse clicks, use its AFC feature etc but also to be able to operate frequencies/bands from radio directly or via flrig xmlrpc API.

Thanks,
--
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )

开云体育

Hi.

If you run Flrig alone, does Flrig "follow" what you do at the radio?

If not, you need to find out why.? (Flrig settings, or Radio issue.)

If it does, then something is wrong in how FlDigi, interacts with Flrig.

Fldigi should "follow" any changes at FlRig.? If WITH FlRig and FlDigi running, and you change the frequency (or mode) at Flrig, does FlDigi follow those changes.? I assume the radio follows FlRig.

Regards.

Dave G0WBX.

On 15/11/2024 11:23, Dave, G?WBX via groups.io wrote:

Hi.
If you run Flrig alone, does Flrig "follow" what you do at the radio?

Yes. Flrig alone and:

- flrig frequency display follows frequency changes made at radio
- same for the other way - frequency changes made at flrig are applied to radio correctly
- changes made via flrig xmlrpc api are applied to radio correctly

flrig works reliably for me.

If it does, then something is wrong in how FlDigi, interacts with Flrig.
Fldigi should "follow" any changes at FlRig.

Ok, so I didn't miss any special option.

If WITH FlRig and FlDigi running, and you change the frequency (or mode) at Flrig, does FlDigi follow those changes.

When changing frequency on flrig then fldigi tries to follow but with the same "revert" problem, sometimes, as when changing frequency on radio.

I assume the radio follows FlRig.

Yes.

Debug log with rig i/o, server and client on:


- fldigi started with freq 14078100 being on its display
- (mouse) clicked *fldigi* third freq digit from right ("1") down, it changed frequency to 14078000, good, flrig follows, radio follows
- now started clicking fourth digit down on *flrig*
- one click -> fldigi went to 14077000
- second click -> fldigi went to 14076000
- and then fldigi went back itself to 14077000

Regards.
Dave G0WBX.

--
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )

On 15/11/2024 17:13, Arek M., SP2AM via groups.io wrote:

If WITH FlRig and FlDigi running, and you change the frequency (or mode) at Flrig, does FlDigi follow those changes.

When changing frequency on flrig then fldigi tries to follow but with the same "revert" problem, sometimes, as when changing frequency on radio.

Tracked it down.

Frequency was being changed in maclogger_set_qsy().

I had "Tune to Rx Spot" turned on and fldigi reacted on:

[Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100]
[Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100]
[Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100]
[Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100]
[Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100]
[Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100]
[Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100]
[Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100]
[Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB, Power:100]

These look like a kind of "current status report" and not "spot" for me.

Anyway disabling "Tune to Rx Spot" and the problem went away.

--
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )

On 15/11/2024 17:47, Arek M., SP2AM via groups.io wrote:

Anyway disabling "Tune to Rx Spot" and the problem went away.

That was too fast. No - it doesn't make it go away.

Added:

diff --git a/src/logbook/maclogger.cxx b/src/logbook/maclogger.cxx
index 1947a21b..087a3654 100644
--- a/src/logbook/maclogger.cxx
+++ b/src/logbook/maclogger.cxx
@@ -125,6 +125,8 @@ void maclogger_set_qsy()
unsigned long long hz = mclg_rxhz;
if (hz <= 0 || !progdefaults.maclogger_spot_rx) hz = mclg_txhz;
if (hz <= 0) return;
+ printf("progdefaults.maclogger_spot_rx %d\n", progdefaults.maclogger_spot_rx);
+ printf("mclg_txhz = %llu, maclogger_set_qsy: %llu\n", mclg_txhz, hz);
sendFreq(hz);
wf->rfcarrier(hz);
wf->movetocenter();

changing freq on radio and:

progdefaults.maclogger_spot_rx 0
mclg_txhz = 7245000, maclogger_set_qsy: 7245000
progdefaults.maclogger_spot_rx 0
mclg_txhz = 7247280, maclogger_set_qsy: 7247280
progdefaults.maclogger_spot_rx 0
mclg_txhz = 7249560, maclogger_set_qsy: 7249560
progdefaults.maclogger_spot_rx 0
mclg_txhz = 7254380, maclogger_set_qsy: 7254380
progdefaults.maclogger_spot_rx 0
mclg_txhz = 7254380, maclogger_set_qsy: 7254380
progdefaults.maclogger_spot_rx 0
mclg_txhz = 7255740, maclogger_set_qsy: 7255740
progdefaults.maclogger_spot_rx 0
mclg_txhz = 7256960, maclogger_set_qsy: 7256960


so it does sendFreq(hz) every short time. Just hz it has is sometimes old value (radio already has been set to new freq) which makes it tell flrig to go back to old freq.

Shouldn't it just do

maclogger_set_qsy() {
...
if (!progdefaults.maclogger_spot_rx)
return;

?

--
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )

On 15/11/2024 23:30, Dave, G?WBX via groups.io wrote:

OK.? AFICR, no other software other than the Flsuite was mentioned originally.

Could you list *All* the software you wish to use together, and

details

of the OS running it all.

macos 15.1
macloggerdx 6.53
flrig 2.0.05
fldigi - built from git today, also 4.2.06.05

Especially version numbers, for all software items you wish to run together.
That will help a lot.

I know nothing to little about Apple Mac's and their software, but I do know others on this list do know that stuff.

I think what happens is, macloggerdx reports over UDP:

[Radio Report:RxMHz:7.07968, TxMHz:7.07968, Band:40M, Mode:LSB,

fldigi reads that and parses it in parse_maclog() using parse_report() function. That function reads frequency

if ((p = str.find("RxMHz:")) != std::string::npos)
mclg_rxhz = get_freq(str.substr(p));

and then at the end of parse_report() show_mac_strings() is called which requests frequency change to flrig:

void show_mac_strings()
{
SET_THREAD_ID(MACLOGGER_TID);

if (mclg_txhz > 0) REQ(maclogger_set_qsy);

That calls maclogger_set_qsy() which requests outdated frequency (sendFreq(hz);) to be applied to the radio.

Outdated because macloggerdx sends reports not too often and fldigi assumes them to be "current" (which is wrong; the frequency is already different due to changes on radio knob or via flrigi freq display).

Why fldigi requests frequency changes based on maclogger radio report - no idea.

For spots, with "Tune to Rx Spot" being on that makes sense, for regular radio report - it doesn't IMO.

All the best.
Dave G0WBX.

--
Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )