[Scan-DC] SOTU and the new USCPD trunked system

[Alan Henney]

On Monday, I started running Pro96Com on the new US Capitol PD trunked system through to this morning after the SOTU.  The system has not been busy considering the big event.

Here is some data produced by Pro96Com.  It matches what was shown in the original Navy document with these two exceptions:

162.25 should be the input for 169.575.  For some reason, Pro96Com still shows the default of 136.0.

Also, 165.0375 is reported as the input to 172.6875, not 165.0875, which I believe came from the Navy document.

SystemID=1410
SystemIDHEX=582
WACN=BEE00

Frequency(/Slot)        Input Frequency(/Slot)        Hit Count
172.6875        165.0875        193
172.3875        164.8125        184
172.9625        165.5375        183
173.1625        165.7750        12 (alternate control)
173.8125        166.4250        79 (alternate control)
170.1375        162.8000        199
169.5750        136.0000        191
173.4750        166.2250        42 (alternate control)
169.8375        162.6125        189
170.3750        163.1625        202
171.7875        164.6125        212
171.4125        164.3250        199
171.0000        164.0125        171
170.5750        163.6000        0 (primary control)

Talkgroups are numbered 2 through 52 but do not appear to simulcast the analog system.  All encryption noted so far but a couple talkgroups logged suggest they are not encrypted (I can hope?).

Can anybody explain how several of the analog freqs -- both inputs and especially outputs -- can be used simultaneously by the trunked system?

Any clue how the USCPD will accommodate seamless interoperability?  Will the primary talkgroups have a fixed encryption key (like MPD does) or will the entire system be OTAR?

I have the Pro96Com log files if anybody wants them.

Here is a related article from Roll Call:

http://www.rollcall.com/news/capitol_police_begin_testing_long_delayed_radio_upgrade-228775-1.html


Alan