Hardware & Mesh.

Route Cost & AutoInterface.

In a mixed-bearer environment, the mesh gateway must constantly decide whether to send a packet over a fast but incredibly expensive satellite link (Iridium), a fast but short-range cellular link (LTE), or a slow but completely free sub-GHz RF link (LoRa).

OMEGA utilizes a highly customized route-scoring algorithm that dynamically weighs Route Cost (the financial or bandwidth penalty of the transmission) against Route Weight (the physical latency or topological distance of the hop). The Python mesh router ranks every physical interface mapped to a target node.

Operational Use: For local mesh clustering, OMEGA implements a Reticulum-inspired AutoInterface. When a new edge node or Buoy is powered on, it immediately begins broadcasting UDP multicasts over its active hardware interfaces. Nearby nodes intercept these multicasts, extract the cryptographic public key, and instantly map a valid route to the new node without requiring a human to statically assign an IP address. It is true, zero-configuration networking in the field.

The Envelope Protocol v1.0 vs Binary TLV.

A major design decision in OMEGA was determining how to balance massive hardware heterogeneity (satellites, cell modems, LoRa radios, acoustic modems) with extreme bandwidth constraints. The solution is a dual-layer protocol architecture.

The Air Interface (Layer 1): Over 900MHz LoRa, every byte is expensive. Standard formats like CBOR, MessagePack, and Cayenne LPP carry too much structural overhead (~150B per frame). So, OMEGA uses a Custom Mesh Binary TLV Protocol. This drops the payload to 84B, requires zero external firmware parsing libraries, and enables trivial relay paths where intermediary nodes simply bump a single hop_count byte without deserializing the payload.

The Federation Interface (Layer 2): When that 84B binary packet hits a gateway, it is instantly translated into the OMEGA Envelope Protocol v1.0. This is a self-describing, globally standard format (using Canonical UTF-8 JSON or SenML CBOR for constrained IP bearers). Because "identity and meaning travel with the data", external databases, web portals, and federated science platforms never need to know the raw binary structure of the mesh. The Envelope Protocol ensures that a reading from a LoRa node and a reading from a NATO JANUS acoustic buoy look exactly the same to the backend.

IEEE 802.11ah HaLow IP Backhaul.

LoRa is a great telemetry bearer but a poor IP pipe. To give the fleet an optional higher-throughput backhaul link, OMEGA has a companion-firmware architecture for 802.11ah (HaLow) on T-HaLow ESP32-S3 boards. HaLow here is strictly an IP backhaul between a node and shore — it is not a mesh bearer, and it is not intended for video.

Status — designed, not yet brought up: the build flags below configure one side as an ap-root and the peer as an sta-client to form a sub-GHz TCP/IP link. On the hardware, the HaLow radio (the TX-AH module) runs its own firmware and is driven over SPI by the host ESP32; that SPI path is not yet implemented, so bring-up is pending the vendor hardware. The companion firmware and its peering configuration exist on paper and in the build, but no live HaLow link has been stood up yet.

Meshtastic & MeshCore Bridging.

OMEGA does not reinvent the wheel. It ships a runnable Meshtastic bridge built on the official Meshtastic Python SDK — bidirectional, over both serial and TCP, and tested against real radios — alongside a MeshCore mesh-interface framework for the same role.

The intent is that of a last-resort bearer: if operators already have Meshtastic or MeshCore radios in the area, the OMEGA gateway can serialize its outbox payloads and piggyback them across that existing mesh. Crucially this is reciprocal — OMEGA also forwards the host mesh's own traffic in return, so it behaves as a good airtime citizen rather than a free rider on someone else's network.

Cloud CGNAT Tunneling.

Field operations often rely on marine cellular routers, which are trapped behind massive Carrier-Grade NAT (CGNAT) firewalls. The scripts/tunnel-up.ps1 daemon automates the execution of Cloudflared or Ngrok. It securely punches a reverse TCP tunnel from the edge node gateway out to the public internet, securely exposing the local React Mission Portal to oceanographic teams thousands of miles away.

Cloud-to-Node Command Architecture.

