Email Delivery

Receive new posts as email.

Email address

Syndicate this site

RSS | Atom

Contact

About This Site
Contact Us
Privacy Policy

Search


November 2010
Sun Mon Tues Wed Thurs Fri Sat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30        

Stories by Category

Basics :: Basics
Casting :: Casting Listen In Podcasts Videocasts
Culture :: Culture Hacking
Deals :: Deals
FAQ :: FAQ
Future :: Future
Hardware :: Hardware Adapters Appliances Chips Consumer Electronics Gaming Home Entertainment Music Photography Video Gadgets Mesh Monitoring and Testing PDAs Phones Smartphones
Industry :: Industry Conferences Financial Free Health Legal Research Vendor analysis
International :: International
Media :: Media Locally cached Streaming
Metro-Scale Networks :: Metro-Scale Networks Community Networking Municipal
Network Types :: Network Types Broadband Wireless Cellular 2.5G and 3G 4G Power Line Satellite
News :: News Mainstream Media
Politics :: Politics Regulation Sock Puppets
Schedules :: Schedules
Security :: Security 802.1X
Site Specific :: Site Specific Administrative Detail April Fool's Blogging Book review Cluelessness Guest Commentary History Humor Self-Promotion Unique Wee-Fi Who's Hot Today?
Software :: Software Open Source
Spectrum :: Spectrum 60 GHz
Standards :: Standards 802.11a 802.11ac 802.11ad 802.11e 802.11g 802.11n 802.20 Bluetooth MIMO UWB WiGig WiMAX ZigBee
Transportation and Lodging :: Transportation and Lodging Air Travel Aquatic Commuting Hotels Rails
Unclassified :: Unclassified
Vertical Markets :: Vertical Markets Academia Enterprise WLAN Switches Home Hot Spot Aggregators Hot Spot Advertising Road Warrior Roaming Libraries Location Medical Public Safety Residential Rural SOHO Small-Medium Sized Business Universities Utilities wISP
Voice :: Voice

Archives

November 2010 | October 2010 | September 2010 | August 2010 | July 2010 | June 2010 | May 2010 | April 2010 | March 2010 | February 2010 | January 2010 | December 2009 | November 2009 | October 2009 | September 2009 | August 2009 | July 2009 | June 2009 | May 2009 | April 2009 | March 2009 | February 2009 | January 2009 | December 2008 | November 2008 | October 2008 | September 2008 | August 2008 | July 2008 | June 2008 | May 2008 | April 2008 | March 2008 | February 2008 | January 2008 | December 2007 | November 2007 | October 2007 | September 2007 | August 2007 | July 2007 | June 2007 | May 2007 | April 2007 | March 2007 | February 2007 | January 2007 | December 2006 | November 2006 | October 2006 | September 2006 | August 2006 | July 2006 | June 2006 | May 2006 | April 2006 | March 2006 | February 2006 | January 2006 | December 2005 | November 2005 | October 2005 | September 2005 | August 2005 | July 2005 | June 2005 | May 2005 | April 2005 | March 2005 | February 2005 | January 2005 | December 2004 | November 2004 | October 2004 | September 2004 | August 2004 | July 2004 | June 2004 | May 2004 | April 2004 | March 2004 | February 2004 | January 2004 | December 2003 | November 2003 | October 2003 | September 2003 | August 2003 | July 2003 | June 2003 | May 2003 | April 2003 | March 2003 | February 2003 | January 2003 | December 2002 | November 2002 | October 2002 | September 2002 | August 2002 | July 2002 | June 2002 | May 2002 | April 2002 | March 2002 | February 2002 | January 2002 | December 2001 | November 2001 | October 2001 | September 2001 | August 2001 | July 2001 | June 2001 | May 2001 | April 2001 |

Recent Entries

In-Flight Wi-Fi and In-Flight Bombs
Can WPA Protect against Firesheep on Same Network?
Southwest Sets In-Flight Wi-Fi at $5
Eye-Fi Adds a View for Web Access
Firesheep Makes Sidejacking Easy
Wi-Fi Direct Certification Starts
Decaf on the Starbucks Digital Network
Google Did Snag Passwords
WiMax and LTE Not Technically 4G by ITU Standards
AT&T Wi-Fi Connections Keep High Growth with Free Service

