PNWDigital.Net MMDVM Talkgroup Matrix
for Managers, TG Appearances & Timers

UPDATE: The talkgroup picker is now the authoritative source used by PNWDigital.Net's repeaters for listing the repeater's talkgroup deck.  This page will likely not updated further.

The PNWDigital.Net's MMDVM servers are an adjunct to and for the use of our c-Bridge repeater network.  The MM's were not designed to be used for hotSpot to hotSpot QSO's.  While is is technically possible, we wish our servers to primarily support our repeater network.  PNW repeaters should be your first choice and leave the MMDVM servers for those who do not have access to a PNW repeater.

If you wish to use a PNW MMDVM server, you may request access.  Much more information is in our MMDVM IO group and you should be a member of this group if you wish to use our MMDVM servers.

On-timers tend to be shorter for the PTT talkgroups on the MMDVM servers are we are handling talkgroups from both repeater timeslots and shoving them down a single slot pipe to the hotspots.  These servers tend to have many hotspots connected and shorter timers frees up the resource sooner fo the other users.

Be sure not to put your hotSpot on any repeater output or input/output frequency as it likely will result in looping and render the server useless and busy out a timeslot on the c-Bridge.  If you have 2 hotSpots, use different frequencies (and a different IRD or ID extension) for the same reason.

PNW has 2 servers each for Suzy and Bridget, known as East or West.  They have the same talkgroup decks but off redundancy and user choice.  Members may use whichever works best from their location.

Rex is our server for use of 2 slot devices such as MMDVM based repeaters and now 2-slot hotSpots.  Most hotspots are single slot devices so the c-Bridge programming is different for the hold-off timers.  All other MM servers have all talkgroups the same timeslot, 1 or 2, depending on the HotSpot.

TAC 2 and TAC 8 have been added.  TAC 8 has no connections to any c-Bridge repeaters so it is the primary MM-to MM QSO talkgroup. Talkgroup 9 is no longer supported between MMDVM servers and is strictly for use to hear messaging.

W7NCX's LED VU Meter will soon be driven by a dedicated MMDVM server and will annunciate Audio Test 2, Parrot 1, PNW Regional and Washington 2 as well as a few other talkgroups.

PNWDigital.Net Members: See our Wiki page for more information on our MMDVM portal project.


PNWDigital.Net Members: Please do not share any MMDVM server credentials.  Only Peter is public.

This page is the controlling document and may be updated frequently, refresh to see changes:      (Revised: 10/23/2020)

TG Viewer


Public Access
(WA East)
(WA West)
(2 slot devices)
Audio Test 2 9999 P1/0 P1/0 P2/0   P1/0 P1/0 P2/0
Cascades East 1 3191 P15/2m P5/2m? P15/3m P5/2m F/2m n/a F/3m
Idaho 1 (bm) 3116 P15/2m P5/2m? P15/3m   P15/2m   P15/3m
I-5 3168 P10/2m n/a n/a n/a n/a P5/2 n/a
Montana 2 (bm) 3130         P5/2m    
MPRG1-2 (bm) 31301         P10/2m    
Oregon 1 (bm*) 3141 P5/2m P5/2m? F/3m   P5/2m P15/2 P15/3m
Parrot 1 9998 P2/0 P2/0 P2/0   P2/0 P2/0 P2/0
PNW 1 3187 F/2m P5/2m? F/3m   P5/2m P5/2 F/3m
PNW 2 103187 F/2m P5/2m? F/3m   P5/2m P5/2 F/3m (TS2)
PNW Reg 2 (bm) 31771 F/2m P5/2m? F/3m F/2m F/2m F/2 F/3m (TS2)
PS 1 ----- F/120m F/120m   n/a F/120m F/120m  
PS 2 ----- P60/60m F/60m   n/a P60/60m P60/60m  
TAC 1 8951 P5/2m P5/2m? P15/3m P5/2m P5/2m P5/2 P15/3m (TS2)
TAC 2 8952 P5/2m P5/2m? P15/3m P5/2m P5/2m P5/2 P15/3m (TS2)
TAC 8 (MM to MM QSO) 8958 P5/2m P5/2m? P5/3m   P5/2m P5/2 P5/3m (TS2)
USA 2 1776             P15/3m (TS2)
Washington 1 (bm*) 3153 F/2 P5/2m P15/3m P15/3m F/2m F/2 F/3m
Washington 2 103153 F/2 P5/2m P15/3m Net Only P15/2m F/2 F/3m (TS2)

Data / Private Call

  Yes/No Yes/No Yes/No No/No Yes/No Yes/No Yes/No

MCT/HO Enabled

  Yes/Yes Yes/Yes Yes/Yes No/No Yes/Yes Yes/Yes Yes/Yes

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.

A Kerchunk will 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.

Peter is a minimal support server for use primarily as a testing server for hotspot set-up

TAC 8 is a local only talkgroup and is not connected across the other servers nor the c-Bridge.

n/a 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 PNW but may be part of an agreement with other organizations which control their talkgroups appearance, distribution and/or use.

Master Control Talkgroups or MCT's and HO's (hold-offs) 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 MCT control and relying on Hold-off timers far less but some HO's may be coded as a convenience to users, possibly: I-5 1,ID 1, Oregon 1 , PNW 1/2, PNWR 2 and/or WA 1&2.  So options are Yes/No/Partial for both MCT's and Hold-off timers being coded into each manager.

Typical PTT talkgroups on the MMDVM servers have an "on-timer" for 15 minutes and most have "hold-off timers" for 2 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)
~~ = Confirmed working while Bell VHF manager is being built out
* = talkgroup is PTT from Brandmeister

Blank = No appearance of TG on manager
tbd = no decision on this talkgroup on this manager
Question Mark = unknown status, incomplete programming, pending adoption or otherwise potential changes tbd
+ = 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

This matrix is now the baseline or controlling document to determine all interactions on each manager listed in this matrix.  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.

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


Revised: 10/23/2020 12:07