Many DXpeditions operate on alternate FT8 dial frequencies (Fox/Hound), e.g.:
80m: 3567
40m: 7064
30m: 10131
20m: 14090
17m: 18095
15m: 21091
12m: 24911
10m: 28091
It would be useful if these could be added as additional FT8 autorun entries (e.g. FT8-20m-DX) without replacing the standard FT8 frequencies.
This would allow Web-888 receivers feeding PSKReporter to monitor either standard or DXped frequencies depending on activity.
Proposed implementation:
Append new FT8 DXped entries to ft8_cfs[]
Append matching names to ft8_name[]
Do not modify existing indices
This preserves backward compatibility while enabling more flexible autorun configurations.
OR
Make FT8 autorun frequencies configurable in websdr.json
Thank you.
Many DXpeditions operate on alternate FT8 dial frequencies (Fox/Hound), e.g.:
80m: 3567
40m: 7064
30m: 10131
20m: 14090
17m: 18095
15m: 21091
12m: 24911
10m: 28091
It would be useful if these could be added as additional FT8 autorun entries (e.g. FT8-20m-DX) without replacing the standard FT8 frequencies.
This would allow Web-888 receivers feeding PSKReporter to monitor either standard or DXped frequencies depending on activity.
Proposed implementation:
Append new FT8 DXped entries to ft8_cfs[]
Append matching names to ft8_name[]
Do not modify existing indices
This preserves backward compatibility while enabling more flexible autorun configurations.
OR
Make FT8 autorun frequencies configurable in websdr.json
Thank you.