Documentation index

SSTV reference library

Start here when you need more than a mode name. 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.

Learning route

From picture-by-sound history to per-mode timing

Read the history to understand why SSTV fits in voice-bandwidth radio.
Compare mode families before choosing a compatibility target.
Use the spec sheet when you need VIS, duration, raster, color model, or source notes.
Check public activity before assuming a satellite or event is currently on air.

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

Source-backed 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

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.

How SSTV mode families evolved

Monochrome and early hardware: narrow information rate, simple video tone mapping, and receiver stability as the central problem.
Robot and VIS: machine-readable mode identification made automatic receiving more practical.
Martin and Scottie color modes: Martin's RGB sequence and Scottie's G-B-R color scan pattern became durable compatibility targets.
Pasokon and PD: longer transmissions trade time for larger images and higher fidelity.
MMSSTV extended and narrowband modes: software-era modes add extended or N-VIS style identifiers and narrower deviations.
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

AVT FAX Kenwood FAST FM MMSSTV MSCAN Martin Monochrome PD Pasokon Proskan Robot Scottie Vester Wraase

Mode family comparison

Family	Typical role	Signal shape	Strength	Watch point
Martin	Classic HF color	RGB components with short sync/porch timing	Broad compatibility and familiar M1/M2 behavior	Longer than quick Robot modes
Scottie	Classic RGB color	RGB line sequence with Scottie timing	Good compatibility, including DX-oriented variants	Some historical tables disagree around DX variants
Robot	Fast color and monochrome	Y plus color-difference components	Very common, short transmissions such as Robot 36	Lower detail than long PD/Pasokon frames
PD / Pasokon	Higher-resolution color	Larger frames and longer scan durations	More detail for planned transmissions	Requires more pass time and cleaner channel conditions
MMSSTV	Software-era extended modes	MP/MR/ML and narrowband variants	Rich software compatibility and N-VIS style options	Less universal than Martin, Scottie, Robot, and PD
AVT / Wraase / FAX	Historical compatibility	Family-specific sync and component timing	Keeps uncommon analog SSTV modes documented	Several rows require source-by-source verification