Re: [AFMUG] Addition to new site.

[Sam Lambie]

kiss kiss! You da man Seth. thank you very much.

On Wed, Apr 19, 2017 at 10:07 AM, Seth Mattinen  wrote:

> On 4/19/17 07:59, Sam Lambie wrote:
>
>> That seemed to work, but the odd thing is that it took the Medusa 11
>> hours to switch over to using the Timing port. Even though I made doubly
>> sure that I had sync turned off on the power port of the Sync Injector,
>> it still indicated that it had sync. Then at 0004 it switched. The radio
>> did show that timing was available on the UGPS port right away as well
>> as on the power port. Now the radio intermittently show sync-no sync on
>> the power power port. is there a way to force the radio to only listen
>> on the timing port so it doesn't get confused?
>>
>
>
> There is, in the command line. Telnet to it and you should have:
>
> synconboard -- Enable/Disable On-board GSP Sync
>  synctimingport -- Enable/Disable GSP Sync over Timing Port
>   syncpowerport -- Enable/Disable GSP Sync over Power Port
>
> Then you can do "syncpowerport off".
>
> ~Seth
>



-- 
-- 
*Sam Lambie*
Taosnet Wireless Tech.
575-758-7598 Office
www.Taosnet.com 

Re: [AFMUG] Addition to new site.

[Seth Mattinen]

On 4/19/17 07:59, Sam Lambie wrote:

That seemed to work, but the odd thing is that it took the Medusa 11
hours to switch over to using the Timing port. Even though I made doubly
sure that I had sync turned off on the power port of the Sync Injector,
it still indicated that it had sync. Then at 0004 it switched. The radio
did show that timing was available on the UGPS port right away as well
as on the power port. Now the radio intermittently show sync-no sync on
the power power port. is there a way to force the radio to only listen
on the timing port so it doesn't get confused?



There is, in the command line. Telnet to it and you should have:

synconboard -- Enable/Disable On-board GSP Sync
 synctimingport -- Enable/Disable GSP Sync over Timing Port
  syncpowerport -- Enable/Disable GSP Sync over Power Port

Then you can do "syncpowerport off".

~Seth

Re: [AFMUG] Addition to new site.

[Jon Langeler]

Throwing those pictures on your website alone would be great

Jon Langeler
Michwave Technologies, Inc.


> On Apr 18, 2017, at 3:21 PM, Forrest Christian (List Account) 
>  wrote:
> 
> Partially our fault...  We really should have better docs available.  There's 
> a lot of reasons why we don't,  but suffice it to say that it is not because 
> of lack of desire.
> 
>> On Apr 18, 2017 9:08 AM, "Sam Lambie"  wrote:
>> Thanks for the heads up on the pin out. I feel pretty dumb now
>> 
>>> On Mon, Apr 17, 2017 at 10:22 AM, Forrest Christian (List Account) 
>>>  wrote:
>>> There's a drawing in the 450i or 450m documentation which shows how to 
>>> cable a 6p6c device to the 8p8c port.   Snip shown below:
>>> 
>>> 
>>> ​
>>> 
 On Mon, Apr 17, 2017 at 9:06 AM, Sam Lambie  wrote:
 Ok Thanks. The Syncbox is new as of a month ago.
 Cabling from to Medusa is RJ-12 using pins 1 and 6 for sync. I have a 
 feeling that I need to use a different termination
 What is the proper termination type and cabling pinout? Your site is 
 lacking on documentation.
 
 Thanks
 Sam
 
> On Mon, Apr 17, 2017 at 8:59 AM, Forrest Christian (List Account) 
>  wrote:
> This is definitely in the weird category.  
> 
> Can you verify how old this syncbox 12 is?   I'm guessing that it is new 
> from us in February.
> 
> Can you also let me know how you cabled the syncbox to the medusa?
> 
> The two weird items here are:
> 
> 1) Why is it not picking up sync from the timing port?   (Cabling issue?  
> There's a special cable from the syncbox to the aux port since the aux 
> port is a 8p8c with a different pinout)
> 
> 2) Why does it think it's picking up sync from the power port?
> 
> 
> 
>> On Mon, Apr 17, 2017 at 8:45 AM, Sam Lambie  wrote:
>> Well, That didn't work... I turned off Sync to the radio via the Site 
>> Monitor on Friday and the Radio still flopped all weekend. It still 
>> thinks it is getting sync from the power port and never has indicated 
>> that it is getting sync from the timing port. Are there any settings on 
>> the radio that I am missing?
>> 
>> 
>> 
>>> On Fri, Apr 14, 2017 at 5:53 PM, Forrest Christian (List Account) 
>>>  wrote:
>>> Yes, that was correct, and yes, as long as it's a recent syncbox it 
>>> should work fine.
>>> 
>>> -forrest
>>> 
 On Fri, Apr 14, 2017 at 3:22 PM, Sam Lambie  
 wrote:
 I just did that and will monitor it over the weekend. Thanks for the 
 tip. Lastly, The Sync coming out of the Sync Box into the timing port 
 of the Medusa should work right?
 
