[wsjt-devel] FT4 and Hold TX

2023-01-20 Thread George J Molnar via wsjt-devel
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 ___

Re: [wsjt-devel] Hashed callsign collisions?

2023-01-20 Thread George J Molnar via wsjt-devel
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

Re: [wsjt-devel] Unable to find how to reset Q65A default Tx duration (defaults to 30 sec and my operating requires 60 seconds)

2023-01-08 Thread George J Molnar via wsjt-devel
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)

Re: [wsjt-devel] Unable to find an App at the Apple App web site

2022-02-14 Thread George J Molnar via wsjt-devel
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

Re: [wsjt-devel] WSJT-X 2.5.3 GA Release for macOS

2021-12-13 Thread George J Molnar via wsjt-devel
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

Re: [wsjt-devel] Good old-fashioned Grids-Only mode

2021-08-02 Thread George J Molnar via wsjt-devel
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.

Re: [wsjt-devel] Good old-fashioned Grids-Only mode

2021-08-01 Thread George J Molnar via wsjt-devel
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

Re: [wsjt-devel] Good old-fashioned Grids-Only mode

2021-08-01 Thread George J Molnar via wsjt-devel
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” st

[wsjt-devel] Good old-fashioned Grids-Only mode

2021-08-01 Thread George J Molnar via wsjt-devel
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

Re: [wsjt-devel] Possible feature request, time skew notification?

2021-07-18 Thread George J Molnar via wsjt-devel
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