Email:
> supp...@snappytelecom.net
>
> From: "Chadwick Wachs" mailto:c...@auwireless.net>>
> To: "WISPA General List" mailto:wireless@wispa.org>>
> Sent: Monday, June 20, 2016 12:47:43 PM
> Subject: Re: [WISPA] Any IgniteNet MetroLinq customers out
t;>> linked up on the bench, but would not link nor go thru the alignment
>>>> process on a 400m link).
>>>>
>>>> Regards.
>>>>
>>>> Faisal Imtiaz
>>>> Snappy Internet & Telecom
>>>> 7266 SW 48 Street
>>>&g
Going with faulty boards. Had a link with good signal then it died and we
could never get the 60 GHz radio to recover. Tried a couple factory Ignite
power bricks with the same result. Either real bad firmware or a bad radio
module. Going back for repair.
On Mon, Jun 20, 2016 at 11:02 PM, Judd Da
.
>>>
>>> Faisal Imtiaz
>>> Snappy Internet & Telecom
>>> 7266 SW 48 Street
>>> Miami, FL 33155
>>> Tel: 305 663 5518 x 232
>>>
>>> Help-desk: (305)663-5518 Option 2 or Email: supp...@snappytelecom.net
>>>
>>> --
>&g
>>
>> Regards.
>>
>> Faisal Imtiaz
>> Snappy Internet & Telecom
>> 7266 SW 48 Street
>> Miami, FL 33155
>> Tel: 305 663 5518 x 232
>>
>> Help-desk: (305)663-5518 Option 2 or Email: supp...@snappytelecom.net
>>
>> ----
Almost sounds like a low voltage issue or faulty boards internally.
On Jun 20, 2016 10:48 AM, "Chadwick Wachs" wrote:
> Update to all on this. We are running MCS1, the latest public firmware
> and contacted Ignite support. They are responsive. We did get the 60 GHz
> radios to link up once - fo
t;
> Help-desk: (305)663-5518 Option 2 or Email: supp...@snappytelecom.net
>
> --
>
> *From: *"Chadwick Wachs"
> *To: *"WISPA General List"
> *Sent: *Monday, June 20, 2016 12:47:43 PM
> *Subject: *Re: [WISPA] Any IgniteNet MetroLinq customer
"WISPA General List"
> Sent: Monday, June 20, 2016 11:37:00 PM
> Subject: Re: [WISPA] Any IgniteNet MetroLinq customers out there
> How are you powering them? Power brick or switch?
> On Jun 20, 2016 7:35 PM, "Faisal Imtiaz" < fai...@snappytelecom.net > wrote
reet
Miami, FL 33155
Tel: 305 663 5518 x 232
Help-desk: (305)663-5518 Option 2 or Email: supp...@snappytelecom.net
--
*From: *"Chadwick Wachs"
*To: *"WISPA General List"
*Sent: *Monday, June 20, 2016 12:47:43 PM
*Subject: *Re: [WISPA] Any Ignit
supp...@snappytelecom.net
> From: "Chadwick Wachs"
> To: "WISPA General List"
> Sent: Monday, June 20, 2016 12:47:43 PM
> Subject: Re: [WISPA] Any IgniteNet MetroLinq customers out there
> Update to all on this. We are running MCS1, the latest public firmware a
Update to all on this. We are running MCS1, the latest public firmware and
contacted Ignite support. They are responsive. We did get the 60 GHz
radios to link up once - for about 30 minutes. Then, the 60 GHz radio on
the client end died. Can't open the 60 GHz aiming tool and the dashboard
acts li
Aiming takes patience, the scopes aren't perfect but a huge help. We
found that turning off auto MCS and using fixed lower rate helped a
lot. Make sure you have the newest firmware, I believe there are more
updates coming out soon as well. IgniteNet support was responsive and
very helpful when w
smartphone
Original message From: Chadwick Wachs
Date: 6/15/16 7:55 PM (GMT-05:00) To: Wireless@wispa.org Subject: [WISPA] Any
IgniteNet MetroLinq customers out there
I have been trying for a couple days to get a new PTP60-35 60 GHz link up and
running with no luck. Looking
.net
> From: "Chadwick Wachs"
> To: "WISPA General List"
> Sent: Wednesday, June 15, 2016 7:55:04 PM
> Subject: [WISPA] Any IgniteNet MetroLinq customers out there
> I have been trying for a couple days to get a new PTP60-35 60 GHz link up and
> running with no
I have been trying for a couple days to get a new PTP60-35 60 GHz link up
and running with no luck. Looking for some help / suggestions from anyone
who has been successful getting links up. The 5 GHz link is working but 60
never trains up. I bought the spotting scopes and each end is dead center.
G
15 matches
Mail list logo
