Sentinel: SAME Codes not able to be deleted?

[Computrguy]

This is in Sentinel.
Anyone else have a problem where SAME codes for WX cannot be deleted? Yes, it initially looks like you can place all dashes there but they do not save.
If I leave the Edit Profile screen and come back in the codes that were there previously are back.
I am thinking this is a bug.

 

[werinshades]

This is in Sentinel.
Anyone else have a problem where SAME codes for WX cannot be deleted? Yes, it initially looks like you can place all dashes there but they do not save.
If I leave the Edit Profile screen and come back in the codes that were there previously are back.
I am thinking this is a bug.

Any changes you make, you must go into File..Save prior to writing to scanner.

 

[Computrguy]

Any changes you make, you must go into File..Save prior to writing to scanner.

I get that. But it is still reverting to the prior SAME code. I've tried every way I can to delete it and I cannot.
All other fields seem to be fine.
Can you actually try this in your Sentinel installation?
Edit the WX SAME code. Exit the Edit Profile screen. Save if you like. Go back in the Edit Profile and the SAME code is back.

 

[K4EET]

I get that. But it is still reverting to the prior SAME code. I've tried every way I can to delete it and I cannot.
All other fields seem to be fine.
Can you actually try this in your Sentinel installation?
Edit the WX SAME code. Exit the Edit Profile screen. Save if you like. Go back in the Edit Profile and the SAME code is back.

I've noticed the same scenario with the SAME Codes. Once you populate a field with a SAME Code, the best that you can do if you want to essentially make it "kaput" from alerting is to change it to a SAME Code that is not in your coverage area. I have found no way to actually delete the SAME Code and revert back to dashes.

Perhaps @JoeBearcat could look into that "issue" and suggest a modification to the Sentinel code sometime in the future.

73, Dave K4EET

 

[Computrguy]

I've noticed the same scenario with the SAME Codes. Once you populate a field with a SAME Code, the best that you can do if you want to essentially make it "kaput" from alerting is to change it to a SAME Code that is not in your coverage area. I have found no way to actually delete the SAME Code and revert back to dashes.

Perhaps @JoeBearcat could look into that "issue" and suggest a modification to the Sentinel code sometime in the future.

73, Dave K4EET

Agreed it would be nice if fixed.
There is a workaround. Not convenient but it does get rid of it. I just tried it. Delete the code on the radio then read from the radio into Sentinel and it stayed as dashes.

 

[K4EET]

Agreed it would be nice if fixed.
There is a workaround. Not convenient but it does get rid of it. I just tried it. Delete the code on the radio then read from the radio into Sentinel and it stayed as dashes.

Well that is good to know. I’ll give that a try tomorrow and see if I can get some dashes showing where I want them to and actually stay there. Thanks for the tip!

Calling @JoeBearcat, calling @JoeBearcat. This is @K4EET. Please accept for consideration as a future enhancement to Sentinel some easier method to delete SAME Codes as opposed to @Computrguy’s method which is more complex than a direct deletion algorithm within the Sentinel program itself. Thanks @JoeBearcat!

73, Dave K4EET

 

[dave3825]

I have found no way to actually delete the SAME Code and revert back to dashes.

And surprisingly, pasting 6 dashes back in the box, or typing 6 dashes still reverts to the last numeric value entered.

 

[hiegtx]

And surprisingly, pasting 6 dashes back in the box, or typing 6 dashes still reverts to the last numeric value entered.

I noticed the same, even after 'saving' the profile after entering the dashes to null out the field.

 

[JoeBearcat]

I've noticed the same scenario with the SAME Codes. Once you populate a field with a SAME Code, the best that you can do if you want to essentially make it "kaput" from alerting is to change it to a SAME Code that is not in your coverage area. I have found no way to actually delete the SAME Code and revert back to dashes.

Perhaps @JoeBearcat could look into that "issue" and suggest a modification to the Sentinel code sometime in the future.

73, Dave K4EET

When programming that slot, hit the decimal point then ENTER. It will go back to dashes.

 

[dave3825]

When programming that slot, hit the decimal point then ENTER. It will go back to dashes.

edit:
Decimal point does not work for me either.

