Menu
▾
▴
wsjt-devel
|
From: R E. <rae...@gm...> - 2017-07-21 09:50:12
|
In JT65/JT9, I often will try to find a clear transmit frequency, and by turning off TX/RX lock, work other stations split-frequency. In the hectic waterfall of FT8, that is something I would especially like to do in this mode - I don't want to step on other callers to a CQ'ing station, and would like to "homebase" myself on one sliver of the bandwidth to use for calling other stations or CQ'ing. No matter if TX/RX lock is on or off, my initial calls to other stations are moved to their transmit frequency. I can move away after the first call and my subsequent calls can be on a different frequency, but I can't figure out how to keep my initial call to a station on my chosen transmit frequency. Am I missing something, or is there not a way to lock my transmit frequency as there is in JT65/JT9? Kudos to all who have done such a great job with the software, and especially the new features in 1.8! 73, Bob Edward KH6BE Honolulu, HI |
|
From: Bill S. <g4...@cl...> - 2017-07-21 10:09:59
|
On 21/07/2017 10:49, R Edward wrote: > In JT65/JT9, I often will try to find a clear transmit frequency, and by turning off TX/RX lock, work other stations split-frequency. > > In the hectic waterfall of FT8, that is something I would especially like to do in this mode - I don't want to step on other callers to a CQ'ing station, and would like to "homebase" myself on one sliver of the bandwidth to use for calling other stations or CQ'ing. > > No matter if TX/RX lock is on or off, my initial calls to other stations are moved to their transmit frequency. I can move away after the first call and my subsequent calls can be on a different frequency, but I can't figure out how to keep my initial call to a station on my chosen transmit frequency. > > Am I missing something, or is there not a way to lock my transmit frequency as there is in JT65/JT9? > > Kudos to all who have done such a great job with the software, and especially the new features in 1.8! Aloha Bob, firstly I should say that if everyone worked split on a busy band then the overall capacity would probably be reduced. Maybe it wouldn't due to the strictly timed sequences but coordination of everyone would be tricky. So I think that using two different frequencies for a QSO should be reserved for only when it is necessary for example when using less power than most users or when calling a popular and busy station. All that "Lock Tx=Rx" does is ensure that both frequencies are the same i.e. if you or the program changes one then the other will follow. Un-checking the option reverts to normal behaviour where it is expected that a CQ caller stays on one frequency and stations calling move to his/her frequency. As part of a review of the sequencing logic I am going to add a modified mouse click action, probably ALT+double-click on a decoded message to only move the Rx frequency to a CQ caller. This should meet your requirement. 73 Bill G4WJS. |
|
From: Steve N. <sn...@ch...> - 2017-07-21 11:21:41
|
I concur with Bob on a need for this feature and like your solution Bill. 73, Steve K5FR -----Original Message----- From: Bill Somerville [mailto:g4...@cl...] Sent: Friday, July 21, 2017 5:10 AM To: wsj...@li... Subject: Re: [wsjt-devel] RX/TX lock in FT8 On 21/07/2017 10:49, R Edward wrote: > In JT65/JT9, I often will try to find a clear transmit frequency, and by turning off TX/RX lock, work other stations split-frequency. > > In the hectic waterfall of FT8, that is something I would especially like to do in this mode - I don't want to step on other callers to a CQ'ing station, and would like to "homebase" myself on one sliver of the bandwidth to use for calling other stations or CQ'ing. > > No matter if TX/RX lock is on or off, my initial calls to other stations are moved to their transmit frequency. I can move away after the first call and my subsequent calls can be on a different frequency, but I can't figure out how to keep my initial call to a station on my chosen transmit frequency. > > Am I missing something, or is there not a way to lock my transmit frequency as there is in JT65/JT9? > > Kudos to all who have done such a great job with the software, and especially the new features in 1.8! Aloha Bob, firstly I should say that if everyone worked split on a busy band then the overall capacity would probably be reduced. Maybe it wouldn't due to the strictly timed sequences but coordination of everyone would be tricky. So I think that using two different frequencies for a QSO should be reserved for only when it is necessary for example when using less power than most users or when calling a popular and busy station. All that "Lock Tx=Rx" does is ensure that both frequencies are the same i.e. if you or the program changes one then the other will follow. Un-checking the option reverts to normal behaviour where it is expected that a CQ caller stays on one frequency and stations calling move to his/her frequency. As part of a review of the sequencing logic I am going to add a modified mouse click action, probably ALT+double-click on a decoded message to only move the Rx frequency to a CQ caller. This should meet your requirement. 73 Bill G4WJS. ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel |
|
From: dgb <ns...@ba...> - 2017-07-21 11:27:28
|
Very good idea Bill! tnx 73 Dwight NS9I On 7/21/2017 5:09 AM, Bill Somerville wrote: > On 21/07/2017 10:49, R Edward wrote: >> In JT65/JT9, I often will try to find a clear transmit frequency, and >> by turning off TX/RX lock, work other stations split-frequency. >> >> In the hectic waterfall of FT8, that is something I would especially >> like to do in this mode - I don't want to step on other callers to a >> CQ'ing station, and would like to "homebase" myself on one sliver of >> the bandwidth to use for calling other stations or CQ'ing. >> >> No matter if TX/RX lock is on or off, my initial calls to other >> stations are moved to their transmit frequency. I can move away after >> the first call and my subsequent calls can be on a different >> frequency, but I can't figure out how to keep my initial call to a >> station on my chosen transmit frequency. >> >> Am I missing something, or is there not a way to lock my transmit >> frequency as there is in JT65/JT9? >> >> Kudos to all who have done such a great job with the software, and >> especially the new features in 1.8! > > Aloha Bob, > > firstly I should say that if everyone worked split on a busy band then > the overall capacity would probably be reduced. Maybe it wouldn't due > to the strictly timed sequences but coordination of everyone would be > tricky. So I think that using two different frequencies for a QSO > should be reserved for only when it is necessary for example when > using less power than most users or when calling a popular and busy > station. > > All that "Lock Tx=Rx" does is ensure that both frequencies are the > same i.e. if you or the program changes one then the other will > follow. Un-checking the option reverts to normal behaviour where it is > expected that a CQ caller stays on one frequency and stations calling > move to his/her frequency. > > As part of a review of the sequencing logic I am going to add a > modified mouse click action, probably ALT+double-click on a decoded > message to only move the Rx frequency to a CQ caller. This should meet > your requirement. > > 73 > Bill > G4WJS. > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > |
|
From: Jim B. <k9...@au...> - 2017-07-21 17:27:16
|
On 7/21/2017 3:09 AM, Bill Somerville wrote: > firstly I should say that if everyone worked split on a busy band then > the overall capacity would probably be reduced. There are good reasons for not calling zero beat. Taking 6M double-hop E-skip as an example, I often find myself beaten by a W0 station when calling W1 or W2. Another example is a pileup for a rare country, state, or grid, where the strongest station is likely to win. And with modes like FT8 that don't do well with multiple signals on the same frequency, no one gets decoded. This often happens with humans attempting to decode CW with multiple callers zero beat with each other as a result of clicking on a cluster spot. 73, Jim K9YC |
Thanks for helping keep SourceForge clean.
X