Batboard

I just got a conventional mts2000 that is in decent shape. The problem was that the ABC selector was broken so I felt compelled to go and exchanged it with an extra one that was laying around. I turned back on the radio and the screen was blank. After making sure the ribbon was in the right place, and trying in a different radio ( that the display doesn't work in anymore) I am where I am at right now. Did I fry the circuits for the screens or is it possible that my radio needs a codeplug refresh?

I have worked inside many of these fine radios. I hope you used the standard esd ground strap while working on the innards.

I have had a few of these type of problems in the past. Sometimes the front panel flex end that goes into the flex
connector gets a little twisted out of shape and does not seat properly. If all else fails put the original flex and parts
back in and see if that brings the display back to life. Good luck...

it may have gotten bent out of shape, i'll keep trying to re-seat the ribbon but its not looking to good.

When you apply power to the radio, does it beep on power up, or is it silent?

You could have the tone disabled in the RSS, but many I've seen/used have had the beep enabled.

If the radio does power up, but the display still does not work, you may have a bad pin on the socket the display flex slides into...which will need to be resoldered if possible.

Never leave any radio supplied with power while replacing a display flex assy, you can easily destroy the controller board.

And always make certain the 'lock' on the flex header is seated firmly or the flex will walk out and probably destroy the controller by shorting sections that are driven by other circuits on that board.

Thanks for the reply. All those things you mentioned before Ernest I did (I always have power on beep on all my /\/\ radios and I always keep my battery disconnected when I'm fiddling around inside my radio). I believe it's some type of damage to the flex or a bad flex socket right now. ( which is bad news ) I don't have the resources right now to be able to fix or test this problem which is a bummer.

Thanks again for all your help!