In Phase 1, edge nodes were purely telemetry broadcasters. With the new binary protocol, OMEGA implements a fully bidirectional mesh. The shore gateway can now construct binary COMMAND frames and route them over the mesh directly to specific nodes.

Execution: By injecting a dest_id into the binary header, commands like restart, set-telemetry-interval, or set-tx-power are routed across the ocean. Intermediary nodes receive the packet, check the destination, and automatically re-transmit (relay) the packet if it is not meant for them. This creates a true, self-healing bidirectional mesh network.

Hardware PA Clamping & RX Boost.

Achieving absolute maximum range requires hardware-level tuning of the silicon. OMEGA firmware interfaces directly with the Semtech SX126x radio registers to bypass standard defaults.

Execution: The firmware enables RxBoostedGainMode, physically increasing the Low-Noise Amplifier (LNA) gain by ~3 dB at the cost of ~2 mA extra RX current. For short-duty mesh nodes, this provides a massive mathematical advantage, allowing them to decode marginal cross-family packets that previously failed at the noise floor. Concurrently, internal Power Amplifiers (PA) are strictly clamped at +22 dBm to prevent silicon burnout when driving external 1-Watt High Power Amplifiers (HPA).

DTN Command Versioning.

Uplink telemetry is inherently order-independent, but bidirectional downlink commands (like telling a node to change its transmission power) are stateful. In a store-and-forward network, a delayed command might arrive at a node days after a newer command was already applied.

The Newest-Wins Rule: OMEGA solves this by enforcing declarative, versioned commands. Every command carries a monotonic operator version and a target key. The node tracks the applied version per-key in Non-Volatile Storage (NVS). When a command arrives, it only executes if cmd.version > applied[key]. Older arrivals are instantly dropped as stale, completely eliminating rollback issues under extreme packet loss or reordering.

CSMA-CA Collision Avoidance.

When deploying 50+ floating sensor nodes in a small coastal bay, transmitting simultaneously on the 915MHz LoRa band guarantees catastrophic packet collisions. OMEGA firmware implements low-level Carrier Sense Multiple Access with Collision Avoidance (CSMA-CA).

Execution: Before any node fires a transmission, it drops its SX1262 transceiver into CAD (Channel Activity Detection) mode. The silicon mathematically scans the physical RF spectrum for existing LoRa preamble chirps. If the channel is active, the node backs off for a randomized exponential interval (slotted ALOHA). This decentralized coordination allows dense mesh networks to self-regulate without a master polling node.

Snell's Law & Refraction.

Standard radio frequencies cannot penetrate water. The NATO-standard JANUS protocol (STANAG 4748) is the intended way to reach Remotely Operated Vehicles (ROVs) and benthic sensors. The physics below is why acoustic links are hard; the OMEGA side of it is currently a message format and a software bridge, not an on-device modem.

Where OMEGA actually sits: sound travels at ~1,500 m/s underwater, subject to heavy multi-path and thermocline refraction, and JANUS uses Frequency-Shift Keying (FSK) to carry data over that channel. OMEGA does not do the FFT wakeup detection, PLL synchronization, or FSK demodulation itself. Instead, janus_bridge.py defines the JANUS message format and forwards JANUS JSON to and from an external acoustic / SDR modem, which owns the real DSP. The bridge's job is translating those messages onto the LoRa mesh — there is no on-device signal processing.

JANUS Initialization.

Because underwater acoustic physics are incredibly hostile, bandwidth is severely limited—often maxing out at a mere 80 bits per second (bps). Therefore, OMEGA cannot stream complex JSON over a hydrophone.

How it works: The JSON structure below represents the source representation of the simulated NATO-standard JANUS initialization frame before it undergoes SenML CBOR serialization per the Envelope Protocol v1.0 specifications. The payload explicitly defines the center_frequency_hz and the rx_level_db. The Gateway crushes this into a binary string and uses it to align the hydrophone's physical oscillator. Once aligned, the actual data transferred via the acoustic bridge is strictly limited to heavily compressed initialization vectors and critical emergency stop commands, preserving the fragile acoustic channel.