Documentation index

SSTV reference library

Use this index when a mode name is not enough. The library links the history of Slow Scan Television to the practical timing contracts behind Martin, Scottie, Robot, PD, Pasokon, MMSSTV, AVT, Wraase, FAX, and other analog SSTV families.

Mode field guide

14 families

Family pages explain the operating role, signal shape, strengths, watch points, and mode rows for each analog SSTV group.

Browse the mode field guide

Cited spec sheet

85 rows

Filter by family, support status, duration, VIS or app identifier, color model, frame size, and line-timing notes.

Open the spec sheet

Packet image formats

SSDV packet reference

SSDV is kept separate from analog mode rows: it is packetised JPEG image data with headers, CRC32, and optional Reed-Solomon FEC.

Open the SSDV tables

Algorithm notes

JPEG fragments, MCU recovery, and FEC

Walk through encode and decode stages, including packet identity, MCU offset recovery, missing packets, and transport framing.

Read the SSDV algorithm notes

Related articles

Packets before pictures

Field notes compare SSDV with analog SSTV and explain what a ground station should log before judging the final JPEG.

Read the SSDV ground-station note

DRM radio system

DRM robustness modes

Mode A through Mode E are DRM COFDM robustness profiles, with different guard intervals, carrier spacing, bandwidths, and service capacity.

Open the DRM tables

Algorithm notes

FAC, SDC, MSC, coding, and OFDM

Follow the DRM encode and receive path through energy dispersal, multilevel coding, interleaving, pilot cells, and guard intervals.

Read the DRM algorithm notes

Related articles

Check the DRM signal first

Digital SSTV station notes should separate the RF/audio recording, DRM lock state, application object, and final recovered picture.

Read the DRM receiving note

Catalog coverage

46 app-supported rows

Generated from sstvparam.swift, including duration, frame, VIS/app identifier, porch timing, subcarrier, and tone range.

29 reference rows

Compiled from checked mode tables where duration, raster, VIS behavior, or line rate are published but the app does not implement the mode.

10 verification rows

Used for historical or conflicting entries such as secondary AVT rows, unknown VIS rows, and published collision notes.

Choose by operating situation

Short public satellite window

Start with the activity source. If the organiser names Robot 36 or PD120, follow that mode rather than guessing from audio alone.

Check source status

HF compatibility check

Compare Martin, Scottie, Robot, PD, and Wraase rows by duration, component sequence, VIS behaviour, and tolerance for a noisy channel.

Compare mode families

Implementation or decoder work

Use per-mode pages for timing fields, source notes, sample cards, FLAC audio, and round-trip receiver evidence where the app supports the mode.

Open the spec sheet

Bench evidence

Supported mode pages publish a generated colour test card, lossless audio encoded by the app transmitter path, and receiver loopback evidence after the FLAC has been restored to WAV. Reference-only modes still get raster matched test cards so uncommon rows remain inspectable.

How SSTV mode families evolved

  1. Monochrome and early hardware: narrow information rate, simple video tone mapping, and receiver stability as the central problem.
  2. Robot and VIS: machine-readable mode identification made automatic receiving more practical.
  3. Martin and Scottie color modes: Martin's RGB sequence and Scottie's G-B-R color scan pattern became durable compatibility targets.
  4. Pasokon and PD: longer transmissions trade time for larger images and higher fidelity.
  5. MMSSTV extended and narrowband modes: software-era modes add extended or N-VIS style identifiers and narrower deviations.
  6. Satellite practice: public ISS SSTV commonly favors highly compatible modes such as Robot 36 and PD120 when scheduled by operators.

What the tables are trying to answer

Can an automatic receiver identify it?

Classic modes usually use 8-bit VIS values; MMSSTV software-era rows can use extended identifiers, while AVT and some FAX-style rows need family-specific handling.

How much channel time does it need?

Short Robot and monochrome modes are useful for marginal paths. PD and Pasokon modes spend more time on larger frames and usually reward cleaner passes.

What color model is being scanned?

RGB, G-B-R, Y/R-Y/B-Y, and luma-only modes all fit inside the same audio tone idea, but the receiver has to know the component order and timing.

Family index

Mode family comparison

FamilyTypical roleSignal shapeStrengthWatch point
MartinClassic HF colorRGB components with short sync/porch timingBroad compatibility and familiar M1/M2 behaviorLonger than quick Robot modes
ScottieClassic RGB colorRGB line sequence with Scottie timingGood compatibility, including DX-oriented variantsSome historical tables disagree around DX variants
RobotFast color and monochromeY plus color-difference componentsVery common, short transmissions such as Robot 36Lower detail than long PD/Pasokon frames
PD / PasokonHigher-resolution colorLarger frames and longer scan durationsMore detail for planned transmissionsRequires more pass time and cleaner channel conditions
MMSSTVSoftware-era extended modesMP/MR/ML and narrowband variantsRich software compatibility and N-VIS style optionsLess universal than Martin, Scottie, Robot, and PD
AVT / Wraase / FAXHistorical compatibilityFamily-specific sync and component timingKeeps uncommon analog SSTV modes documentedSeveral rows require source-by-source verification