SDS100/SDS200: Understanding User Edits - Reading / Writing Between PC and SDS100

[rkillins]

I will be honest, I am struggling with understanding the concepts and processes involved with using Sentinal software with my SDS100. For that, I apologize if I look stupid or fail to explain myself clearly or with the right terminology.

I have made my favourites lists using data from the master database. I haved made edits withion my favourites lists, changing name tags and settings for example.
When I start writing back to the scanner, there are several interruptions in which I am advised that {specific favourite list} is different on unit, and provides 3 option to proceed. Copy and replace on scanner, copy with new name or skip.

What is the best choice here? I'm not sure what effects each option has on the final transfer to the scanner, or the software? Clearly I want to carry over my customizations? What is being compared to determine things are different?

Going the other way, uploading from the scanner to the PC, I get the same interruption, with data on the PC being different. I\m not sure what to do to avoid loosing my customizations.

On another note, how (if possible) to I update my favourites lists to reflect changes made in the master database (ie new talkgroups added to a trunk system) without affecting my customized favourites? In other words, simply assessing a system for changes and appending changed/added information?

My apologies again for failing to understand what is likely very basic.

 

[werinshades]

Once you make changes to your programming, in Sentinel..File..Save...Write to Scanner (Copy and Replace in Scanner).

If you made changes on the scanner..open Sentinel...Read from Scanner (Save to PC).

To change favorite lists to reflect database update(s) on Sentinel...Edit..Edit Favorite List...Highlight System you're updating in left pane...Department...add/delete/modify there. Once you're done...File..Save..Write to Scanner (Copy and Replace on Scanner).

This is my preferred way of programming since you don't have to wait for the weekly database update but still use the information.

 

[rkillins]

Hi werinshades, thank you for your reply. What do you do when prompted during writing of changes? I'm not sure the effects of each of the three options ... Copy and replace on scanner, copy with new name, or skip.

 

[werinshades]

Hi werinshades, thank you for your reply. What do you do when prompted during writing of changes? I'm not sure the effects of each of the three options ... Copy and replace on scanner, copy with new name, or skip.

I thought I mentioned that in my post...(in parenthesis). That means any changes you made will be sent to the scanner or the PC. If you make any changes via Sentinel...File..Save before writing to the Scanner.

 

[rkillins]

Oh, ok. So replace on scanner essentially "clears" the existing data and replaces it with whatever data is coming in from sentinal (incl. new edits). I assume that Skipping retains the existing data and doesn't carry any changes over. Copy with a new name essentially creates a new favourite ... the one with changes while still keeping the original on the scanner.

I understand. I'm still trying to understand the updating of existing favourite lists to accomodate changes from the master database. If I click on the system I want to update from the master database, opt to "Append to favorites list", and select the appropriate favourite list, the changes are carried over. However, if it's a system in which I customized things differently than what's in the master database, I get duplicate info in that favourite list. My customized labels are retained, but that same talkgroup is imported to that favourites list again (appended) in it's orginal form from the master database. I'm looking for a way to add just the changes not reflected in my favourites list. This works, but requires me to manually go through the favourite list to delete the duplicates from the master DB.

It might be just as effective/easier to manually enter changes as they happen as you suggest.

 

[werinshades]

Oh, ok. So replace on scanner essentially "clears" the existing data and replaces it with whatever data is coming in from sentinal (incl. new edits). I assume that Skipping retains the existing data and doesn't carry any changes over. Copy with a new name essentially creates a new favourite ... the one with changes while still keeping the original on the scanner.

I understand. I'm still trying to understand the updating of existing favourite lists to accomodate changes from the master database. If I click on the system I want to update from the master database, opt to "Append to favorites list", and select the appropriate favourite list, the changes are carried over. However, if it's a system in which I customized things differently than what's in the master database, I get duplicate info in that favourite list. My customized labels are retained, but that same talkgroup is imported to that favourites list again (appended) in it's orginal form from the master database. I'm looking for a way to add just the changes not reflected in my favourites list. This works, but requires me to manually go through the favourite list to delete the duplicates from the master DB.

It might be just as effective/easier to manually enter changes as they happen as you suggest.

For the reasons you mentioned is why I program the way I do. I also add/update Unit ID's (Radio ID's) frequently too. I find it easier and I learn the programming on the scanner a little better. I also create new Favorite Lists manually, but use the information submitted from the database and update as I described.

