SDS100/SDS200: BCDx36HP/SDS100 Sentinel v2.00.09 Prerelease

[UPMan]

We'll likely make this a "live" version this week (along with the latest open beta firmware), but meanwhile, why wait. If you want to take advantage of the new settings added in open beta, this version should help.

What is Changed:
1) Added Site NAC Operation to the Profile Editor (Miscellaneous tab)
2) Changed the initial dB version to the 7/1/18 release.
3) Added the "Modulation" attribute to MotoTRBO, DMR, and NXDN sites.

http://info.uniden.com/twiki/pub/PartnerWeb/SDS100-Beta/BCDx36HP_Sentinel_Version_2_00_09.zip

 

[WX4JCW]

Thank You


Sent from my iPhone 8 using Tapatalk Pro
Jason WX4JCW
XPR7550 - SDS100

 

[jodyobrien]

THANK YOU sooo much! your de best!! thanks "Up-Man"

 

[rbrtklamp2]

Thanks Paul!

Sent from my SM-N910V using Tapatalk

 

[mike1988]

Thank you Paul.


Sent from my iPhone using Tapatalk

 

[buddrousa]

Thanks UPMAN and your team

 

[pinballwiz86]

Thanks a lot! It is working good under Windows 10 Pro.

 

[kruser]

No Manual Digital Settings for NXDN trunked

Still no Manual Digital Decode settings available in Sentinel for x36HP models on NXDN trunked systems.?

 

[del1964]

What is Changed:
1) Added Site NAC Operation to the Profile Editor (Miscellaneous tab)
Q.)Should this be set to "Ignore Site NAC"?

2) Changed the initial dB version to the 7/1/18 release.

3) Added the "Modulation" attribute to MotoTRBO, DMR, and NXDN sites.
Q.) Is "Auto" a "better" setting than say NFM or FM?
I'll be monitoring Indianapolis, Indiana ERS-OCI TRBOconnect Con+ sites


[/QUOTE]



See questions above. Thanks, Del

 

[del1964]

Found the answer to my first question:


"Regarding Site NAC Operation:

You can select (use or ignore) Site NAC of P25 Trunked Systems (including P25 OFT) in RRDB and Favorites Lists. When we added NAC support, we did not anticipate that the NAC would be incorrect in RRDB for many sites. This has caused many reports that the scanner stopped working with the new firmware (it was actually working correctly and rejecting the site traffic with the "incorrect" NAC). So, we've added an option to ignore the programmed NAC."

 

[werinshades]

Found the answer to my first question:


"Regarding Site NAC Operation:

You can select (use or ignore) Site NAC of P25 Trunked Systems (including P25 OFT) in RRDB and Favorites Lists. When we added NAC support, we did not anticipate that the NAC would be incorrect in RRDB for many sites. This has caused many reports that the scanner stopped working with the new firmware (it was actually working correctly and rejecting the site traffic with the "incorrect" NAC). So, we've added an option to ignore the programmed NAC."

It's been discussed somewhere and I had a chance to see this, if you program a NAC and it's not correct or you have other site frequencies programmed in, the "corrected" NAC will flash alongside the "programmed" NAC.

Last night one of my sites briefly went off line. Under my site frequencies section, I have other site's frequencies programmed in the event I'm out and I lose the control channel. Under the previous firmware, this would not work as the NAC site was programmed. With the latest firmware the SDS 100, immediately picked up a neighboring sites control channel and the new NAC was flashing in the display. Didn't realize this until I noticed some choppiness in the transmission and took a look at the display.

I have set mine to Display NAC, but I don't use location control or Zip code based programming from RRDB. Instead I program using the database as a tool and unless I put in the CTCSS,DCS or NAC codes myself, they are always set to Search until I can confirm or another local user emails me or texts me that he confirmed the entry. This could be a reason why I've had much success with my SDS 100, while others are reporting programming issues?

 

[jonwienke]

There are two typos in the File menu--"Favoites" instead of "Favorites" in the import and export HPE menus.

 

[kikito]

There's a small bug I think when it comes to the Profile settings between radios. Some of the settings keep going back to default whenever I switch between radios while programming.

Specifically the 'Display Mode' on the BCDx36HP always switches back to Mode 1 under Display Options.

And here's how I can duplicate it: With Sentinel on BCDx36HP mode, I verify my BCD436 profile has Mode 2 selected under Display Options.I switch Sentinel to SDS100 mode. Read from the SDS. Switch Sentinel back to BCDx36HP mode and now under Display Options the BCx36HP is set back to Mode 1. There might be another setting or two that also defaults but I can remember now which, if any other.

 

[jonwienke]

That's not a bug, that's a side effect of settings being used differently and having different valid values from one model to another. You should not be constantly switching a profile back and forth between x36 and SDS modes, you should have completely separate profiles for x36 and SDS.

 

[kikito]

That's not a bug, that's a side effect of settings being used differently and having different valid values from one model to another. You should not be constantly switching a profile back and forth between x36 and SDS modes, you should have completely separate profiles for x36 and SDS.

Hmm, I guess I haven’t thought about it that way but kind of makes sense the way you put it, although I cannot quite agree why it has to work that way.

I just want and have been keeping both radios programmed exactly the same. And I thought that switching models on Sentinel would only tell the software to load the radio specific features of each and keep the base programming the same. It doesn’t make sense to me to need to have different profiles for each radio if I want the same exact programming on both.

If that’s the case as you say... then I can turn this into a request post instead and maybe have Sentinel automatically load a default programming file for each radio model when you select it in the menus. In fact, honestly I don’t know why we even have to manually switch anything when the software talks to the radio and can identify everything about it even before you read or write to the radio.

Either way not a big deal and I can live with it as it is.

 

[jonwienke]

I just want and have been keeping both radios programmed exactly the same. And I thought that switching models on Sentinel would only tell the software to load the radio specific features of each and keep the base programming the same. It doesn’t make sense to me to need to have different profiles for each radio if I want the same exact programming on both.

Programming is stored in Favorite Lists, which are the same no matter which profile you use.

 

[kikito]

Programming is stored in Favorite Lists, which are the same no matter which profile you use.

Exactly. So even less reason for me to have to worry about anything else but to switch Sentinel to the appropriate radio I’m programming and Sentinel to use the last known profile settings for each instead of defaulting some of them.

But I’ll stop now and let it be because we’re not getting anywhere. I guess is up to Uniden to change or not that “behavior” or “feature” I mentioned earlier...

 

[jonwienke]

Exactly. So even less reason for me to have to worry about anything else but to switch Sentinel to the appropriate radio I’m programming and Sentinel to use the last known profile settings for each instead of defaulting some of them.

Which is EXACTLY what would happen if you switched profiles, instead of changing a profile back and forth between x36 and SDS mode. Make a separate profile for your x36 and SDS scanners, and the problem goes away.

Hint: Make a new profile by using the File \ Save As menu, and save under a new name matching the scanner that will use it.

 

[KE5MC]

Exactly. So even less reason for me to have to worry about anything else but to switch Sentinel to the appropriate radio I’m programming and Sentinel to use the last known profile settings for each instead of defaulting some of them.

But I’ll stop now and let it be because we’re not getting anywhere. I guess is up to Uniden to change or not that “behavior” or “feature” I mentioned earlier...

While each profile will use the same Favorites List in the profile the monitor and download can be set different between the profiles. There are changes like the NAC options of use/ignore for SDS100 present and missing for x36 profiles. Also the display customizer is greyed out unless targeted for SDS100. Might be other items too I have missed.

It is a pain to remember to switch targets via profiles. It is what it is for now.

Mike

 

[KC3BJE]

Thank you!!