Seems a very strange bug. Could the power from the Netonix be unstable and fooling the APs into thinking they are getting power port sync?
Isn’t there a telnet command to disable individual sync sources, maybe disable power port sync if you’re not using it? But you said that power cycling the Syncbox makes the weird behavior go away? Hmmmmmmmmm. Does the Syncbox have its own power, or is it parasitic on the feed to one of the APs? If you have a Netonix, I’m going to guess you are using a dedicated port on it to power the Syncbox? From: Craig House Sent: Wednesday, February 17, 2016 3:49 PM To: [email protected] Subject: Re: [AFMUG] Sync box 12's losing sync I see what you mean now. I didn't even notice that it is showing power port. Must be a bug because there is no other sync source. They have to be getting sync from timing and all the AP's are doing the same thing Craig -------------------------------------------------------------------------------- From: "Craig House" <[email protected]> To: [email protected] Sent: Wednesday, February 17, 2016 3:48:41 PM Subject: Re: [AFMUG] Sync box 12's losing sync Netonix. I have them setup this way in about 25 locations. Only 2 or 3 are having this issue Craig -------------------------------------------------------------------------------- From: "Ken Hohhof" <[email protected]> To: [email protected] Sent: Wednesday, February 17, 2016 3:46:46 PM Subject: Re: [AFMUG] Sync box 12's losing sync ????????????? Syncbox is timing port sync. What are you powering these from? From: Craig House Sent: Wednesday, February 17, 2016 3:37 PM To: [email protected] Subject: Re: [AFMUG] Sync box 12's losing sync I have checked the GPS statistics screen and the number of tracked and the number of visible birds are changing. Staying around 10 visible and 7-8 tracked. Seems normal but the event log shows the following on all AP's feeding from it. FPGA Features : DES, Sched, US/ETSI; 02/16/2016 : 20:03:09 UTC : :Time Set 02/16/2016 : 20:03:10 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:03:21 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:03:23 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:03:26 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:03:28 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:03:30 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:03:32 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:03:35 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:03:37 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:03:39 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:03:41 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:03:44 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:03:46 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:03:48 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:03:50 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:03:53 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:03:55 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:03:57 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:03:59 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:04:02 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:04:02 UTC : :GPS Date/Time Set; 02/16/2016 : 20:04:04 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:04:06 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:04:08 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:04:11 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:04:13 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:04:15 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:04:17 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:04:20 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:04:22 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:04:24 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:04:26 UTC : Acquired sync pulse from Power Port. 02/16/2016 : 20:04:29 UTC : Lost sync pulse from Power Port. 02/16/2016 : 20:04:31 UTC : Acquired sync pulse from Power Port. -------------------------------------------------------------------------------- From: "Forrest Christian (List Account)" <[email protected]> To: "af" <[email protected]> Sent: Tuesday, February 16, 2016 10:07:28 AM Subject: Re: [AFMUG] Sync box 12's losing sync The only issues I've heard like this are specifically related to mounting in a bad location, and then the problem seems to come and go just like you expect. The units don't really have firmware on the unit itself, only in the GPS module, and I can honestly say we've never had to update a module in the field. I don't even know how to make that happen at this point other than it can be done. The modules come from the factory with our preloaded firmware, which never changes unless we switch modules, which has happened once, the last time being at least a year ago. One caveat is that the newest syncboxes have been modified to work with the 450i. So the radio driving electronics are slightly different, even though the firmware is the same. This only is relevant to units shipped in the last month or so. If you can come up with the serial numbers of affected units that might help in case something happened to a batch here (like some undetected bad modules from our supplier) The other thing to look at is if the status screen is really updating on the radios. If the gps module doesn't supply data, the screen stays the same. On Feb 15, 2016 7:26 PM, "Craig House" <[email protected]> wrote: We have been deploying sync box 12 units with Netonix switches for the last 6-9 months with great success. However, several of the syncbox12's we have deployed seem to loose and acquire sync repeatedly until they are power cycled. This affects all the customers on the tower during that time. Is there a firmware version that fixes this? I'm not sure how to even update firmware on a syncbox? The Sync status tab always shows that the device is tracking 10 or so satellites but the device is not passing sync on. In some other installations we have out there they have never had any issues. It seems to be several that were deployed about the same time that are doing this but I cant swear to it. Forrest?? is there an easy fix to this or have you heard about this from anyone else? Craig
