A complete walkthrough about Setting Up SSTV for amateur radio operators working with uBITX, sBITX, and similar QRP transceivers
Before diving into connections and configuration, it’s essential to understand how SSTV signals flow through your station. The process involves converting digital image data into audio tones, transmitting those tones through your SSB transceiver, and reversing the process on the receiving end. The entire system relies on maintaining proper audio levels and frequency stability throughout the chain.

The diagram above illustrates the complete transmission path. Your computer generates audio tones representing pixel data, which then pass through an audio interface responsible for both signal routing and PTT (Push-To-Talk) control. The transceiver modulates these audio signals onto an RF carrier using Upper Sideband (USB) mode, and the resulting signal propagates through your antenna system to distant stations.
The weakest link in your SSTV chain will determine overall performance. A $1000 transceiver paired with a poor audio interface will yield worse results than a budget rig with properly implemented interfacing. Pay attention to every connection point, ensuring clean audio paths and proper grounding throughout.

Equipment Requirements and Preparation
Setting up for SSTV operation requires surprisingly little specialized equipment beyond your basic HF station. The uBITX and sBITX transceivers come equipped with everything necessary for quality SSTV work, including stable VFOs, clean SSB generation, and accessible audio input/output connections. What you add to this foundation will determine the ease of operation and consistency of your results.
uBITX / sBITX Specifics
Both the uBITX and sBITX designs by Farhan provide excellent platforms for SSTV operation. The uBITX, built around the Si5351 clock generator and featuring a dual-conversion superheterodyne receiver, offers stable frequency generation crucial for maintaining proper SSTV tone spacing. The newer sBITX takes this further with integrated Raspberry Pi control, built-in audio interfacing capabilities, and a more refined front-end design that reduces the need for external components.
The sBITX particularly shines for SSTV work because its internal Raspberry Pi provides a built-in sound-card and control interface directly connected to the RF hardware. Unlike the original uBITX, which requires an external computer and audio coupling interface, the sBITX can run SSTV software natively on its internal Linux system without any external PC. This fully integrated design eliminates ground-loop issues and greatly simplifies setup. An external computer can still be connected via network or USB if desired, but it is not required.
Transceiver Preparation Tip: Before connecting any computer equipment, verify your transceiver’s audio output level with headphones during normal SSB reception. Set the volume to a comfortable listening level—this same level typically works well for driving your computer’s audio input. On the sBITX, access the built-in web interface to configure audio routing and enable the USB audio device.
SSTV Audio Interfaces
In a typical computer-controlled SSTV station (e.g., with uBITX), the audio interface performs three essential functions:
- Transmit audio coupling
It feeds SSTV tones from the computer’s sound card into the transceiver’s microphone input at the correct level and impedance. - Receive audio routing
It sends demodulated audio from the transceiver’s speaker or line output back to the computer for decoding. - PTT control
It keys the transmitter at precisely the right times under software control.
These three functions are required for all sound-card digital modes (SSTV, FT8, PSK31, RTTY).
Commercial SSTV / digital interfaces
Commercial devices such as the SignaLink USB, RigBlaster, and DigiRig provide a convenient, ready-to-use solution.
Typical features include:
- Transformer-isolated audio paths (prevents ground loops)
- Adjustable transmit and receive levels
- Reliable PTT keying circuits
- USB connection presenting as a standard sound device
Because they appear as normal audio hardware to the operating system, SSTV software configuration is straightforward.
Homebrew SSTV interfaces
Many operators successfully build their own interfaces with simple components:
- Two small audio isolation transformers
- A few resistors and capacitors for level matching
- An optocoupler or small relay for PTT
A well-built homebrew interface performs just as well as commercial units at very low cost. Any standard FT8 digital interface will also work perfectly for SSTV. That’s because SSTV, FT8, PSK31, RTTY, etc. all use the same basic analog audio + PTT method.
Refer – Building an FT8 Digital Interface – Dive into Digital Modes
For sBITX, the audio interface functions are already integrated inside the radio. The internal Raspberry Pi is directly connected to the RF/audio circuitry:
- Transmit and receive audio are routed internally between the Pi audio codec and the transceiver stages
- PTT is controlled via GPIO lines tied into the radio’s logic
- No external sound card or coupling hardware is needed
This means SSTV (and other digital modes) can run natively on the sBITX without any external computer or interface box.
Software Selection and Configuration
Selecting SSTV software comes down to two main factors: your operating system and how you prefer to operate. Mature applications exist on every major platform, so reliability is rarely an issue. The real differences lie in how well the software integrates with your computer’s audio system and how easily you can manage modes, frequencies, and transmit controls during operation.
Windows: MMSSTV
For Windows operators, MMSSTV by Makoto Mori (JE3HHT) is widely regarded as the reference implementation for SSTV. It has been refined over decades and supports all commonly used SSTV modes. The program provides a clear waterfall display for signal identification, automatic mode detection, and stable decoding even when signals are weak or distorted by propagation.

