Skip to content

Use XIT to offset the transmit frequency without changing RX

XIT (Transmit Incremental Tuning) lets you shift your transmit frequency by a fixed number of hertz while your receive frequency stays on the VFO. This is useful when working split, compensating for a TX offset requested by the other station, or matching a net frequency without retuning the panadapter.

Before you start

  • AetherSDR must be connected to the radio. XIT controls are only active when a radio connection is present.
  • Open the RX Controls applet. If it is not visible, click the RX tray button on the right sidebar.
  • Select the slice you want to adjust using the slice tabs (A..H) at the top of the applet.

Steps

  1. In the RX Controls applet, scroll down to the RIT/XIT section.
  2. Click XIT to enable Transmit Incremental Tuning. The button lights when active.
  3. Adjust the XIT offset using one of these methods:
  4. Click the < or > buttons flanking the XIT offset spinbox to step in 10 Hz increments.
  5. Hover over the XIT offset spinbox and scroll the mouse wheel to step in 10 Hz increments.
  6. To return the TX offset to zero without disabling XIT, click XIT 0.
  7. To turn XIT off, click XIT again so the button is no longer lit.

What each control does

Control What it does Default
XIT Toggles Transmit Incremental Tuning on or off. Off
XIT offset Sets the TX frequency offset in hertz. Adjusted with the < / > buttons or mouse wheel. +0 Hz
XIT 0 Resets the XIT offset to +0 Hz without turning XIT off.
## Tips
  • RIT and XIT are independent. You can run both simultaneously: RIT shifts your receive frequency, XIT shifts your transmit frequency, and the VFO readout stays unchanged.
  • If you need the TX offset to persist across a session, set the XIT offset before transmitting; it remains set until you click XIT 0 or disable XIT.
  • To zero the offset quickly before a transmission, click XIT 0 rather than toggling XIT off and back on.

Troubleshooting

  • XIT controls are greyed out — The radio is not connected. Use Settings > Connect to Radio... to establish a connection, then try again.
  • TX frequency is not shifting as expected — Confirm the correct slice is selected using the slice tabs (A..H). XIT acts only on the currently bound slice.

Slice tab and badge colors (v0.9.3)

Starting in v0.9.3, the slice tab buttons (A..H) and the slice badge in the top-left of the applet are colored by the SliceColorManager. Each slice has its own color that persists across sessions. The same color is reflected in the VFO widgets and meter strips for that slice. Colors are not configurable from within the RX Controls applet itself; they are managed centrally by SliceColorManager and apply consistently across all widgets that reference a given slice.

Slice tab behavior on reconnect (v0.9.5.1)

In v0.9.5.1, the slice tab row is rebuilt correctly when the number of available slices changes, such as after a disconnect and reconnect or after the radio reports a different slice count.

Previously, the tab buttons were created only once and never replaced. Now, if the radio reports a different maximum slice count from the one already displayed, the existing buttons are torn down first — removing them from the layout and restoring the static slice badge — before the new set is built. This prevents stale tab buttons from appearing after reconnection.

The click handler that emits sliceActivationRequested is connected only once per applet instance, regardless of how many times the tab row is rebuilt. This prevents duplicate signal handlers from accumulating across reconnects.

No action is required from you. The tab row updates automatically when the radio connection changes.

Filter preset storage format (v0.9.5.1)

In v0.9.5.1, filter presets saved by the FilterPresets setting can store either a plain bandwidth width value or an explicit low-edge/high-edge pair. This matches the format used by the VFO widget.

  • Width-only format — a single integer in hertz, for example 2700. The applet centers the passband symmetrically around the carrier using the mode's default edges.
  • Lo:Hi format — two integers separated by a colon, for example 300:3000. The applet sets the filter low edge to 300 Hz and the high edge to 3000 Hz exactly. The displayed width label shows the computed difference (2700 Hz in this example).

Both formats can appear in the same comma-separated FilterPresets value for a given mode. Entries that are malformed, have a high edge equal to or below the low edge, or are zero or negative are silently skipped.

This change affects how custom filter presets are saved and loaded but does not change how you interact with the filter preset buttons. Right-click a preset button to save the current passband to that slot; click it to apply the preset. The lo:hi format is written automatically when you save a preset whose low edge differs from the mode default.

NT mode behavior

The NT mode is treated as a digital mode by the RX Controls applet. Specifically:

  • NT follows the same filter width presets and step sizes as DIGU and DIGL.
  • The filter width label calculates bandwidth the same way as DIGU (using the high-edge value).
  • The SQL button and squelch level slider are disabled when NT is active, because audio is routed via DAX and squelch is not meaningful. If squelch was on when you switched to NT, it is turned off automatically and the previous state is saved for restoration when you leave NT mode.
⚡ Athena AetherSDR Assistant
Hi! I'm Athena, the AetherSDR AI assistant. Ask me anything about installation, configuration, or troubleshooting.