DOJ IWN Washington DC changing all WACN/Sys_ID/Site numbers

Status
Not open for further replies.

dlwtrunked

Member
Premium Subscriber
Joined
Dec 19, 2002
Messages
2,128
DOJ IWN changes (these are tentative--other later when I get time to sort through). Note that peers ("neighbors") are no longer transmitted.
Format: WACN.Sys_ID-Site.SubSite (NAC)
BF58A.010-9.1 (010) -> BEE0A.715-1.84 (717)
BF58A.010-3.1 (010) -> BEE0A.715-1.85 (717)
BF58A.010-12.1 (010) -> BEE0A.715-1.86 (717)
BF58A.010-7.1 (011) -> BEE0A.715-1.89 (717)
BF58A.010-14.1 (011) -> BEE0A.715-1.90 (717)
BF58A.010-2.1 (010) -> BEE0A.715-1.92 (712-not 717)
BF58A.010-13.1 (010) -> BEE0A.715-1.94 (717)
BF58A.010-6.1 (010) -> BEE0A.715-1.98 (717)
 

radiojoedc

Member
Premium Subscriber
Joined
Feb 4, 2019
Messages
14
Location
Fairfax County, VA
I stumbled across BEE0A.715-1.98 just now on 168.2625MHz. No activity at all, but the neighbor list shows:
BEE0A.715-1.84: 172.2125MHz
BEE0A.715-1.86: 172.6375MHz
BEE0A.715-1.87: 171.4375MHz
BEE0A.715-1.88: 171.5375MHz
BEE0A.715-1.89: 170.7250MHz
BEE0A.715-1.90: 173.9000MHz

I tried all those frequencies, and the only other one that I seemed to be able to receive was 1.90. No activity on that site either, but the neighbor list showed the 1.86, 1.87, 1.98 sites, but also the following sites none of which I was able to receive:

BEE0A.715-1.91 - 171.2750MHz
BEE0A.715-1.93 - 173.7250MHz

EDIT: Also, on the 1.98 site the only channels were 168.2625MHz for the CC and a secondary control channel of 168.8250MHz. The 1.90 site had three channels, 173.9000MHz CC, 170.6375MHz scc and 170.8625MHz scc.
 
Last edited:
Status
Not open for further replies.
Top