The information I submitted earlier this evening was the three missing frequencies, but also just a bit of housekeeping, correcting the System ID, Site ID's and fixing an incorrect License, along with other minor things. The proper LCN's were already documented in the system notes, they just weren't assigned to the correct sites, and the capture that
@kbk777 shared back in the earlier message showed all three in use (DSDPlus logs by "Logical Slot Numbers" LSN's, and the LSN's when calculated match the "Logical Channel Numbers" LCN's that Uniden uses, hence why they can be considered verified. Since each frequency has 2 "slots" there are 2 LSN's for every 1 LCN. (meaning one frequency can carry two conversations, be them voice or data or control channel) at the same time.
Quick lesson on most Tier III systems, both Standard and Non-Standard (including Capacity Max) - These systems typically run a "bandplan" much like a P25 system does, but unlike a P25 system, that bandplan is not transmitted over the air (which is why you only need to program the control channels on a P25 system, since it gets the bandplan and can decode the rest), only the channel assignments for traffic. In Tier III terms, the channel assignments are sent as LSN's. The good news is that with a bit of math, once you match one or two frequencies to the LSN's that they use, you can calculate the bandplan, which will line up with all frequences.
In the case of this system, there is actually 2 bandplans, the first has a base frequency of 450.4125 (which is LSN 3 and 4, or LCN 1), the second is a base frequency of 460.0 (which again is LSN 3 and 4, or LCN 1). On both bandplans they are using 12.5KHz spacing between results, so LSN 5 and 6 or LCN 2 would be 450.425 and 460.0125 respectively.
Some people use a spreadsheet to lay out the bandplan once it's determined, others, like me use the
DMR frequency calculator, which makes quick work of mapping the bandplan to what is being seen in DSDPlus.
When
@kbk777 was monitoring Site 1, I observed a few entries as (see the highlighted part for the LSN's):
Using my decoder, I was able to get the frequency, and since the LSN's received and LCN's that were already posted were consistent, I could submit it to RRDB as:
Code:
Site Frequency Table:
LCN LSNs or CH IDs Frequency Color Code
2153 4307/4308 477.3125 0 ***ADD***
The same could be said for the two frequencies on Site 2:
Which resulted in this being submitted:
Code:
Site Frequency Table:
LCN LSNs or CH IDs Frequency Color Code
2129 4259/4260 477.0125 0 ***ADD***
2145 4291/4292 477.2125 0 ***ADD***
I strongly believe in "quality not quantity", and I only submit data if I have a high confidence of its accuracy. Likewise how I submit it is formatted in a way that leaves little room for a misunderstanding by the fine database admins (based on many lessons learned). Scanners may give you functional data, but its tools like DSDPlus that give you the complete picture, and I have begun to rely on it more heavily in the past few years (I own 6 SDR Radios, so yes, it is a big deal for me), but still leverage my SDS100/200 for parts of assembling that big picture and verifying what I get.
