Ok, I am going to want to montior a local Astro SmartZone system. I will be programming the Astro Spectra for WAMSS so that the radio does not affliate with the system.
Now, there are 16 sites in this system. In order to properly receive the system thoughtout the state, do I need to create a new system for each site, or do I use 1 system for everything? If I just use 1 system, I can only input 15 talkgroups, and there are more than 15 talkgroups system wide.
Is this correct? 1 "system" per site?
Any other tips would be great.
This is one of the systems that I would like to have in there:
http://www.trunkedradio.net/modules.php ... DB&sid=832
Astro trunking help
Moderator: Queue Moderator
Astro trunking help
Lowband radio. The original and non-complicated wide area interoperable communications system
Pj,
Are you using a xts3x00 or an Astro Saber? I programmed an xts3000 and used one system with multiple sites. I just added more than one personality to accommodate more than 15 talkgroups. If you'll be doing a lot of scanning try to group those talkgroups in the same personality, it makes setting up your scan list a lot easier. I don't know how different it is for an astro saber though.
Are you using a xts3x00 or an Astro Saber? I programmed an xts3000 and used one system with multiple sites. I just added more than one personality to accommodate more than 15 talkgroups. If you'll be doing a lot of scanning try to group those talkgroups in the same personality, it makes setting up your scan list a lot easier. I don't know how different it is for an astro saber though.
T.J.P. FF/EMT
I'm using an Astro Spectra, but I think I found a way, I just have to play with the radio on monday to see if it works. I was thinking of terms or all sorts of channels in one zone, but if I put everything BUT the trunking in zone 1, and I but the trunking info in zone two and not enable zones in the radio. Round about way, lets see if it works.
Lowband radio. The original and non-complicated wide area interoperable communications system
Get rid of AMSS and program "Coverage Type" for "Disabled" and "Affiliation" for "PTT." (And then don't PTT.)
Program each "zone" as a separate system (i.e., SysID and control channel(s)) separately and manually change systems when moving about. You can define as many personalities for each system as you like.
Something like Trunker will be helpful in figuring out how talkgroups are allocated within the system. The choices are:
Native only: the T/G will only come up on one "zone" (or "system").
Simulcast: audio on the T/G will be OSW'd on all "zones" all the time.
SmartZone: audio on the T/G will be OSW'd on his "native" "zone" ("system") and also on any other "zone" on which any user has affiliated with that T/G selected.
SmartZone allows users to treat a multi-"zone" system as a single system, but it only works if you are capable of affiliating and allowed to do so. For others, you have to treat the overall system as comprised of separate systems.
Program each "zone" as a separate system (i.e., SysID and control channel(s)) separately and manually change systems when moving about. You can define as many personalities for each system as you like.
Something like Trunker will be helpful in figuring out how talkgroups are allocated within the system. The choices are:
Native only: the T/G will only come up on one "zone" (or "system").
Simulcast: audio on the T/G will be OSW'd on all "zones" all the time.
SmartZone: audio on the T/G will be OSW'd on his "native" "zone" ("system") and also on any other "zone" on which any user has affiliated with that T/G selected.
SmartZone allows users to treat a multi-"zone" system as a single system, but it only works if you are capable of affiliating and allowed to do so. For others, you have to treat the overall system as comprised of separate systems.