Batboard

I realize this list barely scratches the surface, but I've actually seen these revisions so I know they exist.

I had wondered if different revisions related to different bands, but I have a 6.83 in UHF and 900Mhz

What changed/improved with each revision? I made notes of what I've found, which isn't much so far.

1.36 -
2.01 -
3.xx - Do any of these even exist?
4.xx - Do any of these even exist?
5.41 - Last pre-Toolproofing
5.42 - Toolproofing introduced
5.60 -
5.65 -
6.13 -
6.26 -
6.27 - European firmware, NOT Toolproofed (VHF Only?)
6.58 -
6.81 -
6.83 -
7.xx - Do any of these even exist?
8.xx - Latest firmware?

I don't believe 8.xx is required for rebanding, I've seen 5.xx and 6.xx radios that have already been flashed for rebanding.

IIRC rebanding can be done on any 5.60 or greater 512K controller, it's the older 256K non-Flashport controllers that cannot be upgraded.

I've never seen any 3.xx or 4.xx controller. My 900 MTS2000 is a depot rebuild of a 1993 radio, it has all new parts (RF board, rear chassis, controller, front housing, display board etc) but still has firmware R01.55.

CPS won't write to the 256K radios.

I'd love to see a comprehensive list of firmware myself.

I have R08.71 in a radio, and I think it's the latest for the MTS, but I could be wrong..


-Marc

[quote="Mfire39"]I have R08.71 in a radio, and I think it's the latest for the MTS, but I could be wrong../quote]

That sounds about right... I think MCS2000 Is 7.71 or in that area. It doesn't follow the MTS version for version - which seems kind of odd since having 8.x out for MTS would suggest some sort of "major" revision.

-Alex

I heard that CPS won't write to a 256K controller... after I'd already done it.

I have an old Thinkpad Pentium with 98SE+ installed, only has 32mb of memory in it, and CPS complains when writing, but it works with my 1.36 800 M2. It also works on a Compaq PII desktop that I sometimes use.

That radio pukes everytime with a P4, haven't tried the P3 Thinkpad, but I don't think I want to press my luck.

MTS2000des wrote:
CPS won't write to the 256K radios.

P25Digital wrote:I heard that CPS won't write to a 256K controller... after I'd already done it.

I have an old Thinkpad Pentium with 98SE+ installed, only has 32mb of memory in it, and CPS complains when writing, but it works with my 1.36 800 M2. It also works on a Compaq PII desktop that I sometimes use.

That radio pukes everytime with a P4, haven't tried the P3 Thinkpad, but I don't think I want to press my luck.

MTS2000des wrote:
CPS won't write to the 256K radios.

Are you talking about CPS, or RSS? Computer speed shouldn't matter with CPS, since it's Windows based programming software. Even with DOS based RSS, the later versions work just fine on modern machines (such as my 1.8GHz Centrino Duo laptop).

My MTS2000 Model I did NOT like CPS, and gave me FAIL 01/98.

I'm using CPS. For some reason, that one radio just does not play well with a faster machine. I think the machine is trying to write the codeplug faster than that old firmware/controller can accept it. Since we're talking about a 256k memory chip, could it be that that chipset is just too slow for the newer machines? Same principal as trying to run an old AT card in a P4.

This 1.36 is the oldest MTS2000 that I own, everything else works fine with CPS.

Are you talking about CPS, or RSS? Computer speed shouldn't matter with CPS, since it's Windows based programming software. Even with DOS based RSS, the later versions work just fine on modern machines (such as my 1.8GHz Centrino Duo laptop).

I think MPL starts with v6.xx firmware.

O own MTS2000 with 05.40 F/W and it's have MPL.

How I can determine EU version of MTS2000 if no tags on radio? It's possible via CPS?

The EC radios that I"ve seen and the ones I own are all ###IWW####. I think the 'I' denotes manufacture at a European plant. There's nothing in the codeplug/CPS that notes it as being an EC radio, except the S/N.

P25Digital wrote:###IWW####

In serial? In model number?

The ###IWW#### is the serial number. As an example:

An MTS2000 S/N may look like this - 466ITW0000

466 - Denotes an MTS2000 Model I, II, or III

I - Denotes European manufacture (A=Ft. Lauderdale, C=Shaumberg)

T - Second letter denotes year of manufacture (I and O are not used)

W - Third letter denotes month of manufacture (I and O are not used)

0000 - Sequential manufacturing number

P25Digital wrote:The ###IWW#### is the serial number. As an example:

An MTS2000 S/N may look like this - 466ITW0000

466 - Denotes an MTS2000 Model I, II, or III

I - Denotes European manufacture (A=Ft. Lauderdale, C=Shaumberg)

T - Second letter denotes year of manufacture (I and O are not used)

W - Third letter denotes month of manufacture (I and O are not used)

0000 - Sequential manufacturing number

Thank you very much for helpful info!

My S/N is: 466AUW****. It means: MTS2000, Ft. Lauderdale.

How year (U) and month (W) can be decoded?

