Default to ID Search in Full Database

[DataSquid]

I'm not too sure the logic behind using ID Scan for Full Database systems. If I'm using the Full Database, I want to discover everything out there. More is better. Even unidentified TGIDs. So why not have ID Search as the default for all systems in the Full Database? I'm getting a little sick of having to create a new FL every week just to go and flip this bit for every system in my area.

 

[Jay911]

I don't think you'd want to default it to on for everyone. There's a lot of people who aren't interested in hearing everything, and only want what is programmed into the DB.

It would certainly be nice if you could configure the radio (any HP radio, that is) to do ID search on a per-system basis, but the way Uniden stores and uses the database doesn't seem to allow for it. Hopefully they can look at that after they sort out all the other messes they're in.

 

[DataSquid]

Why isn't everything programmed into the database?

 

[Voyager]

Because everything is not known or not submitted.

I fall in the middle - sort of. There are times I want to hear specifica things and times I want to hear everything. I have one FL programmed for ID SCAN and another for ID SEARCH.

I'm sure if the full dB defaulted to ID SEARCH you would see a ton of posts "What are all these strange numbers and how do I get rid of them? I don't want to hear the trash collectors!"

 

[DataSquid]

Exactly. And some friendly DB admin will add it, and tell the noob how to avoid it in the meantime/avoid the service type after the next DB update. No pain, no progress.

 

[dave3825]

I have 1 FL and set everything to Id search. I lock out/avoid.everything I have no interest in hearing. If something new pops up, I know instantly. If it's interesting I save it and alpha tag it. If it's not of interest, it gets the permanent avoid..

Pretty simple and effective.

 

[marksmith]

It would certainly be nice if you could configure the radio (any HP radio, that is) to do ID search on a per-system basis, but the way Uniden stores and uses the database doesn't seem to allow for it. Hopefully they can look at that after they sort out all the other messes they're in.

Not sure I understand. I change my HP-1 and HP-2 back and forth between search and scan on a per-system basis all the time. Doing it on a per-system basis is the only way that you can do it on any scanner. I do have the extreme upgrade in both radios and this capability might be part of that.

Mark
536HP/HP1e/HP2e/996P2/996XT
996T/396XT(2)/PSR800/PRO668

 

[Jay911]

Not sure I understand. I change my HP-1 and HP-2 back and forth between search and scan on a per-system basis all the time. Doing it on a per-system basis is the only way that you can do it on any scanner.

I assure you, in the main database (not in favorites lists), you do not have the ability to set any HP radio to ID search.

 

[DataSquid]

I have 1 FL and set everything to Id search. I lock out/avoid.everything I have no interest in hearing. If something new pops up, I know instantly. If it's interesting I save it and alpha tag it. If it's not of interest, it gets the permanent avoid..

Pretty simple and effective.

Great idea! Thanks!