I believe this is the SM trying to sync up its frequency offset or oscillator or something when syncing with an AP. Many, many releases ago, I think Aaron explained that the AP sends frequency calibration info to the SMs using the sync pulse for precision. The SMs store this offset locally so they can get on-frequency faster at boot. I remember at one time this was broken, possibly because of an AP generating its own sync or something like that, and some SMs couldn't detect APs on certain frequencies because of the bad stored offset.

So anyway, if it's working fine, I wouldn't worry about it.

On 3/27/2015 4:35 PM, Bill Prince wrote:
I've only seen it once. So maybe it's not a big deal.

bp
<part15sbs{at}gmail{dot}com>

On 3/27/2015 1:48 PM, Caleb Knauer wrote:
It's mentioned that you should call support if you see it a lot here:
http://community.cambiumnetworks.com/t5/PMP-450/System-Release-13-3-Now-Available/m-p/38153#M428

On Fri, Mar 27, 2015 at 11:53 AM, Bill Prince <part15...@gmail.com> wrote:
I saw these entries in a PMP450 (5 GHz) this morning, and have no idea what
it's trying to tell me. Firmware is 13.2. Anyone know?

03/18/2015 : 09:12:04 PDT : :XO trim at min diff=-2471 c=7 cmove=-16 f=8058
fmove=-71
03/18/2015 : 13:26:14 PDT : :XO trim at max diff=4509 c=35 cmove=30 f=41
fmove=9


--

bp
<part15sbs{at}gmail{dot}com>



Reply via email to