Module profiles 

The vetted PHY profiles, re-exported so a board crate that depends only on this one can name a profile without a manifest entry. Vetted LoRa PHY profiles.

The one table every shipped preset comes from: firmware factory defaults, host tools, the web debugger, and the iOS app through umsh-mobile-core. Tests and examples spell out their own PHY literals instead of reaching for this table, so editing an entry here never silently rewrites a test.

The MeshCore entries mirror that project’s published suggested settings, https://api.meshcore.nz/api/v1/config (config.suggested_radio_settings.entries), read 2026-08-26. The two entries MeshCore marks deprecated are left out, as is its path_hash_size, which has no UMSH meaning.

Structs

PhyProfile

A vetted PHY profile: the four parameters two nodes must agree on to hear each other, plus the local settings vetted alongside them.

Constants

DEFAULT

The profile a device comes up on out of the box, and after a factory reset.

DEFAULT_SYNC_WORD

The private-network sync word every vetted profile uses. The spec suggests it in docs/protocol/src/ulcp-radio.md, and it is what enable_public_network = false selects on an SX126x.

DEFAULT_TX_POWER_DBM

DEFAULT’s vetted transmit power, for the firmware defaults that need a plain value. A default profile without one fails the build.

SUPPORTED_BANDWIDTHS_HZ

The LoRa bandwidths a device accepts for PROP_PHY_LORA_BW, in Hz.

VETTED

Every vetted profile, in the order an operator is offered them: the default first, then the rest as MeshCore publishes them.

Functions

by_id

The profile with the given identifier.

matching

The vetted profile the given parameters spell out, if any.