开云体育

I can run WSJT-X with Commander 15.15.1 doing CAT control on my K2 in WSJT-X split mode "None".? In split::rig and split::fakeit, TX is blipped for less than 1 second rather than the normal 13 or so seconds.? Long story short, split:rig and split:fakeit work if I enable the debug log on Commander.? I guess that logging slows Commander down, so maybe there's a timing problem with WSJT-X, the K2, and Commander.

Am I willing to run with the debug log on until my disk fills up?? Yes.? But any suggestions would be appreciated.

73 de Benjy AC4XO

+ AA6YQ comment sbelow

I can run WSJT-X with Commander 15.15.1 doing CAT control on my K2 in WSJT-X split mode "None".? In split::rig and split::fakeit, TX is blipped for less than 1 second rather than the normal 13 or so seconds.? Long story short, split:rig and split:fakeit work if I enable the debug log on Commander.? I guess that logging slows Commander down, so maybe there's a timing problem with WSJT-X, the K2, and Commander.

+ Or maybe your K2's split is enabled. When the WSJT-X "Spit Operations" panel is set to "Rig" or "Fake It", you must manually disable your transceiver's split.

? ? ? ?73,

? ? ? ? ? ? ? ?Dave, AA6YQ

Dave,

When I see this problem, the K2 Split mode is definitely off.? I tried turning Commander debug logging on and off with K2 split off, and split:rig and split:fakeit only worked with logging on.? Xmit was only blipped when logging was off.? I didn't change the rig setting in between.

I had this very same issue a few years ago with a different computer and different versions of the WSJT-X and Commander software.? As a matter of fact, I think the K2 firmware has been upgraded since then.? I guess I did import the software settings from the older versions.

The fact that other K2 users haven't reported the problem is a bit perplexing.

Benjy AC4XO

+ AA6YQ comments below

When I see this problem, the K2 Split mode is definitely off. I tried turning Commander debug logging on and off with K2 split off, and split:rig and split:fakeit only worked with logging on. Xmit was only blipped when logging was off. I didn't change the rig setting in between.

I had this very same issue a few years ago with a different computer and different versions of the WSJT-X and Commander software. As a matter of fact, I think the K2 firmware has been upgraded since then. I guess I did import the software settings from the older versions.

The fact that other K2 users haven't reported the problem is a bit perplexing.

+ The only recent problem reported in this area was recently resolved with a diagnosis of "RF interference". Is there any change in behavior if you temporarily reduce your K2's RF output power to zero?

73,

Dave, AA6YQ

Dave,

That's a good suggestion given that I have ladder line coming into the shack.? I set the K2 power to 0 and got the same results.

Anyway, this looks like a really hard problem to troubleshoot since getting a debug log makes the problem go away (heisenbug?) and since it appears the problem is something specific to my setup.? So I'm really happy to just run with the debug log enabled since I don't plan to spend too much time doing FT8.? At least I can do FT8 fox/hound mode now if the need arises which is why I was pursuing this problem.

73 de Benjy AC4XO

+ AA6YQ comments below

That's a good suggestion given that I have ladder line coming into the shack.? I set the K2 power to 0 and got the same results.

Anyway, this looks like a really hard problem to troubleshoot since getting a debug log makes the problem go away (heisenbug?) and since it appears the problem is something specific to my setup.? So I'm really happy to just run with the debug log enabled since I don't plan to spend too much time doing FT8.? At least I can do FT8 fox/hound mode now if the need arises which is why I was pursuing this problem.

+ Thanks for completing the RFI-check. Please do the following:

1. Set your K2 to a clear frequency using the same transceiver mode that you're using for FT8 operation

2. On the General tab of Commander's Configuration window, uncheck the "Log debugging info" box

3. On Commander's Main window, click the PTT panel's TX button; how long does it take for your K2 to switch from RX to TX?

4. On Commander's Main window, click the PTT panel's RX button; how long does it take for your K2 to switch from TX to RX?

5. Repeat steps 3 and 4 ten times, waiting at least 5 seconds between operations; is there any significant variation in the times to switch from RX to TX, or from TX to RX?

+ In the response that you post here, please include the value you've specified in the interval box to the right of the "Continuous interrogation" checkbox in the Radio panel on the Configuration window's General tab.

? ? ? ? ?73,

? ? ? ? ? ? ? ? Dave, AA6YQ

Dave,

The times are short and hard to measure, but there doesn't seem to be much variation in the times.? TX button to K2 transmit is almost instantaneous.? RX button to receive mode is a little longer but less than a second.

I assume you mean the "interrogation" checkbox.? The interval is 200.? Earlier today, I tried 500 and 800 with no noticeable change in the symptoms.

73 de Benjy AC4XO

+ AA6YQ comments below

The times are short and hard to measure, but there doesn't seem to be much variation in the times.? TX button to K2 transmit is almost instantaneous.? RX button to receive mode is a little longer but less than a second.

I assume you mean the "interrogation" checkbox.? The interval is 200.? Earlier today, I tried 500 and 800 with no noticeable change in the symptoms.

+ Thanks. Those results mean that Commander is correctly switching your K2 between RX and TX. Thus the symptoms you report are either the result of misconfiguration of WSJT-X , or a problem with the communications via TCP that that WSTJ-X employs to direct Commander. If you have any anti-malware running, I suggest that you disable it.

? ? ? 73,

? ? ? ? ? ? ?Dave, AA6YQ

?

?

Dave,

This looks like a good place to end this thread.? You've ruled out the obvious stuff; I? have a work-around; and it appears the problem only affects one person/equipment configuration.? So thanks for the help and suggestions.

73 de Benjy AC4XO

+ AA6YQ comments belo-w

This looks like a good place to end this thread.? You've ruled out the obvious stuff; I? have a work-around; and it appears the problem only affects one person/equipment configuration.? So thanks for the help and suggestions.

+ Assuming that disabling your anti-malware did not eliminate the symptoms, here is the next step in the diagnostic process:

1. in your Commander folder, delete the errorlog.txt file
2. start Commander
3. on the Configuration window's General tab, check the "Log debugging info" box
4. terminate Commander
5, configure the "Split Operations" panel in WSJT-X for "rig"
6. start Commander
7. direct WSJT-X to transmit on a clear frequency
8. on the Configuration window's General tab, uncheck the "Log debugging info" box
9. attach the errorlog.txt file from your Commander folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

? ? ? ?73,

? ? ? ? ? ? ?Dave, AA6YQ