I have a 536 HP. I just got the GPS receiver. I have it hooked up and working. I'm taking a long road trip across several states for the holidays. Will the 536 keep updating my location and the systems it scans automatically or is there something I have to do to make it update?
The GPS can/will use the full database and will automatically start including and removing whatever is in the full database that meets a combination of your location (per the GPS), your settings (range, service types, etc.), and whatever was entered into the RRDB.
If you just want to hear "whatever" as you go, this will work. But, depending upon the areas you are in, how much and how accurate the data on RRDB is (particularly lot/lon and "radius" information), you may both miss things you want to hear while at the same time stopping on alot of things you don't (including noise and static on old conventional analog frequencies). Additionally, if you have the DMR upgrade, I've found many times that some of those tend to "hang" (stop, won't release). At some point you start saying to yourself - hey, why is it so quiet?
Also - if there is alot of information for a given area (to include nationwide information), the scan rate (time to get all the way through it) may be pretty slow.
As I found and reported
early in this thread (and won't rehash too much), the location/range data for frequencies, systems, sites, and departments are not something most users really consider about or provide when they submit frequency and talkgroup data to RR. As a result, in some cases, some information either lacks location data completely, is inaccurate, and/or is set to some type of default.
Over time, I've attempted (for my local area/state at least) to submit changes for this incorrect or missing information. This improved what I wanted to hear (locally) but not what I didn't want to hear.
What I have found that works best in my situation is to use Sentinel and create a favorites list of the things I do want to hear along my trip route. I then set the favorites list to use the GPS. This combination works better in my opinion (call me a control freak - that's fine). It's a bit tedious and still isn't perfect. On a recent trip across central parts of North Carolina, even with the range set to 0.0, I was still seeing the radio try to scan things in Virginia. There is (or was in the past) also a federal system in the RRDB where the range was set to something like 600 miles (seemed like the right thing to do I guess). At the same time there are other departments", etc. that have their ranges set as low as 1 mile (I think I've seen some set to 0.5).
Perhaps this capability will improve down the road but as long as the data in the RRDB relies entirely on user supplied information and is maintained by a large number of database admins, it's not likely to get all that much better. As UpMan always says - YMMV.