<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks Bob, much appreciatted<br>
<br>
This started on a project we where working on in Phoenix doing due
diligence on a data management system with multiple wireless inputs.<br>
<br>
It was plagued with errors shut downs and faults and so I did a
complete inventory of the buildings wireless systems and also did
wireless frequency detection mapping on several layers to see what was
what.<br>
<br>
Multiple signal detection at 802.11b ( yes its up to 2.4ghz - 2.6 was a
typo ) and 900 htz was detected outside of the buildings frame but with
potential interference to the remotes together with 5.8 .<br>
<br>
The second weekend we where there suddenly the system started
functioning correctly and the cross signals disappeared and I went to
the high rise next door and a financial company was in the process of
shutting down there entire business and turning of all the MISIT
networks which were using Canopy and extensive wi - fi with boosters
all over the place . In the same clients building on one floor all of
the 5.8ghz cordless phones kept dropping signals and malfunctioning and
after the Canopy wi fi experience we went looking for a similar issue
and found that the floor used 802.11n 5.8ghz airport extreme all over
the place, turned of the airport bases and the phones work fine turn
them on and the phone system cordless sucks. We also found that
multiple systems are set up with little MISIT support and multiple
medical systems are set up by the companies who supply the equipment
and the SCADA in turn is set up by a maintenance contract team and they
do not talk or coordinate with each other period. An error arises and
fingers are pointed<br>
<br>
After this we contacted several other hospitals who are having similar
problems and asked if anyone had done a signal conflict analysis and
test and whether this was part of any systems integration due diligence
and of course its not and they had not. We also then went to several
other clients in the area and drew the same conclusions as they had
been having loads of interference. This is especially pertinent on
signal transmitters and boosters.<br>
<br>
It would seem like everything else that 900 was used until it got
crowded then up we went to 2.4 now thats getting crowded we go to 5.8<br>
<br>
Go ask if anyone has done real world testing and analysis with best
practices and the answer seems to be no hence our question<br>
<br>
Needless to say this is scaring the crap outa the insurance carriers<br>
<br>
( : ( : pete<br>
<div class="moz-signature">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="ProgId" content="Word.Document">
<meta name="Generator" content="Microsoft Word 11">
<meta name="Originator" content="Microsoft Word 11">
<link rel="File-List"
href="Peter%20Baston%20Signature_files/filelist.xml">
<title>Peter Baston</title>
<o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address">
<o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
<o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State">
<o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PostalCode"><!--[if gte mso 9]><xml>
<o:DocumentProperties>
<o:Author>ideapete</o:Author>
<o:LastAuthor>ideapete</o:LastAuthor>
<o:Revision>2</o:Revision>
<o:TotalTime>3</o:TotalTime>
<o:Created>2007-07-27T22:44:00Z</o:Created>
<o:LastSaved>2007-07-27T22:44:00Z</o:LastSaved>
<o:Pages>1</o:Pages>
<o:Words>42</o:Words>
<o:Characters>241</o:Characters>
<o:Company>IDEAS</o:Company>
<o:Lines>2</o:Lines>
<o:Paragraphs>1</o:Paragraphs>
<o:CharactersWithSpaces>282</o:CharactersWithSpaces>
<o:Version>11.8132</o:Version>
</o:DocumentProperties>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" LatentStyleCount="156">
</w:LatentStyles>
</xml><![endif]--><!--[if !mso]><object
classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC4D" id=ieooui></object>
<style>
st1\:*{behavior:url(#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:#606420;
text-decoration:underline;
text-underline:single;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style><!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";
mso-ansi-language:#0400;
mso-fareast-language:#0400;
mso-bidi-language:#0400;}
</style>
<![endif]-->
</o:SmartTagType></o:SmartTagType></o:SmartTagType></o:SmartTagType></o:SmartTagType></o:SmartTagType>
<div class="Section1">
<p class="MsoNormal"><span
style="font-size: 10pt; font-family: Arial; color: maroon;">Peter
Baston</span></p>
<p class="MsoNormal"><strong><span
style="font-size: 10pt; font-family: Arial; color: maroon;">IDEAS</span></strong></p>
<p class="MsoNormal"><span
style="font-size: 10pt; font-family: Arial; color: maroon;"><a
href="http://www.ideapete.com/"><em><span style="font-family: Arial;">www.ideapete.com</span></em></a></span></p>
<br>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<br>
<br>
Bob Knight wrote:
<blockquote cite="mid:494C4C2C.9060903@bobknight.net" type="cite">Another
note - polarization may be your friend in crowded spectrum.
<br>
<br>
Bob
<br>
<br>
<br>
Bob Knight wrote:
<br>
<blockquote type="cite">You need to look at the WISPA archives
relative to Motorola Canopy. While it is the largest deployed base in
that community, it also is considered to be the largest problem
interference-wise, at least in the 2.4 (not 2.6) Ghz band. In our area,
though, they're using 900 Mhz.
<br>
<br>
In 2.4, there are 11 channels (in the US, at least). Ideally (and
nowadays, this is far from ideal given the spectrum pollution), one
wants things 5 channels apart, especially when hidden node problems are
anticipated. The problem is that hidden node is going to be a problem
pretty much no matter what measures you take.
<br>
<br>
WiMax can be used in various bands from 2-66 Ghz. 2.5 and 3.5 are
licensed spectrum and it can be used in 5.8. It seems to be suited to
700 Mhz as well.
<br>
<br>
Our experience on 5.8 is very positive. We use it for our backhauls.
One nice thing about this spectrum allocation is that the channels are
non-overlapping. Our backhaul sink for the DS-3 has 5 different links
coming in with no interference.
<br>
<br>
Admittedly, we are rural. But I guarantee that if the Santa Fe spectrum
in 5.8 (or Eldo for that matter) were crowded, we'd see it. And we
don't.
<br>
<br>
So where are you seeing problems?
<br>
<br>
Bob
<br>
<br>
peter wrote:
<br>
<blockquote type="cite">We are involved in several projects
investigating wireless conflict signals within corporations and
hospitals and are finding some strange results which could impact Wi-Fi
and Wi - Max usage and indeed the whole paradigm first mile wireless
use.
<br>
<br>
Basically this is what we are seeing
<br>
<br>
Open wireless frequencies that have been typical used are 900 - 2.6 and
now 5.8ghtz.
<br>
<br>
802.11 of various types operates in both the 2.6 and 5.8 sectors ( 5.8
is 802.11n and 802.16 wi max ) the 900 htz range is packed and so is
the 2.8 ghtz
<br>
<br>
Inside of a hospital for instance multiple monitoring equipment types
and portable phone systems operate on the same frequencies and so does
a huge amount of SCADA operations.
<br>
<br>
Although channel switching is supposed to prevent signal conflict
wi-fi signal boosters and all wimax whether static or mobile is
continually channel hunting and knocking everything else of of the
channel making many types of systems non usable
<br>
<br>
It would seem that a major problem is manufacturers testing their
equipment in a silo arena and this would also be relevant to the white
space transmission requests before the FCC at present
<br>
<br>
This looks like a huge problem and if anyone is experiencing the same
issues please contact us
<br>
<br>
Apparently Motorola with their Canopy system and Intel ( wi-fi and max
) did a large amount of research but when the conflict issues arose
chose to ignore the results or assumed that channel frequency switch
would fix the problem but its not
<br>
<br>
( : ( : pete
<br>
-- <br>
<br>
Peter Baston
<br>
<br>
*IDEAS*
<br>
<br>
/www.ideapete.com/ <a class="moz-txt-link-rfc2396E" href="http://www.ideapete.com/"><http://www.ideapete.com/></a>
<br>
<br>
3210 La Paz Lane
<br>
<br>
Santa Fe, NM 87507
<br>
<br>
/Albuquerque// Office: 505-890-9649/
<br>
<br>
/Santa Fe// Office: 505-629-4227/
<br>
<br>
/Cell: 505-690-3627/
<br>
<br>
/Fax: 866-642-8918/
<br>
<br>
/_<a class="moz-txt-link-freetext" href="Mailto:pete@ideapete.com">Mailto:pete@ideapete.com</a> <a class="moz-txt-link-rfc2396E" href="mailto:pete@ideapete.com"><mailto:pete@ideapete.com></a>_/
<br>
<br>
<br>
<br>
<br>
<br>
------------------------------------------------------------------------
<br>
<br>
_______________________________________________
<br>
1st-mile-nm mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:1st-mile-nm@mailman.dcn.org">1st-mile-nm@mailman.dcn.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://www2.dcn.org/mailman/listinfo/1st-mile-nm">http://www2.dcn.org/mailman/listinfo/1st-mile-nm</a>
<br>
</blockquote>
_______________________________________________
<br>
1st-mile-nm mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:1st-mile-nm@mailman.dcn.org">1st-mile-nm@mailman.dcn.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://www2.dcn.org/mailman/listinfo/1st-mile-nm">http://www2.dcn.org/mailman/listinfo/1st-mile-nm</a>
<br>
</blockquote>
<br>
</blockquote>
</body>
</html>