PNW DMR       News     Talkgroups     Matrix; OR WA     MCT     Visuals     Netwatch     YahooGroup     History

DCI Home

DCI Site Map

Oregon Talkgroup Matrix  for Managers, TG Appearances & Timers

This is the controlling document used by PNW DMR Oregon for tracking its repeater managers, talkgroups and their timers

The Oregon South manager's talkgroup deck is not yet finalized

See Washington/Idaho manager talkgroup matrix

This page may be updated frequently, refresh to see any changes:    (Revised: 05/16/2017)




Oregon-N Oregon-S Hebo Mt Hood Talkgroup
Audio Test 2 9999 2 P2/0 P2/0 P2/0 P2/0 Audio Test 2
Bridge 2 (bm) 3100 2   P15/m     Bridge 2 (bm)
British Columbia 1 3027 1   P15/m     British Columbia 1
Comm 1 3777215 1   P15/m     Comm 1
Comm 2 3777216 2         Comm 2
DCI 1 3160 1   F/m     DCI 1
DCI 2 3162 2   F/m     DCI 2
iCall 2 8952 2         iCall 2
I-5 3168 1 F/3 F/m F/m F/m I-5
Local 1 3181 1 F/5 F/5 F/5 F/5 Local 1
Local 2 3166 2 F/5 F/5 F/5 F/5 Local 2
Mountain 2 (bm) 3177 2   P15/m     Mountain 2 (bm)
North America 2 3163 2   P5/m     North America 2
Oregon 1 (bm) 3141 1 F/3 F/m F/m F/m Oregon 1 (bm)




Oregon-N Oregon-S Hebo Mt Hood Talkgroup
Parrot 1 9998 1 P2/0 P2/0 P2/0 P2/0 Parrot 1
PNW 1 3187 1 F/3 F/m F/m F/m PNW 1
PNW 2 103187 2 F/3 F/m F/m F/m PNW 2
PNWR 2 (bm) 31771 2         PNWR 2 (bm)
TAC 310 (bm) 310 2 P5/3 P15/m P5/m P5/m TAC 310 (bm)
TAC English 2 123 2         TAC English 2
USA 2 1776 2   P15/m     USA 2
Washington 1 (bm) 3153 1 P5/3 P15/m P5/m P5/m WA 1 (bm)
Washington 2 103153 2 P15/3 P15/m P15/m P15/m WA 2




Oregon-N Oregon-S Hebo Mt Hood Talkgroup

Data / Private Call

    N/No N/No N/No N/No Data/Private Call

MCT Enabled

    No Yes Yes Yes MCT Enabled
How to use the 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.  These timers and MCT's help to insure that an active local talker will not lose 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.

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 but some HO's may be coded as a convenience to users, possibly: BC 1, DCI 1, I-5, ID 1, PNW 1 OR 1, WA 1

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".

Columns:  F/y = Fulltime / Hold-off Timer (y min or mct)
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
MCT controls = 55 or 59 min On / 15 or 29 min Off and may or may not have supplemental HO's for fulltime talkgroups for better experience

∞∞ 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.

This slate of talkgroups has been approved by each repeater owner or manger admin.  If you want changes, additions or deletions, then the owner or admin must agree to that.  Please contact them directly for discussion of any changes.

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 Search and Rescue, EMCOMM or other public service events.

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.

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 and MCT's 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 if it is still available.

 Questions about your manager     /     Return to PNW's Home page

Revised: 05/23/2017 16:27