RadioReference on Facebook   RadioReference on Twitter   RadioReference Blog
 

Go Back   The RadioReference.com Forums > Scanners, Receivers and Related Equipment Forums > Uniden Forums > Uniden Tech Support


Uniden Tech Support - For discussion of all technical aspects of current or future Uniden scanners.

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 03-04-2018, 1:44 PM
DaveNF2G's Avatar
Member
  Premium Subscriber
Premium Subscriber
Amateur Radio Operator
Amateur Radio
 
Join Date: Jan 2001
Location: Rensselaer, NY
Posts: 8,905
Default Unsupported Patch Type?

A local agency on a P25 trunked system is using a group ID that shows as "Patch" in DSDPlus and is not received by my 436. Checking the agency's regular talkgroups while this Patch is in use reveals no traffic anywhere. It seems to stand alone.

In the DSDPlus log, transmissions show up starting like this:

P-Group call; TG=121

It seems that the scanner does not recognize "P-Group" calls.
__________________
David T. Stark
NF2G WQMY980 KYR7128
ARRL VE & Registered Licensing Instructor
Reply With Quote
Sponsored links
  #2 (permalink)  
Old 03-04-2018, 2:11 PM
Spitfire8520's Avatar
Member
  Premium Subscriber
Premium Subscriber
 
Join Date: Jun 2009
Location: Colorado
Posts: 1,715
Default

None of Uniden's products has ever supported talkgroup patching on P25 systems. This missing feature (or issue) has known for a long time, but it appears that Uniden is not interested by their constant lack of response for the past decade. You can manually monitor the patched talkgroup by programming it directly.

April, 2009
Patched Talkgroups/Status Bit
April, 2010
Talkgroup Patch Feature
May, 2012
Talkgroup Patches on Motorola P25 systems
February, 2014
Uniden BCD536HP & Patched Talkgroups on Phase II System
April, 2015
P25 Patch Following
July, 2015
Uniden, please fix the P25 system patch issue
September, 2017
BCDx36HP P25 Patch Following...
__________________
Mile-High Spitfire
RadioShack Pro-106 RadioShack Pro-652 RTL-SDR Unication G5 Uniden BCD436HP (On Loan)
MNN-250
Reply With Quote
  #3 (permalink)  
Old 03-04-2018, 3:02 PM
jonwienke's Avatar
Member
   
Join Date: Jul 2014
Location: PA
Posts: 8,884
Default

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.
__________________
Gone camping.
Reply With Quote
  #4 (permalink)  
Old 03-04-2018, 4:01 PM
Spitfire8520's Avatar
Member
  Premium Subscriber
Premium Subscriber
 
Join Date: Jun 2009
Location: Colorado
Posts: 1,715
Default

Quote:
Originally Posted by jonwienke View Post
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.
That would depend on the system. For Motorola systems, the traffic will end up on either talkgroup X or talkgroup Y. For Harris systems, the traffic will end up on a completely different talkgroup Z (which is pulled from a large group of talkgroups) and monitoring talkgroup X & Y will not work.

For the OP case, monitoring TG 121 directly will let you hear the patched traffic. With Uniden scanners, anything short of monitoring the the "P-Group" directly will not work.
__________________
Mile-High Spitfire
RadioShack Pro-106 RadioShack Pro-652 RTL-SDR Unication G5 Uniden BCD436HP (On Loan)
MNN-250
Reply With Quote
  #5 (permalink)  
Old 03-05-2018, 4:57 AM
Member
   
Join Date: Sep 2006
Location: Stockholm, Sweden
Posts: 2,156
Default

If DSD shows a patched talk group then the talkgroups that have been patched are no longer in use and only the patched TG are used.
It would be a huge waste of resources if three talkgroups got activated when someone uses his PTT in any of the patched TG's.

/Ubbe
__________________
TRX-2 BCD536 HP1 BCT15 BC246 BC346 BR330 UBC3500 Pro2006 Pro2042 Optocom OS545 Scout PCR1000 ICR2500 IC75 DX394 AR8200 IC-R2 IC-R10 UBC780 MD380 CS580 CS750 Pro96 Perseus ADCR25 AcecoSC1plus RTL-SDR
Reply With Quote
Sponsored links
  #6 (permalink)  
Old 03-05-2018, 8:26 AM
Member
   
