A common point of confusion for digital voice users is the difference between Bit Error Rate (BER) and Packet Loss (Loss). Because both issues can cause choppy, robotic, or dropped audio, they are often mistaken for the same thing.

However, they are completely different measurements that occur on entirely different parts of your hotspot setup.

The Quick Breakdown

Visualizing the Data Path

To understand where these errors happen, look at how your voice travels from your radio out to the digital network.

graph LR
    subgraph RF_Zone [RF Link: Subject to BER]
        Radio[Your Radio] <-->|Radio Waves| Hotspot[WPSD Hotspot]
    end

    subgraph Net_Zone [Network Chain: Subject to Packet Loss]
        Hotspot <-->|Wi-Fi / Ethernet| Router[Local Router]
        Router <-->|Your ISP| Internet((Internet Backbone))
        Internet <--> Server((Master Server / Reflector))
        Server <--> Remote[Remote Peers / Repeaters]
    end

    style RF_Zone fill:RFZONEFILL,stroke:RFZONESTROKE,stroke-width:2px
    style Net_Zone fill:NETZONEFILL,stroke:NETZONESTROKE,stroke-width:2px
  

Bit Error Rate (BER) – The Local RF Link

BER measures the health of the digital radio signal traveling through the air between your handheld/mobile radio and your hotspot’s MMDVM modem.

If your radio transmits a stream of ones and zeros, and your hotspot misinterprets a 0 as a 1 due to local noise or a bad frequency alignment, that counts as a bit error.

• On the WPSD Dashboard: A low BER (typically under 1% to 2%) is perfectly normal. Digital voice modes have built-in Forward Error Correction (FEC) to repair minor bit flips automatically.
• Local/RF Traffic Only: The Network Activity table only ever shows BER for your own local/RF transmissions. It cannot show BER for networked users (traffic arriving from BrandMeister, TGIF, YSF, XLX, etc.), because BER is strictly a measurement of the RF link between your radio and your hotspot’s modem — there’s no equivalent RF link to measure for a signal that arrived over the internet.
• Short Transmissions May Show No BER: MMDVMHost needs roughly 2-3 seconds of continuous RF transmission to properly measure and calculate BER. Quick keyups shorter than that won’t leave enough time for a BER value to be calculated, so brief transmissions may show no BER at all even when the RF link is healthy.
• The Result of High BER: If BER spikes too high, the audio turns into robotic “digital garbage” or cuts out completely because the modem can no longer decode the frames.
• The Fix: High BER is almost always fixed by calibrating your modem (adjusting RXOffset / TXOffset), changing frequencies to avoid local RF interference, or lowering your radio’s transmit power to prevent overloading the hotspot’s receiver.

Loss – The End-to-End Network Link

Packet Loss has absolutely nothing to do with your radio, your antenna, or your RF signal. It measures the health of the data packets traveling over IP networks (Wi-Fi, Ethernet, and the internet).

Unlike BER, which only exists between your radio and your hotspot, Packet Loss is a two-way street that can happen at any single point along the entire internet path.

graph TD
    A[WPSD Hotspot]

    subgraph Row2[ ]
        direction LR
        s2["        "] ~~~ B[Home Router]
    end

    subgraph Row3[ ]
        direction LR
        s3["                "] ~~~ C[Internet Routing Hubs]
    end

    subgraph Row4[ ]
        direction LR
        s4["                         "] ~~~ D[Master Server / Reflector]
    end

    subgraph Row5[ ]
        direction LR
        s5["                               "] ~~~ E[Remote Users / Nodes]
    end

    A -->|1. Weak Wi-Fi / Bad Cable| B
    B -->|2. Local ISP Throttling / Glitch| C
    C -->|3. Data Center Congestion| D
    D -->|4. Heavy Traffic / Server Load| E

    style Row2 fill:none,stroke:none
    style Row3 fill:none,stroke:none
    style Row4 fill:none,stroke:none
    style Row5 fill:none,stroke:none
    style s2 fill:none,stroke:none
    style s3 fill:none,stroke:none
    style s4 fill:none,stroke:none
    style s5 fill:none,stroke:none
  

Packet loss can occur at any of these hops:

• Your Local Network (The First Mile): A weak Wi-Fi signal between your hotspot and your router, a faulty Ethernet cable, or local network congestion (e.g., someone else in the house streaming heavy video traffic).
• Your Internet Service Provider (ISP): Issues with your local internet connection, high latency, or temporary routing glitches on your ISP’s network.
• The Internet Backbone: The physical routing paths across the country or world. If a major data hub experiences issues, packets get dropped.
• The Server Side (The Destination): The master server (BrandMeister, TGIF, YSF, an XLX reflector, etc.) could be overloaded, experiencing a traffic spike, or having network issues at its hosting facility.
• The Other User’s End: If you are listening to a peer who has a terrible connection, their loss is baked into the stream sent to the server. The server passes that broken stream down to you. Your WPSD dashboard will show packet loss because the data arriving at your hotspot is already incomplete—even if your own local internet is 100% perfect.

The Mailbox Analogy

Think of sending a letter to a friend:

• High BER is like bad handwriting. If you smudge a few letters on the envelope, the post office can usually still figure out where it goes (Error Correction). But if your handwriting is completely illegible (High BER), the message cannot be read or delivered.
• Packet Loss is the mail truck catching fire. It doesn’t matter how neat your handwriting was; the letter simply vanished in transit and never arrived at its destination.

Bottom line: You can have a perfect 0.0% BER on your radio link and still experience heavy dropouts because a node three states away is dropping 15% of the internet packets. They are completely separate metrics.