UCAN Rebanding has started

[ww7y]

Looks like Promontory Point is done, new CC on 853.7000. Unitrunker IDs it as Site 6 but not decoding any freqs. I guess I need to put in the new bandplan. I will give it a try.
Steve

 

[ww7y]

OK, I'm lost. After putting in the bandplan, I show the following LCNs:

29 0.00000
449 0.00000
462 0.00000 (yellow)
514 0.00000
533 0.00000
547 0.00000 (red) Frequency needed!
1012 0.00000 (yellow)

I am seeing Talkgroup IDs on the voice channels, just no freq. info. HELP!

Steve

 

[qlajlu]

I don't know how to help you with the UniTrunker, but each of the frequencies should have dropped 15 MHz.

 

[ww7y]

OK, I'm lost. After putting in the bandplan, I show the following LCNs:

29 0.00000
449 0.00000
462 0.00000 (yellow)
514 0.00000
533 0.00000
547 0.00000 (red) Frequency needed!
1012 0.00000 (yellow)

I am seeing Talkgroup IDs on the voice channels, just no freq. info. HELP!

Steve

OK, figured it out. After you put in the custom bandplan, you have to go into the channels tab and delete each channel. As the program discovers the new LCNs, it updates the freqs. Found this in one of Unitrunkers posts for this thread. Now, if we could just get voice following to work, we would be good to go with Unitrunker.

Now seeing on Site 6 Promontory Point
LCN - Freq - Use
29 - 851.73750 - Voice
449 - 851.25000 - Voice
462 - 851.57500 - Alt. CC
514 - 852.87500 - Voice
533 - 853.35000 - Voice
547 - 853.70000 - CC

Steve

 

[qlajlu]

Yep! Each one is exactly 15 MHz lower than what they were before.

 

[theaton]

Rebanding

Thanks Steve. I updated Site 6 Promontory Point from your info.

-Tim

 

[qlajlu]

Question About Logan Peak - Site 014

Actually, I have a couple of questions. Well, okay, many questions.

QUESTION 1: If you go to the Db and click on Logan Peak, site 014, then click on the site's call sign (KNIV722) it brings up a map showing the tower(s) used for this site. This map shows three (3) towers and they are located in two other counties, Wasatch and Sanpete. In fact, Sanpete (Gunnison), Wasatch (Fruitland or Currant Creek), and Cache (Logan Peak) are listed as service areas for this site. How can that be?

These sites are separated by a whole bunch of miles and mountains and therefore cannot be a part of a simulcast or do I completely misunderstand how this works? Did all three of these sites get changed?

QUESTION 2: Except for what I listed above, all the sites that have so far been rebanded have only had one tower. How are they going to tackle the larger sites like Davis and Salt Lake Counties where there are multiple towers involved? Are they going to take one tower down expecting the load to be carried by the others, and then do another tower, and so on? What happens to the service area when half or more of the towers have been changed? The users' radios must automatically recognize the change without further intervention.

Or are they going to take down the WHOLE bloody county at one time? ...doubtful.

 

[Junior1970]

Judging by whats been rebanded from what still need to be done my guess is that UCAN will do all the IR sites first then do the Simocast sites last. That way Nelson can take the load when they take SL Simo down for rebanding. Same with UtCo, reband West Mountain and do UC Simo later. With Davis and Weber the IR sites will cover the load while their simo sites get done, etc.

Of course this is still a guess.

Anyone know if Lewis, Clayton, Parleys, Daniels & Current Creek have been rebanded yet. If not I guess I'll find out when I go up to Oakley next weekend.

 

[theaton]

Currant Creek rebanded, but Daniel's Canyon??

I traveled across the Uinta Basin over the weekend to do a mad dash up Mt. Emmons (notice all the new conventional additions!). I wasn't set up to monitor trunked frequencies, but I scanned the 800 MHz band a few times through Daniels Canyon to see what control channels were active. I picked up the rebanded Strawberry and Teat sites (already updated in the DB) plus Ctrl on 852.250. This matches Currant Creek -15 MHz, so Currant Creek is rebanded.

But I heard nothing that corresponds to the Daniels Canyon site (rebanded or otherwise). I wonder what's going on there?

-Tim

 

[qlajlu]

But what is the deal with UCAN site 014 (Logan Peak) showing three towers in the Db when two of those towers are not in a position to be of any use to the Cache area? That has me perplexed.

 

[theaton]

But what is the deal with UCAN site 014 (Logan Peak) showing three towers in the Db when two of those towers are not in a position to be of any use to the Cache area? That has me perplexed.

You expect FCC licenses to be logical??? Half the time they are and half the time they're not. That's why they're useless without field checking.

-Tim

 

[qlajlu]

You expect FCC licenses to be logical??? Half the time they are and half the time they're not. That's why they're useless without field checking.

-Tim

Ya know, Tim, that makes more sense than you think! :lol:

 

[bneilson]

