Share TGRP's in EDACS Networked System

[kruser]

Hi,

I like to monitor an Edacs Networked Multi-zone or site system.
AmerenUE in Missouri to be specific.

The system has several sites and when I travel, the primary site I monitor becomes weak so I switch to one of two other sites as needed.
My problem now is that I've become interested in a StarCom system across the river that is fairly big and thus fills up the PSR-600 memory. So I'm attempting to clean things up but having an issue as listed below.

My question is, is it possible to program the three Edacs sites as seperate TSYS's but let them share the common set of TGRP ID's. The Edacs sites all share the same TGRP ID's.
I know the three EDACS sites have to go into a seperate TSYS location due to LCN ordering but I don't know if sharing of the TGRP's can be accomplished between the three TSYS's.

I use WIN500 and have programmed one site to use the TGRP's in scan list 2 which is also the TSYS id.
Now I go back and again add one of the other sites TSYS's frequencies but assign it to ID 3.
I then go into my scan lists in WIN500 and change them all to be associated with both 2 and 3.

However, I never see my talkgroups on the second system I added even though I associated the TGRP's assigned to scan list 2 with scan list 3. All that TSYS 3 shows are the wildcards but no talkgroup text tags etc.

When I programmed the first system using WIN500 and the RR database I selected all the frequencies for the primary site I monitor as well as ALL the TGRP Id's. I set the first system to Scanlist 2.
When I added the second system I just imported the site frequencies plus allowed it to create wildcards. I did not import the TGRP's again as I did not want to use up the memory by duplicating talkgroups. I set this second site to Scanlist 3.

Am I doing something wrong or does this not work on EDACS systems or perhaps a limitation in the PSR500/600?

Thanks for any advice.

 

[qlajlu]

I have never worked with an EDACS system and although I know it must have the frequencies in a certain order is it not possible to put the frequencies from the second EDACS system in the same System Frequencies list since you are working with objects instead of banks? That frequencies list will accept up to 32 frequencies and since both systems service the same TGs it would be like entering a second site under a Motorola 800 MHz SmartZone system.

Just asking because I really don't know.

 

[jb853]

TSYS Sharing

You cannot share talkgroup IDs among systems. You can out them multiple scan lists, but a given ID can only belong to one TSYS.

 

[Astrak]

Uhhh no a TGID can belong to many TSYS.

 

[ibagli]

A single TGID object can only belong to one TSYS, though. To put the same talkgroup in more than one system requires it to be duplicated.

My question is, is it possible to program the three Edacs sites as seperate TSYS's but let them share the common set of TGRP ID's.

No. They must be duplicated for each TSYS.

 

[kruser]

I have never worked with an EDACS system and although I know it must have the frequencies in a certain order is it not possible to put the frequencies from the second EDACS system in the same System Frequencies list since you are working with objects instead of banks? That frequencies list will accept up to 32 frequencies and since both systems service the same TGs it would be like entering a second site under a Motorola 800 MHz SmartZone system.

Just asking because I really don't know.

I don't think an EDACS system will work like that.
You thoughts do bring up an interesting idea though.

Say one was lucky enough to have a multi-site edacs system that used LCN's that did not repeat from one site to the next, I wonder if it would work to put all the LCN's for two or more sites in one TSYS and then simply lock out the control channel for the site you do not want. This of course would only work if no two LCN's used the same LCN number.
I also don't know if individual frequencies for a given TSYS can be locked out in an EDACS system on the PSR-500/600. I think individual frequencies can be locked out in the Unidens but I'd have to confirm that.
I think the AmerenUE sites I'm working with may have some sites that don't have duplicate LCN's being used but I'm not sure I'm in range to test this theory.

Maybe someone else has tried this before and can confirm if it works or not.

I think it is rare to find a multi site edacs system that does not re-use LCN's across sites though so if this works then it would only apply to a very small percentage of users.

 

[kruser]

A single TGID object can only belong to one TSYS, though. To put the same talkgroup in more than one system requires it to be duplicated.



No. They must be duplicated for each TSYS.

Thanks everyone for their input. I figured my idea must not work after several hours of trying different combinations of settings and bad results each time

I have one other question for those that are familiar with Arc500 and Win500.
While messing around with my idea I find that in ARC500 it is relatively easy to re-associate a TGRP with a TSYS. But I cannot find any way of doing the same in WIN500.
Sure I can change the scan list for a given set of TGRP's but that does not appear to actually associate the TGRP's with a different TSYS.
Is this not possible in WIN500 or did I miss something?
The only way I've found to do such in WIN500 is to delete the TSYS and all associated TGRP's and then re-import them into the correct TSYS via the RR web import feature.

I guess if nobody knows then I'll repost this question in radio software forum.

Thanks again!

 

[Forts]

For a multisite EDACS system near me, I ended up making separate systems for each site, assign the talkgroups that I wanted, then put all the systems on the same scan list. Not very efficient memory wise, but it seems to work ok. Fortunately there are only a handful of talkgroups that I want to monitor so it was easy to do.

 

[jb853]

Uhhh no a TGID can belong to many TSYS.

Astrak,
Perhaps I should have been more clear, since you seem to be confused. When I referred to a "talkgroup" here, I meant the entire "object", not just the numerical ID. A "talkgroup object" can only be attributed to one "TSYS" in the PSR-500/600. If a user desires to use the same talkgroup number in more than one system, the user must create an "object" for each TSYS. There is no restriction on multiple uses of the same talkgroup number in different systems.

 

[SCPD]

You can totally have multiple systems ... with the same talkgroups. I have my PSR-500 programmed like this.

 

[ibagli]

But only if you duplicate the talkgroup objects completely. It is not possible to have one talkgroup object affiliated with more than one system object.