Maybe when the correct procedure is established, maybe that wording can be included in any future Sentinel updates?

 

[hiegtx]

When programming that slot, hit the decimal point then ENTER. It will go back to dashes.

That does not work for me, even after saving it.

 

[JoeBearcat]

That does not work for me, even after saving it.

I will check into that. I confirmed the procedure before posting it, but perhaps it is not working on other models.

Which models is it not working on? Or are we only talking about Sentinel?

EDIT: Just re-read the thread and Sentinel was specified. On my Sentinel (currently the latest public release), setting a slot for six dashes (like the original) works.

My previous reply (decimal point - ENTER) is for the scanner keypad entry.

 

[hiegtx]

I will check into that. I confirmed the procedure before posting it, but perhaps it is not working on other models.

Which models is it not working on? Or are we only talking about Sentinel?

EDIT: Just re-read the thread and Sentinel was specified. On my Sentinel (currently the latest public release), setting a slot for six dashes (like the original) works.

My previous reply (decimal point - ENTER) is for the scanner keypad entry.

I’ve tried the “six dashes” in Sentinel, and the code resurfaces, even if I try to save the changes. I have not tried to do the ‘deletion’ directly on the scanner via the keypad.

When I get back home later today, I will verify that I do have the latest version. (I think I already have it, from the last noted update that was posted, but wii recheck.)

 

[Computrguy]

I will check into that. I confirmed the procedure before posting it, but perhaps it is not working on other models.

Which models is it not working on? Or are we only talking about Sentinel?

EDIT: Just re-read the thread and Sentinel was specified. On my Sentinel (currently the latest public release), setting a slot for six dashes (like the original) works.

My previous reply (decimal point - ENTER) is for the scanner keypad entry.

This is my version and the six dashes does not save when I come back into the Profile
2.03 (revision 00)

 

[JoeBearcat]

I see that now. It deletes them but does not write them to the profile when saved.

I'll add that to the list, but in the mean time you can just use a code from Hawaii or something that is far from your area.

 

[fxdscon]

I see that now. It deletes them but does not write them to the profile when saved.

.
This takes a minute to setup, but if you really want the dashes back where they were without having to delete the code through the scanner's menu system and then reading it back into Sentinel, this is a quick and easy work around for now until Sentinel is updated...

Look in Windows Explorer to find the "profile.cfg" file for the profile you are currently using in Sentinel. Put a shortcut to it (not a copy) on your desktop where it's easy to get to. (Make a backup copy of that file before editing it if you like.)

With Sentinel NOT running, open that "profile.cfg" file in a text editor and place the 6 dashes in place of a code in the "SAME" section near the top as shown in the pic. "Save" the changes to that file and close it, and when you start Sentinel again the dashes will be there when you open the Sentinel profile editor.





To find where your Sentinel profiles are stored on your computer: from the Sentinel tool bar...... tools ---> options ---> the path to your profiles is shown under "Sentinel Folder". Look in that folder for the "profile" sub folder, then open the sub folder there that has the name of the profile that you are currently working with in Sentinel. You'll see the "profile.cfg" file in there.

 

[Computrguy]

That's good info fxdscon.
I did a search. I have 45 profiles because I travel all over the country and have a SDS100 and a BCD436. That's a lot of links and updates on my desktop
Hopefully a fix will be done for the next version of Sentinel.

 

[fxdscon]

This is in Sentinel.
Anyone else have a problem where SAME codes for WX cannot be deleted? Yes, it initially looks like you can place all dashes there but they do not save.
If I leave the Edit Profile screen and come back in the codes that were there previously are back.
I am thinking this is a bug.

I see that now. It deletes them but does not write them to the profile when saved.

I'll add that to the list, but in the mean time you can just use a code from Hawaii or something that is far from your area.

Just checked in the new version of Sentinel (BCDx36 - v2.05.03), and this bug is still there. I guess they didn't consult "The List".

 

[mc48]

Just enter all Zeros and replace the name with SAME X.

 

[K4EET]

Is this topic still an issue with Sentinel? I have the Uniden BCD536HP and would like to delete some SAME codes. TIA! Dave K4EET