Bad error causing major problems

Products PMP
1 
03:41:12 UT : 01/01/01 : File root.c : Line 940 ******System Startup******
03:41:12 UT : 01/01/01 : File root.c : Line 945 Software Version : CANOPY 7.2.9 Jul 23 2005 01:49:03 AP-DES
03:41:12 UT : 01/01/01 : File root.c : Line 949 Software Boot Version : CANOPYBOOT 3.0
03:41:12 UT : 01/01/01 : File root.c : Line 955 FPGA Version : 070605
03:41:12 UT : 01/01/01 : File root.c : Line 959 FPGA Features : DES Sched
03:41:23 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/rfhwsched.c : Line 1449 Acquired GPS Sync Pulse.
03:41:28 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : FF32
03:41:28 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : FF36
03:41:31 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : FF37
03:41:31 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : FF70
03:41:31 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : FF69
03:55:42 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : FF84
04:12:23 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : FFA3
04:12:36 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : FFF6
04:13:20 UT : 01/01/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : FF3D
04:20:20 UT : 01/01/01 : File httptask.c : Line 733 Reboot from Webpage.


Has anyone ever seen Ranging Diff errors before? I am getting these on 2 APs and customers are getting 0% downlink effeciency because of it. Both APs are 900Mhz 7.3.6 Revision in Hardware scheduling.
2

3:41:12 UT : 01/01/01 : File root.c : Line 945 Software Version : CANOPY 7.2.9 Jul 23 2005 01:49:03 AP-DES

That doesn’t look like 7.3.6 to me?

3

Whoops. Yeah it was doing it on 7.2.9 as well. It is now 7.3.6 and is still doing that. I just didnt want to post a few pages worth of event log showing the same thing so I grabbed a single entry.

4

Never heard of that one. Starts immediately upon acquisition of GPS.

Try a power reset, I have seen some odd behavior and rebooting from the webpage didn’t clear it, but power cycling did.

If that doesn’t do it then I would try re-loading the software.

If that doesn’t work, I would try swapping the cables on the CMM to known working ports and see if the problem follows the radio or the CMM port.

Worst case would be to swap the CMM but I doubt that’s it.

5

Question…The Tower that these AP’s are on, is it being back hauled using an SM?

6
Frothingdog.ca wrote:
Question...The Tower that these AP's are on, is it being back hauled using an SM?


If by tower you mean pine tree? And, yes these APs were being sync'd from an SM. Now its using a sync pipe and the problem is gone.
7

A Ha! Glad you were able to fix it.

8

If the problem comes back you might want to set the AP that the SM is linking to Wirelessly to 50% downlink ratio as well as all the AP’s in the …umm…Pine Tree.

9

I just installed sync via an SM this week as it was the last AP that was generating sync on the network. I’ve never seen this one, but I have now. I am getting the same errors. Is there any more information on this error that we can get? You said that your APs were syncing from an SM, was there any other factors you could think of that would have caused this? How long was your cable? was it close to another antenna not recieving sync? or was your tower mixed with M and S BHs?

The reason I ask is that as I will continue trying to simply install the tower’s own source of timing. This particular one will not be easy to do so. I have three BH on there, all but one on the far side are slaves. The other is a master at the time untill I can get more timing equipment. that is the only thing I can think of, the fact that there is one master on the tower (though all backhauls are performing fine) or the cable simply being too long.

Any ideas?

Thanks