Batboard

I’ve been trying to take delivery of a new MC2000 deskset for the last few months. After several program changes (major miscommunications during the order process) I was ready to accept it (again) two weeks ago.

So the tech from our local Motorola shop comes in to deliver it. I plug it in and it works fine. We reprogram some portables to make use of the MDC signaling capabilities we now have. I start sending tones, checking the displayed IDs and so on just to make sure everything works right.

About after an hour it stopped passing audio received from the repeater. I can still transit voice, tones MDC and everything else just fine from the console, but it won’t pass received audio.

Here’s a few more things:
It is still decoding MDC (ID still shows, emergency still works)
I still get the beep from the console whenever I hit an invalid button, so the speaker still works.
No Rx audio with the handset either.
Other tone remotes on the same line work fine.

It died right in front of our tech from the Motorola shop, and he has no idea what happened. Any ideas?

I’m glad it happened before he left, that way he knows we didn’t do anything to it.

sound like a signaling issue in the programming.
does the busy light flash on recieve regardless of werther or not you hear it?

The busy LED never lights up (I was wondering about that. Shouldn't it light whenever another tone remote is keyed?)

I think the LCD still shows "call" when it receives. I can't remember- our tech has it back at his shop.

The console worked fine and then without any warning or changes it stopped working.

Don't laugh; I've done this: some form of "mute" button inadvertently invoked?

if it was the mute button then the led would still flash

We had a mute button, but it was removed during the last round of programming. I really did not like the idea of letting my dispatchers have access to a mute key. I can just hear it now: "all the talking was annoying me, so I turned it off'

Anyway, we tried a reset and cycled the power a few times. I would think that would reset the mute if it was still programmed, but relabeled something different and we hit it thinking it was the new button.

we'll see...

The weird thing is it was working just fine, then poof - nothing.

Could rf from keying up a portable by it piss it off?