> On Fri, Apr 14, 2017 at 3:20 PM, Sam Lambie  
> wrote:
> Changing the value function on the Radio 4 Sync from 1 to 0 will do 
> the trick?
> 
>> On Fri, Apr 14, 2017 at 3:08 PM, Forrest Christian (List Account) 
>>  wrote:
>> This error means you have sync over power pulses coming in from the 
>> syncinjector.
>> 
>> The radio is seeing the old-style pulses and is trying to lock onto 
>> them, which won't work reliably - since the pulses aren't even close 
>> to what it's expecting.
>> 
>> You need to disable the pulses in the injector in some way.   If 
>> you've got a SiteMonitor base unit attached, just turn off sync on 
>> those ports.   If you don't, then just use a cambium power supply 
>> and skip the injector, or if you don't have any radios which need 
>> the sync over power pulse attached to the injector, make a cable 
>> shorting pins 1 and 2 of a RJ45 jack and plug that into the sync 
>> input port on the syncinjector.   
>> 
>> 
>> 
>>> On Thu, Apr 13, 2017 at 9:28 AM, Sam Lambie  
>>> wrote:
>> 
>>> Medusa doesn't seem to like the packetflux gps. I am getting this 
>>> most of the time.
>>> 04/13/2017 : 09:12:44 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:12:45 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:12:45 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:00 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:03 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:03 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:03 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:05 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:05 MDT : Generating Sync - Free Run
>>> 

Re: [AFMUG] Addition to new site.

[Sam Lambie]

Ok Thanks. The Syncbox is new as of a month ago.
Cabling from to Medusa is RJ-12 using pins 1 and 6 for sync. I have a
feeling that I need to use a different termination
What is the proper termination type and cabling pinout? Your site is
lacking on documentation.

Thanks
Sam

On Mon, Apr 17, 2017 at 8:59 AM, Forrest Christian (List Account) <
li...@packetflux.com> wrote:

> This is definitely in the weird category.
>
> Can you verify how old this syncbox 12 is?   I'm guessing that it is new
> from us in February.
>
> Can you also let me know how you cabled the syncbox to the medusa?
>
> The two weird items here are:
>
> 1) Why is it not picking up sync from the timing port?   (Cabling issue?
> There's a special cable from the syncbox to the aux port since the aux port
> is a 8p8c with a different pinout)
>
> 2) Why does it think it's picking up sync from the power port?
>
>
>
> On Mon, Apr 17, 2017 at 8:45 AM, Sam Lambie  wrote:
>
>> Well, That didn't work... I turned off Sync to the radio via the Site
>> Monitor on Friday and the Radio still flopped all weekend. It still thinks
>> it is getting sync from the power port and never has indicated that it is
>> getting sync from the timing port. Are there any settings on the radio that
>> I am missing?
>> [image: Inline image 1]
>> [image: Inline image 2]
>>
>> On Fri, Apr 14, 2017 at 5:53 PM, Forrest Christian (List Account) <
>> li...@packetflux.com> wrote:
>>
>>> Yes, that was correct, and yes, as long as it's a recent syncbox it
>>> should work fine.
>>>
>>> -forrest
>>>
>>> On Fri, Apr 14, 2017 at 3:22 PM, Sam Lambie 
>>> wrote:
>>>
 I just did that and will monitor it over the weekend. Thanks for the
 tip. Lastly, The Sync coming out of the Sync Box into the timing port of
 the Medusa should work right?

 On Fri, Apr 14, 2017 at 3:20 PM, Sam Lambie 
 wrote:

