BCD436HP/BCD536HP: Just purchased BC436HP and questions

[UPMan]

How would Sentinel know that a channel is not in a favorites list because you don't want it there? If a new channel appears in the database (relatively frequently) would they just all get added to your FL for you to delete every week?

How would Sentinel know that a channel is in a FL because you know about it, but it isn't in the RadioReference database. If a channel is in your FL that is not in the weekly main dB update, should it be deleted from your FL for you to readd every week?

How would Sentinel know that the channel name in your FL is different because you changed the alpha? If the channel name in the FL doesn't match the weekly update, should it change the alpha back to match the main dB for you to change back every week?

 

[marksmith]

Plus you need to use the Sentinel app for firmware or database updates. Can't do in Butel.

Setting up favorites just like your 396 is very easy. You can create new departments etc in Sentinel for a system and cut/paste chennels to/from departments etc.

You can break out multiple site systems into single sites, etc.

It does anything that Freescan does only you don't have to manually type any alpha tags, etc.

Only people who have not really spent the time with Sentinel to find out all you can do find it difficult. It's the easiest scanner software I have used in 10-15 years and I have used all of them.

Mark
536/996P2/HP1e/HP2e/996XT/
396XT/PSR800/PRO668/PRO652

 

[dsalomon]

How would Sentinel know that a channel is not in a favorites list because you don't want it there? If a new channel appears in the database (relatively frequently) would they just all get added to your FL for you to delete every week?

How would Sentinel know that a channel is in a FL because you know about it, but it isn't in the RadioReference database. If a channel is in your FL that is not in the weekly main dB update, should it be deleted from your FL for you to readd every week?

How would Sentinel know that the channel name in your FL is different because you changed the alpha? If the channel name in the FL doesn't match the weekly update, should it change the alpha back to match the main dB for you to change back every week?

Upman -

All great points. I did a poor job of communicating what I'm asking for.

I set up favorites lists that match entities in the master database. What I'm really asking for is a favorite item that is pointer to the master database. Therefore, when the master database entity is updated, the favorite list pointing to it is also updated. Does that make more sense?

 

[Voyager]

If you want to use the Main dB, just enable the Main dB.

 

[UPMan]

Well, while it does occasionally happen it is relatively rare that a channel is simply edited. Adds and deletions are pretty frequent. But, if a channel is edited in the main dB, then point #3 remains. If a description for a channel in the main dB changes, how will Sentinel know whether you want to use your current FL's description or the main dB's changed description.

 

[BLAH]

Ok, Now that I have had a chance to really use it for a few hours (before I open my big mouth) I agree, Sentinel is the best program to use for any HP unit, There are some things I still don't like about it / I wish it had, However it's very good software!!

Paul I would suggest (if you have not already) you download it and build your database the way you want now (like I am doing) While your waiting for your radio to arrive And hey there are some cool youtube videos / reviews to watch about the HP,.. https://www.youtube.com/watch?v=qcR25Gs5dlU

Hey great advise as always UPMAN ! I big thanks for all your posts here on RR...

bLAH

 

[mancow]

The ability to directly mod the database and the option to update those edits from database uploads is what makes the GRE software so great.

 

[Voyager]

And how does the GRE SW know what you want updated and what you don't?

 

[mancow]

And how does the GRE SW know what you want updated and what you don't?

There are options presented to you you can choose from.

Do you want to update changed data with labels from the update file... something along that line. I can't recall specifically right now. All I know is is much more flexible and logical in my opinion.

 

[marksmith]

You do get options in EZSCAN and iScan for updating your scanlists based on changes in the database.

One specifically goes to Upman's comment on how would the program know if you want to use your own or the database description. In this case it's checkmark for database, unchecked to keep your own.

A second option asks if you want it to update other database changes.

I always uncheck the first option. If I went through the effort to change it, why would I not want to keep it?

That being said... I usually make manual changes to scanlists or favorites lists so I can determine what is added/deleted/changed.

Mark
536/996P2/HP1e/HP2e/996XT/
396XT/PSR800/PRO668/PRO652

 

[ofd8001]

I still think another column or two needs to be added in the database. That could be used to show whether a channel is added/edited/deleted and the date it was done.

 

[marksmith]

I still think another column or two needs to be added in the database. That could be used to show whether a channel is added/edited/deleted and the date it was done.

This would make sense. I'm sure the info is in the database, just does not show on the site. It would be useful to be able to see the sequence in which talkgroups were added to a system and more particularly which have been recently added and when.

