Slashdot Log In
The Journey of Radios From Hardware to Software
Posted by
Zonk
on Sat Sep 22, 2007 10:15 PM
from the wave-of-the-future dept.
from the wave-of-the-future dept.
An anonymous reader writes "The New York Times is carrying a story all about the process of replacing radios with software. The article tells the tale of Vanu Bose, son of the man who started the Bose company, and his quest to bring software to what was previously a hardware-only enterprise. He met a lot of resistance in the 90s to his ideas, because processor technology was not up to the task. Now that technology has caught up with Vanu, his software (and other products like it) are increasingly replacing now-outdated hardware components. 'Well-established companies like Motorola and Ericsson now use elements of software-defined radio for their base stations. But Mr. Bose was the first to come to market with software that could handle multiple networks with the same equipment. Software radio appears to offer an elegant solution to what has been a vexing problem: how to have a single handset, like a cellphone, communicate across multiple networks. For instance, the G.S.M. standard, for global system for mobile communications, is used broadly in Europe, and most notably in the United States by AT&T.'"
This discussion has been archived.
No new comments can be posted.
The Journey of Radios From Hardware to Software
|
Log In/Create an Account
| Top
| 114 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
An interesting idea (Score:4, Interesting)
(http://127.0.0.1/)
Re:An interesting idea (Score:5, Informative)
(http://127.0.0.1/)
Well, yeah. Square wave outputs do tend to generate alllll sorts of harmonics. But it does technically work. If I were serious about it, I'd at least add a capacitor across the output, to make some attempt at filtration.
The "schematic" involved an 8-pin microprocessor, with two outputs each connected to a 1k resistor. The other ends of both resistors were connected to the antenna. Not very efficient, but as a proof of concept, it was a cool toy. Tuning was completely via software (tweak the timing loop to provide the correct waveform.)
You want pictures? Happy to oblige. (The idea was to see just how simple a transmitter I could make...)
http://www.intellectualism.org/electronics/schematic.jpg [intellectualism.org]
http://www.intellectualism.org/electronics/Closeup.jpg [intellectualism.org]
Re:An interesting idea (Score:4, Informative)
(Last Journal: Monday May 30 2005, @10:02AM)
Bottom line - the harmonics can be taken care of by wave-shaping, i.e. you take the output load configuration into equation as you design the radio.
Obvious Next Step (Score:2)
(http://onphilosophy.wordpress.com/)
Re:Obvious Next Step (Score:4, Insightful)
Re:Obvious Next Step (Score:4, Insightful)
(https://addons.mozil...&application=firefox)
Software radios are awesome! (Score:2, Offtopic)
(http://www.thoughtbug.com/ | Last Journal: Thursday September 27, @05:52PM)
It's the multiplexing (Score:5, Informative)
(http://www.animats.com)
It's not that a single software-defined radio is all that important. It's that you can do the transforms on the incoming waveform and then extract N different channels with one signal processing system. That's what's been making cellular base stations go for almost two decades. (All the hard work is on the receive side; transmission is easy.)
First generation cellular base stations (i.e. AMPS) had one big analog card per channel, each heavily shielded from its neighbors. The amount of hardware required was huge, and cell sites tended not to be fully populated with channel cards, so they were easy to overload.
Then things started to go digital, with combinations of analog and DSP components processing the signal. Both GSM and CDMA inherently assume digital processing, and in early systems, hard-wired special purpose components were used. As CPUs get faster, there's a steady trend toward using general purpose CPUs.
It's still rare to actually process RF directly in software. Usually, there's a local oscillator and mixer to down-convert the desired band to a working IF frequency, which is then digitized and processed. So it's only necessary to digitize at maybe 10-100MHz, not up in the gigahertz range.
For lower bands, though, a true software RF receivers [rfspace.com] are available. These just suck up everything from 0 to 30MHz and digitize it. An attached PC does all the hard work.
Re:didn't someone ... (Score:4, Interesting)
That's an oversimplification, but it may be what you were thinking of.
Two Words (Score:5, Informative)
Re:Two Words (Score:4, Informative)
You can use a capture card with a BT878 chip as a cheap entry into SDR and GNU Radio. See Here [domenech.org]
The card I have didn't require any kind of modifications, and I've successfully captured signals all the way up to about 400kHz directly from the air simply using a long wire, including digital radio (the unfortunately named DRM [wikipedia.org]) signals.
A little too much feature creep. (Score:1, Offtopic)
Companies seem to forget that there is still a market for the simple. It took me two weeks of looking to find a piece of stand alone desktop equipment that satisfactorily met the following requirements:
1) AM/FM radio
2) AC plug
3) Headphone jack
4) Let's try keeping it under $30
5) Doesn't look like crap.
Sometimes, all you want is to listen to the baseball game on the radio. I didn't want to stream online (especially paying the usurious fees charged by MLB). I didn't want to change batteries. I didn't want to bother the folks in the rest of the office. Is that too much to ask, or is it simply not sexy enough for the modern consumer electronics market?
Re:A little too much feature creep. (Score:4, Insightful)
(http://fennecfoxen.org/)
This is about radios in a variety of communication devices. Like cell phones. And cell phone towers. Especially cell phone towers. Not so much your Sony Walkman et al.
I read this and... (Score:2)
I read this and end up believing that my next radio will be delivered to me as a software printout on a sheet of paper.
Bose blows (Score:1, Informative)
Re:Bose blows (Score:5, Funny)
(http://www.the-h.net/h)
Only midrange! Must be Bose.
Cell Phones (Score:2, Interesting)
(http://geekinacan.blogspot.com/)
gnuradio (Score:2)
(Last Journal: Friday February 02 2007, @12:54AM)
if anyone's interested, more here:
http://www.gnu.org/software/gnuradio/doc/exploring-gnuradio.html [gnu.org]
and a bunch of links on wikipedia:
http://en.wikipedia.org/wiki/Gnuradio [wikipedia.org]
Not the first time I noticed this (Score:3, Interesting)
Vanu Bose's bitter battle with MIT (Score:1)
In older days, his father Amar Bose's company was made possible because MIT let him have the patent for nothing. Now that Amar is (presumably) a billionaire from his high profit-margin products that gross $600 million a year, he has donated $6 million back to MIT. Whether or not that is generous, given that MIT made it all possible, is a matter of opinion I suppose.
For those who think the Boses should have owned the patents on their technologies outright, and not MIT, it is a complicated issue. I don't know about the Bose's particular cases, but keep in mind that usually PhD theses are not developed in a vacuum: ideas are discussed, topics are suggested, usually the thesis advisor is interested in the topic if not actively working on it already, there is a support staff to help develop it, etc.
Emergency Communications (Score:3, Interesting)
(http://slashdot.org/)
The DoD's new Software-based Radio (Score:4, Interesting)
(http://nixwizard.net/)
That's a direct quote from the Wikipedia article (which looks like it's pretty accurate), located here: http://en.wikipedia.org/wiki/JTRS [wikipedia.org]
I'm in the Army, and buddies of mine have played with it and can attest that "it's pretty cool"
Software radio scaners (Score:2, Interesting)
(http://www.tampascanner.info/)
http://groups.yahoo.com/group/gnu_radio_scanner/ [yahoo.com]
This is a group looking to build on the GNU Radio blocks.
GNU Radio (Score:2)
(http://www.karastathis.org/ | Last Journal: Tuesday April 05 2005, @07:51PM)
Software replacing hardware... (Score:5, Interesting)
(Last Journal: Monday October 15, @11:53PM)
There are just two big problems that have made software control a non-starter.
First is customization. Put a spring in the mechanics of an engine, and I can replace it with a shorter/longer/stronger/weaker spring. I can heat it up to weaken it, grind it down, etc... With software, you are given a black box, binary-only, with no documentation on how it works, and definitely no common interface to access and modify it. So every time car companies add another function to their cars' onboard computers, and take away mechanical systems, there's extreme resistance, as buyers know they're out of the loop, and if they want to adjust anything, or if something should go wrong, they can only take it to the select few company-blessed shops, which have paid the necessary bribes to get enough info to do just a few basic things with the onboard computer. And you're entirely screwed if you want more changes than that, because the company doesn't WANT you to, and without man millions of dollars on the line, you're not even a blip on their radar.
Despite what many believe, cost is almost never a problem. For low cost products, low-end micro-controllers can be found for pennies, and even cheaper are the basic I/O elements like thermistors, power meters, transistors, relays, etc. Yet even the dirt cheap processors sold today can do many millions of calculations per second, far faster than could be needed for damn near any products.
Second, and perhaps more important, is reliability. Computer hardware is EXTREMELY reliable. You can go buy a dirt cheap commodity CPU, RAM and MOBO, and be pretty damn sure it will run for 20 years without a SINGLE error. The only big exception to this is power supplies... a marginal one, not supplying enough power will cause a crash, but that generallyonly happens in the case of the cheapest no-name junk. What's more, go up a small step to a high quality MOBO, ECC RAM, redundant PSUs, UPS, etc., and you'll never ever see a hardware-induced glitch.
The reliability problem comes ENTIRELY from poor software, and mostly commonly available kernels, at that. People don't want to believe that, but the facts are that computers are 100% pure math machines, and math is 100% accurate. A computer will do exactly what you tell it to do, but most people are trying to program their computer through several million lines of indirection... If you write, in hex, a simple loop with a bit of processing, a computer will run it error-free, from here until doomsday, but programing a complex system in hex is much too hard, and human programmers aren't perfect enough to do so.
The only real possibility to ensure reliability with reasonable development time is something very much like a micro-kernel. You need a tiny bit (a few hundred KBs) of EXTREMELY-thoroughly audited code, that can very strictly manage memory, do strict input and bounds checking, carefully manage communications between independent modules of code, instantly tear-down and restart any bit of code which shows the slightest signs of an error, and also strictly ensuring real-time operation.
I'm not endorsing any product here. The fact is nothing like this exists. That is why we aren't seeing mechanical systems having components being replaced by software as quickly as they can be redesigned. Open source operating systems
SDR has been around for years (Score:1)
Anyone from ACT/SDR reading this could perhaps fill in more details.
I think the company is out of business now. Here's an early press release:
http://www.rmit.edu.au/browse/News%20and%20Events%2FFor%20Media%2FNews%2Fby%20date%2F2000%2F;ID=poid0yrprddq;STATUS=A [rmit.edu.au]