MTS Failure 01/82
Moderator: Queue Moderator
MTS Failure 01/82
I am looking for some help regarding some older MTS2000 flashport portables and an issue we are having.
First please let me apologize for my lack of knowledge as I am learning this process and new to programming.
The portables in question have been read with CPS (older version not sure ver#). This is CPS using a RIB. From what I have been told these portables were programmed years ago with the same software and computer but I cannot personally verify that. No issues noted with read. The problem comes when attempting to save the changes back into the portable. No errors are noted on computer but the portable now reads F01-82. I have looked through many searches and have read up on what this error means as well as the suggested fix of reprogramming the codeplug.
When connecting the portables I receive the block checksum failure in CPS and continue unpack anyway. The portable reads correctly but will not allow the reprogram of the codeplug from memory. Restarts portable and F01/82.
What exactly does bad external eeprom and external codeplug mean and is there a fix? These are older radios that we were reassigning and are needed but not in a budget to really repair or replace. So I'm trying to get the best possible solution. Are they really bricks now or is there hope?
One portable did reprogram but here is what I noticed. The model numbers were identical across all units. The one that did work had the following visual differences: two battery prongs, orange gaskets on battery prongs and a different part number for back case. The other units have three battery prongs with black gaskets.
My local radio expert is not much help and not really working on my timeframe.... Of anytime this year.......
Thank you in advance for the help. I apologize for the sketchy information. I do not have the portables or computer with me at this time.
First please let me apologize for my lack of knowledge as I am learning this process and new to programming.
The portables in question have been read with CPS (older version not sure ver#). This is CPS using a RIB. From what I have been told these portables were programmed years ago with the same software and computer but I cannot personally verify that. No issues noted with read. The problem comes when attempting to save the changes back into the portable. No errors are noted on computer but the portable now reads F01-82. I have looked through many searches and have read up on what this error means as well as the suggested fix of reprogramming the codeplug.
When connecting the portables I receive the block checksum failure in CPS and continue unpack anyway. The portable reads correctly but will not allow the reprogram of the codeplug from memory. Restarts portable and F01/82.
What exactly does bad external eeprom and external codeplug mean and is there a fix? These are older radios that we were reassigning and are needed but not in a budget to really repair or replace. So I'm trying to get the best possible solution. Are they really bricks now or is there hope?
One portable did reprogram but here is what I noticed. The model numbers were identical across all units. The one that did work had the following visual differences: two battery prongs, orange gaskets on battery prongs and a different part number for back case. The other units have three battery prongs with black gaskets.
My local radio expert is not much help and not really working on my timeframe.... Of anytime this year.......
Thank you in advance for the help. I apologize for the sketchy information. I do not have the portables or computer with me at this time.
- The Pager Geek
- Posts: 1250
- Joined: Fri Jun 21, 2002 10:31 pm
- What radios do you own?: Disney FRS
Re: MTS Failure 01/82
Can you give model number and firmware version of the radio?
I have a feeling that you are dealing with an OLD MTS firmware revision that doesn't like the CPS codeplugs.
tpg
I have a feeling that you are dealing with an OLD MTS firmware revision that doesn't like the CPS codeplugs.
tpg
Experienced Provider of Useless Information
Re: MTS Failure 01/82
I had that fail code show up when writing to one with CPS. When I went back and hit it with DOS it corrected itself. Do you have a saved dos codeplug?
Re: MTS Failure 01/82
I will check on the model and firmware today. As well the cps version we have. Unfortunately I do not have a dos version to work with for these portables so there is probably not a dos codeplug saved anywhere. I do have 9 other portables that still work. I stopped after three died from different attempts. Only dos I have is for HT1000 and mtx. That specifically states it does not support my model type though.
Is there a way to clone from one to another on these? One of the places I read said the older MTS do not like cloning but I only saw that once.
Thanks for the help.
Is there a way to clone from one to another on these? One of the places I read said the older MTS do not like cloning but I only saw that once.
Thanks for the help.
-
- Posts: 439
- Joined: Mon Feb 20, 2006 5:42 pm
Re: MTS Failure 01/82
Yes, provided the model numbers match exactly. If you can't get it done with the rss/cps you have, then you can use a jedi cloning cable. They clone rather easily with the cable, if you have one...hfd4 wrote:Is there a way to clone from one to another on these? One of the places I read said the older MTS do not like cloning but I only saw that once.
Thanks for the help.
Terry
Terry
Re: MTS Failure 01/82
Thanks for the help.
Here is the info I was able to attain today.
Model # H10RDD9PW1BN
Serial numbers all start with 432ATJ0 (if that help to figure age)
On the radios only the new one had a series of numbers on the bottom of the label. The radios in question had nothing.....
According to CPS
Codeplug 000F
Firmware unknown
System pack H35
I also have gotten the following errors:
Invalid dos checksum header followed by unable to read file header.
The dos version I have is MTSX 2000 ver R06.08.00. When I click on the mtsx2000 icon i get the install screen. Install appears to work and finishes with "type mtsx at dos command" when I do that i get the old bad caommand or file name error..... In the readme file for the mstx it states "this version of software no longer support mts2000 radio with the model number format H01xxxxPWxxx. Please upgrade to MTS2000 CPS R01.13.00.
That's the model number I have the the cps version we have....... Any ideas?
On the cloning question. The cable I have says cloning will only work with HT and JT models. There are other cables that appear similar in the case but nothing is clearly marked. Will the cloning bypass the F01/82 error and clone the good codeplug? I have not tried this yet as I am trying to not fry any other radios and put us down even more....
THANK YOU!
Here is the info I was able to attain today.
Model # H10RDD9PW1BN
Serial numbers all start with 432ATJ0 (if that help to figure age)
On the radios only the new one had a series of numbers on the bottom of the label. The radios in question had nothing.....
According to CPS
Codeplug 000F
Firmware unknown
System pack H35
I also have gotten the following errors:
Invalid dos checksum header followed by unable to read file header.
The dos version I have is MTSX 2000 ver R06.08.00. When I click on the mtsx2000 icon i get the install screen. Install appears to work and finishes with "type mtsx at dos command" when I do that i get the old bad caommand or file name error..... In the readme file for the mstx it states "this version of software no longer support mts2000 radio with the model number format H01xxxxPWxxx. Please upgrade to MTS2000 CPS R01.13.00.
That's the model number I have the the cps version we have....... Any ideas?
On the cloning question. The cable I have says cloning will only work with HT and JT models. There are other cables that appear similar in the case but nothing is clearly marked. Will the cloning bypass the F01/82 error and clone the good codeplug? I have not tried this yet as I am trying to not fry any other radios and put us down even more....
THANK YOU!
Re: MTS Failure 01/82
I suppose you could hit it with an s record from another similar model as a last ditch effort.
-
- Posts: 439
- Joined: Mon Feb 20, 2006 5:42 pm
Re: MTS Failure 01/82
Model # indicates the radio is an MTS2000 model 1, 48 channel, 403-470 UHF, basic package with LCD display.hfd4 wrote:Here is the info I was able to attain today.
Model # H10RDD9PW1BN
Serial # indicates the radio was manufactured in Schuamburg, IL in May of 1993.hfd4 wrote:Serial numbers all start with 432ATJ0 (if that help to figure age)
Well, if you mean the series of numbers on the very bottom of the label with a bunch of zeros, that should show your flashcode... 000100000009, or similar.hfd4 wrote:On the radios only the new one had a series of numbers on the bottom of the label. The radios in question had nothing.....
According to CPS
Codeplug 000F
Firmware unknown
System pack H35
To get the firmware version in your radios you need to turn the power on, then immediately (before the radio beeps) press the monitor button (lower side button) 5 times and read the firmware off the radios LCD screen as it scrolls.
You have the very last version of MTSX RSS (latest) that Motorola released. It is rare, and it is FLAWED and full of bugs. Most shops no longer even use it. They throw it away and reinstall R06.07.00 instead or go on to CPS. Latest CPS is R02.02.00, I believe.hfd4 wrote:The dos version I have is MTSX 2000 ver R06.08.00. When I click on the mtsx2000 icon i get the install screen. Install appears to work and finishes with "type mtsx at dos command" when I do that i get the old bad caommand or file name error..... In the readme file for the mstx it states "this version of software no longer support mts2000 radio with the model number format H01xxxxPWxxx. Please upgrade to MTS2000 CPS R01.13.00.
That's the model number I have the the cps version we have....... Any ideas?
Here are some facts:
1) If your MTS2000's have been sent in to the Motorola Depot any time after end of May 2005 they must be programmed with CPS.
2) The MTSX R06.08.00 RSS is junk and causes one type of problem or another on 80% of radios you attempt to program with it.
3) If your radios have ever been programmed with CPS, then none of the RSS programs will work with them any longer.
The HT/JT cable is the same one used with MTS and MT2000's. If you are trying to clone, the F01/82 error should be over-ridden. Sometimes it may take several attempts though, and each time you try you need to start the whole attempt over from scratch. Also, make certain you MTS2000 batteries are good and fully charged when attempting to program or clone.hfd4 wrote:On the cloning question. The cable I have says cloning will only work with HT and JT models. There are other cables that appear similar in the case but nothing is clearly marked. Will the cloning bypass the F01/82 error and clone the good codeplug? I have not tried this yet as I am trying to not fry any other radios and put us down even more....
THANK YOU!
Good luck, and keep us updated here!
Terry
Terry
Re: MTS Failure 01/82
Thanks for the info. It was the flashcode seris that the radios in question are missing.
As for the cloning with a cable could you please give me instruction steps on that? I will give it a shot and hope for the best. If nothing else I cen get the radios back to working condition. I will give up on the fact of reprogramming. I can live with the channels we have in there. Only wanted to change the last 6 anyway.
Thank you!
As for the cloning with a cable could you please give me instruction steps on that? I will give it a shot and hope for the best. If nothing else I cen get the radios back to working condition. I will give up on the fact of reprogramming. I can live with the channels we have in there. Only wanted to change the last 6 anyway.
Thank you!
Re: MTS Failure 01/82
Could the problem be caused by trying to program with cps when the last program was with rss?
This could actually be the first time they are seeing cps but I cannot verify that for sure.... Or can I?
Thanks again.
This could actually be the first time they are seeing cps but I cannot verify that for sure.... Or can I?
Thanks again.
-
- Posts: 439
- Joined: Mon Feb 20, 2006 5:42 pm
Re: MTS Failure 01/82
You can read the flashcode and firmware on the LCD by turning on the radio and pressing the monitor button 5 times in quick sucession, as mentioned above. The source radios firmware needs to match the target radio in order to clone them.hfd4 wrote:Thanks for the info. It was the flashcode seris that the radios in question are missing.
You'll have to insure that your RSS or CPS is completely installed and working properly first then you need to read and save the codeplug out of one of the working radios. Then with RSS/CPS install the codeplug into the radio showing the 01/82 error...hfd4 wrote:As for the cloning with a cable could you please give me instruction steps on that? I will give it a shot and hope for the best. If nothing else I cen get the radios back to working condition. I will give up on the fact of reprogramming. I can live with the channels we have in there. Only wanted to change the last 6 anyway.
Before I go any farther, are you at all familiar with navigating Motorola CPS or RSS for programming the jedi radios?
Well, if you can read the radio the CPS shows you, first thing, the last software version it was programmed with. CPS is back compatible with any radio previously programmed with rss. Not the other way around though.hfd4 wrote:Could the problem be caused by trying to program with cps when the last program was with rss?
This could actually be the first time they are seeing cps but I cannot verify that for sure.... Or can I?
Terry
Re: MTS Failure 01/82
I'll check the radios and see if the firmware is identical. I think this may be where the problem has stemmed from. The first radio that I tried to program worked ok and then after that the issues started. Initially i tried the quick clone option in CPS and the first radio died. Then I tried another with the clone wizard, same result. Both of those were from the initial radio's codeplug file.Terry_Glover wrote:You can read the flashcode and firmware on the LCD by turning on the radio and pressing the monitor button 5 times in quick sucession, as mentioned above. The source radios firmware needs to match the target radio in order to clone them.
The third that died I am not sure what happened. I read it and changed the frequencies then tried to save it back into the radio and it failed too. I stopped at that point. I wasn't killing any more.
The CPS worked to program the first radio without issue. This is the one that may have a newer firmware. I actually managed to make changes in that radio several times. I tried the two clones with failure through the cps and then tried another straight forward and it failed.Terry_Glover wrote:You'll have to insure that your RSS or CPS is completely installed and working properly first then you need to read and save the codeplug out of one of the working radios. Then with RSS/CPS install the codeplug into the radio showing the 01/82 error....
Learning.... I have used the rss to program several ht1000's and the cps for the one mts2000 that worked ok. Other than that not much under my belt.... Sorry.Terry_Glover wrote:Before I go any farther, are you at all familiar with navigating Motorola CPS or RSS for programming the jedi radios?
Re: MTS Failure 01/82
So here is all the information I was able to obtain today. Hopefully it will help answer some questions and maybe point towards a fix.
Last program (working) date was Aug 2004 and it was done in cps. So I know rss is out of the question and it had to be done with the same computer and cps version.
Codeplug is 0007 and firmware is version 01.12. (this was the same on radios that are ok and dead radios when read with cps.)
I am unable to get the radio to display the firmware on the screen with the depressing monitor button 5 times method. Good radio or dead.
All 3 radios that are dead show the last program date of when I tried to reprogram and when I tried the suggested fixes today they show todays date and timestamp for last program.
The methods I attempted today are as follows:
Cloning radio to radio. I had two versions of radio-radio cables. One for HT/JT with 3 prongs and one that I think was for our newer xts with 5 or 6 prongs. Followed the directions as listed with zero results. All that ever happened is the dead radio failed and the good keyed up. Tried multiple times, tore down and restarted to make sure all was correct.
Cloning in cps. No luck. I get the errors: Communication with radio failed. Please try again. After several attempts and the same error the most i could get was another error. This error was received when I would accept clone radio in cps and then turn the radio on. It would sit at self test and after a little give the error: Radio and codeplug feature set are different. Cloning cannot continue.
Tried the clone wizard, clone file only, Opened a good file, changed the serial number and ten attempted to save to radio. Nothing. Except another error... Communication with radio failed....
When I read the radio with cps i get the following: Block checksum failed for Vector for external radio blk Block. Continue unpack anyway? After that it will read the radio information and when trying to save to radio is when the communication with radio failed error appears....
I am using a rib which should be correct. This is too old to use a usb ribless version correct? I think that's for the xts.
I'm at a loss.
Thank you all for the help. I appreciate it.
Last program (working) date was Aug 2004 and it was done in cps. So I know rss is out of the question and it had to be done with the same computer and cps version.
Codeplug is 0007 and firmware is version 01.12. (this was the same on radios that are ok and dead radios when read with cps.)
I am unable to get the radio to display the firmware on the screen with the depressing monitor button 5 times method. Good radio or dead.
All 3 radios that are dead show the last program date of when I tried to reprogram and when I tried the suggested fixes today they show todays date and timestamp for last program.
The methods I attempted today are as follows:
Cloning radio to radio. I had two versions of radio-radio cables. One for HT/JT with 3 prongs and one that I think was for our newer xts with 5 or 6 prongs. Followed the directions as listed with zero results. All that ever happened is the dead radio failed and the good keyed up. Tried multiple times, tore down and restarted to make sure all was correct.
Cloning in cps. No luck. I get the errors: Communication with radio failed. Please try again. After several attempts and the same error the most i could get was another error. This error was received when I would accept clone radio in cps and then turn the radio on. It would sit at self test and after a little give the error: Radio and codeplug feature set are different. Cloning cannot continue.
Tried the clone wizard, clone file only, Opened a good file, changed the serial number and ten attempted to save to radio. Nothing. Except another error... Communication with radio failed....
When I read the radio with cps i get the following: Block checksum failed for Vector for external radio blk Block. Continue unpack anyway? After that it will read the radio information and when trying to save to radio is when the communication with radio failed error appears....
I am using a rib which should be correct. This is too old to use a usb ribless version correct? I think that's for the xts.
I'm at a loss.
Thank you all for the help. I appreciate it.
- MTS2000des
- Posts: 3347
- Joined: Sat Jan 04, 2003 4:59 pm
- What radios do you own?: XTS2500, XTS5000, and MTS2000
Re: MTS Failure 01/82
I've had this problem with old MTS2000's that have early (1.xx) firmware versions, calls to the RSC lead me to being told that a 256K controller, such as these early radios are NOT compatible with CPS. I've had some that will read just fine in CPS but get a FAIL 01/82 on write, or not write at all. Usually reverting back to a DOS codeplug brings it back to life. IIRC the MTS2000's have the have a firmware version of 5.60 or greater to be "officially" supported by current MTS2000 CPS (yet I have a ton of 5.42, 5.51 etc that have 512K controllers and read/write just fine with CPS R02.02).
You say the same computer was used? I'd put lots of money lots of changes have taken place on that machine in 4 years.
Newer versions of Windows are out, several service packs, etc.
The good news is if the firmware versions are that old, there is no risk in toolproofing the controllers from using that "version we don't speak of" and forcing a good codeplug into them to bring them back to life. Of course this will mean those radios need a proper alignment and tune-up, but better than chunking them.
MTSX 6.07 is the last DOS RSS worth a hoot for the MTSX- just don't try reading or writing running under any NT kernel based Windows (NT4, 2000, XP, Vista). Use a DOS boot disk (or even Win95/98 Safe mode command prompt only) and it runs fine even on a P4 2.6GHz CPU.
You say the same computer was used? I'd put lots of money lots of changes have taken place on that machine in 4 years.
Newer versions of Windows are out, several service packs, etc.
The good news is if the firmware versions are that old, there is no risk in toolproofing the controllers from using that "version we don't speak of" and forcing a good codeplug into them to bring them back to life. Of course this will mean those radios need a proper alignment and tune-up, but better than chunking them.
MTSX 6.07 is the last DOS RSS worth a hoot for the MTSX- just don't try reading or writing running under any NT kernel based Windows (NT4, 2000, XP, Vista). Use a DOS boot disk (or even Win95/98 Safe mode command prompt only) and it runs fine even on a P4 2.6GHz CPU.
The views here are my own and do not represent those of anyone else or the company, the boss, his wife, his dog or distant relatives.
-
- Posts: 439
- Joined: Mon Feb 20, 2006 5:42 pm
Re: MTS Failure 01/82
I've never messed with (or seen) an MTS with a firmware number that low. I've programmed dozens with f/w 05.42 and higher without problems, but 01.12, if it is an MTS f/w, may have some quirks that I'm not familiar with.hfd4 wrote:So here is all the information I was able to obtain today. Hopefully it will help answer some questions and maybe point towards a fix.
Last program (working) date was Aug 2004 and it was done in cps. So I know rss is out of the question and it had to be done with the same computer and cps version.
Codeplug is 0007 and firmware is version 01.12. (this was the same on radios that are ok and dead radios when read with cps.)
Never had that happen either. Every MTS2000 or MT2000 I've ever seen will display the f/w in service mode. Again, maybe that firmware is outside my experience.hfd4 wrote:I am unable to get the radio to display the firmware on the screen with the depressing monitor button 5 times method. Good radio or dead.
You will not be able to clone the MTS2000's radio to radio, that's simply not supported. You need to save a good codeplug and clone it into the target radio via software only. HT1000, JT1000, MT2000 and MTS2000 all program with the same RIB to radio cable, but only the HT, JT and MT2000 can be cloned radio to radio with that double ended cable.hfd4 wrote:All 3 radios that are dead show the last program date of when I tried to reprogram and when I tried the suggested fixes today they show todays date and timestamp for last program.
The methods I attempted today are as follows:
Cloning radio to radio. I had two versions of radio-radio cables. One for HT/JT with 3 prongs and one that I think was for our newer xts with 5 or 6 prongs. Followed the directions as listed with zero results. All that ever happened is the dead radio failed and the good keyed up. Tried multiple times, tore down and restarted to make sure all was correct.
No, you don't want to mess with a USB ribless cable with those IF you already have a working RLN4008 RIB and RKN4035 cable.hfd4 wrote:Cloning in cps. No luck. I get the errors: Communication with radio failed. Please try again. After several attempts and the same error the most i could get was another error. This error was received when I would accept clone radio in cps and then turn the radio on. It would sit at self test and after a little give the error: Radio and codeplug feature set are different. Cloning cannot continue.
Tried the clone wizard, clone file only, Opened a good file, changed the serial number and ten attempted to save to radio. Nothing. Except another error... Communication with radio failed....
When I read the radio with cps i get the following: Block checksum failed for Vector for external radio blk Block. Continue unpack anyway? After that it will read the radio information and when trying to save to radio is when the communication with radio failed error appears....
I am using a rib which should be correct. This is too old to use a usb ribless version correct? I think that's for the xts.
I'm at a loss.
Thank you all for the help. I appreciate it.
Hopefully some one else will come along and be able to help you.
Good luck!
Terry
Re: MTS Failure 01/82
The situation has been resolved. Thank you allfor the input.
We managed to confirm the original program was not from the computer in question but a private computer. A good codeplug was read then programmed to the three dead portables.
Thanks.
We managed to confirm the original program was not from the computer in question but a private computer. A good codeplug was read then programmed to the three dead portables.
Thanks.