Hi Peter, Ed, and all,

Best WSJT-X operating practices are not necessarily the same for all modes. Q65 is the youngest mode in the program: since October 2020 it has been developed and optimized with special attention to its use for propagation modes mentioned in its Quick-Start Guide such as tropospheric scatter, rain scatter, ionospheric scatter, TEP, and EME.
These optimizations require example *.wav files recorded by WSJT-X.

So far we have no such files for the December-January openings between the Americas and VK/ZL on 6 meters. Please help us in this regard! It's a big help to us if you always operate with "Save all" checked on the save menu -- at the very least, do this when operating in unusually interesting propagation conditions. Then, remember to send us a few examples of interesting files. You can always invoke "File | Delete all *.wav & *.c2 files in SaveDir" to clean out unwanted files.

On specifics of best operating practices for Q65 modes: many recommended settings are explicitly mentioned in the Quick-Start Guide to Q65 or shown in the screen shot there. It is no longer necessary to set

I generally use FTol = 100, or even less, and set the Rx Freq on the sync tone of the station I'm trying to work. If "Single decode" is unchecked on the "Settings | General" tab you will normally see decodes of other signals in the passband as well as the one at the selected frequency. If you see a signal that does not decode, you can always double-click on its sync tone to force a decoding attempt there. For EME signals you must always check "Decode after EME delay".

Q65 decoding can take longer than for other modes, so I generally use the Fast setting on the Decode menu. If you have a fast shack computer you might want to experiment with Normal or Deep. However, note that with the Fast setting you get quick decodes of most decodable signals, and when you double-click on a signal the decoder always uses Deep parameters. So then you're covered, both ways.

Peter, your comments about q3 decodes of the signal carrying message "K1JT K9AN R-16" suggest that you haven't yet quite understood the "q#" meanings. With MyCall set to K1JT and DxCall set to K9AN, you'll get q3 decodes because both calls are as specified. With MyCall = K1JT and DxCAll set to something else (or blank), you can gen a q2 decode. With MyCall = something other than K1JT, you can only get a q0 decode. For the example in the Quick Start Guide, you get a q03 average decode after three files are processed.

Please send us some files with good intercontinental DX signals!

        -- 73, Joe, K1JT

On 1/5/2022 6:25 AM, Peter Sumner wrote:
Hello Joe and others.

It would seem I am the creator of my own problems, I have been chatting with Charlie G3WDG and he made mention that he was using a narrow Ftol value and could decode all signals from my shared test WAV file and the multiple signals in the files he created and sent to me.

I have been setting my Ftol to be a large value (1,000Hz) which was covering many of the wanted signals in the passband, something I thought I needed to do, which is a bit of a hangover from using JT65 I guess.

As soon as I set my Ftol down to 20 Hz like Charlie and I now notice you also made mention of 20Hz in your quick start guide, I am able to decode all signals in my sample files and those from Charlie on a complete range of WSJT-X instance I have on the shack PC's and Raspberry PI's I use for WSPR duties.

For those who like to test it for themselves, my test file for Q65-A 30sec period is here: https://vk5pj.com/wsjtx/220103_224100.wav <https://vk5pj.com/wsjtx/220103_224100.wav>
If successful you will see these three decodes:

224100  -7  0.3 1173 :  CQ OC W4TAA EL87  q0
224100 -11  0.2 1520 :  CQ AC4TO EM70      q0
224100 -17  0.2 2510 :  CQ KD5M EM60      q0

I suspect there are many more than I with this wrong setting, so would encourage people to check their Q65 setup.

regards,
Peter, vk5pj


On Wed, Jan 5, 2022 at 2:43 AM Joe Taylor <j...@princeton.edu <mailto:j...@princeton.edu>> wrote:

    Hi Peter,

    I tries WSJT-X 2.5.4 on the Q65 sample Q65 files.   I see all the
    decodes for Q65-60A and Q65-30A that are mentioned in the "Quick-Start
    Guide to Q65," so I have no idea what may be causing you trouble.  If
    you haven't figured it out, you could send me a copy of file WSJT-X.ini
    in your log directory, and I'll look further...

             -- 73, Joe, K1JT

    On 1/4/2022 5:16 AM, Peter Sumner via wsjt-devel wrote:
     > Hi,
     >    at some point the Q65 decoder engine has stopped showing
    decodes from
     > multiple signals in the WSJT-X passband and I am at a loss to
    explain
     > how or when this has occurred.
     >
     > I have downloaded the sample files from the main Pulsar web site and
     > tried to follow the Q65 quick start guide to no avail.
     >
     > At this point none of the Q65-30A sample WAV files produce a
    decode for
     > me, the single sample for Q65-60A seems to have two signals but
    can not
     > get either to decode no matter what combination of Fast, Deep or
    Normal
     > I have tried.
     >
     > While I have successfully had some Q65 contacts to the USA today
    from
     > Australia, it is making me doubt the results of the decoder.
     >
     > Does anyone in the group have some proven Sample WAV files with
    multiple
     > stations in a period I could try? (other than the ones from the
    WSJT-X
     > web site)
     >
     > So far tried WSJT-X version, 2.4, 2.50, 2.51 and 2.54 with the
     > same result.  I know this used to work for me as in June July it was
     > doing multi pass decoding on the openings to the EU and was
    working on
     > EME during the recent W7GJ trip away.
     >
     > I am leaning to this being a problem with a windows update as
    going back
     > and testing with v2.4 should have given me good results but alas no
     >
     > Still scratching my head.
     >
     > Regards,
     > Peter, vk5pj
     >
     >
     > _______________________________________________
     > wsjt-devel mailing list
     > wsjt-devel@lists.sourceforge.net
    <mailto:wsjt-devel@lists.sourceforge.net>
     > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
    <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>



_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to