Thanks everyone for all the information. It appears that the only way to
implement this feature would be to do a second decode with the inverse
of the timing sequence, the way Joe did with JT65. That sure would be a
great feature for Q65 Pileup!!! TNX and VY 73, Lance
On 19 Aug 2025 22:11, Lance Collister, W7GJ wrote:
Hi Reino,
MNI TNX for the background. No, we need the grid for the contact
exchange. So the message would have to be TX2 PLUS some other
indicator such as a hyphen (-) between the calls and the grid. I was
hoping this could be done instead of the R, but I understand that
apparently there is not enough available bits to send - instead of R
🙁 It is only valuable to know if a trace was copied (yellow spike
received) during the immediately preceding sequence...
VY 73, Lance
On 19 Aug 2025 21:07, Reino Talarmo wrote:
Lance Collister, W7GJ, Tuesday, August 19, 2025 8:25 AM wrote
I thought
that there might be room for this information the way the R
report is inserted in TX3. I wonder if the program could
automatically send a message in place of TX2, but similar to
TX2 except with some other character (perhaps just a dash
instead of a space) to indicate that the station copied a
yellow spike during the receive cycle immediately
preceding their transmit cycle.
Hello Lance and Charlie,
Unfortunately, that message or all standard messages support the 'R'
using a single bit and there is no easy way to add another bit for
that message. On the other hand, the field that conveys the report,
grid or any of 'RRR', 'RR73', '73' and 'space' have available some
unused bit combinations.
If the grid is important for the QSO one possibility is to allocate a
value that is presented to the user as '*' or any text. That new
message could indicate that the station has *not* received the yellow
spike in the immediately preceding slot. Or we could have even more
values:
'BLIND ONLY', 'THREE OR MORE CYCLES AGO', TWO CYCLES AGO' and 'ONE
CYCLE AGO' or something similar. The previous cycle would be
indicated by the use of the grid i.e. normal Tx2.
That method may not be best. if you need the grid value in the list
for any transmission or reception purposes. In the case EME it may
not be so important as it will be there once you want to contact that
station.
Whatever it is a program update, I leave it to the designers.
73, Reino OH3mA
--
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, 3B9GJ, ZD9GJ, H40GJ)
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 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
