Perhaps this thread should be relabeled as "GRE for Beginners" or even better, "GRE for Dummies." However, if explaining the difficulties I have encountered and how I have been able to solve them will help just one person make the transition to GRE PSR 500/600 easier, then lowering the natural defense mechanism I use to conceal my ignorance will be worth it. Some of you are already familiar with the Object scanning of the GRE because other makes of scanners have employed it in some way ("CC Only" scanning comes close), but this is new territory for me and probably others who are only used to the older, traditional Banks/Channels used by Uniden.
You must also remember that everything I do in configuring my GRE is done using Starrsoft's WIN500 software. I must also give credit to
gadgetmikey's unselfish tutelage because he set me off on the right path. Unknowingly,
gadgetmikey and I both ordered GRE PSR 600s from the same dealer on the same day and took delivery of them both on the same day even though half a state separates us. Weird.
"Need more time, I guess. Seems like I'm turning this thread into my own personal educational and complaint tool, too. Sorry."
Don't worry about it. It is a learning experience for most/all of us here as well. Any questions that you (or I) would have, someone else is wondering as well.
Hey, qlajlu dont worry about it. Now when ever I can afford my GRE I will have a great resource available

always remember that's what this group is sbout.... helping each other, working together, and advancing our hobby !
Okay, using the above quotes as encouragement I am going to explain something that presented itself over the weekend that had me on a slow burn wishing the whole situation would just go away and how I solved it.
When I imported a sizable chunk of the UCAN system and was able to start scanning (see other posts above), I noticed that my scanner would spend an inordinate amount of time on TGs from Box Elder, Weber, and Davis Counties in that order. I was getting very little traffic from Tooele, Summit/Wasatch, and Salt Lake Counties, if any. The sites I imported were 001 (Weber County), 002 (Davis County), 003 (Salt Lake County), 004 (Utah County), 007 (Mt. Ogden), and 011 (Nelson Peak) because those sites have given me the best coverage on my BC780XLTs. The software imports the CCs from the RR Db in order from the lowest numbered site to the highest if you select several sites to import at the same time. That’s logical.
Not understanding how the scanner decides what it will scan, I theorized that maybe if I rearranged the order of the CCs in the TSYS frequency list, it would change the emphasis on what the scanner spent time scanning so I manually exchanged the positions of the CC frequencies of sites 001 (Weber) and 003 (Salt Lake) in the TSYS frequency list. At the same time I went through the list of all the TGs and distributed them to different scan lists according to geographical area so I could lockout different areas as it suited me and uploaded the changes to the scanner. The result of making these changes was I ended up with a deaf-mute scanner. Well, not so much. All I could hear at that point was Box Elder! Hmm, what the…?

[The slow burn starts.]
At this point I went through all kinds of trials and tribulations, contortions, pushing this, pulling that, trying this, trying that, and all for naught. All I had was Box Elder County talking to me. HMM, WHAT THE...? :evil: [The burn deepens.]
For some unknown reason which I still do not understand, I decided to check the trunking table. I had entered the custom table (below) sent to me by
gadgetmikey with instructions on how to enter it when I first set up the scanner. I could not find it. Hmm, what the…?

(Remember that I have, up to this point, imported all the frequencies and TGs twice before, so I easily could have overwritten the table inadvertently.) So I re-entered it, uploaded it to the scanner, and, EUREKA!

...we were off like a turpentined cat! AND…I'm getting equal coverage on all geographical areas without it seeming to spend a lot of time on one area over another, depending, of course, on the traffic volumes.
Code:
[U]Lo Chan[/U] [u]Hi Chan[/u] [u]Offset[/u] [u]Base Freq[/u] [u]Step[/u]
0 439 0 851.012500 25.000
440 559 440 851.025000 25.000
560 719 560 865.012500 25.000
720 759 720 866.000000 25.000
815 831 815 867.000000 25.000
958 958 958 868.975000 25.000
961 1022 961 867.425000 25.000
There is another feature on the GRE that I have learned to love. I have added an audible notification tone and COLORED LED light to the Regional TGs. If there is any traffic on one of the Regional TGs, I get a hi-lo tone and the LED on the face of the scanner comes on. I have chosen a different color for each Regional TG. Very cool feature!
By the way, have any of you with GREs been picking up a large amount of background noise when listening to TGs from Weber, Davis Counties, and some Salt Lake? I don't get that on the 780s but it is quite noticeable on the 600. I'm wondering if it is a particular site having problems, but why don't I hear it on the Unidens?