> Changing the value function on the Radio 4 Sync from 1 to 0 will do
> the trick?
>
> On Fri, Apr 14, 2017 at 3:08 PM, Forrest Christian (List Account) <
> li...@packetflux.com> wrote:
>
>> This error means you have sync over power pulses coming in from the
>> syncinjector.
>>
>> The radio is seeing the old-style pulses and is trying to lock onto
>> them, which won't work reliably - since the pulses aren't even close to
>> what it's expecting.
>>
>> You need to disable the pulses in the injector in some way.   If
>> you've got a SiteMonitor base unit attached, just turn off sync on those
>> ports.   If you don't, then just use a cambium power supply and skip the
>> injector, or if you don't have any radios which need the sync over power
>> pulse attached to the injector, make a cable shorting pins 1 and 2 of a
>> RJ45 jack and plug that into the sync input port on the syncinjector.
>>
>>
>>
>> On Thu, Apr 13, 2017 at 9:28 AM, Sam Lambie 
>> wrote:
>>
>>> Medusa doesn't seem to like the packetflux gps. I am getting this
>>> most of the time.
>>>
>>> 04/13/2017 : 09:12:44 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:12:45 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:12:45 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:00 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:03 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:03 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:03 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:05 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:05 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:05 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:07 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:07 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:07 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:09 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:09 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:09 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:12 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:12 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:12 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:14 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:14 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:14 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:16 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:16 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:21 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:23 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:23 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:23 MDT 

Re: [AFMUG] Addition to new site.

[Forrest Christian (List Account)]

This is definitely in the weird category.

Can you verify how old this syncbox 12 is?   I'm guessing that it is new
from us in February.

Can you also let me know how you cabled the syncbox to the medusa?

The two weird items here are:

1) Why is it not picking up sync from the timing port?   (Cabling issue?
There's a special cable from the syncbox to the aux port since the aux port
is a 8p8c with a different pinout)

2) Why does it think it's picking up sync from the power port?



On Mon, Apr 17, 2017 at 8:45 AM, Sam Lambie  wrote:

> Well, That didn't work... I turned off Sync to the radio via the Site
> Monitor on Friday and the Radio still flopped all weekend. It still thinks
> it is getting sync from the power port and never has indicated that it is
> getting sync from the timing port. Are there any settings on the radio that
> I am missing?
> [image: Inline image 1]
> [image: Inline image 2]
>
> On Fri, Apr 14, 2017 at 5:53 PM, Forrest Christian (List Account) <
> li...@packetflux.com> wrote:
>
>> Yes, that was correct, and yes, as long as it's a recent syncbox it
>> should work fine.
>>
>> -forrest
>>
>> On Fri, Apr 14, 2017 at 3:22 PM, Sam Lambie  wrote:
>>
>>> I just did that and will monitor it over the weekend. Thanks for the
>>> tip. Lastly, The Sync coming out of the Sync Box into the timing port of
>>> the Medusa should work right?
>>>
>>> On Fri, Apr 14, 2017 at 3:20 PM, Sam Lambie 
>>> wrote:
>>>
 Changing the value function on the Radio 4 Sync from 1 to 0 will do the
 trick?

 On Fri, Apr 14, 2017 at 3:08 PM, Forrest Christian (List Account) <
 li...@packetflux.com> wrote:

> This error means you have sync over power pulses coming in from the
> syncinjector.
>
> The radio is seeing the old-style pulses and is trying to lock onto
> them, which won't work reliably - since the pulses aren't even close to
> what it's expecting.
>
> You need to disable the pulses in the injector in some way.   If
> you've got a SiteMonitor base unit attached, just turn off sync on those
> ports.   If you don't, then just use a cambium power supply and skip the
> injector, or if you don't have any radios which need the sync over power
> pulse attached to the injector, make a cable shorting pins 1 and 2 of a
> RJ45 jack and plug that into the sync input port on the syncinjector.
>
>
>
> On Thu, Apr 13, 2017 at 9:28 AM, Sam Lambie 
> wrote:
>
>> Medusa doesn't seem to like the packetflux gps. I am getting this
>> most of the time.
>>
>> 04/13/2017 : 09:12:44 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:12:45 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:12:45 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:00 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:03 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:03 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:03 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:05 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:05 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:05 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:07 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:07 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:07 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:09 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:09 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:09 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:12 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:12 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:12 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:14 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:14 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:14 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:16 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:16 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:21 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:23 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:23 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:23 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:25 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:25 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:27 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:30 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:30 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:30 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:32 MDT : Lost sync pulse from 