I understand the green coded lines etc and they have a different purpose. Most recent changes to a system might be close to a year ago, beyond when these new entry indicators have turned back off.

The history of changes is there but it does not show what specific changes were made.

Mark
536/996P2/HP1e/HP2e/996XT/
396XT/PSR800/PRO668/PRO652

 

[daveharpe]

How would Sentinel know that a channel is not in a favorites list because you don't want it there? If a new channel appears in the database (relatively frequently) would they just all get added to your FL for you to delete every week?

Make "add new channels" an option. Instead of deleting channels I would lock out the ones I don't want.

How would Sentinel know that a channel is in a FL because you know about it, but it isn't in the RadioReference database. If a channel is in your FL that is not in the weekly main dB update, should it be deleted from your FL for you to readd every week?

Again make it an option - "Purge unknown channels".

How would Sentinel know that the channel name in your FL is different because you changed the alpha? If the channel name in the FL doesn't match the weekly update, should it change the alpha back to match the main dB for you to change back every week?

Option as well - "Reconcile" or something to that effect.

If you didn't want to do options for each permutation how about an option per-FL that says, "Keep systems in sync with RR database". If set, old channels are deleted, new channels are added, modifications are made. Leave the lock status alone. If you have a custom-tweaked FL you unset the option and the update won't touch it.

Pretty much any of these options would be better than the tedious way we have to do it now.

 

[marcotor]

Sentinel and the various flavors of the original GRE based software are so different as to be not Ford vs. Chevy but a bicycle vs. a Harley (your preference which is which).

I would love an option in Sentinel and the 436/536 to use the tags instead of the RR description as I end up editing endlessly things like:

County Services IS Department, Radio Techs and Testing, Southern Division (Patched from EDACS System2 02-1662)

Which of course, is ridiculous to try to display.

 

[mancow]

Sentinel and the various flavors of the original GRE based software are so different as to be not Ford vs. Chevy but a bicycle vs. a Harley (your preference which is which).

I would love an option in Sentinel and the 436/536 to use the tags instead of the RR description as I end up editing endlessly things like:

County Services IS Department, Radio Techs and Testing, Southern Division (Patched from EDACS System2 02-1662)

Which of course, is ridiculous to try to display.

Which was exactly my point in the thread about the database names but for some reason I'm one of the only ones that seem to find this an issue.

The GRE EZSCAN software is by far my favorite.

 

[DataSquid]

How would Sentinel know that a channel is not in a favorites list because you don't want it there? If a new channel appears in the database (relatively frequently) would they just all get added to your FL for you to delete every week?

How would Sentinel know that a channel is in a FL because you know about it, but it isn't in the RadioReference database. If a channel is in your FL that is not in the weekly main dB update, should it be deleted from your FL for you to readd every week?

How would Sentinel know that the channel name in your FL is different because you changed the alpha? If the channel name in the FL doesn't match the weekly update, should it change the alpha back to match the main dB for you to change back every week?

Here's the answer to all of these:

1. Hire a junior programmer
2. Have them google "dealing with merge conflicts ux"
3. Give them maybe a week or two to think about it and prototype something
4. Do anything they recommend, as it can't be worse than what we've got today.

 

[Voyager]

You forgot the step of trying to convince RR to change their data to add timestamps which I bet are not provided in the data DL. RR has a history of not wanting to comply with any one manufacturer to change anything. In fact, I believe it is is a RR policy. So, step 2 won't do much good except show how nice things could be in an ideal world.

 

[Tramagod]

I have had my 436 since this past Christmas, I have had zero problems, which is more than I can say aboutmy Home Patrol 1.

 

[DataSquid]

You forgot the step of trying to convince RR to change their data to add timestamps which I bet are not provided in the data DL. RR has a history of not wanting to comply with any one manufacturer to change anything. In fact, I believe it is is a RR policy. So, step 2 won't do much good except show how nice things could be in an ideal world.

Unless there's some strange license that prohibits it, just timestamp all the entries in Sentinel's DB on import. Then compare diffs on merges. The world is littered with information systems that have had this same problem solved. The frustration is the belief that it's impossible to do. There are several ways, including one that's already been developed, posted to these very forums, and is free to use.

 

[Voyager]

If you timestamp them on import, any merge will see that data as newer even though minutes or days prior you corrected a tag from RR data that was entered years prior. Hence, all your updates will be lost.

It's no different than it is currently where Sentinel just writes any channels that are not 'found' in the FL.

The only way to determine which is newer is to tag on entry (to Sentinel or to the RRDB).