Which Trunk Systems Need Base/Offset?

[b52hbuff]

I thought I understood about what systems need Base/Offset. Basically any Motorola P16 System not in 800/900MHz needed base / offset. So UHF and VHF trunking.

My understanding is that true P25 systems didn't need base and offset. But then I see:
http://www.radioreference.com/modules.php?name=TRSDB&sid=4076

Is this correct??

 

[kikito]

You're right, If it's a true P25 system (9600bps CC), it does NOT need the Base/Offset.

Maybe that system you pointed out has an error in the entry for type of system or something....

 

[fmon]

You're right, If it's a true P25 system (9600bps CC), it does NOT need the Base/Offset.

Maybe that system you pointed out has an error in the entry for type of system or something....

The entries for the 2 Base/Offset tables for the new West Virginia UHF 400 P25 sysatem are incorectly placed in the Database for the referenced page. Thus, when using Web Import in Win96, only the frequencies will import, the tables do not.

BTW, I checked that system on I-64 going West on Sept 18 and going East on Oct 1. No CC's were heard yet. However, Brucewarning indicated in this feed http://www.radioreference.com/forums/showthread.php?t=18334 that he is getting CC's up north but no traffic.

 

[kikito]

Maybe the tables were listed for using in the Pro-96 because of the known bug that it doesn't track P25 systems correctly without multiple 'weird' tables put in. I know when I use my Pro-96 in my local system, I have to put in 6 tables in order to track all the sites correctly. But don't need anything when using the Unidens


Just for reference, here's my local system:

http://www.radioreference.com/modules.php?name=TRSDB&sid=2447

Again, to reiterate to the original poster, P25 systems don't need Base/Offset tables defined unless you're using the Pro-96/2096.

 

[fmon]

Again, to reiterate to the original poster, P25 systems don't need Base/Offset tables defined unless you're using the Pro-96/2096.

Except you didn't say the part about the Pro-96/2096 in your first answer. And it still doesn't explain why RR Database has the two tables for the WVA system misplaced for Web Import users and Butel's RR CSV creator does not import the tables data either, apparently due to the misplacement of the info.

 

[brucewarming]

fmon- check your private messeges.

 

[fmon]

Got the PM brucewarming.

kikito,
I wasn't being critical, in fact, I salute your input to this and other forums. Your state planners have provided you with a great challenge in the ALMR system and you have provided considerable info on how it works by pioneering the Tables early in the life of the Pro-96. This type of info is invaluable to us normal scanner users.

I do note that the tables are misplaced on the ALMR page also, thus cannot be imported with Web Import. This—with the same problem in the WV Interoperability Radio System—makes me wonder if the people doing the database pages are doing this on purpose. Since Web Import only works with Win96, could it be that Uniden users have more need for future imports then does Pro-96/2096 users?

 

[kikito]

I do note that the tables are misplaced on the ALMR page also, thus cannot be imported with Web Import.

OK, now I understand what you're saying and why the Web Import doesn't work.

The only reason I could think of why is done this way is the same reason you mentioned. The current way allows everyone to do an import regardless of scanner brand and for those that need the Tables, they need to enter them manually. Otherwise, I can see how those tables could create problems with Uniden users during an import, especially since Uniden only allows 3 of them.

Except you didn't say the part about the Pro-96/2096 in your first answer.

I'm editing that to show it now!
EDIT: I guess I can't edit it after all, too late.

kikito,
I wasn't being critical, in fact, I salute your input to this and other forums. Your state planners have provided you with a great challenge in the ALMR system and you have provided considerable info on how it works by pioneering the Tables early in the life of the Pro-96. This type of info is invaluable to us normal scanner users.

No problem and thanks.

I did get a lot of help from many people in this community like wayne_h (trunked system knowledge), Mike Vanderveer (excellent Pro96Com software), Don Starr (GRE radios knowledge) and several others, so it was more of a group effort.

 

[b52hbuff]

Maybe the tables were listed for using in the Pro-96 because of the known bug that it doesn't track P25 systems correctly without multiple 'weird' tables put in. I know when I use my Pro-96 in my local system, I have to put in 6 tables in order to track all the sites correctly. But don't need anything when using the Unidens


Just for reference, here's my local system:

http://www.radioreference.com/modules.php?name=TRSDB&sid=2447

Again, to reiterate to the original poster, P25 systems don't need Base/Offset tables defined unless you're using the Pro-96/2096.

Thanks for the information. So how do you go about determining the table values to work around a Pro-96 bug?

 

[fmon]

If the tables on your link are correct, set as follows:

Table 1. 380 578 453.0125 380 12.5
Table 2. 579 759 460.0125 579 12.5

This may not be correct because the system is 9600 baud (verified by brucewarming in Martinsburg on another feed running Pro96Com). Thus should not require any tables to be set. And these settings (380, 578, 579 & 759) are for 3600 baud systems. However, brucewarming is logging ID hits on Pro96Com but has not heard any traffic yet. BTW, Pro96Com will not link up to a 3600 baud system, only 9600 baud.