RadioShack Pro 106 handheld scanner

[Jeremy173]

Recently purchased this scanner and it works like a charm, just wondering if anyone out here knows if there are sub-banks for the talk id groups or if it all has to be in one list. I can't seem to find out anywhere I look.

Thanks!

 

[RickS31]

This is a great question, at least for me as well. I too am a newbie in programming this great scanner and would appreciate our more knowledgeable 106 owner answers. I have programmed a full TSYS and Talk Group into mine manually.

My belief is that a scan list (1-20) must have the TSYS info programmed into it first then the respective Talk Groups after. My thought is that a given scan list needs the Tsys info in it, then the desired TGRPs that you want to monitor. Some large P25 systems will have the same TSYS info but different TGRPs depending on what you want that scan list to monitor. Like one scan list for only police activity while another for fire.

This, of course, is for P25 systems only or I guess other types that also require the basic info as well, then the talk groups after. I could be totally all wet and would gladly listen to how it is if I am.

Rick

 

[OsloViking1975]

Recently purchased this scanner and it works like a charm, just wondering if anyone out here knows if there are sub-banks for the talk id groups or if it all has to be in one list. I can't seem to find out anywhere I look.

Thanks!

There are no sub banks Just scan lists 1-22 actually. So yes you do have to program the talkgroups into one list. But if you want to break up the talkgroups for example police in one, ems, fire etc. You can put them into different scanlists but make sure you have to the correct system your monitoring such as Motorola: 800/900
Motorola: UHF/VHF,P25 Auto, P25 MANUAL EDACS STD, EDAC NARROW, LTR which ever it may be.
Don't forget though to put in your control channels if you decide to use a different scanlist.

Rick you are correct it is for P25 and Motorola Systems.

 

[ibagli]

Talkgroups can be in any and however many scanlists that you want them to be in. The talkgroup objects have to be affiliated with a trunked system, but the TSYS object itself doesn't actually belong to any scanlist.

 

[OsloViking1975]

Thanks Ibagli thats a much better explanation.

 

[RickS31]

Thanks guys. You have started clearing away some of the confusion. With ibagli's statement, this brings me to the crux of my 106 programming confusion.

Perhaps if I can use my real life situation you can permanently clear up the cobwebs on this. Here is my current plan. I have two major metro Atlanta area systems I want to monitor. Both are large P25 systems. I want to put my county in Scan list 1 with police only. Same Tsys data with fire TGs in #2, EMS in #3. I'll leave #4 empty for other found special TGs I want to monitor from the same system as I find them. Again, all on the same TSYS data and CCs.

I want to program the second major area system with different TSYS data and CCs in Scan List 5 w/Police, #6 w/Fire, etc. That's where my confusion lies.

I want to learn this cold before I get the programming software so that I really understand the nuts & bolts of the scanner. Your explanation will go a long way to helping me clean out the fog.

Thanks.

 

[ElliotGillum]

All you need to do is create the first TSYS and then using that TSYS assign the desired TGs to the desired scan lists. If you can do that then you should be able to do the exact same thing with the next system. Can you be a little bit more specific about your problem because it seems like you are answering your own question.

Thanks guys. You have started clearing away some of the confusion. With ibagli's statement, this brings me to the crux of my 106 programming confusion.

Perhaps if I can use my real life situation you can permanently clear up the cobwebs on this. Here is my current plan. I have two major metro Atlanta area systems I want to monitor. Both are large P25 systems. I want to put my county in Scan list 1 with police only. Same Tsys data with fire TGs in #2, EMS in #3. I'll leave #4 empty for other found special TGs I want to monitor from the same system as I find them. Again, all on the same TSYS data and CCs.

I want to program the second major area system with different TSYS data and CCs in Scan List 5 w/Police, #6 w/Fire, etc. That's where my confusion lies.

I want to learn this cold before I get the programming software so that I really understand the nuts & bolts of the scanner. Your explanation will go a long way to helping me clean out the fog.

Thanks.

 

[GrayJeep]

Not completely sure about the question but here's something might be useful-

A new TSYS has to be created when you want to use a different set of towers than another TSYS OR when you are really programming different systems (P25 vs EDACS, Town vs. State).

Scanlist can be used to just select different TGs you want to listen to. Don't need a new TSYS for that. (though it will still work)

(It takes awhile to wrap your head around how these radios work.)

 

[RickS31]

Thanks much for the info. I guess where my confusion lies is trying to classify the TSYS data as a requirement to be in the same scan list as the TGIDs I want to monitor. That (possibly misconception) comes from the fact that when I programmed my first TSYS it defaulted to SL1. I also noticed that when I went to program TSYS2 it also wanted to go into SL1 but did allow you to change SL number. That's where my assumption comes from and the piece I need clearing up on.

So, with your explanation above, I can create a new TSYS object by just programming it in and then when it comes up to enter TGIDs THEN just select the scan lists I want them in. Right? If so, I was trying to make this way too hard.

I presume then, when I want to add new TGIDs to a specific TSYS just do an edit on it, enter the new ID and assign it to the proper SL.

Let me know if I'm on the right track and thanks,
Rick

 

[GrayJeep]

Thanks much for the info. I guess where my confusion lies is trying to classify the TSYS data as a requirement to be in the same scan list as the TGIDs I want to monitor. That (possibly misconception) comes from the fact that when I programmed my first TSYS it defaulted to SL1. I also noticed that when I went to program TSYS2 it also wanted to go into SL1 but did allow you to change SL number. That's where my assumption comes from and the piece I need clearing up on.

