Category: EHN Blog

  • Bridging Encrypted Networks to Amateur Radio: A Necessary Constraint, Not a Limitation

    Bridging Encrypted Networks to Amateur Radio: A Necessary Constraint, Not a Limitation

    Introduction

    One of the most interesting—and challenging—problems in building the EmergencyHam.Net architecture is not technical at all.

    It’s regulatory.

    As we begin to explore bridging modern encrypted communication systems—such as mesh networks and mobile messaging—into amateur radio, we run into a fundamental rule:

    Amateur radio transmissions must not obscure their meaning.

    At first glance, this might seem like a limitation. But in reality, it forces a deeper and more important question:

    How do we responsibly connect modern, private communication systems with open, regulated radio networks?


    The Real Problem Isn’t Encryption—It’s Meaning

    It would be easy to say:

    “We’ll just decrypt the message and send it.”

    But that’s not enough.

    A decrypted message could still be:

    • encoded
    • obfuscated
    • machine-generated
    • or deliberately structured to hide its meaning

    So the real requirement is stronger:

    Only forward messages into the ham network when they are clearly intelligible as plain language.

    That’s a very different standard.


    Introducing a New Architectural Component

    Through this discussion, we identified the need for a dedicated part of the system:

    Content Transparency & Compliance

    This is not just another filter—it is a decision point in the architecture.

    It sits between message processing and ham transmission:

    Ingress → EMP Normalize → Identity/Policy → Compliance Gate → Ham Egress

    Its job is simple to describe, but critical to get right:

    • ensure the message can be understood
    • ensure it is attributable
    • ensure it meets policy
    • ensure it is safe to transmit

    What Does “Plain Language” Actually Mean?

    We quickly realized there is no single test for this.

    Instead, we use a layered approach:

    • can the message be decoded into readable text?
    • is it mostly printable characters?
    • does it resemble natural language?
    • does it avoid long random or encoded sequences?
    • can an operator read and understand it?

    This produces a confidence score, not just a yes/no answer.

    👉 This is important:
    We are not trying to “prove” something is safe—we are building enough confidence to act responsibly.


    Automation First, Humans When Needed

    The system is designed to make most decisions automatically, but not blindly.

    Each message falls into one of four categories:

    • PASS — clearly plain language, safe to forward
    • PASS WITH RECORD — forward, but retain full audit record
    • REVIEW REQUIRED — hold for operator decision
    • BLOCK — do not transmit

    This allows the system to scale, while still respecting the role of the control operator.


    Logging Becomes More Than Logging

    This discussion led to an important realization:

    The compliance system is not just a filter—it is an evidence system.

    For any message that crosses into the ham network, the gateway will:

    • log the full plaintext
    • record origin, destination, and path
    • store a compliance decision
    • retain the record for 30 days
    • protect it with encryption and tamper-evident hashing

    This ensures that:

    • decisions can be reviewed
    • misuse can be investigated
    • operators remain accountable
    • the system remains trustworthy

    Local First, Network When Available

    Because EmergencyHam.Net is designed for off-grid use, we cannot depend on central systems.

    So we adopted a simple principle:

    Logs are local and authoritative. Central copies are optional.

    Each gateway:

    • keeps its own secure compliance log
    • continues operating fully off-grid
    • forwards logs to central nodes when connectivity exists

    This gives us:

    • resilience in emergencies
    • visibility when networks are available
    • no single point of failure

    Why This Matters

    This is one of the most important steps in the project so far.

    It moves EmergencyHam.Net from:

    “a system that connects networks”

    to:

    a system that connects networks responsibly

    It also addresses a key concern anyone will have when reviewing the architecture:

    • Can this be misused?
    • Can it be trusted?
    • Can it operate within existing regulations?

    By designing for compliance from the beginning, we avoid having to retrofit it later.


    Looking Ahead

    This is just the first version.

    Future work will include:

    • refining plaintext confidence scoring
    • improving operator review tools
    • defining key management for logs
    • correlating logs across multiple gateways
    • integrating compliance decisions into routing

    Final Thought

    It’s easy to focus on radios, protocols, and networks.

    But systems like this ultimately succeed or fail based on trust.

    This work is about building that trust—into the architecture itself.


    👉 If you’re interested in helping shape this work, review the documents or join EmergencyHam.Net as a founding member.

  • From Idea to Reality: EmergencyHam.Net Starts to Take Shape

    From Idea to Reality: EmergencyHam.Net Starts to Take Shape

    When we first talked about EmergencyHam.Net, it was very much an idea.

    A good one, we thought—but still just an idea.

    Could you take all these different ways people communicate—radios, mesh networks, phones, and the internet—and make them work together in a simple, reliable way? Especially when systems aren’t behaving the way they normally do?

    That was the question.

    Over the past few weeks, things have started to shift from “what if” to “this might actually work.”


    A Small Build That Changed Everything

    One of the first things we built was simple on the surface:

    A bridge between SMS and a mesh radio network.

    No big framework. No complex infrastructure. Just a way to take a text message from a phone, push it into a radio-based network, and return the reply.

    But once it was working, something clicked.

    You could send a message like:

    “Need supplies at checkpoint”

    …and it would travel through a completely different kind of network—one that doesn’t depend on cellular or internet infrastructure.

    When the reply came back, it appeared on the phone like any other text.

    No special apps. No explanation needed.

    That’s when it stopped being theoretical.


    Stepping Back to See the Bigger Picture

    After that, we paused and asked a bigger question:

    What are we actually building?

    Instead of continuing piece by piece, we documented the system as a whole—creating a structured, versioned design.

    At a high level, it comes down to three ideas:

    • Messages are addressed to people or locations, not devices
    • The system determines how to deliver them
    • Different networks should work together naturally

    A Simple Way to Think About It

    Every message starts somewhere—a person, a sensor, or a system.

    It’s addressed to a destination:

    “Send this to CLINIC01”

    Each step in the network doesn’t need full awareness of the path.

    It simply asks:

    • “Is this for me?”
    • If not: “Where should this go next?”

    The message continues moving until it reaches its destination.


    Where It Gets Interesting

    This model changes how you think about communication.

    You don’t need to decide in advance whether a message will travel over:

    • radio
    • mesh
    • internet
    • SMS

    The system handles that dynamically.

    And more importantly:

    The user doesn’t need to care.

    They just send the message.


    What We’re Building Next

    We now have:

    • A working prototype (SMS ↔ mesh bridge)
    • A defined architecture

    The next step is bringing those together into a more structured system.


    A More Structured Mesh Layer

    We’re exploring how this could run on platforms like MeshCore, with additional structure layered on top.

    The goal is to move from:

    “Messages happen to get through”

    to:

    “Messages are handled in a consistent, predictable way”


    Connecting to APRS

    APRS has proven its value over decades.

    We’re looking at how to integrate with it in a way that:

    • Respects how it’s used today
    • Enables more structured data alongside traditional messaging

    Looking at Winlink

    For longer messages and store-and-forward communication, Winlink provides another important path.

    It operates differently—but fits naturally into the same overall architecture.


    Where This Is Heading

    This didn’t start as something this broad.

    But piece by piece, it’s becoming clear:

    This isn’t about one network.

    It’s about making all of them easier to use together.


    Still Early—But Real

    There’s still a lot to figure out.

    But we now have:

    • A working prototype
    • A defined architecture
    • A clear path forward

    And that’s real progress.


    From Concept to Controlled Architecture

    As the pieces started to come together, it became clear that this needed more than notes or diagrams—it needed a defined structure.

    We’ve now captured the current system design in a formal, versioned document:

    EmergencyHam Full-Stack Summary (v0.2)

    This document represents the current controlled architecture of the system.

    It defines:

    • What is already stable and agreed
    • How messages are structured and routed
    • How different networks interoperate
    • Which areas still need refinement

    At its core, it confirms that EmergencyHam is built around:

    • Identity-based communication (people and locations, not devices)
    • A consistent message format across all networks
    • A hop-by-hop routing model
    • A layered architecture separating applications, messaging, and transport

    Just as importantly, it also identifies the open areas—routing intelligence, delivery behavior, trust models, and operational policy—that will shape the next phase of development.

  • Bridging Meshtastic to SMS/RCS

    Bridging Meshtastic to SMS/RCS

    A Meshtastic ↔ Phone SMS/RCS Gateway (Now Working)

    One of the first questions people ask when they discover Meshtastic is:

    “This is great… but how do I message someone who isn’t on the mesh?”

    We now have a working answer.

    We’ve built a Meshtastic ↔ Android SMS/RCS gateway, and it’s already proving to be both useful—and honestly, pretty fun.


    Why This Matters

    Meshtastic is incredibly powerful:

    • long-range
    • low power
    • infrastructure-independent

    But it has one real-world limitation:

    👉 Everyone needs to be on the mesh

    That’s fine for enthusiasts.
    Not so much for:

    • friends and family
    • local volunteers
    • the people you actually need to reach

    This gateway bridges that gap.

    Now you can:

    • send a message from the mesh
    • deliver it as a normal phone text (SMS or RCS)
    • receive replies back into the mesh

    How It Works (Simple, On Purpose)

    👉 Your contacts don’t need an app.
    👉 They don’t need a node.
    👉 They just text like normal.

    The gateway runs on an Android phone, connected via USB to a Meshtastic device running standard firmware.

    From there:

    • Incoming SMS/RCS messages are read by the phone
    • Converted into Meshtastic messages
    • Injected into the mesh
    • Mesh messages are received and sent back out as texts

    So your phone becomes a bridge:

    Phone (SMS/RCS) ↔ Gateway App ↔ USB ↔ Meshtastic Node ↔ Mesh Network


    Message Routing Options

    There are two practical ways to use it, depending on your setup:

    Shared Channel Mode

    • Messages from multiple contacts go into a shared (private) Meshtastic channel
    • Each message is tagged with a short name
    • Works well for group-style communication

    To reply:

    jackie - got it, heading over

    Simple, but effective.


    Direct / Dedicated Mode

    • A single contact maps to a specific private channel
    • Feels more like one-to-one messaging
    • No prefix needed when replying

    Tradeoffs:

    • More natural to use
    • Limited by Meshtastic channel count
    • Slightly more setup required

    The Short Name Trick (Surprisingly Important)

    SMS and RCS don’t identify people consistently:

    • SMS → phone numbers
    • RCS → long or changing names

    That gets messy fast.

    So the gateway maps each sender to a short name:

    • +12013417589 → jr
    • Johnathan M. Rodriguez (Work) → jr

    Now replies are fast and reliable:

    jr - ok, moving now

    This turns out to matter a lot—especially under pressure.


    What It Feels Like in Practice

    Reach Anyone

    You send:

    mom - running late, all good

    It goes over LoRa → hits the gateway → arrives as a normal text.

    The reply comes right back into the mesh.

    Here are a couple of screen captures showing the Meshtastic and phone screens.


    Web Client View of SMS Conversation
    Android Phone View of the SMS Conversation

    Extend Your Network (No Hardware Required)

    You can include people who don’t have:

    • a node
    • a radio
    • any special software

    That’s a huge usability win.


    EmergencyHam Use Case

    This ties directly into the bigger picture:

    • A sensor or operator sends an alert over the mesh
    • The gateway forwards it as a phone message
    • A response comes back into the system

    Simple. But powerful.


    Under the Hood (Without Getting Scary)

    It looks simple from the outside.

    Inside, there’s some real work happening:

    • message parsing and normalization
    • identity mapping
    • SMS vs RCS handling
    • routing logic
    • retry and delivery behavior

    The goal wasn’t just to make it work—but to make it:

    • predictable
    • usable under stress
    • easy to extend

    This is also the first step toward something bigger:

    👉 a common message model across multiple networks


    Why This Is Actually Fun

    This isn’t just emergency comms.

    It’s also:

    • a great experiment platform
    • a way to extend your local mesh
    • a way to show others what Meshtastic can do

    There’s something very satisfying about sending a LoRa message… and watching it land as a normal text.


    Looking for Alpha Testers

    This is working—but still early.

    We’re looking for people who want to help test and shape it.

    Ideal testers:

    • already using Meshtastic
    • have an Android phone available
    • comfortable experimenting
    • willing to give honest feedback

    What we want to learn:

    • usability
    • edge cases
    • reliability
    • real-world behavior

    What Comes Next

    This gateway is just the beginning.

    Planned next steps:

    1. Improve message handling and UI flow
    2. Add MeshCore support
    3. Introduce structured messaging (EMP V1)
    4. Bridge into APRS and Winlink

    The long-term goal:

    👉 interoperable messaging across multiple networks


    Closing Thought

    This started as a simple idea:

    “What if Meshtastic could text a phone?”

    Turns out, that opens the door to something much bigger:

    • connecting isolated networks
    • enabling real, usable traffic
    • building systems that still work when infrastructure doesn’t

    If that sounds interesting—we’d love your help testing it.


    👉 Get Involved

    Reach out via EmergencyHam.net if you’d like to be part of early testing.

  • Experimentation, Not Circumvention

    Experimentation, Not Circumvention

    Why Amateur Radio Needs Real Traffic, Not Just Emergency Drills

    When people first hear about EmergencyHam.net, a natural question arises:

    “Is this trying to turn amateur radio into a messaging network?”

    The short answer is no.

    EmergencyHam exists for a much more traditional amateur radio reason: experimentation and education.


    Amateur Radio Has Always Been About Experimentation

    The Amateur Radio Service was created not just for communication, but for technical exploration and operator training.

    The FCC’s own statement of purpose (§97.1) highlights several goals:

    • advancement of the radio art
    • training of operators and technicians
    • development of new communication techniques
    • enhancing emergency communications capability

    From spark transmitters to packet radio, APRS, satellites, and modern digital modes, amateur radio has always advanced through experimentation.

    EmergencyHam simply continues that tradition by exploring how amateur radio can interact with modern sensor networks and digital systems.


    A New Generation of Technology

    Students today learn electronics and programming through:

    • microcontrollers and embedded systems
    • environmental sensors
    • wireless networks
    • IoT platforms

    Yet most of these projects depend entirely on internet infrastructure.

    EmergencyHam explores a simple but important question:

    What happens to these systems when the internet disappears?

    By connecting student-built sensors to amateur radio relay stations, students can see how resilient communications networks actually work.

    They learn about:

    • RF propagation
    • digital modes
    • network reliability
    • responsible spectrum use

    And they do so with the guidance of experienced amateur radio operators.


    Why Amateur Radio Needs Real Traffic, Not Just Emergency Drills

    One of the challenges facing emergency communications systems today is that they are rarely used under real conditions.

    Emergency nets and drills are valuable, but they often simulate traffic rather than carrying meaningful information. Systems that are not used regularly can develop hidden weaknesses that only appear during real emergencies.

    EmergencyHam addresses this by creating regular, legitimate traffic in the form of:

    • environmental telemetry
    • weather data
    • air quality monitoring
    • simple operational messages

    This kind of everyday traffic keeps systems exercised, operators engaged, and infrastructure tested.

    When an actual emergency occurs, the network is already functioning.


    Not a Messaging Service

    It is important to be clear about what EmergencyHam is not.

    The project is not intended to:

    • replace commercial messaging systems
    • provide a public communications service
    • create encrypted data networks on amateur bands

    Instead, the focus is on experimental telemetry and limited structured messaging within the amateur service.

    All transmissions remain consistent with amateur radio regulations and operating practices.


    Designed with Regulatory Awareness

    From the beginning, the system has been designed to respect the rules and traditions of the Amateur Radio Service.

    Key safeguards include:

    • All transmissions on amateur bands are plain text and human readable
    • No encryption is used on amateur frequencies
    • Relay stations operate under licensed control operator oversight
    • Messages are logged and auditable
    • Traffic policies prevent use as a general-purpose messaging service

    These safeguards ensure the system remains consistent with the principles of amateur radio while still allowing meaningful experimentation.


    Learning by Building Real Systems

    One of the most powerful aspects of the project is its educational value.

    Students who build environmental sensors and deploy them as part of EmergencyHam gain hands-on experience with:

    • electronics and embedded systems
    • wireless networking
    • RF communications
    • data systems and telemetry

    At the same time, experienced operators mentor them in the practical aspects of radio communication.

    This creates a true intergenerational exchange of knowledge.


    Looking Forward

    EmergencyHam is not presented as a finished system.

    It is an open experiment exploring how amateur radio can continue to evolve in an IoT-enabled world.

    By creating real technical collaboration between students, makers, and experienced operators, the project aims to demonstrate that amateur radio remains a relevant and powerful platform for experimentation, learning, and community resilience.

    Because amateur radio’s greatest strength has always been the willingness of its operators to explore new ideas.

    And that spirit of experimentation is what will carry the service forward.

  • Building a Resilient Emergency Messaging Bridge

    Building a Resilient Emergency Messaging Bridge

    When communication systems fail during an emergency, it’s rarely because everything stops working at once. More often, individual pieces break down: cellular networks become overloaded, internet backhaul disappears, or power becomes unreliable.

    The lesson learned from decades of emergency communications is simple:

    Resilience comes from layered systems, not a single perfect tool.

    At EmergencyHam.net we are experimenting with a practical messaging bridge architecture that connects local mesh radio networks, amateur radio messaging systems, and everyday devices such as smartphones.

    The goal is straightforward: allow messages and telemetry to move across whatever networks remain available.


    A Layered Communication Model

    Instead of building a single monolithic communications system, the EmergencyHam gateway acts as a message exchange point between multiple networks.

    These networks may include:

    • Meshtastic LoRa mesh
    • MeshCore LoRa mesh
    • Phone text messaging (SMS-style interfaces)
    • APRS messaging
    • Winlink store-and-forward email

    Each network connects through an adapter that translates between its native format and a common internal message structure called EMP (Emergency Message Protocol).

    EMP provides a unified message model that allows different communication subsystems to interoperate by exchanging a limited set of common message types, independent of the specific requirements or limitations of any individual network.

    Rather than attempting to reproduce the full capabilities of every system, EMP focuses on the small set of message behaviors that can be shared across them all.

    This design allows traffic to move between networks depending on availability, priority, and delivery requirements.


    EMP as the Interoperability Layer

    EMP is intentionally minimal.

    It defines only the message primitives needed to support interoperable communications across heterogeneous networks.

    In that sense, EMP plays a role similar to other foundational interoperability layers:

    • IP unified many different physical network technologies
    • SMTP allowed email systems to exchange messages
    • MQTT enables distributed message systems to communicate through simple publish/subscribe semantics

    EMP applies the same principle to emergency communications.

    Instead of tying applications to a specific radio technology, EMP represents message intent.

    For example, a simple “wellness check” or “sensor alert” can be represented as a standard EMP message. Each network adapter then translates that intent into its own native format.

    This approach allows new communication systems to be added without redesigning the application layer.


    Development Roadmap

    Rather than trying to connect every communications system at once, the bridge is being built in stages.

    Phase 1 — Meshtastic and Phone Messaging

    The first stage links Meshtastic mesh messaging with simple phone text messaging.

    Both transports connect to the gateway through EMP adapters.

    The gateway:

    1. Receives a message from Meshtastic
    2. Converts it into an EMP frame
    3. Routes it to the phone messaging adapter
    4. Sends responses back through the mesh

    Importantly, the phone interface is not simply a user console for the mesh.

    It is treated as another network transport operating at the same EMP level.

    This phase validates the core EMP message model and routing logic.


    Phase 2 — MeshCore Integration

    The second stage introduces support for MeshCore mesh networking.

    Adding MeshCore demonstrates that the system can support multiple mesh ecosystems simultaneously.

    Messages from either mesh network can be normalized into EMP frames and routed across other available transports.


    Phase 3 — Amateur Radio Messaging Systems

    Once the mesh adapters are stable, the next step is connecting to established amateur radio messaging systems such as:

    • APRS messaging
    • Winlink email relay

    These networks provide long-distance store-and-forward capability, allowing information originating on a local mesh network to travel beyond the immediate radio coverage area.


    Practical Examples

    Two simple examples illustrate how this layered messaging model might work in practice.

    Wellness Check

    During emergency operations or public service events, maintaining awareness of team status is essential.

    A simple workflow might look like this:

    • Field operators send periodic check-in messages over a mesh network.
    • The gateway tracks acknowledgements from command stations.
    • If several check-ins are missed, the system generates an escalation alert.

    Routine traffic remains lightweight, while the system still provides accountability and exception awareness.


    Water Leak Alert

    Sensors provide another valuable application.

    For example, a water leak sensor deployed in a remote building might trigger an alert when a leak is detected.

    • The sensor sends a telemetry message across the local mesh network.
    • Nearby operators receive immediate notification.
    • The gateway can later forward a richer incident report through long-distance messaging systems such as Winlink.

    This combination provides fast local awareness with resilient escalation paths.


    Educational Value

    One of the primary goals of EmergencyHam.net is hands-on learning.

    Projects like this allow students and new operators to explore multiple technical disciplines at once:

    • radio communications
    • networking and distributed systems
    • embedded electronics and sensors
    • software development
    • resilient system design

    A student might deploy a sensor, watch its telemetry move across a LoRa mesh network, pass through a gateway, and appear on a remote dashboard.

    At the same time, experienced amateur radio operators can mentor students on:

    • propagation and antenna design
    • interference mitigation
    • operating practices
    • regulatory considerations

    This kind of intergenerational collaboration is central to the EmergencyHam.net mission.


    The EMP V1 Protocol

    The technical details of the EMP messaging model are described in the EmergencyHam Message Protocol (EMP) V1 Draft.

    EMP defines:

    • compact message frames for low-bandwidth radio links
    • structured message types such as TXT, CMD, ACK, and TLM
    • duplicate suppression and retry behavior
    • fragmentation rules for larger messages

    EMP is designed to be simple enough for embedded systems while still supporting reliable communication workflows.

    The full draft specification is available here:

    EmergencyHam Message Protocol (EMP) V1 Draft


    Why This Matters

    Emergency communications shouldn’t depend on a single network or technology.

    They should be built from interoperable layers that support each other.

    By connecting mesh networks, amateur radio systems, and everyday devices like smartphones through a common messaging model, we can create systems that remain useful even when normal infrastructure fails.

    Just as importantly, we can use these systems to teach the next generation how resilient communications actually work.


    Get Involved

    If you are interested in:

    • reviewing the EMP protocol
    • developing gateway software
    • experimenting with mesh networks
    • field testing sensors and telemetry

    we would welcome your input.

    EmergencyHam.net is built through collaboration between radio operators, developers, educators, and makers.

  • Turning a Salvaged Dash‑Cam GPS into a Precision Off‑Grid Time Source (FT8 Ready)

    Turning a Salvaged Dash‑Cam GPS into a Precision Off‑Grid Time Source (FT8 Ready)

    Introduction

    When operating off‑grid — whether portable, emergency, or simply disconnected from the internet — accurate system time becomes a real problem.

    Digital modes like FT8 require your computer clock to be within approximately ±1 second of UTC (ideally ±0.5 seconds). Consumer laptops, when disconnected from network time sources, can drift several seconds per day. Over weeks, that drift becomes catastrophic for digital decoding.

    This project documents how a salvaged Street Guardian dash camera GPS module was repurposed into a reliable, infrastructure‑independent UTC time source for Windows 11.

    This article covers:

    • Hardware reuse and wiring
    • Real measured drift results
    • Python time comparison tool
    • Smart GPS sync utility
    • Practical off‑grid workflow
    • Lessons learned

    Why GPS is Ideal for Off‑Grid Timing

    GPS offers:

    • Passive reception (no license required)
    • True UTC derived from atomic standards
    • No dependence on internet or cellular networks
    • Consistent accuracy worldwide

    Unlike WWV or WWVB, GPS requires no HF propagation or LF antenna challenges. It simply works.


    Hardware Used

    GPS Module

    • Salvaged Street Guardian dash camera GPS puck
    • Outputs standard NMEA 0183
    • Default baud rate: 9600 8N1
    • Uses 2.5 mm TRS (3‑conductor) plug
    • Supply voltage: 3.3V

    Alternate Hardware Option (Simple USB GPS)

    If you do not want to build a TRS-to-UART interface, a USB-terminated GPS receiver is a practical alternative.

    • Typical cost: about $12 USD on Amazon (varies by seller and chipset)
    • Usually presents as a serial COM port on Windows
    • Common output: NMEA 0183 ($GPRMC / $GNRMC, etc.)
    • Often works at 9600 baud, but verify in Device Manager/vendor docs

    For this project, either hardware path is valid as long as UTC sentences are available on a COM port.

    USB‑UART Adapter

    • FTDI / CP2102 / CH340 compatible
    • 3.3V logic preferred
    • Only RX required (GPS → PC)

    Pinout Discovery

    Testing revealed:

    • Tip = 3.3V supply
    • Ring = UART TX (GPS data output)
    • Sleeve = Ground

    Confirmed by:

    1. Measuring ~3.3V on tip
    2. Reading valid NMEA at 9600 baud
    3. Observing stable serial output

    UART output is push‑pull. No pull‑ups required.


    Hardware and Run Captures

    Salvaged hardware setup

    GPS with USB interface example

    Batch run screen capture


    Verifying NMEA Output

    At 9600 baud the module outputs:

    • $GPGGA
    • $GPRMC
    • $GPGSA
    • $GPVTG

    Before satellite lock:

    $GPGGA,,,,,,0,00,99.99,,,,,,*48
    $GPRMC,,V,,,,,,,,,,N*53
    

    After lock, $GPRMC status changes to A and UTC time/date populate.


    Measured Drift: Real‑World Results

    After the laptop was powered off for approximately three weeks, the comparison script reported:

    GPS UTC: 2026-02-26T22:20:38+00:00
    SYS UTC: 2026-02-26T22:18:19.788402+00:00
    SYS-GPS: -138.212 s
    

    The system clock was 138 seconds slow.

    Drift calculation:

    138 seconds / 21 days ≈ 6.5 seconds/day (~75 ppm)

    This is entirely believable for consumer laptop RTC crystals.


    After Network Time Sync

    After running:

    w32tm /resync
    

    New comparison:

    GPS UTC: 2026-02-26T22:24:11+00:00
    SYS UTC: 2026-02-26T22:24:11.155475+00:00
    SYS-GPS: +0.155 s
    

    Typical post‑sync offset:

    +0.14 to +0.16 seconds

    This residual difference is normal NMEA and USB latency and is well within FT8 tolerance.


    Simple Comparison Script

    Install dependency:

    pip install pyserial
    

    gps_time_compare.py

    import sys
    import datetime as dt
    import serial
    
    def parse_gprmc(line):
        if not line.startswith("$GPRMC"):
            return None
        parts = line.split(",")
        if len(parts) < 10 or parts[2] != "A":
            return None
        t_str = parts[1]
        d_str = parts[9]
    
        hh = int(t_str[0:2])
        mm = int(t_str[2:4])
        ss = int(t_str[4:6])
    
        dd = int(d_str[0:2])
        mo = int(d_str[2:4])
        yy = int(d_str[4:6])
        year = 2000 + yy
    
        return dt.datetime(year, mo, dd, hh, mm, ss, tzinfo=dt.timezone.utc)
    
    port = sys.argv[1]
    ser = serial.Serial(port, 9600, timeout=1)
    
    while True:
        line = ser.readline().decode(errors="ignore").strip()
        gps_dt = parse_gprmc(line)
        if gps_dt:
            sys_dt = dt.datetime.now(dt.timezone.utc)
            offset = (sys_dt - gps_dt).total_seconds()
            print(f"SYS-GPS: {offset:+.3f} seconds")

    Smart GPS Sync Utility

    The current gps_time_sync.py workflow:

    • Accepts serial port as positional value (COM10) or --port COM10
    • Waits for valid RMC fix (GPRMC not valid yet... message)
    • Calculates and displays UTC offset
    • Warns when offset exceeds --warn
    • Syncs only when offset exceeds --sync-threshold

    Example:

    python gps_time_sync.py COM10 --warn 0.35 --sync-threshold 0.75
    

    Use --dry-run to measure/verify without changing the system clock.


    Windows Batch Launcher + Admin Shortcut

    The included launcher:

    • Run_GPS_Time_Sync.bat

    Current command in the batch file:

    python gps_time_sync.py COM10 --warn 0.35 --sync-threshold 0.75
    

    Because Windows time set operations require elevation, create an administrator shortcut:

    1. Right-click Run_GPS_Time_Sync.bat → Create shortcut
    2. Right-click the shortcut → Properties
    3. Select Advanced…
    4. Enable Run as administrator
    5. Use that shortcut for normal operation

    This keeps operating workflow simple and repeatable before FT8 sessions.


    Practical Off‑Grid Workflow

    1. Power GPS module
    2. Wait for satellite lock
    3. Run sync script
    4. Confirm offset < ±0.2 s
    5. Start FT8

    No internet required.


    Lessons Learned

    • Consumer laptop RTCs drift more than many operators expect.
    • GPS NMEA timing is extremely stable for amateur digital work.
    • Windows NTP sync is accurate, but unavailable off‑grid.
    • A simple script is sufficient — no service or daemon required.
    • Manual execution before operating is practical and reliable.

    Conclusion

    This project demonstrated:

    • Real‑world RTC drift of ~6 seconds/day
    • GPS provides atomic‑referenced UTC
    • Windows post‑sync offset ~0.15 seconds
    • Off‑grid discipline is straightforward
    • No license required
    • No complex hardware needed

    For portable or emergency FT8 operation, this solution is inexpensive, elegant, and robust.

    Full code and instructions at emergencyhamnet/gps-offgrid-time-sync: Using a salvaged dash-cam GPS module as an off-grid UTC time source for Windows (FT8 ready).

  • Local Wi-Fi Information Nodes: A Simple Tool for Community Communication

    Local Wi-Fi Information Nodes: A Simple Tool for Community Communication

    A Practical, Educational Tool for Community Resilience

    When large-scale communications fail, people don’t stop needing information — they just lose access to it. In many emergency scenarios, cellular networks and internet connectivity become unreliable or unavailable, leaving communities with few ways to share updates, instructions, or basic status information.

    One promising approach to this challenge is surprisingly simple: local Wi-Fi information nodes.


    What Is a Local Wi-Fi Information Node?

    A local Wi-Fi information node is a small, self-contained station that broadcasts a local Wi-Fi network and hosts a simple web server. Anyone nearby with a Wi-Fi-enabled device — a phone, tablet, or laptop — can connect and access information using a standard web browser.

    No internet connection is required.
    No apps need to be installed.
    No accounts are needed.

    The experience is intentionally simple: connect to the network, open a browser, and view the available information.


    Why Wi-Fi Works When Other Systems Don’t

    Modern smartphones and computers are extremely capable, but they depend heavily on centralized infrastructure. When that infrastructure fails, their built-in radios and browsers still function — they just need something local to connect to.

    Local Wi-Fi nodes take advantage of this reality. As long as the node has power and is within range, it can continue to provide access to information even when wider networks are unavailable.

    This makes Wi-Fi an effective last-meter communication tool during disruptions.


    Information Sharing Without Complexity

    The content hosted on a local Wi-Fi node can be intentionally modest:

    • Situation updates and bulletins
    • Shelter locations and hours
    • Health and safety guidance
    • Maps or static reference material

    In addition to receiving information, users can also submit short text messages or status updates through simple web forms. These might include:

    • “I’m safe” check-ins
    • Requests for assistance
    • Observations about local conditions

    Even limited two-way communication can dramatically improve situational awareness.


    How This Integrates With Amateur Radio

    From an amateur radio perspective, local Wi-Fi nodes serve as access points, not transmitters.

    Devices on the Wi-Fi network operate under license-free rules, while licensed amateur radio operators can supervise the handling and forwarding of appropriate information using established digital modes. This clear separation preserves regulatory compliance while allowing information to move beyond the local area when needed.

    The result is a layered system:

    • Wi-Fi provides simple access for the public
    • Amateur radio provides resilient long-distance transport
    • Control operators ensure responsible use

    This approach respects both technical and regulatory boundaries.


    Strong Educational Value

    Local Wi-Fi information nodes are also powerful teaching tools.

    Students and makers can learn about:

    • Networking fundamentals
    • Client/server models
    • User interface design under constraints
    • Data reliability and prioritization
    • Ethical information handling

    Because the systems are small and understandable, participants can see the entire flow of information — from user input to transmission — rather than working with opaque cloud services.


    Practical, Portable, and Approachable

    These systems can be built using modest hardware:

    • Single-board computers
    • Off-the-shelf Wi-Fi radios
    • Lightweight web servers

    They can be deployed in schools, libraries, community centers, or mobile setups powered by batteries. This portability makes them ideal for both educational exercises and real-world demonstrations.


    Not a Replacement — A Complement

    It’s important to be clear about what local Wi-Fi nodes are not.

    They are not:

    • Emergency call systems
    • Replacements for first responder radio networks
    • Substitutes for cellular or public safety infrastructure

    They are best viewed as community information tools — filling gaps when other systems are strained and providing learning opportunities at the same time.


    A Natural Fit for EmergencyHam.net

    EmergencyHam.net focuses on education, mentorship, and practical experimentation within amateur radio. Local Wi-Fi information nodes align naturally with that mission by connecting modern devices, real-world networking concepts, and licensed radio operation in a responsible way.

    By exploring simple, resilient communication tools like these, communities can better understand how information flows — and how it can continue flowing when conditions are less than ideal.

  • Introducing the New EmergencyHam.net:

    Introducing the New EmergencyHam.net:

    Bridging Generations Through Amateur Radio, Education, and Modern Technology

    After a long period of quiet development and reflection, EmergencyHam.net is officially relaunching with a renewed focus, a clearer mission, and a growing community vision.

    At its core, EmergencyHam.net is about bringing people together — licensed amateur radio operators, students, educators, and modern technologists — to explore how amateur radio can remain relevant, educational, and community-focused in the 21st century.

    This project is not about replacing existing emergency communication organizations or competing with established programs. Instead, it explores a complementary idea:
    What happens when traditional amateur radio expertise meets modern IoT technology and hands-on STEM education?


    A Project Built Around Learning and Mentorship

    EmergencyHam.net creates opportunities for real, hands-on learning that go far beyond textbooks or simulations.

    Students and makers design and deploy simple IoT sensors — monitoring weather, air quality, environmental conditions, or basic telemetry — and learn how those data systems work end-to-end. They gain exposure to:

    • Electronics assembly and troubleshooting
    • Programming microcontrollers and gateways
    • Network design and reliability concepts
    • RF fundamentals and propagation basics
    • Regulatory awareness and responsible spectrum use

    Just as importantly, students work alongside experienced amateur radio operators who bring decades of practical knowledge, patience, and problem-solving experience. These relationships turn abstract concepts into lived understanding — and transform amateur radio from a historical curiosity into a living, evolving discipline.


    A New Kind of Role for Amateur Radio Operators

    For licensed operators, EmergencyHam.net offers something many have been looking for: renewed purpose and engagement.

    Operators act as mentors, guides, and system stewards — helping younger participants understand RF principles, antenna basics, frequency coordination, and good operating practices. In return, they gain exposure to modern tools and ideas such as IoT sensors, gateways, digital protocols, and distributed systems.

    This is a two-way exchange:

    • Students bring energy, curiosity, and modern development skills
    • Operators bring experience, discipline, and real-world engineering judgment

    Together, they build something neither group could easily achieve alone.


    Why Emergency Communications Still Matter — Even in Education

    While EmergencyHam.net does not focus on fear-driven disaster messaging, resilient communications provide meaningful context for learning.

    Designing systems that continue working when infrastructure is stressed teaches students about:

    • Redundancy and reliability
    • Network failure modes
    • Responsible automation
    • Community service and public benefit

    In some cases, the same educational projects may later provide useful environmental data or communication pathways during real-world events — reinforcing the idea that learning can have genuine civic value.


    Who EmergencyHam.net Is For

    EmergencyHam.net is intentionally broad and inclusive. It is designed for:

    • Amateur radio operators interested in mentorship, experimentation, and modern relevance
    • STEM educators and schools seeking authentic project-based learning
    • IoT developers and makers curious about resilient, low-cost communication paths
    • Students who want hands-on experience with technology that matters

    You do not need to be an expert in all areas. Curiosity, willingness to collaborate, and respect for good operating practices are what matter most.


    A Community in Its Early Stages

    EmergencyHam.net is still growing. The current relaunch represents an invitation, not a finished product.

    We are actively looking for:

    • Founding members
    • Educators and program leaders willing to provide feedback
    • Licensed operators interested in mentoring or technical review
    • Developers and makers who want to experiment responsibly

    If you explored EmergencyHam.net in the past, or are discovering it for the first time, now is the right moment to take another look.


    Join the Next Chapter

    Amateur radio has always been about experimentation, learning, and service. EmergencyHam.net aims to carry those values forward by connecting generations, embracing modern tools, and creating space for meaningful collaboration.

    We invite you to explore the site, review the project ideas, and — if it resonates — consider joining as a participant or founding member.

    The future of amateur radio doesn’t have to be invented from scratch.
    Sometimes, it just needs to be shared.

  • GhostNet – HF Digital Communications

    GhostNet – HF Digital Communications

    During a recent literature search as I re-boot myself back into the Emergency Ham Network headspace I came across GhostNet. Perhaps this is a complimentary track to help the EMH? Who knows but I feel good reading about someone else organizing Operators by establishing new procedures using data communications and existing Ham Radio communications.

    I sense the author some frustration with the FCC regarding encryption and restrictions, but a cheerful realization it is the world we live in. Just that his repetition of “the FCC is no longer here” sends a chill down my neck.

    Of course, I am envious of his latest YouTube video that has 4k plus views in a month and almost 1k comments, clearly I have a lot to learn about marketing. More seriously it is great to see interest in taking Ham Radio to a new place and trying out new things. I don’t think the GhostNet does conflict with much of the EHN, indeed if it GhostNet succeeded it would make it much simpler for operators to use it for sending a base load of traffic from the IoT and Part 15 technologies. GhostNet calls out Meshtastic as a link into what it calls the Public Sphere.

    To quote his document: GhostNet is the overarching term for a collection of communications networks set up to allow users around the world to exchange information without relying on pre-established infrastructure. Far from being just an emergency plan, GhostNet is intended to ease the transition of radio technology into everyday life. Though radio networks cannot truly replace the internet, we hope that we can replace a substantial portion of a person’s daily information requirements and promote a culture of off-grid information sharing.

    From what I have read it has maturity and would offer a practicable way of an Operator to quickly learn and use the digital forms of licensed modes. I particularly warmed to using RTTY since I grew up using it during the glory years in the 70’s.

    This recent Blog is my start of continuing the EHN, to put an end to the unexpected two year planning phase and now make or break the endeavor by reaching back out to the 50 or so interested people who have responded to work out where we go next.

    2026 Update: Where GhostNet Stands Today

    Since this article was first published, GhostNet has continued to exist as a conceptual framework for off-grid, radio-based communication. While there have been refinements and ongoing discussion within the community, there has not been a significant shift toward a structured, interoperable system architecture.

    GhostNet remains a strong example of how disciplined operators can build resilient communication networks using existing radio tools. However, it also highlights a key limitation—most implementations rely heavily on human coordination rather than system-level integration.

    This raises an important question:

    What would it take to evolve this concept into a system that can integrate multiple networks, automate routing, and operate across modern communication platforms?

    👉 We explore that question further in our latest post on EmergencyHam.net and the evolution of resilient communication systems.

  • The People’s Network – low-power wide-area networks

    The People’s Network – low-power wide-area networks

    The term “Peoples Network” has been used by some new players in the emerging private network infrastructure termed low-power wide-area networks (LPWAN) or the older term low power wide Area (LPWA). These have re-emerged as a growth segment because of the development of the IoT and changes in incumbent cellular networks. LPWA is not new, in 2013 it became a fully defined thing in the GSM industry who offered low data rate low-cost connectivity within their network. LORA formed to offer LPWA using a completely different technology, in turn several low data rate standards have become players in this growth market. Now in 2022 there are many competing companies trying to establish themselves as major players in this segment.

    What does LPWAN Offer:

    The three most quoted benefits of LPWAN are:

    • Long range: from a few kilometers in urban areas to over 10 km in rural settings.
    • Low power: Optimized for power consumption, they can run on small, inexpensive batteries for up to 20 years.
    • Lightweight protocols that reduce complexity in hardware design and lower device costs.

    The combination of long range combined with a star topology reduce expensive infrastructure requirements, and the use of license-free or licensed bands reduce network costs. These features justify calling it “the people’s network”.

    The technology is optimized for low-end low cost IoT applications which transmit infrequently using small bursts of data. They can support large numbers of devices, often spread over wide areas, and devices that need to operate autonomously for many years.

    When trying to quantify the size of the market I kept seeing this quote: “According to Global Market Insights, the global LPWAN market is set to surpass $65 billion by 2025”. If this is a reasonable estimate then this is a big deal, most of us will be affected by its adoption and will probably use it to monitor or control something in our lives.

    What does any of this have to do with Amateur Radio:

    All the current LPWAN deployments I have studied require connectivity to the Internet or Private Networks such as cellular. The available public frequency bands and power levels limit the coverage and so a separate network is needed to link the islands and provide central control.

    As licensed operators we have the transmit power and multiple frequency options to be able to link almost any two places on the earth.Not all the IoT traffic will be commercial (remote meter billing or commercial monitoring), a good percentage will be hobbyists, students or clubs interested in developing new devices and solutions. In today’s world they will have to pay or try to use some of the free LPWAN networks.What if there was a branch of the Amateur Radio movement who made it their job to link small LPWAN clusters and manage their traffic. Immediately we would tap into many new technologies and experimenters, including our young people. This could fuel the next generation of Radio Amateur’s.

    I have written some blogs on the available technologies that could provide point to point and meshed links between public systems. Historically Ham Radio helped make technological advances in communications, this seems to be happening less frequently but embracing the new communications systems and becoming relevant in the lives of the next generation could turn this around.

    To understand the opportunities Radio Amateurs might have in the LPWAN it is helpful to study the major players and technologies in use. The current market seems to be split into four types of technology.

    1. Narrowband Internet of things (NB-IoT) is a technology standard developed by 3GPP for cellular devices and services and provided by many of the traditional wireless providers. It uses their infrastructure and backbone so offers little opportunity for connectivity to Amateur Radio systems.
    2. LoRa (from “long range”) is the physical proprietary radio modulation technique based on spread-spectrum modulation techniques derived from chirp spread spectrum (CSS) technology. It is patented and currently owned by Semtech. The LoRa Alliance is a 501(c) association created in 2015 to support LoRaWAN (long range wide-area network) protocol, as well as to ensure interoperability of all LoRaWAN products and technologies. This open, nonprofit association has over 500 members. A LoRa chip is widely manufactured and can be purchased as a module for less than $8 and widely used by experimenters. This technology looks attractive to radio Amateurs since it forms the basis of many IoT networks and capable of experimentation and enhancements (better antenna, more power).
    3. LTE-M is a type of low power technology standard developed by 3GPP to enable a wide range of cellular devices and services (specifically, for machine-to-machine and Internet of Things applications). The difference between LTE-M and NB-IoT is its comparatively higher data rate, mobility, and voice over the network. From a Ham Radio perspective it is not interesting because it is owned and operated by the big cellular providers.
    4. Sigfox is a French global network operator founded in 2010 that builds wireless networks to connect low-power objects such as electricity meters and smartwatches, which need to be continuously on and emitting small amounts of data. The network is based on one-hop star topology and requires a mobile operator to carry the generated traffic. They have partnered with over cellular operators in over 72 countries to create a massive global network. This mature system would not benefit from Radio Amateur involvement.

    It seems that LoRa technology and systems offers the best opportunity for Radio Amateurs to help connect and innovate. In 2019 LoRa had about 36% of the global market which makes it a significant player. This is why the LoRa Mesh is shown on the basic nodes of the proposed EHN.