Batboard

Sorry for the long post, but I want to convey everything I’ve tried.

I have a 99Ch 30-36MHz MT1000 that was manufactured in Dec 1993. Model number H41GCJ7130AN, programmed with RSS version R.03.01.02.

I recently received this radio and it seemed to be working fine. It had 21 channels programmed upon receipt. I originally had 15 of those overwritten with receive only channels, while I worked out what I wanted programmed into it. It worked great during those few days. Then, I had it programmed again with 46 receive only channels. After that codeplug (which I have a copy of, as well as the original) was programmed into the radio, the display showed the SP 88 which is displayed when the radio is first turned on, and stays on the display. No beep (got one before), no squelch when the monitor button is pressed. The backlight does work, however, no Tx or Rx.

The radio can be read after about three tries through “SERIAL BUS ACCESS ERROR 003!!!” Funny thing is, once read, the entire codeplug is as programmed with the 46 channels except for the Tx/Rx pairs, which when originally programmed were both the same (no repeaters), but now all of them read 70.25 for Rx and 90.20 for Tx. All PL, QCII, radio wide parameters and scan list entries are what was programmed.

Nothing can be written at all to the radio. Even tried reading it, modified that invalid freq. pair codeplug and tried reprogramming. Still no luck. When writing you get “SERIAL BUS ERROR 003!!!” and occasionally you’ll get “Programmer Not Compatible With This Radio.” Another version of MT1000 RSS (R03.01.00) was tried to no avail as well as P200LB RSS. I know it’s not the computer because other MT1000's were programmed during this same period using the same computer and RSS. All equipment (RIB and cables) are OEM Motorola.

So what’s the deal? I’ve been trying to fix this for two weeks. I tried the suggestions for clearing an invalid codeplug on the main batlabs page, however, at least one of those shot the 5 amp resistor on the radio, and I had to replace it. I’ve searched the archives but no one has seemed to have this problem. I’m going crazy trying to fix this. Is it a bad controller? Why did it work so well before? I never got and weird sounds that others have reported when the controller goes bad. Any help would be greatly appreciated! I can forward a copy of the codeplug if necessary.

Sounds like a corrupt codeplug, and from everything you describe i had one that was like that before.

If you popped the 5amp fuse when trying to clear the codeplug then you must have shorted out the wrong line going to the controller, chances are the fuse popped before any other damage happened, but that may have caused you even more troubles with the controller.

You won't pop the fuse when shorting the lock detect line to ground, that's the right end of the left plug going to the VCO, the last contact is the lock detect and needs to be shorted to ground but you have to be darn careful not to short the second one in when you short that last one. I usually just tack solder a small piece of wire to the last contact on the plug and then ground the other end of the wire until i am done with the repair.

Your going to need to create a new codeplug and write it to the radio with the lock detect line grounded, the controller is stuck in a loop because of the out of band frequencies and/or corrupt codeplug. Ground the lock line, load and program the new codeplug to it, then turn off the radio and disconnect the programming cable. Turn the radio back on and see if it works, transmits and receives normally, then turn off the radio, disconnect your jumper from the lock line to ground and turn it back on. If it still works then your good to go, if it craps out and shows 88 on the display then the controller is toast.

And if push comes to shove get a hold of me, I've fixed a lot of Genesis series radios and could take a stab at it, i only charge for the work if the repair is successful and return shipping.