Hi! I have a problem with a CPE where it won’t connect after I peak the reception to about -71. Once this is done we try to connect using Winbox, the system says “searching for network”. Push the CPE out of line, down to about -80, will immediately connect. When connected, low CCQ, bouncing around 50%. But it will stay connected.
The CPE is a RB411/ R52H in a 19dB 2.4 Rootenna. The AP is a RB433AH, R52H, and a 16 dB, 95 degree sector. Not a bad line of sight, skimming the treetops at the AP, about 5 km link.
The AP has Version 3.30, not sure of the CPE version.
I have some very smart guys helping me out, and so far no one has been able to put their finger on this problem. We thought we had it licked yesterday, with “adaptive noise immunity” settings but the thing dropped back off line about an hour later. We’re out in the sticks where the noise floor is about -105.
Has anyone else seen this issue or can offer suggestions?
Thanks,
Jon.
Strange. Looks like some problem related to Freznel zone or multi-path problems…or who knows… Try moving something, like putting the CPE higher or somewhere else…
What is link distance.
What is SNR in both circumstances.
Please forward a link to the manufacturers polar diagram plot.
in the meantime, try other polarisation. Or even 45 degrees.
I know of no antenna that does not have side lobes, maybe in one direction you are also peeking an interfering signal on a side lobe. Trying an alternate polarisation may change that.
My opinion of the R52h is not so good, however in the absence of my supplier not having stocks of R52, I had to again take another batch of R52h… (I hope it wasnt a mistake)
Please read former posts relating to the failures of the R52h.
Hi,
We found the problem last night (correction: my Real Smart Guy found the problem).
It was the connect list. There shouldn’t have been anything in there but someone in the past put in the following:
-95 to -35 dB: connect: yes
-80 to -35 dB: connect: no
Therefore, the system would not connect unless the received signal was less than -80 dB. Everything started to work fine once we blew away these two lines.
We fought with this issue for 5 months. :>( Frap!!
There were extenuating circumstances that masked the problem: We have two 90 degree sector AP’s on that tower, pointing different directions. When the CPE couldn’t log onto the correct AP, even though instructed to by SSID, it would log onto the other AP since it was usually visible at less than -80dB. Then, if we had a heavy fog, rain, or snow, the signal strength on the correct AP might drop enough to reconnect to the AP for a while. This particular CPE had collected 5 IP addy’s on the second AP by the time we figured out what was happening. The SSID displayed in Winbox was the correct one but apparently the connect list overrode the SSID instruction.
A headscratcher fell out of this solution, too: Once we blew away the connect list, the signal strength on all of the CPE’s connected to this AP jumped by at least 10 dB. It was almost like this set of instructions were also holding down the signal strength.
Thanks,
Jon.
PS–I’ve seen the threads on the failures of R52H radios but have taken a lot of the buzz with a grain of salt. I’ll bet a lot of guys aren’t aware that powering up these radios without an antenna load may fry them in short order–for example, when they power up the Routerboard/radio to program it before taking it out to the field. I take a lot of care to get an antenna onto my radios before ever powering them up. So far, so good----havent lost one.
Blimey mate, I bet you were doing some cursing, bet the air was blue with all sorts of explicatives.
Still never mind at least you got there in the end.
I agree entirely abt what you say regarding higher power cards. I always use an N type to BNC adaptor and then plug up the bnc port with a bnc dummy load.
However even though I have taken the upmost care, I still have fallen fowl of the mysterious failing, and it happens in service. Still thats another thread.
Best regards
Simon