So, with your explanation above, I can create a new TSYS object by just programming it in and then when it comes up to enter TGIDs THEN just select the scan lists I want them in. Right? If so, I was trying to make this way too hard.

I presume then, when I want to add new TGIDs to a specific TSYS just do an edit on it, enter the new ID and assign it to the proper SL.

Let me know if I'm on the right track and thanks,
Rick

I think you've got it. All those statements sound correct to me.

Every TG initially programmed goes to SL1 unless you change that from being the default SL in the GLOB experts (I think that's where it is) settings. A TSYS isn't connected to an SL until there is a TG and the SL connection is when you assign the TG to it.

I program using Win500 which gives a graphical presentation of "where" everything is. I don't think I would have been smart enough to do it thru the front panel. But now that I've been trained by Win500 I understand what I need to do at the front panel to make it go.

 

[W6KRU]

Hi Rick, Scanlists contain things that you can scan. You can't scan a TSYS. You scan TGs that point to a TSYS. A TG can point to one and only one TSYS. When you scan a TG the scanner checks the TSYS that the TG points to, to see if that TG is currently active on the TSYS that it points to.

When a new TG is created, it is in the default scanlist which is scanlist1 unless you change that. The default scanlist is an option you can change. I use scanlist 1 a lot for TGs that I really want to scan so I changed the default scanlist to 20 so all of my new TGs go into scanlist 20 which makes them easier to find.

 

[ElliotGillum]

Yes, it sounds like you got it.

A TSYS isn't in a scan list. You could have ten TSYSs programmed and have nothing in any of the scan lists. Your first TSYS didn't default to scan list #1, but subsequent TGs that were programmed did. All TGs default to scan list #1, so when you program your second TSYS you need to manually move the TGs that you want in scan list #2 to scan list #2.

Your second and third paragraphs are completely accurate.

It sounds like you have it down.

Thanks much for the info. I guess where my confusion lies is trying to classify the TSYS data as a requirement to be in the same scan list as the TGIDs I want to monitor. That (possibly misconception) comes from the fact that when I programmed my first TSYS it defaulted to SL1. I also noticed that when I went to program TSYS2 it also wanted to go into SL1 but did allow you to change SL number. That's where my assumption comes from and the piece I need clearing up on.

So, with your explanation above, I can create a new TSYS object by just programming it in and then when it comes up to enter TGIDs THEN just select the scan lists I want them in. Right? If so, I was trying to make this way too hard.

I presume then, when I want to add new TGIDs to a specific TSYS just do an edit on it, enter the new ID and assign it to the proper SL.

Let me know if I'm on the right track and thanks,
Rick

 

[RickS31]

Thanks to Elliot, Dan, ibagli, Oslo and NW0U for all the help. It now becomes much clearer how this works. Once I get this organized it will be great to use. On to Win500.

Thanks,

Rick

 

[fmon]

I have two major metro Atlanta area systems I want to monitor. Both are large P25 systems. I want to put my county in Scan list 1 with police only. Same Tsys data with fire TGs in #2, EMS in #3. I'll leave #4 empty for other found special TGs I want to monitor from the same system as I find them.

Set list #'s 1, 2 and 3 as stated but insure #4 has a wildcard only with no wildcard in 1st 3 list.

I want to program the second major area system with different TSYS data and CCs in Scan List 5 w/Police, #6 w/Fire, etc. That's where my confusion lies.

Same procedure as 1st 4 scanlist but with the new TSYS.

BTW, your thoughts regarding programming this scanner are very much like those by the GRE people when they designed and provided upgrades for this scanner.

 

[RickS31]

Hey fmon,

Thanks for the input. I suspect you are recommending putting the TG wildcard in SL 4 to act like a place holder making it easy to edit the Tsys to add other IDs later in that list. Instead of the wildcard I may just throw in an ID of a lesser favorite department.

Thanks guys, again. Always glad I found and joined this great forum.

Rick

 

[Highpockets]

Thanks to Elliot, Dan, ibagli, Oslo and NW0U for all the help. It now becomes much clearer how this works. Once I get this organized it will be great to use. On to Win500.

Thanks,

Rick

If you ever decide to become a Premium Subscriber of RR, here is a Guide that will help with importing info from RR to Win500 for uploading to your scanner, if you have the programming cable.

WIN500 - UtahRadio

 

[RickS31]

Thanks HighPockets for that from one Viet Vet to another.

Rick

 

[Highpockets]

Thanks HighPockets for that from one Viet Vet to another.

Rick

Brothers for ever!

 

[RoninJoliet]

My "UTMOST RESPECT for the Viet-Vets, i would not be free if it were not for you....If you program a Trunk system in SList 1 with a "Wildcard", as you see the TG's pop up you press "stor", then you press "pgm", go to the SList you would like them in, ex:4 and press the "sel" and you will get the *, astrisk which designates the SL you want them in....Then press "save"....

 

[RickS31]

RoninJoliet

Certainly not the right forum for a right/wrong discussion about the Vietnam war but I'm sure many of that era's vets believe it was probably, in hindsight, ill-advised. But then like all good US military men and women, ours was but to do or die. Unfortunately, many of our compatriots did die. Thanks so much for your kind statement. Wish we would have had that kind of sentiment at the time.

That aside, was curious about the store function and was getting ready to "play" with that at your post.

Regards,