Re: [AFMUG] Addition to new site.

[Sam Lambie]

Well, That didn't work... I turned off Sync to the radio via the Site
Monitor on Friday and the Radio still flopped all weekend. It still thinks
it is getting sync from the power port and never has indicated that it is
getting sync from the timing port. Are there any settings on the radio that
I am missing?
[image: Inline image 1]
[image: Inline image 2]

On Fri, Apr 14, 2017 at 5:53 PM, Forrest Christian (List Account) <
li...@packetflux.com> wrote:

> Yes, that was correct, and yes, as long as it's a recent syncbox it should
> work fine.
>
> -forrest
>
> On Fri, Apr 14, 2017 at 3:22 PM, Sam Lambie  wrote:
>
>> I just did that and will monitor it over the weekend. Thanks for the tip.
>> Lastly, The Sync coming out of the Sync Box into the timing port of the
>> Medusa should work right?
>>
>> On Fri, Apr 14, 2017 at 3:20 PM, Sam Lambie  wrote:
>>
>>> Changing the value function on the Radio 4 Sync from 1 to 0 will do the
>>> trick?
>>>
>>> On Fri, Apr 14, 2017 at 3:08 PM, Forrest Christian (List Account) <
>>> li...@packetflux.com> wrote:
>>>
 This error means you have sync over power pulses coming in from the
 syncinjector.

 The radio is seeing the old-style pulses and is trying to lock onto
 them, which won't work reliably - since the pulses aren't even close to
 what it's expecting.

 You need to disable the pulses in the injector in some way.   If you've
 got a SiteMonitor base unit attached, just turn off sync on those ports.
 If you don't, then just use a cambium power supply and skip the injector,
 or if you don't have any radios which need the sync over power pulse
 attached to the injector, make a cable shorting pins 1 and 2 of a RJ45 jack
 and plug that into the sync input port on the syncinjector.



 On Thu, Apr 13, 2017 at 9:28 AM, Sam Lambie 
 wrote:

> Medusa doesn't seem to like the packetflux gps. I am getting this most
> of the time.
>
> 04/13/2017 : 09:12:44 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:12:45 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:12:45 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:00 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:03 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:03 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:03 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:05 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:05 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:05 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:07 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:07 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:07 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:09 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:09 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:09 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:12 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:12 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:12 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:14 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:14 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:14 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:16 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:16 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:21 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:23 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:23 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:23 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:25 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:25 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:27 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:30 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:30 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:30 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:32 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:32 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:32 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:33 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:33 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:37 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:39 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:39 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:48 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:51 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:51 MDT : Generating Sync - Free Run

Re: [AFMUG] Addition to new site.

[Forrest Christian (List Account)]

Yes, that was correct, and yes, as long as it's a recent syncbox it should
work fine.

-forrest

On Fri, Apr 14, 2017 at 3:22 PM, Sam Lambie  wrote:

> I just did that and will monitor it over the weekend. Thanks for the tip.
> Lastly, The Sync coming out of the Sync Box into the timing port of the
> Medusa should work right?
>
> On Fri, Apr 14, 2017 at 3:20 PM, Sam Lambie  wrote:
>
>> Changing the value function on the Radio 4 Sync from 1 to 0 will do the
>> trick?
>>
>> On Fri, Apr 14, 2017 at 3:08 PM, Forrest Christian (List Account) <
>> li...@packetflux.com> wrote:
>>
>>> This error means you have sync over power pulses coming in from the
>>> syncinjector.
>>>
>>> The radio is seeing the old-style pulses and is trying to lock onto
>>> them, which won't work reliably - since the pulses aren't even close to
>>> what it's expecting.
>>>
>>> You need to disable the pulses in the injector in some way.   If you've
>>> got a SiteMonitor base unit attached, just turn off sync on those ports.
>>> If you don't, then just use a cambium power supply and skip the injector,
>>> or if you don't have any radios which need the sync over power pulse
>>> attached to the injector, make a cable shorting pins 1 and 2 of a RJ45 jack
>>> and plug that into the sync input port on the syncinjector.
>>>
>>>
>>>
>>> On Thu, Apr 13, 2017 at 9:28 AM, Sam Lambie 
>>> wrote:
>>>
 Medusa doesn't seem to like the packetflux gps. I am getting this most
 of the time.

 04/13/2017 : 09:12:44 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:12:45 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:12:45 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:00 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:03 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:03 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:03 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:05 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:05 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:05 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:07 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:07 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:07 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:09 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:09 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:09 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:12 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:12 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:12 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:14 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:14 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:14 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:16 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:16 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:21 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:23 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:23 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:23 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:25 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:25 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:27 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:30 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:30 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:30 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:32 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:32 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:32 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:33 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:33 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:37 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:39 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:39 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:48 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:51 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:51 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:53 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:55 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:55 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:55 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:13:57 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:13:57 MDT : Generating Sync - Free Run
 04/13/2017 : 09:13:57 MDT : Acquired sync pulse from Power Port
 04/13/2017 : 09:14:00 MDT : Lost sync pulse from Power Port
 04/13/2017 : 09:14:00 

