Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×

Submission + - The Lost History of Sodium Wiring

Rei writes: On the face of it, sodium seems like about the worst thing you could make a wire out of — it oxidizes rapidly in air, releases hot hydrogen gas in water, melts at 97,8C, and has virtually no tensile strength. Yet, in the late 1960s and early 1970s, the Nacon Corporation did just that — producing thousands of kilometers of high-gauge sodium wiring for electrical utilities — and it worked surprisingly well.

While sodium has three times the (volumetric) resistivity of copper and nearly double that of alumium, its incredibly low density gives it a gravimetric resistivity less than a third of copper and half of alumium. Priced similar to alumium per unit resistivity (and much cheaper than copper), limitless, and with almost no environmental impact apart from its production energy consumption, sodium wiring proved to be much more flexible without the fatigue or installation damage risks of alumium. The polyethylene insulation proved to offer sufficient tensile strength on its own to safely pull the wire through conduits, while matching its thermal expansion coefficient. The wiring proved to have tamer responses to both over-current (no insulation burnoff) and over-voltage (high corona inception voltage) scenarios than alumium as well. Meanwhile, "accidental cutting" tests, such as with a backhoe, showed that such events posed no greater danger than cutting copper or alumium cabling. Reliability results in operation were mixed — while few reliability problems were reported with the cables themselves, the low-voltage variety of Nacon cables appeared to have unreliable end connectors, causing some of the cabling to need to be repaired during 13 years of utility-scale testing.

Ultimately, it was economics, not technical factors, that doomed sodium wiring. Lifecycle costs, at 1970s pricing, showed that using sodium wiring was similar to or slightly more expensive for utilities than using alumium. Without an unambiguous and significant economic case to justify taking on the risks of going larger scale, there was a lack of utility interest, and Nacon ceased production.

Comment Re:Stretching things? (Score 1) 2

Nah, when the license specify that the recipient must receive the copyright notice, the conditions and the disclaimer in the documentation and/or other material, then it is for the purpose of the recipient to read and be able to understand. If you printed the license in a completely unreadable font in the manual, then you would not comply. If you store the license completely unreadable Huffman coded inside a flash, then you would not comply.

Submission + - The secret use of Minix3 inside Intel ME can be copyright infringement 2

anjara writes: Almost all Free Software licenses (BSD,MIT,GPL...) require some sort of legal notice (legal attribution) given to the recipient of the software. Both when the software is distributed in source and in binary forms. The legal notice usually contains the copyright holder's name and the license text.

This means that it is not possible to hide and keep secret, the existence of Free Software that you have stuck into your product that you distribute. If you do so, then you are not complying with the Free Software license and you are committing a copyright infringement!

This is exactly what Intel seems to have done with the Intel ME. The Minix3 operating system license require a legal notice, but so far it seems like Intel has not given the necessary legal notices. (Probably because they want to keep the inside of the ME secret.) Thus not only is Minix3 the most installed OS on our recent x86 cpus, but it might also the most pirated OS on our recent x86 cpus!

Here is a longer explanation that I wrote:
http://www.ipwatchdog.com/2017...

Slashdot Top Deals

You know you've landed gear-up when it takes full power to taxi.

Working...