Batboard

I have a MT2000 VHF with full keypad and front display. The other day for no reason i started having problems with it. I would turn it on and the screen would stay blank, the led would be green, and ide hear a low BOOP from the speaker. Then occationally it would turn on and seem ok, then the display would freak out and if i tried to change channel it would say unprogrammed. Once it gave me the Fail 01/82 message. I hooked it up to my computer and tried downloading and uploading the codeplug to see if that fixed it however it continues to have this problem. I need to try and get this solved because like most of you, depend on this radio for all of my fire/ems dutys and work.

Ok i went home and put in the original codeplug i had for this radio and it worked fine for awhile. Then it started having the problem again. Like i said for the most part i just get that BOOP and a blank display.

Today it didnt want to work at all. One time it seemed to come on then the display went nuts again and i got Fail 002. Im guessing this radio would require a trip the the depot?

obvious things to check:

try verifying the interconnect jumper between the RF and controller board (assuming you know how to open the radio). A loose jumper can cause this to happen. (if it's an older radio made before late 1994 it will have a soldered jumper flex. This should be replaced anyway) Also verify the connection of all flex cables. Pending this doesn't solve the issue, then yes, a repair might be needed. IMO it might be cheaper to replace the radio, as the MT2000 is aging, they can be had for under 250.00 which is less than a flat rate repair will run you.

Ok i opened the radio and looked at the flex connections. They are all intact. I took them off and cleaned the contact points and put it all back together. For awhile it worked then it went back to haveing the error and not working.

Check the legs on the EEPROM on top of the controller next to the control flex socket. There are 3 legs to that chip that tend to pop loose and may give you that error on an intermittent basis. Generally this problem is associated with having a secure board installed which causes a little more stress but it's not required. Wish I still had my pics of this but I don't. However if you've got the schematics the chip you are looking for is U713.