Custom Tables

[camelcacher]

I am still getting long moments of silence my scanner will work great then out of the clear blue it stopes for about 3-5 mins with nothing, then starts working great again could it be the Trunking table or some thing else?

Here is what Trunking table I am using, is there another one out there that might work better
I have Slco. Utah Co, Tooele Co, Davis Co, Wasatch/Summitt in my TSYS

Sorry for the table but it doesn't seem to cut and paste right


LOW HIGH OFFSET FREQ STEP
0 439 0 851.0125 25
440 559 440 851.0250 25
560 719 560 865.0125 25
720 759 720 866.0000 25
815 831 815 867.0000 25
958 958 958 868.9750 25
61 1022 961 867.4250 25

 

[qlajlu]

The table you have posted is correct, however, I can find one problem but I think it might have to do with the copy/paste you did while making your post. Check the last line in your Trunking Tables to make sure. The first entry on the last line should be 961. The last line should be:

961 1022 961 867.425000 25.000

You posted:

LOW HIGH OFFSET FREQ STEP
0 439 0 851.0125 25
440 559 440 851.0250 25
560 719 560 865.0125 25
720 759 720 866.0000 25
815 831 815 867.0000 25
958 958 958 868.9750 25
61 1022 961 867.4250 25 - This line should read 961 1022 961 867.4250 25

If you do, in fact, have that line correct, then the issues you are experiencing are not due to the trunking table.

 

[Highpockets]

I am still getting long moments of silence my scanner will work great then out of the clear blue it stopes for about 3-5 mins with nothing, then starts working great again could it be the Trunking table or some thing else?

Here is what Trunking table I am using, is there another one out there that might work better
I have Slco. Utah Co, Tooele Co, Davis Co, Wasatch/Summitt in my TSYS

Sorry for the table but it doesn't seem to cut and paste right


LOW HIGH OFFSET FREQ STEP
0 439 0 851.0125 25
440 559 440 851.0250 25
560 719 560 865.0125 25
720 759 720 866.0000 25
815 831 815 867.0000 25
958 958 958 868.9750 25
61 1022 961 867.4250 25

Sounds like an antenna (receiving) problem to me.

 

[Highpockets]

I am still getting long moments of silence my scanner will work great then out of the clear blue it stopes for about 3-5 mins with nothing, then starts working great again could it be the Trunking table or some thing else?

Here is what Trunking table I am using, is there another one out there that might work better
I have Slco. Utah Co, Tooele Co, Davis Co, Wasatch/Summitt in my TSYS

Sorry for the table but it doesn't seem to cut and paste right


LOW HIGH OFFSET FREQ STEP
0 439 0 851.0125 25
440 559 440 851.0250 25
560 719 560 865.0125 25
720 759 720 866.0000 25
815 831 815 867.0000 25
958 958 958 868.9750 25
61 1022 961 867.4250 25

What's your multisite mode set to?

 

[camelcacher]

The table you have posted is correct, however, I can find one problem but I think it might have to do with the copy/paste you did while making your post. Check the last line in your Trunking Tables to make sure. The first entry on the last line should be 961. The last line should be:

961 1022 961 867.425000 25.000

You posted:

LOW HIGH OFFSET FREQ STEP
0 439 0 851.0125 25
440 559 440 851.0250 25
560 719 560 865.0125 25
720 759 720 866.0000 25
815 831 815 867.0000 25
958 958 958 868.9750 25
61 1022 961 867.4250 25 - This line should read 961 1022 961 867.4250 25

If you do, in fact, have that line correct, then the issues you are experiencing are not due to the trunking table.

Just a cut and paste problem I do have 961 in the low band
Thanks

 

[camelcacher]

What's your multisite mode set to?

My miltisite mode is set to Off should it be set to roam when driving?

 

[bneilson]

The table you have posted is correct, however, I can find one problem but I think it might have to do with the copy/paste you did while making your post. Check the last line in your Trunking Tables to make sure. The first entry on the last line should be 961. The last line should be:

961 1022 961 867.425000 25.000

You posted:

LOW HIGH OFFSET FREQ STEP
0 439 0 851.0125 25
440 559 440 851.0250 25
560 719 560 865.0125 25
720 759 720 866.0000 25
815 831 815 867.0000 25
958 958 958 868.9750 25
61 1022 961 867.4250 25 - This line should read 961 1022 961 867.4250 25

If you do, in fact, have that line correct, then the issues you are experiencing are not due to the trunking table.