MotoFAN wrote:How year (U) and month (W) can be decoded?

http://www.batlabs.com/mfgtabl.html


-Marc

Mfire39 wrote:

MotoFAN wrote:How year (U) and month (W) can be decoded?

http://www.batlabs.com/mfgtabl.html

Thank you!

Guys,

MTS2000 Firmware made for US radios will work properly on EC (Euro) MTS2000?

It's been a long time since I came on Batlabs and posted a reply so here goes. I'm going to try to answer many of the questions that have been posted in this thread.

7.XX.XX - Never existed. The jump was made when the 8.XX firmware came out. I think it was 8.56 or something like that. This was due to the Nextel issue just prior to rebanding. This firmware coincided to the introduction of the PMUF6533 RF board and the cap mod to the 6500.

The issue with CPS and the AN models was very touchy. The problem is related to firmware. For some reason it was assumed that if you had a firmware of 1.55 or 1.53 etc the radio was supposed to be a MTX. We all know this isn't really the case but it seems to have stuck. CPS can program the radios but it's a game of roulette as to getting a fail code or not. Generally it's an 01/82. Technically the software doesn't support AN firmware. However, if you have an AN radio that has a level firmware then CPS will work just fine. I remember "upgrading" many an AN unit to the 6150 just because of this problem.

Firmware versions: I do recall using nearly all of those versions here in the US some/most of them were simple fixes. One I remember is an audio holes fix for units that have secure boards. Many of the others are likely just feature upgrades etc.

I think that covers everything.

Wanted to add the lower end firmwares, I could be backwards on some of these.

1.36 - Masked ROM supposed to be MTX
1.37 - flashable can be AN or MTX
1.52 - Masked ROM came in 2 flavors just like the 1.36 (top/no display and front display)
1.53 - flashable same as 1.37
2.01 - MT2000 firmware required special set up to flash
2.10, 2.11,2.12 and 2.13 all MT2000 firmware. This firmware not compatible with MOSCAD systems that require 2.01. I recall this biting us a few times.
1.55 - which was also a flashable firmware for the MTX and AN MTS2000

Here is one for the firmware experts. I have a MTS2000 with is reporting 6.27 firmware which according to this is thread is European firmware. All the numbers on the radio tell me its USA radio as well as what is reported in the CPS as far as I can tell (Model/Serial). Tags match.

CPS will not allow me to upgrade the firmware via legit means. Try to upgrade to 8.XX with an I button and 2.02 CPS. I get about 1/2 way through the firmware upgrade and it says there is an authorization error or something like that.

Any ideas?

Jason

Try to DL 2.03 and see if that works. I vaguely recall taking radios to that firmware version.

I can read and write just fine to the radio. I just get this error when doing the firmware upgrade: "FLASH Authcode Verify Error - Upgrade Aborted" at block #9.

Jason

Karfield wrote:


The issue with CPS and the AN models was very touchy. The problem is related to firmware. For some reason it was assumed that if you had a firmware of 1.55 or 1.53 etc the radio was supposed to be a MTX. We all know this isn't really the case but it seems to have stuck.

But actually it was. Years ago, when the Jedi first came out, I was at a free flea in the Motorola parking lot in Plantation. One of the big shots in the plant had a 800 MTS2000, & it was broken down on the table for all to see what was inside. The controller board had no encryption slot, & instead of having the 2 parallel chips which are on all MTS radios, it had the 1 big chip that came on all the MTX radios. The f/w was 1.53. We were told the MTS controller board was not in production yet, & until they were ready, MTX controller boards were used. So the rumor is true, the early MTS radios were actually MTX radios. GARY N4KVE

I posted this a while ago in the 900 MHz forum from a bunch of MTS2000 radios that I was moving to the amateur 900MHz band.

Two of them, a WCH and a WCF with firmware R05.53 date from '93 and '94 program and work pretty well using CPS 1.06. They just need a bit of soft pot tweaking to get the deviation right.

However another bunch of six WCD top display models with R06.14 from around '98 seem to receive OK down to around 925 MHz but won't transmit in talk around below 933MHz or so.

In fact when programmed with say 927.5 MHz they happily transmit around 939 MHz without giving an unlock indication.

I thought this was a software issue but it turned out that radios that will work in the amateur band are those fitted with the NUF6395 RF transceiver board. None of those fitted with the NUF6499 worked.

Problem fixed. Updater took care of kicking the "bad" 6.27 firmware out and then I was able to uprade to the lastest with CPS.

Thanks

Jason

KB9KST wrote:Here is one for the firmware experts. I have a MTS2000 with is reporting 6.27 firmware which according to this is thread is European firmware. All the numbers on the radio tell me its USA radio as well as what is reported in the CPS as far as I can tell (Model/Serial). Tags match.

CPS will not allow me to upgrade the firmware via legit means. Try to upgrade to 8.XX with an I button and 2.02 CPS. I get about 1/2 way through the firmware upgrade and it says there is an authorization error or something like that.

Any ideas?

Jason