I’ve got 4 rb133c CPE’s, one rb333 and 5 xr9’s. I can set the rb133c v2.9.46 to 10 or 5MHz channels in WDS bridge mode and have access, however if I try it with the 333, I can’t see it. The 333 runs rc4 and the 133c’s run 2.9.46, and I’ve tried 3rc9 with no change. I have not tried an updated version of 3 on the 333 as I’m on dial up. It takes quite a bit of time to download. v10 is on the way. Any tips, info, etc? Anyone else seen this pretty signifigant problem? I’ve got a few sr9’s I can test, just ran out of time today, so I’m not sure if it is a rc4 problem or an xr9 problem.
0ldman -
From the Beta ROS forum - so far the SR or XR 9 will not talk to a 2.9.xx - no one has specified why - though my own advice and that of many others is to keep the versions, ROS / Beta, the same. I have always noticed that in early versions minor revisions can cause issues between ROS versions. Once the ROS is more mature - like 2.9 is, minor revisions don’t seem to be an issue.
I never said anything about sr9’s communicating with xr9s. The entire setup is different, the rf converter is completely reversed. I have sr9’s I can test with the 333 to see if the half or quarter channel problems are xr9 related or a 333 rc4 bug, just need an hour or so free to try it.
I never said anything about sr9’s communicating with xr9s.
Neither did I - what I said was from posts in the Beta forum that neither an XR9s or SR9s, when talking to an RB with an ROS not Beta, will not talk to each other. It is not a matter of the cards (although an XR9 will not talk to an SR9 as we both know already) but rather a matter of the ROS not being compatible between the two ROS versions Beta ROS3 and 2.9.xx.
I went further to say that through my experience that different early versions of ANY ROS typically has issues when they are not the same revision. And that in later, more mature versions, that minor revisions don’t seem to matter as much.