XR-9 incompatible?

Who else has stumbled onto this problem of the SR-9 and XR-9 are not compatible?

-Sincerely,
DesertAdmin

Well known fact. Any reputable reseller posts this information under XR9/SR9 descriptions.

compatible with what ?

Each other.

oh, this is not related to mikrotik and routeros …

Yeah I guess this is true that it is not related but it helps to know this I use the MT religiously and did not know this problem with the Ubiquity 900MHz cards that are not from RouterOS related or MT related. It was just a cry for help on this sorry. I just needed to know who else has seen this problem.

Thanks for everyone’s response on this.

-Sincerely,
DesertAdmin

Yep XR-9 started to work great once I paired them up but I had some SR-9s and I thought hey 900MHz will work well with another 900MHz but they unfortunately did not. Any ways the 900MHz XR-2 did perform even better connection wise when I enabled the NSTREME on both sides. Some how this made the connections more stable not that I care about the pTHROUGHPUT at this point but the actually radio connection seemed to have cleared up once I enabled the NSTREME. I thought this was very interesting and so I wanted to share this back to the MT community.

Thanks

-Sincerely,
DesertAdmin

Can you tell which version of ROS are you using with nstreme?

3.30 Not sure if it is actually working as NSTREME but it cleared up my connection when I enabled it. It stabilized the pthroughput and the data rates in a awful area that I was shooting through to the AP from the CPE.

I hope that helps.


-Sincerely,
DesertAdmin

Thanks for the info. Seems like 3.30 is a safe bet…I guess I will not be trying 4.x just yet.

I really like 3.30 it seems very stable. No oddities so far.

Did you happen to see an improvement with the XR-9 vs an SR-9? I do not see a difference at the moment but I will be do ing a full on install here in the next week or so. Just curious if anyone has seen a diff or not.

-Sincerely,
DesertAdmin

I have not used SR-9 so I have nothing to compare…

Sounds like firmware/driver problem that got “overwritten” when you enabled nstreme. I wonder if on that level - there are enough ckechs to make sure the hardware has all its lower level settings (registers) right…

A piece of thoutht for the developers that handle those.. :wink: