Rebanding hype ha ha ha

[jpm]

My paperweight bc785d is currently working and tracking with the rebanded frequencies. Just like my friend that works at NWCDispatch there said no problem for your scanners to work when we reband. So for the ones claiming this would be a paperweight WRONG. Thanks for trying Uniden get me a job there i could waste time wisely too.

 

[ecps92]

And who are you listening to that has rebanded?

My paperweight bc785d is currently working and tracking with the rebanded frequencies. Just like my friend that works at NWCDispatch there said no problem for your scanners to work when we reband. So for the ones claiming this would be a paperweight WRONG. Thanks for trying Uniden get me a job there i could waste time wisely too.

 

[Highpockets]

My paperweight bc785d is currently working and tracking with the rebanded frequencies. Just like my friend that works at NWCDispatch there said no problem for your scanners to work when we reband. So for the ones claiming this would be a paperweight WRONG. Thanks for trying Uniden get me a job there i could waste time wisely too.

Read this thread, it might explain why your scanner works after rebanding in your area, read the text under sentence in red.

http://www.radioreference.com/forum...5682-custom-band-plan-s-rebanded-systems.html

 

[KC1UA]

It's my understanding that while some trunking systems have moved down 15 MHz and "rebanded", some of them are not using the new channel spacing/assignments yet. With that in mind I would expect the 785D to still work. I believe Nashua NH's system may be one such system, and I believe I read this in the NH Yahoogroup. Why they would not be using the new channel assignments I don't know as I haven't been following rebanding too closely as of late. But, this may be the case in your situation as well.

 

[UPMan]

JPM:

If you are talking about this system:
Scanner Frequencies: Northwest Central Dispatch - NWCD P25 (Lake/Cook) Trunking System, Arlington Heights, Illinois

Then you are probably not hearing any comms that fall on either 853.07500 or 853.75000. On average you should be missing about 25% of system traffic.

 

[jpm]

The 785, 796 and 996 are picking up all transmissions but the 396 misses some transmissions. I don't know if NWCD (Northwest Central Dispatch) did the reband thing as far as following those related tables but all scanners are pickin up NWCD and the 396 is the only one missing transmissions. They might of just reprogrammed the radios due to a move with a new trunked system and my understanding is possibly the one current scanners can't track in trunk mode. TDKA?

 

[jpm]

Ok I'm on a long 5 day w/e and just returned the 396 back to normal activity, resetting the rebanded frequencies and getting rid of this custom band stuff and back in service with all tx. Could this be the reason why I was missing tx due to the fact NWCD is not using the custom band/table jive..

 

[dougr1252]

Since Motorola systems usually assign channels in frequency order as needed, if the system's not very busy then those last 2 splinter channels might hardly be used. Any Mot trunking scanner could probably monitor it with good results until the traffic load increases.

 

[ButchGone]

Re:

From my experience listening to rebanded systems, anything 854 MHz and UP just changed frequencies and NOT the new channelization scheme used to track MOTO systems. That's why nothing has to be done to hear the rebanded system other than change frequencies. But systems that were in the 866-868MHz range and rebanded to 851-853.9875 indeed DO have to be set with a custom table because the channelization scheme changed. And that's what the Uniden rebanding patch addresses, and I might say adresses very well. A 780/785 will NOT work on rebanded trunked systems below 854MHz but will work above that frequency. Not all 800Mhz systems and channelization schemes are the same.
That's just what I'm finding.
BG..

 

[SCPD]

From my experience listening to rebanded systems, anything 854 MHz and UP just changed frequencies and NOT the new channelization scheme used to track MOTO systems. That's why nothing has to be done to hear the rebanded system other than change frequencies. But systems that were in the 866-868MHz range and rebanded to 851-853.9875 indeed DO have to be set with a custom table because the channelization scheme changed. And that's what the Uniden rebanding patch addresses, and I might say adresses very well. A 780/785 will NOT work on rebanded trunked systems below 854MHz but will work above that frequency. Not all 800Mhz systems and channelization schemes are the same.
That's just what I'm finding.
BG..

