I believe (but am not more than about 50% certain) that there was a version of the cambium software which didn't update the GPS status screen unless it was using that device as it's sync source. Which was frustrating since you couldn't tell why you weren't getting sync from the device unless you were getting sync from the device. I'm not sure if that has been fixed or not.
I will say that there have been numerous changes to the sync reception hardware and software on the cambium side made with the intent to improve sync reliability. I'd say in some ways this has been the case, and some cases this hasn't. I think they'd be the first to admit that there have been some challenges with the automatic switching between sync sources, and I feel they still have some distance to go to fix this on a more permanent basis. On Wed, Feb 17, 2016 at 4:43 PM, George Skorup <[email protected]> wrote: > We've seen our share of odd SyncPipe/SyncBox issues. Sometimes the > receiver just gets confused and needs to be power-cycled. I've seen them > reporting miles of location inaccuracy until reset. > > One issue I had with the SyncBox at multiple sites last summer is really > weird. Power would go out and the UPS died. Came back a couple hours later. > And then I got no sync and no data from them on all APs. Two of the sites > we're using the parasitic power and running one AP through it. All of the > radios were working perfectly fine, just no GPS data nor sync. Power cycle > it, nothing. Leave it alone and then a couple hours later, bam, GPS sync > and data comes back out of the blue. Even if the receiver can't get lock, I > should see some data on the AP's GPS status pages. No idea what that's > about. > > On 2/17/2016 4:56 PM, Bill Prince wrote: > > We have a site that starts getting sync errors once or twice a day. We've > found if we power cycle the sync injector and the sync pipe, the errors "go > away" for a period of 3 - 6 weeks. > > So that is our solution for the time being. We set up an alert when we get > sync errors. At which time we power cycle the sync injector/sync pipe > during off-hours (~~ 2AM-3AM), and wait for another few weeks. > > bp > <part15sbs{at}gmail{dot}com> > > > On 2/16/2016 8:07 AM, Forrest Christian (List Account) wrote: > > 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 >> > > > -- *Forrest Christian* *CEO**, PacketFlux Technologies, Inc.* Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602 [email protected] | http://www.packetflux.com <http://www.linkedin.com/in/fwchristian> <http://facebook.com/packetflux> <http://twitter.com/@packetflux>