The interface is dense but highly configurable. With regular use, most operators find that all essential controls—mode selection, slant correction, and transmit parameters—are quickly accessible. MMSSTV also includes built-in image editing tools for adding text, overlays, and callsign templates before transmission.
Download: MMSSTV Official Site
Initial Configuration
After installation, begin setup from the Option menu.
1. Audio Device Selection
-
Choose your sound card or external audio interface for both Input and Output.
-
If your system has multiple audio devices, confirm you’re using the one connected to your radio interface.
-
Set the sample rate to 8000 Hz or 11025 Hz. Higher rates provide no SSTV benefit and only increase CPU load.
2. PTT / Transmit Control
In the PTT/TX Control section, select the keying method appropriate to your interface:
-
Serial control: choose the correct COM port and select RTS or DTRaccording to your wiring.
-
CAT / Hamlib control: select your radio model and port settings if your transceiver supports CAT keying.
-
GPIO control (sBITX): when using an sBITX, PTT can be handled through the Raspberry Pi GPIO via Hamlib rather than a serial interface.
With audio and PTT configured, MMSSTV is ready for on-air testing. Tune to an SSTV frequency (such as 14.230 MHz USB), verify waterfall activity, and confirm that received images decode cleanly before attempting transmission.
Linux Platform: QSSTV
Linux operators have QSSTV, a powerful open-source application that rivals MMSSTV in capability while integrating perfectly with the Linux audio system. QSSTV uses either PulseAudio or ALSA for audio routing and supports multiple methods for PTT control including serial ports, parallel ports, and Hamlib-based CAT control. Its modern Qt-based interface provides clarity that newcomers often appreciate, with logical groupings of controls and excellent visual feedback during both transmission and reception.

Install QSSTV on most Linux distributions through your package manager, or download from: QSSTV Homepage

After installation, QSSTV’s configuration wizard guides you through audio setup. Select your audio interface from the ALSA or PulseAudio device list, paying attention to both capture and playback device names. Linux users working with the sBITX benefit from straightforward USB audio device recognition—the Raspberry Pi’s audio interface typically appears as “USB Audio Device” in the selection menu. For PTT, configure serial port control if using a traditional interface, or set up Hamlib for direct rig control. The sBITX responds well to Hamlib commands, allowing QSSTV to toggle PTT through the transceiver’s CAT interface.
macOS Platform: MultiMode
Mac operators can use MultiMode or the cross-platform Black Cat Systems suite. These applications provide familiar macOS interfaces while delivering full SSTV functionality. MultiMode particularly integrates well with macOS audio routing and can work with both built-in sound cards and external audio interfaces through Core Audio.
Download MultiMode from: Black Cat Systems
Don’t feel compelled to master every feature immediately. Start with basic image transmission and reception, using default settings for image size and transmission speed. Once comfortable with the fundamental workflow, explore advanced features like image templates, automatic logging, and waterfall-based signal monitoring.
Making Physical Connections
Proper physical connections between your computer, audio interface, and transceiver form the foundation of reliable SSTV operation. Poor connections cause numerous problems: excessive noise, weak signals, distorted images, or complete failure to receive. Taking time to implement clean, properly shielded connections pays dividends through countless trouble-free QSOs.
Audio Path Connections
Start with the receive audio path, connecting your transceiver’s speaker or line output to the audio interface’s input. The uBITX typically provides a 3.5mm speaker jack on the front panel, while the sBITX offers line-level output through its rear panel connectors. Use shielded cable for this connection—even short runs benefit from shielding that prevents RF pickup and reduces hum. Set your transceiver’s audio output to a moderate level; you’ll fine-tune this later, but starting conservatively prevents overdriving the computer’s input stage.
For the transmit path, connect your audio interface output to the transceiver’s microphone input. Most homebrew transceivers use a standard 3.5mm or 6.35mm jack for the microphone, expecting audio levels in the range of a few hundred millivolts. Commercial interfaces like the SignaLink include adjustable potentiometers to set proper drive levels. If building your own interface, include a voltage divider network to reduce the computer’s line-level output (typically 1-2 volts) to microphone level. Excessive drive causes distortion, splatter, and garbled images, while insufficient drive results in weak signals that don’t propagate well.

