MTR2000: DPL won't reset after pressing Monitor button...

[chipjumper]

Here is the setup: MTR2000 on VHF with a DPL of 131. It is hooked up to a C200 Tone remote deskset at the radio and a VoIP link to Central Dispatch. It works well. TX's from the deskset just fine. RX's just fine. The problem is odd -- it has never done this before until now. When someone presses the "Monitor" button on the C200 tone remote desket, it obviously takes down the DPL and will receive everying around; not a surprise. The problem is that it won't revert back. It used to go back to DPL Rx as soon as someone pressed the "Monitor" button again. I did some testing:

Left the MTR2000 plugged in, Cycled the power on the C200 --- no luck; DPL Rx not active.

Cycled the power on the MTR2000, left the C200 plugged in --- Voila! Life is good again. Will on receive DPL encoded transmissions as its supposed to.

Has anyone ever experienced this issue before? Do MTR2000's get lazy after a while? Bad C200 deskset?

[Bill_G]

The monitor will stay active until the next transmit command.

[chipjumper]

My apologies, --- it would usually clear with a hit of the transmit button --- not hitting the "Monitor" button again. So basically, it is not reverting back after hitting the transmit button. I'm running over there right now to get a voltage log form the Eaton rackmount UPS that powers the MTR and accessories.

[chipjumper]

I just checked the Eaton UPS management logs. The voltage stays at a constant 122V. The input power slowly fluctuates from 122V to 124V so that looks okay.

[AEC]

I would check your wireline connections to the MTR.
If you are using punchdowns, a loose wire, or one not punched down firmly can also cause this very problem.
Also check your connections on the wildcard on the MTR as well.

[thebigphish]

I fought the holy war with Moto and a VHF MTR2k, that I was convinced developed Alzheimers disease. Unit would behave properly, and then randomly crap out and act bizarre. It took 2 trips to the factory, thousands of $ in repair visits and consults, and what was found to be the problem was hypothesized by a factory repair tech (while on his lunchbreak, nonetheless).

http://batboard.batlabs.com/viewtopic.p ... 85&start=9

Rebuild the codeplug from one of the default codeplugs found in the software folders. Don't download - change - upload. The unit mentioned in the posted link has been online now for over a year w/o any of the previous issues. This should help you at least rule out codeplug issues as your problem.

[chipjumper]

Interesting; I will do that and report back!

[Bill_G]

That would be good to know if it is caused by a corrupted codeplug. All of us have had an MTR do something weird that eventually required a new station control module to fix.