Re: [wsjt-devel] Message Bit to Request Other Station to QSY to your Frequency
Joe, Do actually want people to turn the dial? How arcane is that? Jim KC7QY On Friday, July 9, 2021, 12:02:36 PM MDT, Joe Taylor wrote: Hi Al, As Bill has explained, the WSJT-X Rx bandwidth is currently limited to 5000 Hz. But I agree that larger FT8 sub-bands (or multiple sub-bands on a given HF band) are really what is required to relieve congestion. -- 73, Joe, K1JT On 7/9/2021 11:54 AM, Al Pawlowski wrote: > Given FT8’s growth, a built-in way to ask for a jump to an clear frequency, > or channel, certainly seems like a good idea. However, a larger channel is > what really seems to be needed. This could be accomplished (other mode user > squawks not considered) by just setting the WSJTx, and radio, rx bandwidths > higher. With my setup, I can work up to a 4500Hz FT8 channel. If more users > were to use larger BW, it might be a significant congestion relief. > > Though my rig can go to Hz rx BW and WSJTx v2.4.0 set to 6000Hz, 4500kHz > is all I can get - above that, decodes stop and the waterfall fills with > noise. I wonder if the limit is due to my CPU speed (usage increases with BW > and channel activity) or a WSJTx thing. Reports from others doing larger BW > would be interesting. > > > Al Pawlowski, K6AVP > Los Osos, CA USA > > > > ___ > 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] 2021 Field Day Logging Issues
Bill, Texas has three ARRL sections so you would have had to enter NTX, STX or WTX depending which section you were operating from. Jim KC7QY On Sunday, June 27, 2021, 02:58:21 PM MDT, Yahoo Group wrote: I also like WSJT-X Digital software. I never have had any problems with the program or any updates.However, During FD I went to the Advance tab, checked the Special operating activity box, and checked the ARRL Field Day box.I was unable to make any kind of an entry in the FD Exch box other than 1D T. I am in Texas. I always got the "Invalid Contest Exchange" message.Couldn't work any FT-8 on Field day.Bill hoffmanw5wjhw5...@sbcglobal.net On Sunday, June 27, 2021, 2:55:06 PM CDT, Marty wrote: First, I really like the WSJT Digital Software. I’ve been using it for about 4+ years. Thanks to the teams great effort making a user friendly software. I noticed an issue during Field Day and wonder if it could be looked into. If the station I was working had a location error code such as “a1” or “a3”, when trying to log the contact the program would show an “Invalid Qso Data” error message and the QSO could not be logged. I also noticed in the Band Activity window, this location error was displayed before the country. In non-FD use, this error is displayed after the country. In the RX Frequency window, the error appeared after the FD exchange. Marty Wayne, W6NEV408-234-8023mcwayne2@comcast.net___ 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] Call for information about PC systems being used for WSJT-X
Bill, I''m still on a Pentium. I'm in the process of changing to a much new machine (i7) but if you had asked a month ago I'd still be mired in a Pentium. Jim KC7QY On Tuesday, June 8, 2021, 05:40:53 PM MDT, Bill Somerville wrote: Hi all WSJT-X users, we are looking into some performance enhancements that will take advantage of some parallel processing features of modern CPU architectures. In order to gauge how much backwards compatibility for older CPUs we will have to implement it would help to know who is using such older processors. Please don't turn this thread in to a mine is better than yours conversation, all I need to know is who or how many of you are using the older CPU architectures. Note that this applies to MS Windows, Intel Linux, and Intel macOS users, it is about CPUs not operating systems. The technology we will use is called AVX and that is present on all Intel CPUs branded Core i3/i5/i7/i9 (circa 2010 to present), it is also present on AMD CPUs since the Jaguar or Puma based CPU models (some late Athlon-II CPUs, all Zen based CPUs, including Ryzen) circa 2013 to present. Notably Intel CPUs branded Celeron, Pentium, or Atom do not support the AVX technology. 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. 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] FT4 logging prompt
Russ, Glad you chimed in. I was thinking the same thing. Contest rules almost always require a complete exchange during your QSO (I say almost only because there may be some contests that have exceptions). NIL penalties for Digi modes has been quite high compared to phone or CW. Choose your poison, shorten the QSO and experience more NIL penalties or get the 73 confirmation with fewer penalties and better QSL confirmations after the test. Jim KC7QY On Monday, May 10, 2021, 08:39:30 AM MDT, Russ wrote: Paul Kube wrote: - Answering a CQ: CQ WW W0YK DM97 Tx6 W0YK K6PO R DM12 Tx3 K6PO W0YK RR73 Tx4 - Tailending a QSO. K6PO has already copied W0YK’s grid. Then: W1AW W0YK RR73 Tx4 W0YK K6PO R DM12 Tx3 K6PO W0YK RR73 Tx4 - Tailending a QSO. K6PO has not yet copied W0YK’s grid. Then: W1AW W0YK RR73 Tx4 W0YK K6PO DM12 Tx2 K6PO W0YK R DM97 Tx3 W0YK K6PO RR73 These are NOT contacts! Contact rules specifically state that you must copy your call sign from your QSO partner before sending a report. Regardless of the fact that some misguided contest rules may allow ‘contacts’ in that form, those contacts would not be good for other awards (DXCC, VUCC, etc). Eliminating 73 – a bad idea. If I send 73 and the other guy receives it, then he knows it was a good contact. If I continue to send my report then he should know to continue sending RRR. Otherwise he may log a contact that was incomplete. 73, Russ K2TXB ___ 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.4.0 RC2
Hi I downloaded rc-2 last week shortly after it became available. I've managed a Q65 QSO over the weekend with a rover. I noticed that when I went to TX there seemed to be a delay between the clock rolling over and when I heard audio from the rig. On MSK144 and Q65 this didn't present too much of a problem but when I went to FT8 this morning I couldn't get any replies, even from strong stations. The delay was in the 2 -3 second range. I reverted to 2.3.0 and the delay has gone away. Admittedly my shack computer is old and slow but I don't see the delay in 2.3.0 that I did with rc-2. Computer is dual core Pentium running under Win 10 Home. I'm excited about the possibilities of Q65 but can't live with the delay on FT8. Jim KC7QY ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
