Bug: Squelch "Master" setting is 0% on 222 MHz

Post Reply
KD7MW
Posts: 41
Joined: Sun Feb 06, 2022 4:18 am

Bug: Squelch "Master" setting is 0% on 222 MHz

Post by KD7MW » Sun May 08, 2022 12:20 am

Summary: 222 MHz channels whose Squelch level in the CPS is set to "Master" end up with the squelch wide open. But only on the MD-9600. The problem does not occur on my GD-77 with the same codeplug.

Details: I have several receive-only channels that are 222 MHz analog repeaters. The "OpenGD77 Squelch Level" is set to "Master" in the CPS, just as they are for all other analog repeaters. But when that codeplug is sent to my MD-9600, all the 222 MHz channels have the squelch set wide open.

I can then adjust the squelch manually on the radio in the Channel Details. That works. But the moment I switch to another channel and back, it reverts back to "Master" and is again wide open. Saving a percentage squelch setting with P1 (Func) + Enter does save that setting to the codeplug as it should. So it appears that for the 222 MHz band, "Master" is being incorrectly interpreted as "0%" for 222 MHz channels.

This same squelch setting works properly for all 2m and 70cm analog repeaters in the codeplug.

I double-checked whether Radio Type was set correctly when I wrote the codeplug to each radio. Yes, it was.

I tested whether unchecking the Receive Only box a 222 MHz channel would fix the problem. No, it did not.

Both radios are running the firmware built 20:50:44, May 1, 2022. CPS is v. E2022.05.04. Both radios have "Band Limits" set to "On" in Radio Options. The CPS band limits are set to the defaults as shown in the current manual on GitHub: VHF 136-174, UHF 400-470.

I should also note a briefly confusing inconsistency: When I used the OpenGD77-CSV program to organize things, the squelch setting is written in the CSV as "Disabled" on all three bands. Evidently "Disabled" in British English means "Master" in Australian and French. :mrgreen: =

Seriously, big thanks to all the developers. The MD9600 firmware is quite usable now. OpenGD77-CPS made it possible for me to combine my old analog repeater list with my DMR list, and now I have A Radio For All Seasons.

73,
--Peter, KD7MW

VK3KYY
Posts: 7484
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: Bug: Squelch "Master" setting is 0% on 222 MHz

Post by VK3KYY » Sun May 08, 2022 4:55 am

The MD9600 can't operate on the 220Mhz band, even on Rx only. However the codeplug format is common to both the GD77 and MD9600 and it doesnt matter what radio type you select.

A lot of people have both a GD77 and MD9600, so it would be counter productive if we did something in the CPS that disallowed channels on the 220Mhz band when you had MD9600 as the radio type, as that would screw up the codeplug they are also using for their GD77

I suppose we could add some more checking on the MD9600 so that if you changed to a channel of VFO freq which is out of range, even on Rx it displays a message.
But its up to the operator of the radio to not create channels that are outside the operational range of the radio.
Or if you have common codeplugs for GD77 and MD9600, don't select those channels on the MD9600

KD7MW
Posts: 41
Joined: Sun Feb 06, 2022 4:18 am

Re: Bug: Squelch "Master" setting is 0% on 222 MHz

Post by KD7MW » Sun May 08, 2022 6:09 am

Ah, I didn't realize that the MD-9600 couldn't receive the 222 band. No problem. I've isolated those channels in their own zone, so I simply won't try to receive them with the MD-9600. Just sorry I haven't made myself useful by finding a real bug.

VK3KYY
Posts: 7484
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: Bug: Squelch "Master" setting is 0% on 222 MHz

Post by VK3KYY » Sun May 08, 2022 6:23 am

KD7MW wrote:
Sun May 08, 2022 6:09 am
Ah, I didn't realize that the MD-9600 couldn't receive the 222 band. No problem. I've isolated those channels in their own zone, so I simply won't try to receive them with the MD-9600. Just sorry I haven't made myself useful by finding a real bug.
No worries

I think we probably need to put a warning message into the firmware of "Out of range", for this instance.

Or possibly "No PLL lock", but I don't know if we can determine whether the PLL is locked or not.

Post Reply