Hi Paul,
there's only one bit per callsign. The protocol doesn't support both /P
and /R for the same callsign, neither does it support /P for one
callsign and /R for the other. Note only standard callsigns can be
augmented with /P or/R, and then only when used in certain specific
message types, which in turn encode that bit.
Note also that /P and /R suffixes are supported for the message types
that allow a non-standard callsign, there's nothing special about that
usage.
73
Bill
G4WJS.
On 12/06/2020 22:17, Paul Kube wrote:
Question: am I understanding correctly that the standard message
payload devotes two whole bits for callsign suffixes /p and /r? (So it
is theoretically possible to have a call using both?) Since these
suffixes are so rare in practice I wonder if in retrospect you think
this is a perhaps regrettable use of the message payload.
73, Paul K6PO
On Fri, Jun 12, 2020 at 11:52 AM Joe Taylor <j...@princeton.edu
<mailto:j...@princeton.edu>> wrote:
If you're interested in how the FT4 and FT8 modes work, and how
they are
implemented in WSJT-X, you can find all the technical details in a
paper by Steve Franke, K9AN, Bill Somerville, G4WJS, and Joe Taylor,
K1JT, published in the July/August issue of QEX.
A copy has been posted on the WSJT web site here:
https://physics.princeton.edu/pulsar/k1jt/FT4_FT8_QEX.pdf
-- 73, Joe, K1JT
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
