CDN/cdn-star
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Revert 150-160MHz as "valid" for POCSAG frequency - hardware rejects it

Browse Source 
Confirmed on real hardware: setting POCSAG frequency to 155MHz makes
MMDVMHost exit immediately with "Received a NAK to the SET_FREQ
command from the modem" - the MMDVM_HS_Dual_Hat's ADF7021 chips are
tuned for UHF and can't physically retune to VHF 150-160. Since
MMDVMHost controls DMR/YSF/NXDN/P25/POCSAG through one process, this
takes the whole modem down, not just POCSAG - matches the "DMR turns
red after setting POCSAG" symptom reported.

The earlier commit (that added this range as green/valid) was wrong;
it gave false confidence for a frequency that hard-crashes the radio
service. Back to the original 144-148/220-225/420-450/842-950 ranges.
This commit is contained in:
yuancheng
2026-07-22 00:07:16 +08:00
parent 53b0218f75
commit 2c815cec02
2 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
functions.js
-1
View File
@@ -94,7 +94,6 @@ function checkFrequency(){
var intFreqPOCSAG = parseFloat(freqPOCSAG.value); // Swap to float
// TX Good
if (144 <= intFreqPOCSAG && intFreqPOCSAG <= 148) { pocsagFrequency.style.backgroundColor = goodColor; }
if (150 <= intFreqPOCSAG && intFreqPOCSAG <= 160) { pocsagFrequency.style.backgroundColor = goodColor; }
if (220 <= intFreqPOCSAG && intFreqPOCSAG <= 225) { pocsagFrequency.style.backgroundColor = goodColor; }
if (420 <= intFreqPOCSAG && intFreqPOCSAG <= 450) { pocsagFrequency.style.backgroundColor = goodColor; }
if (842 <= intFreqPOCSAG && intFreqPOCSAG <= 950) { pocsagFrequency.style.backgroundColor = goodColor; }