Sounds like Onmi-Rig did not migrate correctly. Download a new copy from <http://dxatlas.com/omnirig/> and reinstall it. Make sure it is also configured to run at user level and not administrator. 73,

#Cat_RigControl

A couple of reasons ... the available spectrum for data modes is quite limited on 160 and the band tends to be quite noisy. SN requirements for FT4 are such that other modes - particularly FT8, JT9, a

#NewUser

Never had a problem. WSJT 2.4.0-rc4, Windows 10 20H2, microHAM MK II/MK III (external USB sound card), Elecraft K3. Using PTT=RTS on a separate COM port. I'd be more disposed to an error in your confi

#BugReport #AudioIssues

As G4WJS has told you ... This is *basic Windows* for any system that uses USB devices for communication with external hardware (e.g. a transceiver). Windows is very poor in determining if a USB devic

#AudioIssues

Have you set Settings -> Radio -> Mode to DATA/PKT? Try setting Settings -> Radio -> Mode to USB 73, ... Joe, W4TV

#WSJTX_config #FT8

Select (activate) the Callsigns window -> click the gear icon or press F2 -> Select Callsigns -> Set "Display width" to any value you like other than "Auto" (90 works for me). 73, ... Joe, W4TV

#WSJTX_config

Windows Sound Control Panel. Connect one (say the 7300), rename it. Then connect the other and rename it. You want to rename both the input (in the "recording" tab) and the output (in the "playback" t

#GeneralGroupInfo

That you are not a programmer answers your own question. WSJTX can maintain a database of each country, grid and zone for the current colors. Add "worked B4" for every callsign (and band and supported

#FT8 #GeneralGroupInfo

In WSJTX the default order (after all the new DXCC, new zone, and new grid both on any band and on the current band options) is New Call, New Call this band and Calling CQ. If it is not a new call or

#FT8 #GeneralGroupInfo

JTAlert has both an explicit "B4" (Settings -> Alerts -> Worked B4) and and CQ (Settings -> Alerts -> CQ) alert/colors. The B4 overrides all other alerts. 73, ... Joe, W4TV

#FT8 #GeneralGroupInfo

As one of the developers has told you several times - *THERE IS NO B4 COLOR IN WSJTX*. I have gone back to version 2 and checked - there is no B4 color in any version 2, version 3 *or* version 4 (-RC#

#FT8 #GeneralGroupInfo

There is no PTT from WSJTX with Signalink! Signalink is an audio card with built-in VOX. Use the "VOX" setting in WSJTX. 73, ... Joe, W4TV

#AudioIssues

*THERE IS NO B4 COLOR IN SETTINGS -> COLORS* The only way one gets a specific color for B4 is with JTAlert. 73, ... Joe, W4TV

#FT8 #GeneralGroupInfo

If you are using WSJTX, JTAlert *and* DXKeeper, you will need to do it this way as JTAlert will use your DXKeeper log for "B4" and not the WSJTX file. The adif file is only used when JTAlert is not lo

#udp #ContestMode #FT8 #logging

Better stated as "send your RR73 *or* RRR" .... 73, ... Joe, W4TV

#FT8

That's well and good until you are on the other side ... Say you are working a rare DX (or rare state for WAS, etc.), he sends you RR73 and someone else (who also needs him) calls right on top of your

#FT8

Take this to the JTDX support list. The is the WSJTX list. 73, ... Joe, W4TV

#logging

If that is your definition of a "complete" QSO, 90+ of CW/SSB DXpedition and contest QSOs in the last 50 years are not "complete". A QSO is complete when each station has received and acknowledged the

#FT8

No! 73 in response to 73 is redundant and wasteful. When the first station sends R-## he is already acknowledging the calling station's report. When the calling station sends RRR and the first station

#FT8

Beacon List here: <https://www.qsl.net/wj5o/bcn.htm> The FT4 segment is questionable. I would recommend staying *below* 28.160 and look for something below 28.145 ... perhaps between 28.130 and 28.140

#Q65