Power Port Receiving Sync but Sync Source=iGPS?

Hello all.

What could cause all 6 APs to revert to their on board GPS even though they are all receiving sync from the CMM4 on the power port? The CMM4 shows it is receiving sync from the master GPS(See screen copies below) and the APs show they are receiving sync on the power port, but do not Xmt until they switch to the onboard GPS

Immediatly after boot up

All APs

Sync Status

Sync Pulse Source :
Searching
Sync Pulse Status :
No Sync Since Boot Up
Sync Pulse Status - On-board GPS :
No Sync
Sync Pulse Status - Timing Port/UGPS :
No Sync
Sync Pulse Status - Power Port :
Receiving Sync
UGPS Power Status :
Power Off

 After a few minutes (varies Ap to AP)

Sync Status

Sync Pulse Source :
On-board GPS
Sync Pulse Status :
Receiving Sync
Sync Pulse Status - On-board GPS :
Receiving Sync
Sync Pulse Status - Timing Port/UGPS :
No Sync
Sync Pulse Status - Power Port :
Receiving Sync
UGPS Power Status :
Power Off
 
 

CMM4

Sync Status

SYNC Pulse Status :
SYNC OK
SYNC Pulse Source :
Master (GPS Module)
Satellites Visible :
8
Satellites Tracked :
8
Date from GPS :
03/15/2015
Time from GPS :
19:29:04
Antenna Connection :
OK
Tracking Mode :
3D Fix
Latitude :
40° 37' 20.04" N
Longitude :
81° 3' 54.66" W
Height :
377 meters

This scenario  is true with all APs powered up or just 1.

----We did have a previous problem- when more than one AP was powered up, the power port sync would go away on all of them. With just one powered, it would behave exactly as they all do now (Power Port=Receiving Sync and Sync Pulse Source=OnBoard GPS)  Fearing RF interference, I grounded the copper sheath on all the CAT 5s to the power ports and now all APs receive sync on the power port at the same time.-----

We have 6 APs mounted at 295ft. A CMM4 at the base of the tower.

Superior Essex CAT5 (Copper Clad sheath)

Cable length is 304-306 feet between the CMM4 and APs

We also have a permanent Default Cable from the AP to the base of the tower (ends are cut and cleared)

Could this be RF interference? The tower we are on is basically 300 feet of Fire and EMS antennas (and our 6 PMP 450s at the top) 

Thank you for any ideas.

What software release are you running?

AP=13.1.3

CMM4= 3.0

GPS Receiver Information
(c) 2006 SiRF Technology, Inc.
SFTW P/N # 61-G10628A
SOFTWARE VER # 1
SOFTWARE REV # 1
SOFTWARE DATE SEP 06 2006
MODEL # P383T12T12
HWDR P/N # L
SERIAL # AB5961
MANUFACTUR DATE 3A14
 
Canopy iGPS
Function: 3
Software Version: AXN_1.30
Software Revision: 2501
Software Date: 004-20-2011
Model: FGPMMOPA6B
 

These are the stats for the AP on start up. Some APs sync to iGPS after only a minute, others will after a couple of hours. The CMM4 GPS reads good all the time.       Sync Status

Sync Pulse Source :
Searching
Sync Pulse Status :
No Sync Since Boot Up
Sync Pulse Status - On-board GPS :
Receiving Sync
Sync Pulse Status - Timing Port/UGPS :
No Sync
Sync Pulse Status - Power Port :
Receiving Sync
UGPS Power Status :
Power Off

Device Information

Device Type :
5.7GHz MIMO OFDM - Access Point - 0a-00-3e-xx-xx-xx-
Software Version :
CANOPY 13.1.3 AP-DES
Board Type :
P12
Board MSN :
6069qj08le
FPGA Version :
011514
FPGA Type :
C200
PLD Version :
20
Uptime :
07:12:38
System Time :
07:12:38 01/01/2011 UTC
Last NTP Time Update :
00:00:00 00/00/0000 UTC
Ethernet Interface :
100Base-TX Full Duplex
Regulatory :
Passed
Antenna Type :
External
Channel Center Frequency :
5765.0 MHz
Channel Bandwidth :
20.0 MHz
Cyclic Prefix :
1/16
Color Code :
1
Max Range :
9 Miles
Transmitter Output Power :
16 dBm
Temperature :
21 °C / 71 °F
Access Point Stats
Registered SM Count :
0
Sync Pulse Status :
No Sync Since Boot Up
Sync Pulse Source :
Searching
Maximum Count of Registered SMs :
0

