Uniden 396XT/996XT UID programming

[radio]

1. Do you put ALL the UIDs for an entire system in one group or do you separate fire unit UIDs into fire groups where those talk groups are programmed and law enforcement into those groups, etc?

2. What do you do for mutual aid situations where a unit comes up on a separate different system for mutual aid? Do those UIDs get programmed into that other system?

Examples: Ft Carson has its own system. They respond with both CSFD and El Paso and come up on that system. Do I put Ft Carson unit UIDs into the CSFD/El Paso system?

Same goes when El Paso runs into Douglas County and vice versa? Douglas County has its own system Do I put those UIDs in each others systems?

I just started using a program that logs the UID transmissions so I have to listen and write that info down and keep listening and figure what UID is for whom Considering almost all units have the multiple radios, this task is going to be quite time consuming.

Thanks in advance for any hints.

 

[Voyager]

1. The UIDs are system-wide, so they can all go in one Group. You don't need to waste a GQK on it, either.

2. If the system is different, it will have a different UID most likely. A different TG on the same system would use the same UID.

Keep in mind the XT series is limited to 500 IDs per System, so you may have to separate PD and FD to separate Systems, for example.

 

[alphaacres]

I use Proscan for UID labeling and I put P25 and one trunk labels in the same list they can be as long as you want this only works with Proscan's virtual control and history log can be found in Options - Logging - UID Text tag lookup file

You can put the UID labeling in a TGID list but it does not work the way it should and Uniden will not add the UID list editor HP 1/2 and 536HP 436HP has.

 

[Voyager]

You can put the UID labeling in a TGID list but it does not work the way it should and Uniden will not add the UID list editor HP 1/2 and 536HP 436HP has.

My RIDs are in Groups called RIDs and work fine.

 

[radio]

Just heard Palmer Lake and Tri Lakes responding into Douglas County. They came up on Douglas Co System with their same UIDs from the El Paso Co home system.

What a task sorting out all these UIDs!

Thanks for the hints.

 

[ofd8001]

I keep all of my Unit IDs in its own group. That makes it easier to "pass" them from one scanner to another. For example x96XT to x36HP. Use of an intermediate spreadsheet to add/extract the "i" is needed, however.

 

[alphaacres]

I have the problem with history the log showing blank UID labels when UID tags programed in the scanner in UID search I run search all the time because you never know when new UID's will pop up.

Another tip is to put the UID number at the beginning of a UID alpha tag

 

[radio]

Why only 500 TGIDs and UIDs per system?

I wonder why Uniden chose system max of 500 TGIDs including UIDs per system?

I have already had to separate CSFD and El Paso CO FDs into 2 systems. El Paso FD is almost up to the 500 limit already.

Once I have figured out CSPD and the EPSO and CSP, they will have to be in 2 separate systems as well.

 

[marksmith]

I wonder why Uniden chose system max of 500 TGIDs including UIDs per system?

I have already had to separate CSFD and El Paso CO FDs into 2 systems. El Paso FD is almost up to the 500 limit already.

Once I have figured out CSPD and the EPSO and CSP, they will have to be in 2 separate systems as well.

Not even sure if the XT series supported UID when introduced. I think it was a fire update that allowed identifying UID text labels etc. I think the system with a max of 500 items (total frequencies, talkgroup id's and UID's) had already been defined.

Not certain of this, but my memory is that UID'S came along in this era.

Everything after the XT series is unlimited in items per system.

Mark
536/996P2/HP1e/HP2e/996XT/
396XT/PSR800/PRO668/PRO652

 

[marksmith]

Read firmware update for "fire" update in previous. The auto spellchecker program got me again.

Mark
536/996P2/HP1e/HP2e/996XT/
396XT/PSR800/PRO668/PRO652

 

[Voyager]

I wonder why Uniden chose system max of 500 TGIDs including UIDs per system?

I have already had to separate CSFD and El Paso CO FDs into 2 systems. El Paso FD is almost up to the 500 limit already.

Once I have figured out CSPD and the EPSO and CSP, they will have to be in 2 separate systems as well.

Uniden didn't really 'choose' the limit as I understand it. I think it was a memory allocation issue. And the XT i'm pretty sure had UIDs from the start.

The newer high end scanners are designed to handle larger TRSs better in many ways.

 

[ofd8001]

Mark is correct. Support for Unit IDs came after the XT scanner was introduced. I believe it was the 1.08.14 firmware update.

I suspect the size limitation is due to the ability of the processors to perform certain functions. Just like how scanners went from 100 channels to 500, to 1,000 then on to just about unlimited.

 

[marksmith]

When the XT series came out, the limit of 500 for frequencies and talkgroups was way more than adequate. There were no systems that big.

Then the firmware update produced the ability to assign text tags to UID's. Unit ID'S may have existed, but no text tags when the xt's came out. Once you could tag the UID'S with a text description, the 500 limit all of a sudden became very small. Since the radio system already had the system total size limit of 500 items, it was what it was.

By the way... the brand new 996p2 and 325p2, because they rely on the XT system, also continue to have this limitation. The HP 1&2, and x36 radios are unlimited with dynamic memory for each system. They are basically limited by what you can fit on an SD card.

Mark
536/996P2/HP1e/HP2e/996XT/
396XT/PSR800/PRO668/PRO652