I bought an RX65 direct from Bel end of October and sent it back about two weeks later for service due to what I felt was very poor/intermittent k sensitivity. I was getting almost no k band readings compared to my 980. Tested it out at the mall, etc - even with it set on HWY pointed right at the mall entrances I was getting 1 or 2 bars, or no reading at all on the RX65 - but my 980 was blaring away at full strength.
Called Bel and got a bunch of blah, blah, "better filtering" talk from the first customer service rep, so I went and did some more testing. Same results - and yes, I made sure to not run with both detectors on at the same time. Called them again and they had me send it back. They replaced the antenna, updated to the newest firmware, and re-calibrated it.
Seemed to work better; but just this Saturday I was going down a road where I know there's a speed cam, and was very surprised when the RX didn't pick it up til I was almost on top of it (still running in HWY mode). Then on the return trip it didn't pick it up at all. The 980 used to pick it at least a 1/4 mile out, and picked it up even coming up behind it, and from the rear.
I drove back & forth about 6 times with mixed results all the way from no reading at all on some drive by's - to almost full strength on others. I even took a picture of the sign flashing away with a speed displayed of a passing car by with me parked about 300ft directly in front of the camera - and the detector showing NO reading at all. On another pass I stopped in front of the sign sitting in the same area with no signal, and then about ten second later it started ramping up in signal til it was full signal and stayed there. My experience with this sign is that it has always been a pretty strong C/O signal.
I called BEL when I got home and the Cust Svc rep tried telling me that the sign was probably calibrated wrong and that maybe it was fading in and out of the wrong frequency..... WHAT??? I also mentioned that the detector has flashed "SELF CAL" about 4 or 5 times in the past week, which it never did before. He told me that was normal and it was just calibrating itself for optimum preformance, and tried telling me that if it was reading in some places, and not in others, that there was nothing wrong with the detector.
Is this guy full of BS or what?