160M "Out of Band"

[K0HB]

This evening, working a station at 1.845 LSB, program would not allow me to log the contact, raising "OUT OF BAND" error.

I had just logged another station at 1.826 CW with no problem.

Tuning the radio, it appears the program understands 160M band to end at 1.840.

Where can I set the band limits?

[K0HB]

Additional to the above.

Tuning further up band, at 1.850 the "OUT OF BAND" error is withdrawn.

It seems Log4OM does not wish me to operate the 10kHz from 1.840 to 1.850?

[G4POP]

Additional to the above.

Tuning further up band, at 1.850 the "OUT OF BAND" error is withdrawn.

It seems Log4OM does not wish me to operate the 10kHz from 1.840 to 1.850?

Having checked the ITU regional bandplans here

http://www.iaru-r2.org/documents/explor ... 202013.pdf

It would appear that you were out of band for the mode that you were using

However you can edit the bandplans yourself, just locate the region 2 bandplan which is in the c:\........\roaming\logom folder

[K0HB]

Additional to the above.

Tuning further up band, at 1.850 the "OUT OF BAND" error is withdrawn.

It seems Log4OM does not wish me to operate the 10kHz from 1.840 to 1.850?

Having checked the ITU regional bandplans here

http://www.iaru-r2.org/documents/explor ... 202013.pdf

It would appear that you were out of band for the mode that you were using

However you can edit the bandplans yourself, just locate the region 2 bandplan which is in the c:\........\roaming\logom folder

I will check there and edit.

For what it is worth, US regulations allow SSB in that band segment. The IARU bandplan does also.

Having said that, IARU has no regulatory authority and Log4OM should not attempt to regulate what I can put in my log. Had I not noticed, this perfectly legal QSO would not have been recorded.

It is useful to raise the "OUT OF BAND" alert, but it is unacceptable that the program will not record the QSO.

[K0HB]

Further to the above, I have located the bandplan document you referred me to at bandplan_r2.xml

Since I am not competent in markup language, it is foolish for me to go mucking about in that file.

Meanwhile nobody in Region II may work SSB 1840-1850.

[G4POP]

Tomorrow I will modify the r2 bandplan and post it here for you

[K0HB]

Tomorrow I will modify the r2 bandplan and post it here for you

Thanks!

As a more user friendly solution, perhaps a future addition would be for a user-modifiable (txt?) file or user-entry grid in the program. Here is an example from another logging program. This would give each user the option to construct a personal bandplan appropriate to their national regulations and license class.

[G4POP]

This would give each user the option to construct a personal bandplan appropriate to their national regulations and license class.

It would also give users the opportunity to completely screw up their band plan and operate illegally plus the chance of transmitting in areas that could disrupt emergency services and military opps.

It's safer and far easier doing it the way we do now and just modifying the band plan as required the few users that have issues with it.

Revised band plan follows shortly

[G4POP]

Tomorrow I will modify the r2 bandplan and post it here for you

Zipped revised band plan, without the gap, here for you to use

Please note that you can modify this file easily using "Notepad"

[IW3HMH]

It is useful to raise the "OUT OF BAND" alert, but it is unacceptable that the program will not record the QSO.

The only thing you should do, in that case, is to manually set the band. Then Log4OM will save your QSO.
if bandplan has a gap in that frequency area (can be an error, happens) Log4OM is not able to identify band because the reported frequency is not "recognized".
Setting band manually will allow you to log everything, everywhere, even out of band.

xml structure is also very simple to understand, but terry provided you a revised file to fix that issue.
place it in your configuration folder. HELP MENU -> OPEN CONFIGURATION FOLDER

There are a lot of "unacceptable" bugs in any software (it's normal).
Rarely they have a patch in one day. Please remember we are all, freely, working for amateurs in our spare time (all spare time)