swimmingcat For example, when replying to someone's CQ callsign: YU1EA BI1RLR -18 It's already 16 characters long and can be sent normally, and the recipient can also decode it correctly.
BG6QED A data compression protocol was used to reduce the number of bits required for call signs and grid locations, such as using a fast hashing algorithm to map call signs to fixed-length hash values, requiring only the transmission of these hash values.https://do1alx.de/2021/the-pitfalls-of-ft8-grid-locators-and-special-calls/
BG5GNC-NingBo Why can my wsjt normally input very long texts (16 characters), but when sending, I see that the last few characters are truncated?
BI1NIZ Once you've reviewed the relevant WSJT-X literature, you'll know everything... https://wsjt.sourceforge.io/refs.html
Liridice This video is a bit long, but it explains everything clearly: https://www.bilibili.com/video/BV1wm421G7py Each time I observe, I gain new insights (even explaining how I sometimes see signal beginnings and endings with broadened peaks on the spectrum).
Liridice Syryia That's why it's not surprising that JTDX often uses a non-standard call sign hash, and even after the next round, it still can't be guessed.
闽ICP备2021006864号-7
闽公网安备35020602002794号