Programming STARS into PSR-500

[tglendye]

I currently have STARS into 2 scanlists due to the # of CC's. I am trying to create a rhyme or reason as to what scanlist I put the system frequencies into.

I am thinking geographically or maybe all of the primary CC's into 1 scanlist. Right now most of the towers are in Central or Eastern Va, so I'm thinking if I put the primary into a single list, that might be the better option.

Does anyone have any suggestions?

Thanks,
Todd

 

[n4jri]

Do you mean that you're putting STARS into two different TSYS objects?

Couple of things....

SCAN LISTS - Remember that with the 500 (unlike the PRO-96) a trunked system is not tied to a particular scanlist.You'll actually be scanning TGRP objects, and those can be assigned to any scanlist you like. They all know which TSYS object to connect to, and that TSYS object has no scanlist.

For example, much of northern West Virginia is on a STARS-like system of its own. (WVIRP) With one TSYS for that system and all the most likely CC's, I might put WV state TG's in SL#4, while putting Berkeley County TG's in SL#5 and Jefferson County TG's in SL#6. There's also a bunch of statewide EMS stuff that I might put into SL#10. So I have TG's for the same system all operating from the same TSYS object, but spread among at least 4 scanlists. The 500 allows this and does it well.

MULTIPLE TSYS OBJECTS - If you create additional TSYS objects to handle extra CC's, you also have to create a set of TGRP objects to monitor for each TSYS you have. STARS is only going to add more sites, and more talkgroups. Soon it'll outgrow your radio. I suggest putting all STARS stuff with a single TSYS object, and to only enter the CC freqs that you most frequently use. That leaves the rest of the CC spaces open for CC's that you might encounter on a trip somewhere. I keep all the STARS tower and their CC's in my GPS and can check my direction and distance from the nearest 4 towers simultaneously. If getting outside my stomping grounds, I can check the CC's for those sites (they appear on the GPS as well) and enter the ones I need.

In a recent trip to North Carolina, I used this setup with its VIPER system. I'd left blank spaces for CC's in my VIPER TSYS. While travelling down there, I selected CC's from sites displayed on my GPS, or simply entered CC's that I found in search mode and analyzed in tune mode.

MULTIPLE V-SCANNERS
I don't know about you, but I use multiple V-scanner files as I move around. I have a normal one for Richmond, plus extra ones for the areas around Petersburg, Lynchburg, Roanoke, Fredercksburg, DC, Charlottesville, Winchester, Staunton, etc. In each of those, I program the most likely STARS freqs and TG's as well as all the local stuff. This lets me take a pretty long trip without the need for a lot of keystrokes. This is how I solved the dilemma of STARS and all its different CC's.

It's also easy to find STARS CC's via search mode anywhere that's in range of the system. That's how we found most of the CCs that are in the database.

The multiple V-scanners is the way to go. With 1852 objects in 20 scanlists, you can cover a lot of territory with each one.

Just my 2 cents...

73/Allen (N4JRI)

 

[fmon]

I agree with Allen regarding STARS expansion, you will likely need various V-folders in the future.

However, I made a file more then a year ago with two TSYS and entered all TGRP's in both TSYS and Scanlist 1 as duty. TSYS 1 is alpha tagged STARS 101-112 and 2 is alpha tagged STARS 114-126. Both have room for several additional CC's.

During no activity, list 1 quickly flip flops between the two alpha tags on bottom line of display.

We will be taking a trip to KS in about 7 weeks using I-64 through St Louis. Usually on return we enter BRPW at Buena Vista and run it to at least Peaks Of Otter (43).then 460 to Ivor and county roads to Smithfield. This setup was fairly active from home into Rockbridge Co going out and inbound most of BRPW and again somewhere approaching Farmville to home in Suffolk.

Going to be refining that file shortly and likely rearrange scanlist by Law/F-EMS/other for STARS. Also, need to add more TGRP's and control/alt frequencies.

BTW, I use a similar two TSYS setup for KSICS statewide P25 system. Though we only go to Great Bend. Fortunately IL, IN and WV we can use a single TSYS.

 

[tglendye]

Thanks guys for your help. I have created different V-folders for the state and other areas, however I had left STARS w/ the same towers as I have when I am home- even in the v-folders. I think that might be a good option. I do like scanning all of the TG's most of the time, however because it seems like you never know what TG you might hear, if a unit affiliates w/ a different tower.

Another thing I had not thought of was to select multiple scanlists for TG's. When I want to listen to STARS, I was turning the scanlist on. I have now programmed the VSP Culpeper and DGIF TG'S associated w/ my home area scanlist. I figure that should help once Culpeper STARS comes on line.

That's a great idea to to name the list with the site #'s. As of now, I have no idea what sites I actually have in the TYS's.

Thanks Allen and Frank for your ideas.

Todd

 

[n4jri]

I would definitely use the ShowCCinfo option with STARS. I've really enjoyed it using it to watch the radio migrate on STARS, VIPER, etc. and even on the Richmond supersystem.

73/Allen (N4JRI)

 

[tglendye]

I wonder if the PSR500 would accept alpha tags and Don could change win500 for that. I would rather have the CC shown as an alpha tag than a freq. that I would have to reference the database or other notes.

 

[fmon]

I too would prefer alpha tags, however, the scanner doesn't have a place for listing TSYS frequency alpha tags. They are listed by channel number only.