band Plans ARE the same on 800MHZ they are done by the FCC not nt specific brand of radio. Get your facts/babbling straight lol

 

[ButchGone]

No...

The systems used in Tennessee and north Georgia that have been rebanded do NOT trunk the same way. Those below 854Mhz have to be programmed with a custom band plan. These are the systems formerly in the 866-868 range. They will not otherwise work on Unidens, as I have had to reflash the radios with the upgrades and reprogram accordingly with custom plan. They don't work without the custom plan. For those above 854, like the Chattanooga main system, they don't need a custom plan. But Chattanooga's two remote intellipeater sites, Ringgold and Brock Road, do need custom plans and they are below 854.
BG..

 

[N_Jay]

Why all the guessing. EVERYTHING, yes EVERYTHING about rebanding is well documented.

800 MHz Band Reconfiguration
800 MHz Reconfiguration Transition Administrator
800MHz Rebanding Resource
800MHz Rebanding Resource

 

[zz0468]

Since Motorola systems usually assign channels in frequency order as needed, if the system's not very busy then those last 2 splinter channels might hardly be used. Any Mot trunking scanner could probably monitor it with good results until the traffic load increases.

That's an interesting misconception. I haven't heard that one before.

 

[qlajlu]

From my experience listening to rebanded systems, anything 854 MHz and UP just changed frequencies and NOT the new channelization scheme used to track MOTO systems. That's why nothing has to be done to hear the rebanded system other than change frequencies. But systems that were in the 866-868MHz range and rebanded to 851-853.9875 indeed DO have to be set with a custom table because the channelization scheme changed. And that's what the Uniden rebanding patch addresses, and I might say adresses very well. A 780/785 will NOT work on rebanded trunked systems below 854MHz but will work above that frequency. Not all 800Mhz systems and channelization schemes are the same.
That's just what I'm finding.
BG..

WRONG! All Motorola 800 MHz trunking systems are set up the same.

Why all the guessing. EVERYTHING, yes EVERYTHING about rebanding is well documented.

800 MHz Band Reconfiguration
800 MHz Reconfiguration Transition Administrator
800MHz Rebanding Resource
800MHz Rebanding Resource

RIGHT! Absolutely right, N_Jay.

Utah Communications Agency Network (UCAN) finished rebanding the last of their 45+ trunked sites (System ID 7202) in Utah on Dec. 10, 2008. During the months long process of rebanding all the sites in the state, we found that our older trunk-tracking scanners would continue to track Motorola 800 MHz trunked systems with some limited success without any upgrades. LCN channels 440 through 559 were configured to insert between existing frequencies creating 12.5 kHz steps and it has been these frequencies that have created the issues. Scanners that cannot have their firmware "flashed" so that updated trunking tables can be entered will still continue to track, but will not "hear" all the frequencies. The frequencies that cannot be received by legacy trunk-tracking scanners are those frequencies that start with 851, 852, 853, and have a "0" in the fourth decimal place.

Of course, all of the frequencies can be entered as conventional frequencies and scanned as conventional frequencies, but the listener will not have the benefit of knowing who is talking and any "following" will be strictly coincidental.

Those scanners that could be upgraded so that edited trunking tables (custom band plans) could be entered had no trouble in the rebanding process once the "new" tables were entered. The custom band plans that are now general knowledge will allow scanners to trunk-track sites and/or systems that have not been rebanded yet as well as those that have been rebanded.

The Control Channel uses LCNs to assign a frequency. Trunk-tracking scanners capture the LCN in the Control Channel's data stream and then use the trunking tables in a mathematical formula to determine what the frequency will be based on the LCN assigned by the Control Channel. It is the LCN (Logical Channel Number) that tells the radios on the trunked system which frequency they will use to transmit and receive voice traffic.

