13:33:44 UT : 02/12/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : E6BC
13:35:12 UT : 02/12/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : C749
13:35:31 UT : 02/12/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : E4E7
13:35:56 UT : 02/12/01 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : E725
I get this in the event log. This AP is timed through the Slave back-haul as are some of my other towers with only one AP. this is, however, the first time I am seeing this error. Anybody know what it means?
I am emailing support on the matter. This error is showing up on more APs now. Here’s what I know is wrong with my setup and I’m working on resolving this… a few towers have both M and S backhauls, Some towers are timed via SMs, I have some BH that do not support hardware scheduling, and thus are running is software, I am using both CMMs and Pipesyncs in my network. I started with the timing issue, and have been installing pipesync for remote locations that I don’t see CMMs being much of a value. The more timing I get on my network, the more of these errors I am getting.
Anyone have any ideas?
19:47:07 UT : 06/11/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
21:19:03 UT : 06/11/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : FDAA
21:25:56 UT : 06/11/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : FF43
21:31:41 UT : 06/11/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : E837
23:27:57 UT : 06/11/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : F48F
23:28:21 UT : 06/11/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : EA44
23:58:00 UT : 06/11/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : E813
00:27:57 UT : 06/12/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : E817
00:46:36 UT : 06/12/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : EA39
01:10:46 UT : 06/12/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : EA17
03:13:04 UT : 06/12/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : E6C1
03:22:36 UT : 06/12/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : E945
04:14:54 UT : 06/12/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : EE90
05:06:44 UT : 06/12/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : E8D6
LP wrote: I am emailing support on the matter. This error is showing up on more APs now. Here's what I know is wrong with my setup and I'm working on resolving this.... a few towers have both M and S backhauls, Some towers are timed via SMs, I have some BH that do not support hardware scheduling, and thus are running is software, I am using both CMMs and Pipesyncs in my network. I started with the timing issue, and have been installing pipesync for remote locations that I don't see CMMs being much of a value. The more timing I get on my network, the more of these errors I am getting.
Anyone have any ideas?
19:47:07 UT : 06/11/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/syslog.c : Line 1062 Time set
21:19:03 UT : 06/11/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : FDAA
21:25:56 UT : 06/11/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : FF43
21:31:41 UT : 06/11/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : E837
23:27:57 UT : 06/11/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : F48F
23:28:21 UT : 06/11/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : EA44
23:58:00 UT : 06/11/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : E813
00:27:57 UT : 06/12/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : E817
00:46:36 UT : 06/12/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : EA39
01:10:46 UT : 06/12/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : EA17
03:13:04 UT : 06/12/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : E6C1
03:22:36 UT : 06/12/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : E945
04:14:54 UT : 06/12/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : EE90
05:06:44 UT : 06/12/07 : File C:/ISIPPC/pssppc.250/bsps/devices/whisp/fpgaapi.c : Line 1677 Ranging Diff : E8D6
Did you find a solution for this issue? Was tech support able to shed light on what was causing the issue?
I fixed this problem by installing a pipe sync at the location. I now do not use timing over the “one hop” from BHs anymore. Once the new pipe sync was installed, all timing errors subsided. I still would love to know what the error is specifically, but I have not seen it since getting off the bhs timing. This BH link was 13 miles, so maybe that had something to do with it.
You may also get this error if the AP can see other AP’s and the settings are different.
ie…2.4AP-75% ratio-2 control slots-10mile range…can see another AP, 2.4-65% ratio-1 control slot-15mile range.
The second AP may not be yours but you need to match settings the best you can to keep interference to a minimum.