Hello Joe and all, . Most of questions raised on this subject can be solved via HLR/VLR database server usage, where visitor location register can match to the specific HF band where callsign, frequency, hash of the message being transmitted, protocol and code rate can be stored, callsign hash can be calculated from callsign in the VLR server. . Hash conflict of two or more callsigns on the same band can be solved as well via VLR connection using frequency window and other possible criteria. . Users who have not Internet connection can still operate FT8 via default coder/decoder with limited sensitivity to the current FT8 decoder value, while users who have connection to the VLR can get maximum performance via variable protocol and code rate. . Current implementation of the FT8 special messages(i3bit==1) does not allow to decode callsign from the hash if this callsign was not decoded in the previous message. Special messages are being used in MSHV software as effective way to increase QSO rate in the common FT8 bands, with extended FT8+ protocol the gap in software compatibility may increase and VLR server connection would let us to resolve such issues. . The best way to go forward is a sharing FT8+ flexibility to the Internet connection and limiting radio interface traffic to callsign and report transmission, the same QSO radio exchange protocol have been in use for a while in DXpeditions and contests where in CW callsign 'hash' can be recognized by human brain from multiple signals per frequency, speed and timing criteria. . 73 Igor UA3DJY
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
