|
How to use the matrix /
PNW Matrix:
Find the repeater column and then scan down to see
which talkgroups are listed. Or to find where
a talkgroup may appear, locate the talkgroup of
interest and scan across for repeaters that carry
that talkgroup. The entry at the intersection
tells you if it is carried full-time (F) or if it is
on
PTT (P). If
a "P" then the numbers indicate how long the
talkgroup is active after any local kerchunk or
key-up is initiated. The number after the
forward slash (/) indicates how long it will hold
off most other talkgroups on that timeslot after the
last local kerchunk. A "m" appearing before or
after the slash indicates control by
MCT as well. These timers
and MCT's help to insure
that an active local talker will not loose that
talkgroup. |
|
All PTT actions connect
a TG immediately if their is no active talker.
HOWEVER: if there is an active talker, at the
time of your PTT or Kerchunk, the talkgroup traffic will not be
connected or heard by you until the current talker unkeys
and the next talker keys-up. |
|
Columns: F/y = Fulltime / Hold-off Timer (y min)
Columns:
Px/y = PTT On Timer (x min) / Hold-off Timer (y min)
Columns:
Pr/y = PTT On Timer (x min)
r = Receive Only / Hold-off Timer (y min)
Columns: Px/0.f = HO's only for the fulltime
TG's for minimal control (.f = fulltime) |
Blank = No appearance of
TG on manager
+ = Some hold-off timers are in place but incomplete
programming
MCT controls=m for 59 min On/ 29 min Off, may or may
not have supplemental HO's for fulltime talkgroups
for better experience |
|
The
stock talkgroups available on most managers are:
Bridge 2, Comm 1, DCI 1, DCI 2, Local 1 & 2, Parrot
1, TAC 1, TAC 310, TAC 311, TAC 312, TAC English and USA.
Custom manager support is being curtailed except for
repeaters in our Pacific Northwest region. |
|
Master Control Talkgroups
or MCT's may be
implemented to provide more control over the
timeslot than the timer based "hold off's".
New managers are now being programmed for active
local repeater users' control and relying on
Hold-off timers far less |
|
Local 1 and Local 2 are not connected outside of its
manager/IPSC network unless by special request.
Hold-off timers may turn off some networked
talkgroups for 5 minutes as a loose form of priority to locally
generated
traffic. Some custom managers may hold-off
talkgroups for up to 2 hours for SAR or public
service events. |
|
Typical PTT talkgroups
have an "on-timer" for 15 minutes and most have
"hold-off timers" for 3 minutes. Not all
hold-off timers for the PTT TG's may be in place.
Some TG's have a bare minimum as indicated by "P15/0" as
they are quick to program and somewhat
useable for PTT purposes by repeaters that have not
expressly requested those particular talkgroups.
In other words, the talkgroup is programmed into the
manager and usable via PTT but the more involved
programming to implement the hundreds of hold-off timers, has
not been implemented. So it is probable
that other talkgroups may capture the slot and stomp
on these "zero" talkgroups, especially the full time
talkgroups. Somewhat of an approach that "it
is better than nothing". |
|
Yellow Highlight
or
"Not Active" indicates that there are no current
active connections outside of the DCI c-Bridge or
not currently in active use on DCI.
These talkgroups are currently: Colorado, Kansas,
New Jersey (currently Tri-state is active as NJ), Texas and Utah. Typically they may
have been in use at one time but not currently in
use. |
|
This
matrix is now the baseline or controlling document to determine all
interactions on each manager. If you have any
issues with talkgroups, stomping on other
talkgroups, etc, please look to this chart,
determine what should be the listed action and then
armed with that information,
report issues. |
|
∞∞
indicates
that a talkgroup may not be available to all
managers, in your area or may come with restrictions
on their use. These conditions are not
necessarily set by
DCI but may be part of an agreement with other
organizations which control their talkgroups
appearance, distribution and/or use. |
|
LAST
THOUGHT: The coding of the c-Bridge bridge
groups and super groups is fairly complex when
handling over 500 bridge groups and in excess of 50
talkgroups on 2 timeslots, but especially DCI's
timeslot 2 which has the bulk of the networked
talkgroups. There are around 7,500 programming
lines, each have up to 10 pieces of data (North
America alone had over 775 lines of coding at last
count). So, unless requested, not all
hold-offs on TS 2 have been created due to the
additional work/complexity and because the PTT TG's
have less potential to collide with the full-time
TG's. Coding mistakes in logic as well as typos,
inject more issues. So reporting problems is
encouraged to both excise the mistakes as well as
complete the hold-offs as they are ever more
important as more talkgroups and managers are added
to the DCI c-Bridge. Your input is needed
to reduce your users frustration when TG activity
collides. If something occurs that you feel is
wrong, document and report it, ASAP so that the
logging info can be used to aid in fixes. |
