Hot answers tagged

8

You can find the code in packjt77.f90. Callsign encoding (for "standard" callsigns that don't require hashing) is in function pack28. A quick summary: Adjust a few strange prefixes that don't follow the usual arrangement of letters and numbers. Swaziland 3DA0* will be encoded as if it was 3D0* instead, and Guinea 3XA1A will be encoded as if it was ...


5

Found on the JTDX groups.io (link won't work without login, unfortunately): sybmol • - this operator loaded his log into LoTW symbol ° - this operator loaded his log into LoTW and this is Hint decode (FT8 AP or matched filter based decoder in JT65 JT9 T10 modes) symbol * - Hint decode (FT8 AP or matched filter based decoder in JT65 JT9 T10 modes) So ...


4

My guess, looking at WSPR reports, is that, on average (median), WSPR beacons are transmitted at power levels maybe in the range of 10 to 30 dB lower than the median of FT8 transmissions. e.g. 20 dBm Raspberry Pi hat vs. 37 dBm QRP SDR, or 30 dBm WSPR appliance vs 50+ dBm desktop transceiver and/or QRO amp, as bracketing examples. So the reported 10 dBm ...


1

Having nothing but my own personal experience as data, I would say, no this is not common. Sometimes people can't click fast enough to respond to a CQ and so their response comes on the "2nd time around", but after that all the responses are usually immediate. Though I wouldn't say that means your idea wouldn't work. QSOs that are right on the edge ...


Only top voted, non community-wiki answers of a minimum length are eligible