Batboard

i bought a mts 2000 at a auction and when i got home tried to read it. cant read the radio. when i go to comm test it says radio com is ok..back to read radio. com failed buss line busy. is it the dreaded tool proof, i hope not.thank you olepro

If the radio gives the power up self-test beep and then something on the display, it is not the toolproofing block.

Most likely causes:

Trying to run RSS under Windows or a DOS Window under windows;
Bad RIB;
Bad RIB to radio cable;
Low battery in the portable; or
RSS not configured for the correct COM port on the PC.

olepro1 wrote:i bought a mts 2000 at a auction and when i got home tried to read it. cant read the radio. when i go to comm test it says radio com is ok..back to read radio. com failed buss line busy. is it the dreaded tool proof, i hope not.thank you olepro

Sounds like there is another program that won't let go of your serial port.

sounds correct fuel 4300, is there a fix for this condition thanks olepro

Note, though, that Fuel4300's suggestion implies that you are running Windows. The MTSX RSS will not run under Windows or a so-called DOS Window under Windows. The program may give the appearance of running until you try to read or write, but because Windows does not surrender control of the UART chip, you will at the least have the sort of problems you are describing and, at worst, brick the radio on an attempted write.

You might search the archives on this board for a number of threads on this topic.

olepro1 wrote:sounds correct fuel 4300, is there a fix for this condition thanks olepro

Try booting your pc into DOS. From the DOS prompt run the MTSX programming software. If your pc does not have DOS you may need to boot your pc into safe mode and try running the MTSX programming from that point...

More than likely it has been programed with CPS rather than RSS

Bruce: No that is the "Codeplug is too New for this Application" error.

Like fineshot1 said, try true DOS for running the MTSX RSS.

First off, we don't know what versio of RSS he's using, that alone could be the stumbling block he's facing if the radio was programmed last with R06.04 and he's using an earlier version, he will not be able to program the radio.

If he's got R06.07 or later, and that still causes the codeplug too new for this application error to show up, then it probably was last programmed with CPS.

I'll side with using older than R06.07 personally...get a later realease and try again.....That's my suggestion.

i am using 06-07. mod ho1ucf6pw1bn, ser 466aty3942. when i try to read the radio it says warning com with radio failed >request not acked/naked error< if i go to computer setup and try the com test everything is ok, it passes the com test. the radio has some local trunking in it and i hear them ok. i just can''t read or write to the radio i have another 2000 and everything works ok reading and writing to it. i need help or a can of gas olepro

Try swapping the front cover from your other MTS2000.

Todd

This is a little off main subject

I have had a fail code when using cps and a non motorola (crappywell) battery on a mts2000 with the last 2 ver. of cps.
I'm clueless why, but who cares, I just sell them a new NTN7144AR and all is good.

What kind of RIB are you using? I had a knock-off RIB do something very similar (I can't remember exactly what error, but it wouldn't read/write but the comm test was fine). I had to replace the MAX-232 chip, then it worked just fine again.

i have 2 sandy ganz ribs that i have never had trouble reading and writeing to max-mara spectra-mtx . but just to be sure i borrowed a true motorola rib. same thing olepro

I'd really have to question the ribbon flex inside the radio, as other radios program fine, this leads me to suspect internal troubles with the interconnects, both on the controls flex, and the front cover ribbon flex.

Check them for proper seating and make sure the clamps are pressed all the way down and seated firmly. in the sockets.

I had a similar problem with my MTS.

The RIB to PC cable I was using was 15pin to 25pin and I had a 9-pin adapter attached to the 25-pin where it goes into the PC.

For some reason, it wouldn't work properly with the adapter so I built a true 15-pin to 9-pin cable and didn't have the problem anymore.

For the record, I was running in true DOS by using the restart in MS-DOS method in Windows 98.