PTT Control Implementation for SSTV
Push-to-talk (PTT) control is the most variable part of an SSTV station. The objective is straightforward: your computer must key the transmitter exactly when transmission starts and release it when the image finishes. Several proven methods can achieve this, each suited to different hardware setups.
1. Serial Port (RTS/DTR) Keying
Serial control remains the simplest and most direct approach when a hardware serial port is available. The SSTV software toggles the RTS or DTR line, which your interface converts to a PTT signal for the radio.
Best for: Dedicated shack PCs or USB-to-serial adapters
Tip: On Linux, confirm device permissions (e.g.,/dev/ttyUSB0) so the SSTV software can access the port.
Modern USB-to-serial adapters work reliably once drivers are installed and the correct COM/tty device is selected in software.
2. VOX (Audio-Triggered) Keying
VOX provides a no-control-wire solution. The radio automatically keys whenever SSTV audio appears at the microphone input. Both uBITX and sBITX firmware include adjustable VOX.
Setup: Enable VOX → raise mic audio → lower threshold until reliable keying
Adjust:Hold time long enough to bridge brief SSTV pauses
Watch: Avoid triggering from room noise or receiver audio leakage
VOX works surprisingly well for SSTV, though some operators prefer explicit control over transmit timing.
3. sBITX GPIO / Hamlib Control
With the sBITX, the internal Raspberry Pi can assert PTT directly via GPIO under software control. When SSTV software connects through Hamlib using the sBITX rig profile, PTT is handled automatically.
Advantage: No external interface or serial adapter required
Result: Low-latency, fully synchronized keying
Configure:Select Hamlib rig = sBITX → set local host/port as defined in firmware
This is the cleanest integration method when running SSTV locally on the sBITX or over its network link.
PTT Timing Adjustment
Most SSTV programs provide PTT lead time—the delay between asserting PTT and starting audio. This compensates for relay closure and transmitter stabilization.
Recommended: 100–200 ms for most HF transceivers
Too short: First image lines clipped
Too long:Only wastes a small amount of airtime
Always verify by transmitting a test pattern and confirming the top of the received image is intact.
Configuration and Testing Procedure
With all connections made, systematic testing ensures every component works correctly before attempting your first on-air transmission. This methodical approach identifies problems early, when they’re easier to diagnose and fix. Begin with passive monitoring to verify the receive path, then proceed to transmit testing using dummy loads before finally attempting live QSOs.
SSTV Audio Level Setup and On-Air Testing
Correct audio levels are essential for clean SSTV decoding and transmission. The goal is to deliver strong, undistorted audio between your transceiver and computer so the software can accurately interpret and generate SSTV tones.
1.Tune and Identify an SSTV Signal
Begin by tuning your transceiver to a known SSTV frequency.
Primary HF SSTV frequency: 14.230 MHz USB (20 m band)
Mode:Upper Sideband (USB) — SSTV universally uses USB
Activity:Most common during daylight and weekends
With your computer volume at a moderate setting, listen through the radio speaker. SSTV sounds like a sequence of rising and falling chirps.
What to look for in software: Bright traces in the waterfall between ~1500–2300 Hz
Meaning: Your receive audio path is working correctly
2. Adjust Receive Audio Level
Use the transceiver’s AF (volume) control to set the proper audio level into your interface and computer.
Target: Waterfall signal strong but not saturated
Meter level:~70–80 % of maximum input
Too low: Weak, noisy or incomplete images
Too high: Clipped audio → distorted or scrambled pictures
If your SSTV software shows flat-topped waveforms or overload indicators, reduce the radio volume.
3. Prepare for Transmit Level Adjustment
Transmit testing should not radiate unintended signals.
Preferred: Connect a dummy load
Alternative: Set RF power to minimum
Goal:Safely observe transmitter behavior during SSTV tones
Most interfaces provide a transmit audio level control (potentiometer or trim adjustment).
4. Set Transmit Audio Drive
Start with the interface transmit control at mid-range. In SSTV software, select a test image and begin transmission into the dummy load.
Watch the transceiver’s ALC (Automatic Level Control) meter if available.
Ideal ALC: Light movement, ~20–30 % of scale
No ALC:Audio drive too low
Heavy ALC:Overdrive → distortion and splatter
Adjust the interface transmit level until ALC just begins to respond on peaks of the SSTV tones.
5. Final Check
Receive: Strong waterfall, no clipping
Transmit: Slight ALC action, clean RF output
Result:Proper SSTV image quality on air
Once levels are set, they rarely need readjustment unless you change radios, interfaces, or audio devices.
Frequency Calibration
SSTV relies on precise frequency relationships between the transmitted tones encoding image data. While modern synthesized transceivers like the uBITX and sBITX offer excellent frequency stability, slight calibration errors can affect image quality. Most SSTV software includes tools for calibrating your sound card and transceiver combination to ensure accurate frequency generation and detection.

