General Information
Most of this information is for the Astro Saber, but since the XTS3000 and its family are programmed by the same RSS, a lot of the information will be relevant for it too.
All these radios use a standard SMA connector for the antenna. The radio end is a male. Be sure that you use a high quality adapter if you are going to convert from the SMA to something else. There are some cheap adapters that have a recessed center pin on the female side. This causes problems since the center pin on the radio may not make contact and you will be transmitting into an open (bad).
The radio uses a third generation keyloader, there is a retro kit to upgrade the DES-XL key loader, and the data in and out pins are different.
Only keyloaders with a model suffix DX or later will properly keyload an Astro, while BX & CX (as well as DX) models will work fine with a regular Saber.
For keyloading, you use the same cable as a regular Saber, TKN8506, and the pinout is available here.
The part number for the HHCH for the XTS3000 Vehicular Adapter (XTVA) may be PLN7737A (unconfirmed).
Here you can find the Astro Portable model breakdown chart. Note that it is the same as the one for the mobiles, except for the available power levels and the "H" at the beginning of the model number to denote portable.
A listing of the flash upgrade options can be found here.
You may also want to look at the Saber Page.
Take a look at the programming cable for the Astro Saber. The programming cable for the XTS3000 and XTS3500 is the same as the other Jedi radios, RKN4035A, and its pinout can be found here.
You may also want to take a look at the RKN4046A Flash/Service Cable. This cable is for the Astro Saber and Saber Si. This cable is made up of the following parts:
| Reference | Part Number | Description |
| 1 | 0984538E03 | Receptacle, 25 Pos |
| 2 | 1580349B36 | Housing, Connector |
| 3 | 3000864145 | Cable, 5 Conductor |
| 4 | 0180754R26 | Plug Assembly |
| 5 | 4210217R24 | Strap, Tie |
| 6 | 3880373L24 | Protective Cap |
| 7 | 0410058B12 | Washer, Nylon |
| 8 | 0960113A07 | Connector and Cable |
| C1 | 2184008H06 | Capacitor, 33 nF |
| R1 | 0611009C59 | Resistor, 2.7 kohm |
| R2 | 0611009C73 | Resistor, 10 kohm |
By the way, if you thing you can make yourself a cheap cable by just ordering part number 0960113A07, well, forget it. The current list price for that item is $166US.
Astro Saber and LAPD
There seems to be a number of people interested in the Astro Sabers that the LAPD uses. This section will try and answer many of those related questions.
First, the radio that the LAPD is using is the H04SDH9PW7AN.
You are probably better off not trying to get Motorola to flash your Astro Saber "just like LAPD's". Motorola considers FlashCodes 840101-8F0000-4 and now 540001-070000-7 to be RESTRICTED. If you send in a radio to the depot for service with one of these flash codes, they will only send it back with H35 and you have to buy any upgrades you want for the radio.
If you do try to get that flashed into your radio, Motorola security may get involved and start asking questions. Although it IS legal to ask about it, Motorola may not do it and may get nosey.
There is not much they can really do, since you are only inquiring about it. Remember though, that if you are fishing for FlashCode info while talking to Motorola, and you give three codes in a row with invalid data (including the last checksum byte), you will probably find yourself transferred to someone in Security to speak with.
By the way, the options contained in FlashCode 840101-8F0000-4 are:
Emergency Receive
H869 Multikey Operation
H39 Selective Radio Inhibit
H35 Conventional Operation
H29 Software Encryption
Q351 MODAT
Q352 Soft Id
Q353 OTACR (Over The Air Channel Reassignment)
Q354 OTACS (Over The Air Channel Steering)
The options in the new FlashCode 540001-070000-7 are:
H14 Digital ID Display Q806 ASTRO Digital CAI (IMBE) Operation H869 Multikey Operation H35 Conventional Operation Q352 Soft ID Q353 OTACR (Over The Air Channel Reassignment) Q354 OTACS (Over The Air Channel Steering)
Now you know. If you want to have your radio working close to a LAPD model, have your radio flashed with something similar, by dropping one of these options (one of the lesser important, like H869, since you'd not likely get your hands on keys anyways).
If you want to just be able to monitor the LAPD, you need a FlashCode of at least 100001 000000 1 (guessing at the checksum). This gives you options Q806 and H35. Those are the minimums. If you have any conventional Astro with a first digit FlashCode that is odd, then you should have option Q806 and be able to monitor the LAPD. The rest of the FlashCode shouldn't really matter all that much.
Modat can in fact be used with both IMBE and VSELP radios. It's Software Encryption that can't (isn't supposed to) be in an IMBE radio.
There is no such thing as "Astro encryption" as such. The encryption types that can be used in an Astro system are the same types used in standard systems... DES, DES-XL, etc.
However, if your radio is CAI compliant, you can set the "RX Unmute Rule" to "Digital Carrier Squelch" and that will decode ALL Apco-25 compliant digital signals! (Excluding encrypted ones, of course!)
Converting Astro's to the "LAPD" Setup
An Astro Saber can be made to operate just like the LAPD codeplug (old version) does.
Here are some things that you need to watch out for:
OTACS/OTACR
You need to program in the RSS one astro channel (you can delete it later). In that channel screen, go into Astro options (F6) then (F7). Disable both the OTACS and OTACR options. Under that you will see a table. Make sure that the CCS Pos 1 is set to Zone 1 and Channel 1, and set CCS 2 to Zone 1 Channel 2 all the way to position 16, or the channel selector WILL NOT work properly.
+------------------------------------------------------------------------------+ �MOTOROLA Radio Service Software �Use UP/DOWN Arrows to Select Choice. � �ASTRO PORTABLE Model: H04SDH9PW7AN � � � � � �...CONV:PERS:OPTIONS:OPTIONS:OTACR � � �------------------------------------------------------------------------------� � OTACR/S � � ------- � � Change-> OTACR Feature....Enabled OTACS Feature....Enabled <-Change � � OTACR Command Limited Patience Time (ms)...6375 � � � � CSS Pos Zone Channel CSS Pos Zone Channel � � ------- ---- ------- ------- ---- ------- � � Change -> 1 1 107 9 1 113 <-Change � � All of 2 1 104 10 1 110 � � these 3 1 105 11 1 106 � � 4 1 20 12 1 109 � � 5 1 21 13 1 112 � � 6 1 22 14 1 111 � � 7 1 23 15 1 28 � � 8 1 108 16 1 19 � +------------------------------------------------------------------------------+ F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 HELP EXIT
BAND CONVERSIONS
This must be done with LAB for the LAB options. Under the hidden LAB options, you must change the band to what the radio has in it. You will also need to have a codeplug that will work with the radio in the service menu in normal RSS. The serial number needs to be the same. What you will have to do after the "upgrade" is to load the old codeplug into normal RSS and go into the service menu. Program the old values back into the radio. DO NOT READ THE RADIO FIRST - LOAD THE OLD CODEPLUG FIRST. This way the values from the old plug will override the values in the plug that you just loaded into the radio. Its the TX/RX alignment screens that you need to deal with. If they are not changed, your radio will not properly lock, hence useless.
MODEL NUMBER/SERIAL NUMBER
Make sure in lab that you change the codeplug model/serial numbers to the one your radio is assigned with. Makes life easier in the future.
OLD INFO
The best thing to do is the erase all the old info prior to loading it up. If you leave all the old info and program the radio, you may not be able to access certain screens.
This upgrade has been performed two ways, and they both worked. One was to use the CLONE menu, and the other was the straight F8 program radio menu. Both most likely do the same thing.
REMEMBER: Always keep a backup copy around.....just in case!
How to Tell if Your Radio is CAI Compliant
CAI compliance is most easily determined by going into the RSS and doing the following:
IMBE, VSELP, and MODAT
If you want to determine whether your radio is VSELP (Vector Sum Excited Linear Prediction) or IMBE (Improved Multi-Band Excitation), look in RSS at the Astro ID number. Try changing the ID. If it will not go above 16773119, it is a VSELP. An IMBE radio will let you use anything up to ID 99999999.
You can convert a VSELP radio to IMBE if you have the version F, or G vocoder boards (1 Meg Boards) in other words any radio with a 1 meg vocoder can be converted be used for either IMBE or VSELP but not both.
IMBE and VSELP radios are both capable of using software encryption.
The options for getting a radio to do MODAT are as follows:
VSELP, IMBE and iDEN
iDen is VSELP based. It allows for up to 6:1 compression using TDMA (Time Division Multiple Access).
We have reason to believe that TDMA decoding is a built-in function of the Astro hardware, part of the modulation scheme. Although, this information is not documented in the software or mentioned in the service manuals (we are still trying to confirm all this for sure).
We have been told that there may be able to monitor iDEN radio traffic using an Astro Saber.
What you need to do is take a VSELP Astro of the appropriate band and cram an IMBE codeplug into it (using Lab or whatever).
The theory behind this being that you should be able to use the "digital squelch" options of the codeplug, along with the VSELP hardware to monitor the traffic.
We have no idea if this works for sure or not, but hey, you never know!.
HOST/DSP Information
First off, it appears that every XTS-3000 has a 1M vocon board. The ASTRO Saber's on the other hand could have either 512k or 1M.
In a fully compliant, Project-25, Astro, digital tunking system (9600 baud control channel, etc.), you must have a radio with e 1M vocon board, and the HOST firmware version must be equal or greater then R07.00.00.
For every HOST firmware version, there is a matching, correct, DSP version to go with it.
There is no way to get HOST version R07.00.00 in a 512k radio.
The highest HOST firmware version that a 512k radio will take is R05.60.00. And, the matching DSP version for this 512k radio is R06.05.04. If those matching versions are are not present together, you may find that some features are missing or not working correctly.
Radios which are correctly programmed, and upon reading show ???????? in certain fields are probably affected with this HOST/DSP firmware mismatch problem.
Any radio that displays "UNKNWN" in the self test sequence is one that may have been incorrectly field upgraded, or maybe hacked. It pretty much means that the radio has had its feature set changed by possibly an unapproved procedure. It is possible that this could have been done at the depot or factory when a quick change/revision was necessary, but the correct tools were not available.
You will find that only radios that have version R04.00.00 or higher HOST firmware are capable of showing the "UNKNWN" error, or the vocon board size (512k or 1M). If the radio has the "UNKNWN" error, it will usually replace the field that would show the vocon board size during the self test sequence.
Flash Upgrading
You will probably want to see the Flash Upgrading Primer page to find out more information about flash upgrading your radio.
You may also want to check out the Flash Code Decoder if you want to see what is included in a particular flash code. The interactive version is pretty cool too.
Note that these flash decoding tools have been updated recently, and should be pretty accurate.
Getting flash upgrades is nearly impossible unless you're an original purchaser of the radio from Motorola directly. Officially, they don't sell any flash upgrades to any secondary market radios. Exceptions are rare.
Service Manuals
Here are a listing of the Service Manual part numbers for this series of radios:
Saber Accessory Connector Pinout
The pinout can be found here.
The Astro Saber uses a small, recessed, plunger type button, just under the retaining screw receptacle on the radio. This is how the radio decides whether to use the internal or external antenna, when pressed in, it selects the external antenna.
Astro Vehicular Adapter (AVA) Information
We have heard the question often, "What's the difference between an Astro Saber Vehicular Adapter (AVA) and a normal Saber Vehicular Adapter (SVA)?".
The front panel of an AVA IS physically different than the one on an SVA. If you look at the bottom area of the accessory connector on an Astro Saber you will notice that there is a raised area (bump) on it. That bump is there to keep you from putting an Astro Saber into an SVA. The AVA's front panel has additional clearance in that spot to allow the radio to enter.
Furthermore, the firmware chip in an AVA is believed to be an updated version of the firmware in an SVA. The main boards in both the AVA and the SVA may be the same otherwise. The firmware changes adds the support for the Astro.
An AVA has been confirmed to be UNIVERSAL to ALL radios that carry the Saber name of any type. Astro Sabers, Sabers, the Saber SI, and Systems Sabers will work in an AVA. You can switch display microphones as required for the individual radios. That is not true of the SVA.
To date, no ConvertaCom for any RUGGEDIZED Saber series radio of any description has ever been sighted.
The part number for the Astro AVA is NTN7227BSP01. Other revisions exist, in which case the B in that part number is replaced with a C, D, or E, which is the most current version.
The part number for a standard SVA is NTN5487A.
There is a decal on top of the Astro SVA that gives the following useful data:
"CAUTION: Inserting the wrong radio may Damage the Adapter. This Adapter works with ASTRO Digital SABER, SABER and Systems SABER radios manufactured on or after September 1, 1994. These radios can be identified by their serial numbers: The 5th character (year) must be "U" or later (V, W, X, Y, or Z). If 5th character is U, the 6th character (month) must be "S" or later (T, U, V, W, X, Y, or Z). Use Adapter ONLY with approved radio models. For radios manufactured prior to this date please contact: Motorola at 1-800-523-4007 (ext. 112) for upgrade details."
One thing to note when using your AVA, if you pull the radio out while it is on, you may loose your volume control (any other controls). This may be intentional, or it may be a firmware issue. Since the AVA doesn't know when you are going to remove the radio from the cradle, it can't completely return control of the radio to the user before it is detached. As a result, some radios still pretend that they are in the AVA, and don't respond to user controls without a power cycle. On the other hand, there are some radios that seem to work fine some/all the time when they are pulled out of the AVA. This points to the firmware in the radio and the newer revisions may be able to compensate for the loss of the AVA control without the radio being power cycled. Just something to be aware of.
Out of Band Information (DOS RSS)
The following applies to all DOS versions of Astro RSS. For Windows CPS, check here.
SAVE BACKUP FILES BEFORE YOU BEGIN
The later versions of Astro RSS are a combined portable and mobile software package. As a result, there are two files of interest Astrop.odb for portables, and Astrom.odb for mobiles.
Both these files are write-protected, and that protection must be removed before editing them. You can use Windows Explorer to do this (by using the File/Properties menu). You can also navigate to the file through My Computer and right click on the file to access the Propertied menu and then de-select the read only attribute.
So now you have two unprotected .ODB files. Use a Hex editor to make the changes. Open the file you want to edit, and using the search or find functions of the software, search out the ORIGINAL band limit of interest to you (eg. to pick the lower end of UHF 450-520 split use "450.0000"), and having confirmed that it's there, do a global search and replace of that band limit with your intended limit, example take it down to 430.0000. You want to do a global search because that way you make all adjustments you need at once, transmit, receive, and every other place the software looks. If you need to, make sure you are doing a text search or ASCII search for the string.
Save the files, run the software normally and enter your new out of band frequencies that will be accepted and programmed. If it's a reasonable change, the radio will take it and it will work. Some people have had success taking a 450-520 radio down to 430.0000 (haven't tried any lower than that) and have taken it as high as 535.0000. Your mileage may vary.
Getting Around "Codeplug Too New For This Application"
No doubt you know that the RSS automatically 'upgrades' the radios that are programmed with it so that no EARLIER version of software will work on that radio. The infamous "Codeplug too new for this application" message.
There is a way around this, sort of.
What you need is an OLD codeplug from the same radio, or type of radio, that you want to use with older software. The model number needs to be the same, and the FlashCode should be the same (this has not been tested with radios and files of differing FlashCodes, it might just complain, and then again it might end up in a paperweight radio).
The old radio codeplug needs to be one that can be read by the Version B03.04.00 Depot RSS.
Load that codeplug into the Depot RSS. Add your channels, scan lists, etc. Go into the hidden LabTool menus (F9 works in places where the area over the F9 button is blank like there's no feature available) and make whatever changes you want. LabTool Configuration 2 will allow you to put up to 16 software encryption keyslots into the radio if software encryption is set up in your radio (Multikey Operation), but if you try them out, you will find that they are really only the first five keys repeating over and over. From here, you can even change the controller's operating frequency band from VHF to UHF low or high, or 800 MHz (not to say that it will actually work there since the RF sections are different, but it is there anyways).
So, you've got your lab codeplug ready, and a radio with a new codeplug that isn't going to take that codeplug, right?
Wrong! Rather than PROGRAM the radio, you go into the CLONE menu, read the serial number, and then CLONE the codeplug into the radio! Error checking is minimal, consisting of the serial, model number, and (probably) the FlashCode, and that's about it.
When you're done programming the radio, it can now be read by the Depot B03.04.00 RSS directly, along with other older versions. And once you HAVE those extra features in your radio, you can use your newer RSS and always know that you can go back and use LabTools on your radio again by following the same procedure.
A word of caution: Your "old" files that were SAVED TO DISK or programmed into the radio with the OLD software are precious. If you read one of those files and then save it with NEWER RSS, it won't work with the Depot software anymore, so keep those old files away from the newer RSS! You can use any software version you want to on the radio, including the newest one, but you've GOT to safeguard the old codeplug!
As a side note to all this... one interesting thing to note about this procedure, you could use it to transfer codeplugs between different radios.
The reason this would be useful is if you have an RF board that needs a controller, but all you have is an old archive from the radio and a controller from a different radio with the wrong bandsplit that you want to use.
If you took that codeplug and loaded it into the donor controller using read/write with no pack/unpack, you could in effect re-initialize the controller.
There are limitations to this, though. The HOST and DSP should be similar if not exact between what the codeplug you are using is set up for and the controller you are dumping it in to. If they are different, it may not work, or you could kill the donor controller.
Proceed with caution, and always have a backup codeplug in case you screw up.
The Toy of All Toys...
There are several references to an SP version of the Astro Saber that is equipped with Fascinator Securenet, AND works with GE/Ericsson's EDACS format trunking. The word is that this ultra-special radio was created in response to a Marine Corps special requirement for a radio that would work with their land based EDACS system and would also have Fascinator encryption in conventional operation for (mostly) tactical and/or offshore operations. Fact, or fiction... who knows at this point.
Motorola was able to supply this item because Ericsson doesn't have authorization to produce or have Fascinator encrypted technology since they are not a US-based company. Supposedly this special radio type is in use at a Marine Corps base in the vicinity of Corpus Christi, Texas.
We have been advised that such a radio does in fact exist, and has been confirmed. As to any further details on the unit, SP number, flashcode, model number, etc. have yet to been provided. The true capabilities of the radio are not known, but it looks like the Fascinator part is true, click to see the radio label.
Astro Lab B03.04.00 RSS
NOTE: The following information is VERY dangerous to play with. It is all a matter of one wrong keystroke and you turn your expensive radio into a paperweight. You have been warned. The only reason that Motorola doesn't complain too loudly about people doing this is because when you want that paperweight fixed... they get to charge you whatever they want! :)
You will find that version 3.04 Astro Depot Lab software is perfectly capable of doing a direct read/write with no unpack and S-record conversion on all radios (of this type), even on radios that have been programmed with the newest software.
You can also transfer the codeplug you read to ANY OTHER radio of the same type, regardless of the version of the programming RSS, but you have to use the read/write without pack/unpack menus. Do not attempt to unpack, edit s-records, or anything, just do a straight transfer. If the hardware and firmware are compatible, it'll work. But it completely clones the radios, and overwrites the old codeplug information in the target radio. Model, serial, the whole bit. You would probably want to try and correct those IF you can.
As far as editing the codeplug with the Lab RSS goes, there really isn't much you can do if you have a newer codeplug. You can NOT unpack the newer S-records with this software, so there are no changes possible this way. All you get is a block type mismatch when it tries to do the unpack (it expects a different S-record layout). As a result, you can't use Lab to open and edit the features stored in the S-records directly.
The new type S-record layout, and the one the Lab RSS expects are sufficiently different that a direct comparison between two codeplugs of IDENTICAL content but written with different software shows the two files to be very different, to the point that comparing the two by hand would be virtually pointless.
On another note... a dead UHF Astro Saber was sent into Motorola for repair*, it came back working, but with a totally basic FlashCode. This radio was a good candidate for experimenting. This "useless" radio was read (with new enough regular RSS) and the codeplug file saved (just in case...).
The radio couldn't be read with Version B03.04.00 Lab, but there are LAPD-style codeplug archives to work with. :)
A different Astro Saber was read with Lab, and CLONED it directly into the new radio. The full clone explained above took place. The serial number and everything else was transferred into the target radio. This included the FlashCode.
Once again, the trick when you are doing the transfer is NOT to unpack the data. Leave it packed during the trip from one radio to the other (read/write with no pack/unpack).
MODAT SIGNALLING NOW WORKS (the cloning source radio has MODAT).
Software encryption transferred, but it is really STRANGE now. It is not usable because the noise coming out of the other radio sounds like insane crickets in a blender. Chirps, squeals, all kinds of odd noises. The reason why software encryption can become non-functional in a cloned radio is because of a version mismatch for the DSP in the radios. It must be of the same version if they are to work properly.
The DSP processes the audio differently in software encryption mode, depending on the DSP version. So if you have two radios with different DSP versions and you clone software encryption enabled codeplugs into them, the radios may not work properly in software encryption mode, but they should be fine if their DSP versions match.
The transfer may have been a one way street. Newer software DOES check the FlashCode before cloning and it wasn't possible to get the old software to read the newer codeplug.
No clue as to whether or not this trick will work on all radios.
It is presumed that cross-FlashCode cloning will work perfectly on any radios that are VSELP based. The Lab RSS is merely a tool for reading and writing to the radios in the most basic of modes, and could really care less of what all the features are.
So, this version of RSS CAN be used in place of the FlashPort system in some situations. Provided that you understand that this is an all-or-nothing cloning operation at this time. For example, MODAT WILL transfer, and so will some other features, but no clue as to exactly which ones, yet.
However, IMBE/VSELP conversions are NOT going to happen this way.
We are under the impression that this technique will work on H-options, not Q-options. We believe that Q-options actually require reprogramming the firmware in the radios, and H-options merely need to be switched on and off. Q-option changes would absolutely REQUIRE a SmartRib and upgrade files, since the programming voltages for the firmware chips need to be provided externally if Motorola is to be believed.
Something else...
An Astro Saber with a problem was recently 'converted' from one band to another (800 to VHF in this case) using Version B03.04.00 Lab software and the 'hidden menus', and replacing the RF deck with the right one for the new band. It is important to adjust the model number to be correct for the new band or the 'normal' software may not recognize the radio.
The results of this experiment? Success. Astro 8.5 has no problem with this radio and it seems to be normal in every respect for a radio with this feature set.
Again, this must be undertaken with great caution, the HOST/DSP versions need to match or be very close (see above) or you get a paperweight. This does not change the FlashCode in the radio, but if the firmware in the target controller is high enough, it can work like a charm.
Newer versions of Lab RSS do exist. Supposedly there is one around version 5 or so, as well as one that is around version 8. We do not know anything about the capabilities of these versions of software, other than they are out there, somewhere.
We have heard that the version 8 Lab RSS is VERY tightly guarded and protected. I is supposed to be able to be installed only on one computer at a time and the disks are copy protected. Rumour has it that this version has the capability to generate FlashPort upgrade packages, and has the ability to get new HOST and DSP firmware packages for integration into the FlashPort upgrades. This is all rumour of course, and it would be one nasty thing to get caught in the un-authorized possession of... you'd be in prison for a LONG time.
*This was an unusual case because they actually accepted the radio for flat rate repair, and actually did the work on flat rate. This is not typical for a radio that is privately owned. If you have a shop send in the radio, you'll pay a service charge, but your chances of getting a flat rate repair are much greater.
The "New" RSS (Windows CPS)
The Astro CPS, version 1.00.00 has been released. This package has the part number of RVN4182, covering the portables, XTS3000 and Astro Saber. Astro Spectras are covered by RVN4183.
The package deal, carrying both of the above titles, is RVN4184.
Current subscribers to the DOS Astro package, RVN4100, receive RVN4184, the combo value meal.
Support for the DOS versions will discontinue until the end of August, 2002, at which time only Windows based CPS software will be available. Until that time, subscribers will receive support for both DOS and CPS. At this point in time, the CPS will be version-for-version compatible with the equivalent release of the DOS RSS. This will continue to be the case in all upcoming revisions until August, 2002. Any CPS revision will be accompanied by an equivalent RSS revision, and the two packages are intercompatible.
We have heard from some of the users of the new CPS. The initial evaluation of this software follows.
This will take a little getting used to, but it has the right features and allows rapid viewing of large blocks of channels at a time, with multiple option fields in view. This WILL result in faster and more accurate programming. Thumbs up.
The navigation structure is undoubtedly simpler to get around. There are some options that are more than eight keystrokes into the tree on the DOS RSS, and it's easy to miss something important. With the CPS, you can search by keyword for the option you want, and then click straight to that field. It also shows enough fields at a time that locating ANY option is very simple.
This CPS package has clearly defined support for the Astro HHCH, applicable primarily to the use of an XTS-3000 in an XTVA with HHCH, but also quite applicable to those who have Astro Sabers and HHCH compatible AVA's. The HHCH's top and side buttons can be programmed directly via the CPS, which is a feature that hasn't been seen on the DOS RSS since before version 6.5.
It has been discovered that if the CPS reads a radio that has hacked bandsplit limits (frequencies out of band), the CPS WILL..I repeat...WILL allow those frequencies to remain in the codeplug unchallenged unless you retype them. The cursor can be moved around in the frequency entry boxes without causing the software to reject the out of band frequencies. You can even press the ENTER key while the cursor is in the box. This allows previously frequency-hacked radios to be read and written via the unmodified CPS without losing any of the special data. This must have required a conscious decision on the part of the programming team, and Motorola is to be commended for this slightly hacker-friendly decision. Perhaps there is hope for them.
(As a side note, I have heard an unconfirmed report that the majority of the computers running the RSS in Motorola's labs and facilities have been bandsplit hacked... the same hack reported here... how flattering :) Probably the only reason that the hack isn't part of the standard package is the FCC-accepted operating frequency range of the radios as manufactured. But FCC certification isn't necessary on the ham bands anyway.)
On the down side, the Astro CPS is hard limited to accepting a maximum of FIVE software encryption keys (part of the Multikey Option), while the DOS version will accept up to 16. A UHF Astro Saber (an LAPD one) got tweaked to have 16 keys instead of the default five, and the CPS won't read those radios (errors out) until the default setting of five keys is restored via lab. This isn't really a problem though. It has been determined that even if you have more than five keys programmed into the radio, if you actually try them, you will find that there are really only five keys, and after number five they just repeat starting at key one. So, having to go back and correct the radio to the default of five is no great loss, since it appears that the hardware doesn't support anymore anyhow.
Now, as far as out of band hacks go, some progress has been made. You can check here for details.
Lower Case Display Letters
The radios that are capable of displaying lower cased letters are caused by manually editing the codeplug file.
We know of someone who has done it this way, and it works just fine. However, it is not an easy task, and takes a lot of time to edit.
Available Bandsplits (per RSS)
The available bandsplits (per the RSS) are:
VHF 136-174 (1W/5W), 174-178 (1W/4W)
UHF-LO403-470 (1W/4W), UHF-HI450-512 (1W/4W) 512-520 (1W/3W)
800/900 (3W)
Astro Saber Error Codes
Here's a list of the error codes that may be displayed on your Astro Saber, and their meaning:
| Error Code | Description | Action |
| 01/02 | External EEPROM Checksum Non-Fatal Error | Reprogram the Codeplug |
| 01/81 | Host ROM Checksum Failure | Reprogram the FLASH Memory |
| 01/82 | External EEPROM Checksum Failure | Reprogram the Codeplug |
| 01/84 | SLIC Initialization Failure | Turn the radio off then on |
| 01/88 | MCU (Host uC) External SRAM Failure | Turn the radio off then on |
| 01/90 | General Hardware Failure | Turn the radio off then on |
| 01/92 | Internal EEPROM Checksum Failure | Reprogram the Codeplug |
| 02/81 | DSP ROM Checksum Failure | Reprogram the FLASH Memory |
| 02/82 | DSP External SRAM1 Failure U402 | Turn the radio off then on |
| 02/84 | DSP External SRAM2 Failure U403 | Turn the radio off then on |
| 02/88 | DSP External SRAM3 Failure U414 | Turn the radio off then on |
| 02/90 | General DSP Hardware Failure (DSP startup message no received correctly) |
Turn the radio off then on |
| 02/A0 | ADSIC Checksum Failure | Turn the radio off then on |
| 09/10 | Secure Hardware Failure | |
| 09/90 | Secure Hardware Failure | |
| 001 | Synthesizer Out of Lock | Reprogram the Codeplug/Replace RF Board |
| 002 | Selected Mode/Zone Codeplug Checksum Error | Reprogram the Codeplug |
Note: If the corrective action does not fix the failure, replace the controller board.
Astro Saber Test Mode
Getting into test mode is the same as most of the newer handheld radios. To get into test mode, do the following:
| Name of Display | Description | Appears |
| SERVICE | The literal string indicates the radio has entered test mode | Always |
| Radio Host Software Version | The version of radio firmware is displayed | Always |
| DSP Software Version | The version of firmware being used by the DSP | Always |
| EMC Secure Version | Version of the encryption hardware | When the radio is secure equipped |
| Encryption Type 1 | Type of encryption being used | When the radio is secure equipped |
| Encryption Type 2 | Type of encryption being used | When the radio is secure equipped |
| Model Number | The radio�s model number as programmed in the codeplug | Always |
| Serial Number | The radio�s serial number as programmed in the codeplug | Always |
| ROM Size | The memory capacity of the flash part | Always |
| FLASHcode | The FLASHcodes as programmed as part of the radio�s codeplug | Always |
NOTE: All displays are temporary and will expire without any user intervention. If information is longer than the physical length of the control-head display, the information will wrap around to the next display. After the last display, "RF TEST" will be displayed.
Press Side Button 1 to stop the displays and put the radio into Control Top and Keypad test mode. The test mode menu "CH TEST" will be displayed.
Note: Each press of the Side Button 1 will toggle between CH TEST and RF TEST.
Astro Saber Batteries
Available chemistries are NiCd or NiMH. Nominal Voltage: 7.5 volts. Range: 6-9 volts.
| Medium Capacity NiCd | NTN4593 |
| Ultra-High Capacity NiCd | NTN4595 |
| Medium Capacity NiMH | NTN7014 |
| High Capacity NiMH | NTN7251 |
| Hi Cap Factory Mutual | NTN4538*/** |
| Ultra Hi Cap Factory Mutual | NTN4596*/** |
*FM Intrinsically Safe Class 1,2,3 Divison 1, Groups D,F,G
**FM Nonincendive Class 1, Division 2, Group A,B,C,D
