800 MHz Rebanding Plan

[ECHO3]

For members of this forum who are more familiar with the above-referenced subject, when are the proposed changes to be implemented and what impact, if any, will this have on all of us who have TRSs programmed in our scanners?

http://wireless.fcc.gov/publicsafety/800MHz/bandreconfiguration/index2.html


http://mrtmag.com/news/800_mhz_register_112304/

 

[INDY72]

Its supposedly supposed to begin in the next couple of years,.. and the impact... Any TRS using above 860 MHz has to be redone lower,.. so that means not only the system, and all its radios reprogrammed, but also every tt scanner thats set up for the system.... In other words itll be a PITA all the way around!

 

[FPO703]

They should just boot NexTel completely out of 800 MHz and leave things how they are. Once they get NexTel out of the 800 band, things will be just fine.

 

[ShawnCowden]

U mean our tt scanners will be useless ??

 

[FPO703]

no. They will just need to be re-programmed.

 

[INDY72]

Not useless as was siad,.. just have to completely reprogrammmed to match whatever the newest setup the current TRS's go to...

Just to make sure you know whats going to happen:

All Public Safety systems using freqs ABOVE 860 MHz must move DOWN below 860 MHz. In other words, if your local TRS is say loaded with 866 MHz freqs,... they have to go down below 860. Kinda strange considering that the 866 band was originally set aside for just PS...... But Nextel has the CASH! Anyway... Nextel is abandoning everything below 860, thus opening that all up again.

This along with the now opening 700 band, should eliminate the clash of Nextel vs PS. *Note*- There will be NO analog on 700, its supposed to be all digital per the FCC.

Most likely when rebanding takes effect, the TRS's that have to change, will go digital then just to make things easier.

 

[ShawnCowden]

hope win96 will let us program 700 mhz trunk digital systems in the future!!!

 

[ECHO3]

Thanks to all of you for your input. Basically, you are validating what I thought because most of the trunked systems I have programmed are above 860.000. Now that the plan has been published in the Federal Register, I suspect the plan is final. EDACS users are probably biting bullets. I hope the RR database will remain a good source for all changes. Big PITA for LE, etc.

 

[poltergeisty]

Oh man I love when a plan comes together .LOL.:wink:

 

[ECHO3]

Thanks for your words of wisdom.

 

[poltergeisty]

Thanks for your words of wisdom.

Yes the same wisdom as the fcc's. :lol:

 

[poltergeisty]

So is there a possibility that my local ps will go to 700 Mhz.? Or would that be a major radio and equipment change? and thus not being done. And if they did how can the current radios cope for 700 Mhz. can the 296d for example be loaded with a new firmware to allow 700 Mhz. or not I know a firmware update was able to tune the radio better for 800 Mhz. so I think allowing 700 Mhz might be concievable. This scares me, if they go 700 and my radio can't cope I will have a $500.00 paper weight. In that case I think I will just forget about this digital crap try to sell the radio on ebay and take the money and build a gamer pc. Later on when prices come down for a new radio I might buy one. By that time it might be all encrypted, go figure.
:shock:


Lastly how can I find out what my public safety communications providers are doing in regards to the change in the future. And most importantly when? I live in Colorado.

 

[AZScanner]

All Public Safety systems using freqs ABOVE 860 MHz must move DOWN below 860 MHz. In other words, if your local TRS is say loaded with 866 MHz freqs,... they have to go down below 860. Kinda strange considering that the 866 band was originally set aside for just PS......

Aww, this is just ridiculous! :evil:

What a pain this will be. We have 2 monster SmartNet systems that reside almost exclusively in 866-868Mhz: Mesa/Phoenix and Maricopa County. There are 59 control channels alone that must be changed, according to the RRDB. That's not counting the 200+ other frequencies in these systems that must be reassigned. The cost to AZ taxpayers will be in the millions to implement these changes. And the FCC doesn't care. Once again, the FCC proves themselves to be nothing more than a wholly owned subsidiary of Nexthell.

Not to mention the news stations that my paging group supports will be totally hosed when this happens and I will be running around like a chicken with no head reprogramming radios - both mine and theirs! Grrrrrrr..... unitCharlie, you feelin' me on this? This is gonna SUCK!

-AZ

 

[ECHO3]