Re: [AFMUG] Addition to new site.

[Sam Lambie]

I just did that and will monitor it over the weekend. Thanks for the tip.
Lastly, The Sync coming out of the Sync Box into the timing port of the
Medusa should work right?

On Fri, Apr 14, 2017 at 3:20 PM, Sam Lambie  wrote:

> Changing the value function on the Radio 4 Sync from 1 to 0 will do the
> trick?
>
> On Fri, Apr 14, 2017 at 3:08 PM, Forrest Christian (List Account) <
> li...@packetflux.com> wrote:
>
>> This error means you have sync over power pulses coming in from the
>> syncinjector.
>>
>> The radio is seeing the old-style pulses and is trying to lock onto them,
>> which won't work reliably - since the pulses aren't even close to what it's
>> expecting.
>>
>> You need to disable the pulses in the injector in some way.   If you've
>> got a SiteMonitor base unit attached, just turn off sync on those ports.
>> If you don't, then just use a cambium power supply and skip the injector,
>> or if you don't have any radios which need the sync over power pulse
>> attached to the injector, make a cable shorting pins 1 and 2 of a RJ45 jack
>> and plug that into the sync input port on the syncinjector.
>>
>>
>>
>> On Thu, Apr 13, 2017 at 9:28 AM, Sam Lambie  wrote:
>>
>>> Medusa doesn't seem to like the packetflux gps. I am getting this most
>>> of the time.
>>>
>>> 04/13/2017 : 09:12:44 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:12:45 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:12:45 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:00 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:03 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:03 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:03 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:05 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:05 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:05 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:07 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:07 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:07 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:09 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:09 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:09 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:12 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:12 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:12 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:14 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:14 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:14 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:16 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:16 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:21 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:23 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:23 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:23 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:25 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:25 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:27 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:30 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:30 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:30 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:32 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:32 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:32 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:33 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:33 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:37 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:39 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:39 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:48 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:51 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:51 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:53 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:55 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:55 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:55 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:13:57 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:13:57 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:13:57 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:14:00 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:14:00 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:14:00 MDT : Acquired sync pulse from Power Port
>>> 04/13/2017 : 09:14:02 MDT : Lost sync pulse from Power Port
>>> 04/13/2017 : 09:14:02 MDT : Generating Sync - Free Run
>>> 04/13/2017 : 09:14:02 MDT : Acquired 

Re: [AFMUG] Addition to new site.

[Sam Lambie]

Changing the value function on the Radio 4 Sync from 1 to 0 will do the
trick?

On Fri, Apr 14, 2017 at 3:08 PM, Forrest Christian (List Account) <
li...@packetflux.com> wrote:

> This error means you have sync over power pulses coming in from the
> syncinjector.
>
> The radio is seeing the old-style pulses and is trying to lock onto them,
> which won't work reliably - since the pulses aren't even close to what it's
> expecting.
>
> You need to disable the pulses in the injector in some way.   If you've
> got a SiteMonitor base unit attached, just turn off sync on those ports.
> If you don't, then just use a cambium power supply and skip the injector,
> or if you don't have any radios which need the sync over power pulse
> attached to the injector, make a cable shorting pins 1 and 2 of a RJ45 jack
> and plug that into the sync input port on the syncinjector.
>
>
>
> On Thu, Apr 13, 2017 at 9:28 AM, Sam Lambie  wrote:
>
>> Medusa doesn't seem to like the packetflux gps. I am getting this most of
>> the time.
>>
>> 04/13/2017 : 09:12:44 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:12:45 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:12:45 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:00 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:03 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:03 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:03 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:05 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:05 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:05 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:07 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:07 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:07 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:09 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:09 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:09 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:12 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:12 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:12 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:14 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:14 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:14 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:16 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:16 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:21 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:23 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:23 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:23 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:25 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:25 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:27 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:30 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:30 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:30 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:32 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:32 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:32 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:33 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:33 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:37 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:39 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:39 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:48 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:51 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:51 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:53 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:55 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:55 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:55 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:57 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:57 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:57 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:14:00 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:14:00 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:14:00 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:14:02 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:14:02 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:14:02 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:14:03 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:14:03 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:14:07 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:14:10 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:14:10 MDT : Generating Sync - Free Run
>> 

