Strange how yesterday my PSR800 stopped receiving. For over an hour it was silent during rush hour. I thought something was up. I hooked it to my laptop and again the software was telling me during an update check that I had firmware 1.0. Yet I was running 1.7. Something keeps haunting my scanner yet I've only had it a little over a month. This is the second time it has told me I was running firmware 1.0. after the scanner starting acting up or stopped working.
Fed up I uninstalled the EZ Scan software yet again and went back to the original that came on the CD. I followed the instructions in the recent beta updates to revert back to the previous firmware updates. Beta can sometimes be a good thing, but I don't like the odd things that have been happening lately.
I even deleted some of my trunk systems and that was odd too. When importing them again some of the TGID names didn't match how they were labeled on RR or my previous labeling in the software. Where did the names come from? I don't know who is responsible for that happening.
Then I heard a fire dispatch and waited to hear the rest of the call but it switches to another dispatch for this frequency, one that is more distant in the county. I turned on my ham radio and it was picking it up fine with just a whip antenna on it. The scanner is hooked to a comet discone outside. Then I realized it was because of the attenuator. For these 3 county fire frequencies I programmed in that the attenuator be on since it was the only way they came in before.
This was backward thinking for me at the time. Turning on the attenuator to pick up the most distant stations from me. But it was the only way they would come in. Now when I do that, the signal drops to nothing, but when I turn off the attenuator the signal goes to full scale. Yet another thing that has completely changed from one extreme to another.
Recently other odd things were happening too. I'm going to work on deleting all the trunk systems today and import them again. The other day I went through all my conventional frequencies to check them and make sure everything was ok. I did the same with the trunk ones while doing this, but I'm still going to import them fresh again. I don't think this will help since its the scanner and software that seem to be the root of the trouble, but until I go through all my programming I won't be at peace.
I wonder when this scanner is going to start being consistent. Or when the ghosts in the machine will leave me be.
Fed up I uninstalled the EZ Scan software yet again and went back to the original that came on the CD. I followed the instructions in the recent beta updates to revert back to the previous firmware updates. Beta can sometimes be a good thing, but I don't like the odd things that have been happening lately.
I even deleted some of my trunk systems and that was odd too. When importing them again some of the TGID names didn't match how they were labeled on RR or my previous labeling in the software. Where did the names come from? I don't know who is responsible for that happening.
Then I heard a fire dispatch and waited to hear the rest of the call but it switches to another dispatch for this frequency, one that is more distant in the county. I turned on my ham radio and it was picking it up fine with just a whip antenna on it. The scanner is hooked to a comet discone outside. Then I realized it was because of the attenuator. For these 3 county fire frequencies I programmed in that the attenuator be on since it was the only way they came in before.
This was backward thinking for me at the time. Turning on the attenuator to pick up the most distant stations from me. But it was the only way they would come in. Now when I do that, the signal drops to nothing, but when I turn off the attenuator the signal goes to full scale. Yet another thing that has completely changed from one extreme to another.
Recently other odd things were happening too. I'm going to work on deleting all the trunk systems today and import them again. The other day I went through all my conventional frequencies to check them and make sure everything was ok. I did the same with the trunk ones while doing this, but I'm still going to import them fresh again. I don't think this will help since its the scanner and software that seem to be the root of the trouble, but until I go through all my programming I won't be at peace.
I wonder when this scanner is going to start being consistent. Or when the ghosts in the machine will leave me be.