Join Date: Sep 2002
Location: Toronto, Ontario
Posts: 4,787
Default

Quote:
Originally Posted by Spitfire8520 View Post
None of Uniden's products has ever supported talkgroup patching on P25 systems.
Well, of course not. As Uniden's shill Voyager put it:

But, if they are using an arbitrary TGID for the supergroup, your only recourse is to use ID SEARCH. There is no practical way for a scanner to know you want to monitor a random TGID.


OMG, what horse manure. So, V-Ger, then how do GRE/Whistler manage to do it?
Reply With Quote
  #7 (permalink)  
Old 03-05-2018, 7:23 PM
DaveNF2G's Avatar
Member
  Premium Subscriber
Premium Subscriber
Amateur Radio Operator
Amateur Radio
 
Join Date: Jan 2001
Location: Rensselaer, NY
Posts: 8,905
Default

I was planning to add another Uniden 536 to my station, but if Uniden's scanners have a built-in disability with respect to monitoring a plain old P25 Phase I system P-Group, then maybe I should reconsider Whistler. (I just hate EZ-Scan, which is far from it.)
__________________
David T. Stark
NF2G WQMY980 KYR7128
ARRL VE & Registered Licensing Instructor
Reply With Quote
  #8 (permalink)  
Old 03-05-2018, 7:30 PM
jonwienke's Avatar
Member
   
Join Date: Jul 2014
Location: PA
Posts: 8,884
Default

Only on Harris P25 systems, and if you have ID Search turned off. Otherwise you will hear patched traffic.
__________________
Gone camping.
Reply With Quote
  #9 (permalink)  
Old 03-05-2018, 10:53 PM
cellphone's Avatar
Member
  RadioReference Database Admininstrator
Database Admin
Amateur Radio Operator
Amateur Radio
 
Join Date: Dec 2002
Location: Ahwatukee, AZ (Phoenix)
Posts: 1,424
Default

Quote:
Originally Posted by slicerwizard View Post
OMG, what horse manure. So, V-Ger, then how do GRE/Whistler manage to do it?

It is rumored that GRE/Whistler owns a patent for monitoring patches on a P25 system, but no one has cited a source.
Reply With Quote
  #10 (permalink)  
Old 03-06-2018, 12:15 AM
Member
   
Join Date: Sep 2002
Location: Toronto, Ontario
Posts: 4,787
Default

No source because that's more manure. It's not that hard to check their patents.

Besides, patch monitoring is quite straightforward - monitor the proprietary patch announcements and teardowns and tie the patch IDs to the patched groups. Simples and not particularly patentable.

Proprietary because even though patching is a known requirement for PS systems, the vendors, who had every opportunity to bake patches into the P25 standard, instead chose to go with incompatible solutions.

Same deal with DMR - no standard method for deploying encryption. Go figure.
Reply With Quote
  #11 (permalink)  
Old 03-06-2018, 10:18 AM
DaveNF2G's Avatar
Member
  Premium Subscriber
Premium Subscriber
Amateur Radio Operator
Amateur Radio
 
Join Date: Jan 2001
Location: Rensselaer, NY
Posts: 8,905
Default

Quote:
Originally Posted by jonwienke View Post
Only on Harris P25 systems, and if you have ID Search turned off. Otherwise you will hear patched traffic.
Hardly a solution on a large system with over 200 talkgroups.
__________________
David T. Stark
NF2G WQMY980 KYR7128
ARRL VE & Registered Licensing Instructor
Reply With Quote
  #12 (permalink)  
Old 03-06-2018, 10:44 AM
jonwienke's Avatar
Member
   
Join Date: Jul 2014
Location: PA
Posts: 8,884
Default

200 talkgroups is relatively small, compared to SIRN, MARCS, and other statewide or multistate systems.

You can program every known talkgroup in those systems with zero impact on performance, and ID Search only hits on new talkgroups and patches. It's not the most elegant solution, but it works.
__________________
Gone camping.
Reply With Quote
  #13 (permalink)  
Old 03-07-2018, 8:56 AM
DaveNF2G's Avatar
Member
  Premium Subscriber
Premium Subscriber
Amateur Radio Operator
Amateur Radio
 
Join Date: Jan 2001
Location: Rensselaer, NY
Posts: 8,905
Default

