H45 (Type I SmartNet Trunking) in an ASTRO Portable?

[MTS2000des]

So would not a type IIi personality work? We have one old POS type IIi system here in Atlanta (Fulton County). The county stuff is still on the old smartnet I side of the system, the cities of roswell and alpharetta are the Smartnet II side.

so when programming an XTS on the system, to use the old side, the personalities are set to IIi. You still enter the fleet, subfleets, failsoft and size code like you do on old smartnet I STX's...dont see why this should not work for you.

I guess you could use this to get an Astro to work on a Privacy Plus system...the "Smartnet" features just would not work (emergency, dynamic regroup, etc)....ideas?

[Josh]

So would not a type IIi personality work? We have one old POS type IIi system here in Atlanta (Fulton County). The county stuff is still on the old smartnet I side of the system, the cities of roswell and alpharetta are the Smartnet II side.

so when programming an XTS on the system, to use the old side, the personalities are set to IIi. You still enter the fleet, subfleets, failsoft and size code like you do on old smartnet I STX's...dont see why this should not work for you.

I guess you could use this to get an Astro to work on a Privacy Plus system...the "Smartnet" features just would not work (emergency, dynamic regroup, etc)....ideas?

I've done a typeI system on my IIi XTS3000...it worked just fine, but when I've got the option of a typeII system or a typeI system all with the same traffic simulcast (yes, the Wayne Co. Sheriff's department) I'm going to stick with the typeII- because A) The typeI system was having problems [and still is with dead-air simulcasting to the typeI system from the typeII- where the II system has audio] and B) The typeI system has a "burp" at the beginning of a repeater keyup which is as annoying as hell and the MTX8000 quieted on.

-Josh

[MTS2000des]

Josh,

Try turning off the "Fast Access" on your type IIi/I personality, this should get rid of that annoying "burp" you hear when the radio umutes. We had this problem on MTS2000's programmed on that system, turning off Fast Access on those personalities did away with the noise. Everything else seemed to operate normally, priority monitor, emergency, etc.

[chiefhal3]

Is there any trick to making and XTS3000 work on a Type I Privacy Plus system? I have all info I think I need, system ID, connect tone, radio id, subfleets, fleet size, control channel freqs. Type I doesn't seem to be an allowable option in the radio but I understand IIi will work just the same, is that correct?

[wavetar]

Is there any trick to making and XTS3000 work on a Type I Privacy Plus system? I have all info I think I need, system ID, connect tone, radio id, subfleets, fleet size, control channel freqs. Type I doesn't seem to be an allowable option in the radio but I understand IIi will work just the same, is that correct?

As far as monitoring a system, yes, setting it for Type IIi should work just fine.

Todd

[chiefhal3]

Well, I am having trouble making it talk. I can monitor just fine even getting everything on the right subfleets but I can't seem to get it to affiliate. The radio Id I am using is a good one, its the one out of the MTX8000 I am taking out of service and replacing with the XTS3000.

[wavetar]

Well, I am having trouble making it talk. I can monitor just fine even getting everything on the right subfleets but I can't seem to get it to affiliate. The radio Id I am using is a good one, its the one out of the MTX8000 I am taking out of service and replacing with the XTS3000.

That is why I said "for monitoring purposes" it would be ok. If you have a true Type I only system, then a Type IIi radio will not work. The system needs to have at least one Type II size code (shown as an "X" in the fleet map) in the controller. This is known as a Hybrid system, and is the only way to get a hybrid Type IIi radio to work properly. Otherwise, you'll hear but not transmit, as you found out.

The other possibility is that it is a Hybrid system, but you are using the wrong ID. Depending on where the "X" sized code resides in the fleet map, the block of ID's allocated for Type IIi operation is different. For instance, if "X" were the first size code, you could use any ID from 0-8191 (0 - 1FFF in hex). If were to occupy the last block, the ID's would have to be between 49152-65534 (C000 - FFFE in hex). Otherwise, again, you'll hear but not transmit. So, first find out if you have a Hybrid system. If not, you're out of luck. If it is, then you need to find out the valid ID range for the system. Most systems are either the first block (0 - 1FFF) or the last (C000 - FFFE).

Todd

[chiefhal3]

Hey, I talked with the system administrator today. He confirmed that the system is truely a Type I system only. He has no Type II blocks of id's. Just curious if anyone knows will all Type I systems allow you to select a block of ID's to be Type II by putting the "X" in the section of the controller as mentioned above? Or, is this only on some systems. He doesn't seem to think his system will do Type IIi now that we have talked a little more. I just can't believe that there is no way to make an XTS3000 work on a Type I system, go figure, M wants to sell more radio's and systems I guess.

[wavetar]

The only way to add an 'X' size code to your system is to have a new 'codeplug' prom blown for it. Cost is somewhere around $700 US for it, I believe. That's if you go with Motorola. There are a few people here on the board who have said to have the capability to make new proms. I have no idea what they might charge. Until then, your XTS3000 isn't going to transmit on your system. The other option is Motorola may have an 'SP' flash that would allow Type I operation...good luck finding the right person to find that out!

Todd