I have not had a chance to get field experience with the Canopy 430.  I
have a few areas I would like to use it, but am afraid to destroy the
frequency of some of my other 5Ghz backhauls.

Regards,
Chuck Hogg
Shelby Broadband
502-722-9292
ch...@shelbybb.com
http://www.shelbybb.com


-----Original Message-----
From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On
Behalf Of Faisal Imtiaz
Sent: Tuesday, April 13, 2010 10:17 PM
To: WISPA General List
Subject: Re: [WISPA] Ubnt vs Moto vs ... your brand

Hi Chuck,

Do you have any field review/ deployment info comparison of the new
Canopy 430 ?  I would love to hear some comparison info..

Thanks
Faisal.

On 4/13/2010 10:06 PM, Chuck Hogg wrote:
> This is what I am in the process of doing now.  We have another 200 
> subs to be converted next month.  Then another 100 subs after that.  
> Not only is it a multiple truck roll incident, but I already paid for 
> the MikroTik gear...and now am replacing customer equipment with
Canopy.
> ROI just got extended an additional 6 months.  We just replaced a 
> complete Trango 900 AP with Canopy 900.  Performance is just better 
> and it scales.
>
> Regards,
> Chuck Hogg
> Shelby Broadband
> 502-722-9292
> ch...@shelbybb.com
> http://www.shelbybb.com
>
>
> -----Original Message-----
> From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] 
> On Behalf Of Travis Johnson
> Sent: Tuesday, April 13, 2010 9:24 PM
> To: WISPA General List
> Subject: Re: [WISPA] Ubnt vs Moto vs ... your brand
>
> Hi,
>
> Let's keep it simple and easy. With Canopy your system can scale 
> infinitely (due to GPS sync) and latency is always very low and 
> consistent (less than 10ms). With UBNT, you can build a system much 
> cheaper, and one that will probably work in a small, rural area.
> However, it does not scale.
>
> So, the question you have to ask is: Will your network ever grow to 
> the size that you run out of channels? On a single tower, there are 
> roughly six legal channels in the 5.8ghz band (using 20mhz channel 
> size). None of the other channels are legal with UBNT gear. So you 
> have 6 channels to use for your entire network, and you can't 
> co-locate near adjacent channels, and you can't have two AP's on 
> different towers facing each other on the same channel.
>
> The problem we made on our network was trying to use Mikrotik for PtMP

> deployments and discovering that it doesn't scale. We ended up having 
> to go to every customer we had installed on two big towers and change 
> them out to Canopy. So we had to roll a truck twice. :(
>
> Travis
> Microserv
>
>
> Glenn Kelley wrote:
>    
>> In trying to make the right buying decision - some simple answers may

>> help.
>>
>>
>>
>> 1.  What is the meantime failure rate for your ubiquity equipment
>>
>> 2.  What is the avg amount of truck rolls per week you run to fix an 
>> issue vs the # of customers you have?
>> ie- if you have say 1500 clients and do 8 troubleshooting calls a 
>> week
>>      
>    
>> then it would be 1500/8 = .0053% )
>>
>> 3.  how often does a tech call come in (w/o a truck roll) that is 
>> equipment related...  For some reason I think some of the ubiquity 
>> radios just need a power cycle and voila - they behave much better...
>> so - what is the average # of calls per total clients that come in 
>> that are fixed w/ simple methods vs a truck roll for the ubiquity 
>> users ...
>>
>>
>>
>> Moto Users - do you have this info as well:
>>
>> Reason I ask is because I am wondering - if the cost of Moto is 
>> actually worth it...  as a smaller operator - this information would 
>> be most beneficial for sure.
>>
>> Buying a Moto radio - even if 2 or 3 times the $$ if - the service 
>> calls on the back side are much less - might be worth it.
>>
>> Perhaps the cost of Radio vs People (both in manpower as well as 
>> client satisfaction for uptime) make the buying decision much 
>> easier...  but having some numbers to go along with this would be
>>      
> great.
>    
>>
>> Thanks
>>
>>
>>
>>
>>      
> ----------------------------------------------------------------------
> --
> --------
>    
>> WISPA Wants You! Join today!
>> http://signup.wispa.org/
>>
>>      
> ----------------------------------------------------------------------
> --
> --------
>    
>>
>> WISPA Wireless List: wireless@wispa.org
>>
>> Subscribe/Unsubscribe:
>> http://lists.wispa.org/mailman/listinfo/wireless
>>
>> Archives: http://lists.wispa.org/pipermail/wireless/
>>
>>
>>      
>
> ----------------------------------------------------------------------
> --
> --------
> WISPA Wants You! Join today!
> http://signup.wispa.org/
> ----------------------------------------------------------------------
> --
> --------
>
> WISPA Wireless List: wireless@wispa.org
>
> Subscribe/Unsubscribe:
> http://lists.wispa.org/mailman/listinfo/wireless
>
> Archives: http://lists.wispa.org/pipermail/wireless/
>
>
> ----------------------------------------------------------------------
> ----------
> WISPA Wants You! Join today!
> http://signup.wispa.org/
> ----------------------------------------------------------------------
> ----------
>
> WISPA Wireless List: wireless@wispa.org
>
> Subscribe/Unsubscribe:
> http://lists.wispa.org/mailman/listinfo/wireless
>
> Archives: http://lists.wispa.org/pipermail/wireless/
>
>    


------------------------------------------------------------------------
--------
WISPA Wants You! Join today!
http://signup.wispa.org/
------------------------------------------------------------------------
--------
 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/


--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Reply via email to