Skip to main content

SAW Filter for WiFi LoRa 32 V4 Signal Reception

The WiFi LoRa 32 V4.3 R2 and R8 are available in two hardware configurations: with or without a SAW filter. This allows users to choose the configuration that best suits their application requirements.

What is a SAW Filter?​

A Surface Acoustic Wave (SAW) filter is a passive RF component that uses acoustic waves to select signals within a specific frequency range while attenuating unwanted frequencies.

In wireless communication devices, it helps suppress out-of-band interference received by the antenna, improving signal selectivity in the RF receiving chain.in the target frequency range and attenuate signals outside that range, reducing the impact of out-of-band interference on subsequent receiver stages.

In simple terms, a SAW filter acts as a frequency selector for RF signals:

  • Passes Target Frequencies: Allows signals within the required frequency range to pass through.
  • Suppresses Out-of-Band Signals: Attenuates signals outside the target frequency range.
  • Reduces RF Interference: Helps minimize the impact of out-of-band interference on the receiver chain.

Main Components of a SAW Filter​

A typical SAW filter consists of a piezoelectric substrate and interdigital transducers (IDTs). Some designs also include reflectors.

1. Piezoelectric Substrate

Provides the medium for surface acoustic wave propagation. Its piezoelectric properties enable the conversion between electrical energy and mechanical deformation.

2. Interdigital Transducer (IDT)

Consists of interleaved metal electrodes patterned on the piezoelectric substrate. It converts between electrical signals and surface acoustic waves through the piezoelectric effect. Electrode geometry and periodicity determine the filter's center frequency and bandwidth.

3. Reflectors

Typically consist of periodically arranged metal strips that reflect surface acoustic waves, forming an acoustic resonant structure and shaping the filter's frequency response. Not all SAW filters include reflectors.


How Does a SAW Filter Work?​

Working Principle

A SAW filter relies on the piezoelectric effect to convert between electrical signals and mechanical vibrations:

  • Inverse Piezoelectric Effect: Electrical signal → Mechanical deformation → Surface acoustic wave.
  • Direct Piezoelectric Effect: Surface acoustic wave → Mechanical deformation → Electrical signal.

The process consists of three main steps:

1. Electrical-to-Acoustic Conversion: When an RF signal enters the filter, the input IDT converts it into surface acoustic waves through the inverse piezoelectric effect. This occurs when the applied electrical signal causes periodic mechanical deformation in the piezoelectric substrate.

2. Frequency Selection: The filter's electrode geometry and acoustic structure are designed to allow surface acoustic waves within the target frequency range to propagate efficiently, while attenuating those outside the range.

3. Signal Output: The output IDT converts the filtered surface acoustic waves back into electrical signals through the direct piezoelectric effect, producing the filtered RF output.

The following diagram provides a simplified illustration of how a SAW filter works:


SAW Filter Frequency Characteristics​

The center frequency of a SAW filter depends on the surface acoustic wave propagation velocity and wavelength.

The relationship is expressed as:

  • f₀: Center frequency.
  • vSAW: Surface acoustic wave propagation velocity.
  • λ: Acoustic wavelength.

Different frequency bands require different IDT designs to achieve the desired center frequencies.

Two SAW filter models are used for different operating frequency bands:

Operating FrequencyModelPackage
868 MHzYF868.5N1-B2SMD1411-5P
915 MHzYFSAS915MV01UC1SMD1411-5P

SAW Filter Placement​

In the previous V4.3 design, two SAW filter footprints were reserved on the PCB:

  • U10: Before the LNA input stage.
  • U11: After the LNA output stage.

In the latest V4.3 revision, SAW filters are now consistently populated at the U10 position , before the LNA input stage. The U11 footprint remains unpopulated.

Field Test Results​

warning

The following results are based on user feedback and field tests and are provided for reference only.

Actual performance may vary depending on the testing environment, antenna configuration, and power supply conditions.

1. Performance Comparison Under Different Power Conditions

The following results compare the observed performance of the V4 with and without a SAW filter during outdoor testing under different power conditions.

Performance MetricOutdoor (Battery-Powered)Outdoor (Mains-Powered)
Noise Floor Reduction8–9 dB6 dB
SNR Improvement on Weak Links3.5–6.2 dB2.0–3.5 dB
RSSI Change on Weak Links−1 to −4 dB−2 to −3 dB

2. Detailed Outdoor Battery-Powered Test Results

The following table shows a comparison between the V4 without a SAW filter and the V4 with a SAW filter during an outdoor battery-powered test.

Performance MetricV4 (Without SAW Filter)V4 (With SAW Filter)
Noise Floor (Median)−88 dBm−96 dBm
Packets Received per Hour111140
RX Error Rate13.7%10.0%
Median SNR Difference on Weak Links (364 Paired Packets)—+4.8 dB
Packets Decoded by This Board Only79380

These results indicate that the SAW filter may help reduce the noise floor and improve SNR, particularly on weak links. Although RSSI may decrease slightly, the improved SNR can contribute to better weak-signal reception.


3. Noise Floor over Time: Compares the background noise levels of the two devices over time, showing differences in noise levels and their response to environmental interference.

4. ΔSNR Histogram: Shows the distribution of SNR differences between the two devices when receiving the same packets, highlighting their relative signal quality.

Together, these results show the observed differences in noise floor and SNR between the two devices under real-world operating conditions.

Summary​

Based on customer feedback and field test results, the SAW filter may reduce RSSI by approximately 2.5 dB while lowering the noise floor by approximately 6–9 dB. Despite the slight reduction in signal strength, SNR improvements of approximately 2–6 dB have been observed on weak links. More significant improvements were observed during outdoor battery-powered operation.

For improved reception, enabling the LNA is recommended when supported by the RF configuration. The SAW filter suppresses out-of-band interference and improves receiver selectivity, while the LNA amplifies weak RF signals with minimal additional noise. Together, they can help improve overall receiver performance.

How Far Can Heltec WiFi LoRa 32 V4 Reach? R2 vs R8 Tested in the Real World

1.Test Summary​


Purpose.​

Compare the RF performance of two Heltec WiFi LoRa 32 V4 transmitter boards — R2 (ESP32-S3R2variant, Vext = GPIO36) and R8 (ESP32-S3R8 variant, Vext = GPIO40) — against one fixed LilyGO T3-S3 reference receiver, over distance, including full round-trip (talkback) verification of the return path.

Test site.​

All runs were performed along the coastal path at East Coast Park, Singapore (parallel to the ECP).The reference/base node sits near East Coast Pk Area D; test points are marked at 500 m, 1 km, 1.5 km, 2 km and 2.5 km along the shore — open, flat, mostly low vegetation, with one exception at the 2 km point (trees blocking line of sight; see §4 and §7).

Test site map: East Coast Park coastal path with base node and 500 m / 1 km / 1.5 km / 2 km / 2.5 km markers

