Hardware Lifetime and Survival: Difference between revisions
No edit summary |
RobClark200 (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
We can expect that demand for OLPC will always outstrip supply. Therefore, it is prudent to extend hardware lifetimes to the extreme, so to minimize the pressure to replace units that have failed. '''A design goal of 10 years for OLPC hardware is a reasonable target''', as there should never be any 'built-in' obsolesence'. This is another aspect of the uniqueness of the hardware design. |
We can expect that demand for OLPC will always outstrip supply. Therefore, it is prudent to extend hardware lifetimes to the extreme, so to minimize the pressure to replace units that have failed. '''A design goal of 10 years for OLPC hardware is a reasonable target''', as there should never be any 'built-in' obsolesence'. This is another aspect of the uniqueness of the hardware design. |
||
The current OLPC implementation likely has a design lifetime a little bit longer than that of commerical laptops. Does anyone really know what the design lifetime of these are now? |
|||
Three aspects are important in extending lifetime: |
|||
As successive generations of OLPC are born, ideally its creators work to improve its longevity. Three aspects are important in extending lifetime: |
|||
== Amplifying Component Lifetimes == |
== Amplifying Component Lifetimes == |
Revision as of 13:57, 8 March 2007
We can expect that demand for OLPC will always outstrip supply. Therefore, it is prudent to extend hardware lifetimes to the extreme, so to minimize the pressure to replace units that have failed. A design goal of 10 years for OLPC hardware is a reasonable target, as there should never be any 'built-in' obsolesence'. This is another aspect of the uniqueness of the hardware design.
The current OLPC implementation likely has a design lifetime a little bit longer than that of commerical laptops. Does anyone really know what the design lifetime of these are now?
As successive generations of OLPC are born, ideally its creators work to improve its longevity. Three aspects are important in extending lifetime:
Amplifying Component Lifetimes
A partial list of components and their limiting design criterion includes
- keyboard - number of keypresses
- battery - number of charge/discharge cycles, currently 2000 charge/discharge cycles
- hinges, etc - number of movements
- NAND flash - number of writes
- DRAM memory - number of writes
- enclosure buttons - number of uses
- any IC fans - hours of operation
- speaker lifetime
- microphone lifetime
- any spring-loaded battery contacts
- connector lifetimes - couple/decouple cycles (for USB, power, mic, line-out, SD Card slot)
- power block - lifetime of braided wiring, and connectors
Later hardware versions hopefully can incorporate various extended life components, as tabulated above.
Field Replaceable Modules (FRU)
This permits the efficient replacement of shorter lifetime components. Modular design
Mitigating Events that Kill Machines
Laptop vendor warranty claims could identify the most frequent kinds of events that kill laptops. Without this data, one could still guess that the following are more frequent:
- dropping laptops
- crushing laptops (sitting on them, etc)
- water seepage
- water immersion
- baking in the sun for extended periods, either open or closed
- lost within water bodies
Makers of ruggedized laptops can suggest ways to make the OLPC more rugged. Failing these dialogs, the following hardware enhancements are prioritized by relative cost/benefit:
- all connectors should be upgraded to water-proofed varieties
- all enclosure seams should be sealed - this also permits the OLPC to be washed like an animal
- additional re-enforcements (skeleton, diagonal members) to strengthen against crushing the units
- increased survival to dropping
- OLPC should be proven to survive immersions upto 5 feet of water
- OLPC should be made to float on water (being sealed, the captured air should float the unit)