I don’t think that would be related, but that 0% beacons is very interesting - are you taking this screen capture from the RF side of the SM?
We’ll take a look. On 11/25/15, 1:48 PM, "Af on behalf of Ken Hohhof" <[email protected] on behalf of [email protected]> wrote: >Is the SM in the attached screenshot another symptom of this? > >(passing data, good SNR, but no numbers for rcv power, signal strength >ratio, or beacons? > >The rcv signal power graph via SNMP just started erroring out for no >apparent reason, reboot the SM and it came back. I don't think I've seen >this before. > > >-----Original Message----- >From: Adam Moffett >Sent: Wednesday, November 25, 2015 1:35 PM >To: [email protected] >Subject: Re: [AFMUG] 450 AP on iGPS makes opposite AP invisible? > >Don't abuse it. > >On 11/25/2015 2:32 PM, George Skorup wrote: >> I knew it, you DO have an email filter that looks for your name.... :) >> >> And this sounds awesome. >> >> On 11/24/2015 10:00 PM, Aaron Schneider wrote: >>> Coming in 14.1.1 for 450/450i and 13.4.1 for 100/430 series, you’ll see >>> fixes for lining up the various sync sources. Over time, they have been >>> a bit off from each other both on sync source (multiple devices) as well >>> as some SW releases. We have dug in to try to correlate all of these, >>> including 3rd party devices such as the SyncPipe. Once you get systems >>> up on these versions, they’ll line up with each other in a much tighter >>> fashion. Until then, loading 13.4.1 on 100/430 and/or 14.1.1 on >>> 450/450i, there will be a configuration option to align the offsets with >>> respect to the SW running remainder of your frequency reuse sectors. >>> >>> If you have mixed timing installations (sync over power vs sync over >>> timing), you’ll want to upgrade everything to 13.4.1 or 14.1.1. >>> >>> There will be more details in the release notes regarding this addition. >>> >>> Regarding autosync, we are planning to go over that in depth too for the >>> next release. The idea and promise was set it and forget it, but >>> unfortunately, we’ve had some issues in this area that we need to >>> address. >>> >>> Regards, >>> -Aaron >>> >>> >>> >>> On 11/22/15, 11:54 AM, "Af on behalf of George >>> Skorup"<[email protected] on behalf of [email protected]> wrote: >>> >>>> I get this on sites with SyncPipes and SyncInjectors. Those put out CMM3 >>>> aligned timing. The on-board GPS is CMM4 aligned. Is the CTM2 CMM3 or 4 >>>> type timing? I don't know how much difference there is exactly, but I >>>> don't get LBT hits on 3GHz, so they're probably not that far apart. I >>>> wonder if Cambium could give us a toggle between CMM3 and CMM4 for the >>>> on-board GPS? Paging Aaron Schneider.... >>>> >>>> AFAIK, the stuck issue is/was only the FreeRun mode. AutoSync does not >>>> go back to the timing port or power port if they return while it's >>>> running on the on-board. I wish that was the case. The on-board is OK >>>> for backup, but most of ours work maybe 70% or less, some have never >>>> worked since install. Many of them created more problems than benefits, >>>> so I disable them where needed. >>>> >>>> On 11/22/2015 9:08 AM, Ken Hohhof wrote: >>>>> Has anyone else seen this? >>>>> >>>>> I have an ABAB site where some SMs couldn't register to the AP or see >>>>> it in AP Eval Data, but could see the opposite AP (same frequency, >>>>> very low signal level, different color code). I checked and the >>>>> opposite AP was stuck on iGPS despite having power port sync >>>>> available. I power cycled the opposite AP, which then came up on >>>>> power port sync, and the SM registered to the correct AP. >>>>> >>>>> I still have these on 13.2.1 and maybe 14.1.1 will fix the "stuck on >>>>> iGPS sync" problem. >>>>> >>>>> But how was the one AP masking the other? The only thing I can think >>>>> of is the sync was slightly different and somehow that prevented the >>>>> SM from seeing the beacons, despite the signal being much higher. The >>>>> only other unique thing about the config is these APs are on 5845 (10 >>>>> MHz channel), so they are on the highest available frequency. The >>>>> power port sync is coming from a CTM2 over 300 ft cables. >>>>> >>>>> Changing out the SM didn't make a difference. >>>>> >>
