rvawatch said:
So it sounds like there is some problems with the STAT mode actually recognizing all the sites or something.......
To recap and add to the above:
Like I said earlier, I'm also seeing the same thing. STAT seems to be skipping some sites. What's weird is that often it'll lock on to more distant sites with weaker signals than those that it usually skips which are stronger. When I set it to ROAM, it locks on right away to that main strong site (our Zone controller) and stays there tracking perfectly. If I program each site individually (the old scanner way), it'll track that site and all the other sites just fine.
The latest find and most interesting one is: using Mike V.'s latest Pro96Com software that supports the PSR-500, I've logged info for at least 6 or 7 sites. But when I try to track one of those very sites that gets skipped by the radio in STAT mode, the program runs for a few seconds and quits with no apparent reason or error message. It does it over and over again with that particular site(s). Then I go back and track a different site and it works just fine with Pro96Com.
So I don't know if that's a clue or just coincidence. And if it's possible some sites out there are putting out some sort of OSW that the radio and software doesn't like or gets them confused. I remember Uniden having a similar problem in the past when some of our sites got upgraded to the latest Motorola software (7.x) that supported Multi-Packets. One day the BCD396T was working and the next day after the update, it couldn't reliably lock on to TGs on any of those sites. It couldn't decode the SysID either (it did before the upgrade) just like the Pro-96 and now PSR-500 still can't today. I'm also wondering if this is also somehow related to the other decoding/tracking problems that started this thread.
Sorry for the rambling. Just trying to brainstorm my observations (and crazy ideas)....