Wireless Interference: Smashup On Interstate 2.4

 
 
By Larry Seltzer  |  Posted 2003-04-03 Email Print this article Print
 
 
 
 
 
 
 

You just can't win in this unregulated wireless spectrum. If the network's not interfering with the phone, the microwave oven's interfering with the network.

Click! Click! Click! Thats the sound of my 2.4GHz Siemens Gigaset phone system when my 802.11b wireless network is nearby, especially in some parts of the house. I actually dont notice it so much, but people I talk to complain. My range on the phone and wireless network is also greatly diminished when both are operating. Wireless comminication frequencies have moved up over the years for a variety of reasons, and the current hot zone is 2.4 GHz. All the wireless devices you want to use operate in that range. In theory these devices are supposed to know how to stay out of each others way, but try to use enough of them at once and youll find out otherwise.
And its not just wireless communications devices that make trouble. The biggest problem in a lot of houses is the microwave oven, which vomits electromagnetic interference all over everything within several feet of it. This can be a problem intermittently for the cordless phone, but less so for the wireless network in my case. I dont usually keep a node on that side of the kitchen.
My interim solution has been to buy a 900MHz phone. You may remember that 900MHz was the 2.4GHz of the mid-1990s. It was the new advanced feature that gave cordless phones better range, less interference, whatever is good about phones, they had it. They were certainly better than the first generation of cordless phones, which worked in the 46-49MHz range, where anything with a motor, from the garage door opener to the electric toothbrush will interfere. Look up tech support on these devices and theyll tell you to keep your phone base station and wireless access point away from each other, but thats easier said than done. My access point needs to be near my other networking equipment, which is in my office. My base station is my primary buisness phone and in -- you guessed it -- my office. Partly because higher frequencies are better in some ways and partly because 900MHz got crowded the FCC opened up the 2.4GHz range. Now we even have the 5.8 GHz range open; its where youll find 802.11a networks and a lot of newer, even more expensive phones.
So like I said, 2.4GHz wasnt big enough for my phones and my network. One of them had to go. An 802.11a wireless network is a possibility because I actually have the equipment left over from a networking book I wrote, but when I used it I found the range to be much less than 802.11b. The higher frequencies have better range out in the middle of the Sahara, but in a house with walls and other obstructions the picture is murkier. Talk to real engineers who work on this stuff and youll find them very reticent to give numbers for range of their products. The truth is that it depends on a large number of variables, too many to predict. That meant moving the phone. The reason I bought the model I bought (the Siemens Gigaset 2420) was that at the time it was the only system that had multiple lines, multiple handsets, caller ID, and a bunch of other things. You can find a lot of phones with these features in 2.4GHz models now, and even a few at outrageous prices in 5.8GHz, but nothing like it in 900MHz. So for now Im satisfying myself with a lesser 900MHz phone. It doesnt have caller ID, no multiple handsets, only 10 speed dials. But I can use the phone right next to my wireless notebook and not sound like a telegraph. Security Supersite Editor Larry Seltzer has worked in and written about the computer industry since 1983.
 
 
 
 
Larry Seltzer has been writing software for and English about computers ever since—,much to his own amazement—,he graduated from the University of Pennsylvania in 1983.

He was one of the authors of NPL and NPL-R, fourth-generation languages for microcomputers by the now-defunct DeskTop Software Corporation. (Larry is sad to find absolutely no hits on any of these +products on Google.) His work at Desktop Software included programming the UCSD p-System, a virtual machine-based operating system with portable binaries that pre-dated Java by more than 10 years.

For several years, he wrote corporate software for Mathematica Policy Research (they're still in business!) and Chase Econometrics (not so lucky) before being forcibly thrown into the consulting market. He bummed around the Philadelphia consulting and contract-programming scenes for a year or two before taking a job at NSTL (National Software Testing Labs) developing product tests and managing contract testing for the computer industry, governments and publication.

In 1991 Larry moved to Massachusetts to become Technical Director of PC Week Labs (now eWeek Labs). He moved within Ziff Davis to New York in 1994 to run testing at Windows Sources. In 1995, he became Technical Director for Internet product testing at PC Magazine and stayed there till 1998.

Since then, he has been writing for numerous other publications, including Fortune Small Business, Windows 2000 Magazine (now Windows and .NET Magazine), ZDNet and Sam Whitmore's Media Survey.
 
 
 
 
 
 
 

Submit a Comment

Loading Comments...
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Rocket Fuel