MMDVM Duplex Hotspot Troubleshooting: Fix Duplex Failure, High BER, Modem Lock & OLED Issues

MMDVM Duplex Hotspot Troubleshooting: Fix Duplex Failure, High BER, Modem Lock & OLED Issues

If you’ve upgraded from a simplex MMDVM hotspot to a duplex board, you may run into configuration issues that don’t appear on simplex setups. Based on real support cases for the AURSINC Mini MMDVM Duplex Hotspot Board, we’ve compiled the most frequent problems and step-by-step fixes to help you get your duplex hotspot running reliably.

Before you start: Always verify your hotspot works properly in simplex mode first. If simplex fails too, double-check your modem type selection, port settings and power supply. If simplex works but duplex doesn’t, continue with the guide below.

1. Simplex works, but duplex mode stops working completely

Symptom

After switching to a duplex modem profile and applying settings, DMR mode briefly shows green then turns red. There is no RF reception and no network connection, even with static talkgroups configured.

Root cause

The most common trigger is a POCSAG frequency conflict. If the POCSAG paging frequency does not match your hotspot’s operating frequency, the duplex service will fail to initialize correctly.

Fix steps
Log in to your Pi-Star / WPSD dashboard
Open the configuration page and locate the POCSAG settings section
Change the POCSAG frequency to exactly match your hotspot’s working frequency
Save settings and reboot the device
Confirm duplex mode initializes normally after the restart

2. High BER (8-10%) in MMDVMCal self-test

Symptom

When running the DMR 1031 Hz test pattern via MMDVMCal, the result shows 8–10% BER, frequent frame loss and intermittent decoding failures.

Root cause

High BER is almost always caused by manually adjusted frequency offset. Many users adjust TX/RX offset to ±400 or even ±800 trying to improve reception, but this actually breaks synchronization and raises error rates significantly.

Fix steps
Go to Expert > MMDVMHost > Modem section
Reset both RX Offset and TX Offset to the default value of 0
Save settings and restart the MMDVMHost service
Re-run the MMDVMCal test — a properly functioning board will return near 0.0% BER on the internal test pattern
Note: Minor frequency drift can be calibrated with small adjustments, but large offset values will always cause instability.

3. "Modem locked" error / cannot flash firmware

Symptom

When running firmware upgrade commands, the system reports "device locked" and refuses to flash. Many users worry the modem is permanently locked.

Root cause

This is a commonly misinterpreted error. The modem is not locked — the flashing tool simply cannot communicate with the modem because it is not in DFU (Device Firmware Upgrade) mode.

Fix steps
Power off the hotspot completely
Press and hold the BOOT button on the hotspot board
Keep holding the button while powering the device back on
Confirm only the green PWR LED is lit, and the red SVC LED is completely off — this confirms DFU mode is active
Connect via SSH, stop the host service first with sudo killall MMDVMHost, then run your flash command

4. OLED display flickering, blank screen, or stuck on "Starting..."

Symptom

The OLED screen works intermittently, stays black even when the hotspot is running, or freezes on the "Initializing / Starting" screen.
Root cause
Incorrect display type selection or default screensaver settings are the most common causes. System version incompatibility after firmware/OS upgrades can also trigger this issue.
Fix steps

On the General Configuration page, set Display Type to OLED Type 3
Go to Expert > MMDVMHost > OLED section
Set LogoScreensaver to 1 to disable the screensaver and keep the display always on
Save and apply changes
If the issue appears right after a system update, roll back to a stable Pi-Star version to rule out system compatibility

5. Slow-flashing SVC red LED: is my system failing to boot?

Symptom

The SVC red LED flashes slowly (approx. 2 seconds on / 2 seconds off), and users assume the operating system failed to load.

Clarification

A slow or fast flashing SVC LED is a normal operating state for the MMDVM modem. It means the modem controller is powered and running.
If your simplex mode works correctly and the system dashboard is accessible, the hardware and OS are fully functional. If duplex mode fails, it is a configuration issue — not a boot or hardware failure.

Final Troubleshooting Checklist

If you still have issues after following all steps above:
Confirm you are using an official stable Pi-Star or WPSD image on a Class 10 SD card
Use a qualified 5V power supply to avoid voltage drop and instability
Run sudo wpsd-detectmodem via SSH to confirm the modem is properly detected
Save your system log and contact our technical support team for further assistance

Back to blog