SDS100 454Mhz Programming

[werinshades]

Recently have been trying to add this system: https://www.radioreference.com/apps/db/?sid=9746. As you can see, this is a NXDN Trunking System and I'm trying to program Site 7's control channel 454.065625 and the SDS 100 & 536 HP rounds off to 454.0625 and the additional frequencies of 454.215625 in which the SDS100 accepts and 536 rounds off to 454.2156 (I'll assume 25 is accepted, just not showing on the display) and 454.590625 which the SDS 100 accepts and the 536 rounds off to 454.5906 (I'll assume 25 is accepted and not showing). Duplicate programming via Sentinel, and the SDS 100 is not receiving the system's control channel and trunking the system while the 536 is. Attempted to manually enter the control channel and it wouldn't accept it, unless it was above the 454.100 threshold.

My first thought was to the Band Defaults, which I tried at both 12.5 and 6.25 spacing. No change there. Took a ride today and gave it a try in the event the signal wasn't strong enough and that did not work. Double checked LCN settings and they also are the same. It would appear, the SDS100 isn't going to trunk track the system unless the frequency is exact while the 536 (and probably the 436) aren't as picky. Taking suggestions..

 

[AvidHiker]

I didn't think the SDS's tuner could resolve such a small difference in frequency.

 

[Hit_Factor]

I use a text editor and correct the frequencies directly in the files after I quit out of Sentinel.

Sent from my SM-G950U using Tapatalk

 

[Ubbe]

It's using a 3.125KHz step size.

/Ubbe

 

[werinshades]

Yes...but not sure why it will not accept a 3.125KHz step size frequency below 454.100 or receive/decode the "rounded off" frequency?

 

[Ubbe]

OK, but did you go into Sentinels profile editor and to Band Defaults and changed the step to 3.125 ?

/Ubbe

 

[werinshades]

OK, but did you go into Sentinels profile editor and to Band Defaults and changed the step to 3.125 ?

/Ubbe

Doesn't allow 3.125khz...6.25 and 5.0 is the lowest. But...the frequencies above 454.100 are accepted and displayed..454.215625, 454.590625.

 

[UPMan]

Regarding programming of 454.065625 MHz, the SDS accepts it, x36 rounds off to 454.0656.
Both scanners will receive on that frequency witn no problem.
It will never be rounded off to 454.0625 in FL programming.

 

[werinshades]

Regarding programming of 454.065625 MHz, the SDS accepts it, x36 rounds off to 454.0656.
Both scanners will receive on that frequency witn no problem.
It will never be rounded off to 454.0625 in FL programming.

I just submitted a debug file for review this morning with a video through Jason Houk. 3.125 khz frequencies were accepted in both Sentinel and the scanner, but appears to be a decoding issue. ERR is very low so ruled out interference. I am using the same antenna I was on the 536.

 

[UPMan]

According to the log, LCNs are 2, 17, and 37. LCN 5 of RR is probably incorrect.
Please check them with LCN finder.
Also, try different filter settings.

 

[werinshades]

According to the log, LCNs are 2, 17, and 37. LCN 5 of RR is probably incorrect.
Please check them with LCN finder.
Also, try different filter settings.

Yes...the LCN's were wrong and I ran LCN Finder to get the correct order. However, issue is still present with intermittent decoding and sometimes no audio at times, and talk group would show. I have additional debug files and tried different filter settings.

 

[jasonhouk]

I just submitted a debug file for review this morning with a video through Jason Houk. 3.125 khz frequencies were accepted in both Sentinel and the scanner, but appears to be a decoding issue. ERR is very low so ruled out interference. I am using the same antenna I was on the 536.

Just FYI, I never linked to the video because it was only shared to me.

Houk

 

[werinshades]

Just FYI, I never linked to the video because it was only shared to me.

Houk

Of course I deleted the video, but if another one is needed this system is busier during weekdays where it wouldn't be an issue. Mainly a few school bus companies.

 

[UPMan]

According to the logs, 454.590625 seems to be incorrect. The log shows:
LCN 17 454.065625 MHz -> OK
LCN 2 454.215625 MHz -> OK
LCN 37 454.590625 MHz -> Does not receive at all

You need to review license information and/or search the general frequency band to find the correct frequency that should be assigned to LCN 37.

 

[werinshades]

According to the logs, 454.590625 seems to be incorrect. The log shows:
LCN 17 454.065625 MHz -> OK
LCN 2 454.215625 MHz -> OK
LCN 37 454.590625 MHz -> Does not receive at all

You need to review license information and/or search the general frequency band to find the correct frequency that should be assigned to LCN 37.

Myself and a database administrator have verified these frequencies on a few occasions, most recently was yesterday. Originally as you posted, the LCN's were incorrect. We both re-ran LCN finder two days ago and did concur with your findings.

Yesterday, I was notified that the LCN's have returned to the original finding after another LCN finder was run and the administrator updated the database again: https://www.radioreference.com/apps/db/?siteId=32395

LCN-37 (454.590625) has been confirmed and never changed. I'll monitor for traffic, but on both the 536 and SDS 200, this LCN order has been confirmed but the 536 is the only scanner properly tracking and receiving. I'm not sure what else is going on here.

 

[werinshades]

Myself and a database administrator have verified these frequencies on a few occasions, most recently was yesterday. Originally as you posted, the LCN's were incorrect. We both re-ran LCN finder two days ago and did concur with your findings.

Yesterday, I was notified that the LCN's have returned to the original finding after another LCN finder was run and the administrator updated the database again: https://www.radioreference.com/apps/db/?siteId=32395

LCN-37 (454.590625) has been confirmed and never changed. I'll monitor for traffic, but on both the 536 and SDS 200, this LCN order has been confirmed but the 536 is the only scanner properly tracking and receiving. I'm not sure what else is going on here.

UPMan:

Today I ran LCN finder on both an SDS 200 and 536HP and the LCN's were changed again. The database administrator ran DSD Plus and his 536HP and his LCN findings were different, or as they are posted. It would appear the scanners are having some difficulty trunk tracking the 3.125 khz control and voice channels as we're both seeing different results. Let me know what else I can do to help..thanks.

 

[werinshades]

According to the logs, 454.590625 seems to be incorrect. The log shows:
LCN 17 454.065625 MHz -> OK
LCN 2 454.215625 MHz -> OK
LCN 37 454.590625 MHz -> Does not receive at all

You need to review license information and/or search the general frequency band to find the correct frequency that should be assigned to LCN 37.

Myself and a database administrator have verified these frequencies on a few occasions, most recently was yesterday. Originally as you posted, the LCN's were incorrect. We both re-ran LCN finder two days ago and did concur with your findings.

Yesterday, I was notified that the LCN's have returned to the original finding after another LCN finder was run and the administrator updated the database again: https://www.radioreference.com/apps/db/?siteId=32395

LCN-37 (454.590625) has been confirmed and never changed. I'll monitor for traffic, but on both the 536 and SDS 200, this LCN order has been confirmed but the 536 is the only scanner properly tracking and receiving. I'm not sure what else is going on here.

UPMan:

Today I ran LCN finder on both an SDS 200 and 536HP and the LCN's were changed again. The database administrator ran DSD Plus and his 536HP and his LCN findings were different, or as they are posted. It would appear the scanners are having some difficulty trunk tracking the 3.125 khz control and voice channels as we're both seeing different results. Let me know what else I can do to help..thanks.

Screen shot from DSD. Channel 37 is still showing correctly with LCN finder today.