Thanks, Patch between the two packetflux is 1 foot.
ePMP is running 6.2.1.X ( don’t want to go to 3.2.x until they work out one more bug. ) Using the SyncBox Junior for the syncpipe. Cable runs to the APs are 140 feet From: Af [mailto:[email protected]] On Behalf Of That One Guy /sarcasm Sent: Thursday, February 16, 2017 11:51 PM To: [email protected] Subject: Re: [AFMUG] ePMP and Packet Flux configuration settings. Shorter the better on the cable Update all the components to the current firmware, and verify the syncpipe is the right revision. The default pinout on the pins inside works with 48v ps On Feb 16, 2017 11:35 PM, "Brandon Yuchasz" <[email protected]> wrote: Hopefully and easy question here. We have always used the onboard GPS for ePMP access points up until this point. We recently installed 4 new ePMP APs and the tower blocks our north facing AP from getting GPS on the onboard GPS. All other track GPS just fine. We also have 450 APs on the tower and are using a PacketFlux PowerInjector Plus to power them and provide GPS and its working fine. I then installed a Gigabit SyncInjector ( had it on the shelf new) to power the ePMP APs and connected it to the GPS feed with a standard patch cable on the PowerInjector Plus. Light flashes shows its getting GPS but no joy on the ePMP AP. So my questions are : what configuration should I use in the ePMP AP? And I am fairly sure stadard patch cable is acceptable between the two packet flux but I wanted to confirm? Thanks everyone. Brandon Yuchasz
