Oh, also, to be clear - I had examined the processes and procedures used. Like I said above (and in the Ubiquiti community posts) - such an occurrence is common, and readily identifiable if you do this a lot.
So it's pretty quick to see should this be what you do all day. And also easy to...
So I'm working with Tim to get his new test setup running such that an error like this does not re-occur.
In the meantime - it's necessary to make the error clear. Once corrected, Tim and I will be able to show the source of the error, and show folks here how to prevent such an error as well...
Just as a quick update - Tim and I have connected so we'll be discussing over Skype the new test setup when I'm back from WISPAmerica on Friday. Will get it dialed in.
Oh and not saying he's done a bad job... just pointing out what's going on here and trying to help.
Also I can show you what I'm talking about. Once you see you'll immediately get what I'm talking about here.
Cheers,
Brandon
So each is set up at each time. And little leaks can have huge differences.
As Tim mentioned he tests one at a time. So there's potential for different levels of leaks during tear down and re-setup.
Cheers,
Brandon
UBNT-Brandon here. Yes reached out and I'm working with Tim.
So the case here is control of the RF path. When doing high attenuation testing often the propagation path ends up not being through the attenuators, and rather through some leakage.
Signs to know this is happening is 'flattening...