M5: design round for transmitting #30

New Issue

2026-10-05T20:07:18Z

twisla commented

2026-10-05 20:07:18 +00:00

What

The question round that opens M5, ending in docs/milestones/M5.md. M5 is the first time this device transmits, so the round also settles what must be true before it may.

Already decided

Scope (first design round): sending, Direct Messages, Relaying, the duty cycle, sending your position.
Nothing transmits until the Region is confirmed (CONTEXT.md: Region; the Setup wizard asks, Settings::canTransmit()).
Every transmission is bounded by the Region and its Duty Cycle Budget (CONTEXT.md).
Defaults: EU868, LongFast, Client role, hop limit 3. Meshtastic's EU_868 is 869.4 to 869.65 MHz, 10 % duty cycle, up to 27 dBm; the SX1262 gives +22 dBm.
The Radio Service has no transmit function (M3, Q94). M5 adds it, deliberately.
Position precision comes from M4's round (#23).

Questions

What else guards a transmission besides the Region: an antenna reminder, a master switch in Settings, a visible mark while sending?
Transmit power: fixed, or a setting? What's the default?
Listen before talk: Meshtastic waits for a quiet channel with random slots. How closely do we follow it?
Direct Messages: recent Meshtastic firmware uses public-key encryption for them. Is M5 the moment to add a key pair (ADR 0001 deferred it), or do we send Direct Messages the older way and accept who can read them?
Relaying: do we relay from the first day, or only originate until our own traffic is proven? Battery cost.
What's tested with two devices, and what's the acceptance test: a message each way with acknowledgement, through a relay?
Does the node respond to requests from others (node info, position, traceroute)?

## What The question round that opens M5, ending in `docs/milestones/M5.md`. M5 is the first time this device transmits, so the round also settles what must be true before it may. ## Already decided - **Scope** (first design round): sending, Direct Messages, Relaying, the duty cycle, sending your position. - **Nothing transmits until the Region is confirmed** (CONTEXT.md: Region; the Setup wizard asks, `Settings::canTransmit()`). - **Every transmission is bounded by the Region and its Duty Cycle Budget** (CONTEXT.md). - **Defaults:** EU868, LongFast, Client role, hop limit 3. Meshtastic's EU_868 is 869.4 to 869.65 MHz, 10 % duty cycle, up to 27 dBm; the SX1262 gives +22 dBm. - **The Radio Service has no transmit function** (M3, Q94). M5 adds it, deliberately. - **Position precision** comes from M4's round (#23). ## Questions 1. What else guards a transmission besides the Region: an antenna reminder, a master switch in Settings, a visible mark while sending? 2. Transmit power: fixed, or a setting? What's the default? 3. Listen before talk: Meshtastic waits for a quiet channel with random slots. How closely do we follow it? 4. Direct Messages: recent Meshtastic firmware uses public-key encryption for them. Is M5 the moment to add a key pair (ADR 0001 deferred it), or do we send Direct Messages the older way and accept who can read them? 5. Relaying: do we relay from the first day, or only originate until our own traffic is proven? Battery cost. 6. What's tested with two devices, and what's the acceptance test: a message each way with acknowledgement, through a relay? 7. Does the node respond to requests from others (node info, position, traceroute)? ## Related CONTEXT.md (Region, Duty Cycle Budget, Relaying, Direct Message), ADR 0001, `docs/milestones/M3.md` (Q94), #22, #23.

twisla added this to the M5 Mesh transmit milestone 2026-10-05 20:07:18 +00:00

twisla added the

labels 2026-10-05 20:07:18 +00:00

twisla referenced this issue

2026-10-05 20:07:18 +00:00