[wsjt-devel] FT4 and Hold TX
Possible bug in 2.6.1 (MacOS) Regardless of the status of the “Hold TX” checkbox, transmit frequency stays locked. This can lead to calling your next contact of the previous one’s frequency. George J Molnar College Park, Maryland KF2TFM19ma ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Hashed callsign collisions?
I had the same thing happen - as if the hash is the same for both /0 and /7, so they both respond. George J Molnar, KF2T FM19ma - Maryland, USA > On Jan 20, 2023, at 3:56 PM, Jon Anhold via wsjt-devel > wrote: > > I was just on 20m trying to work W1AW/7, and W1AW/0 answered me, twice - is > this a known issue with longer/hashed callsigns? > > > > 73 de KM8V Jon > ___ > 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 find how to reset Q65A default Tx duration (defaults to 30 sec and my operating requires 60 seconds)
If your need is immediate, I would recommend downloading rc5, which is still available at Sourceforge. That should keep you going until 2.6.1 is out. As a Mac user, download the dmg-suffixed file. https://sourceforge.net/projects/wsjt/files/wsjtx-2.6.0-rc5/ George J Molnar, KF2T (202) 288-8000 FM19ma - Maryland, USA > On Jan 8, 2023, at 3:45 PM, David Schmocker via wsjt-devel > wrote: > > Everyone > My apologies for dual emails on this single problem. But to clearly > communicate the need, I am currently needing to know (essential requirement) > how to change the Q65 primary/current operating duration (defaults 30 sec); > how do I then change it to 60 sec so I can operate? > > Then part 2 (nice to have) is how does one change the default (where is the > Mac equivalent of Windows WSJTX.ini file)? Thank you > > Very 73, > Dave ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Unable to find an App at the Apple App web site
Not entirely sure of your issue, but I am presuming you were able to download the distribution file from the WSJT Home Page (princeton.edu) and opened it. Were you able to drag the WSJT-X icon to the Applications folder (a shortcut is provided), AND then follow the Readme instructions explicitly, especially as they concern entering data using the "Terminal" app, which is included in every MacOS.Finally, you will need to go to the Applications folder, right click on WSJT-X and "Open" it. A security dialog will pop up asking if you really want to do this. Yes, you do. If you've followed these steps, you should be good to go. Proceed with entering your call, grid, and radio/audio setups, per the manual.Good luck & enjoy!George J Molnar, KF2TOn Feb 14, 2022, at 2:14 PM, Michael Mertes via wsjt-devel wrote:Hi I was able to download the program and initiate the first few steps. The next step is to open the WSJT-X App, I was unable to find an App at the Apple App Store or through link available when the program is double clicked in the Applications section of my Mac mini. Can you help?StartMail makes private and encrypted email easy. Try it here for free!Receive a 50% discount on a new subscription through the referral program.Content-Type: text/plain; charset="us-ascii"MIME-Version: 1.0Content-Transfer-Encoding: 7bitContent-Disposition: inline___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] WSJT-X 2.5.3 GA Release for macOS
Working without incident on my M1 Mac mini under Monterey 12.0.1. George J Molnar College Park, Maryland KF2T | FM19ma > On Dec 13, 2021, at 1:31 PM, Joe Taylor via wsjt-devel > wrote: > > Hi John, > >> On 12/13/2021 1:17 PM, John Stengrevics WA1EAZ via wsjt-devel wrote: >> >> My thanks to John Nelson for this. However, does this Mac installation >> package work with macOS Monterey 12.0.1 running on a M1X chip? > > You just reminded me why I should not have changed "for macOS 10.13 through > 11" to "for macOS 10.13 and later" on the web page. > > I have now changed it back. For more details (and possibly a prognosis > concerning support for macOS 12.0.1) we will need input from a knowledgeable > mac user, perhaps G4KLA, K9AN, or another volunteer? > >-- Joe, K1JT >> 73, >> John >> WA1EAZ On Dec 13, 2021, at 9:37 AM, Joe Taylor via wsjt-devel wrote: >>> >>> John Nelson, G4KLA, has kindly prepared a macOS installation package for >>> WSJT-X 2.5.3. A download link has been posted on the WSJT-X web page: >>> https://physics.princeton.edu//pulsar/k1jt/wsjtx.html >>> >>> We hope that installation packages for other OS varieties and the >>> source-code tarball can be made available in the near future. >>> >>> -- 73 from Joe, K1JT; Steve, K9AN; and Nico, IV3NWV >>> >>> >>> ___ >>> 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] Good old-fashioned Grids-Only mode
My suggestion is not to banish reports. The software can (and should) determine SNR, display it and report it up the spotter path. No harm at all. The valuable data on PSKReporter, HamSpots, etc., would remain intact. The SNR would just not be part of the default over-the-air VHF+ exchange. The suggestion is to enable “grids only” QSOs at VHF and above, with the focus on helping rovers, capitalizing on short openings, and meteor scatter. On 2m in North America, at least, CM is the de facto standard for 2m and above ms already. Having the software support it as default without a Cabrillo log and “CQ TEST” would help. The latter especially if directed CQs or QSX modes (e.g. CQ 160) are desired. By streamlining the default VHF+ contact sequence, we would also gain improved compatibility between contest mode users and those not using CM (either by setting or different software). Sequence confusion should be kept to a minimum. George J Molnar College Park, Maryland KF2T | FM19ma ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Good old-fashioned Grids-Only mode
Going back to my original suggestion - I do not seek to banish signal reports for those that want them, certainly. Only set the -default- VHF condition to grids-only QSOs. This would have the immediate advantage of substantially untying the mess that crops up too often between users in CM working those not in CM, or with different software. In the case of R1 QSO practice, without judging the merits of the R1 Handbook, it would seem that in this case, the non-default condition could be set to reports, just as all special operating conditions contacts are treated as exceptions to the default. European ops - I am very curious about the real world use here. If I work you on 6m Es during the CQ Worldwide Contest, which requires just a grid, is our contact valid? The rules state “Signal reports are not required and should not be included in the log entry.” Do any of your contests contacts count? I’m confused and would like to understand better. Very 73, George J Molnar College Park, Maryland KF2T | FM19ma___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Good old-fashioned Grids-Only mode
Thanks for that info, Bill. So, if I work a R1 station in CM, the contact is not valid for him? That’s very unfortunate. Still, could the option be applied for R2 and R3? Seems like we could build it into a configuration somehow? George J Molnar College Park, Maryland KF2T | FM19ma > On Aug 1, 2021, at 12:59 PM, Bill Somerville via wsjt-devel > wrote: > > > On 01/08/2021 16:44, George J Molnar via wsjt-devel wrote: >> Submitted for discussion… >> >> Would it make sense to make the default sequence for VHF+ operation the >> “Contest Mode” style with no signal reports, no “CQ TEST” and no contest log >> being generated? Good old-fashioned Grids-Only mode. We don’t need signal >> reports on weak signal or Es VHF work, where the intent is to have a valid >> contact in minimum time. >> >> We can probably eliminate the “VHF and above” features checkbox, too. There >> does seem to be confusion around it, sometimes. Just have the application >> default to VHF settings, grids only, above 29.700 MHz. If “Special >> Activity” is selected, then the appropriate TEST message can be generated >> along with opening a Cabrillo log. >> >> I’m not advocating changing the below-50 MHz setting, since I think the >> howls would be large and sustained. >> >> Thoughts? >> >> >> George J Molnar, KF2T >> College Park, Maryland, USA > George, > > that is a non-starter in Region 1 at least since the Region 1 VHF handbook > defines a QSO to include a piece of QSO specific information being exchanged > and confirmed. A grid square does not meet that criteria. OTOH the grid > square is not required by that definition of a QSO. > > 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
[wsjt-devel] Good old-fashioned Grids-Only mode
Submitted for discussion… Would it make sense to make the default sequence for VHF+ operation the “Contest Mode” style with no signal reports, no “CQ TEST” and no contest log being generated? Good old-fashioned Grids-Only mode. We don’t need signal reports on weak signal or Es VHF work, where the intent is to have a valid contact in minimum time. We can probably eliminate the “VHF and above” features checkbox, too. There does seem to be confusion around it, sometimes. Just have the application default to VHF settings, grids only, above 29.700 MHz. If “Special Activity” is selected, then the appropriate TEST message can be generated along with opening a Cabrillo log. I’m not advocating changing the below-50 MHz setting, since I think the howls would be large and sustained. Thoughts? George J Molnar, KF2T College Park, Maryland, USA ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Possible feature request, time skew notification?
Wouldn’t a simple glance at the Wide Graph provide clear evidence of timing errors? Even without WWV, GPS, or software changes, it seems trivial to identify the error and walk in a correction. George J Molnar College Park, Maryland KF2T | FM19ma ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
