Bill,
Thank you, I will test those values and report the results. I was never sure of
the advantages of using Split->Rig -vs- Fake It, but I always thought that Rig
was the correct way to go and Fake It was a workaround.
Jerry KI6RRD
From: Bill Somerville <g4...@classdesign.com>
Sent: Saturday, June 19, 2021 13:31
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] TX start delay
Hi Jerry,
below is the content of an email exchange with Dave, AA6YQ, about these delays.
Please note his suggestions for the Commander Command Interval settings for
each of your rigs, the necessity for the "Verify CI-V command acceptance"
option, and if that is still not fast enough then checking the WSJT-X option
"Settings->Radio->Split Operating->Fake It" will definitely reduce the delay
considerably.
+++++++++++++++
I would start the Pro III at 50 ms. If that works well, reduce it to 25 ms. I
would not go below 25 ms.
The IC-7300 works reliably at 10 ms.
Be sure to enable "Verify CI-V command acceptance".
Dave
-----Original Message-----
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Saturday, June 19, 2021 4:14 PM
To: Dave AA6YQ
Subject: Re: TX Delay
Hi Dave,
in a previous message he reported the delays with both his IC-756-ProIII and
IC-7300. He also reports no significant delays when using "Fake It"
split mode. Do you have a recommended Commander Command Interval for the
IC-756ProIII? I will pass on your recommendations. Thanks for the prompt
analysis and reply.
73
Bill
G4WJS.
On 19/06/2021 21:06, Dave AA6YQ wrote:
At the time that the CmdSendTx was received (2021-06-18 19:39:30.111), there
were already two "Set Split" directives in the processing queue.
2021-06-18 19:39:30.216 > DDEServerModule.Dequeue: command = split, string1 =
50,313.500, string 2 = Y
2021-06-18 19:39:32.919 > DDEServerModule.Dequeue: command = split, string1 =
50,313.500, string 2 = Y
The errorlog does not capture any configuration information, so I can't
determine the Icom model number or the command interval. From the errorlog
entries, I'd guess that the Command Interval is set to 200 ms, but I can't
suggest reducing it without knowing what model transceiver is being controlled.
With my IC-7800, I use a Command Interval of 25 ms; with my IC-7300, I use 10
ms. Commander's "Verify CI-V command acceptance" option should be enabled.
Many Icom users (including me) configure WSJT-X to "fake it" to reduce the
split delays.
73,
Dave, AA6YQ
-----Original Message-----
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Saturday, June 19, 2021 3:22 PM
To: Dave AA6YQ
Subject: Fwd: TX Delay
Hi Dave,
Jerry is seeing lengthy delays when switching to transmit on his Icom with
WSJT-X using Commander for rig control. Here is an extract from the Commander
debug log where it takes over 5 seconds to respond to a
<command:9>CmdSendTx<parameters:0>
query sent directly after a
<command:5>CmdTX<parameters:0>
<snipped>
------------------------
73
Bill
G4WJS.
On 18/06/2021 12:15, Bill Somerville wrote:
Hi Jerry,
thanks for the log file, it reveals that you are using DX Lab Suite Commander
for rig control, it would have been handy to know that before, hi. The issue
seems to be that Commander is taking between 2 and 4 seconds to reply to a PTT
state query sent to it immediately after a prior command to set PTT. This is
probably something Dave, AA6YQ, would need to comment on, but let's gather some
relevant information first. Please repeat the same test to get a new
WSJT-X_RigControl.log file, but this time also enable debug logging in
Commander. To enable debug logging in Commander open the "Config->General" tab
and check the "General->Log debugging info" option before starting the issue
demonstration sequence in WSJT-X. Once the test is complete uncheck the
Commander "Log debugging info" options and quit Commander. As before send me
(g4wjs <at> classdesign <dot> com) the new WSJT-X_RigControl.log file, and also
the file ErrorLog.txt from the C:\DXLab\Commander\ directory.
73
Bill
G4WJS.
On 17/06/2021 08:53, Bill Somerville wrote:
Hi Jerry,
you are the first to report such an unacceptably long delay with any Icom rig
as far as I know. So I can see what is going on, configure WSJT-X such that the
issue is demonstrated, put the attached file into your WSJT-X configuration
files directory (on MS Windows that is the same as the log files directory -
"Menu->File->Open log directory"), restart WSJT-X, carry out a *minimal* test
that demonstrates the issue, then quit WSJT-X. It will have created a new file
WSJT-X_RigControl.log on the Desktop, send that file to me (g4wjs <at>
classdesign <dot> com) for analysis please?
Once you have sent the log file you can delete it from your Desktop, also
delete the log configuration file to return to normal operation.
73
Bill
G4WJS.
On 16/06/2021 23:36, Jerry Shaw wrote:
FYI,
Not sure if this is related, however: I have always seen this delay 2-4 second
with ICOM 756Pro3 and 7300 radios if I set Split to Rig, the problem does not
exist if I set Split to Fake it.
Jerry KI6RRD
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
