A matching connector is half the check.

Every component in the path needs evidence for the frequency you intend to use.

Enter a channel frequency, in MHz

The checker accepts a finite number from 1 to 6000 MHz. Enter 915 for 915 MHz, not 915000000. The input bounds protect against mistaken units and invalid values; they do not establish that any listed radio supports the whole interval. The result evaluates each component separately.

Use the actual configured channel when you know it. A regional name is not a precise frequency. MeshMatch does not inspect firmware or configure a radio, and it does not verify that two radios share modulation, bandwidth, spreading factor or network settings.

Distinguish range from nominal frequency

A range supplies two usable comparison boundaries. For a stated interval, the checker includes both endpoints and rejects a value outside it. A nominal frequency supplies one supported reference point but no band edges. The checker can match that exact value; it returns unknown for nearby values when no published bandwidth is available.

This distinction matters for the cataloged 868 MHz antenna. MeshMatch does not invent a bandwidth around its nominal value. In contrast, the cataloged 915 MHz rod has a published numeric interval in the Seeed accessory guide. Its frequency finding can therefore fail independently of the connector finding.

Read the radio variant

The Heltec V3.2 datasheet lists separate low- and high-frequency hardware coverage. MeshMatch includes the 863-928 MHz HF variant only. The same board family name is not permission to select that range for an LF board.

For the Wio-E5 boards, this catalog uses the documented 868 and 915 MHz reference frequencies conservatively. A result at another frequency may remain unknown even if a broader firmware frequency plan exists. Expanding coverage requires numeric evidence for the exact hardware, rather than extrapolating from the transceiver chip alone.

Resolve the cable rating too

An adapter changes a connector path; it does not translate the transmitted frequency. A cable still needs suitable RF coverage. The two cataloged cable summaries lack a numeric rating, so their RF checks stay unknown. Length-dependent loss, antenna matching, enclosure effects and real performance are outside this calculator.

Hardware compatibility also does not establish permission to transmit. Check the current requirements of your jurisdiction, including power and antenna conditions, using its official regulator. MeshMatch supplies no legal region recommendation or range prediction.

Run a frequency check or read the pre-purchase record guide.