Whiteman P25 system in, M36 system out?

[wbloss]

Today with the UHF band up I again heard a P25 Control channel on 460.1125, SYS ID 157 (Air Force in other states), Site NAC 150, R(FSS) of 02 and S(ite) of 40. In the Air Force system United States Air Force (157) Trunking System, Various, Multi-State - Scanner Frequencies there is not a RFSS of 2 showing, but I think this is Whiteman. Reason: Unitrunker shows 4 freqs in the system: 406.1125, 406.15, 406.5, 408.15; which are the same freqs used by the Whiteman system in the database from the M36 system with Sysid of B310, which I have not seen in a while.

Can someone close to Whiteman ID this and verify the M36 system is gone?
Monitoring over an hour Friday morning showed NO activity, with a 70-85% signal on the control channel.

I'm seeing this from Joplin, saw before in November on a band opening. Who is near Whiteman that can verify?

Wally

 

[CqDx]

I think you meant 406.1125 MHz

Yes Whiteman AFB is part of a larger system upgrade. You can find the RFP details here:

https://www.fbo.gov/utils/view?id=a3713649ab76f0437c0eace31fc70917

 

[wbloss]

I think you meant 406.1125 MHz

Yes Whiteman AFB is part of a larger system upgrade. You can find the RFP details here:

https://www.fbo.gov/utils/view?id=a3713649ab76f0437c0eace31fc70917

YES TYPO ALERT s/b 406.1125 not as I typed. Sorry, Good find. Are you local to the area?
W

 

[CqDx]

Sorry but I live quite far away from Whiteman AFB.

 

[wbloss]

M36 at Whiteman active - new control channe

Today during some tropo enhancement to the north, I realized both the old M36 TRS and the new P25 system control channels are in use at Whiteman AFB in Johnson Co MO - about 150 miles from Joplin where I am..

On 408.15 the M36 buzz showed SID of B310. This system used to have 406.1125 as the M36 cc, but this 406.1125 is now is the control for the new P25 system 157 RFSS2 Site 40 at Whiteman - tho there are no affiliations or TG's showing up on the P25, just the lonely P25 control buzz.
.
Clearly, the M36 system has moved its cc to 408.15 and is fairly active with TG's show including 80, 112, 768, 832, 848, and 2096 and a dozen RIDs.

I cannot remember or dig up the channel plan to make Unitrunker work fully, so I can't deduce the frequencies from the LCNs, but 408.150MHz is channel 543, and the other LCNs are: 3, 31, 142, 147, 212, 383, 411, 495(yellow for alt cc), 522, 527, and 592.

Interesting, both systems at the Base, but the old M36 is what is working with a new cc, and the new whiz-bang P25 is just chugging on the cc with no affiliations.

Wally

 

[talkpair]

I threw a spreadsheet together to show the relationships between the LCN's in your list against frequencies in the database.

Cells with a green background I'm pretty confident about. Cells in yellow need verification.

 

[talkpair]

Unfortunately, I'm not near enough to monitor this system.

Another interesting thing I noticed is that if you add "380" to the LCN's you identified below LCN 380, the results match LCN's identified above 380.

LCN 3 + 380 = LCN 383
LCN 31 + 380 = LCN 411
LCN 142 + 380 = LCN 522

......etc

It makes me wonder now if certain talk groups use LCN's 0-379, while others use 380 and above ?

Can a smartzone system be configured to set up a simplex call ?
Seems like it would be technically possible......Simply shut the repeater channel's TX off for the duration and steer the listening talk group to the mobile input frequency.

....or steer the group to a channel's repeater output frequency.

 

[SCPD]

If someone sends me a *decode* log, I may be able to make some sense of the channel numbers.

UniTrunker | Log Files

 

[wbloss]

If someone sends me a *decode* log, I may be able to make some sense of the channel numbers.

UniTrunker | Log Files

GREAT offer from the author! This was received during some tropo enhancement ~150 miles from me. I see that I have checked logging on the receiver, what would a decode log filename look like? i have one like "Tuner-20130805.LOG" and also "Tuner-20160804.log.z"

W

 

[talkpair]

This appears to be the band plan. Not sure why they needed 2 entires in the plan.

If programming into your radio, the offset value should be the same as the low channel number in the radio's custom table.

Compared to the other day when I had a band opening, I'm getting very few LCN hits in the 0-379 range today.

About 85% of the traffic is encrypted.