qlajlu
Silent Key
I just copied the UCAN techs on TG 4096 getting ready to "roll the site." They are talking about it happening at 10 o'clock pm tonight.
Last edited:
Yeah, I was kinda wondering that, too. In fact, I really tossed it around in my mind whether to start a new thread on it or not after your thread, but with all the hoopla from the other times they rebanded sites I figured a new thread would be best. I really didn't do it to take the wind out of your sails, shootinnews, considering our history.Hmm, so I wonder if they did something earlier that made me assume they were doing some reband stuff this morning?
Sounds like great midnight entertainment, Brent. Maybe they should reband more often. :lol:Half way through this they ran into a wall. Nextel was causing interference with one of the transmitters. You should have heard the techs! "I thought this whole exercise was for them. Why haven't they vacated this band?!" He was NOT happy. UCAN supervisor got Nextel supervisor out of bed. Was good listening.
It appears the Custom Trunking Table in Win97 works only for UHF trunking, but you might as well give it a try and put in the 800 MHz custom tables discussed elsewhere in this forum. You never know...
There has been a lot of 'inadequate' information put out about the Pro-164. It started with the posts that said the Pro-164 and GRE PSR-300 would be totally compatable with the 1.04 firmware update. Someone in Tooele Co said their PSR-300 worked fine on rebanding after programming it with ARC-300 software. So I programmed a Pro-164 with ARC-300 for a friend and it "appeared" to work on SL Simo, but turns out it does not. So I am as much to blame as anyone for perpetrating the wrong information and I owe an apology to everyone who took my advice. I still don't know for fact the Tooele PSR-300 works properly.
There is good news: Radio Shack will have a rebanding update for this scanner - at some point - no date has been announced yet. So... yes the 164 is reband capable, but the firmware has to be flashed.
I'm not going to wade in on the scanner itself since I know nothing about it, but the band plans you have seen especially in this post are at most seven lines. The most critical lines in the first table are the first three and in the second table the first two lines.dpalmer2508 said:I don't run any form of Trunker or computerized decoding, but the custom band plans that I have seen in other threads have 7 or 8 rows of data for the different LCN ranges. I am not sure that these three rows would be enough to accomplish what was needed.
The ARC300 has a rebanding Utility that allows you to put in a Start Frequency and Stop Frequency, and then an offset, and then asked you if you want it applied to the current bank or all banks. The defaults is shows are 866.00 for Start and 869.00 for Stop and a -15 for the offset. So, I just assume that when ever the old band plan points to a LCN that points to a freq in that range, it will drop it 15 mhz on the fly? Sounds like a fix, but not necessarily an efficient one. But does it work if the correct start, stop, and offset numbers are put in for the UCAN system?
WIN97 has an option for a MOT Custom Trunking Table, but the defaults are for UHF. It has inputs for BASE Freq, Offset, and Step, with room for three rows of data for each. I don't run any form of Trunker or computerized decoding, but the custom band plans that I have seen in other threads have 7 or 8 rows of data for the different LCN ranges. I am not sure that these three rows would be enough to accomplish what was needed.
We still need someone to run UniTrunker on Site 001 Weber County to verify frequencies!
I'm really amazed. When every other site was rebanded we had three or ten people posting UniTrunker readouts on the frequencies within 24 hours and there has not been even one with this site yet.
C'mon guys. We need to get the Db updated!