OK, figured it out. After you put in the custom bandplan, you have to go into ...

In the Alpha 2 version of Unitrunker you can change to "Rebanded" under the Options Tab and under Motorola.

Of course this will only be of value if you only listen to rebanded sites.

 

[ww7y]

In the Alpha 2 version of Unitrunker you can change to "Rebanded" under the Options Tab and under Motorola.

Of course this will only be of value if you only listen to rebanded sites.

I tried that Brett, but didn't seem to make any difference, and didn't appear to load a new bandplan. Seems you have to do things in Unitrunker in the correct sequence and in certain states when the changes are made. Possibily didn't do it "right". Is that how you got your bandplan in?

 

[bneilson]

I had never change it from the default plan.

Now that you had mentioned this I put in the following table in and deleted the channels like you identified:

[U]Lo Chan[/U] [u]Hi Chan[/u]   [u]Offset[/u]    [u]Base Freq[/u]     [u]Step[/u]
0          439      0       851.012500   25.000
440        559      440     851.025000   25.000
560        719      560     865.012500   25.000
720        759      720     866.000000   25.000
815        831      815     867.000000   25.000
958        958      958     868.975000   25.000
961        1022     961     867.425000   25.000

 

[KT7L]

Lewis Peak CC is now on 852.9120

I'll have to reset my tables in UniTrunker to see the audio channels tomarrow...

 

[Junior1970]

Lewis Peak CC is now on 852.9120

I'll have to reset my tables in UniTrunker to see the audio channels tomarrow...

That is good to know! Lewis is an important site for it covers the I-80 corridor from east of Park City to Echo. Also it helps me in my Oakley plans next weekend. Thanks.

 

[kd7rto]

OK, figured it out. After you put in the custom bandplan, you have to go into the channels tab and delete each channel. As the program discovers the new LCNs, it updates the freqs. Found this in one of Unitrunkers posts for this thread. Now, if we could just get voice following to work, we would be good to go with Unitrunker.

Now seeing on Site 6 Promontory Point
LCN - Freq - Use
29 - 851.73750 - Voice
449 - 851.25000 - Voice
462 - 851.57500 - Alt. CC
514 - 852.87500 - Voice
533 - 853.35000 - Voice
547 - 853.70000 - CC

Steve

It looks like if the LCN is < 440 (hex 0x1B8), it's the same as before. > 339, this formula seems to work:

frequency = ((LCN - 440) * .025) + 851.025

For trunker, all you have to do is change PLAN=8 to PLAN=0, edit the frequencies where LCN > 339, and you're all set. That was a lot easier than figuring out sys 6227 (Federal 406 MHz). My biggest question about rebanding has been answered.

My 7202C6.TXT file from today:

Promontory
MAP=222?2???
OPTIONS=nVDf
PLAN=0
DESCR=Type II NetWkd 138.46 Hz
THRESHOLD=50
DISPOSITION=ebfulxnbsr
v851.7375,1d,ffff,36a8
v851.2500,1c1,ffff,3889
av851.5750,1ce,ffff,ca
v852.8750,202,ffff,400
v853.3500,215,ffff,379c
d 853.7000,223,ffff,0

 

[KT7L]

Lewis Pk and UT Alpha 2

I had never change it from the default plan.

Now that you had mentioned this I put in the following table in and deleted the channels like you identified:

[U]Lo Chan[/U] [u]Hi Chan[/u]   [u]Offset[/u]    [u]Base Freq[/u]     [u]Step[/u]
0          439      0       851.012500   25.000
440        559      440     851.025000   25.000
560        719      560     865.012500   25.000
720        759      720     866.000000   25.000
815        831      815     867.000000   25.000
958        958      958     868.975000   25.000
961        1022     961     867.425000   25.000

Ok, I did this table in the Alpha 2 Band Plan (though I don't see a column for 'offset'), then I set the MOT system to 'Reband' in Options. I am monitoring Site 22 -- Lewis Peak on the CC of 852.9120

This is the Channel Plan that I get:

LCN Frequency Control?

52 852.3125
85 853.1375
95 853.3875
503 852.6000
528 853.2250 YES

Ok, why doesn't the 'real' CC show up in the table? This looks a little out of wack, though I am receiving the normal amount of traffic over the audio channels....

EDIT:

UT Alpha Crashed... I restarted it, and it's back to the original 'band plan'... NOW, the proper CC shows up in the Channels List:

LCN FREQUENCY CONTROL

52 852.3150
76 852.9125 YES
85 853.1375
95 867.3125
503 863.5875
528 864.2125 YES -- Pre Reband

I take it that w/o the new bandplan, UT shows the wrong audio frequencies -- Now to figure out why it didn't get saved when I updated it.

 

[gadgetmikey]

Are you getting a pretty high decode value.

852.9120 is not valid; it is is either channel number 75 at 852.8875 or channel number 76 at 852.9125. I wonder if your just above or below making the scanner feed not clear enoght for a good decode.