Hi Neil, and David, it's not that simple. The working frequencies tables for every configuration have to be read into memory at application start up, that can only work if all the modes used are defin

#Q65

On 50305 I and I think a few others are planning to use odd in NA for transatlantic work and hope the other side will use even. This worked out well on FT8. Jim VE1JF

#Q65

Many Thanks... I have seen a post on a logbook forum on this topic of adding Q65 to logging option best 73 Dave

#Q65

You DO study documentation on the WSJT-X main page before asking questions here, don't you? 73, Jim K9YC

#Q65

Great, thanks Bill.. (I suspected it had something to do with the fact that 2.4.0 is an RC version) 73 de Jim VE4CY

#Q65

That did the trick Neil, thanks. I looked at it earlier but didn't see Q65 mode...after your comment I just did an edit and put "all" in for mode. Probably not the best way to have done it but it work

#Q65

No problem, try 50.275 MHz and 30A, there seems to be a lot of activity there. People have also been on 50.235 MHz 120E

#Q65

OK.. 30A then. Will try that today. Thanks to all who replied.. -- (Too many to thank individually :) ) 73 de Jim VE4CY

#Q65

Yep, I have those same problems with terrestrial operations. 73, Jay K0GU

#Q65

Here in the US, the sweet spot to take advantage of its greater noise rejection is FST4-60, and nearly all activity is between 1839.5 and 1840 kHz. Using the multi-decoder set for those limits works f

#Q65

Hi Mike, Yes, interesting times. Lots of experimenting to do. Frequencies will eventually sort themselves out, for now, we just need a common watering hole and until we get close to an official releas

#Q65

Hi David You are right this feature is not implemented on the A and B sub-modes which is probably an oversight for a Beta test version. But it does work well on the C, D and E sub-modes that are prima

#WSJTX_config #Q65