Dbii F-50 pro help

Hey guys, need some help, I currently have the 411 routerboard with a 27dbi grid on my side connecting to a sector on 5.8 around 7km away, signal strength was bad at about -85. At first i was using the R52 radio and noise floor was around -104. I have upgraded the radio to the Dbii F-50 Pro and now cant pick up the SSID of the sector, but the sector can pick me up at -80, the noise floor is now jumping from -92 to -99 and Signal to Noise has dropped for everything else to, and cant pick up sector anymore.

What can I do to fix this and pick up the SSID again? or is it a hardware problem maybe?

If theres anything else you need to know please ask :slight_smile:

Thanks in advance

Hi Koeks,
Do you happen to have the MAC address and the 4 digit date code? The date code would start off with 09xx or 10xx. We did have some issues with date codes starting with 09xx that was mentioned on our website last year. It had to do with Rx.

But on the other hand, we had other customers change a card and notice that they couldn’t get the SSID. Perhaps you can double check to make sure the following (based on what they found out when they were diagnosing):

  1. wrong SSID; (maybe there’s an extra space missing)
  2. dhcp client went away due to the wlan1 card change
  3. bridge went away due to the wlan1 card change

You can e-mail me at lawrence {at} dbii {dot} com if you need further help.

Thanks for reply :slight_smile:

The Digit code on the radio is 1019
The Mac address is 00:21:A4:30:26:EA

All else seems fine, just when i upgraded from the R52 everything seems worse now, signal strength, noise floor, signal to noise(to other SSID’s) and now cant even pick up the sector I need. So it might be a hardware problem?

Thanks for help

hi Koeks…
with the -80 signal strength, it’s bad idea to serve your customer.

make sure you sector polarization is correct and the client is in the coverage angle.
in fact, i have deploy almost 200 unit’s with the F50-Pro with no issue.

most the issue still the Mikrotik ethernet locked up with no solution up to date.

p/s: try to secure you connection <-72dbm.