This happen to you? PRO-96 oddity

[AZScanner]

OK, do this - scan your favorite 9600BPS system, then when it's locked onto the CC, hit the manual button. Hear that noise? See the display? Now imagine all these events happening except you never hit the manual button, infact you never touched the scanner at all. And instead of seeing a decode rate on the screen, that line is blank. Sometimes, but not always, the MO on the display changes to a DG but the CC channel noise continues. That's what's happening to mine.

It only happens sometimes and usually hitting scan will fix it. Sometimes it takes a few presses of the scan button before it takes. Sometimes one press is all that is needed for the scanner to go "oh yeah, sorry" and resume normal operation.

Bug? Undocumented feature? Figment of my imagination? Wondering if anyone else is having a similar problem.

-AZ

[mikey60]

I've seen this, but usually after turning a scan bank on or off..

Mike

[n4voxgill]

In the back of my house, the signal strength is marginal and occasionally the scanner will drop the signal, when it does it locks onto the control channel, but not in trunked mode so i hear the noise. I hit trunk and it goes back into normal trunktracking mode. It is a problem with weak signal in my case not the scanner.

[AZScanner]

Originally Posted by n4voxgill

In the back of my house, the signal strength is marginal and occasionally the scanner will drop the signal, when it does it locks onto the control channel, but not in trunked mode so i hear the noise. I hit trunk and it goes back into normal trunktracking mode. It is a problem with weak signal in my case not the scanner.

I suspect this is the case with mine also. It usually only happens when I'm monitoring the Phoenix/Mesa DTRS. It wouldn't suprise me in the least that the signal quality is crap - the whole damn digital system sucks with the raw, cavernous, insatiable sucking power of a galactic black hole.

Yes, for those keeping score at home, that's one point for "AZ doesn't like it". Better yet, mark it as 2.

Actually, if you can pull in a decent quality signal it's not too bad. But the conditions vary from day to day, and I find, especially on my 796D, that I constantly have to fiddle with things to receive comm's reliably. It's rapidly taking something "fun" and making it "work" - but unlike "work", where I'm at least compensated for my time, I paid a buttload of money for these 2 radios that seem to only work when they want to. I love the idea of the 396, but at the same time I'm going to wait until I can see one in action here in Phoenix for myself before I plunk down another $500 on one of these "toys" again.

Thanks for the input.
-AZ