Hi David,?
tnx for looking into this. I have not run down every permutation
yet, but looking good.
- I don't know if it is a good idea to clear the Lk mode on a
modem change. The operators may just be continuing a QSO at a
different data rate. Difficult of course to differentiate between
just staying in the current bandpass vs doing a major QSY.
- When the Lk state is cleared by a modem change (as above), its
LED/indicator stays on. Clicking on it twice brings back the Lk
state.
- I notice the Lk state clears on RSID receipt when "Retain TX
Freq Lock" is disabled (a good thing). It might of course confuse
an operator that has Lk set for another reason and RSID use was
infrequent. One of those "read the manual" situations..?
- Thinking now in terms of NBEMS use (which I know little about,
so just thinking out aloud), I wonder if there is any point trying
to get away from any "pre session netting requirement", by the
setting of Lk and "Retain TX Freq Lock" operationally. Not of
course an issue with an IFK mode, but (say) switching to a wide
PSKR modem for a flamp transfer, then back to the the messaging
modem might be worth a discussion. Also means that operators can
arrive and leave with less setup/config time. Handy if the traffic
has a higher urgency. Would of course need more RSID use.
Cheers Bob
On 12/1/25 02:28, Dave, W1HKJ wrote:
toggle quoted message
Show quoted text
Bob,
Please download, install, and test fldigi-4.2.06.20
posted at
commit 62c2e6ca9566f04035a9c9bb5258348be369c3a4
Author: dave-w1hkj <w1hkj@...>
Date: Fri Jan 10 08:59:28 2025 -0600
RSID squelch
* correct RsID detection behavior
commit 33c741533ee618b10b405815abcbcccefbebc185
Author: dave-w1hkj <w1hkj@...>
Date: Thu Jan 2 18:41:09 2025 -0600
t
* reverted interleave depth to 25 ( 1 sec )
* reverted flush length to 20.
Those users testing THOR-25, please note that all testers should be on the same fldigi revision.
73, David
W1HKJ
On 1/10/25 01:23, Bob Cameron, VK2YQA
via groups.io wrote:
Wonder if you would review this again Dave. Same behaviour in
4.2.06.19 (yeah I am slow...)
What I didn't make clear in my OP was with "Retain tx freq
lock" enabled, the operational expectation is that the RX freq
would shift to meet the RSID centre, but leave the TX
frequency where it is. If "Retain tx freq lock" is disabled I
expect the TX and RX to shift together. (which is what it
does)
Note there us differing action too if the modem changes vs
not. Please try a few RSID's of the same modem, then try
changing the modem.
Cheers Bob
On 19/8/24 20:22, w1hkj wrote:
Bob,
This is on 4.2.05.25
The transmit stays locked at 7071.0 and the Rx is at
7071.3.
Dave
On 8/14/24 21:54, Bob Gypay
wrote:
Crossposted? to both fldigi-devel and linuxham
Tested on v4.2.04.11 and 4.2.04.24 against 3.23.21 (By
John VK2ETA)
Using PSK250RC7, PSK500RC3, PSK125RC10 and PSK63RCx (ie
not all modems checked)
With "Retain tx freq lock" enabled in RsID configuration
plus Lk set, V4 no longer enables Lk operation nor splits
the wfall TX/RX for the PSK125RC &? PSK63RC modems.
The PSK250RC and PSK500RC modems act in the same way as
8PSKx and OFDMx modems, shifting TX/RX together, ignoring
the RsID config setting and also not responding to Lk.
It might also be a good idea to force Lk operation when
setting this RsID config parameter and update the tooltip
to explain what is happening.
As it currently stands a mode such as PSK63RC5 is quite
troublesome to RsID tune as disabling TX lock can cause
TX/RX "walking" if any RIT is in play.
And since it is in the same "auto" tuning area it might
be a good idea to modify the AFC button tooltip to grey
out on unsupported modes. ie only single carrier PSK.
Cheers Bob VK2YQA
_______________________________________________
fldigi-devel mailing list
fldigi-devel@...
Dave, W1HKJ