Equipment and configuration.​

  • R2 / R8: Heltec V4.3 hardware, KCT8103L front-end module (FEM), ≈22 dBm radiated (SX1262 register 11 dBm + ~11 dB FEM gain). Both run firmware "v2" with identical radio settings.

  • T3-S3: Fixed reference receiver and talkback transmitter; logs every packet to CSV. Its transmitter has no power amplifier, so its radiated talkback power is well below the Heltec's ~22 dBm FEM output (see §8).

  • Radio (identical on all three): 923.2 MHz (AS923, Singapore 915–928 MHz), SF7, BW 125 kHz, coding rate 4/5, preamble 8 symbols, sync word 0x12 (private), fixed 32-byte payloads, 1 packet per second.

Round-trip protocol (per 1-second slot).​

  1. Heltec → T3-S3: data packet (id),(seq).

  2. T3-S3 → Heltec: talkback T3,(seq) (PA-less transmit, see §8).

  3. Heltec → T3-S3: ack AK,(seq),(rssi),(snr) — the Heltec's measured RSSI/SNR of the talkback (this is the TB_RSSI / TB_SNR columns).

Each waiting window is 200 ms. If no talkback arrives, the T3-S3 still logs the data packet but writes -,- in the TB columns.

Column semantics.​

  1. *_RSSI / *_SNR: forward link, data packet as received by the T3-S3.

  2. *_TB_RSSI / *_TB_SNR: return link, talkback as received by the Heltec (relayed in the ack).

  3. *_Transmission: session verdict — PASS = every packet completed a full round trip; MARGINAL = some talkbacks failed; FAIL = data received but no talkback at all.

What was covered.​

Both devices were tested at all five distances: 25 packets per distance per device (5distances × 25 packets × 2 devices = 250 packet slots; 246 were recorded). No FAIL and no blank verdicts occurred in either file. All statistics below are computed from the recorded rows only.

Not covered by the data.​

The CSVs contain no date/time, antenna heights, orientation, or weather. The siteitself is documented above (coastal path, East Coast Park), and the 2000 m obstruction is known (trees blocking line of sight), but per-run conditions cannot be determined from the files alone (see §7).

2.Per-Device, Per-Distance Statistics​


"Packets recorded" is counted against the expected 25 rows per run. "Loss %" is therefore missing rows, not necessarily over-the-air packet loss (see §7). TB success counts only rows where a talkback value was logged.

Totals.​

Both devices recorded 123/125 packets. Overall talkback success: R2 = 102/123 (82.9 %), R8 =92/123 (74.8 %).

2.3 Headline plots​

Mean RSSI vs distance for both devices, forward and talkback links

Mean SNR vs distance for both devices, forward and talkback links

Forward RSSI per packet for every distance, R2 and R8 panels

Boxplot of forward RSSI distribution per distance for both devices

3.R2 vs R8 Comparison​


Discussion.​

  • Forward link (RSSI at the T3-S3). The two boards track each other within ±3 dB at every distance. R8 is ahead at 500 m (−1.6 dB), 1000 m (−1.9 dB) and 2000 m (−2.7 dB); R2 is ahead at 1500 m (+1.5 dB); at 2500 m they are effectively tied (0.4 dB). The sign flips between distances, and a 1–3 dB spread is normal run-to-run variation for a single 25-packet sample (per-run RSSI σ ≈ 1.1–3.1 dB). On the forward link no consistent winner emerges — R8 is nominally better at 3 of 5 distances, but by margins inside the measurement noise.

  • SNR mirrors the RSSI results (same sign at every distance), confirming the differences are genuine link-strength differences rather than noise-figure artifacts.

  • Round trip (talkback). This is where the boards diverge. R8 is clearly better at 1500 m (100 % vs 96 %) and at 2000 m (70 % vs 35 %) — R8 held the return link twice as reliably at 2000 m. However, R2 is dramatically better at 2500 m (80 % vs 4 %). Because R8's 2500 m collapse dominates the totals, R2 wins overall round-trip reliability (82.9 % vs 74.8 %) despite R8's forward-link edge.

  • Verdicts. R8 achieves PASS at 1500 m while R2 is MARGINAL there (a single failed talkback: packet 7). Both are MARGINAL at 2000 m and 2500 m.

  • Interpretation. The ESP32-S3R2 vs S3R8 module differences (flash/PSRAM variants) are not expected to change RF performance, and the data bears that out on the transmit side. The asymmetric 2500 m talkback result points to a receive-side/environmental event at the R8 position during that run, not a weaker transmitter (see §5 and §7).

4.Path-Loss Trend vs Distance​


Path loss fit, RSSI vs log10 distance

Comments on consistency.​

  • The trend is monotonic from 500 → 1500 m and then 2000 → 2500 m behaves oddly: 2000 m reads worse than 2500 m on both boards — by 8.8 dB (R2: −99.0 vs −90.2) and 6.5 dB (R8: −96.3 vs −89.8) — and the TB link shows the same inversion (R2: 7.4 dB, −111.9 vs −104.5; R8: 6.4 dB, −110.4 vs −104.0). Because the inversion appears identically on both devices and in both directions, it is a property of the 2000 m site/path, not of either radio. Known cause: trees block line of sight at the 2 km marker (site survey) — the only obstructed point on the route.

  • With the 2000 m site excluded, the fit is very clean (R² = 0.93–0.96) with n ≈ 2.4–2.7 — slightly worse than free space (n = 2), typical for an open/semi-open ground path at ~900 MHz.

  • The 1000 m and 1500 m points for R2 are nearly identical (−84.3 / −84.7 dBm), i.e. the path lost almost nothing over that extra 500 m — again consistent with location-to-location variation dominating small distance steps.

  • Full five-point fits (n ≈ 3.0–3.2, R² = 0.77–0.86) understate the underlying regularity because they are dragged down by the 2000 m site; for prediction, the four-point fits excluding 2000 m are more representative of these paths.


Forward vs talkback mean RSSI per device

Talkback success rate per distance

Direction asymmetry.​

Forward minus return RSSI, averaged over the run, is 14.3 dB (R2) and 14.3 dB (R8) —remarkably consistent per distance (12.9–14.8 dB across all ten runs). This matches the expected ~15–25 dB asymmetry (lower end), caused by the Heltec receive path passing through its FEM while the T3-S3 receive path does not. Note additionally that the talkback signal originates from the T3-S3's PA-less transmitter, so the return link also starts from a much lower radiated power than the forward link — it is doubly disadvantaged (reflected in §8's next steps).

Return-link levels vs forward levels per distance (mean RSSI):

Note. The 2000 m gap is smaller only because the TB average is computed over the subset of successful talkbacks (15 of 23 rows failed on R2, 7 of 23 on R8); the failed rows have no value at all, so the true return-link mean is worse than shown.

Talkback / ack reliability.

  • 100 % round trip at 500 m and 1000 m for both boards.

  • R2 @ 1500 m: 24/25 (96 %) — the single failure (packet 7) is what demotes the run from PASS to MARGINAL.

  • R2 @ 2000 m: 8/23 (35 %) — failures on packets 2, 3, 4, 6, 8, 9, 11, 13, 16, 17, 18, 20, 23, 24, 25.

  • R8 @ 2000 m: 16/23 (70 %) — failures on packets 4, 9, 11, 15, 19, 20, 22.

  • R2 @ 2500 m: 20/25 (80 %) — failures on packets 8, 12, 14, 15, 23.

  • R8 @ 2500 m: 1/25 (4 %) — only packet 19 succeeded (−104 dBm / −6.5 dB); every other talkback timed out.