In MMSSTV, access the Option menu & Setup MMSSTV(o) and locate “Calibration.” The software generates test tones and measures actual frequencies, calculating any deviation from ideal. Similarly, QSSTV includes calibration routines in its configuration dialogs. Run these calibrations with your transceiver connected and operating normally. The software typically reports calibration factors as small percentages—values within plus or minus 100 PPM indicate excellent accuracy, while larger deviations may require attention to your transceiver’s reference oscillator.
Before transmitting on the air, spend time receiving images from other stations. This passive monitoring accomplishes several goals: verifying your receive audio path works correctly, familiarizing yourself with different SSTV modes and their sounds, and building confidence in the software before others judge your transmitted images. Many operators successfully decode dozens of images before transmitting their first one.
Operational Testing Sequence
When ready for live testing, choose a low-traffic time and announce your intentions clearly. Call “CQ SSTV, this is [your callsign], testing” on voice, then transmit a simple test image. Start with one of the faster SSTV modes like Martin M1 or Scottie S1, which complete transmission in roughly 90 seconds rather than the three minutes required by higher-resolution modes. This shorter transmission time reduces spectrum congestion during testing and provides faster feedback on whether your configuration works.
14.230 MHz USB is the worldwide SSTV calling frequency.
Most HF SSTV activity gathers around this frequency, especially on weekends and during events.
After transmitting your test image, listen for responses. Station 14.230 MHz USB serves as the primary calling frequency, but actual image exchanges often occur on nearby clear frequencies. If another operator responds to your test, they may critique your signal quality or suggest adjustments. Take this feedback seriously—experienced SSTV operators can often identify specific problems like insufficient audio drive, excessive deviation, or frequency drift from the sound and appearance of your signal.
Operating Practices and Optimization
Successful SSTV operation extends beyond simply making connections and launching software. Understanding mode selection, propagation characteristics, and proper operating procedures helps you make reliable contacts and transmit images that other stations can decode successfully. The SSTV community has developed conventions and etiquette that smooth operations and maximize enjoyment for everyone involved.
Mode Selection Strategy
SSTV modes represent trade-offs between image quality, transmission time, and robustness under poor propagation. The original Robot modes from the 1980s offer excellent performance under marginal conditions due to their narrow bandwidth and redundant sync signals. Martin modes provide good color reproduction and reasonable transmission times, making them popular for routine QSOs. Scottie modes excel under good propagation conditions, delivering high-quality images quickly. More exotic modes like PD (Pasokon Digital) and newer formats like MP73 and MP115 provide specific advantages but see less common use.
Start with Martin M1 (114 seconds) or Scottie S1(110 seconds) for general operation. These modes balance quality and speed while remaining widely recognized and supported. As you gain experience, experiment with different modes based on band conditions. During DX openings with strong signals, try higher-resolution modes like Martin M2 or Scottie S2. When chasing weak DX or operating under poor propagation, fall back to Robot 36 Color (roughly 36 seconds) for its superior performance under difficult conditions.
Image Preparation and Content
The images you transmit represent you to the amateur radio community. Most SSTV software includes templates overlaying your callsign, name, and location on images, helping other operators identify your station and encouraging callbacks. Prepare several images in advance showing your station, antennas, operating position, or local scenery. Many operators maintain libraries of seasonal images, rotating through different pictures to keep transmissions interesting.
Pay attention to image composition and contrast. High-contrast images with distinct subjects transmit more successfully than low-contrast photos where details blend together. Remember that SSTV operates at relatively low resolution—the Martin M1 mode transmits 320×240 pixels, similar to early digital cameras. Images requiring fine detail to appreciate suffer in transmission, while bold, simple compositions shine. Consider adding text overlays with larger fonts, ensuring readability even if some image corruption occurs during transmission.
Remember that SSTV transmissions are completely public and often monitored by operators worldwide. Keep image content appropriate for all audiences and respectful of amateur radio’s reputation. Most operators enjoy seeing station equipment, antennas, family photos, pets, and scenic locations. Creative seasonal greetings and themed images also prove popular during holidays and special events.
Troubleshooting Common Issues
Even carefully assembled SSTV stations occasionally develop problems. Most issues trace back to a handful of common causes relating to audio levels, grounding, or software configuration. Systematic troubleshooting usually identifies problems quickly, allowing rapid resolution and return to operations.
1.Poor Reception or Decode Failures
If SSTV images come through garbled or full of noise—even though the signal sounds strong in the speaker—the culprit is almost always audio level. Take a quick look at your software’s input meter. You want healthy movement without hitting the top. Too little level and the image turns weak and speckled; too much and the decoder chokes, often producing vertical streaks or total failure even on loud signals. A small tweak of the radio’s volume control usually clears this up.
Another thing that trips people up is frequency drift. When you see a steady diagonal slant or colors that slowly shift across the picture, the radio isn’t quite staying put on frequency. The uBITX is normally very stable thanks to its Si5351 clock, but it can wander if the supply voltage is noisy or parts get warm. It’s worth checking that the power source is clean and regulated.
On the sBITX, there’s an extra variable: the Raspberry Pi. If it gets hot and starts throttling, timing can slip just enough to affect decode. Make sure cooling is adequate and that no throttle warnings appear while you’re receiving.
2. Weak or Distorted Transmitted Signals
When other operators say your SSTV looks faint or washed out, yet your power meter shows full RF output, that usually means the transmitter isn’t being driven hard enough with audio. In plain terms, the carrier is there but the picture modulation is shallow. Bring up the audio level feeding the mic input and watch the ALC meter if your rig has one. A little movement is what you want—it shows the audio is reaching proper modulation depth.
The opposite problem is just as common. Reports of wide signals, splatter, or smeared images point to overdrive. Back the audio down until ALC only just flickers, then ease off a touch more. SSTV really rewards restraint here; clean tones matter more than brute level.
If transmitted images look flattened or compressed, there’s distortion somewhere in the audio chain. It might be the computer sound output clipping, the interface stage saturating, or the transmitter itself being pushed too far. The easiest way to track it down is step-by-step: lower everything, then raise levels gradually while monitoring on a second receiver or a nearby WebSDR.
PTT Problems and Timing Issues
When the radio refuses to switch into transmit during SSTV, start with the obvious: PTT. It sounds simple, but most hiccups come down to wiring or control settings. If you’re using VOX, try talking into the mic. If the rig keys for your voice but stays silent for SSTV tones, the threshold is just set too low—bump the sensitivity up a bit. SSTV audio is steadier than speech, so VOX sometimes needs a nudge to notice it.
With serial-controlled PTT, things get a little more technical. Double-check that your software is pointing to the right port and actually has permission to use it (Linux users get caught by this a lot). Also make sure you’ve picked the correct line—RTS vs DTR. Most programs let you toggle PTT manually in the setup screen; that’s the quickest sanity check. Click it and watch the rig’s TX light. If nothing happens, the problem is still on the control side, not SSTV itself.
Quick check: Toggle PTT in software and watch the rig’s TX indicator.
VOX tip: If voice keys the rig but SSTV doesn’t, raise VOX sensitivity.
Serial tip: Confirm port, permissions, and RTS/DTR selection.
Clipped SSTV images—the kind where the top looks chopped off—usually mean the transmitter didn’t key soon enough before audio started. That’s what the PTT lead-time setting is for. Add a little delay, maybe 50–100 ms at a time, until the whole image shows up cleanly on the other end. There’s no prize for extra delay, though; too much just keeps the frequency occupied longer than needed. Aim for the shortest delay that still captures the full image.
Symptom: Top of image missing
Cause: PTT lead time too short
Fix: Increase delay in small steps until clean start
Then there’s the classic ground-loop hum. If you see faint horizontal bars drifting through received pictures, or hear a low buzz under the SSTV tones, grounding is the first suspect. Try powering the computer from a different outlet, or better yet, make sure all the gear shares a single ground reference. Good shielded audio cables help too. Ferrite chokes can tame stubborn RF or hum pickup, but they’re really a band-aid—the real cure is proper grounding and clean cable routing.
Hum bars in image: Likely ground loop
Try: Common ground point and different AC outlet
Extras: Shielded leads and ferrites can help, but grounding matters most
Advanced Topics and Optimization
Once comfortable with basic SSTV operation, several advanced techniques can improve your results and expand your capabilities. These topics require deeper understanding but offer significant benefits for serious SSTV operators interested in maximizing performance.
Digital Audio Processing
SSTV software these days does a fair bit of signal polishing without making a fuss about it. Filters like pre-emphasis and de-emphasis are there to counter how HF propagation tends to shave off higher audio tones over distance. Normally you just leave them alone—they’re already tuned well enough. But if signals start sounding oddly dull or the image contrast feels off, a small adjustment can sometimes bring things back to life.
Noise reduction is another one of those features that’s easy to overdo. A touch of it can make a scratchy, fading picture look much cleaner. Push it too far and you end up smearing detail or softening edges, which is worse than the original noise. The safest way to get a feel for it is to experiment on saved recordings rather than live signals, where you can compare results without pressure.
HF paths often attenuate higher SSTV tones more than lower ones, which is why mild high-frequency boost (pre-emphasis) improves long-distance readability.
Human eyes tolerate noise better than blur—slightly noisy SSTV images are usually easier to interpret than heavily filtered ones.
Macros and Automated Responses
Once you start using macros in SSTV, you wonder how you ever managed without them. Instead of typing your callsign, name, QTH, and pleasantries over and over, they drop straight into the image with a keystroke. It keeps exchanges consistent and avoids typos, especially when things get busy on frequency.
Many operators also build reusable image templates—essentially pre-designed SSTV cards with blank fields for text. The macro content fills those fields automatically, so every transmission looks neat and intentional rather than thrown together. It takes a little setup time, but the payoff is transmissions that look polished even when you’re working quickly.
SSTV exchanges often function as visual QSL cards, with callsign and location embedded directly in the transmitted image.
DX and Contesting Considerations
SSTV contests and DX chasing feel quite different from relaxed everyday contacts. In contests, pace matters. Faster modes like Robot 36 or Martin M1 keep the exchange moving, and having pre-prepared images with the right info already filled in saves valuable seconds between overs. Knowing the expected exchange format beforehand also prevents awkward pauses while you figure out what to send next.
DX work is almost the opposite mindset. Success comes more from patience and timing than speed. Rare stations tend to attract clusters of callers, and jumping in constantly just adds to the noise. It’s usually better to listen for a bit—notice the rhythm of contacts and the brief quiet moment after one finishes. A single clean call placed right there often gets through when repeated attempts don’t.
SSTV pileups behave much like SSB ones—most callers transmit immediately after a DX station stops, creating a short burst of overlap. A clean, undistorted SSTV signal is easier to decode under pileup conditions than a stronger but overdriven one.
Conclusion and Next Steps
Setting up SSTV operation with modern homebrewed transceivers like the uBITX and sBITX demonstrates the continuing vitality of amateur radio experimentation. These affordable, technically sophisticated rigs prove that high-quality digital mode operation doesn’t require expensive commercial equipment. With careful attention to audio interfacing, proper software configuration, and systematic testing, any operator can establish a capable SSTV station ready for both local ragchewing and DX hunting.
The journey from first connection to polished operation involves considerable learning, but each challenge overcome builds deeper understanding of radio technology and signal processing. Start simply, focusing on reliable reception before transmitting. When you do begin transmitting, start with test images into dummy loads before venturing on-air. Listen to experienced operators, study the characteristics of different modes, and don’t hesitate to ask questions—the SSTV community generally welcomes newcomers and happily shares knowledge.
Final Thought: SSTV uniquely combines the technical satisfaction of digital mode operation with the emotional connection of sharing visual experiences across vast distances. Your first successfully decoded DX image—perhaps showing a snowy mountain scene from Japan or a sunset over the Mediterranean—creates a moment of real connection that pure voice or data contacts rarely match. That blend of technology and humanity defines amateur radio’s enduring appeal.
Remember that optimal configurations vary among individual stations based on specific equipment, location, and operating preferences. The settings and procedures outlined here provide starting points requiring adjustment for your particular situation. Keep detailed notes of configuration changes and their effects, gradually refining your station toward peak performance. Most importantly, get on the air and enjoy the unique experience of visual communication through amateur radio’s oldest image mode.
Welcome to the fascinating world of Slow Scan Television. May your signals be strong, your images clear, and your contacts many!
Frequently Asked Questions (FAQ)
Q1. Do I need a special modem or dedicated hardware to get started with SSTV on my uBITX or sBITX?
No special modem is needed. SSTV runs entirely through your rig’s normal SSB audio path. Your computer’s sound card does all the work — it generates and decodes the tones just like any other digital mode. If you already have a digital interface set up for FT8 or PSK31, that same interface works perfectly for SSTV without any changes.
Q2. Can I use the same audio interface I built for FT8 for SSTV as well?
Yes, absolutely. Any FT8 digital interface — whether homebrew or commercial — works directly for SSTV. Both modes use the same three connections: transmit audio into the mic input, receive audio from the speaker output, and a PTT line. Nothing about the interface needs to change. SSTV is just another audio-based digital mode from the interface’s point of view.
Q3. I have an sBITX — do I still need an external computer and audio interface for SSTV?
No. The sBITX is unique in that its internal Raspberry Pi is directly wired to the radio’s audio and PTT circuitry. You can run SSTV software like QSSTV natively on the sBITX itself, with no external computer, no sound card, and no interface box required. An external PC can still be connected over USB or network if you prefer, but it is entirely optional.
Q4. Which SSTV software should I use on Windows, and on Linux?
On Windows, MMSSTV by JE3HHT is the most widely used and time-tested choice — it has been refined over decades and handles all common SSTV modes reliably. On Linux, QSSTV is the go-to option; it integrates cleanly with PulseAudio or ALSA and has a clear, logical interface that is friendly for beginners. On macOS, MultiMode from Black Cat Systems is a solid choice. All three are free to download.
Q5. What audio sample rate should I set in MMSSTV or QSSTV?
Set it to either 8000 Hz or 11025 Hz. Higher sample rates give no benefit for SSTV and only add unnecessary CPU load. Keeping the rate low also helps maintain stable timing, which matters for clean image decode.
Q6. How do I set the correct receive audio level so images decode properly?
Tune to 14.230 MHz USB and watch your SSTV software’s input meter while an SSTV signal is coming through. Aim for around 70–80% of the maximum input level — strong and healthy but not hitting the top. If the meter is peaking and clipping, turn the radio’s AF volume down. If images are coming through speckled and weak, turn it up. Flat-topped waveforms on the screen are a clear sign of overload.
Q7. How do I know if my transmit audio drive is set correctly?
Watch your transceiver’s ALC meter while transmitting a test image into a dummy load. You want to see just a light flicker of ALC movement — around 20–30% of full scale on peaks. If the ALC meter barely moves, drive is too low and your signal will be weak. If it swings heavily, you are overdriving the rig, which causes distortion and splatter that makes your images look smeared on the receiving end.
Q8. Which PTT control method is the simplest and most reliable for a beginner?
VOX is the easiest to get started with — just enable it on your uBITX or sBITX and the radio will key itself whenever SSTV audio appears. Set the VOX hold time long enough to bridge brief pauses between tones. If you notice the rig occasionally keys from room noise or receiver audio bleed, tighten the VOX threshold slightly. For more precise control, a USB-to-serial adapter with RTS or DTR keying is the next step up and works very reliably once drivers are installed and the correct port is selected in software.
Q9. The top portion of my transmitted image is being clipped on the receiving end. What is causing this?
This is a PTT lead-time problem. The radio is not finishing its switch into transmit before the image audio starts. Go into your SSTV software’s PTT settings and increase the lead time in small steps of 50 ms at a time until the full image arrives cleanly. For most HF transceivers, a lead time of 100–200 ms is sufficient. There is no benefit to going much beyond that — it just wastes a little airtime.
Q10. My received images have faint horizontal bars or a low hum running through them. What is wrong?
This is almost always a ground loop — a small difference in ground potential between your computer and radio causing 50 Hz or 60 Hz hum to sneak into the audio path. First, make sure all your equipment shares a single common ground point and is powered from the same AC outlet where practical. Use shielded audio cables for all connections. If the problem persists, transformer-isolated audio paths — which commercial interfaces like the SignaLink provide — eliminate ground loops entirely. Ferrite chokes on cables can help in stubborn cases, but proper grounding is the real fix.
Q11. Other operators say my signal sounds clean but my images look washed out and faint. What should I check?
This usually means your transmit audio level is too low — the carrier is there, but the modulation depth is shallow, so the tones encoding the image don’t have enough level to decode properly on the other end. Gradually raise the audio drive on your interface while watching the ALC meter until it just begins to respond. Do not push it further than light ALC movement, or you will trade one problem for another.
Q12. I am getting garbled images even though signals sound strong in the speaker. What is the most likely cause?
Audio level is the first thing to check — even on a strong signal, clipping the input stage of your sound card will scramble decoding completely. Turn the radio volume down and see if images improve. The second common cause is frequency drift: if the radio is not holding frequency steadily, you may see a consistent diagonal slant across images or colours that slowly creep sideways. On the uBITX, check that your power supply is clean and well-regulated. On the sBITX, make sure the Raspberry Pi is not thermal-throttling due to poor cooling, as this can introduce timing errors that affect decoding.
Q13. Does SSTV need a specific transceiver mode — and does it matter which sideband I use?
SSTV always uses Upper Sideband (USB), universally, on all HF bands. Never use LSB or AM for SSTV — the tone relationships that encode the image data are calibrated for USB. This is true regardless of which software you use or which band you are on.
Q14. Which SSTV mode should I start with for general on-air operation?
Start with Martin M1 or Scottie S1. Both complete a transmission in around 90–110 seconds, deliver good colour quality, and are universally supported by every SSTV program in use today. Once you are comfortable, try Robot 36 when band conditions are poor — it completes in only 36 seconds and holds up better under weak or fading signals. Save higher-resolution modes for when propagation is excellent and signals are strong.
Q15. Where should I tune to find SSTV activity, and what is the standard calling frequency?
The primary worldwide SSTV calling frequency is 14.230 MHz USB on the 20 metre band. This is where most activity concentrates, especially on weekends and during special event operations. Listen there first — SSTV signals have a distinctive rising and falling chirp that is easy to recognise once you have heard it a few times. Actual image exchanges sometimes shift to a nearby clear frequency once contact is established, but 14.230 MHz is always the starting point.
Related Posts
