I usualy do not log the specific Frequency, only the Band. When I do this in PoLo, the ADIF has no frequency field. This dos not work for uploading to other Logbooks. They put for 40m, 7mhz, 20m, 14mhz, 15m 21mhz, …. Is this behavior wanted? If so, it is also very annoying, that when you enter 14mhz manualy, you have to switch the mode from CW to SSB.
I’m afraid PoLo is built mainly around setting the frequency in the QSO panel and having systems derive the band.
There is also a band plan map in PoLo which can be customised for different jurisdictions which maps mode to band segments.
If you log frequency in PoLo it will all be taken care of.
SOTA e.g. can have just the band.
We’ve not had anyone want to just put band in without frequency to my knowledge.
Alan
I have had our VK band map change so it does not assume mode for band segments. Maybe @KI2D can make the band selection process also ignore mode and leave it as you set it.
Are you saying that you would like 7.000 set as frequency when on only 40m band is logged? This sounds like it can be done.
Alan
And I assume this is for operations/logs where you are not spotting yourself. It’s just for generic logging. Correct?
Which Logbook apps have problems loading ADIF files without frequency? The standard clearly suggests “FREQ and/or BAND” as the minimum set of fields.
Ideally, I’d prefer not to include a frequency, as a clear way to indicate that one was not entered. But if this is a problem, and the other apps cannot address it, I certainly can add a way to deal with this in PoLo.
Yes, I want to set the Frequency to 7.000 when logging 40m.
I use POLO for generic logging. In QRZ and eQSL. The QSOs dont match up for confirmation (even though only the Band is required) or even do not show up.
Id would be great if there is such an option to set the frequency, when setting the band, as I am to lazy to log every frequency.