Where the verdict is not PASS, and why. All four non-PASS verdicts (R2 @1500/2000/2500, R8 @2000/2500) are caused exclusively by missing talkbacks — the forward data link was received in every recorded case. The verdict follows the return path, not the transmit path:

  • Failures correlate with return-link level: runs whose mean TB RSSI was ≈ −86 to −101 dBm (500–1500 m) were 96–100 % reliable; the runs averaging −110 to −112 dBm (2000 m) collapsed to 35–70 %.

  • The R8 2500 m anomaly is different: its return-link level when it worked (−104 dBm, single sample, SNR −6.5 dB) is the same as R2's healthy 2500 m average (−104.5 dBm), yet 24 of 25 talkbacks were lost. The forward link that run was normal (−89.8 dBm, tied with R2). This pattern — normal transmit, normal receive sensitivity when it works, near-total round-trip loss — suggests a run-local problem at the R8 receive side (e.g. elevated local noise/interference at that spot during the 2500 m session, a receive-window timing glitch, or an intermittent antenna/SMA issue) rather than a marginal RF link.


Judged against the SX1262 SF7/BW125 sensitivity of ≈ −132 dBm, margin = observed RSSI − (−132). Forward link — worst observed packet per run:

Forward link margin vs distance

  • R8 @2500 m has only one successful talkback sample; its "worst TB" is that single value and must not be read as a stable measurement. Projection. The forward link always kept ≥ 28 dB of margin over every observed packet at every tested distance, so the data link is far from the sensitivity cliff (SNR was positive at all times except isolated deep fades such as R2 2000 m min SNR −6.75 dB). The return link is the limiting factor: talkbacks already failed intermittently when the return link averaged ≈ −110…−112 dBm (18–22 dB nominal margin). Using the four-point slopes (excluding the 2000 m site), the return link degrades ≈ 24–27 dB per decade of distance; extrapolating from 2500 m (≈ −104.5 dBm) gives ≈ −109…−110 dBm at 4 km — i.e. at 4 km the round trip would sit right at the level where 2000 m failed 30–65 % of the time. Expect the forward link to keep working well beyond 4 km while full round-trip PASS results stop somewhere between 2.5 and 3.5 km with the present setup and antenna placement. (Extrapolation is indicative only — it assumes the same environment and does not model fading statistics.)

7.Anomalies, Missing Data, and Data-Quality Caveats​


All of the following are stated rather than hidden:

  1. Missing rows (4 of 250 slots). R2 @2000 m: packets 12 and 14 have an entirely empty block; R8 @2000 m: packets 7 and 21 have an entirely empty block. They are counted as 8 % "loss" in the tables (23/25 recorded). Whether those packets were never transmitted (run stopped/aborted) or simply not logged cannot be determined from the CSV. No distance block is entirely empty for either device, and no verdict cell is blank in either file.

  2. -,- talkback rows. 21 rows on R2 and 31 rows on R8 have -,- in the TB columns: the data packet was received by the T3-S3, but no talkback arrived in the 200 ms window. These rows are excluded from TB RSSI/SNR averages (they have no value), which biases the TB averages optimistically at 2000/2500 m. R8 @2500 m has only one TB sample, so its TB statistics are effectively a single point.

  3. 2000 m site inversion. Both boards, in both directions, read 6–9 dB worse at 2000 m than at 2500 m (forward: 8.8 dB on R2, 6.5 dB on R8; talkback: 7.4 dB on R2, 6.4 dB on R8). Cause confirmed by the test operator: trees block line of sight at the 2 km marker — the only obstructed point on an otherwise open coastal path. The 2000 m data is therefore a NLOS sample and should not be pooled naively with the LOS points in path-loss fits.

  4. Non-monotonic 1000/1500 m on R2. −84.3 vs −84.7 dBm — essentially flat; small-site variation, not a measurement error.

  5. First-packet dips. Several runs open with a weaker first packet (e.g. R8 @1000 m packet 1 = −92 dBm vs ≈ −82 dBm for the rest; R8 @2500 m packet 1 = −104 dBm vs ≈ −89 dBm; R2 @2500 m packet 1 = −98 dBm vs ≈ −90 dBm). Possible settling/AGC effect or momentary fade; worth re-checking with repeat runs. These first packets also dominate the min column, which is why worst-case margins at 1000 m and 2500 m look worse than the averages suggest.

  6. No saturation observed. The note about T3-S3 RSSI saturating near 0 dBm applies at very close range; at the closest tested distance (500 m) readings were −69…−75 dBm, i.e. far from saturation. No values required discarding for that reason.

  7. No FAIL verdicts were produced; every non-PASS run is MARGINAL. All verdicts within a distance block are uniform (one verdict per run, no conflicts).

  8. Remaining environmental metadata gaps. The CSVs carry no timestamps, antenna type/height/polarization, or weather. The site is known (East Coast Park coastal path, map in §1) and the 2000 m obstruction is identified (trees blocking line of sight), but the R8 @2500 m talkback collapse (1/25) is still unexplained by the data — it can only be confirmed by re-running that session. The T3-S3's lack of a TX power amplifier (§8) is likewise a setup fact, not visible in the CSVs, and applies to every talkback row.

  9. Method. Packet loss = missing rows vs the expected 25 (not provable over-the-air loss). Averages are arithmetic means of the recorded rows; SNR/TB statistics exclude -,- cells; R² values are from ordinary least-squares fits on log₁₀(distance). All computations were scripted from the raw CSVs (analyze.py, graphs.py) — no numbers in this report were typed by hand.


Conclusions.

  1. Both boards pass cleanly to 1000 m: 100 % packet reception and 100 % round-trip success at 500 m and 1000 m, ≥ 40 dB forward-link margin.

  2. Forward-link performance is effectively equivalent: R2 and R8 agree within ±3 dB at every distance; the sign of the difference changes with distance, so neither board is provably better on transmit. Nominal edge to R8 (better at 3 of 5 distances), inside run-to-run noise.

  3. The return (talkback) link decides every non-PASS verdict. The forward data link never failed in any recorded packet; all MARGINAL ratings come from missing talkbacks.

  4. Round-trip reliability: R2 82.9 % overall vs R8 74.8 % overall. R8 is much better at 2000 m (70 % vs 35 %), R2 vastly better at 2500 m (80 % vs 4 %). The latter looks like a run-local receive-side failure on R8, not a hardware deficit — its forward link that run was normal.

  5. The 2000 m point is the weakest path for both boards (forward −96…−99 dBm, return −110…−112 dBm, return success only 35–70 %) and behaves unlike the 2500 m point: trees block line of sight at the 2 km marker, so this is a known obstruction effect, not a device fault.

  6. Path loss follows a normal log-distance law (n ≈ 2.4–2.7, R² ≥ 0.93) once the 2000 m site is excluded; the full five-point fit gives n ≈ 3.0–3.2 with lower R².

  7. Limiting factor going further: the return link, which is ~14.3 dB weaker than the forward link on both boards. Forward margin stays ≥ 28 dB to 2500 m, but the round trip is already intermittent once the return link averages ≈ −110 dBm — extrapolation puts 4 km roughly at that boundary.

