DSD+ shows another callsign- KEH-307
NYPD Trunk?
- Thread starter GraniteScanner
- Start date
coolrich55
Member
NYPD trunk system? WOW
richee2000
Communications Professional
Now picking up the control channel 471.2375 in sea bright New Jersey, very weak signal. No activity.
Last edited:
- Joined
- Dec 22, 2005
- Messages
- 1,915
What catches my eye is frequency range diversity. Note the thoughtful effort to choose frequencies over a range for CC’s. This clearly anticipates band openings.
That is a good start.
That is a good start.
| 453.250 | 453.625c | 471.2375c | 472.6125 | 483.0625c | 484.8125 |
Those 453 Mhz. freqs are going to cause me problems from my location. Multiple users in Ct.. and LI on those freqs will cause havoc on me hearing the NYC system. But that's my problem, not theirs.....
richee2000
Communications Professional
We don't even know what this system is going to be for. We don't know if it's in the clear or encrypted, eventually.... So many unanswered questions right now....
That license does list 453.2500, and 2 others. One also licensed to WIM507 Tac V Comm/Fleet Services. The other did not pop.
So true, this is a huge jump from what's deployed currently.
coolrich55
Member
To say it won't be encrypted in the end is laughable. But we shall see...
richee2000
Communications Professional
has anyone heard any activity on this system today?
only 2 hits since last night, both on the Transit CW TG 405. It was dispatcher only patch. No mobile reply was patched.
richee2000
Communications Professional
Thanks for the info.
Three more new TG's
132
136 RID 330007
101 with 100 . Never seen it like this before with 2 talkgroups together
And 100 came up a couple more times and it had 100 with it.
Anyone know why there are two talkgroups on the same entry?
132
136 RID 330007
101 with 100 . Never seen it like this before with 2 talkgroups together
And 100 came up a couple more times and it had 100 with it.
Anyone know why there are two talkgroups on the same entry?
According to DSD+, there have been a lot more hits since then. (Which I saw in your other post). My monitoring location has a pretty good reception of citywide and special unit channels. So im trying to listen to both side by side to compare activity.
Yes, 100 and 101 were patched together for some time yesterday and today. This is what I have in my logs from this morning.
2024/07/31 08:39:36 Freq=471.237500 NAC=6C1 Patch Supergroup: TG=100
2024/07/31 08:39:36 Freq=471.237500 NAC=6C1 Patch Subgroup: TG=101
2024/07/31 08:45:14 Freq=471.237500 NAC=6C1 P-Group call; TG=100 Src=EXTERNAL Ch=484.8125-1 Pri0 1s
2024/07/31 08:45:14 Freq=484.812500 NAC=6C1 P-Group call; TG=100 Pri0 9s
2024/07/31 08:45:22 Freq=471.237500 NAC=6C1 P-Group call; TG=100 Ch=484.8125-1 Pri0
2024/07/31 08:45:23 Freq=484.812500 NAC=6C1 P-Group call; TG=100 Pri0 1s
2024/07/31 08:49:33 Freq=471.237500 NAC=6C1 P-Group call; TG=100 Src=EXTERNAL Ch=453.25-2 Pri0 10s
2024/07/31 08:49:56 Freq=471.237500 NAC=6C1 P-Group call; TG=100 Src=EXTERNAL Ch=484.8125-2 Pri0 2s
2024/07/31 08:49:56 Freq=484.812500 NAC=6C1 P-Group call; TG=100 Pri0 3s
2024/07/31 08:50:47 Freq=471.237500 NAC=6C1 P-Group call; TG=100 Src=EXTERNAL Ch=453.25-1 Pri0 1s
2024/07/31 08:50:53 Freq=471.237500 NAC=6C1 P-Group call; TG=100 Src=EXTERNAL Ch=484.8125-1 Pri0 7s
2024/07/31 08:50:53 Freq=484.812500 NAC=6C1 P-Group call; TG=100 Pri0 9s
2024/07/31 08:51:10 Freq=471.237500 NAC=6C1 P-Group call; TG=100 Src=EXTERNAL Ch=453.25-2 Pri0 3s
2024/07/31 08:51:22 Freq=471.237500 NAC=6C1 P-Group call; TG=100 Src=EXTERNAL Ch=484.8125-2 Pri0 1s
2024/07/31 08:51:23 Freq=484.812500 NAC=6C1 P-Group call; TG=100 Pri0 1s
2024/07/31 08:51:29 Freq=471.237500 NAC=6C1 P-Group call; TG=100 Src=EXTERNAL Ch=453.25-1 Pri0 1s
2024/07/31 08:51:34 Freq=471.237500 NAC=6C1 P-Group call; TG=100 Ch=453.25-1 Pri0
2024/07/31 08:51:38 Freq=471.237500 NAC=6C1 P-Group call; TG=100 Src=EXTERNAL Ch=484.8125-1 Pri0 1s
2024/07/31 08:51:39 Freq=484.812500 NAC=6C1 P-Group call; TG=100 Pri0 1s
2024/07/31 08:53:30 Freq=471.237500 NAC=6C1 P-Group call; TG=100 Src=EXTERNAL Ch=453.25-2 Pri0 2s
2024/07/31 08:54:25 Freq=471.237500 NAC=6C1 P-Group call; TG=100 Src=EXTERNAL Ch=484.8125-2 Pri0 1s
2024/07/31 08:54:25 Freq=484.812500 NAC=6C1 P-Group call; TG=100 Pri0 3s
2024/07/31 08:54:28 Freq=471.237500 NAC=6C1 P-Group call; TG=100 Src=EXTERNAL Ch=484.8125-2 Pri0 1s
2024/07/31 08:54:29 Freq=484.812500 NAC=6C1 P-Group call; TG=100 Pri0 2s
2024/07/31 08:54:32 Freq=471.237500 NAC=6C1 P-Group call; TG=100 Src=EXTERNAL Ch=453.25-1 Pri0 4s
2024/07/31 08:57:08 Freq=471.237500 NAC=6C1 Deregistration; RID=19100
2024/07/31 08:58:10 Freq=471.237500 NAC=6C1 Patch subgroup timeout: TG=101
2024/07/31 08:58:10 Freq=471.237500 NAC=6C1 Patch timeout: TG=100
I don't understand all the licenses in this system; they are not really licensed correctly, so I've learned to ignore them.
richee2000
Communications Professional
Just picked up talk group 104 with a brief transmission
tg 104 is MTS/17/MTN Precinct
richee2000
Communications Professional
Interesting. So this trunking system is not just for citywide. The purpose of this system is a real mystery.
In addition to my earlier post above, TG 100 or 101 sounds like MTN 1/5/7 Precints. But don't quote me on that.
It could be either TG because al i got were patches and on Moto systems when a patch call takes place it takes place on both TGs at the same time
Last edited:
Has anyone looked over the associated licenses to see if there are any other freqs (not used on 2.1) that may be part of a different site?
That didn't take long. Encr has started already.
See the yellow arrows up top.
See the yellow arrows up top.
