← Emcomm workflow · Extra hub · Digital bundle

HF digital paths operators actually deploy

Weak-signal skeds, formal message traffic, and position data — mapped to PACE layers. East Tennessee examples throughout; workflows apply in any county.

PACE planner Winlink workflow HF traffic hub

FT8 / JS8Call coordination

  • Calling freqs: FT8 / JS8 reference — USB dial segments by band.
  • When to use: Propagation marginal, need a sked, repeaters down — FT8 emcomm guide.
  • Not for: Directed nets, radiogram precedence, or served-agency record traffic.

VARA HF & Winlink

NBEMS / Fldigi (THOR, Olivia, MFSK)

Many agencies expect NBEMS (Fldigi + Flmsg) for ICS-style forms on data segments. Pair ICS-213 bodies with agency template libraries — NBEMS / Fldigi reference covers THOR, Olivia, and session checklist; document mode in PACE. See digital modes bundle for DMR/Meshtastic contingency.

APRS & propagation checks

Digital mode decisions

When does NBEMS outperform Winlink?

When your served agency already standardizes on NBEMS/Fldigi forms (THOR/Olivia) and expects ICS-213 bodies on agency templates — Winlink is the common ham volunteer path, but NBEMS matches many EMA workflows directly.

Is FT8 a replacement for voice nets?

No — FT8/JS8Call are weak-signal coordination and test contacts. Use them when propagation is marginal and you need a sked, not for directed net traffic or formal radiogram precedence.

Where does VARA fit in PACE?

VARA HF is a high-throughput data mode for Winlink sessions when gateways are reachable — document it as Alternate or Contingency in your PACE plan, not Primary voice.

What is APRS for in emcomm?

Position and status when voice is congested — a data layer, not message-of-record. Pair with ICS-214 logging for formal traffic.