|
|
Post by Fred k1io on Mar 14, 2023 20:44:18 GMT
I'm not sure if I'm having a sync problem, but I know I caused one. :-( I notice that all of the FT8 blocks are showing as two seconds early (e.g., 20:40:43, 20:40:58). Maybe harmless. But also, after a QSO, when the other guy calls CQ and I should not call, sometimes JTDX triggers the CAT to transmit for a fraction of a second. I wondered if the two were connected.
I'm using Meinberg NTP and it says I'm sync'd within 30 ms. But anyway, I tried the Sync button. I wondered what would happen if I sync'd to another station, rather than just the clock. So I used the control-shift-double click method. It didn't change the sync. But it caused the DX station to display in blue, and now whenever that station is heard, I also get the notification beep, as if it were calling me. How do I undo that?
|
|
|
|
Post by Arvo ES1JA on Mar 15, 2023 6:27:20 GMT
there at least three independent problems/situations.
"sometimes JTDX triggers the CAT to transmit for a fraction of a second."
Caused by positive Lag value ( jtdx does not know is needed to transmit last tx message again or not until decoding is finished )
If You not able to bring down Lag value then You need to use Autoseq2/6 but You may lose some stations from autoselect or late change tx message within QSO.
"I'm using Meinberg NTP and it says I'm sync'd within 30 ms."
It just says wrong, computer clock is much more inaccurate.
"I tried the Sync button. I wondered what would happen if I sync'd to another station, rather than just the clock. So I used the control-shift-double click method. It didn't change the sync."
You done something wrong. 1.Activate Sync button. 2 control-alt-double click (not control-shift-double click)
Now Sync button should show Offset set from clicked message). Right click of Sync deactivates JTDX internal Offset.
"But it caused the DX station to display in blue, and now whenever that station is heard, I also get the notification beep, as if it were calling me. How do I undo that?"
No, all this from Your Notification settings, check where You set beep.
MyCall in message colour is most likely caused by Your Wanted settings ( this message is matched to some wanted entry)
I see JTDX is to complicated, SRY I made it. There way to many options.
|
|
|
|
Post by Fred k1io on Mar 15, 2023 18:02:03 GMT
No, please don't apologize for anything -- JTDX is, in the famous words of St. Steve the Calligrapher, INSANELY GREAT!
It's just that the documentation is several years old and some things are missing. Like sync and the Wanted function. I don't have Beep turned on for anything except my call but the "wanted" call (displays in blue on white background) beeps. I just found wanted behind that little button and that did have the unwanted beepers. So that problem is solved, thanks!
The beep functions in JTDX do seem to make JTAlert unnecessary. I tried installing that on WSJT-X last year on my old computer (which was too slow for JTDX) and it simply wouldn't run. Now I don't need it!
I did back off to Autoseq 2. My computer is pretty fast but when it is decoding over 50 calls at a time the lag does go into the + range. Ten meters has been hot lately. And 40 of course normally goes nuts at night. I also experimentally verified that Auto is the right number of threads. :-)
> You done something wrong. 1.Activate Sync button. 2 control-alt-double click (not control-shift-double click)
> Now Sync button should show Offset set from clicked message). Right click of Sync deactivates JTDX internal Offset.
Where does it show the offset? Control-alt-double click on a received signal does seem to make it Wanted, regardless of the sync button.
|
|
|
|
Post by Arvo ES1JA on Mar 15, 2023 18:36:38 GMT
If You dblclick with not activated (green) sync button then callsign will be added into wanted. If Sync is activated then You see Yellow sync button and offset also there.
Using Autoseq2/6 should be used when nothing other helps, first experiment with decoder settings, use low thresholds instead of subpass.
Instead of outdated documentation try to use Hints that jtdx displays, they are up to date.
|
|
|
|
Post by Fred k1io on Mar 15, 2023 21:51:16 GMT
That's an interesting screen shot. On mine (2.2.160-rc3 on Windows), I never see a number displayed on the Sync button, nor on the AGC Comp button! I didn't know it was possible. I do see how ctrl-alt-doubleclick adds to the Wanted list. Doing that with Sync in green state makes Sync yellow. But no numbers are displayed.
Maybe it's a bug in this version, or something that doesn't work in Windows for some reason. The area below the Rx Frequency window, where those buttons is, is smaller in the Windows version than on yours (Linux?), when I size the screen similarly. My Rx Frequency windows also thus is a bit bigger. So the buttons in Windows below Rx Frequency aren't as tall and maybe only have room for one line to display.
|
|
