Harris Dynamic Patching

[KI5IRE]

I have some questions about the Harris Dynamic Patching (or whatever the real name may be..)

Is there any specific block of TGIDs that is reserved for this? It seems in the few other threads I've read that most of the systems have dynamic patching on TGIDs 65xx. However, on a system near me, there are talkgroups with 4xxxx, 5xxxx and 64xxx.

My other question is are talkgroups with 4 digits normal static talkgroups and 5 digit talkgroups usually patches?

That's the way it appears to me...

I am mainly trying to figure out if there are specific TGID ranges for my scanners to add to my scan list without having to add and lockout talkgroups I don't want and then set it in ID SCAN mode.

 

[natedawg1604]

The easiest thing to do is monitor the system with a rtl dongle and Unitrunker, that will show you what TG's your particular Harris system uses for patching.

 

[GTR8000]

If Harris is anything like Motorola when it comes to ISSI patching and roaming, the temporary TGID's and temporary WUID (Working User ID) are determined by the system admin(s). You provision a block of ID's for each purpose, which are used exclusively for these temporary patches and roaming users. In other words, they can be pretty much any range of ID's as chosen by the operator of the system, as long as they don't conflict with "real" ID's on the system, it doesn't much matter. 65xxx seems to be something of a loose standard for the range of temporary TGID's, and I often see 167xxxxx range for temporary WUID's on ASTRO 25 systems being used. YMMV with your local systems.

 

[rjschilder]

If Harris is anything like Motorola when it comes to ISSI patching and roaming, the temporary TGID's and temporary WUID (Working User ID) are determined by the system admin(s). You provision a block of ID's for each purpose, which are used exclusively for these temporary patches and roaming users. In other words, they can be pretty much any range of ID's as chosen by the operator of the system, as long as they don't conflict with "real" ID's on the system, it doesn't much matter. 65xxx seems to be something of a loose standard for the range of temporary TGID's, and I often see 167xxxxx range for temporary WUID's on ASTRO 25 systems being used. YMMV with your local systems.

This is correct, they are referred to as System Assign ID's (SAID).

 

[Forts]

^^^ what he said. My local Harris system has a block of 100 (no idea why so many) TGIDs that are used as SAIDs. The system seems to rotate thru them in groups of 10 at a time, give or take.

 

[KI5IRE]

Are SAID's the same thing as Simulselect?

Also, this may be getting a little off topic from this thread, but can anyone help me in figuring out the best way to program these kinda talkgroups into the Uniden scanners and Unication pagers? I work overnights as a TV photojournalist, so I will be needing these patches when in and out of the car in the case of priority calls being dispatched (how I've been seeing them done on BCFY calls) rather than on a static talkgroup.

 

[KI5IRE]

The easiest thing to do is monitor the system with a rtl dongle and Unitrunker, that will show you what TG's your particular Harris system uses for patching.

It is for the OKC Metro P25 System in Oklahoma City, OK. I've been following along with the activity and trying to identify unidentified talkgroups using the BCFY calls platform until I get moved up there in a couple of weeks and I plan to run a Pro96Com session as soon as I get moved.

 

[wa8pyr]

Are SAID's the same thing as Simulselect?

Also, this may be getting a little off topic from this thread, but can anyone help me in figuring out the best way to program these kinda talkgroups into the Uniden scanners and Unication pagers? I work overnights as a TV photojournalist, so I will be needing these patches when in and out of the car in the case of priority calls being dispatched (how I've been seeing them done on BCFY calls) rather than on a static talkgroup.

Once you identify the specific range of talkgroups used for dynamic patching, just program them into your scanner as you would any other talkgroup, and name each one "Patch xxxxx" (where xxxxx is the talkgroup ID). If you later confirm that a specific patch talkgroup is for a specific function you can change your entry for that TG.

^^^ what he said.

Dang it, stole my joke...

 

[rjschilder]

Are SAID's the same thing as Simulselect?

I don't think Simulselects utilize a SAID, I'd have to check. I don't believe so though, because when you Simulselect, only the dispatcher can communicate to all the talkgroups in the simulselect, but they can't respond to each other.

So...the dispatcher can PTT on TG 1,2,3 at the same time. A person on TG 1 can respond to dispatch, but 2 and 3 will not hear that transmission. If it were a patch, 1,2, and 3 would hear every transmission no matter who was talking. Hopefully that makes sense.

 

[rjschilder]

Also, I'd agree with programming the Patch XXXXX into a scanner. However, you probably won't get to name it anything else. You don't get a choice of what SAID is used. It's all determined by the core.

 

[wa8pyr]

Also, I'd agree with programming the Patch XXXXX into a scanner. However, you probably won't get to name it anything else. You don't get a choice of what SAID is used. It's all determined by the core.

As it was explained to me, the sysadmin can assign a specific SAID to a specific patch combination (for example, a fireground talkgroup to a mutual aid talkgroup), but I've never been able to confirm this.