6 Commits

Author	SHA1	Message	Date
Bill Somerville	52b2084882	Update WSPRnet.org posts to allow mode to be determined ... The sent/received 'mode' parameter posted to WSPRnet.org has been amended as follows: WSPR-2: "2" FST4W-120: "3" FST4W-300: "5" FST4W-900: "16" FST4W-1800: "30" this change is designed to maintain backwards compatibility with older versions of WSJT-X and other software like WSPR-X which already post these values: WSPR-2: "2" WSPR-15: "15" It is expected that the WSPRnet.org server side will be updated in sync with a WSJT-X v2.3.0 RC2 (or GA) release to account for this change.	2020-10-20 12:43:45 +01:00
Bill Somerville	add63fb374	Adapt WSPRnet.org spotting to moveable Rx analysis window ... This allows spots at any frequency to be posted rather than just those in the 1400 to 1600 Hz range above the VFO dial frequency.	2020-10-04 22:41:52 +01:00
Bill Somerville	5cc48497b8	Remove constraint on WSPRnet.org spots being in WSPR band segments ... This seems harmless and will accommodate FST4W spots where operation is outside of WSPR band segments.	2020-10-01 11:29:25 +01:00
Bill Somerville	7566f3548d	Post FST4W spots to WSPRNet.org ... Includes a re-factoring of the WSPRNet class, particularly to handle direct spot posts as well as via a file from wsprd. Switched from GET http request method to POST method. FST4W spots post the same information a WSPR spots except the drift field is always zero (FST4W has no drift compensation, so no drift figure is calculated by the decoder), and the mode field reflects the T/R period in minutes. This means FST4W-120A will be similar to WSPR-2, an FST4W-900 will be similar to WSPR-15. I don't see any way to view the mode field on either the new or old database format queries on WSPRnet, so it is hard to tell if that field is actually stored.	2020-07-26 02:58:04 +01:00
Bill Somerville	9c22b5c3ed	Qt v5.15 compatibility	2020-06-13 16:04:41 +01:00
sirhc808	1f57ba5fec	improve physical structure	2019-07-02 12:45:05 -05:00