Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working
; >
> > Ed N4II.
> >
> >
> >
> > *From:* Frode Igland via wsjt-devel
> > mailto:wsjt-devel@lists.sourceforge.net>> *Sent:* Thursday, October 13,
> > 2022 5:06 AM *To:* WSJT software development
> > mailto:wsjt-devel@lists.sourceforge.net>> *Cc:* Frode Igland
> > mailto:frodeigla...@gmail.com>>
*Subject:* [wsjt-devel] WSJT-X 2.6.0-rc4:
> > Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops
> > working
> >
> >
> >
> > I have used -rc4 since it was released and have found it quite
> > stable with three notable exceptions:
> >
> >
> >
> > *1. Sudden closing in FT8 after extended periods of operation*
> >
> > After an extended period of use in FT8 mode (normally more than two
> > hours), WSJT-X may close down abruptly. The closing happens at the
> > start of an FT8 sequence. I have never experienced closing on FT4,
> > but then I have very rarely worked FT4 for extended periods. To
> > start again, an orphaned JT9 decoding application first has to be
> > terminated in the Task Manager. This issue started with WSJT-X
> > 2.6.0-rc1 and still happens.
> >
> >
> >
> > *2. "CQ: Max Dist" doesn't work*
> >
> > After selecting "CQ: Max Dist", WSJT-X still selects the station
> > first decoded, notwithstanding the distance. It makes no difference
> > whether "CQ: Max Dist" is selected after "CQ: None" or "CQ: First"
> > or if "CQ: Max Dist" was selected on start-up before first CQ.
> >
> >
> >
> > *3. "CQ: None" stops working after a while*
> >
> > I often call CQ DX with the "CQ: None" setting, to be able to
> > select which DX station to work. This normally works well, but
> > suddenly WSJT-X may start answering the first station decoded
> > automatically, without being selected manually by me. Sometimes,
> > reselecting "CQ: None" helps, and sometimes I have to close and
> > reopen WSJT-X and select "CQ: None" before calling CQ.
> >
> >
> >
> > These are my experiences with WSJT-X 2.6.0-rc4.
> >
> >
> >
> > 73, Frode LA6VQ
> >
> >
> >
> >
> > ___
> > wsjt-devel mailing list
> > 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
<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
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working
; >
> > Ed N4II.
> >
> >
> >
> > *From:* Frode Igland via wsjt-devel
> > mailto:wsjt-devel@lists.sourceforge.net>> *Sent:* Thursday, October 13,
> > 2022 5:06 AM *To:* WSJT software development
> > mailto:wsjt-devel@lists.sourceforge.net>> *Cc:* Frode Igland
> > mailto:frodeigla...@gmail.com>>
*Subject:* [wsjt-devel] WSJT-X 2.6.0-rc4:
> > Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops
> > working
> >
> >
> >
> > I have used -rc4 since it was released and have found it quite
> > stable with three notable exceptions:
> >
> >
> >
> > *1. Sudden closing in FT8 after extended periods of operation*
> >
> > After an extended period of use in FT8 mode (normally more than two
> > hours), WSJT-X may close down abruptly. The closing happens at the
> > start of an FT8 sequence. I have never experienced closing on FT4,
> > but then I have very rarely worked FT4 for extended periods. To
> > start again, an orphaned JT9 decoding application first has to be
> > terminated in the Task Manager. This issue started with WSJT-X
> > 2.6.0-rc1 and still happens.
> >
> >
> >
> > *2. "CQ: Max Dist" doesn't work*
> >
> > After selecting "CQ: Max Dist", WSJT-X still selects the station
> > first decoded, notwithstanding the distance. It makes no difference
> > whether "CQ: Max Dist" is selected after "CQ: None" or "CQ: First"
> > or if "CQ: Max Dist" was selected on start-up before first CQ.
> >
> >
> >
> > *3. "CQ: None" stops working after a while*
> >
> > I often call CQ DX with the "CQ: None" setting, to be able to
> > select which DX station to work. This normally works well, but
> > suddenly WSJT-X may start answering the first station decoded
> > automatically, without being selected manually by me. Sometimes,
> > reselecting "CQ: None" helps, and sometimes I have to close and
> > reopen WSJT-X and select "CQ: None" before calling CQ.
> >
> >
> >
> > These are my experiences with WSJT-X 2.6.0-rc4.
> >
> >
> >
> > 73, Frode LA6VQ
> >
> >
> >
> >
> > ___
> > wsjt-devel mailing list
> > 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
<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
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working
>Frode, I don't know what it means. I read that text hastly, so, apologize. I stop allways there, where is something mentioned "contest". Not my thing... :) We wait now time, when manual is written.. Hi Jarmo, Frode, The draft User Guide for 2.6.0 states simply: "When calling CQ you may choose to select CQ: First to reply automatically to the first decoded responder, or CQ: Max Dist to reply to the most distant responder." There is no limitation to only contests. It is not defined in that text for CQ: Max Dist, whether the decision is made after the first decoding round or after the last decoding attempt. If the latter, then in a slow computer that may happen after the start of the next transmission time. 73, Reino OH3mA ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working
Thu, 13 Oct 2022 19:29:48 +0200 Frode Igland via wsjt-devel kirjoitti: Frode, I don't know what it means. I read that text hastly, so, apologize. I stop allways there, where is something mentioned "contest". Not my thing... :) We wait now time, when manual is written.. jarmo, oh1mrr > Hi, Jarmo. > Does that mean that "CQ: Max Dist" is setup to work *only* with the > ARRL International Digital Contest? > Neither the Release Notes nor the -rc4 User Guide say anything about > "CQ: Max Dist", so it is difficult to say. "CQ: Max Dist" looks like > the FT8 version of the "Best S+P" functionality in FT4, which works > also outside contests, although FT4 was developed primarily for > contesting. Then I find it strange that similar functionality in the > general usage FT8 mode should work only in contest, and even only in > one contest of the year. > > The ARRL International Digital Contest ran on 4-5 June 2022, whilst > the WSJT-X 2.6.0-rc1 introducing "CQ: Max Dist" was published only > on 20 June, i.e. shortly after this year's contest. If your > information is correct, I guess it will not be possible to test this > functionality until next June. Then it is strange that it was > introduced almost a year before it was needed or useful. > > The hover-over help text reads "Max* Pts*", not "Max Dist", probably a > small typo. > > 73, Frode LA6VQ > > tor. 13. okt. 2022 kl. 16:33 skrev jarmo via wsjt-devel < > wsjt-devel@lists.sourceforge.net>: > > > Thu, 13 Oct 2022 08:34:37 -0400 > > Dennis W1UE via wsjt-devel > > kirjoitti: > > > > Problem2 in not a problem, hover mouse over text, you can see, that > > shoud wor with ARRL contest. > > > > jarmo, oh1mrr > > > I can also confirm problem #1. It is the same problem that > > > existed in version 2.6.0 RC1,2,3 and 4. > > > > > > Since I use WSJT in combination with N1MM+ for logging, I get a > > > "TCP Error" when the program closes. > > > If I'm not using the combo, WSJT just closes. I have not noticed > > > that the closing occurs when using > > > only FT8; it may also occur when using FT4, but there isn't enough > > > activity on FT4 to see if it happens. > > > > > > A couple of additional observations: > > > 1. At the suggestion of K1JT, I replaced the Hamlib dll of > > > 2.6.0rc4 with the same dll from 2.5.4. The closing > > > seemed to stop. This only works if your rig is supported by the > > > earlier dll. > > > 2. A fresh install of 2.6.0rc4 will enable 20+ hours of operation > > > before it closes. Once it starts closing, it will > > > continually do it. > > > > > > I have not seen the issues with "CQ MAX DIST". Are you sure it's > > > not picking the correct call? > > > 1. Calls without a grid are never selected unless they are the > > > only reply to your CQ. > > > 2. Band/Mode dupes are given a score of zero and only selected if > > > the only caller. > > > 3. Call selection is based on the point score generated by the > > > program calculations; I know SP is further than > > > DL, but if they have the same point total and the DL is before > > > the SP in the decode window, the WSJT will > > > select the DL station to call. > > > > > > Dennis W1UE > > > > > > > > > On Thu, Oct 13, 2022 at 8:21 AM jan0--- via wsjt-devel < > > > wsjt-devel@lists.sourceforge.net> wrote: > > > > > > > I can confirm problem 1, as it happened to me less than an hour > > > > ago, including the orphaned JT9 decoding application. Running > > > > Win 10 on a Lenovo X1 Carbon laptop. I had been on FT8 for > > > > about an hour when it happened. > > > > > > > > > > > > > > > > Ed N4II. > > > > > > > > > > > > > > > > *From:* Frode Igland via wsjt-devel > > > > *Sent:* Thursday, October 13, > > > > 2022 5:06 AM *To:* WSJT software development > > > > *Cc:* Frode Igland > > > > *Subject:* [wsjt-devel] WSJT-X > > > > 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: > > > > None" stops working > > > > > > > > > > > > > > > > I have used -rc4 since it was released and have found it quite > > > > stable with three notable exceptions: > > > > > > > > > > > > > &
Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working
Hi, Jarmo. Does that mean that "CQ: Max Dist" is setup to work *only* with the ARRL International Digital Contest? Neither the Release Notes nor the -rc4 User Guide say anything about "CQ: Max Dist", so it is difficult to say. "CQ: Max Dist" looks like the FT8 version of the "Best S+P" functionality in FT4, which works also outside contests, although FT4 was developed primarily for contesting. Then I find it strange that similar functionality in the general usage FT8 mode should work only in contest, and even only in one contest of the year. The ARRL International Digital Contest ran on 4-5 June 2022, whilst the WSJT-X 2.6.0-rc1 introducing "CQ: Max Dist" was published only on 20 June, i.e. shortly after this year's contest. If your information is correct, I guess it will not be possible to test this functionality until next June. Then it is strange that it was introduced almost a year before it was needed or useful. The hover-over help text reads "Max* Pts*", not "Max Dist", probably a small typo. 73, Frode LA6VQ tor. 13. okt. 2022 kl. 16:33 skrev jarmo via wsjt-devel < wsjt-devel@lists.sourceforge.net>: > Thu, 13 Oct 2022 08:34:37 -0400 > Dennis W1UE via wsjt-devel kirjoitti: > > Problem2 in not a problem, hover mouse over text, you can see, that > shoud wor with ARRL contest. > > jarmo, oh1mrr > > I can also confirm problem #1. It is the same problem that existed in > > version 2.6.0 RC1,2,3 and 4. > > > > Since I use WSJT in combination with N1MM+ for logging, I get a "TCP > > Error" when the program closes. > > If I'm not using the combo, WSJT just closes. I have not noticed > > that the closing occurs when using > > only FT8; it may also occur when using FT4, but there isn't enough > > activity on FT4 to see if it happens. > > > > A couple of additional observations: > > 1. At the suggestion of K1JT, I replaced the Hamlib dll of 2.6.0rc4 > > with the same dll from 2.5.4. The closing > > seemed to stop. This only works if your rig is supported by the > > earlier dll. > > 2. A fresh install of 2.6.0rc4 will enable 20+ hours of operation > > before it closes. Once it starts closing, it will > > continually do it. > > > > I have not seen the issues with "CQ MAX DIST". Are you sure it's not > > picking the correct call? > > 1. Calls without a grid are never selected unless they are the only > > reply to your CQ. > > 2. Band/Mode dupes are given a score of zero and only selected if the > > only caller. > > 3. Call selection is based on the point score generated by the program > > calculations; I know SP is further than > > DL, but if they have the same point total and the DL is before the SP > > in the decode window, the WSJT will > > select the DL station to call. > > > > Dennis W1UE > > > > > > On Thu, Oct 13, 2022 at 8:21 AM jan0--- via wsjt-devel < > > wsjt-devel@lists.sourceforge.net> wrote: > > > > > I can confirm problem 1, as it happened to me less than an hour ago, > > > including the orphaned JT9 decoding application. Running Win 10 on > > > a Lenovo X1 Carbon laptop. I had been on FT8 for about an hour > > > when it happened. > > > > > > > > > > > > Ed N4II. > > > > > > > > > > > > *From:* Frode Igland via wsjt-devel > > > *Sent:* Thursday, October 13, > > > 2022 5:06 AM *To:* WSJT software development > > > *Cc:* Frode Igland > > > *Subject:* [wsjt-devel] WSJT-X 2.6.0-rc4: > > > Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops > > > working > > > > > > > > > > > > I have used -rc4 since it was released and have found it quite > > > stable with three notable exceptions: > > > > > > > > > > > > *1. Sudden closing in FT8 after extended periods of operation* > > > > > > After an extended period of use in FT8 mode (normally more than two > > > hours), WSJT-X may close down abruptly. The closing happens at the > > > start of an FT8 sequence. I have never experienced closing on FT4, > > > but then I have very rarely worked FT4 for extended periods. To > > > start again, an orphaned JT9 decoding application first has to be > > > terminated in the Task Manager. This issue started with WSJT-X > > > 2.6.0-rc1 and still happens. > > > > > > > > > > > > *2. "CQ: Max Dist" doesn't work* > > > > > > After selecting
Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working
Hi, Dennis. I will try the Hamlib dll from v2.5.4, a version where I had no problems with sudden closing. I cannot say whether the sudden closings apply to FT4, but I cannot remember noticing the sudden closing in FT4, whilst it happens now and then with FT8, as described. Re the "CQ: Max Dist" issue: Working from Norway, I have observed a locator from Germany being selected over a locator from the USA, with both stations being new to me. I am aware that the callers with no locator is placed last in the queue. 73, Frode LA6VQ tor. 13. okt. 2022 kl. 14:39 skrev Dennis W1UE via wsjt-devel < wsjt-devel@lists.sourceforge.net>: > I can also confirm problem #1. It is the same problem that existed in > version 2.6.0 RC1,2,3 and 4. > > Since I use WSJT in combination with N1MM+ for logging, I get a "TCP > Error" when the program closes. > If I'm not using the combo, WSJT just closes. I have not noticed that the > closing occurs when using > only FT8; it may also occur when using FT4, but there isn't enough > activity on FT4 to see if it happens. > > A couple of additional observations: > 1. At the suggestion of K1JT, I replaced the Hamlib dll of 2.6.0rc4 with > the same dll from 2.5.4. The closing > seemed to stop. This only works if your rig is supported by the earlier > dll. > 2. A fresh install of 2.6.0rc4 will enable 20+ hours of operation before > it closes. Once it starts closing, it will > continually do it. > > I have not seen the issues with "CQ MAX DIST". Are you sure it's not > picking the correct call? > 1. Calls without a grid are never selected unless they are the only reply > to your CQ. > 2. Band/Mode dupes are given a score of zero and only selected if the only > caller. > 3. Call selection is based on the point score generated by the program > calculations; I know SP is further than > DL, but if they have the same point total and the DL is before the SP in > the decode window, the WSJT will > select the DL station to call. > > Dennis W1UE > > > On Thu, Oct 13, 2022 at 8:21 AM jan0--- via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > >> I can confirm problem 1, as it happened to me less than an hour ago, >> including the orphaned JT9 decoding application. Running Win 10 on a >> Lenovo X1 Carbon laptop. I had been on FT8 for about an hour when it >> happened. >> >> >> >> Ed N4II. >> >> >> >> *From:* Frode Igland via wsjt-devel >> *Sent:* Thursday, October 13, 2022 5:06 AM >> *To:* WSJT software development >> *Cc:* Frode Igland >> *Subject:* [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max >> Dist" doesn't work, "CQ: None" stops working >> >> >> >> I have used -rc4 since it was released and have found it quite stable >> with three notable exceptions: >> >> >> >> *1. Sudden closing in FT8 after extended periods of operation* >> >> After an extended period of use in FT8 mode (normally more than two >> hours), WSJT-X may close down abruptly. The closing happens at the start of >> an FT8 sequence. I have never experienced closing on FT4, but then I have >> very rarely worked FT4 for extended periods. To start again, an orphaned >> JT9 decoding application first has to be terminated in the Task Manager. >> This issue started with WSJT-X 2.6.0-rc1 and still happens. >> >> >> >> *2. "CQ: Max Dist" doesn't work* >> >> After selecting "CQ: Max Dist", WSJT-X still selects the station first >> decoded, notwithstanding the distance. It makes no difference whether "CQ: >> Max Dist" is selected after "CQ: None" or "CQ: First" or if "CQ: Max Dist" >> was selected on start-up before first CQ. >> >> >> >> *3. "CQ: None" stops working after a while* >> >> I often call CQ DX with the "CQ: None" setting, to be able to select >> which DX station to work. This normally works well, but suddenly WSJT-X may >> start answering the first station decoded automatically, without being >> selected manually by me. Sometimes, reselecting "CQ: None" helps, and >> sometimes I have to close and reopen WSJT-X and select "CQ: None" before >> calling CQ. >> >> >> >> These are my experiences with WSJT-X 2.6.0-rc4. >> >> >> >> 73, Frode LA6VQ >> >> >> >> >> ___ >> wsjt-devel mailing list >> 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 > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working
For those having problems please provide some debug to see if we can figure this out. Please place this file as described belowhttps://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0 C:\Users\[username]\AppData\Local\WSJT-X The WSJT-X_Rigcontrol.log file will be in the same location For Linux put it in ~/.config The WSJT-X_Rigcontrol.log file will be here: ~/.local/share/WSJT-X For MacOS put it in /Users/[username]/Library/Preferences Restart WSJT-X and duplicate the problem.Shut down WSJT-X Then send me the WSJT-X_RigControl.log fileMike W9MDB On Thursday, October 13, 2022 at 09:33:26 AM CDT, jarmo via wsjt-devel wrote: Thu, 13 Oct 2022 08:34:37 -0400 Dennis W1UE via wsjt-devel kirjoitti: Problem2 in not a problem, hover mouse over text, you can see, that shoud wor with ARRL contest. jarmo, oh1mrr > I can also confirm problem #1. It is the same problem that existed in > version 2.6.0 RC1,2,3 and 4. > > Since I use WSJT in combination with N1MM+ for logging, I get a "TCP > Error" when the program closes. > If I'm not using the combo, WSJT just closes. I have not noticed > that the closing occurs when using > only FT8; it may also occur when using FT4, but there isn't enough > activity on FT4 to see if it happens. > > A couple of additional observations: > 1. At the suggestion of K1JT, I replaced the Hamlib dll of 2.6.0rc4 > with the same dll from 2.5.4. The closing > seemed to stop. This only works if your rig is supported by the > earlier dll. > 2. A fresh install of 2.6.0rc4 will enable 20+ hours of operation > before it closes. Once it starts closing, it will > continually do it. > > I have not seen the issues with "CQ MAX DIST". Are you sure it's not > picking the correct call? > 1. Calls without a grid are never selected unless they are the only > reply to your CQ. > 2. Band/Mode dupes are given a score of zero and only selected if the > only caller. > 3. Call selection is based on the point score generated by the program > calculations; I know SP is further than > DL, but if they have the same point total and the DL is before the SP > in the decode window, the WSJT will > select the DL station to call. > > Dennis W1UE > > > On Thu, Oct 13, 2022 at 8:21 AM jan0--- via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > > I can confirm problem 1, as it happened to me less than an hour ago, > > including the orphaned JT9 decoding application. Running Win 10 on > > a Lenovo X1 Carbon laptop. I had been on FT8 for about an hour > > when it happened. > > > > > > > > Ed N4II. > > > > > > > > *From:* Frode Igland via wsjt-devel > > *Sent:* Thursday, October 13, > > 2022 5:06 AM *To:* WSJT software development > > *Cc:* Frode Igland > > *Subject:* [wsjt-devel] WSJT-X 2.6.0-rc4: > > Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops > > working > > > > > > > > I have used -rc4 since it was released and have found it quite > > stable with three notable exceptions: > > > > > > > > *1. Sudden closing in FT8 after extended periods of operation* > > > > After an extended period of use in FT8 mode (normally more than two > > hours), WSJT-X may close down abruptly. The closing happens at the > > start of an FT8 sequence. I have never experienced closing on FT4, > > but then I have very rarely worked FT4 for extended periods. To > > start again, an orphaned JT9 decoding application first has to be > > terminated in the Task Manager. This issue started with WSJT-X > > 2.6.0-rc1 and still happens. > > > > > > > > *2. "CQ: Max Dist" doesn't work* > > > > After selecting "CQ: Max Dist", WSJT-X still selects the station > > first decoded, notwithstanding the distance. It makes no difference > > whether "CQ: Max Dist" is selected after "CQ: None" or "CQ: First" > > or if "CQ: Max Dist" was selected on start-up before first CQ. > > > > > > > > *3. "CQ: None" stops working after a while* > > > > I often call CQ DX with the "CQ: None" setting, to be able to > > select which DX station to work. This normally works well, but > > suddenly WSJT-X may start answering the first station decoded > > automatically, without being selected manually by me. Sometimes, > > reselecting "CQ: None" helps, and sometimes I have to close and > > reopen WSJT-X and select "CQ: None" before calling CQ. > > > > > > > > These are my experiences with WSJT-X 2.6.0-rc4. > > > > > > > > 73, Frode LA6VQ > > > > > > > > > > ___ > > wsjt-devel mailing list > > 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 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working
Thu, 13 Oct 2022 08:34:37 -0400 Dennis W1UE via wsjt-devel kirjoitti: Problem2 in not a problem, hover mouse over text, you can see, that shoud wor with ARRL contest. jarmo, oh1mrr > I can also confirm problem #1. It is the same problem that existed in > version 2.6.0 RC1,2,3 and 4. > > Since I use WSJT in combination with N1MM+ for logging, I get a "TCP > Error" when the program closes. > If I'm not using the combo, WSJT just closes. I have not noticed > that the closing occurs when using > only FT8; it may also occur when using FT4, but there isn't enough > activity on FT4 to see if it happens. > > A couple of additional observations: > 1. At the suggestion of K1JT, I replaced the Hamlib dll of 2.6.0rc4 > with the same dll from 2.5.4. The closing > seemed to stop. This only works if your rig is supported by the > earlier dll. > 2. A fresh install of 2.6.0rc4 will enable 20+ hours of operation > before it closes. Once it starts closing, it will > continually do it. > > I have not seen the issues with "CQ MAX DIST". Are you sure it's not > picking the correct call? > 1. Calls without a grid are never selected unless they are the only > reply to your CQ. > 2. Band/Mode dupes are given a score of zero and only selected if the > only caller. > 3. Call selection is based on the point score generated by the program > calculations; I know SP is further than > DL, but if they have the same point total and the DL is before the SP > in the decode window, the WSJT will > select the DL station to call. > > Dennis W1UE > > > On Thu, Oct 13, 2022 at 8:21 AM jan0--- via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > > I can confirm problem 1, as it happened to me less than an hour ago, > > including the orphaned JT9 decoding application. Running Win 10 on > > a Lenovo X1 Carbon laptop. I had been on FT8 for about an hour > > when it happened. > > > > > > > > Ed N4II. > > > > > > > > *From:* Frode Igland via wsjt-devel > > *Sent:* Thursday, October 13, > > 2022 5:06 AM *To:* WSJT software development > > *Cc:* Frode Igland > > *Subject:* [wsjt-devel] WSJT-X 2.6.0-rc4: > > Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops > > working > > > > > > > > I have used -rc4 since it was released and have found it quite > > stable with three notable exceptions: > > > > > > > > *1. Sudden closing in FT8 after extended periods of operation* > > > > After an extended period of use in FT8 mode (normally more than two > > hours), WSJT-X may close down abruptly. The closing happens at the > > start of an FT8 sequence. I have never experienced closing on FT4, > > but then I have very rarely worked FT4 for extended periods. To > > start again, an orphaned JT9 decoding application first has to be > > terminated in the Task Manager. This issue started with WSJT-X > > 2.6.0-rc1 and still happens. > > > > > > > > *2. "CQ: Max Dist" doesn't work* > > > > After selecting "CQ: Max Dist", WSJT-X still selects the station > > first decoded, notwithstanding the distance. It makes no difference > > whether "CQ: Max Dist" is selected after "CQ: None" or "CQ: First" > > or if "CQ: Max Dist" was selected on start-up before first CQ. > > > > > > > > *3. "CQ: None" stops working after a while* > > > > I often call CQ DX with the "CQ: None" setting, to be able to > > select which DX station to work. This normally works well, but > > suddenly WSJT-X may start answering the first station decoded > > automatically, without being selected manually by me. Sometimes, > > reselecting "CQ: None" helps, and sometimes I have to close and > > reopen WSJT-X and select "CQ: None" before calling CQ. > > > > > > > > These are my experiences with WSJT-X 2.6.0-rc4. > > > > > > > > 73, Frode LA6VQ > > > > > > > > > > ___ > > wsjt-devel mailing list > > 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
Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working
I can also confirm problem #1. It is the same problem that existed in version 2.6.0 RC1,2,3 and 4. Since I use WSJT in combination with N1MM+ for logging, I get a "TCP Error" when the program closes. If I'm not using the combo, WSJT just closes. I have not noticed that the closing occurs when using only FT8; it may also occur when using FT4, but there isn't enough activity on FT4 to see if it happens. A couple of additional observations: 1. At the suggestion of K1JT, I replaced the Hamlib dll of 2.6.0rc4 with the same dll from 2.5.4. The closing seemed to stop. This only works if your rig is supported by the earlier dll. 2. A fresh install of 2.6.0rc4 will enable 20+ hours of operation before it closes. Once it starts closing, it will continually do it. I have not seen the issues with "CQ MAX DIST". Are you sure it's not picking the correct call? 1. Calls without a grid are never selected unless they are the only reply to your CQ. 2. Band/Mode dupes are given a score of zero and only selected if the only caller. 3. Call selection is based on the point score generated by the program calculations; I know SP is further than DL, but if they have the same point total and the DL is before the SP in the decode window, the WSJT will select the DL station to call. Dennis W1UE On Thu, Oct 13, 2022 at 8:21 AM jan0--- via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > I can confirm problem 1, as it happened to me less than an hour ago, > including the orphaned JT9 decoding application. Running Win 10 on a > Lenovo X1 Carbon laptop. I had been on FT8 for about an hour when it > happened. > > > > Ed N4II. > > > > *From:* Frode Igland via wsjt-devel > *Sent:* Thursday, October 13, 2022 5:06 AM > *To:* WSJT software development > *Cc:* Frode Igland > *Subject:* [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max > Dist" doesn't work, "CQ: None" stops working > > > > I have used -rc4 since it was released and have found it quite stable with > three notable exceptions: > > > > *1. Sudden closing in FT8 after extended periods of operation* > > After an extended period of use in FT8 mode (normally more than two > hours), WSJT-X may close down abruptly. The closing happens at the start of > an FT8 sequence. I have never experienced closing on FT4, but then I have > very rarely worked FT4 for extended periods. To start again, an orphaned > JT9 decoding application first has to be terminated in the Task Manager. > This issue started with WSJT-X 2.6.0-rc1 and still happens. > > > > *2. "CQ: Max Dist" doesn't work* > > After selecting "CQ: Max Dist", WSJT-X still selects the station first > decoded, notwithstanding the distance. It makes no difference whether "CQ: > Max Dist" is selected after "CQ: None" or "CQ: First" or if "CQ: Max Dist" > was selected on start-up before first CQ. > > > > *3. "CQ: None" stops working after a while* > > I often call CQ DX with the "CQ: None" setting, to be able to select which > DX station to work. This normally works well, but suddenly WSJT-X may start > answering the first station decoded automatically, without being selected > manually by me. Sometimes, reselecting "CQ: None" helps, and sometimes I > have to close and reopen WSJT-X and select "CQ: None" before calling CQ. > > > > These are my experiences with WSJT-X 2.6.0-rc4. > > > > 73, Frode LA6VQ > > > > > ___ > wsjt-devel mailing list > 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
Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working
I can confirm problem 1, as it happened to me less than an hour ago, including the orphaned JT9 decoding application. Running Win 10 on a Lenovo X1 Carbon laptop. I had been on FT8 for about an hour when it happened. Ed N4II. From: Frode Igland via wsjt-devel Sent: Thursday, October 13, 2022 5:06 AM To: WSJT software development Cc: Frode Igland Subject: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working I have used -rc4 since it was released and have found it quite stable with three notable exceptions: 1. Sudden closing in FT8 after extended periods of operation After an extended period of use in FT8 mode (normally more than two hours), WSJT-X may close down abruptly. The closing happens at the start of an FT8 sequence. I have never experienced closing on FT4, but then I have very rarely worked FT4 for extended periods. To start again, an orphaned JT9 decoding application first has to be terminated in the Task Manager. This issue started with WSJT-X 2.6.0-rc1 and still happens. 2. "CQ: Max Dist" doesn't work After selecting "CQ: Max Dist", WSJT-X still selects the station first decoded, notwithstanding the distance. It makes no difference whether "CQ: Max Dist" is selected after "CQ: None" or "CQ: First" or if "CQ: Max Dist" was selected on start-up before first CQ. 3. "CQ: None" stops working after a while I often call CQ DX with the "CQ: None" setting, to be able to select which DX station to work. This normally works well, but suddenly WSJT-X may start answering the first station decoded automatically, without being selected manually by me. Sometimes, reselecting "CQ: None" helps, and sometimes I have to close and reopen WSJT-X and select "CQ: None" before calling CQ. These are my experiences with WSJT-X 2.6.0-rc4. 73, Frode LA6VQ ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working
I have used -rc4 since it was released and have found it quite stable with three notable exceptions: *1. Sudden closing in FT8 after extended periods of operation* After an extended period of use in FT8 mode (normally more than two hours), WSJT-X may close down abruptly. The closing happens at the start of an FT8 sequence. I have never experienced closing on FT4, but then I have very rarely worked FT4 for extended periods. To start again, an orphaned JT9 decoding application first has to be terminated in the Task Manager. This issue started with WSJT-X 2.6.0-rc1 and still happens. *2. "CQ: Max Dist" doesn't work* After selecting "CQ: Max Dist", WSJT-X still selects the station first decoded, notwithstanding the distance. It makes no difference whether "CQ: Max Dist" is selected after "CQ: None" or "CQ: First" or if "CQ: Max Dist" was selected on start-up before first CQ. *3. "CQ: None" stops working after a while* I often call CQ DX with the "CQ: None" setting, to be able to select which DX station to work. This normally works well, but suddenly WSJT-X may start answering the first station decoded automatically, without being selected manually by me. Sometimes, reselecting "CQ: None" helps, and sometimes I have to close and reopen WSJT-X and select "CQ: None" before calling CQ. These are my experiences with WSJT-X 2.6.0-rc4. 73, Frode LA6VQ ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
