Oh I forgot... Some of the older syncpipes only do Motorola Binary format output. The newer ones either do NMEA or Motorola Binary. I can't remember how long ago (aka which rev) the pipes re-gained NMEA, but I wouldn't be surprised if it was as late as Rev G or as early as Rev E. I know C was Mot Binary Only (although I could release a firmware to fix that, at this point). I also know rev H was definitely both. Between them I'd have to get some pipes and look at the output.
-forrest On Thu, Jul 23, 2015 at 6:43 PM, Forrest Christian (List Account) < li...@packetflux.com> wrote: > Yep... See http://tickets.packetflux.com/kb/faq.php?id=14 > > If you have these on the bench, I'd upgrade them before you put them in > the field. > > If they're in the field, and you have to go out to get them detected, I'd > wait for another week or so until I release the next syncinjector > firmware. The firmware releases for the injector are at the top of my > list. Well, top of my list right behind getting a couple of circuit board > layouts done (which are basically 'send off and then wait for 2 weeks > before you do anything else for that product). > > -forrest > > On Thu, Jul 23, 2015 at 12:02 PM, George Skorup <geo...@cbcast.com> wrote: > >> It sounds like you're having the module detection issue on the expansion >> bus. Forrest put out some new firmware that fixes those issues. >> >> I also recall that there was a wiring/pinout change with the newer >> SyncInjectors. Or maybe the GPS data issue is because the Rev E pipes don't >> do NMEA format? >> >> On 7/23/2015 12:29 PM, That One Guy /sarcasm wrote: >> >> Forrest? >> I have a revision E0 Parasitic >> Base Unit II - Firmware - March 12 2013 >> SyncInjector100RevH1 22-Jan-14 >> SyncInjector430RevH1 12-Jan-15 >> >> The 100 injector will not show connected unless it is the first device, >> it was doing some weird stuff like randomly not being connected, but I >> think it may have been due to the amount if time I left power off when >> cycling >> >> I have the parasitic connected to the syncinjector 100, its is getting >> pulses and both the fsk and the 320 AP are showing sync, but there is no >> GPS data. Is this normal behavior when using a parasitic? >> >> Parasitics dont generate their own sync, is this correct? So if it is >> sending pulses, even without the satellite info they should be valid timing? >> >> I though when I shop tested these that they were showing GPS data, but >> I dont know if I tested with this particular parasitic >> >> On Fri, Jun 19, 2015 at 4:21 PM, George Skorup <geo...@cbcast.com> wrote: >> >>> The link Josh posted to wire the RJ12 to RJ45 jumper will allow you to >>> use the spare parasitics with SyncInjectors. But I think you need at least >>> Rev E or possibly Rev F/G/H pipes with the newer SiteMonitor controlled >>> SyncInjectors. There's some difference, I forget what it is. I think the >>> no-no was Rev C pipes on Rev H SyncInjectors. Forrest would have to say for >>> sure what works with what. >>> >>> On 6/19/2015 12:18 PM, That One Guy /sarcasm wrote: >>> >>> We have always used the parasitics, syncsplitters, creative taps and >>> syncbox, but these syncinjectors are the bees knees, other than that they >>> arent universal. BUT, not having to climb up makes a huge difference, and >>> being able to do with packetflux with a handful of hundred dollar bills >>> what the CMMs do, its a no brainer. but now we have a bunch of parasitics >>> laying around. They just wont die, so we have to use them >>> >>> On Fri, Jun 19, 2015 at 11:19 AM, George Skorup <geo...@cbcast.com> >>> wrote: >>> >>>> Yeah, I have a couple sites with either a SyncPipe Deluxe or a SyncBox >>>> on top powered separately and a SyncInjector with it's own Basic pipe at >>>> the bottom to provide redundant timing to some 450 sectors. >>>> >>>> I also have some 450 sectors each with their own Parasitic pipes >>>> because they're far apart on the tower. And I get some strange GPS issues >>>> there when it rains or there's heavy cloud cover. So I asked Forrest if it >>>> would be OK to put a sync over power pulse through the Parasitic pipes. He >>>> said no issues and I've bench tested it, so I'm going to add a SyncInjector >>>> on those APs >>>> >>>> On 6/19/2015 11:06 AM, Ken Hohhof wrote: >>>> >>>> I have mostly switched to using the Syncbox12 instead of Parasitics. >>>> It does have a Syncinjector port on it (which I haven’t had a use for). >>>> >>>> *From:* Josh Luthman <j...@imaginenetworksllc.com> >>>> *Sent:* Friday, June 19, 2015 10:48 AM >>>> *To:* <af@afmug.com>af@afmug.com >>>> *Subject:* Re: [AFMUG] 24v syncinjector wiring >>>> >>>> 1. From what I'm told you can do it. Just reverse the blue/brown >>>> pairs. Sync pulse doesn't cause damage from what Forrest said. >>>> >>>> 2. >>>> <http://manuals.packetflux.com/index.php?page=using-a-syncpipe-parasitic-with-a-syncinjector> >>>> http://manuals.packetflux.com/index.php?page=using-a-syncpipe-parasitic-with-a-syncinjector >>>> >>>> >>>> Josh Luthman >>>> Office: 937-552-2340 >>>> Direct: 937-552-2343 >>>> 1100 Wayne St >>>> Suite 1337 >>>> Troy, OH 45373 >>>> >>>> On Fri, Jun 19, 2015 at 11:45 AM, That One Guy /sarcasm < >>>> <thatoneguyst...@gmail.com>thatoneguyst...@gmail.com> wrote: >>>> >>>>> I thought I had read these are both doable, >>>>> 1. Can I power ubnt devices off these? what is the cross pinout? and >>>>> do I need to turn off the sync pulse on that port? >>>>> >>>>> 2. Can I use a syncpipe parasitic on the syncinjector? Isnt there a >>>>> particular cable pinout to do this? >>>>> >>>>> -- >>>>> If you only see yourself as part of the team but you don't see your >>>>> team as part of yourself you have already failed as part of the team. >>>>> >>>> >>>> >>>> >>>> >>> >>> >>> -- >>> If you only see yourself as part of the team but you don't see your >>> team as part of yourself you have already failed as part of the team. >>> >>> >>> >> >> >> -- >> If you only see yourself as part of the team but you don't see your >> team as part of yourself you have already failed as part of the team. >> >> >> > > > -- > *Forrest Christian* *CEO**, PacketFlux Technologies, Inc.* > Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602 > forre...@imach.com | http://www.packetflux.com > <http://www.linkedin.com/in/fwchristian> <http://facebook.com/packetflux> > <http://twitter.com/@packetflux> > > -- *Forrest Christian* *CEO**, PacketFlux Technologies, Inc.* Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602 forre...@imach.com | http://www.packetflux.com <http://www.linkedin.com/in/fwchristian> <http://facebook.com/packetflux> <http://twitter.com/@packetflux>
