Handheld and Hotspot Troubleshooting for Digital Voice
This guide is for the most common setup on the air: a handheld radio talking to a personal hotspot. It is organized by symptom. Find what you are seeing, read the likely causes, and work down the fixes. It covers DMR, D-Star, and Fusion, with the most detail on DMR because that is where most people start.
Start here: the four things that must all be true
Most hotspot problems are one of these four not lining up. Check them before anything else.
The hotspot is online. Its dashboard shows it connected to the network. If the dashboard is unreachable or shows disconnected, the problem is the hotspot, not the radio.
The radio and hotspot are on the same frequency. A hotspot is a tiny transmitter, so the handheld channel has to match the hotspot's frequency.
The radio is in the right digital mode. A DMR radio for a DMR hotspot, D-Star for D-Star, Fusion (C4FM) for Fusion. An analog channel will do nothing.
You are close enough. A hotspot puts out only a few milliwatts. Keep the handheld in the same room. Standing too far away looks just like a dead network.
Symptom: the hotspot will not connect to the network (DMR)
The dashboard shows disconnected, or it never logs in. On BrandMeister, the causes are well documented, and the first one is by far the most common today.
Hotspot Security Password missing or wrong
BrandMeister requires a personal Hotspot Security Password on every MMDVM or homebrew hotspot. Without a matching password, the hotspot will not pass traffic. It exists so nobody else can connect using your registered ID.
Set the password in BrandMeister SelfCare: click your callsign, choose SelfCare, open the Radio ID tab, and find the Hotspot Security section. The password may be 20 characters or fewer and should not use special characters.
Enter that same password into your hotspot (Pi-Star or WPSD, in the BrandMeister settings). It is case sensitive.
If you copied and pasted it, check that you did not pick up a space at the start or end. That is a common reason a correct-looking password still fails.
Running two hotspots on the same Radio ID is allowed. Set the security password for that ID and use the same password on both devices.
Radio ID not registered, or does not match your callsign
Your DMR Radio ID has to be registered (at RadioID.net) and has to match the callsign in the hotspot. If it does not match the registration, BrandMeister will refuse it.
Watch for look-alike characters: use zero (0), not the letter O, and use the numeral 1, not the letter I or L.
A very old 1xxxxx style ID will not import into BrandMeister. You need a current seven-digit ID.
If you recently changed your callsign, you will need to register a new BrandMeister account for it.
Wrong connection method or stale software
On Pi-Star, connect to BrandMeister with the DMR Host method and the BrandMeister network enabled. If you set it up through DMR Gateway and it will not connect, switch to the DMR Host method.
Make sure the hotspot software is current. Run the update in the configuration page. An out-of-date build is a real cause of connection trouble.
If it still fails after everything checks out, a corrupted SD card is possible. A fresh install of the hotspot software is the last resort.
Symptom: connected, but nobody hears me (no audio out)
The hotspot shows connected and you can hear other people, but your transmissions go nowhere. This is almost always a radio-side setting, not the hotspot.
DMR
The talkgroup is not linked. A dynamic talkgroup only stays linked for a few minutes after activity, then drops. Key up once on it to bring it back, or set it as a static talkgroup in SelfCare or in the hotspot so it stays connected.
The channel is on the wrong time slot. A simplex hotspot generally uses Time Slot 2. If your channel is set to the other slot, your audio has nowhere to go.
The color code does not match. The radio channel and the hotspot must share the same color code. Hotspots usually default to color code 1.
The TX contact is wrong. The channel has to transmit to the talkgroup you think you are on. If the TX contact points at a different talkgroup, you will be talking on the wrong one.
Nobody is there. A quiet talkgroup is not a fault. Use the network's Parrot or echo test to confirm your audio is getting out before assuming something is broken.
D-Star
You are not registered. D-Star gateway and reflector use requires your callsign to be registered on the D-Star (US-TRUST) system. Local simplex may work while anything through the gateway fails, which is the classic sign of an unregistered call.
UR, RPT1, and RPT2 are set wrong. For normal use, set UR to CQCQCQ. RPT1 is the hotspot's callsign with the module letter, and RPT2 is the same callsign with the gateway letter (G). Reflector commands go in the UR field.
The callsign fields are mis-spaced. D-Star callsign fields are a fixed width, and the module letter sits in the last position. A letter in the wrong column is a frequent cause of a route that will not complete.
Fusion (C4FM)
The DG-ID does not match. On Fusion, DG-ID 0 talks to everyone, while a specific DG-ID reaches a specific room or node. If your radio's DG-ID does not match what the hotspot expects, your audio will not go where you want, or nowhere at all.
The radio is in the wrong mode. Set the radio to the digital (DN) mode, not analog, and let AMS follow the incoming signal if your radio has it.
YSF versus WIRES-X. A hotspot uses the YSF or FCS side, not Yaesu's own WIRES-X network. Make sure you connected the hotspot to the room you meant on the right system.
Symptom: audio is choppy, robotic, or keeps dropping
You get through, but the audio breaks up. On a handheld-to-hotspot link this is almost always the little RF path between the two, not the internet side.
Move closer, but not too close. A few milliwatts does not go far, so distance and walls break the signal up quickly. Standing right on top of the hotspot can overload it, so a few feet away is the sweet spot.
Check the frequency and any offset. The handheld and hotspot must be on the same frequency. A simplex hotspot needs a simplex channel with no repeater offset. A duplex hotspot uses different receive and transmit frequencies.
Watch the BER on the dashboard. A rising bit error rate points at the RF link. A clean link reads near zero.
You are on Parrot. The Parrot or echo test talkgroup is built to record you and play you back. That is not a fault, it is the test working. Move off Parrot for normal use.
A cross-mode loop. If you built a bridge or linked the same conversation two ways, audio can come back to you. On a plain handheld-to-hotspot setup this is rare, so suspect Parrot first.
Odd but normal: someone else's callsign on my screen
On bridged and transcoded systems, the callsign your radio shows is sometimes the gateway or bridge callsign rather than the person talking. When a conversation crosses from one mode to another, the equipment supplies a callsign because the original station's ID does not carry across. Seeing an unfamiliar call on a linked system is usually this, not a problem with your radio.
Mode notes worth keeping handy
DMR. The four settings that must agree with the hotspot are frequency, color code, time slot, and the talkgroup on your TX contact. Static talkgroups stay linked; dynamic ones drop after a few minutes of quiet.
D-Star. Registration first, then MY, UR, RPT1, and RPT2. Most routing failures come down to registration or a mis-typed callsign field.
Fusion. Digital mode on, DG-ID matched, and the right room on the YSF or FCS side.
The one-line version: if it will not connect, check the hotspot security password and your registered ID. If it connects but nobody hears you, check the talkgroup link, time slot, color code, and TX contact. If the audio is rough, it is the RF between the handheld and the hotspot.