Ah....some one suggested going back and checking USB settings...I did that and found all ok...so I'm sitting here thinking what did I do between the night when the signals were blasting in and the

Don't feel silly. This is just a new way of operating with a new set of modes that are unlike anything we are used to from the past. Perfectly acceptable. Think of it like holding a run frequency in a

Reverting back to v2.2.2 is great, however, installing v2.3.0 in another directory and giving Bill Somerville as much detail as possible would benefit everyone as v2.2.2 does not have the same version

Time to put this thread to bed. I found a solution, uninstall version 2.3 and re-install version 2.2.2. Problem fixed. There is no doubt there is something with the newer version that was causing the

Tony, As I've said before, I can do that by turning the VFO knob, *IF I REMEMBER IT AFTER CHANGING BANDS*. I"m looking for a way to automate that (e.g., tune to 7.073,500 MHz instead of 7.074,000

Hi Joe - I think you have CAT Control on your rig? You can change the frequency of WSJT-X by typing the required frequency into the "band" box. Instead of selecting 7.074 (40m) from the drop down list

For the record here in the UK I have had successful 1296MHz QSO's on troposcatter over obstructed paths greater than 300 miles with 10W stations. This was from normal station locations not mountain

I haven't had any issues with CAT on my few F/H QSOs. I generally handle the low TX offset by cranking the main VFO down 300 - 400 Hz but it too easy to forget it when hopping among bands until one

Moving up/down is not the issue. The issue is the stations calling (CQ) or working other stations with TX offsets less than 300 or 400 Hz. They are greatly attenuated by the default flyers in

Hi Dave, Good question... Good answer - "OLDER radio"! Fake it - does NOT work right on some radios! MANUAL - ALWAYS works! Proof? You want proof? "Auto-drive" mode on cars! Works great! Until it

why not just turn on fake it, assuming you have cat control. this will automatically put you up ( or down) when needed to be in the desired audio range Dave Garber VE3WEJ / VE3IE

Hi Joe, Yes, and this issue is especially true on fox & hound when the fox insists on dragging you down to 300 or 400 hz on older radio's (like mine). I have found that just manually tuning 1kHz lower

That first part seems like it might make a good app enhancement. Perhaps "Stop TX upon target response to another station."

Is there a convenient way (other than editing all of the frequencies in the frequency list) to get WSJTX to "come up" 200, 300, 500 Hz *below* the nominal frequency? I ask because many common

Jarmo - I would guess that back in 2010 you were probably running Windows Vista or XP and used the computer's true RS232 serial port with DB9 connector for the radio CAT control functions. And a

I'm surprised you would imagine there has not been much use of Q65 on U=HF and SHF bands. Quite the contrary! Q65 was extensively tested with EME on bands from 432 MHz through 10 HGz, even before

I choose not to call a DX station every 30 seconds as an attention-getting measure. I wait until the DX station sends RR73 or 73, and then I transmit. If the DX station comes back to someone else, I

Hi Mike, I suspect that Q65B would be more tolerant of frequency variations. My only experience on 2m EME was with Q65A, which I was very pleasantly pleased worked with most stations. It is most

On PSK at the moment the only stations I here are those fldigi tell me I’ve worked before. If someone tells me we’ve worked before I don’t regard that as a telling off. 73 Phil. Sent

Did you guys try Q65B on 2m, or would that suffer from the same problems that you noticed with Q65A? (Full disclosure: I have not tried EME at all yet, but once I build a reasonable 2m Yagi and put