Re: [wsjt-devel] Message Bit to Request Other Station to QSY to your Frequency
Yeah, that would be a really useful addition if it's in fact feasible. I have a "QRM UR FREQ" free-form message that I use in these situations. Sometimes people get it, sometimes not. -- Ray WQ5L On Thu, Jul 8, 2021 at 2:24 AM Saku wrote: > > Yes! > > I have suggested this kind of solution years ago. > Now I have tried free message "QSY MY QRG" but it spends more periods and > seldom results to anything. > > Easier solution for us, the users, would be to spread 2kHz up or down with > vfo dial. That way a part of "official" dial traffic can still be seen.But > also this seems to be too difficult in practice. > > Good "bad" example is 6m. All stations use 50.313 and just few are brave > enough to call CQ with 50.323 dial. > > One good thing also to mention from 6m: It seems that with EU-AS qsos most of > the EU stations use 1st/even period for calling and AS stations use 2nd/odd > period. It makes working a little bit easier than in HF bands. > > -- > Saku > OH1KH > > Tim Goeppinger via wsjt-devel kirjoitti 8.7.2021 klo 6.07: > > There are so many times on FT8 or FT4 that the station you are in QSO with is > buried in QRM by a signal they probably don't even know is on their audio > frequency. > > On future releases of FT4 or FT8, if there is ever a spare bit in the message > formats, I propose adding a "please QSY to my tx audio frequency" bit. > There would be a "Pse QSY: button on the user interface that would be off by > default. > There would be an indicator to the other op that a QSY is requested, and it > is up to them whether or not to hit the up arrow button to sync TX > frequencies. > > There have been several times on 6 meters recently where this could have been > helpful, and would have cut down on all of the repeats back and forth. > > Thanks for your consideration & 73, > > Tim N6GP ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Call for information about PC systems being used for WSJT-X
Bill, I use this oldie w/o AVX for everyday WSJT-X. I do use a newer PC for contests though. processor : 0 vendor_id : AuthenticAMD cpu family : 16 model: 4 model name : AMD Phenom(tm) II X2 550 Processor stepping: 2 cpu MHz : 800.000 cache size : 512 KB -- Ray WQ5L On Tue, Jun 8, 2021 at 6:44 PM Bill Somerville wrote: > > Hi all WSJT-X users, ... > So in summary, look up your CPU and if it **does not support AVX** > (https://en.wikipedia.org/wiki/Advanced_Vector_Extensions) then let me > know. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.2.0-rc1
Bill, Some early observations of 2.2.0-rc1 decoding: I parsed through my ALL.TXT (375+ MB) counting number of decodes per cycle. Prior to yesterday, my highest number of unique FT8 decodes in one cycle was 63. After installing 2.2.0-rc1, I monitored 14.074 for a couple of hours yesterday afternoon. During that time I logged 10 cycles with >63 unique decodes, the highest being 72. So, it's definitely working well for me. I also monitored 30 meter WSPR for a little while and was regularly getting 10-15 decodes per cycle. Anecdotally that feels like a big improvement but I don't monitor WSPR enough to have a meaningful baseline. I noticed that the final WSPR decode pass extended well into the next cycle, 10 seconds or more, when the window was busy. Granted, this is with a 10+ year old AMD CPU... 73 -- Ray WQ5L On Tue, May 12, 2020 at 3:30 PM Bill Somerville wrote: > > On 12/05/2020 20:45, j...@comcast.net wrote: > > >one feature of the latest decoder is there to yield decodes before all > >transmissions are completed. > > > > Bill, > > > > Was this a user request, or just a result of the new decoding algorithm? > (My curiosity has been piqued.) > > > > Ed N4II. > > Hi Ed, > > because the FT8 protocol includes Forward Error Correction (FEC) information > it is possible to successfully decode a signal before the complete block of > data has been received, this is an opportunity to pick the "low hanging > fruit" as early as is practical, leaving more elapsed time to work on the > remaining signals. The intent is both to deliver some decodes earlier and to > utilize more CPU resource to yield more decodes in a reasonable time frame. > Most users, probably all, on a busy band will see some decodes earlier in the > receive period and also more decodes overall with the last few maybe only > printing some time into the following period. We have not put a number to the > extra decode yield but we have certainly see up to one third more when > processing saved .WAV files from congested bands compared to the v2.1.2 FT8 > decoder. Steve K9AN has a "golden" test FT8 .WAV file that he uses to verify > decoder yield and I believe the current result from that file is 67 unique > valid decodes. > > 73 > Bill > G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] 2.1.0-rc6 and Fedora 29?
Bill, Chopping out the cty.dat allows rc6 to work without mucking with the ADIF file. My original ADIF file is still in place, I can start and restart the program, my QSOs are logged to it, no problem. -- Ray WQ5L p.s. just got an FT4 decode at -19, nice On Mon, Jun 3, 2019 at 12:07 AM Bill Somerville wrote: > > On 03/06/2019 00:54, Ray Rocker wrote: > > Bill, > > > > Taking some clues from the other threads -- I'm able to make QSOs > > using 2.1.0-rc6 by replacing ~/.local/share/WSJT-X/cty.dat by a zero > > length file. > > > > I tried a newer cty.dat from countryfiles.com just for grins, no joy. > > > > -- Ray WQ5L > > Hi Ray, > > that may avoid the issue but the real problem is in the code that reads > in the WSJT-X ADIF log file. You can work around it but is is messy. You > must move aside the ADIF log file (wsjtx_log.adi) then start WSJT-X, > then move the ADIF log file back, then finally go to "Settings->Colors" > and push the "Rescan ADIF log" button. You would have to do that every > time you start WSJT-X or when switching configurations. A fix is on the > way in a day or so. > > 73 > Bill > G4WJS. > > > > ___ > 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] 2.1.0-rc6 and Fedora 29?
Bill, Taking some clues from the other threads -- I'm able to make QSOs using 2.1.0-rc6 by replacing ~/.local/share/WSJT-X/cty.dat by a zero length file. I tried a newer cty.dat from countryfiles.com just for grins, no joy. -- Ray WQ5L On Sun, Jun 2, 2019 at 10:36 PM Ray Rocker wrote: > > Bill, > > Yes, 2.1.0-rc6 does start up OK when I run it with --rig-name=test. > > -- Ray WQ5L > > > On Sun, Jun 2, 2019 at 9:21 PM Bill Somerville wrote: > > > > On 02/06/2019 22:06, Ray Rocker wrote: > > > Bill, > > > > > > Thanks for confirming. I did the upgrade to Fedora 30; RPM installs > > > fine but I'm getting segfaults: > > > > > > $ wsjtx > > > Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use > > > QT_QPA_PLATFORM=wayland to run on Wayland anyway. > > > Segmentation fault (core dumped) > > > > > > $ QT_QPA_PLATFORM=wayland wsjtx > > > Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use > > > QT_QPA_PLATFORM=wayland to run on Wayland anyway. > > > QSocketNotifier: Can only be used with threads started with QThread > > > Segmentation fault (core dumped) > > > > > > Could be something in my environment. I'll poke at it some more later. > > > > > > -- Ray WQ5L > > > > Hi Ray, > > > > upgrading to FC30 was of course the other option, hi hi. > > > > On the segfault, can you try starting wsjtx with a command line option > > '--rig-name=test'. That will set up a whole new configuration and user > > files directory (~/.config/WSJT-X\ -\ test.ini and > > ~/.local/share/WSJT-X\ -\ test/') which can be deleted after the test > > run if you wish. Let me know if that allows WSJT-X to start up? > > > > 73 > > Bill > > G4WJS. > > > > > > > > ___ > > 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] 2.1.0-rc6 and Fedora 29?
Bill, Yes, 2.1.0-rc6 does start up OK when I run it with --rig-name=test. -- Ray WQ5L On Sun, Jun 2, 2019 at 9:21 PM Bill Somerville wrote: > > On 02/06/2019 22:06, Ray Rocker wrote: > > Bill, > > > > Thanks for confirming. I did the upgrade to Fedora 30; RPM installs > > fine but I'm getting segfaults: > > > > $ wsjtx > > Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use > > QT_QPA_PLATFORM=wayland to run on Wayland anyway. > > Segmentation fault (core dumped) > > > > $ QT_QPA_PLATFORM=wayland wsjtx > > Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use > > QT_QPA_PLATFORM=wayland to run on Wayland anyway. > > QSocketNotifier: Can only be used with threads started with QThread > > Segmentation fault (core dumped) > > > > Could be something in my environment. I'll poke at it some more later. > > > > -- Ray WQ5L > > Hi Ray, > > upgrading to FC30 was of course the other option, hi hi. > > On the segfault, can you try starting wsjtx with a command line option > '--rig-name=test'. That will set up a whole new configuration and user > files directory (~/.config/WSJT-X\ -\ test.ini and > ~/.local/share/WSJT-X\ -\ test/') which can be deleted after the test > run if you wish. Let me know if that allows WSJT-X to start up? > > 73 > Bill > G4WJS. > > > > ___ > 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] 2.1.0-rc6 and Fedora 29?
Bill, Thanks for confirming. I did the upgrade to Fedora 30; RPM installs fine but I'm getting segfaults: $ wsjtx Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. Segmentation fault (core dumped) $ QT_QPA_PLATFORM=wayland wsjtx Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. QSocketNotifier: Can only be used with threads started with QThread Segmentation fault (core dumped) Could be something in my environment. I'll poke at it some more later. -- Ray WQ5L On Sun, Jun 2, 2019 at 8:40 PM Bill Somerville wrote: > > On 02/06/2019 20:15, Ray Rocker wrote: > > WSJT-X Home Page still says Fedora 29, but I'm guessing the RPMs were > > built for fc30? > > > > # dnf update ./wsjtx-2.1.0-rc6.x86_64.rpm > > Last metadata expiration check: 0:16:09 ago on Sun 02 Jun 2019 06:48:38 PM > > GMT. > > Dependencies resolved. > > > > Problem: cannot install the best update candidate for package > > wsjtx-2.1.0_rc5-1.x86_64 > >- nothing provides libm.so.6(GLIBC_2.29)(64bit) needed by > > wsjtx-2.1.0_rc6-1.x86_64 > >- nothing provides libreadline.so.8()(64bit) needed by > > wsjtx-2.1.0_rc6-1.x86_64 > > > > # cat /etc/fedora-release > > Fedora release 29 (Twenty Nine) > > > > 73 -- Ray WQ5L > > Hi Ray, > > you are correct, the RPM released by the WSJT-X team is indeed > targetting Fedora Core 30, sorry for the misleading information, we > track new versions of the Linux distros we make packages for pretty > closely. You can either build from the source tarball or wait a few days > when Richard, KF5OIM, may well update the Fedora repos with WSJT-X > v2.1.0 RC6. > > 73 > Bill > G4WJS. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] FT4 mock contest
On Wed, May 8, 2019 at 10:21 PM Gary - K7EK via wsjt-devel wrote: > On multiple occasions the other station failed to receive my RR73 and kept > sending his exchange over and over. Unfortunately there was no timely method > to requeue an exchange with RR73. This lost more contacts and appeared to > confuse the autosequencer. I am very sure that I had set things up precisely > as stated in the various emails. That was my biggest source of consternation in the mock contest. The scenario: I'm doing S I see... <-- CQ RU W1ABC FN00 Ok I'll answer... --> W1ABC WQ5L 559 MS <-- WQ5L W1ABC R 559 PA --> W1ABC WQ5L RR73 At this point the QSO is logged and Enable TX turns off. --> WQ5L W1ABC R 559 PA Oh, he didn't get my RR73, let's double click him to keep going... --> W1ABC WQ5L 559 MS Argh! Double-click restarts the QSO and I wind up logging it again, if he plays along. What I want is to just re-send the RR73 when I double-click on a message to me containing " R ". Also: the Best S at least once chose a normal (not in the contest) CQ. Should it only select CQs containing the contest indicator? I made 31 Qs in the mock contest hour. 14 of them were in the first 15 minutes. The rate nosedived, I suspect, due to QRM inside my skip zone that I could not see in the waterfall. Moving around more probably would have helped. 73 -- Ray WQ5L ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
