A good site is a contribution, not a coverage promise
A well-placed fixed node can help a neighborhood. A high site could connect otherwise separated areas. Neither outcome follows from elevation alone: terrain, antenna pattern, receiver noise, local interference, radio settings, and congestion all affect the result.
This article is a proposed engineering workflow. No roof survey, White Tanks spectrum survey, hardware installation, or over-the-air test was performed for this series. It does not announce a club deployment or an approved site change.
Begin on the ground
Establish that two portable nodes exchange messages with the same settings. Measure a direct link before adding a relay. Keep a record of hardware, firmware, antenna, position, and power source. A failed test with unknown configuration is difficult to learn from.
Then temporarily raise one node at the proposed home location using safe, authorized access. Repeat the same destinations and directions. This separates the benefit of height from simultaneous changes to antennas, power, and firmware.
Arizona heat is a design input
Water resistance does not establish acceptable battery charging temperature. Seeed's Solar Node P1-Pro specification lists a 0–50°C charging range for its supplied batteries. Sun-exposed enclosure temperatures can exceed ambient air temperature, so a roof installation needs a thermal plan. Manufacturer specification
Our design preference is an exposed solar panel with shaded electronics and a battery-temperature cutoff suited to the actual chemistry. Do not substitute a different battery chemistry into a charger designed for another one. Log temperature and voltage during a realistic trial before leaving the equipment unattended.
Size solar capacity from measured average load and the desired overnight/cloudy-day reserve. Include conversion losses, recharge time, and battery aging. A 5 W panel rating alone does not establish daily energy production, and a large battery alone does not establish safe charging.
Roof node: the practical arrangement
Keep the radio close to its antenna where possible, with a short suitable feedline. Use weather-resistant cable entries, strain relief, drip loops, and a mounting arrangement that can be serviced. Account for grounding and surge protection as part of the building's installation, not as an afterthought.
Choose the node role with the local network. AZMSH recommends ordinary CLIENT for home/roof nodes and reserves router roles for suitable permanent high sites. A solar device sold as a “repeater” does not require selecting a router firmware role in every installation. AZMSH guidance
White Tanks: treat it as a shared RF site
At an established repeater site, evaluate available backed-up DC power before adding a separate solar system. Check permission, mounting space, cable routing, service access, and the battery system's load budget. The desired design is one the site team can maintain.
Receiver performance must be measured while nearby transmitters are operating normally. A quiet bench cannot reveal co-site desensitization. Antenna separation and appropriate filtering may matter more than transmitter power. Record observations rather than assuming a problem or assuming immunity.
Coordinate with local mesh operators before selecting high-site role, antenna pattern, and traffic policy. A high node can hear a large population and amplify unnecessary broadcasts. The route should solve an identified gap rather than merely create a distant map pin.
An RF test worksheet
Use the downloadable field-test worksheet for each route. Suggested columns include date, endpoint, firmware, preset/frequency, antenna, direct or relayed path, sent/received counts, acknowledgments, latency, RSSI/SNR when available, and internet-bridge state.
- Baseline: test the two handhelds close together, then at increasing separation.
- Home relay: repeat identical destinations with the elevated node.
- Two-way check: send from both ends; a heard beacon is not an acknowledged conversation.
- Dependency check: disable internet bridging for the RF-only run.
- Representative use: test indoors, outdoors, and with the radio carried normally.
- Soak: log battery and temperature through day/night cycles before permanent mounting.
- Recovery: verify restart behavior, retained settings, and how the site can be serviced.
Set acceptance criteria before testing. For example, a team might require nine of ten acknowledgments in each direction within a chosen interval at a defined destination. Those numbers are an illustrative test goal, not a guaranteed service level or a claim about either protocol.
What completion would mean
A useful deployment record names the exact hardware and settings, shows measured destinations and failures, identifies remaining dependencies, and assigns maintenance ownership. Offline tests, an online map, and software booting successfully are different evidence from sustained two-way RF operation.