We declared that a completed QSO had a 599 signal report... Since the 59 or 599 is given automatically by most contest logging programs, this is not a real deciding element of the exchange. With the successful exchange of the location data either there or absent, this is actually a better signal report than the usual "you are 59, repeat the exchange agn agn, slowly with phonetics..." exchange. The location exchange would be set before the contest or when a rover changed locations so there is no need to look it up during the contest. 14A NV is my location in Pershing county, 14B is Elko/Humboldt/Lander counties junction... It is really no different than having to look up the county abbreviations as they may be different in different states--Lincoln, Oregon is ORLNN and Lincoln, Nevada is NVLIN and in Maine it is LINME.
We run a program that translates the FT8 Cabrillo log into the same format as the Cabrillo log for SSB, CW and the conversational digital modes and appends that log if necessary to the end of that other log. (1500 lines of COBOL that adds the 599. the 5 digit state/county abbreviation, and turns them into multiple contacts if either the sent or received is on a countyline....) This is a workaround that tries to stay in the limitations of the current capabilities of WSJT-X. It will take a huge effort to expand that program to 110 bits. Thanks for your great work on this program. I like the more visible green marker on the waterfall!!!! 73 Jim W6US On Mon, May 25, 2020 at 11:10 AM Joe Taylor <[email protected]> wrote: > Hi Jim, > > Of course it would be trivial to enable display of characters G and H as > "pseudo-classes" in the ARRL Field Day message formats used for MSK144, > FT4, and FT8. But I don't see this as a very desirable message format > for state QSO parties. A few problems, for example: > > - Operators would need a look-up table to determine their appropriate > "number of transmitters" and operating class. > > - Displayed message information would mean something very different > from what it appears to mean. > > - Messages would contain no signal report -- presently a required part > of the NV QSO Party exchange. > > SSeems to me that a good solution for the wide variety of exchanges in > state QSO parties really needs a message payload more like 110 bits, > rather than 77. > > -- 73, Joe, K1JT > > On 5/25/2020 1:20 PM, Jim Shepherd wrote: > > Hi, > > There are 8 characters available for the Field Day contest overlay > > to designate class of operation. Currently A-F are used, and if G and H > > are activated it will allow for 256 combinations of the transmitter > > number (1-32) and the letters. Right now only 192 combinations are > > available. Why this matters is that this overlay can be used for state > > QSO parties to add county and county line designations for the FT8/FT4 > > contacts. Here in Nevada we have 17 counties and 54 county line > > locations, and the system works fine for us. Maryland is using 25 > > counties this year. Texas has 254 counties, so while county line > > operations would require a couple of thousand designations, they would > > just have to settle with the single counties only. It would also allow > > the ARRL to add two new classes to Field Day to handle VPN linked > > locations in the new normal of social distancing in the future. > > > > Thanks for considering this. > > > > 73 > > > > Jim Shepherd W6US > > NVQSO Party Chairman > > > > > > _______________________________________________ > > wsjt-devel mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