Site Philosophy

This site operates as an independent editorial operation. Advertising, sponsorships, and other non-editorial materials represent the opinions and messages of their respective origins, and not of the site operator. Part of the FM Tech advertising network.

Copyright

Entire site and all contents except otherwise noted © Copyright 2001-2010 by Glenn Fleishman. Some images ©2006 Jupiterimages Corporation. All rights reserved. Please contact us for reprint rights. Linking is, of course, free and encouraged.

Powered by
Movable Type

« Google's SF Participation Raises Privacy Hackles | Main | Laptop Theft on Rise in SF »

April 10, 2006

Boston Globe Disses MIMO

Did MIMO run over Eileen McCluskey's bike as a kid? I'm slightly baffled by the treatment of MIMO technology in this otherwise reasonable set of consumer advice about Wi-Fi in the Boston Globe yesterday. It's possible the single source cited in the article poisoned her information well.

"These Multi Input, Multi Output gadgets achieve excellent signal quality and range by hogging the wireless spectrum up to 219 yards away. If you live in the city or suburbs, your MIMO router will knock out your wireless-enabled neighbors' connections." Huh?

Here's my letter to the editor just sent off to the Globe:

"Less Is More" (Apr. 9, 2005) contains a glaring error regarding multiple antenna wireless networking. The reporter says that MIMO (multiple not "multi" input/output) gateways hog spectrum and knock out neighbors' reception. This is entirely untrue. MIMO gateways for Wi-Fi, unlike previous range-extending Wi-Fi, are more sensitive receivers not more powerful transmitters.

It used to be that to extend range, you pumped up the volume (increased signal power output), which could interfere with neighboring networks. MIMO uses several antennas to better reconcile radio signals as they reflect off walls and metal objects. This allows the technology to more discretely receive fainter or less clear signals from further away.

There is the danger that a newer form of Wi-Fi, called 802.11n, that will be on the market soon may interfere with older networks in some cases, but Wi-Fi product makers haven't finalized the standard, and it's one of their key concerns.

The other also states that MIMO won't work with free Wi-Fi hotspots. This is entirely untrue. Current MIMO gateways and future gatweays that use MIMO as one piece in a faster Wi-Fi standard are entirely compatible with Wi-Fi equipment sold as long as ago as the first devices in 1999. MIMO devices won't communicate at their highest possible speeds except with compatible devices from the same maker (today) or with the newer standard with any maker (in about 3 to 6 months).

3 Comments

Well, there is a grain of truth to the accusation that MIMO equipment can negatively affect other networks, if you consider Atheros's Super G to be MIMO. Personally, I don't. Airgo's "True MIMO" is definitely MIMO, Video54's BeamFlex sorta-kinda might be, but Atheros relies primarily on channel bonding to get throughput. Channel bonding has been proven to pollute the local EM environment.
http://www.theregister.co.uk/2003/12/18/tests_confirm_atheros_super_g/ is a good starting point for looking into one set of experiments showing this effect. The confusion occurs because Atheros has been stubborn regarding this issue, and also because they also call their stuff MIMO when it's not.

I have seen increased interference from pre-n gear since the devices have an increased effective transmit power due to the additional required radios and power amplifiers. For example, a typical 11g AP has a single 20 dBm (100 mW) power amplifier (20 dBm PA's are relatively cost effective and hence fairly popular in consumer 11g gear). A typical pre-N solution would have two 20 dBm PA's -- one for each transmit radio chain. This exactly doubles the effective output power of the device, at least in the U.S. where legal power limits are much higher. So in addition to the increased interference from (optional) 40 Mhz channels, 11n devices will also generate more interference in practice due to higher effective output powers.

Glenn, if nothing else, you've at least provided readers one of the few plain-English explanations of MIMO technology I've read. Thanks for the clarity.