We had a discussion about some updates to the parsing of frequencies when uploading CSV files. This is to warn everyone that the change will be implemented soon. The change will apply to both chasers and activators.
After the change it will not be possible to use wavelengths to specify the frequency used. i.e. entering “40m” or “15m” etc. will cause an error and you will have to edit and resubmit your CSV file.
The parser will accept real frequencies or normalised ones and you can use either MHz (or GHz for everything above 2300MHz)
1.8MHz or 1.823MHz or 1.823 will all be accepted and logged as 1.8MHz
2320MHz or 2.3GHz or 2320.101MHz or 2.320101GHz will be logged as 2.3GHz
Before the pedants (and you know who you are) complain that the heading used for frequency selection defaults to “all bands” so we should change the heading or use wavelength not frequency. Yes, I know. But that’s the way it is and the way it’s staying!
I don’t believe that this will affect either utilities from Alain F6ENO or Stewart G0LGS or Mario DC7CCC.
I’m giving everyone advance notice now. Expect the change in a few days.