Yup.
It's a SiteMonitor II, plus a sync injector plus a sync pipe. It's not
in the best location. It's on the 11th floor of a 13 story building, and
is blocked from seeing ~~ 190° of the sky. It's exposure is generally
south.
From the time we installed it, it would occasionally get sync events.
We figured it was probably the lack of a good sky view, but decided to
replace the sync pipe anyway, just in case the one we had was
particularly sensitive.
Lo and behold, the new sync pipe did not get any sync events for ~~ 3
weeks. We thought we had fixed it.
Then it started behaving the same way as the old one.
On a hunch, at 0-dark:30 one night, I power cycled the sync pipe and
sync injector. By golly, the problem cured itself for another 3 weeks.
Hmmm. maybe I got something.
So the next time it got a couple of sync events in one day, I power
cycled it again.
Rinse. Repeat.
bp
<part15sbs{at}gmail{dot}com>
On 2/17/2016 11:00 PM, Forrest Christian (List Account) wrote:
On this site, I'd like to find out more about what the syncinjector is
seeing ... is there a sitemonitor attached to it?
I get random reports occasionally where there is 'something odd'
happening. Where this is recurring, and there's a syncinjector
attached, this seems to present an opportunity to look at this when
it's misbehaving and figure out whether it's the syncpipe misbehaving
or something else. Would I believe that the GPS receiver can get into
a state where it isn't happy and needs a reboot? Definitely. But
these tend to be really hard *especially* if you can't get
instrumentation on the misbehaving device. If this is reoccuring,
then we can possibly get a look at this.
On Wed, Feb 17, 2016 at 3:56 PM, Bill Prince <[email protected]
<mailto:[email protected]>> 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]
<mailto:[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] <mailto:[email protected]> |
http://www.packetflux.com <http://www.packetflux.com/>
<http://www.linkedin.com/in/fwchristian>
<http://facebook.com/packetflux> <http://twitter.com/@packetflux>
