What was debunked was some scam artist's idea of transmitting data not through the power line, but the EM field generated by the power line. Using wires to transmit data is a solid idea, using EM waves as a waveguide is not.
Please, RTFA!
This BitTorrent thing seems MUCH better than searching around for ISO's on ftp servers. I am averaging 220 kB/s down and 25 kB/s up, so, you can at least get 10 times as much down as up, but those numbers are basically bordering the limits of my cable connection.
I don't much about LED's used for lighting, but I know your post is based on the little LED's you use in your little electronics projects.
So, lets check out the power; you said 3 volts across the LED with 20mA through it, P=VI=(3V)(0.02A) = 0.06W
Compared to a regular 60W bulb, your effeciency is amazing! Your LED consumes 1000 times less power than the traditional bulb....Unless of course you have no idea what you are talking about.
I don't know anything about this stuff, so I don't post any BS about it. You should try the same.
It looks the author made a Web site full of examples, the wrote a Perl script to generate the book. Pretty clever way to sell 1000 pages of text, which anyone get free anyway!
Who cares if the development computer has Web access - just because the JavaDocs are in HTML doesn't meen you have to be online to read them!
Find an Internet connection, download the docs, put docs of development machine. Done, $25 and HOURS flipping through pages saved.
I can't image developing in Java with a paper copy of the API docs. Flipping through pages sucks compared to clicking on hyperlinks!
I can't see why anyone would want a paper copy of an huge API....
What you have to worry about is the Windows CE that's embedded in your onboard computer(s). That's where perceptible Windows Liscenscing fees will show up, not so much in the overhead of production.
I just happened to check out a textbook on the subject of asynchronous circuit design and so far its been pretty good (1st part of chapter 1)
Anyway it gives the benefits of asynchronous design:
Elemination of clock skew problems - the clock is a timing signal, but it takes a certain amount of time for the clock signal to propogate around the chip, so as the clock frequency goes up, this becomes a huge problem
Average-case Performance Synchronous circuits must be timed to the worst performing elements. Asynchronous circuits have dynamic speeds.
Adaptivity to processing and environmental variations Dynamic speed here againg. If temp goes down, circuit speeds up. If supply voltage goes up, speed goes up. Adapts to fastest possible speed for given conditions
Component modularity and reuse easier interface because difficulty with timing issues are avoided (handshake signals used instead).
Lower system power requirements it takes alot of power to propogate the clock signal, plus spurios transistor transistions are avoided. (MOSFETS only use considerable power when they change states).
Reduced noise All activity is locked into a single frequency in synchronous, so big current spikes cause large ammounts of noise. Good analogy is the noise of 50 marching soldiers vs. the noise of 50 people walking at their own pace. The synchronous nature of the soldiers causes the magnitude of the noise to be much greater.
Major drawback: Not enough designers with experience and lack of asynchronous design tools.
So far the book is a great read, but pretty technical (good for an EE or com sci person who's had a basic digital logic class).
The book is "Asynchronous Circuit Design" by Chris J Myers from the University of Utah.
Asynchronous circuits inherently run at the fastest possible speed, given the conditions (i.e. temperature, operating voltage), because they are self-timed, not timed by an external source.
Transistors change state faster in lower temperatures and higher voltages. Since the transistors trigger each other to change states, that automatically happens as fast as possible.
In synchrounous logic, the clock time is the assumed ammount of time of the worst case of the slowest transistor combination.
What was debunked was some scam artist's idea of transmitting data not through the power line, but the EM field generated by the power line. Using wires to transmit data is a solid idea, using EM waves as a waveguide is not. Please, RTFA!
This BitTorrent thing seems MUCH better than searching around for ISO's on ftp servers. I am averaging 220 kB/s down and 25 kB/s up, so, you can at least get 10 times as much down as up, but those numbers are basically bordering the limits of my cable connection.
I don't much about LED's used for lighting, but I know your post is based on the little LED's you use in your little electronics projects. So, lets check out the power; you said 3 volts across the LED with 20mA through it, P=VI=(3V)(0.02A) = 0.06W Compared to a regular 60W bulb, your effeciency is amazing! Your LED consumes 1000 times less power than the traditional bulb....Unless of course you have no idea what you are talking about. I don't know anything about this stuff, so I don't post any BS about it. You should try the same.
Nvidia - Random Video Card Driver?!
That's like saying that Microsoft is porting some random operating system to the Hammer architecture.
It looks the author made a Web site full of examples, the wrote a Perl script to generate the book. Pretty clever way to sell 1000 pages of text, which anyone get free anyway!
Who cares if the development computer has Web access - just because the JavaDocs are in HTML doesn't meen you have to be online to read them! Find an Internet connection, download the docs, put docs of development machine. Done, $25 and HOURS flipping through pages saved. I can't image developing in Java with a paper copy of the API docs. Flipping through pages sucks compared to clicking on hyperlinks! I can't see why anyone would want a paper copy of an huge API....
What you have to worry about is the Windows CE that's embedded in your onboard computer(s). That's where perceptible Windows Liscenscing fees will show up, not so much in the overhead of production.
- Elemination of clock skew problems - the clock is a timing signal, but it takes a certain amount of time for the clock signal to propogate around the chip, so as the clock frequency goes up, this becomes a huge problem
- Average-case Performance Synchronous circuits must be timed to the worst performing elements. Asynchronous circuits have dynamic speeds.
- Adaptivity to processing and environmental variations Dynamic speed here againg. If temp goes down, circuit speeds up. If supply voltage goes up, speed goes up. Adapts to fastest possible speed for given conditions
- Component modularity and reuse easier interface because difficulty with timing issues are avoided (handshake signals used instead).
- Lower system power requirements it takes alot of power to propogate the clock signal, plus spurios transistor transistions are avoided. (MOSFETS only use considerable power when they change states).
- Reduced noise All activity is locked into a single frequency in synchronous, so big current spikes cause large ammounts of noise. Good analogy is the noise of 50 marching soldiers vs. the noise of 50 people walking at their own pace. The synchronous nature of the soldiers causes the magnitude of the noise to be much greater.
Major drawback: Not enough designers with experience and lack of asynchronous design tools. So far the book is a great read, but pretty technical (good for an EE or com sci person who's had a basic digital logic class).The book is "Asynchronous Circuit Design" by Chris J Myers from the University of Utah.
Also I wrote a paper about this for my computer architecture class:
http://ee.okstate.edu/madison/asynch.pdf
Asynchronous circuits inherently run at the fastest possible speed, given the conditions (i.e. temperature, operating voltage), because they are self-timed, not timed by an external source. Transistors change state faster in lower temperatures and higher voltages. Since the transistors trigger each other to change states, that automatically happens as fast as possible. In synchrounous logic, the clock time is the assumed ammount of time of the worst case of the slowest transistor combination.