add if possible database compare

[mrscanner2008]

Is it possible to add when you are in custom search or close call and the scanner stops on a frequency to go and check in the scanner database to see who owns this frequency if it is already in our database?

example: custom search 410-420 mhz, the scanner stops on the frequency 411.1025 in max capacity and displays the name of the system since it is already programmed in the scanner or if it found new frequency display no database match.

I think I've already seen a comparison function with the radio database but I'm not sure if it was Uniden.

thanks

[Ubbe02]

In Discovery mode you have a "compare to database" function, that was working in very old firmwares but Uniden broke that code many years ago and I don't know if they have restored a working function. But if it works then when the scanner loads a new frequency to monitor and its active and it goes to the Alice file to check if it needs a decryption key, it could after that process then use the "compare to database" firmware code, if the Alice file had that feature set, to find a match from the DB, and the original Uniden code also checks your favorite list. I don't know how much extra time it will take to check the DB, it could slow down the normal process of unmute and present display texts.

But what should it do if it finds a match, and it originally only finds the first match and set a flag "Yes, already in DB or FV" and ignores all others that might exist in the DB. If that would be enough, to just have an indicator that the frequency do exist in the DB then it can be a simple addition. But if you want it to show what system the frequency belongs to then it is a much more complicated process and especially if the first frequency match in the DB isn't the one you wanted to see.

With all feature and function addition requests you should try and write a flow diagram what exactly the scanner should do. Something like this:

1. When scanner encounters any active frequency, exactly as in the CFT/Alice decryption key loading, it should also check the DB for that frequency, perhaps using Unidens original firmware code segment from Discovery mode, but not do it in scan mode and only during search or CloseCall.
2. If frequency are found in DB then do this and do that. Could include to also ignore that frequency and continue search.
3. On the display row# show this and that.
4. Display clears as in the normal way when search mode continues or CloseCall after a keypress.

Uniden uses a frequency list of all systems when doing Auto Locate in location controlled scanning of the DB. It might be that the "Compare to Database" function are using that much smaller list than the whole DB when comparing a frequency to the DB. Then a function to only indicate "Yes, it is in the DB" flag will be possible.