Re: [AFMUG] Addition to new site.

[Forrest Christian (List Account)]

This error means you have sync over power pulses coming in from the
syncinjector.

The radio is seeing the old-style pulses and is trying to lock onto them,
which won't work reliably - since the pulses aren't even close to what it's
expecting.

You need to disable the pulses in the injector in some way.   If you've got
a SiteMonitor base unit attached, just turn off sync on those ports.   If
you don't, then just use a cambium power supply and skip the injector, or
if you don't have any radios which need the sync over power pulse attached
to the injector, make a cable shorting pins 1 and 2 of a RJ45 jack and plug
that into the sync input port on the syncinjector.



On Thu, Apr 13, 2017 at 9:28 AM, Sam Lambie  wrote:

> Medusa doesn't seem to like the packetflux gps. I am getting this most of
> the time.
>
> 04/13/2017 : 09:12:44 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:12:45 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:12:45 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:00 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:03 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:03 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:03 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:05 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:05 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:05 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:07 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:07 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:07 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:09 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:09 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:09 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:12 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:12 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:12 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:14 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:14 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:14 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:16 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:16 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:21 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:23 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:23 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:23 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:25 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:25 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:27 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:30 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:30 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:30 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:32 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:32 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:32 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:33 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:33 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:37 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:39 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:39 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:48 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:51 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:51 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:53 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:55 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:55 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:55 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:13:57 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:13:57 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:13:57 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:14:00 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:14:00 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:14:00 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:14:02 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:14:02 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:14:02 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:14:03 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:14:03 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:14:07 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:14:10 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:14:10 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:14:10 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:14:12 MDT : Lost sync pulse from Power Port
> 04/13/2017 : 09:14:12 MDT : Generating Sync - Free Run
> 04/13/2017 : 09:14:12 MDT : Acquired sync pulse from Power Port
> 04/13/2017 : 09:14:14 

Re: [AFMUG] Addition to new site.

[Sam Lambie]

Yeah, I am going that route. Not worth it to me to worry about GPS going
out in the middle of the night like it did last night...

On Fri, Apr 14, 2017 at 6:59 AM, Dave  wrote:

> For that many subs I would have went full out on sync and POE using the
> CMM5
>
>
> On 04/12/2017 09:48 PM, Sam Lambie wrote:
>
> Cambium Medusa. Synced with Packetflux Syncbox 12. Powered with
> Syncinjectors by Packetflux.
>
> Just put it up today so no performance reviews yet. 101 customers coming
> from a 450 AP.
>
> Psyched
>
>
> --
>



-- 
-- 
*Sam Lambie*
Taosnet Wireless Tech.
575-758-7598 Office
www.Taosnet.com 

Re: [AFMUG] Addition to new site.

[Dave]

For that many subs I would have went full out on sync and POE using the CMM5


On 04/12/2017 09:48 PM, Sam Lambie wrote:
Cambium Medusa. Synced with Packetflux Syncbox 12. Powered with 
Syncinjectors by Packetflux.


Just put it up today so no performance reviews yet. 101 customers 
coming from a 450 AP.


Psyched



--

Re: [AFMUG] Addition to new site.

[George Skorup]

Do you have the SyncBox 12 powered on the SyncInjector port which in 
turn is connected to the PowerInjector+Sync's GPS port?


(I hope you're using a PowerInjector+Sync and not a SyncInjector to 
power a 450m??? And I hope you have the jumpers set for power on all 
four pairs.)


Is the PowerInjector connected to a SiteMonitor? Do you see the 1PPS 
Active event counter incrementing? That would mean loss of the sync 
pulse from the 'Box.


The SyncBox needs to be a Rev.i. Forrest said previous revisions did not 
have enough drive for the 450i and 450m timing/aux ports. Does your Sync 
Status tab show that the timing port is receiving sync?