If your programming is a mess with Appended Favorite lists, duplicates and you want to clean it up and use your programming only, Delete the Favorite list(s) in the left pane..Write to Scanner, and when the box comes up..Erase all Favorite Lists. You'll be prompted to confirm the change, click yes, and it's all your programming.

 

[rkillins]

Perfect! Curious, you mentioned that you work with unit id's. I've been looking at that as well, but again not familiar with their purpose. If I program a specific unit ID, for instance a police dispatch console, where is it used (displayed) on the SDS100? I have all data displayed on my SDS100, and UID populates with the number. If I associate that number with a unit ID in Sentinal, will that number then be replaced by the tag? I have tried, but have yet to see that unit active to see for myself.

 

[werinshades]

Perfect! Curious, you mentioned that you work with unit id's. I've been looking at that as well, but again not familiar with their purpose. If I program a specific unit ID, for instance a police dispatch console, where is it used (displayed) on the SDS100? I have all data displayed on my SDS100, and UID populates with the number. If I associate that number with a unit ID in Sentinal, will that number then be replaced by the tag? I have tried, but have yet to see that unit active to see for myself.

You can replace Unit ID with Unit ID with name. If Radio ID 100001 is Engine 1 apparatus and you add that information, it will display where the Unit ID is or wherever you decide to move it to. Keep in mind, and I preach this to friends who make changes, any changes you make prior to Write to Scanner..File/Save.

 

[rkillins]

Great advice. Thank you for helping me further understand this complicated radio.

 

[werinshades]

Great advice. Thank you for helping me further understand this complicated radio.

Have fun..let us know how it goes.

 

[ECPD279]

FYI, Sentinel (as well as ProScan) will throw the notification for ANY change. Even if you write to the radio, then turn a few lists on / off and read it back it will be "different". The technique of reading the radio, making adjustments, then writing back to the radio is pretty much the standard in the professional radio world. In that way you get to keep any programming or settings changes you've made manually while using the radio because you'll read it back before changing anything in Sentinel. I get the notifications every single time I read or write my radios. I just click the box and accept all, secure in the knowledge I'm using the most current information.

Also, there is NOTHING about these radios that is in ANY WAY basic. Don't feel the least bit bad for asking questions.

 

[werinshades]

FYI, Sentinel (as well as ProScan) will throw the notification for ANY change. Even if you write to the radio, then turn a few lists on / off and read it back it will be "different". The technique of reading the radio, making adjustments, then writing back to the radio is pretty much the standard in the professional radio world. In that way you get to keep any programming or settings changes you've made manually while using the radio because you'll read it back before changing anything in Sentinel. I get the notifications every single time I read or write my radios. I just click the box and accept all, secure in the knowledge I'm using the most current information.

Also, there is NOTHING about these radios that is in ANY WAY basic. Don't feel the least bit bad for asking questions.

I think the OP is asking how to manually make a change in Sentinel and write it to the scanner?

 

[drdispatch]

Merely updating the database in Sentinel will not change your Favorites Lists. Let's say you create a Favorites List, and you change the name of a system in that Favorites List. Then after a subsequent database update (or perhaps you are on the database page on RR), you notice some new talkgroups on that system. So you append those new talkgroups to your Favorites List. What Sentinel does is create (what it perceives is) a new system in your Favorites List, because by changing the name when you originally added it, Sentinel sees it as a different system.
The way around that is simple: Copy and paste those new talkgroups from the new system into your original system.

 

[werinshades]

Merely updating the database in Sentinel will not change your Favorites Lists. Let's say you create a Favorites List, and you change the name of a system in that Favorites List. Then after a subsequent database update (or perhaps you are on the database page on RR), you notice some new talkgroups on that system. So you append those new talkgroups to your Favorites List. What Sentinel does is create (what it perceives is) a new system in your Favorites List, because by changing the name when you originally added it, Sentinel sees it as a different system.
The way around that is simple: Copy and paste those new talkgroups from the new system into your original system.

I just tried to do this as an experiment and as you posted, it creates an entire new system even if you want to add one new talk group. Once you copy and paste that talk group, you have to delete the new system: Edit..Edit favorite list..choose the system, X (deletes it)..File..Save..Write to Scanner. It's another way to do it, but seems like a lot to do so little.

 

[drdispatch]

I just tried to do this as an experiment and as you posted, it creates an entire new system even if you want to add one new talk group. Once you copy and paste that talk group, you have to delete the new system: Edit..Edit favorite list..choose the system, X (deletes it)..File..Save..Write to Scanner. It's another way to do it, but seems like a lot to do so little.

