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 )
