v1.581: FT8 extension
Kiwi software version v1.581 has an initial release of the FT8 extension (based on open source library code ft8_lib)
FT8/FT4 spots will be uploaded to pskreporter.info if you have entries in the
Reporter callsign and
Reporter grid square fields on the admin page, extensions tab, FT8 subtab. These fields get their initial values from the similar entries on the WSPR subtab (if any). So uploading to pskreporter.info will occur by default if you currently have WSPR spot uploading to wsprnet.org configured.
If you don't want any uploading to pskreporter.info then make the
Reporter callsign field blank. Consider leaving the
Reporter grid square field set however as this enables calculation of the distance (km) between the Kiwi and the spotted station. FT8 and WSPR spot uploading are completely independent.
Uploads to pskreporter.info only occur every 5 minutes per their API spec. So please be patient. If you have an entry in the
Antenna field on the admin page, public tab, this will be included in the upload.
Performance: Don't expect too much from this decoder. Running on a fast PC (not a Kiwi) ft8_lib only has about 70% decoding efficiency against its test files. This of course will be reduced on the Kiwi due to cpu speed limitations.
*** Help needed with SNR calibration. ft8_lib is known to need better SNR calculation. You can help determine if a linear SNR correction will solve this problem by running the following experiment: Use a VAC to route Kiwi audio to WSJT-X at the same time the Kiwi FT8 is running. Compare the Kiwi FT8 SNR values in the listing to what WSJT-X reports. On the admin FT8 page adjust the SNR correction field until the two SNR values better agree (e.g. start with a negative value like -10). As soon as a change is made in the field it will be reflected in the SNR values of the next time slot. No need to restart the Kiwi or anything. Report your SNR correction values in this thread and let's see if there's any agreement.
Currently, SNR values are not uploaded to pskreporter.info because of this issue (will always show as "0 dB").