Yeah, I pulled the trigger on that post a little too soon, before realizing that I had left out that part. Plus it was past my bedtime...

Excuses aside, if you have to add a lot to a system, the method I outlined works well. If you're just adding 1 or 2 new talkgroups, it is easier to just manually add them to the appropriate system. Once a year or so I update my Favorites Lists using the method I outlined, just to make sure that I've got all the talkgroups that I want & any new frequencies which have been added to sites.

 

[werinshades]

Yeah, I pulled the trigger on that post a little too soon, before realizing that I had left out that part. Plus it was past my bedtime...

Excuses aside, if you have to add a lot to a system, the method I outlined works well. If you're just adding 1 or 2 new talkgroups, it is easier to just manually add them to the appropriate system. Once a year or so I update my Favorites Lists using the method I outlined, just to make sure that I've got all the talkgroups that I want & any new frequencies which have been added to sites.

No problem, that's why I gave it a try. I can understand some of the confusion people experience when that's the only method they know. If you don't delete the system, you'll be scanning alot more than they expected.

Another reason I recommend users should become familiar with editing things themselves is the database download only takes place on Monday. If I understand this correctly, the updated talkgroup/site etc won't appear in the database download pull until the following Monday. If an important update is submitted on Tuesday and your unfamiliar with the manually editing process, you'll have to wait. Just my way preferred method as I mentioned.

 

[hiegtx]

No problem, that's why I gave it a try. I can understand some of the confusion people experience when that's the only method they know. If you don't delete the system, you'll be scanning alot more than they expected.

Another reason I recommend users should become familiar with editing things themselves is the database download only takes place on Monday. If I understand this correctly, the updated talkgroup/site etc won't appear in the database download pull until the following Monday. If an important update is submitted on Tuesday and your unfamiliar with the manually editing process, you'll have to wait. Just my way preferred method as I mentioned.

The database download, to Uniden from RadioReference actually takes place on Sunday. While I don't know the exact start time, the late UPMan had indicated it was done, state by state, in alphabetical order. Once the download is done, it's processed into the database update that is made available normally mid-morning on Mondays. So if the update has been done by the time 'your' state is processed on Sunday, it will be in that weeks update for Sentinel.

In general, I monitor my systems, counties, and agencies of interest, and adjust my programming files as needed. Most times, I only need to change a handful of entries, if even that many, during a normal week. The exception would be when there is a major change in one of the trunked systems, with a large number of new, or modified, talkgroups involved. That's very rare in my area.

 

[werinshades]

The database download, to Uniden from RadioReference actually takes place on Sunday. While I don't know the exact start time, the late UPMan had indicated it was done, state by state, in alphabetical order. Once the download is done, it's processed into the database update that is made available normally mid-morning on Mondays. So if the update has been done by the time 'your' state is processed on Sunday, it will be in that weeks update for Sentinel.

In general, I monitor my systems, counties, and agencies of interest, and adjust my programming files as needed. Most times, I only need to change a handful of entries, if even that many, during a normal week. The exception would be when there is a major change in one of the trunked systems, with a large number of new, or modified, talkgroups involved. That's very rare in my area.

That's why I think it's important to learn how to program yourself and not depend on the database to import. Editing/adding information doesn't have to wait till Monday if a change is made on Tuesday and it happens to be something important to you. I also see database entries with question marks in talk group description areas, and while I understand the submitter isn't sure, having ??? looks a little messy to me and I never program them in.

To each their own I say...if you get it to the way you want it, then that's why it's your scanner and not mine. Hopefully someone else reading this who might have been unsure how to edit or add might give it a try?

 

[Solidus]

There are a lot of good tips in here. As another new user, I appreciate it!

I must say, I expected Sentinel to be a bit smarter about this stuff. Like, if I add a particular system from the database as a favorite, and then the frequencies for that system change in a database update, I figured it would propagate those changes to the favorites list.

Short of that, it could at least do an audit to show you what has changed. Maybe a flag next to things that are out of date, or a color coding system, so I’d know that I need to replace them. Having to religiously monitor this site for changes is not the best. I’m sure I’ve missed some changes and have outdated entries as a result.

 

[JoeBearcat]

The SW would have no way to know if the changed data was changed by you or changed by updates.
(scenario is that you change a site name then the update changes it back ad infinitum)

Yes, the flag is a possibility, but that would be very involved and there are much bigger fish to fry right now.

You can just make a new FL for a system and compare that to your FL.