Hi Dave, the specific actual situation I have encountered involves using WSJT-X for WSPR (not FT8).
Your thoughts? David / K7DB On Sun, Oct 20, 2019, 2:50 PM David Gilbert <xda...@cis-broadband.com> wrote: > > As best I know, you don't need to ID every contact, and I suspect you > wouldn't even if moving around within a bandwidth as narrow as is typical > for FT8. So why not simply use the freeform 13-character TX5 message to > periodically ID? I've played around with it a bit and it will even accept > a few non-alphanumeric symbols like -, ?, and +. It certainly will accept > four character suffixes ... even four characters after a "/". It shouldn't > even matter whether any other amateur station realizes that it was you who > sent it. > > I've seen several FT8 stations with long callsigns using TX5 to > periodically identify their grid when it won't fit within the normal > message exchange. > > What don't I understand? > > 73, > Dave AB7E > > > On 10/20/2019 12:48 PM, David A. Behar wrote: > > Hi friends, I am writing to share an idea... > > WSJT callsign encoding generally accommodates most amateur radio > callsigns, but some callsigns -- e.g., some special-event callsigns, and > callsigns which might use a *four character suffix* as provided at ITU > RR19-7 ยง30 <http://life.itu.int/radioclub/rr/art19.pdf#page=7> -- can't > be accommodated by the coding scheme. There has been plenty of previous > discussion about that, and I think no more is necessary. > > WSPR-X provides for the user's specification of a single callsign; that > callsign is used for encoding into messages, and also for use in optional > CW Morse identification. > > I think it would be nice if a user could optionally specify a free-form CW > identification callsign which is not subject to the restrictions of the > callsign encoding scheme. This would enable stations to comply with > regulatory station identification requirements in cases of callsigns which > are not accommodated by the callsign coding scheme. > > David / K7DB > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
