There may well be reasons that you prefer TX Offset which I don't appreciate (like memory size), but it really should be a RX offset.? Here's a final example.? Say that WB4SON has been spotted on the DX Cluster or Reverse Beacon Network on 7.039.0 KHz.? He is using any commercial radio.? Therefore his TX frequency, as reported by the cluster is going to be 7.039.0 KHz. ?
With no RX offset in the BITX40, if you tuned to 7.039.0 KHz you would hear absolutely nothing, because you would be zero-beat with WB4SON's carrier.? Suppose you like a 1200 Hz CW Tone (eeak).? To find WB4SON on the BITX40 you would actually need to tune to 7.037.8 KHz.? You would hear the code with a 1200 Hz tone.
With a RX offset you would actually see 7.039.0 on the screen and hear a 1200 HZ Tone.? The actual frequency is 7.039.0.? You can find a spotted frequency, and everyone's dial agrees.
Anyway, like I said, you probably have a good reason for sticking to TX offset, but that's not the usual way it is done.
On Wed, May 31, 2017 at 6:50 PM, Allard PE1NWL <pe1nwl@...> wrote:
Yes your observations are correct Bob,
and I agree that it's important that the correct frequency is displayed
during TX.
I have already corrected this in the next version v1.14 which will be
released soon.
The display will show the correct frequency both in RX as well as in TX.
However it will still use TX offset, not RX offset (perhaps XIT would be a
better name).