Questions Regarding Reference Material on this Web Site

[NORCAL]

I have two (2) questions regarding the RF Database reference area. The first question is regarding the RF Database located under the State of Nevada, Clark County, the Nevada Shared Radio System (a EDACS Wide Area system).

Please refer to the System Frequencies Table listed here. Under Site 003 for Las Vegas, the sequence of the frequency listings does not fully follow the Logical Channel Number (LCN) convention. The 003 Row is duplicated here for your review: (01) 854.9625, (02) 855.4625, (03) 855.9875, (04) 856.4875, (05) 857.2125, (06) 858.2125, (07) 859.2125, (08) 859.7125, (09) 860.2125, (10) 860.7125 [Here is where the sequence breaks down] (11) 856.2375, (12) 856.9625, (13) 858.4375, (14) 859.4375, and (15) 860.9625.

After No 10, the sequence stops following LCN convention. It reverts back to a lower frequencies number and then ascends to a higher number again. Is this a simple data entry error, or is it something I don’t understand about the EDACS system.

Second area in question is related to the same location. It is located in the System Talkgroups Table (lower down the page below the System Frequencies Table) for the Nevada Shared Radio System, the State of Nevada, Clark County. Please refer to the DEC column and go to DEC 740. Using a conversion table referenced in the EDACS Trunking Information article under Trunk Information reference area, DEC 740 converts 14-080, not as listed 05-124. None of the DEC-AFS listings in this table are correct if I’m to follow the conversion table mentioned above.

With reference to the above discussion, does any one have a good answer to these “so-called discrepancies”? Your response is appreciated. NORCAL

 

[blantonl]

After No 10, the sequence stops following LCN convention. It reverts back to a lower frequencies number and then ascends to a higher number again. Is this a simple data entry error, or is it something I don’t understand about the EDACS system.

EDACS LCNs are in no set order or sequence, they can be in any sequence that the system administrator chooses. They may be in order of lowest freq to highest (common) - or any arbitrary scheme that the admin chooses. That's why they are called "Logical Channel Numbers"

So, there's no problem there unless the LCNs are incorrect.

Please refer to the DEC column and go to DEC 740. Using a conversion table referenced in the EDACS Trunking Information article under Trunk Information reference area, DEC 740 converts 14-080, not as listed 05-124. None of the DEC-AFS listings in this table are correct if I’m to follow the conversion table mentioned above.

Ooops! You referenced the HEX column in that table you mention. Dec 740 does indeed convert to 05-124.

With reference to the above discussion, does any one have a good answer to these “so-called discrepancies”? Your response is appreciated. NORCAL

See above... :wink:

 

[NORCAL]

Web Master,

Thanks for quick response and education on the EDACS system. Thanks for pointing out my mistake on HEX vs DEC.

NORCAL

 

[iceman47]

The input is incorrect.
In the NHP EDACS all LCN's are in ascending order(lowest to highest).
This probably doesn,t matter since the system operates so badly.
All kinds of comments by troopers on the air about the poor operation of the system. It's almost comical if it were not so dangerous for their safety.
Seems it's easier to cover up a screw up than to fix the problem for officer safety.
Another 15 or 20 million dollars should do it.