Hi Lance,
On 10/1/2021 10:47 AM, Lance Collister, W7GJ via wsjt-devel wrote:
On 10/1/2021 14:38:24, Lance Collister, W7GJ wrote:
Hi guys! TNX for the new version! I ran Q65-60A for 8 hours Thursday
on 6m EME to test out my DXpedition setup. I am going to try to use
Q65-60A for both my 6m EME DXpeditions in October.
Good decision. Q65-60A is clearly the best digital mode for EME on 6
and 2 meters.
I was able to install 2.5.0 fine, but it did crash once because it
couldn't find a file called red.dat (I think) in
AppData\Local\Temp\WSJT-X\. I made the folder and the file and then
was able to restart the program, but the folder and file were gone
after I shut down the program....so I don't know if this is going to
be a problem next time or not.
There's no need for you to create this directory. It's done
automatically by WSJT-X, and deleted when the program terminates.
I am not sure I understand how the red Q65 Sync line works. Sometimes
it is there and other times when I hit the Decode button I don't get
the red sync line. I don't know if this is some kind of bug or I just
don't understand how to make it visible after every decode.
Where have you been since June? The time to learn such things was 4
months ago, when the first candidate releases of WSJT-X 2.5.0 were made.
The orange sync curve refers to the most recent received sequence. The
red curve refers to the average. If fewer than 2 sequences are
available in to be averaged, there is no red curve.
I also think it would really be helpful if people could easily choose
different TX offsets in Q65-##A and have their transmitter frequency
automatically adjust, just as it does in FT8. I tried to explain the
problem and what callers need to do to spread out, but it is still
more complicated than they are used to, and many of them assume that
Q65 works just like FT8:
http://www.bigskyspaces.com/w7gj/Q65%20Offset%20Guide.pdf
It would really be great if you could make Q65-A behave like FT8!
The best time to make such a suggestion was more like 10 months ago --
back when you were first testing Q65 for 6m EME.
Things are the way they are because many of the Q65 submodes have large
bandwidths -- up to more than 30 times the FT8 bandwidth. In these
cases it's impossible to keep the Q65 Tx frequency in the range 1500 -
2000 Hz.
I also would like to again request that the DEEP DECODE option in Q65
initiate a search in
CALL3.TXT similar to what is done in JT65 with the Deep Search. Even
if the callsigns and messages that are found are not used by the AUTO
SEQ in a QSO, it would really help to know where and with whom to try
to start a contact! Some identifier after the decoded message could
indicate it was a DS and is there for suggested information only.
Maybe it could also be a different color so people don't confuse it
with other callers. Thanks for your kind consideration!
Q65 does not use a callsign database. Everything required to complete a
QSO is already known (such as your own callsign) or copied over the air.
Nevertheless, Q65 has better performance than JT65 with Deep Search
engaged.
-- 73, Joe, K1JT
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
