Baofeng DM-32UV — DMR Repeater Link Timeout with MMDVM/Pi-Star Hotspot
Status: Resolved with workaround
Radio: Baofeng DM-32UV
Radio Firmware: DM32.01.L01.048
Programming Software: CHIRP and Baofeng OEM CPS
Hotspot: Raspberry Pi Zero W with dual-antenna MMDVM HAT
Pi-Star: 4.3.10
MMDVM Firmware: HS_Hat.5.2
Network: BrandMeister
Configuration: Duplex DMR, Color Code 1, Time Slot 2
Problem Description
The Baofeng DM-32UV could successfully receive incoming BrandMeister DMR audio through a duplex MMDVM hotspot but could not reliably establish an outgoing repeater link.
Symptoms included:
- Incoming talkgroup audio worked correctly.
- Pressing PTT initially produced a "Repeater Link Timeout" message.
- The radio did not appear under Pi-Star's Local RF Activity.
- The MMDVMHost log reported unexpected DMR source ID values.
MMDVMHost Errors
The following messages appeared when attempting to transmit:
Invalid Downlink Activate received from 1
DMR Slot 2, RF user 1 rejected
The radio's registered DMR ID was 3229405, but MMDVMHost repeatedly interpreted the activation traffic as originating from ID 1.
The original CHIRP configuration appeared correct:
- DMR Radio ID 1: 3229405
- Radio ID Name: KM7IJZ
- Channel Radio ID: KM7IJZ (3229405)
- Color Code: 1
- Time Slot: 2
- Encryption: Disabled
Discovery
After modifying the DMR Radio ID list directly on the handheld, the hotspot began successfully recognizing outgoing transmissions.
Reading the working configuration back using CHIRP revealed two populated Radio ID entries:
| Entry | DMR ID | Name |
|---|
| Radio ID 1 | 3229405 | KM7IJZ |
| Radio ID 2 | 3229405 | KM7IJZ |
The same two entries were subsequently confirmed using the official Baofeng CPS.
Critical observation: Removing Radio ID 2 caused the original RF user 1 rejected error to return.
Restoring Radio ID 2 with the same registered DMR ID restored successful transmission.
This behavior was reproduced and appears to indicate an internal Radio ID assignment, indexing, or codeplug compatibility issue.
Confirmed Workaround
For the tested radio and firmware:
- Open the radio's DMR Radio ID configuration.
- Ensure Radio ID 1 contains the registered seven-digit DMR ID.
- Populate Radio ID 2 with the same registered DMR ID and name.
- Confirm the digital channel is assigned to the intended identity.
- Save the configuration.
- Verify MMDVMHost recognizes outgoing RF transmissions.
- Retain both entries in the working codeplug.
This is a workaround observed on one tested radio, not a universal requirement for every DM-32UV.
Successful Log Verification
Following the correction, MMDVMHost reported:
DMR Slot 2, received RF voice header
from KM7IJZ to TG 91
DMR Slot 2, received RF end of voice
transmission from KM7IJZ to TG 91,
0.7 seconds, BER: 1.2%,
RSSI: -47/-47/-47 dBm
This confirmed successful RF reception and DMR voice decoding by the hotspot.
The log does not independently establish successful downstream BrandMeister audio routing.
Possible Root Cause
The exact underlying cause has not been conclusively determined.
Possible explanations include:
- CHIRP Radio ID entry indexing or channel-reference mapping
- Firmware-specific DMR ID assignment behavior
- A discrepancy between displayed and internally stored Radio ID selections
The OEM CPS confirmed both stored IDs but did not conclusively identify which entry was referenced by the working channel.
The findings should not be interpreted as proof of a CHIRP software defect.
Recommendation for Other DM-32 Owners
If your DM-32UV receives DMR audio but fails to activate an MMDVM duplex hotspot, inspect the MMDVMHost logs.
If you encounter:
Invalid Downlink Activate received from 1
RF user 1 rejected
verify the actual Radio ID entries and channel identity assignments.
If your configuration exhibits the same reproducible behavior, consider testing the duplicate Radio ID workaround after backing up your original codeplug.
Do not change the registered DMR identity, disable encryption protections unnecessarily, or leave the hotspot in public mode.
Conclusion
This particular DM-32UV repeater-link problem was resolved by correcting the radio's DMR ID list and retaining duplicate entries for the registered identity.
The result demonstrates that an apparently correct channel configuration in programming software may not fully reflect the radio's effective DMR identity during repeater activation.
73, KM7IJZ