BCD436HP/BCD536HP: Unsupported Patch Type?

[troymail]

How about Uniden just fix it?

...always a good option!

:lol:

 

[DaveNF2G]

No. ID Search/Scan only affects the way the scanner handles talkgroups that are not programmed. Scan ignores all traffic with unprogrammed talkgroup IDs. Search plays all traffic with unprogrammed talkgroup IDs.

Programmed talkgroups are not affected either way--the decision to play or ignore a transmission is determined by Location Control, active Service Type selections, and Avoids, regardless of whether ID Search or ID scan is selected.

I don't know why you prefaced your description of what I said with "no".

I use ID Search on the systems that are still being built in my area constantly. All talkgroups, known (programmed) and unknown are monitored.

 

[jonwienke]

I don't know why you prefaced your description of what I said with "no".

Because saying "ID Search hits on every talkgroup it detects" is not correct. ID Search only hits on talkgroups that are not programmed. Programmed talkgroups are handled according to how they are programmed, regardless of the ID Search/Scan setting.

 

[ScannerSK]

If there is a patch between talkgroup X and talkgroup Y, You can hear the patch traffic by monitoring talkgroup X or talkgroup Y. You just can't monitor the patch itself. Try using ID SEARCH instead of ID SCAN.

I tested this on the large 2,600 talkgroup Colorado DTRS P25 phase 1 system using a BCD436HP and it does not work. If I am monitoring one CSP talkgroup (A) and they patch into another CSP talkgroup (B) which is not enabled and which I am not interested in monitoring on a regular basis, then I cease to receive all traffic on talkgroup A.

I also tested this on the Weld County, Colorado FRCC P25 phase 2 system using a BCD436HP and it does not work either. Our dispatch office often patches three police clearance channels together (county {A}, sheriff North {B} and sheriff South {C}). This is clearly seen in the Pro96Com software where B is shown as patched into A and also C is shown as patched into A. The only way to monitor traffic on B or C in a Uniden BCD436HP is if A is enabled. However, on the GRE scanners, a person can have just one of any A or B or C enabled and all the traffic patched together is received. I verified this with a BCD436HP and a PSR-600 running side by side. Avoid A on the Uniden and no further traffic is heard even though B and C are enabled and not avoided. However, temporarily lock out A on the GRE scanner and traffic is still heard from B and C.

Uniden just needs to fix this plain and simple or they are going to fall by the way side sooner or later when a better company comes along that listens to its consumers.

Shawn

 

[DaveNF2G]

Because saying "ID Search hits on every talkgroup it detects" is not correct. ID Search only hits on talkgroups that are not programmed. Programmed talkgroups are handled according to how they are programmed, regardless of the ID Search/Scan setting.

I think it is a distinction without a difference. When searching, every talkgroup on the system is received regardless of programming. The display will show whatever labels are programmed, or just the ID if the group is not programmed.

 

[Thunderknight]

You probably would like that as a patch are only set up when something big has happened, that you do not want to miss.

That’s not true in all systems. A system here patches the dispatch group to the individual station’s alert talk group every fire call.

 

[cellphone]

One of the bullets in today’s firmware update for Uniden BCDx36HP radios is:

* Supports Motorola and Harris P25 Patch ID

I probably won’t be able to test for a couple of days. Does this solve our talkgroup patch issues?

 

[ScannerSK]

One of the bullets in today’s firmware update for Uniden BCDx36HP radios is:

* Supports Motorola and Harris P25 Patch ID

I probably won’t be able to test for a couple of days. Does this solve our talkgroup patch issues?

I can verify the new firmware completely solves the patching (superpatch) issue on my end. With the 1.14.00 firmware, having any one of the talkgroups which are patched together enabled will now allow reception of the patched traffic.

Thank you Uniden!

Shawn

 

[scannerhead]

Woohoo! Had actually given up on this ever being added. Happy day!

Thanks UPMan/Uniden!

 

[scan-pa]

it also works great on EDACS Multi-Cast patches.

 

[ScannerSK]

I can verify the new firmware completely solves the patching (superpatch) issue on my end. With the 1.14.00 firmware, having any one of the talkgroups which are patched together enabled will now allow reception of the patched traffic.

Thank you Uniden!

Shawn

I wonder what the chances are of this issue being fixed in the BCD396XT?

Shawn

 

[pinballwiz86]

I wonder what the chances are of this issue being fixed in the BCD396XT?

Shawn

I wouldn't mind a firmware update! The 396XT is still my go-to.