Too many characters. That’s why CQ AS…… works better. AS and others are “built-in” to the program and are recognized and dealt with. Gary - AG0N

This are continents, not countries. Gary - AG0N

Thanks Bill. -- Ryan, KC0QNB, DN90WW. Gothenburg, NE

recommends I've searched documentation and have found nothing on Alternate F1-F6 bindings. I can select it under Settings/General, but what does it do. How does one use it in various situations? Help

Hi Ryan, the WSJT-X highlighting logic does not specifically highlight worked before stations, it highlights stations calling CQ or QRZ that you may want to work. If you enable the "New Call" and

“More Power, Scotty!” Gary - AG0N

I have the show DXCC, grid and worked before status checked, I have seen callsigns show up that I know that I have worked, before, what differentiates worked before status from a standard green CQ

Hi John, As mentioned in the WSJT-X User Guide: "Be sure to read the operating instructions for FT8 DXpedition Mode." -- 73, Joe, K1JT

Are you saying that following your ODD Tx time, you see nothing on the EVENs, then the next ODD Tx time (evidently you disabled the Transmit button) you don't see anything either?

Thanks Martin, I don't normally have the TX1 etc tab open so I wasn't aware of it. 73 Phil GM3ZZA -- 73 Phil GM3ZZA

John, All of your questions...and probably some that you haven't thought of can be answered by having a quick read of this

Tnx Dave, I've got things back to normal. Disconnected everything and got each working on its own. Had to revise the new path to HamPrograms folder in a few places I missed the first time around.

Log checking for several recent contests that used the FT4 and FT8 modes has shown undesirably large numbers of claimed QSOs that receive not-in-log ("NIL") status from the other station. The WSJT

Ok, I will try the Esc key , but I find also entries that do have other QSO's in between - that is what really concerns me . I'm just sitting and editing my logs in MacLogger - and find 1 out of 100

I am new to using fox and hound. I was trying it out yesterday. In hound mode, WSJT-X would transmit the TX1 message a few times and then stop. Is that normal? Should I just enable transmit again? I

-- I use wsjtx 2.1.2 with Ic-7300 for Ft8 for a couple of years now, it works fine. I have an issue when I go to fox and hound. When I enable the transmit button after I make my call for 15 seconds

On 26/02/2020 16:12, Steinar Fremme wrote: Knut, this will only happen if you have no intervening QSOs. If you abandon a QSO then hit the ESC key, this will forget the

Sure I can , but why should it be necessary - I classify it as a bug in functionality. And yes - I just set the start time - 1 minute before end-time - and then all is ok. Now when I know about - i'm

On 25 Feb 2020 at 21:45, Steinar Fremme wrote: > When I then look at the entries I > find that the start-time for the log > entry is the start time for the > FIRST QSO, that did not succeed , and >

Lots of good stuff here, but I really like the cold cerveza tip -- 73 Mick VA3EPM