Bob, Here is s snapshot of my setup screen.

Bob, It looks like you are still pointing to ACLog. Laurie has a nice tutorial in the help section that explains how to set up for contesting. Hope this helps. Steve, AI3KS

Greg, Be sure that N3FJP FD Logger has the API enabled. Configure both WSJT-X and JTAlert for Field Day. In WSJT-X enter a call in the DX CAll window. Click Log QSO In the QSO entry window fill in bot

Sam, From what I have been reading on the N3FJP groups, you MUST have the "OPERATOR" Field on the Settings>Setup screen set either to your Call or Blank. If not, then the newest version of TQSL throws

#FT8

Norm, Do you have the API enabled in ACLog (under sedttings)? Steve, AI3KS

Stan, Laurie, The exhange is not the same. RU wants State, the HPM event wants section. Steve, AI3KS

Garry, I had some problems getting it all tied together too. Make sure that when you log from WSJT-X that the entire contest exchange (rst and state) are showing in the exchange sent and received boxe

Laurie, Thanks for the help. I figured out that my problem was self inflicted. In my manual qsos I was not entering the full exchange in the WSJT-X Log screen, only the state. 73, Steve, AI3KS

Carey, Thanks for the help. I figured out that my problem was self inflicted. In my manual qsos I was not entering the full exchange in the WSJT-X Log screen, only the state. 73, Steve, AI3KS

I am posting this both in the HamApps and N3FJP Forums, so please excuse the extra bandwidth. I must be missing something simple but I can't get JTAlert to properly log to N3FJP RTTY Log. Running: N3F