NBEMS and Fldigi modes for served-agency emcomm — THOR, Olivia, MFSK settings, ICS-213 pairing, and PACE placement vs Winlink. Works offline after your first visit.

← Digital emcomm hub · All tools

NBEMS / Fldigi Reference

Fldigi + Flmsg (NBEMS) modes many EMA agencies expect for ICS-style forms on HF/VHF data segments — pair with ICS-213 bodies and document in PACE.

Common NBEMS modes (field reference)

Confirm your served agency's standard library before an activation. Operate within license privileges and band plans.

ModeTypical useNotes
THORRobust narrow dataCommon agency default — moderate baud, good on noisy HF
OliviaWeak-signal formsMultiple tone pairs — verify exact Olivia variant in agency template
MFSKStructured messagesOften paired with Flmsg ICS templates
MT63Wide HF trafficLegacy interoperability — check net instructions

Session checklist

Common questions

What is NBEMS?

Narrow Band Emergency Messaging Software — Fldigi + Flmsg for ICS-style forms many EMA agencies expect on HF/VHF data modes.

When does NBEMS outperform Winlink?

When your served agency standardizes on NBEMS templates (THOR/Olivia) and expects agency form bodies — Winlink is the common ham path, but NBEMS matches many EMA workflows.