Hi Peter,
MNI TNX for your email and suggestions. As I understand your approach, you would
suggest that the different reception states be encoded into the Q65 messages sent by
the caller. I am not sure this is easily done, or that it could be done without
corrupting the received AVERAGE on the DXpedition end. However, it sure would be a
good idea if it could be done without breaking the protocol itself!
One of the nice things about JT65 is that the sync tone is just reversed to indicate
that OOO are being sent. That was nice because it was easily identified by a
character change from * to # in the decoded messages window. It would be SUPER if
something similar could be done with Q65 to indicate that a station was decoding, or
at least copying well enough so that they WOULD decode if I were to direct a response
to their callsign. If this additional information could be conveyed in the Contest
Mode without corrupting the average at the DX station's end, it would be an
incredible aid in boosting contacts!
However, I suspect this would require a change in the program in use at both ends of
the contact. Joe had mentioned to me before that a similar kind of trick as the one
he used with the sync tone in JT65 would not be possible with Q65, so I guess it
would have to come from some other aspect of the message. I am not familiar enough
with the mechanics of the actual Q65 messages to suggest a solution myself - I can
only explain the request and the reason for it. However, I can't help but think the
developers are clever enough to encode this information into the message somehow,
even if it has to take the place of a gridsquare or something.
If we could use NA VHF Contest Mode for VHF EME DXpeditions, and there was a way to
identify stations in the pileup that were copying well enough that a quick contact
with them would be possible if they were called by the DXpedition station, it would
greatly increase the number of stations that could be worked! It would be for Q65 VHF
EME DXpeditions what F/H is for FT8 HF DXpeditions.
VY 73, Lance
On 1/9/2023 20:50:41, Petr Suchomel wrote:
Lance,
Looking at possible solutions and without breaking the protocol itself, imo the
easiest solution would be an enhancement to NA contest mode, where instead of sole
R, I would suggest following:
R - Roger, confirmation
C - calling, not decoding
D - calling, decoding
This could be done in QT part of product?? IMO without touching decoder or format
of message itself.
73,--Petr AG6EE
Get BlueMail for Android <https://bluemail.me>
On Jan 9, 2023, at 12:27 PM, "Lance Collister, W7GJ" <w...@bigskyspaces.com>
wrote:
Hi Tim,
Thanks for your feedback. Yes, I agree it would be ideal if there were a new
"VHF EME
DXpedition Mode" in WSJT-X ;-) But I think many of the problems faced by the
DXpedition station - like trying to decode callers in pileups - could even
be solved
if just the DXpedition station had a version with some special tools in it.
Unfortunately, without some changes in the software, I am not sure how I
will be able
to identify callers who are copying me at a given time ;-( As you know from
our on
the air tests (which I tried to duplicate again here in the shack this
morning),
sending the single tone of the Tune Sync Tone for the last 8 seconds of the
TX minute
doesn't isn't long enough to be visually recognized :-(
Another possibility would be for the caller who is copying me right then to
switch to
CQ, and I could interpret that as a sign that I could call them for a quick
contact.
CQ is pretty easily decoded, I think. However, that still doesn't solve the
issue of
my received average being corrupted because of his changing message :-(
I did experiment with Q65-60A in NA VHF Contest Mode and that did seem to
work well
and significantly shorten the time required to complete a contact, but I am
not sure
what problems there might be if people call me who are not running NA VHF
Contest
Mode. I know with FT8 there have been some glitches when people are trying
to operate
in contest mode and are called by non-contest mode stations.
It will be interesting to see if anything evolves to help VHF DXpeditions
before I go
out again this coming fall...
GL and VY 73, Lance
On 1/9/2023 19:16:04, Tim Blank wrote:
Hi Lance, your document does a good job of describing some of the short
comings of WSJT-X/Q65 for EME dxpeditions. In my opinion we should not
be
creating one-off (hacks) of WSJT-X, this is fraught with problems (both
technical and potentially legal). The right way to do this is by
offering
resources to the WSJT-X development team that would work with the
existing
team to enhance the software (to address the issues you documented) with
their blessings and support. I am not sure how that would be received by
the WSJT-X owners but it would be the route that would give the best
outcome for all users.
_._,_._,_
-------------------------------------------------------------------------------------
Groups.io Links:
You receive all messages sent to this group.
View/Reply Online (#903) <https://groups.io/g/MagicEME/message/903> | Reply To
Group
<mailto:magic...@groups.io?subject=Re:%20Re%3A%20%5BMagicEME%5D%20VHF%20EME%20DXPEDITION%20MODE%20CONSIDERATIONS>
| Reply To Sender
<mailto:p...@petrsuchomel.com?subject=Private:%20Re:%20Re%3A%20%5BMagicEME%5D%20VHF%20EME%20DXPEDITION%20MODE%20CONSIDERATIONS>
| Mute This Topic <https://groups.io/mt/96143041/4876986> | New Topic
<https://groups.io/g/MagicEME/post>
Your Subscription <https://groups.io/g/MagicEME/editsub/4876986> | Contact Group
Owner <mailto:magiceme+ow...@groups.io> | Unsubscribe
<https://groups.io/g/MagicEME/unsub> [w...@bigskyspaces.com]
_._,_._,_
--
Lance Collister, W7GJ(ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR,
5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, S79GJ,
TX7MB, TO7GJ)
P.O. Box 73
Frenchtown, MT 59834-0073
USA
TEL: (406) 626-5728
QTH: DN27ub
URL: http://www.bigskyspaces.com/w7gj
Skype: lanceW7GJ
2m DXCC #11 - 6m DXCC #815 - FFMA #7
Interested in 6m EME? Ask me about subscribing to the new Magic Band EME
email group, or just fill in the request box at the bottom of my web
page (above)!
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
