Uh Oh....lol
NYPD encryption technical thread
- Thread starter Hbright
- Start date
People just can't refrain from the peanut gallery comments. WTF.
@RadioDitch mentioned in the other clown-show thread that there was a specific order in which the PCTs were being changed. Something strictly geographic.
@n2nov Positive those are PBSI-1 and PBQN-1 and not PBSI-4 and PBQN North 4 Charles? I know your word is gold, just I have something different.
n2nov
Active Member
No, not "gold". I am just reporting what I was given off of a list last year and matched up to the callsigns and FCC indicated locations. Now we wait for the final verification upon use. We should be "radio detectives".
No, not "gold". I am just reporting what I was given off of a list last year and matched up to the callsigns and FCC indicated locations. Now we wait for the final verification upon use. We should be "radio detectives".
Well, I hold your word in high regard. Once the automated transmission starts playing we'll know for sure.
Is anyone logging radio id's on any of these enc freqs?
Or key IDs and AlgIds? Assume they'd all be the same, but if not that might be a good indicator of who is on what Freq/TG.
n2nov
Active Member
The new Patrol Boro frequencies are laid out by their respective areas. The frequency, callsign and area simulcast sites have been matched up to the FCC records. The following list (without the P25 NAC) is from a list given to me last year (see my November posting).
Remember:
PBMS - 1, 5, 7, 6, 9, 10, 13, MTS14, 17, MTN18
PBMN - 19, 20, CP22, 23, 24, 25, 26, 28, 30, 32, 33, 34
PBBX - 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 52
PBBS - 60, 61, 62, 63, 66, 67, 68, 69, 70, 71, 72, 76, 78
PBBN - 73, 75, 77, 79, 81, 83, 84, 88, 90, 94
PBQS - 100, 101, 102, 103, 105, 106, 107, 113
PBQN - 104, 108, 109, 110, 111, 112, 114, 115
PBSI - 120, 121, 122 123
484.1875 PBMS 1 WIM673
483.3125 PBMS 2 WIM662
483.8125 PBMS 3 WIM665
482.9125 PBMN 4 WIM638
484.4125 PBMN 5 WIM674
483.4375 PBMN 6 WIM630
483.1625 PBBX 1 WIM646
484.1625 PBBX 2 WIM672
484.6625 PBBX 3 WIM675
483.0875 PBBS 1 WIM491
483.5875 PBBS 2 WIM499
483.8375 PBBS 3 WIM503
483.5625 PBBN 4 WIM663
484.0625 PBBN 5 WIM666
484.3125 PBBN 6 WIM667
483.6625 PBQS 1 WIM650
483.1875 PBQS 2 WIM626
483.4125 PBQS 3 WIM642
482.9375 PBQN 4 WIM622
483.6875 PBQN 5 WIM670
483.9375 PBQN 6 WIM671
484.0875 PBSI 1 WIM634
484.3375 PBSI 2 WIM564
Submitted.
Admins say they might want to wait to add everything until they're all active and NAC's have been captured. Which is logical and makes perfect sense. Maybe I should have waited. So gents...time to scan and log!
Oh so I thought they would complete the transition with one borough (brooklyn) then move onto to the next. But it looks like every borough has their own dedicated radio tech team that will transition simultaneously from what's being said here.
I put them into SDRTrunk for a little bit of time (obviously not the right way but I can’t get DSDPlus to work) and I got a few in the 48### and 18### range on PBBN4 and PBBN6 but that was it
Unitrunker for the win... (shrug)
Go with Unitrunker. It has by far the best logging capabilities out there.
Unitrunker only supports trunking, not conventional P25. No control channel = no decoding/logging.
SDRTrunk is the way to go, as it not only supports conventional P25, but will also display any RID/TGID/NAC/KeyID/Algo in use.
EDIT: If someone wants to correct me and tell me that it's possible to create a voice VFO in UT to capture conventional P25, then I'll have learned something new today lol
SDRTrunk is the way to go, as it not only supports conventional P25, but will also display any RID/TGID/NAC/KeyID/Algo in use.
EDIT: If someone wants to correct me and tell me that it's possible to create a voice VFO in UT to capture conventional P25, then I'll have learned something new today lol
All entered. For those observing, please submit the missing NAC when they go online. Thanks.Admins say they might want to wait to add everything until they're all active and NAC's have been captured. Which is logical and makes perfect sense. Maybe I should have waited. So gents...time to scan and log!
Nope. You're right. I'm just that exhausted and my brain short circuited there for a minute. Long week.