Recommended next steps.

  1. Remove the T3-S3 from future testing as the reference/talkback node. Its transmitter has no power amplifier, so its radiated TX power is far below the Heltec boards' ~22 dBm FEM output. As the return-link transmitter it under-drives the link, and every non-PASS verdict in this report was decided by that weak return link — the round-trip results therefore characterise the T3-S3's TX shortfall at least as much as the Heltecs. Replace it with a PA-equipped reference node (22 dBm+), or take the ground truth from the mesh stack's own delivery/ack metrics, so round-trip figures reflect the R2/R8 transmitters rather than the reference node.

  2. Re-flash both R2 and R8 with Meshtastic firmware and repeat the distance runs to test reliability in a mesh network. Run both boards at the same 500 m – 2.5 km markers with identical Meshtastic settings and compare mesh-level metrics instead of a single point-to-point round trip: packet delivery ratio / acknowledged-message success per distance, behaviour of the Meshtastic stack (routing, retries, hop handling, channel settings), and R2 vs R8 under identical mesh conditions — including whether the 2 km (trees, NLOS) and 2.5 km points stay reliable in a real mesh deployment.


Report generated 5 October 2026. All statistics and graphs computed directly from R2.csv and R8.csv via analyze.py and graphs.py in their respective project folder.

Special Thanks to Dave Cuyler

We would like to extend our sincere thanks to Dave Cuyler for conducting the field tests and generously sharing his detailed results and data. All testing and data presented in this report were provided by Dave. We greatly appreciate his time, effort, and valuable contribution to the Heltec community.

OSHI on Heltec Nodes: Flashing, and 2,000 Bytes Over a V4-to-T114 Link

A Heltec Mesh Node T114 running the OSHI build, next to a Heltec WiFi LoRa 32 V4 on the bench

OSHI is a messenger for iPhone and Android that keeps working when the network does not. It carries messages over Bluetooth and the local Wi-Fi between nearby phones, and over LoRa when you give it a radio — and the radio we flash, carry and test with is Heltec hardware.

This write-up is the hardware half: what we put on a Heltec node, how we put it there, and what the link between two of them actually measured. Every figure below is something we read off a device or a log, with the date it was read.

Heltec Wi-Fi HaLow Enables Smart Farming

Context​

A few years ago, a family story prompted us to try to detect changes early on that might go unnoticed during visits. Ariel Pérez, Sebastián's father, was in charge of citrus orchards when a plague suddenly broke out and most of the crop was lost. Nothing like that had ever happened there before.

We chose to start with the delta trap: the producer already knows it, the problem is contained, and between visits a pest can grow without anyone noticing.

The trap takes and sends a photo every day. This allows us to see if insects are starting to fall in without waiting for the next sweep.

This is what we aim for with Luma: clarity and reliable data in real time. On the outside, it's a standard delta trap. Inside, it houses a solar panel, a ESP32 Wi-Fi HaLow board with HaLow Wi-Fi, and a camera. Before discussing artificial intelligence or alerts, we need to answer the basics:

  • Is the connection reliable, does the battery last, and does the trap hold up in the field?
  • Do you take and send photos every day?
  • Do photos allow us to tell what's falling?

How we did the test​

We hung the trap in a plum and peach orchard in San José, Uruguay. The trees were in bloom. We placed it on the wire, at branch level, where the traps were already being checked. We used an attractant in the trap. We were looking for codling moth, but we didn't check if all the captured specimens were of that species.

The trap was located about 100 meters from the office, where we installed the HaLow internet-connected access point. The signal passed through two walls and several rows of plants.

In this test we used Wi-Fi HaLow instead of 4G. In the previous test, the cellular signal was insufficient to reliably send the photos. The trap took a photo every day at 12:20 and sent it. We also requested some extra photos from the office. We left the same adhesive flooring in place throughout the test, which is why the insects accumulated. Until Thursday the 17th, the photos showed other insects, but no moths of interest. On Friday the 18th, we counted 14 specimens. After the peak, the daily catches were 3, 3, 10, and 0.

From 0 to 14 in 24 hours​

On Thursday the 17th at 12:20 other insects were seen, but no moths of interest.

Thursday 17, 12:20: other insects are seen, but no moths of interest.

On Friday the 18th, at the same time, we counted 14 specimens of interest. The previous photo did not show any.

Friday 18, 12:20: 14 copies marked with red boxes.

Upon seeing the jump from 0 to 14, the local agronomist told us that he liked being able to check the trap online and the possibility of receiving alerts when the catches increased. The trap continued sending photos. The captures varied from day to day. To determine if pest control is necessary, the species, the crop, and the stage of infestation must be considered. This test did not assess these factors. It still needs to be repeated with more traps and in different locations.

What we learned in the field​

It's funny, but what we learned most had to do with how we held the trap. The trap hung from a wire, and the wind blew it from side to side. At one point, it ended up leaning against a plant, which covered its solar panel. Without power, the battery died, and the trap stopped working. We removed it to recharge it and reinstalled it. On another occasion, the wind blew the antenna inside a metal pipe, and we stopped receiving photos. We believe the metal blocked the signal. When we removed the antenna, we started receiving them again. We're going to install a fixed antenna, pointing upwards, and secure the trap better with tape or a hook attached to the wire or the plant. We want to prevent it from moving and the panel from being covered. Cloudy days weren't a problem. The battery is small, but the trap is off most of the time and the solar panel recharges it. The power outage occurred when a plant covered the panel. With the antenna free, the photos arrived at the office and looked good enough to count the insects.

What does this test prove?​

  • The trap worked in the field.
  • The panel kept the battery charged, even on cloudy days, as long as it received light.
  • One photo per day and extra photos when we ask for them.
  • We validated the usefulness of having daily information to alert in time when captures increase.

Next steps​

The next step is to connect several traps and add up the automatic count. This will allow us to track captures from different locations each day and see on a map where pest pressure is increasing. By expanding this network, the data can be used to generate alerts and develop predictions for producers, companies, and institutions. The idea is to help them detect increases early and decide where to focus their attention.

We were able to observe from the office how a trap changed in the field. Now we need to test if we can reliably do this with more traps.

Sources: photos sent by the trap in September 2026, photos of the installation, and internal LUMA records. We counted the insects by looking at the photos. The previous test is in “Wi-Fi HaLow Field Test.” https://lab.luma.uy/publicaciones/ya-validamos-en-campo

MeshMesh — MeshCore firmware with an on-device interface for the Heltec V4 and T114

Author: Igor Krasnodymov · MIT licence · GitHub · Website and browser installer

MeshMesh is an open-source firmware for LoRa boards. It runs on the MeshCore network and stays compatible with standard MeshCore nodes, repeaters, room servers and the official MeshCore apps. Its main idea is to use the mesh straight from the device: chats, channels, contacts and settings live on the board's own screen and button, so no phone is required. When you want a phone, there is an Android app and a web page.

Two Heltec boards are among the main test boards of the project and are tested on real hardware:

BoardScreen and controlsConnectivity
Heltec WiFi LoRa 32 V4 (ESP32-S3, SX1262)128×64 OLED, the PRG buttonWi-Fi access point and web page, Bluetooth LE, USB
Heltec Mesh Node T114 (nRF52840, SX1262)240×135 colour TFT, the USER button, L76K GPS (optional)Bluetooth LE, USB

