Sentinel 2.00.01 (NXDN and SDS100 Support)

[Jay911]

Some of you people act as if it's unreasonable to expect you to spend 2 minutes reading all the posts in this thread, where every question you have has been answered.

You don't "start up" Sentinel in a mode for any radio. The profile you last used is what determines what radio type is used. The reason it asks you when you start the program for the first time is because you've never told it before, and it needs to know so it can write the profile for the first time.

You set the target model from the Tools menu on the main page of Sentinel, not in the Miscellaneous section of a random profile. The display editor is accessed from the Edit menu on the main page of Sentinel, when the target model is set to SDS100.

All of this is either posted in this thread or intuitively obvious if you spend 90 seconds thinking about it.

 

[phask]

I'm only using ONE profile for both radios, as far as I can tell, no issues.


If I find any I'll use 2 profiles.

 

[UPMan]

Are you trying to change the display fields and colors? Click on the colored icon in the main icon bar, not in settings editor.

 

[jonwienke]

The only difference is the availability of display settings that are unique to a particular model. So if you specify x36, you can't adjust the display colors and layout for the SDS-100, and if you specify SDS-100, you can't flip the display of a 536 upside-down.

 

[nd5y]

Is anybody using Sentinel successfully on WINE/Linux?

 

[garys]

That is a much better explanation than the others have given.

Are you trying to change the display fields and colors? Click on the colored icon in the main icon bar, not in settings editor.

 

[wm8s]

Is that a scanner or a pride flag?

Uniden Pride!!

 

[jonwienke]

 

[wm8s]

Maintaining separate profiles, with separate FL statuses, sort orders, etc., is going to be a pain. What are the exact consequences of selecting the Target Model? I.e., what happens if I just have one profile, and immediately before I do Scanner / Write to Scanner, I select the correct target model b/w my 436, 536, and 100?

...R

 

[jonwienke]

Maintaining separate profiles, with separate FL statuses, sort orders, etc., is going to be a pain. What are the exact consequences of selecting the Target Model? I.e., what happens if I just have one profile, and immediately before I do Scanner / Write to Scanner, I select the correct target model b/w my 436, 536, and 100?

It's not a pain. Switching profiles is a couple mouse clicks, no more of an inconvenience than changing the Target Model setting. I maintain separate profiles for my 436 and 536, a profile for a friend's 436 who isn't super computer savvy, a profile for the SDS-100 on the way, as well as a temp profile I use to load customers' scanner configurations. Just give the profiles obvious/sensible names, and it's no more of an issue than having multiple Word documents with slightly different contents and different names.

Note that Favorite Lists are not part of a profile, so changes to a Favorite List will be reflected in all profiles that are configured to use that Favorite List.

Also, Save As is an option if you want to transfer settings from one profile to another.

 

[wm8s]

It's not a pain. Switching profiles is a couple mouse clicks, no more of an inconvenience than changing the Target Model setting. I maintain separate profiles for my 436 and 536, a profile for a friend's 436 who isn't super computer savvy, a profile for the SDS-100 on the way, as well as a temp profile I use to load customers' scanner configurations. Just give the profiles obvious/sensible names, and it's no more of an issue than having multiple Word documents with slightly different contents and different names.

Note that Favorite Lists are not part of a profile, so changes to a Favorite List will be reflected in all profiles that are configured to use that Favorite List.

Also, Save As is an option if you want to transfer settings from one profile to another.

All true, but it doesn't answer my question. It's not simply switching profiles that's going to be the problem; it's keeping multiple profiles synchronized --- that is, I don't want any differences among my scanners --- that's going to be extra work if unnecessary. If I have to maintain separate profiles for the two separate models [x36 v 100], then when I change something in one of them [e.g., FL sort list, QKs enabled, etc.], I'll have to go change it in all of them. All I need to know is, are there any consequences if I just maintain one profile, and select the Target Model immediately before programming? Thanks.

 

[wm8s]

