MT2000 Receiver Problem - Controller Failure?
Posted: Wed May 10, 2006 6:36 pm
I've got an odd MT2000 Model III problem.
This is a UHF radio where the receiver was intermittent. The user thought it was something that was best fixed by squeezing the case - popped the pico fuse.
I had a new HT1000 RF deck so I installed it, aligned it, seemed to come and go. I installed a new front case, flex, speaker, etc. Seemed ok for a moment, but I let it run to make certain.
Hmm, the receiver became intermittent, again. When pushing the "monitor" button, the receiver spits an odd sound a couple of times, and then changes to a more normal sounding noise. It is completely deaf, as if it isn't listening on the programmed frequency.
I noticed when scrolling through the zones back and forth, one of the zones had changed to "unprogrammed". I reloaded the codeplug, and the zone was restored but still no receive.
So, it seems to me the controller has something flaky going on, even though it originally tuned up. This is the only thing left, but, I've never seen one go like this.
I tried to force in another codeplug but I got a "codeplug too old for application" when using 2.00.01.
Has anyone seen this kind of failure? Any ideas? I want to understand a root cause (besides, I don't have a controller!).
Rob
This is a UHF radio where the receiver was intermittent. The user thought it was something that was best fixed by squeezing the case - popped the pico fuse.
I had a new HT1000 RF deck so I installed it, aligned it, seemed to come and go. I installed a new front case, flex, speaker, etc. Seemed ok for a moment, but I let it run to make certain.
Hmm, the receiver became intermittent, again. When pushing the "monitor" button, the receiver spits an odd sound a couple of times, and then changes to a more normal sounding noise. It is completely deaf, as if it isn't listening on the programmed frequency.
I noticed when scrolling through the zones back and forth, one of the zones had changed to "unprogrammed". I reloaded the codeplug, and the zone was restored but still no receive.
So, it seems to me the controller has something flaky going on, even though it originally tuned up. This is the only thing left, but, I've never seen one go like this.
I tried to force in another codeplug but I got a "codeplug too old for application" when using 2.00.01.
Has anyone seen this kind of failure? Any ideas? I want to understand a root cause (besides, I don't have a controller!).
Rob