Re: [wsjt-devel] Made the spot counter work for WSPR.
Tim If you know where the spot counter is for FT8, that is where the spot counter is for WSPR. It’s along the bottom line of the WSJT window. Dennis W1UE On Mon, Mar 11, 2024 at 14:42 Tim Urban via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > > I the Release: WSJT-X 2.7.0-rc3 January 1, 2024 there is a item -- - > Made the spot counter work for WSPR. > > A search of > https://wsjt.sourceforge.io/wsjtx-doc/wsjtx-main-2.7.0-rc3.html#INTRO > finds no reference to spot counter > > Is there documentation for "the spot counter"? > > > 73 > > Tim > > N4WLO > > > > ___ > 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] FT8 on 160m with Beverage antenna
Glenn A beverage antenna will often produce weaker signals than, say, an inverted L. However, it will decrease the noise on the signal, and make it easier to copy, which should make it easier to decode. Dennis W1UE On Mon, Nov 13, 2023 at 4:29 PM Glenn Williams via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > This is a theory question. There is a bit of FT8 on 160m. Does use of a > Beverage Antenna to get more signal raise the S/N value? Would that > antenna help with receiving weaker signals (a variation of that S/N > question)? > --73, Glenn, AF8C > > -- > This email has been checked for viruses by Avast antivirus software. > www.avast.com > > > ___ > 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] Extra characters in ALL.TXT for F/H
Glenn Please read section 12 of the online documentation. It explains what you want to know. Dennis W1UE On Sat, Oct 21, 2023 at 8:27 AM Glenn Williams via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi, > The following line of text is found once in my huge ALL.TXT file. Note > the "a4" far to the right. > > V2.6.1 Windows 10 USB-USB to TS590SG DATA port, Special Op F/H, Split->Rig > > "231005_00530024.911 Rx FT8-20 0.0 720 AF8C RR73; NR4N > -14 a4" > > The following 2 lines of text are found in K8LBT's ALL.TXT file. Note > the "a3" far to the right. (I transcribed this from his email image of > file; in case the columns appear to have misalignment - it's just my > typing.) I do not know whether his file contains more than two instances. > > V2.5.4Windows 10 through Signalink USB, TS590S, microphone port, > Special Op F/H, SPLIT-> None > > "231015_114530 1.836 Rx FT8-20 1.2 364 K8LBT W8S -15 > a3" > ... > ... > "231015_115000 1.836 Rx FT8-19 1.1 304 K8LBT W8S -19 > a3" > > Explanation would be interesting to see. Should I send any of my files > such as a log? > > --73, Glenn, AF8C > > -- > This email has been checked for viruses by Avast antivirus software. > www.avast.com > > > ___ > 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] Need Hamlib Testers for IC7300 and IC7600
Thank you Gene! UE On Thu, Jun 29, 2023 at 8:31 AM Gene Hinkle via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > K5PA, Yes, for IC-7300, IC-705, IC-7610 > > Gene, K5PA > > > Gene > > > On Jun 29, 2023, at 6:03 AM, Dennis W1UE via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > > > > > Anyone around that can test the upcoming Hamlib dispersal with the RC2 > software that's coming out in the near future? Instructions will be > provided to volunteers. Its simple, probably won't take you 30 minutes. > > > > Dennis w1UE > > > > ___ > > 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
[wsjt-devel] Need Hamlib Testers for IC7300 and IC7600
Anyone around that can test the upcoming Hamlib dispersal with the RC2 software that's coming out in the near future? Instructions will be provided to volunteers. Its simple, probably won't take you 30 minutes. Dennis w1UE ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] ARRL Digi contest log converting to Cabrillo
Hannu Use N1mM+. Setup the contest i nN1mM+, then import the adi file into N1MM+. Then you can write the Cabrillo file from that. Dennis W1UE On Mon, Jun 5, 2023 at 2:48 AM Hannu Eloranta via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > So Cabrillo log creation didn't work. > How do I convert wsjtx_log.adi to Cabrillo format? (Easiest way) > > 73 OG3Z Hannu > ___ > 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] Unable to create shared memory segment in 2.7.0-rc1
I have seen this twice before, all while switching configurations.
However, not
every time I switch configurations do I see it. It only happens once in a
while.
Using 2.7.0RC1 Improved, Win 10/11.
Dennis W1UE
On Thu, Jun 1, 2023 at 2:36 PM Rick via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> Hi
>
> I have the same situation.
>
> Running Linux Mint 20.3 and wsjtx2.7.0-rc1 built from source.
> The Optimising Decoder FFT dialog only pops up (intentionally) if the fail
> to mem_qmap dialog is on the screen for some time although it's less than
> the 15 seconds stated in the code comments, more like 1.5. So not related
> to the issue.
>
> Dismissing both dialogs allows wsjtx to run normally (as far as I can see)
> on linux.
>
> I did a bit of diagnostics. The code is at widgets | mainwindow.cpp lines
> 472 -47 9. I used the default config and a clone of the default config both
> unchanged.
>
> //Attach or create a memory segment to be shared with QMAP.
>
> int memSize=4096;
>
> if(!mem_qmap.attach()) {
>
> if(!mem_qmap.create(memSize)) {
>
> MessageBox::information_message (this,
>
> "Unable to create shared memory segment mem_qmap.");
>
> }
>
> }
>
> This code runs when wsjtx is first instantiated, before any app windows
> appear. It creates the shared memory segment and links the app to it OK.
> Normal operation proceeds. When the Op changes to another configuration the
> code is run again and *wsjtx is still attached*. (mem_qmap.isAttached
> returns true). Consequently mem_qmap.attach fails and the code tries to
> create the shared memory segment again which also fails because the
> previous shared memory segment and key still exist. Hence the dialog
>
> Should mem_qmap and it's key have been disposed of when wsjtx terminated
> as the configuration was changed? Perhaps it would be better to test
> whether the shared memory segment exists and is attached or not rather than
> just attempting to attach it.
> My reading of the situation is that both dialogs can safely be dismissed
> and wsjtx will run OK since the shared memory segment is attached.
>
> 73s
>
> Rick (GM4JIB)
>
> On 01/06/2023 17:14, Erik Icket via wsjt-devel wrote:
>
> Dear developers,
>
> When switching to a predefined configuration, an information dialog pops up
> with the message 'Unable to create shared memory segment mem-qmap',
> followed by another modal message a few secs later 'Optimizing FFTs for your
> CPU. Please be patient ...'
> After that, the program does not respond anymore. Aborting the program and
> restarting brings back the original config.
>
> 73's Erik
> ON4PB
>
>
>
>
>
>
>
>
> ___
> wsjt-devel mailing
> listwsjt-devel@lists.sourceforge.nethttps://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] Hamlib Beta Testing Group needed
George What operating system are you using? Since you're the first with a 7610, I"d like to include you as a tester. Dennis W1UE On Sat, May 13, 2023 at 5:01 PM WB5JJJ via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > This also affected the IC-7610, but the new file fixed the problem. > > 73's > George - WB5JJJ > HoIP - 100105 > > > On Sat, May 13, 2023 at 3:29 AM Tom M0LTE via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > >> Hey Uwe >> >> While manual testing could probably never be eliminated in the case of >> hamlib, has there been any consideration of creating test harnesses to >> remove/reduce the need for manual testing? >> >> It strikes me that there could be potential to capture test cases from >> manual testing with real rigs, then at least there would be regression >> tests. Future bug fixes could have test cases added to prevent further >> regression, again without requiring physical radios and manual testing. >> >> Apologies if I am not the first to ask this question. >> >> Kind regards >> Tom M0LTE >> >> On Sat, 13 May 2023 at 08:11, Uwe, DG2YCB via wsjt-devel < >> wsjt-devel@lists.sourceforge.net> wrote: >> >>> Dear WSJT-X users, >>> >>> Please allow me to summarize again here on this email reflector a topic >>> that is very important to me and to all of us. My original post was on >>> https://groups.io/g/wsjtgroup, so maybe it's best if you join the >>> discussion there. >>> >>> Despite great personal commitment of the hamlib developers it has >>> unfortunately happened very often that immediately after a new WSJT-X >>> release serious problems with one or another hamlib rig driver become >>> apparent. If something like this happens over and over again, it shows that >>> there is a *systematic* error somewhere. In my opinion this is due to >>> the fact that *too few* users try the current development versions of >>> hamlib, so that errors are detected *too late*. Keep in mind that >>> hamlib drivers often change as they evolve. >>> >>> So I* would like to ask you all that enough OMs act as hamlib bata >>> tester in the future.* For those who own one of the rigs below and work >>> on Windows, just do the following every 2, 3 or 4 weeks: >>> >>>1. Download the daily updated libhamlib-4.dll file available on >>>https://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll. >>>2. Copy the file to the bin folder of your WSJT-X installation (i.e. >>>usually c:\WSJT\wsjtx\bin). Rename the existing libhamlib-4.dll file >>>beforehand so you can use it again later. >>>3. Start WSJT-X (or the respective variant), connect your rig via >>>hamlib (i.e. *not* via OmniRig, HRD, DXLabSuite, etc.) and check if >>>the CAT control runs properly. >>>4. If anything is not working properly, please contact Mike W9MDB >>>via direct email, so he or his team can fix the bug in time. >>>5. If everything works fine, keep the new libhamlib-4.dll file, >>>otherwise delete it and rename the previously used one. >>>6. In the future I would like to contact you before a new WSJT-X or >>>wsjt-x_improved release to be able to choose a bug free hamlib version. >>> >>> In my opinion, at least the following rigs need to be tested regularly >>> regarding hamlib: >>> >>>- Yaesu: FT-991, FT-101, FT-847 >>>- Kenwood: which models? >>>- Icom: IC-7300, IC-9100, IC-9700, IC-705 >>>- Elecraft: KX3, what else? >>>- FlexRadio: which models? >>>- Anything else? >>> >>> *Now, the most important thing is that **one of you* * organizes it*. I >>> can't do it myself because of time constraints, and Mike W9MDB is also >>> overloaded with work. >>> >>> For example, what about the people who have stood out so intensively in >>> the last few days with posts about something trivial? Wouldn't one of you >>> like to take over and invest your energy there? *Seriously: Who?* *Y* >>> *ou are now requested! * >>> I mean, what needs to be done is evident: >>> >>>1. Create a list of commonly used rig models. >>>2. Find beta testers for each of these models and assign >>>responsibilities. >>>3. Get an overview of the status quo and summarize the results >>>clearly. >>> >>> Something like this can be done e.g. with a simple Excel file: >>> >>> >>> >>> >>> It's sad enough that obviously, the hamlib development team can't do >>> something so essential themselves. But *this definitely has to come now*, >>> because we can't get the next frustration after every new WSJT-X release. >>> Makes no sense! >>> >>> So, again: >>> >>> *Who of you will take this in hand and organize such a systematic beta >>> testing? *I do not want to see one more "stupid" post as long as this >>> problem is not solved, hi, hi! >>> >>> 73 de Uwe, DG2YCB >>> ___ >>> wsjt-devel mailing list >>> wsjt-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>> >>
Re: [wsjt-devel] Release Candidate WSJT-X 2.7.0-rc1
John What is your operating system? Thanks! Dennis W1UE On Sat, May 13, 2023 at 8:38 AM g4kla--- via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Mike, > > No problem with Hamlib-4.6 on Kenwood TS870s. Working correctly with dual > VFOs (Split Operation: Rig) > > — John G4KLA > > ___ > 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] Volunteers Needed- Hamlib Reviews
I'm looking to get a group of ops together to review Hamlib files prior to the release of new ones. Any op with any rig is eligible to apply. If you're interested, please specify your rig, version of Windows (or your OS), and any other specifics that may be applicable. Our immediate task is to review the last several Hamlib files, and see if we have a "best working" file that can be released with the upcoming version of WSJT-improved. After that, we will be looking to check out Hamlib files PRIOR to their release. Instructions will be provided on how to do the testing. Dennis W1UE ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Bug in RC5
Found what appears to be a bug. If you set CQ: to “Max Dist”, and set the special Activity to be the FT Roundup contest. Then call a normal CQ. When you get an answer or several, the program does not move any of the callers and generate the standard messages. WSJT just calls another CQ. If you reset the CQ: to “First”, the automatic pull and sequencing of the messages works correctly. This error is easy to reproduce now, will be less easy to reproduce after the test. Dennis W1UE ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] v2.6.0-rc4 observations
Dave I’ve operated a lot as the Fox from HQ9X the past week. Let me assure you, if u try to operate as the Fox on one of the standard frequencies, you get a warning box and PTT won’t energize, ie wSJT won’t xmit. Dennis HQ9X for one more day! On Mon, Nov 28, 2022 at 08:02 Dave Bernheisel via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > I have noticed that if the Hound mode is enabled and on a frequency that > is not in the list of frequencies, > > switching from Hound mode to FT8 also changes the frequency to one of the > frequencies in the dropdown list. > > > A fox was operating in F/H mode on one of the default frequencies, and I > changed to Hound mode. A station, not the Fox, > > called me. I responded to the call and then discovered that both RRR and > RR73 were disabled. I did not find this in the users guide for > > F/H operation. I realize that the Fox was not following the rules. Since > the usual frequencies are in the dropdown, perhaps > > WSJT-X should prohibit or nag the Fox when operating on one of the known > frequencies for normal operation. A warning to the hound > > would not be a bad idea, in my opinion. > > 73, > > Dave Bernheisel, N2DPF > ___ > 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] YBDXPI Contest Performance
GM Joe Summation of Yesterdays info: 1 .Mike K1IU is experiencing crashes with the 2.6.0 rc files. He uses LOG4OM2 in conjunction with WSJT. 2. Tony ZL3HAM is experiencing crashes with the 2.6.0 rc files. He uses DXLab Suite and JTAlert with WSJT. 3. Dennis W1UE and Ty K3MM are both experiencing crashes with the 2.60 rc files. They use N1MM+. I have yet to see any reports that 2.5.4 has caused crashes. When I used it, I did not experience crashes. When 2.6.0 RC4 came out, it took 20+ hours of operating before I had a crash. Once it crashed, the next crash didn't take anywhere near as long. Still, there is no time frame for crashes; it may crash 5 times in an hour, then not crash for 4 hours. I'm retired and have plenty of time to test out any revised files. Tracking down a fix for a crash that happens sporadically can be quite time consuming; if any member of the development team needs an extended period of operating time to test out changes, please don't hesitate to get in touch with me. Dennis W1UE On Mon, Oct 24, 2022 at 1:53 PM Joe Taylor via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi Dennis, > > Thanks for your helpful report. I guess it's not yet perfectly clear > whether using the hamlib4.dll from v2.5.4 helped, or whether you were > just lucky for the last 7 hours of the contest. > > In any event, it seems that there must be some kind of negotiation issue > between N1MM+ and WSJT-X. Somehow we need to isolate this problem and > see what can be done to make the negotiation more forgiving of delays, > or whatever, and not simply shut down the channel. > > -- Joe, K1JT > > On 10/24/2022 8:54 AM, Dennis W1UE via wsjt-devel wrote: > > I started the contest using 2.6.0RC4. I operate with WSJT in > > conjunction with N1MM+, using the DX Lab Suite Commander to a K30/Mini, > > through a Remote Rig > > unit to the remote transmitting site. I used SO1V mode for this > > contest- no SO2R. The combination worked perfectly for about 6 hours, > > then the WSJT-X for EW1 just "disappeared" with the TCP error from > > N1MM+. I opened Task Manager, killed the orphan JT process, and was > > back on the air- for maybe 15 minutes, when it happened again. This > > time I Restarted the computer, started up again, and within 30 minutes > > it happened again. > > > > Remembering a conversation i had with Joe K1jt a while ago, I then > > substituted the 2.5.4 hamlib4.dll for the 2.6.0 dll, restarted the > > computer, and started operating again. It lasted about 30 minutes, and > > the same error again. I deleted the orphan JT9 process and started up > > again. That was the end of the errors- it never happened again for the > > next 7 hours of operation. > > > > In his write-up on 3830, Ty, K3MM, also tried 2.6.0rc4 to start the > > contest. Within an hour of the start, he had his WSJT-X EW2 window just > > disappear. Rather than fight it, he went back to 2.5.4 and had no more > > "disappearances" the rest of the contest (about 27 hours). > > > > I typically use 100w or less in contests, but did use 800-1000w for this > > contest. I saw no difference in "disappearances" between the two power > > categories. > > > > Thanks to all for their work in supporting WSJT-X. Its truly a great > > program! > > > > Dennis w1UE > > > > > > > > > > > > ___ > > 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] Program crash
Mike Are you using WSJT with N1MM, JTAlert, or any other linked program, or are you using it standalone? How does it crash- does the Entry Window just “disappear” without an error message, or ? Dennis W1UE On Mon, Oct 24, 2022 at 17:27 mpcorey--- via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > It would be helpful to determine what is causing the orphaned JT9.exe > crash. Like others I’ve been experiencing it consistently since trying the > beta. Mostly recently, four crashes in less than five minutes after using > the program for several hours and many Q’s. > > > > Mike, KI1U > > > > > > > > *From:* Alan via wsjt-devel > *Sent:* Monday, October 24, 2022 4:13 PM > *To:* WSJT software development > *Cc:* Alan > *Subject:* Re: [wsjt-devel] Program crash > > > > Hi, I've experienced this intermittent orphaning of jt9.exe, reported by > me in an earlier version. I couldn't find any obvious root cause. > > > > Two suggestions: > > > > 1. Put something in the user guide about stopping the orphan process > rather than rebooting the computer? > > > > 2. Is there a way of globally trapping fatal errors such that the program > exits more gracefully? > > > > The latter might also assist in finding the fault? > > > > If not directly then maybe run it in its own container so if that sees a > fatal error in its content it can close nicely? > > > > Alan G0TLK, sent from my mobile device > > > > On 24 October 2022 20:09:58 Joe Taylor via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > > > Tony -- > > > > Yes, you were using the executable called jt9.exe. That program > > provides the decoding for all slow modes in WSJT-X. > > > > Rebooting is not necessary. Simply use Windows Taskmaster to kill the > > still-executing jt9.exe. > > > > A report of program failure is useful only if you can provide details of > > what may have caused the crash. Obviously it doesn't happen most of the > > time, or we would not have released the beta-test version If possible, > > we need to know what was special about your usage that resulted in a crash. > > > > -- 73, Joe, K1JT > > > > On 10/24/2022 2:16 PM, Tony ZL3HAM via wsjt-devel wrote: > > Hi Dennis, > > > > I use DX Lab Suite and JT Alert and I got a Fatal Error message and also > > one that said JT9 failed to close but I wasn't using JT9. > > > > The program just closed and I had to reboot the PC to correct it. > > > > This happened the same as it did on earlier rc versions. > > > > Thanks. > > > > 73 Tony, ZL3HAM > > > > > > On 25/10/2022 6:58 am, Dennis W1UE via wsjt-devel wrote: > > Tony > > Were you just using WSJT only, or were you using it with N1MM+ > > > > Any error messages, or did the WSJT entry window just "disappear"? > > > > Dennis W1UE > > > > > > On Mon, Oct 24, 2022 at 1:52 PM Tony ZL3HAM via wsjt-devel > > wrote: > > > > Hi All, > > > > I'm running Ver 2.6.0-rc4 on Windows 11 Pro and the program has > > just > > crashed for the second time and it needed a PC reboot to > > restore. At > > the time I was on 20m FT4 after having a few QSO's and it crashed > > whilst in listening mode. > > > > 73 Tony, ZL3HAM > > > > > > > > ___ > > 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 > > > > > > ___ > > 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] Program crash
Tony Were you just using WSJT only, or were you using it with N1MM+ Any error messages, or did the WSJT entry window just "disappear"? Dennis W1UE On Mon, Oct 24, 2022 at 1:52 PM Tony ZL3HAM via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi All, > > > > I'm running Ver 2.6.0-rc4 on Windows 11 Pro and the program has just > > crashed for the second time and it needed a PC reboot to restore. At > > the time I was on 20m FT4 after having a few QSO's and it crashed > > whilst in listening mode. > > > > 73 Tony, ZL3HAM > > > > ___ > 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] YBDXPI Contest Performance
I started the contest using 2.6.0RC4. I operate with WSJT in conjunction with N1MM+, using the DX Lab Suite Commander to a K30/Mini, through a Remote Rig unit to the remote transmitting site. I used SO1V mode for this contest- no SO2R. The combination worked perfectly for about 6 hours, then the WSJT-X for EW1 just "disappeared" with the TCP error from N1MM+. I opened Task Manager, killed the orphan JT process, and was back on the air- for maybe 15 minutes, when it happened again. This time I Restarted the computer, started up again, and within 30 minutes it happened again. Remembering a conversation i had with Joe K1jt a while ago, I then substituted the 2.5.4 hamlib4.dll for the 2.6.0 dll, restarted the computer, and started operating again. It lasted about 30 minutes, and the same error again. I deleted the orphan JT9 process and started up again. That was the end of the errors- it never happened again for the next 7 hours of operation. In his write-up on 3830, Ty, K3MM, also tried 2.6.0rc4 to start the contest. Within an hour of the start, he had his WSJT-X EW2 window just disappear. Rather than fight it, he went back to 2.5.4 and had no more "disappearances" the rest of the contest (about 27 hours). I typically use 100w or less in contests, but did use 800-1000w for this contest. I saw no difference in "disappearances" between the two power categories. Thanks to all for their work in supporting WSJT-X. Its truly a great program! Dennis w1UE ___ 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 Stopping
GA Joe, and thanks to you and the development team for their efforts. I hope I included all the info that you wanted. WSJT-x doesn't really "crash"- one of the WSJT Entry Windows simply "disappears". No BSOD, No RTE. There is an error message in a little box: "Something unexpected caused WSJT to close the Radio TCP port unexpectedly. Please try restarting WSJT again. If that does not work restart N1MM." I can't tell what was happening just before the failure, as there is no warning there is going to be a failure. WSJT is controllilng two radios through N1MM using the DX Lab Commander process, as detailed in the N1MM setup instructions. I have not found a way to force a failure. I will note, that version 2.5.4 did not have this problem. The EW that closes may be either EW1 or EW2; there is no way of guessing which is going to crash, and no indication that I've noticed to indicate which window is about to crash. If you then restart WSJT, you will get another error box: "Sub-process error. Failed to close orphaned jt9 process." Going into Task Manager and closing that JT9 function does not restore functionality. If I close all the WSJT windows and all the N1MM+ windows, and try to restart N1MM, I get another error message about a port 13064 not being closed. The quickest and most reliable way to get back to making contacts is to restart the computer, restart N1MM, and restart each WSJT window. Yes, there are other reasons for wanting N1MM. I use it to keep track of multipliers- what do I need, and where what I need is operating. I also tie in Telnet with N1MM to keep me up on multipliers and what bands are open and to where. Rate info, transferring score to one of the Online Scoreboards. Since I don't have a big big display for all this, I also network N1MM to display info that won't fit on my regular display. One other thing I noticed after the last crash- I went in to delete the orphaned JT9 process, and found that there were two JT9 processes, one about 20Mb and one about 180Mb. After I restarted the N1MM and the 2 WSJT EWs, I went into the same process and found only 1 JT9 process, about 18-22Mb. I just restarted the computer and reentered everything again, and now I have 2 jT9 processes, one about 20Mb and one about 194Mb. Took another look- now they are both 14.5Mb. Now both are at 180Mb. Don't know if this is apropos at all, just seems odd. Right now, I'm planning to use 2.5.4 for the WWDigi Test. I hate to give away the advantages of using 2.6.0rc3, but I can't handle the interruptions and lost QSOs. Dennis W1UE On Tue, Aug 23, 2022 at 4:35 PM Joe Taylor wrote: > Hi Dennis and Ron, > > Thanks for your reports. This message is off-list, since your needs are > rather specialized -- but I have CC'd other members of our core > development group. > > On 8/23/2022 2:43 PM, Dennis W1UE via wsjt-devel wrote: > > I had high hopes for 2.6.0 rc3. I ran it for 25 hours decode time using > > an SO2R setup. It never stopped working nor crashed.2.6.0 rc1 and rc2- > > the EW just disappeared from the screen and I got an error box related > > to TCP. Since that first stoppage- or crash- I've had 4 more crashes. > > The longest I've operated since then has been about 40 minutes. > > > > So, the bug that is causing the program to suddenly close, has not been > > found. And it was looking so good! > > On 8/23/2022 2:52 PM, Ron WV4P via wsjt-devel wrote: > > Same here, running N1MM with 2 instances it keeps crashing and locking > > everything down when it does. It took a long time for the first > > occurrence but now its lucky to stay up 30 min. > > ... > > > I'll be single op. > > If anyone makes it work with the Max Distance feature they will have a > distinct advantage. Sadly it's back to 2.54 for me, I could not make it > work reliably. I'll run it again this evening to try and get some screen > shots and data that might help the Smart people, before I swap back to the > stable version. > > Good luck, Dennis ! You rocked the last one. > > We'll be happy to help you guys to isolate the problem you're having, > apparently with communication between WSJT-X and N1MM+, but I must > caution you that it may take some time. Moreover, in the immediate > future my time is largely committed to a paper on the EME Echo mode > features in WSJT-X 2.6.0. > > None of our program versions 2.6.0-rc1, -rc2, or -rc3 have intentional > changes to the way communications take place with an external program > such as N1MM+. At present I don't know the details of what happens when > you say it (I suppose you mean WSJT-X) crashes. Any error message? > What was happening just before the failure? Is WSJT-X doing any rig > control? Can you stress-test the situation in a way that reliably > forces a
Re: [wsjt-devel] WSJT-x Stopping
Ron I thought I was the only one crazy enough to do this! I also ran 2 instances with N1MM+. I had high hopes of using it in WWDigi, but I don't think its ready yet. You doing a Multi-op or SO2R? I'm SO2R LP. Dennis W1UE On Tue, Aug 23, 2022 at 2:58 PM Ron WV4P via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Same here, running N1MM with 2 instances it keeps crashing and locking > everything down when it does. It took a long time for the first occurrence > but now its lucky to stay up 30 min. > > Ron, WV4P > > On Tue, Aug 23, 2022, 1:48 PM Dennis W1UE via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > >> I had high hopes for 2.6.0 rc3. I ran it for 25 hours decode time using >> an SO2R setup. It never stopped working nor crashed.2.6.0 rc1 and rc2- the >> EW just disappeared from the screen and I got an error box related to TCP. >> Since that first stoppage- or crash- I've had 4 more crashes. The longest >> I've operated since then has been about 40 minutes. >> >> So, the bug that is causing the program to suddenly close, has not been >> found. And it was looking so good! >> >> Dennis W1UE >> >> ___ >> 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
[wsjt-devel] WSJT-x Stopping
I had high hopes for 2.6.0 rc3. I ran it for 25 hours decode time using an SO2R setup. It never stopped working nor crashed.2.6.0 rc1 and rc2- the EW just disappeared from the screen and I got an error box related to TCP. Since that first stoppage- or crash- I've had 4 more crashes. The longest I've operated since then has been about 40 minutes. So, the bug that is causing the program to suddenly close, has not been found. And it was looking so good! Dennis W1UE ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Release Candidate WSJT-X 2.6.0-rc3
Installed RC3 on Win10 and Win11 computers. No issues with either install. Set up and operated So2R using Win10. Been operating now for 2 1/2 hours- have not had a crash! Have utilized the Active Stations Window, and kept CQ:Max Dist the entire time on both EWs. No issues with any part of the program so far. So far, great! Dennis W1UE On Mon, Aug 22, 2022 at 12:20 PM Joe Taylor via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Dear WSJT-X Users, > > We are pleased to announce that Release Candidate WSJT-X 2.6.0-rc3 is > ready for download by beta testers. A list of its essential changes from > previous releases can be found in the Release Notes: > https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt > > Links for downloading WSJT-X 2.6.0-rc3 can be found on the WSJT-X Home > Page, https://physics.princeton.edu/pulsar/k1jt/wsjtx.html > Scroll down to find "Candidate release: WSJT-X 2.6.0-rc3". > > We hope you will enjoy using this beta release of WSJT-X 2.6.0. As a > beta tester you should report on your experiences with its new features, > successful and otherwise, on one of the relevant WSJT forums. Bugs > should be reported by following instructions found here in the User Guide: > > > https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.6.0-rc3.html#_bug_reports > > WSJT-X and MAP65 are licensed under the terms of Version 3 of the GNU > General Public License (GPLv3). Development of this software is a > cooperative project to which many amateur radio operators have > contributed. If you use our code, please have the courtesy to let us > know about it. If you find bugs or make improvements to the code, > please report them to us in a timely fashion. Additional licensing > details can be found here: > https://physics.princeton.edu//pulsar/k1jt/devel.html > > 73 from the WSJT Core Development Team > Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Chet, KG4IYS; Uwe, DG2YCB; > Brian, N9ADG; and John, G4KLA > > > ___ > 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] Two small Issues
Marty #1 was fixed in tx 2.6.2. The blue color was not random- either the OK button or the cancel button had the blue outline. The one that had the outline was the one that was “clicked” when you last clicked a button. So, if u used the ENTER key to clear the window you either logged or didn’t log the QSO, depending on where the blue outline was. If you never used the ENTER key to log a contact, you wouldn’t have noticed it. If you have deep decode enabled, depending on the power of ur computer, it may take several seconds before u see the last decodes. This sounds like what ur seeing. Dennis W1UE On Thu, Aug 4, 2022 at 13:53 Marty Wayne via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi, > > I seem to have two small issues. > > 1. Every once in a while when the logging window opens, the “OK” button > shows up grayed out but still enters the QSO into the log. At other times, > it shows up as blue and also logs the contact. This seems rather random. > > 2. During a contact or while calling CQ, I get no responses. When I > click Halt TX or un-click the Enable TX button, I get a response from some > station. This happens more frequently than purely random but not > frequently to be a hard issue. > > I’ve been using WSJTx since 2018 and as I recall, these have been there. > > Any thoughts? > > 73, > > Marty, W6NEV > _ . . . . _ _ _ . . . . _ . . . . . _ > mcway...@comcast.net > 408-234-8023 > > > > ___ > 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] V. 2.6 Error and Crash
Mike Green found the same as you. If I just deleted the JT9 process, it still didn’t work with N1MM. I have to restart the computer to again operate. UE On Wed, Jul 27, 2022 at 21:54 mpcorey--- via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Thanks Dennis, it sounds very similar to what I’m experiencing. Just this > evening, while calling CQ on 40, it has crashed three times. Each time I > open task manager and find the JT9 process, end it, and it will restart. > Although in once instance it crashed again within seconds of restarting. > I’m not getting the error messages though, like I did with 2.6rc1, unless I > try and restart the program without first ending the jt9 process. > > > > > > > > *From:* Dennis W1UE via wsjt-devel > *Sent:* Wednesday, July 27, 2022 8:40 PM > *To:* WSJT software development > *Cc:* Dennis W1UE > *Subject:* Re: [wsjt-devel] V. 2.6 Error and Crash > > > > Mike > > I wrote this up and submitted it a week ago. I could not find any > sequence of events to cause the WSJT window to suddenly close. I found it > took anywhere from 15min to 3 hrs between crashes. I also get a TCP error > when it closes, as I have wsjt mated to N1mm+ for logging. > > > > Dennis W1UE > > > > On Wed, Jul 27, 2022 at 20:26 mpcorey--- via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > So I posted to this list a few weeks ago about the problem with 2.6rc1 > suddenly crashing, and to restart ending a JT9 process through task > manager. Last week, prior to the release of rc2, this problem was occurring > about 2 times per day while I was on an Iota activation. So, when I > returned home, I downloaded rc2 to the main station computer. The problem > is still occurring, just had a crash and “end JT9 process” fix to restart > it. I recall others mentioning they experienced this, has anyone else had > it happen with rc2? Is this a software bug? Or something to fix on the > operator end? > > > > Thanks, > > Mike, KI1U > > > > ___ > 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] V. 2.6 Error and Crash
Mike I wrote this up and submitted it a week ago. I could not find any sequence of events to cause the WSJT window to suddenly close. I found it took anywhere from 15min to 3 hrs between crashes. I also get a TCP error when it closes, as I have wsjt mated to N1mm+ for logging. Dennis W1UE On Wed, Jul 27, 2022 at 20:26 mpcorey--- via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > So I posted to this list a few weeks ago about the problem with 2.6rc1 > suddenly crashing, and to restart ending a JT9 process through task > manager. Last week, prior to the release of rc2, this problem was occurring > about 2 times per day while I was on an Iota activation. So, when I > returned home, I downloaded rc2 to the main station computer. The problem > is still occurring, just had a crash and “end JT9 process” fix to restart > it. I recall others mentioning they experienced this, has anyone else had > it happen with rc2? Is this a software bug? Or something to fix on the > operator end? > > > > Thanks, > > Mike, KI1U > > > ___ > 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] WSJT-X-For EWx Crashing- TCP Error
I really appreciate the hours and effort that have gone into the creation of WSJT. The enhancements in 2.6 are all great, except for the one that seems to have created a problem for me. I'll describe my setup and then the problem. Computer #1- I7 11th gen, 16Gb RAM, Win 11 Pro Computer #2- I5 4th gen, 8Gb RAM, Win10 Pro- new (to me) computer, very little on it WSJT 2.5.4 works flawlessly in my setup. Setup: WSJT configured to work with N1MM+ Logger thru DX Lab Commander. Local rigs are K3 radios, connected to Remote Rig (RR) boxes that stream the audio to a radio site 70 miles away. The computer and K3s talk at 38400. My normal operation is So2R, although at times I may operate with only one For EW. I use separate sound cards to decode each radio, and a third soundcard that generates the transmit tones. All the signal processing (WSJT, N1MM+, sound cards) is done at the Control site. Problem: With no warning and no provocation, one of the WSJT-X-FOR EW will suddenly close and I'll ge this error message: "Something caused WSJT to close the Radio TCP Port unexpectedly. Please try starting WSJT again. If that doesn't restore operation, restart N1MM+." Restarting WSJT doesn't work, and restarting N1MM+ doesn't work. The only way to restore operation at this point is to restart the computer. 1. The time between crashes is 15 min to 3 hrs. 2. Either WSJT-X ForEW1 or EW2 can crash. 3. THe problem occurs on both of the above computers. 4. The problem occurs when local communications are at 38400 or 9600. 5. I have not found a way to generate the problem, it just happens. 6. The crash can occur when I'm not touching the keyboard or mouse. 7. The crash occurs when using either the 32 or 64 bit program 8. On Mike W9MDB's suggestion, I reconfigured WSJT and N1MM so that WSJT controlled the radios directly; the crash still occurs. Since I haven't heard many complaining about this, I'm thinking there aren't many ops trying to operate SO2R through a remote station, and the remote station has something to do with it (something timing out, momentary interruption of data or audio streams) I"ve also considered that maybe that error message is something of a catchall, and the problem doesn't have a specific error message. Since this problem didn't occur with 2.5.4, and does with 2.6.0, something changed between the two to create this problem. In any case, thanks for anything that can be done to correct this. If I can assist with any fixes on this or other items please feel free to call on me. Dennis W1UE ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
