On 26/07/2017 17:54, Alex, VE3NEA wrote:
The JT65 Communications Protocol document describes two QSO scenarios, an HF-type scenario that consists of 4 messages, and a VHF-type one, that consists of 6 messages. Currently the FT8 Auto Seq function in WSJT-X supports only the VHF scenario. Since FT8 has become so popular on HF, the HF-style auto sequence should probably be implemented as well. The message sequence would be like this:

1:  VK0EK VE3NEA FN03
2:  VE3NEA VK0EK -20
3:  VK0EK VE3NEA R-15
4:  VE3NEA VK0EK RR CQ

Note the last message that both completes the current QSO and invites other stations to call. This message should be added to the already existing list of special messages (CQ, QRZ and DE). I hope there is still a spare grid square around the North Pole for this new message.

The first three messages in this sequence work the same way as in the 6-message scenario. At stage 4, if the caller (VE3NEA) receives (4), he knows that the QSO is complete. If he receives (2) again, this means that the DX did not copy his report, so he repeats his message (3). If he receives "CQ VK0EK MD66" instead, the caller knows that the DX OP has given up, and the QSO should not be logged. If nothing is received at stage 4, then perhaps (3) should be sent a couple more times before giving up.

Would it be possible to implement this scenario as a user-selected option in Auto Seq in WSJT-X?

73 Alex VE3NEA

Hi Alex,

the "... RR CQ" type message is what many users use "... RR73" for and WSJT-X v1.8.0 will optionally support that, it will also support another abbreviation used for pile up situations or in very brief 6m openings where a reply to a CQ or QRZ message can be a report message rather than sending a grid message. The former should only be used judiciously when the station electing to substitute RR73 for RRR must assess the band conditions and QSO partner signal strength and use it only when message repetitions are unlikely to be needed.

This is already coded in the WSJT-X development branch and awaiting testing before merging to the v1.8 release branch.

73
Bill
G4WJS.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to