Mike, I owe you an apology, and I feel like a dummy. I forgot about one other variable in the mix. I use Win4Yaesu to interface to the rig, going through microHam microKeyer router. When I take Win4Ya

#hamlib

Mike, I set the number as high as 10000, and still got the warnings. The warnings are generated whenever I change the audio offset for xmit (the red mark in the wide graph). Also, this only happens if

#hamlib

Mike, The attachment didn't come through. Here is a link to the file on Dropbox: https://www.dropbox.com/s/o97q3d0c773p750/WSJT-X_RigControl.log?dl=0 73, Jim N6VH

#hamlib

Mike, Yes, WSJT-X now connects to the rig immediately. I re-checked split using "rig" and "fake it", and they work fine also. However, there were still some warnings in the wsjtx_syslog.log not relate

#hamlib

In WSJT-X Settings/General, check "Start new period decodes at top". 73, Jim N6VH

#TechnicalHelpQuestion

Joe, I tested with both "Rig" (which is what I normally use) and "Fake It". In both cases, the rig control behaved as it should. However, with the new file, it takes about five seconds to connect to t

#hamlib

Tom, Does this involve WSJT-X set to Omnirig in Settings - Radio? If so, my solution is to not use that setting, but instead set it to Yaesu FTDX-5000. In Bo's case, he would set it to IC-7610. While

#Cat_RigControl

Bo, Yes, that's what Log4OM says. However, that document wasn't written with your (and my) setup in mind. Using Win4Icom (or Win4Yaesu in my case) negates what is in that document. Use Omnirig with Lo

#Cat_RigControl

Bo, Since you are using Win4Icom, you do NOT need to run Log4OM and Omnirig as Administrator. The only reason to do that would be if you are using the multi-threading feature of Omnirig. That is only

#Cat_RigControl

Dick, I'll chime in with my two cents worth. Is it possible that something else on your computer is causing delays when you first start the programs? It could be something running in the background, l

#FT8 #logging

Dan, Not every one has the same requirement for what constitutes a valid QSO. Some require a 73, others don't. In my case, all I ask is that I get an acknowledgement of the report I sent. RR73 covers

#QSO_practices

Dick, There seem to be a number of issues here, and they might not be with WSJT-X. First, you said that your configuration was working fine previously. Had you made any changes that might have caused

#FT8

#QSO_practices

Ken, If I don't receive an RRR or RR73 (or something else that tells me the other station received my report) I send my report again, usually 4 or more times. If I still don't get an acknowledgement,

#QSO_practices

2.5.1 x64 opens at the most recent size on my machine. 73, Jim N6VH

Rick, In the "Generate Standard Messages" tab, do you have one of the "TX " boxes selected that is empty (see attached). If so, that, could cause the problem. Since you said it works you use a differe

#transmit

In WSJT-X, go to File/Open Log Directory. The file should be there. 73, Jim N6VH

#FT8

Jim, Use Tab 1. The CQ button will be TX 6. See attached picture. 73, Jim N6VH

#mainscreen #GeneralGroupInfo

Bobby, That's the point of Hold TX Freq. Your frequency shouldn't move to the other station's frequency. Assuming you have a clear freq to start with, their should be no problem. Granted, ia very few

#FT8

Bill, Yes, that's what I meant by middleman - WSJT - HRD - LOTW. HRD is what I was considering the middleman. WSJT - LOTW would be without a middleman. I have never seen a way of doing this, but was j