Sheppard AFB trunked system changed

[nd5y]

The Sheppard AFB trunked system has changed.
The voice channels 409.5625, 410.2375, and 410.6375 don't appear to be used any longer.
They seem to be replaced by 410.3625 and 410.7625
These two new channels seem to need a new frequency table.
The one listed in the DB (406.0, 12.5, 380) doesn't work for the new channels but works for the old ones, 406.3625, 407.7625, 408.1625 still work with the table listed in the DB
The the remaining channel 408.9625 is the control channel today so I'm not sure if it was affected.

 

[nd5y]

I figured it out
406.3625, 407.7625, 408.1625, 409.5625 require the 406.0 12.5 380 band plan
410.3625, 410.7625 require the 406.125 12.5 380 band plan
I can put up to 3 band plans in the 396 but it will not track this system properly with both band plans at the same time.

409.5625 appears to only be used for telephone interconnects.

 

[ericcarlson]

Those two frequency tables are contradictory. Does the new one perhaps replace the old one?

-Eric

 

[nd5y]

Does the new one perhaps replace the old one?

-Eric

Eric, I don't have the capability or running unitrunker up there so I don't know exactly what is going on but it looks to me like you need both tables, but my 396 won't work properly with both. I don't know if it is possible for a trunked system to require multiple tables. If not, then why does the 396 have a way to enter three of them? The only problem is the 396 only seems to work with one table at a time.

Like I said earlier, with the 406.0 12.5 380 table I can get everything but the two new channels. If I put in 406.125 12.5 0 it works with the two new channels but not the rest. If I use both tables it does the same thing, depending on what order I entered the tables.

I tried using all the common tables from some other 400 MHz trunked systems in the database and tried using the lowest frequency (406.3625) as a base frequency and nothing worked.

Then I noticed the two new voice channels 410.3625 and 410.7625 were both exactly .125 MHz higher than the old ones that don't appear to be used any more, and when those are in use the 396 frequency display tries to show the old frequencies, so I set the base freq to 406.125 instead of 406.0 and it worked for those two channels but not the rest.

Do you have any other ideas that I can try?

 

[ericcarlson]

We really need trunker data to figure this out, otherwise it's just a guessing game. The problem is that with both ranges having the same offset (380) what you've done is defined two possible frequencies for each channel number which does not make sense.

-Eric

 

[loumaag]

I have been away from the computer for several days and looking at what has been posted here the following should work:

Entry 1:
Base - 406.0000
Offset - 380
Spacing - 12.5

Entry 2:
Base - 410.0000
Offset - 690
Spacing - 12.5

Both of those will go into the tables without a conflict and satisfy the frequencies as posted above.

 

[DPS8504]

I have been away from the computer for several days and looking at what has been posted here the following should work:

Entry 1:
Base - 406.0000
Offset - 380
Spacing - 12.5

Entry 2:
Base - 410.0000
Offset - 690
Spacing - 12.5

Both of those will go into the tables without a conflict and satisfy the frequencies as posted above.

Lou,

I reprogrammed both my Pro96 and my Pro2096 with two different banks using your plan. On the new bank with it set up as:
Entry 2:
Base - 410.0000
Offset - 690
Spacing - 12.5
I am getting a log of activity, with several new talk groups and new frequencies, but no voice. I have the bank set up a MOT. Could some of these new talk groups be encrypted as to why I am not getting any voice on them?

 

[loumaag]

Lou,

I reprogrammed both my Pro96 and my Pro2096 with two different banks using your plan. On the new bank with it set up as:
Entry 2:
Base - 410.0000
Offset - 690
Spacing - 12.5
I am getting a log of activity, with several new talk groups and new frequencies, but no voice. I have the bank set up a MOT. Could some of these new talk groups be encrypted as to why I am not getting any voice on them?

Sorry for the delay in responding, been away from the computer for several days.

Well it is possible, but more likely that I screwed up the entry.
What you describe is exactly what would happen from a wrong entry.

Attached is the Excel spreadsheet that I used to develop the entry (zipped of course), take a look and see if you can spot what I did wrong.

 

[ericcarlson]

Assuming the 406.125/12.5/380 was on the right track and that we know all the frequencies, then Lou's suggested second table should work. Without trunker data this is a needle-in-a-haystack problem to solve though.

-Eric

 

[nd5y]

So if you use a base of 690, what happens if a voice channel is assigned that is lower than that? Does the scanner ignore it and look it up from the other table?

 

[ericcarlson]

The first table ends at channel 689 by inference due to the second table starting at 690. The two tables combined define the available channels: one covers 380-689 and the other 690-759.

-Eric

 

[DPS8504]

The first table ends at channel 689 by inference due to the second table starting at 690. The two tables combined define the available channels: one covers 380-689 and the other 690-759.

-Eric

Is ther some type of formular for figuring this out? I have two banks set up in both my 2096 and my 96. Using custom tables with 380 and the other as 690. I am seeing some new frequencies, new talk goups, but some times there is no voice on the channel. I have seen frequencies in the lower 380 table as high as 415.22500. And talk groups 12416, 18432 and others.

 

[dste]

I have two banks set up in both my 2096 and my 96. .

I think you probably want to put both tables into the same bank with something like WIN96. You seem to be saying that table 2's channels are running up table 1's VCs instead of changing over to table 2 for the high ones.

You can't enter it manually from the keypad.

 

[DPS8504]

I think you probably want to put both tables into the same bank with something like WIN96. You seem to be saying that table 2's channels are running up table 1's VCs instead of changing over to table 2 for the high ones.

You can't enter it manually from the keypad.

Well, I thought I new how to program with the Win96, but how do you do that???

 

[dste]

Well, I thought I new how to program with the Win96, but how do you do that???

Select "Moto 3600 CC" to "multi-table" and put both tables into "Extended Tables."

Good luck

 

[DPS8504]

Select "Moto 3600 CC" to "multi-table" and put both tables into "Extended Tables."

Good luck

Here is how I set up my multi tabel for the UHF system at Sheppard


CH Hi CH lo Base Freq Offset Step
380 689 460.000 380 12.5
690 758 410.00 380 12.5

I have noticed that it will track and display the talk groups, but there is no audio on anything above 410.000 Mhz. I am seeing a lot of activity on it and new talk groups along with the old talk groups, but can't figure out why there is no audio.

 

[dste]

Here is how I set up my multi tabel for the UHF system at Sheppard


CH Hi CH lo Base Freq Offset Step
380 689 460.000 380 12.5
690 758 410.00 380 12.5

IQUOTE]

Look at the 2nd offset. Should be 690?

 

[loumaag]

Here is how I set up my multi tabel for the UHF system at Sheppard


CH Hi CH lo Base Freq Offset Step
380 689 460.000 380 12.5
690 758 410.00 380 12.5

I have noticed that it will track and display the talk groups, but there is no audio on anything above 410.000 Mhz. I am seeing a lot of activity on it and new talk groups along with the old talk groups, but can't figure out why there is no audio.

As dste points out, the offset should be 690 for the second one.
Try this:

CH Hi       CH lo      Base Freq        Offset        Step
380          689         460.000           380           12.5
690          75[B]9[/B]         410.000           690           12.5

Note the 759 as fixing the second CH Lo also.

 

[SCPD]

Why are "Ch Hi" and "Ch Lo" backwards on most of these posts?

 

[loumaag]

Why are "Ch Hi" and "Ch Lo" backwards on most of these posts?

It's the new way to confuse the man, man!