In 1970, Norman Abramson at the University of Hawaii had a problem. He needed to connect computer terminals across the Hawaiian Islands using a single shared radio channel. His solution: just transmit and hope for the best. If two stations talked at once — a collision — each would wait a random amount of time and try again.
He called it ALOHAnet. The protocol was called Pure ALOHA.
It’s 2026, and most LoRa mesh networks are still using it.
That’s not a simplification. Meshtastic — the most popular open-source LoRa mesh firmware, running on hundreds of thousands of nodes worldwide — uses flooding-based channel access that is functionally identical to what Abramson built 56 years ago. Nodes transmit when they have data. If packets collide, they’re lost. Retransmissions compound the problem. As node density increases, the network eats itself.
I’ve spent 33+ years building wireless infrastructure — from the world’s first metro-scale WiFi network in 2000 to municipal fiber to enterprise PTMP deployments. Every other wireless layer I’ve worked with solved this problem decades ago. Open mesh radio is the last holdout, and the reason it’s still running 1970s channel access is economic, not technical.
The economics just changed. And at Edge Orbital, that change is what makes a sensor mesh — the kind that holds together when the human mesh needs it to — actually viable outside the lab.
The math that kills your mesh
Pure ALOHA has an elegant throughput formula and a brutal ceiling.
Pure ALOHA throughput
S = G × e^(−2G)
Maximum at G = 0.5:
S_max = 1/(2e) ≈ 0.18418.4% maximum channel utilization. That’s not a pessimistic estimate. That’s the theoretical maximum under ideal conditions. Real-world deployments do worse.
Slotted ALOHA — where nodes can only transmit at the beginning of defined time slots — doubles this:
Slotted ALOHA throughput
S = G × e^(−G)
S_max = 1/e ≈ 0.36836.8%. Better, but still leaving 63% of channel capacity on the floor.
The collision probability for n nodes, each transmitting with probability p per slot:
P(collision) = 1 − n·p·(1−p)^(n−1) − (1−p)^nAt 20 nodes with modest traffic, you’re already seeing meaningful collision rates. At 50 nodes, the network starts to choke. At 100+ nodes, you hit cascade failure: collisions cause retransmissions, retransmissions cause more collisions, and throughput collapses below 10%.
The Meshtastic community knows this. They’ve lived it. The workaround is switching to faster radio presets — MediumFast, ShortTurbo — which trade range for throughput. The DefCon 2000-node mesh ran on ShortTurbo, which works inside a convention center but doesn’t give you the 10km links that make the radio layer valuable in the first place.
That’s treating symptoms. The disease is the channel access protocol.
What every other wireless layer figured out
Synchronized time division is standard practice in every other wireless layer. It’s not exotic. It’s not experimental. It’s how the industry works.
Cambium Networks (ePMP / PMP 450). The WISP industry’s backbone for 15+ years. Every Cambium access point synchronizes its transmit and receive windows to GPS Pulse-Per-Second. This enables collocated sectors on the same tower to reuse the same frequency without self-interference. Four to six sectors per tower, all coordinated by atomic clocks in orbit. If you’ve ever had fixed wireless internet in a rural area, this is why it works.
Ubiquiti LTU. Even Ubiquiti, historically a “good enough” vendor, added GPS synchronization to their LTU product line. The market demanded it.
Baicells CBRS. Their entire private LTE product line is built on TDD with GPS synchronization. Every deployment. No exceptions.
MikroTik NV2 — the cautionary tale. MikroTik built NV2 as a proprietary TDMA protocol but refused to add GPS sync. The result: operators have been begging on their forums since 2014 — literal years of unanswered feature requests. Many migrated to Cambium specifically because MikroTik wouldn’t give them synchronized timing. Forum thread titles tell the story: “TDMA with GPS sync: NV3?” (2014, still unanswered in 2026).
5G TDD. The 3GPP standard mandates GPS/GNSS synchronization with ±1.5µs accuracy (ITU-T requirement). This isn’t optional — 5G Time Division Duplex literally cannot function without it. Every major 5G deployment globally depends on synchronized timing.
The critical detail: none of these systems can cross-synchronize. A Ubiquiti LTU and a Cambium 450 sitting on the same tower cannot sync to each other. Each vendor implements GPS timing as a proprietary coordination layer. The wireless industry solved the timing problem 20 years ago — then every vendor locked the solution inside their own ecosystem.
That gap at the bottom of the stack is where open mesh radio still sits. Not because the engineers don’t know better — the Meshtastic developers are sharp — but because the cost math used to make GPS modules a non-starter at the node level.
The $200 problem that became a $2 problem
When Cambium started deploying GPS-synchronized PTMP systems in the mid-2000s, GPS modules cost $150–$200 per unit. At that price, GPS sync only makes sense on infrastructure equipment — access points and base stations costing $500–$2,000 each. Adding $200 to a $2,000 AP is a 10% cost increase. Acceptable.
Adding $200 to a $35 LoRa node? A 570% cost increase. Insane.
Here’s what changed: GPS modules now cost $2. The u-blox MAX-M10S is $3.50 in single quantities. The Quectel L86 is under $5. At volume, GPS receivers with PPS output are $1.50–$2.00. They’re smaller than a thumbnail. They draw less than 25mA.
The academic literature is still catching up. A 2023 paper from the University of Kragujevac (Pešović, UNITECH 2023) studied time synchronization in LoRa networks and explicitly dismissed GPS as “impractical for WSN due to larger dimensions, power consumption and high cost.” Their measured data was solid — they documented crystal oscillator drift in LoRa nodes from 8.36 ppm at SF7 to 170.33 ppm at SF12. At the highest spreading factor, clock drift makes coordinated transmission impossible without external synchronization.
Their conclusion was right about the problem. It was wrong about the solution — because their cost assumptions were already obsolete.
10-page PDF: faction breakdowns, zone strategy, mesh tech explained. Yours free.
The economics caught up to the physics. Nobody built the protocol.
Until now.
Edge Orbital Sync: the architecture
The approach is straightforward in concept. The implementation details matter.
Every GPS satellite broadcasts time signals synchronized to atomic clocks with nanosecond-level accuracy. GPS receivers output a Pulse-Per-Second (PPS) signal — a sharp electrical pulse at the top of every UTC second. This PPS signal is accurate to within ±10–50 nanoseconds of true GPS time.
For context: a LoRa transmission at SF7 (the fastest spreading factor) takes about 36 milliseconds. At SF12 (the slowest, longest range), over 1.4 seconds. We’re synchronizing with nanosecond accuracy to coordinate transmissions that last tens of milliseconds to over a second. The timing margin is enormous.
The protocol — what we file as Edge Orbital Sync, patent-pending, three filings, 82 claims:
- Every node has a GPS receiver with PPS output. All nodes synchronize their local clocks to GPS PPS.
- The channel is divided into fixed-duration time slots, aligned to the GPS time reference.
- Each node is assigned specific slots for transmission. During its slot, a node has exclusive access to the channel.
- Outside its assigned slot, the node’s radio is either receiving or sleeping.
- Slot assignment is managed through a lightweight coordination protocol (specifics in the patent filing).
The results:
- Near-100% channel utilization — no capacity wasted on collisions because collisions don’t happen.
- Zero protocol-layer collisions by design — not probabilistic collision avoidance. Collisions are structurally eliminated.
- Deterministic latency — every node knows exactly when it transmits. Worst-case latency calculable to the millisecond.
- Graceful scaling — adding nodes means subdividing or allocating additional slots, not increasing collision probability.
- 5–10× effective throughput on identical hardware. Same radio, same antenna, same power. Just a fundamentally better protocol.
ALOHA real-world utilization: 10-15%
TDMA utilization: 85-95% (accounting for guard times)
Improvement factor: 85% / 12.5% = 6.8× throughput on same hardwareThe power story nobody expected
When I posted about this on Reddit’s r/meshtastic community, I expected pushback on the GPS requirement. Instead, the most upvoted technical insight was about power consumption — something I’d underweighted in my initial framing.
The community pointed it out immediately: synchronized time division doesn’t just fix throughput. It fixes battery life.
In an ALOHA-based mesh, every node must keep its receiver on continuously. You don’t know when another node will transmit, so you have to be listening all the time. Always-on receive is the dominant power draw in a LoRa node — the SX1276 draws 10.3mA in receive mode, which doesn’t sound like much until you multiply by 24 hours a day, 7 days a week.
With scheduled transmission slots, each node knows exactly when it needs to transmit and exactly when to expect incoming traffic. Outside those windows, the radio sleeps. Deep sleep on LoRa hardware draws microamps, not milliamps.
Always-on receive (ALOHA): 10.3mA × 24h = 247.2 mAh/day
5% duty cycle (scheduled sleep): 10.3mA × 1.2h + 0.01mA × 22.8h = 12.6 mAh/day
Power reduction: ~95% — weeks become months on the same battery“Deploy and forget” becomes real. Sensor networks that currently need weekly battery swaps become seasonal maintenance at most.
Credit where it’s due: the r/meshtastic community surfaced this independently. When the people running the largest LoRa mesh deployments in the world tell you the power benefit matters more than the throughput benefit, you listen.
The tradeoffs
Every engineering decision has costs.
GPS on every node. Every transmitting node needs a GPS receiver with PPS output. Indoor-only nodes need a sky-view antenna or must receive timing from nearby GPS-equipped boundary nodes. Subterranean deployments and dense urban canyons require timing propagation. Solvable, but adds complexity.
Cold start time. GPS acquisition takes 30 seconds to 2 minutes from cold start. A node can’t transmit on the schedule until it has a GPS fix. We mitigate this with a fallback: nodes without GPS lock can listen immediately but can’t transmit until synchronized. In practice, 30 seconds is acceptable for most deployments.
Slot assignment complexity. Who decides which node gets which slot? Static assignment works for fixed deployments but breaks when nodes join and leave dynamically. Dynamic slot allocation requires a coordination protocol — this is where most of the engineering complexity lives, and it’s the core of the patent filings.
Bursty traffic. ALOHA handles bursty traffic naturally. Scheduled access can waste slots when a node has nothing to send. The solution is hybrid: reserve a portion of the frame for scheduled slots and a portion for contention-based access. Most serious time-division systems do this. It’s well-understood engineering.
GNSS vulnerability. GPS signals can be jammed or spoofed — serious enough that the 5G industry is developing GNSS-independent timing alternatives. For consumer mesh, this is an edge case. For critical-infrastructure deployments, we’ve designed fallback to free-running crystal oscillators with holdover algorithms. At 170ppm drift (worst case, SF12), a node maintains usable synchronization for tens of seconds without GPS.
Academic validation
The Pešović paper (UNITECH 2023, University of Kragujevac) is the most directly relevant academic work. Their findings:
- Crystal oscillator drift in LoRa nodes: 8.36 ppm (SF7) to 170.33 ppm (SF12)
- Higher spreading factor (longer range) = worse clock drift = bigger sync problem
- Used IEEE 1588 PTP-style master/slave sync packets over LoRa
- Dismissed GPS as “impractical” based on cost and size assumptions
Their data validates the problem statement perfectly. At SF12, 170ppm drift means nodes drift apart by 170 microseconds per second — coordinated transmission is impossible without external synchronization. Their solution (PTP sync packets over LoRa) works but eats bandwidth for synchronization overhead.
GPS PPS uses zero network bandwidth for timing. The synchronization signal comes from space, not from the mesh itself. Every byte of channel capacity is available for actual data.
The economics that made them dismiss GPS have changed. $2 modules. Sub-centimeter packages. 25mA power draw. The paper’s conclusion was sound in 2023. It’s obsolete in 2026.
Vendor-agnostic, by physics
Every existing GPS-synchronized wireless system implements synchronization as a proprietary layer. You cannot sync a Cambium AP with a Ubiquiti AP. Operators running mixed-vendor towers have been complaining about this for years.
Edge Orbital Sync synchronizes to GPS PPS directly. Not to a vendor’s interpretation of GPS PPS. Not to a proprietary frame counter derived from GPS. To the physical signal — the electrical pulse that arrives every second from the atomic clocks in orbit.
Any LoRa radio — Semtech SX1276, SX1262, LLCC68, whatever comes next — paired with any GPS receiver that outputs PPS can participate. The synchronization source isn’t firmware. It’s physics.
Patent filing. Three filings, 82 claims, including Non-Provisional CIP Application #19/553,084 — “GPS-Synchronized Time-Division Multiple Access Systems and Methods for Multi-Band Mesh Networks Including Orbital and Cislunar Relay Applications.” The implementation is protected. The principle is physics.
What this means for the human mesh
Every time the wireless industry has hit a density wall, the answer has been the same: synchronized time division.
WISPs hit PTMP congestion → Cambium solved it with GPS-sync TDD.
MikroTik refused to add GPS sync → operators migrated away.
Cellular needed coordinated spectrum → TDD with GPS sync became the global standard.
5G mandated ±1.5µs GPS sync across every base station on earth.
Open mesh radio is hitting that same wall right now. The protocol layer Abramson designed for a handful of terminals in Hawaii doesn’t scale to thousands of nodes in a city.
The fix isn’t smarter routing or faster presets or reduced telemetry. Those are optimizations within a broken paradigm. The fix is the same thing every other wireless layer already uses.
GPS modules cost $2. The PPS signal is free. The physics works.
The wireless industry spent 20 years locking synchronized timing into proprietary silos. We built it on physics — because the human mesh, the people you already trust to notice, deserves an infrastructure layer that holds when the cellular layer doesn’t.
The first deployment target is critical-infrastructure monitoring — substation perimeters, BESS facilities, rural electric cooperative distribution feeders. The places where reliable comms matter most are the places where cellular does not reach. Read the thesis.
If you want to follow this work: edgeorbital.io. If you want to argue about the math: @TheCJWolff on X.