Define the question
Each test starts with a specific question about coverage, reliability, mobility, infrastructure, power, usability, or another measurable part of the problem.
Field Testing
Turn field observations into useful evidence.
Community Frequency uses practical field testing to understand how affordable mesh communications behave outside controlled laboratory conditions. The goal is not to collect impressive demonstrations. It is to produce observations that can be repeated, compared, documented, and used to make better decisions.
Control what we can
Where practical, radio configuration, antenna setup, node placement, routes, and test conditions are defined so results can be compared meaningfully.
Repeat and compare
Successful one-off tests are not treated as conclusions. Results are repeated across locations and conditions and compared between approaches where appropriate.
What we measure
Field testing can examine several parts of a communications system at the same time:
- message and packet delivery;
- coverage and practical range;
- direct and relayed communication;
- multi-hop and path behavior;
- node and antenna placement;
- mobility and changing conditions;
- power consumption, battery life, and solar operation;
- setup, configuration, and maintenance requirements;
- usability in realistic field conditions; and
- equipment cost, availability, and practical limitations.
From experiment to evidence
A field test produces an observation. A useful research result requires context.
For that reason, testing records include the conditions under which a result was obtained, the equipment and configuration involved, what was measured, what was expected, and what remains uncertain.
Not every successful test is a finding.
A result becomes more useful when it can be reproduced, explained, compared with other observations, and understood within the conditions in which it occurred.
A result becomes more useful when it can be reproduced, explained, compared with other observations, and understood within the conditions in which it occurred.
Current testing
Current work includes Meshtastic and MeshCore testing in Arizona, with an emphasis on practical behavior that can inform the Peru 2026 research mission.
Testing is also being used to develop methods for evaluating portable nodes, repeaters, multi-hop communication, mobility, power systems, and small-scale mesh infrastructure.
Why this matters for Peru
The purpose of the Arizona work is not to assume that results will transfer directly to Peru. It is to improve the questions, measurements, procedures, and documentation before testing in the environments that matter to the project.
Terrain, infrastructure, power availability, community needs, regulations, and operating conditions will all influence what is practical in Peru.
The research record
Detailed test logs, measurements, configurations, observations, and limitations belong in the project's technical record. The website provides the methodology and context; the public GitHub repository preserves the deeper experimental record.