SDS100/SDS200: Tier III Systems - LCN Oddity....

[Forts]

I'm not sure if this has been discussed already but I've discovered something odd with Tier III systems regarding the LCN numbering. I have a fairly active TIII system near me that I logged for a while with DSD+. I gathered all the system frequencies, LCN order, color code etc (and noted that RAS was active) then put it all in the SDS. And received nothing. Not a peep. After lots of double checking I figured it was either a RAS issue or something with the LCN stuff, so on a whim I ran the LCN finder for a while. After discovering most of the LCNs I compared values with what I had from DSD+ and discovered something odd. All the values the SDS came up with were half of what DSD+ showed, across the board. In fact I noticed that I could take all the LCN values from DSD+ and just divide them by 2.. and in each case it would come back as a fraction (IE 488.5) so I would just drop the fraction for each one. I updated everything in the radio and away it went... works like a champ (maybe the 436/536 are like this too? I dunno)...

So I guess my next question would be regarding the database.... should we be submitting the values from DSD+ or the Uniden happy values?

 

[BigWonton]

There is a portion in the Uniden wiki that explains it:

http://info.uniden.com/twiki/bin/view/UnidenMan4/DigitalMobileRadioUpgradeforBCDxxxP2


Manually Determining the LCN for DMR Tier III Systems based on DSD+ Logs

DSD+ combines the LCN and Slot together in the style of MotoTRBO Capacity Plus. This combination was coined as LSN. You need to divide the lower number by two and ignore the fraction.

1899/1900 would be 949
1941/1942 would be 970
1985/1986 would be 992

 

[mrscanner2008]

I'm not sure if this has been discussed already but I've discovered something odd with Tier III systems regarding the LCN numbering. I have a fairly active TIII system near me that I logged for a while with DSD+. I gathered all the system frequencies, LCN order, color code etc (and noted that RAS was active) then put it all in the SDS. And received nothing. Not a peep. After lots of double checking I figured it was either a RAS issue or something with the LCN stuff, so on a whim I ran the LCN finder for a while. After discovering most of the LCNs I compared values with what I had from DSD+ and discovered something odd. All the values the SDS came up with were half of what DSD+ showed, across the board. In fact I noticed that I could take all the LCN values from DSD+ and just divide them by 2.. and in each case it would come back as a fraction (IE 488.5) so I would just drop the fraction for each one. I updated everything in the radio and away it went... works like a champ (maybe the 436/536 are like this too? I dunno)...

So I guess my next question would be regarding the database.... should we be submitting the values from DSD+ or the Uniden happy values?

Forts do you received 100% of the communication ? because here in Quebec I have a T3 system that I receive only 50% of communications and this even if I have all the good LCN

see thread https://forums.radioreference.com/uniden-tech-support/370903-upman-logs-lcn-finder-problems-cap-max-tiii.html


I have this problem with both the SDS100 and the x36, and I'm not the only one, we are 5-6 to have this problem.