I'm sure you know that the power port = sync over power. 450m pulls 70 
watts, and the power interruption scheme with sync-over-power all comes 
back to the bounce/ringing issues mentioned here several times. The 
radio can see two pulses and get very confused.


The new SyncBox Junior Aux port version uses UGPS power from the radio. 
We have several in use on 450i's and it works great.


On 4/13/2017 10:28 AM, Sam Lambie wrote:
Medusa doesn't seem to like the packetflux gps. I am getting this most 
of the time.

04/13/2017 : 09:12:44 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:12:45 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:12:45 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:00 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:03 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:03 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:03 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:05 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:05 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:05 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:07 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:07 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:07 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:09 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:09 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:09 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:12 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:12 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:12 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:14 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:14 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:14 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:16 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:16 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:21 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:23 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:23 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:23 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:25 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:25 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:27 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:30 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:30 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:30 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:32 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:32 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:32 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:33 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:33 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:37 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:39 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:39 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:48 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:51 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:51 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:53 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:55 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:55 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:55 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:57 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:57 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:57 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:00 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:00 MDT : Generating Sync - Free Run
04/13/2017 : 09:14:00 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:02 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:02 MDT : Generating Sync - Free Run
04/13/2017 : 09:14:02 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:03 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:03 MDT : Generating Sync - Free Run
04/13/2017 : 09:14:07 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:10 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:10 MDT : Generating Sync - Free Run
04/13/2017 : 09:14:10 MDT : Acquired sync pulse from Power Port

Re: [AFMUG] Addition to new site.

[SmarterBroadband]



 

WOW bet they are much happier now.

 

We went 450M with 77 customers and saw throughput double. 

 

 

From: Af [mailto:af-boun...@afmug.com] On Behalf Of Sam Lambie
Sent: Thursday, April 13, 2017 1:01 PM
To: af@afmug.com
Subject: Re: [AFMUG] Addition to new site.

 

Yep on the 450 AP with 101 Customers... A little overloaded!

 

Thanks Sean for the tip. I'll keep monkeying around.

 

On Thu, Apr 13, 2017 at 12:28 PM, Sean Heskett <af...@zirkel.us 
<mailto:af...@zirkel.us> > wrote:

The syncbox 12s seem to be really finicky with where the GPS antenna is 
located.  On 1 tower we had to move it towards the center of all the metal 
instead of away from the tower like you'd think.

 

You can also run a sync cable from another packetflux sync device to the 12.

 

The uGPS is most reliable but the 12 Will work, you just have to monkey with it.

 

Hope that helps!

 

-Sean

 

On Thu, Apr 13, 2017 at 8:28 AM Sam Lambie <samtaos...@gmail.com 
<mailto:samtaos...@gmail.com> > wrote:

Medusa doesn't seem to like the packetflux gps. I am getting this most of the 
time.


04/13/2017 : 09:12:44 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:12:45 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:12:45 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:00 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:03 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:03 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:03 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:05 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:05 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:05 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:07 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:07 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:07 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:09 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:09 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:09 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:12 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:12 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:12 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:14 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:14 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:14 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:16 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:16 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:21 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:23 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:23 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:23 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:25 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:25 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:27 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:30 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:30 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:30 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:32 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:32 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:32 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:33 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:33 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:37 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:39 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:39 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:48 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:51 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:51 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:53 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:55 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:55 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:55 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:57 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:57 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:57 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:00 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:00 MDT : Generating Sync - Free Run
04/13/2017 : 09:14:00 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:02 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:02 MDT : Generating Sync - Free Run
04/13/2017 : 09:14:02 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:03 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:03 MDT : Generating Sync - Free Run
04/13/2017 : 09:14:07 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:10 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:10 MDT : Generating Sync - Free Run
04/13/2017 : 09:14:10 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:12 MDT : Lost sync pulse from Power Po

Re: [AFMUG] Addition to new site.

[Sam Lambie]

Yep on the 450 AP with 101 Customers... A little overloaded!

Thanks Sean for the tip. I'll keep monkeying around.

On Thu, Apr 13, 2017 at 12:28 PM, Sean Heskett  wrote:

> The syncbox 12s seem to be really finicky with where the GPS antenna is
> located.  On 1 tower we had to move it towards the center of all the metal
> instead of away from the tower like you'd think.
>
> You can also run a sync cable from another packetflux sync device to the
> 12.
>
> The uGPS is most reliable but the 12 Will work, you just have to monkey
> with it.
>
> Hope that helps!
>
> -Sean
>
> On Thu, Apr 13, 2017 at 8:28 AM Sam Lambie  wrote:
>
>> Medusa doesn't seem to like the packetflux gps. I am getting this most of
>> the time.
>>
>> 04/13/2017 : 09:12:44 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:12:45 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:12:45 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:00 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:03 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:03 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:03 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:05 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:05 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:05 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:07 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:07 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:07 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:09 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:09 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:09 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:12 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:12 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:12 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:14 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:14 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:14 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:16 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:16 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:21 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:23 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:23 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:23 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:25 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:25 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:27 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:30 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:30 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:30 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:32 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:32 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:32 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:33 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:33 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:37 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:39 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:39 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:48 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:51 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:51 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:53 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:55 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:55 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:55 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:13:57 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:13:57 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:13:57 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:14:00 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:14:00 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:14:00 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:14:02 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:14:02 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:14:02 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:14:03 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:14:03 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:14:07 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:14:10 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:14:10 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:14:10 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:14:12 MDT : Lost sync pulse from Power Port
>> 04/13/2017 : 09:14:12 MDT : Generating Sync - Free Run
>> 04/13/2017 : 09:14:12 MDT : Acquired sync pulse from Power Port
>> 04/13/2017 : 09:14:14 MDT : 

Re: [AFMUG] Addition to new site.

[Sam Lambie]

Medusa doesn't seem to like the packetflux gps. I am getting this most of
the time.

04/13/2017 : 09:12:44 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:12:45 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:12:45 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:00 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:03 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:03 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:03 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:05 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:05 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:05 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:07 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:07 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:07 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:09 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:09 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:09 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:12 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:12 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:12 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:14 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:14 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:14 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:16 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:16 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:21 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:23 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:23 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:23 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:25 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:25 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:27 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:30 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:30 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:30 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:32 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:32 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:32 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:33 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:33 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:37 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:39 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:39 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:48 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:51 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:51 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:53 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:55 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:55 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:55 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:13:57 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:13:57 MDT : Generating Sync - Free Run
04/13/2017 : 09:13:57 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:00 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:00 MDT : Generating Sync - Free Run
04/13/2017 : 09:14:00 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:02 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:02 MDT : Generating Sync - Free Run
04/13/2017 : 09:14:02 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:03 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:03 MDT : Generating Sync - Free Run
04/13/2017 : 09:14:07 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:10 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:10 MDT : Generating Sync - Free Run
04/13/2017 : 09:14:10 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:12 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:12 MDT : Generating Sync - Free Run
04/13/2017 : 09:14:12 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:14 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:14 MDT : Generating Sync - Free Run
04/13/2017 : 09:14:14 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:15 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:15 MDT : Generating Sync - Free Run
04/13/2017 : 09:14:20 MDT : Acquired sync pulse from Power Port
04/13/2017 : 09:14:22 MDT : Lost sync pulse from Power Port
04/13/2017 : 09:14:22 MDT : Generating Sync - Free Run
 tried replacing the timing cable and making adjustments to no avail. It
comes and goes. Going up there to plug in the old 450 ap to it and see if
that AP sees the same issue.Sean Heskitt, have you seen any issues with
this setup?

On Wed, Apr 12, 2017 at 9:06 PM, Jaime Solorza 
wrote:

> AwesomeGreat viewWife and I will be headed out to Taos soon...
>
> On Apr 12, 2017 8:48 PM, "Sam Lambie" 

Re: [AFMUG] Addition to new site.

[Jaime Solorza]

AwesomeGreat viewWife and I will be headed out to Taos soon...

On Apr 12, 2017 8:48 PM, "Sam Lambie"  wrote:

> Cambium Medusa. Synced with Packetflux Syncbox 12. Powered with
> Syncinjectors by Packetflux.
>
> Just put it up today so no performance reviews yet. 101 customers coming
> from a 450 AP.
>
> Psyched
>
>

Re: [AFMUG] Addition to new site.

[Jacob Turner]

Gorgeous site!

On Wed, Apr 12, 2017 at 7:48 PM, Sam Lambie  wrote:

> Cambium Medusa. Synced with Packetflux Syncbox 12. Powered with
> Syncinjectors by Packetflux.
>
> Just put it up today so no performance reviews yet. 101 customers coming
> from a 450 AP.
>
> Psyched
>
>