Meshtastic guide clarifies regional presets and Canada 902-928 MHz rules

D-Central Technologies’ new Meshtastic reference lands on the problem that trips up a lot of first-time builds and too many repeat ones: the wrong regional setting, or a preset mistaken for a region. That sounds small until a node looks configured in the app but is actually off-band, underperforming, or needlessly hard to coordinate with the rest of the mesh.

The mistake that costs you airtime, range, and compliance

Meshtastic’s own docs draw a hard line between channel settings and modem preset settings, and that distinction matters. A preset is the radio configuration that applies across all channels, including frequency settings, spreading factor, and bandwidth. If you treat it like a simple profile name instead of the core of the radio setup, you can end up with a mesh that is technically awake but practically misaligned.

That is why this reference works so well. It does not just warn you away from mistakes, it turns the decision into a usable field guide. The page lays out 18 LoRa regions and 10 modem presets, then immediately points North American users to the most important rule in the whole chart: Canada uses the US region, which means the 902-928 MHz band.

Why Canada maps to the US region

Meshtastic’s region-by-country documentation places Canada in the U.S. 915 MHz region, and the radio settings docs use the same 902-928 MHz band range for North America. That lines up with Canada’s current RSS-247 Issue 4, which covers digital transmission systems and frequency-hopping systems in 902-928 MHz. For a Meshtastic build, that is not a bureaucratic footnote. It is the difference between a node that fits the local radio framework and one that starts from the wrong assumption.

The D-Central reference also calls out an important detail that is easy to miss: the power figures listed on the page are Meshtastic defaults, not device EIRP. That matters because a displayed number in the app is not the same thing as the actual radiated output of the hardware once antenna gain and device behavior enter the picture. In other words, the chart is a deployment aid, but it is not a substitute for understanding what the radio is truly putting into the air.

What the preset table really tells you

The strongest part of the page is how it translates abstract radio choices into something you can actually use. Instead of leaving you with “pick the right preset,” it lays out the band ranges, default power caps, slot counts, and duty cycles by region, then explains presets by spreading factor, bandwidth, and data rate. That makes the tradeoff visible: speed, range, and congestion are all linked.

Meshtastic’s North America settings note that LongFast provides 104 frequency slots and defaults to Slot 20, or 906.875 MHz, after a factory reset. The preset comparison also lists LongFast at 250 kHz bandwidth, SF11, and 1.07 kbps. Those numbers tell you exactly why it remains the default for many setups: it reaches well, it is familiar, and it works in a broad range of conditions.

But LongFast is not free. Meshtastic’s own blog explains that it can become a bottleneck in larger or denser meshes because it uses more airtime and consumes precious channel time. That is the hidden cost most people do not notice until messages slow down or the mesh feels crowded. In a small group, LongFast can be perfectly fine. In a busier network, it can start spending the band like it owns it.

When to think beyond LongFast

The reference becomes especially useful when you start comparing the faster presets. Meshtastic’s table shows MediumSlow, MediumFast, ShortSlow, ShortFast, and ShortTurbo moving progressively toward higher data rates and lower link budgets. That is the real decision point for field operators: faster presets can improve throughput and reduce airtime, but they do so by giving up some of the safety margin that helps a signal travel farther or survive tougher conditions.

That tradeoff is why the page is more than a static chart. If your mesh is local, active, and dense, a faster preset can make the network feel less clogged. If you are chasing maximum reach across rough terrain, a slower preset may still be the better fit. The point is to choose intentionally, not by habit.

Use the reference like a deployment checklist

The practical win here is that the dataset is available as CSV, JSON, and through a REST API. That makes it useful for more than one-off reading. You can feed it into automation, fleet setup tools, or deployment checklists, which is exactly the kind of operational help Meshtastic users need when building repeatable networks instead of one-off experiments.

The reference also sits neatly beside other parts of Meshtastic’s radio guidance. Region and preset choices are only part of the configuration picture, along with transmit power, hop limits, frequency slot selection, and role settings. Meshtastic’s docs recommend keeping most nodes set to CLIENT, CLIENT_MUTE, or CLIENT_BASE rather than jumping to ROUTER or REPEATER unless there is a specific reason. That advice fits the same theme as the region guide: the simplest-looking settings are often the ones that keep a mesh stable.

For a project built around open, off-grid, low-power communication, that is the whole game. A node can be affordable, portable, and perfectly flashed, but the network still depends on the right regional frame, the right preset, and a role that matches what the node is supposed to do.

The point of the guide

This is why the Canada and US 902-928 MHz guidance matters so much. The costly error is not just choosing the wrong menu item, it is building a mesh that feels right in the app while being wrong for the band, wrong for the traffic load, or wrong for the role. D-Central’s reference gives Meshtastic users a cleaner path through that maze, and in this hobby, that means getting on-air faster with fewer surprises.