This discussion is surrounding this system:
Probably one of the last analog (ProVoice capable) public safety systems left on the air.
The system architecture can best be described as having three Simulcast cells; North, South and Beachside. Please do not get wrapped around the term simulcast with this particular system. This system does not operate like a modern-day P25 simulcast system (where each site would have the exact same frequencies). Totally different on this system.....
A few things up front.
I never was, and do not claim to be, an EDACS expert.
I am aware that EDACS can be set up to make an individual TG (or entire Agency / Fleet / Subfleet) to operate in "Wide-Area" mode - which will key the talkgroup across all of the simulcast sites of the system (in this case, all 3 of the sites would be simulkeyed if a group was set to W/A. I do not think that very many of the TGs on this particular system are configured this way.
So here is the dilemma / question.
In my example, I will say that I have just imported the ENTIRE system and TGs into Sentinel.
At the bottom of the favorites list, you will see the 3 simulcast sites, North, South and Beach - along with all the various municipalities associated with Brevard county.
I am going to use two extremes for examples.
1. Titusville - this city is at the north end of the county. There is no reasonable probability that a radio affiliated with this city would be "roaming" onto the beach or south towers.
2. Palm Bay - similar situation. This city is at the extreme south end of the county, and none of their radios should ever be on the North system.
so - for these two examples, what I would want to do is limit the systems that would be scanned for those particular entities. In other words, there is no reason for my scan list associated with Titusville to scan the south tower - and no need for the Palm Bay talkgroups to scan the north tower.
What's the best solution here?
Is it to create a "new" system for these two examples and delete out the non-applicable sites?
or
is the best way to just dump everything into a single favorites list and "let the radio figure it out"?
////
I >think< my current method - a single system entry and favorites list with all cities - is causing loss of some traffic.
Then again, the more systems I create, wouldn't there be a potential to slow down the overall time it takes to scan the TGs I want to hear.... (?) - because the radio has to swap over to a "new" (aka different) system for those "other cities"....?
TIA
doug
Brevard County Government Trunking System, Brevard County, Florida
Brevard County Government Trunking System Profile
www.radioreference.com
Probably one of the last analog (ProVoice capable) public safety systems left on the air.
The system architecture can best be described as having three Simulcast cells; North, South and Beachside. Please do not get wrapped around the term simulcast with this particular system. This system does not operate like a modern-day P25 simulcast system (where each site would have the exact same frequencies). Totally different on this system.....
A few things up front.
I never was, and do not claim to be, an EDACS expert.
I am aware that EDACS can be set up to make an individual TG (or entire Agency / Fleet / Subfleet) to operate in "Wide-Area" mode - which will key the talkgroup across all of the simulcast sites of the system (in this case, all 3 of the sites would be simulkeyed if a group was set to W/A. I do not think that very many of the TGs on this particular system are configured this way.
So here is the dilemma / question.
In my example, I will say that I have just imported the ENTIRE system and TGs into Sentinel.
At the bottom of the favorites list, you will see the 3 simulcast sites, North, South and Beach - along with all the various municipalities associated with Brevard county.
I am going to use two extremes for examples.
1. Titusville - this city is at the north end of the county. There is no reasonable probability that a radio affiliated with this city would be "roaming" onto the beach or south towers.
2. Palm Bay - similar situation. This city is at the extreme south end of the county, and none of their radios should ever be on the North system.
so - for these two examples, what I would want to do is limit the systems that would be scanned for those particular entities. In other words, there is no reason for my scan list associated with Titusville to scan the south tower - and no need for the Palm Bay talkgroups to scan the north tower.
What's the best solution here?
Is it to create a "new" system for these two examples and delete out the non-applicable sites?
or
is the best way to just dump everything into a single favorites list and "let the radio figure it out"?
////
I >think< my current method - a single system entry and favorites list with all cities - is causing loss of some traffic.
Then again, the more systems I create, wouldn't there be a potential to slow down the overall time it takes to scan the TGs I want to hear.... (?) - because the radio has to swap over to a "new" (aka different) system for those "other cities"....?
TIA
doug