Today we plugged 2 of the APs into a UGPS via the timing port. Low and Behold! they immediately synced to the POWER port!  This change is immediate, plug into UGPS--AP syncs to POWER port, unplug UGPS--AP is searching for sync.( eventually to the iGPS). The status of the POWER Port is always RECEIVING. At least one of the APs internal GPS is blind to the sky, so if it does not receive sync on the power or timing port, it never syncs.

Sync Stats without UGPS

Sync Status

Sync Pulse Source :
On-board GPS
Sync Pulse Status :
Receiving Sync
Sync Pulse Status - On-board GPS :
Receiving Sync
Sync Pulse Status - Timing Port/UGPS :
No Sync
Sync Pulse Status - Power Port :
Receiving Sync
UGPS Power Status :
Power Off

Sync Stats with UGPS

Sync Status

Sync Pulse Source :
Power Port
Sync Pulse Status :
Receiving Sync
Sync Pulse Status - On-board GPS :
Receiving Sync
Sync Pulse Status - Timing Port/UGPS :
Receiving Sync
Sync Pulse Status - Power Port :
Receiving Sync
UGPS Power Status :
Power Off

"Blind to the Sky" AP without UGPS on timing port.

Sync Status

Sync Pulse Source :
Searching
Sync Pulse Status :
No Sync
Sync Pulse Status - On-board GPS :
No Sync
Sync Pulse Status - Timing Port/UGPS :
No Sync
Sync Pulse Status - Power Port :
Receiving Sync
UGPS Power Status :
Power Off

Solution?!?- buy two more UGPS (or a sync splitter, or a sync pipe with 6 outputs) and plug into all 6 APs? This seems like an expensive fix to me. Why would providing sync on the timing port cause an AP to sync to the power port? I was hoping someone would tell me about the "rookie mistake" I am making. Or something I am overlooking.

Solved.

8K resistor between pins 5&6 on the default plug.

Can someone explain the solution to this problem to me?

I am having the same issue, where the pmp 450's will not sync through the power port.


2 out of the 4 AP's in my cluster say they are syncing through the on-board GPS, the other 2 just say searching.

This has been a real issue and I need need help with the resolution.

Thank you,

Joe

Which Build are you running ?

13.4 fixes this issue,

I am running 13.4

Here is an attachment showing the Sync Status of AP1 AP2 AP3 and AP4, respectively.

Please send snapshot of General Status page (the page that came after you logged in )

Here is the General Status Page of all 4 APs, respectively.

With your issue, is there any cable connected to the  timing port?  

There is a cable connected to the timing port. The cable is terminated into a surge protection device, but does not go anywhere from there.


The cable is there in case we need to connect an override plug to it.

Any help as to why a cable being connected to the timing port is important?

Please send CNUT logs of AP, If not possible then please send engineering.cgi

Open AP IP address in browser

Goto http://<AP IP>/engineering.cgi>

Capture the html contents and sends us back there are logs in there to help ud debug the issue.

Thanks

Attached is the html contents that you had asked for. Please help me debug the issue.

The file I am sending you is for AP 4. Where the sync input is set to Auto Sync, but instead of getting its sync from the power port (which I want it to do), it's getting the sync from the onboard GPS. 

In AP4 case it receive the synce from On-Board first and software uses it .Our software is designed such that  whatever first GPS lock it receive whether Power or iGPS will use it.

Please send logs of AP1 , which is more concerning since it has sync on both iGPS and Power but still sync status shows searching.

For AP1, I want to let you know that I tried changing the parameter for AP Type from "Standard AP" to "Remote AP". When I did this, it immediately disabled the sync to the power port and synced to the on-board GPS. 

My question is, how to I enable to the Power Port again? I tried switching the parameter back to "Standard AP" and a reboot, but it seems like  that did nothing because it still shows that the sync to the power port is disabled. 


Attached is the html file before I changed the parameter to remote AP, and another html file after I changed the parameter to remote AP. 

Access your AP via telnet.

Then run the command "synctimingport off"

This will disable the timing port as a snyc source.  

You can then log into your AP via web interface and check "Sync Status" tab on the home menu to confirm it is disabled.

We had to do this for a simialr issue with the onboard GPS overriding the power port source.