Re: [wsjt-devel] Timer
All four stations were strong. K1JT started out at +15 on 20 meters, but within 20 minutes had dropped to -23 (late afternoon band change). 30 dB change in about 20 minutes...talk about catching the band moving! Completed with all 4 stations, but one completion was aided by a trick on my end. After I had been "moved" to the lower freq tier by the Fox, it put me in a mess of others. So I watched the rx window for a while and when I saw a hole develop, I moved my TX there (still in the lower freq tier area where the Fox had put me, but in a clearer spot). Immediately on my next transmission, the qso finished out. The attached image shows a nice trace of the N=5 Fox ...very cool! It was a fun test, noticed same anomalies as others. Had two lockups on Rx. Killed and restarted program and all was fine. Deliberate qrm was significant in amount, but ineffective. I saw it all, but it cause me no problems with the Fox, nor completing contacts. I look look forward to the next test. This was MOST enjoyable. Congrats to the team! 73, N0AN Hasan On Wed, Mar 7, 2018 at 10:09 AM, Joe Taylor <j...@princeton.edu> wrote: > Jim -- > > I don't think you had to scramble. If Fox calls you, your Tx3 message > will be sent (somewhere in 300-900 Hz), even if Tx Enable is not engaged. > -- Joe > > > On 3/7/2018 11:05 AM, James Shaver wrote: > >> Yep, twice the timer had expired on me right as the “Fox” called me and I >> had to scramble. >> >> Jim S. >> N2ADV >> >> *From:*Bill Turner via wsjt-devel [mailto:wsjt-devel@lists.sourc >> eforge.net] >> *Sent:* Wednesday, March 7, 2018 11:03 AM >> *To:* WSJT Software Development >> *Cc:* Bill Turner >> *Subject:* [wsjt-devel] Timer >> >> Great job with the test last night. I did find the 2 minute timer to be >> a real pain, however. I understand you do not want a robot operation, but a >> 5 or 10 minute timer would be less frustrating. >> >> When the software shuts off the Enable TX, how do we know that we are >> still on the correct sequence when we click on Enable TX? I noticed some >> comments about folks calling on the wrong sequence last night. >> >> Again, thanks for the effort in the test. >> >> Bill Turner, W4WNT >> >> >> >> >> -- >> 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 >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >> > > -- > 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 > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- 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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Timer
Thanks, Steve and Joe both - my sleep-deprived brain completely failed to register that part. Jim S. -Original Message- From: Steven Franke [mailto:s.j.fra...@icloud.com] Sent: Wednesday, March 7, 2018 11:13 AM To: WSJT software development Subject: Re: [wsjt-devel] Timer Hi Jim, Check out item 12 in the Hound instructions: “12. After you receive a signal report from Fox, WSJT-X will automatically send your next transmission as message Tx 3 (“R+rpt”) at a randomly chosen frequency between 300 and 900 Hz. Note that WSJT-X will send this message even if Enable Tx is disabled, and even if you have not called Fox for several Tx sequences. If you have stopped calling Fox because you will be leaving the rig unattended, you should quit WSJT-X or disable Hound mode in order to avoid the possibility of unwanted transmissions." It is important to understand this behavior. It means that, in most cases, you should not just leave your rig on and monitoring the DX after you have stopped paying attention, as you could be in for a surprise when your rig springs to life and starts TXing. Steve K9AN > On Mar 7, 2018, at 10:05 AM, James Shaver <n2...@windstream.net> wrote: > > Yep, twice the timer had expired on me right as the “Fox” called me and I had > to scramble. > > Jim S. > N2ADV > > From: Bill Turner via wsjt-devel > [mailto:wsjt-devel@lists.sourceforge.net] > Sent: Wednesday, March 7, 2018 11:03 AM > To: WSJT Software Development > Cc: Bill Turner > Subject: [wsjt-devel] Timer > > Great job with the test last night. I did find the 2 minute timer to be a > real pain, however. I understand you do not want a robot operation, but a 5 > or 10 minute timer would be less frustrating. > > When the software shuts off the Enable TX, how do we know that we are still > on the correct sequence when we click on Enable TX? I noticed some comments > about folks calling on the wrong sequence last night. > > Again, thanks for the effort in the test. > > Bill Turner, W4WNT > -- > 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 > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- 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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- 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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Timer
Bill, TX timeout timer is about right. Prevents non-stop (when not being heard) QRM from Hounds. Also, when it times out, you have time to let a couple cycles go by and see where in the band it might be best to call (look for hole). I did this multiple times (let it expire), watched the pileup, found a hole, then simply hit Enable Tx...off it went. No settings needed to be changed. Sequence is automatic, no intervention needed. If people were off sequence it was either caused by 1) Incompetence, 2) a bug , 3) Deliberate interference, of which there was a bunch. As far as the Hounds are concerned, there is no sequence...it is all controlled by the Fox. If you double click on the Fox, after setting your Tx freq > 1000, then the only intervention required is if you aren't getting heard, and then just Enable Tx again. 73, N0AN Hasan On Wed, Mar 7, 2018 at 10:02 AM, Bill Turner via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Great job with the test last night. I did find the 2 minute timer to be a > real pain, however. I understand you do not want a robot operation, but a 5 > or 10 minute timer would be less frustrating. > > When the software shuts off the Enable TX, how do we know that we are > still on the correct sequence when we click on Enable TX? I noticed some > comments about folks calling on the wrong sequence last night. > > Again, thanks for the effort in the test. > > Bill Turner, W4WNT > > > -- > 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 > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > -- 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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Timer
Hi Jim, Check out item 12 in the Hound instructions: “12. After you receive a signal report from Fox, WSJT-X will automatically send your next transmission as message Tx 3 (“R+rpt”) at a randomly chosen frequency between 300 and 900 Hz. Note that WSJT-X will send this message even if Enable Tx is disabled, and even if you have not called Fox for several Tx sequences. If you have stopped calling Fox because you will be leaving the rig unattended, you should quit WSJT-X or disable Hound mode in order to avoid the possibility of unwanted transmissions." It is important to understand this behavior. It means that, in most cases, you should not just leave your rig on and monitoring the DX after you have stopped paying attention, as you could be in for a surprise when your rig springs to life and starts TXing. Steve K9AN > On Mar 7, 2018, at 10:05 AM, James Shaver <n2...@windstream.net> wrote: > > Yep, twice the timer had expired on me right as the “Fox” called me and I had > to scramble. > > Jim S. > N2ADV > > From: Bill Turner via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] > Sent: Wednesday, March 7, 2018 11:03 AM > To: WSJT Software Development > Cc: Bill Turner > Subject: [wsjt-devel] Timer > > Great job with the test last night. I did find the 2 minute timer to be a > real pain, however. I understand you do not want a robot operation, but a 5 > or 10 minute timer would be less frustrating. > > When the software shuts off the Enable TX, how do we know that we are still > on the correct sequence when we click on Enable TX? I noticed some comments > about folks calling on the wrong sequence last night. > > Again, thanks for the effort in the test. > > Bill Turner, W4WNT > -- > 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 > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- 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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Timer
I missed that in the documentation - thanks for that, Joe! My cat was very put out when I made a mad dash for the mouse ;) I'll apologize to her later. Jim S. N2ADV -Original Message- From: Joe Taylor [mailto:j...@princeton.edu] Sent: Wednesday, March 7, 2018 11:09 AM To: WSJT software development Subject: Re: [wsjt-devel] Timer Jim -- I don't think you had to scramble. If Fox calls you, your Tx3 message will be sent (somewhere in 300-900 Hz), even if Tx Enable is not engaged. -- Joe On 3/7/2018 11:05 AM, James Shaver wrote: > Yep, twice the timer had expired on me right as the “Fox” called me and > I had to scramble. > > Jim S. > N2ADV > > *From:*Bill Turner via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] > *Sent:* Wednesday, March 7, 2018 11:03 AM > *To:* WSJT Software Development > *Cc:* Bill Turner > *Subject:* [wsjt-devel] Timer > > Great job with the test last night. I did find the 2 minute timer to be > a real pain, however. I understand you do not want a robot operation, > but a 5 or 10 minute timer would be less frustrating. > > When the software shuts off the Enable TX, how do we know that we are > still on the correct sequence when we click on Enable TX? I noticed > some comments about folks calling on the wrong sequence last night. > > Again, thanks for the effort in the test. > > Bill Turner, W4WNT > > > > -- > 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 > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- 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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- 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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Timer
Jim -- I don't think you had to scramble. If Fox calls you, your Tx3 message will be sent (somewhere in 300-900 Hz), even if Tx Enable is not engaged. -- Joe On 3/7/2018 11:05 AM, James Shaver wrote: Yep, twice the timer had expired on me right as the “Fox” called me and I had to scramble. Jim S. N2ADV *From:*Bill Turner via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] *Sent:* Wednesday, March 7, 2018 11:03 AM *To:* WSJT Software Development *Cc:* Bill Turner *Subject:* [wsjt-devel] Timer Great job with the test last night. I did find the 2 minute timer to be a real pain, however. I understand you do not want a robot operation, but a 5 or 10 minute timer would be less frustrating. When the software shuts off the Enable TX, how do we know that we are still on the correct sequence when we click on Enable TX? I noticed some comments about folks calling on the wrong sequence last night. Again, thanks for the effort in the test. Bill Turner, W4WNT -- 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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- 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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Timer
Yep, twice the timer had expired on me right as the “Fox” called me and I had to scramble. Jim S. N2ADV From: Bill Turner via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: Wednesday, March 7, 2018 11:03 AM To: WSJT Software Development Cc: Bill Turner Subject: [wsjt-devel] Timer Great job with the test last night. I did find the 2 minute timer to be a real pain, however. I understand you do not want a robot operation, but a 5 or 10 minute timer would be less frustrating. When the software shuts off the Enable TX, how do we know that we are still on the correct sequence when we click on Enable TX? I noticed some comments about folks calling on the wrong sequence last night. Again, thanks for the effort in the test. Bill Turner, W4WNT -- 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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Timer
Great job with the test last night. I did find the 2 minute timer to be a real pain, however. I understand you do not want a robot operation, but a 5 or 10 minute timer would be less frustrating. When the software shuts off the Enable TX, how do we know that we are still on the correct sequence when we click on Enable TX? I noticed some comments about folks calling on the wrong sequence last night. Again, thanks for the effort in the test. Bill Turner, W4WNT -- 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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