PS Also, just for you, I have turned off the pride flag on my 536

 

[jonwienke]

The File \ Save As menu copies a profile's settings to another profile.

Switching Target Model risks having your display settings reset to default. Not a big deal for x36, but a potential major PITA for the SDS-100. My recommendation is to have the SDS-100 profile be the "master" since it has the most custom settings, and Save As the x36 profile if you need to copy a bunch of profile settings. If you change a Favorite list you don't need to redo profiles because a Favorite List is its own separate entity.

 

[phask]

So far - I'm using ONE profile for both - just changing the target.


Seen no issues so far.

Maintaining separate profiles, with separate FL statuses, sort orders, etc., is going to be a pain. What are the exact consequences of selecting the Target Model? I.e., what happens if I just have one profile, and immediately before I do Scanner / Write to Scanner, I select the correct target model b/w my 436, 536, and 100?

...R

 

[jasonhouk]

All true, but it doesn't answer my question. It's not simply switching profiles that's going to be the problem; it's keeping multiple profiles synchronized --- that is, I don't want any differences among my scanners --- that's going to be extra work if unnecessary. If I have to maintain separate profiles for the two separate models [x36 v 100], then when I change something in one of them [e.g., FL sort list, QKs enabled, etc.], I'll have to go change it in all of them. All I need to know is, are there any consequences if I just maintain one profile, and select the Target Model immediately before programming? Thanks.

I just tested your scenario and using the 436's profile written to both, results in loss of customization on the SDS100's screen which reverted back to default simple display and nothing more.

Also used the SDS100's profile and wrote to both and I lost the UID setting on the 436.

I'll advise if I find anymore anomalies using the SDS's profile

Houk

 

[jonwienke]

I just tested your scenario and using the 436's profile written to both, results in loss of customization on the SDS100's screen which reverted back to default simple display and nothing more.

Also used the SDS100's profile and wrote to both and I lost the UID setting on the 436.

That's exactly what I expected. The display settings unique to each model get reset to their defaults when you switch Target Model.

 

[wm8s]

So far - I'm using ONE profile for both - just changing the target.


Seen no issues so far.

Thanks. Jon had a good point about the display options, so I did some snooping. When you change the Target Model to SDS100 in Sentinel, Sentinel actually changes the ProductName parameter in the current profile's profile.cfg file to SDS100 (and curiously leaves the TargetModel parameter equal to BCDx36HP). Sentinel does not prompt you to save this change, I assume on the premise that it's really not a "profile change".

If you change one of the SDS100-specific display info items or colors, it also [and expectedly] saves this in the profile.cfg and does prompt you if you want to save it if you exit with the dirty bit set.

Most importantly, changing the Target Model in Sentinel (i.e., the ProductName file parameter, not the TargetModel parameter) to BCDx36 does not delete the SDS100-specific display info and color options parameters from the profile.cfg file.

So it seems like I'll be OK with one profile [YMMV].

...R

 

[allend]

[emoji23][emoji23]


Sent from my iPhone using Tapatalk

So is this a joke with customizing your screen with different colors or not? Also, is there an official release notes on the latest firmware upgrade for the 536? Just curious what the firmware upgrade was suppose to fix

 

[KE4ZNR]

So is this a joke with customizing your screen with different colors or not? Also, is there an official release notes on the latest firmware upgrade for the 536? Just curious what the firmware upgrade was suppose to fix

The only scanner with adjustable screen colors is the SDS-100. Period.
This is why folks need to be careful when making jokes.
Marshall KE4ZNR

Sent from my Pixel XL using Tapatalk

 

[garys]

From the first email announcing the release of 1.22

1.22.00 Release Notes (06/01/2018)

Improved false TGID display on DMR systems
Modified LCN finder
Fixed an issue where avoided sites were being scanned

So is this a joke with customizing your screen with different colors or not? Also, is there an official release notes on the latest firmware upgrade for the 536? Just curious what the firmware upgrade was suppose to fix