The Heltec V4-R8, V3 and Wireless Tracker targets are also built, but they have not yet been run on hardware.

Heltec WiFi LoRa 32 V4​

The V4 gets a one-button interface: a click goes to the next screen, a hold opens the actions of the screen (reply, announce the node, open a game, change a setting).

Home screen: clock, radio profile, RX/TX counters

A node: type, route, signal, distance and bearing

Signal radar: Wi-Fi, Bluetooth and LoRa around

Chess over the mesh on the OLED

Device mode at boot: normal, repeater, room server

The network pet

  • Messages: direct chats and channels (hashtag, meshcore:// link or QR, key, invitations), delivery receipts, the route of every message.
  • Nodes: signal, hops, distance and bearing; announce the node, share the position.
  • MeshCore regions: a default region and one per channel, and a search of the regions served by nearby repeaters.
  • Repeater and room server modes, chosen at boot with the button or in the settings; admin login and remote CLI from the MeshCore app.
  • Signal radar for Wi-Fi, Bluetooth and LoRa with "warmer / colder" homing, and a Wi-Fi CSI motion sensor between two boards.
  • Wardriving: a coverage map of the mesh, exported to CSV, GeoJSON, KML and WiGLE.
  • Chess with contacts over the mesh (Elo ratings and Swiss-system tournaments), a network pet that feeds on radio traffic, and the DIC3R dice roller.
  • Web page over the board's own Wi-Fi access point: chats, map, nodes, radar and settings in a browser.

Heltec Mesh Node T114​

The T114 has its own colour interface, drawn at the native 240×135 resolution, with the same one-button logic.

T114 home: radio profile and tiles

T114 node card

T114 radar: Bluetooth and LoRa

T114 chess games

T114 network pet

T114 dice roller

It has messaging, nodes, regions, repeater and room server modes, chess, the pet and dice, as on the V4. The radar covers Bluetooth and LoRa (the nRF52840 has no Wi-Fi). Position and clock come from the L76K GPS on boards that have it fitted. The phone connects over Bluetooth LE (PIN pairing) or USB.

Android app and the official MeshCore apps​

The MeshMesh Android app shows the device's own interface on the phone over Wi-Fi (V4), Bluetooth or USB. It adds notifications, offline maps with relief kept on the phone, and the packet path of every message: which repeaters passed it on, with SNR and RSSI.

App homeApp chatApp message path

Both boards also speak the MeshCore companion protocol, so the official MeshCore apps connect to them over Bluetooth or USB and work with the board's chats, contacts and channels.

The device screens, the web page and the app are available in 15 languages: English, Chinese, Russian, Ukrainian, Spanish, Portuguese, French, German, Italian, Polish, Turkish, Japanese, Korean, Arabic and Indonesian.

Installation​

Open the MeshMesh website in Chrome or Edge on a computer, connect the board over USB, choose the board and the screen language, and press Install.

  • Heltec V4: the installer writes the firmware over USB. Tick "Erase device" only when coming from other firmware; MeshMesh updates keep the key, contacts, settings and history.
  • Heltec T114: press RESET twice quickly to enter the bootloader when the board runs other firmware, then press Install (serial DFU in the browser). Alternatively, after a double RESET an HT-n5262 drive appears, and firmware.uf2 from the website can be copied onto it.

Default radio profile: 868.731 MHz, BW 62.5 kHz, SF8, CR 4/6. Change it in Settings → Radio; all nodes of a network must use the same profile. Follow the radio regulations of your country.

Feedback, bug reports and translations by native speakers are welcome on GitHub.

Heltec v4 Exp Kit Distance Testing with BLackout Comms

Screenshot of Heltec v4 r8 running Blackout Comms Blackout Comms is private-cluster LoRa mesh firmware for encrypted texting, location sharing, and mesh memory. It runs without phones, cell service, or internet. The Heltec WiFi LoRa 32 Expansion Kit V2 (R8) touchscreen has proven to be a very strong platform for it.

Project Background and Motivation​

My family and I often go camping and traveling in locations that don't have cell service at all, and this allows us to track & text over fairly long distance, in the complete absence of grid services.

Blackout Comms was built to address that gap for small trusted groups (like families) that need reliable text and location when infrastructure is unavailable or unreliable. It prioritizes privacy, persistence of messages and last-known positions, frequency hopping, and simple on-device use.

A secondary goal was making the system work on readily available and inexpensive LoRa hardware without requiring a phone for core operation. Since the original implementation, I quickly realized some people prefer to use an app, so I also created open source companion apps for Android, Windows, and Linux.

Why the Heltec V4 Expansion Kit V2 (R8)​

The R8 Expansion Kit offers a compact touchscreen handheld form factor, solid SX1262 radio with external amplifier, microSD slot, and enough PSRAM/flash for offline maps and a responsive UI. These match Blackout Comms’ needs for on-device mapping and a phone-optional experience better than many bare development boards. Heltec Slots and Buttons

One thing that sets the Heltec v4 Exp Kit apart from most other LoRa devices is its integrated LNA (low-noise amplifier). This drastically increases practical range of the device, as you'll see further down in the demo.

Hardware Configuration​

  • Heltec WiFi LoRa 32 Expansion Kit V2 (R8) touchscreen
  • MicroSD card (recommended, installed before flashing for maps)
  • Optional BME280 sensor and buzzer for environmental data and alerts
  • Standard LoRa antenna (SMA)

Older Expansion Kit variants (touchscreen and glass/OLED) also work; they use a different firmware build.

Blackout Comms Architecture and Firmware Workflow​

Blackout Comms uses a private-cluster model. One device acts as the root for onboarding. Devices form a trusted mesh with asymmetric encryption, digital signatures, and frequency hopping. Direct messages can be held in the mesh for up to 24 hours for later delivery. Location and status are shared within the cluster.

Onboarding Example

Flashing is done through a web installer. Select the R8 / Expansion Kit V2 build, connect the device, and flash. After flashing, create or join a cluster on the device itself.

Offline Mapping and MicroSD Usage​

The R8’s microSD slot and memory allow offline map tiles to be stored and displayed on the device. Maps remain available without a phone or internet. Install the card before flashing for the smoothest experience.

Heltec Map Example

Encryption, Cluster Communication, and Message Delivery​

How Blackout Comms Communicates

  • End-to-end asymmetric encryption and ECDSA signatures on messages and location data
  • Unpredictable frequency hopping with packet striping
  • Mesh memory of last-known positions, heading, and status for offline or out-of-range devices
  • Delivery confirmations and up to 24-hour hold for direct messages
  • Optional bridges (e.g., MQTT or Mesh Cloud) when internet is available, while keeping end-to-end encryption

Companion Apps for Android, Linux, and Windows​

Blackout Comms is designed specifically to not require any phones or apps, but companion apps are available that can make certain things easier. As you'll see in the field test, I do often use the Blackout Comms Live app for Android, as zooming/swiping on a map, checking for connectivity pings, and certain other test-type activites are just faster to do on a phone. Currently, there are 2 companion apps available.

Blackout Comms Live for Android​

Blackout Comms Live mesh companion for Android

  • Connects to the Heltec via BLE
  • Shows a dashboard of your connected device (connectivity, temperature, battery level, current stealth mode, etc)
  • Maps the current or last-known locations of all devices in your cluster
  • Shows connectivity (the Mesh Graph) throughout your cluster, allowing you to see which devices have good connectivity
  • Allows sending/receiving of encrypted messages and broadcasts
  • Analyzes/charts your cluster's mesh traffic, all the way down to individual pings/packets
  • Automatically downloads map tiles as needed, which remain cached on your phone/tablt for fully offline use
  • Open Source - or get it in the Google Play Store
  • Learn more

Overlook for Windows and Linux​

Overlook companion tool for Windows and Linux

  • Connects to the Heltec via BLE
  • Suitable for laptops, Raspberry PIs; Looks great on large screens
  • Shows a dashboard of your connected device
  • Maps the current or last-known locations of all devices in your cluster
  • Shows connectivity (the Mesh Graph) throughout your cluster, allowing you to see which devices have good connectivity
  • Allows sending/receiving of encrypted messages and broadcasts
  • Charts your cluster's mesh traffic level
  • Automatically downloads map tiles as needed, which remain cached on your phone/tablet for fully offline use
  • Open Source - or get it in the Google Play Store
  • Learn more

Field-Test Setup and Methodology​

Tests used pairs of R8 Expansion Kits running current Blackout Comms firmware. Devices were configured for the same region and cluster. Range tests measured direct (non-meshed) delivery of messages and location updates under real terrain conditions, including wooded areas to a base location. Companion apps (Blackout Comms Live on Android and Overlook on desktop) were used for monitoring.

Watch the Demo​

Heltec Mesh Range Demo

Range Results​

Reliable direct messaging and location updates were achieved at distances exceeding 11 km. These results were obtained with standard antennas under typical outdoor conditions.

One woods-to-base transmission covered approximately 13 km (8 miles), using a standard Heltec v4 R8 at one end and some less typical equipment at my house.

  • Install a microSD card before flashing if on-device maps are desired.
  • Include the BME sensor and buzzer for maximum features and audible alerts.
  • Use the correct firmware build (R8 vs. older Expansion Kit).
  • Place always-on links/nodes with good line-of-sight to improve mesh resilience.
  • Frequency hopping and mesh memory provide practical benefits in interference-prone or intermittent environments.

The R8 Expansion Kit V2 provides a practical handheld platform for advanced private mesh applications beyond standard Meshtastic use cases. Pre-flashed units are also available for users who prefer a ready-to-run configuration.


Blackout Comms is developed by Altware Development LLC. Firmware is free for supported devices; certain cluster features may require a license.

KoaOS for Heltec V4

A small Unix-style operating system for the Heltec WiFi LoRa 32 V4. Flash it once, log in over USB, and the board becomes a pocket computer with a shell, a text editor, GPS, Wi-Fi, weather and LoRa APRS. Then install apps over Wi-Fi without ever reflashing, or write your own in C.

KoaOS is an independent, open-source project (MIT) by Koakno. It is not made or endorsed by Heltec; "Heltec" is used only to say which board it runs on.


Why KoaOS​

The V4 is a capable board, but most firmware turns it into a single-purpose device. KoaOS treats it as a small computer. You operate it from a serial terminal (USB), everything you type is mirrored on the board's OLED, and no phone app or PC is needed once it has been flashed.

KoaOS is built around three ideas:

  • A real shell and filesystem. Login, processes, files that survive reboots, a Nano-style editor, and simple shell scripts.
  • Apps you install and remove at runtime. The firmware stays put. Apps are separate packages (.esp) downloaded over Wi-Fi and run in a WebAssembly sandbox, so a crashing app does not take the OS down.
  • The OS owns the hardware. Apps ask for Wi-Fi, GPS, LoRa or pins, and the OS grants, shares or refuses. Two apps cannot fight over the radio or the same pin, and everything an app holds is released when it exits or is killed.

What you get out of the box​

Built into the firmware, ready right after flashing:

  • Shell with login, ps, kill, background jobs (&), redirection (>, >>) and scripts
  • LittleFS storage that survives reboots and reflashes (same partition scheme)
  • GPS with a shared on/off manager
  • Wi-Fi client (wifi scan, wifi connect) with HTTP/HTTPS
  • Weather from Open-Meteo
  • LoRa APRS (aprs, plus an aprsd background daemon)
  • edit text editor, neofetch, pins, and more

Apps and the SDK​

Apps are written in C, compiled to WebAssembly and run by wasm3, with app memory held in PSRAM (about 1 MB per app). The SDK exposes a 48-function ABI covering:

  • Console and file I/O (each app gets a private /data/<app>/ folder)
  • Wi-Fi and HTTP(S), GPS, and LoRa (configure, CAD, TX, RX)
  • GPIO, two UARTs, I2C and SPI on OS-approved pins
  • Hardware RNG, SHA-256, HMAC-SHA256 and AES-128
  • IPC, so a command like myapp start can talk to a running myapp daemon

Every package declares what it needs (for example requires=wifi,gps), and the OS enforces it at run time. Apps cannot touch the pins used for GPS, the radio, the OLED, USB or power.

Included example apps: hellowasm, gpswatch, webget, iodemo, and an experimental MeshCore client.

Quick start​

  1. Flash the firmware (see below) and open a serial terminal on the board's USB port: Arduino Serial Monitor, PuTTY, or a serial app on your phone.
  2. Log in with root / 1234, then try:
help
free # should show a psram line
wifi scan
wifi connect <ssid> <password>
weather
gps
  1. To install an app, serve a folder of .esp packages from any computer or phone on the same Wi-Fi, then on the board:
install -s <host-ip>:8000
install -l
install meshcore

Flashing​

KoaOS needs the V4's PSRAM, so other boards, including the V3, are not supported. You can either:

  • Use the prebuilt firmware from the project's GitHub Releases page and flash it at address 0 with esptool, Espressif's Flash Download Tool, or an Android flasher such as ESPFlash; or
  • Build it yourself with the Arduino IDE (or ArduinoDroid on Android). The README lists the exact board settings; the important ones are QSPI PSRAM, 16 MB flash, and the No OTA (2MB APP/2MB SPIFFS) partition scheme.

KoaOS was built and flashed entirely from an Android phone, so no PC is required at any step.

Good to know​

  • V4 only. Input is by USB serial terminal; an on-board keyboard is not supported yet.
  • GPIO is an app API, not a driver layer. Not available to apps yet: GPIO interrupts, PWM, ADC, display drawing, and command-line arguments.
  • Apps are interpreted, so heavy computation is slow. Each .wasm is limited to 256 KB.
  • Security is basic and meant for hobby use. The default login is a convenience, and anyone holding the board can reflash it. install uses plain HTTP, and the SHA-256 in a package catches corruption but does not prove authorship, so only install from servers you control. The firmware runs no network server, so nothing listens on Wi-Fi.
  • MeshCore is experimental. The client implements the MeshCore protocol and passes native tests, but has not yet been tested against real MeshCore nodes over the air. Feedback is welcome.

Roadmap​

Planned work includes saved Wi-Fi networks, I2C keyboard support (if there is demand), a graphical home screen for the V4 Expansion Kit's touchscreen, and a public app repository. See ROADMAP.md in the repository.

Credits​

Built on wasm3 (MIT), with U8g2, TinyGPSPlus, RadioLib and arduino-esp32. The MeshCore app speaks the MeshCore protocol.

Into the Orchard: Real-World Long-Range Wi-Fi HaLow Testing

With the development of smart agriculture, an increasing number of agricultural monitoring systems are shifting from traditional manual inspections toward automated and digital monitoring. Cameras, sensors, and other devices can continuously collect field data and transmit it to remote servers for analysis via wireless networks.

However, in large outdoor environments such as orchards and farms, the trade-off between long-range connectivity, low power consumption, and high bandwidth remains a major challenge when deploying wireless monitoring systems.

To address these challenges, LUMA Lab in Uruguay is developing an automated system for agricultural pest monitoring.

Traditional pest monitoring typically relies on workers periodically checking traps. An automated solution, by contrast can continuously capture images with cameras and send them to a server for identification and analysis.

The overall system can be simplified as:

Field Trap → Camera → Wireless Network → Server → Image Analysis

In this system, wireless data transmission becomes a key factor in determining whether the entire system can operate reliably over the long term.

Unlike conventional sensors, this system needs to transmit image data. A single image typically ranges from 200~600 KB, meaning the system needs not only to cover a relatively large area, but also to provide sufficient data throughput.

This creates new challenges for traditional low-power wireless communication technologies.


Traditional Wireless Solutions is Limited

1. Cellular Networks:​

During the initial stage of the project, a prototype system was developed using an ESP32, camera, 4G modem, battery, and solar power supply. However, field tests in the orchard revealed that the 4G network could not maintain a consistently stable connection under the environmental conditions. At the same time, the cellular modem and its power system increased the overall power consumption of the device. For outdoor terminals powered by a combination of batteries and solar energy, higher power consumption directly shortens maintenance intervals and increases deployment costs. Therefore, although cellular networks offer excellent data rates, they are not necessarily the optimal choice for all remote agricultural environments.

2. LoRaWAN:​

LoRaWAN is a widely used communication technology in agricultural IoT. It offers low power consumption and long-range coverage, making it well suited for small amounts of telemetry data such as temperature and humidity, positioning, and device status. However, this project needs to transmit image files ranging from 200–600 KB. If LoRaWAN were used to carry image data, the files would need to be divided into multiple packets, resulting in long transmission times and a higher risk of packet retransmission. In general, LoRa is better suited to small telemetry data rather than large image files.


Wi-Fi HaLow: Another Networking Option

Wi-Fi HaLow is based on IEEE 802.11ah and operates in the Sub-1 GHz frequency band.

Compared with conventional 2.4 GHz and 5 GHz WiFi, WiFi HaLow is not primarily designed to pursue higher peak data rates. Instead, it uses a lower frequency band to achieve longer coverage distances while supporting the connectivity requirements of IoT devices.

For agricultural remote monitoring systems, its advantages can be summarized in three areas:

Long-Range Connectivity

The Sub-1 GHz frequency band has propagation characteristics that are well suited to long-distance wireless communication, enabling connections over hundreds of meters and potentially even farther.

IP Networking

Wi-Fi HaLow remains part of the WiFi ecosystem and can directly carry IP traffic.

This means remote devices can connect to existing network architectures without requiring a completely new proprietary communication protocol.

Higher Data Throughput

Compared with low-speed long-range communication technologies such as LoRaWAN, Wi-Fi HaLow can provide significantly higher data throughput, making it more suitable for applications involving images, files, and other larger data transfers.


Field Testing in a Real Orchard Environment

To evaluate the performance of Wi-Fi HaLow in a real-world environment, LUMA Lab built a test network consisting of a fixed AP and mobile nodes.

The basic architecture was:

Internet / Ethernet
↓
Wi-Fi HaLow Dongle AP
↓
Wi-Fi HaLow Camera
↓
Mobile Test Node
↓
Data Transmission

The test used the Wi-Fi HaLow Dongle, configured as a HaLow AP.

Rather than being conducted in a laboratory, the test was carried out in actual apple orchards and road environments to evaluate how vegetation, terrain, and other environmental factors affected the wireless link.


The tests were conducted at multiple locations, including apple orchards and road environments.

The test distances ranged from:

137.6 meters → 753 meters

The measured parameters included:

  • Download

  • Upload

  • RSSI

  • Latency

  • Maximum communication interruption time

This testing approach differs from simply measuring the "maximum communication distance." Instead, it focuses more on whether the network can still provide usable data transmission at practical operating distances.


The first test was conducted in an apple orchard. At a distance of 301.1 meters:

Download: 1.863 Mbps
Upload: 1.164 Mbps

The results show that even with trees and vegetation obstructing the wireless path, Wi-Fi HaLow was still able to achieve Mbps-level data transmission.

The second test extended the distance further. At 534.4 meters:

Download: 1.088 Mbps
Upload: 0.397 Mbps
RSSI: approximately −90.22 dBm

At 640.1 meters:

Download: 0.218 Mbps
Upload: 0.053 Mbps

This indicates that in the vegetation-rich orchard environment, Wi-Fi HaLow could still maintain a usable connection over several hundred meters.

The third test was conducted in a road environment and produced one of the most representative results of the study. At a distance of 506 meters:

Download: 1.710 Mbps
Upload: 1.634 Mbps

Even beyond 500 meters, the bidirectional throughput remained above 1 Mbps. For an agricultural monitoring system, remote devices can not only upload sensor data but also transmit relatively large files such as images. This is an important difference between Wi-Fi HaLow and traditional low-speed long-range IoT technologies.

This is also one of the key differences between WiFi HaLow and conventional low-speed long-range IoT communication technologies.

More importantly, the test validated a practical networking requirement:

Transmitting larger amounts of data over hundreds of meters while maintaining an IP network connection.

This sits in a space between several traditional wireless technologies.

Traditional Wi-Fi offers high data rates but limited transmission distance; 4G/5G provides high speeds and wide coverage, but depends on carrier networks and generally consumes more power.

LoRa/LoRaWAN offers long range and low power consumption, but its extremely low bandwidth makes it unsuitable for transmitting large amounts of data such as images.

Wi-Fi HaLow, meanwhile, combines long-range connectivity, IP networking, and relatively high throughput. This makes it particularly suitable for outdoor agricultural environments spanning hundreds of meters where image transmission is required and traditional solutions are less suitable. It provides an effective complement to existing wireless IoT technologies.


LoRa and Wi-Fi HaLow Can Complement Each Other

In practical IoT systems, LoRa and Wi-Fi HaLow do not necessarily need to compete with each other.

A more suitable architecture could be:

LoRa​

Responsible for:

  • Sensor data

  • GPS

  • Status information

  • Alerts

  • Control commands

Wi-Fi HaLow​

Responsible for:

  • Images

  • Files

  • Camera data

  • High-volume IP communication

By combining the two technologies, a system can balance low power consumption, long-range connectivity, and higher data throughput.


More Possibilities for Long-Range Connectivity

For developers who need to quickly build a long-range IP network, the Heltec Wi-Fi HaLow 7608 Router and Wi-Fi HaLow Dongle can serve as the network center and remote terminal, respectively.

Internet / Ethernet
↓
Heltec Wi-Fi HaLow 7608 Router
↓
Wi-Fi HaLow Dongle

This architecture eliminates the need to equip every remote device with a cellular connection while retaining IP networking capabilities.

As a result, the technology can be applied not only to agricultural monitoring, but also to:

  • Remote cameras

  • Farms and ranches

  • Industrial parks

  • Warehousing and logistics

  • Construction sites

  • Large outdoor areas

The LUMA Lab field test demonstrates a typical application of Wi-Fi HaLow in a real outdoor environment.

The test results show that even under the influence of vegetation, terrain, and other environmental factors, Wi-Fi HaLow can maintain usable data communication over several hundred meters. For devices that need to transmit images, files, or other IP data over long distances, this provides an alternative to traditional Wi-Fi, cellular networks, and LoRa.

More importantly, the test demonstrates more than simply a "maximum range" figure. It points to a more practical networking concept:

Extending IP connectivity into areas that are difficult for traditional Wi-Fi to reach.

As applications such as remote cameras, smart agriculture, industrial IoT, and outdoor monitoring continue to develop, Wi-Fi HaLow has the potential to become an important wireless technology for connecting long-distance, high-data-volume devices.

Data sources : https://lab.luma.uy/en/publications/wifi-halow-field-test

Every Node Counts Meshtastic for Beginners — a community mesh-networking workshop

About the workshop​

Every Node Counts brought together around a dozen students from across the School of the Art Institute of Chicago for one shared question: at a moment when almost all of our communication runs through infrastructure we don't own, what does it take to build a network of our own?

The workshop was selected by SAIC's Student Government through a competitive Art for Impact grant, and it was open to everyone - no prior electronics experience required. Over a single afternoon, participants went from "what is a mesh network?" to holding a working, off-grid radio node they had flashed and configured themselves. The whole workshop was built around the Heltec LoRa 32 V3, an affordable, all-in-one board that let complete beginners hold a working node in a single afternoon.

We built together rather than working alone. Meshtastic is a network that gets stronger with every device added to it, so the room worked the same way: people who finished first turned around and helped their neighbors. By the time the last node came online, nobody had gotten there entirely by themselves.

For us the point was never only the device. In these precarious times it felt important to make something together - to build local community, to have the kind of rich conversations that don't happen often, and to think about what it means to spend time outside the large data networks we're usually placed inside. It was, simply, a beautiful afternoon.

Pairing up to flash firmware and work through the radio settings together.

The build​

Participants flashed Meshtastic firmware onto their boards over USB-C, set their region and channel, gave each node its own name and identity, and joined a shared local mesh. The moment a neighbor's message first appeared on their own screen was, every time, the moment it clicked.

Working with the Heltec V3​

At the center of every build was the Heltec LoRa 32 V3. For a room of first-time makers it worked out well: the board arrives with the ESP32, the SX1262 LoRa radio, USB-C, battery management, and a small OLED display already integrated, so participants had a complete, self-contained node the moment they plugged in - nothing to wire up or solder.

Flashing Meshtastic onto the V3 was straightforward even for people who had never used a microcontroller: connect over USB-C, flash the firmware, and the onboard OLED immediately confirms the node is alive. That instant feedback mattered - seeing their own name and node ID appear on the little screen was the moment mesh networking stopped being abstract. The built-in display also meant nobody was flying blind out in the field, with signal, battery, and messages all readable right on the device.

A finished node, housed in a hand-decorated case with beads and a broken-heart charm.

The build plan projected in the lab during the workshop.

Workshop poster, designed by Helen Janjaa Lee.

Thank you​

Thank you to Heltec for supporting Every Node Counts. The boards were the heart of the workshop, and the beginner-friendliness of the V3 is a big part of why a room of artists with no electronics background left as node operators. We're hoping to grow this into an ongoing mesh-networking group on campus, and we'd love to stay in touch as it develops.

Acknowledgements​

Every Node Counts was made possible by the Art for Impact grant from SAIC Student Government, and by the ATSP faculty, who supported the workshop and provided the space and facilities. With gratitude to Heltec for their material support. Photographs by Doug Rosman. Poster design by Helen Janjaa Lee. A workshop by Nickii Schamborski and Helen Janjaa Lee.

Heltec V3 & V4 Mountain Field Test: LoRa Mesh Performance in Real Terrain

For the vehicle test, Daniel used a Heltec V3 with the stock antenna and operated it from inside the vehicle.

Test Route​

  • Total distance: approximately 4 km
  • Elevation ranged from 808 m down to 620 m
  • The route followed mountain roads

Despite:

  • Potential RF signal attenuation from the vehicle's metal body
  • Extensive blockage from the surrounding mountains

the communication link remained stable throughout the test.


Daniel also conducted a multi-hop mesh test on foot.

Because the mountainous terrain blocked the path, a direct line-of-sight link could not be established between the starting point and the destination node. Communication was therefore relayed through two high-altitude nodes:

  • Monte Livata (elevation: 1,350 m)
  • Marsia (elevation: 1,980 m)

Final Test Results​

  • Message delivery rate reached 100%
  • All five test messages were transmitted successfully
  • Multi-hop link latency was approximately 10 seconds

This test demonstrates the potential of LoRa Mesh networks in mountainous areas and environments with limited infrastructure.


Heltec V4: Exploring a Compact, Portable Communication Solution

For the Heltec V4, Daniel focused on a different use case:

A compact, portable node design.

During the test, the V4 was installed in a pocket-sized enclosure with an integrated GPS module and an internal antenna.

Although an internal antenna typically involves some trade-offs in RF performance, the V4's greater transmit capability can partially offset the antenna's limitations.

Vehicle Test​

Daniel drove from Cervara di Roma (Lazio) to Oricola (Abruzzo). During the test, he:

  • Used the pocket-sized V4 device
  • Used no external antenna
  • Maintained communication through a multi-node Mesh relay network

This test demonstrates the potential of compact LoRa Mesh devices for portable and off-grid communications.


Important Feedback from Real-World Testing

We are very grateful to Daniel for the time and effort he invested in this comprehensive field test.

Realistic testing is extremely valuable because it helps us understand how devices actually perform outside the laboratory and provides important guidance for future product improvements.

During the tests, Daniel also shared practical feedback on:

  • Power consumption
  • Hardware interaction and usability
  • Firmware flashing experience

These suggestions have been shared with our engineering team. We are actively evaluating possible improvements and considering them for future hardware revisions and software updates.

Feedback from community users has always been an important part of our product development process.

Every test helps us better understand user needs and continuously improve the product experience.


Advancing Off-Grid Communication Together

The combination of LoRa technology and Mesh networking continues to demonstrate tremendous potential in:

  • Outdoor exploration
  • Emergency communications
  • Communication in areas without network coverage
  • Community-based communication networks

As more users explore decentralized communication systems, real-world testing and feedback from the community are helping drive the technology forward.

Once again, our thanks to Daniel IU6WSC for sharing these detailed test results, photographs, and valuable suggestions with the community.

We look forward to seeing more real-world use cases and to continuing the development of Heltec products together with makers and communication communities around the world.