During the recent 160m contest, about 20% of the time I noticed that my transceiver mode would change from LSB to USB when I doubled clicked a cluster spot. If I checked the "Mode Lock" box the mode would still change from LSB to USB. I suspect this is due to the logic in "band plan". I would like the "Mode Lock" selection to prevent the mode from being sent from the band plan to the transceiver. Another option would be to add a another "Mode Lock" that would prevent the mode from being sent out.
This may sound nitpicky, however, during a contest, when the bands are crowded, in can take quite a few seconds before one realizes that you can't tune in anything because the mode changed from LSB to USB.
Ray Mikula
W9NZ formerly WA9ZVF
Modify "Mode Lock" to prevent "band plan" from changing transceiver mode
- G4POP
- Log4OM Alpha Team
- Posts: 11592
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Modify "Mode Lock" to prevent "band plan" from changing transceiver mode
Moved topic to user support because you have the wrong impression of what the 'Mode lock' filter does, it actually should filter spots to only show spots for the mode the radio is set to.
e.g. If the radio is set to SSB then only SSB (Phone) spots will be displayed - No CW, FM, RTTY etc
Similarly 'Band lock' filters just spots on the band the radio is set to.
I have just checked and the filters are working correctly!
Now to your issue which could be caused by a couple of things
1. The bandplan selected by you could be the wrong region
2. The band plan could have an error, without knowing what frequency you were using its hard to check
3. It could be radio or CAT related - Without knowing what radio, CAT control (Hamlib or Omnirig), Log4OM version number and what interface your using we cant help you.
Supplying full information about your set up is of prime importance to enable us to help
e.g. If the radio is set to SSB then only SSB (Phone) spots will be displayed - No CW, FM, RTTY etc
Similarly 'Band lock' filters just spots on the band the radio is set to.
I have just checked and the filters are working correctly!
Now to your issue which could be caused by a couple of things
1. The bandplan selected by you could be the wrong region
2. The band plan could have an error, without knowing what frequency you were using its hard to check
3. It could be radio or CAT related - Without knowing what radio, CAT control (Hamlib or Omnirig), Log4OM version number and what interface your using we cant help you.
Supplying full information about your set up is of prime importance to enable us to help
73 Terry G4POP
Re: Modify "Mode Lock" to prevent "band plan" from changing transceiver mode
Terry,
I created some confusion in my posting. When I referred to "Mode Lock", I was referring to the "Mode with the lock symbol next to the mode drop down menu" this is in the upper left quadrant along with callsign, band, mode, country. I was not referring to the "Mode Lock" checkbox. Sorry for the impreciseness on my part.
During the recent 160m contest, about 20% of the time I noticed that my transceiver mode would change from LSB to USB when I doubled clicked a cluster spot. If I checked the "Lock Symbol" in the upper left quadrant, the mode would still change from LSB to USB. I suspect this is due to the logic in "band plan". I would like the "Mode Lock" selection to prevent the mode from being sent from the band plan to the transceiver. Another option would be to add a another "Mode Lock" that would prevent the mode from being sent out.
I did some testing and it is the band plan that is creating the issue and it is not because I have the wrong band plan. Band plans are not absolutes but are more like a gentleman's agreement, a convention or a suggestion. An example of this is the typical operating practice the LSB is used on 160m, 80m and 40m and USB is used on 20m, 15m, 10m. This is not mandated by law. So, my point is that during a contest, especially on 160m, there are many cluster spots that are SSB phone using LSB that get characterized incorrectly by the band plan. It would be nice to have an option to prevent the mode from being sent from the cluster to the rig.
Ray Mikula
W9NZ
I created some confusion in my posting. When I referred to "Mode Lock", I was referring to the "Mode with the lock symbol next to the mode drop down menu" this is in the upper left quadrant along with callsign, band, mode, country. I was not referring to the "Mode Lock" checkbox. Sorry for the impreciseness on my part.
During the recent 160m contest, about 20% of the time I noticed that my transceiver mode would change from LSB to USB when I doubled clicked a cluster spot. If I checked the "Lock Symbol" in the upper left quadrant, the mode would still change from LSB to USB. I suspect this is due to the logic in "band plan". I would like the "Mode Lock" selection to prevent the mode from being sent from the band plan to the transceiver. Another option would be to add a another "Mode Lock" that would prevent the mode from being sent out.
I did some testing and it is the band plan that is creating the issue and it is not because I have the wrong band plan. Band plans are not absolutes but are more like a gentleman's agreement, a convention or a suggestion. An example of this is the typical operating practice the LSB is used on 160m, 80m and 40m and USB is used on 20m, 15m, 10m. This is not mandated by law. So, my point is that during a contest, especially on 160m, there are many cluster spots that are SSB phone using LSB that get characterized incorrectly by the band plan. It would be nice to have an option to prevent the mode from being sent from the cluster to the rig.
Ray Mikula
W9NZ
- G4POP
- Log4OM Alpha Team
- Posts: 11592
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: Modify "Mode Lock" to prevent "band plan" from changing transceiver mode
Why not just edit the bandplan and save it as a user bandplan as explained elsewhere on these forums by adding the underscore 'User' suffix (_user)
e.g.
bandplan_r2_user.XML
or
bandplan_dxcc291_user.XML
e.g.
bandplan_r2_user.XML
or
bandplan_dxcc291_user.XML
73 Terry G4POP