Putting Two TRS into One TSYS in Pro-106?

[jeffkraussws]

Can create a TSYS object that contains the frequencies for two different trunked radio systems (of the same type)? The two systems don't have overlapping coverage areas.
I know I can only have one TGRP object for each talk group ID, so if the talk group IDs overlap it might display the wrong alpha tag.

 

[JoeyC]

You can put whatever frequencies you want in your TSYS, whether they are part of the system or not, it will only work with the valid ones, but why would you want to do this when alls you would need to do is create the 2nd TSYS and associate the associated TGs with it???

 

[Forts]

Just create two separate systems but assign them to the same scanlist.

 

[jeffkraussws]

There is a limit of 20 TSYS objects and I want to have access to more than 20 trunked systems.

 

[Forts]

Limit of 20? 20 Where? I have 22 trunked systems programmed into my current configuration.

 

[jeffkraussws]

Limit of 20? 20 Where? I have 22 trunked systems programmed into my current configuration.

20 or maybe 22, that seems to be the limit for TSYS objects.
Please tell me how you entered more than 20 TSYS objects.
Or how you entered more than 20 trunked systems.

 

[Forts]

Well.. I used PSREdit to program my radio. I started by importing all the systems I had in my Pro-96 then went from there. Just created new systems as I needed them. As I mentioned earlier I currently have 22 trunked systems in my radio, spread over the 20 scan lists. Once scan list is for distant 'skip' systems and has about 5 systems assigned to it. You should only be limited by your available memory.

 

[gearbox]

20 or maybe 22, that seems to be the limit for TSYS objects.
Please tell me how you entered more than 20 TSYS objects.
Or how you entered more than 20 trunked systems.

I've had my 106 for all of three days . . . ahem . . . so i shouldn't give advice. Conside the source.

There is a limit of 20 'regular' scan lists, plus FAV and SAME. But, each scan list is essentially unlimited (save the overall 1800 V-folder limit) to the number of objects on it. TSYS objects are just one possible component . . . and there is no inherent limit (again, subject to the 1800) to the number created.

The pre-programmed workspaces are set up one TSYS per list . . . but that needn't be so.

I lack a cable -- and it is awfully tedious to input via keys -- to test this, but the documentation is fairly clear. If i'm wrong, then the documentation is awfully misleading.

-- gary ray

 

[mikey60]

20 or maybe 22, that seems to be the limit for TSYS objects.
Please tell me how you entered more than 20 TSYS objects.
Or how you entered more than 20 trunked systems.

There are 20 (plus Favorites and Skywarn) scan lists. Talkgroups from multiple TSYS objects may be placed into a single scan list without a problem.

As an example, when I travel across the state to visit family, I have one scan list for the Lansing Michigan area. Within that scan list, I have talkgroups from the MPSCS (statewide P25 System), Talkgroups from Ingham County (400MHz EDACS), talkgroups from Clinton County (800 MHz EDACS), and conventional frequencies from Eaton and Ingham counties. Turning on a single scan list turns on all of those items. (3 separate trunked systems and some conventional)

In your case, you could create two separate TSYS Objects (one for each system), and place the talkgroups for both systems in the same scan list.

Mike

 

[jeffkraussws]

Ah. I thought there was a limit of one TSYS per scan list, because that's the way the vscanner data is set up.
Thanks.

 

[mikey60]

Ah. I thought there was a limit of one TSYS per scan list, because that's the way the vscanner data is set up.
Thanks.

Nope, you can mix and match talkgroups, Conventional, sweeper (stalker), and search objects in any scan list. The talkgroups can be from the same trunked system (TSYS) or from multiple trunked systems of any type...

Mike