Excellent questions. poltergeisty! I honestly wish that I had answers. If a PS entity moves to the 700 MHz band they must be digital. I'm certain that others share your concerns. I, personally, would be out about $1500.00 or more since I have scanners installed in my SUV in an equipment console. I don't mind doing some reprogramming, but replacing the equipment would be impossible for me.

Although we as hobbyists can anticipate some frustration, I suspect that many PS entities will experience shock. Whether the entity has 5, 200, 1000 or thousands of vehicles equipped with two-way radios operating above 860 MHz, they will be confronted with service interruptions, costs either for retuning or replacing equipment and excessive frustration. Small volunteer fire companies, e.g. barely have the financial resources to function now. Why doesn't NEXTEL just get out of picture!!!!!!

 

[FPO703]

Aww, this is just ridiculous! :evil:

What a pain this will be. We have 2 monster SmartNet systems that reside almost exclusively in 866-868Mhz: Mesa/Phoenix and Maricopa County. There are 59 control channels alone that must be changed, according to the RRDB. That's not counting the 200+ other frequencies in these systems that must be reassigned. The cost to AZ taxpayers will be in the millions to implement these changes. And the FCC doesn't care. Once again, the FCC proves themselves to be nothing more than a wholly owned subsidiary of Nexthell.

Not to mention the news stations that my paging group supports will be totally hosed when this happens and I will be running around like a chicken with no head reprogramming radios - both mine and theirs! Grrrrrrr..... unitCharlie, you feelin' me on this? This is gonna SUCK!

-AZ

The tax payers won't have to pay anything for the reprogramming. NEXTEL will be paying for it. That's what this whole topic is talking about.

 

[mikey60]

What a pain this will be. We have 2 monster SmartNet systems that reside almost exclusively in 866-868Mhz: Mesa/Phoenix and Maricopa County. There are 59 control channels alone that must be changed, according to the RRDB. That's not counting the 200+ other frequencies in these systems that must be reassigned.

Compare that to the state of Michigan. 183 towers (IIRC), all operating in the 866-868.9875 range. Add to that the City of Detroit with a 10 site simulcast that's linked to the state system, and somewhere in the range of 20000-30000 radios on the system... Now THAT will be a pain...

Then add Colorado, who is still in the implementation stage, although well on their way. Minnesota is in the same boat as well.. It's gonna be a pain for all involved, and 3 years may not be enough time to do all of it...

Mike

 

[FPO703]

Same thing with Ohio.

 

[INDY72]

Put it like this-
Over 1 Million radios nationwide to be reprogrammed, at least 20 entire TRS's to be re-liscensed for new freqs and resetup, All paid for by Nextel, then the FCC PAYS Nextel back.... as well as gives them a huge new chunk of spectrum..... Yeah its WHACKED, but YES its happening. It will take five years at least to reconfigure, reliscense, and reprogram...

But it should totally fix the Nextel crappola situation....

On the scanner side-
1 day's worth of reprogramming and griping....

Not too bad a situation......

 

[poltergeisty]

Well I was looking at the fcc's web site and I see that there are and have been 700 Mhz. planing meetings in Colorado. So common sense tells me that a definite 700 Mhz. solution is just beyond the horizon. I'm guessing no latter then dec.2006 when the fcc finally turns all our tv's into s**t in favor of being able to see ones pours on his or her face on a movie or show.LOL. :lol:

 

[AZScanner]

On the scanner side-
1 day's worth of reprogramming and griping....

"One day" he says...

You've never set up scanners for a news organization then. It's far from a one day process. Plus you're not considering all the research involved before you even begin reprogramming. It's taken several months to document the PHX/MESA systems, and the records on this site are STILL incomplete. And that is WITH cooperation and information from Phoenix PD's PIO. And that is only the PD side of things, most of the FD and municipal agencies are not on the new system yet!

Let's just hope people drag their feet and the systems have a couple years to "burn-in" before people have to go back in and screw them all up.

As for Nextel paying the bill, I'll believe that when I see it. They've already proven they can push the FCC around, what makes you think they are going to pay for every little thing each city and county does to their radio systems? They'll pay maybe 50% of the actual cost and leave the rest to the taxpayers - you watch and see.

Oh and did I mention this is gonna take 5 YEARS? How many first responders are we gonna lose due to an interference related radio failure in that time? Even if it's only one, that's one too many in my opinion. But hey, who cares, look it's Nextel with a big barrel full of money! Let's do what they want!

Idiots. (the FCC)

-AZ