moderated Re: Auto-sequence definately fouled up!

Bill Somerville

Hi John,

OK, I suspect the issue relates to your not having "Settings->Reporting->Clear DX call and grid after logging", that action "clears down" the QSO. Although it should not be responding again in the way that it did, and I will resolve that, I recommend you either set that option or at least hit ESC when you are done with a QSO so that WSJTY-X knows you are done with it. Note logging does not necessary say you are done with the QSO, many of us log upon receipt of an R+report but continue with the QSO until we are sure a QSO partner has received their RRR or RR73 acknowledgement.


On 22/11/2020 14:45, JP Tucson, AZ wrote:

I thought it was pretty clear, but I'll try to clarify... (smart ass remark warning - humor not being offensive - you're in England, you sure English is your native language? ūü§®)

I'll answer below in red...

Thanks Bill

73 - John - N7GHZ

On Sun, Nov 22, 2020, 5:14 AM Bill Somerville <g4wjs@...> wrote:
On 22/11/2020 06:03, JP Tucson, AZ wrote:
> Again, the thing has lost its mind!
> It is all over the place!!!
> Sometimes, after a 73, it sends you back to an "R-xx" report,
> sometimes as the attached shows, it sends you back to the CQ call
> (TX1) that you just completed.
> And sometimes it now just stops, it didn't do anything...!  It had tx
> enabled and should have went to CQ - TX6, instead it just hung up
> (stayed in RX/monitor mode & kept rx) even though the red - enable tx
> was on. I had to hit Halt TX (3 times!), then re-enable TX before it
> would do anything.
> All cpu indications are clear, nowhere near limits on cpu or graphics,
> can start other programs (like gmail) & all works fine w/wsjtx
> running, until it loses its mind again a few cycles later.  I did a
> full shut down, 5 min., then restart, with nothing else running, it
> went crazy again after 3 cycles, that's when I snipped the image below.
> [[[Completed N6RCS, then it went back to calling N5CRS again on CQ, even
> though I selected K7KE
> Had to manually reselect K7KE again, went thru & completed that QSO]]] &
> it did it again, not shown in this snip.
> It started off ok, but now its getting worse.


referring to "the thing" and "it" in your description of an issue is
most unhelpful,[meaning the auto sequencer, as I stated in the title   -"Auto-sequence(r)definately fouled up!"] nor do I have the faintest idea what actions you took in
the exchange you describe. [I actually did, see the triple brackets above ([[[)] For example, did you log the QSO [yes, as I indicated when I stated that I completed the QSO - meaning I logged it!], if so at
what point? [When it (wsjtx) went to TX4 (RRR) & popped up the log box & I did, and it's in the log]   Did you double-click the 73 response from your QSO partner
or did the retransmission of your Tx1 message happen spontaneously? [The latter, as I didn't touch anything until after I sent my final 73 & then selected my next tart station - K7KE - - - INSTEAD of calling K7KE as I directed, it went back to TX1 with "CQ K6RCS N7GHZ DM42"] Do
you have "Settings->Reporting->Prompt me to log QSO" checked? [YES] Do you
have "Settings->Reporting->Clear DX call and grid after logging"
checked? [No, never have] Do you have "Settings->General->Disable Tx after sending 73"

So that you see the answer to Roger's Q.,  no, I don't have an rfi issue, the mouse & kb have ferrites % the pc is grounded to the single point station ground.  I have also swept my for stray rf with a field strength meter - nothing at all, anywhere in the shack!


Join to automatically receive all group messages.