SDS100/SDS200: NXDN problem

[ngel]

I am trying to monitor this system with my SDS100 Florida FleetTalk Site: Hudson

I programmed it as NXDN trunk , ran the LCN finder with it finding all LCN order and have it in ID search mode. The trunking channel is being received I see the NEX4 symbol and confirmed all system types are checked. I have the filter set as auto for now

This morning with my TRX1 side by side the TRX is receiving traffic and the SDS100 is not. The SD100 will stop on the talkgroup but no audio comes through when the talkgroup comes up. The talkgroup is 1161 and is not encrypted. Anyone have any suggestions?

 

[bmendez]

Housekeeping feature may be the reason to blame I been having issues with the same thing for a long time

 

[werinshades]

I am trying to monitor this system with my SDS100 Florida FleetTalk Site: Hudson

I programmed it as NXDN trunk , ran the LCN finder with it finding all LCN order and have it in ID search mode. The trunking channel is being received I see the NEX4 symbol and confirmed all system types are checked. I have the filter set as auto for now

This morning with my TRX1 side by side the TRX is receiving traffic and the SDS100 is not. The SD100 will stop on the talkgroup but no audio comes through when the talkgroup comes up. The talkgroup is 1161 and is not encrypted. Anyone have any suggestions?

Is it safe to assume you purchased the NXDN key and entered it into the scanner? TRX-1 doesn't require a key because it's not trunk tracking the system.

 

[werinshades]

Housekeeping feature may be the reason to blame I been having issues with the same thing for a long time

Ummm what? Did you purchase the NXDN key? Do you have the latest firmware in..1.23.07/1.03.06?

 

[bmendez]

Yup the sds100 have an issue with nxdn it don’t decode good at all

 

[werinshades]

Yup the sds100 have an issue with nxdn it don’t decode good at all

Many of us aren't having issues so I suspect it's the operator and not the scanner. Housekeeping?

 

[tvengr]

The Hudson site in Pasco County uses RAN 45. The CH ID's for the site are in the database. You do not need to run the LCN finder.

CH ID Frequency 903 462.7375c 740 463.625c 683 463.2125

 

[ngel]

The Hudson site in Pasco County uses RAN 45. The CH ID's for the site are in the database. You do not need to run the LCN finder.

CH ID Frequency 903 462.7375c 740 463.625c 683 463.2125

I programmed it manually after having continuous issues not getting traffic

 

[ngel]

Ummm what? Did you purchase the NXDN key? Do you have the latest firmware in..1.23.07/1.03.06?

Yes I purchased the key and it’s up to date

 

[tvengr]

Please export and attach your favorites list so we can take a look at it. Go to the File tab in Sentinel and click on Export to hpe file (Favorites List). You will need to zip the exported file to be able to attach it. Click on Attach files and open the zipped file.

 

[ngel]

@tvengr see attached

 

[tvengr]

You have LCN's 683 and 740 reversed for the 2 frequencies. Also, there is no department or talkgroups.

 

[ngel]

@tvengr Wouldn’t the LCN I have be correct as I used the LCN finder on the scanner? Also I have the programming in ID search mode, is it required to have talkgroups programmed in ? I don’t know which talkgroups are active in my area as it’s a statewide regional system and not all those talkgroups listed are active on my nearest site

 

[tvengr]

The LCN finder needs to be run for a long time to be accurate. It can have errors. For now, go with what is in the database. Sometimes, you need a talkgroup programmed for ID Search to work. Add a department with TGID 1161 which you know is active.

 

[Ubbe]

Sometimes, you need a talkgroup programmed for ID Search to work.

Isn't the case that you always have to program a dummy TG to get IDSearch to work, or have Uniden changed their firmware lately to operate differently? It's a kind of bug, that it first detect what TG are active in the received system and then goes to programmed TG's in the scanner and if the TG are not found it checks if IDSearch are on. But if the TG list are empty it never checks the IDSearch flag. Maybe they have fixed that bug now?

I believe that other functions like LCN Finder where using the same code structure and also had issues when no fixed TG where programmed?

/Ubbe

 

[werinshades]

Isn't the case that you always have to program a dummy TG to get IDSearch to work, or have Uniden changed their firmware lately to operate differently? It's a kind of bug, that it first detect what TG are active in the received system and then goes to programmed TG's in the scanner and if the TG are not found it checks if IDSearch are on. But if the TG list are empty it never checks the IDSearch flag. Maybe they have fixed that bug now?

I believe that other functions like LCN Finder where using the same code structure and also had issues when no fixed TG where programmed?

/Ubbe

I've never had to do this on any of the systems I didn't have a talk group programmed.

 

[ngel]

I've never had to do this on any of the systems I didn't have a talk group programmed.

Neither have I. I have multiple systems of different types programmed in ID search with no talk group programmed and only in ID search mode.

 

[Whiskey3JMC]

Isn't the case that you always have to program a dummy TG to get IDSearch to work

No. I have quite a few systems with no talkgroups programmed. ID Search works fine

 

[tvengr]

Does it make a difference that there are no departments programmed?

 

[Whiskey3JMC]

Does it make a difference that there are no departments programmed?

I've never noticed a difference