I think there are a few other problems with the table... Here is what I am using and it is working just fine:

ChLO ChHI  Step    Offset  Base
440  559  25.000  440     851.025000
000  719  25.000    0     851.012500
720  759  25.000    0     848.000000
815  831  25.000    0     846.625000
958  958  25.000  958     868.975000
961 1022  25.000    0     843.400000

 

[N7YUO]

Try this amended zip file

The first time I compressed and sent a zip file of your program,
I used WinRAR. You found the file to be corrupt.

This time, I used WinZip, so it should work.
Give it a try and see what you have.

I await your reaction.

 

[ranger2004]

I think there are a few other problems with the table... Here is what I am using and it is working just fine:

ChLO ChHI  Step    Offset  Base
440  559  25.000  440     851.025000
000  719  25.000    0     851.012500
720  759  25.000    0     848.000000
815  831  25.000    0     846.625000
958  958  25.000  958     868.975000
961 1022  25.000    0     843.400000

I know WIN500 puts this in, but its wrong.
Todate nothing has gone above 719. I am trying to find an official site for the list.

*ok*
440 559 25.000 440 851.025000
000 719 25.000 0 851.012500

****Crap*****
720 759 25.000 0 848.000000
815 831 25.000 0 846.625000
958 958 25.000 958 868.975000
961 1022 25.000 0 843.400000

 

[qlajlu]

I know WIN500 puts this in, but its wrong.

DonS would not have included that plan in his software if it did not work. I think it may have changed with the new update to WIN500 because I have a completely different trunking table that I took out of WIN500 prior to the latest update to that program.

Right now there are three (3) Custom Band Plans available and mathematically they all accomplish the very same thing.

I'm of the opinion that if it works, use it. If it doesn't work, try one of the others. I know the top plan in the the Sticky at the top of this forum works, at least for a GRE PSR-600 that remains stationary. I use the top plan and I'm receiving both rebanded and not-yet-rebanded sites without a hiccup and I know it is also being used by others with the same results. bneilson obviously has his scanner working with the plan he posted. Different strokes for different folks.

 

[ranger2004]

V1.168 band plan is off even for standard.


0 719 0 851.012500 25.000
720 759 0 848.000000 25.000
815 831 0 846.625000 25.000
958 958 958 868.975000 25.000
961 1022 0 843.400000 25.000

 

[qlajlu]

V1.168 band plan is off even for standard.


0 719 0 851.012500 25.000
720 759 0 848.000000 25.000
815 831 0 846.625000 25.000
958 958 958 868.975000 25.000
961 1022 0 843.400000 25.000

I don't understand what you are saying. Please point specifically to the problem you are referring to.

I have run several examples through this plan and compared them to the other two plans and they all come up with the same frequency. The biggest difference I can see between the plans is the base frequencies and offsets.

 

[ranger2004]

I don't understand what you are saying. Please point specifically to the problem you are referring to.

I have run several examples through this plan and compared them to the other two plans and they all come up with the same frequency. The biggest difference I can see between the plans is the base frequencies and offsets.

V1.168 band plan is off even for standard.


0 719 0 851.012500 25.000
720 759 0 848.000000 25.000 <----848.0000 Uh No
815 831 0 846.625000 25.000 <----846.6250 Nope
958 958 958 868.975000 25.000
961 1022 0 843.400000 25.000 <----843.4000 Nope

Outside of band. Not in NPSPAC.
Luckily nothing above 719 on UCAN or you would missing traffic.

 

[qlajlu]

V1.168 band plan is off even for standard.


0 719 0 851.012500 25.000
720 759 0 848.000000 25.000 <----848.0000 Uh No
815 831 0 846.625000 25.000 <----846.6250 Nope
958 958 958 868.975000 25.000
961 1022 0 843.400000 25.000 <----843.4000 Nope

Outside of band. Not in NPSPAC.
Luckily nothing above 719 on UCAN or you would missing traffic.

Just to make sure we are on the same page, would you post what you are calling standard?

The Standard Plan I have shows the first line you question as

720 759 720 866.000000 25.000

If you will do the math on, let's say LCN 721 using both, you will find that LCN 721 points to 866.0250 MHz in both. Just because it is stated a different way does not mean it doesn't come back to the same point.

Since you brought it up, I will let you explain NPSPAC and what the limits (high and low) are because everyone on this board will now want to know, even me.

 

[gadgetmikey]

0 719 0 851.012500 25.000
720 759 0 848.000000 25.000 <----848.0000 Uh No