Some agencies are fortunate in having their trunked systems already using frequencies that are below the threshold where the FCC required abandonment and reassignment. These agencies did not have to undergo rebanding because their systems already conformed to the mandate. However, the custom band plan(s) (trunking tables) could still be used on their system!

 

[UPMan]

However, the custom band plan(s) (trunking tables) could still be used on their system!

To clarify a bit, there are currently three formulas (channelization schemes) in use on Motorola 3600 systems:

* 800 Standard (pre-rebanding)
* 800 Standard (post-rebanding) (use 800 Custom in Uniden Scanners with a custom band plan)
* 800 Splinter (pre-rebanding)

Each type typically needs to be set up differently in your scanner. It happens that if your 800 Standard (pre-rebanding) system does not use frequencies in the 866-869 MHz range, then you can use either the 800 Standard (pre-rebanding) or 800 Standard (post-rebanding) setup when you program it into your scanner.

There is at least one other formula expected to become used at some point:
* 800 Splinter (post-rebanding)

I have not yet seen a channelization plan for a post-rebanded splinter system so don't know what band plan table it will use...

We have also allowed for the use of an "inverted channel plan" that has not yet been implemented on any system, but that Moto has been trying to sell into some of the rebanded systems. It uses the exact same formula as a normal system, except that the offset is subtracted from the base frequency rather than added to the base frequency.

So it is not quite accurate to say that all 800 MHz systems are set up the same...

 

[torontokris]

Im guessing your monitoring this system
Scanner Frequencies: Northwest Central Dispatch - NWCD Analog (Cook) Trunking System, Hoffman Estates, Illinois

Based on this reply you knew that the system would be fine way back in 2005
http://www.radioreference.com/forum.../16511-northwest-central-dispatch-analog.html

 

[torontokris]

I dont think Uniden ever said the scanners would be "bricks" or un-usable or paperweights at all.

also EDACS and LTR still work after re-banding as well (long as the freq are reprogrammed). So its never a paperweight even if your system moved to a different rebanding frequency.

Just be happy its working and hope they dont go to 9600 P25 =)

 

[DonS]

All Motorola 800 MHz trunking systems are set up the same.

Not true.

On some, "channels" (Motorola's channel numbers, as sent on the CC) 440-559 mean one thing, while on others, "channels" 440-559 mean something else. What they mean (i.e. what voice frequency corresponds to what channel number) depends on the "bandplan" or "channel map" in use on that particular system.

EDIT: and then, of course, there are the splinter systems with their own, different "channel map".

 

[RoninJoliet]

Today i visited the NWCD-Arlington Hts area with my GRE500 and PRO96...On the GRE 500 NWCD 3600 Motorola system i entered the necessary multi-table info from Win500, the system worked perfect even on the 853.75 freqy...In my PRO96 i put the NWCD system in two different "banks", one with the Win96 multi-table 800-3600baud and one bank with just the re-programmed freqys, the bank with "multi-table rebanding worked perfect even on 853.75, but the bank with the non-rebanding worked fine "except on the 853.75, while i was hearing things fine on the GRE500 rebanded the non rebanded PRO96 bank on the 853 freqy showed a freqy of 864.7375 and i heard nothing ...

 

[slicerwizard]

To clarify a bit, there are currently three formulas (channelization schemes) in use on Motorola 3600 systems:

* 800 Standard (pre-rebanding)
* 800 Standard (post-rebanding) (use 800 Custom in Uniden Scanners with a custom band plan)
* 800 Splinter (pre-rebanding)

What about this system? Scanner Frequencies: Red Deer Public Safety & Public Works Trunking System, Red Deer, Alberta

It is none of the above. The DMA scanners didn't handle this system until firmware support for custom bandplans was added, yet some older Unidens should handle it as they have four 800 MHz bandplan choices.

Why were these extra bandplans left out of the DMA scanners?