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 From: John Kludt <johnnykl...@gmail.com> Sent: Wednesday, June 16, 2021 3:29 PM To: w3...@verizon.net; WSJT software development <wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] TX start delay All, Before everyone starts yelling at me I got confused. It is when I run WSJT-X 2.4 standalone on the remote port at 9600 or 19200 baud that I have seen the delay issue resolved by a computer restart. When I run WSJT--X 2.4 from within N1MM at 115200 I have no problems. John On Wed, Jun 16, 2021 at 3:20 PM John Kludt <johnnykl...@gmail.com<mailto:johnnykl...@gmail.com>> wrote: I use an IC-7300 and have noticed the 3-4 second delay issue but it is intermittent. It usually occurs after I have been doing things in Device Manager with my com ports like trying to figure out which port is which. . It is resolved with a computer restart. I then get a TX delay that is imperceptible, presumably the delay I have set in WSJT-X (0.2 msec). Trying to think if it occurs when I connect via the USB port or via a CT-17 as I have both. I usually connect N1MM to the radio via the USB port so I can run at 115200 baud for the spectrum display. I run WSJT-X from within WSJT-X via the remote port at 9600 or 19200 baud. That has been a very stable configuration for me. I have wondered more about Win 10 and my com port drivers than the WSJT-X software itself. John K7SYS On Wed, Jun 16, 2021 at 2:45 PM w3nzl--- via wsjt-devel <wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>> wrote: FYI, I too have noticed this phenomena, an I am using an Icom 7300... Paul, W3NZL -----Original Message----- From: Black Michael via wsjt-devel <wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>> To: WSJT software development <wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>> Cc: Black Michael <mdblac...@yahoo.com<mailto:mdblac...@yahoo.com>> Sent: Wed, Jun 16, 2021 5:09 pm Subject: Re: [wsjt-devel] TX start delay Working on it...seems unique to K3/K3S but one other Icom user is complaining too... Mike W9MDB On Wednesday, June 16, 2021, 03:32:19 PM CDT, Joe Taylor <j...@princeton.edu<mailto:j...@princeton.edu>> wrote: Hi Mike, I assume these recent complaints about "Tx start delay" are the result of hamlib changes affecting certain rigs. Is this correct? Do you understand just what changes caused the problem, and do you have a fix in preparation? Let me know... -- Joe, K1JT On 6/15/2021 6:08 PM, Black Michael via wsjt-devel wrote: > What rig? > > Mike W9MDB > > On Tuesday, June 15, 2021, 05:06:26 PM CDT, Ned > <a...@cox.net<mailto:a...@cox.net>> wrote: > > Befuddled. I noticed that the TX start on FT8 using v2.4.0 seemed late > soon after I upgraded months ago. I always felt like I had taken a step > back in performance with v2.4.0 and decided to look at into it today. > > I measured the TX start delay today and it was like 4 to 5 seconds. When > I run v2.3.0 on the same computer using the same configuration I get no > detectable delay. When I use v2.5.2rc1 on the same computer with the > same configuration I get the same 4 to 5 second delay. When I use JTDX > which is based on v 2.4.0, I get the same 4 to 5 second delay. I see a > slight delay in one of the other stations in the shack on v 2.4.0 but > not as much as my main station. The main station is an i5 that with 8 G > available RAM. I have not tried other modes, but I am running v2.3.0 > until I get an inspiration about what to try to address this. I get the > same delay whether I use the VOX, CAT or DTR/RTS PTT interface. The > audio starts in the TX sequence at the same time I get the command to > PTT...always 4 to 5 seconds late. > > Thoughts? > > Ned / AA7A > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net> > <mailto:wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