ID Search hits on every talkgroup it detects. If the TGID is programmed into the scanner with a label, then that label will be displayed.
__________________
David T. Stark
NF2G WQMY980 KYR7128
ARRL VE & Registered Licensing Instructor
Reply With Quote
  #14 (permalink)  
Old 03-07-2018, 9:29 AM
jonwienke's Avatar
Member
   
Join Date: Jul 2014
Location: PA
Posts: 8,884
Default

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.
__________________
Gone camping.
Reply With Quote
  #15 (permalink)  
Old 03-07-2018, 11:36 AM
troymail's Avatar
Silent Key
  Premium Subscriber
Premium Subscriber
 
Join Date: Dec 2002
Location: Supply (Lockwood Inlet area), NC
Posts: 9,977
Default

For ID Search to work properly, you must have all known talkgroups programmed against a given system with those not of interest locked out in some way. Otherwise, you'll get tons of false hits for "new/unknown" talkgroups.
__________________
Unication G5(UHF)
TRX-2,TRX-1,WS1098,1088x2,1095,1080, PSR1080,PSR500,PRO96
BCD536,436,396T,BC296D,245XLT,600XLT,IV,VX-8R,MD-390
Reply With Quote
  #16 (permalink)  
Old 03-07-2018, 11:52 AM
Member
   
Join Date: Sep 2002
Location: Toronto, Ontario
Posts: 4,787
Default

Quote:
Originally Posted by jonwienke View Post
You can program every known talkgroup in those systems with zero impact on performance, and ID Search only hits on new talkgroups and patches. It's not the most elegant solution, but it works.
That's great if you want to be bothered by every patch.
Reply With Quote
  #17 (permalink)  
Old 03-07-2018, 12:06 PM
jonwienke's Avatar
Member
   
Join Date: Jul 2014
Location: PA
Posts: 8,884
Default

Generally not an issue. The great majority of traffic is not patched. And if a patch pops up you aren't interested in, an avoid is a single button press away.
__________________
Gone camping.
Reply With Quote
  #18 (permalink)  
Old 03-07-2018, 1:58 PM
troymail's Avatar
Silent Key
  Premium Subscriber
Premium Subscriber
 
Join Date: Dec 2002
Location: Supply (Lockwood Inlet area), NC
Posts: 9,977
Default

If you are really sure you don't want to hear patches, you could always create a set of patch talkgroups using something like Excel, etc., cut and paste them into Sentinel and set them to Avoid..... It's probably just some specific range of TGIDs....
__________________
Unication G5(UHF)
TRX-2,TRX-1,WS1098,1088x2,1095,1080, PSR1080,PSR500,PRO96
BCD536,436,396T,BC296D,245XLT,600XLT,IV,VX-8R,MD-390
Reply With Quote
  #19 (permalink)  
Old 03-07-2018, 3:18 PM
MikeWazowski's Avatar
Forums Manager/Global DB Admin/Commie
  RadioReference Database Admininstrator
Database Admin
 
Join Date: Jun 2001
Location: Central Ontario
Posts: 10,256
Default

How about Uniden just fix it?
__________________
Mike.

Sorry but I don't accept PM's. Please use email instead.
Reply With Quote
  #20 (permalink)  
Old 03-07-2018, 3:23 PM
Member
   
Join Date: Sep 2006
Location: Stockholm, Sweden
Posts: 2,156
Default

Quote:
Originally Posted by slicerwizard View Post
That's great if you want to be bothered by every patch.
You probably would like that as a patch are only set up when something big has happened, that you do not want to miss.

/Ubbe
__________________
TRX-2 BCD536 HP1 BCT15 BC246 BC346 BR330 UBC3500 Pro2006 Pro2042 Optocom OS545 Scout PCR1000 ICR2500 IC75 DX394 AR8200 IC-R2 IC-R10 UBC780 MD380 CS580 CS750 Pro96 Perseus ADCR25 AcecoSC1plus RTL-SDR
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 12:37 AM.


Powered by vBulletin® Version 3.8.2
Copyright ©2000 - 2018, vBulletin Solutions, Inc.
All information here is Copyright 2012 by RadioReference.com LLC and Lindsay C. Blanton III.Ad Management by RedTyger
Copyright 2015 by RadioReference.com LLC Privacy Policy  |  Terms and Conditions