There is two ways of looking at this. The way it is shown in this table it is confusing because there is no offset.
It could also be entered as 720 759 720 866.0000. But instead it is shown without an offset so the frequency has to be lower to make up for an offset. If you take the 720 * .025 it gives you 18 and you subtract that from the 866 that is where you end up with the 848.000.

815 831 0 846.625000 25.000 <----846.6250 Nope
958 958 958 868.975000 25.000
961 1022 0 843.400000 25.000 <----843.4000 Nope

After rebanding the only valid public safety freq are the 0-559. So after rebanding you only need the first two lines. The other five lines are to support systems that have been rebanded as well as those that have not at the same time.

 

[Highpockets]

V1.168 band plan is off even for standard.


0 719 0 851.012500 25.000
720 759 0 848.000000 25.000 <----848.0000 Uh No
815 831 0 846.625000 25.000 <----846.6250 Nope
958 958 958 868.975000 25.000
961 1022 0 843.400000 25.000 <----843.4000 Nope

Outside of band. Not in NPSPAC.
Luckily nothing above 719 on UCAN or you would missing traffic.

I'm very much interested in the rebanding in Utah, NJ will be rebanding soon and if possible would you post a custom table that you say is correct and will work.

 

[ww7y]

0 719 0 851.012500 25.000
720 759 0 848.000000 25.000 <----848.0000 Uh No

There is two ways of looking at this. The way it is shown in this table it is confusing because there is no offset.
It could also be entered as 720 759 720 866.0000. But instead it is shown without an offset so the frequency has to be lower to make up for an offset. If you take the 720 * .025 it gives you 18 and you subtract that from the 866 that is where you end up with the 848.000.

815 831 0 846.625000 25.000 <----846.6250 Nope
958 958 958 868.975000 25.000
961 1022 0 843.400000 25.000 <----843.4000 Nope

After rebanding the only valid public safety freq are the 0-559. So after rebanding you only need the first two lines. The other five lines are to support systems that have been rebanded as well as those that have not at the same time.

I only put the first two lines in my BC246T after installing the new reband update. It is working fine and receiving everything on rebanded sites, as verified on UniTrunker.

 

[bchris]

Rebanded LCN's &amp; Freqs

Does everyone agree that after Weber & Davis are rebanded in the next week or so, or right now if you don't monitor those sites, us UCAN locals don't care about any LCN above 559 or any frequency above 862 Mhz?

Let me review why one might think such a thing. The chart attached below shows the FCC's new band plan for public safety beginning at 851 and ending at 862 Mhz, including the expansion and guard bands. (It is still referred to as '800 Mhz public safety'.) There were previously existing LCN's (channel numbers) spaced every .025 Mhz from 851-862, with LCN #zero centered at 851.0125. This puts #439 at 861.9875, just inside the upper boundary.

The FCC wanted to double the channels available from 851-854 Mhz, so they squeezed the new channels in between the old ones in this lower 3 Mhz area. They assigned LCN #440 to 851.0250, right in the middle of LCN's 0 & 1. Then with the same .025 Mhz spacing, each new channel will leapfrog an old channel, like a checkerboard pattern. This puts 559 at 853.9750, just inside the upper edge of the lower 3 Mhz.

The bottom line result is that LCN's 0-559 occupy the frequencies 851-862 Mhz. Any LCN or frequency outside this range will be used for business or commercial radios, such as Nextel. All valid custom tables I have seen coincide with this plan, including the 2-liner just posted by Uniden for their '246 update instructions. It looks like the first 2 lines of every table I have seen cover the new public service band, and all the other lines are only needed for pre-rebanded systems.

Are we all in agreement on this?

-bc

Highpockets - In my opinion the pretty-looking table recently posted by GadgetMikey is THE standard table to use during the rebanding process. Other tables might cover wider frequency ranges that we don't care about, or the lines seem 'out of order' for whatever reason, or they have extra numbers that to me are redundant (but do need to be entered for some software). They all work out mathematically (barring any typos) to be the same for the LCN's and frequencies that we care about, but GadgetMikey's is the most simple and straightforward, and has worked in every case that I know of. I think after next week we Utah-folk will only need the first 2 lines anyway.
.

 

[qlajlu]

bchris, that is one of the most informative things I have read about this whole mess. You have done a spectacular job of removing many misconceptions.

 

[Highpockets]

bchris, I agree with qlajlu, thank you very much for the information.