Logbook and Split Operation

Modified on Tue, Aug 12 at 10:14 PM

This is updated as of the v6.9 release that is finishing beta testing at the time this article is being written (12-Aug 2025).


In the past, there was code in Logbook that tried to determine (a) if the radio has the Split enabled and (b) which VFO the operator was using for transmit. Developers couldn't figure out how to determine this from within Logbook, so they tried to force operators to RX on VFO-A and TX on VFO-B when in Split. But that's not always how we operate. This cause the creation of an option to allow TX on VFO-A. But this was never well executed. 


Distinction - the RX and TX in the Logbook ALE is not intended to show VFO-A and VFO-B respectively. It's meant to show you what frequency you're receiving on and what frequency you're transmitting on. It's a different concept entirely.


During the v6.9 beta testing, we determined that this approach was the wrong approach; a "fool's errand." 


This is because Rig Control already tells us which VFO is being used for RX and TX. It's visually obvious. That is:

  • The large upper frequency displayed is always RX regardless of the condition of Split.
  • The large upper frequency displayed is TX when Split is Off.
  • The small lower frequency displayed is TX when Split is On.


This is determined in Rig Control, rather than Logbook. Once this simple fact became obvious, then the following diagrams depict the resulting logic for Split.


Split is OFF



Split is ON



Functions of DX Cluster


When the operator selects a Spot that requires Split to be enabled, it will change the frequency of the RX and TX VFOs (as the operator has them in Rig Control) and then enable Split.


When the operator selects a Spot that requires Split to be disabled, it will disable Split and change the frequency of the upper VFO.


This change eliminates all of the existing bugs in the software related to Split, regardless of manufacturer or model.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article