<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Hi Dirk,<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>If you get no other takers, I’m willing to have a go. I don’t think these things change frequently enough to make it worth having it as a dynamic item – probably best updating is obtained by including it in the package. You’ll know better – but I suspect those that don’t update their code moderately regularly perhaps don’t update the subtle features like this either?<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>One point of discussion. You can apply the band plans as the are stated in the IARU documentation – or as they get applied in practice in the busiest contests. For example – on normal days – RTTY on 20m is normally around 14070-14090 region, but in the busiest RTTY contests it extends way up to 14150 (in the All Modes section). But, on 360 days of the year, 14101-14150 is occupied by SSB. So – if we set the limits to where the contest stuff spreads, then in most times – users with the RTTY filter set would get lots of false SSB spots. <o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>For that reason – I think it would probably be best to retain it as it is with ‘normal operation’. Contesters are best not to set a filter on the cluster and use the bandmap functions in their logging software to customise what they want to see.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>73<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Andy, G4PIQ<o:p></o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> Dxspider-support <dxspider-support-bounces@tobit.co.uk> <b>On Behalf Of </b>Dirk Koopman via Dxspider-support<br><b>Sent:</b> 18 April 2024 22:38<br><b>To:</b> Dxspider-Support <dxspider-support@dxcluster.org><br><b>Cc:</b> Dirk Koopman <djk@tobit.co.uk><br><b>Subject:</b> [Dxspider-support] bands.pl<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:13.5pt'>It is becoming clear that the issued version of bands.pl is woefully out of date. I don't have deep knowledge to maintain this and frankly cannot make head nor tail of the reference documentation without giving myself a headache. <br><br>Is there someone out there, that has more knowledge about the subject than I do, that can take this task on? Or has someone done a (much) more up to date version that they might be willing to share? Would it be a good idea to have a plan for keeping it up to date and, if so, distributing it. It seems to me that now we have the 'download' command in mojo, this would be something that could be kept in a central place and simply downloaded in the same way as the badip lists are done. A new version of bands.pl can be loaded, while running, with the 'load/bands' command. <br><br>73 Dirk G1TLH</span><o:p></o:p></p></div></body></html>