Info for BCD396XT & poss BCD996XT users

[rustynswrail]

If anyone is using the imported Uniden BCD396XT and possibly BCD996XT scanners, then I have some information that maybe of some use.

While playing around with the P25 trunking settings, I lowered the P25 delay to 0 and set up custom Motorola band plans for the trunking. In field one, entered 412.4750 as lower, 420.0125 as the upper, with a step of 6.25 and offset of 756.

Now it maybe my imagination, but it seems to improve the trunking speed, with less misses of transmissions. As I said. not proof, just my impression.

R

[jaskel]

hmm anyone else tried this?? might make a grn only profile and try it

[Bigfella237]

Rusty,

I can only assume you're talking about the setup for the old Type II GRN as I don't think you can enter a bandplan for a P25 system?

If so then that bandplan shouldn't work? Because the old system used OBT (Other Band Trunking) Control Channels, to properly trunk-track the old 4.1 GRN you need to enter three separate bandplans:

Base Freq: 415.5750 Step: 12.5 Offset: 380
Base Freq: 413.1000 Step: 12.5 Offset: 723
Base Freq: 415.0000 Step: 12.5 Offset: 748

If you were creating a bandplan for the new P25 GRN (which you shouldn't have to because it's an implicit system) it would be:

Base Freq: 412.47500 Step: 6.25 Offset: 04-0000 (as we're only using bandplan 4 at the moment)

But I think where you *may* have gained some speed is by setting the System Delay to zero, this setting is the minimum amount of time the scanner will spend parked on the trunk system, however it only makes any difference if the delay is set higher than the amount of time that it actually takes to scan all the control channels in that system?

To explain further, if it takes 0.8 seconds to scan all the frequencies entered into the system but the delay is set to 2 seconds, the scanner will continue scanning that system over and over for 2 seconds; if the delay is set to zero, the scanner will still scan all the frequencies once and then move on to the next system immediately (because it's already taken longer than the specified delay time).

Andrew

[rustynswrail]

Rusty,
I can only assume you're talking about the setup for the old Type II GRN as I don't think you can enter a bandplan for a P25 system? If so then that bandplan shouldn't work? Because the old system used OBT (Other Band Trunking) Control Channels, to properly trunk-track the old 4.1 GRN you need to enter three separate bandplans:
Base Freq: 415.5750 Step: 12.5 Offset: 380
Base Freq: 413.1000 Step: 12.5 Offset: 723
Base Freq: 415.0000 Step: 12.5 Offset: 748
If you were creating a bandplan for the new P25 GRN (which you shouldn't have to because it's an implicit system) it would be: Base Freq: 412.47500 Step: 6.25 Offset: 04-0000 (as we're only using bandplan 4 at the moment) But I think where you *may* have gained some speed is by setting the System Delay to zero, this setting is the minimum amount of time the scanner will spend parked on the trunk system, however it only makes any difference if the delay is set higher than the amount of time that it actually takes to scan all the control channels in that system? To explain further, if it takes 0.8 seconds to scan all the frequencies entered into the system but the delay is set to 2 seconds, the scanner will continue scanning that system over and over for 2 seconds; if the delay is set to zero, the scanner will still scan all the frequencies once and then move on to the next system immediately (because it's already taken longer than the specified delay time). Andrew

Andrew,

That is the strange part, I know the P25 doesn't need the base frequencies etc, but I put it another way, it doesn't seem to have an adverse effect on the scanner. I am still sticking by my comment - it maybe my imagination, but....

And agreed, the delay time is probably having more an effect than the bandplan.


Russell

[jaskel]

howd you go with this