Hi All, Another possibility to move Hounds to a DX frequency, say 14.090 MHz, could be that the Fox sometimes sends on a standard frequency "CQ 090" (perhaps even above 100 Hz audio). See 17.1.

A F/H station should never be on the normal frequency segments. That said, it has been abused by a few. Normally, an expedition will publish special frequencies along with their operating

How do I set RR73 in the Generated Message list? Tnx.

I've moved an external USB adapter from my Linux Mint 19.3 laptop to my Linux 20.3.  WSJTX works fine on the 19.3 laptop but on the 20.3 laptop my Elecraft KX3 doesn't appear to be transmitting even

WSJT-X (running on Linux) running with my KX3 receives and decodes FT8 fine but no transmissions ever show up on PSKREPORTER. WSJT-X can change bands and follows the frequency if I manually change

Kari, Most likely the op was using MSHV. MSHV's multi stream looks like F/H but it's not. If you attempt to transmit as a fox on a standard frequency you will get the following message: [image:

@ Joel: > For whatever reason, macOS has the scaling correct. Windows does not. Windows 10 also has the scaling correct, and I see no reason why this should be different on Windows 11. See my

Here's something that worked for me, starting with the directory structure after you've untarred the 'source tarball', made the build directory, and encountered the error: in your wsjt-x build

The power in Fox mode is reduced to allow for this. So when the Fox increases slots the power of each signal is reduced. From the FT8 Dxpedition Guide (in the Help menu) Thus, for N Slots = 1, 2, 3,

Just FYI - the standard for the 1st 4 digits of the locator is upper case. So there are some instances where a ’standard’ does exist. :-) Regards Tom GM8MJV Tom@... See:

Was trying to diagnose a double HRD LB logging problem, but in trying to roll back from v2.6.0-rc1 to v2.5.4 to check, I found that the older version would install, but would NOT execute. Rebooted

I think if you're in Hound mode that WSJTX should disallow transmitting until the dxpedition is detected. A little cache of decoded callsigns < 500Hz (like the last 20 or so) would detect the Fox and

WSJT-X forces the hound to be on the correct time slot. I’m not sure about the WSJT knock-offs… Bill WB6JJJ I should've been more clear. If a station is in Hound mode, it is indeed forced to

——— The software could even pop a message up if a Hound tried to call in the wrong time sequence or below 1000 Hz. ——— WSJT-X forces the hound to be on the correct time slot. I’m not

I think if you're in Hound mode that WSJTX should disallow transmitting until the dxpedition is detected. A little cache of decoded callsigns < 500Hz (like the last 20 or so) would detect the Fox and

Probably MSHV ... not WSJT-X. Neil, KN3ILZ

Well, there was one just a few minutes ago on 18.100 ... 73's de Kari, oh2gqc Yeah... This has become somewhat common of late, hasn't it? I guess some DXpeditions are finding that if they use the

I built 2.6.0-rc1 from source on my RPi4 and all seems fine at 1600 x 1200. Font is Pibota 10. 73, Joel - W4JBB

Well, there was one just a few minutes ago on 18.100 ... 73's de Kari, oh2gqc

1. Fox calls CQ -Even/1st 2. Fox will NOT be on standard frequencies i.e. 14074, etc. 3. Fox will be below 1000 Hz, usually 200-400 Hz I'm sure others will provide additional info. Robie - AJ4F